Post #2386011

2026-05-03 23:51 UTC

@jacksonchen666 lmao take a look at this shit 🙃 in the process, I discovered that the vscode changelogs are a lie, and the behavior was actually introduced in 1.117 not 1.118. the fix still hasn&#39;t been released, so I suspect that the dropoff at the end there is a result of commits authored in the past few days not having been pushed yet rather than actually related to the 1.118 release. charles did have a more optimistic hypotheses, that it might be the result of folks catching on and disabling the flag or leaving vscode entirely. I&#39;m choosing to hope for that one :) (source code to collect and plot data)

Replies (2)

@leo@60228.dev 2026-05-04 19:07

@olivia@pl.firechicken.net @jacksonchen666@micro.jacksonchen666.com the logic is implemented by checking analytics data to see if the "accepted copilot edits" counter increased since the last commit and the issue was that that counter was being spuriously incremented in unclear scenarios, since afaik the copilot implementation itself is closed-source it might have been updated out-of-band?

Open ##2626301
@jacksonchen666@micro.jacksonchen666.com 2026-05-03 23:56

@olivia@pl.firechicken.net horrendous :DDDDDDDD i'm still stumbling over whether it was 1.117.0 or 1.118.0. the complaints only really seem to have started around 1.118.0, but github says the commits are part of 1.117.0. i guess it was part of 1.117.0 then well time to hack in extra special checks for this special case :p

Open ##2626302