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

Unable to open Release Notes - cannot read property replace of null #15183

Closed
normalser opened this issue Nov 8, 2016 · 5 comments
Closed

Unable to open Release Notes - cannot read property replace of null #15183

normalser opened this issue Nov 8, 2016 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded

Comments

@normalser
Copy link

  • VSCode Version: Code - Insiders 1.8.0-insider (44901c2, 2016-11-08T07:55:03.135Z)
  • OS Version: Darwin x64 16.1.0

Steps to Reproduce:

  1. Got "New update available" top bar
  2. Clicked Read Release Notes

image

workbench.main.js:92 Unable to open 'Release Notes: VSCode': Cannot read property 'replace' of null
Please report this to https://github.com/chjj/marked..: Error: Unable to open 'Release Notes: VSCode': Cannot read property 'replace' of null
Please report this to https://github.com/chjj/marked..
    at t.doHandleSetInputError (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:15892)
    at file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:15498
    at then (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:32:17435)
    at t.doSetInput (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:15246)
    at file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:13133
    at then (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:32:18059)
    at t.doOpenEditor (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:13105)
    at t.openEditor (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:118:12384)
    at e.doOpenEditor (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:105:13762)
    at e.openEditor (file:////Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:105:13192)
@joaomoreno
Copy link
Member

joaomoreno commented Nov 9, 2016

This was fixed by my latest merge from the update branch.

Great catch, no one actually found this for quite some time.

@joaomoreno joaomoreno added the bug Issue identified by VS Code Team member as probable bug label Nov 9, 2016
@ramya-rao-a ramya-rao-a added the verified Verification succeeded label Dec 9, 2016
@ad05bzag
Copy link

I got the same error today:

VS info:
Version 1.7.2
Commit 7ba55c5
Date 2016-11-21T22:14:18.217Z
Shell 1.3.8
Renderer 52.0.2743.82
Node 6.5.0

OS:
4.4.0-51-generic #72~14.04.1-Ubuntu SMP Thu Nov 24 19:22:30 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

steps to reproduce:

  1. Got "New update available" top bar
  2. Clicked Read Release Notes

@gregzuro
Copy link

gregzuro commented Feb 8, 2017

Got this today:

Version 1.10.0-insider
ad605ea
2017-02-06T07:02:27.982Z

on OSX 10.12.3

Just clicked "Read Release Notes"

Have been getting this error with each new release.

@joaomoreno
Copy link
Member

@gregzuro Update to the latest. 👍

@bbonczek
Copy link

bbonczek commented Feb 23, 2017

Got this today on Windows 8.1. My spec:

image

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants