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

[1.1.3.dev3] Components are not waiting for all connected inputs #6062

Open
severfire opened this issue Feb 1, 2025 · 3 comments
Open

[1.1.3.dev3] Components are not waiting for all connected inputs #6062

severfire opened this issue Feb 1, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@severfire
Copy link

Bug Description

Components are not waiting for all connected inputs and starting executing when whichever connecting to input hits first.
IMHO it is critical issue - cause it breaks main functionality of langflow, which is relying on connecting components and they should be executed in right order.

Reproduction

  1. Create for example loop flow
  2. Try to do something more complicated in it, like with Prompt connecting to Google Generative AI from outside the main line of loop
  3. Connect other fields
  4. It breaks if it missing info, one for sure will be ignored and if required and critical for functionality it will break

more details at:
https://discord.com/channels/1116803230643527710/1334573004029431900

Expected behavior

it should work

Who can help?

@ogabrielluiz @anovazzi1

Operating System

Ubuntu

Langflow Version

Version 1.1.3.dev3

Python Version

None

Screenshot

No response

Flow File

No response

@severfire severfire added the bug Something isn't working label Feb 1, 2025
@severfire severfire changed the title Components are not waiting for all connected inputs [1.1.3.dev3] Components are not waiting for all connected inputs Feb 1, 2025
@severfire
Copy link
Author

@ogabrielluiz i was able to resolve this issue by using async in functions of the components - checking further

@ogabrielluiz
Copy link
Contributor

That's interesting! Maybe threads are making things run in the incorrect order...

@severfire
Copy link
Author

Hi, next week I will check this issue with newest nightly version

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

2 participants