Bug description
The examples CI job reports success for Python and Go without executing a single non-TLS example.
Root cause — scripts/utils.sh:318:
commands=$(echo "${commands}" | grep -v "${grep_exclude}" || true)
Python and Go pass --tls as the exclude (scripts/run-examples-from-readme.sh:259, :231). grep parses --tls as an unknown long option and exits 2 with no output; || true swallows the error, the command list ends up empty, and the function returns without running anything. The other languages are fine because their excludes (tcp-tls, TcpTls) don't start with dashes.
This is a regression from #2920 (658eb89, 2026-03-16): the removed per-language scripts had no exclude and executed everything. The TLS passes still run (they select by pattern, no exclude).
Fix:
commands=$(echo "${commands}" | grep -v -e "${grep_exclude}" || true)
All six skipped commands were verified to pass when executed manually against a local server, so the fix should not surface new failures.
Affected area / component
CI / build / tooling
Deployment
Not applicable
Versions
master (c5fec1f); broken since 658eb89 (#2920)
Hardware / environment
No response
Sample code
$ printf 'uv run a\nuv run b --tls\n' | grep -v "--tls"; echo "exit=$?"
grep: unrecognized option `--tls'
exit=2
Or run ./scripts/run-examples-from-readme.sh --language python --skip-tls: it succeeds without printing a single Checking command from README.md: line.
Logs
No response
Iggy server config
No response
Reproduction
$ printf 'uv run a\nuv run b --tls\n' | grep -v "--tls"; echo "exit=$?"
grep: unrecognized option `--tls'
exit=2
Or run ./scripts/run-examples-from-readme.sh --language python --skip-tls: it succeeds without printing a single Checking command from README.md: line.
Contribution
Good first issue
Bug description
The examples CI job reports success for Python and Go without executing a single non-TLS example.
Root cause —
scripts/utils.sh:318:commands=$(echo "${commands}" | grep -v "${grep_exclude}" || true)Python and Go pass
--tlsas the exclude (scripts/run-examples-from-readme.sh:259,:231). grep parses--tlsas an unknown long option and exits 2 with no output;|| trueswallows the error, the command list ends up empty, and the function returns without running anything. The other languages are fine because their excludes (tcp-tls,TcpTls) don't start with dashes.This is a regression from #2920 (658eb89, 2026-03-16): the removed per-language scripts had no exclude and executed everything. The TLS passes still run (they select by pattern, no exclude).
Fix:
commands=$(echo "${commands}" | grep -v -e "${grep_exclude}" || true)All six skipped commands were verified to pass when executed manually against a local server, so the fix should not surface new failures.
Affected area / component
CI / build / tooling
Deployment
Not applicable
Versions
master (c5fec1f); broken since 658eb89 (#2920)
Hardware / environment
No response
Sample code
Or run
./scripts/run-examples-from-readme.sh --language python --skip-tls: it succeeds without printing a singleChecking command from README.md:line.Logs
No response
Iggy server config
No response
Reproduction
Or run
./scripts/run-examples-from-readme.sh --language python --skip-tls: it succeeds without printing a singleChecking command from README.md:line.Contribution
Good first issue