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
Hi! My team has struggled with some false positives for ModelDiff saying there are changes, even when the input files haven't changed between two versions of the model.
We've narrowed it down to a difference in metadata merged from multiple files. It seems like, depending on the location on disk of the files being parsed (even if they're in the same relative directories, they may have a different base directory - e.g. in CI runs this may differ from run to run).
I'm wondering if it's something that should be expected.
I suppose users shouldn't rely on metadata having any specific order - is that true?
If that's the case, should ModelDiff be adjusted to ignore changes in ordering of metadata on the top level, or should I adjust that on my side? Thanks!
The text was updated successfully, but these errors were encountered:
Hi! My team has struggled with some false positives for
ModelDiff
saying there are changes, even when the input files haven't changed between two versions of the model.We've narrowed it down to a difference in metadata merged from multiple files. It seems like, depending on the location on disk of the files being parsed (even if they're in the same relative directories, they may have a different base directory - e.g. in CI runs this may differ from run to run).
You can see this behavior here (runnable online on Scastie):
I'm wondering if it's something that should be expected.
I suppose users shouldn't rely on metadata having any specific order - is that true?
If that's the case, should
ModelDiff
be adjusted to ignore changes in ordering of metadata on the top level, or should I adjust that on my side? Thanks!The text was updated successfully, but these errors were encountered: