primordic/IssueDupesLite huggingface dataset:
Repository: VSCodeVim/Vim

Issue #854: Mapping capslock to esc has issues
Created: 2016-10-06T20:49:46Z
Please thumbs-up 👍 this issue if it personally affects you! You can do this by clicking on the emoji-face on the top right of this post. Issues with more thumbs-up will be prioritized.

What did you do?
Attempted to map the caps lock key to the escape key, via the below in keybindings.json
{"key": "capslock", "command": "extension.vim_escape"} 
Note: I also tried via the below, using "capslock" and "", but this had no effect, as it appears from the codebase <CapsLock> isn't recognized notation.
{
    "vim.insertModeKeyBindings": [
        {
            "before": ["capslock"],
            "after": ["<Esc>"]
        }
    ]
}
What did you expect to happen?
This should allow me to exit insert mode via the close-by caplock key.
What happened instead?
It does kinda work via the first form above, however if also toggles caps lock on/off, which makes it impossible to use (as every key press is then a capital after exiting insert mode). Preferably the "vim.insertModeKeyBindings" would work, and recognize the capslock key and intercept it - preventing it from toggling caps-lock.
Technical details:

VSCode Version: 1.5.3
VsCodeVim Version: 0.3.0
OS: Windows 10

Duplicate issue #4612: Remap keys not working
Created: 2020-03-01T03:19:34Z
I'm using VSCodium and VSCodeVim both latest stable version in Arch Linux
Short report: Global keyboard rebinding doesn't work on VSCodeVim.
Full report:
I swapped ESC and Caps Lock with this command line
linux> setxkbmap -option caps:swapescape
The swapping works just fine with Arch Linux in general and specifically VSCodium, but when it comes to Vim the swapping didn't work, which mean I still have to press ESC to return to Normal Mode, and that's eqivalent to Caps Lock to my machine.
The main reason I swapped them is to switch mode more comfortably. Is there any way to fix this problem?

Closing comment (2020-03-05T05:10:19Z): sorry just realised this is a duplicate of #854 and #2859 and is actually a vscode issue microsoft/vscode#23991 with a workaround at microsoft/vscode#23991 (comment)
Repository: VSCodeVim/Vim

Issue #1017: `S`/`cc` doesn't auto indent on empty line
Created: 2016-10-31T15:27:45Z
When your in Normal mode and your on an empty line and the cursor is at the very left, pressing 'S' in normal Vim auto indents the line and goes into insert mode, but VS Vim doesn't seem to indent at all.
Technical details:

VSCode Version: 1.6.1
VsCodeVim Version: 0.4.0
OS: OSX El capitan

What happened:

Typing cc when cursor is at col 0 and in block on empty line: Jumping to input mode, but won't indent correctly
Typing cc when cursor is at col 2 (or any col): Removes line and ends up at col 0 with no indentation
Typing cc when cursor is at col 0 but there is valid code on line that is inside a block: Removes line as it should do, but cursor ends at col 0 with trailing whitespace
Typing cc when cursor is at col >2 (in block, line with valid code, cursor on code): Removes line of code and indents correctly ✅

Here all of those scenarios in a GIF (with tab width of 3 instead of 2)

Contributed by @lumio at #1828.

What did you expect to happen: Typing cc will always clear the line, indents it and cursor jumps to end of line.
How to reproduce it: See above, but typically typing cc on different col positions.

Duplicate issue #1828: Typing cc clears line but won't position cursor and sometimes won't indent correctly
Created: 2017-06-12T16:55:58Z
Click thumbs-up 👍 on this issue if you want it!
Click confused 😕 on this issue if not having it makes VSCodeVim unusable.

The VSCodeVim team prioritizes issues based on reaction count.

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Environment: Mac OS, Node JS

EditorConfig: 0.9.3
ESLint: 1.2.11
Vim: 0.8.5



VSCode Version: 1.13.0
VsCodeVim Version: 0.8.5
OS: Mac OS 10.12.5

What happened:

Typing cc when cursor is at col 0 and in block on empty line: Jumping to input mode, but won't indent correctly
Typing cc when cursor is at col 2 (or any col): Removes line and ends up at col 0 with no indentation
Typing cc when cursor is at col 0 but there is valid code on line that is inside a block: Removes line as it should do, but cursor ends at col 0 with trailing whitespace
Typing cc when cursor is at col >2 (in block, line with valid code, cursor on code): Removes line of code and indents correctly ✅

Here all of those scenarios in a GIF (with tab width of 3 instead of 2)


What did you expect to happen: Typing cc will always clear the line, indents it and cursor jumps to end of line.
How to reproduce it: See above, but typically typing cc on different col positions.

Closing comment (2017-06-14T01:39:23Z): This is a duplicate of #1017 but has much better detail.
I'm going to close this issue in favor of that one, but copy your feedback over into the other thread.
Repository: VSCodeVim/Vim

Issue #5209: Failed to handle key=u. HistoryTracker:Tried to modify history at index -1
Created: 2020-09-23T00:45:13Z
To Reproduce
Steps to reproduce the behavior:

use vscode-insiders
install vim plugin (vscodevim.vim)
install .NET notebooks
create a .dib file
create multiple code cells
add content to cells
go to a previous cell and press u in command mode (undo in vim)
see error

VSCodeVim version: 1.17.0
Stack trace
Error: Failed to handle key=u. HistoryTracker:Tried to modify history at index -1
	at h.get currentHistoryStep [as currentHistoryStep] (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:508876)
	at h.setLastHistoryEndPosition (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:516428)
	at F.runAction (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:478631)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async F.handleKeyAsAnAction (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:474707)
	at async F.handleKeyEvent (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:471516)
	at async Object.promise (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:235653)
	at async Object.runTasks (/Users/eper363/.vscode-insiders/extensions/vscodevim.vim-1.17.0/out/extension.js:9:621827)

Duplicate issue #6072: Failed to handle key=i. HistoryTracker:Tried to modify history at index -1
Created: 2021-01-31T06:49:50Z
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

VSCodeVim version: 1.18.5
Stack trace
Error: Failed to handle key=i. HistoryTracker:Tried to modify history at index -1
	at h.get currentHistoryStep [as currentHistoryStep] (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:200309)
	at h._isDocumentTextNeeded (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:203302)
	at h.addChange (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:203495)
	at F.handleKeyAsAnAction (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:169454)
	at F.handleKeyEvent (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:167823)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async Object.promise (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:9:216269)
	at async Object.runTasks (/home/chen/.vscode/extensions/vscodevim.vim-1.18.5/out/extension.js:11:327644)

Closing comment (2021-02-06T05:58:19Z): Duplicate of #5209
Repository: VSCodeVim/Vim

Issue #5180: getLineLength() called with out-of-bounds line 223
Created: 2020-09-12T23:52:52Z
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

VSCodeVim version: 1.16.3
Stack trace
Error: getLineLength() called with out-of-bounds line 223
    at Function.getLineLength (/home/saulo/.vscode/extensions/rebornix.999-test-vim-1.16.3/out/extension.js:1:22162)
    at l.getLineEnd (/home/saulo/.vscode/extensions/rebornix.999-test-vim-1.16.3/out/extension.js:1:13712)
    at F.handleSelectionChange (/home/saulo/.vscode/extensions/rebornix.999-test-vim-1.16.3/out/extension.js:9:468948)
    at Object.promise (/home/saulo/.vscode/extensions/rebornix.999-test-vim-1.16.3/out/extension.js:9:235726)
    at Object.runTasks (/home/saulo/.vscode/extensions/rebornix.999-test-vim-1.16.3/out/extension.js:9:620104)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)

Duplicate issue #5798: Failed to handle key=<BS>. getLineLength() called with out-of-bounds line 221
Created: 2020-12-01T15:11:17Z
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

VSCodeVim version: 1.17.2
Stack trace
Error: Failed to handle key=<BS>. getLineLength() called with out-of-bounds line 221
	at Function.getLineLength (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:1:22225)
	at l.getUpWithDesiredColumn (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:1:11622)
	at l.getLeftThroughLineBreaks (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:1:10872)
	at /home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:475270
	at Array.map (<anonymous>)
	at F.runAction (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:475217)
	at F.handleKeyAsAnAction (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:474805)
	at F.handleKeyEvent (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:471614)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:94:5)
	at async Object.promise (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:231560)
	at async Object.runTasks (/home/gcameron/.vscode/extensions/vscodevim.vim-1.17.2/out/extension.js:9:621914)

Closing comment (2020-12-05T21:53:56Z): Duplicate of #5180
Repository: VSCodeVim/Vim

Issue #2696: Add support for new grid layout with splits
Created: 2018-05-30T19:43:55Z
** Feature request **
Split command should support the upcoming grid layout feature from VsCode.
VsCode issue and PR:

microsoft/vscode#14909
microsoft/vscode#49599

Duplicate issue #2810: :sp should split horizontally
Created: 2018-07-05T22:47:19Z
FEATURE REQUEST
Now that VS Code 1.25 is out with the grid editor layout feature (https://code.visualstudio.com/updates/v1_25#_grid-editor-layout) it's now possible to split windows "horizontally".  Doing a :sp in Vim mode still splits vertically though.  Ideally I'd like this command to match what happens in Vim.
What happened:
:sp still splits "vertically" -- ie creates a new column
What did you expect to happen:
It should split "horizontally" -- ie create a new row
How to reproduce it (as minimally and precisely as possible):
In NORMAL mode type :sp.  Note that instead of splitting the current buffer horizontally, it opens a new buffer to the left.
Environment:


Extension Name: vim
Extension Version: 0.14.1
OS Version: Darwin x64 16.7.0
VSCode version: 1.25.0

Closing comment (2018-07-06T05:37:50Z): Duplicate of #2696
Repository: VSCodium/vscodium

Issue #1032: Double-clic on title bar doesn't maximise window
Created: 2022-04-02T10:45:09Z
Describe the bug
Since VSCodium version 1.66.0 a double-click on the title bar of a VSCodium window no longer maximizes the window.
The "Enlarge" button and the keyboard shortcut "Windows + up arrow" are still OK.
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
 I don't have Microsoft's Visual Studio Code for testing if the bug happen on it...

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

open a VSCodium window as normal size
double click on the title bar to maximize it
the window don't maximise

Expected behavior
As of all Windows window, a double-clic on title bar must maximise the window
Desktop :

OS: Windows 10 pro
Architecture : x64
Version : version 21H2, build 19044.1586

Duplicate issue #1055: [windows] cannot double click title bar to maximize window anymore
Created: 2022-04-19T14:23:52Z
Describe the bug
double clicking the title bar of the application now does nothing. normally it would maximize or un-maximize the window, now nothing happens.
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

open vscodium
double-click title bar
observe nothing happen

Expected behavior
double clicking the title bar should retain normal behavior of changing window size
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: windows 10
Architecture x64
Version 1.66.2

Additional context
seems to work fine on mac os still

Closing comment (2022-04-19T14:30:37Z): duplicate of #1032
Repository: VSCodium/vscodium

Issue #699: Possible false positive virus detected: Win32/Fuerboos.B!cl
Created: 2021-04-09T02:43:36Z
Describe the bug
Windows Defender is reporting the following issues:
After checking for updates via Help > Check for Updates...:

When downloading an installer from the release page:

Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

There are two similar but not exactly the same issue:

#579 Win32/Fuery.C!cl, Win32/Wacatac.D3!ml
#331 Win32/Detplock

To Reproduce
Windows Defender will quarantine and alert you to a potential virus when:

From VSCodium press Help > Check for Updates...
Download VSCodium from the 1.55.1 release page.

Desktop (please complete the following information):

OS: Windows 10 Enterprise LTSC 1809
Architecture x64
Version: 1.55.0 (user setup)
Commit: c185983a683d14c396952dd432459097bc7f757f
Date: 2021-04-01T15:04:22.515Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.17763

Duplicate issue #704: VSCodium update file infected with trojan
Created: 2021-04-15T01:44:35Z
When updating my copy of VSCodium (not VSCode) I got this "Threat Quarantined" notification from Windows Defender. Attached is the screenshot of the notification.

Closing comment (2021-04-15T01:47:00Z): Closing as duplicate of #699
Repository: VSCodium/vscodium

Issue #486: Latex Workshop Extension not working
Created: 2020-08-24T07:20:41Z
Describe the bug
The LaTeX Workshop extension is currently not working in VS Codium. The extension symbol is not showing, other extensions are working as expected.
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Install the extension: Press Ctrl + P and enter ext install James-Yu.latex-workshop
Open a .tex file, an example file can be found here
Try to build the document, using the shortcut Ctrl + Alt + b
(to check if you have all latex packages this can also be done via the terminal, e.g. with pdflatex [NAME].tex)
See error "command 'latex-workshop.build' not found" in the right bottom corner

Expected behavior
The  latex document is compiled into an output format, e.g. a PDF file.
Desktop (please complete the following information):

OS: Ubuntu and Kubuntu 20.04
Architecture x86_64
Version 1.48.1

Additional context
This issue might be relevant.

Duplicate issue #839: Latex Workshop
Created: 2021-09-12T19:35:32Z
Describe the bug
Latex Workshop doen't work in VSCodium. It doesn't show the TeX icon, neither can I compile TeX projects. It even throws an exception :
`Yu.latex-workshop' failed: Cannot find module '/home/eolien55/.vscode-oss/extensions/james-yu.latex-workshop-8.20.2/out/src/main.js'
Require stack:

/usr/share/vscodium/resources/app/out/vs/loader.js
/usr/share/vscodium/resources/app/out/bootstrap-amd.js
/usr/share/vscodium/resources/app/out/bootstrap-fork.js`

Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium. I tried and TeX workshop does work

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Install TeX workshop
Observe
Open developer tools, and see thrown exception

Expected behavior
Having TeX working like it does in MS VSCode
Screenshots
None needed
Desktop (please complete the following information):

OS: Garuda Linux (arch-based)
Architecture x64
Version 1.60.0

Additional context
Mentioned extension's repo

Closing comment (2021-09-12T19:44:31Z): Hi, it's a duplicate of #486

This is an issue of OpenVSX which has publish a broken version. (I've checked, files are missing). I would encourage you to encourage the author of the extension to publish directly the extension.
In the meantimes, you can download the vsix from https://marketplace.visualstudio.com/items?itemName=James-Yu.latex-workshop and install it manually.

I've opened the issue: James-Yu/LaTeX-Workshop#2865
Repository: VSCodium/vscodium

Issue #746: [1.58] Extension marketplace not working
Created: 2021-06-20T16:11:54Z
Describe the bug
I built my own vscode for macos using main branch of vscode and extension store is not loading

Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Open VSCodium
Click on Extensions button from left side bar
See error

Expected behavior
Extension store should load
Screenshots

Desktop (please complete the following information):

OS: Mac OS
Architecture x64
Version [1.58.0]

Additional context
NA

Duplicate issue #786: Can't explore in the open VSX marketplace
Created: 2021-08-04T21:49:56Z
Describe the bug
When I try to search an extension, this message appears:

However, if I go to open vsx website, download a .vsix and install it with ctrl+shift+p, it works.
Note: I saw https://github.com/VSCodium/vscodium/blob/master/DOCS.md#howto-vscode-marketplace, will it work with open vsx instead of microsoft's marketplace?
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

Download codium using the appimage
Search for any extension or theme
See error

Expected behavior
Extensions from OpenVSX are visible. I think that OpenVSX should be the default and that microsoft marketplace should be optional.
Screenshots
Already included in the top of this issue.
Desktop (please complete the following information):

OS: Ubuntu 20.10
Architecture x64
Version 1.58.2

Closing comment (2021-08-04T22:22:56Z): Hi, it's a duplicate of #746.
Repository: VSCodium/vscodium

Issue #2082: Crash on Linux when attempting to open "File" menu
Created: 2024-11-02T18:50:54Z
(First time writing one of these, so sorry if I've fail to provide good information)
Describe the bug
After a recent update, trying to use the File menu/dropdown results in a crash after about a second of the program freezing.
Please confirm that this problem is VSCodium-specific

 I temporarily installed Visual Studio Code via the Linux 64 deb package on code.visualstudio.com. The crash does not occur there.
 The crash also does not occur on VSCodium's flatpak option it seems. Only the deb package.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and the Troubleshooting page and was unable to find my issue mentioned there.

To Reproduce
Steps to reproduce the behavior:

Update VSCodium to 1.95.1.24307
Open VSCodium
Hover over "File" in top right and click.
Encounter crash after 1 or 2 seconds.
Its notable that all the other drop downs such as Edit and Terminal seem to render without issue.
Expected behavior
The File dropdown to render and allow options to be selected.

Desktop (please complete the following information):

OS: Linux Mint 21.3 MATE Edition
Architecture amd64 (I believe)
Version 1.95.1.24307
App Manager apt / mintUpdate
Sandboxed Flatpack and Snap are both enabled, but not being relevant to this bug.

Additional context
This bug did not happen on version 1.94.2.24286

Duplicate issue #2106: Whenever i try to select File bar from leftcorner VScodium crashes
Created: 2024-11-12T01:30:37Z
Type: Bug
Just opening File bar
VSCodium version: VSCodium 1.95.2 (7656a0bea17ba6cf301721572e10c9035bb378e6, 2024-11-08T18:21:12.757Z)
OS version: Linux x64 6.8.0-48-generic
Modes:

System Info



Item
Value




CPUs
Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz (4 x 1999)


GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_offwebnn: disabled_off


Load (avg)
7, 3, 1


Memory (System)
7.61GB (5.30GB free)


Process Argv
--extensions-dir /home/priyanshu/.var/app/com.vscodium.codium/data/codium/extensions --ozone-platform=x11


Screen Reader
no


VM
0%


DESKTOP_SESSION
cinnamon


XDG_CURRENT_DESKTOP
X-Cinnamon


XDG_SESSION_DESKTOP
cinnamon


XDG_SESSION_TYPE
x11



Extensions (2)



Extension
Author (truncated)
Version




vscode-vibrancy-continued
ill
1.1.41


material-icon-theme
PKi
5.13.0

Closing comment (2024-11-12T08:45:57Z): Yes, duplicate of #2082
Repository: VSCodium/vscodium

Issue #726: extension is  not updating to latest version 
Created: 2021-05-28T11:47:29Z
Describe the bug
When try to update code runner extension in latest version
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

when i go to extension tabs
Click on code runner extension
click on 'update to 0.11.4'
See error

Screenshots

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-14T00:17:59.109Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.10.0-6parrot1-amd64
log
[2021-05-28 17:14:58.564] [renderer1] [error] Corrupt ZIP: end of central directory record signature not found: validating: Corrupt ZIP: end of central directory record signature not found
at H.downloadInstallableExtension (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:217098)
at async H.doInstallFromGallery (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:214247)
[2021-05-28 17:15:01.551] [renderer1] [error] ["validating: Corrupt ZIP: end of central directory record signature not found","    at H.downloadInstallableExtension (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:217098)","    at async H.doInstallFromGallery (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:214247)"]
[2021-05-28 17:15:01.595] [renderer1] [error] Corrupt ZIP: end of central directory record signature not found: validating: Corrupt ZIP: end of central directory record signature not found
at H.downloadInstallableExtension (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:217098)
at async H.doInstallFromGallery (file:///usr/share/codium/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:47:214247)

Duplicate issue #727: Latest version of extension not installing
Created: 2021-05-28T11:53:51Z
Describe the bug
When i try to install python extension , its showing me old version of python extension(v2020.10.332292344) , that is too old.
But latest version of python extension is v2021.5.842923320
Please confirm that this problem is VSCodium-specific

 This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and my issue is not mentioned there.

Screenshots

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-14T00:17:59.109Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.10.0-6parrot1-amd64

Closing comment (2021-05-28T13:31:25Z): Is it related to #726? Linux, v1.56.2, same day...

No
Repository: VSCodium/vscodium

Issue #2082: Crash on Linux when attempting to open "File" menu
Created: 2024-11-02T18:50:54Z
(First time writing one of these, so sorry if I've fail to provide good information)
Describe the bug
After a recent update, trying to use the File menu/dropdown results in a crash after about a second of the program freezing.
Please confirm that this problem is VSCodium-specific

 I temporarily installed Visual Studio Code via the Linux 64 deb package on code.visualstudio.com. The crash does not occur there.
 The crash also does not occur on VSCodium's flatpak option it seems. Only the deb package.

Please confirm that the issue/resolution isn't already documented

 I checked the Docs page and the Troubleshooting page and was unable to find my issue mentioned there.

To Reproduce
Steps to reproduce the behavior:

Update VSCodium to 1.95.1.24307
Open VSCodium
Hover over "File" in top right and click.
Encounter crash after 1 or 2 seconds.
Its notable that all the other drop downs such as Edit and Terminal seem to render without issue.
Expected behavior
The File dropdown to render and allow options to be selected.

Desktop (please complete the following information):

OS: Linux Mint 21.3 MATE Edition
Architecture amd64 (I believe)
Version 1.95.1.24307
App Manager apt / mintUpdate
Sandboxed Flatpack and Snap are both enabled, but not being relevant to this bug.

Additional context
This bug did not happen on version 1.94.2.24286

Duplicate issue #2115: Crash when interacting with the file tab of the menu bar
Created: 2024-11-15T03:01:22Z
Type: Crash
If I try to interact with the file tab of the menu bar VSCodium crashes.
VSCodium version: VSCodium 1.95.2 (7656a0bea17ba6cf301721572e10c9035bb378e6, 2024-11-08T18:21:12.757Z)
OS version: Linux x64 6.6.54-2-MANJARO
Modes:

System Info



Item
Value




CPUs
12th Gen Intel(R) Core(TM) i7-12700H (20 x 3895)


GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_offwebnn: disabled_off


Load (avg)
1, 2, 1


Memory (System)
62.59GB (56.87GB free)


Process Argv



Screen Reader
no


VM
0%


DESKTOP_SESSION
plasma


XDG_CURRENT_DESKTOP
KDE


XDG_SESSION_DESKTOP
KDE


XDG_SESSION_TYPE
x11




Process Info
CPU %	Mem MB	   PID	Process
    0	   256	 17442	codium main
    0	   128	 17445	   zygote
    0	   192	 17478	     gpu-process
    0	     0	 17526	       broker
    0	   128	 17446	   zygote
    0	     0	 17448	     zygote
    0	   192	 17496	window [1] (Welcome - VSCodium)
    0	   128	 17482	   utility-network-service
    0	   192	 17565	shared-process
    0	     0	 17627	     /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	   128	 17566	fileWatcher [1]
    0	   192	 17567	extensionHost [1]



Workspace Info
;


Extensions: none

Closing comment (2024-11-15T09:26:17Z): duplicate #2082
Repository: VSCodium/vscodium

Issue #1502: Missing Release notes on 1.78.1
Created: 2023-05-10T08:13:03Z
Trying to see the relase notes results in a blank editor tab.

Duplicate issue #1510: stopped displaying
Created: 2023-05-10T18:08:15Z
Type: Bug
stopped displaying details in window.
VSCodium version: VSCodium 1.78.1 (748cf23d39091308b3b0d65ac43f0d784709fdcc, 2023-05-10T01:49:13.634Z)
OS version: Linux x64 6.2.6-76060206-generic
Modes:
Sandboxed: No

System Info



Item
Value




CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 3353)


GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off


Load (avg)
2, 1, 1


Memory (System)
15.36GB (7.62GB free)


Process Argv
--unity-launch


Screen Reader
no


VM
0%


DESKTOP_SESSION
pop


XDG_CURRENT_DESKTOP
Unity


XDG_SESSION_DESKTOP
pop


XDG_SESSION_TYPE
x11



Extensions (33)



Extension
Author (truncated)
Version




Bookmarks
ale
13.0.1


vscode-sqlite
ale
0.14.1


arepl
alm
2.0.5


vscode-django
bat
1.8.0


githistory
don
0.6.20


python-environment-manager
don
1.0.4


python-extension-pack
don
1.7.0


gitlens
eam
13.5.0


vscode-python-config
fra
1.17.0


vscode-pull-request-github
Git
0.64.0


test-adapter-converter
hbe
0.1.6


vscode-test-explorer
hbe
2.21.1


rest-client
hum
0.25.0


vsc-python-indent
Kev
1.18.0


jupyter
lum
2022.3.108


MagicPython
mag
1.1.1


rainbow-csv
mec
3.3.0


python-path
mge
0.0.14


git-graph
mhu
1.30.0


vscode-docker
ms-
1.25.0


vscode-language-pack-pt-BR
MS-
1.78.0


vscode-dotnet-runtime
ms-
1.6.0


python
ms-
2023.6.0


jupyter
ms-
2023.3.100


jupyter-keymap
ms-
1.1.0


jupyter-renderers
ms-
1.0.15


autodocstring
njp
0.6.1


oracledevtools
Ora
21.5.0


code-spell-checker
str
2.20.4


vscode-remotework-extension-pack
sug
1.1.4


python
tht
0.2.2


jinja
who
0.0.8


markdown-editor
zaa
0.1.9



(2 theme extensions excluded)

Closing comment (2023-05-11T07:32:06Z): Probably related to #1502, #1503 and #1504.
Opening the Commit Graph with GitLens also does not work and just shows an empty window.
Repository: VSCodium/vscodium

Issue #1227: Update from <`1.70.0` to >`1.71.0`
Created: 2022-09-02T08:04:06Z
Hello,
In the process of trying to debrand (when doing the insider version), I've overlooked several issues:
On macOS
When updating, you will get the error:
Could not locate update bundle for com.visualstudio.code.oss within file:///Users/<user>/Library/Caches/com.visualstudio.code.oss.ShipIt/update.<id>/

The new bundle identifier is com.vscodium instead of com.visualstudio.code.oss.
I'm sorry about the issue but we will need to manually update to this version.
The next versions will keep com.vscodium so the automatic update will work.
On Windows
The update is executed successfully but you will 2 uninstall instances due to different id: (VSCodium.VSCodium instead of Microsoft.VSCodium)
@GitMensch @paulcarroty What do you think about this issue?

Duplicate issue #1399: How to download updates from the specified source instead of GitHub release
Created: 2023-02-05T09:31:32Z
The update-api seems to hardcode the GitHub release URL. So to download updates from the specified source, it seems that another update api needs to be built and the update url in product.json needs to be modified. Is it possible to modify the product.json directly in the installed VSCodium without recompiling?

Closing comment (2023-02-05T10:27:09Z): The update url is defined here: 
  
    
      vscodium/prepare_vscode.sh
    
    
         Line 105
      in
      9ad93a4
    
  
  
    

        
          
           setpath "product" "updateUrl" "https://vscodium.now.sh" 
        
    
  


Not sure what's the issue? Maybe related to #1227
Repository: VadimDez/ng2-pdf-viewer

Issue #46: Retina display support
Created: 2017-01-21T13:36:25Z
Currently viewport.width and viewport.height are used for the rendering. This does not take retina display into account, such as iOS and macOS devices. The rendered text quality is therefore quite bad.
https://developer.mozilla.org/en/docs/Web/API/Window/devicePixelRatio
Please extend the component to support sub-pixel rendering.

Duplicate issue #106: Very poor quality PDF
Created: 2017-07-11T12:44:56Z
I saw this problem also in other issues.
How did you fix it?
For me it's a big problem. It is really unreadable.

Closing comment (2017-08-04T15:41:57Z): Duplicate #46
Repository: VadimDez/ng2-pdf-viewer

Issue #805: [7.0.1] width of pdf page exceed the maximum width and got trimmed from the right side
Created: 2021-06-20T12:20:37Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [x] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

I have an issue with a pdf exceeding the width from style max-width which is mentioned in the docs, but seems that does not work, that issue happened with the latest changes (version 7.0.1).

I was using it as simple as:
<pdf-viewer [original-size]="false" [render-text]="false" [src]="pdfUrl" style="display: block; max-width: 1200px; margin: 0 auto;"></pdf-viewer>

Which was working, and tried:
<pdf-viewer [original-size]="false" [zoom-scale]="'page-width'" [fit-to-page]="true"  [autoresize]="true" [render-text]="false" [src]="pdfUrl"
              style="display: block; max-width: 1200px; margin: 0 auto;"></pdf-viewer>
Nothing worked, but when I changed .ng2-pdf-viewer-container to be position: relative it is worked fine.

So the change that I can say is behind this issue is this: 8d4f8ad#diff-c0a5f3426a537629a18cbeb63abc55b7ce727f267c2e85acf84c88ddd96e4cb1R3
The problem solved only runtime, but if I do something like:
pdf-viewer {
  ::ng-deep {
    .ng2-pdf-viewer-container {
      position: relative;
    }
  }
}
I get only blank screen.
The workaround for this is to make the style inside pdf-viewer tag:
pdf-viewer {
  ::ng-deep {
    .ng2-pdf-viewer-container {
      max-width: 1200px;
    }
  }
}

Duplicate issue #811: .ng2-pdf-viewer-container not in parent container
Created: 2021-07-30T09:20:20Z
Bug Report or Feature Request (mark with an x)
- [X] Regression (a behavior that used to work and stopped working in a new release)
- [ ] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

File : pdf-viewer.component.scss
In the latest version, the .ng2-pdf-viewer-container is set with position:absolute and width:100%
This leads to multiple styling problems, especially in pages where the pdf viewer is supposed to be contained in a container.
In previous versions, the position was set to relative and there was no problems.

Closing comment (2021-08-20T12:04:10Z): I think it is a duplicate of #805 (workaround provided)
Here is the change to blame: 8d4f8ad#diff-c0a5f3426a537629a18cbeb63abc55b7ce727f267c2e85acf84c88ddd96e4cb1R3
Repository: VadimDez/ng2-pdf-viewer

Issue #392: Memory issue
Created: 2018-10-11T20:25:28Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [x] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

Using under ionic 3 application, on ios 12, got the following memory issue after increasing the zoom:
ng2-pdf-viewer version: 5.0.1
      total canvas memory use exceeds the maximum limit (224 mb)

The source file weight its around 700kb which I think is accurate.
Any help its appreciated

Duplicate issue #492: canvas memory is not destroying while close the opened pdfs in tabs(max 5 pdf) in ionic v4 cordova (Total canvas memory exceeds the maximum limit (224mb)) and showing the blank pages
Created: 2019-06-13T13:18:07Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [ ] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

Closing comment (2020-06-28T21:27:07Z): I think this one is related to #392.
I am having the same problem on Safari ("Mozilla/5.0 (iPhone; CPU iPhone OS 13_5_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148") so it is not Ionic related.
Maybe this are possible solutions: mozilla/pdf.js#11297 and mozilla/pdf.js#11245
changing maxCanvasPixels to a very low number does fix the issue, but obviously you can not read anything :)
    const pdfOptions: PDFViewerParams | any = {
      eventBus: eventBus,
      container: this.element.nativeElement.querySelector('div'),
      removePageBorders: !this._showBorders,
      linkService: this.pdfMultiPageLinkService,
      textLayerMode: this._renderText
        ? this._renderTextMode
        : RenderTextMode.DISABLED,
      findController: this.pdfMultiPageFindController,
      maxCanvasPixels: 1000
    };

UPDATE:
I changed the ngOnDestroy function to the following and removed the maxCanvasPixels option.
  ngOnDestroy() {
    this.clear();
  }

Now it seems to work. Before the change I could only opening a pdf 6 times in a row. After the change I can easily open it >30 times.
Repository: VadimDez/ng2-pdf-viewer

Issue #624: Angular 10 issue -> optimization bailouts
Created: 2020-06-25T19:08:23Z
WARNING in /../node_modules/ng2-pdf-viewer/ivy_ngcc/fesm2015/ng2-pdf-viewer.js depends on pdfjs-dist/build/pdf. CommonJS or AMD dependencies can cause optimization bailouts.
For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

Duplicate issue #643: Warning in Angular 10
Created: 2020-08-07T16:20:34Z
Bug Report or Feature Request (mark with an x)

 Regression (a behavior that used to work and stopped working in a new release)
 Bug report -> please search issues before submitting
 Feature request
 Documentation issue or request

./node_modules/ng2-pdf-viewer/__ivy_ngcc__/fesm2015/ng2-pdf-viewer.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map: "ng:/ng2-pdf-viewer/src/app/pdf-viewer/pdf-viewer.component.ts" URL is not supported

Use this lib in angular 10 with sourcemap will case warning.
Update ng-packagr to 10 will remove this warning for angular 10 users.

Closing comment (2021-11-11T14:11:19Z): This is a duplicate of #624. Let's close this one and subscribe there ;)
Repository: VadimDez/ng2-pdf-viewer

Issue #706: Get currentPageNumber()
Created: 2021-01-13T20:10:22Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [ ] Bug report -> please search issues before submitting
- [ X] Feature request
- [ ] Documentation issue or request

For a couple of days, i was working with PDF Viewer and I hade a pretty good success while making functions that I needed for my task but within my task todo list i hade to make that pdf will serve only 5 pages at a time and I should know user on which page it is but I could figure it out how to get a current page number.
Is there any function or any way that i can get a currentPageNumber that is being shown to the user not rendered pages but the exact page number that is being shown on user?

Duplicate issue #710: How to get the current page number
Created: 2021-01-18T12:42:19Z
Angular 6,
how to get the current page number?

Closing comment (2021-02-16T17:09:39Z): Duplicate of #706
Repository: VadimDez/ng2-pdf-viewer

Issue #200: PDFDocumentProxy, PDFProgressData are undefined for compiler
Created: 2017-11-08T14:21:08Z
Reported in #199

Duplicate issue #208: Cannot find name 'PDFDocumentProxy' when upgrading from v2.x to v3.x
Created: 2017-11-13T11:57:04Z
Was trying to upgrade to the newest version 3.0.1 (coming from 2.0.3). Strictly followed the setup as decribed in the "Usage"-section but it's giving me the error:
Cannot find name 'PDFDocumentProxy'
Probably an error related to the after-load-complete-Attribute.
I removed the type from the callback-function in order to get it working again, but I'm not entirely sure if just removing it will give me other drawbacks.

Closing comment (2017-11-13T13:41:03Z): Duplicate of #200
Repository: VadimDez/ng2-pdf-viewer

Issue #729: how to get selected text from pdf viewer
Created: 2021-02-25T06:49:56Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [ ] Bug report -> please search issues before submitting
- [x] Feature request
- [ ] Documentation issue or request

Is there a API to set a listener to watch the 'select' event or get the selected text in this module?

Duplicate issue #734: Getting PDF text
Created: 2021-03-05T16:13:44Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [ ] Bug report -> please search issues before submitting
- [x] Feature request
- [x] Documentation issue or request

I can't find a way to get selected text, is there any way to get selected text ?

Closing comment (2021-03-11T10:16:27Z): Duplicate of #729
Repository: VadimDez/ng2-pdf-viewer

Issue #367: Out of bounds index in pdf_viewer: "TypeError: Cannot read property 'div' of undefined" - when closing PDF too quickly - or zooming
Created: 2018-08-20T21:57:01Z
Seems to be a race-condition type of bug, if I close the pdf viewer too quickly.  (or change [zoom])
I get this with ng2-pdf-viewer v5.1.1 (angular 5.2) in Chrome if I close (set *ngIf=false the parent's div) too quickly before the PDF is totally loaded...    I have a "close" button that kills the pdfviewer parent div.   To guard it, to only be able to close when the PDF is loaded, I am catching the (after-load-complete) and (page-rendered), not allowing to set the pdfviewer parent div's ngIf to false unless those have completed, but still getting the crash/exception.
TypeError: Cannot read property 'div' of undefined
    at backtrackBeforeAllVisibleElements (VM474151 pdf_viewer.js:558)
    at getVisibleElements (VM474151 pdf_viewer.js:605)
    at PDFViewer._getVisiblePages (VM474151 pdf_viewer.js:5400)
    at PDFViewer.forceRendering (VM474151 pdf_viewer.js:5080)
    at PDFRenderingQueue.renderHighestPriority (VM474151 pdf_viewer.js:4191)
    at continueRendering (VM474151 pdf_viewer.js:4256)
    at ZoneDelegate.invoke (VM472116 zone.js:388)

offending line of code is here in pdf_viewer.js:558:
function backtrackBeforeAllVisibleElements(index, views, top) {
  if (index < 2) {
    return index;
  }
  var elt = views[index].div;   <----- HERE pdf_viewer.js:558

where index == 3 for my 3-page pdf (out of bounds!).
The html template:
<div *ngIf='showing' (click)="close()">
<div (click)="$event.stopPropagation()">
<pdf-viewer
	[src]='content_url'
        [zoom]='pdfzoom'
	[original-size]="false"
	[render-text]="true"
	[autoresize]="true"
	[show-all]="true"
	[fit-to-page]="false"
	(after-load-complete)="onPdfLoad($event)"
	(error)="onPdfError($event)"
	(on-progress)="onPdfProgress($event)"
	(page-rendered)="onPdfRendered($event)"
></pdf-viewer>
</div>
</div>

the component.ts
close() {
   if (this.can_close) this.showing = false;
}
onPdfLoad(e) {
  this.can_close = true;
}
zoomIn() {
  if (this.can_close) {
    this.pdfzoom = Math.min( this.pdfzoom_max, this.pdfzoom+0.1 );
  }
}
zoomOut() {
  if (this.can_close) {
    this.pdfzoom = Math.max( this.pdfzoom_min, this.pdfzoom-0.1 );
  }
}

Duplicate issue #344: After zoom the pdf doc, drag is throwing and error
Created: 2018-07-09T12:17:27Z
Bug Report or Feature Request (mark with an x)
- [ ] Regression (a behavior that used to work and stopped working in a new release)
- [ x ] Bug report -> please search issues before submitting
- [ ] Feature request
- [ ] Documentation issue or request

Hi,
I am experimenting a error. Once the zoom value is different than 1, if you drag the document to see the zoomed content it gives error. Attached image.

In an Angular app is only giving the error in the console. But in the ionic app it shows the ionic exception page crashing the user experience.
Gr.

Closing comment (2018-09-06T17:32:31Z): See the duplicate #367
Repository: VadimDez/ng2-pdf-viewer

Issue #18: Is it possible to enable hyperlinks in the rendered PDF?
Created: 2016-09-21T19:17:41Z
https://github.com/mozilla/pdf.js/blob/master/examples/components/simpleviewer.js#L37
// (Optionally) enable hyperlinks within PDF files.
var pdfLinkService = new PDFJS.PDFLinkService();

Is it possible to show the hyperlinks in proper annotated PDF ?
other related post:
http://stackoverflow.com/questions/37016124/display-annotations-hyperlinks-using-pdf-js
http://stackoverflow.com/questions/33813373/pdf-js-how-to-open-hyperlinks-in-a-new-tab-window

Duplicate issue #49: Hyperlinks are not working
Created: 2017-01-26T01:45:00Z
I am able to view the pdf on the browser but none of the hyperlink works. Is there any option to enable it as I am already using [render-text]="true" and that did not enable hyperlinks?

Closing comment (2017-01-27T19:32:29Z): Closing as duplicate of #18
Repository: ValveSoftware/SteamOS

Issue #321: gnome-terminal not working on Brewmaster
Created: 2015-06-26T23:22:51Z
I have installed Brewmaster on my system using the Expert Install option. In the Gnome session, gnome-terminal refuses to run. Here is the error that I got when I tried to launch it from xterm.
Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.Terminal exited with status 8

I found some posts mentioning similar problems on the Arch Linux forums. The workaround for setting the locale via localectl fixed the problem on my system. The workaround also allowed desktop effects to start working.
https://bbs.archlinux.org/viewtopic.php?id=180103

Duplicate issue #724: The terminal doesn't work
Created: 2020-12-04T16:35:20Z
The terminal does not work after expert installation with a change of the default language.

Closing comment (2021-01-27T10:49:38Z): Duplicate of #321