docker stats --no-stream might hang indefinitely #4585
Comments
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 5, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90%. Fixes vmware#4549, vmware#4585
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 6, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90%. Fixes vmware#4549, vmware#4585
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 6, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90%. Fixes vmware#4549, vmware#4585
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 6, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% Fixes vmware#4549, vmware#4585
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 6, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% Fixes vmware#4549, vmware#4585
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 6, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 8, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 8, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 10, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 10, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 13, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 13, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 13, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
cgtexmex
pushed a commit
to cgtexmex/vic
that referenced
this issue
Apr 14, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
matthewavery
pushed a commit
to matthewavery/vic
that referenced
this issue
May 3, 2017
In some cases a race could be encountered when executing docker stats. The race would result in an orphaned go routine that would be a memory leak. In addition if stats --no-stream -all was requested the persona would hang on any stopped containers. Stats now will consider the container state when processing these requests. Finally, the unit testing coverage was increased to just over 90% and integration tests were created. Fixes vmware#4549, vmware#4585, vmware#4421
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
if a user calls
docker stats --no-streambefore any stats are available for a given VM (i.e. it just started and no stats have been generated) then the call will not return.The only remedy is for a user to cancel the request.
The text was updated successfully, but these errors were encountered: