Tracking: Report an Issue link does not work if not logged in to github

Open
  • Is something wrong?
#481 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, typescript, vscode
Domain
developer-experience

Research direction

Reproduce the supplied GitHub issue URL in Chrome while signed out, then locate the code behind the extension's Report an Issue link. Done means the link opens a new issue page instead of the empty result shown in the report.

Written by the indexing model from the issue text.

Description

In Chrome, make sure you're not logged in to github, then paste the following link: https://github.com/Microsoft/vscode-azurearmtools/issues/new?body=%0A%3C!--%20IMPORTANT%3A%20Please%20be%20sure%20to%20remove%20any%20private%20information%20before%20submitting.%20--%3E%0A%0ARepro%20steps%3A%0A%3C!--%20TODO%3A%20Enter%20steps%20to%20reproduce%20issue%20--%3E%0A%0A1.%0A2.%0A%0AAction%3A%20startArmLanguageClient%0AError%20type%3A%20Error%0AError%20Message%3A%20hi%0A%0AVersion%3A%200.5.1-alpha%0AOS%3A%20win32%0AProduct%3A%20Visual%20Studio%20Code%20-%20Insiders%0AProduct%20Version%3A%201.34.0-insider%0ALanguage%3A%20en%0A%0A%3Cdetails%3E%0A%3Csummary%3ECall%20Stack%3C%2Fsummary%3E%0A%0A%60%60%60%0AObject.vscode_azureextensionui_1.callWithTelemetryAndErrorHandlingSync%20(startArmLanguageServer.js%3A17%3A15)%0AObject.callWithTelemetryAndErrorHandlingSync%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A46%3A25)%0AObject.startArmLanguageServer%20(startArmLanguageServer.js%3A16%3A31)%0AAzureRMTools.ensureDeploymentTemplateEventsHookedUp%20(out%2Fsrc%2FAzureRMTools.js%3A226%3A34)%0AObject.%5Banonymous%20(out%2Fsrc%2FAzureRMTools.js%3A128%3A24)%0AObject.callWithTelemetryAndErrorHandlingSync%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A46%3A25)%0AAzureRMTools.updateDeploymentTemplate%20(out%2Fsrc%2FAzureRMTools.js%3A110%3A35)%0Anew%20AzureRMTools%20(out%2Fsrc%2FAzureRMTools.js%3A88%3A18)%0AObject.%5Banonymous%5D%20(out%2Fsrc%2FAzureRMTools.js%3A45%3A44)%0AGenerator.next%20(%5Banonymous%5D)%0A__awaiter%20(out%2Fsrc%2FAzureRMTools.js%3A10%3A71)%0Anew%20Promise%20(%5Banonymous%5D)%0A__awaiter%20(out%2Fsrc%2FAzureRMTools.js%3A6%3A12)%0AObject.%5Banonymous%5D%20(out%2Fsrc%2FAzureRMTools.js%3A41%3A20)%0AObject.%5Banonymous%5D%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A61%3A51)%0AGenerator.next%20(%5Banonymous%5D)%0A__awaiter%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A11%3A71)%0Anew%20Promise%20(%5Banonymous%5D)%0A__awaiter%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A7%3A12)%0AObject.callWithTelemetryAndErrorHandling%20(node_modules%2Fvscode-azureextensionui%2Fout%2Fsrc%2FcallWithTelemetryAndErrorHandling.js%3A58%3A12)%0AObject.%5Banonymous%5D%20(out%2Fsrc%2FAzureRMTools.js%3A40%3A41)%0AGenerator.next%20(%5Banonymous%5D)%0A__awaiter%20(out%2Fsrc%2FAzureRMTools.js%3A10%3A71)%0Anew%20Promise%20(%5Banonymous%5D)%0A__awaiter%20(out%2Fsrc%2FAzureRMTools.js%3A6%3A12)%0AObject.activateInternal%20(out%2Fsrc%2FAzureRMTools.js%3A34%3A12)%0Aactivate%20(main.js%3A24%3A28)%0AFunction._callActivateOptional%20(AppData%2FLocal%2FPrograms%2FMicrosoft%20VS%20Code%20extensionHostProcess.js%3A725%3A689)%0AFunction._callActivate%20(AppData%2FLocal%2FPrograms%2FMicrosoft%20VS%20Code%20extensionHostProcess.js%3A725%3A378)%0Adefine._doActivateExtension.Promise.all.then.e%20(AppData%2FLocal%2FPrograms%2FMicrosoft%20VS%20Code%20extensionHostProcess.js%3A724%3A569)%0A%60%60%60%0A%0A%3C%2Fdetails%3E

EXPECTED: new issue page
ACTUAL:
image

Dominant language
TypeScript
Stars
145
Forks
84
Avg merge
19h 55m
Merged PRs (30d)
17

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-azuretools

All issues in microsoft/vscode-azuretools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.