Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking: [Library] Deployment Failure Due to Typeguard Version Update #31749

Open
Eva9260 opened this issue Oct 14, 2024 · 5 comments
Open

Tracking: [Library] Deployment Failure Due to Typeguard Version Update #31749

Eva9260 opened this issue Oct 14, 2024 · 5 comments
Labels
@aws-cdk/aws-iam Related to AWS Identity and Access Management effort/medium Medium work item – several days of effort management/tracking Issues that track a subject or multiple issues p2

Comments

@Eva9260
Copy link

Eva9260 commented Oct 14, 2024

Overview

We encountered a deployment failure during our recent deployment caused by an unexpected version change in the typeguard library. Previously, we were using the following set of libraries:

aws-cdk-lib==2.161.1
aws-cdk.aws_scheduler_alpha==2.161.1a0
aws-cdk.aws_scheduler_targets_alpha==2.161.1a0
aws_cdk.aws_glue_alpha==2.161.1a0
aws_cdk.aws_lambda_python_alpha==2.161.1a0
constructs
yamldataclassconfig
yjrtr

This configuration worked fine in previous deployments. However, in the latest deployment, the typeguard version was unexpectedly updated to 4.3.0, causing the following error:

typeguard.TypeCheckError: list did not match any element in the union:
  Sequence[aws_cdk.aws_iam.IManagedPolicy]: item 0 is not compatible with the IManagedPolicy protocol because it has no method named '__jsii_proxy_class__'
  NoneType: is not an instance of NoneType

Link to the service’s CDK Construct Library API reference page.

https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_iam-readme.html

Maturity: CloudFormation Resources Only

Stable

Implementation

The issue was traced back to the version bump of typeguard from 2.13.3 to 4.3.0. We had to manually lock the typeguard version back to 2.13.3 to resolve the issue and successfully complete the deployment.

Action Needed: Update the requirements to lock typeguard to 2.13.3 or ensure compatibility with the latest version of typeguard to prevent future issues.

Issue list

  • Deployment Failure Due to Typeguard Version Update
@Eva9260 Eva9260 added management/tracking Issues that track a subject or multiple issues needs-triage This issue or PR still needs to be triaged. labels Oct 14, 2024
@github-actions github-actions bot added the @aws-cdk/aws-iam Related to AWS Identity and Access Management label Oct 14, 2024
@ashishdhingra
Copy link
Contributor

Internal ticket: P161022461

@ashishdhingra ashishdhingra added p2 effort/medium Medium work item – several days of effort and removed needs-triage This issue or PR still needs to be triaged. labels Oct 14, 2024
@khushail
Copy link
Contributor

we got similar issue reported last week- aws/jsii#4667
Moving the corresponding issue to JSII Repo.

@medley56
Copy link

aws/jsii#4657 is also related

@mrgrain
Copy link
Contributor

mrgrain commented Oct 15, 2024

In jsii, we are mainly tracking this in aws/jsii#4658

@BwL1289
Copy link

BwL1289 commented Nov 1, 2024

Can we please bump typeguard version? See more here: aws/jsii#4658.

CDK pinned to extremely old version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-iam Related to AWS Identity and Access Management effort/medium Medium work item – several days of effort management/tracking Issues that track a subject or multiple issues p2
Projects
None yet
Development

No branches or pull requests

6 participants