Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workflow page error message #670

Conversation

Assem-Hafez
Copy link
Contributor

Summary

  • Add error message to summary/history/queries page.
  • Handle workflow not found error and omit logs for it

Screenshots

not found
Screenshot 2024-09-19 at 16 54 30

generic error
Screenshot 2024-09-19 at 16 55 10

Assem-Hafez and others added 11 commits September 17, 2024 15:06
* Init commit

* more commit

* Add more changes

* Add tests

* clean up code

* Init queries UI

* Add unit tests

* Fix unsaved merge conflict

* Fix tests and merge conflicts again

* update snapshot

* Fix snapshot

* Reorder some props in tile

* resolve comments

* Fix tests

* Fix tests and make design responsive

* Remove snapshots

* Update tests for tile input
@@ -48,9 +49,9 @@ export default function WorkflowPageHeader({
</StyledLink>
<div className={cls.breadcrumbItemContainer}>
{runId}
<Suspense>
<ReactErrorBoundary fallbackRender={() => null}>
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't a suspense the same thing in this situation?
Also, you should use the ErrorBoundary component we wrote, since it has extras like logging.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is what i though initially but seems like suspense only handles the loading fallback, while errors crashes the whole page.

I wanted to omit logging for it as the error is already logged in the page content.
But Actually i can use the other error boundary and pass omitLogging to it

@@ -19,7 +18,7 @@ export default async function WorkflowPage({ params, children }: Props) {
cluster={decodedParams.cluster}
/>
<WorkflowPageTabs />
<PageSection>{children}</PageSection>
{children}
Copy link
Contributor

Choose a reason for hiding this comment

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

If you're removing PageSection here, we need to add it to every workflow tab. Did you make the change in History?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, also i will be making changes later along with the virtual list to handle use cases like query page expand the whole page

@Assem-Uber Assem-Uber merged commit 932bb51 into uber:release/4.0.0 Sep 20, 2024
6 checks passed
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.

3 participants