---
# System prepended metadata

title: Rails 6 Bugs

---

# Rails 6 Bugs

* NAM watermarking (ActiveStorage::IntegrityError)
    * [sentry](https://sentry.io/organizations/power-home-remodeling-group/issues/3644446224/?project=1240006)
    * [other sentry](https://sentry.io/organizations/power-home-remodeling-group/issues/3644041456/?environment=production&project=1240006&query=is%3Aunresolved&statsPeriod=24h)
    * (we also think it was breaking [appointment issuing](https://gist.github.com/wadewinningham/5a1e1b1d24ec53c67926db8da551c3f5))
    * The fix is in three parts:

    1. Track whether the image was watermarked in a way that persists. PR: https://github.com/powerhome/nitro-web/pull/27678
    2. (optional) manually backfill NAMs so they are marked as watermarked. It could be something like [this](https://github.com/powerhome/nitro-web/pull/27673/files#diff-bcdbc2df9c5f62e20a1178bd7b99784af518bd2190158de903d7d52ced97bf53R5)
    3. Background the watermarking job and add the safety to ensure an already-watermarked image doesn't get re-queued. PR: https://github.com/powerhome/nitro-web/pull/27673

* Unknown ActiveStorage::IntegrityError 1
    * [sentry](https://sentry.io/organizations/power-home-remodeling-group/issues/3644526434/?environment=production&project=1240006&query=is%3Aunresolved&statsPeriod=24h)
    * Sentry reported it happening to only three users:
        * DJ Johnson (Installation Manager)
        * Jimmy Cancel (Warranty Service)
        * Cody Brown (Samurai)
    * Places we know that were affected:
        * Support Tickets
            * https://nitro.powerhrg.com/support/tickets/453963
            * I linked these back to three different support tickets, all of them older (Jan, Feb, and June). These attachments are all currently working in production. I tried to re-create this issue on my local version of R6, but any attachments for support tickets I created seemed to be cleanly effective.
        * Media Library
            * https://nitro.powerhrg.com/media/documents?documentsfilter%5Bactive%5D=0&documentsfilter%5Bactive_cond%5D=eq&documentsfilter%5Bcategories%5D=&documentsfilter%5Bcategories_cond%5D=eq&documentsfilter%5Bterritory%5D=&documentsfilter%5Bterritory_cond%5D=eq&documentsfilter%5Bupload_date_from%5D=&documentsfilter%5Bupload_date_from_cond%5D=ge&documentsfilter%5Bupload_date_to%5D=&documentsfilter%5Bupload_date_to_cond%5D=le&page=5
            * I was able to replicate this issue in both my local R6 env and in the R5-based QA. I think this is a preexisting bug/issue with the MediaLibrary that's raising a different error since the upgrade

* NitroErrors::DeprecationError
    * This isn't something we want to stop someone working in production over, but we do want to report to Sentry. PR: https://github.com/powerhome/nitro-web/pull/27671/

* ActiveModel::RangeError
    * This bug happened to come from ransack, and the monkey-patches offered are Rails-version-specific. PR is here, but will be cherry-picked to the Rails 6 Exploration branch: https://github.com/powerhome/nitro-web/pull/27669

* Apply Changes to Setup Script

* Apply Changes on merged/reverted Rails 6 branch
    * forwardable: https://github.com/powerhome/nitro-web/pull/27699