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

Permission denied on add-on launch #3

Open
taco-paco opened this issue Mar 2, 2024 · 9 comments
Open

Permission denied on add-on launch #3

taco-paco opened this issue Mar 2, 2024 · 9 comments

Comments

@taco-paco
Copy link
Owner

          Ok, I am able to see the GUI, but when I click start, I get
yarn run v1.22.21
warning package.json: No license field
$ electron dist/main.js
/home/fabijanc/shardlabs/alpaca/dist
[main]:  create-engine-process
[main]:  second start
[main]:  engine-created [ null ]
cat: standard output: Bad file descriptor
[main]:  startDevnet { seed: 20, port: 5050, totalAccounts: 10 }
onEvent: error, Error: internal error in Neon module: called `Result::unwrap()` on an `Err` value: IoError(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })
    at eval (webpack://basic/./node_modules/@taco-paco/alpaca-addon-linux-x64/src/promise.js?:6:9)
    at new Promise (<anonymous>)
    at Object.createPromise (webpack://basic/./node_modules/@taco-paco/alpaca-addon-linux-x64/src/promise.js?:5:12)
    at Devnet.start (webpack://basic/./node_modules/@taco-paco/alpaca-addon-linux-x64/index.js?:20:26)
    at eval (webpack://basic/./app/engine/index.ts?:70:77)
    at step (webpack://basic/./app/engine/index.ts?:36:23)
    at Object.eval [as next] (webpack://basic/./app/engine/index.ts?:17:53)
    at eval (webpack://basic/./app/engine/index.ts?:11:71)
    at new Promise (<anonymous>)
    at __awaiter (webpack://basic/./app/engine/index.ts?:7:12)

Do you want me to post this in a new issue? Should I have devnet globally installed?

Originally posted by @FabijanC in #2 (comment)

@taco-paco
Copy link
Owner Author

@FabijanC Was able to reproduce the error. Recompiled and published new binaries for linux-x64. Pull from the master branch run

yarn
yarn build
yarn start

Let me know if issue still there.

@FabijanC
Copy link
Contributor

FabijanC commented Mar 4, 2024

I pulled and ran all the yarn steps, still getting the same error as originally reported.

@taco-paco
Copy link
Owner Author

taco-paco commented Mar 4, 2024

Did it fetch newer version of alpaca-addon? Can be checked in package.json within node_modules/@taco-paco/alpaca-addon-linux-x64/

@FabijanC
Copy link
Contributor

FabijanC commented Mar 4, 2024

From my package.json:

  "optionalDependencies": {
    "@taco-paco/alpaca-addon-mac-arm64": "^0.0.1",
    "@taco-paco/alpaca-addon-mac-x64": "^0.0.1",
    "@taco-paco/alpaca-addon-win-x64": "^0.0.1",
    "@taco-paco/alpaca-addon-linux-x64": "^0.0.2",
    "@taco-paco/alpaca-addon-linux-arm64": "^0.0.1"
  }

@taco-paco
Copy link
Owner Author

That is correct but i meant node_modules/@taco-paco/alpaca-addon-linux-x64/package.json

@FabijanC
Copy link
Contributor

FabijanC commented Mar 4, 2024

From my node_modules/@taco-paco/alpaca-addon-linux-x64/package.json:

{
    "name": "@taco-paco/alpaca-addon-linux-x64",
    "description": "Rust addon that wraps around starknet-devnet-rs.",
    "author": {
        "name": "Edwin Paco",
        "email": "[email protected]"
    },
    "main": "index.js",
    "version": "0.0.2",
    "os": [
        "linux"
    ],
    "cpu": [
        "x64"
    ],
    "repository": {
        "type": "git",
        "url": "[email protected]:taco-paco/alpaca-addon.git"
    }
}

Also maybe worth mentioning, there is a file node_modules/@taco-paco/alpaca-addon-linux-x64/taco-paco-alpaca-addon-linux-x64-0.0.1.tgz, but no -0.0.2.tgz

@taco-paco
Copy link
Owner Author

Could you try one more thing:
remove dist folder and rerun build again. Maybe existing dist/alpaca.node file isn't replaced

@FabijanC
Copy link
Contributor

FabijanC commented Mar 4, 2024

Tried removing both node_modules and dist, didn't help.

@taco-paco
Copy link
Owner Author

I see. I'm almost done with adding backtraces into the binaries, before that it will be hard to understand where exactly is an issue. Thanks for trying. Will give an update once those binaries are available

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

2 participants