-
-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.16 results change break the app #1154
Comments
Same here, no idea why it expects EDIT: Going back to 0.15.5 brings everything right back up for me, no data lost. |
Same problem for me |
Same |
Some for me, but I use sqlite and when I went to v0.15.5 I "lost" everything. Looking the database.sqlite the results table is empty but the results_bad_json is ok. When I try to run the latest version this error occour: I removed the results table and renamed the results_bad_json to results and now the v0.15.5 it's showing the results.
|
Workaround: i stopped the container, renamed the table "results_bad_json" to "bak_results_bad_json", started the container an it works. then you need to change the value for "bad_json_migrated" in the settings table from true to false. Start the container and migrate your data. |
For those having an issue can you confirm if you're using my image or the LSIO one? |
I'm Using your image |
I got this issue with both your image and the LSIO one. Reverting to 0.15.5 fixed it with both versions. Using Postgres. |
I used yours
Switched to linuxserver and its the same.
…On Mon, 19 Feb 2024 at 22:36 Alex Justesen ***@***.***> wrote:
For those having an issue can you confirm if you're using my image or the
LSIO one?
—
Reply to this email directly, view it on GitHub
<#1154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AO5ATMH4HZ3PVFIVQOYBKTTYUOZVJAVCNFSM6AAAAABDP2TSKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGEZDSOJSGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Same here with the official repo. Going back to 0.15.5 solved it here as well. |
upgraded to 0.16, failed to start the app
🚛 Migrating the database...
[2024-02-19 17:23:00] production.ERROR: Tried loading settings 'App\Settings\GeneralSettings', and following properties were missing: prune_results_older_than {"exception":"[object] (Spatie\LaravelSettings\Exceptions\MissingSettings(code: 0): Tried loading settings 'App\Settings\GeneralSettings', and following properties were missing: prune_results_older_than at /var/www/html/vendor/spatie/laravel-settings/src/Exceptions/MissingSettings.php:13)
[stacktrace]
#0 /var/www/html/vendor/spatie/laravel-settings/src/SettingsMapper.php(118): Spatie\LaravelSettings\Exceptions\MissingSettings::create()
#1 /var/www/html/vendor/spatie/laravel-settings/src/SettingsMapper.php(42): Spatie\LaravelSettings\SettingsMapper->ensureNoMissingSettings()
#2 /var/www/html/vendor/spatie/laravel-settings/src/Settings.php(266): Spatie\LaravelSettings\SettingsMapper->load()
#3 /var/www/html/vendor/spatie/laravel-settings/src/Settings.php(97): Spatie\LaravelSettings\Settings->loadValues()
#4 /var/www/html/database/migrations/2024_02_18_100000_results_bad_json_table.php(60): Spatie\LaravelSettings\Settings->__set()
#5 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(493): Illuminate\Database\Migrations\Migration@anonymous->up()
#6 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(410): Illuminate\Database\Migrations\Migrator->runMethod()
#7 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(419): Illuminate\Database\Migrations\Migrator->Illuminate\Database\Migrations\{closure}()
#8 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(216): Illuminate\Database\Migrations\Migrator->runMigration()
#9 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/View/Components/Task.php(37): Illuminate\Database\Migrations\Migrator->Illuminate\Database\Migrations\{closure}()
#10 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(756): Illuminate\Console\View\Components\Task->render()
#11 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(216): Illuminate\Database\Migrations\Migrator->write()
#12 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(181): Illuminate\Database\Migrations\Migrator->runUp()
#13 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(124): Illuminate\Database\Migrations\Migrator->runPending()
#14 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(90): Illuminate\Database\Migrations\Migrator->run()
#15 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Migrations/Migrator.php(633): Illuminate\Database\Console\Migrations\MigrateCommand->Illuminate\Database\Console\Migrations\{closure}()
#16 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(83): Illuminate\Database\Migrations\Migrator->usingConnection()
#17 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(36): Illuminate\Database\Console\Migrations\MigrateCommand->handle()
#18 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Util.php(41): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#19 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(93): Illuminate\Container\Util::unwrapIfClosure()
#20 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(35): Illuminate\Container\BoundMethod::callBoundMethod()
#21 /var/www/html/vendor/laravel/framework/src/Illuminate/Container/Container.php(662): Illuminate\Container\BoundMethod::call()
#22 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(211): Illuminate\Container\Container->call()
#23 /var/www/html/vendor/symfony/console/Command/Command.php(326): Illuminate\Console\Command->execute()
#24 /var/www/html/vendor/laravel/framework/src/Illuminate/Console/Command.php(180): Symfony\Component\Console\Command\Command->run()
#25 /var/www/html/vendor/symfony/console/Application.php(1096): Illuminate\Console\Command->run()
#26 /var/www/html/vendor/symfony/console/Application.php(324): Symfony\Component\Console\Application->doRunCommand()
#27 /var/www/html/vendor/symfony/console/Application.php(175): Symfony\Component\Console\Application->doRun()
#28 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(201): Symfony\Component\Console\Application->run()
#29 /var/www/html/artisan(35): Illuminate\Foundation\Console\Kernel->handle()
#30 {main}
"}
In MissingSettings.php line 13:
Tried loading settings 'App\Settings\GeneralSettings', and following proper
ties were missing: prune_results_older_than
s6-rc: warning: unable to start service laravel-automations: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
prog: fatal: stopping the container.
usermod: no changes
and now after reboot
[2024-02-19 17:23:07] production.ERROR: SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'results_bad_json' already exists (Connection: mysql, SQL: rename table
results
toresults_bad_json
) {"exception":"[object] (Illuminate\Database\QueryException(code: 42S01): SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'results_bad_json' already exists (Connection: mysql, SQL: rename tableresults
toresults_bad_json
) at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Connection.php:829)The text was updated successfully, but these errors were encountered: