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

Generate TRAPI log if BTE marks API unavailable, skips subquerying it #888

Open
colleenXu opened this issue Oct 17, 2024 · 0 comments
Open
Labels
good first issue Good for newcomers

Comments

@colleenXu
Copy link
Collaborator

Jackson's info from lab Slack (emphasis mine):

For context, BTE keeps track of APIs which should be considered unavailable for the duration of query execution. This occurs when a subquery to said API fails 3 times in a row with an HTTP 502 or higher, or the connection was aborted. When that happens, it logs to debug, but should also show up in the TRAPI logs as a failed subquery. From then, all subsequent subqueries to that API are skipped silently for the rest of execution.

It would be helpful if it wasn't silent! Instead, a TRAPI log could be generated saying that we're not going to subquery this API for the rest of this query's execution. (Note: is this any different in creative-mode? with parallel execution?)

FYI: I think a console log like this is already being generated.

@colleenXu colleenXu added the good first issue Good for newcomers label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant