chore: Prevent stack trace exposure in the tck error error response#2437
Conversation
Signed-off-by: Manish Dait <daitmanish88@gmail.com>
Signed-off-by: Manish Dait <daitmanish88@gmail.com>
Signed-off-by: Manish Dait <daitmanish88@gmail.com>
af6b79f to
9cfc080
Compare
WalkthroughUpdated SDK and registry error handling to add method-specific diagnostics and prevent unexpected exception details from appearing in JSON-RPC internal-error responses. ChangesRPC error handling
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: bd60ebbf-8efd-4879-9637-f89a2898fc51
📒 Files selected for processing (2)
tck/errors.pytck/handlers/registry.py
Signed-off-by: Manish Dait <daitmanish88@gmail.com>
0fa3ac4 to
9888edc
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: d104ec66-9e92-4ff1-b542-d297f001481e
📒 Files selected for processing (2)
tck/errors.pytck/handlers/registry.py
Description:
This PR silence error details in JSON-RPC error responses and improve logging for the errors.
Related issue(s):
Fixes #2416
Notes for reviewer:
Checklist