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

Have trouble running "the-rewarder" #6

Closed
Flyy-yu opened this issue Mar 3, 2021 · 0 comments
Closed

Have trouble running "the-rewarder" #6

Flyy-yu opened this issue Mar 3, 2021 · 0 comments

Comments

@Flyy-yu
Copy link

Flyy-yu commented Mar 3, 2021

This is what I got by running "npm run the-rewarder" with the original "the-rewarder.challenge.js" file.
No problem with all other challenges.


All contracts have already been compiled, skipping compilation.


  [Challenge] The rewarder
    1) "before all" hook for "Exploit"
    2) "after all" hook for "Exploit"


  0 passing (433ms)
  2 failing

  1) [Challenge] The rewarder
       "before all" hook for "Exploit":
     Error: Contract error: contract binary not set. Can't deploy new instance.
This contract may be abstract, not implement an abstract parent's methods completely
or not invoke an inherited contract's constructor correctly

      at Function.new (node_modules/@truffle/contract/lib/contract/constructorMethods.js:47:13)
      at Context.<anonymous> (test/the-rewarder/the-rewarder.challenge.js:23:55)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)

  2) [Challenge] The rewarder
       "after all" hook for "Exploit":
     TypeError: Cannot read property 'roundNumber' of undefined
      at Context.<anonymous> (test/the-rewarder/the-rewarder.challenge.js:76:37)
      at processImmediate (internal/timers.js:456:21)



npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! @ the-rewarder: `npm run compile && npx mocha --timeout 50000 --exit test/the-rewarder/the-rewarder.challenge.js`
npm ERR! Exit status 2
npm ERR! 
npm ERR! Failed at the @ the-rewarder script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.



@Flyy-yu Flyy-yu closed this as completed Mar 3, 2021
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

1 participant