If an annotation is to close to another annotation, the epoch calculation will fail because both annotations fall on the same index. Should add options to keep existing error (strict), shift the second annotation if there is a difference in milliseconds but not index to the next available index, up to a reasonable shift (0.1s?). If the annotations fall perfectly on the same millisecond, shift one at random. Last option could be to just delete the second event, or one at random if there is a tie.
If an annotation is to close to another annotation, the epoch calculation will fail because both annotations fall on the same index. Should add options to keep existing error (strict), shift the second annotation if there is a difference in milliseconds but not index to the next available index, up to a reasonable shift (0.1s?). If the annotations fall perfectly on the same millisecond, shift one at random. Last option could be to just delete the second event, or one at random if there is a tie.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If an annotation is to close to another annotation, the epoch calculation will fail because both annotations fall on the same index. Should add options to keep existing error (strict), shift the second annotation if there is a difference in milliseconds but not index to the next available index, up to a reasonable shift (0.1s?). If the annotations fall perfectly on the same millisecond, shift one at random. Last option could be to just delete the second event, or one at random if there is a tie.
Partially added in 1.3.0. Did not implement deletion of events as was deemed not necessary for now.