-
Notifications
You must be signed in to change notification settings - Fork 24
Report a bug in PythonFunction.node.ts #12
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
Comments
I think it should be |
Hi @KevinRich651 |
hi @naskio Many thanks for your reply. The entire python code is huge. I removed the irrelevant code, only left the key part related to this issue. The code is as following:
![]()
![]() |
hi @naskio any ideas about this issue? Thank you in advance. |
hi @naskio would you mind to take a brief look at this issue. Perhaps a cue from you will help me a lot. |
Hi @KevinRich651 |
Thanks for your suggestion. I will take a try. I am still confused why the error response in n8n web page and cloud logging is totally different? |
hi @naskio I located the accurate line, which triggers the failure. I have never encountered so weird a issue...
In the above code, all_data is a pandas Dataframe containing hundreds of rows. It can run normally and output what I expect, no error log and items is a valid json array from the previous node. But if I comment or remove the line I run the above code in local environment, the code also runs normally. My thoughts:In the GCP logging, I still get the same error as I attached couple weeks ago. What weird! Hope to get some suggestions from you |
hi Naskio,
I encountered a troublesome issue in the n8n.
I think it might be a bug in this code
In line 195, the code 0 represent success, but the stderr will be parse.
if (!code) { returnData.items = parseShellOutput(returnData.stderr); } else { returnData.error = new Error(returnData.stderr); }
The text was updated successfully, but these errors were encountered: