Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Topology needs a bounded link snapshot so a 24-hour view does not page through every route and exhaust the shared request budget. Add
GET /api/v1/routes/topologyfor deduplicated adjacent links, with validated region/window filters, a 100,000-link cap and short cache. Expose cached MeshMapper scope catalogue metadata and mark channel messages decrypted with the default Public key for the paired web view.The dev1 audit also found malformed TRACE payloads resolving into confident routes, including unvisited requested hops. Validate TRACE structure using its own 1/2/4/8-byte hash widths, retain all identity candidates, and promote only consumed, unambiguous hops. Retained raw observations are preserved and receive quality reasons; this does not prove RF corruption or remove historical neighbour aggregates. Fixes #223.
Paired frontend: MeshCore-Beacon/beacon-web#165. Targets the new
dev1baseline at the current upstream server revision. Preview version: 2.1.0-dev1.1 (API version 2.1.0). No schema, retention, Collector or credentials changes.Validation: build, format, vet, full Go suite, PostgreSQL topology/trace-quality regressions, existing database and backup tests, scope refresh race tests, vulnerability scan and generated Swagger all passed in CI. The exact candidate image passed its Actions build. The qualified candidate is now deployed on dev1.meshcore.ca; see runtime evidence below.
Runtime qualification: deployed v2.1.0-dev1.1, web
33793697e721498d30b2a2a33013c1448b158fc2and server1d3f7ce6211bce9a3bb8fc0693eb4d10965c3fac, using digest-pinned Actions images. All 27 public assets match. The sampled 24h snapshot returned 8,029 links in 0.967s without a cap. Both MQTT brokers are connected and app/web have zero restarts. Desktop/narrow Topology, pan/orbit/zoom, fullscreen, global-region focus reset, live activity, Atlas persistence/Heard by and suspect-trace reveal/analyzer checks passed. A naturally received Public message included the required metadata; automated tests cover bubble rendering/expiry.Only dev1 app/web changed; schema, data, retention, configuration, other containers and Pi/production were preserved. Saved prior images were load-verified; a fresh database archive passed full stream validation and a separate schema restore. The paired rollback checkpoint is retained privately. This is an open-PR candidate deployment, not a merge into
dev1.Separate release concerns remain: #224 (route reconfirm timeouts) and #226 (synchronous boot backfill, about 159 seconds to readiness in this rollout). Those are not claimed fixed by this PR.