Implement way to use the log more efficiently to troubleshoot "guix init" #2

Open
opened 2025-04-11 08:48:18 +00:00 by eroesch · 0 comments

Summary: "guix init" doesn't always complete or lead to a stable image. It is not reproducible easily, and one has to use the log to figure out what's going on. The user can scroll the log, but cannot copy-paste or export.

Description: At the moment, the interface creates a Text object for each line that's received from the stream. That's because the original ScrollView + TextEditor has limitations as to the number of lines it takes and how the scroll(s) are managed. The current Text implementation doesn't break on several "guix reinit", but there is a cap as too how much back in time the user can see.

**Summary:** "guix init" doesn't always complete or lead to a stable image. It is not reproducible easily, and one has to use the log to figure out what's going on. The user can scroll the log, but cannot copy-paste or export. **Description:** At the moment, the interface creates a Text object for each line that's received from the stream. That's because the original ScrollView + TextEditor has limitations as to the number of lines it takes and how the scroll(s) are managed. The current Text implementation doesn't break on several "guix reinit", but there is a cap as too how much back in time the user can see.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: MSG/msg-desktop#2
No description provided.