Cryptocurrency

Following the merge of bitcoin/bitcoin#23083, we'll throw a non-fatal error at runtime if the documentation for an RPC is incorrect. This behaviour has found numerous issues over a very short period (of the PR being opened). However, this is not something that we want in production / release builds, instead, we want the ability to have it enabled in the CI and when running

Describe your environment

N/A

Describe the enhancement

Currently it seems the max_open_trades can have significant impact on profit. The only way I have been able to find a good number is to run several back

Creating a new issue based on lbryio/lbry-sdk#877

• Update ensure_directory_exists() to check that the directory is writable by the current process.
• If it's not, return a useful error
• Add tests to cover the case when
  • download directory does not exist
  • download dir exists but is not writable
  • dir exists an

Background

Inspired by C-Otto/rebalance-lnd#241.

As part of pathfinding, lnd might encounter edges that have a policy specifying a zero CLTV delta (possibly because of no/outdated gossip?). Every time an edge like this is used in the pathfinding code, a warning is logged: https://github.com/lightningnetwork/lnd/blob/290b78e700021e238f7e6bdce6acc80de8d0a64f/routi

Currently stratumserver has no unit tests. This will improve the quality and allow future commits to be TDD safe. All units will be tested to ensure the module as a unit itself is tested.

Reading currencies, alphavantage returns a greeting note ("welcome") and this note raises an error in alphavantage.py line 363.

            elif "Note" in json_response and self.treat_info_as_error:
                raise ValueError(json_response["Note"])

For this reason, alphavantage does not work in home assistant.

Some unit tests use constructors instead of the block builders, but updating all unit tests is desirable. See nanocurrency/nano-node#2808.

Add custom clj-kondo hooks for macroses to ensure that lint rules are followed inside them.

Macros to be handled:

• fx/defn - similarly to defn with check on metadata for ::events
• fx/merge - seems like it could be lint'ed as thread macro, plus warn on limitations
• defview
• letsubs - lint as let + check on types for

Is your feature request related to a problem? Please describe.
Ugly title for asset new asset. The asset node gets New Asset title after entering the codename.

Describe the solution you'd like
auto rename by referring the codeName --> iconName
set iconName as variable.

Describe alternatives you've considered

Additional context
Add any other context or screenshots

Those two things tend to stall a bit on startup. It would be nice to have the [0%]... output for them.