feat(amazonq): display transformation history and add ability to resume interrupted jobs #7781

tgodara-aws · 2025-07-28T23:54:39Z

Problem

Users cannot see previous job details (status, project name, job id, etc) and cannot access the final diff patch. Network issues can cause jobs to fail on client side while they continue on the backend, and users have no way to access those artifacts.

Solution

Repurpose the job status table to show most recent 10 jobs run in the last 30 days, including links to final diff patch and summary files. Allow users to retrieve missing artifacts for jobs and to resume incomplete jobs via refresh button.

Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
Your code changes must meet the guidelines in CONTRIBUTING.md.
License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

packages/core/src/codewhisperer/models/constants.ts

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

ntarakad-aws · 2025-07-29T00:05:58Z

packages/core/src/shared/datetime.ts

+    // Convert milliseconds to days (1000ms * 60s * 60min * 24hr)
+    const daysDifference = timeDifference / (1000 * 60 * 60 * 24)
+
+    return daysDifference <= 30


Do we need to explain why 30?

I'll just provide some context in this reply: we decided to only show users jobs from up to 30 days ago because on our backend we only store jobs and artifacts for up to 30 days. This way we align with that storage policy.

ntarakad-aws · 2025-07-29T00:09:39Z

packages/core/src/amazonqGumby/activation.ts

    void setContext('gumby.wasQCodeTransformationUsed', false)

-    const transformationHubViewProvider = new TransformationHubViewProvider()
+    const transformationHubViewProvider = TransformationHubViewProvider.instance


Can we just explain this for context?

Using TransformationHubViewProvider.instance here to construct the instance implements the singleton pattern and ensures that only one instance exists throughout. That way, when TransformationHubViewProvider.instance is referenced in different parts of the code, we get the same instance every time. I was having issues with accessing the instance with the way it was constructed previously since there seemed to be two instances that existed at the same time.

ntarakad-aws · 2025-07-29T00:12:31Z

packages/core/src/codewhisperer/commands/startTransformByQ.ts

        transformByQState.setPolledJobStatus('FAILED')
        // jobFailureErrorNotification should always be defined here
-        const displayedErrorMessage =
-            transformByQState.getJobFailureErrorNotification() ?? CodeWhispererConstants.failedToCompleteJobNotification


Can we just add some context to the PR why we are getting rid of these so reviewers are aware?

We decided to remove the stopJob() call because with the introduction of the refresh functionality, users can actually resume their jobs within 12 hours. This call was initially added so that jobs that were interrupted on client side would not just run till they time out on the backend. However, with this feature, since users can now continue their jobs, stopping the job on the backend would prevent users from taking this action.

ntarakad-aws · 2025-07-29T03:40:15Z

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

-                    : this.getTableMarkup(sessionJobHistory[transformByQState.getJobId()])
+                    : this.getTableMarkup(jobsToDisplay)
            }
+            <script>


Just curious, are there other examples of us returning script tags within HTML?

There are a few that I can see: showPlanProgress() method in TransformationHubViewProvider.ts, getWebviewContent() method in webViewPanel.ts -- this one uses it similarly to how I have done so here --, and getHtml() method in referenceLogViewProvider.ts

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

dhasani23 · 2025-07-29T21:21:56Z

packages/core/src/codewhisperer/commands/startTransformByQ.ts

        })
+
+        // create local history folder(s) and store metadata
+        const jobHistoryPath = path.join(os.homedir(), '.aws', 'transform', transformByQState.getProjectName(), jobId)


Is this the same folder as where the QCT CLI stores artifacts?

No, the CLI stores artifacts in .aws/qcodetransform/ (specifically within the transformation_projects subdirectory)

dhasani23 · 2025-07-29T21:25:33Z

packages/core/src/codewhisperer/commands/startTransformByQ.ts

+    if (
+        transformByQState.isSucceeded() ||
+        transformByQState.isPartiallySucceeded() ||
+        transformByQState.isCancelled()


Instead of checking the job status to delete these files, just check if fs.existsSync() to determine whether or not to delete the files

The reason I was thinking of using status as the check here is because if the job fails or is incomplete on client side, we do not want to delete the metadata file and zip copy since those are needed to resume the job. Is there a better way to do this check?

Sidenote: I will be moving the original zip deletion (lines 757-760) outside of this if clause since that can be deleted regardless

packages/core/src/codewhisperer/commands/startTransformByQ.ts

packages/core/src/codewhisperer/models/model.ts

dhasani23 · 2025-07-29T23:02:05Z

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

+                                        ? 'disabled title="A job is ongoing"'
+                                        : job.status === 'CANCELLED' ||
+                                            job.status === 'STOPPED' ||
+                                            job.status === 'FAILED_BE'


How is FAILED_BE managed? We already have FAILED so wondering if we need this

I added FAILED_BE for the case where a job actually fails on the backend, though users will still only see it show up as FAILED in the Transformation Hub. In such a case we do not want users to be able to refresh that job because there are no updates for it on the backend. I had to add this local status because when checking for any jobs that may need to be resumed, I search for a status of FAILED in the local transformation history file (since this is the status that shows up on the frontend in the case of a client-side failure, like a network disruption). We don't want to mislead users into thinking an actual failed job is still refreshable or "in progress," so this FAILED_BE status helps differentiate that. But it's only used in the context of the history file/table.

Perhaps there is a better way I could've done this?

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

dhasani23 · 2025-07-29T23:03:37Z

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

+            // artifacts should be available to download
+            jobHistoryPath = await this.retrieveArtifacts(jobId, projectName)
+
+            // delete metadata and zipped code files, if they exist


what happens if they don't exist?

Nothing happens; since I'm using { force: true } here, no error is thrown even if the files don't exist

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts

packages/core/src/amazonqGumby/chat/controller/controller.ts

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts

…tches locally; write history details to local log file

…diff patch if available), also added isWithin30Days util func for future use

