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

[ =] info - Generating static pages (0/0) never completes #22994

Closed
tm1000 opened this issue Mar 11, 2021 · 2 comments · Fixed by #22996
Closed

[ =] info - Generating static pages (0/0) never completes #22994

tm1000 opened this issue Mar 11, 2021 · 2 comments · Fixed by #22996
Assignees
Milestone

Comments

@tm1000
Copy link
Contributor

tm1000 commented Mar 11, 2021

What version of Next.js are you using?

npm i next@10.0.9-canary.6

What version of Node.js are you using?

12.19.1

What browser are you using?

Chrome Version 89.0.4389.82

What operating system are you using?

CentOS 7

How are you deploying your application?

next build

Describe the Bug

After running into problems similar in nature to #22815 and #22907 I upgraded to 10.0.9-canary.6. This seemed to resolve the issue with it blowing when running next build however when it gets to the "Generating static pages" section there are 0 static pages and this seems to cause some sort of infinite loop. I walked away for 45 minutes while it sat there doing [ =] info - Generating static pages (0/0) but nothing changed. I had to abort back to 10.0.7 (before the issues in #22815 and #22907)

Expected Behavior

I'd expect it to be able to complete generating static pages (of which there are none)

To Reproduce

Not sure of the exact steps to reproduce other than what was mentioned in #22815 and #22907

@tm1000 tm1000 added the bug Issue was opened via the bug report template. label Mar 11, 2021
@ijjk ijjk added kind: bug and removed bug Issue was opened via the bug report template. labels Mar 11, 2021
@ijjk ijjk self-assigned this Mar 11, 2021
@tm1000
Copy link
Contributor Author

tm1000 commented Mar 12, 2021

Thanks @ijjk !!!!

@kodiakhq kodiakhq bot closed this as completed in #22996 Mar 12, 2021
kodiakhq bot pushed a commit that referenced this issue Mar 12, 2021
This makes sure we don't trigger the export step if we aren't exporting any static pages during a build. This also adds an invariant to ensure we don't attempt creating a progress with 0 items.

Fixes: #22994
@Timer Timer added this to the iteration 17 milestone Mar 12, 2021
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants