Closed itexpertshire closed 2 years ago
fabioz
commented
2 years ago Humm, I think that the post install script would be: rfbrowser init
If you remove that line (actually the whole rccPostInstall: block) from the conda.yaml and restart VSCode, does it work?
itexpertshire
commented
2 years ago It failed with below error message after long time.
Command ["rfbrowser" "init"] at "c:\\ProgramData\\robocorp\\ht\\h5fdbf96_44412bd2016a11t":
Installing node dependencies...
Installing rfbrowser node dependencies at c:\programdata\robocorp\ht\h5fdbf96_44412bd2016a11t\lib\site-packages\Browser\wrapper
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN old lockfile FetchError: request to https://registry.npmjs.org/@babel%2fhighlight failed, reason: self signed certificate in certificate chain
npm WARN old lockfile at ClientRequest.<anonymous> (c:\ProgramData\robocorp\ht\h5fdbf96_44412bd2016a11t\node_modules\npm\node_modules\minipass-fetch\lib\index.js:110:14)
npm WARN old lockfile at ClientRequest.emit (node:events:526:28)
npm WARN old lockfile at TLSSocket.socketErrorListener (node:_http_client:442:9)
npm WARN old lockfile at TLSSocket.emit (node:events:538:35)
npm WARN old lockfile at emitErrorNT (node:internal/streams/destroy:157:8)
npm WARN old lockfile at emitErrorCloseNT (node:internal/streams/destroy:122:3)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:83:21)
npm WARN old lockfile Could not fetch metadata for @babel/highlight@7.13.8 FetchError: request to https://registry.npmjs.org/@babel%2fhighlight failed, reason: self signed certificate in certificate chain
npm WARN old lockfile at ClientRequest.<anonymous> (c:\ProgramData\robocorp\ht\h5fdbf96_44412bd2016a11t\node_modules\npm\node_modules\minipass-fetch\lib\index.js:110:14)
npm WARN old lockfile at ClientRequest.emit (node:events:526:28)
npm WARN old lockfile at TLSSocket.socketErrorListener (node:_http_client:442:9)
npm WARN old lockfile at TLSSocket.emit (node:events:538:35)
npm WARN old lockfile at emitErrorNT (node:internal/streams/destroy:157:8)
npm WARN old lockfile at emitErrorCloseNT (node:internal/streams/destroy:122:3)
npm WARN old lockfile at processTicksAndRejections (node:internal/process/task_queues:83:21) {
npm WARN old lockfile code: 'SELF_SIGNED_CERT_IN_CHAIN',
npm WARN old lockfile errno: 'SELF_SIGNED_CERT_IN_CHAIN',
npm WARN old lockfile type: 'system'
npm WARN old lockfile }Humm, I think that the post install script would be:
rfbrowser initIf you remove that line (actually the whole
rccPostInstall:block) from theconda.yamland restart VSCode, does it work?
Yes, it's the issue with rfbrowser library. After removing this, it worked fine.
kariharju
commented
2 years ago Hi @itexpertshire,
This error is not coming from the extension, but the NodeJS steps that are required by the Playwright setup.
The error looks like you are behind a network proxy that breaks the HTTPS certificate chain, so your HTTPS_PROXY setting is probably pointing to a URL that starts with http://...
NodeJS has a way to ignore the certificate checking by setting an environment variable:
NODE_TLS_REJECT_UNAUTHORIZED = 0
..which should help your case.
Describe the bug Robocorp activation step is not completing and running post install scripts phase forever.
To Reproduce Steps to reproduce the behavior:
Expected behavior It should complete and allow me to run sample tasks.robot file
Screenshots
Versions:
Logs Add the logs obtained when reproducing the issue. Output> Robocorp Code
Output>Robot Framework