heyaim 7cff2e3987 Handle relay port integer overflow without aborting parsing ...

A relay row with valid coordinates and a digit-only port outside the
integer range caused directory parsing to throw a NumberFormatException.
The surrounding load handlers caught the exception, but that parse
returned no relay list. This did not establish an application crash or a
delivery failure.

Changed the conversion to skip that row. Added a regression containing
valid rows before and after it, plus ordinary-port controls. Narrowed
the source, selection and test descriptions: sharing a source alone does
not establish equal loaded snapshots or successful message delivery.
Used the Kotlin preferences helper for asynchronous writes.

The integer-overflow port test reproduced the parsing failure before the
fix and passed afterward. The full test suites passed with three
unrelated skips, and debug builds passed. Lint reported errors and
warnings, with none in the changed files. Required physical Mesh Lab
validation remains unperformed.

2026-10-10 10:08:24 -05:00

..

DISCUSSION_TEMPLATE

Update references to new GitHub organization in project files.

2025-07-11 22:31:38 +02:00

ISSUE_TEMPLATE

Update references to new GitHub organization in project files.

2025-07-11 22:31:38 +02:00

workflows

Handle relay port integer overflow without aborting parsing

2026-10-10 10:08:24 -05:00

pull_request_template.md

Update references to new GitHub organization in project files.

2025-07-11 22:31:38 +02:00