You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6256bf0
Browse filesBrowse the repository at this point in the historyBrowse files
fix!: Rename blocking to returnImmediately in SendMessageConfiguration
Sync a2a.proto with upstream (dec790a -> 601c408).
The `blocking` field in `SendMessageConfiguration` has been renamed to
`return_immediately` with inverted semantics:
- `blocking=true` (wait) -> `returnImmediately=false`
- `blocking=false` (return immediately) -> `returnImmediately=true`
The default behavior changed: `false` now means "wait for completion"
instead of "return immediately".
BREAKING CHANGE: `MessageSendConfiguration.blocking()` renamed to
`returnImmediately()`. Builder method `.blocking(boolean)` renamed to
`.returnImmediately(boolean)` with inverted value. JSON wire format
field changed from `"blocking"` to `"returnImmediately"`.
Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
LOGGER.debug("DefaultRequestHandler: Client sent configuration but blocking=null, using default blocking={} for task {}", blocking, taskId.get());
453
+
LOGGER.debug("DefaultRequestHandler: Client sent configuration but returnImmediately=null, using default blocking={} for task {}", blocking, taskId.get());
453
454
} else {
454
455
LOGGER.debug("DefaultRequestHandler: Client sent no configuration, using default blocking={} for task {}", blocking, taskId.get());
0 commit comments