Andrei Zharikov

For anyone having same issue, as I do: use reverse_proxy_options replace_response_host: true, along with other options.

@brendon @tjwallace thanks for asking guys! > Perhaps just as a courtesy, contact the person who introduced this feature and see if they're using sequential_updates? I'm not using it right...

Also, you can add table constraints to raise exception in case of attempt to insert duplicate values. It will act like safety net. And then you will need proper locking...

@stepheneb you can create compound unique index: `CREATE UNIQUE INDEX position_on_parent_idx ON items (parent_id, position)`

> Is there something I should change There are two options on the backend: a) return 204 No content status, that way Ember will not try to parse response body...

So far I use this hack in initializers/active_admin.rb # every resource must use permitted_attributes from Pundit policies ActiveSupport::Notifications.subscribe ActiveAdmin::Resource::RegisterEvent do |_event, resource| resource.dsl.send :permit_params do active_admin_authorization.retrieve_policy(resource_class).permitted_attributes end end

@alfonsocora > Imagine you enable a feature for all of your users and then you figure out it's giving problems to only one user. I don't want to turn everyone...

Same for us. Really want to decrease identical-code threshold only for the Javascript, as we use Ember. Works fine for the backend part on Rails.

Will forward this to the Heroku team, they could probably fix it, thanks.

I have faced the same issue. For somewhat reason, global exclusion pattern didn't help to deal with node_modules. The workaround is to add explicit paths for duplication engine: ``` version:...