| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
errors (#2463)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
Co-authored-by: Allen Hutchison <[email protected]>
|
|
Co-authored-by: Allen Hutchison <[email protected]>
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
|
|
Co-authored-by: Jacob Richman <[email protected]>
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
Co-authored-by: Scott Densmore <[email protected]>
|
|
|
|
|
|
429 errors (#1376)
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
|
|
This commit refactors the `usageStatisticsEnabled` setting from a sub-property of the `telemetry` configuration to a top-level setting. This change simplifies the configuration by decoupling usage statistics from the telemetry settings.
The documentation has also been updated to reflect this change.
|
|
(#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.
|
|
|
