Could not determine schema/structure #1254
Comments
|
I'm seeing the same with I've not modified the Running Interestingly, running P.S. I tried removing the |
|
I see the Heroku Ruby Buildpack is printing the error here. The code is checks for Next step might be to do some hacking on the buildpack and see what's happening in more detail. I'll come back to that if this ticket doesn't otherwise move forwards before then :) |
|
Hello. Sorry for the delay here. I was out. I took a look and I was unable to reproduce this behavior with a Rails 7 app https://github.com/sharpstone/rails-jsbundling. I get a successful migration: I'm going to need some more information to debug this. Do you have any support tickets open with this behavior on Heroku? If not, do you have an example app that reproduces the behavior that you could post publically? https://codetriage.com/example_app |
|
Thanks @schneems - I've raised a Heroku ticket @ https://help.heroku.com/tickets/1064070 with an example failing build linked, and production access granted. Hope that helps. |
|
Got it. I responded over on that channel. If anyone else has an issue number, feel free to link it on GitHub. I've also opened up a PR with my example app running on Heroku CI. I hope to write a failing test that captures one or more of the conditions you all are seeing and incorporate it into the test matrix. That will help me work on a fix and hopefully prevent future regressions. |
|
I've also pushed what I believe may be a fix to my branch 2e98e35. You can try it out by replacing Also, I still am in need of a working reproduction of a failure case to ensure no regressions in the future. |
Added a test for Rails 7 to exercise behavior in #1254. Update the Rails 7 example app to use the released version instead of alpha. Also update the app to be Heroku CI compat app (adds app.json): - sharpstone/rails-jsbundling@34bd25c - sharpstone/rails-jsbundling@a98a4e4 - sharpstone/rails-jsbundling@b4ec664 - sharpstone/rails-jsbundling@1fb48b4 Add CI tests against Rails 7
* Test Rails 7 app against Heroku CI Added a test for Rails 7 to exercise behavior in #1254. Update the Rails 7 example app to use the released version instead of alpha. Also update the app to be Heroku CI compat app (adds app.json): - sharpstone/rails-jsbundling@34bd25c - sharpstone/rails-jsbundling@a98a4e4 - sharpstone/rails-jsbundling@b4ec664 - sharpstone/rails-jsbundling@1fb48b4 Add CI tests against Rails 7 * Specialize Rails7 Database setup In Rails 6.1 the tasks used for database setup in our test pack were deprecated. They were removed in Rails 7 https://edgeguides.rubyonrails.org/7_0_release_notes.html. This commit moves to specialize the tasks for Rails7+ to use `db:schema:load` per deprecation instruction: ``` DEPRECATION WARNING: Using `bin/rails db:schema:load_if_ruby` is deprecated and will be removed in Rails 7.0. Configure the format using `config.active_record.schema_format = :ruby` to use `schema.rb` and run `bin/rails db:schema:load` instead. (called from <main> at /app/bin/rake:4) ``` * v236
|
I've deployed my fix, you can revert back to |
I upgraded to Rails 7 and started getting these errors on the CI environment.
It seems to fail at loading the DB from dump and thus the tables don't exist when rails is initialized and crashed.
The text was updated successfully, but these errors were encountered: