-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #3796 upgrade rails_admin gem #3797
Conversation
Hey @Morrism1 - thank you for contributing! Unfortunately, it looks like something went wrong - you should only need to change a handful of files, but this is reporting 500+. Please fix that and re-push |
I did mess up the changes due to the Rspec actions was failing but locally was working, but I reverted the changes now. I think it is all good. 🤦🏽♂️ |
@Morrism1 Yes, we've tracked down the issue to a configuration problem with Docker, but otherwise I'm running the tests myself locally to verify things are good. |
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797.
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797.
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode.
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode.
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use `shell` keyword. `pwd` was returning nothing, so it wasn't able to properly find the config file.
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use [the `shell` keyword][shell]. `pwd` was returning nothing, so it wasn't able to properly find the config file. [shell]: https://stackoverflow.com/a/18137056/372479
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use [the `shell` keyword][shell]. `pwd` was returning nothing, so it wasn't able to properly find the config file. [shell]: https://stackoverflow.com/a/18137056/372479
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use [the `shell` keyword][shell]. `pwd` was returning nothing, so it wasn't able to properly find the config file. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][seg] in Ruby, making builds (and deploys) super flaky. [shell]: https://stackoverflow.com/a/18137056/372479 [seg]: sass/sassc-ruby#207
**What** * Introduce `app/assets/config/manifest.js`. Sprockets was [recently upgraded][upgrade] to version 4, but [it now requires this file][file] to exist in order to determine which files to compile. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][segfault] in Ruby, making builds (and deploys) super flaky. I've already seen it fail a few times working on getting the build passing. [upgrade]: #3797 [file]: https://github.com/rails/sprockets/blob/master/UPGRADING.md#manifestjs [segfault]: sass/sassc-ruby#207
**What** * Introduce `app/assets/config/manifest.js`. Sprockets was [recently upgraded][upgrade] to version 4, but [it now requires this file][file] to exist in order to determine which files to compile. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][segfault] in Ruby, making builds (and deploys) super flaky. I've already seen it fail a few times working on getting the build passing. [upgrade]: #3797 [file]: https://github.com/rails/sprockets/blob/master/UPGRADING.md#manifestjs [segfault]: sass/sassc-ruby#207
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use [the `shell` keyword][shell]. `pwd` was returning nothing, so it wasn't able to properly find the config file. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][seg] in Ruby, making builds (and deploys) super flaky. [shell]: https://stackoverflow.com/a/18137056/372479 [seg]: sass/sassc-ruby#207
**What** * Update the CI configuration for Rubocop to install the same version that is specified in `Gemfile.lock`. I think it might be better to run `bundle` instead of installing `rubocop` directly, but it will be good to set up caching to reduce performance overhead. * Downcase `PWD`. I'm guessing these files were developed on a file system that is not case sensitive. Linux, on the other hand, is. * Introduce `config/manifest.js`. Sprockets throws an error when trying to boot the server. It now requires this file to exist, I believe as of version 4.0. I'm guessing this issue started in #3797. * Disable Rollbar in dev/test mode. * Update CodeClimate in `Makefile` to use [the `shell` keyword][shell]. `pwd` was returning nothing, so it wasn't able to properly find the config file. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][seg] in Ruby, making builds (and deploys) super flaky. [shell]: https://stackoverflow.com/a/18137056/372479 [seg]: sass/sassc-ruby#207
**What** * Introduce `app/assets/config/manifest.js`. Sprockets was [recently upgraded][upgrade] to version 4, but [it now requires this file][file] to exist in order to determine which files to compile. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][segfault] in Ruby, making builds (and deploys) super flaky. I've already seen it fail a few times working on getting the build passing. [upgrade]: #3797 [file]: https://github.com/rails/sprockets/blob/master/UPGRADING.md#manifestjs [segfault]: sass/sassc-ruby#207
**What** * Introduce `app/assets/config/manifest.js`. Sprockets was [recently upgraded][upgrade] to version 4, but [it now requires this file][file] to exist in order to determine which files to compile. * Disable concurrent exports for Sprockets. It has a tendency to [cause segfaults][segfault] in Ruby, making builds (and deploys) super flaky. I've already seen it fail a few times working on getting the build passing. [upgrade]: #3797 [file]: https://github.com/rails/sprockets/blob/master/UPGRADING.md#manifestjs [segfault]: sass/sassc-ruby#207
In your PR did you:
Upgraded Rails_admin gem to ~> 2.0
Fixes Upgrade rails_admin gem #3796 upgrade rails_admin gem
Include a description of the changes?
Mention the issue the PR addresses?
Isolate any changes to gems (meaning that any new, updated, or removed gems and resulting code changes should be in their own PR)?
- Add and/or update specs for your code?