Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Possible concurrent adjustments to GapAwareTrackingToken.gaps #646

Closed
smcvb opened this issue Jul 5, 2018 · 0 comments
Closed

Possible concurrent adjustments to GapAwareTrackingToken.gaps #646

smcvb opened this issue Jul 5, 2018 · 0 comments
Assignees
@abuijze @smcvb
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
Milestone
Release 3.3.1

Comments

@smcvb
Copy link
Member

smcvb commented Jul 5, 2018

We have encountered two scenarios where we think the gaps in a GapAwareTrackingToken might be adjusted concurrently. One such place is during the GapAwareTrackingToken#advanceTo() function where in some scenario we end up with a NoSuchElementException. Another recent scenario is the one giving in this user group thread, where the GapAwareTrackingToken#covers(TrackingToken) ends up with a IllegalArgumentException if a replay is performed whilst new events are added.
@smcvb smcvb added the Type: Bug Use to signal issues that describe a bug within the system. label Jul 5, 2018
@smcvb smcvb added this to the Release 3.3.1 milestone Jul 5, 2018
@abuijze abuijze closed this as completed in 8fa8b68 Jul 5, 2018
@smcvb smcvb added Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. labels Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abuijze abuijze

@smcvb smcvb

Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
Projects
None yet
Milestone
Release 3.3.1
Development

No branches or pull requests
2 participants
@abuijze @smcvb