We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(ActiveRecord::StatementInvalid) "Mysql2::Error: Table 'sequencescape_snapshot.labware' doesn't exist
Describe the bug
[Psd-exceptions] [Sequencescape Training] (ActiveRecord::StatementInvalid) "Mysql2::Error: Table 'sequencescape_snapshot.labware' doesn't An ActiveRecord::StatementInvalid occurred in background at 2025-01-18 12:00:10 +0000 : Mysql2::Error: Table 'sequencescape_snapshot.labware' doesn't exist /var/www/sequencescape/shared/vendor/bundle/ruby/3.2.0/gems/mysql2-0.5.6/lib/mysql2/client.rb:151:in `_query'
Acceptance Criteria
To Reproduce Steps to reproduce the behaviour:
Expected behaviour An error is not thrown
Additional context Error message contains the below data: {:message=>"Import Fluidigm Data Cron Failed"}
data: {:message=>"Import Fluidigm Data Cron Failed"}
It is likely that the cron running every hour fails during the weekly training database dump as the tables may temporarily not exist.
The text was updated successfully, but these errors were encountered:
This has been happening for 8 years. You are correct that it is caused by the training database being recreated.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Acceptance Criteria
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
An error is not thrown
Additional context
Error message contains the below
data: {:message=>"Import Fluidigm Data Cron Failed"}
It is likely that the cron running every hour fails during the weekly training database dump as the tables may temporarily not exist.
The text was updated successfully, but these errors were encountered: