microsoft / microsoft/vscode-java-debug

Add "run as sudo" to launch.json for VSC Java project

Ouverte
#953 2 commentaires 1 réaction 1 personne assignée Voir sur GitHub

@testforstephen y travaille déjà.

Depuis le 28/4/2021.

ai-triaged enhancement feature request launch
Langage dominant
TypeScript
Étoiles
591
Forks
429
Merge moyen
1 j 9 h
PR mergées (30 j)
19

Description

I'm working on the Pi4J project (https://v2.pi4j.com/) to control GPIOs with a Java application. Pi4J uses a native library to communicate with the GPIOs. For some protocols (like I2C) the library needs to be called with "sudo". I know this is a bad idea and should be avoided, and we are looking for an alternative solution, but in the mean-time I found out you can't run or debug a Java application in VSC as sudo.

You could launch VSC itself as sudo, but this gives the following warning, so that's probably even a worse idea ;-)

$ sudo code
You are trying to start Visual Studio Code as a super user which isn't recommended. If this was intended, please specify an alternate user data directory using the `--user-data-dir` argument.
Environment
  • Operating System: Raspberry Pi OS (Linux, Debian)
  • JDK version: OpenJDK 11.0.9.1
  • Visual Studio Code version: 1.53.2
  • Java extension version: Java Extension Pack 0.12.1
  • Java Debugger extension version: 0.31.0
Steps To Reproduce
  1. Create a launch.json file, e.g.
{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "java",
            "name": "Launch CrowPiApp",
            "request": "launch",
            "mainClass": "com.pi4j.example/com.pi4j.example.CrowPiApp",
            "projectName": "pi4j-example-crowpi",
            "args": "-a -p"
        }
    ]
}
  1. It should be possible to add extra setting
    "sudo": true
Current Result

sudo setting not available

Expected Result

sudo true/false can be defined

Additional Informations

The example project is https://github.com/Pi4J/pi4j-example-crowpi

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.