Repository navigation
Add a facility to test whether a snapshot is up-to-date without running it #20802
Description
Activity
I'm increasing the priority of this. Relying on exit code detection causes serious problems for pub executables, especially since the VM emits exit code 255 for both an invalid snapshot number and an unhandled exception, so any unhandled exception in an executable causes the executable to be re-run over and over.
Removed Priority-Unassigned label.
Added Priority-High label.As of r43505 the VM returns exit code 253 if an API error is triggered. This generally happens when loading an invalid snapshot.
Set owner to @iposva-google.
Added Fixed label.Having a different error code helps somewhat, but it doesn't solve the issue. This will still break if the Dart code itself emits exit code 253, and it still requires that we try to run the snapshot to determine whether it's up-to-date, which means we show users a confusing error message (20784).
Added Triaged label.
6 remaining items
- removed this from the milestone
on Mar 20, 2018 This feature request has been slowly shifting from milestone to milestone with nothing happening to it. Closing it as stale for now.
This is still something I would very much like for pub!
Okay - removing Stale marker and priority. Lets see if we can slate this to be implemented.
That would be great 😄
Is this issue talking about a script snapshot or an application snapshot ?
Both.
This might solve an issue in Flutter too (for Linux/Mac at least, haven't investigated Windows): flutter/flutter#19208
The fix for issue #15982 is great, but now we also need the ability to check whether a snapshot is up-to-date without actually having to run it. Just something like "dart --is-snapshot-up-to-date <snapshot-path>" that returned a 0 or 1 exit code would be fine.