Skip to content

Upstream merge - #183

Open
Sandeep-BA wants to merge 21 commits into
redbus-labs:mainfrom
google:main
Open

Upstream merge#183
Sandeep-BA wants to merge 21 commits into
redbus-labs:mainfrom
google:main

Conversation

@Sandeep-BA

Copy link
Copy Markdown
Collaborator

Please ensure you have read the contribution guide before creating a pull request.

Link to Issue or Description of Change

1. Link to an existing issue (if applicable):

  • Closes: #issue_number
  • Related: #issue_number

2. Or, if no issue exists, describe the change:

If applicable, please follow the issue templates to provide as much detail as
possible.

Problem:
A clear and concise description of what the problem is.

Solution:
A clear and concise description of what you want to happen and why you choose
this solution.

Testing Plan

Please describe the tests that you ran to verify your changes. This is required
for all PRs that are not small documentation or typo fixes.

Unit Tests:

  • I have added or updated unit tests for my change.
  • All unit tests pass locally.

Please include a summary of passed java test results.

Manual End-to-End (E2E) Tests:

Please provide instructions on how to manually test your changes, including any
necessary setup or configuration. Please provide logs or screenshots to help
reviewers better understand the fix.

Checklist

  • I have read the CONTRIBUTING.md document.
  • My pull request contains a single commit.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have manually tested my changes end-to-end.
  • Any dependent changes have been merged and published in downstream modules.

Additional context

Add any other context or screenshots about the feature request here.

damianmomotgoogle and others added 21 commits July 16, 2026 06:43
Config-driven loaders confine every reflectively loaded class to the intended
type (BaseTool, BaseToolset, BaseExampleProvider, or the caller's expectedType)
before constructing it or reading a static field, so a non-intended type is never
instantiated nor its static initializer run (type-confinement, not a sandbox).

CompiledAgentLoader also gains source-dir confinement
(adk.agents.confine-to-source-dir), keeping compiled agents within source-dir.
Type confinement is on by default; source-dir confinement is off by default (with
a warning) to avoid breaking existing setups, and will default on in a future
release.

PiperOrigin-RevId: 948941874
…to match python ADK

PiperOrigin-RevId: 949268862
…sion/listEvents

FirestoreSessionService stores each session at /{root}/{userId}/sessions/{sessionId},
so the document is keyed only by (userId, sessionId). getSession, deleteSession, and
listEvents fetched the document by (userId, sessionId) and never checked the stored
appName against the requested one, so a caller could read, list the events of, or
delete another application's session for the same user by passing any appName.
listSessions already scopes by appName (whereEqualTo(APP_NAME_KEY, appName)).

Add the same appName check to getSession, deleteSession, and listEvents, treating a
mismatch as "session not found", and add unit tests covering the appName-mismatch
cases for all three methods.
Prevents a NullPointerException in the google-genai library when an Agent is defined without a description. Includes a regression test.
…oserverparams

PiperOrigin-RevId: 951989850
…rces

Ensure every Java source carries the canonical Apache 2.0 header from
`java.header`, without changing existing copyright years (the year reflects
when a file was created):

- Add the header to files that were missing it, using each file's creation year.
- Repair malformed headers: drop duplicated/garbled lines and convert
  `//`-style headers to the required `/* */` block form, preserving the year.

PiperOrigin-RevId: 952623369
…nMemorySessionService

`getSession` applied `afterTimestamp` only when `numRecentEvents` was unset, so the two `GetSessionConfig` filters could not be combined. Apply `numRecentEvents` first, then `afterTimestamp`, so both compose. Mirrors Python and Go, which already apply both.

PiperOrigin-RevId: 952725154
…ertexAiSessionService

`getSession` gated the server-side `timestamp>=` filter on `numRecentEvents` being absent, so the two `GetSessionConfig` filters could not be combined. Send the `afterTimestamp` filter whenever it is set and still trim to `numRecentEvents` client-side, so both compose. Mirrors the Go port, which already applies both.

PiperOrigin-RevId: 952765675
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.

8 participants