- Notifications
You must be signed in to change notification settings - Fork1.1k
fix: display build timings when all timings are loaded#15728
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
6067e102181becb16fad153f267b0c7abeeFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -58,17 +58,9 @@ export const infiniteWorkspaceBuilds = ( | ||
| }; | ||
| // We use readyAgentsCount to invalidate the query when an agent connects | ||
| exportconstworkspaceBuildTimings=(workspaceBuildId:string)=>{ | ||
| return{ | ||
Contributor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. What was the ContributorAuthor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. It was to refetch the query when a new agent was marked as ready but it was very buggy and a bad decision on my end. The current refetch logic makes more sense and it is easier to follow. | ||
| queryKey:["workspaceBuilds",workspaceBuildId,"timings"], | ||
| queryFn:()=>API.workspaceBuildTimings(workspaceBuildId), | ||
| }; | ||
| }; | ||
Uh oh!
There was an error while loading.Please reload this page.