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

Permit rpc help even during warmup #433

Closed
wants to merge 131 commits into from

Conversation

jmjatlanta
Copy link

Fixes #432

This will allow the server to reply to the help rpc call even if the server is not fully warmed up.

NOTE: Implementations of new RPC functionality must assure that nothing is done if the help boolean is set to true.

tonymorony and others added 30 commits April 8, 2020 09:15
Mihailo: `changed vout order so it is comparing marker value instead of vout to destination value.`
fix chanelsCC test vouts
fix broken secret reveal test
add rpc response validation
refund check no longer depends on the vout number
prevents test failure on different branches due to ChannelsCC changes
In some cases CCs throwing exception such as:

`{'error': {'code': -3, 'message': 'Amount out of range'}`

And in some cases errors responses forming manually, e.g.:

`{'error': {'code': -3, 'message': 'Amount out of range'}`

lets handle both options (thanks to @dimxy for advise)
Workflows - fix pull_request events trigger
Corrected hardfork timestamp to June14th
Added enter/leave critical section around TestBlockValidity call in BitcoinMiner()
…-komodo

# Conflicts:
#	qa/pytest_komodo/basic/pytest_util.py
@jmjatlanta jmjatlanta marked this pull request as ready for review May 14, 2021 18:33
@ca333 ca333 changed the base branch from research-archive to dev May 23, 2021 09:59
@ca333
Copy link

ca333 commented Jun 1, 2021

@jmjatlanta plz if you get a chance sync this one up - changed the base to dev which seem caused some conflicts

@jmjatlanta
Copy link
Author

jmjatlanta commented Jun 1, 2021

@jmjatlanta plz if you get a chance sync this one up - changed the base to dev which seem caused some conflicts

I added unrelated changes to this PR, mainly comments, which caused conflicts. I will create a new PR based on dev that will only contain the requested change. (See PR #452)

@jmjatlanta jmjatlanta closed this Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants