-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
create-payload-app@beta data seeding broken #8879
Comments
Hey! We couldn't reproduce your issue, I tried:
|
Hey @stevekuznetsov & @r1tsuu! I've also encountered this exact issue during a new project setup today. Steps to Reproduce:
Environment Info
|
Yeah sorry @r1tsuu I don't believe there were any other steps necessary to reproduce this. |
I have had the same issue. It is erroring out at the following stage of the seeding function: I wonder if it is trying to update the related posts data for each post, before it has actually finished populating each post, so it is requesting post1Doc.id, and that doesn't yet exist? When I comment out the three related post updates in the seed function it completes the seeding successfully. I'm also having some slowness issues on even my localhost, so i wonder whether the vercel postgres connection is slow and that is causing the issues. |
Describe the Bug
I created a brand-new app and connected to a Vercel-managed Postgres instance. I opened the admin panel and clicked the seed button. Seeding fails with this error while adding the related posts to the first post:
I've added loads of debugging information and I can fetch all of the posts, cycle through them and execute the meat of the
populateAuthors
logic - fetching the authors - with no issue whatsoever. As far as I can tell there is nothing in theposts
table after this script runs and fails.Link to the code that reproduces this issue
NWACus/website@5a9b520#diff-ec70d248db3563b095d5b75fc9c001d30a315e4b2e01e920277bb1c1261adfe5R238
Reproduction Steps
Which area(s) are affected? (Select all that apply)
area: templates
Environment Info
The text was updated successfully, but these errors were encountered: