-
Notifications
You must be signed in to change notification settings - Fork 21.4k
whisper: move whisper to another repo #21371
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
Conversation
github.com/golang/snappy v0.0.2-0.20200707131729-196ae77b8a26 | ||
github.com/google/go-cmp v0.3.1 // indirect | ||
github.com/gorilla/websocket v1.4.1-0.20190629185528-ae1634f6a989 | ||
github.com/gorilla/websocket v1.4.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is actually going from 1.4.1+ back to 1.4.1, no?
I think in general, you seem have updated the go modules in 'wildcard mode'? While that may be good (or not), I think deps-updates should be done more deliberately in a separate PR.
whisperFlags = []cli.Flag{ | ||
utils.WhisperEnabledFlag, | ||
utils.WhisperMaxMessageSizeFlag, | ||
utils.WhisperMinPOWFlag, | ||
utils.WhisperRestrictConnectionBetweenLightClientsFlag, | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be better to leave the flags, but put them in 'DeprecatedFlags' and just issue warnings whenever any one of them is used. "The flag xxx has been deprecated; whisper has been moved to a separate repository (link)." Otherwise nodes which uses these flags will just fail to come up again after an update.
Replaced by #21487. |
Move Whisper to its own repo.