eWaterCycle / eWaterCycle/grpc4bmi

Unwrap server exception

Open
#83 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
5
Forks
5
PR merge metrics
No merged PRs in 30d

Description

At the moment a server exception is wrapped in a client exception with some grpc wrappings as well. It would be nice if the exception on the server was the only thing the user was bothered with.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how server exceptions are wrapped through the gRPC server and client layers; the issue names no files or tests. Done means a user receives the server exception directly, without the client exception or additional gRPC wrapping.

Written by the indexing model from the issue text.

Assessment

Tech stack
grpc, python
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.