-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serve-d
fails to initialize: Failed processing notification: mir.ion.exception.IonException: unexpected Ion type
#364
Comments
I tried downgrading but I still have this issue. Not sure why, because it worked for months until 15 min ago when I decided to update. |
And here is a detailed log, from running serve-d from source:
|
serve-d
fails to initialize after updating to VSCode 1.87.2serve-d
fails to initialize: Failed processing notification: mir.ion.exception.IonException: unexpected Ion type
I believe I found the issue: looks like my settings synced at the same time the update happened. The problematic part of the config: "editor.rulers": [
{
"color": "#e2c75b",
"column": 160
},
{
"color": "#ee3656",
"column": 180
}
], I had done this earlier based on this comment on another issue; looks like setting the above settings causes initialization to fail in this way? I'm not sure what about it causes the crash, but I can definitely reproduce that adding in the above config makes it crash with the above error. |
I am on the Nightly release channel of serve-d on
osx aarch64
.It then goes into a crash loop.
Relevant code: https://github.com/Pure-D/serve-d/blob/master/serverbase/source/served/serverbase.d#L418-L439
The text was updated successfully, but these errors were encountered: