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.

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

Closed
agis opened this issue May 2, 2018 · 0 comments
Closed

web view doesn't stream logs properly #71

agis opened this issue May 2, 2018 · 0 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@agis
Copy link
Contributor

agis commented May 2, 2018

No description provided.

@agis agis added the bug Something isn't working label May 2, 2018
@agis agis added this to the 1.0 milestone May 2, 2018
@apostergiou apostergiou self-assigned this May 7, 2018
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 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
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants