-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Describe the bug
Called mw container logs <container> for a container with an extensive log file. The command hanged indefinitely.
To Reproduce
- Have a container with a large stdout log
- Run
mw container logs <container> - Wait 😴
Expected behavior
Should work just like in the mStudio UI.
Console logs
Relevant debug log output (note the aborted error after the v2/stacks/:stackId/services/:serviceId/logs request):
mw:api:client:request GET v2/stacks/fafeb305-3310-4726-8169-6f67a57cab3e/services/9f970413-d56c-4459-a015-b0e478a0137f/logs requested with undefined +210ms
follow-redirects options {
[...]
} +209ms
mw:api-retry retrying request after 1 attempts; error: 'aborted' +0ms
The mw:api-retry output then repeats ad infinitem.
Full output with DEBUG=*
mw:api:client:request GET v2/projects/fafeb305-3310-4726-8169-6f67a57cab3e/services requested with undefined +0ms
follow-redirects options {
[...]
} +0ms
mw:api:client:response GET v2/projects/fafeb305-3310-4726-8169-6f67a57cab3e/services responded with '200 OK' [
[...]
mw:api:client:response ] +0ms
mw:api:client:request GET v2/stacks/fafeb305-3310-4726-8169-6f67a57cab3e/services/9f970413-d56c-4459-a015-b0e478a0137f/logs requested with undefined +210ms
follow-redirects options {
[...]
} +209ms
mw:api-retry retrying request after 1 attempts; error: 'aborted' +0ms
mw:api:client:request GET v2/stacks/fafeb305-3310-4726-8169-6f67a57cab3e/services/9f970413-d56c-4459-a015-b0e478a0137f/logs requested with undefined +4s
Environment (please complete the following information):
- OS: macOS 26
- Shell: zsh
- Terminal: iTerm2
- Version (output of
mw --version): @mittwald/cli/1.13.3 darwin-arm64 node-v20.19.3
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels