Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

JSONResponseError: 400 Bad Request #703

Closed
bbangert opened this issue Oct 13, 2016 · 3 comments · Fixed by #718
Closed

JSONResponseError: 400 Bad Request #703

bbangert opened this issue Oct 13, 2016 · 3 comments · Fixed by #718
Assignees
Labels

Comments

@bbangert
Copy link
Member

Occasionally requests have a token error, these should be caught since they're not addressable bugs.

Most likely in track_provisioned so they can be logged out appropriately for ops to look at if desired.

See: https://sentry.prod.mozaws.net/operations/autopush-prod/issues/358013/

@pjenvey
Copy link
Member

pjenvey commented Oct 17, 2016

@pjenvey pjenvey self-assigned this Oct 18, 2016
@pjenvey pjenvey added in progress and removed ready labels Oct 18, 2016
@pjenvey
Copy link
Member

pjenvey commented Oct 18, 2016

I see sentry entries for db calls: all_channels, fetch_messages, fetch_notifications, register_user

These come from websocket. endpoint/web.base already traps the parent BotoServerError

track_provisioned should increase a metric and reraise, then websocket can handle as it likes

pjenvey added a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
pjenvey added a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
pjenvey added a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
@pjenvey
Copy link
Member

pjenvey commented Oct 20, 2016

actually any db call can trigger this

https://sentry.prod.mozaws.net/operations/autopush-prod/issues/360478/

pjenvey added a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
pjenvey added a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
bbangert pushed a commit that referenced this issue Oct 20, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
jrconlin pushed a commit that referenced this issue Oct 21, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
jrconlin added a commit that referenced this issue Oct 21, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
jrconlin added a commit that referenced this issue Oct 21, 2016
have websocket log them instead of passing along to sentry and give them
a metric

closes #703
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants