{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":368565094,"defaultBranch":"master","name":"cockroach","ownerLogin":"THardy98","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-05-18T14:41:50.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/15315413?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1696971323.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"ff64a259cd3a8ddc6c54d6af7d2fc12017e671ad","ref":"refs/heads/fix_TestInsightsIntegrationForContention_schema_name","pushedAt":"2023-10-10T20:55:23.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"sqlstats: fix schema name for estInsightsIntegrationForContention\n\nFix TestInsightsIntegrationForContention, by adding COALESCE on possible\nNULL schema name.\n\nFix #111883\n\nRelease note: None","shortMessageHtmlLink":"sqlstats: fix schema name for estInsightsIntegrationForContention"}},{"before":"71947a43ce6bc9e00cd93bf09da97c3a54c30d35","after":"20f8af5be1dd41d67fa56f25c0b888be8db44338","ref":"refs/heads/backport22.2-105070","pushedAt":"2023-10-10T14:37:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"sql: fix flaky test TestSQLStatsCompactor\n\nThe failure does not reproduce locally. The test ran for over 30mins\nwith no failures using the same flags and commit in the last reported\ntest failure.\n\nThe theory is the test count mistmatch is due to the test cases\nrunning in parrallel. The individual test cases are using the same\nshared interceptors. To fix this the interceptors and server are\ncreated as part of the test case to avoid any possible conflict.\n\nFixes: https://github.com/cockroachdb/cockroach/issues/102750\n\nEpic: none\nRelease note: None","shortMessageHtmlLink":"sql: fix flaky test TestSQLStatsCompactor"}},{"before":"2a30644e2b4ba7c021d727e16503f8903e4b160b","after":"71947a43ce6bc9e00cd93bf09da97c3a54c30d35","ref":"refs/heads/backport22.2-105070","pushedAt":"2023-10-10T13:45:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":null,"after":"2a30644e2b4ba7c021d727e16503f8903e4b160b","ref":"refs/heads/backport22.2-105070","pushedAt":"2023-10-07T18:52:20.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"sql: fix flaky test TestSQLStatsCompactor\n\nThe failure does not reproduce locally. The test ran for over 30mins\nwith no failures using the same flags and commit in the last reported\ntest failure.\n\nThe theory is the test count mistmatch is due to the test cases\nrunning in parrallel. The individual test cases are using the same\nshared interceptors. To fix this the interceptors and server are\ncreated as part of the test case to avoid any possible conflict.\n\nFixes: https://github.com/cockroachdb/cockroach/issues/102750\n\nEpic: none\nRelease note: None","shortMessageHtmlLink":"sql: fix flaky test TestSQLStatsCompactor"}},{"before":null,"after":"cba2c3839b32b023eb50ca48d87d4eff7bc723f2","ref":"refs/heads/update_txn_exec_insight_endpoint","pushedAt":"2023-10-07T18:46:55.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: update txn insights endpoint\n\nEpic: https://cockroachlabs.atlassian.net/browse/CRDB-25473\nJira issue: CRDB-31500\n\nAddresses: #110552\n\nThis change migrates the old transaction insights endpoint using /sql\nwith the newly introduced one on the status server (provided here: #110894)\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: update txn insights endpoint"}},{"before":"0c2a103f5f0bdafdfa08967d10692a7ed4c45a0e","after":"566c68ae7179d76b003a57b41cce23c915e614e2","ref":"refs/heads/update_stmt_exec_insight_endpoint","pushedAt":"2023-10-06T15:29:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: update statement insights endpoint\n\nAddresses: #110552\n\nThis change migrates the old statement insights endpoint using `/sql`\nwith the newly introduced one on the status server (provided here:\n\nThis change does *not* change the existing transaction insights\nendpoint. This endpoint relies on some utilities from the former\nstatement insights endpoint. These utilities have been move to\n`legacyStmtInsightsUtils.ts` and are intended to be removed once the\ntransaction insights endpoint has also been migrated.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: update statement insights endpoint"}},{"before":"9901e152f9c886005167e8c9aaff4afab1f27aa8","after":"0c2a103f5f0bdafdfa08967d10692a7ed4c45a0e","ref":"refs/heads/update_stmt_exec_insight_endpoint","pushedAt":"2023-10-06T15:09:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":"0862c47efc17a1f2adef50fecfc711e6f19cef1e","after":"9901e152f9c886005167e8c9aaff4afab1f27aa8","ref":"refs/heads/update_stmt_exec_insight_endpoint","pushedAt":"2023-10-06T14:55:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":null,"after":"0862c47efc17a1f2adef50fecfc711e6f19cef1e","ref":"refs/heads/update_stmt_exec_insight_endpoint","pushedAt":"2023-10-06T02:40:01.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: update statement insights endpoint\n\nAddresses: #110552\n\nThis change migrates the old statement insights endpoint using `/sql`\nwith the newly introduced one on the status server (provided here:\n\nThis change does *not* change the existing transaction insights\nendpoint. This endpoint relies on some utilities from the former\nstatement insights endpoint. These utilities have been move to\n`legacyStmtInsightsUtils.ts` and are intended to be removed once the\ntransaction insights endpoint has also been migrated.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: update statement insights endpoint"}},{"before":null,"after":"b0a36c79da263459a186ab5fdca9b833473ff6fa","ref":"refs/heads/backport23.1-111440","pushedAt":"2023-10-04T12:52:54.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: fix db page stories\n\nEpic: none\n\nThis change fixes the stories for the database pages.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: fix db page stories"}},{"before":null,"after":"3f7e4f6a7c6902919ced900d98810aedcdd52b7a","ref":"refs/heads/pin_cluster_ui_publish","pushedAt":"2023-10-03T15:37:58.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: pin `pnpm` to `8.6.10` for cluster-ui-release workflow\n\nEpic: none This change pins `pnpm` to `8.6.10` for the cluster-ui\nrelease (and release-next) workflow(s) to prevent not up-to-date\nlockfiles when installing cluster-ui dependencies with pnpm.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: pin pnpm to 8.6.10 for cluster-ui-release workflow"}},{"before":"53e39a879ae61a575a39704c20b3c55a6a476845","after":"1796236137f09920dab6b3b7193901a789948c4a","ref":"refs/heads/fix_db_pages_stories","pushedAt":"2023-09-29T13:47:51.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: fix db page stories\n\nEpic: none\n\nThis change fixes the stories for the database pages.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: fix db page stories"}},{"before":null,"after":"53e39a879ae61a575a39704c20b3c55a6a476845","ref":"refs/heads/fix_db_pages_stories","pushedAt":"2023-09-28T19:01:13.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: fix db page stories\n\nEpic: none\n\nThis change fixes the stories for the database pages.\n\nRelease note: None","shortMessageHtmlLink":"cluster-ui: fix db page stories"}},{"before":"f186d32935af09b6cde95f3ab9bc6e6bb8a10c21","after":"f1b3bf6fcb34f780c6266b4fe4787d8e121a194f","ref":"refs/heads/bump-cluster-ui-23.1.11","pushedAt":"2023-09-21T15:29:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"ui: bump cluster-ui to 23.1.11\n\nBump cluster-ui to 23.1.11\n\nEpic: none\n\nRelease note: None","shortMessageHtmlLink":"ui: bump cluster-ui to 23.1.11"}},{"before":"cc6d0d9f82ba3bc65539553b0754207d472625ca","after":"f186d32935af09b6cde95f3ab9bc6e6bb8a10c21","ref":"refs/heads/bump-cluster-ui-23.1.11","pushedAt":"2023-09-21T15:27:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":null,"after":"cc6d0d9f82ba3bc65539553b0754207d472625ca","ref":"refs/heads/bump-cluster-ui-23.1.11","pushedAt":"2023-09-21T15:26:34.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"Merge pull request #110962 from cockroachdb/blathers/backport-release-23.1-110918\n\nrelease-23.1: changefeedccl: deflake TestAlterChangefeedAddTargetsDuringBackfill","shortMessageHtmlLink":"Merge pull request cockroachdb#110962 from cockroachdb/blathers/backp…"}},{"before":"0408c766852ce6551404433b86078db4e9e594b0","after":"36c73dab189eb717e0115c795219dbc7dff23bc6","ref":"refs/heads/backport23.1-109521","pushedAt":"2023-09-15T19:54:17.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database table page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase table page, enabling non-admin users to use the database table\npage and providing better transparency to data fetching issues.\n\n`unavailable` fields provide a tooltip that displays the error impacting\nthat field.\n\nRelease note (ui change): Non-admin users are able to use the database\ntable page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database table page"}},{"before":null,"after":"52385a8f5f8aad188fe95f82dc2e1d77c152afbf","ref":"refs/heads/backport23.1-106778","pushedAt":"2023-09-15T18:22:06.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: skip undefined regions on database pages\n\nThis patch skips `undefined` regions on the databases pages. The\n`undefined` behaviour occurs when we try to match a database's node IDs\n(i.e. the nodes with ranges that contain data belong to one of the\ndatabase's tables) from the database details endpoint, to nodes' region\ninformation from the nodes endpoint.\n\nThe nodes endpoint is authoritative and is refreshed at a regular\ninterval. However, the database details endpoint is only fetched once on\npage load, and it's node information comes from a cache, leading to the\npotential of stale data (this information is authoritative in 23.1, but\nnot in 22.2).\n\nConsequently when trying to match cached node IDs with recent node\nregions information, we can come across behaviour where we try to get\nregion information for a node ID that is no longer valid (i.e. in the\ncase of a decommissioned node), resulting in `undefined` and surfacing\noutdated node information.\n\nThis change ensures that when we encounter such occurrences, we avoid\ndisplaying them in the console.\n\nRelease note (bug fix): Avoid displaying `undefined` regions on the\ndatabases pages.","shortMessageHtmlLink":"cluster-ui: skip undefined regions on database pages"}},{"before":null,"after":"0a7c93c7d1a8c3b58c33f92bd1879ac51eb16b40","ref":"refs/heads/backport23.1-107893","pushedAt":"2023-09-15T14:14:50.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: fix replicas and regions query for the database details API\n\nA change in #105582 caused the regions/replicas query to return\nincorrect, unexpected results causing the endpoint to never resolve\nproperly, which in turn, caused an infinite loading state. This change\nfixes the regions/replicas query for the database details API.\n\nRelease note (ui change): fix a broken query for the database details\npage that was causing an infinite loading state.","shortMessageHtmlLink":"cluster-ui: fix replicas and regions query for the database details API"}},{"before":null,"after":"0408c766852ce6551404433b86078db4e9e594b0","ref":"refs/heads/backport23.1-109521","pushedAt":"2023-09-14T21:00:18.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database table page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase table page, enabling non-admin users to use the database table\npage and providing better transparency to data fetching issues.\n\n`unavailable` fields provide a tooltip that displays the error impacting\nthat field.\n\nRelease note (ui change): Non-admin users are able to use the database\ntable page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database table page"}},{"before":"d745754735edbb3e748e4c8050002cd9ddf5c324","after":"27d65522eeb7a6b5ebd7981c7abd321023494132","ref":"refs/heads/db_table_page_partial_err","pushedAt":"2023-09-13T19:51:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database table page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase table page, enabling non-admin users to use the database table\npage and providing better transparency to data fetching issues.\n\n`unavailable` fields provide a tooltip that displays the error impacting\nthat field.\n\nRelease note (ui change): Non-admin users are able to use the database\ntable page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database table page"}},{"before":"87f5b563d30e89611904c42b2834ae690a7bf800","after":"d745754735edbb3e748e4c8050002cd9ddf5c324","ref":"refs/heads/db_table_page_partial_err","pushedAt":"2023-09-12T13:14:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database table page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase table page, enabling non-admin users to use the database table\npage and providing better transparency to data fetching issues.\n\n`unavailable` fields provide a tooltip that displays the error impacting\nthat field.\n\nRelease note (ui change): Non-admin users are able to use the database\ntable page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database table page"}},{"before":"599872a4958649f8091ebe3ea9296404eafd15a5","after":"87f5b563d30e89611904c42b2834ae690a7bf800","ref":"refs/heads/db_table_page_partial_err","pushedAt":"2023-09-11T19:44:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database table page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase table page, enabling non-admin users to use the database table\npage and providing better transparency to data fetching issues.\n\n`unavailable` fields provide a tooltip that displays the error impacting\nthat field.\n\nRelease note (ui change): Non-admin users are able to use the database\ntable page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database table page"}},{"before":null,"after":"d47133fa371384b96cdd592b501496eb4c2bbfbc","ref":"refs/heads/backport23.1-109432","pushedAt":"2023-09-11T19:04:03.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database details page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase details page, enabling non-admin users to use the database\ndetails page and providing better transparency to data fetching issues.\n\nErrors encountered while fetching table details can be viewed via the\ntooltip provided by the `Caution` icon at the table's name.\n`unavailable` cells also provide a tooltip that displays the error\nimpacting that exact cell.\n\nRelease note (ui change): Non-admin users are able to use the database\ndetails page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database details page"}},{"before":"1bfdb4aeac53f1e2681cbf4c7f0ee2f6e11d222f","after":null,"ref":"refs/heads/backport23.1-109432","pushedAt":"2023-09-11T19:03:27.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":"0935fa09dbb39d587f792c4d442ada45463edab8","after":"599872a4958649f8091ebe3ea9296404eafd15a5","ref":"refs/heads/db_table_page_partial_err","pushedAt":"2023-09-11T19:01:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":null,"after":"1bfdb4aeac53f1e2681cbf4c7f0ee2f6e11d222f","ref":"refs/heads/backport23.1-109432","pushedAt":"2023-09-11T15:29:51.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"}},{"before":null,"after":"3fbd2747f20eb5429177151d8bb6fe5c49d51004","ref":"refs/heads/backport23.1-109245","pushedAt":"2023-09-11T15:27:25.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the databases page\n\nPart of: #102386\n\nPrior to this change, any query error in the reponse payload for the\ndatabases page would cause the page to render an error. This was\nproblematic as some queries used to power the databases page directly\nquery `system` tables, meaning only `ADMIN` users could access the page.\nThis change allows the databases page to handle network responses with\nquery errors, consequently allowing non-admin users to view the data\nthey are privy to.\n\nOn the databases page, two types of requests are made:\n- a single request to fetch all database names\n- a request to fetch the database details for each database name\n\nThe error handling for these requests has changed as such:\n- if we encounter a network or a non size-related query error when\n requesting database names, render a page error\n\n- if we encounter a 'max size' query error when requesting database\n names, render an alert that we're showing partial results\n\n- if we encounter any error requesting a database's details, render a\n `Caution` icon next to the database's name to indicate there was an\nissue getting results, the `Caution` icon has a tooltip providing a\ngeneral explanation as to what the issue is\n\n- network errors when fetching database details provide no data for the\n database's table row, consequently the row of statistics for that\ndatabase is `unavailable`, the network error message is provided in the\n`Caution` icon tooltip\n\n- query errors when fetching database details are scoped to the row\n cells for that query, which are `unavailable`\n\n- `unavailable` cells have a tooltip that highlight the error for that\n cell as well\n\nRelease note (ui change): Allow non-admin users to view the databases\npage.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the databases page"}},{"before":"5569ffc218190f5d253d2a87fcc7a80785ff8e70","after":"001ca87b050bdc064aaef69b5aeabf0548a75e9b","ref":"refs/heads/db_details_page_partial_err","pushedAt":"2023-09-11T14:47:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the database details page\n\nPart of: #102386\n\nThis change applies the same error handling ideas from #109245 to the\ndatabase details page, enabling non-admin users to use the database\ndetails page and providing better transparency to data fetching issues.\n\nErrors encountered while fetching table details can be viewed via the\ntooltip provided by the `Caution` icon at the table's name.\n`unavailable` cells also provide a tooltip that displays the error\nimpacting that exact cell.\n\nRelease note (ui change): Non-admin users are able to use the database\ndetails page.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the database details page"}},{"before":"61cdea01f4d58b6141ab9a4fe115e654f586ab4b","after":"d77bee0bbceb9be7dd433364c869f9cab4e2890c","ref":"refs/heads/db_page_partial_err","pushedAt":"2023-08-28T14:17:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"THardy98","name":"Thomas Hardy","path":"/THardy98","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/15315413?s=80&v=4"},"commit":{"message":"cluster-ui: handle partial response errors on the databases page\n\nPart of: #102386\n\nPrior to this change, any query error in the reponse payload for the\ndatabases page would cause the page to render an error. This was\nproblematic as some queries used to power the databases page directly\nquery `system` tables, meaning only `ADMIN` users could access the page.\nThis change allows the databases page to handle network responses with\nquery errors, consequently allowing non-admin users to view the data\nthey are privy to.\n\nOn the databases page, two types of requests are made:\n- a single request to fetch all database names\n- a request to fetch the database details for each database name\n\nThe error handling for these requests has changed as such:\n- if we encounter a network or a non size-related query error when\n requesting database names, render a page error\n\n- if we encounter a 'max size' query error when requesting database\n names, render an alert that we're showing partial results\n\n- if we encounter any error requesting a database's details, render a\n `Caution` icon next to the database's name to indicate there was an\nissue getting results, the `Caution` icon has a tooltip providing a\ngeneral explanation as to what the issue is\n\n- network errors when fetching database details provide no data for the\n database's table row, consequently the row of statistics for that\ndatabase is `unavailable`, the network error message is provided in the\n`Caution` icon tooltip\n\n- query errors when fetching database details are scoped to the row\n cells for that query, which are `unavailable`\n\n- `unavailable` cells have a tooltip that highlight the error for that\n cell as well\n\nRelease note (ui change): Allow non-admin users to view the databases\npage.","shortMessageHtmlLink":"cluster-ui: handle partial response errors on the databases page"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADlAIynQA","startCursor":null,"endCursor":null}},"title":"Activity · THardy98/cockroach"}