Notification message producer integrated with the platform MQ #1
Conversation
This file contains 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
Supabase types and v2 notifications
❌ Deploy Preview for kleros-tg-court-notifications failed.
|
jaybuidl
changed the title
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.
This PR implements the
KAFKAMQ notification architecture described in the hermes notion doc.It relies on modifications to the Kleros-Display and Kleros-v2 subgraphs, for which relevant PRs should be merged first, then explicit mentions to the subgraphs deployed under my personal account should be removed from this PR before merging.
Note that the V1 notifications are tested adhoc, and V2 notifications are tested for limited cases based on existing activity in the testnet.
Future work will include appeal funding notifications for V2 and perhaps a test suite.
The PR introduces an optional test tg user id in env variables. When set, only this user will receive notifications. This should likely be the first deployment configuration to monitor notifications.