hermes - 💡(How to fix) Fix Webhook: coalesce same-object GitHub events to avoid duplicate agent runs and 429s [1 comments, 1 participants]

TL;DR

Implement a debounce mechanism in Hermes to coalesce same-object GitHub events within a short configurable window, ensuring only the last event triggers an agent run.

Guidance

• Identify the logical object (e.g., issue or pull request) and group incoming webhook events accordingly to enable coalescing.
• Introduce a configurable debounce window (e.g., 1-2 seconds) to determine the time frame within which duplicate events are dropped.
• Develop a mechanism to preserve idempotency for exact delivery retries, ensuring that retries of the same event do not cause duplicate agent invocations.
• Implement logging to track the number of coalesced events and the final chosen event for debugging and monitoring purposes.

Example

No code example is provided due to the high-level nature of the issue and the need for a specific implementation details.

Notes

The solution should focus on modifying the Hermes infrastructure to handle webhook events more efficiently, without affecting project business code. The debounce window duration and coalescing logic may require tuning based on the specific requirements and event patterns of the application.

Recommendation

Apply a workaround by implementing the proposed debounce mechanism in Hermes, as it directly addresses the issue of duplicate agent invocations and transient-state misreads caused by rapid successive webhook events.