local: Matomo analytics tracking (never push upstream)#4
Merged
Conversation
Injects Matomo snippet (analytics.fiten.eu, site ID 8) before </body>. This commit is local-only — keep on origin/master and deploy branches, never cherry-pick to upstream PRs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Kpa-clawbot
pushed a commit
that referenced
this pull request
May 16, 2026
… — failure observability, lock granularity, single cutoff, atomic contract Five-in-one because they all touch the same hot-startup data flow: #3 backgroundLoadFailed flag: surfaced in /api/perf map and the typed PerfPacketStoreStats struct. Set true iff at least one chunk errored during loadBackgroundChunks. backgroundLoadComplete now only signals 'the loader returned', backgroundLoadFailed signals data integrity. #4 atomic ordering contract: doc comment on hashMigrationComplete / backgroundLoadDone / backgroundLoadFailed explaining what each gates and the read-order invariant (Done must be read before Failed is meaningful). Kpa-clawbot#6 loadChunk merge: the previous implementation held s.mu.Lock across the entire merge of a chunk (hundreds of ms on large chunks); runtime.Gosched between chunks didn't help readers/ingest that arrived mid-chunk. Now the prepend is one short critical section and the per-index merge runs in 500-packet batches with the lock released+reacquired between batches plus a Gosched. Counter update is its own tiny final section. Kpa-clawbot#7 single cutoff in Load(): replaced the second time.Now().UTC() call used to seed s.oldestLoaded with the same hotCutoffStr that fed the load SQL. Microsecond skew at chunk borders is gone. #3 covered by TestHotStartup_BackgroundLoadFailureSurfacesInPerf (RED in the previous commit, GREEN here). Kpa-clawbot#6/Kpa-clawbot#7 covered by existing TestHotStartup_BackgroundFillsToRetention and TestHotStartup_ConcurrentQueryDuringBackgroundLoad — both still pass. bounded_load_test fixture had to switch observations.timestamp from RFC3339 string to unix int (production schema) so the restored item-1 RFC3339 subquery query path can match.
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.
What
Adds the Matomo tracking snippet (analytics.fiten.eu, site ID 8) to
public/index.htmljust before</body>.Important
This PR is local-only. It must be kept on
efiten/master(the deploy branch) and never cherry-picked to any upstream PR targetingKpa-clawbot/meshcore-analyzer.When rebasing upstream changes into the deploy branch, re-apply this commit on top.