Closed Bug 1221396 Opened 9 years ago Closed 6 years ago

Categories

(developer.mozilla.org Graveyard :: General, defect)

All
Other
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: 446240525, Unassigned)

References

Details

(Keywords: in-triage, Whiteboard: [specification][type:bug])

What did you do?
================
Open https://developer.mozilla.org/en-US/docs/feeds/json/all

What happened?
==============
500 INTERNAL SERVER ERROR

What should have happened?
==========================
Returns the feeds as json format.

Is there anything else we should know?
======================================
https://developer.mozilla.org/zh-CN/docs/feeds/json/all doesn't have this problem.
:robhudson, can you paste a traceback?

This is intermittent -- not happening for everyone all the time. If it is preventing people from doing work, let's promote to major and put in dev inbox.
Severity: normal → minor
Flags: needinfo?(robhudson)
Keywords: in-triage
For what it's worth, it worked for me just now, but Rob Hudson just had it ISE right before I tried it. Weird.
I saw an error come in for this via Sentry:

https://errormill.mozilla.org/mdn/mdn/group/409935/

ERROR: AmbiguousTimeError: 2015-11-01 01:33:08
Flags: needinfo?(robhudson)
Is this problem still occurring?
Yes. We've switch Sentry instances, now tracked at:

https://sentry.prod.mozaws.net/operations/mdn-prod/issues/222629/

It is blocked by adding timezone-aware date times to Kuma, which is tracked in confidential bug 1142203.  A severely out-of-date PR is at mozilla/kuma#3334.
Depends on: 1385951
I've implemented an alternate fix in bug 1173189, where I just handle AmbiguousTimeErrors from the transition from daylight saving time to standard time (early November in the US). Timezone-aware datetimes will have to wait a bit longer.
Status: NEW → RESOLVED
Closed: 6 years ago
Depends on: 1173189
No longer depends on: 1385951
Resolution: --- → FIXED
See Also: → 1385951
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.