Closed WenyXu closed 1 week ago
The primary change involved removing the retry_on: error
configuration from the runs
section of the GitHub action setup for GreptimeDB cluster. This modification impacts the error handling behavior during the action execution, potentially streamlining action performance and reducing redundant retry attempts.
File Path | Change Summary |
---|---|
.github/actions/setup-greptimedb-cluster/... | Removed retry_on: error from the runs section. |
In the land of code, where actions run, A tweak was made, a change begun. No more retries on errors appear, GreptimeDB’s setup, now more clear. With steady steps, without the fuss, Smoothly executing, less to discuss.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.87%. Comparing base (
a710676
) to head (451b829
). Report is 1 commits behind head on main.
I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
What's changed and what's your intention?
Make operator installation step retry on error or timeout
Checklist
Summary by CodeRabbit