Skip to content

Conversation

@meowsbits
Copy link
Contributor

@meowsbits meowsbits commented Mar 17, 2020

Follow up to #20771

Since its always available, why would a user specify it explicitly?
#20771 (comment)

I don't know... because they can? Should they know otherwise that the module is always available? Doesn't seem to be mentioned at all in https://geth.ethereum.org/docs/rpc/server.

I think we should just tell people that it's always available and not specify it.
#20771 (comment)

Documentation would be helpful.


This just prevents a false negative ERROR warning when, for some unknown reason, a user attempts to turn on the module rpc even though it's already going to be on.

@meowsbits meowsbits requested review from fjl and holiman as code owners March 17, 2020 21:05
rpc/endpoints.go Outdated

// checkModuleAvailability check that all names given in modules are actually
// available API services.
// available API services. It assumes that the special snowflake "rpc" module is always available.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please reword this comment to be more neutral.

@fjl fjl merged commit 93ffb85 into ethereum:master Mar 21, 2020
@karalabe karalabe added this to the 1.9.13 milestone Mar 27, 2020
enriquefynn pushed a commit to enriquefynn/go-ethereum that referenced this pull request Mar 10, 2021
…0776)

This just prevents a false negative ERROR warning when, for some unknown
reason, a user attempts to turn on the module rpc even though it's already going
to be on.
gzliudan added a commit to gzliudan/XDPoSChain that referenced this pull request Nov 13, 2024
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.

3 participants