Skip to content

[WIP] Copilot Request#9959

Draft
Copilot wants to merge 1 commit into
mainfrom
copilot/fix-6844498-106580024-99046813-9fa3-4a9b-aa99-196e1f9fd84c
Draft

[WIP] Copilot Request#9959
Copilot wants to merge 1 commit into
mainfrom
copilot/fix-6844498-106580024-99046813-9fa3-4a9b-aa99-196e1f9fd84c

Conversation

Copilot AI commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.


This section details on the original issue you should resolve

<issue_title>[containerapp] Container Apps logs in follow mode exit after not receiving new logs for a few minutes</issue_title>
<issue_description>Source: Azure/azure-cli#33487 (by @catmanjan)
Affected extension: containerapp (src/containerapp/)


<<UNTRUSTED:issue-33487>>

Issue Azure/azure-cli-extensions#33487 (by @catmanjan)

Title

Container Apps logs in follow mode exit after not receiving new logs for a few minutes

Body

Describe the bug

Similar to Azure/azure-cli#28267

I am following container logs like so

az containerapp logs show --n cmlinux -g cmlinux --follow --tail 30

The container is intentionally quiet in logging, after approximately 3 minutes the log command just stops

Related command

az containerapp logs show --n cmlinux -g cmlinux --follow --tail 30

Errors

N/A

Issue script & Debug output

az containerapp logs show --n cmlinux -g cmlinux --follow --tail 30

{"TimeStamp": "2026-06-03T04:45:59.2214149+00:00", "Log": "F 013c:fixme:file:NtFsControlFile FSCTL_PIPE_IMPERSONATE: impersonating self"}
{"TimeStamp": "2026-06-03T04:48:25.34888", "Log": "No logs since last 60 seconds"}
{"TimeStamp": "2026-06-03T04:49:25.74618", "Log": "No logs since last 60 seconds"}
{"TimeStamp": "2026-06-03T04:50:26.18445", "Log": "No logs since last 60 seconds"}
{"TimeStamp": "2026-06-03T04:51:26.71221", "Log": "No logs since last 60 seconds"}
sysadmin@nuc:~$

Expected behavior

Should tail forever

Environment Summary

azure-cli 2.87.0

Can also reproduce it in browser

Additional context

No response

Comments

Comment by @yonzhan

Thank you for opening this issue, we will look into it.
<<END:issue-33487>></issue_description>

Comments on the Issue (you are @copilot in this section)

@azclibot Hi Copilot! Please investigate and fix this bug in the `containerapp` extension.

Issue summary: az containerapp logs show --follow exits after a few minutes of inactivity instead of tailing indefinitely.

Failing command:

az containerapp logs show --n cmlinux -g cmlinux --follow --tail 30

Observed behavior: After ~3 minutes with no new log output, the command exits. The output shows repeated "No logs since last 60 seconds" messages until the command terminates.

Expected behavior: The --follow flag should keep the log stream open indefinitely, regardless of inactivity periods.

CLI version: azure-cli 2.87.0

Notes:

Please look at the containerapp extension's log follow implementation and fix the idle timeout / reconnection behavior so that --follow truly tails forever.


Posted by agent-assist (autonomous bug-fix pipeline).</comment_new>

@azure-client-tools-bot-prd

azure-client-tools-bot-prd Bot commented Jun 20, 2026

Copy link
Copy Markdown
️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi @copilot,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

@yonzhan

yonzhan commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

Copilot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto-Assign Auto assign by bot ContainerApp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[containerapp] Container Apps logs in follow mode exit after not receiving new logs for a few minutes

3 participants