Skip to content

Conversation

@IanButterworth
Copy link
Member

Fixes #1283

I guess the db got out of sync with the installed channels, somehow.. This seems a logical check to add.

@davidanthoff
Copy link
Collaborator

I think I would prefer that we just update the error message to be correct ("Something like release is pointing to X, but you have Y").

With this PR we would never be able to switch a channel back to an older version, and when I designed this originally, I wanted to have the ability to for example pull a prematurely released build.

Also, it would be good to actually understand what caused the underlying situation. I can't really wrap my head around what could have cause this, and I think I would prefer that we add diagnostic code that helps us track down what is going on with the DB versions if we encounter this situation. If we merge this PR we essentially will never be able to track down what is causing the problem in the first place..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wrong update message?

2 participants