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

Gen2: Type instantiation is excessively deep and possibly infinite #2262

Closed
2 tasks done
johnpc opened this issue Feb 8, 2024 · 7 comments
Closed
2 tasks done

Gen2: Type instantiation is excessively deep and possibly infinite #2262

johnpc opened this issue Feb 8, 2024 · 7 comments
Assignees
Labels
bug Something isn't working data-schema Gen 2

Comments

@johnpc
Copy link
Contributor

johnpc commented Feb 8, 2024

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

v20.8.1

Amplify CLI Version

0.11.1

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

Describe the bug

With certain data model settings, I encounter a type error Type instantiation is excessively deep and possibly infinite. which causes my build to fail. I've set up a repo with a model that experiences this failure here: https://github.com/johnpc/amplify-demo-data-type-infinite (see repro steps).

Expected behavior

Build succeeds without type error

Reproduction steps

git clone https://github.com/johnpc/amplify-demo-data-type-infinite
cd amplify-demo-data-type-infinite
npm install
npm run build
# build will fail with "Type instantiation is excessively deep and possibly infinite."

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@AnilMaktala AnilMaktala self-assigned this Feb 8, 2024
@AnilMaktala
Copy link
Member

Hey @johnpc , Thank you for reporting this. We are able to replicate this issue by cloning your repo. Hence, marking this as bug for the team to evaluate further.
image

@AnilMaktala AnilMaktala added bug Something isn't working and removed pending-triage labels Feb 8, 2024
@AnilMaktala
Copy link
Member

image

@phani-srikar
Copy link
Contributor

Closing since the fix has been merged in.

@johnpc johnpc reopened this Mar 6, 2024
@johnpc
Copy link
Contributor Author

johnpc commented Mar 6, 2024

I had talked to @iartemiev about this, but the perf improvements in #104 did not resolve my issue.

@johnpc
Copy link
Contributor Author

johnpc commented Mar 6, 2024

actually false alarm, this is fixed in the latest @beta

@johnpc johnpc closed this as completed Mar 6, 2024
@anthonyhoegberg
Copy link

is this fixed in normal stable? im getting the same issue, or is it only fixed in beta for now aswell?

@nam-truong-le
Copy link

I'm facing the same issue:

Bildschirmfoto 2024-11-22 um 14 30 23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working data-schema Gen 2
Projects
None yet
Development

No branches or pull requests

5 participants