-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: graphprotocol/graph-node
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: graphprotocol/graph-node
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: lutter/hosted
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 10 commits
- 20 files changed
- 3 contributors
Commits on Sep 16, 2025
-
all: fix all cargo check warnings (#6102)
Fixes all 16 cargo check warnings across the codebase: **Cargo.toml fixes:** - Remove invalid `doc = false` key from git dependency **Dead code warnings:** - Add #[allow(dead_code)] to reference implementations and test utilities - PoI struct and helper functions (proof_of_indexing/reference.rs) - AscSubgraphEntityOp enum (runtime/wasm) - CopyVid struct (store/postgres) **Lifetime syntax warnings:** - Add explicit '_ lifetime parameters to fix confusing syntax - Fix 11 lifetime warnings across store, runtime, and utility modules All tests pass and cargo check now produces zero warnings. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for a5d8811 - Browse repository at this point
Copy the full SHA a5d8811View commit details -
core: Better logging of assignment events
In particular, include the deployment hash
Configuration menu - View commit details
-
Copy full SHA for 388d230 - Browse repository at this point
Copy the full SHA 388d230View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2bd144b - Browse repository at this point
Copy the full SHA 2bd144bView commit details -
Configuration menu - View commit details
-
Copy full SHA for d2f40bd - Browse repository at this point
Copy the full SHA d2f40bdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 260f13f - Browse repository at this point
Copy the full SHA 260f13fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 35554d0 - Browse repository at this point
Copy the full SHA 35554d0View commit details
Commits on Sep 17, 2025
-
Configuration menu - View commit details
-
Copy full SHA for e734af7 - Browse repository at this point
Copy the full SHA e734af7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 25caea7 - Browse repository at this point
Copy the full SHA 25caea7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 98dea2e - Browse repository at this point
Copy the full SHA 98dea2eView commit details -
all: Defer getting manifest from IPFS when starting subgraph
The current code in `SubgraphAssignmentProvider.start` fetched the manifest from IPFS before starting a subgraph. But the code calling `start`, ultimately `SubgraphRegistrar.start_assigned_subgraphs` waited for all subgraphs to start successfully before processing assignment events. That could lead to a situation where a slow IPFS server, even if it was slow for just one subgraph, could keep a node from processing assignment events. With these changes, interacting with IPFS is deferred to the future that is spawned for running the subgraph so that slow IPFS can slow how long it takes for a subgraph to start, but not the system overall.
Configuration menu - View commit details
-
Copy full SHA for 0106f26 - Browse repository at this point
Copy the full SHA 0106f26View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...lutter/hosted