fix: add HTTP timeout configuration to mitigate version.json fetch failures #84
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.
HeadlessMC intermittently times out when fetching version.json from Mojang servers, causing CI failures that require manual reruns.
Changes
Added Java HTTP timeout system properties to all HeadlessMC launcher invocations:
Modified 4 commands in
action.yml:Both timeouts set to 30 seconds (30000ms) to handle transient network issues while preventing indefinite hangs.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
https://api.github.com/repos/3arthqu4ke/headlessmc/releases/latestcurl -s REDACTED(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This section details on the original issue you should resolve
<issue_title>Frequent test failures due to timeout while fetching version</issue_title>
<issue_description>I've introduced the mc-runtime-test and mc-server-test actions into several Hex Casting-related projects, and all of them have recently started running into frequent but intermittent failures caused by an HTTP timeout while fetching version.json. Manually rerunning the job often resolves the timeout.
Example of a workflow run that failed due to this issue: https://github.com/FallingColors/HexMod/actions/runs/18510809336/job/52751586190
Traceback: