Ashish Kumar
Ashish Kumar
@JanJakes The reason why I like what we have more is that it explicitly begins with a tiny script changing the version number in code files `bin/prepare-release.sh 1.2.3`. The resultant...
@MidhunSureshR This is now finished and ready for your review :)
Could you point to the page where the link is broken?
I am unable to reproduce the issue. I tried with a couple of sql files, biggest one being 829M and as soon as import fails, Electron Helper process which was...
Hi @countfak Yes, that's likely that stray process in background isn't an issue anymore. And import is currently failing on some zips due to a regression that I am looking...
Documenting the work I am doing in this regard: - Expose more info on when a wp-cli command fails - Big imports would also time out after 5mins, so I...
I realized `wp-cli command canceled` only happens when the process times out. Anytime an actual error happens, it gets logged to the log file. And since the default timeout for...
Hi @countfak Do you mind giving `v1.3.4` a try to see if the issue is resolved for you, it has higher timeout limits for import/export?
It would be nice to know whether WP was just installed or we are just "resuming", so that diff blueprint steps can be run accordingly.
> `shouldRunBlueprint: 'when-installing-wordpress' | 'always' // naming tbd` @adamziel This allows conveying, whether "always" or just on "first boot". Doesn't let a user specify blueprint for only post-installation boots. In...