This message was deleted.

sparse-intern-71089

04/30/2019, 5:16 PM

This message was deleted.

full-dress-10026

04/30/2019, 5:25 PM

I have tried deleting node_modules, does not help.

full-dress-10026

04/30/2019, 5:29 PM

It appears to have something to do with Pulumi printing the stack outputs. I commented out all my `export`s and still get the error.

white-balloon-205

04/30/2019, 6:14 PM

Do you have any calls to

JSON.stringify

in your own code?

full-dress-10026

04/30/2019, 6:14 PM

Downgrading to pulumi CLI 0.17.5 does not fix it.

full-dress-10026

04/30/2019, 6:14 PM

white-balloon-205

04/30/2019, 6:16 PM

Is there more detail in the callstack or is that all you get?

full-dress-10026

04/30/2019, 6:17 PM

Copy code

Diagnostics:
  pulumi:pulumi:Stack (fib-fib-dev):
    TypeError: Converting circular structure to JSON
        at stringify (<anonymous>)
        at OutputImpl.<anonymous> (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:102:47)
        at Generator.next (<anonymous>)
        at /home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:20:71
        at new Promise (<anonymous>)
        at __awaiter (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:16:12)
        at exports.Output.promise.then (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:89:70)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:189:7)
    TypeError: Converting circular structure to JSON
        at stringify (<anonymous>)
        at OutputImpl.<anonymous> (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:102:47)
        at Generator.next (<anonymous>)
        at /home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:20:71
        at new Promise (<anonymous>)
        at __awaiter (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:16:12)
        at exports.Output.promise.then (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:89:70)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:189:7)
 
    error: Running program '/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate' failed with an unhandled exception:
    TypeError: Converting circular structure to JSON
        at stringify (<anonymous>)
        at OutputImpl.<anonymous> (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:102:47)
        at Generator.next (<anonymous>)
        at /home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:20:71
        at new Promise (<anonymous>)
        at __awaiter (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:16:12)
        at exports.Output.promise.then (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:89:70)
        at <anonymous>
        at process._tickCallback (internal/process/next_tick.js:189:7)

full-dress-10026

04/30/2019, 6:18 PM

FWIW the previous Pulumi version this stack was using was 0.16.

full-dress-10026

04/30/2019, 6:18 PM

I tried creating an entirely new stack and still received the error.

white-balloon-205

04/30/2019, 6:18 PM

CLI version, or also

@pulumi/pulumi

versions?

white-balloon-205

04/30/2019, 6:19 PM

And you said that this reprod even after removing stack exports?

full-dress-10026

04/30/2019, 6:19 PM

Just did the CLI. Can try both.

full-dress-10026

04/30/2019, 6:19 PM

And yes. I commented out all lines that have

export

white-balloon-205

04/30/2019, 6:20 PM

Which versions of

@pulumi/pulumi

@pulumi/aws

and

@pulumi/awsx

are you using?

full-dress-10026

04/30/2019, 6:20 PM

Copy code

{
  "@pulumi/pulumi": "0.17.8",
  "@pulumi/aws": "0.18.3",
  "@pulumi/awsx": "0.18.3"
}

white-balloon-205

04/30/2019, 6:20 PM

And it works with the old CLI but not the new one? That would be surprising given the error message.

full-dress-10026

04/30/2019, 6:21 PM

No. Downgrading the CLI did not fix the error.

white-balloon-205

04/30/2019, 6:23 PM

Ahh - I see. Do you have any idea what other changes you made recently between when you were not seeing this and when you started seeing it?

full-dress-10026

04/30/2019, 6:24 PM

CLI upgrade and updating from

Copy code

"@pulumi/pulumi": "0.16.14",
"@pulumi/aws": "0.16.7",
"@pulumi/awsx": "0.16.4"

Copy code

"@pulumi/pulumi": "0.17.8",
"@pulumi/aws": "0.18.3",
"@pulumi/awsx": "0.18.3"

full-dress-10026

04/30/2019, 6:25 PM

It only happens with this project - I can run

pulumi up

in other projects.

white-balloon-205

04/30/2019, 6:32 PM

cc @lemon-spoon-91807. My guess is that this is either: https://github.com/pulumi/pulumi-awsx/blob/906696bcdd23cb99f1c6c9d9a1ceb257633dd1bc/nodejs/awsx/apigateway/api.ts#L338 or: https://github.com/pulumi/pulumi-awsx/blob/906696bcdd23cb99f1c6c9d9a1ceb257633dd1bc/nodejs/awsx/ecs/taskDefinition.ts#L77

full-dress-10026

04/30/2019, 6:32 PM

I don't use the former.

lemon-spoon-91807

04/30/2019, 6:32 PM

hey there!

lemon-spoon-91807

04/30/2019, 6:32 PM

i do see

pulumi-fargate

in your path

lemon-spoon-91807

04/30/2019, 6:33 PM

are you not using TaskDefs/Services?

lemon-spoon-91807

04/30/2019, 6:33 PM

there's one thing we can try to help figure this out

full-dress-10026

04/30/2019, 6:33 PM

I am using

awsx.ecs.FargateService

lemon-spoon-91807

04/30/2019, 6:33 PM

then it's quite likely to beTaskDefinition

lemon-spoon-91807

04/30/2019, 6:34 PM

a quick way to find out is to go to that line in your

node_modules/@pulumi...

folder and change it to:

lemon-spoon-91807

04/30/2019, 6:34 PM

.apply(x => JSON.stringify(x))

lemon-spoon-91807

04/30/2019, 6:34 PM

can you try that, and see what callstack you get now

lemon-spoon-91807

04/30/2019, 6:34 PM

also, can you link me to your code that makes the Service

lemon-spoon-91807

04/30/2019, 6:34 PM

we might be able to see a root cause quickly

full-dress-10026

04/30/2019, 6:37 PM

I think I found it. The

portMappings

API used to take a load balancer and now takes a listener. I was still passing the load balancer. Any way to improve that error message?

lemon-spoon-91807

04/30/2019, 6:37 PM

The
portMappings
API used to take a load balancer

lemon-spoon-91807

04/30/2019, 6:37 PM

!!!

lemon-spoon-91807

04/30/2019, 6:37 PM

well, 1. that shouldn't have ever worked 😄

lemon-spoon-91807

04/30/2019, 6:37 PM

2.... i'm shocked TS allowed that

lemon-spoon-91807

04/30/2019, 6:37 PM

can you send me your code?

lemon-spoon-91807

04/30/2019, 6:37 PM

i need to try to repro this

full-dress-10026

04/30/2019, 6:38 PM

I'm fairly certain it worked because the stack was working on 0.16. Sure.

lemon-spoon-91807

04/30/2019, 6:38 PM

because from TS's perspective it has this sig

lemon-spoon-91807

04/30/2019, 6:38 PM

Copy code

portMappings?: (pulumi.Input<aws.ecs.PortMapping> | ContainerPortMappingProvider)[];

lemon-spoon-91807

04/30/2019, 6:38 PM

and a LoadBalancer is definitely not either of those!

lemon-spoon-91807

04/30/2019, 6:39 PM

so i have no idea how TypeSCript even compiled this without issue!

full-dress-10026

04/30/2019, 6:40 PM

Yep - changing to a listener fixed this.

lemon-spoon-91807

04/30/2019, 6:41 PM

where's the line that you had the LB passed in on?

full-dress-10026

04/30/2019, 6:41 PM

lemon-spoon-91807

04/30/2019, 6:43 PM

oh... i see because you basically are using hte any-type

lemon-spoon-91807

04/30/2019, 6:43 PM

so TypeScript couldn't even complain...

lemon-spoon-91807

04/30/2019, 6:43 PM

hrmm

lemon-spoon-91807

04/30/2019, 6:43 PM

we can def be more aggressive at trying to weed out bad data. but it's a harder problem in that more or less bad data can be everywhere

full-dress-10026

04/30/2019, 6:43 PM

Is there a better way to write that? I need to dynamically create the

FargateServiceArgs

lemon-spoon-91807

04/30/2019, 6:43 PM

and we want to leverage TS pretty heavily to catch more of the stuff.

full-dress-10026

04/30/2019, 6:43 PM

Seems like a common case.

lemon-spoon-91807

04/30/2019, 6:44 PM

in this case, defining it as:

lemon-spoon-91807

04/30/2019, 6:45 PM

`let fibContainerMap: Record<string, aws.ecs.Container>> = {}

lemon-spoon-91807

04/30/2019, 6:45 PM

then TS will actually typecheck it and catch those issues

lemon-spoon-91807

04/30/2019, 6:45 PM

(note: this is def not your fault)

lemon-spoon-91807

04/30/2019, 6:45 PM

you did something totally reasonable and things blew up.

lemon-spoon-91807

04/30/2019, 6:46 PM

bbiab

full-dress-10026

04/30/2019, 6:49 PM

Gotcha - ok. I'll add that type hint.

lemon-spoon-91807

05/01/2019, 12:44 AM

This change will also at least help a bit in the future: https://github.com/pulumi/pulumi-awsx/pull/260

lemon-spoon-91807

05/01/2019, 12:45 AM

as it will give you a callstack that shows you're inside the TaskDef code, not in some random Ouput callstack.

lemon-spoon-91807

05/01/2019, 12:45 AM

(or, at least, it will help us if we see the callstack) 🙂

full-dress-10026

05/01/2019, 12:45 AM

Thanks!

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.