Set higher timeouts for import/export wp-cli commands

[ashfame]

Related issues

• Database import from .sql file failes, but process keeps running in the background #544

Proposed Changes

• Default timeout of 5mins for waiting on wp-cli command to finish is too small for big imports. In this PR, I have added a higher timeout for import/export commands, which gets used by passing an arg longRunning: true to executeWpCliCommand()
• Show a custom error message when it does timeout (currently set to 24hrs)

Testing Instructions

• I tested it by lowering the default timeout to small like 5 secs and process a normal backup file, it fails as per the linked issue
• Then on this branch, keep the default timeout lowered and see it uses the higher timeout set for import/export and finishes up.

Pre-merge Checklist

• Have you checked for TypeScript, React or other console errors?

[sejas]

The changes look good. Increasing the import process will allow users to import websites with more content.

To establish reasonable limits, we might need to benchmark the amount of content imported on a typical computer and set a limit based on those metrics.

I’ve added a couple of suggestions, please let me know what you think.

[sejas]

@ashfame, Thanks for considering my suggestions. I like the new approach where wp-cli-process handles selecting the timeout based on the command.

I've tested it and confirmed that the timeout for SQLite export and import processes is 6 hours, while the rest of wp-cli commands still 5 minutes.

I've left a couple of non-blocking comments.

[ashfame]

@sejas Thanks for the review! I made both the changes. Will merge shortly 👍