Show link to full execution logs when `rockcraft pack --debug` enters debug session
Metadata
Current evaluation
The requested pre-debug-session execution-log link is still not shown; the current path launches the shell after error handling, and useful inner logs are copied only when the outer process exits.
Suggested action: keep open
Reason: @tigarmo's response explicitly acknowledges the problem and explains the outer/inner Rockcraft process behavior; the current lifecycle code still calls handle_runtime_error() and then _launch_shell() before re-raising. The reporter's follow-up that useful inner logs are written only after the debug session shows this remains a valid UX and log-lifecycle issue, although the fix must address log flushing or copying rather than only moving one message.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
15
Complexity:
55
Confidence:
89
Actionability:
82
Issue body
### What needs to get done
When `rockcraft pack --debug` exits in error, provide the user with the link to the full execution log before landing the user in the debug session.
### Why it needs to get done
The current state looks like this:
```
rockcraft pack --debug
'override-prime' in part 'backend' failed with code 1.
Launching shell on build environment...
root@rockcraft-katib-ui-on-amd64-for-amd64-19746510:~/project#
```
The user has no context as to what happened. If they then type `exit` and complete the rockcraft session, they're provided with:
```
2023-11-28 09:13:41.104 Full execution log: '/home/scribs/.local/state/rockcraft/log/rockcraft-20231128-091052.127801.log'
```
This log would be convenient to have when they hit the debug session. Otherwise they don't know what they're debugging, and the logical solution is to run the command once, `exit`, read the log, then relaunch the debug session
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
15
Complexity:
55
Confidence:
89
Actionability:
82
|
keep open | The requested pre-debug-session execution-log link is still not shown; the current path launches the shell after error handling, and useful inner logs are copied only when the outer process exits. | |
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
9
Complexity:
64
Confidence:
88
Actionability:
60
|
keep open | Valid debug UX gap: rockcraft pack --debug drops users into a failed build shell without the host execution-log link; log timing complicates a fix. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
50
Actionability:
60
|
needs triage | Feature request to show full execution log link when `rockcraft pack --debug` enters debug session. Open with no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
20
Staleness:
70
Complexity:
35
Confidence:
60
Support Request:
10
|
needs triage | Feature request: when `rockcraft pack --debug` drops the user into a debug shell after a build failure, also print the full execution log path so the user knows what failed. Maintainer acknowledged the report and explained the outer/inner instance log-copy behavior; no fix has landed. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
10
Confidence:
90
Support Request:
0
|
keep open | Request to print the full execution log path before entering the debug session when rockcraft pack --debug fails. Maintainer acknowledged the UX gap and explained the outer/inner process architecture, but no fix has been implemented in over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | Feature request to display the full execution log path immediately when rockcraft pack --debug fails and drops into a debug shell. Currently unlabelled and awaiting prioritization. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
82
Complexity:
15
Confidence:
85
Support Request:
10
|
keep open | Feature request to display the full execution log path when rockcraft pack --debug fails and drops into a shell. A maintainer acknowledged the UX gap and explained the sandbox architecture, but the improvement remains unimplemented after nearly three years. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.