You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I never approved the idea of the visor writing to its own config, and worked to minimize this as much as possible.
This is only the immediately visible portion of a much larger issue.
Any changes made in the hypervisor UI for such things as app autostart or persistent transports are not currently persisted across update cycles or even running default config gen, or the scripted generation of that command used by skywire-autoconfig.
Efforts were made to set some things separately in an env file, however, this may require a different implementation
the reward setting uses its own file and is persisted.
The text was updated successfully, but these errors were encountered:
̶M̶y̶ ̶g̶u̶e̶s̶s̶ ̶i̶s̶ ̶t̶h̶a̶t̶ ̶t̶h̶e̶ ̶c̶o̶n̶f̶i̶g̶ ̶i̶s̶ ̶l̶e̶f̶t̶ ̶i̶n̶ ̶a̶ ̶m̶o̶d̶i̶f̶i̶e̶d̶ ̶s̶t̶a̶t̶e̶ ̶i̶n̶ ̶c̶e̶r̶t̶a̶i̶n̶ ̶i̶n̶s̶t̶a̶n̶c̶e̶s̶,̶ ̶s̶o̶ ̶t̶h̶a̶t̶ ̶t̶h̶e̶ ̶v̶i̶s̶o̶r̶ ̶c̶a̶n̶'̶t̶ ̶s̶t̶a̶r̶t̶ ̶a̶g̶a̶i̶n̶s̶t̶ ̶i̶t̶.̶
̶R̶e̶g̶e̶n̶e̶r̶a̶t̶i̶n̶g̶ ̶t̶h̶e̶ ̶c̶o̶n̶f̶i̶g̶ ̶s̶e̶e̶m̶s̶ ̶t̶o̶ ̶s̶o̶l̶v̶e̶ ̶t̶h̶e̶ ̶i̶s̶s̶u̶e̶.̶
the panic shown was caused by
running in a terminal in the background while attempting to start skywire
...
For reference, the script I was running
I exited the script. I exited the visor. I restarted the visor, redirecting the output to a file, which in itself should not have caused an issue
I never approved the idea of the visor writing to its own config, and worked to minimize this as much as possible.
This is only the immediately visible portion of a much larger issue.
Any changes made in the hypervisor UI for such things as app autostart or persistent transports are not currently persisted across update cycles or even running default config gen, or the scripted generation of that command used by skywire-autoconfig.
Efforts were made to set some things separately in an env file, however, this may require a different implementation
the reward setting uses its own file and is persisted.
The text was updated successfully, but these errors were encountered: