hiero-ledger / hiero-ledger/hiero-consensus-node
TransactionStateLogger uses unstable implementation detail
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
The class `TransactionStateLogger` uses the following conditional when deciding to write some logs:
```
Thread.currentThread().getName().startsWith(HANDLE_THREAD_NAME)
```
This is based on the name of the thread where transactions are handled. This thread is named by the platform, and is likely to change in the future as we continue our migration to the new wiring framework. Platform thread names are not safe to rely on, and should only be used for production logic.
Contributor guide
Research direction
Start by locating the TransactionStateLogger class and the conditional that checks the current thread name. Trace how transaction handling and logging are distinguished, then determine a replacement that does not rely on platform thread names while preserving the intended logging behavior. No specific file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100