aws / aws/aws-durable-execution-sdk-java
[Bug]: fix behavior differences in local runner
- Dominant language
- Java
- Stars
- 28
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 47
Description
### Expected Behavior
The behavior of generating responses and history events in local runner is same as the actual backend.
### Actual Behavior
The behavior of generating responses and history events in local runner is different from the actual backend.
For example,
- attempt always starts with 1 while in the real backend attempt starts with 0 in STARTED and 1 in the other statuses.
- attempt gets plus 1 when switching from READY to STARTED (should keep same)
### Steps to Reproduce
NA
### SDK Version
1.0.0
### Java Version
17
### Is this a regression?
No
### Last Working Version
_No response_
### Additional Context
_No response_
Contributor guide
Research direction
Start with the local runner's response and history-event generation and compare it with the actual backend behavior described in the issue. Check attempt values when entering STARTED, in later statuses, and when switching from READY to STARTED; done means the local runner matches those backend semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100