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

The faucet does not always receive notifications about new epochs. #3024

Open
afck opened this issue Dec 12, 2024 · 2 comments
Open

The faucet does not always receive notifications about new epochs. #3024

afck opened this issue Dec 12, 2024 · 2 comments
Assignees
@Twey @afck @christos-h
Labels
bug Something isn't working

Comments

@afck
Copy link
Contributor

afck commented Dec 12, 2024

This was observed on testnet-archimedes.

Locally with latest main (a3cce00) I cannot reproduce it. Trying with latest main on GCP now.
@afck afck added the bug Something isn't working label Dec 12, 2024
@christos-h
Copy link
Contributor

Reproducing on a temporary network, the issue stems from the faucet ingress BackendConfig having a timeout of 60s which kills the notifications stream. There are several things that need to be done:

  1. Clients should try to reconnect anyway.
  2. Perhaps introduce a heartbeat to maintain open connections.

@christos-h
Copy link
Contributor

This should also be used to address the aggressive timeout limits on validator ingresses.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Twey Twey

@afck afck

@christos-h christos-h

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

No branches or pull requests
3 participants
@Twey @afck @christos-h