Daniel Strobusch comments

Results 88 comments of


                                            Daniel Strobusch

Support Async Tool Execution

Async tool execution would be helpful for integration with frameworks that favor an async/reactive approach. For example, tool calls that do REST API calls may often be asynchronous in nature.

`TLSRoute` promotion to standard

/remove-lifecycle stale

[tempo] helm chart is not ready for monolithic scaling

I ended up switching to microservices mode.

Support for adding/removing subnet delegation after the subnet is created.

Any update or creative ideas on how to handle subnet Delegation on a provided subnet?

Recreate immutable resources on upgrade

remove stale

fix: copy dependencies on aliasing to avoid sharing chart references on multiply aliased dependencies [v3 backport]

> Should it be closed? With the new backport strategy ? What is the new back-port strategy? I created the PR as a request for a back-port.

feat(helm): add new update-policy annotation to recreate resources

@joejulian could you unlock #7082 to be able to comment on in again, since I am not able to comment on this issue anymore?

feat(helm): add new update-policy annotation to recreate resources

remove stale

Tool executions on streaming models lead to `The current thread cannot be blocked: vert.x-eventloop-thread-0`

There is a request on async tool execution in lang chain: https://github.com/langchain4j/langchain4j/issues/1183 but it doesn't seem to get implemented soon.

Support Multi<ChatCompletionResponse> AI services

@geoand you would check on the `finish_reason` of the last event before the `[DONE]` event. Here is an example of a raw api call (with `max_tokens` set to 1): ```...