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
{{ message }}
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
The *.gz files contain a timestamp in the gzip header (mtime). (See next comment for correction)
This is a problem because the apis.gz and relations.gz outputs are used as inputs to downstream actions.
Are those files necessary as inputs? Removing them doesn't seem to break anything, but I'm not sure what Zinc uses them for.
If they are needed, we'll need to find a reproducible way to create them.
The text was updated successfully, but these errors were encountered:
After further investigation it is not the timestamp like I thought. Instead it's that the APIs message has unordered elements, which are sometimes serialized in a different order.
I think they make incremental compilation work more effectively if it is enabled.
You could ask on the Zinc Gitter. I am not certain they are necessary.
They are used for sbt test discovery in scala_test, and they are necessary for that.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The(See next comment for correction)*.gz
files contain a timestamp in the gzip header (mtime).This is a problem because the
apis.gz
andrelations.gz
outputs are used as inputs to downstream actions.Are those files necessary as inputs? Removing them doesn't seem to break anything, but I'm not sure what Zinc uses them for.
If they are needed, we'll need to find a reproducible way to create them.
The text was updated successfully, but these errors were encountered: