meshbay.git/packages/meshbay-hub/tests/test_cleanup_foreign_keys.py, branch mainMeshBay — read-only public mirrorhttps://git.meshbay.org/meshbay.git/atom?h=main2026-09-30T09:22:24Zfix: a member can no longer lock a node, crash it with a link, or stop hub cleanup2026-09-30T09:22:24ZChristophe Bessoncbesson@gmail.com2026-09-30T09:22:24Zurn:sha1:69554fac7eba6eef7eb8a1c0111c5b92e7f21256
- node: only a wrong code counts towards the join lock, now per account
(5) as well as node-wide (20), and it is consulted only when a code is
tried. Every member reconnecting gets the group key through join_request,
so a lock checked before recognition let one member refuse it to everyone.
- node: link previews read the body as a stream and stop at the cap,
counted on decoded bytes; a declared oversized image is not read; 15 s
total deadline; image decoding off the loop. `client.get` had buffered
the whole (decompressed) response before the caps looked at it.
- hub: the daily purge of never-verified accounts detaches their IP-log
rows (keeping the name) and clears every other reference first, and each
cleanup step runs on its own. On PostgreSQL the bare DELETE violated the
ip_logs foreign key and stopped every purge behind it for good.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>