Skip to content

Conversation

@rhatdan
Copy link
Member

@rhatdan rhatdan commented Nov 21, 2017

No description provided.

@TomSweeneyRedHat
Copy link
Member

@rhatdan looks like ci is failing with a missing dependency on containerd?

Copy link
Member

Choose a reason for hiding this comment

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

would it make sense to declare a string, append it to warnings then send it to logrus.Warn to avoid the duplications?

Copy link
Member Author

Choose a reason for hiding this comment

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

Makes sense.

Copy link
Member

Choose a reason for hiding this comment

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

If you have multiple warnings packed into 'warnings' will it be readable? Can we stuff a \n at the end of each?

Copy link
Member Author

Choose a reason for hiding this comment

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

warnings is a list of strings, I believe. The caller would be responsible for how he wants to display the warnings.

Copy link
Member Author

Choose a reason for hiding this comment

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

Added an addWarnings function

cmd/kpod/spec.go Outdated
Copy link
Member

Choose a reason for hiding this comment

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

would "<0" be better here? I think it's pretty controlled now, but might be a good hedge long-term.

Copy link
Member Author

Choose a reason for hiding this comment

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

-1 seems to be the special value (Default which indicates whether to use the Swappiness or not. (At least in Docker.)

cmd/kpod/spec.go Outdated
Copy link
Member

Choose a reason for hiding this comment

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

This looks like it's from #54 except it seems to be missing the latest changes from there

Copy link
Member Author

Choose a reason for hiding this comment

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

That's why this is a WIP, waiting for it to get merged, then I can rebase and remove WIP

@rh-atomic-bot
Copy link
Collaborator

☔ The latest upstream changes (presumably 91b406e) made this pull request unmergeable. Please resolve the merge conflicts.

@rhatdan rhatdan changed the title [WIP] Add verification code to verify user input on resources. Add verification code to verify user input on resources. Nov 22, 2017
Update version of docker to pull in lates code
Remove kubernetes since libpod is not tied to it.
Remove a few other packages that we don't seem to use.
Left in the networking stuff, since we will hopefully be wiring that together.

Signed-off-by: Daniel J Walsh <[email protected]>
@TomSweeneyRedHat
Copy link
Member

Changes LGTM, tests are not at all happy.

Added lots of verification code to make sure resourses asociated with
containers is correct.

Signed-off-by: Daniel J Walsh <[email protected]>
@rhatdan
Copy link
Member Author

rhatdan commented Nov 22, 2017

@TomSweeneyRedHat Tests are passing now.
@mheon @baude @umohnani8 PTAL

@umohnani8
Copy link
Member

LGTM

@rhatdan
Copy link
Member Author

rhatdan commented Nov 22, 2017

@rh-atomic-bot r=umohnani8

@rh-atomic-bot
Copy link
Collaborator

📌 Commit 616667b has been approved by umohnani8

@rh-atomic-bot
Copy link
Collaborator

⌛ Testing commit 616667b with merge 195d48d...

rh-atomic-bot pushed a commit that referenced this pull request Nov 22, 2017
Added lots of verification code to make sure resourses asociated with
containers is correct.

Signed-off-by: Daniel J Walsh <[email protected]>

Closes: #60
Approved by: umohnani8
@rh-atomic-bot
Copy link
Collaborator

☀️ Test successful - status-papr
Approved by: umohnani8
Pushing 195d48d to master...

wking added a commit to wking/libpod that referenced this pull request May 11, 2018
This directory just had Markdown and vendor.conf.  I'm not sure why we
have it in our version control, maybe old versions of vndr kept it?
Or maybe folk dropped it into vendor/ by hand without using vndr?  The
history of that vendored directory is:

* 619637a (Handle Linux Capabilities from command line, 2017-11-03,
  containers#17) added the three files to our version control.
* c344fe6 (Update vendoring, 2017-11-22, containers#60) bumped hack/README.md.
* af64e10 (Vendor in lots of kubernetes stuff to shrink image size,
  2018-03-26, containers#554) bumped hack/README.md.
* 27107fd (Vendor in latest containers/image and contaners/storage,
  2018-04-18, containers#509) removed the files.
* a824186 (Use buildah commit and bud in podman, 2018-04-25, containers#681)
  added the files back.
* I'm removing them again in this commit.

With this commit,

  $ vndr github.com/docker/docker

becomes a no-op.

Signed-off-by: W. Trevor King <[email protected]>
rh-atomic-bot pushed a commit that referenced this pull request May 11, 2018
This directory just had Markdown and vendor.conf.  I'm not sure why we
have it in our version control, maybe old versions of vndr kept it?
Or maybe folk dropped it into vendor/ by hand without using vndr?  The
history of that vendored directory is:

* 619637a (Handle Linux Capabilities from command line, 2017-11-03,
  #17) added the three files to our version control.
* c344fe6 (Update vendoring, 2017-11-22, #60) bumped hack/README.md.
* af64e10 (Vendor in lots of kubernetes stuff to shrink image size,
  2018-03-26, #554) bumped hack/README.md.
* 27107fd (Vendor in latest containers/image and contaners/storage,
  2018-04-18, #509) removed the files.
* a824186 (Use buildah commit and bud in podman, 2018-04-25, #681)
  added the files back.
* I'm removing them again in this commit.

With this commit,

  $ vndr github.com/docker/docker

becomes a no-op.

Signed-off-by: W. Trevor King <[email protected]>

Closes: #752
Approved by: baude
@rhatdan rhatdan deleted the verify branch December 1, 2022 22:02
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants