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

Remove bootstrapping code #37

Merged
merged 2 commits into from Dec 9, 2019
Merged

Remove bootstrapping code #37

merged 2 commits into from Dec 9, 2019

Conversation

aschmahmann
Copy link
Contributor

@aschmahmann aschmahmann commented Nov 11, 2019

Now that PubSub has an optional discovery service built into it seems reasonable for the PubsubValueStore to assume that the PubSub instance passed into it utilizes this discovery mechanism (if that is in fact what the caller intends). This closes #28.

While we're doing breaking the constructor and semantics anyway (removing the mandatory ContentRouter and needing the PubSub instance passed in to have Discovery enabled) I also added an option pattern to the constructor.

Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

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

Could you write a test to stress concurrent PutValue calls?

pubsub.go Outdated Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
fetch_test.go Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Outdated Show resolved Hide resolved
pubsub.go Show resolved Hide resolved
@aschmahmann aschmahmann force-pushed the feat/discovery branch 2 times, most recently from 26324c6 to e81940b Compare December 9, 2019 16:09
pubsub.go Show resolved Hide resolved
@aschmahmann aschmahmann force-pushed the feat/discovery branch 3 times, most recently from c9170fb to e6a6cc9 Compare December 9, 2019 17:10
@aschmahmann
Copy link
Contributor Author

Before I merge this it'd be nice to be able to run CI on the go-ipfs PR that incorporates the change, for extra testing. However, that's currently blocked bc this repo was updated to the latest version of the datastore interface.

@Stebalien should I just merge this and we can worry about the integration later?

Copy link
Contributor

@dirkmc dirkmc left a comment

Choose a reason for hiding this comment

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

One nit - otherwise LGTM

pubsub_test.go Outdated Show resolved Hide resolved
Copy link
Member

@Stebalien Stebalien left a comment

Choose a reason for hiding this comment

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

LGTM!

@Stebalien Stebalien merged commit cc68c1a into master Dec 9, 2019
@Stebalien Stebalien deleted the feat/discovery branch December 9, 2019 21:09
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.

PutValue context not utilized or propagated into bootstrapping
3 participants