TOS 7.0.0427 Beta (X86) is Released for Update

[bartmans99]

Could someone give a bit more info on 'developer mode'. What does it do exactly? And is it reversable, ie. can I switch it off again?

[bartmans99]

The issue with 'Backup system configuration' hasn't been fixed. The filesize is still very small and the location of the file remains in the root (/).

Especially when using beta versions, it would be usefull to have a working backup of the system config.

[Gremlin]

I have just checked System config backup on this version and it saves it to pc downloads folder as I would expect.
Turn off developer mode and see if it works correctly

[bartmans99]

I have just checked System config backup on this version and it saves it to pc downloads folder as I would expect.
Turn off developer mode and see if it works correctly

Developer mode is off.

It does save the .bin file to desktop. But also leaves it in the / root. And the file is 272kb in filesize, which seems small.

[Gremlin]

I don't have an issue with size
237,658

[Joesh]

In the initial post of this release, there is this: " Fixed other known issues" (it would be better if the other known issues just had a link so someone can go look in more details)

If I don't see a specific issue that has been called out as being fixed, should I just re-test any issues I have found and submitted?
For Example:
Recurring rsync jobs, don't generate status/email messages (yes it is turned in notifications) or display any info on the completed task, start/stop times and data transmitted.

Maybe the list is too long to mention one by one, so we as users must actively report problems that are still being experienced.
Beta programs do require active users to report problems they experience before the final version is launched.

[rfbjr]

All I'm saying is if I reported an issue and it was confirmed as a bug and "will be addressed in a future release". I have to re-test it either way anyway. If listed as resolved, I'll test it to see if I get the same results. If it is not listed or could be in other known, I have to test it to see if the issue is still there.
Of course, I report problems if I run across them, that was this post as about, following up on reported problems when they aren't specifically mentioned as resolved in the new beta announcement.

[danx]

早速アップデートをしました再起動したりするとDocker Engineが落ちてダウンしてしまいます
そうなると手動でDocker Engineを立ち上げないといけません
Docker Engine有効にしよと、Docker Engineを立ち上げようと思いますが思うように
Docker Engineが立ち上がらず再度Docker Engineが落ちてしまうというループ現象を確認しました
これはDocker Engineが立ち上がらないという致命的な不具合かと思われます


I immediately updated it. If you restart, the Docker Engine will go down.

If that happens, you have to launch the Docker Engine manually.

I'm going to launch Docker Engine to enable Docker Engine, but as I think

I confirmed the loop phenomenon that the Docker Engine did not stand up and the Docker Engine fell again.

This seems to be a fatal problem that the Docker Engine does not stand up.

[OttO1916]

My F2-221 en F5-221 were updated without any problems.
Thumbs up!

[TMzethar]

早速アップデートをしました再起動したりするとDocker Engineが落ちてダウンしてしまいます
そうなると手動でDocker Engineを立ち上げないといけません
Docker Engine有効にしよと、Docker Engineを立ち上げようと思いますが思うように
Docker Engineが立ち上がらず再度Docker Engineが落ちてしまうというループ現象を確認しました
これはDocker Engineが立ち上がらないという致命的な不具合かと思われます
I immediately updated it. If you restart, the Docker Engine will go down.
If that happens, you have to launch the Docker Engine manually.
I'm going to launch Docker Engine to enable Docker Engine, but as I think
I confirmed the loop phenomenon that the Docker Engine did not stand up and the Docker Engine fell again.
This seems to be a fatal problem that the Docker Engine does not stand up.

We are aware of the phenomenon you mentioned. In fact, Docker Engine starts later in the boot sequence and does not complete its startup immediately. As a result, Docker Engine typically finishes starting up shortly after you successfully access the TOS web page. =
We recommend waiting a moment and then checking the status of Docker Engine.