Skip to content
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

Mode check should be added #27

Open
musicpanda opened this issue Nov 10, 2022 · 1 comment
Open

Mode check should be added #27

musicpanda opened this issue Nov 10, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@musicpanda
Copy link

After I had run the filecompare of the Coreupdate I changed my mind on the mode and went in a different window to the Modules section to change it from "stable" to "bleeding edge". Then I went back to Coreupdater page and pressed the "Update" button. The page initially told me that it was updating to the stable version. A bit later it ended with the attached error.
coreupdate
More people will do this so it shouldn't result in an error.

@getdatakick getdatakick added the enhancement New feature or request label Nov 10, 2022
@getdatakick
Copy link
Contributor

This is actually an expected behaviour. The comparison result showed information related to previously selected channel. If the channel was changed, the process should not be allowed to continue.

I agree that more user-friendly error message is needed, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants