You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to be added:
A new option to limit the time spent checking external sources. It could be a total time or a number of retries. I assume the latter is simpler but exposes more of the implementation, I leave that to the project leads 🙇
Scan just stays for an indefinite time when there's an issue in the search services and nothing is shown in the console, only in debug.
This is happening right now due to issues with search.maven.org/, and we found what was causing issues when enabled debug and found the logs. However, it takes a long time to even show that.
failed to match against upstream data for HdrHistogram: status 504 Gateway Timeout from [https://search](https://search.maven.org/solrsearch/select?q=1%3A%226eb7552156e0d517ae80cc2247be1427c8d90452%22&rows=1&wt=json)
Additional context:
The text was updated successfully, but these errors were encountered:
Hi @abelsromero, thank you for the suggestion. We'll put this in the backlog for consideration. Are you interested in working on this? We'd be happy to point you in the right direction. Thanks again!
If you can provide specific of what configuration options you feel comfortable I can give it a try. Like what I mentioned, do you think it'd be better to have a number of retries or a total time?
That would be great! I think total time would be a good starting point.
One thing that would be nice is if the setting cascaded--in other words, you could set a global abort-after as well as abort-after values for individual sources:
external-sources:
enable: trueabort-after: 10mmaven:
search-upstream-by-sha1: truebase-url: https://search.maven.org/solrsearch/selectabort-after: 5m# override the global configanother-source:
blah-blah: true# aborts after 10m by inheriting the global config
What would you like to be added:
A new option to limit the time spent checking external sources. It could be a total time or a number of retries. I assume the latter is simpler but exposes more of the implementation, I leave that to the project leads 🙇
Why is this needed:
Scan just stays for an indefinite time when there's an issue in the search services and nothing is shown in the console, only in debug.
This is happening right now due to issues with
search.maven.org/
, and we found what was causing issues when enabled debug and found the logs. However, it takes a long time to even show that.Additional context:
The text was updated successfully, but these errors were encountered: