-
Notifications
You must be signed in to change notification settings - Fork 202
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The previous `hashCode` of `Project` was using the hash of the serialized file. At the time of doing that, I did not realize the use case that this commit fixes would be affected. We're now using a unique ID composed of the name and the configuration path a file comes from. Whenever that is different, it must be a different project. We use `ByteHasher` instead of `hashCode` to avoid hash code collisions. The probability of a hash code collision is very slow, especially because the server should only have around 100 or 200 projects maximum, but it's better be safe than sorry. Fixes #733
- Loading branch information
Showing
4 changed files
with
26 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters