Opened 5 years ago

Closed 3 years ago

#15178 closed enhancement (fixed)

Improve Atlas' error messages

Reported by: phw Owned by: phw
Priority: Low Milestone:
Component: Metrics/Relay Search Version:
Severity: Normal Keywords: easy
Cc: nusenu@…, kleft Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Whenever Onionoo is offline, Atlas shows an error message:

Backend error!
The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted it may mean that there is an issue with your browser/add-ons. Please report which browser/addons/etc. you're using to the bug tracker.

This suggests that the user made a mistake, which results in several trac tickets every time Onionoo is offline. We should improve the error message and make it clear that waiting a little bit might solve the problem. Here's a suggestion:

Backend error!
Atlas is unable to get a response from its backend server. This probably means that the backend server is unavailable right now. This can also happen, however, if you did not format your query correctly. Please have a look at this page that explains what type of search queries are supported by Atlas.

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by karsten

So, improving the text as you suggest is a fine first step.

But what Atlas should also do is distinguish what error code it gets back from Onionoo and display an appropriate error message. See #8667.

A related issue is whether Atlas can somehow become better at deciding how old the returned data is and handle outdated data by itself. Let me explain: when Onionoo learns that its data is more than 6 hours old it returns an internal server error. What I'd want to do is remove that check and just give out whatever data Onionoo has, together with a timestamp. The client could then decide when to warn the user and when to refrain from displaying old data. Any chance we can do something like this? Happy to create a ticket for this, but it seemed related here, which is why I went slightly off-topic.

comment:2 in reply to:  1 Changed 5 years ago by phw

Keywords: easy added

Replying to karsten:

So, improving the text as you suggest is a fine first step.

Done and deployed.

But what Atlas should also do is distinguish what error code it gets back from Onionoo and display an appropriate error message. See #8667.

A related issue is whether Atlas can somehow become better at deciding how old the returned data is and handle outdated data by itself. Let me explain: when Onionoo learns that its data is more than 6 hours old it returns an internal server error. What I'd want to do is remove that check and just give out whatever data Onionoo has, together with a timestamp. The client could then decide when to warn the user and when to refrain from displaying old data. Any chance we can do something like this? Happy to create a ticket for this, but it seemed related here, which is why I went slightly off-topic.

Good ideas! I'll leave the ticket open so I can work on these next---unless somebody beats me to it.

comment:3 Changed 5 years ago by tyseom

Cc: nusenu@… added

comment:4 Changed 4 years ago by karsten

There, I just created #16907 for the Onionoo part and #16908 for adding a similar warning to Globe. I'd want to make this change to Onionoo in a month from now, so around end of September. Hope that's enough of a heads-up. If not, please let me know. Thanks!

comment:5 Changed 4 years ago by kleft

Cc: kleft added
Severity: Blocker

comment:6 Changed 4 years ago by phw

Severity: BlockerNormal

comment:7 Changed 3 years ago by kleft

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.