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

Running two instances on same laptop #225

Closed
michielbdejong opened this issue May 15, 2024 · 1 comment
Closed

Running two instances on same laptop #225

michielbdejong opened this issue May 15, 2024 · 1 comment

Comments

@michielbdejong
Copy link

I'm trying to run two instances of cabal on the same laptop, but the second one crashes:

npx cabal cabal://628d1d75d1197fe05c650fb6b2d5a90171adb1185c0d89772db758b93803b94b?admin=d431586157ba4ed341883c41054c1a5779388236fe8e4c2736d10f7d2191efa1

/Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/levelup/lib/levelup.js:119
      return callback(new OpenError(err))
                      ^
Error [OpenError]: IO error: lock /Users/michiel/.cabal/v1/archives/628d1d75d1197fd05c650fb6b2d5690171adb5185c0d89772db758b93803b94b/views/LOCK: Resource temporarily unavailable
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/levelup/lib/levelup.js:119:23
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/abstract-leveldown/abstract-leveldown.js:38:14
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/deferred-leveldown/deferred-leveldown.js:31:21
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/abstract-leveldown/abstract-leveldown.js:38:14
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/abstract-leveldown/abstract-leveldown.js:38:14
Emitted 'error' event on LevelUP instance at:
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/levelup/lib/levelup.js:60:19
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/levelup/lib/levelup.js:119:14
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/abstract-leveldown/abstract-leveldown.js:38:14
    [... lines matching original stack trace ...]
    at /Users/michiel/.npm/_npx/bf9e302668aa8d99/node_modules/abstract-leveldown/abstract-leveldown.js:38:14 {
  [cause]: undefined
}

Node.js v20.11.0

When I stop the first one and retry the second one, it succeeds. Is there a way to tell cabal not to use this default global resource?

@michielbdejong
Copy link
Author

Ah, found it! Running both instances with npx cabal --temp cabal://628d1d75d1197fe05c650fb6b2d5a90171adb1185c0d89772db758b93803b94b?admin=d431586157ba4ed341883c41054c1a5779388236fe8e4c2736d10f7d2191efa1 works for this, now I can /join default in both terminal windows and the two can chat with each other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant