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

2 users cant checkout after v3 deployment in AUS - bugsnag UnhandledRejection/checkout #5772

Closed
luisramos0 opened this issue Jul 15, 2020 · 2 comments
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.

Comments

@luisramos0
Copy link
Contributor

Description

I am a bit puzzled by these two users that did not manage to checkout in AUS in the last 24 hours...
https://app.bugsnag.com/yaycode/open-food-network-js-australia/errors/5e830917206643001787799f?filters[event.since][0]=30d&filters[error.status][0]=open&pivot_tab=event
This could be an S1/S2 in v3...  only 2 users, stripe payments. 3 retries for each of these 2 users, no success as far as I can see.
The 7th event on the list (3rd user) managed to checkout on a second attempt.

The problem is that this error UnhandledRejection/checkout was not happening in v2 after 2 of my javascritpt PRs improving checkout code... so, it's a new type of error where the server returns 404. I may be missing something.

Expected Behavior

Actual Behaviour

Steps to Reproduce

Animated Gif/Screenshot

Workaround

Severity

Your Environment

  • Version used:
  • Browser name and version:
  • Operating System and version (desktop or mobile):

Possible Fix

@luisramos0 luisramos0 added v3-regression bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround. labels Jul 15, 2020
@RachL
Copy link
Contributor

RachL commented Jul 21, 2020

@luisramos0 as we decided in delivery train I'm closing this one as there hasn't been any more report, and probably linked to #5785 . Please reopen if I've misunderstood.

@RachL RachL closed this as completed Jul 21, 2020
@luisramos0
Copy link
Contributor Author

yes, let's keep it closed. We can reopen if/when the bugsnag alert appears again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.
Projects
None yet
Development

No branches or pull requests

2 participants