| Age | Commit message (Collapse) | Author |
|
logging. (#6074)
Co-authored-by: christine betts <[email protected]>
Co-authored-by: Jacob Richman <[email protected]>
Co-authored-by: matt korwel <[email protected]>
|
|
|
|
telemetry" (#6161)
|
|
Co-authored-by: jacob314 <[email protected]>
|
|
|
|
|
|
Co-authored-by: christine betts <[email protected]>
Co-authored-by: Jacob Richman <[email protected]>
Co-authored-by: matt korwel <[email protected]>
|
|
|
|
Co-authored-by: Ravikant Agarwal <[email protected]>
|
|
|
|
Co-authored-by: Shi Shu <[email protected]>
|
|
Firebase Studio (#5790)
|
|
|
|
Co-authored-by: Ravikant Agarwal <[email protected]>
|
|
and add logging of connection events (#5591)
Co-authored-by: matt korwel <[email protected]>
|
|
|
|
ToolCallResponseInfo and ToolResult (#5222)
|
|
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
|
|
|
|
|
|
|
early return for empty events (#1601)
Co-authored-by: Scott Densmore <[email protected]>
|
|
Co-authored-by: N. Taylor Mullen <[email protected]>
|
|
|
|
|
|
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
|
Co-authored-by: N. Taylor Mullen <[email protected]>
|
|
Co-authored-by: Dcatfly <[email protected]>
|
|
|
|
Co-authored-by: matt korwel <[email protected]>
|
|
|
|
|
|
|
|
(#3914)
|
|
|
|
|
|
|
|
(#3744)
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
remove debug logs (#1393)
|
|
Fix for Clearcut logging wire format based on validation thread with Clearcut / Concord eng
|
|
(#1357)
|
|
The previous implementation used `flushIfNeeded` to batch most telemetry events, but it was not reliably sending them, leading to data loss. Notably, the `startSession` event, which already used `flushToClearcut`, was working correctly, indicating an issue with the batching logic itself.
This change replaces all calls to `flushIfNeeded` with `flushToClearcut` to align all event logging with the working `startSession` implementation and ensure that events are sent immediately. This prioritizes the reliability of data collection over network efficiency.
This is a temporary solution to prevent further data loss. The underlying issue with the batching mechanism in `flushIfNeeded` should be investigated and fixed in the future, at which point this change can be reverted.
|