-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Comparing changes
Open a pull request
base repository: containerd/containerd
base: v1.2.0
head repository: containerd/containerd
compare: 8afcade1a6041b8301b6f6d8b88bae909993b989
- 13 commits
- 13 files changed
- 5 contributors
Commits on Oct 25, 2018
-
optimize shim lock in runtime v1
apply lock only around process map of shim service, avoid lock affect other procs operations. Signed-off-by: Ace-Tang <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c206da7 - Browse repository at this point
Copy the full SHA c206da7View commit details -
Signed-off-by: Sebastiaan van Stijn <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 07237e3 - Browse repository at this point
Copy the full SHA 07237e3View commit details
Commits on Oct 26, 2018
-
Change unsupported snapshot warnings to INFO
Since there is no real action the user can do, these can safely be informative that the underlying filesystem does not support a snapshot plugin at boot. Signed-off-by: Michael Crosby <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 16aaf6c - Browse repository at this point
Copy the full SHA 16aaf6cView commit details -
Update ZFS for unsupported warnings
Signed-off-by: Michael Crosby <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1301813 - Browse repository at this point
Copy the full SHA 1301813View commit details -
Merge pull request #2435 from thaJeztah/bump_go_1.11
Bump to Go 1.11.0
Configuration menu - View commit details
-
Copy full SHA for 86b8c48 - Browse repository at this point
Copy the full SHA 86b8c48View commit details -
Merge pull request #2745 from crosbymichael/snapshot-warnings
Change unsupported snapshot warnings to INFO
Configuration menu - View commit details
-
Copy full SHA for 7f8b405 - Browse repository at this point
Copy the full SHA 7f8b405View commit details -
Bump aufs for unsupported errors
Signed-off-by: Michael Crosby <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 1cc9346 - Browse repository at this point
Copy the full SHA 1cc9346View commit details
Commits on Oct 28, 2018
-
bugfix: CloseIO should return correct status code
Signed-off-by: Wei Fu <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 00ba923 - Browse repository at this point
Copy the full SHA 00ba923View commit details
Commits on Oct 29, 2018
-
Merge pull request #2746 from crosbymichael/aufs-bump
Bump aufs for unsupported errors
Configuration menu - View commit details
-
Copy full SHA for 05f8c3a - Browse repository at this point
Copy the full SHA 05f8c3aView commit details -
Merge pull request #2743 from Ace-Tang/shim_lock
bugfix: optimize shim lock in runtime v1 avoid dead lock
Configuration menu - View commit details
-
Copy full SHA for 6f8edc2 - Browse repository at this point
Copy the full SHA 6f8edc2View commit details -
Merge pull request #2747 from fuweid/bugfix_wrap_error_in_closeIO
bugfix: CloseIO should return correct status code
Configuration menu - View commit details
-
Copy full SHA for 35a32a8 - Browse repository at this point
Copy the full SHA 35a32a8View commit details -
Increase reaper buffer size and non-blocking send
Fixes #2709 This increases the buffer size for process exit subscribers. It also implements a non-blocking send on the subscriber channel. It is better to drop an exit even than it is to block a shim for one slow subscriber. Signed-off-by: Michael Crosby <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 232a063 - Browse repository at this point
Copy the full SHA 232a063View commit details -
Merge pull request #2748 from crosbymichael/reaper-buffer
Increase reaper buffer size and non-blocking send
Configuration menu - View commit details
-
Copy full SHA for 8afcade - Browse repository at this point
Copy the full SHA 8afcadeView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.2.0...8afcade1a6041b8301b6f6d8b88bae909993b989