Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Past proceedings URLs are broken #55

Closed
matthewfeickert opened this issue Mar 10, 2024 · 6 comments · Fixed by #56
Closed

Past proceedings URLs are broken #55

matthewfeickert opened this issue Mar 10, 2024 · 6 comments · Fixed by #56
Labels
bug

Comments

@matthewfeickert
Copy link
Contributor

matthewfeickert commented Mar 10, 2024 •
edited
Loading

One of the projects I work on uses sphinx's linkcheck to validate all the URLs in our docs. We noticed that the URLs that link to the conference proceedings have started to fail the linkcheck

...
2024-03-10T06:07:22.7942075Z (        outreach: line   60) broken    http://conference.scipy.org/proceedings/scipy2019/slides.html - 404 Client Error: Not Found for url: https://conference.scipy.org/proceedings/scipy2019/slides.html
2024-03-10T06:07:22.9437406Z (       citations: line   25) ok        https://arxiv.org/abs/2103.12504
2024-03-10T06:07:22.9849483Z (        outreach: line   39) broken    http://conference.scipy.org/proceedings/scipy2020/slides.html - 404 Client Error: Not Found for url: https://conference.scipy.org/proceedings/scipy2020/slides.html
...

and currently all the links on https://conference.scipy.org/proceedings/ (e.g. https://conference.scipy.org/proceedings/scipy2023 fail with a 404).
@matthewfeickert matthewfeickert mentioned this issue Mar 10, 2024
Open
@achabotl
Copy link
Member

achabotl commented Mar 11, 2024 •
edited
Loading

The proceedings pages were hosted on an Enthought-owned S3 bucket. When we changed the DNS to publish this site to Github pages, the proceedings links broke.

I made a local copy of all the proceedings pages, but we have a problem due to GitHub Pages limits. A Pages site can have a max size of 1GB and all proceedings add up to ~900 MB.

Looks like we'll have to go the S3 route.

We can't transfer ownership of a bucket, only of objects. In fact, the recommended thing to do is to sync two buckets, effectively copying all the files.

Investigation continues.

@achabotl
Copy link
Member

I'll temporarily try to write a redirect to missing pages until we have a solution.

@achabotl achabotl mentioned this issue Mar 11, 2024
Merged
@achabotl
Copy link
Member

A minimal redirect like this doesn't work by default. Pelican wants more metadata

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="refresh" content="0; url='http://conference.scipy.org.s3-website-us-east-1.amazonaws.com/proceedings/scipy2023/'" />
  </head>
  <body>
    <p>You will be redirected soon!</p>
  </body>
</html>

@matthewfeickert
Copy link
Contributor Author

Reopening given PR #56 isn't enough to fully close.

@bsipocz bsipocz added the bug label Mar 13, 2024
@achabotl
Copy link
Member

@matthewfeickert I think this will be "fixed" by #56. That PR is not the real solution, but it's better than completely broken.

@achabotl achabotl mentioned this issue Mar 19, 2024
Open
@matthewfeickert
Copy link
Contributor Author

Thanks very much, @achabotl!

That PR is not the real solution, but it's better than completely broken.

Yes, agreed. We can close this one and move watching over to Issue #58 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Experiment: Temporarily redirect a missing proceedings page scipy-conference/conference.scipy.org
3 participants
@achabotl @matthewfeickert @bsipocz