Workaround for a concurrency bug with date parsing

[mitsuhiko]

This is needed because otherwise sometimes we fail parsing timestamps
that would otherwise be valid. Mostly happens after interpreter
startup if there are multiple threads doing stuff.

@getsentry/infrastructure

---

This change is

[mattrobenolt]

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable

[mattrobenolt]

I TRUST IN YOU ARMIN

[mattrobenolt]

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

---

src/sentry/wsgi.py, line 18 [r1] (raw file):

We need to run this here because of a concurrency bug in Python's locale

with the lazy initialization.

datetime.datetime.strptime('', '')

Should we put this in runner/__init__.py instead? This code is only run for the wsgi interface, so it won't get applied for say, async workers or other standalone scripts. But runner/__init__.py is executed for everything.

---

Comments from Reviewable

[mitsuhiko]

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

---

src/sentry/wsgi.py, line 18 [r1] (raw file):

Previously, mattrobenolt (Matt Robenolt) wrote…

We need to run this here because of a concurrency bug in Python's locale

with the lazy initialization.

datetime.datetime.strptime('', '')

Should we put this in runner/__init__.py instead? This code is only run for the wsgi interface, so it won't get applied for say, async workers or other standalone scripts. But runner/__init__.py is executed for everything.

Done.

---

Comments from Reviewable

[dcramer]

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

---

Comments from Reviewable