When it determines the number of configs at the start,
it attempts to scan past this number:
and then errors:
(node:32908) UnhandledPromiseRejectionWarning: Error: Invalid bool: 32 at WrappedLayout.decodeBool [as decoder] (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\borsh\dist\lib\index.js:124:11) at WrappedLayout.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\borsh\dist\lib\index.js:62:21) at Structure.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\buffer-layout\lib\Layout.js:1234:32) at Structure.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\buffer-layout\lib\Layout.js:1234:32) at AccountsCoder.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\anchor\dist\cjs\coder\accounts.js:36:23) at C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:193:63 at Array.reduce (<anonymous>) at C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:191:37 at Generator.next (<anonymous>) at fulfilled (C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:25:58) (Usenode --trace-warnings ...to show where the warning was created) (node:32908) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:32908) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
When it determines the number of configs at the start,
it attempts to scan past this number:
and then errors:
(node:32908) UnhandledPromiseRejectionWarning: Error: Invalid bool: 32 at WrappedLayout.decodeBool [as decoder] (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\borsh\dist\lib\index.js:124:11) at WrappedLayout.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\borsh\dist\lib\index.js:62:21) at Structure.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\buffer-layout\lib\Layout.js:1234:32) at Structure.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\buffer-layout\lib\Layout.js:1234:32) at AccountsCoder.decode (C:\Users\*\Documents\Projects\willy-wonka\ts\node_modules\@project-serum\anchor\dist\cjs\coder\accounts.js:36:23) at C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:193:63 at Array.reduce (<anonymous>) at C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:191:37 at Generator.next (<anonymous>) at fulfilled (C:\Users\*\Documents\Projects\willy-wonka\ts\build\cli.js:25:58) (Usenode --trace-warnings ...to show where the warning was created) (node:32908) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag--unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:32908) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.Might be because there's no cutoff?