[
https://issues.apache.org/jira/browse/CAMEL-27004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-27004:
--------------------------------
Fix Version/s: 4.24.0
(was: 4.25.0)
> camel-jbang - outbound network calls, the rest: response bodies without a
> deadline, infra run --background output, camel debug, Vertex AI token,
> Quarkus offline cache
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-27004
> URL: https://issues.apache.org/jira/browse/CAMEL-27004
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> What is left of CAMEL-26914 after
> [#29804|https://github.com/apache/camel/pull/29804] (merged as 60f5651b1f0a
> for 4.24.0), checked on main bd5528c88795. The item numbers are those of
> CAMEL-26914. Paths are relative to {{dsl/camel-jbang/}}.
> h3. 3. HttpRequest.timeout() does not bound the response body
> A server that sends the headers and then stalls hangs
> {{send(BodyHandlers.ofString())}} past the timeout. #29804 fixed
> {{GitHubHelper}} and {{GistHelper}} with {{sendAsync}} plus {{get(timeout)}}.
> Still affected:
> * camel-jbang-run {{QuarkusHelper}}:348
> * camel-jbang-core {{ExampleHelper}}:553, {{VersionList}}:575,
> {{ai/DependencyLookup}}:72
> * camel-launcher {{ManifestFetcher}}:219 and {{InstallScriptFetcher}}:103
> * {{LlmClient}}: about 10 {{send()}} calls; the streaming ones have no idle
> timeout, so {{camel ask}} can hang mid-answer
> h3. 4. install.sh runs curl and wget without a connect or max time
> The CLI now gives up on the installer after 5 minutes, but the script itself
> has no limit.
> h3. 5. camel infra run --background loses the output of the child
> {{InfraRun}} (around lines 179-192) starts the child with the default pipes
> and returns 0 at once. With Docker down, the user only sees "Running ... in
> background with PID".
> h3. 6. camel debug
> {{doReadLog}} ({{Debug.java}} around lines 285-307) loops at 100% CPU after
> EOF, and stderr is read only after the process exits, so a full stderr pipe
> can block it.
> h3. 7. Vertex AI runs gcloud auth print-access-token on every LLM request
> {{LlmClient.getGcloudAccessToken}} (around line 1877): about 1s per call, no
> timeout, and stderr is merged into the token. The token should be cached
> until it expires.
> h3. 8. QuarkusHelper offline
> When the daily refresh fails, it throws instead of using the stale cache it
> has.
> h3. 9. camel version list makes one sequential, uncached GET per unknown
> version
> They run before the {{--lts}}/{{--patch}} filters, and misses are never
> cached. (Not checked again on main.)
> h3. 10. GitHub example downloads
> The download of an example ({{camel run --example}}, and the TUI) is
> sequential and skips failed files silently. The TUI {{OsvClient}} fetches
> vulnerability details one at a time. (Not checked again on main.)
> Item 2 is gone: {{PipeProvider}} was removed with camel bind by CAMEL-27002.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)