fix: restrict cfn-lint schema update to us-east-1 to avoid pickle error#3901
Merged
fix: restrict cfn-lint schema update to us-east-1 to avoid pickle error#3901
Conversation
cfn-lint -u fails with a multiprocessing pickle error when updating schemas for all regions. Restricting to us-east-1 avoids the issue since schema structure validation doesn't require region-specific schemas. See aws-cloudformation/cfn-lint#4379
roger-zhangg
approved these changes
Apr 2, 2026
reedham-aws
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
cfn-lint -ufails intermittently with a multiprocessing pickle error when updating schemas for all regions:This is a known cfn-lint bug: aws-cloudformation/cfn-lint#4379
Fix
Pass
--regions us-east-1to restrict schema updates to a single region. This avoids the multiprocessing issue since cfn-lint is used here for CloudFormation template structure validation, which doesn't require region-specific schemas.