nft-merkle-allowlist-scaffold icon indicating copy to clipboard operation
nft-merkle-allowlist-scaffold copied to clipboard

hey everyone thread '<unnamed>' panicked at 'assertion failed: `(left == right)` error when I run command 'yarn dev'

Open jianvector opened this issue 2 years ago • 1 comments

Describe the bug A clear and concise description of what the bug is. [root@VM-0-15-centos web]# yarn dev yarn run v1.22.17 $ next dev ready - started server on 0.0.0.0:3000, url: http://localhost:3000 info - Loaded env from /root/NFT/nft-merkle-whitelist-scaffold/web/.env thread '' panicked at 'assertion failed: (left == right) left: 22, right: 0', library/std/src/sys/unix/condvar.rs:63:9 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 error - ./node_modules/next/dist/client/dev/amp-dev.js Error: failed to process ^C [root@VM-0-15-centos web]# yarn build yarn build yarn run v1.22.17 $ next build info - Loaded env from /root/NFT/nft-merkle-whitelist-scaffold/web/.env info - Checking validity of types info - Creating an optimized production build ..thread '' panicked at 'assertion failed: (left == right) left: 22, right: 0', library/std/src/sys/unix/condvar.rs:63:9 note: run with RUST_BACKTRACE=1 environment variable to display a backtrace thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 thread '' panicked at 'Once instance has previously been poisoned', library/std/src/sync/once.rs:393:21 info - Creating an optimized production build Failed to compile.

./node_modules/next/dist/client/next.js Error: failed to process assertion failed: (left == right) left: 22, right: 0

./node_modules/next/dist/client/router.js Error: failed to process

./node_modules/next/dist/pages/_error.js Error: failed to process

./pages/_app.js Error: failed to process

./pages/index.js Error: failed to process

Build failed because of webpack errors error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

To Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context Add any other context about the problem here.

jianvector avatar Mar 04 '22 06:03 jianvector

Hey! This is likely because you have an empty .env variable or something missing from there

straightupjac avatar Apr 13 '22 22:04 straightupjac