Update. The solution is lower from a few years ago and applies when Rail 2 was new and plugins were still common. Now that the use of the gemstone is better and the standard solution, the answer below is no longer applicable to newer applications; instead, the solution that @TALlama posted is working. I leave this answer here because it is a working solution if your application is outdated and still uses the plugin.
You can modify the rails_xss plugin to remove this message. The offensive part of the plugin is in "/plugins/rails_xss/lib/rails_xss/erubis.rb". At the very top of the file you need:
require 'erubis/helpers/rails_helper'
Modify this to simply redirect standard output to dummy IO before requesting and restore standard output when you are done:
stdout_original, $stdout = $stdout, StringIO.new require 'erubis/helpers/rails_helper' $stdout = stdout_original
This is ugly, but it solves the problem in a relatively unobtrusive way. I had a similar problem with the OP, which was supposed to handle the output of the "script / run" process to another process, and erubis flagrantly violated the agreement that rails components / plugins are silent on the stdout front (this is the reason for this). The above solution is what I came across and it works for me.
source share