Transfer Feature Hangs on Asset Transfer

[MihaiSandor]

Bug Report: Transfer Feature Hangs on Asset Transfer

Required System Information

• Node.js version: v20.12.2
• NPM version: 10.8.2
• Strapi version: 4.25.8
• Database: PostgreSQL
• Operating system: Darwin arm64 (macOS on ARM)
• Project Language: JavaScript (please confirm or correct to TypeScript if applicable)

Describe the Bug

The asset transfer feature hangs during the transfer process. When attempting to transfer assets from a remote Strapi CMS deployed on Strapi Cloud to a local instance, the transfer begins but does not complete, persistently stalling at the assets transfer step.

Steps to Reproduce the Behavior

1. Start the asset transfer via the command yarn strapi transfer --from https://cms.domain.org/admin.
2. Enter the necessary transfer token and confirm the deletion of local assets and database to proceed.
3. Confirm continuation despite schema differences between the source and destination.
4. Observe that the entities transfer completes successfully but the asset transfer hangs indefinitely (over 266 seconds observed with no completion).

Expected Behavior

The transfer process should complete successfully without hanging, allowing all entities and assets to be transferred from the source to the destination within a reasonable time frame.

Screenshots

Not applicable

Code Snippets

yarn strapi transfer --from https://cms.domain.org/admin
? Please enter your transfer token for the remote Strapi source [hidden]
? The transfer will delete all the local Strapi assets and its database. Are you sure you want to proceed? Yes
[2024-08-21 19:22:34.754] warn: (Schema Integrity) Review workflows feature does not exist on destination
? There are differences in schema between the source and destination, and the data listed above will be lost. Are you sure you want to continue? Yes
Starting transfer...
✔ entities: 1265 transferred (size: 897.2 KB) (elapsed: 4581 ms)
⠇ assets: 511 transferred (size: 262.4 MB) (elapsed: 266200 ms) (1009.3 KB/s)

Additional Context

This issue occurred under the development environment with Strapi Community Edition. The size of the assets being transferred is significant, and there might be an underlying issue with how large data transfers are handled or a potential timeout/interruption issue that isn't adequately surfaced in the logs.