Www.julialang.org: Dead links

Created on 13 Mar 2020  ·  9Comments  ·  Source: JuliaLang/www.julialang.org

In the process of #655 I was checking links with blc

It's a bit finicky and sometimes just crashes so one may have to restart it with exclusion rules via --exclude URL1 --exclude URL2 etc.

A partial dump of what I could check below, not sure what to do about it. Some of these have just ceased to exist, and so it's probably fine to leave them dead... but some I feel could be fixed eventually.

Getting links from: https://julialang.netlify.com/community/
├─BROKEN─ https://www.meetup.com/Bangalore-Julia-User-Group/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Juliadelhi/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Singapore-Julia-User-Group/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/JuliaStanbul/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Montreal-Julia-Programming-Language-Meetup/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Machine-Deep-Learning-an-Introduction/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Vancouver-Julia-Users/ (HTTP_404)
├─BROKEN─ https://www.meetup.com/Julia-lang-bsb/ (HTTP_404)

Getting links from: https://julialang.netlify.com/learning/
├─BROKEN─ https://www.youtube.com/watch?v=0-Xsts_s5W (HTTP_404)
├─BROKEN─ https://syl1.gitbook.io/julia-language-a-concise-tutorial/ (HTTP_204)
├─BROKEN─ https://www.packtpub.com/application-development/mastering-julia-10 (HTTP_404)


Getting links from: https://julialang.netlify.com/research/
├─BROKEN─ https://dx.doi.org/https:/doi.org/10.1016/j.softx.2019.03.005 (HTTP_404)
├─BROKEN─ https://dx.doi.org/https:/doi.org/10.1016/j.trb.2016.07.003 (HTTP_404)
├─BROKEN─ https://eprints.ma.man.ac.uk/2426 (ERRNO_ECONNREFUSED)

Getting links from: https://julialang.netlify.com/blog/2019/09/profilers/
├─BROKEN─ https://www.brendangregg.com/flamegraphs.html (ERRNO_EPROTO)
├─BROKEN─ https://www.brendangregg.com/perf.html (ERRNO_EPROTO)
├─BROKEN─ https://www.brendangregg.com/flamegraphs.html (HTTP_undefined)
├─BROKEN─ https://github.com/JuliaLang/julia/tree/jn/profile-recurflat (HTTP_404)
├─BROKEN─ https://docs.junolab.org/stable/man/juno_frontend.html#Profiler-1 (HTTP_404)

Getting links from: https://julialang.netlify.com/blog/2019/09/julia-workshop-beijing-zh_cn/
├─BROKEN─ https://www.bilibili.com/video/av65371788 (HTTP_403)

Getting links from: https://julialang.netlify.com/blog/2019/09/julia-workshop-beijing/
├─BROKEN─ https://www.bilibili.com/video/av65371788 (HTTP_403)

Getting links from: https://julialang.netlify.com/blog/2019/07/multithreading-zh-cn/
├─BROKEN─ https://www.gotw.ca/publications/concurrency-ddj.htm (ERRNO_EPROTO)
├─BROKEN─ https://julialang.netlify.com/blog/2019/07/multithreading-zh-cn/TBB (HTTP_404)
├─BROKEN─ https://www.intel.com/ (HTTP_404)

Getting links from: https://julialang.netlify.com/blog/2019/07/multithreading/
├─BROKEN─ https://www.gotw.ca/publications/concurrency-ddj.htm (HTTP_undefined)
├─BROKEN─ https://cilk.mit.edu/ (HTTP_undefined)
├─BROKEN─ https://julialang.netlify.com/blog/2019/07/multithreading/TBB (HTTP_404)
├─BROKEN─ https://www.intel.com/ (HTTP_404)

Getting links from: https://julialang.netlify.com/blog/2019/05/jsoc19/
├─BROKEN─ https://sharanry.github.io/post/ (HTTP_404)
├─BROKEN─ https://towardsdatascience.com/@saumyagshah (HTTP_409)
├─BROKEN─ https://retiredparkingguard.com/posts/index.html (HTTP_522)

Getting links from: https://julialang.netlify.com/blog/2019/05/beyond-ml-pipelines-with-mlj/
├─BROKEN─ https://github.com/alan-turing-institute/MLJ.jl/blob/master/docs/src/tour.ipynb (HTTP_404)
├─BROKEN─ https://github.com/alan-turing-institute/MLJ.jl/blob/master/examples/random_forest.ipynb (HTTP_404)
├─BROKEN─ https://github.com/alan-turing-institute/MLJ.jl/blob/master/CONTRIBUTE.md (HTTP_404)
├─BROKEN─ https://alan-turing-institute.github.io/MLJ.jl/dev/learning_networks/ (HTTP_404)

Getting links from: https://julialang.netlify.com/blog/2019/04/fluxdiffeq-zh_tw/
├─BROKEN─ https://docs.juliadiffeq.org/latest/features/monte_carlo.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/features/callback_functions.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/tutorials/ode_example.html (HTTP_404)
├─BROKEN─ https://julialang.netlify.com/blog/2019/04/fluxdiffeq-zh_tw/(https:/docs.juliadiffeq.org/latest/solvers/dynamical_solve.html#Symplectic-Integrators-1) (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/solvers/split_ode_solve.html#Implicit-Explicit-(IMEX)-ODE-1 (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/tutorials/dde_example.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/tutorials/sde_example.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/tutorials/discrete_stochastic_example.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/tutorials/jump_diffusion.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/analysis/sensitivity.html (HTTP_404)
├─BROKEN─ https://docs.juliadiffeq.org/latest/features/callback_functions.html (HTTP_404)

Getting links from: https://julialang.netlify.com/blog/2019/02/julia-entities/
├─BROKEN─ https://www.linkedin.com/in/keno-fischer-974261b0/ (HTTP_999)
├─BROKEN─ https://www.linkedin.com/in/deepakvinchhi/ (HTTP_999)

All 9 comments

Linkedin is just weird. I bet you those links are fine.

@ChrisRackauckas Did you change those URLs?

LinkedIn requires the user to log in. So the link is fine but the response is different.

I think we can keep a separate job in CI to check for dead links. I was using htmltest where we could simply pass the bad external links while they're still being tested. Every failing internal link will fail the job. So it will be a good check imo.

Maybe point to stable version if possible?

I believe I fixed all the wrong links pointing to docs.juliadiffeq.org (probably a good idea to double check) #664

The link to the license in the footer is also broken.

The content on this website is made available under the MIT license.

The link to the license in the footer is also broken.

The content on this website is made available under the MIT license.

I'll fix that asap; edit: fixed

I'll close this, I think the most reasonable way about it is to go page by page and fix everything. The hardest will be /blog/ as there are so many pages but I guess we could split the work by looking by year. I'll open an issue to try to organise the work.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

PallHaraldsson picture PallHaraldsson  ·  6Comments

ViralBShah picture ViralBShah  ·  7Comments

ExpandingMan picture ExpandingMan  ·  7Comments

essenciary picture essenciary  ·  8Comments

jekbradbury picture jekbradbury  ·  7Comments