Fix cURL example to use $max_delay variable instead of hardcoded value #6575
+1
−1
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.
Addresses review feedback on #6574 regarding inconsistent use of the
max_delayparameter in the exponential backoff cURL example.Changes
content/shared/influxdb3-write-guides/troubleshoot-distributed.mdto use$max_delayvariable instead of hardcoded30max_delayas awk variable-v m=$max_delayand uses it in the comparison:if(d>m) d=mmax_delayvariablesBefore:
delay=$(awk -v b=$base -v a=$attempt 'BEGIN{d=b*(2^a); if(d>30) d=30; print d}')After:
delay=$(awk -v b=$base -v a=$attempt -v m=$max_delay 'BEGIN{d=b*(2^a); if(d>m) d=m; print d}')(if necessary)
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.