gc-excelviewer
gc-excelviewer copied to clipboard
After.csv unopenable
Issue Type: Bug
VScode threw the following error whenever I attempted opening "After.csv" simply changing the "A" to lowercase "a" allowed the file to be opened. Unable to open 'After.csv': Assertation Failed:argument is undefined or null
the error ceased after titleing some different csv files as After.csv
the csv file was being generated by an AutoHotKey Script and its exact contents were as follows between the | symbols | "Keys","Values" "1","Frontier%20Delaware%20Central%20Ave" "2","Forced%20Echo%20for%20testing" "3","Fenwal%208000" "4","Fenwal%206000" "5","Fenwal%202000" "6","Fenwal" "7","FCI%20E3/S3" "8","FCI%207100" "9","Default%20Settings" "10","AES" "11","1200%20N%208%201" "12","1200%20N%207%201" "13","0000" "","0000"
|
Extension version: 4.2.53 VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No
System Info
Item | Value |
---|---|
CPUs | Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz (4 x 2594) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 7.92GB (2.95GB free) |
Process Argv | --crash-reporter-id 683714e3-85b4-490b-aaed-2d22e2e17adb |
Screen Reader | no |
VM | 0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvspyt640:30450904
vscscmwlcmc:30438804
vscgsvidc:30447482
dockersurvey3:30453609
vscaac:30438847
pynewfile477cf:30450039
@natesones I can reproduce your issue if the rename only changes case. If I rename to a totally different name it works fine. Still investigating, but it may be related to this issue in VS Code itself: https://github.com/microsoft/vscode/issues/86146
@natesones I can reproduce this issue without my extension using the VS Code custom editor sample. Reported here: https://github.com/microsoft/vscode-extension-samples/issues/582