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

[BUG] This Page encountered an Error! Sorry! #200

Closed
1 of 3 tasks
zhaolinlau opened this issue Sep 10, 2023 · 2 comments
Closed
1 of 3 tasks

[BUG] This Page encountered an Error! Sorry! #200

zhaolinlau opened this issue Sep 10, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@zhaolinlau
Copy link

Is this Bug Present in the upstream API Server?

  • Yes
  • No
  • Unsure

What is the Bug
Most of the package links cannot be accessed

How to Replicate the Bug

  1. browse https://web.pulsar-edit.dev/
  2. click any of the packages
  3. then it will say "This Page encountered an Error! Sorry!"
    image
@zhaolinlau zhaolinlau added the bug Something isn't working label Sep 10, 2023
@zhaolinlau zhaolinlau changed the title [BUG] **This Page encountered an Error! Sorry!** [BUG] This Page encountered an Error! Sorry! Sep 10, 2023
@confused-Techie
Copy link
Member

Thanks a ton for reporting this.

This is an error we have seen once before, where our autoscaling cluster of instances will create on bad instance. Essentially creating the chance that anyone that happens to be connected to that bad instance will have every single page fail. Meanwhile every other instance is still healthy, so to others there is no issue.

The problem does eventually resolve itself once there is low usage and the instance is killed, which is exactly what's happened in this case.

But as we currently have no idea what causes this to happen, or how we can fix it, I'll go ahead and leave this issue open until we are able to do something to mitigate this issue.

Thanks a ton for reporting this!

@confused-Techie
Copy link
Member

While the root cause of this issue hasn't been totally addressed, since the implementation of improved error handling, and providing much better logging, as well as returning errors to the user in a better way has been added, I'll go ahead and close this one for now.

While the root cause of this issue may still appear, we will now be much more equipped to actually solve it, and I feel like this is the best place for us to close this issue, since it's possible the issue may not return.

Thanks a ton again for reporting this, resolve via pulsar-edit/package-frontend#123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants