indeedeng / indeedeng/iwf-java-sdk
Provide clear error message instead of Null Pointer Exception(NPE)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
When workflow type, workflowState, RPC are not registered, what are the errors we are thrown today?
Some of them are NPE which is hard to troubleshoot. We should provide clear message that these entities are not registerd, maybe even provide potential reasons (delete or rename), and how to fix them.
Also similarly:
- data attribute
- search attribute
- Signal channel
- InternalChannel
What are the behavior when they are used without proper registered?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how unregistered workflow types, workflowState, RPCs, data attributes, search attributes, Signal channels, and InternalChannel are looked up or used. Reproduce each missing-registration case and define completion as clear errors that identify the missing entity and, where supported, explain likely causes and fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100