-
Notifications
You must be signed in to change notification settings - Fork 74
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
Incorrect message when mapping modules can't be initialized. #1524
Comments
My impression is that the misleading debug message has been in the code since the beginning. Up to 2023-02-25 there also seems to have been an error where the non-existent method |
when the mapping object could not be created. Do not emit the empty error message from a previous function call.
Reusing variable names is not a good practice.
Running the test suite showed new errors:
However these error occur also without the changes for this issue. Thus the PR can be applied. Closing this issue. |
While looking into this, I noticed that there is a mixup of message for the generic interface debugger. When a mapping module can't be initialized then the error message of a previous function result is written into the debug log.
The underlying cause is the reusing of the variable
$FunctionResult
.Creating an extra issue for this, as this is a bug.
Originally posted by @bschmalhofer in #1471 (comment)
The text was updated successfully, but these errors were encountered: