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
{{ message }}
This repository was archived by the owner on Aug 31, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 31, 2023. It is now read-only.
Rome 12.1.1 running in https://github.com/sonnyp/Workbench/
bash-5.1$ /app/bin/rome rage
CLI:
Version: 12.1.1
Color support: true
Platform:
CPU Architecture: x86_64
OS: linux
Environment:
ROME_LOG_DIR: unset
NO_COLOR: unset
TERM: "xterm-256color"
JS_RUNTIME_VERSION: unset
JS_RUNTIME_NAME: unset
NODE_PACKAGE_MANAGER: unset
Rome Configuration:
Status: Loaded successfully
Formatter disabled: false
Linter disabled: false
Organize imports disabled: true
VCS disabled: false
Workspace:
Open Documents: 0
Discovering running Rome servers...
What happened?
The server crashed when typing constructor(){. See snippet below.
Rome encountered an unexpected error
This is a bug in Rome, not an error in your code, and we would appreciate it if you could report it to https://github.com/rome/tools/issues/ along with the following information to help us fixing the issue:
Source Location: /home/runner/work/tools/tools/crates/rome_js_semantic/src/semantic_model/model.rs:332:19
Thread Name: tokio-runtime-worker
Message: no entry found for key
The snippet:
importGObjectfrom"gi://GObject";importGtkfrom"gi://Gtk?version=4.0";Gtk.init();constAwesomeButton=GObject.registerClass({GTypeName: "AwesomeButton",Template: workbench.template,},classAwesomeButtonextendsGtk.Button{constructor(){// server crash when I type the `{`onclicked(){console.log("Clicked");}},);constcontainer=newGtk.FlowBox({hexpand: true,});for(leti=0;i<100;i++){constwidget=newAwesomeButton();container.append(widget);}workbench.preview(container);
Expected result
The LSP really shouldn't crash when the user type something.
These issues are very hard to debug, specially when they happen to end-users. LSP clients don't show stderr.
Environment information
What happened?
The server crashed when typing
constructor(){. See snippet below.The snippet:
Expected result
The LSP really shouldn't crash when the user type something.
These issues are very hard to debug, specially when they happen to end-users. LSP clients don't show stderr.
Is there no safeguard you can put in place?
Code of Conduct