Skip to content

Fix logs --since for non-follow mode#2170

Merged
jonathan343 merged 1 commit into
masterfrom
fix/logs-since-without-follow
May 6, 2026
Merged

Fix logs --since for non-follow mode#2170
jonathan343 merged 1 commit into
masterfrom
fix/logs-since-without-follow

Conversation

@jonathan343

Copy link
Copy Markdown
Collaborator

Fixes #2144

Overview

This PR fixes chalice logs --since when running without --follow.

Previously, --since was parsed correctly but ignored by the non-follow log retrieval path, causing chalice logs --since ... to return older CloudWatch log events. The follow path worked because it already passed startTime to CloudWatch.

Summary

  • Pass startTime through the iter_log_events() CloudWatch paginator call.
  • Add regression coverage to verify startTime is sent for non-follow log retrieval.
  • Add a jmeslog bugfix entry.

Testing

  • python -m pytest tests/functional/test_awsclient.py -k log tests/unit/test_logs.py

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Honors --since when running chalice logs without --follow by passing
startTime through the CloudWatch log paginator, and adds a regression
test plus jmeslog entry.
@jonathan343 jonathan343 merged commit 1df169c into master May 6, 2026
18 checks passed
@jonathan343 jonathan343 deleted the fix/logs-since-without-follow branch May 6, 2026 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--since option not respected unless --follow is passed as well.

2 participants