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.

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

feat: store previous response codes, calculate error rate, consider #12

Merged
merged 4 commits into from
Aug 15, 2024
Merged

Conversation

caarlos0
Copy link
Contributor

  • theres a new ttlslice internal package for storing things in a slice with a ttl
  • these are used to store success status codes and error status codes
  • these are then used to check if a node is healthy or not
  • it also shows the error rate in the index page
  • there's also a small fix regarding the handling of the /rpc trailing bit

closes #10

- theres a new `ttlslice` internal package for storing things in a slice
  with a ttl
- these are used to store success status codes and error status codes
- these are then used to check if a node is healthy or not
- it also shows the error rate in the index page
- there's also a small fix regarding the handling of the `/rpc` trailing
  bit
Signed-off-by: Carlos Alexandro Becker <[email protected]>
Signed-off-by: Carlos Alexandro Becker <[email protected]>
@caarlos0 caarlos0 mentioned this pull request Aug 15, 2024
@troian troian merged commit 6e56229 into main Aug 15, 2024
4 checks passed
@troian troian deleted the 10 branch August 15, 2024 19:04
This was referenced Aug 16, 2024
troian pushed a commit that referenced this pull request Aug 17, 2024
- move the seed updating logic to its own thing
- add rest nodes to the seed updater
- reused the previous proxy implementation for both rpc and rest calls 
- fixed status page to show both kinds of nodes
- fixed a possible nil access when response is nil (introduced in #12)

closes #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid rpc nodes
2 participants