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

Move notifications package to status-go codebase. #692

Merged
merged 1 commit into from
Feb 22, 2018
Merged

Conversation

mandrigin
Copy link
Contributor

Minimum viable changes to unblock #686.
notifications package is moved to status-go, unnecessary parts of patches are removed.

Closes #655

@mandrigin mandrigin force-pushed the igorm/655-2 branch 2 times, most recently from be66daf to 2adfeee Compare February 21, 2018 17:37
@dshulyak
Copy link
Contributor

looks good, but why not to drop this packages completely, right in this change? i think it was already confirmed that it is not used

@mandrigin
Copy link
Contributor Author

@dshulyak was it? I missed that discussion...

@JekaMas
Copy link
Contributor

JekaMas commented Feb 21, 2018

I think we can drop it.

@dshulyak
Copy link
Contributor

@mandrigin #648 (comment)

@mandrigin
Copy link
Contributor Author

mandrigin commented Feb 21, 2018

@dshulyak

		// enable notification service
		if whisperConfig.EnablePushNotification {
			log.Info("Register PushNotification server")

			var notificationServer notifications.NotificationServer

That is exactly where this moved code is used, NotificationServer was never in status-go, see the same file, https://github.com/status-im/status-go/blob/develop/geth/node/node.go#L22

GitHub
status-go - The Status module that consumes go-ethereum

@dshulyak
Copy link
Contributor

@mandrigin maybe i misunderstood smth, but i decided that this EnabledPushNotification is not used at all

@mandrigin
Copy link
Contributor Author

@adambabik can you help?

@dshulyak
Copy link
Contributor

if we do then we need to cover it with e2e tests asap

@adambabik
Copy link
Contributor

It does not take part in sending push notifications. We can remove it and also remove the place where it is used.

@@ -1,36 +0,0 @@
diff --git a/whisper/notifications/utils.go b/whisper/notifications/utils.go
Copy link
Contributor

Choose a reason for hiding this comment

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

We can also remove the reference to this file from the README.md

@pedropombeiro
Copy link
Contributor

Shouldn't the shh.notify command-line option be removed as well?

@mandrigin
Copy link
Contributor Author

@pombeirp yeah, that exactly what linter told me :)

@pedropombeiro
Copy link
Contributor

pedropombeiro commented Feb 21, 2018

The same changes should be made to _assets/patches/geth/0014-whisperv6-notifications.patch and 0015-whisperv6-envelopes-tracing.patch

Copy link
Contributor

@pedropombeiro pedropombeiro left a comment

Choose a reason for hiding this comment

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

LGTM once the whisperv6 patch files are addressed.

Copy link
Contributor

@JekaMas JekaMas left a comment

Choose a reason for hiding this comment

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

Great to see this PR

@mandrigin mandrigin merged commit c06d58a into develop Feb 22, 2018
@mandrigin mandrigin deleted the igorm/655-2 branch February 22, 2018 10:10
return nil, errors.New("notification server requires -identity file to be specified")
}

if whisperConfig.IdentityFile != "" {
Copy link
Contributor

Choose a reason for hiding this comment

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

IdentityFile may be useful to make sure the nodeID stays the same.

Copy link
Contributor

Choose a reason for hiding this comment

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

Scratch that. Let's leave it removed. If we hit some issues it should be implemented from scratch as this should not be a part of Whisper config if used as a nodeID.

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.

5 participants