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

feat: delete GetValues #728

Merged
merged 1 commit into from
Jul 22, 2021
Merged

feat: delete GetValues #728

merged 1 commit into from
Jul 22, 2021

Conversation

Stebalien
Copy link
Member

This was a somewhat strange interface that returned one value from each peer. It has been replaced by SearchValue that returns better and better values as we get them.

In the future, we should be able to introduce a new GetValues that returns a "bag" of values (possibly multiple values from individual peers).

fixes #416

While breaking, there are currently no users of this method. This used to be used in namesys, but that now uses SearchValue.

This was a somewhat strange interface that returned one value from each
_peer_. It has been replaced by `SearchValue` that returns better and
better values as we get them.

In the future, we should be able to introduce a _new_ `GetValues` that
returns a "bag" of values (possibly multiple values from individual
peers).

fixes #416
@aschmahmann
Copy link
Contributor

While breaking, there are currently no users of this method. This used to be used in namesys, but that now uses SearchValue.

If actually nobody is using this let's kill it, it doesn't seem super useful.

In the future, we should be able to introduce a new GetValues that returns a "bag" of values (possibly multiple values from individual peers).

The current setup only really allows returning a single value from a peer for a given key (e.g. IPNS records). If we landed something like #584 then having multiple values per peer would be a possibility.

@aschmahmann
Copy link
Contributor

Side note: CI seems to be flipping out here, any idea what's up?

@Stebalien
Copy link
Member Author

The current setup only really allows returning a single value from a peer for a given key (e.g. IPNS records). If we landed something like #584 then having multiple values per peer would be a possibility.

Yeah, this just clears the way a bit.

Side note: CI seems to be flipping out here, any idea what's up?

Flakes. There are a lot of flakes.

@Stebalien
Copy link
Member Author

@aschmahmann can I merge?

Copy link
Contributor

@aschmahmann aschmahmann left a comment

Choose a reason for hiding this comment

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

Sure, let's kill it. We should make sure to note it in the release notes though

@Stebalien Stebalien merged commit 65773b1 into master Jul 22, 2021
@Stebalien Stebalien deleted the fix/416 branch July 22, 2021 18:29
@aschmahmann aschmahmann mentioned this pull request Aug 23, 2021
62 tasks
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.

GetValues and friends should not use RecvdVal
2 participants