Skip to content

feat: auto-reconnect provider after 502 command response via ReconnectDelay#58

Merged
javi11 merged 1 commit intomainfrom
feat/reconnect-delay-on-502
Mar 14, 2026
Merged

feat: auto-reconnect provider after 502 command response via ReconnectDelay#58
javi11 merged 1 commit intomainfrom
feat/reconnect-delay-on-502

Conversation

@javi11
Copy link
Copy Markdown
Owner

@javi11 javi11 commented Mar 14, 2026

Summary

  • Add ReconnectDelay time.Duration field to Provider (opt-in, default 0 = disabled for backward compatibility)
  • When a command returns 502, the provider is removed as before; if ReconnectDelay > 0, a goroutine waits the configured duration then re-adds it via AddProvider
  • Both main and backup provider 502 paths are covered
  • scheduleReconnect respects client shutdown — exits immediately on c.ctx.Done()

Test plan

  • TestClient_502ReconnectDelay: mock server returns 502 on first command, 223 on subsequent ones; asserts provider removed after 502, re-added after delay, second request succeeds
  • make check passes (lint + race detector + all existing tests)

🤖 Generated with Claude Code

…tDelay

Add opt-in ReconnectDelay field to Provider. When non-zero, a goroutine
re-adds the provider via AddProvider after the configured delay once a
command-502 removes it. Default is 0 (disabled) for full backward
compatibility.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@javi11 javi11 merged commit 7d14318 into main Mar 14, 2026
1 check passed
@javi11 javi11 deleted the feat/reconnect-delay-on-502 branch March 14, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant