davsclaus opened a new pull request, #26854:
URL: https://github.com/apache/camel/pull/26854
`RestProducerUnresolvedPathWarnTest`, added with #26843, failed on its first
run and passed on rerun — twice in full camel-core runs — once counting two
warnings where it expected one:
```
The path parameter {id} of list/{id} has no value...
The path parameter {id} of list/{id}_{val} has no value...
```
The second is from `RestProducerPathTest`. My appender is on the shared
`RestProducer` logger, my test used **the same paths as that class**
(`list/{id}` and `list/{id}/{val}`), and the two run in the same JVM — so its
warnings were counted as mine. My own bug, from the PR that added the test.
Each test now uses a path of its own (`warnsays`, `warnonce`, `warnnone`)
and counts only the warnings for that path. The filter matches the path's
**first segment**, because the message carries the path as resolved —
`warnsays/{id}/{val}` appears as `warnsays/1/{val}` once `id` has a value,
which my first attempt at the filter got wrong. The appender also gets a unique
name, so two of these cannot replace each other's registration.
Test-only; no production change.
Found by the core review session running the full suite — thanks for the
report, it would have been an intermittent CI failure for everyone otherwise.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj
--
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]
