-
Notifications
You must be signed in to change notification settings - Fork 88
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
CV does not generate #245
Comments
Hi @GurdipS5 I was not able to reproduce this error. Could you please provide the exact versions of node and npm you are using? |
Hi,
NPM is 9.6.7
Nodejs is 18.17.0
…On Sun, Jun 23, 2024 at 4:20 PM Marcin Woś ***@***.***> wrote:
Hi @GurdipS5 <https://github.com/GurdipS5> I was not able to reproduce
this error. Could you please provide the exact versions of node and npm you
are using?
—
Reply to this email directly, view it on GitHub
<#245 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU2JXHB25NE5DZGPLNWESXLZI3RVVAVCNFSM6AAAAABJBKCQESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGAZTQOJRGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
What's your setup?
…On Mon, Jun 24, 2024 at 4:26 PM Gurdip sira ***@***.***> wrote:
Hi,
NPM is 9.6.7
Nodejs is 18.17.0
On Sun, Jun 23, 2024 at 4:20 PM Marcin Woś ***@***.***>
wrote:
> Hi @GurdipS5 <https://github.com/GurdipS5> I was not able to reproduce
> this error. Could you please provide the exact versions of node and npm you
> are using?
>
> —
> Reply to this email directly, view it on GitHub
> <#245 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AU2JXHB25NE5DZGPLNWESXLZI3RVVAVCNFSM6AAAAABJBKCQESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGAZTQOJRGM>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Most testing/ development was done on Mac. I can confirm it also does work on WSL/Ubuntu. On Windows I am able to reproduce the error but it is very inconsistent, sometimes it works and generates PDF, sometime it doesn't 😕. I checked couple of nodejs version and this issue seems to be present in all recent versions. I figured the problem must be with how child process is spawned in nodejs on Windows but I am kinda stuck there. |
I tried this on wsl but no luck. Going to setup a Linux teamcity agent so
the build/this command can run successfully on there.
I love the template though!
…On Tue, Jul 9, 2024 at 7:59 PM Marcin Woś ***@***.***> wrote:
Most testing/ development was done on Mac. I can confirm it also does work
on WSL/Ubuntu. On Windows I am able to reproduce the error but it is very
inconsistent, sometimes it works and generates PDF, sometime it doesn't 😕.
I checked couple of nodejs version and this issue seems to be present in
all recent versions. I figured the problem must be with how child process
is spawned in nodejs on Windows but I am kinda stuck there.
—
Reply to this email directly, view it on GitHub
<#245 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AU2JXHGWSKGTFQJXRAXVB53ZLQXHVAVCNFSM6AAAAABJBKCQESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYGQZTCNBRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Describe the bug
Running the generate-pdf command runs indefinitely.
To Reproduce
Steps to reproduce the behavior:
Execute npm run generate-pdf
D:\Repositories\Portfolio\pages\node_modules\puppeteer-core\src\util\Deferred.ts:34
this.reject(new TimeoutError(opts.message));
^
TimeoutError: Navigation timeout of 30000 ms exceeded
at Timeout. (D:\Repositories\Portfolio\pages\node_modules\puppeteer-core\src\util\Deferred.ts:34:25)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
Expected behavior
The command finishes and cv generated.
Screenshots
If applicable, add screenshots to help explain your problem.
Version:
0.3.0
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: