Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: display startup script logs while agent is starting#19530

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

Merged
BrunoQuaresma merged 8 commits intomainfrombq/handle-agent-being-ready-for-tasks
Aug 26, 2025

Conversation

@BrunoQuaresma
Copy link
Contributor

Closes#19363

Screenshot:

Screenshot 2025-08-25 at 11 02 25

Demo:

Screen.Recording.2025-08-22.at.16.00.23.mov

@BrunoQuaresmaBrunoQuaresma requested a review froma teamAugust 25, 2025 14:02
@BrunoQuaresmaBrunoQuaresma self-assigned thisAug 25, 2025
@BrunoQuaresmaBrunoQuaresma requested review froma team andbcpeinhardt and removed request fora team andbcpeinhardtAugust 25, 2025 14:03
Copy link
Contributor

@buenos-nachosbuenos-nachos left a comment

Choose a reason for hiding this comment

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

Looks good! Just had a few small suggestions

level:"info",
output:line,
source_id:MockWorkspaceAgentLogSource.id,
created_at:newDate().toISOString(),
Copy link
Contributor

Choose a reason for hiding this comment

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

Just to be on the safe side, do we want to hard-code the date here, sincenew Date() would create a non-deterministic value for each story run?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Good catch!

Your task will be running in a few moments
</div>
</header>
<sectionclassName="flex-1 p-16 overflow-y-auto">
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason for theflex-1? I wouldn't expect a page-level component to need to worry about arbitrarily growing or shrinking

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

That is true

<h3className="m-0 font-medium text-content-primary text-xl">
Starting your workspace
</h3>
<divclassName="text-content-secondary">
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we swap thisdiv for ap?

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Sure!


useEffect(()=>{
if(listRef.current){
listRef.current.scrollToItem(logs.length-1,"end");
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you know what the scroll behavior is for the React Window component? As in, do you know if the scroll is instant, or if it does an animation?

Because if it's instant, we could swap inuseLayoutEffect to reduce any risk of screen flickering

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

It is instant, and we can move to useuseLayoutEffect for sure.

<h3className="m-0 font-medium text-content-primary text-xl">
Running startup scripts
</h3>
<divclassName="text-content-secondary">
Copy link
Contributor

Choose a reason for hiding this comment

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

Think we could use ap here, too

BrunoQuaresma reacted with thumbs up emoji
@BrunoQuaresmaBrunoQuaresma merged commit59525f8 intomainAug 26, 2025
27 checks passed
@BrunoQuaresmaBrunoQuaresma deleted the bq/handle-agent-being-ready-for-tasks branchAugust 26, 2025 15:45
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsAug 26, 2025
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@aslilacaslilacAwaiting requested review from aslilac

1 more reviewer

@buenos-nachosbuenos-nachosbuenos-nachos approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@BrunoQuaresmaBrunoQuaresma

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

tasks: ui: show build logs and agent logs in task UI when workspace build is in progress

3 participants

@BrunoQuaresma@buenos-nachos

[8]ページ先頭

©2009-2025 Movatter.jp