anthonydresser / testissues

0 stars 0 forks source link

Notebook syntax/error highlighting behaves differently before kernel start #847

Open adsbot[bot] opened 5 years ago

adsbot[bot] commented 5 years ago

Issue Type: Bug

If you enter code before a kernel session starts the syntax and error highlighting is incorrect and remains that way through the rest of the session. It seems that it uses the colorization and snippets from the first kernel and this does not reset even after adding new cells.

Notebook Error Highlighting Incorrect

Compare the colorization of this notebook where code cells were not added until after the kernel started:

image

To this one, where the first code cell was added before the kernel started (but after moving from SQL) and the second code cell was added after the kernel had started:

image

In the latter case, SQL snippets are available in all new cells even well after the kernel has been running.

image

Azure Data Studio version: azuredatastudio 1.7.0-insider (2b8e0cc6c43fa212741e57adc8966e434eb65628, 2019-05-10T15:55:49.193Z) OS version: Windows_NT x64 10.0.17763

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-7600U CPU ! 2.80GHz (4 x 2904)| |GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.84GB (2.85GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|
Extensions (11) Extension|Author (truncated)|Version ---|---|--- newdatabase|kev|0.0.3 admin-pack|Mic|0.0.2 agent|Mic|0.38.0 dacpac|Mic|0.2.0 import|Mic|0.7.0 profiler|Mic|0.7.0 schema-compare|Mic|0.2.0 server-report|Mic|0.1.5 sql-vnext|Mic|0.10.3 whoisactive|Mic|0.1.1 azdata-sanddance|msr|1.0.0 (1 theme extensions excluded)
adstestbot[bot] commented 5 years ago

Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: