You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I sometimes abuse unsaved files in an open project as a notepad, when I do that, CSC seems to try to run on them which fails with the following message
Steps to reproduce
Open new file in a project that uses Biome
Don't save it
Write something to trigger Biome
Expected behavior
No errors
Does this issue occur when using the CLI directly?
No
Logs
Copying binary to temporary folder: file:///home/stan/.vscode-server/data/User/workspaceStorage/af22f4201bf263a53fb80c4d8a54ca94/biomejs.biome/biome
Executing Biome from: /home/stan/.vscode-server/data/User/workspaceStorage/af22f4201bf263a53fb80c4d8a54ca94/biomejs.biome/biome
[cli-stdout] data 43
[cli] exit 0
Connecting to "/home/stan/.cache/biome/biome-socket-1.8.3" ...
[Info - 4:37:44 PM] Server initialized with PID: 207559
[Error - 5:17:41 PM] Request textDocument/codeAction failed.
Message: failed to access range Range { start: Position { line: 7, character: 0 }, end: Position { line: 7, character: 0 } } in document untitled:Untitled-1 LineIndex { newlines: [0, 45, 46, 83, 84, 135, 136], line_wide_chars: {} }
Code: -32603
failed to access range Range { start: Position { line: 7, character: 0 }, end: Position { line: 7, character: 0 } } in document untitled:Untitled-1 LineIndex { newlines: [0, 45, 46, 83, 84, 135, 136], line_wide_chars: {} }
Caused by:
position Position { line: 7, character: 0 } is out of range
The text was updated successfully, but these errors were encountered:
VS Code version
1.92.2
Extension version
2.3.0
Biome version
1.8.3
Operating system
Description
I sometimes abuse unsaved files in an open project as a notepad, when I do that, CSC seems to try to run on them which fails with the following message
Steps to reproduce
Expected behavior
No errors
Does this issue occur when using the CLI directly?
No
Logs
The text was updated successfully, but these errors were encountered: