Some async functions hang while running reach stdlib

[hmzdot]

const { loadStdlib } = require("@reach-sh/stdlib")
const { assert } = require("chai")

const reach = loadStdlib("ALGO")

describe("Simple Suite", function() {
    this.timeout(100000000)

    async function setup() {
        const startBal = reach.parseCurrency(100)
        console.log(startBal)

        const accs = await reach.newTestAccounts(2, startBal)
        console.log(accs)
        return accs
    }

    it("Test #1", function(done) {
        setup().then((accs) => { 
            assert.lengthOf(accs, 2, `expected accs len 2 got ${accs.length}`)
            done() 
        })
    })

    it("Test #2", async function() {
        try {
            const accs = await setup()
            console.log(accs)
        }
        catch(e) { console.log(e) }

        assert.lengthOf(accs, 2, `expected accs len 2 got ${accs.length}`)
    })
})

Both ''Test 1" and "Test 2" appear to hang when execution comes to the newTestAccounts part while running the contracts with npx mocha

[hmzdot]

This might be related to running stdlib on node environment because a similar thing happens when the code is ran without mocha and chai

[jeapostrophe]

Every test program and the tutorials all run with node and we obey all the normal JS/node patterns. I would investigate your node setup, your network setup, and if the JS package you're using is blocking or hiding activity. Running with debugging messages may show what is happening behind the scenes.

[Lucaster13]

I have gotten reach to run tests before but for some reason since I've gotten a new machine, reach no longer works.

My Setup:

Node 18.1.0
npm 8.8.0

I created a completely clean project and the package.json only imports reach

package.json:

{
    "name": "app",
    "version": "0.1.0",
    "private": true,
    "type": "module",
    "dependencies": {
        "@reach-sh/stdlib": "^0.1.10-rc.4"
    },
    "scripts": {
    },
    "devDependencies": {
    }
}

test.mjs:

import { loadStdlib } from "@reach-sh/stdlib";

const reach = loadStdlib("ALGO");

(async () => {
    console.log("here");
    const provider = await reach.getProvider();
    console.log(provider);
    const accs = await reach.newTestAccount(reach.parseCurrency(10));
    console.log(accs);
})();

I am trying to run node test.mjs and the program prints "here", but then never resolves the promises. I am sort of at a loss for how to debug this. Was hoping starting a fresh project might pinpoint the issue, but unfortunately this still hangs in limbo.

Is your testing setup using a different node/npm version?

Thanks!

[hmzdot]

I think it is possible to replicate this by starting a new project with npm init -y; npm install @reach-sh/stdlib then running node index.js where index.js is

const { loadStdlib } = require("@reach-sh/stdlib")
 
 const reach = loadStdlib("ALGO")
 
 const main = async () => {
     const startBal = reach.parseCurrency(100)
     console.log(startBal)
 
     await reach.wait("2")
 }
 
 main()
 .then(() => { process.exit(0) })
 .catch((e) => { console.error(e); process.exit(-1) })

[jeapostrophe]

I recommend running with REACH_DEBUG=Y and you'll be able to see what is being waited on

[hmzdot]

This was because most stdlib functions require devnet to be running in the background and as it will try to connect to the devnet it looks like halting.

Starting a development network using ./reach devnet and then running tests works fine

[michaelsermoneta]

thank you Jeapostrophe, I think you are right. My IDE is Intellij Ultimate on Windows, while devnet is running in WSL (Ubuntu). What is the solution? Find a way to run the devnet on Windows?

[jeapostrophe]

My advice is to do the opposite and try to run the program in WSL2, such as by running it with reach run

[michaelsermoneta]

Thank you. I already made it work with the "reach run" command, but I was trying to make the debugger work with the breakpoints, so i needed node js. I solved changing this line
const stdlib = loadStdlib();
to
const stdlib = loadStdlib('ALGO');
I'm totally new to reach , so this could be the wrong solutions, I don't know.

[DanBurton]

loadStdlib() will look at your environment variables by default, and will use the input if specified. loadStdlib('ALGO') is a valid way to do it. You may, alternatively, want to consider using REACH_CONNECTOR_MODE=ALGO in whatever environment is used to run node.js.

[jeapostrophe]

Yea, it looks like you were trying to connect to an ETH devnet but you actually started an ALGO devnet. Your original post didn't say that you were trying to do ALGO, so I assumed the ETH error message was intentional