Jennifer Richards
Jennifer Richards
I believe the 1970-01-01 date is because there is not yet an agenda for IETF 114. This should probably be indicated instead of displaying a bogus timestamp. For https://datatracker.ietf.org/meeting/113/agenda/, the...
Poking, there's an attempt to hide the "updated" indicator if `meeting.updated()` is not defined. Unfortunately, the `updated()` method returns 1970-01-01T00:00:00 rather than`None` in that situation, which defies the effort.
It localizes to `PRODUCTION_TIMEZONE`, so won't change due to the `USE_TZ` settings. It'd be nice to change it to be explicitly UTC instead of something that depends on `settings.py` if...
Starting to look at what's involved here. My initial musing is that it might be most straightforward to create some phony non-persisted `TimeSlot` instances with a flag to indicate that...
I think that would be fantastic. It might be a bit nontrivial to track down the places we need to seed - I know we import random and use it...
It looks like the base for that branch is out of date. On main, the urllib3 exception is converted to a warning (https://github.com/ietf-tools/datatracker/blob/5b6695a04c46e1756183272e8da4195f1ebea1a7/ietf/settings.py#L16) and the ci-run-tests workflow was modified to...
May need to update your fork to see the changes.
Yeah, it looks like it should be working. Looking at it.
It looks like it's checking out https://github.com/larseggert/datatracker/commit/0ba50999d93f1bd210c15d5590cf1d9a8ca89e08 to run the tests. That is old and not the branch in this PR. Not sure why that's happening. (I hadn't noticed this...