# Rubocop performance gem warning
**URL:** https://meta.discourse.org/t/rubocop-performance-gem-warning/116629
**Category:** Support
**Created:** [May 1, 2019, 11:32pm UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629 "2019-05-01T23:32:26Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 1, 2019, 11:32pm UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/1 "2019-05-01T23:32:26Z")
Hey, @tgxworld, I’m guessing that this is on your radar, but rebuilds include this:
```plaintext
Post-install message from rubocop:
Performance Cops will be removed from RuboCop 0.68. Use rubocop-performance gem instead.
Put this in your Gemfile.
gem 'rubocop-performance'
```
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [May 1, 2019, 11:37pm UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/2 "2019-05-01T23:37:45Z")
Do you see that in **rebuilds**? Last I checked rubocop was only in development/test environments.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 1, 2019, 11:39pm UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/3 "2019-05-01T23:39:27Z")
Yup. I saw that message in a rebuild on a [Standard install](https://meta.discourse.org/t/142537?silent=true) that I did today. I started noticing it a few days ago.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [May 2, 2019, 1:05am UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/4 "2019-05-02T01:05:44Z")
Where are you seeing the message? I looked through the code paths where we run `bundle install` and those paths are correctly including `--without test --without development`.
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [May 2, 2019, 1:34am UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/5 "2019-05-02T01:34:03Z")
I’ve seen it as well, this is what I’m seeing:
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [May 2, 2019, 2:24am UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/6 "2019-05-02T02:24:33Z")
Ouch this was a bad one. We’ve been installing test gems in production since forever.
Fixed in
[https://github.com/discourse/discourse\_docker/commit/b8866fb9bbda41b643dd1acf9798b230b75ddb62](https://github.com/discourse/discourse_docker/commit/b8866fb9bbda41b643dd1acf9798b230b75ddb62)
[https://github.com/discourse/docker\_manager/commit/79aa85a88a15836ec881bb91c321978434c2f85a](https://github.com/discourse/docker_manager/commit/79aa85a88a15836ec881bb91c321978434c2f85a)
We’re releasing a new base image soon to fix this issue once you rebuild.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [May 2, 2019, 3:31am UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/7 "2019-05-02T03:31:16Z")
> [@tgxworld](#):
>
> We’re releasing a new base image soon to fix this issue once you rebuild.
Wow! I found a real problem!
Here’s a question that I should know the answer to, but don’t.
What do I watch to know when there is a new image that requires a command line upgrade?
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [June 1, 2019, 3:46am UTC](https://meta.discourse.org/t/rubocop-performance-gem-warning/116629/8 "2019-06-01T03:46:14Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.