This message was deleted.

Haven’t seen that. Are you on a different node version than Chris perhaps?

We have not seen that issue. And it's definitely not good. Does it survive a reboot? does it happen on every run (presumably with a different

pulumi#####

pipe)?

I believe we have checked all versions, but I will double check that one

also, do you potentially run any sort of antivirus or other disk-scanning tool?

YES to the antivirus/diskcheck

1. it looks like you're makin a call to getSubnet. Are you making that call directly yourself?

Confirmed. The pipenames are different

i.e. right here: index.ts2630. That's what the callstack seems to indicate, but i just want to check before assuming

yes, lines 31 thru 36 are const subnet = azure.network.getSubnet({ name: config.require('subnet'), virtualNetworkName: config.require('vnet'), resourceGroupName: config.require('vnet-rg'), });

how do you then use that 'const subnet' later in your program?

I dont'. It's leftover code.

well, that could certainly potentially help 😄

this is a working stack I use to try different things

in general though, until we figure out why you're gettin the EBUSY, what we can do is switch away from "synchronous invokes", and move to "async invokes". This will mean that instead of calling just

azure.network.getSubnet({ ... })

we would isntead call

azure.network.getSubnet({...}, { async: true })

.

error: Running program 'C:\work\repos\hondofoozle' failed with an unhandled exception: Error: EBUSY: resource busy or locked, open '\\.\pipe\pulumi4203104520\invoke_req' at Object.openSync (fs.js4483) at Object.tryGetSyncInvokes (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\settings.js16329) at invokeSync (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\invoke.js9536) at Object.invoke (C:\work\repos\hondofoozle\node_modules\@pulumi\pulumi\runtime\invoke.js8424) at Object.getClientConfig (C:\work\repos\hondofoozle\node_modules\@pulumi\core\getClientConfig.ts3168) at Object.<anonymous> (C\work\repos\hondofoozle\index.ts59:28) at Module._compile (internal/modules/cjs/loader.js93630) at Module.m._compile (C\work\repos\hondofoozle\node modules\ts node\src\index.ts439:23) at Module._extensions..js (internal/modules/cjs/loader.js94710) at Object.require.extensions.<computed> [as .ts] (C\work\repos\hondofoozle\node modules\ts node\src\index.ts44

Or you'd need to do:

ok

my guess though is that this might be related to antivirus. it might be seeing us open a connectoin between our processes and it might be scanning it.

ok

LMK if you need any more info or help here.

so run these failed commands azynchronously?

if you do need them, yes.

k, will try.

if antivirus is the cause, let us know.