justinmclean opened a new issue, #4261: URL: https://github.com/apache/iggy/issues/4261
### Description connect() blocks forever with no output when the server isn't reachable. The default reconnection policy is unlimited retries, and the only trace of a retry is a tracing::info! call that's silent without a subscriber, so a newcomer running the quick-start against a server they forgot to start sees a program that never returns and no reason why. A fail-fast option already exists (reconnection_retries=0 on the connection string, or .with_reconnection_max_retries(Some(0)) on the Rust builder); it's just not in the quick-start docs. The fix is to add it to the quick-start snippets (sdk/rust/intro.mdx and sdk/python/intro.mdx) so a copy-pasted example gets a bounded connect and a clear error instead of a silent hang. This is a good first issue: a small, well-defined docs change with the exact files and the existing option named. ### Affected area / component Documentation ### Proposed solution Add the existing fail-fast option to the quick-start snippets (`sdk/rust/intro.mdx`, `sdk/python/intro.mdx`) so a newcomer copy-pasting the example gets a bounded connect and a clear error instead of a silent hang. ### Alternatives considered Changing the SDK default from unlimited retries to a bounded value. Unlimited retries is right for a long-running service, and the Python docstring already flags this default as wrong for request/reply usage, so a docs fix beats a breaking default change. ### Contribution - [ ] I'm willing to submit a pull request to implement this feature ### Good first issue - [x] I think this could be a good first issue for a new contributor -- 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]