…build log; open diff patch and summary directly in VSCode

…less often, limit table to 10 rows and validate dates

… transform initiated; create unit tests for job history feature

…issue, etc.

laileni-aws · 2025-08-04T18:34:55Z

/retryBuilds

amazon-inspector-ohio · 2025-08-04T21:51:26Z

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

amazon-inspector-ohio · 2025-08-04T21:51:57Z

✅ I finished the code review, and didn't find any security or code quality issues.

amazon-inspector-ohio · 2025-08-05T00:14:17Z

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

amazon-inspector-ohio · 2025-08-05T00:14:48Z

✅ I finished the code review, and didn't find any security or code quality issues.

chungjac · 2025-08-05T00:14:53Z

/retryBuilds

ntarakad-aws reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/models/constants.ts Show resolved Hide resolved

ntarakad-aws reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

ntarakad-aws reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

ntarakad-aws reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Show resolved Hide resolved

ntarakad-aws reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/commands/startTransformByQ.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/models/model.ts Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

dhasani23 reviewed Jul 29, 2025

View reviewed changes

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts Show resolved Hide resolved

tgodara-aws force-pushed the feature/transformation-history-table branch from 8e20bee to 1609879 Compare July 31, 2025 04:43

dhasani23 reviewed Aug 1, 2025

View reviewed changes

packages/core/src/amazonqGumby/chat/controller/controller.ts Outdated Show resolved Hide resolved

tgodara-aws force-pushed the feature/transformation-history-table branch 2 times, most recently from d9ccc41 to ad8ef31 Compare August 1, 2025 20:50

tgodara-aws marked this pull request as ready for review August 1, 2025 21:15

tgodara-aws requested a review from a team as a code owner August 1, 2025 21:15

laileni-aws reviewed Aug 1, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

laileni-aws reviewed Aug 1, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

laileni-aws reviewed Aug 1, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

tgodara-aws force-pushed the feature/transformation-history-table branch from ad8ef31 to a50281b Compare August 1, 2025 23:48

laileni-aws reviewed Aug 2, 2025

View reviewed changes

packages/core/src/codewhisperer/service/transformByQ/transformationHubViewProvider.ts Outdated Show resolved Hide resolved

laileni-aws reviewed Aug 2, 2025

View reviewed changes

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts Show resolved Hide resolved

laileni-aws reviewed Aug 2, 2025

View reviewed changes

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts Outdated Show resolved Hide resolved

laileni-aws reviewed Aug 2, 2025

View reviewed changes

packages/core/src/test/amazonqGumby/transformationJobHistory.test.ts Show resolved Hide resolved

laileni-aws previously approved these changes Aug 2, 2025

View reviewed changes

tgodara-aws dismissed laileni-aws’s stale review via 0b29f26 August 4, 2025 16:18

tgodara-aws force-pushed the feature/transformation-history-table branch from 6689e8f to 0b29f26 Compare August 4, 2025 16:18

dhasani23 approved these changes Aug 4, 2025

View reviewed changes

tgodara-aws added 7 commits August 4, 2025 10:55

modify job status table to show transformation history; store diff pa…

ab1d404

…tches locally; write history details to local log file

Refresh button original functionalilty (updates status and downloads …

c86fa10

…diff patch if available), also added isWithin30Days util func for future use

Modify refresh button functionality to handle CSB; store summary and …

941d18e

…build log; open diff patch and summary directly in VSCode

Change job history table file reading logic - store array, read file …

0bb9102

…less often, limit table to 10 rows and validate dates

add more messaging during refresh and check for in progress jobs when…

51d749a

… transform initiated; create unit tests for job history feature

Minor fixes: move strings to constants file, fix circular dependency …

deadc6d

…issue, etc.

PR fixes: refactoring, syntax changes

31bd370

tgodara-aws force-pushed the feature/transformation-history-table branch from 0b29f26 to 31bd370 Compare August 4, 2025 18:00

laileni-aws approved these changes Aug 4, 2025

View reviewed changes

laileni-aws closed this Aug 4, 2025

laileni-aws reopened this Aug 4, 2025

Merge branch 'master' into feature/transformation-history-table

caa800d

chungjac closed this Aug 5, 2025

chungjac reopened this Aug 5, 2025

Merge branch 'master' into feature/transformation-history-table

eaa61b9

chungjac merged commit 712d978 into aws:master Aug 5, 2025
30 of 31 checks passed

feat(amazonq): display transformation history and add ability to resume interrupted jobs #7781

feat(amazonq): display transformation history and add ability to resume interrupted jobs #7781

Uh oh!

Conversation

tgodara-aws commented Jul 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

laileni-aws commented Aug 4, 2025

Uh oh!

amazon-inspector-ohio bot commented Aug 4, 2025

Uh oh!

amazon-inspector-ohio bot commented Aug 4, 2025

Uh oh!

amazon-inspector-ohio bot commented Aug 5, 2025

Uh oh!

amazon-inspector-ohio bot commented Aug 5, 2025

Uh oh!

chungjac commented Aug 5, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

tgodara-aws commented Jul 28, 2025 •

edited

Loading