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

don't send stack track back for body parse errors when environment is production #3347

Conversation

nwhatt
Copy link
Contributor

@nwhatt nwhatt commented Oct 29, 2015

Not sure what if any tests should be updated for this.

@sgress454
Copy link
Member

Thanks @nwhatt!

@sgress454 sgress454 merged commit 8031cee into balderdashy:master Dec 23, 2015
@RWOverdijk
Copy link
Contributor

You're on fire @sgress454 :) One thing to note, shouldn't it move down 2 lines? Now the error doesn't get logged either.

@sgress454
Copy link
Member

Ah, good call. I thought that was consistent with what we were doing in responses, but looks like we're logging the error there even in production (which makes sense).

sgress454 added a commit that referenced this pull request Dec 23, 2015
… production env (just not sent w/ response)

refs #3347
@RWOverdijk
Copy link
Contributor

:) Still on fire though!

ctartist621 pushed a commit to ctartist621/sails that referenced this pull request Feb 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants