-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
NestJS Microservice: response.status is not a function #16051
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
Comments
Hey @vahidvdn! Can you confirm that this issue is caused by the Sentry SDK? If so would you mind sharing a minimal reproduction repo? |
@vahidvdn So the issue is that our exception handler does not handle rpc contexts, you can follow the PR above and once it is released use |
@chargome Sounds good! Thank you. |
For graphql yes, for ws not yet! |
@chargome One more question, my app is a hybrid app. So, I have both http context and rpc context (in this case mqtt). After you released a new version, which filter do I need to use? Does it support such a case? |
@vahidvdn with the change you can then add both filters, as the |
Is there an existing issue for this?
How do you use Sentry?
Self-hosted/on-premise
Which SDK are you using?
@sentry/nestjs
SDK Version
9.2.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
@MessagePattern('yourtopic')
)false
inside the guard (it means rejecting the request)Expected Result
App should be able to continue its job without any error.
Actual Result
I get this error:
The text was updated successfully, but these errors were encountered: