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

chore: NTRN-288: use websocket to wait for new block #50

Merged
merged 4 commits into from
Jan 18, 2023

Conversation

foxpy
Copy link
Contributor

@foxpy foxpy commented Dec 9, 2022

Previous behaviour used to be HTTP polling busy loop.

[NTRN-288] [Test run]

@foxpy foxpy force-pushed the chore/NTRN-288-wait-for-new-block-websocket branch 4 times, most recently from 3942479 to c0b1fae Compare December 24, 2022 07:41
@foxpy foxpy force-pushed the chore/NTRN-288-wait-for-new-block-websocket branch 2 times, most recently from fd74c90 to 5cdd69b Compare December 28, 2022 11:33
src/helpers/wait.ts Outdated Show resolved Hide resolved
@foxpy foxpy force-pushed the chore/NTRN-288-wait-for-new-block-websocket branch from 5cdd69b to 5a88673 Compare January 15, 2023 21:32
@foxpy foxpy requested a review from sotnikov-s January 16, 2023 10:45
@foxpy foxpy force-pushed the chore/NTRN-288-wait-for-new-block-websocket branch 2 times, most recently from 9990285 to cc02750 Compare January 16, 2023 15:06
@foxpy foxpy force-pushed the chore/NTRN-288-wait-for-new-block-websocket branch from cc02750 to 6210a02 Compare January 17, 2023 11:54
}
};

waitBlocks(n: number) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
waitBlocks(n: number) {
waitBlocks(n: number, timeout=120000): Promise<void> {

src/helpers/wait.ts Outdated Show resolved Hide resolved
@zavgorodnii zavgorodnii merged commit c8e2d0a into main Jan 18, 2023
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.

4 participants