Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[feature request] "lossy" event observer #5818

Open
obycode opened this issue Feb 10, 2025 · 0 comments
Open

[feature request] "lossy" event observer #5818

obycode opened this issue Feb 10, 2025 · 0 comments
Assignees
@rdeioris
Labels
feature Brand new functionality. New pages, workflows, endpoints, etc.

Comments

@obycode
Copy link
Contributor

obycode commented Feb 10, 2025

Some event observers may not require perfect delivery of events, i.e. the node should not be blocked if it cannot successfully deliver the event. We should add a way to specify this in the configuration, being sure to make it very clear that this is lossy, so that event observers like exchanges and explorers do not accidentally use it.
@obycode obycode added the feature Brand new functionality. New pages, workflows, endpoints, etc. label Feb 10, 2025
@github-project-automation github-project-automation bot moved this to Status: 🆕 New in Stacks Core Eng Feb 10, 2025
@rdeioris rdeioris mentioned this issue Feb 13, 2025
Open
5 tasks
@rdeioris rdeioris moved this from Status: 🆕 New to Status: In Review in Stacks Core Eng Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rdeioris rdeioris

Labels
feature Brand new functionality. New pages, workflows, endpoints, etc.
Projects
Stacks Core Eng
Status: Status: In Review
Milestone
No milestone
Development

No branches or pull requests
2 participants
@obycode @rdeioris