Skip to content

feat: show workspace build logs during tasks creation #19413

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

Merged
merged 5 commits into from
Aug 21, 2025
Merged

Conversation

BrunoQuaresma
Copy link
Collaborator

This is part of #19363

Screenshot:
Screenshot 2025-08-19 at 12 32 54

Video demo:

Screen.Recording.2025-08-19.at.12.32.15.mov

@BrunoQuaresma BrunoQuaresma requested review from johnstcn and a team August 19, 2025 15:35
@BrunoQuaresma BrunoQuaresma self-assigned this Aug 19, 2025
@BrunoQuaresma BrunoQuaresma removed the request for review from a team August 19, 2025 15:35
@BrunoQuaresma BrunoQuaresma requested a review from aslilac as a code owner August 19, 2025 15:35
@BrunoQuaresma BrunoQuaresma changed the title feat: shows workspace build logs during tasks creation feat: show workspace build logs during tasks creation Aug 19, 2025
@matifali
Copy link
Member

Should we collapse/hide these by default and only show if a user clicks on show build logs?

I think for most Tasks users they may not be interested in seeing the build logs.

Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

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

Could you add some stories for the following scenarios:

  • Workspace build pending
  • Workspace build running
  • Workspace build failed

@BrunoQuaresma
Copy link
Collaborator Author

@matifali I would agree with you if the screen had more info. Display the build logs is a way to show to the user that things are in progress. Before make any changes to it, I would like to test this hypothesis and see what users think about that, wdyt?

@BrunoQuaresma
Copy link
Collaborator Author

@johnstcn they are already there.

@BrunoQuaresma BrunoQuaresma requested a review from johnstcn August 19, 2025 16:01
@matifali
Copy link
Member

@BrunoQuaresma, I am fine if we want to test this. What I was thinking is a loading animation of some kind (Spinner) and a button to view logs if needed.

Copy link
Member

@johnstcn johnstcn left a comment

Choose a reason for hiding this comment

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

Sorry, missed seeing the stories! UI changes LGTM but also need approval from FE domain expert.

@BrunoQuaresma BrunoQuaresma requested review from a team and removed request for code-asher August 21, 2025 14:00
Copy link
Member

@aslilac aslilac left a comment

Choose a reason for hiding this comment

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

overall looks good!

return (
<>
<Helmet>
<title>{pageTitle(ellipsizeText(task.prompt, 64) ?? "Task")}</title>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<title>{pageTitle(ellipsizeText(task.prompt, 64) ?? "Task")}</title>
<title>{pageTitle(ellipsizeText(task.prompt, 64) || task.workspace.name)}</title>

...might be nice as a still safe but more descriptive fallback. also maybe || incase prompt is ""? I think you said that's not possible, but if it isn't I'm kinda confused on why we need the fallback at all

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good catch. I'm going to remove this fallback too 👍

</>
);
};

export default TaskPage;

const TaskBuildingWorkspace: FC<{ task: Task }> = ({ task }) => {
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
const TaskBuildingWorkspace: FC<{ task: Task }> = ({ task }) => {
type TaskBuildingWorkspaceProps = {
task: Task;
};
const TaskBuildingWorkspace: FC<TaskBuildingWorkspaceProps> = ({ task }) => {

import { Link as RouterLink } from "react-router";
import { TaskStatusLink } from "./TaskStatusLink";

export const TaskTopbar: FC<{ task: Task }> = ({ task }) => {
Copy link
Member

Choose a reason for hiding this comment

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

same here, give this type a name pls

</TooltipProvider>

<h1 className="m-0 text-base font-medium truncate">
{task.prompt || task.workspace.name}
Copy link
Member

Choose a reason for hiding this comment

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

re: fallbacks

this stands out to me too

@@ -9,9 +9,9 @@ import { type FC, useEffect, useState } from "react";

dayjs.extend(duration);

// ActiveTransition gets the build estimate for the workspace,
// getActiveTransitionStats gets the build estimate for the workspace,
Copy link
Member

Choose a reason for hiding this comment

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

ty for the rename

@BrunoQuaresma BrunoQuaresma merged commit 8aafbcb into main Aug 21, 2025
48 of 53 checks passed
@BrunoQuaresma BrunoQuaresma deleted the bq/19363 branch August 21, 2025 18:01
@github-actions github-actions bot locked and limited conversation to collaborators Aug 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy