Joseph T. Lyons b6189b05f9 Add telemetry for supermaven (#11821) ... Data migration plan: - [X] Make a duplicate table of `copilot_events` - Name: `inline_completion_events` - Omit `suggestion_id` column - [X-reverted-skipping] In collab, continue to match on copilot_events, but simply stuff their data into inline_completion_events, to forward it to the new table - [skipping] Once collab is deployed, ensure no events are being sent to copilot_events, migrate `copilot_events` to new table via a transaction - [skipping] Delete `copilot_events` table --- - [X] Locally test that copilot events sent from old clients get put into inline_completions_table - [X] Locally test that copilot events and supermaven events sent from new clients get put into inline_completions_table --- - [X] Why are discard events being spammed? - A: 8d4315712b/crates/editor/src/editor.rs (L2147)  This will throw off the past results for accepted / dismissed that I was wanting to use to evaluate Supermaven quality, by comparing its rate with copilot's rate. I'm not super thrilled with this fix, but I think it'll do. In the `supermaven_completions_provider`, we check if there's a `completion_id` before sending either an accepted or discard completion event. I don't see a similar construct in the `copilot_completions_provider` to piggyback off of, so I begrudgingly introduced `should_allow_event_to_send` and had it follow the same pattern that `completion_id` does. Maybe there's a better way? --- Adds events to supermaven suggestions. Makes "CopilotEvents" generic -> "InlineCompletionEvents". Release Notes: - N/A		2024-05-16 17:18:32 -04:00
..
src	Add telemetry for supermaven (#11821)	2024-05-16 17:18:32 -04:00
Cargo.toml	Supermaven (#10788)	2024-05-03 12:50:42 -07:00
LICENSE-GPL	chore: Change AGPL-licensed crates to GPL (except for collab) (#4231)	2024-01-24 00:26:58 +01:00