Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cln-gprc
is assuming therpc-file
path is set as default, which may not always be the case. Set the path the what the plugin manager reportsContext
Lately, Polar for macOS has been unable to deploy CLN nodes due to an issue with how the
rpc-file
is generated on the docker volume (see jamaljsr/polar#779 for details). Recently, a workaround has been found, consisting of moving therpc-file
outside of its default location. However, doing so makescln-grpc
unable to connect to the backend.This can be worked around by creating a simlink in the default location to point to where
lightning-rpc
is actually located. However, the underlying issue lies incln-grpc
not getting the info fromcln-plugin
but instead, assuming the location of the file.