graphprotocol / graphprotocol/contracts
Resuming `migrate` will not perform calls on already deployed contracts
Open
Nobody has claimed this yet.
bug
- Dominant language
- Solidity
- Stars
- 374
- Forks
- 176
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 4
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the migrate command's resume path and reproduce the behavior where already deployed contracts receive no calls. Trace the resume handling and identify the existing test or migration fixture that covers deployed contracts; done means resuming migrate performs the expected calls and the behavior is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100