Error: Lock file is already being held

[autonome]

Now that the service is back up (#115), I'm seeing a new error.

(node:21553) UnhandledPromiseRejectionWarning: Error: Lock file is already being held

I see the log below, and long hangs periodically during execution, then more of the same errors, and then I force kill it.

Log:

twerkworker-5935:buttons dietrich$ npm-ipfs i hypersimple
superagent: Enable experimental feature http2
👩‍🚀 Starting local proxy
🚀 Server running on port 63344
🎁 Installing dependencies with /Users/dietrich/.npm-packages/bin/npm
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs22622a40
Swarm listening on /ip4/127.0.0.1/tcp/63347/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4
Swarm listening on /p2p-circuit/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4
Swarm listening on /p2p-circuit/ip4/127.0.0.1/tcp/63347/ipfs/QmdUbfvZohU6F6e24MJU8R8NEhRFZPq1rGyP78uy8nsGw4
🗂️ Loading registry index from https://registry.js.ipfs.iossion 2681a7af22622a40
☎️ Dialling registry mirror /ip4/35.178.192.119/tcp/10029/ipfs/Qmf5Rpj2FVVFnvReM7sdjrBTroVhwQSjUrkPbzo5XoVuiE,/dns4/registry.js.ipfs.io/tcp/10029/ipfs/Qmf5Rpj2FVVFnvReM7sdjrBTro
VhwQSjUrkPbzo5XoVuiE
📱️ Connected to registryrollbackFailedOptional: verb npm-session 2681a7af22622a40
📄 GET /hypersimple 200 8569msckFailedOptional: verb npm-session 2681a7af22622a40
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfsple@0.4.0 checking installable status
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rej
ecting a promise which was not handled with .catch(). (rejection id: 1)
(node:21161) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process
with a non-zero exit code.
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rej
ecting a promise which was not handled with .catch(). (rejection id: 2)
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rej
ecting a promise which was not handled with .catch(). (rejection id: 3)
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rej
ecting a promise which was not handled with .catch(). (rejection id: 4)
⸨░░░░░░░░░░░░░░░░░░⸩ ⠧ fetchMetadata: sill resolveWithNewModule hypersimple@0.4.0 checking installable status

(A COUPLE MINUTES OF HANG)

😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfs
😈 Spawning an in-process IPFS node using repo at /Users/dietrich/.jsipfsple@0.4.0 checking installable status
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
(node:21161) UnhandledPromiseRejectionWarning: Error: Lock file is already being heldcking installable status
at options.fs.stat (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/proper-lockfile/lib/lockfile.js:68:47)
at callback (/Users/dietrich/.npm-packages/lib/node_modules/ipfs-npm/node_modules/graceful-fs/polyfills.js:295:20)
at FSReqWrap.oncomplete (fs.js:155:5)
(node:21161) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
⸨░░░░░░░░░░░░░░░░░░⸩ ⠧ fetchMetadata: sill resolveWithNewModule hypersimple@0.4.0 checking installable status

(MORE HANG)

[achingbrain]

Are you running an IPFS daemon at the same time?

[autonome]

I was... should I not be?

…

On Thu, Sep 12, 2019 at 12:55 AM Alex Potsides ***@***.***> wrote: Are you running an IPFS daemon at the same time? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#116?email_source=notifications&email_token=AAAMHN7QNHH72RDJI32EWZDQJHYWBA5CNFSM4IV7BJP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6RAD5Y#issuecomment-530711031>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAMHN5DUYDOOBKWXHKMMNLQJHYWBANCNFSM4IV7BJPQ> .

[achingbrain]

No, they'll fight over the repo and you'll see lockfile errors (as well you are). Eventually you should be able to get npm-ipfs to connect to an existing daemon - see #105

[autonome]

Looks like that'll be resolved(-ish) by #113.

Using npm-on-ipfs is pretty much not possible until that's fixed, afaict?