Rake | Android app that uses Firebase ML Kit | Authentication library

Plugins usually are built to extend core classes. Using the generator and following the linked guide at my_plugin/lib/my_plugin/rails_core_ext.rb you have to use class you want to extend.

Your code become

ModuleNotFoundError: Module not found: Error: Can't resolve '@popperjs/core' suggests that you need to install @popperjs/core.

the error undefined method 'needs_migration?' for ActiveRecord::Migrator:Class (NoMethodError) be thrown because the method needs_migration? belongs to ActiveRecord::MigrationContext not ActiveRecord::Migrator

try this

"running" is not associated with anything. You need a while running loop.

the way asset pipeline resolve asset path that it'll look up the fingerprinting of the asset file first (which be generated by the rake task precompile) then map to asset_host (if any), if there's no fingerprinting map to the asset then it'll throw exception, it does not check on your asset_host.

if you don't include the precompiled assets in your docker image, your rails app in docker container can't find asset files since there's no fingerprinting be generated in that container.

so yes, you have to.

however, you can bypass the asset pipeline by add a forward slash before the asset path or add skip_pipeline: true, in your case, you already generate the fingerprinting and push those files to your asset host so you can bypass ,for example the application.css, like this stylesheet_link_tag '/application-{fingerprinting}.css', but obviously it's not the good choice since you need to do this for all files.

It really was as simple as adding in a default_scope with a select:

This issue got solved after doing the following:

• Delete bootsnap cache:

  rm -rf tmp/cache/bootsnap*

This might have solved the issue, but I did also:

• Use ruby 2.7.3
• bundle update bootsnap simplecov Installing bootsnap 1.7.5 (was 1.7.2)

It looks like you have a type column defined. In Rails the type column is used by default for indicating inheritance. If you're not intending on using inheritance then you can rename the column (something like kind is common) or you can overwrite the column name that Rails will use Base.inheritance_column.

I think you may be in a situation where you're using older gems than the documentation expects. For flying-sphinx v1.x, you need to use the flying-sphinx executable instead of the ts:-prefixed rake tasks: heroku run bundle exec flying-sphinx rebuild.

If you upgrade to flying-sphinx v2.x, then you'll be able to use the ts rake tasks on Heroku as well as locally. (Yes, this would have been the ideal behaviour from the get-go, but better late than never!)