Closed
Bug 833622
Opened 13 years ago
Closed 13 years ago
Bubble up proxy errors nicely
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-04-25
People
(Reporter: krupa.mozbugs, Assigned: andy+bugzilla)
References
Details
(Whiteboard: u=dev p=2)
steps to reproduce:
1. Launch marketplace-dev app on your unagi phone
2. Log in using Identity
3. Click on the purchase button for 'Private Yacht'
observed behavior:
'Something went wrong' screen is shown
traceback details:
HttpServerError: Server Error 500: https://payments-dev.allizom.org/bango/billing/ Content: {"error_code": "AttributeError", "error_data": {}, "error_message": "'NoneType' object has no attribute 'responseCode'"} : JSON: {u'error_data': {}, u'error_code': u'AttributeError', u'error_message': u"'NoneType' object has no attribute 'responseCode'"}
sentry: http://sentry.dmz.phx1.mozilla.com/marketplace-dev-webpay/group/10984/
Updated•13 years ago
|
Whiteboard: u=dev p=
Target Milestone: --- → 2013-01-24
| Assignee | ||
Comment 1•13 years ago
|
||
This was fixed yesterday, it was due to solitude deployment issues. It's not urgent but the handling of the 500 in a nicer manner is something I'd like to fix.
Assignee: kumar.mcmillan → amckay
Severity: critical → minor
Target Milestone: 2013-01-24 → 2013-01-31
| Assignee | ||
Updated•13 years ago
|
Assignee: amckay → xwraithanx
Updated•13 years ago
|
Priority: -- → P4
Updated•13 years ago
|
Whiteboard: u=dev p= → u=dev p=1
| Assignee | ||
Updated•13 years ago
|
Summary: [traceback] HttpServerError: Server Error 500: https://payments-dev.allizom.org/bango/billing/ Content: {"err... → Bubble up proxy errors nicely
Updated•13 years ago
|
Version: 1.0 → 1.1
Updated•13 years ago
|
Target Milestone: 2013-01-31 → 2013-02-14
| Assignee | ||
Updated•13 years ago
|
Version: 1.1 → 1.2
Updated•13 years ago
|
Target Milestone: 2013-02-14 → 2013-02-28
| Assignee | ||
Updated•13 years ago
|
Priority: P4 → P1
| Assignee | ||
Updated•13 years ago
|
Severity: minor → major
Target Milestone: 2013-02-28 → 2013-03-14
Comment 2•13 years ago
|
||
This has been bumped a lot. What's the status?
Target Milestone: 2013-03-14 → 2013-03-21
Comment 3•13 years ago
|
||
I am working on this today, I haven't done much with the interaction between solitude and solitude-proxy, and may need to bubble all the way to webpay depending on what we want, so it is a bit involved.
Whiteboard: u=dev p=1 → u=dev p=2
Updated•13 years ago
|
Target Milestone: 2013-03-21 → 2013-04-04
Updated•13 years ago
|
Target Milestone: 2013-04-04 → ---
Comment 4•13 years ago
|
||
This critical, we need to fix this ASAP. bug 864672 was really hard to track down.
| Assignee | ||
Updated•13 years ago
|
Assignee: wraithan → amckay
Target Milestone: --- → 2013-04-25
| Assignee | ||
Comment 5•13 years ago
|
||
https://github.com/mozilla/solitude/commit/d25161
You will get two log messages: one on the proxy and then on the client. Then there's a list of errors that are fatal from the proxy. Currently a 500 from the proxy is the only error. But its now a proxy error, not a SUDS processing error.
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•