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

WIP Refactor filtering moving from CLI to server #2201

Closed
wants to merge 1 commit into from

Conversation

jwhonce
Copy link
Member

@jwhonce jwhonce commented Jan 22, 2019

  • Filter on server side to reduce amount of data pushed over Varlink

Signed-off-by: Jhon Honce jhonce@redhat.com

@jwhonce jwhonce added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2019
@jwhonce jwhonce self-assigned this Jan 22, 2019
@jwhonce
Copy link
Member Author

jwhonce commented Jan 22, 2019

@baude I uploaded the WIP so you can review where I'm going

@@ -436,7 +437,7 @@ func (r *Runtime) LookupContainer(idOrName string) (*Container, error) {
// Filters can be provided which will determine what containers are included in
// the output. Multiple filters are handled by ANDing their output, so only
// containers matching all filters are returned
func (r *Runtime) GetContainers(filters ...ContainerFilter) ([]*Container, error) {
func (r *Runtime) GetContainers(filters ...filterable.Filter) ([]*Container, error) {
Copy link
Member

Choose a reason for hiding this comment

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

I think we can keep the definition for ContainerFilter in libpod - anything that matches the signature will be treated by Go as a ContainerFilter, even if it's defined in another package

Copy link
Member

Choose a reason for hiding this comment

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

Oh, I see you redefined it. Hmmm.

Can we have filterable.Filter produce a ContainerFilter instead? I kind of like arbitrary-function interface we have going on here, and I'd like to keep it if we're retaining filtering.

@rh-atomic-bot
Copy link
Collaborator

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

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 9, 2019
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jwhonce
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mrunalp

If they are not already assigned, you can assign the PR to them by writing /assign @mrunalp in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 18, 2019
* Filter on server side to reduce amount of data pushed over Varlink

Signed-off-by: Jhon Honce <jhonce@redhat.com>
@openshift-ci-robot
Copy link
Collaborator

@jwhonce: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/images a1bc0b5 link /test images
ci/prow/validate a1bc0b5 link /test validate
ci/prow/lint a1bc0b5 link /test lint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 24, 2019
@openshift-ci-robot
Copy link
Collaborator

@jwhonce: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@rhatdan
Copy link
Member

rhatdan commented Mar 8, 2019

@jwhonce Are you still working on this?

@rhatdan
Copy link
Member

rhatdan commented Mar 21, 2019

@jwhonce What is the skoop on this one?
@baude Do you know what is going on?

@jwhonce
Copy link
Member Author

jwhonce commented Apr 11, 2019

We went a different direction.

@jwhonce jwhonce closed this Apr 11, 2019
@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 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants