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

Remove block index arg from manual account sync test util #255

Merged
merged 1 commit into from
Feb 17, 2022

Conversation

Shramp
Copy link
Contributor

@Shramp Shramp commented Feb 17, 2022

Soundtrack of this PR: No Ghosty

Motivation

We don't actually need to provide a target block index. Instead, let the account sync up to the most recent block.

In this PR

  • Remove target block index arg from manually_sync_account fn.
  • Remove that arg from all calls to that fn.

Ticket

@Shramp Shramp changed the base branch from main to develop February 17, 2022 00:46
@Shramp Shramp merged commit adbac63 into develop Feb 17, 2022
@Shramp Shramp deleted the feature/remove-block-index-from-test-util branch February 17, 2022 17:14
briancorbin added a commit that referenced this pull request Mar 4, 2022
* adding max limit to some API endpoints (#248)

* Remove unnecessary foreign keys from gift_codes table. (#249)

* Update readme installation instructions (#250)

* Enable foreign key constraints. Fix transient FK errors when deleting an account. (#251)

* Remove foreign key check before running migrations. This allows databases with existing foreign key errors to be fixed by the migrations. (#252)

* Fix a bug causing sync to create many tiny chunks. (#253)

* Remove target block arg from manually sync account fn (#255)

* Initial action to build containers for tag pushes (#256)

* Supporting FOG enabled accounts (#254)

* FOG Creds default to empty string if not provided from API (#257)

* update readme (#259)

* Api key guard (#205)

* fixing issue with ledger not syncing automatically (#261)

* sync up to the last block instead of excluding it (#262)
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.

3 participants