Closed karafecho closed 2 months ago
Also see #195 and #181.
We might want to consolidate these issues. This is essentially the same as #195 and #181
As mentioned in #181 there are really two issues: the error message should be improved for timeouts, and we should try to find the cause of timeouts for queries that we would expect to be faster, but there are a number of reasons why we might see performance variability, and we may not be able to recreate the issue.
This has never had anything to do with the port, that's just part of the aragorn endpoint the UI communicates with.
Closing, see consolidated issue in #215.
This issue is to suggest that we prioritize fixing the 8080 port error that seems to show up somewhat randomly, somewhat consistently.
Here's the (fleeting) error message:
And here's an example query, but note that I can provide others:
I think it would be good to fix this issue prior to any upcoming presentations/demos/workshops, e.g., the planned meeting with Scott Auerbach (NIEHS DTT) and his team.