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
@apdavison proposed that:
model version does not have to be unique, but rather the combination of version and parameters should be considered unique.
You can have two model instances with the same code version but different parameters.
I had always worked with the presumption that version for instances was similar to alias for models/tests (a human readable unique identifier, as opposed to the UUID). All my implementations were with this understanding, and I believe even the unit tests were written to test only this aspect. So parts of the codebase could be faulty for this scenario.
The code for the web apps and unit tests would need to be reviewed and updated, where required, to handle this.
To be decided: if the same rule should apply for test instances
The text was updated successfully, but these errors were encountered:
@apdavison proposed that:
model
version
does not have to be unique, but rather the combination ofversion
andparameters
should be considered unique.I had always worked with the presumption that version for instances was similar to alias for models/tests (a human readable unique identifier, as opposed to the UUID). All my implementations were with this understanding, and I believe even the unit tests were written to test only this aspect. So parts of the codebase could be faulty for this scenario.
The code for the web apps and unit tests would need to be reviewed and updated, where required, to handle this.
To be decided: if the same rule should apply for test instances
The text was updated successfully, but these errors were encountered: