You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ef82ece
Browse filesBrowse the repository at this point in the historyBrowse files
Fix for removing delay and handshake mode from the codebase (#283)
* Allow for automated call graph generation to keep contexts unique within
StdCallbackContext for replay deduping. Now developers do not need to
provide a name when calling services. There is a unique call graph
context maintained for each service call made. The context is request
aware, so different requests made will have their own independent
context for dedupe
Dedupe identical requests
```java
ProgressEvent<Model, StdCallbackContext> result =
initiator.translateToServiceRequest(m -> createRepository)
.makeServiceCall((r, c) ->
c.injectCredentialsAndInvokeV2(
r, c.client()::createRepository))
.success();
ProgressEvent<Model, StdCallbackContext> result_2 =
// make same request call
initiator.translateToServiceRequest(m -> createRepository)
.makeServiceCall((r, c) ->
c.injectCredentialsAndInvokeV2(
r, c.client()::createRepository))
.success();
assertThat(result).isEqualsTo(result_2);
```
* Prevent ConcurrentModificationExceptions in stabilize calls if they
access the map and attempt to modify it
* - Remove 60s hard coded callback
- Remove handshake mode
- Adding wait strategy that can be changed, defaulting to re-schedules with
no local waits for Lambda binding
- changes unit tests to reflect removal of handshake mode, fixed unit
tests for serialization errors
Co-authored-by: diwakar <diwakar@amazon.com>
0 commit comments