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

recreate rpc.pb.go #1601

Closed
wants to merge 1 commit into from
Closed

Conversation

34ro
Copy link

@34ro 34ro commented Jul 22, 2018

I got some diff when I tried to execute lnrpc/gen_protos.sh.

I used libprotoc 3.6.0 for OSX.

@Roasbeef
Copy link
Member

See #1467. Until that's merged, you'll need to use the versions that are specified in the contribution guidelines: https://github.com/lightningnetwork/lnd/blob/master/docs/code_contribution_guidelines.md#456-protobuf-compilation

@@ -17,7 +17,8 @@
"paths": {
"/v1/balance/blockchain": {
"get": {
"summary": "* lncli: `walletbalance`\nWalletBalance returns total unspent outputs(confirmed and unconfirmed), all\nconfirmed unspent outputs and all unconfirmed unspent outputs under control\nof the wallet.",
"summary": "*\nGenSeed is the first method that should be used to instantiate a new lnd\ninstance. This method allows a caller to generate a new aezeed cipher seed\ngiven an optional passphrase. If provided, the passphrase will be necessary\nto decrypt the cipherseed to expose the internal wallet seed.",
Copy link
Contributor

Choose a reason for hiding this comment

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

Interesingly, it has the same problem as #1467 (diff) that indicates there is something wrong with our proto files.

cc @wpaulino

@34ro 34ro force-pushed the recreate-rpc-files branch from 828ba4c to fc810d1 Compare July 23, 2018 14:11
@34ro 34ro changed the title recreate rpc.pb.go rpc.pb.gw.go rpc.swagger.json recreate rpc.pb.go Jul 23, 2018
@34ro
Copy link
Author

34ro commented Jul 23, 2018

I ran gen_protos.sh with v.3.4.0. ( I got the same error as #1570 )
There remain some diffs, but they look trivial.

@halseth
Copy link
Contributor

halseth commented Sep 19, 2018

Closing, as the changes are insignificant at this point. Thanks for the heads up though, we'll make sure this becomes consistent once we have updated to the newet protoc! 😀

@halseth halseth closed this Sep 19, 2018
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.

4 participants