lightning

Background

Macaroons are created after wallet creation. However, the documentation in the main installation (https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md) states the following:

Running lnd for the first time will by default generate the admin.macaroon, read_only.macaroon, and macaroons.db files that are used to authenticate into lnd.

As a first-time LND user,

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

It would be nice if we could rename each individual node. Sometimes, Alice, Bob and Carol... are too vague for practical usage.

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

Ie. https://btcpay.kukks.org/rates?storeid=GPpuLBt2VaQEFySV4qjXM2xNCMo5iQDoKuqiRP6DA37T&currencyPairs=BTC_USD,BTC_EUR

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

The outputs are great, although not the same as yolov5, maybe some pre-processing/post-processing steps are different.

That's a great catch! I think it is caused by the different pre-processing operations. I've verified the the post-processing stages before, it can get the same results as ultralytics/yolov5 (when w/o TTA predict). And I've uploaded a [notebook](https://github.com/zhiqwang/yol