I'm preparing a new French translation for publication, but I'm encountering a problem with our system of using nbviewer to render ipynb notebooks in lessons.
The structure is identical, so I am confident that my URL construction is correct.
I note that there seem to be a lot of people raising Issues on nbviewer's repository.... https://github.com/jupyter/nbviewer/issues including multiple 503: Service Unavailable reports, and a 400: Bad Request server certificate verification failed report. This isn't very promising and indicates ongoing problems (nothing specific to my file).
One observation is that older nbviewer links in our repository still work, so their system outage isn't generalised – it is only affecting newly generated links. Maybe nbviewer is using cache to serve old links?
This problem on nbviewer's side may well be temporary. I think the best thing to do for the moment might be to link directly to the GitHub rendering of the notebook instead: https://github.com/programminghistorian/jekyll/blob/gh-pages/assets/vision-par-ordinateur-apprentissage-profond-pt1-2/vision-par-ordinateur-apprentissage-profond-pt1-2.ipynb (even though it is a less elegant solution).
When the problem is resolved, our link should start working. So, we could merge the PR #3755 without the nbviewer link for now, and then I can follow up to add it back in next week.
In the longer-term, maybe we need to consider some alternatives to nbviewer? What do you think, @rivaquiroga?
I'm preparing a new French translation for publication, but I'm encountering a problem with our system of using nbviewer to render
ipynbnotebooks in lessons.The English original's nbviewer link still works:
But this one for the French translation is failing:
The structure is identical, so I am confident that my URL construction is correct.
I note that there seem to be a lot of people raising Issues on nbviewer's repository.... https://github.com/jupyter/nbviewer/issues including multiple 503: Service Unavailable reports, and a 400: Bad Request server certificate verification failed report. This isn't very promising and indicates ongoing problems (nothing specific to my file).
One observation is that older nbviewer links in our repository still work, so their system outage isn't generalised – it is only affecting newly generated links. Maybe nbviewer is using cache to serve old links?
This problem on nbviewer's side may well be temporary. I think the best thing to do for the moment might be to link directly to the GitHub rendering of the notebook instead: https://github.com/programminghistorian/jekyll/blob/gh-pages/assets/vision-par-ordinateur-apprentissage-profond-pt1-2/vision-par-ordinateur-apprentissage-profond-pt1-2.ipynb (even though it is a less elegant solution).
When the problem is resolved, our link should start working. So, we could merge the PR #3755 without the nbviewer link for now, and then I can follow up to add it back in next week.
In the longer-term, maybe we need to consider some alternatives to nbviewer? What do you think, @rivaquiroga?