Consensys / truffle-security

MythX smart contract security verification plugin for Truffle Framework
https://mythx.io
124 stars 28 forks source link

--yaml not working #142

Closed nbanmp closed 5 years ago

nbanmp commented 5 years ago

--yaml is not working correctly. It errors with something like:

{ YAMLException: unacceptable kind of an object to dump [object Function]
    at writeNode (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:756:13)
    at writeBlockMapping (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:634:10)
    at writeNode (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:727:9)
    at writeBlockMapping (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:634:10)
    at writeNode (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:727:9)
    at writeBlockSequence (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:521:9)
    at writeNode (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:740:9)
    at dump (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:817:7)
    at Object.safeDump (/home/nat/Dev/mythx/truffle-security/node_modules/js-yaml/lib/js-yaml/dumper.js:823:10)
    at objects.forEach.obj (/home/nat/Dev/mythx/truffle-security/helpers.js:381:34)
    at Array.forEach (<anonymous>)
    at doReport (/home/nat/Dev/mythx/truffle-security/helpers.js:380:17)
    at Object.analyze (/home/nat/Dev/mythx/truffle-security/helpers.js:572:12)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)
  name: 'YAMLException',
  reason: 'unacceptable kind of an object to dump [object Function]',
  mark: undefined,
  message: 'unacceptable kind of an object to dump [object Function]' }
rocky commented 5 years ago

Yep. As Valintin would put it, that was a "known problem", (i.e. one that I encountered before, but was waiting for someone else to discover, in the hope I would have been able to fix it first before others encountered.)

@nbanmp want to try your hand at it? It shouldn't be difficult to fix.