Cryptocurrency

Similar to how the fee is returned in getblock (#18771), it should be returned in getrawtransaction.

Useful skills:

Understanding of undo data, the RPC interface and the functional tests.

Want to work on this issue?

For guidance on contributing, please read CONTRIBUTING.md before opening your pull request

This is a very simple enchantment, but I think it is so helpful for intuitively comparing strat's performances.

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

When compaction failed as described in #5936 I got the following message:

could not start compaction, destination folder /home/bitcoin/.lnd/data/graph/mainnet only has 10823012352 bytes of free disk space available while we need at least 10196967424 for worst-case compaction

This is confusing, as 10823012352 > 10196967424.

Your environment

• 0.14.0-beta.rc2
• L

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.

The instructions and infrastructure for building on windows are not very good. It takes too long and there are too many manual steps and too much ambiguity and it takes too long between each manual step. We need to do better. I followed the instructions at build options on nano.org. I did not try to follow the steps taken by the CI build which maybe would been better because at least there would b

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

As discussed in cosmos/cosmos-sdk#9913

In adr-046, the sdk decided to move away from a param module in favor of having each sdk module handle its own parameters. This is an optional change for applications and the Param module will live on in a deprecated form. The sdk w

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