Xerios
commented
1 month ago This issue has been annoying me for quite some time. Happens quite often and its been like that since as long as I can remember.
- Very hard to reproduce, but I think it occurs often during refactors (although it might've occurred once for a very large js file few months ago, but it wasn't reproducible)
> Biome restart LSP serverdoesn't fix the issue (bugged instances still remain even on newer code or files)- Duplicated msgs/bugged instances only grow (e.g. it starts with two duplicate errors then eventually through unknown means it becomes x7 )
- Biome output or trace don't seem to contain any useful information or errors
- Nothing helpful in vscode's DevTools
> Developer: Reload Windowfixes the issue- happened when I had biome part my
package.jsonand it also happens now that I use bundled version
biome version: since 1.6.x to current 1.8.3
vscode version: since 1.88.x to current 1.91.0
platform: windows
const currDate = Number.parseIntarseIntarseIntarseIntarseIntarseIntarseInt(window.revision, 36)Observed behavior
The erroneous change doesn't get applied in one go, I can see it parseInt duplicating several times (most likely up to the amount of error messages) until it settles. Often misses a letter or modifies an unrelated line making the whole code into a mess.
This affects any fixable rule (e.g. template strings, imports, etc.. ) which ends up being applied multiple times. Doesn't matter if it's a manual "Quick Fix" or through "format on save". This happens for both linter's auto-fixes and formatter, both are affected.
This often corrupts the code in a noticeable way, but sometimes the corrupted code ends up being subtle and valid which ends up wasting a lot of time (e.g. when it only duplicates two times).
When multiple auto-fixes are present in the file, it can completely destroy parts of the code. Almost as if each biome instance has their content cached and is unaware of previous biome instance's changes, which ends up in with every biome instance applying their changes blindly like 7 monkeys trying to type a sentence at the same time on a single typewritter.
I'm unsure how exactly to replicate this issue, but I do think this happens more often when I'm refactoring code (e.g. find and replace across multiple files) then saving multiple files ( saveAll command using Ctrl+K S shortcut )
Perhaps unrelated: Old version of biome.json file got loaded while I was changing file. Oddly enough I had latest version of config loaded, made a new change, then it loaded the version prior to my latest. Unfortunately, I didn't check if I had duplicate biome msgs due to my sudden reflex of reloading the app.
Temp workaround
Using > Developer: Reload Window command in Command Palette fixes this until it occurs again.
ematipico
throrin19
0-CAT
nhedger
radium-v
VS Code version
1.89.1
Extension version
2.2.2
Biome version
1.7.3
Operating system
Description
Hello, We have a weird problem in our vscode with biome.
Sometimes Biome doesn't display warnings once, but x times, as if there were several instances of Biome in the background.
This is all the more problematic when saving fixes (and especially when reordering imports), which can cause Biome to step on itself between its different instances.
The only way we've found to undo this is to completely restart VSCode, which is not an acceptable solution in the medium/long term :
And for example before formating :
And after :
Steps to reproduce
Unknown, We don't know why biome runs several times in the background
Expected behavior
Biome for vscode launch correctly with only one instance and all formatting is correct.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Logs
No response