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
When using the sde build or sde test command, if an error occurs, it currently prints the error message only (without stack trace), for example:
$ ./tests/modeltests longeqns
Testing the longeqns model
ERROR: Cannot read properties of undefined (reading 'size')
This is because the error handler in sde-build.js for example looks like this:
}catch(e){// Exit with a non-zero error code if any step failedconsole.error(`ERROR: ${e.message}\n`)process.exit(1)}
A while back I had changed other sde commands to log the full error message including stack trace, but looks like I missed a couple. We should change these two remaining cases to use the same code as the others:
}catch(e){// Exit with a non-zero error code if any step failedconsole.error(e)console.error()process.exit(1)}
This will result in the full stack trace appearing:
$ ./tests/modeltests longeqns
Testing the longeqns model
TypeError: Cannot read properties of undefined (reading 'size')
at generateArrayFunctionCall (file://sdeverywhere/packages/compile/src/generate/gen-expr.js:650:31)
at generateFunctionCall (file://sdeverywhere/packages/compile/src/generate/gen-expr.js:282:14)
at generateExpr (file://sdeverywhere/packages/compile/src/generate/gen-expr.js:150:14)
...
The text was updated successfully, but these errors were encountered:
When using the
sde build
orsde test
command, if an error occurs, it currently prints the error message only (without stack trace), for example:This is because the error handler in
sde-build.js
for example looks like this:A while back I had changed other
sde
commands to log the full error message including stack trace, but looks like I missed a couple. We should change these two remaining cases to use the same code as the others:This will result in the full stack trace appearing:
The text was updated successfully, but these errors were encountered: