stack-auth/pgmock

RangeError: Maximum call stack size exceeded

Opened this issue · 1 comments

I'm trying to add pgmock in our E2E testing suite using NestJS, TypeORM + Jest.

I get the following error thrown though:

Unhandled Rejection at: Promise {
      <rejected> TypeError: Cannot read properties of undefined (reading '0')
          at Object.<anonymous>.r.Bitmap.get (/<REDACTED>/node_modules/pgmock/dist/main.js:3039:25)
          at E.Object.<anonymous>.E.unpack_memory (/<REDACTED>/node_modules/pgmock/dist/main.js:10548:19)
          at E.Object.<anonymous>.E.set_state (/<REDACTED>/node_modules/pgmock/dist/main.js:10491:14)
          at E.Object.<anonymous>.E.restore_state (/<REDACTED>/node_modules/pgmock/dist/main.js:8124:18)
          at D.Object.<anonymous>.D.restore_state (/<REDACTED>/node_modules/pgmock/dist/main.js:2881:25)
          at Y.d (/<REDACTED>/node_modules/pgmock/dist/main.js:12413:35)
          at listOnTimeout (node:internal/timers:569:17)
          at processTimers (node:internal/timers:512:7)
    } reason: TypeError: Cannot read properties of undefined (reading '0')
        at Object.<anonymous>.r.Bitmap.get (/<REDACTED>/node_modules/pgmock/dist/main.js:3039:25)
        at E.Object.<anonymous>.E.unpack_memory (/<REDACTED>/node_modules/pgmock/dist/main.js:10548:19)
        at E.Object.<anonymous>.E.set_state (/<REDACTED>/node_modules/pgmock/dist/main.js:10491:14)
        at E.Object.<anonymous>.E.restore_state (/<REDACTED>/node_modules/pgmock/dist/main.js:8124:18)
        at D.Object.<anonymous>.D.restore_state (/<REDACTED>/node_modules/pgmock/dist/main.js:2881:25)
        at Y.d (/<REDACTED>/node_modules/pgmock/dist/main.js:12413:35)
        at listOnTimeout (node:internal/timers:569:17)
        at processTimers (node:internal/timers:512:7)

...

RangeError: Maximum call stack size exceeded

      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:471691)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)
      at _ZN3v863cpu3cpu21call_interrupt_vector17h15f125d3196b6ae5E (wasm:/wasm/0060a6c6:1:734657)
      at _ZN3v863cpu3cpu12do_page_walk17h3226b305185b420aE (wasm:/wasm/0060a6c6:1:472412)

Any ideas what this might indicate?

N2D4 commented

Thanks for the report, do you have a minimal reproducible example?