-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
[BUG] "Scope not in graph" for children of "for", when using listener #675
Comments
|
I ran into a similar issue. I believe it has to do with iterating over arrays that are contained in listened-for objects. When I isolated the array from the object, only printing the array to the listener raw, the errors stopped. |
bumping this, this might be closed by #1189. feel free to test things out and report your findings there! |
found the problem: i'll see whether i can fix it, it's always this error update: update 2: here's my debugging config:
funnily enough, the whole widget disappears if the initial array is left empty. that's probably a different edge case bug |
Checklist before submitting an issue
Description of the bug
When the listener script outputs a line, eww logs shows: "Scope not in graph"
I went through the code and changed the error so that I could see the Scope index that couldn't be found, and noticed that the values continually get bigger and bigger.
The above statement isn't the issue, I just thought it would be relevant and was trying to do some debugging on my own.
The error leads me to believe that there are hanging references somewhere.
Sorry for not being able to provide more information
Reproducing the issue
Minimal config:
eww.yuck
./desktops:
Expected behaviour
There shouldn't be an error as far as I'm aware, the listeners should stop before the widget updates and the notify is sent.
Additional context
The
bspc query -T --monitor
outputs with the following format:Full output
There are a bunch of omitted fields, so here's a full example output:
Full example output from bspc
Prettified
The text was updated successfully, but these errors were encountered: