Brendon Muir

You could try overriding the `placeholder_will_change!` method so that it raises an error when it's triggered. You could then see a stacktrace of what code triggered the method. There's probably...

I'm not sure if setting a default value for that column is supported from an ideological point of view unless you set it to the maximum or minimum value?

This leaves the actual toolbar laying around collapsed with a slight border. It would be better if the whole thing got hidden?

In my experience of having a similar thing happen (not involving `recurring_select`) it turned out to be to do with mutating a 'constant' in my app. Just a thought :)

Adding the `//` gives me a Bad Gateway response. I've tested that I can get to the IP on that port without puma-dev and it works fine, so the bad...

Figured it out. I needed to be explicit about the scheme, so add `http://` to the front of the `ip:port`.

Just wondering if anyone would be able to help with this?

Hi @schneems, `less-rails` works with Sprockets 3. I'm trying to prepare it for Sprockets 4. I simply changed the `Gemfile` to reference it: ``` gem "sprockets", git: "https://github.com/rails/sprockets.git", branch: "v4.0.0.beta4"...

Here's a link to the gem that works with sprockets 2 and 3 but fails with 4. I'm almost 100% sure the files aren't getting produced at all, and thus...

Just wanted to ping this as we're hoping to get less-rails 4.0.0 released, and adding proper tests for sprockets 4 would be a boon :)