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

Fix the bug where the worker can not find the desired event #636

Closed
aramikm opened this issue Oct 21, 2024 · 0 comments · Fixed by #650
Closed

Fix the bug where the worker can not find the desired event #636

aramikm opened this issue Oct 21, 2024 · 0 comments · Fixed by #650
Assignees
@JoeCap08055
Labels
bug Something isn't working Hardening and Readiness

Comments

@aramikm
Copy link
Contributor

aramikm commented Oct 21, 2024

Context

There are situations where the notification service can not find the desired event in the block

Example

2024-10-17 15:09:12 [Nest] 43  - 10/17/2024, 10:09:12 PM   ERROR [TxnNotifierService] Watched transaction 0x1043d17555bf5f7286a06a0b30d22158ff2367525f20d9122370172f28f8f4e6 found, but neither success nor error???
2024-10-17 15:09:12 [Nest] 43  - 10/17/2024, 10:09:12 PM   ERROR [TxnNotifierService] Empty block hash encountered; end of chain at block 2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JoeCap08055 JoeCap08055

Labels
bug Something isn't working Hardening and Readiness
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: was monitoring incorrect event name for msa.MsaRetired ProjectLibertyLabs/gateway
2 participants
@aramikm @JoeCap08055