Skip to content
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

environment variable is null when execute node #10065

Open
5 tasks done
Qiuzg opened this issue Oct 30, 2024 · 3 comments
Open
5 tasks done

environment variable is null when execute node #10065

Qiuzg opened this issue Oct 30, 2024 · 3 comments
Labels
🐞 bug Something isn't working

Comments

@Qiuzg
Copy link

Qiuzg commented Oct 30, 2024

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.2

Cloud or Self Hosted

Self Hosted (Docker), Self Hosted (Source)

Steps to reproduce

In version 0.10.2, when executing a node individually, if the node requires the use of environment variables, the input value obtained for the environment variable is none. However, when the entire process is executed, the environment variables can be obtained. This issue did not exist in version 0.9.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Oct 30, 2024
Copy link

dosubot bot commented Oct 30, 2024

The issue you're experiencing, where environment variables are null when executing a node individually in version 0.10.2, might be related to how the VariablePool class initializes and manages environment variables. When executing nodes individually, it's possible that the environment variables are not being correctly passed or initialized in the VariablePool.

In the Dify codebase, the VariablePool class is responsible for managing environment variables, and it initializes them by accepting them as an optional parameter during its initialization. These variables are then added to the pool for access during node execution [1].

To address this issue, you might want to check if the environment variables are being correctly passed to the VariablePool when executing nodes individually. Ensure that the initialization process for the VariablePool includes the necessary environment variables in this context, similar to how they are handled when executing the entire process.

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 30, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2024
@dosubot dosubot bot removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Dec 15, 2024
@Qiuzg
Copy link
Author

Qiuzg commented Dec 18, 2024

this bug still exists

@dosubot dosubot bot reopened this Dec 18, 2024
Copy link

dosubot bot commented Dec 18, 2024

@takatost, the user Qiuzg has indicated that the bug still exists despite the issue being marked stale and closed. Could you please assist them with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant