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 e796dd5
Browse filesBrowse the repository at this point in the historyBrowse files
The suggestion reaches the client only once the model has finished writing it, so nothing appears until the whole generation is done.
Serve it from GET /integration/ai/stream as a UI message stream, text/event-stream carrying typed parts. The alternative, pipeTextStreamToResponse, writes the model's text as bare bytes under text/plain; that body has no framing, so everything in it is content and the server cannot say that what follows is a failure rather than more of the answer.
The route reuses the workspace membership check that guards the GraphQL field, which is why checkUserInWorkspaceByProjectId becomes exported. The Express request helper written for the GitHub route tests moves to test/helpers/expressRequest.ts so both suites share one copy.
Event lookup fails the same way whether the factory throws or returns nothing: both become "Event not found", which the route answers with 404. The one-shot path shares that helper, so a lookup error no longer leaves it with its original message.
0 commit comments