Skip to content

Tried to initialize from a previous compilation #36992

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
Andrious opened this issue May 17, 2019 · 4 comments
Closed

Tried to initialize from a previous compilation #36992

Andrious opened this issue May 17, 2019 · 4 comments
Labels
closed-duplicate Closed in favor of an existing report legacy-area-front-end Legacy: Use area-dart-model instead. P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@Andrious
Copy link

Warning: Tried to initialize from a previous compilation (build/app.dill.track.dill), but the file was not self-contained. This might be a bug.
initialize_from.dill.gz

@a-siva a-siva added the needs-info We need additional information from the issue author (auto-closed after 14 days if no response) label May 24, 2019
@a-siva
Copy link
Contributor

a-siva commented May 24, 2019

@Andrious can you provide more details or reproduction instructions for this, the information provided here is not sufficient for us to root cause the issue.

@Andrious
Copy link
Author

At this time, no. If and when it's encountered again, I will make efforts to provide more details.

@no-response no-response bot removed the needs-info We need additional information from the issue author (auto-closed after 14 days if no response) label May 24, 2019
@a-siva
Copy link
Contributor

a-siva commented May 24, 2019

This appears to be a duplicate of #37043

@a-siva a-siva added legacy-area-front-end Legacy: Use area-dart-model instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) P2 A bug or feature request we're likely to work on closed-duplicate Closed in favor of an existing report labels May 24, 2019
@jensjoha
Copy link
Contributor

Thank you for taking the time to report this issue.

This appear to be the same thing as in #36759.
To summarize, everything is fine - the compile that reported this will be slower, but the output will be perfectly fine. It is caused by an updated flutter sdk.

For instance, if you updated from flutter beta to flutter master around the time where you reported this issue (i.e. the file we're trying to initialize from was created on flutter beta, now we're trying to initialize from it on flutter master) - you'll get a warning about not being able to initialize from it (because of a change in the sdk, specifically in flutter/engine@3e47b4b the getter "left" on class "Rect" was removed and became a field instead).
It will ultimately be fixed via #36032 and our initial fix (5eff2a0) would have caught this to (so the error wouldn't have been issued).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report legacy-area-front-end Legacy: Use area-dart-model instead. P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants