Get Variable Node Doesn't Work With VariableOutputSocket Setters
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
When a variable is set automatically via a 'VariableOutputSocket' the 'Get Variable' node in the UI throws an error for 'has no attribute save to variable' and prevents you from assigning the output socket value to anything.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the error by setting a variable through a VariableOutputSocket and using the Get Variable node in the UI. Trace the failing “save to variable” lookup, then verify that the output socket value can be assigned without an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100