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

Investigate potential goroutine leak #286

Closed
goenning opened this issue Feb 28, 2018 · 1 comment
Closed

Investigate potential goroutine leak #286

goenning opened this issue Feb 28, 2018 · 1 comment
Labels
type: bug something is broken, we need to fix it
Milestone
v0.11: March/2018

Comments

@goenning
Copy link
Member

No description provided.

@goenning goenning added type: bug something is broken, we need to fix it help wanted labels Feb 28, 2018
@goenning goenning added this to the v0.11.0: March/2018 milestone Feb 28, 2018
This was referenced Feb 28, 2018
Merged
Merged
Merged
@goenning
Copy link
Member Author

goenning commented Mar 2, 2018

The latest PR fixed this issue.

@goenning goenning closed this as completed Mar 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: bug something is broken, we need to fix it
Projects
None yet
Milestone
v0.11: March/2018
Development

No branches or pull requests
1 participant
@goenning