You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the hooks are run in dartdev/flutter_tools, the assets might be copied/signed/install_name modified etc.
We'd like to ensure that we can cache those steps.
We cannot blindly rely on timestamps, as a hook might return a file with an older timestamp (on Windows downloaded files have their creation date as lastmodified, not the downloaded time). We could fix this by mandating that assets should have monotonically increasing timestamps, but that puts burden on the hook writer.
Maybe there are better solutions (using a hash, ...).
Also flutter run and flutter build --release copy files both to build/native_assets/* which also breaks the NOP-ness.
After the hooks are run in dartdev/flutter_tools, the assets might be copied/signed/
install_name
modified etc.We'd like to ensure that we can cache those steps.
We cannot blindly rely on timestamps, as a hook might return a file with an older timestamp (on Windows downloaded files have their creation date as lastmodified, not the downloaded time). We could fix this by mandating that assets should have monotonically increasing timestamps, but that puts burden on the hook writer.
Maybe there are better solutions (using a hash, ...).
Also
flutter run
andflutter build --release
copy files both tobuild/native_assets/*
which also breaks the NOP-ness.To investigate
Context:
This needs to play well with concurrent invocations as well:
Edit:
Thanks @mkustermann and @blaugold
The text was updated successfully, but these errors were encountered: