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

Bump hcsshim to v0.8.5 #4

Merged
merged 2 commits into from
Feb 5, 2019
Merged

Bump hcsshim to v0.8.5 #4

merged 2 commits into from
Feb 5, 2019

Conversation

arjun024
Copy link
Member

@arjun024 arjun024 commented Jan 29, 2019

Tracker-story: https://www.pivotaltracker.com/story/show/162997839

cc: @achasveachas

arjun024 and others added 2 commits January 29, 2019 16:05
Some error messages changed with the bump to hcsshim v0.8.5

Signed-off-by: Yechiel Kalmenson <ykalmenson@pivotal.io>
Uses greenhouse-org/hcsshim, branch upstream-v0.8.5-mod.
This contains all commits from Microsoft/hcsshim v.0.8.5 +
commits made by our team to the fork.

Many transitive dependencies have been updated.

This update includes our PR (microsoft/hcsshim#431)
to the syscall watcher

All the tests pass with no major API changes

Signed-off-by: Arjun Sreedharan <asreedharan@pivotal.io>
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/163575800

The labels on this github issue will be updated when the story is started.

@cfdreddbot
Copy link

✅ Hey arjun024! The commit authors and yourself have already signed the CLA.

@arjun024
Copy link
Member Author

@sesmith177 @natalieparellano -- Thought we'll run it by you and see if you have any comments before merging.

@sesmith177
Copy link
Contributor

I have two small concerns here:

  1. For our fork of hcsshim, it's probably easiest just to create a new commit on top of the v0.8.5 branch instead of a rebase. That way, anyone looking at that branch will be able to tell easily what the diff is
  2. Adding fsnotify to Gopkg.toml seems odd to me -- it's not a dependency of winc or hcsshim that I can tell

@achasveachas
Copy link
Contributor

  1. Guess we can do that. But someone can tell just by comparing the branches -> microsoft/hcsshim@v0.8.5...greenhouse-org:upstream-v0.8.5-mod
  2. That seems to be a known bug. We ran into it in groot-windows as well. This seems to be the only way around it.

@arjun024
Copy link
Member Author

arjun024 commented Jan 30, 2019

On the fork, we have made one commit that takes all the changes in "our" previous commits and pushed it on top of v0.8.5. Now the git history is clean -- our changes are on top of the Microsoft changes. See greenhouse-org/hcsshim@d3cfe7c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants