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 was archived by the owner on Sep 9, 2020. It is now read-only.
Analyzer info is currently incorporated in gps' input hashing logic, but that information isn't exposed anywhere. Consequently, if two people were to work on the same project with different versions of dep's analyzer, they would constantly get lock memo mismatches, but with no idea why the mismatch is occurring.
To provide better guidance to users when such a situation arises, we should explicitly store the analyzer name and version used in the lock file.
For the same class of reason, we should also store the solver version (once sdboyer/gps#173 is done and it's available).
The text was updated successfully, but these errors were encountered:
Analyzer info is currently incorporated in gps' input hashing logic, but that information isn't exposed anywhere. Consequently, if two people were to work on the same project with different versions of dep's analyzer, they would constantly get lock memo mismatches, but with no idea why the mismatch is occurring.
To provide better guidance to users when such a situation arises, we should explicitly store the analyzer name and version used in the lock file.
For the same class of reason, we should also store the solver version (once sdboyer/gps#173 is done and it's available).
The text was updated successfully, but these errors were encountered: