Unit testing for epoch-based runtime timeout

Open
#5,237 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
testing-qa

Research direction

Start by reading the epoch-based runtime timeout fix in pull request 5236 and identify the changed code and its existing test area. Add a unit test covering that timeout behavior, then run the relevant Rust test target and confirm the regression is covered.

Written by the indexing model from the issue text.

Description

Stale testing

The bug fix in https://github.com/graphprotocol/graph-node/pull/5236 was merged without an unit test due to being a hotfix.

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.