vscode-language-renpy icon indicating copy to clipboard operation
vscode-language-renpy copied to clipboard

Error: Illegal argument: character must be non-negative

Open renpytom opened this issue 2 years ago • 2 comments

I've been getting the attached error in language-renpy v , in vs code 1.79.2. When it happens, it interrupts my typing, with a second-long pause. I'm seeing this in the extension host output - not sure if there's something more directly part of vs code. It seems to happen when editing strings in the renpy/common directory.

I'm also seeing a lot of "The token tree is not covering the entire match range" errors in the developer tools console.

To repeat, go to renpy/common/00director.rpy, line 1372, and add a space after int(v), at the end of the line.

2023-06-22 23:03:23.278 [error] [LuqueDaniel.languague-renpy] provider FAILED
2023-06-22 23:03:23.285 [error] Error: Illegal argument: character must be non-negative
    at m (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:7:1267)
    at new s (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:13554)
    at t.getSignatureHelp (/home/tom/.vscode/extensions/luquedaniel.languague-renpy-2.2.1/dist/extension.js:2:73557)
    at Object.provideSignatureHelp (/home/tom/.vscode/extensions/luquedaniel.languague-renpy-2.2.1/dist/extension.js:2:29736)
    at be.provideSignatureHelp (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:101:56126)
    at /usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:101:73424
    at oe.s (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:101:63904)
    at oe.$provideSignatureHelp (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:101:73410)
    at s.N (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11717)
    at s.M (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11435)
    at s.H (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:10477)
    at s.G (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:9494)
    at /usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:8282
    at b.invoke (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at deliver (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
    at n.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
    at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
    at /usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:32461
    at b.invoke (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
    at deliver (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2121)
    at n.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:1729)
    at p.fire (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:73:14783)
    at MessagePortMain.<anonymous> (/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:30587)
    at MessagePortMain.emit (node:events:513:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367)

renpytom avatar Jun 23 '23 03:06 renpytom

Hi tom, it seems you are still using v2.2.1.

at t.getSignatureHelp (/home/tom/.vscode/extensions/luquedaniel.languague-renpy-2.2.1/dist/extension.js:2:73557)

In 2.2.1 we had a bug in the tokenizer that would cause an infinite loop or major slowdown in some cases. v2.2.2 stable was just released with all the bug fixes from the pre-release version so it should be okay in the latest build.

I did try to reproduce it, but I was unable to do so. Let me know if you are still experiencing issues in the latest build and I'll be happy to take another look :)

duckdoom4 avatar Jun 23 '23 13:06 duckdoom4

I actually did manage to find the error you got. #352 should fix that, though it seems the error is unrelated to the interrupted typing

duckdoom4 avatar Jun 23 '23 15:06 duckdoom4