Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Communication wrappers can be initialized with closed uTransport

Open
#172 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
networking

Research direction

Start with InMemortyRpcClient's constructor and the uTransport.registerListener call described in the issue. Determine whether closed transports should be accepted and notified on state changes or rejected during wrapper creation; done requires an agreed lifecycle behavior and corresponding validation.

Written by the indexing model from the issue text.

Description

For example InMemortyRpcClient can be created with a closed uTransport instance. It calls uTransport.registerListener in constructor which fails and never retried.
Do we want to allow creation of communication wrappers passing not opened uTransport instance? Then we need a callback interface from uTransport to notify its state changes.
Or we must fail wrapper creation with a closed transport as an argument. But then wrapper reference cannot be initialized ahead (before transport is connected) and the code should check for null before using it.

Dominant language
Java
Stars
14
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-uprotocol/up-java

All issues in eclipse-uprotocol/up-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.