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

The read metrics #667

Open
dasiyes opened this issue Jan 31, 2024 · 2 comments
Open

The read metrics #667

dasiyes opened this issue Jan 31, 2024 · 2 comments
Labels
bug Something isn't working legacy for legacy issues wontfix This will not be worked on

Comments

@dasiyes
Copy link
Contributor

dasiyes commented Jan 31, 2024

Screenshot 2024-01-31 at 08 45 43

Hi there,
Looking at the attached screenshot, I wonder what is wrong with the answer from my relay, so that the read metrics still stay red.
Can you help understand how to satisfy its logic?

@dskvr
Copy link
Collaborator

dskvr commented Jan 31, 2024

I looked into it briefly, and it does appear that the read results for your relay are incorrect for some reason. Unfortunately, I am away from my workstation today, but I will take a deeper look when I am capable of doing so,

Some context, I am presently refactoring the entire stack and so the library presently responsible for checking relays on nostr.watch is a bit out of date.

Thanks for bringing this to my attention, I’ll let you know when I know a bit more.

@dasiyes
Copy link
Contributor Author

dasiyes commented Jan 31, 2024

Thanks for the rapid reply!
No worries at all. There is nothing urgent here.

@dskvr dskvr added bug Something isn't working wontfix This will not be worked on legacy for legacy issues labels Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working legacy for legacy issues wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants