Matthew Draper

Unfortunately that'll just send Bundler to find the latest version that had the more open-ended dependency. Best might be to explicitly check the Rails version and no-op in the Railtie?

@lucasmazza it's not a JavaScript string; the current behaviour is correct.

https://github.com/rails/ruby-coffee-script/pull/15 should mean a sufficiently recent (read: from git) pair of sprockets + coffee-script doesn't bother sending the complex data across the boundary at all.

IMO, if you're publishing a well-known URL for a thing, you're better off serving it via the router and a controller. That way you have full control of caching policies,...

I'll try to come back and look into this properly, but for now I can only offer some vague thoughts: - AC::Live spawns a new thread to handle the request,...

Hi! I just tried this out... I clicked More options -> Trigger build, left branch as master, and in custom config I entered: ``` addons: postgresql: "9.4" dist: precise ```...

@iriberri 👌🏻 perfect, thank you!

Yeah, I think I agree there are some semantic questions here. Particularly given the explicitly documented "run-then-sleep-N loop" implementation (as opposed to "run every N"), I think it's reasonable to...

I'm happy to provide information on what Rails needs etc. I've given up on addressing it myself -- all my attempts have been vetoed because they involve providing APIs that...

@jrochkind right, that's exactly what I wanted to do: allows Rails (or any other interested library) to automatically wrap futures when it is necessary to ensure [high-concurrency] safety. The cost...