Fix file watcher infinite loops and improve logging for local invoke #8196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The AWS SAM CLI file watcher was experiencing infinite loops during local development, particularly with LoopBack applications that create temporary
.sandbox
directories. This caused:Solution
This PR implements two key improvements:
1. Configurable Ignore Patterns for File Watching
SAM_CLI_FILE_OBSERVER_IGNORE_PATTERNS
(default: enabled)Default ignore patterns:
2. Enhanced Lock Acquisition Logging
Usage
Default behavior (recommended):
sam local start-api
Disable ignore patterns for debugging:
SAM_USE_IGNORE_PATTERN =false sam local start-api
Windows Installation Instructions
For Windows users experiencing file watcher performance issues:
Install from source (recommended for testing):
git clone https://github.com/aws/aws-sam-cli.git cd aws-sam-cli
make init
./Make -Init
Verify the fix is working:
Environment variable usage in Windows:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.