Skip to content

Tags: avandras/graph-node

Tags

fraction3

Toggle fraction3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
build(deps): bump substreams from 0.5.10 to 0.5.12 (graphprotocol#5041)

Bumps [substreams](https://github.com/streamingfast/substreams-rs) from 0.5.10 to 0.5.12.
- [Release notes](https://github.com/streamingfast/substreams-rs/releases)
- [Changelog](https://github.com/streamingfast/substreams-rs/blob/develop/CHANGELOG.md)
- [Commits](streamingfast/substreams-rs@v0.5.10...v0.5.12)

---
updated-dependencies:
- dependency-name: substreams
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

fraction

Toggle fraction's commit message
graphql: wire SQLParser in StoreResolver::handle_sql

fraction2

Toggle fraction2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Fix offchain created from offchain (graphprotocol#5051)

* refactor: Refactor SubgraphInstance::new_host

* refactor: Move `Hosts` to a module of `instance`

* refactor: Use `mod.rs` style for context and instance

* refactor: Make `mod instance` private to `context`

* fix(offchain): Separate onchain and offchain hosts

The hosts Vec expected the hosts to be pushed in ascending order
of block number. Creating a file ds B within another file ds A violated
that assumption, because B will have the same creation block as A. This
is by design, so the cleanest way to fix this seemed to be separating
the data structures for onchain and offchain hosts. Offchain data sources
do not need to maintain insertion order, as their processing order
ultimately does not impact determinism because they each have their own
causality region. If in the future we introduce a feature that allows
two different offchain data sources to have the same causality region, we maybe
need to revisit this.

* fix: Fix an optimize `*Host::contains`, rename iter_by_address

canary-investigate-stuck-substreams-v0.33.0-2dbfca2d7

Toggle canary-investigate-stuck-substreams-v0.33.0-2dbfca2d7's commit message
Added all messages for coverage

v0.33.0

Toggle v0.33.0's commit message
Add new API Version to validate when setting fields not defined in th…

…e schema (graphprotocol#4894)

* build(deps): bump chrono from 0.4.26 to 0.4.31 (graphprotocol#4876)

Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.26 to 0.4.31.
- [Release notes](https://github.com/chronotope/chrono/releases)
- [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md)
- [Commits](chronotope/chrono@v0.4.26...v0.4.31)

---
updated-dependencies:
- dependency-name: chrono
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump webpki from 0.22.0 to 0.22.1 (graphprotocol#4857)

Bumps [webpki](https://github.com/briansmith/webpki) from 0.22.0 to 0.22.1.
- [Commits](https://github.com/briansmith/webpki/commits)

---
updated-dependencies:
- dependency-name: webpki
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* runtime: only include valid fields in entity for store_set

* graph, runtime: add new apiVersion to validate fields not defined in the schema

* graph: update tests for setting invalid field

* tests: add runner tests for undefined field setting validation in apiVersion 0.0.8

* graph: add check_invalid_fields method to HostExports

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

v0.33.0-rc.0

Toggle v0.33.0-rc.0's commit message
Add new API Version to validate when setting fields not defined in th…

…e schema (graphprotocol#4894)

* build(deps): bump chrono from 0.4.26 to 0.4.31 (graphprotocol#4876)

Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.26 to 0.4.31.
- [Release notes](https://github.com/chronotope/chrono/releases)
- [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md)
- [Commits](chronotope/chrono@v0.4.26...v0.4.31)

---
updated-dependencies:
- dependency-name: chrono
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump webpki from 0.22.0 to 0.22.1 (graphprotocol#4857)

Bumps [webpki](https://github.com/briansmith/webpki) from 0.22.0 to 0.22.1.
- [Commits](https://github.com/briansmith/webpki/commits)

---
updated-dependencies:
- dependency-name: webpki
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* runtime: only include valid fields in entity for store_set

* graph, runtime: add new apiVersion to validate fields not defined in the schema

* graph: update tests for setting invalid field

* tests: add runner tests for undefined field setting validation in apiVersion 0.0.8

* graph: add check_invalid_fields method to HostExports

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

integer

Toggle integer's commit message
Add new API Version to validate when setting fields not defined in th…

…e schema (graphprotocol#4894)

* build(deps): bump chrono from 0.4.26 to 0.4.31 (graphprotocol#4876)

Bumps [chrono](https://github.com/chronotope/chrono) from 0.4.26 to 0.4.31.
- [Release notes](https://github.com/chronotope/chrono/releases)
- [Changelog](https://github.com/chronotope/chrono/blob/main/CHANGELOG.md)
- [Commits](chronotope/chrono@v0.4.26...v0.4.31)

---
updated-dependencies:
- dependency-name: chrono
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump webpki from 0.22.0 to 0.22.1 (graphprotocol#4857)

Bumps [webpki](https://github.com/briansmith/webpki) from 0.22.0 to 0.22.1.
- [Commits](https://github.com/briansmith/webpki/commits)

---
updated-dependencies:
- dependency-name: webpki
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* runtime: only include valid fields in entity for store_set

* graph, runtime: add new apiVersion to validate fields not defined in the schema

* graph: update tests for setting invalid field

* tests: add runner tests for undefined field setting validation in apiVersion 0.0.8

* graph: add check_invalid_fields method to HostExports

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

canary-investigate-stuck-substreams-ccac28fd4

Toggle canary-investigate-stuck-substreams-ccac28fd4's commit message
Improved `Next response received` to also log the message kind (to be…

…tter "see" the stream)

canary-investigate-stuck-substreams-def370693

Toggle canary-investigate-stuck-substreams-def370693's commit message
Added more logging to check if Substreams is stuck or something else

invalid-field-validation

Toggle invalid-field-validation's commit message
tests: add runner tests for undefined field setting validation in api…

…Version 0.0.8