Hello, one of the recent releases broke 3000 of our stacks https://github.com/pulumi/pulumi/releases/tag/v3.202.0

[components/{go,nodejs}] Send component inputs to be saved in state. This brings NodeJS and Go inline with Python behaviour

caused by

error: pre-step event returned an error: failed to save snapshot: serializaing checkpoint: marshalling checkpoint: json: unsupported value: +Inf
error: update failed

+ snapshotRetentionDays: {
                                  + def      : {
                                      + checks: [
                                      +     [0]: {}
                                        ]
                                      + type  : "number"
                                    }
                                  + format   : <null>
                                  + isFinite : true
                                  + isInt    : false
                                  + maxValue : +Inf
                                  + minValue : 0
                                  + type     : "number"
                                  + ~standard: {
                                      + vendor : "zod"
                                      + version: 1
                                    }
                                }

export abstract class LambdaFunction<Def extends config.ServiceDef> extends pulumi.ComponentResource {
  protected readonly rcName: lib.pulumi.ResourceNameFn;

  fn: aws.lambda.Function;
  role: aws.iam.Role;
  rolePolicy: aws.iam.RolePolicy;

  public readonly region: string;
  public readonly observabilityEnvironment: string;
  protected readonly eventInvokeConfig: aws.lambda.FunctionEventInvokeConfig | undefined;
  protected serviceDef: Def;
  protected args: FunctionArgs<Def>;

  protected constructor(
    name: string,
    args: FunctionArgs<Def>,
    opts?: pulumi.ComponentResourceOptions,
    type?: string,
    extras?: BaseExtras
  ) {
    super(type ?? "org:aws:lambda:Function", name, args, opts);
    // ....
  }}

I can take a look. I'm guessing that's a +Inf is from a float value?

Here’s more info

Def

contains zod type which has a member of

snapshotRetentionDays: z.number().positive(),

Yeh +inf won't JSON marshal by itself, I think we can fix that though

I am not sure how much information you intend to store in the state but it feels like the more information it contains more complicated it becomes to perform a manual surgery

yeh that does repro. We want to store as much of the component inputs in state as we can, A) so we can give users a view of how their components are being used B) So we can diff inputs and run update lifecycle hooks at the right time

Understood! I love lifecycle hooks, the best addition!

Yeh we figured people would like those 😆

🙌

I'll get the inf in state bug fixed as well. Funny that somehow despite accepting full float values over the wire since forever, apparently no ones ever tried to use inf with a custom resource or python component resource (they're always sent their inputs to the engine)