atharvalade opened a new issue, #2907:
URL: https://github.com/apache/iggy/issues/2907

   ### Problem
   
   We have 7 separate scripts for testing SDK examples:
   
   - `scripts/run-node-examples-from-readme.sh`
   - `scripts/run-rust-examples-from-readme.sh`
   - `scripts/run-go-examples-from-readme.sh`
   - `scripts/run-python-examples-from-readme.sh`
   - `scripts/run-java-examples-from-readme.sh`
   - `scripts/run-csharp-examples-from-readme.sh`
   - `examples/node/test-examples.sh`
   
   Each script duplicates ~60-70% of its code (server binary check, startup, 
wait-for-ready loop, README parsing, teardown). `scripts/utils.sh` already has 
process management helpers but none of the example scripts use it. We also 
added TLS support across multiple SDKs but have no TLS example test runs.
   
   These should be unified into a single script that sources shared utilities 
from `scripts/utils.sh`, starts 2 servers (one plain, one TLS-enabled), and 
runs all examples from each language's `README.md` as the single source of 
truth. CI should be updated accordingly and old per-language scripts removed.
   
   ### Languages & README patterns
   
   | Language | README(s) | Grep pattern |
   |----------|-----------|--------------|
   | Rust | `README.md`, `examples/rust/README.md` | `cargo r --bin iggy --`, 
`cargo run --example` |
   | Node | `README.md`, `examples/node/README.md` | `npm run`, `tsx` |
   | Go | `examples/go/README.md` | `go run` |
   | Python | `examples/python/README.md` | `uv run` |
   | Java | `examples/java/README.md` | `./gradlew` |
   | C# | `README.md`, `examples/csharp/README.md` | `cargo r --bin iggy --`, 
`dotnet run --project` |
   
   ### TLS-capable SDKs
   
   Rust, Go, C#, Java, Node (Python has no TLS support yet).


-- 
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]

Reply via email to