Open luceos opened 7 years ago
This has been most likely a memory issue.
@Luceos but how come it used to work like a charm before? It used to work perfectly until i updated to the version with the update feature.
Updating is a very lengthy process, we will explore new ways of reducing memory usage and process duration in the future. We already have some ideas how to do so, but that will be a bit more far-reaching in what we do to change the Flarum install.
@Luceos it's not the updating of extensions that's not working (in fact, I haven't even tried using the update feature yet) .... it's the installation of extensions.... it used to always work but ever since the bazaar version that contains the extension update feature, even the extensions that successfully installed previously now give this same exact error if i try install them again (yes, i did remove them for the purpose of testing... but I removed them through ssh)
I have no idea what could trigger this error, but here are a few leads:
Laravel sets a database reconnect strategy (https://github.com/laravel/framework/blob/v5.1.38/src/Illuminate/Database/DatabaseManager.php#L195) but Flarum does not (https://github.com/flarum/core/blob/v0.1.0-beta.6/src/Database/DatabaseServiceProvider.php) so any database timeout will cause this exception (thrown here https://github.com/laravel/framework/blob/v5.1.38/src/Illuminate/Database/Connection.php#L715)
Not found any useful Stackoverflow thread so far, this exception probably never happens with a real Laravel application given it has a reconnector. Maybe adding a reconnector to Flarum could prevent such issue to happen again.
We could temporarily do this ourselves and PR against core to patch this.
@Luceos Can't wait!!!
@ibrahimk157 reports having issues with bazaar, the error triggered is: