lightning

In the output of list channels the private/public status of the channel is returned, but in the output of pending channels the status is not revealed. To allow for recognizing a pending open channel as a private requires waiting for the channel to confirm.

Ideally the PendingChannelsResponse would include the channel flags or the private/public status of the channel to know which type of chan

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

When we return a bitcoin amount, our JSON responses currently specify the unit (btc, sat, msat) in the parameter name, but it's a bit ugly and is missing in some places.

Maybe it would be better to include the unit explicitly in the response. I see two different options:

• Instead of returning a numeric value, return a string including the unit (e.g. "2500 msat", "0.45 btc", "1.5 mbtc"). The

Just a note as a reminder to update the Electrs guide with the latest version v0.9.6 (the git clone and git verify-tag commands)

Summary

_This has been happing somewh

I am unable to resize text in the xterm.js instance

I would like to be able to press ctrl+ to increase text size and ctrl- to decrease text size.

🚀 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:

• #355
• profiling
• type conversions to pandas

However, those useful features are (partial

payment_request is returned so you can parse that to display the memo

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

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