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

Research: Handle 500s #164

Open
cavis opened this issue Nov 18, 2024 · 2 comments
Open

Research: Handle 500s #164

cavis opened this issue Nov 18, 2024 · 2 comments
Labels
Level: Intermediate Smooth for some, bumpy for others Priority: Normal Cruising speed Size: S Less than a day

Comments

@cavis
Copy link
Member

cavis commented Nov 18, 2024

When an RSS url returns a 500 (or a connection timeout as recently seen)... we should:

  • Log a warning (so we can track in CloudWatch)
  • Return a 200 to the user (or a different non-5XX?)
  • Render a nice error message for the user

That way we get visibility into these, but don't have to sift through a bunch of 5XX alarms on our side.
@cavis
Copy link
Member Author

cavis commented Dec 2, 2024

Update: these 500s are coming from our own proxy. So the frontend is requesting the proxy, and the proxy gets an ECONNRESET or somethnig.

@cavis cavis changed the title Handle 500s Research: Handle 500s Dec 2, 2024
@cavis
Copy link
Member Author

cavis commented Dec 2, 2024

Update 2: this is now a research. Can we track these down? If not, can we have the client retry the proxy request a couple times?

@cavis cavis added Level: Intermediate Smooth for some, bumpy for others Size: S Less than a day Priority: Normal Cruising speed labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Level: Intermediate Smooth for some, bumpy for others Priority: Normal Cruising speed Size: S Less than a day
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cavis