Skip to content

fix: Health check config collides between two targets sharing the same backen... - #462

Merged
oschwartz10612 merged 1 commit into
fosrl:mainfrom
Roshan931:prilog/fix-error-newt-wg-connect-payload-decoded-into-10-06-2026-1e998b
Oct 12, 2026
Merged

oschwartz10612 merged 1 commit into
fosrl:mainfrom
Roshan931:prilog/fix-error-newt-wg-connect-payload-decoded-into-10-06-2026-1e998b

Conversation

@Roshan931

Copy link
Copy Markdown
Contributor

Fixes #411

Root cause

newt/wg/connect payload decoded into persistent n.wgData, merging JSON arrays by position

Changes

  • Decode the registration payload into a fresh WgData and assign it only on success (applyWgData), eliminating encoding/json positional slice merging and no-op null scalar decodes; added regression tests covering the reordered health-check payload, stale field clearing, and error paths.

Signed-off-by: Robert Markovski <5818108+Roshan931@users.noreply.github.com>
@oschwartz10612
oschwartz10612 merged commit 514dd0d into fosrl:main Oct 12, 2026
13 checks passed
@oschwartz10612

Copy link
Copy Markdown
Member

Thanks!

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.

Health check config collides between two targets sharing the same backend host:port on reconnect/reload

2 participants