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

Fix inspector warnings #848

Closed
danielrbradley opened this issue May 18, 2022 · 4 comments
Closed

Fix inspector warnings #848

danielrbradley opened this issue May 18, 2022 · 4 comments
Assignees
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@danielrbradley
Copy link
Member

The following warning text is emmitted on provider instantiation, which doesn't actually cause a failure but is not helpful output.

    error: [runtime] Error [ERR_INSPECTOR_NOT_AVAILABLE]: Inspector is not available
        at new NodeError (node:internal/errors:372:5)
        at node:inspector:23:9
        at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:312:7)
        at NativeModule.compileForPublicLoader (node:internal/bootstrap/loaders:252:10)
        at loadNativeModule (node:internal/modules/cjs/helpers:49:9)
        at Function.Module._load (node:internal/modules/cjs/loader:804:15)
        at Module.require (node:internal/modules/cjs/loader:999:19)
        at Module.require (pkg/prelude/bootstrap.js:1812:31)
        at require (node:internal/modules/cjs/helpers:102:18)
        at /snapshot/bin/node_modules/@pulumi/pulumi/runtime/closure/v8Hooks.js:44:62
@danielrbradley danielrbradley self-assigned this May 18, 2022
@danielrbradley danielrbradley added the kind/bug Some behavior is incorrect or out of spec label May 18, 2022
@danielrbradley
Copy link
Member Author

One option is to build the nodejs binary ourselves with the --inspect-brk flag set: vercel/pkg#93 (comment)

@danielrbradley
Copy link
Member Author

danielrbradley commented May 18, 2022

A better option would be to fix the side-effect of importing @pulumi/pulumi which causes the inspector to be pre-loaded on import, even if unused.

Relevant issue: pulumi/pulumi#9375

@danielrbradley
Copy link
Member Author

Waiting on the fix to merge and get released then a simple package upgrade should fix this pulumi/pulumi#9614

@danielrbradley danielrbradley added awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). resolution/fixed This issue was fixed labels May 19, 2022
@danielrbradley
Copy link
Member Author

This is now resolved in 1.0.0-beta.7 by using the latest unreleased version of @pulumi/pulumi. This should be change to version 3.34 once it's released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

1 participant