New install error: relation "heya_steps" does not exist

[acallaghan]

Hey there, I've been integrating Heya with our app, and came across this issue. I have added the gem and run the installation commands and migration. I then setup my first campaign.

However, when I run the campaign scheduling rake task, I get this error:

$ rails heya:scheduler 
rails aborted!
ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  relation "heya_steps" does not exist
LINE 1: ...M "public"."heya_campaign_memberships" INNER JOIN "heya_step...
                                                             ^
Caused by:
PG::UndefinedTable: ERROR:  relation "heya_steps" does not exist
LINE 1: ...M "public"."heya_campaign_memberships" INNER JOIN "heya_step...
                                                             ^

Tasks: TOP => heya:scheduler
(See full trace by running task with --trace)

A --trace led me to the lines:

lib/heya/campaigns/scheduler.rb:21:in `run'
lib/tasks/heya_tasks.rake:6:in `block (2 levels) in <main>'

It looks like these files are referring to a table called heya_steps, and referenced in a few places like:

scope :with_steps, -> {
  joins(
    %(INNER JOIN "heya_steps" ON "heya_steps".gid = "heya_campaign_memberships".step_gid)
  )
}

This table isn't in the generator for the installation migration, so not sure where this should come from? Any ideas would be welcome!

I'm using Rails 6.1, Ruby 3.0.1 and postrges 13.3

Thanks in advance,
Andy

[joshuap]

@acallaghan hey thanks for the bug report. We use some magic to make the heya_steps table available in heya queries (I try to avoid this type of thing as much as possible but it's part of what makes Heya's Ruby configuration approach work):

https://github.com/honeybadger-io/heya/blob/master/lib/heya/active_record_extension.rb

Can you check to see if that extension is being loaded? You can use bundle open heya if you want to add some debugging output. This library is tested with Rails 6.1 and Ruby 2.6. I'll bump CI to Ruby 3 to see if there are any issues there. It's possible there is a bug in the extension that is not recognizing the query to heya_campaign_memberships or something.

[acallaghan]

Ah, it could be that I'm using the Apartment gem for multi-tenant schemas, I think the two are conflicting - the "public"."heya_campaign_memberships" table in the public schema, but the "heya_steps" table is being defined without a schema. I think this is it anyway.

I might come back to this gem once I've removed Apartment, as I'm pretty sure that's the cause

Thanks anyway

[kimili]

Hi @joshuap! Just a heads up on this old issue. It looks like if you try to set up campaigns in subdirectories of the app/campaigns folder, you'll hit this issue. Not sure if that's something worth investigating, or at least make a note of in the docs.

[joshuap]

Hi @joshuap! Just a heads up on this old issue. It looks like if you try to set up campaigns in subdirectories of the app/campaigns folder, you'll hit this issue. Not sure if that's something worth investigating, or at least make a note of in the docs.

@kimili thanks! I created a new issue to remind myself to investigate this when I have the time. 😁

#264