rollbar | Go client for Rollbar | Architecture library

I have resolved this issue using some middleware. This will intercept all incoming requests, scan if they are ActiveStorage urls, find the ones with the deprecated combine_options and just return 404 not found. This code will also raise an error is the current environment is development, this way I don't accidentally introduce the deprecated code again.

For those of you who might have the same problem, here's the code.

application.rb

Update:

It looks like it was a problem with my post-Bower configuration (I migrated from Bower --> Yarn) I was able to solve Sprockets errors by adding this line to my assets.rb:

Rails.application.config.assets.paths << Rails.root.join('node_modules')

and by running yarn add for files that Sprockets could not locate.

I also made the following updates to old package names in my `application.rb'

With the help of @jeb I managed to resolve this FIND issue on jenkins by placing the absolute path for (find) in the shell script - initially it was using the windows FIND cmd, so i needed to point to cygwin find cmd

before: for path in $(find dist/renew -name "*.js"); do

and after: for path in $(/usr/bin/find dist/renew -name "*.js"); do

Thaks to all that commented

This seems to be a problem with the virtual box filesystem. I created an issue to composer and hopefully more insight will be gained.

https://github.com/composer/package-versions-deprecated/issues/21

Rollbar configuration was failing because for access token it was expecting a string that was not null/empty. Since I store Rollbar access token in Azure AppService Configuration and appsettings.json did not have access token listed, error was happening. So I added access token to appsettings.json with a dummy non-empty string value. That helps Rollbar to configure itself and not fail.

I just found the reason for this error. In my codebase, I have multiple .pdspec files defined (one per each SDK module). Some of the podspecs were complete and worked for a long time with no changes (except the version bumps). Other podspecs were introduced recently and are work-in-progress.

The error in question was happening while I was trying to either publish or lint the complete podspecs. However, as it appears (after digging into the Ruby scripts mentioned with the error log) that Cocoapods runs the validation step during both lint and publishing of a specific podspec. Part of the validation steps iterates through all .podspec files within the same directory (or maybe even directory tree - ? ). So, in my case, it was discovering the incomplete podspecs and trying to validate them as well (WHY?) and of cause failing with the error.

The error is not helpful at all to troubleshoot the problem as well as log traces reported with it. The only way to find out some helpful hints was to look into code blocks around the Ruby script-lines mentioned in the log and try to reverse engineer what possibly was going on wrong.

I just wanted to share my story and to possibly prevent other people from running into a similar error (a Google search shows a lot of those) and losing days in frustration trying to troubleshoot it.

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.

I'm sure Vue CLI minifies JS output when running build in production mode. It's just using different naming convention (no "min.js")

To tweak file names of JS chunks produced by Vue CLI, you can do the following:

Check the default Webpack config Vue CLI uses by running vue inspect on command line (dev mode) or vue inspect --mode production (production mode)

Look for an output (should be near the beginning of the output). In my project it looks like this:

Dev mode:

Look's like an issue with Django 1.10.x and Python 3.6:

https://bugs.python.org/issue23722 https://github.com/django/django/pull/7653/commits/5a36dbc634f4ebd7ccae8f0a4bab987b478750cb

Options are to downgrade Python to version 3.5 or to update Django to newer release.