fedocal has 2025-12-31 invisibly hard-coded for meeting end dates #232
Labels
No labels
Closed As
Duplicate
Closed As
Fixed
Closed As
Insufficient data
Closed As
Invalid
easyfix
meeting
slots
timezone
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
apps/fedocal#232
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Creating new recurring events in fedocal silently fails when you don't specify an end date. This is because 2025-12-31 is invisibly hard-coded as a default value. When a meeting ends before it begins, no calendar entries are created at all.
Since this is a rarely-maintained piece of software I'd suggest changing the 2027 to 2037 in these files:
doc/usage.rst
fedocal/fedocallib/init.py
fedocal/fedocallib/dbaction.py
tests/test_fedocallib.py
There appear to also be some 2038 issues, so just s/2025/2037/ in the source tree will solve the problem.
Bah, I have the commit but:
remote: Forgejo: User 'james' is not allowed to push to branch 'master' in 'apps/fedocal'.