Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: GetRemainingPaymentCount was off by 1 #602

Merged
merged 1 commit into from
Sep 7, 2015
Merged

fix: GetRemainingPaymentCount was off by 1 #602

merged 1 commit into from
Sep 7, 2015

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Sep 7, 2015

No description provided.

@UdjinM6 UdjinM6 added the bug label Sep 7, 2015
eduffield222 pushed a commit that referenced this pull request Sep 7, 2015
fix: GetRemainingPaymentCount was off by 1
@eduffield222 eduffield222 merged commit 818303d into dashpay:v0.12.0.x Sep 7, 2015
@UdjinM6 UdjinM6 deleted the remainingoffby1 branch March 7, 2016 03:06
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jun 9, 2022
…ption methods

a63b60f refactor: Add OptionsModel getOption/setOption methods (Ryan Ofsky)

Pull request description:

  This is a trivial change which is needed as part of dashpay#602 to get bitcoind and bitcoin-qt to use the same settings instead of different settings. It is split off from dashpay#602 because it causes a lot of rebase conflicts (any time there is a GUI options change).

  This PR is very small and easy to review ignoring whitespace: https://github.com/bitcoin-core/gui/pull/600/files?w=1

ACKs for top commit:
  vasild:
    ACK a63b60f
  furszy:
    Code review ACK a63b60f
  promag:
    Code review ACK a63b60f.

Tree-SHA512: 1d99a1ce435b4055c1a38d2490702cf5b89bacc7d168c9968a60550bfd9f6dace649d5e98699de68d6305f02d5d1e3eb7e177ab578b98b996dd873b1df0ed236
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Jun 9, 2022
…s to OptionsModel constructor

31122aa refactor: Pass interfaces::Node references to OptionsModel constructor (Ryan Ofsky)

Pull request description:

  Giving OptionsModel access to the node interface is needed as part of dashpay#602 to get bitcoind and bitcoin-qt to use the same settings instead of different settings.

  It has been split off from dashpay#602 to simplify that PR. Previously these commits were part of bitcoin#15936 and also had some review discussion there.

ACKs for top commit:
  promag:
    Code review ACK 31122aa.
  furszy:
    Code ACK 31122aa
  jarolrod:
    ACK 31122aa

Tree-SHA512: b8529322fd7ba97e19864129e6cf5f9acc58c124f2e5a7c50aca15772c8549de3c24e8b0c27e8cf2c06fd26529e9cdb898b0788a1de3cbfdfbdd3f85c9f0fe69
PastaPastaPasta pushed a commit to PastaPastaPasta/dash that referenced this pull request Feb 19, 2023
… onion-prev settings

9d3127b Add settings.json prune-prev, proxy-prev, onion-prev settings (Ryan Ofsky)

Pull request description:

  With dashpay#602, if proxy and pruning settings are disabled in the GUI and the GUI is restarted, proxy and prune values are not stored anywhere. So if these settings are enabled in the future, default values will be shown, not previous values.

  This PR stores previous values so they will preserved across restarts. I'm not sure I like this behavior because showing default values seems simpler and safer to me. Previous values may just have been set temporarily and may have never actually worked, and it adds some code complexity to store them.

  This PR is one way of resolving dashpay#596. Other solutions are possible and could be implemented as alternatives.

ACKs for top commit:
  hebasto:
    ACK 9d3127b, tested on Ubuntu 22.04.
  vasild:
    ACK 9d3127b
  jarolrod:
    tACK 9d3127b

Tree-SHA512: 1778d1819443490c880cfd5c1711d9c5ac75ea3ee8440e2f0ced81d293247163a78ae8aba6027215110aec6533bd7dc6472aeead6796bfbd51bf2354e28f24a9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants