atiaomar1978-hub commented on PR #25551: URL: https://github.com/apache/camel/pull/25551#issuecomment-5363861212
## Review tables — corrected formatting _AI-generated on behalf of atiaomar1978-hub_ The markdown tables in the approval review above may render poorly on GitHub (one letter per line). Here is the same content in plain list form: ### Prior feedback — resolved - **Variables table (`message`/`exchange`/`context` in default mode)** — Fixed: docs now split default bindings vs trusted `createWithHostAccess()` mode - **`@Metadata` / docs accuracy** — Fixed: clear Security + Trusted host access sections - **Materialize Python sets/tuples before context close** — Implemented: `materialize()` handles set/frozenset/tuple + tests - **Separate GraalPy version property** — Fixed: shared `graalvm-version` (25.2.4) per @jamesnetherton ### CI failure analysis — not this PR **`camel-python3`: 43/43 tests passed on JDK 17 and JDK 25.** - **JDK 25 (`build (25)`)** — `camel-pqc`: `PQCSignatureOnlyKeyStoreTest` + `PQCSignatureWithKeyStoreTest` fail with `InvalidKeyException: unknown private key passed to ML-DSA`. Failed all 3 Surefire reruns → **not flaky**, deterministic JDK 25 issue - **JDK 17 (`build (17)`)** — unrelated modules (`camel-core` file tests, `camel-mail`, `camel-jms`, `camel-jetty`, etc.) — also unrelated to `camel-python3` Doc validation and dependency review passed. **Verdict: Approved** — CI red is unrelated infrastructure/main-branch noise; safe to re-run or merge after maintainer ack on `camel-pqc` JDK 25. -- 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]
