ERROR: ActiveRecord::NotNullViolation: PG::NotNullViolation: ERROR: null value in column "service_name" violates not-null constraint

[Suraj-Chandola]

Getting
ERROR: ActiveRecord::NotNullViolation: PG::NotNullViolation: ERROR: null value in column "service_name" violates not-null constraint
When calling .attach(io: File.open('/path/to/file'), filename: 'file.pdf') from Worker
Worker is called using .perform_async

CODE:

class User < ApplicationRecord
  has_one_attached :avatar
end

user.avatar.attach(io: File.open('/path/to/file'), filename: 'file.pdf')

user.avatar.attach is called from sidekiq worker

Getting
ERROR: ActiveRecord::NotNullViolation: PG::NotNullViolation: ERROR: null value in column "service_name" violates not-null constraint

System configuration

Rails version: 6.1.4:

Ruby version: 2.5.0:

[hahmed]

I think this is an issue with how your config/storage.yml file is setup, could you have a look at the docs https://guides.rubyonrails.org/active_storage_overview.html#setup and see if that helps?

It looks your config is has something missing so when you attach a file the service_name is missing when the record is saved -- causing the error you are seeing.

[indrajithi]

Hello @hahmed. I work with @Suraj-Chandola and we were pairing to solve this issue. Here are some observations.

• This problem started occurring when we upgraded the gems.
• The problem happens only on the staging server. This works normally on our local.
• We have a method called export! which when called on rails console directly, does the export to GCS and emails us the link.
• When we call perform_async from console, the sidekick job fails and we can see ERROR: null value in column "service_name" violates not-null constraint error on the logs. perform method in the worker calls job.export! (which works when called directly but not through worker).
• All jobs using sidekiq passes when there are no active storage attachments to make. All the jobs with active storage attachments fails.
• Attachments when done without sidekiq works.

LMK if you need any other information. Thanks!

gem 'redis', '~> 4.4.0'
gem 'rails', '~> 6.1.4'
ruby '2.5.0'
gem 'sidekiq', '~> 6.2.2'

[hahmed]

@indrajithi can you reproduce the issue using the bug template https://github.com/rails/rails/tree/main/guides/bug_report_templates or upload a repo to GitHub -- that will help debug the issue 👍

[rails-bot]

This issue has been automatically closed because there has been no follow-up response from the original author. We currently don't have enough information in order to take action. Please reach out if you have any additional information that will help us move this issue forward.

[Rosie-Brigham]

@hahmed did you solve this issue? I am experiencing the same error

[hahmed]

@Rosie-Brigham I'm not seeing the issue reported by the OP.

Any chance you could reproduce using https://github.com/rails/rails/blob/main/guides/bug_report_templates/active_storage_gem.rb or upload a repo that demonstrates the issue, that will really help in debugging the issue 🙂

[Rosie-Brigham]

@hahmed this is no longer a blocker for me and I wish I could remember why - I think it was because my storage.yml was incorrect - I'd copied over a commit that changed the config by mistake from another repo.

[troelskn]

For anyone arriving here, trying to upgrade ancient versions of Rails. I ran into this issue when running tests and the cause was a fixture, which - for some reason - didn't have the column service_name filled in.