Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

VertexAiSessionService: Event.id differs between the streamed event and getSession (id is not sent to Vertex and the appendEvent response is empty)

Ouverte
  • Quelque chose ne va pas ?
#1,651 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@hemasekhar-p y travaille déjà.

Depuis le 13/10/2026.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
java
Domaine
backend

Piste de recherche

Start with VertexAiSessionService.appendEvent and SessionJsonConverter in com.google.adk.sessions, then compare event serialization with the Python fix linked in the issue. Check how the REST rawEvent field can preserve the ADK id and how session loading chooses an id. Done means the streamed event and the event returned by getSession retain the same id, with tests covering the round trip.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

waiting on reporter
Describe the bug

With VertexAiSessionService, the same logical event has two different ids depending on how it is observed:

Observed via Event.id
Runner.runAsync(...) stream ADK-generated UUID (Event.generateEventId())
getSession(...) afterwards Vertex resource id (last segment of the event name)

InMemorySessionService keeps the ADK UUID, so the two services behave differently and the problem does not show up in local development.

Where (checked on 1.8.0 and 1.10.1)
  1. BaseLlmFlow creates the id with Event.generateEventId() (a random UUID) and resets it for each resulting event.
  2. Runner.runAsync calls sessionService.appendEvent(session, event) for every non-partial event, then emits the event to the caller.
  3. VertexAiSessionService.appendEvent sends SessionJsonConverter.convertEventToJson(e) to :appendEvent. That JSON contains author, invocationId, timestamp, actions, eventMetadata and content, but no event id, and no rawEvent (there is no reference to rawEvent anywhere in com.google.adk.sessions in these versions).
  4. VertexAiClient.appendEvent only checks the response body for ClientException and returns Completable.complete(). VertexAiSessionService.appendEvent then returns the local event (.toSingleDefault(e)), so the caller keeps the ADK UUID.
  5. On getSession, SessionJsonConverter rebuilds the id from the API resource name:
    .id(Iterables.getLast(Splitter.on('/').split(apiEvent.get("name").toString())))
What the API allows

From the SessionEvent REST reference:

  • name is documented as "Identifier. The resource name of the event" (…/sessions/{session}/events/{event}). There is no other field meant to carry a client-assigned event id.
  • rawEvent is "Optional. Weakly typed raw event data in proto struct format."
  • sessions.appendEvent returns an empty body on success, so the id created by the service is not available at append time.
Documentation

The Events documentation says that the session service "records the event as it received it" (in the Python description) and recommends using event.id to reference specific occurrences. This does not hold for VertexAiSessionService: the id seen during the run is never stored and is replaced on reload.

Impact

Anything that correlates a streamed event with its persisted form by Event.id breaks. In our case (a chat UI built on top of an AG-UI endpoint), message ids sent to the client while streaming do not match the ids returned when the conversation is reloaded, so per-message state (for example feedback) can be attached to an id that no longer exists. The only workaround we found is to reload the session after the run and pair events by invocationId and order while checking the text, which is fragile.

Expected behavior

One of:

  • Persist the ADK id (for example in rawEvent, as ADK Python now does) and prefer it over the resource name when reading; or
  • Make the id assigned by Vertex available to the caller at append time (not possible today since the response is empty); or
  • If neither is possible, document that Event.id is not stable across streaming and reload on this service.
Related
  • google/adk-python#6530: same behavior in Python, closed as a bug and fixed by keeping the id stored in raw_event (commit 864914b). The Java converter does not write rawEvent, so that fix does not port directly.
  • google/adk-go#1329: same behavior in Go (open), noting that SessionEvent has no field for a client event id.
Environment
  • google-adk 1.8.0 (the same code is present in 1.10.1)
  • VertexAiSessionService on Vertex AI Agent Engine sessions
Langage dominant
Java
Étoiles
1.7k
Forks
433
Merge moyen
2 j 23 h
PR mergées (30 j)
52

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de google/adk-java

Toutes les issues de google/adk-java

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.