Skip to content

Refactor to new engine-api events api #25853

Merged
vdemeester merged 1 commit intomoby:masterfrom
jhorwit2:jah/event-refactor
Sep 24, 2016
Merged

Refactor to new engine-api events api #25853
vdemeester merged 1 commit intomoby:masterfrom
jhorwit2:jah/event-refactor

Conversation

@jhorwit2
Copy link
Contributor

@jhorwit2 jhorwit2 commented Aug 18, 2016

ref docker-archive-public/docker.engine-api#315

- What I did

refactored to the new engine-api proposed events api.

- How I did it

Found all occurrences of the old Events call and replaced it with the new one.

- How to verify it

Run unit tests and integration tests.

- Description for the changelog

Refactored events api to updated engine-api interface

Signed-off-by: Josh Horwitz horwitzja@gmail.com

cc @vdemeester

@vdemeester
Copy link
Member

LGTM 🐸
/cc @stevvooe @cpuguy83 @LK4D4 @runcom

@vdemeester
Copy link
Member

ping 👼

Choose a reason for hiding this comment

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

"Error waiting for..."?

Also, error string should generally start with a lowercase character.

Copy link
Contributor

Choose a reason for hiding this comment

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

Could probably just use errors.Wrap here, as well.

@stevvooe
Copy link
Contributor

Design LGTM

@runcom
Copy link
Member

runcom commented Sep 14, 2016

we are we on this? tests are failing though.

@jhorwit2
Copy link
Contributor Author

I'll take a look at the tests.

Copy link
Member

@dnephin dnephin Sep 14, 2016

Choose a reason for hiding this comment

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

I believe this should use the existing ctx, and not create a new one. Unless there is some special reason this needs its own context? If that's the case I think that warrants a comment about it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

👍 i noticed that also while fixing the test. I think this was due to a recent rebase where the context was added. Don't remember one when i first wrote this. 👼

@vdemeester
Copy link
Member

ping @jhorwit2 👼

@stevvooe
Copy link
Contributor

@vdemeester @jhorwit2 Let's try to get this merged. This is a net positive change.

@jhorwit2
Copy link
Contributor Author

@stevvooe @vdemeester sorry for delay. I fixed one of the issues (was with waitExitOrRemoved). I should have time tomorrow to figure out the other tests failing.

@jhorwit2 jhorwit2 force-pushed the jah/event-refactor branch 6 times, most recently from 962465b to 969657c Compare September 22, 2016 18:39
Signed-off-by: Josh Horwitz <horwitzja@gmail.com>
@jhorwit2
Copy link
Contributor Author

@vdemeester should be all good now! 👼

@vdemeester
Copy link
Member

LGTM 🐸
/cc @stevvooe @runcom

@stevvooe
Copy link
Contributor

LGTM

@vdemeester vdemeester merged commit 8c929ee into moby:master Sep 24, 2016
@thaJeztah thaJeztah added this to the 1.13.0 milestone Sep 25, 2016
dnephin pushed a commit to dnephin/docker that referenced this pull request Apr 17, 2017
Refactor to new engine-api events api
dnephin pushed a commit to dnephin/docker that referenced this pull request Apr 17, 2017
Refactor to new engine-api events api
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants