Open
Description
I am on the Nightly release channel of serve-d on osx aarch64
.
serve-d standalone v0.8.0-beta.15
Included features: "d", "workspaces"
Built: Thu Apr 4 02:26:06 2024
with compiler LDC v2.107 on osx aarch64
dub, dfmt and dscanner are bundled within (compiled in)
2024-04-11T12:44:18.645 [error] serverbase.d:427:__lambda2 Failed processing notification: mir.ion.exception.IonException@../../../.dub/packages/mir-ion/2.2.1/mir-ion/source/mir/ion/exception.d(297): IonException: unexpected Ion type
----------------
??:? pure nothrow @trusted rt.critical_.D_CRITICAL_SECTION* core.lifetime._d_newitemT!(rt.critical_.D_CRITICAL_SECTION)._d_newitemT() [0x102f07027]
mir.ion.exception.IonException@../../../.dub/packages/mir-ion/2.2.1/mir-ion/source/mir/ion/exception.d(297): IonException: unexpected Ion type
----------------
??:? pure nothrow @trusted rt.critical_.D_CRITICAL_SECTION* core.lifetime._d_newitemT!(rt.critical_.D_CRITICAL_SECTION)._d_newitemT() [0x102f07027]
[Info - 12:44:20 PM] Connection to server got closed. Server will restart.
serve-d standalone v0.8.0-beta.15
Included features: "d", "workspaces"
Built: Thu Apr 4 02:26:06 2024
with compiler LDC v2.107 on osx aarch64
dub, dfmt and dscanner are bundled within (compiled in)
2024-04-11T12:44:20.104 [error] serverbase.d:427:__lambda2 Failed processing notification: mir.ion.exception.IonException@../../../.dub/packages/mir-ion/2.2.1/mir-ion/source/mir/ion/exception.d(297): IonException: unexpected Ion type
----------------
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
Activity
redthing1 commentedon Apr 11, 2024
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.
redthing1 commentedon Apr 11, 2024
And here is a detailed log, from running serve-d from source:
redthing1 commentedon Apr 11, 2024
I believe I found the issue: looks like my settings synced at the same time the update happened. The problematic part of the config:
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.