Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to perform feed account for main-v2 #4

Closed
GistKen opened this issue Jun 3, 2022 · 3 comments
Closed

Unable to perform feed account for main-v2 #4

GistKen opened this issue Jun 3, 2022 · 3 comments

Comments

@GistKen
Copy link

GistKen commented Jun 3, 2022

Unable to perform feed account for main-v2

  1. Spin up main-v2 fork: npm run node:fork:main-v2
  2. Attempt to feed the account with the balances: npm run feed-accounts:main-v2 -- --accounts 0x976EA74026E726554dB657fA54763abd0C3a0aa9

Error:

[warning] balance storage layout not found for [
  'AMPL',
  '0xD46bA6D942050d489DBd938a2C909A5d5039A161',
  symbol: 'AMPL',
  tokenAddress: '0xD46bA6D942050d489DBd938a2C909A5d5039A161'
]
- Succesfully changed the balance of input addresses to:
An unexpected error occurred:

Error: cannot find artifact "IERC20DetailedBytes"
    at Object.getArtifact (/com.docker.devenvironments.code/node_modules/hardhat-deploy/src/DeploymentsManager.ts:213:17)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async getContract (/com.docker.devenvironments.code/helpers/utils.ts:30:20)
    at async getTokenSymbol (/com.docker.devenvironments.code/helpers/utils.ts:183:33)
    at async /com.docker.devenvironments.code/helpers/utils.ts:218:15

Expected: Fed Accounts with no errors

@kartojal
Copy link
Contributor

kartojal commented Aug 5, 2022

Could you try to use latest version? Them compile the contracts to create the artifacts.

npm run compile

npm run node: fork:main-v2

npm run feed-accounts:main-v2 -- --accounts 0x976EA74026E726554dB657fA54763abd0C3a0aa9

@A-ndy-git
Copy link

Updating the package version alone should resolve this issue.

It is also worth noting npm run compile is unnecessary as it gets called within npm run node:fork:main-v2.

package.json:

{
     "node:fork:main-v2": "MARKET=main-v2 npm run node:eth",
     "node:eth": "npm run compile && env-cmd --use-shell \"npm run node:eth:subtask\""
}

@kartojal
Copy link
Contributor

Closing due this should be fixed, @Makalfo let us know if there is any other problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@kartojal @GistKen @A-ndy-git and others