etzel-mes commented on PR #28631: URL: https://github.com/apache/camel/pull/28631#issuecomment-6474524762
Thanks for the thorough read, @davsclaus. Pushed in 7ff41f661b4 and 3e1090b9cd6: - `ArtifactUtils` regenerated with the `update-artifact-helper` goal: the `mtconnect` entry after `mongodb-gridfs`; the other camel-util and camel-main helper goals produce no change. For the record, the failed `build (21)` job died before the regen comparison: Maven Central answered 502 for a camel-drill dependency during `mvn -Pregen`. - Wall-clock bounds: the four assertions now allow a 3 s slack (`SLACK` in `MTConnectTestSupport`). They still show that detection happens on the heartbeat's scale rather than at the await's limit. - Awaitility: every `await()` goes through `awaitAgent()`, which is `await().atMost(10, SECONDS)`; the `during(...)` waits already had their `atMost`. - `src/test/resources/log4j2.properties` writing `target/camel-mtconnect-test.log`, as in camel-clickhouse. - The YAML example is in canonical form (`- route:`, `filter: expression: simple: expression:`, `log: message:`), catalog copy refreshed. - Both stop races closed: `AgentHttpClient.send` cancels the request when the waiting thread is interrupted and closes the body of an answer that arrived meanwhile; `AgentReader.send` closes and fails a response that `abort()` could not see because it was registered after `abort()` iterated the open set. The two bot threads are answered inline. _Claude Code on behalf of etzel-mes_ -- 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]
