Rick Love

I had the same problem. The build failed, but no error displayed. There needs to be an error message which indicates the limitation.

Found this after making my feature request in #1664. There, I specified that I would like to be able to set properties to static values like this: ```json { "name":...

Tried everything here, then realized I was in the wrong directory in my cli... 30 mins later 😭 😆

Here is a workaround - might submit a PR to implement this: ``` // based on https://stackoverflow.com/a/58691389/567524 const emojiToUnified = (emoji: string) => { const code = [...emoji] .map((x) =>...

Getting this error in a complex workflow - working on identifying the source so I can upload a minimal test case: ``` ERROR:root:!!! Exception during processing !!! ERROR:root:Traceback (most recent...

> Getting this error in a complex workflow - working on identifying the source so I can upload a minimal test case: > > ``` > ERROR:root:!!! Exception during processing...

I tested my most complex workflows and everything is working great! Thanks @guill for the great work!

> @comfyanonymous The remaining backward-incompatibilities -- the `JOVConstantNode` issue and the multi-type (`FLOAT,INT`) issues -- are both a result of the fact that optional inputs are now validated by the...

Edit: This was a client issue where the client used null instead of 'None' string. --- Found a weird setup that looks like it is sometimes as issue. In efficiency...

This is happening often whenever something changes in any package.json. But the workaround seems to work each time: `rm -f bun.lockb && bun install`