microsoft / microsoft/vscode-java-debug
Please provide instrumentation key
Personne n'a encore pris cette issue.
- Langage dominant
- TypeScript
- Étoiles
- 591
- Forks
- 429
- Merge moyen
- 1 j 9 h
- PR mergées (30 j)
- 19
Description
I'm trying to debug the java-debug server and for that I've launched vscode-java-debug plugin, in which after launching its "Extension Developement Host" I've opened my sample Java project.
But when I'm trying to launch my sample project vscode-java-debug prints out the following:
{affectsConfiguration: ƒ}
Error: Please provide instrumentation key {stack: 'Error: Please provide instrumentation key
at…code-java-debug\\dist\\extension.js:35150:29)', message: 'Please provide instrumentation key'}
arg0: Error: Please provide instrumentation key {stack: 'Error: Please provide instrumentation key\n\tat…code-java-debug\\dist\\extension.js:35150:29)', message: 'Please provide instrumentation key'}
f @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:163:6
e @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:159:26521
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:159:26388
<anonymous> @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\@vscode\extension-telemetry\dist\node\common\baseTelemetrySender.js:97
◀ Promise.catch ▶
instantiateSender @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\@vscode\extension-telemetry\dist\node\common\baseTelemetrySender.js:96:10
updateUserOptIn @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\@vscode\extension-telemetry\dist\node\common\baseTelemetryReporter.js:31
BaseTelemetryReporter @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\@vscode\extension-telemetry\dist\node\common\baseTelemetryReporter.js:18
TelemetryReporter @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\@vscode\extension-telemetry\dist\node\node\telemetryReporter.js:94
initialize @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:53
<anonymous> @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:29
fulfilled @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:5:43
◀ Promise.then ▶
step @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:7:33
<anonymous> @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:8
__awaiter @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:4
initializeFromJsonFile @ f:\projects\smartgit\javaDebug\vscode-java-debug\node_modules\vscode-extension-telemetry-wrapper\lib\src\index.js:25
<anonymous> @ f:\projects\smartgit\javaDebug\vscode-java-debug\src\extension.ts:32:33
<anonymous> @ f:\projects\smartgit\javaDebug\vscode-java-debug\dist\extension.js:16:71
__awaiter @ f:\projects\smartgit\javaDebug\vscode-java-debug\dist\extension.js:12:12
activate @ f:\projects\smartgit\javaDebug\vscode-java-debug\dist\extension.js:46:12
kb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:15214
jb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:14921
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:13079
◀ Promise.then ▶
hb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:13004
fb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:12205
◀ await ▶
actualActivateExtension @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:9402
n @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:4460
m @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:4421
l @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:3877
K0 @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:3804
k @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:3366
j @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:3321
j @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:3013
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:2292
h @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:2280
activateById @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:115:2192
bb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:10628
qb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:16807
◀ await ▶
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:16470
pb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:16458
ob @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:16248
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:18112
◀ Promise.then ▶
tb @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:18098
$startExtensionHost @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:119:22030
processTicksAndRejections @ <node_internals>/internal/process/task_queues:95:5
◀ await ▶
processTicksAndRejections @ <node_internals>/internal/process/task_queues:95:5
◀ await ▶
S @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:115275
Q @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:115055
M @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:114144
L @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:113249
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:112046
B @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:30:746
fire @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:30:964
fire @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:9457
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:175:13296
B @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:30:746
fire @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:30:964
fire @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:32:9457
<anonymous> @ c:\VSCode\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:175:11588
emit @ <node_internals>/events:518:28
MessagePortMain._internalPort.emit @ <node_internals>/electron/js2c/utility_init:2:2949
callbackTrampoline @ <node_internals>/internal/async_hooks:130:17
Starting jdt.ls (syntax) from vscode-java sources
Starting jdt.ls (standard) from vscode-java sources
Cannot update debug settings. s: No delegateCommandHandler for vscode.java.updateDebugSettings {code: -32601, data: undefined, stack: 'Error: No delegateCommandHandler for vscode.j…Trampoline (node:internal/async_hooks:130:17)', message: 'No delegateCommandHandler for vscode.java.updateDebugSettings'}
And in result no debug session starts.
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Commencez par src/extension.ts et l’appel initializeFromJsonFile affiché dans la trace de la pile, puis inspectez le wrapper de télémétrie de l’extension référencé. Reproduisez le lancement de Extension Development Host avec le projet Java d’exemple et suivez l’échec de la clé d’instrumentation. C’est terminé lorsque l’extension s’active sans cette erreur et qu’une session de débogage démarre.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java, typescript, vscode
- Domaine
- devtools
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100