lightning

Background

When doing a closechannel, you need to give a txid and index, separately. Having the option to provide a channel point would be useful.

Marnix
What would be the risk in accepting a chan_point in closechannel? :thinking_face:

guggero
_on the RPC level it's a channel point. so

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

AFAIK c-lightning and LND already implemented a feature where raised channel relay fees taking effect is delayed by 10 minutes or so to avoid routing failures and give the update message enough time to propagate through the gossip network.

If possible, this should come with an option to optionally enforce the new fee right away, when routing failures are preferred over a quickly depleted channe

Summary

_This has been happing somewh

Is your feature request related to a problem? Please describe.
I would like to use an external on-chain wallet for interacting with the regtest bitcoin network. Currently I have to go the shell and send a transaction an address generated in my external wallet software.

Describe the solution you'd like
I would like a "Mine to address" textbox in each bitcoin node, which allows me to ea

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

🚀 The feature

In version 0.5.x we have full support for YOLOv5, at the cost of introducing more dependencies. If someone just wants to use the models for inference, he/she doesn't need all additional features like:

• visualizations
• profiling
• type conversions to pandas
• ...

However, those useful features are (pa

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

I would appreciate support for my local currency, ILS (Israel Shekels).