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

SyntaxError: Expected ',' or '}' after property value in JSON at position 98 (line 1 column 99) #61

Open
rpressiani opened this issue Nov 9, 2023 · 2 comments
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@rpressiani
Copy link

What happened?

Welcome to Pulumi AI.

Your stack: https://app.pulumi.com/rpressiani/pulumi-ai/dev/resources

What cloud infrastructure do you want to build today?

> an aws s3 bucket
error: SyntaxError: Expected ',' or '}' after property value in JSON at position 98 (line 1 column 99)

Thinking..   t the name of the bucket exports.bucketName = bucket.id; ```

Example

Can be reproduced running pulumi-ai CLI (npx pulumi-ai)

Output of pulumi about

CLI
Version 3.92.0
Go Version go1.21.3
Go Compiler gc

Plugins
NAME VERSION
nodejs unknown

Host
OS darwin
Version 13.3.1
Arch x86_64

Additional context

Started showing this issue today, I was able to run through steps like this before. After submitting the prompt it remains stuck without creating the resource.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@rpressiani rpressiani added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Nov 9, 2023
@AaronFriel AaronFriel removed the needs-triage Needs attention from the triage team label Nov 22, 2023
@AaronFriel
Copy link
Member

AaronFriel commented Nov 22, 2023

I expect this issue is transient, but we should keep an eye on this for when the GPT-4-Turbo model is generally available, as it supposedly is much more reliable at emitting valid JSON.

@AaronFriel
Copy link
Member

Thanks for reporting - @rpressiani have you seen this issue re-occur?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

2 participants