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 am trying to get the LSP to include a library contains a package that I import in my SV files. however when I specify it in the libraryIndexing option the server crashes. this is the log:
[ERROR][2024-11-12 11:28:52] .../vim/lsp/rpc.lua:770 "rpc" "/sbin/svlangserver" "stderr" "/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:395\n for (let incdir of [...new Set(this._srcFiles.map(file => path.dirname(file))), ...new Set(this._srcFiles.map(file => path.dirname(file)))]) {\n ^\n\nTypeError: Cannot read properties of undefined (reading 'map')\n at SystemVerilogIndexer._generateVerilatorOptionsFile (/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:395:55)\n at /usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:76:26\n at f (/usr/lib/node_modules/@imc-trading/svlangserver/node_modules/once/once.js:25:25)\n at Glob.<anonymous> (/usr/lib/node_modules/@imc-trading/svlangserver/node_modules/glob/glob.js:148:7)\n at Glob.emit (node:events:507:28)\n at Glob._finish (/usr/lib/node_modules/@imc-trading/svlangserver/node_modules/glob/glob.js:194:8)\n at next (/usr/lib/node_modules/@imc-trading/svlangserver/node_modules/glob/glob.js:213:12)\n at /usr/lib/node_modules/@imc-trading/svlangserver/node_modules/glob/glob.js:245:9\n at /usr/lib/node_modules/@imc-trading/svlangserver/node_modules/fs.realpath/index.js:37:7\n at LOOP (node:fs:2839:14)\n\nNode.js v23.1.0\n"
~
Any idea why this happens? Am I doing something wrong? Or is it a bug?
The text was updated successfully, but these errors were encountered:
I am trying to get the LSP to include a library contains a package that I import in my SV files. however when I specify it in the
libraryIndexing
option the server crashes. this is the log:Any idea why this happens? Am I doing something wrong? Or is it a bug?
The text was updated successfully, but these errors were encountered: