diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-23 11:36:45 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-23 12:05:31 +0000 |
| commit | 49401286ea7413f834197e6a5b221649e10e2ad8 (patch) | |
| tree | 5ce1f92c6819a59f0372eb9b2c337c8346fae9e3 /docs/archive/2026-01-relay-ngit-dev-migration/scripts | |
| parent | 70749ea9df1f6061c332112c617b615f91d79d48 (diff) | |
fix: promote purgatory announcements after git sync copy path
When a state event arrives and the required commits already exist in
another maintainer's repo on the same relay, process_state_with_git_data
copies the OIDs across and aligns refs — but never called
process_purgatory_announcements for the target repos. Any announcement
waiting in purgatory for that repo stayed there indefinitely.
Fix: after process_state_with_git_data, call process_newly_available_git_data
for each target repo (those that received copied OIDs) so purgatory
announcements are promoted immediately.
Diffstat (limited to 'docs/archive/2026-01-relay-ngit-dev-migration/scripts')
0 files changed, 0 insertions, 0 deletions