-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Problem in flutter debugg #42378
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
Comments
/cc @jensjoha |
Thank you for taking the time to report this issue! Three things happens here:
All of these are caused by not getting the sdk. Why there is no sdk I don't know --- possibly it was accidentally deleted? Or maybe there was an unzipping error or something..? (I don't know whether the flutter tools catch stuff like that) (or is it located on some cloud drive that hasn't synced yet? ( /cc @jonahwilliams who might know of other situations where the sdk has disappeared..? |
…hen not having a platform This CL would have reduced the number of errors given in #42378 Namely the "Warning: Tried to initialize from a previous compilation (build/cache.dill), but couldn't." part wouldn't have been issued. Change-Id: I3e7f2f0115a13a23522643b6f4c9ad8c57bc0d5e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/153141 Reviewed-by: Johnni Winther <[email protected]> Commit-Queue: Jens Johansen <[email protected]>
Yeah, this seems like a case where bin/cache is corrupted that we need to recover from (fyi @christopherfujino who is looking at making this more robust) |
Yes, this issue should be moved to github.com/flutter/flutter. Does a dart-lang/sdk have to do that @jensjoha? I don't see anything in the UI to move the issue. |
Hmmm --- I don't seem to be able to move it to flutter either... (Maybe I just don't know how). |
You can't move issues between organizations AFAIK. So somebody just needs to move it by hand. |
Error....
The text was updated successfully, but these errors were encountered: