NameError: uninitialized constant error during rake assets:precompile using doorkeeper 5.6.3

[denisahearn]

NameError: uninitialized constant error during rake assets:precompile using doorkeeper 5.6.3

[nbulaj]

Hey @denisahearn

Do you still have an issue when upgrading to Doorkeeper 5.6.6 ?

[denisahearn]

@nbulaj Yes, the same issue happens with doorkeeper 5.6.6. In fact that's the version we tried upgrading to yesterday when we experienced the issue. I isolated 5.6.3 as the version that introduced the issue.

[nbulaj]

Could be related to changes in config evaluation, but it's always so hard to debug such things unfortunately
https://github.com/doorkeeper-gem/doorkeeper/pull/1627/files

[AmShaegar13]

Hey @nbulaj

I ran into a similar problem with assets:precompile and doorkeeper. I run precompile in a CI context where there is no database configuration available so it fails when it tries to access certain environment variables in config/database.yml which shouldn't be loaded at all. This is called by the same lines in doorkeeper like for @denisahearn.

To me it looks like orm hooks are run too early and we need to lazy load here as well because access_token_class.constantize in lib/doorkeeper/config.rb:434 loads ActiveRecord::Base too early. I tried to do so by wrapping it like so lib/doorkeeper/engine.rb:23:

    config.to_prepare do
      ActiveSupport.on_load(:active_record) do
        Doorkeeper.run_orm_hooks
      end
    end

At least this fixed the problem for me while keeping everything else functional. However, I am not an expert regarding Rails internals or doorkeeper. I am using doorkeeper for the first time here.

Maybe this helps you isolate or even fixes the problem. :)