temporarily set read timeout to an extremely high value (12 hours)... #5390
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
... mostly to see if this has any effect at all. We keep running into read timeouts at the final step (validating the release), but the timeouts don't quite make sense... see e.g. https://github.com/joernio/joern/actions/runs/13967737826/job/39101942676 ``` 2025-03-20 11:38:44.040Z info [SonatypeCentralClient] Uploading bundle /home/runner/work/joern/joern/target/sonatype-staging/4.0.299-bundle/bundle.zip to Sonatype Central - (SonatypeCentralClient.scala:72) +4 seconds: 2025-03-20 11:38:47.814Z info [SonatypeCentralService] Checking if deployment succeeded for deployment id: 583c03d8-b0cb-431f-b3d5-a7990a1e435d... - (SonatypeCentralService.scala:27) +16mins 11:54:06.356 [main] ERROR sttp.client4.logging.slf4j.Slf4jLoggingBackend - Exception when sending request: POST https://central.sonatype.com/api/v1/publisher/status?id=583c03d8-b0cb-431f-b3d5-a7990a1e435d, took: 5.085s sttp.client4.SttpClientException$TimeoutException: Exception when sending request: POST https://central.sonatype.com/api/v1/publisher/status?id=583c03d8-b0cb-431f-b3d5-a7990a1e435d at sttp.client4.SttpClientExceptionExtensions.defaultExceptionToSttpClientException(SttpClientExceptionExtensions.scala:21) ~[?:?] ```
maltek
reviewed
Mar 20, 2025
|
ha, good find, thank you, that helps |
|
Actually, the correct location is here: Which sets the readTimeout here: Now it all makes sense. We just need to pass a different timeout in sbt-sonatype. |
|
upstream patch: xerial/sbt-sonatype#591 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
... mostly to see if this has any effect at all.
We keep running into read timeouts at the final step (validating the
release), but the timeouts don't quite make sense...
see e.g. https://github.com/joernio/joern/actions/runs/13967737826/job/39101942676