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.

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

Homepage blog post links missing in production #10263

Open
jimchamp opened this issue Jan 3, 2025 · 2 comments
Open

Homepage blog post links missing in production #10263

jimchamp opened this issue Jan 3, 2025 · 2 comments
Labels
Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Investigation This issue/PR needs a root-cause analysis to determine a solution. [managed] Needs: Staff / Internal Reviewed a PR but don't have merge powers? Use this. Priority: 3 Issues that we can consider at our leisure. [managed] Type: Bug Something isn't working. [managed]

Comments

@jimchamp
Copy link
Collaborator

jimchamp commented Jan 3, 2025

Problem

Blog post links on the production homepage have been missing since October. These links are present in staging and testing environments. Sentry suggests that this is due to the requests to blog.openlibrary.org timing out.

image

Reproducing the bug

  1. Go to https://openlibrary.org
  2. Scroll to the bottom of the page and observe.
  • Expected behavior: One sees links to three recent blog posts
  • Actual behavior: One sees no direct links to recent blog posts

Context

  • Browser (Chrome, Safari, Firefox, etc): Any
  • OS (Windows, Mac, etc): Any
  • Logged in (Y/N): N
  • Environment (prod, dev, local): prod

Breakdown

Update rules to allow production instances of Open Library to make requests to blog.openlibrary.org.

Requirements Checklist

  • [ ]

Related files

Stakeholders


Instructions for Contributors

  • Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
@jimchamp jimchamp added Type: Bug Something isn't working. [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Needs: Lead Needs: Staff / Internal Reviewed a PR but don't have merge powers? Use this. labels Jan 3, 2025
@Craig-Rosario
Copy link
Contributor

image
Seems to work now?

@jimchamp
Copy link
Collaborator Author

jimchamp commented Jan 3, 2025

Thanks @Craig-Rosario!

It looks like this is happening intermittently. I was also able to see the links. After refreshing the page, they were again missing.

@mekarpeles mekarpeles added Needs: Investigation This issue/PR needs a root-cause analysis to determine a solution. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] and removed Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Needs: Lead labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Lead: @jimchamp Issues overseen by Jim (Front-end Lead, BookNotes) [managed] Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Investigation This issue/PR needs a root-cause analysis to determine a solution. [managed] Needs: Staff / Internal Reviewed a PR but don't have merge powers? Use this. Priority: 3 Issues that we can consider at our leisure. [managed] Type: Bug Something isn't working. [managed]
Projects
None yet
Development

No branches or pull requests

3 participants