-
Notifications
You must be signed in to change notification settings - Fork 904
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
Attempting to upgrade multiple packages at once causes an error to be thrown about configuration backups #2884
Comments
Further context, seems to be hitting this code path somehow.
|
Further information, this seems to be repeatable if I run |
Thanks for figuring that out. Running |
Also confirmed this issue:
|
In some cases, code paths may attempt to take or restore multiple config backups. Previously, this would always result in an error. With this change, as long as the code paths correctly use start_backup and reset_config, nested levels of backups will work correctly instead of unpredictably interfering with each other.
In some cases, code paths may attempt to take or restore multiple config backups. Previously, this would always result in an error. With this change, as long as the code paths correctly use start_backup and reset_config, nested levels of backups will work correctly instead of unpredictably interfering with each other.
In some cases, code paths may attempt to take or restore multiple config backups. Previously, this would always result in an error. With this change, as long as the code paths correctly use start_backup and reset_config, nested levels of backups will work correctly instead of unpredictably interfering with each other.
In some cases, code paths may attempt to take or restore multiple config backups. Previously, this would always result in an error. With this change, as long as the code paths correctly use start_backup and reset_config, nested levels of backups will work correctly instead of unpredictably interfering with each other.
In some cases, code paths may attempt to take or restore multiple config backups. Previously, this would always result in an error. With this change, as long as the code paths correctly use start_backup and reset_config, nested levels of backups will work correctly instead of unpredictably interfering with each other.
(#2884) Store configuration backups as a Stack
In v1.2.0 choco would fall to pieces on being asked to upgrade multiple packages in a a single command, or when upgrading a package that also needed to upgrade a dependency. The second package installation would fail. This regression test ensures that we can safely `upgrade` multiple packages at once.
Having this issue as well |
In v1.2.0 choco would fall to pieces on being asked to upgrade multiple packages in a a single command, or when upgrading a package that also needed to upgrade a dependency. The second package installation would fail. This regression test ensures that we can safely `upgrade` multiple packages at once.
🎉 This issue has been resolved in version 1.2.1 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
What You Are Seeing?
When attempting to call
choco upgrade -y sql-server-management-studio
I receive the following error in the logs:What is Expected?
Not that.
How Did You Get This To Happen? (Steps to Reproduce)
As described above.
System Details
[System.Environment]::OSVersion.version.tostring()
): 10.0.17763.0$PSVersionTable
):Name Value
PSVersion 5.1.17763.2931
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.2931
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
choco --version
): 1.2.0Output Log
As described above.
The text was updated successfully, but these errors were encountered: