refactor(ui): Remove V1 UI (round 2) #15147

asikowitz · 2025-10-29T23:41:53Z

Initially removed the useIsThemeV2 hook. Then, repeatedly called:

npx knip --fix --allow-remove-files
yarn run eslint . --ext .ts,.tsx --quiet -f json --rule "{@typescript-eslint/no-unused-vars: error}" --output-file out.json
cat out.json | npx remove-unused-vars

to remove unnecessary exports / files and delete those unused variables.

Also deleted all tests in V1 directories so that this process would work better.

alwaysmeticulous · 2025-10-29T23:47:54Z

🔴 Meticulous spotted visual differences in 1107 of 1109 screens tested: view and approve differences detected.

Meticulous evaluated ~9 hours of user flows against your PR.

_{Last updated for commit 4d73b92. This comment will update as new commits are pushed.}

codecov · 2025-10-29T23:49:29Z

Bundle Report

Changes will decrease total bundle size by 969.86kB (-3.39%) ⬇️. This is within the configured threshold ✅

Detailed changes

Bundle name	Size	Change
datahub-react-web-esm	27.61MB	-969.86kB (-3.39%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: datahub-react-web-esm

Assets Changed:

Asset Name	Size Change	Total Size	Change (%)
`assets/index-*.js`	-952.92kB	18.0MB	-5.03%
`assets/index-*.css`	-11.51kB	597.94kB	-1.89%
~~*`assets/Globe-.svg`*~~ (Deleted)*	-5.43kB	0 bytes	-100.0% 🗑️

Files in assets/index-*.js:

./src/app/auth/ResetCredentials.tsx → Total Size: 6.06kB
./src/app/analytics/plugin/mixpanel.ts → Total Size: 337 bytes
./src/CustomThemeProvider.tsx → Total Size: 489 bytes
./src/app/auth/SignUp.tsx → Total Size: 8.93kB
./src/app/applications/CreateNewApplicationModal/ApplicationDetailsSection.tsx → Total Size: 980 bytes
./src/app/browse/BrowseResultCard.tsx → Total Size: 1.46kB
./src/app/auth/LogIn.tsx → Total Size: 5.44kB
./src/app/analyticsDashboard/components/AnalyticsPage.tsx → Total Size: 6.59kB
./src/app/businessAttribute/businessAttributeUtils.ts → Total Size: 736 bytes
./src/app/SearchRoutes.tsx → Total Size: 4.57kB
./src/app/context/userContext.tsx → Total Size: 607 bytes
./src/app/ProtectedRoutes.tsx → Total Size: 1.5kB
./src/app/analytics/event.ts → Total Size: 13.95kB

codecov · 2025-10-29T23:59:43Z

❌ 92 Tests Failed:

Tests completed	Failed	Passed	Skipped
5127	92	5035	32

View the top 3 failed test(s) by shortest run time

create announcement and link post "before each" hook for "cypress/e2e/settings/homePagePost.js"::cypress/e2e/settings/homePagePost.j

Stack Traces | 0.224s run time

2025-10-30T00:17:27.916Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `create announcement and lin...`

glossaryTerm "before each" hook for "cypress/e2e/glossary/glossaryTerm.js"::cypress/e2e/glossary/glossaryTerm.j

Stack Traces | 0.232s run time

2025-10-29T23:57:11.979Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `glossaryTerm`

Verify nested domains test functionalities "before each" hook for "cypress/e2e/domainsV2/v2_nested_domains.js"::cypress/e2e/domainsV2/v2_nested_domains.j

Stack Traces | 0.236s run time

2025-10-29T23:57:57.206Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Verify nested domains test ...`

task runs cypress/e2e/task_runV2/v2_task_runs.js::cypress/e2e/task_runV2/v2_task_runs.js

Stack Traces | 0.236s run time

2025-10-30T00:06:57.575Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

models cypress/e2e/ml/model_sagemaker.js::cypress/e2e/ml/model_sagemaker.js

Stack Traces | 0.237s run time

2025-10-29T23:59:39.694Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

create and manage platform and metadata policies "before each" hook for "cypress/e2e/settingsV2/v2_manage_policies.js"::cypress/e2e/settingsV2/v2_manage_policies.j

Stack Traces | 0.24s run time

2025-10-29T23:59:57.158Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `create and manage platform ...`

create announcement and link post "before each" hook for "cypress/e2e/settingsV2/v2_homePagePost.js"::cypress/e2e/settingsV2/v2_homePagePost.j

Stack Traces | 0.241s run time

2025-10-30T00:00:44.468Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `create announcement and lin...`

features cypress/e2e/ml/feature_table.js::cypress/e2e/ml/feature_table.js

Stack Traces | 0.241s run time

2025-10-29T23:58:52.603Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

siblings cypress/e2e/siblings/siblings.js::cypress/e2e/siblings/siblings.js

Stack Traces | 0.241s run time

2025-10-30T00:08:23.754Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

task runs cypress/e2e/task_runs/task_runs.js::cypress/e2e/task_runs/task_runs.js

Stack Traces | 0.241s run time

2025-10-30T00:08:49.438Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

glossary cypress/e2e/glossary/glossary.js::cypress/e2e/glossary/glossary.js

Stack Traces | 0.243s run time

2025-10-29T23:56:50.729Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

login cypress/e2e/login/login.js::cypress/e2e/login/login.js

Stack Traces | 0.244s run time

2025-10-30T00:06:23.389Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

manage queries "before each" hook for "cypress/e2e/query/query_tab.js"::cypress/e2e/query/query_tab.j

Stack Traces | 0.245s run time

2025-10-29T23:59:38.960Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `manage queries`

Manage Ingestion and Secret Privileges cypress/e2e/mutations/manage_ingestion_secret_privilege.js::cypress/e2e/mutations/manage_ingestion_secret_privilege.js

Stack Traces | 0.246s run time

2025-10-30T00:17:05.791Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

glossaryTerm "before each" hook for "cypress/e2e/glossaryV2/v2_glossaryTerm.js"::cypress/e2e/glossaryV2/v2_glossaryTerm.j

Stack Traces | 0.247s run time

2025-10-29T23:57:07.722Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `glossaryTerm`

tags cypress/e2e/manage_tagsV2/manage_tagsV2.js::cypress/e2e/manage_tagsV2/manage_tagsV2.js

Stack Traces | 0.248s run time

2025-10-29T23:59:25.502Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

domains cypress/e2e/domains/domains.js::cypress/e2e/domains/domains.js

Stack Traces | 0.249s run time

2025-10-29T23:56:45.587Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Verify nested domains test functionalities "before each" hook for "cypress/e2e/domains/nested_domains.js"::cypress/e2e/domains/nested_domains.j

Stack Traces | 0.251s run time

2025-10-29T23:57:03.260Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Verify nested domains test ...`

add remove domain cypress/e2e/mutations/domains.js::cypress/e2e/mutations/domains.js

Stack Traces | 0.252s run time

2025-10-29T23:57:15.564Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

edit documentation and link to dataset cypress/e2e/mutations/edit_documentation.js::cypress/e2e/mutations/edit_documentation.js

Stack Traces | 0.252s run time

2025-10-30T00:01:52.745Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

home cypress/e2e/home/home.js::cypress/e2e/home/home.js

Stack Traces | 0.254s run time

2025-10-29T23:58:47.708Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

manage views cypress/e2e/viewV2/v2_manage_views.js::cypress/e2e/viewV2/v2_manage_views.js

Stack Traces | 0.254s run time

2025-10-29T23:59:26.525Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

businessAttribute cypress/e2e/businessAttribute/businessAttribute.js::cypress/e2e/businessAttribute/businessAttribute.js

Stack Traces | 0.257s run time

2025-10-29T23:57:24.311Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

managing secrets for ingestion creation cypress/e2e/mutations/managing_secrets.js::cypress/e2e/mutations/managing_secrets.js

Stack Traces | 0.257s run time

2025-10-29T23:59:52.231Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Stats tab on entity cypress/e2e/statsTabV2/statsTab.js::cypress/e2e/statsTabV2/statsTab.js

Stack Traces | 0.259s run time

2025-10-30T00:18:34.950Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

analytics cypress/e2e/analytics/analytics.js::cypress/e2e/analytics/analytics.js

Stack Traces | 0.26s run time

2025-10-29T23:57:08.762Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

add_user cypress/e2e/mutations/add_users.js::cypress/e2e/mutations/add_users.js

Stack Traces | 0.261s run time

2025-10-30T00:06:28.598Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

login cypress/e2e/loginV2/v2_login.js::cypress/e2e/loginV2/v2_login.js

Stack Traces | 0.261s run time

2025-10-29T23:57:03.036Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

WelcomeToDataHubModal cypress/e2e/onboarding/welcome-to-datahub-modal.cy.js::cypress/e2e/onboarding/welcome-to-datahub-modal.cy.js

Stack Traces | 0.262s run time

2025-10-29T23:59:23.644Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

ingestion source creation flow cypress/e2e/mutations/ingestion_source.js::cypress/e2e/mutations/ingestion_source.js

Stack Traces | 0.263s run time

2025-10-29T23:59:47.054Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

manage tags cypress/e2e/manage_tags/manage_tags.js::cypress/e2e/manage_tags/manage_tags.js

Stack Traces | 0.265s run time

2025-10-29T23:59:49.225Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

summary tab - glossary term "before each" hook for "cypress/e2e/summaryTab/summaryTab.js"::cypress/e2e/summaryTab/summaryTab.j

Stack Traces | 0.266s run time

2025-10-29T23:59:19.029Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `summary tab - glossary term`

manage ownership cypress/e2e/ownershipV2/v2_manage_ownership.js::cypress/e2e/ownershipV2/v2_manage_ownership.js

Stack Traces | 0.267s run time

2025-10-30T00:00:03.955Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

attribute list adding tags and terms cypress/e2e/businessAttribute/attribute_mutations.js::cypress/e2e/businessAttribute/attribute_mutations.js

Stack Traces | 0.268s run time

2025-10-29T23:56:57.964Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

lineage_graph cypress/e2e/lineageV2/v2_lineage_graph.js::cypress/e2e/lineageV2/v2_lineage_graph.js

Stack Traces | 0.27s run time

2025-10-29T23:59:09.437Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

summary tab - domain "before each" hook for "cypress/e2e/summaryTab/summaryTab.js"::cypress/e2e/summaryTab/summaryTab.j

Stack Traces | 0.27s run time

2025-10-29T23:59:14.515Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `summary tab - domain`

summary tab - glossary node "before each" hook for "cypress/e2e/summaryTab/summaryTab.js"::cypress/e2e/summaryTab/summaryTab.j

Stack Traces | 0.271s run time

2025-10-29T23:59:17.150Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `summary tab - glossary node`

auto-complete dropdown, filter plus query search test "before each" hook for "cypress/e2e/search/query_and_filter_search.js"::cypress/e2e/search/query_and_filter_search.j

Stack Traces | 0.272s run time

2025-10-30T00:00:09.351Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `auto-complete dropdown, fil...`

create and manage platform and metadata policies "before each" hook for "cypress/e2e/settings/manage_policies.js"::cypress/e2e/settings/manage_policies.j

Stack Traces | 0.273s run time

2025-10-29T23:59:43.832Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `create and manage platform ...`

manage applications cypress/e2e/application/manage_applications.js::cypress/e2e/application/manage_applications.js

Stack Traces | 0.273s run time

2025-10-29T23:56:56.883Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

manage views cypress/e2e/views/manage_views.js::cypress/e2e/views/manage_views.js

Stack Traces | 0.273s run time

2025-10-30T00:08:56.663Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

siblings cypress/e2e/siblingsV2/v2_siblings.js::cypress/e2e/siblingsV2/v2_siblings.js

Stack Traces | 0.273s run time

2025-10-30T00:08:41.999Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Charts cypress/e2e/statsTabV2/charts.js::cypress/e2e/statsTabV2/charts.js

Stack Traces | 0.274s run time

2025-10-30T00:06:30.463Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

dataset deprecation cypress/e2e/mutations/deprecations.js::cypress/e2e/mutations/deprecations.js

Stack Traces | 0.275s run time

2025-10-29T23:57:10.499Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

lineage_graph cypress/e2e/lineage/lineage_graph.js::cypress/e2e/lineage/lineage_graph.js

Stack Traces | 0.276s run time

2025-10-29T23:58:27.064Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

view select cypress/e2e/views/view_select.js::cypress/e2e/views/view_select.js

Stack Traces | 0.276s run time

2025-10-30T00:00:04.533Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

containers cypress/e2e/containers/containers.js::cypress/e2e/containers/containers.js

Stack Traces | 0.277s run time

2025-10-29T23:56:40.273Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

column-level lineage graph test cypress/e2e/lineage/lineage_column_level.js::cypress/e2e/lineage/lineage_column_level.js

Stack Traces | 0.278s run time

2025-10-29T23:57:24.109Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

docPropagation cypress/e2e/actions/docPropagation.js::cypress/e2e/actions/docPropagation.js

Stack Traces | 0.278s run time

2025-10-29T23:57:03.380Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

summary tab - data product "before each" hook for "cypress/e2e/summaryTab/summaryTab.js"::cypress/e2e/summaryTab/summaryTab.j

Stack Traces | 0.279s run time

2025-10-29T23:59:21.067Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `summary tab - data product`

search cypress/e2e/search/search.js::cypress/e2e/search/search.js

Stack Traces | 0.283s run time

2025-10-29T23:57:38.386Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

incidents cypress/e2e/incidentsV2/v2_incidents.js::cypress/e2e/incidentsV2/v2_incidents.js

Stack Traces | 0.287s run time

2025-10-29T23:57:08.799Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

containers cypress/e2e/containersV2/v2_containers.js::cypress/e2e/containersV2/v2_containers.js

Stack Traces | 0.288s run time

2025-10-29T23:57:02.436Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

column-level lineage graph test cypress/e2e/lineageV2/v2_lineage_column_level.js::cypress/e2e/lineageV2/v2_lineage_column_level.js

Stack Traces | 0.294s run time

2025-10-29T23:56:58.057Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Column stats cypress/e2e/statsTabV2/columnStats.js::cypress/e2e/statsTabV2/columnStats.js

Stack Traces | 0.303s run time

2025-10-30T00:00:49.854Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

auto-complete cypress/e2e/auto_complete/auto_complete.js::cypress/e2e/auto_complete/auto_complete.js

Stack Traces | 0.312s run time

2025-10-29T23:56:51.419Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

auto-complete "before each" hook for "cypress/e2e/auto_completeV2/v2_auto_complete.js"::cypress/e2e/auto_completeV2/v2_auto_complete.j

Stack Traces | 0.374s run time

2025-10-29T23:57:06.970Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `auto-complete`

experiment "before each" hook for "cypress/e2e/ml/experiment.js"::cypress/e2e/ml/experiment.j

Stack Traces | 0.68s run time

2025-10-30T00:17:00.893Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `experiment`

manage access tokens cypress/e2e/settings/manage_access_tokens.js::cypress/e2e/settings/manage_access_tokens.js

Stack Traces | 0.682s run time

2025-10-30T00:17:33.162Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

manage ownership cypress/e2e/ownership/manage_ownership.js::cypress/e2e/ownership/manage_ownership.js

Stack Traces | 0.691s run time

2025-10-29T23:59:33.912Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

operations cypress/e2e/operations/operations.js::cypress/e2e/operations/operations.js

Stack Traces | 0.691s run time

2025-10-30T00:17:20.793Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Highlights cypress/e2e/statsTabV2/highlights.js::cypress/e2e/statsTabV2/highlights.js

Stack Traces | 0.702s run time

2025-10-29T23:59:51.896Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Verify manage structured properties functionalities "before each" hook for "cypress/e2e/structured_properties/structured_properties.js"::cypress/e2e/structured_properties/structured_properties.j

Stack Traces | 0.712s run time

2025-10-29T23:59:59.815Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Verify manage structured pr...`

Change history calendar chart cypress/e2e/statsTabV2/operationsChart.js::cypress/e2e/statsTabV2/operationsChart.js

Stack Traces | 0.713s run time

2025-10-30T00:17:40.878Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

run managed ingestion cypress/e2e/mutationsV2/v2_managed_ingestion.js::cypress/e2e/mutationsV2/v2_managed_ingestion.js

Stack Traces | 0.713s run time

2025-10-30T00:17:15.325Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

ingestion source creation flow cypress/e2e/mutationsV2/v2_ingestion_source.js::cypress/e2e/mutationsV2/v2_ingestion_source.js

Stack Traces | 0.724s run time

2025-10-29T23:57:33.136Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

search cypress/e2e/search/searchFilters.js::cypress/e2e/search/searchFilters.js

Stack Traces | 0.724s run time

2025-10-30T00:18:23.846Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

edit documentation and link to dataset "before each" hook for "cypress/e2e/mutationsV2/v2_edit_documentation.js"::cypress/e2e/mutationsV2/v2_edit_documentation.j

Stack Traces | 0.736s run time

2025-10-29T23:57:27.455Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `edit documentation and link...`

dataset health test cypress/e2e/mutations/dataset_health.js::cypress/e2e/mutations/dataset_health.js

Stack Traces | 0.737s run time

2025-10-29T23:59:02.241Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

searchBarV2 cypress/e2e/searchV2/searchBarV2Redesigned.js::cypress/e2e/searchV2/searchBarV2Redesigned.js

Stack Traces | 0.76s run time

2025-10-30T00:00:15.490Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

view select cypress/e2e/viewV2/v2_view_select.js::cypress/e2e/viewV2/v2_view_select.js

Stack Traces | 0.763s run time

2025-10-30T00:00:05.831Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

download lineage results to .csv file cypress/e2e/lineage/download_lineage_results.js::cypress/e2e/lineage/download_lineage_results.js

Stack Traces | 10.3s run time

2025-10-29T23:59:13.360Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

run history tab in manage data sources "before each" hook for "cypress/e2e/ingestionV2/run_history.js"::cypress/e2e/ingestionV2/run_history.j

Stack Traces | 10.3s run time

2025-10-30T00:04:54.156Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `run history tab in manage d...`

models cypress/e2e/ml/model_mlflow.js::cypress/e2e/ml/model_mlflow.js

Stack Traces | 10.3s run time

2025-10-30T00:00:44.590Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

column-Level lineage and impact analysis path test cypress/e2e/lineageV2/v2_lineage_column_path.js::cypress/e2e/lineageV2/v2_lineage_column_path.js

Stack Traces | 10.3s run time

2025-10-29T23:59:37.958Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

column-Level lineage and impact analysis path test cypress/e2e/lineage/lineage_column_path.js::cypress/e2e/lineage/lineage_column_path.js

Stack Traces | 10.3s run time

2025-10-29T23:58:31.305Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

ingestion sources "before each" hook for "cypress/e2e/ingestionV2/sources.js"::cypress/e2e/ingestionV2/sources.j

Stack Traces | 10.7s run time

2025-10-29T23:59:04.125Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `ingestion sources`

schema blame cypress/e2e/schema_blameV2/v2_schema_blame.js::cypress/e2e/schema_blameV2/v2_schema_blame.js

Stack Traces | 10.8s run time

2025-10-30T00:17:14.806Z
Timed out retrying after 10000ms: Expected to find element: `#column-field_baz`, but never found it.

glossary cypress/e2e/glossaryV2/v2_glossary.js::cypress/e2e/glossaryV2/v2_glossary.js

Stack Traces | 10.8s run time

2025-10-29T23:58:42.541Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

home cypress/e2e/homeV2/v2_home.js::cypress/e2e/homeV2/v2_home.js

Stack Traces | 10.8s run time

2025-10-29T23:58:06.726Z
Timed out retrying after 10000ms: Expected to find element: `[xmlns="http://www.w3.org/2000/svg"]`, but never found it.

download lineage results to .csv file cypress/e2e/lineageV2/v2_download_lineage_results.js::cypress/e2e/lineageV2/v2_download_lineage_results.js

Stack Traces | 10.8s run time

2025-10-29T23:59:43.771Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

glossary sidebar navigation test "before each" hook for "cypress/e2e/glossaryV2/v2_glossary_navigation.js"::cypress/e2e/glossaryV2/v2_glossary_navigation.j

Stack Traces | 10.8s run time

2025-10-29T23:58:15.048Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `glossary sidebar navigation...`

applications cypress/e2e/application/applications.js::cypress/e2e/application/applications.js

Stack Traces | 13.8s run time

2025-10-30T00:03:46.496Z
Timed out retrying after 10000ms: Expected to find content: 'customers' but never did.

schema blame cypress/e2e/schema_blame/schema_blame.js::cypress/e2e/schema_blame/schema_blame.js

Stack Traces | 20.9s run time

2025-10-30T00:04:07.842Z
Timed out retrying after 10000ms: Expected to find content: 'field_foo' but never did.

View the full list of 8 ❄️ flaky test(s)

add, remove ownership for dataset cypress/e2e/mutations/dataset_ownership.js::cypress/e2e/mutations/dataset_ownership.js

Flake rate in main: 40.00% (Passed 54 times, Failed 36 times)

Stack Traces | 10.7s run time

2025-10-30T00:07:39.381Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

create and manage group cypress/e2e/settingsV2/v2_managing_groups.js::cypress/e2e/settingsV2/v2_managing_groups.js

Flake rate in main: 30.77% (Passed 72 times, Failed 32 times)

Stack Traces | 10.3s run time

2025-10-29T23:59:00.885Z
Timed out retrying after 10000ms: Expected to find element: `input[data-testid=username]`, but never found it.

domains cypress/e2e/domainsV2/v2_domains.js::cypress/e2e/domainsV2/v2_domains.js
Flake rate in main: 29.66% (Passed 83 times, Failed 35 times)
Stack Traces | 10.8s run time
2025-10-29T23:57:51.993Z
Timed out retrying after 10000ms: Expected to find content: 'Testing' but never did.

impact analysis cypress/e2e/lineage/impact_analysis.js::cypress/e2e/lineage/impact_analysis.js

Flake rate in main: 100.00% (Passed 0 times, Failed 8 times)

Stack Traces | 13.8s run time

2025-10-29T23:58:41.951Z
Timed out retrying after 10000ms: Expected to find content: 'SampleCypressKafkaDataset' but never did.

impact analysis cypress/e2e/lineageV2/v2_impact_analysis.js::cypress/e2e/lineageV2/v2_impact_analysis.js

Flake rate in main: 30.77% (Passed 81 times, Failed 36 times)

Stack Traces | 13.8s run time

2025-10-30T00:06:19.911Z
Timed out retrying after 10000ms: Expected to find content: 'SampleCypressKafkaDataset' but never did.

manage access tokens cypress/e2e/settingsV2/v2_manage_access_tokens.js::cypress/e2e/settingsV2/v2_manage_access_tokens.js

Flake rate in main: 29.66% (Passed 83 times, Failed 35 times)

Stack Traces | 0.242s run time

2025-10-29T23:59:07.339Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

managing secrets for ingestion creation cypress/e2e/mutationsV2/v2_managing_secrets.js::cypress/e2e/mutationsV2/v2_managing_secrets.js

Flake rate in main: 36.36% (Passed 7 times, Failed 4 times)

Stack Traces | 0.242s run time

2025-10-29T23:59:18.420Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

search cypress/e2e/browse/browseV2.js::cypress/e2e/browse/browseV2.js

Flake rate in main: 30.77% (Passed 72 times, Failed 32 times)

Stack Traces | 0.711s run time

2025-10-29T23:57:04.140Z
The following error originated from your application code, not from Cypress.

  > React is not defined

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.

https://on.cypress.io/uncaught-exception-from-application

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

asikowitz added 11 commits October 29, 2025 12:04

initial removal

c59f8e3

WIP

9348459

remove unused code

8b1da3b

more removals

565f9c1

another wave

9762631

anothe rround

f4c5d30

again

048b51a

again

bdaf5cf

a

6ecbe46

last?

260d172

last

4d73b92

asikowitz changed the title ~~refactor(ui): Remove V1 UI~~ refactor(ui): Remove V1 UI (round 1) Oct 29, 2025

github-actions bot added the product PR or Issue related to the DataHub UI/UX label Oct 29, 2025

asikowitz changed the title ~~refactor(ui): Remove V1 UI (round 1)~~ refactor(ui): Remove V1 UI (round 2) Oct 29, 2025

github-actions bot deployed to datahub-project-web-react (Preview) October 29, 2025 23:47 View deployment

vercel bot had a problem deploying to Preview October 29, 2025 23:48 Failure

datahub-cyborg bot added the needs-review Label for PRs that need review from a maintainer. label Oct 29, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

refactor(ui): Remove V1 UI (round 2) #15147

refactor(ui): Remove V1 UI (round 2) #15147

asikowitz commented Oct 29, 2025 •

edited

Loading

Uh oh!

alwaysmeticulous bot commented Oct 29, 2025 •

edited

Loading

Uh oh!

codecov bot commented Oct 29, 2025 •

edited

Loading

Assets Changed:

Uh oh!

codecov bot commented Oct 29, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

refactor(ui): Remove V1 UI (round 2) #15147

Are you sure you want to change the base?

refactor(ui): Remove V1 UI (round 2) #15147

Conversation

asikowitz commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

alwaysmeticulous bot commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov bot commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bundle Report

Affected Assets, Files, and Routes:

Assets Changed:

Uh oh!

codecov bot commented Oct 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ 92 Tests Failed:

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

asikowitz commented Oct 29, 2025 •

edited

Loading

alwaysmeticulous bot commented Oct 29, 2025 •

edited

Loading

codecov bot commented Oct 29, 2025 •

edited

Loading

codecov bot commented Oct 29, 2025 •

edited

Loading