#201 schedules its first check of automatic domains' DKIM and ACME
tasks 5 minutes after start. The JMAP suite (RocksDB) runs about 7–8
minutes, so the check fired mid-suite, queued DkimManagement for the
test domain, and the store cleanup at the end failed ("Store is not
empty": two DkimSignature objects and their indexes). Seen while
checking the v0.16.27 import; it fails the same way on main since #201.
The scheduler no longer queues that first check in test_mode builds.
The DKIM tests call check_tasks_for_domains directly, so their
coverage is unchanged; production builds behave as before.
Checked: the JMAP suite passes with this change (464 s, past the
5-minute mark); fork checks clean.
#201 schedules its first check of automatic domains' DKIM and ACME
tasks 5 minutes after start. The JMAP suite (RocksDB) runs about 7–8
minutes, so the check fired mid-suite, queued DkimManagement for the
test domain, and the store cleanup at the end failed ("Store is not
empty": two DkimSignature objects and their indexes). Seen while
checking the v0.16.27 import; it fails the same way on main since #201.
The scheduler no longer queues that first check in test_mode builds.
The DKIM tests call `check_tasks_for_domains` directly, so their
coverage is unchanged; production builds behave as before.
Checked: the JMAP suite passes with this change (464 s, past the
5-minute mark); fork checks clean.
#201 queues its first check of automatic domains' DKIM and ACME tasks
5 minutes after start. The JMAP suite runs longer than that, so the
check gave its test domain DKIM keys mid-run and the store cleanup
failed with leftover DkimSignature objects. Tests call
check_tasks_for_domains themselves.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
#201 schedules its first check of automatic domains' DKIM and ACME
tasks 5 minutes after start. The JMAP suite (RocksDB) runs about 7–8
minutes, so the check fired mid-suite, queued DkimManagement for the
test domain, and the store cleanup at the end failed ("Store is not
empty": two DkimSignature objects and their indexes). Seen while
checking the v0.16.27 import; it fails the same way on main since #201.
The scheduler no longer queues that first check in test_mode builds.
The DKIM tests call
check_tasks_for_domainsdirectly, so theircoverage is unchanged; production builds behave as before.
Checked: the JMAP suite passes with this change (464 s, past the
5-minute mark); fork checks clean.