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

3rd-party: Upgrade versions #471

Merged
merged 1 commit into from
Nov 8, 2018

Conversation

albaguirre
Copy link
Contributor

grpc - Upgrade to v.1.6.0
fmt - Upgrade to latest master
libssh - Upgrade to latest commit from master (Includes sec updates)
yaml-cpp - Upgrade to latest commit from master

grpc - Upgrade to v.1.6.0
fmt - Upgrade to latest master
libssh - Upgrade to latest commit from master (Includes sec updates)
yaml-cpp - Upgrade to latest commit from master
@codecov
Copy link

codecov bot commented Nov 2, 2018

Codecov Report

Merging #471 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #471   +/-   ##
=======================================
  Coverage   66.06%   66.06%           
=======================================
  Files         142      142           
  Lines        5587     5587           
=======================================
  Hits         3691     3691           
  Misses       1896     1896

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c89d67...b24cac1. Read the comment docs.

Copy link
Contributor

@townsend2010 townsend2010 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, all good now:)

bors r+

bors bot added a commit that referenced this pull request Nov 8, 2018
471: 3rd-party: Upgrade versions r=townsend2010 a=albaguirre

grpc - Upgrade to v.1.6.0
fmt - Upgrade to latest master
libssh - Upgrade to latest commit from master (Includes sec updates)
yaml-cpp - Upgrade to latest commit from master

Co-authored-by: Alberto Aguirre <[email protected]>
@bors
Copy link
Contributor

bors bot commented Nov 8, 2018

Build succeeded

@bors bors bot merged commit b24cac1 into canonical:master Nov 8, 2018
@Saviq Saviq mentioned this pull request Dec 20, 2018
bors bot added a commit that referenced this pull request Dec 20, 2018
551: Release 2018.12.1 r=townsend2010 a=Saviq

### Highlights

- On Linux, suspending/resuming the instance to/from disk is now supported. (#374)
- Better handling of delayed shutdown including posting `wall` messages to logged in users and allowing log ins to the instance unless 1 minute or less remains until shutdown. (#461, #50) 
- On Linux, all CPU flags should be passed into the running instance on newly created instances. (#516)
- Fixed some races around mount handling. (#514, #520)

### Bugs fixed:

- make the recover command idempotent (#528)
- explicitly stop mounts when deleting an instance to avoid a race (#520)
- be smarter about what group owns the multipass socket (#513, #523) 
- pass through all CPU flags when launching QEMU or libvirt instances (#516)
- use `info` log level for metrics issues (#515)
- fix potential race when starting a mount (#514)
- use `wall` shutdown messages for users logged into VM when delayed shutdown is initiated (#501)
- fix crash if exception during daemon start up (#487)
- refactor CLI code (#468)
- add default uid/gid mapping (#331)
- fix file metadata passthrough
- display uid/gid maps in info command (#439)
- add support for the suspend command (#374)
- shell to machine in delayed stop state (#461)
- improve uid/gid validation (#479)
- avoid leaking the libvirt bridge (#327, #413)
- add a restart command (#217)
- upgrade 3rd-party versions (#471)

Co-authored-by: bors[bot] <bors[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants