Closed Overload119 closed 8 years ago
This was working fine yesterday, and the Gemfile.lock hasn't been touched. It could be an asset change, but still doesn't make sense to me.
Okay, so I added
require "byebug"
byebug
To the conflicting line in the Gem, and it appears a demon has done something terrible to the asset file. Still investigating...
Unfortunately this is some transient error.
The culprit was a file that has been unchanged for years in the vendors/
The file (probably not important) was code for Chosen.JS.
I added a one-line comment to the file, "// testing" then tried recompiling and it worked. Then I removed what I added, saved, and compiled and it worked again.
So I essentially didn't do anything but resave the file (with no net changes) and the assets compiled again.
Logs
Gemfile.lock