Automattic / studio

Studio by WordPress.com, a free desktop app that helps developers streamline their local WordPress development workflow.
https://developer.wordpress.com/studio/
GNU General Public License v2.0
191 stars 17 forks source link

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

Open countfak opened 1 month ago

countfak commented 1 month ago

Quick summary

Hi, I wanted to share my experience with database import from a .sql file. I tried multiple times with different database sizes, last one was around 40MB. The import goes on for a while, then the import failed message appears. But the import process is still running in the background.

Steps to reproduce

Drop a large .sql file with the built-in import functionality of an existing site and start the import. It will likely fail, open up the Activity Monitor app and find the Studio process at the top with high CPU usage, meaning that the import is still running in the background. After a while the CPU usage of the process drops, and the import is actually finished.

What you expected to happen

I wasn't expecting to get the error message if the import process was still running in the background.

What actually happened

Got import failed message even if the import was still running, see above.

Impact

One

Available workarounds?

No but the app is still usable

Platform

Mac Silicon

Logs or notes

No response

wojtekn commented 1 month ago

Thanks for reporting the issue @countfak . We will check it.

Robertght commented 1 month ago

Marking this as Triaged but let me know @wojtekn or @countfak if you have a large DB file I could use to test this.

countfak commented 2 weeks ago

Just wanted to follow up on this and share my latest successful attempt.

What I tried and didn't work out:

What worked for me was:

Please note that this only applies in case of large databases with a lot of entries (for reference mine was around 40MB), the built-in import works fine if I try with a smaller database.

wojtekn commented 1 week ago

Thanks for sharing your workaround @countfak, it's useful. We will check how we can improve Studio Importer to support databases of any size.