urlyy opened a new issue, #2742: URL: https://github.com/apache/fory/issues/2742
### Feature Request The Python CI workflow sometimes experiences flaky failures. PR #2733 added retry logic to mitigate the issue, but the root cause is that the workflow downloads Bazel on every run. We should use **GitHub Actions caching** to avoid downloading Bazel on every run. ### Is your feature request related to a problem? Please describe #2731 ### Describe the solution you'd like - GitHub Actions cache is Simple, caches the binary directly. - Bazelisk can auto-manages Bazel versions with caching. But I think Fory doesn’t seem to need managing multiple Bazel versions — caching the binary directly is enough. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
