Conversation
🔴 Playwright Results — 1 failure(s), 19 flaky✅ 3621 passed · ❌ 1 failed · 🟡 19 flaky · ⏭️ 209 skipped
Genuine Failures (failed on all attempts)❌
|
| slowTestPipeline.fullyQualifiedName | ||
| )}/pipelineStatus**`, | ||
| async (route) => { | ||
| await page.waitForTimeout(8000); |
There was a problem hiding this comment.
why we are adding manual wait?
There was a problem hiding this comment.
@ShaileshParmar11 This timeout is added to increase the latency of that API to test few changes on UI.
| // Verify the run was triggered by checking the pipeline row shows a running state | ||
| await expect( | ||
| pipelineRow.getByTestId('pipeline-status').first() | ||
| ).toBeVisible({ timeout: 15000 }); |
There was a problem hiding this comment.
in every step i see random timeout, what the reason of it, and do we even need it?
There was a problem hiding this comment.
added this timeout is added because we need to check few things on UI after the api response came for the api for which we have increased the latency by mocking it.
Code Review ✅ Approved 2 resolved / 2 findingsFixes action buttons now displaying immediately by silencing permission promise errors and removing unreachable ✅ 2 resolved✅ Bug: Permission promise errors are silently swallowed
✅ Quality:
|
| Compact |
|
Was this helpful? React with 👍 / 👎 | Gitar
…PI (open-metadata#27139) * fix: action buttons visible immediately despite slow pipelineStatus API * fixed the recent run overlapping issue * addressed gitar comment * addressed PR comment * addressed gitar comment * fixed lint checks
…PI (open-metadata#27139) * fix: action buttons visible immediately despite slow pipelineStatus API * fixed the recent run overlapping issue * addressed gitar comment * addressed PR comment * addressed gitar comment * fixed lint checks
…PI (#27139) * fix: action buttons visible immediately despite slow pipelineStatus API * fixed the recent run overlapping issue * addressed gitar comment * addressed PR comment * addressed gitar comment * fixed lint checks
|



Describe your changes:
On the Ingestion List table, the action buttons (Run, Pause, Logs) were not visible until the pipelineStatus API responded. When this API had high latency, users were blocked from interacting with pipelines.
Root cause: Permissions and run history were fetched sequentially — action buttons only rendered after both APIs settled.
Fire permissions and run history fetches concurrently. Each updates state independently as soon as it settles:
Permissions settle → action buttons render immediately
Run history settles → status dots render (independently)
Fixes 27100
I worked on ... because ...
Fixed the recent runs overlapping issue.
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>