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

If my node is asked to forward N sats to peer X via channel C, lnd is free to pick any other channel it might have to peer X. As far as I understand the code (switch.go:handlePacketForward), all channels to X (not just C) are checked for eligability, and a random eligable channel is then used for the actual forward.

As part of this eligability check (implemented in link.go:Che

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

We should have a checklist of things to do when adding a new go.mod. Right now dependency management is a mess and importing over go.mods will have an app importing multiple versions of the same dependencies.

We should add all go.mods to dependabot.

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