Skip to content

feat: let the ADK Java <-> Kotlin interop run on a caller-supplied dispatcher - #1522

Merged
copybara-service[bot] merged 1 commit into
mainfrom
test_985086481
Sep 21, 2026
Merged

copybara-service[bot] merged 1 commit into
mainfrom
test_985086481

Conversation

@copybara-service

@copybara-service copybara-service Bot commented Sep 21, 2026

Copy link
Copy Markdown

feat: let the ADK Java <-> Kotlin interop run on a caller-supplied dispatcher

JavaAdkToKt and KotlinAdkToJava now accept an optional CoroutineDispatcher (defaulting to Dispatchers.IO) when bridging blocking Java tools, toolsets, plugins, models, and services onto the Kotlin engine. The parameter is defaulted and exposed to Java via @jvmoverloads, so existing callers are unaffected. The supplied dispatcher must be able to service nested bridged calls concurrently, so a single-threaded or tightly bounded one can deadlock.

@copybara-service
copybara-service Bot force-pushed the test_985086481 branch 2 times, most recently from 151337a to a6d3e10 Compare September 21, 2026 10:15
…spatcher

JavaAdkToKt and KotlinAdkToJava now accept an optional CoroutineDispatcher (defaulting to Dispatchers.IO) when bridging blocking Java tools, toolsets, plugins, models, and services onto the Kotlin engine. The parameter is defaulted and exposed to Java via @jvmoverloads, so existing callers are unaffected. The supplied dispatcher must be able to service nested bridged calls concurrently, so a single-threaded or tightly bounded one can deadlock.

PiperOrigin-RevId: 985155333
@copybara-service
copybara-service Bot merged commit 29481a9 into main Sep 21, 2026
1 check passed
@copybara-service
copybara-service Bot deleted the test_985086481 branch September 21, 2026 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant