Error in the generation of the export file

[martinraynov]

We have an error in the end of the script that blocks the generation of the export file :

  ⚛  Normalizing result.
  Uploading chunk of size 4194304 bytes at offset 0 with content range: bytes 0-4194303/4439402
  Uploading chunk of size 1898701 bytes at offset 0 with content range: bytes 0-1898700/1898701
  (node:1835) UnhandledPromiseRejectionWarning: Error: read ECONNRESET
      at TLSWrap.onStreamRead (internal/stream_base_commons.js:201:27)
  (node:1835) 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(). (rejection id: 1)
  (node:1835) [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.```

[zibs1]

Same here. Looks like there is some cap on size of repo users or the amount of repos or maybe the size of exported csv file?
It works ok for me with smaller size orgs and a smaller amount of users.
Found this one below:
https://docs.microsoft.com/en-us/answers/questions/61020/connectionerror-connection-lost-read-econnreset-no.html

Would it be the case to follow workaround?: tediousjs/tedious#923 (comment)

or probably better handling TCP connections as per?
https://stackoverflow.com/questions/54408047/how-to-stop-the-error-read-econnreset-from-happening