hang: waiting for bundle read lock

[dckc]

Describe the bug

A dev reports that they're experimenting with changes to the contract in dapp-offer-up. When running yarn test they see and endless series of

bundles/ waiting for bundle read lock: /Users/NNN/projects/learn/demo/contract/bundles/bundle-assetContract-js.lock in /Users/NNN/projects/learn/demo/contract/src/offer-up.contract.js

Steps to reproduce

the above is what we have

Expected behavior

tests should run

Platform environment

not reported

Additional context

• Mar 20 Office Hours: contract meta, zoe trading contraints, orchestration of bitcoin, upgrade-14, ... Agoric/agoric-sdk#9118

cc @kbennett2000 @kriskowal

[dckc]

work-around: remove bundles directory

rm -rf bundles made the symptoms go away

[kriskowal]

The bundle read lock does not exist on the most recent releases of @endo/bundle-source. This might be solved by an upgrade.

[dckc]

ok... let's track this as a dapp issue, then:

• hang: waiting for bundle read lock in yarn test Agoric/dapp-offer-up#71

[dckc]

The bundle read lock does not exist on the most recent releases of @endo/bundle-source.

I'd like to cite evidence of that and close this issue. I looked in the bundle-source changelog without luck.

Ah... I suppose this works:

Replaces the lockfile mechanism with atomic renames.
-- #1732

That suggests it's fixed in v2.80 2023-09-12.