Inconsistent Activity Alias Mapping Behavior Across Multiple Task Queues

[MMN3003]

Expected Behavior

The getActivityAlias function should not be called or should return an appropriate response when invoked for an activity that belongs to a different task queue. It should only provide an alias mapping for activities that are registered within the same task queue context. This behavior ensures that activity alias mapping is confined to the specific task queue where the activity is registered and does not provide an alias for activities in different task queues.

Actual Behavior

Currently, the getActivityAlias function is called for activities regardless of the task queue they belong to. It provides alias mapping even when the activity is invoked from a different task queue context, which may lead to incorrect alias mapping and behavior that does not align with the original task queue registration. This can result in unexpected or incorrect behavior when trying to retrieve alias information for activities that are not associated with the current task queue.

Steps to Reproduce the Problem

1.Create two distinct task queues, let's call them "QueueA" and "QueueB," within your Temporal application.
2.Register an activity with an alias in each of these task queues. For example

// Activity registration in QueueA (workerA) 
worker.RegisterActivityWithOptions(ActivityA, activity.RegisterOptions{Name: "Name"})

  // Activity registration in QueueB (workerB) 
worker.RegisterActivityWithOptions(Name, activity.RegisterOptions{Name: "OtherName"})

3.In your Temporal workflow, initiate an activity invocation from one task queue but specify an activity that belongs to a different task queue. For example, invoke "ActivityA" from "QueueA" with alias name in a workflow that is running in "QueueB."

// workflow with original task queue "QueueB"
activityOptions := &workflow.ActivityOptions{
              ...
  	TaskQueue:  "QueueA",
  	...
  }
  ctx = workflow.WithActivityOptions(ctx, *activityOptions)
  workflow.ExecuteActivity(ctx, "Name", data).Get(ctx, nil)

getActivityAlias in ExecuteActivity returns OtherName as alias!!

• Version: go.temporal.io/sdk v1.25.1
• Platform: linux

[cretz]

Duplicate of #845.

Yes, we use the workflow's registry to lookup activity aliases. We can't really change this behavior without potentially breaking people. So we created #850 for this situation. We recommend you disable aliasing via the DisableRegistrationAliasing option.

[Quinn-With-Two-Ns]

Closing as duplicate of #845