[
https://issues.apache.org/jira/browse/CAMEL-20138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802051#comment-17802051
]
Aurélien Pupier commented on CAMEL-20138:
-----------------------------------------
In last logs failing with timeout,
https://github.com/apache/camel/network/updates/769390274
* There is no more reference to the Apache Snapshot repository
* It has checked various number of dependencies: 700/781/765/617 (searched for
`Latest versions is` in log)
Not sure how to find a reliable way of the number of existing (non-maven
plugin) dependencies. But it seems quite far from the 20*349 = 6980 provided by
the Dependencies tab on GitHub
https://github.com/apache/camel/network/dependencies?page=349 (even if it
includes the Camel ones and Maven plugins)
> Avoid time out during dependabot Check Update job
> -------------------------------------------------
>
> Key: CAMEL-20138
> URL: https://issues.apache.org/jira/browse/CAMEL-20138
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Aurélien Pupier
> Priority: Major
>
> The dependabot jobs are currently taking more than 45 minutes and are failing
> in timeout -(not a problem right now as it always has enough dependencies
> update to provide)-
> {noformat}
> proxy | 2023/11/21 06:29:21 proxy starting, commit:
> 6cffd6fae1b2f713f2d837bc45fe916f855c821d
> {noformat}
> {noformat}
> updater | time="2023-11-21T07:15:42Z" level=warning msg="timeout running job"
> error="waiting for updater: waiting for container: context deadline exceeded"
> job_id=752523002
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=<nil>
> updater | 2023/11/21 07:15:42 Unsolicited response received on idle HTTP
> channel starting with "0\r\n"; err=<nil>
> {noformat}
> [GitHub is suggesting to limit the number of dependencies to
> check|https://docs.github.com/en/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-timed-out-during-its-update]
> (but in our case we will miss the purpose of it)
> One point that i observed is that the Apache snapshot repository is checked.
> As far as I know it is usually a slow one and i do not think that we care
> about snapshots version. i think this could be the first point to try:
> removing the Apache Snapshots repo during this check
> {noformat}
> proxy | 2023/11/21 06:45:01 [390] HEAD
> https://repository.apache.org:443/snapshots/org/infinispan/infinispan-core/14.0.21.Final/infinispan-core-14.0.21.Final.test-jar
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
