Skip to content

feat: show workspace build logs during tasks creation - #19413

Merged
BrunoQuaresma merged 5 commits into
mainfrom
bq/19363
Aug 21, 2025
Merged

BrunoQuaresma merged 5 commits into
mainfrom
bq/19363

Conversation

@BrunoQuaresma

Copy link
Copy Markdown
Contributor

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 a team and johnstcn 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
Copy Markdown
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.

@johnstcn johnstcn left a comment

Copy link
Copy Markdown
Member

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
Copy Markdown
Contributor 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
Copy Markdown
Contributor Author

@johnstcn they are already there.

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

Copy link
Copy Markdown
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.

@johnstcn johnstcn left a comment

Copy link
Copy Markdown
Member

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

@aslilac aslilac left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

overall looks good!

Comment thread site/src/pages/TaskPage/TaskPage.tsx Outdated
return (
<>
<Helmet>
<title>{pageTitle(ellipsizeText(task.prompt, 64) ?? "Task")}</title>

Copy link
Copy Markdown
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
Copy Markdown
Contributor 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 👍

Comment thread site/src/pages/TaskPage/TaskPage.tsx Outdated

export default TaskPage;

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

Copy link
Copy Markdown
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 }) => {

Comment thread site/src/pages/TaskPage/TaskTopbar.tsx Outdated
import { Link as RouterLink } from "react-router";
import { TaskStatusLink } from "./TaskStatusLink";

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

Copy link
Copy Markdown
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

Comment thread site/src/pages/TaskPage/TaskTopbar.tsx Outdated
</TooltipProvider>

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

Copy link
Copy Markdown
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

dayjs.extend(duration);

// ActiveTransition gets the build estimate for the workspace,
// getActiveTransitionStats gets the build estimate for the workspace,

Copy link
Copy Markdown
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
@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