-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
web view doesn't stream logs properly #71
Comments
apostergiou
added a commit
that referenced
this issue
May 7, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
Merged
apostergiou
added a commit
that referenced
this issue
May 7, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
apostergiou
added a commit
that referenced
this issue
May 7, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
apostergiou
added a commit
that referenced
this issue
May 8, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
apostergiou
added a commit
that referenced
this issue
May 8, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
apostergiou
added a commit
that referenced
this issue
May 8, 2018
The bug was based in a racy condition that could be triggered when a tailer had been terminated for a job ID just after a new job with the same ID has started streaming. To solve this we refactor the concurrency model of the tailers by removing the sync map and depending only on new and closing clients signals sent to the broker. Fixes #71
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: