DT-2686 - show last failure stack trace separately in pending activities

[rossedfort]

Description & motivation 💭

We got feedback that the stack trace on pending activity failures was difficult to interpret because it was being shown in a JSON codeblock. This PR moves the stack trace to a separate code block which is formatted correctly.

Screenshots (if applicable) 📸

before	after

Design Considerations 🎨

Testing 🧪

How was this tested 👻

• Manual testing
• E2E tests added
• Unit tests added

Steps for others to test: 🚶🏽‍♂️🚶🏽‍♀️

1. Create an activity that will fail

import { ApplicationFailure } from "@temporalio/common";

const failAfter = (seconds: number) => {
  return new Promise((_, reject) => {
    setTimeout(() => {
      reject();
    }, seconds * 1000);
  })
}

export const pendingFailure = async (): Promise<void> => {
  try {
    await failAfter(5);
  } catch {
    throw new ApplicationFailure('Error', 'unknown', false, ['Foo', 'Bar', 42]);
  }
}

2. Define a workflow that executes this activity - note, do not specify maximumAttempts so the activity can fail endlessly. Also specify a high enough startToCloseTimeout to be able to test

const {
  pendingFailure,
} = proxyActivities<typeof activities>({
  retry: {
    initialInterval: '50 milliseconds',
  },
  startToCloseTimeout: '1 day',
});

3. Run the workflow, view the Pending Activities tab for the resulting workflow execution, and verify changes.

Checklists

Draft Checklist

Merge Checklist

Issue(s) closed

Docs

Any docs updates needed?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
holocene	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 28, 2025 9:33pm