Yeah, my initial patch was actually for ob-ruby, though, when looking for the change that broke it for the report, I found a change in behaviour of the escaping function and figured that Ruby might not be the only thing broken.
So, instead, I restored the original permissive behaviour of org-babel-script-escape and made a patch of that instead.
Kyle Meyer <kyle@kyleam.com> wrote:
> It seems like org-babel-execute already covers this processing.
s/org-babel-execute/org-babel-execute:ruby/
--
Kyle