lightning

Background

Often Tor only nodes become unreachable while still online which causes long channel downtimes and being unable to fulfill Pool bids.

Your environment

• version of lnd
  v0.12.1
• which operating system (uname -a on *Nix)
  Linux raspberrypi 5.10.17-v8+ #1403 SMP PREEMPT Mon Feb 22 11:37:54 GMT 2021
  aarch64 GNU/Linux
• version of btcd, bitcoind, or other back

Our xgboost models use the binary:logistic' objective function, however the m2cgen converted version of the models return raw scores instead of the transformed scores.

This is fine as long as the user knows this is happening! I didn't, so it took a while to figure out what was going on. I'm wondering if perhaps a useful warning could be raised for users to alert them of this issue? A warning

I have two setups using bitcoind v21.99.0.

Eclair testnet (SQLite backend) has started without wallet parameter in config while mainnet (Postgre) didn't and I could only make it working with provided wallet.

I had to restart mainnet bitcoind because I was thinking that it was in failed state but apparently wallet was loaded and I reloaded it again after restart. Everything returned back

Summary

_This has been happing somewh

Is your feature request related to a problem? Please describe.
LND connect Url contains parameters to work with GRPC API and not REST.

Describe the solution you'd like
Add a new field and a copy button for LND Connect REST API.

Additional context

Description of the Feature or Idea

Ratelimit the speed at which sites can create getInfo()/sendInvoice()/makeInvoice() requests if they require opening a window (for example, getInfo(), if pre-approved, should not be ratelimited). In testing, a buggy/malicious site can easily open tens or hundreds of windows.

Existing Example(s) of Feature

Here is an example piece of code to tri

Some candidates for removal that could easily be re-implemented inside Spark:

• superagent (only used for a simple HTTP GET request, can be replaced with the built-in http module)

• helmet (sets security headers)

• js-yaml (only used to format objects in a human-readable manner, we don't really need yaml)

• nanoid (secure random string generator)

• is-ip (few-liner depende

This might be a good idea and sufficiently easy to implement.
Just leaving the suggestion here for the future.

I'm getting this error when converting a customized yolov5 to yolort:

Traceback (most recent call last):
  File "convert_ultralytics_to_yolort.py", line 31, in <module>
    num_classes=80)
  File "/yolov5/yolort/utils/update_module_state.py", line 74, in update_module_state_from_ultralytics
    module_state_updater.updating(model)
  File "/yolov5/yolort/utils/update_module_state.py", li