EPERM when attempting any operation

[flipphillips]

Using latest build (0.5.0) on M1 macOS.

to replicate

Attempt to verify code, lode library manager, etc, using embeded CLI

expected result

Activity executed

actual result

A system error occurred (EPERM: operation not permitted, chmod '/Users/flip/.vscode/extensions/vsciot-vscode.vscode-arduino-0.5.0-darwin-arm64/assets/platform/darwin-arm64/arduino-cli/arduino-cli.app')

regression

Compiles fine through Arduino IDE.
arduino-cli.app is already executable?

[benmcmorran]

Thanks for the report! I'll start working on a fix for this issue, which looks related to #1584, but in the meantime as a workaround you should be able to manually download Arduino CLI from GitHub, then set arduino.path and arduino.commandPath to point at the downloaded Arduino CLI and ensure arduino.useArduinoCli is true.

[benmcmorran]

@flipphillips I don't currently have M1 hardware to test on, but I wasn't able to reproduce this issue on a x64-based Mac.

• Are you running VS Code under a different user account that you originally used to install the extension?
• Can you check which user is considered the owner of the /Users/flip/.vscode/extensions/vsciot-vscode.vscode-arduino-0.5.0-darwin-arm64/assets/platform/darwin-arm64/arduino-cli/arduino-cli.app file, and what its permissions currently are?

The extension needs to be able to change file permissions on that file at least once because it's not executable by default, but I can add extra logic to not attempt to change executable permissions again if they are already set.

[cliffxzx]

same issue

[flipphillips]

Thanks for the report! I'll start working on a fix for this issue, which looks related to #1584, but in the meantime as a workaround you should be able to manually download Arduino CLI from GitHub, then set arduino.path and arduino.commandPath to point at the downloaded Arduino CLI and ensure arduino.useArduinoCli is true.

In the past, I had downloaded the cli via brew. I wasn't able to get it to work correctly with the plugin, regardless of the path settings in VS Code.

$ arduino-cli config dump
board_manager:
  additional_urls: []
daemon:
  port: "50051"
directories:
  data: /Users/flip/Library/Arduino15
  downloads: /Users/flip/Library/Arduino15/staging
  user: /Users/flip/Documents/Arduino
library:
  enable_unsafe_install: false
logging:
  file: ""
  format: text
  level: info
metrics:
  addr: :9090
  enabled: true
output:
  no_color: false
sketch:
  always_export_binaries: false
updater:
  enable_notification: true

as for the app as installed in the plugin directory, it is very much owned by me, and was executable from the git-go

-rwxr-xr-x@ 1 flip  staff    27M Feb 20 13:41 /Users/flip/.vscode/extensions/vsciot-vscode.vscode-arduino-0.5.0-darwin-arm64/assets/platform/darwin-arm64/arduino-cli/arduino-cli.app*

[benmcmorran]

@flipphillips @cliffxzx I have a new build with the fixes from #1601 ready for testing. If you have time, please download this build artifact, extract it, and then from within VS Code run the "Install from VSIX..." command and select the appropriate platform-specific VSIX file. For M1 Mac, that would be vscode-arduino-darwin-arm64.vsix. The changes in this build will skip attempting to chmod if the executable bit is already set and will provide a better error message if there was a problem setting the executable bit. Let me know if you see any issues and thanks again for your feedback!

[flipphillips]

Absolutely will in a little bit, just in time to show students how to use it :) Update - it's not complaining about some things, but can't do Intellicode for some reason, suggesting it doesn't know where to find anything. But will carry on forward and report back <img width="394" alt="Screenshot 2023-02-22 at 12 49 28 PM" src="https://user-images.githubusercontent.com/671183/220716654-ecbc3915-6fe6-4a9c-9b42-a85301994e8c.png">

[benmcmorran]

Great, thanks for confirming. I'll try to get this fix out soon. IntelliSense only updates after a successful compile, but there may be other things going on that are impacting IntelliSense. We're also planning to overhaul how we get IntelliSense data in a future release.