Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / cdecker/lnet issues and pull requests
#16 - build(deps): bump flask from 1.0.2 to 2.3.2
Pull Request -
State: open - Opened by dependabot[bot] almost 2 years ago
Labels: dependencies
#15 - lnet broke with newer c-lightning API?
Issue -
State: open - Opened by renepickhardt over 5 years ago
#14 - Upgrade pylightning version
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#13 - Improve base Flask route and graph visualization tool
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#12 - Replace deprecated "generate" Bitcoin RPC call
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#11 - Remove requests dependency
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#10 - Ignore bitcoin data dirs
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#9 - Fix UnixDomainSocketRpc method calls
Pull Request -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#8 - Nodes fail to launch
Issue -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#7 - (RPC?) Error
Issue -
State: closed - Opened by justinmoon over 5 years ago
- 1 comment
#6 - update for clightning address type change
Pull Request -
State: closed - Opened by rsbondi over 5 years ago
#5 - How to build / run lnet without pip3 install?
Issue -
State: open - Opened by s-tikhomirov almost 6 years ago
- 6 comments
#4 - OtherError: [Errno 2] No such file or directory: 'lightningd': 'lightningd'
Issue -
State: open - Opened by s-tikhomirov almost 6 years ago
- 6 comments
#3 - Not compatible with newaddr: deprecate 'address' output in clightning
Issue -
State: closed - Opened by rsbondi almost 6 years ago
#2 - ImportError: No module named concurrent.futures
Issue -
State: closed - Opened by ghost about 6 years ago
- 2 comments
#1 - pip3 install lnet does not result in successful execution afterwards: lnet.utils unknown. ModuleNotFoundError: No module named 'lnet'
Issue -
State: closed - Opened by renepickhardt over 6 years ago
- 4 comments