There are many reports of the test being flaky: bitcoin/bitcoin#20672 (comment)

Thus, it should be made more robust, as described in bitcoin/bitcoin#20538 (comment)

Useful skills:

• Background in our functional test suite (python3)
• Background in zmq

Want to work on this issue?

For guidance on

Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Describe the enhancement

freqtrade generates the output of max-drawdown, which is very useful, but lacks an important information.. the real question
of max-drawdown is, does the strategy have a enough money to complete?

i wrote an backtesting tool, and i generate two more columns which i find useful:

df_trades['sum'] = df_trades['profit_abs'].cumsum()
trades_profit_min = df

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Description

I've been noticing a lot of users using the client in fullscreen or constantly resizing the width of the window. The layout of the navigation looks broken whenever the width goes beyond the default on load. It would look a lot more polished if we keep the navigation contained in its original width.

Version

1.5.1

Expected behaviour

Navigation should have a maximum

Refactor function names in costs.clar contract to use dashes instead of underscores