Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stdout printing in when requiring xray alongside rails #2

Open
sconover opened this issue Jan 15, 2010 · 1 comment
Open

stdout printing in when requiring xray alongside rails #2

sconover opened this issue Jan 15, 2010 · 1 comment

Comments

@sconover
Copy link

Hi,

We have some situations where we're sensitive to what gets printed to stdout. When xray is required in an environment that includes rails, the following gets printed out to the console:

XRay: Enabling Rails Controller Tracing
XRay: Enabling Rails DB Tracing

As a temporary measure we're going to pull the xray code in to our project and delete these messages. We would appreciate it if there were some way of turning them off...

...and we aren't using the rails features of xray anyway. It would also work - and perhaps be preferable from our POV - if we could require xray in an environment that uses rails but turn off/not automatically include the xray-rails functionality.

Xray has been enormously useful to us over time (kill -3) - thank you for it.

-Steve

@ph7
Copy link
Owner

ph7 commented Jan 19, 2010

Hi Steve,

Thanks for letting me know. I will push a new version with no stdout output.

If you are not using the Rails instrumentation though, you already have an easy way out in the meantime: In your code, replace your 'require "xray"' with 'require "xray/thread_dump_signal_handler"', that should do the trick!

Cheers,

  • Philippe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants