Skip to content

[BR-2136]: surface failed uploads in the retry modal and task logger - #2076

Open
terrerox wants to merge 1 commit into
feat/folder-upload-partial-failure-retryfrom
feat/failed-uploads-retry-ui
Open

[BR-2136]: surface failed uploads in the retry modal and task logger#2076
terrerox wants to merge 1 commit into
feat/folder-upload-partial-failure-retryfrom
feat/failed-uploads-retry-ui

Conversation

@terrerox

Copy link
Copy Markdown
Contributor

Description

Retry entries are grouped under their parent folder task via relatedTaskId, and non-retryable files show a "Not allowed" label (added to all locales) instead of a retry button.

Also normalizes the two RetryableTask param shapes in TaskToRetryItem behind a getDisplayData helper (file names now display with their extension), tightens the retry modal row padding, and adds sizeClassName/iconSize props to TaskLoggerButton.

Related Issues

Related Pull Requests

Checklist

  • Changes have been tested locally.
  • Unit tests have been written or updated as necessary.
  • The code adheres to the repository's coding standards.
  • Relevant documentation has been added or updated.
  • No new warnings or errors have been introduced.
  • SonarCloud issues have been reviewed and addressed.
  • QA Passed

Testing Process

Additional Notes

Retry entries are grouped under their parent folder task via
relatedTaskId, and non-retryable files show a "Not allowed" label
(added to all locales) instead of a retry button.

Also normalizes the two RetryableTask param shapes in TaskToRetryItem
behind a getDisplayData helper (file names now display with their
extension), tightens the retry modal row padding, and adds
sizeClassName/iconSize props to TaskLoggerButton.
@terrerox terrerox self-assigned this Jul 28, 2026
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying drive-web with  Cloudflare Pages  Cloudflare Pages

Latest commit: af24b14
Status: ✅  Deploy successful!
Preview URL: https://f7a215bf.drive-web.pages.dev
Branch Preview URL: https://feat-failed-uploads-retry-ui.drive-web.pages.dev

View logs

@sonarqubecloud

Copy link
Copy Markdown

Comment on lines +87 to +90
return haveWarnings ? (
<TaskLoggerButton onClick={infoAction} Icon={InfoIcon} iconSize={20} />
) : (
<TaskLoggerButton onClick={magnifyingAction} Icon={MagnifyingGlass} />

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there’s any file with error, do we no longer display the magnifying glass icon to navigate to the folder?

Comment on lines +19 to +25
const getDisplayData = (params: RetryableTask['params']): DisplayData => ({
name: params?.filecontent?.name ?? params.plainName ?? params.name,
type: params?.filecontent?.type ?? params.type,
size: params?.filecontent?.size ?? params.size,
modifiedAt: params?.filecontent?.content.lastModified ?? params.updatedAt,
isFolder: Boolean(params?.isFolder),
});

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand that this depends on whether it’s an upload or a download, as the data arrives with the fields structured differently, but this needs to be reorganised more effectively, as looking at it like this, we can’t tell why there are so many fallback options for the same field.
Looking at this code alone, it’s impossible to tell why, for ‘name’, it checks ‘filecontent.name’, then uses ‘params.plainname’ as a fallback, and then ‘params.name’.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants