Fix JS runtime operation not permitted issue in M1 orbstack #129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dify Version:
Deployment Environment:
Self-Hosted (M1 MacBook with OrbStack Docker)
Issue Description
When creating a new workflow and selecting the Code block, after running the JavaScript runtime returns an empty result accompanied by
operation not permittederrors, whereas the Python runtime executes normally. Further investigation revealed that under certain conditions, Node.js triggers a failed with signal: bad system call error.Root Cause and Resolution
Although the exact root cause of the error remains unclear, testing indicates that upgrading the Golang version resolves the issue.
Changes in This PR
This PR should address the issue with the Node.js runtime while also enhancing the overall build reliability and efficiency.
Test the updated version using my DockerHub image:
🔗 DockerHub: knowlet/dify-sandbox:0.2.11
Reference:
langgenius/dify#7687
langgenius/dify#12287
FIx #128