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
Because basically every variable is assigned to be "null"
So this situation could just be more gracefully handled by spitting out an error message to the user saying parsing failed. Also exceptions really ought to be dumped into the log file. See my log file below - there's nothing after the cache root line when it terminates.
/* These are simple defaults for your project. *//world
mob=/mob
turf=/turf/spacearea=/area/spacefps=25// 25 frames per secondicon_size=32// 32x32 icon size by defaultview=6// show up to 6 tiles outward from center (13x13 view)// Make objects move 8 pixels per tick when walking/mobstep_size=8/objstep_size=8/turf/space/area/space// Upset the parser/node/expression/operator/binary// Break the parser/node/interpreter/proc/Evaluate(node/expression/operator/binary)return
Open StrongDMM
File > Open > Select your test dme file.
Crash w/o anything logged. If ran from VSC with go extensions and exceptions enabled, you'll catch the fatal panic from earlier.
Version
v2.10.0.alpha and latest master 754d662
What happened?
StrongDMM crashes and does not log any error if it attempts to load an environment that spacemandmm has failed to parse.
It took some effort, but I was able to build from source to be able to catch the exception:
The problem is that in
StrongDMM/internal/dmapi/dmmap/storage.go
Line 36 in 754d662
the variable
path
can be"null"
when called fromStrongDMM/internal/dmapi/dmmap/dmmap.go
Line 30 in 754d662
Because basically every variable is assigned to be "null"
So this situation could just be more gracefully handled by spitting out an error message to the user saying parsing failed. Also exceptions really ought to be dumped into the log file. See my log file below - there's nothing after the cache root line when it terminates.
Reproduction
Relevant log output
The text was updated successfully, but these errors were encountered: