-
Notifications
You must be signed in to change notification settings - Fork 310
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
Config breaks on upstream updates. #519
Labels
Comments
thanks @eendebakpt and @nataliejpg and @MerlinSmiles for spotting my horrible 🐛 |
giulioungaretti
added a commit
that referenced
this issue
Mar 10, 2017
giulioungaretti
added a commit
that referenced
this issue
Mar 13, 2017
giulioungaretti
added a commit
that referenced
this issue
Mar 16, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a user had a custom config and we update upstream by adding a new field.
Their config value will remove the new field added upstream, thus breaking the import of qcodes!
The other way around is impossible to prevent though. If we remove a field upstream there's no way to delete it locally ,or even to raise a warning , but that's cool because maybe local uncommitted doe depends on it :D At worst it's a bit of extra noise!
The text was updated successfully, but these errors were encountered: