Skip to content

Conversation

@crankynetman
Copy link
Collaborator

To clean things up, at the cost of negligible resources, we now reprocess updates regardless of which host it came from, to ensure consistency and fix a bug where we were assuming that the instance a block was created on is the instance a block will be deactivated from.

@crankynetman crankynetman marked this pull request as ready for review January 13, 2026 22:39
@github-actions
Copy link

File Coverage
All files 83%
config/consumers.py 78%
config/urls.py 69%
config/settings/base.py 69%
config/settings/local.py 72%
scram/route_manager/admin.py 71%
scram/route_manager/models.py 79%
scram/route_manager/views.py 88%
scram/route_manager/api/serializers.py 92%
scram/route_manager/api/views.py 76%
scram/shared/shared_code.py 56%
scram/templates/403.html 91%
scram/templates/404.html 91%
scram/templates/base.html 99%

Minimum allowed coverage is 50%

Generated by 🐒 cobertura-action against 4daa366

Copy link
Collaborator

@samoehlert samoehlert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crankynetman crankynetman merged commit 0884f16 into main Jan 14, 2026
17 of 19 checks passed
@crankynetman crankynetman deleted the fix/chriscummings/process_updates_yet_again branch January 14, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants