running the following command on our production tenant (>200.000 site collections) results in a traceback:
m365 spo report siteusagedetail --period D180 --output text >foo.csv
(node:15496) UnhandledPromiseRejectionWarning: RangeError: Too many properties to enumerate
at Function.getOwnPropertyNames ()
at Function.formatOutput (C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\cli\Cli.js:372:60)
at Object.log (C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\cli\Cli.js:163:40)
at C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:30:20
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:15496) 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:15496) [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.
running the following command on our production tenant (>200.000 site collections) results in a traceback:
m365 spo report siteusagedetail --period D180 --output text >foo.csv
(node:15496) UnhandledPromiseRejectionWarning: RangeError: Too many properties to enumerate
at Function.getOwnPropertyNames ()
at Function.formatOutput (C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\cli\Cli.js:372:60)
at Object.log (C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\cli\Cli.js:163:40)
at C:\Users\z003292x\AppData\Roaming\npm\node_modules@pnp\cli-microsoft365\dist\m365\base\PeriodBasedReport.js:30:20
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use
node --trace-warnings ...to show where the warning was created)(node:15496) 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:15496) [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.