Skip to content

Upgrading to 1.9.0-dev.8 messing up pub and/or .pub-cache #22499

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

Closed
DartBot opened this issue Feb 19, 2015 · 6 comments
Closed

Upgrading to 1.9.0-dev.8 messing up pub and/or .pub-cache #22499

DartBot opened this issue Feb 19, 2015 · 6 comments

Comments

@DartBot
Copy link

DartBot commented Feb 19, 2015

This issue was originally filed by @yjbanov


What steps will reproduce the problem?

Upgrade to 1.9.0-dev.8

Observed two different outcomes on two different machines that seemingly stem from the same cause:

Outcome #­1:

$ dartformat

["Wrong script snapshot version" pointing at dart_style; sorry don't have a copy of the exact message but it's just a couple hashes]

Workaround: delete .pub-cache, pub global activate dart_style, pub get

Outcome #­2:

$ pub
Wrong script snapshot version, expected '836a274342f7f88d6b5a9bb59b2649a9' found '8a2822fc14c97914b87335dcea37245f'
255 ~

Workaround: delete .pub-cache, reinstall SDK

@kevmoo
Copy link
Member

kevmoo commented Feb 19, 2015

cc @nex3.
cc @munificent.
Added Area-Pub, Pub-Run, Triaged labels.

@DartBot
Copy link
Author

DartBot commented Feb 19, 2015

This comment was originally written by @zoechi


I had this message after each update. activating the package again solved it for me (see also http://stackoverflow.com/questions/28585049/update-all-global-activated-packages) but this seems to be fixed since a few days.

@DartBot
Copy link
Author

DartBot commented Feb 19, 2015

This comment was originally written by @yjbanov


The biggest issue is with the second outcome. If you are unable to run pub at all there is no way for you to activating the package.

@nex3
Copy link
Member

nex3 commented Feb 19, 2015

The first issue is issue #22076; the VM changed its exit code for invalid snapshots and the old binstub scripts are now checking the wrong one. If you run "pub cache repair" it will fix all your activated scripts.

The second issue is nastier. Pub itself should never have an incorrect snapshot version. Can you still reproduce this? What happens if you run "pub --verbose"?

@DartBot
Copy link
Author

DartBot commented Feb 20, 2015

This comment was originally written by @yjbanov


More reluctant to try to reproduce than cannot, mainly because I don't want to break my dev environment, but I'll let you know if it happens again during next upgrade.

@DartBot
Copy link
Author

DartBot commented Jun 5, 2015

This issue has been moved to dart-lang/pub#1251.

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

No branches or pull requests

3 participants