Chetan GowdaandGitHub 5358f6f549 Save the heartbeating worker identity in the activity info (#5586) ...

## What changed?
<!-- Describe what has changed in this PR -->
On an incoming activity task heartbeat, we now save the identity of the
worker sending the heartbeat in the `retry_last_worker_identity` field
of activity info

## Why?
<!-- Tell your future self why have you made these changes -->
Sometimes the worker identity is missing in the activity info. This
change fixes the issue by updating the activity info with the worker
identify from the heartbeat requests. It assumes that the worker sending
the heartbeat is the one working on the activity task.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->
Working on tests.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

2024-03-27 12:49:25 -07:00

..

api.go

Save the heartbeating worker identity in the activity info (#5586)

2024-03-27 12:49:25 -07:00