to spicy up this problem a bit — these kinds of packets only came from remoteterm, mqtt-enabled observers do not produce these
to spicy up this problem a bit — these kinds of packets only came from remoteterm, mqtt-enabled observers do not produce these
<!-- github-comment-id:4444740870 -->
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.
sometimes remoteterm receives packet and cannot decrypt it. but at the same time this packet is sent to mqtt causing some strange behavior.
remoteterm-1 | 2026-05-12 15:11:13 - app.packet_processor - WARNING - Failed to parse 137-byte packet (id=1214846); stored undecrypted
remoteterm-1 | 2026-05-12 15:16:01 - app.packet_processor - WARNING - Failed to parse 146-byte packet (id=1215039); stored undecrypted
remoteterm-1 | 2026-05-12 15:22:49 - app.packet_processor - WARNING - Failed to parse 153-byte packet (id=1215453); stored undecrypted
remoteterm-1 | 2026-05-12 15:25:43 - app.packet_processor - WARNING - Failed to parse 93-byte packet (id=1215667); stored undecrypted
i'm not sure what to do with this but probably you can check it's expected behavior or not
to spicy up this problem a bit — these kinds of packets only came from remoteterm, mqtt-enabled observers do not produce these
Whoops yeah, we shouldn't be forwarding garbage.