Repository navigation
test: measure GitHub webhook ACK latency - #19
Open
zehongye-gaga wants to merge 1 commit into
Open
zehongye-gaga wants to merge 1 commit into
zehongye-gaga wants to merge 1 commit into
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
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.
Purpose
Measure the real GitHub webhook delivery and backend admission latency after the SQLite and durable-ACK rollout. The branch adds one small, unused Python fixture. This is a disposable test PR and should not be merged.
The measurement correlates GitHub delivery IDs with backend receipt timestamps. Signed ping probes compare public n8n, internal n8n and direct backend paths independently; they do not dispatch extra reviews.
AI assistance: the fixture and test setup were created using OpenAI Codex (GPT-6 family).