-
Notifications
You must be signed in to change notification settings - Fork 3
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
lark.exceptions.GrammarError: Dynamic Earley doesn't support weights on terminals #3
Comments
Try removing lark-parser. That's some weird package that seems to break things. I have lark 1.1.9 in my own venv and it works fine. |
Unfortunately, removing lark-parser not only didn't fix comfyui-utility-nodes but broke yet two extensions instead: comfyui-prompt-control and ComfyUI-Easy-Use. And, of course, after the second ComfyUI restarting lark-parser is here again Probably dependencies incompatibility or maybe python version. Mine is I'm afraid I'm not quite ready to reinstall venv from scratch. At least not now while the rest is working (works don't touch). Have any other suggestions? |
My virtualenv uses python 3.11.9, though I'm on linux; the patch version shouldn't matter. If you have some kind of windows-specific bug then I can't be of much help. I have no idea how removing lark-parser could break comfyui-prompt-control, since I don't have that package installed at all in my venv and I would notice if not having it broke prompt control. Maybe some other part of your venv is out of date and causing issues. |
Here's a list of packages in my venv. It probably contains some extra things not strictly needed for ComfyUI but you can use it for reference
|
I thought maybe it the polite reminder to finally clean up my comfy and made the clean install. Only comfy manager, rgthree and yours. Surprisingly or not, it took off Have no idea what it was: yet another bit of pip hell, python version stuff or smth Will try to add one by one only the modules I myself use really. There's a small chance it wouldn't break again. I remembered I saw the modules incompatibility warnings now and then after yet another pip install. All my things were working afterwards though but who knew what these incompatibilities were Many thanks, this cleanup was in my plans for decades) So, when it's working, would you answer please, if it's able to get the another node variables as I hoped for? I need some variable expansion feature like what the the save image node does with filenames. It's a kind of strange, all that I found so far are the two nodes only that can extract only the single value at a time. So it's needed to build the complex node chain instead of simple "A:%node1.fileld1%, B:%node2.field2%" or such |
MUSimpleWildcard doesn't look into other nodes. The values they produce aren't available when expansion happens, and with ComfyUI's lazy evaluation of graphs nowadays, the only way to guarantee that a node's output is available to another node is to connect their input and output. It might be possible to look up literal inputs to other nodes since ComfyUI sends those with the graph, but that's not currently implemented. Is that what you're looking for? |
Kinda sad to know nodes of that kind are not available and it's a bit of strange at once. Why? Am I the one only who need some debugging info inside of the workflow? Some days ago I was building the complex workflow with more or less complicated calculations and I needed to know what the intermediate variables were and the debugging part turned out pretty horrifying clutter of ins, outs, concats and substs. I finally managed them into the group node but it's too far from any good and not changeable at all It seems now is the time to make my own node |
Tried to install your extension but got the error
lark==1.1.9
lark-parser==0.12.0
ComfyUI yesterday's 2024-09-06 10:21, c27ebeb1
I found the discussion here with this error description
lark-parser/lark#383
but it's closed at 2019
The text was updated successfully, but these errors were encountered: