thrown: undefined

Question

thrown: undefined

jjz opened this issue 3 years ago · 28 comments

Instructions

This error occurred when I ran the test:
https://github.com/onflow/kitty-items/tree/master/cadence/tests

Problem

NFT Storefront › should deploy NFTStorefront contract

    thrown: undefined

      30 |
      31 | describe("NFT Storefront", () => {
    > 32 |      beforeEach(async () => {
         |      ^
      33 |              const basePath = path.resolve(__dirname, "../../");
      34 |              const port = 7003;
      35 |              await init(basePath, {port});

      at test/nft-storefront.test.js:32:2
      at Object.<anonymous> (test/nft-storefront.test.js:31:1)

Answer 1 · 2022-02-20T20:48:48.000Z

@jjz can you tell me Flow CLI and flow-js-testing versions you are using?

Answer 2 · 2022-02-21T02:57:43.000Z

flow version
Version: v0.31.1

"flow-js-testing": "^0.2.2"

Answer 3 · 2022-02-21T14:57:44.000Z

Seeing the same error with flow-cli@0.31.1 and flow-js-testing@0.2.2 when deploying a contract.

Upgrading to flow-js-testing@0.2.3-alpha.2 returns a result with this error:

[ null, 'undefined is not supported' ]

This seems to only happen when deploying a contract with arguments, when I deploy another contract without it all works fine.

My args: args: ["lorem", 10000, "123"]

Answer 4 · 2022-02-21T15:47:51.000Z

Seeing the same error with flow-cli@0.31.1 and flow-js-testing@0.2.2 when deploying a contract.

Upgrading to flow-js-testing@0.2.3-alpha.2 returns a result with this error:
[ null, 'undefined is not supported' ]
This seems to only happen when deploying a contract with arguments, when I deploy another contract without it all works fine.

My args: args: ["lorem", 10000, "123"]

Can you put here your contract init method? (with exactly the same formatting)

Answer 5 · 2022-02-21T16:11:27.000Z

@MaxStalker
Here you go, it's the default example NFT init function with some added config parameters (description, supply, IPFS CID)

    init(description: String, maximumSupply: UInt64, metadataCID: String) {
        // Initialize the total supply
        self.totalSupply = 0

        // Initialize the maximum supply
        self.maximumSupply = maximumSupply

        // Initialize the metadata CID
        self.metadataCID = metadataCID

        // Initialize the description
        self.description = description

        // Initialize the revealed flag
        self.revealed = false

        // Set the named paths
        self.CollectionStoragePath = /storage/TokenCollection
        self.CollectionPublicPath = /public/TokenCollection
        self.AdminStoragePath = /storage/TokenAdmin

        // Create a Collection resource and save it to storage
        let collection <- create Collection()
        self.account.save(<-collection, to: self.CollectionStoragePath)

        // create a public capability for the collection
        self.account.link<&Token.Collection{NonFungibleToken.CollectionPublic, Token.TokenCollectionPublic}>(
            self.CollectionPublicPath,
            target: self.CollectionStoragePath
        )

        // Create a Admin resource and save it to storage
        let admin <- create Admin()
        self.account.save(<-admin, to: self.AdminStoragePath)

        emit ContractInitialized()
    }

Answer 6 · 2022-02-22T00:58:10.000Z

Here you go, it's the default example NFT init function with some added config parameters (description, supply, IPFS CID)

I'm using the example [kitty-items] in there and I'm not changing the code

Answer 7 · 2022-02-22T13:55:45.000Z

@jjz can you try 0.2.3-alpha.3

Answer 8 · 2022-02-23T01:57:59.000Z

@jjz can you try 0.2.3-alpha.3

How? Has it been released?

Answer 9 · 2022-02-23T07:17:46.000Z

@jjz can you try 0.2.3-alpha.3

How? Has it been released?

It's on npm, yeah. Simply bump version in package.json and run npm/yarn install

Answer 10 · 2022-02-23T16:47:59.000Z

@MaxStalker bumping to 0.2.3-alpha.3 from 0.1.13 causes alot of problems. Emulator does not stop Aftereach test, and expect changes from a value to an array of [result, error]

Answer 11 · 2022-02-24T09:42:22.000Z

Part of it worked, but there was a new error。

 Kitty Items › supply should be 0 after contract is deployed

    TypeError: e is not iterable

      51 |              await shallPass(setupKittyItemsOnAccount(KittyAdmin));
      52 |
    > 53 |              await shallResolve(async () => {
         |              ^
      54 |                      const supply = await getKittyItemSupply();
      55 |                      expect(supply).toBe(0);
      56 |              });

      at node_modules/flow-js-testing/src/jest-asserts.js:66:26
          at runMicrotasks (<anonymous>)
      at Object.<anonymous> (test/kitty-items.test.js:53:3)

Answer 12 · 2022-02-24T10:42:47.000Z

Hi Everyone
Is there any update for this issue. I also get stuck on the same issue.

Answer 13 · 2022-02-24T12:31:54.000Z

@jjz shallResolve expect that async callback will return tupple [result, err]
you can rewrite your code like this:

const [supply] = await shallResolve(getKittyItemsSupply())
expect(supply).toBe(0)

Answer 14 · 2022-02-24T12:32:28.000Z

Hi Everyone Is there any update for this issue. I also get stuck on the same issue.

@bevis-lin Bump your js-testing-version to 0.2.3-alpha.3

Answer 15 · 2022-02-24T12:33:09.000Z

@MaxStalker bumping to 0.2.3-alpha.3 from 0.1.13 causes alot of problems. Emulator does not stop Aftereach test, and expect changes from a value to an array of [result, error]

@timongll yes, this is a major release, which requires code to be refactored 🤷
I'm looking why afterEach not stopping emulator. But I can't reproduce it here yet. Are you sure it's not running alongside - in VSCode maybe?

Answer 16 · 2022-02-24T15:17:53.000Z

For everyone here still having troubles, please try 0.2.3-alpha.4 version of flow-js-testing together with 0.31.1 of CLI

Answer 17 · 2022-02-27T01:02:03.000Z

This is still broken for me using 0.2.3-alpha.4 with version 0.31.1 of the CLI. I get a long string of

console.log node_modules/flow-js-testing/dist/index.js:1
    DEBUG: 🎁  GetLatestBlock called

when running a test. Test hangs until timeout

Answer 18 · 2022-02-27T16:39:08.000Z

I had some weird cadence errors that don't appear when using the flow emulator but now with 0.2.3-alpha.4 alongside 0.31.1 version all my issues have flown away.

Answer 19 · 2022-03-01T03:33:48.000Z

Hmm, still nothing. Getting the same issue. I'm running on Ubuntu 20.04, in case that's relevant

Answer 20 · 2022-03-19T13:56:02.000Z

Please see: #94 (comment)

Answer 21 · 2022-03-20T02:19:38.000Z

yep, i had this error too.
when i try to test, the error said "undefined is not support"

but we found maybe the panic fields is too long🐱‍🐉? the js-testing it will throw error✔
i change it and make sense ✔

Answer 22 · 2022-04-21T18:41:37.000Z

@s1119858711 @onkel-skrue @seddik11 @adhurjaty @bevis-lin @jjz @timongll @maggo can you try to fetch 0.2.3-alpha.5 version and try to run your tests again?..

Answer 23 · 2022-04-21T22:34:15.000Z

0.2.3-alpha.5

flow cli version: v0.33.0
flow-js-testing version: 0.2.3-alpha.5

No problems or any errors with my tests ✔️

Answer 24 · 2022-04-24T22:08:21.000Z

@MaxStalker changing to alpha.5 fixed my issue. Thanks!

Answer 25 · 2022-06-12T22:43:55.000Z

Probably a duplicated report, but since with Secure Cadence we're using CLI v0.36.0 - with this flow-cli version alpha.5 still has the same error.

Are we expected to get a stable version of flow-js-testing that's working fine with latest cli?

Answer 26 · 2022-07-06T14:22:50.000Z

Still issue with flow-cli v0.37.2 and v0.2.3-alpha.7 :(

Answer 27 · 2022-07-06T16:49:09.000Z

Hi @PeterBenc the package has been moved to @onflow/flow-js-testing - can you confirm you still have this issue with @onflow/flow-js-testing@0.3.0-alpha.8

Answer 28 · 2022-07-15T17:12:03.000Z

Closing, please re-open if this happens again.