%set_env VSCODE_NLS_CONFIG={"locale":"en-us","availableLanguages":{},

SQLvariant commented 4 years ago

After upgrading to powershell-kernel v0.1.3 the issue with lagging results isn't showing up, but I am still sometimes receiving this error, the first time I run a line of code in a PowerShell Notebook:

At line:67 char:37
+ %set_env VSCODE_NLS_CONFIG={"locale":"en-us","availableLanguages":{}, ...
+                                     ~~~~~~~~
Unexpected token ':"en-us"' in expression or statement.
At line:67 char:45
+ %set_env VSCODE_NLS_CONFIG={"locale":"en-us","availableLanguages":{}, ...
+                                             ~
Missing argument in parameter list.
At line:1 char:3
+ . {
+   ~
Missing closing '}' in statement block or type definition.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

}
At line:1 char:1
+ }
+ ~
Unexpected token '}' in expres

Simply running the command again seems to work to get around it.

chlafreniere commented 4 years ago

This only happens in Azure Data Studio. Let's keep tracking it there, although this issue should be resolved by now.

SQLvariant commented 4 years ago

Ok, we'll track in ADS. It happened to me last week during a presentation for the Sacramento UG.

vors / jupyter-powershell

%set_env VSCODE_NLS_CONFIG={"locale":"en-us","availableLanguages":{}, #34