Skip to content

fix(clients): retry a write when nothing was sent - #1681

Open
Goran Gajic (gorangajic) wants to merge 3 commits into
mainfrom
goran/wiz-12618-retry-connect-failures
Open

Goran Gajic (gorangajic) wants to merge 3 commits into
mainfrom
goran/wiz-12618-retry-connect-failures

Conversation

@gorangajic

@gorangajic Goran Gajic (gorangajic) commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Relates to WIZ-12618

Overview of Changes

About 3% of the qawolf runner commands Tester runs fail with "Could not reach the QA Wolf API", and in most of these the connection never opened. The CLI already says when nothing was sent, but it gives up after one try, so Tester spends a turn sending the command again.

Now a write is sent again when nothing was sent the first time, since that cannot repeat the action. Tester only sees the error if every try fails. Writes that may have reached the server are still never retried.

Testing

bun run typecheck
bun run lint
bun run format:check
bun run knip
bun run test

The built CLI pointed at a closed port tries a runner act 3 times, then ends with "Nothing was sent, so this request did not take effect."

Checklist

  • Changes follow the code style of this project
  • Self-review completed
  • Tests added/updated (or not applicable)
  • No breaking changes (or described below)

@gorangajic
Goran Gajic (gorangajic) force-pushed the goran/wiz-12618-retry-connect-failures branch from 4b74902 to e2f616b Compare October 21, 2026 14:36
@gorangajic
Goran Gajic (gorangajic) marked this pull request as ready for review October 21, 2026 14:54
A write whose connection never opened carried no request, so sending it
again cannot repeat the action.
@gorangajic
Goran Gajic (gorangajic) force-pushed the goran/wiz-12618-retry-connect-failures branch from 86f3742 to 9db7e9d Compare October 22, 2026 12:44
@gorangajic Goran Gajic (gorangajic) changed the title fix(clients): retry API requests whose connection never opened fix(clients): retry a write when nothing was sent Oct 22, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants