Handling Stuck Firehose cursor

Open
#5,176 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

The body names no files, tests, or entry points and contains only a task list. Start by reviewing linked issues 5177, 5178, and 5179, then clarify the scope of cursor recovery, block rewind, remote graphman, paused-subgraph listing, database tunneling, and startup behavior; done requires an agreed, testable scope for these items.

Written by the indexing model from the issue text.

Description

### Tasks
- [ ] https://github.com/graphprotocol/graph-node/issues/5177
- [ ] Tool to rewind block ingestor
- [ ] https://github.com/graphprotocol/graph-node/issues/5179
- [ ] Ability to run graphman remotely
- [ ] Flag to start the subgraph after rewind regardless of previous state
- [ ] https://github.com/graphprotocol/graph-node/issues/5178
- [ ] graphman list paused subgraphs
- [ ] Tool to handle tunneling to the DB automatically based on config
Dominant language
Rust
Stars
3.2k
Forks
1.1k
Avg merge
4d 1h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphprotocol/graph-node

All issues in graphprotocol/graph-node

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.