graphprotocol / graphprotocol/indexer

Actions error reporting degraded since `.21` release

Open
#776 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug indexer-agent indexer-cli p2
Dominant language
TypeScript
Stars
262
Forks
148
PR merge metrics
No merged PRs in 30d

Description

Also the actions.. if there is an error it usually just says no actions found instead of the actual error, not sure when that got lost but it doesnt spit out an error since .21 (only for 1 or 2 cases so far, but for most its not)
-Discord link

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing an actions failure described in the issue and compare error reporting before and after the .21 release. Trace where the failure becomes “no actions found” instead of the underlying error. Done means the affected action errors are surfaced accurately rather than replaced by that message.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.