team defaultexpirationdate in production can be insane for historical reasons
Bug #690743 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Curtis Hovey |
Bug Description
OOPS-1808A1755
Module lp.registry.
may_
Module lp.registry.
expires = self.defaultexp
Module lp.registry.
return datetime.
OverflowError: date value out of range
shows In the past users, could create defaultexpirati
We need a SQL query that updates defaultexpirati
tags: | added: teams |
summary: |
- defaultexpirationdate in production can be insane for historical reasons + team defaultexpirationdate in production can be insane for historical + reasons |
Changed in launchpad: | |
milestone: | none → 11.01 |
assignee: | nobody → Curtis Hovey (sinzui) |
status: | Triaged → In Progress |
Changed in launchpad: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
defaultexpirati ondate is set from defaultmembersh ipperiod
days = self.defaultmem bershipperiod now(pytz. timezone( 'UTC')) + timedelta(days)
if days:
return datetime.
The max value for defaultmembersh ipperiod is 3650, but historically, users could put impossible numbers in this field. These values could have worked for a few years, but as time passes, the values are incrementing the timestamps out the the range supported by Python 2.x.
The team in the oops (~ubuntu-l10n-gu) has fixed its data, but there are 8 other teams that still need fixing: ipperiod > 3650; ------- ------
select name from person where defaultmembersh
name
-------
scratchcoding
nasar-merged
mythbuntu-web-devs
osama2006
creatorsdevelopers
saurav
ailurus-developers
robonexus