-
Notifications
You must be signed in to change notification settings - Fork 2
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
pi does not load initial preset intermittently #181
Comments
somehow the latest save of my graph seems to do this every time! Is there something I can send you to help diagnose? maybe this should be on the runner repo rather than this though? |
i wonder if this could be an artifact of the last graph state being loaded and not the last saved graph? it could potentially be the same exact topology as a saved graph but not have a name or presets? |
That might be the case! How does such a state occur? I tend to save a new set on any change that I make and save a preset and the initial preset too. But then I do use the graph which means parameter values get changed before I shut the pi down |
do you mean, it seems to load your set on reboot or have you explicitly loaded your set? |
On reboot before explicitly loading my set it showed the set as loaded (it had the symbol thing next to it) but no presets, after explicitly loading my set it also showed no presets, after saving a new preset my other presets for the set appeared.
…
On Dec 4, 2024 at 10:25 PM, <Alex Norman ***@***.***)> wrote:
>
>
> I looked at this again after starting up the Pi again. This time it seems to load my set, but the presets are not there. Reloading the set did not make the presets appear in the list. Then I saved a new preset and the preset list was populated again! So there's definitely something funky going on here
>
>
do you mean, it seems to load your set on reboot or have you explicitly loaded your set?
—
Reply to this email directly, view it on GitHub (#181 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AEHA6NMCVMIA3G4AM7F5QWD2D56MDAVCNFSM6AAAAABSZR4LAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGY4DGNJSGQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
ahh okay, i suspect that is stale information that the web UI retained, we probably need to clean that up. I bet if you reloaded the webpage you'd see that the indicator is no longer there on the set I am planning to add the ability to set an initial set to load instead of your last graph state after reboot |
I suspect if you reloaded the webpage you'd see that the indicator is no longer there on the set
I’m generally doing this with a restart of my computer as well and a fresh tab but yeah maybe it’s caching somewhere. I’ll test this next time
I am planning to add the ability to set an initial set to load instead of your last graph state after reboot
That would be brilliant because right now I always need a computer as well as my pi to get my graph set into a workable state (as previously discussed because instances don’t have unique presets loaded on start it means it always loads with most of my instance values totally screwed up).
…
On Dec 4, 2024 at 10:40 PM, <Alex Norman ***@***.***)> wrote:
ahh okay, i suspect that is stale information that the web UI retained, we probably need to clean that up. I suspect if you reloaded the webpage you'd see that the indicator is no longer there on the set
I am planning to add the ability to set an initial set to load instead of your last graph state after reboot
—
Reply to this email directly, view it on GitHub (#181 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AEHA6NJY5HPGDKN5S7VPQJL2D6AD7AVCNFSM6AAAAABSZR4LAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYG4YDGNRSGI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I’m not sure exactly how to reproduce this but sometimes after I restart my pi the graph set will reload as it was but the initial preset will not be loaded, causing all the instance values to fall back to default. So far I can’t determine any reason why this happens or what action triggers it but it seems to happen maybe 1 in 10 reboots for me. When this happens and you look in the interface the graph set loaded does not have the little icon next to it and as such the preset list is blank (I guess this is why no preset gets loaded).
I’ve tried this with both saving both graph set and preset before shutting down and also without making any changes to my last loaded graph set and it seems to happen on either occasion.
Sorry I’m not sure exactly how to reproduce this!
The text was updated successfully, but these errors were encountered: