-
Notifications
You must be signed in to change notification settings - Fork 999
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
Change how subgraph_deployment is organized #2267
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lutter
changed the title
Change how subgraph_deloyment is organized
Change how subgraph_deployment is organized
Mar 12, 2021
lutter
force-pushed
the
lutter/deployment
branch
2 times, most recently
from
March 12, 2021 03:21
9013781
to
698cda0
Compare
lutter
force-pushed
the
lutter/deployment
branch
from
March 13, 2021 00:09
698cda0
to
53a7906
Compare
lutter
force-pushed
the
lutter/deployment
branch
from
March 14, 2021 01:15
53a7906
to
a9e366c
Compare
lutter
force-pushed
the
lutter/deployment
branch
from
March 16, 2021 22:27
a9e366c
to
01cfd1b
Compare
tilacog
approved these changes
Mar 17, 2021
lutter
force-pushed
the
lutter/deployment
branch
2 times, most recently
from
March 19, 2021 14:58
7f30603
to
8fc990e
Compare
The test is now independent of how fast the test runs; that will avoid spurious failures in CI
lutter
force-pushed
the
lutter/deployment
branch
2 times, most recently
from
March 19, 2021 23:49
5fffda2
to
857dec3
Compare
Bumps [derive_more](https://github.com/JelteF/derive_more) from 0.99.11 to 0.99.13. - [Release notes](https://github.com/JelteF/derive_more/releases) - [Changelog](https://github.com/JelteF/derive_more/blob/master/CHANGELOG.md) - [Commits](JelteF/derive_more@v0.99.11...v0.99.13) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Bumps [config](https://github.com/mehcode/config-rs) from 0.10.1 to 0.11.0. - [Release notes](https://github.com/mehcode/config-rs/releases) - [Changelog](https://github.com/mehcode/config-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/mehcode/config-rs/commits/0.11.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.38 to 1.0.39. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](dtolnay/anyhow@1.0.38...1.0.39) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Bumps [async-trait](https://github.com/dtolnay/async-trait) from 0.1.41 to 0.1.48. - [Release notes](https://github.com/dtolnay/async-trait/releases) - [Commits](dtolnay/async-trait@0.1.41...0.1.48) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Bumps [tokio-stream](https://github.com/tokio-rs/tokio) from 0.1.3 to 0.1.5. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-stream-0.1.3...tokio-stream-0.1.5) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Since this struct is used to implement LoadQuery for different types, a generic name is better suited for it.
lutter
force-pushed
the
lutter/deployment
branch
from
March 24, 2021 00:50
857dec3
to
64ccc6b
Compare
lutter
force-pushed
the
lutter/deployment
branch
from
March 24, 2021 21:33
64ccc6b
to
f530511
Compare
lutter
force-pushed
the
lutter/deployment
branch
from
March 26, 2021 22:19
f530511
to
85b72ff
Compare
Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.39 to 1.0.40. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](dtolnay/anyhow@1.0.39...1.0.40) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
When an eth adapter would not return the net version or genesis block hash, we would retry indefinitely. We now only try for 30s. If we can not get the net version and genesis block hash during that time, we continue without it. For networks we have used before, we assume that information has not changed. For new networks, we fail startup.
We used to compare the net identifier from the database in ChainStore::new with the net identifier we had previously loaded from the database. We now correctly check the database state with the state we got from providers.
With that, we also use Site more consistently to identify a subgraph
This change gets rid of the block_range column on subgraph_deployment, renames id, the column for the deployment's IPFS hash to 'subgraph', and adds an integer id column whose value will be the same as the id in the deployment_schemas table in the primary.
lutter
force-pushed
the
lutter/deployment
branch
from
March 29, 2021 17:52
85b72ff
to
af76792
Compare
This is merged, but github has trouble tracking this because of the different base branch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a steptowards using the same
id
as the primary key asdeployment_schemas
. It sits on top of #2266 since the former can easily be rolled back in the hosted service if anything goes wrong. This PR contains an irreversible migration and should therefore be rolled out by itself.