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
Describe the bug
The apply(ChunkData data) function does not print an error trace to the log file when its execution fails.
To Reproduce
Go to 'Tools > Change fields'
Click on 'Script'
Enter any script that would produce an error into the function body of apply. Simplest example: a
Click 'OK'
Click 'OK' in the confirmation dialog
View the log file
Observe the absence of error trace in the log
Expected behavior
If the apply method produces any error while being executed, then a trace message for the exception should be printed to the log file in a similar fashion as how the "Custom" field and the before and after methods had done it.
First, I though this was an error on your side, but then I looked at the code and realized you're actually absolulety right. While it does print that there was an error, it does not print what exactly the error was.
Unfortunately, we can't really do anything about it until Querz is back and can merge the open PRs :(
Describe the bug
The
apply(ChunkData data)
function does not print an error trace to the log file when its execution fails.To Reproduce
apply
. Simplest example:a
Expected behavior
If the
apply
method produces any error while being executed, then a trace message for the exception should be printed to the log file in a similar fashion as how the "Custom" field and thebefore
andafter
methods had done it.Screenshots and other files
mcaselector.log
Environment:
The text was updated successfully, but these errors were encountered: