remove --refresh-dependencies to avoid Premature end of Content-Length #14070
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
…h delimited message body > Could not get resource 'https://repo.grails.org/grails/core/org/grails/grails-async/7.0.0-SNAPSHOT/grails-async-7.0.0-20250313.020438-51.jar'. > Premature end of Content-Length delimited message body (expected: 68,766; received: 12,994)
matrei
approved these changes
Mar 13, 2025
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.
to avoid Premature end of Content-Length delimited message body
The theory behind this issue is that when we start a matrixed GitHub action it requests the dependencies over and over again from repo.grails.org (JFrog Artifactory) and it looks like a DOS attack from GitHub actions, which JFrog Artifactory is throttling/mitigating.
--refresh-dependencieswas added to many GitHub workflows to force the workflow to pull the recently published-SNAPSHOTdependencies, which occurs often. The replacement for this approach is to delete all recently used GitHub actions cache and then rerun the action.