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

Error Forwarding #145

Open
mcmonkey4eva opened this issue Jul 31, 2024 · 2 comments
Open

Error Forwarding #145

mcmonkey4eva opened this issue Jul 31, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@mcmonkey4eva
Copy link
Member

Currently when you comfy run (...) some workflow and it fails, eg because the comfy server failed to load, the CLI simply tells you "Workflow completed in 0.01 seconds" and nothing more.

It should ideally instead forward an error message

  • possibly on stderr?
  • should support fundamental errors like the backend server being missing
  • Should also make sure it properly forwards things like basic node errors
  • whenever comfy backend gives a clear error message, the CLI should display the full remote error text (don't shorten/simplify unless it's very confidently tracked to a more precise reason)
@mcmonkey4eva mcmonkey4eva added the enhancement New feature or request label Jul 31, 2024
@abhinavzspace
Copy link

For now, what could be the workaround for this. This seems to be quite necessary for me.

I am running comfy in background through comfy-cli and invoking workflows through run command. How can I check the errors?

@gmpetrov

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants