Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Eliminate separate trace file for the GUI #995

Open
CharliePoole opened this issue Aug 30, 2023 · 1 comment
Open

Eliminate separate trace file for the GUI #995

CharliePoole opened this issue Aug 30, 2023 · 1 comment
Labels
Enhancement An improvement to an existing feature Normal Priority Normal priority issue

Comments

@CharliePoole
Copy link
Contributor

As a step toward unified trace output, we can eliminate the separate trace file for the GUI by using the engine's trace instead.

The main issue is that we want trace output to be available as early as possible in startup. So we may need to acquire the engine a bit earlier than we now do.
@CharliePoole CharliePoole added Enhancement An improvement to an existing feature Normal Priority Normal priority issue labels Aug 30, 2023
@CharliePoole CharliePoole added this to the 2.0.0-beta3 milestone Aug 30, 2023
@CharliePoole CharliePoole modified the milestones: 2.0.0-beta3, 2.0.0-beta4 Oct 22, 2023
@CharliePoole CharliePoole modified the milestones: 2.0.0-beta4, 2.0.0 Nov 23, 2023
@CharliePoole CharliePoole modified the milestones: 2.0.0, 2.0.0-beta5 Dec 28, 2023
@CharliePoole CharliePoole removed this from the 2.0.0-beta5 milestone Mar 1, 2024
@CharliePoole
Copy link
Contributor Author

Removed from milestone. Now that InternalTrace is a separate package, this needs more analysis to decide what changes are needed and I'd like to get the milestone out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement An improvement to an existing feature Normal Priority Normal priority issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CharliePoole