failed to start debugging. task build failed with exit code 1

Repro steps:

Action: azureFunctions.pickProcess
Error type: Error
Error Message: Failed to start debugging. Task "build" failed with exit code "1".
Version: 0.20.0
OS: win32
Product: Visual Studio Code
Product Version: 1.39.2
Language: en

Call Stack
s.tasks.onDidEndTaskProcess.t extension.bundle.js:353:75642
l.fire extensionHostProcess.js:50:519
m.$onDidEndTaskProcess extensionHostProcess.js:684:405

@Divyanshu9114 check the output of the build task to address this issue. If that doesn't help, copy the logs here

Output is blank, I am using a HTTP trigger in Azure Function in C#, trying to create a connection.
LOG (WINDOWS):
[2019-11-11 11:02:28.487] [renderer1] [error] Cannot read property 'trim' of undefined: TypeError: Cannot read property 'trim' of undefined
at ctorParamStr.split.forEach (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:180:37)
at Array.forEach (:null:null)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:177:33)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:03:34.230] [renderer1] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions
[2019-11-11 11:06:10.036] [renderer1] [error] Illegal argument: line must be non-negative: Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:06:38.210] [renderer1] [error] Illegal argument: line must be non-negative: Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
LOG(Extension Host):
[2019-11-11 11:01:29.284] [exthost] [info] extension host started
[2019-11-11 11:01:29.819] [exthost] [info] ExtensionService#_doActivateExtension aaron-bond.better-comments {"startup":false,"extensionId":{"value":"aaron-bond.better-comments","_lower":"aaron-bond.better-comments"},"activationEvent":"onLanguage:plaintext"}
[2019-11-11 11:01:29.819] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/aaron-bond.better-comments-2.0.5/out/extension
[2019-11-11 11:01:30.102] [exthost] [info] ExtensionService#_doActivateExtension craigthomas.supersharp {"startup":false,"extensionId":{"value":"craigthomas.supersharp","_lower":"craigthomas.supersharp"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:30.102] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/craigthomas.supersharp-0.1.4/out/extension
[2019-11-11 11:01:31.641] [exthost] [info] ExtensionService#_doActivateExtension jchannon.csharpextensions {"startup":false,"extensionId":{"value":"jchannon.csharpextensions","_lower":"jchannon.csharpextensions"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:31.641] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/jchannon.csharpextensions-1.3.1/out/src/extension
[2019-11-11 11:01:36.902] [exthost] [info] ExtensionService#_doActivateExtension k--kato.docomment {"startup":false,"extensionId":{"value":"k--kato.docomment","_lower":"k--kato.docomment"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:36.902] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/k--kato.docomment-0.1.8/out/src/extension
[2019-11-11 11:01:37.716] [exthost] [info] ExtensionService#_doActivateExtension kreativ-software.csharpextensions {"startup":false,"extensionId":{"value":"kreativ-software.csharpextensions","_lower":"kreativ-software.csharpextensions"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:37.716] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/kreativ-software.csharpextensions-1.3.0/out/src/extension
[2019-11-11 11:01:38.592] [exthost] [info] ExtensionService#_doActivateExtension Leopotam.csharpfixformat {"startup":false,"extensionId":{"value":"Leopotam.csharpfixformat","_lower":"leopotam.csharpfixformat"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:38.593] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/leopotam.csharpfixformat-0.0.84/out/extension.js
[2019-11-11 11:01:39.002] [exthost] [info] ExtensionService#_doActivateExtension mavis.csharpextensions {"startup":false,"extensionId":{"value":"mavis.csharpextensions","_lower":"mavis.csharpextensions"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:39.002] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/mavis.csharpextensions-1.3.0/out/src/extension
[2019-11-11 11:01:39.900] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.csharp {"startup":false,"extensionId":{"value":"ms-vscode.csharp","_lower":"ms-vscode.csharp"},"activationEvent":"onLanguage:csharp"}
[2019-11-11 11:01:39.900] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/ms-vscode.csharp-1.21.6/dist/extension
[2019-11-11 11:01:40.082] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch {"startup":true,"extensionId":{"value":"vscode.debug-auto-launch","_lower":"vscode.debug-auto-launch"},"activationEvent":""}
[2019-11-11 11:01:40.082] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/debug-auto-launch/dist/extension
[2019-11-11 11:01:40.166] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet {"startup":true,"extensionId":{"value":"vscode.emmet","_lower":"vscode.emmet"},"activationEvent":""}
[2019-11-11 11:01:40.166] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/emmet/dist/extension
[2019-11-11 11:01:40.309] [exthost] [info] ExtensionService#_doActivateExtension vscode.git {"startup":true,"extensionId":{"value":"vscode.git","_lower":"vscode.git"},"activationEvent":""}
[2019-11-11 11:01:40.309] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/git/dist/main
[2019-11-11 11:01:40.690] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict {"startup":true,"extensionId":{"value":"vscode.merge-conflict","_lower":"vscode.merge-conflict"},"activationEvent":""}
[2019-11-11 11:01:40.690] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/merge-conflict/dist/extension
[2019-11-11 11:01:40.861] [exthost] [info] ExtensionService#_doActivateExtension christian-kohler.path-intellisense {"startup":true,"extensionId":{"value":"christian-kohler.path-intellisense","_lower":"christian-kohler.path-intellisense"},"activationEvent":""}
[2019-11-11 11:01:40.861] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/christian-kohler.path-intellisense-1.4.2/out/src/extension
[2019-11-11 11:01:41.673] [exthost] [info] ExtensionService#_doActivateExtension schneiderpat.aspnet-helper {"startup":true,"extensionId":{"value":"schneiderpat.aspnet-helper","_lower":"schneiderpat.aspnet-helper"},"activationEvent":""}
[2019-11-11 11:01:41.673] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/schneiderpat.aspnet-helper-0.6.4/out/src/extension
[2019-11-11 11:01:42.132] [exthost] [info] ExtensionService#_doActivateExtension wayou.vscode-todo-highlight {"startup":true,"extensionId":{"value":"wayou.vscode-todo-highlight","_lower":"wayou.vscode-todo-highlight"},"activationEvent":""}
[2019-11-11 11:01:42.132] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/wayou.vscode-todo-highlight-1.0.4/src/extension
[2019-11-11 11:01:42.232] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.azure-account {"startup":true,"extensionId":{"value":"ms-azuretools.vscode-azurefunctions","_lower":"ms-azuretools.vscode-azurefunctions"},"activationEvent":"workspaceContains:host.json"}
[2019-11-11 11:01:42.232] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/ms-vscode.azure-account-0.8.7/dist/extension
[2019-11-11 11:01:42.708] [exthost] [info] ExtensionService#_doActivateExtension ms-azuretools.vscode-azurefunctions {"startup":true,"extensionId":{"value":"ms-azuretools.vscode-azurefunctions","_lower":"ms-azuretools.vscode-azurefunctions"},"activationEvent":"workspaceContains:host.json"}
[2019-11-11 11:01:42.708] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/ms-azuretools.vscode-azurefunctions-0.20.0/main.js
[2019-11-11 11:01:43.416] [exthost] [info] ExtensionService#_doActivateExtension formulahendry.dotnet-test-explorer {"startup":true,"extensionId":{"value":"formulahendry.dotnet-test-explorer","_lower":"formulahendry.dotnet-test-explorer"},"activationEvent":"workspaceContains:**/.csproj,/*.fsproj"}
[2019-11-11 11:01:43.416] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/formulahendry.dotnet-test-explorer-0.7.1/out/src/extension
[2019-11-11 11:02:20.263] [exthost] [info] ExtensionService#_doActivateExtension jpahnen.dotnet-cli-wrapper {"startup":true,"extensionId":{"value":"jpahnen.dotnet-cli-wrapper","_lower":"jpahnen.dotnet-cli-wrapper"},"activationEvent":"workspaceContainsTimeout:/.csproj,**/.sln"}
[2019-11-11 11:02:20.263] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/jpahnen.dotnet-cli-wrapper-0.1.0/out/extension
[2019-11-11 11:02:22.627] [exthost] [info] ExtensionService#_doActivateExtension tintoy.msbuild-project-tools {"startup":true,"extensionId":{"value":"tintoy.msbuild-project-tools","_lower":"tintoy.msbuild-project-tools"},"activationEvent":"workspaceContainsTimeout:/*.*proj,/.props,**/.targets"}
[2019-11-11 11:02:22.627] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/tintoy.msbuild-project-tools-0.3.2/out/src/extension/extension
[2019-11-11 11:02:26.404] [exthost] [info] ExtensionService#_doActivateExtension firefox-devtools.vscode-firefox-debug {"startup":false,"extensionId":{"value":"firefox-devtools.vscode-firefox-debug","_lower":"firefox-devtools.vscode-firefox-debug"},"activationEvent":"onDebug"}
[2019-11-11 11:02:26.405] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/.vscode/extensions/firefox-devtools.vscode-firefox-debug-2.4.0/dist/extension.bundle.js
[2019-11-11 11:02:26.614] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:02:26.614] [exthost] [error] TypeError: Cannot read property 'trim' of undefined
at ctorParamStr.split.forEach (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:180:37)
at Array.forEach (:null:null)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:177:33)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:02:29.251] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-server-ready {"startup":false,"extensionId":{"value":"vscode.debug-server-ready","_lower":"vscode.debug-server-ready"},"activationEvent":"onDebugResolve"}
[2019-11-11 11:02:29.251] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/debug-server-ready/dist/extension
[2019-11-11 11:02:37.572] [exthost] [info] ExtensionService#_doActivateExtension vscode.grunt {"startup":false,"extensionId":{"value":"vscode.grunt","_lower":"vscode.grunt"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2019-11-11 11:02:37.572] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/grunt/dist/main
[2019-11-11 11:02:37.845] [exthost] [info] ExtensionService#_doActivateExtension vscode.gulp {"startup":false,"extensionId":{"value":"vscode.gulp","_lower":"vscode.gulp"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2019-11-11 11:02:37.845] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/gulp/dist/main
[2019-11-11 11:02:37.913] [exthost] [info] ExtensionService#_doActivateExtension vscode.jake {"startup":false,"extensionId":{"value":"vscode.jake","_lower":"vscode.jake"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2019-11-11 11:02:37.913] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/jake/dist/main
[2019-11-11 11:02:37.973] [exthost] [info] ExtensionService#_doActivateExtension vscode.npm {"startup":false,"extensionId":{"value":"vscode.npm","_lower":"vscode.npm"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2019-11-11 11:02:37.973] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/npm/dist/main
[2019-11-11 11:02:38.274] [exthost] [info] ExtensionService#_doActivateExtension vscode.typescript-language-features {"startup":false,"extensionId":{"value":"vscode.typescript-language-features","_lower":"vscode.typescript-language-features"},"activationEvent":"onCommand:workbench.action.tasks.runTask"}
[2019-11-11 11:02:38.274] [exthost] [info] ExtensionService#loadCommonJSModule file:///c:/Users/divyanshu.s/AppData/Local/Programs/Microsoft VS Code/resources/app/extensions/typescript-language-features/dist/extension
[2019-11-11 11:02:58.533] [exthost] [info] eager extensions activated
[2019-11-11 11:03:34.230] [exthost] [error] [ms-vscode.csharp] provider FAILED
[2019-11-11 11:03:34.230] [exthost] [error] Problem invoking 'GetCodeActions' on OmniSharp server: Error: Pending request cancelled: /v2/getcodeactions
[2019-11-11 11:06:10.034] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:06:10.035] [exthost] [error] Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:06:38.209] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:06:38.210] [exthost] [error] Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:08:18.094] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:08:18.095] [exthost] [error] Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:08:27.634] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:08:27.635] [exthost] [error] Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
[2019-11-11 11:08:41.742] [exthost] [error] [jchannon.csharpextensions] provider FAILED
[2019-11-11 11:08:41.742] [exthost] [error] Error: Illegal argument: line must be non-negative
at Object.t.illegalArgument (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:13:524)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:344:16)
at new p (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:343:392)
at CodeActionProvider.getInitializeFromCtorCommand (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:166:61)
at addInitalizeFromCtor (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:15:28)
at CodeActionProvider.provideCodeActions (c:\Users\divyanshu.s.vscode\extensions\jchannon.csharpextensions-1.3.1\out\src\codeActionProvider.js:19:9)
at o.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:465)
at Promise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:649)
at new Promise (:null:null)
at Object.t.asPromise (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:621)
at C.provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:554:436)
at _withAdapter.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:817)
at U._withAdapter (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:566:593)
at U.$provideCodeActions (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:570:795)
at p._doInvokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:635:275)
at p._invokeHandler (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:634:971)
at p._receiveRequest (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:633:588)
at p._receiveOneMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:632:468)
at _protocol.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:630:691)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at e.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:787:104)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at _.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:181:274)
at t.PersistentProtocol._receiveMessage (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:185:629)
at _socketDisposables.push._socketReader.onMessage.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:182:824)
at l.fire (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:50:519)
at p.acceptChunk (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:178:588)
at _register._socket.onData.e (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:177:958)
at Socket.t (c:\Users\divyanshu.s\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:187:68)
at Socket.emit (events.js:182:13)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)

Hmm I don't think that's the log we want. I'm looking for the output of the build task, which should look something like this:

HI Eric,
Thanks for your response, We found the mistake, there was some glitch with
the environment. I used my supervisor help to sort it.
Thanks for your time you can close the issue.
Thanks and Regards
Divyanshu Singh
On Wed, Nov 20, 2019 at 1:01 AM Eric Jizba<EMAIL_ADDRESS>wrote:

Hmm I don't think that's the log we want. I'm looking for the output of
the build task, which should look something like this:
[image: Screen Shot 2019-11-19 at 11 30 19 AM]
https://user-images.githubusercontent.com/11282622/69179242-0f9a7200-0ac0-11ea-8ba3-2b2f508ce410.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-azurefunctions/issues/1666?email_source=notifications&email_token=AMLVGHFGBJNSTSSTERQHN6DQUQ5IFA5CNFSM4JKFO5SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEPOCNA#issuecomment-555671860,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMLVGHH4B7LGXYP4ZYIUNX3QUQ5IFANCNFSM4JKFO5SA
.


cleaner.go:143:17:1 other occurrence(s) of "improper cluster entries" found in: cleaner.go:97:17

cleaner.go:143:17:1 other occurrence(s) of "improper cluster entries" found in: cleaner.go:97:17

Fixed in https://github.com/RedHatInsights/insights-results-aggregator-cleaner/pull/49


Fix local env in docker-compose.yaml

Description

also load .env.local via env_file to allow local env override
rename .env.development to .env.docker
use YAML anchors to make file shorter

Additional Context
https://github.com/stackernews/stacker.news/pull/1082#issuecomment-2061724213
Checklist

[x] Are your changes backwards compatible?

[x] Did you QA this? Could we deploy this straight to production?

[ ] For frontend changes: Tested on mobile?

[ ] Did you introduce any new environment variables? If so, call them out explicitly in the PR description.

Summary by CodeRabbit

Chores

Updated .gitignore settings for better environment file management.

New Features

Enhanced Docker configurations with health checks and dependencies for improved service reliability.

Refactor

Improved handling of environment files in Docker compose setups.

I wasn't aware of anchors. That's cool!
Why the name change to .env.docker? Nextjs's convention is .env.development.

Oh, I wasn't aware of the NextJS convention. I only changed it because it felt more natural to specify that it specifies the env for the docker containers.
I'll revert the rename


Hue motion sensor 1lx

Hi there, since this morning my Philips Hue motion sensor is stuck at measuring 1lx.
Restarting the app and restarting Homey both didn’t help.

Hi,
This is most likely an issue with the ZigBee implementation of Homey. In the latest Athom newsletter they mentioned that the ZigBee code will be redesigned eventually. Hopefully this will help.


[BEAM-2749] update BeamSqlExample

R: @takidau

R: + @xumingming

Changes Unknown when pulling f03cc869db3801b7913a87f7950e16241b877a5a on XuMingmin:BEAM-2749 into ** on apache:DSL_SQL**.

Just out of curiosity, what's the reason that Tyler's previous try failed?

I don't find the cause, possibly some libraries are broken. It may happens as DSL_SQL uses the same version as master, however the two branches are quite different so far.
Sent from my iPhone

On Aug 8, 2017, at 11:30 PM, James Xu<EMAIL_ADDRESS>wrote:
@xumingming approved this pull request.
LGTM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Glad to know that it works in your env now, mvn clean install seems a one-size-fits-all solution.

Changes Unknown when pulling 3ae49a0fedca8926a7a99df06403f65d827f1f8e on XuMingmin:BEAM-2749 into ** on apache:DSL_SQL**.

Merged, feel free to close. Thank you!

close #3706, thank you @takidau @xumingming


Extract Python installation code into a stand alone project

As discussed with you yesterday, I think it would be benefit to extract the part of rye that is responsible to download and install Python and expose it's API programmatically as a lib so that it could be used in other tools.
This would allow the field of Python bootstrapping to make several explorations based on a commons solid basis:

Some tools may chose a radical simple workflow to make it dead simple to install Python for beginners, without
Some tools may chose a GUI to make it more accessible.
Some tools may include it into other ecosystems like VSCode, QGIS, etc.
Maybe some installer, or packaging tools will want to use that to create a new type of Python toolkit that let you install a program and the run time for it optionally if it doesn't exist.
CI and test tools may want to include it to standardize Python fetching. E.G: imagine tox downloading Python it doesn't have.

All that would be easier if one didn't have to include the entire project management part of rye, which is unnecessary for those steps.
There is already tremendous value for a robust, cross-plateform, unified way of installing and calling Python, and this project is a hint of that.
This would also allow for more sources of contributions, for things like:

Improving the fallback when one download source is not available: other projects could implement alternative repositories for Python so that you can round robin to diminish load or fallback if one fails.
Allow for private download sources for companies that want to restrict which Python is installed and from where.
Add experimental repositories for unstable Python, or non standard Pythons distributions, the way APT add source lists.

Eventually, if this gets popular, in a few years, one can imagine proposing such tool to the core devs as the main way to install Python.

This might be interesting for @jdx, the creator of https://github.com/jdx/mise

Unless I'm missing something mise already solves all of these use-cases.

I really like this idea, but wouldn't it be wise to publish a public API after the project has been somewhat stabilized? Especially the parts of Rye that leverage the Python installation logic.
Also, adding support for a public API at this stage could be a lot to ask from what is currently a one-man show.

It would be great if rye was mise aware. Having a second place in my home to keep multiple versions of portable python isn't ideal. I'm not sure how feasible that is from an implementation standpoint though. Registering mise versions seems to be a functional workaround but it seems like it could get fragile, for example when mise performs a patch update to a minor version.


ujust brew-fleek still broken

Describe the bug
running ujust brew-fleek reports errors
What did you expect to happen?
should install fleek configs
Output of rpm-ostree status
No response
Extra information or context
No response

script needs to be run from $HOME

but that's not enough to fix it :(

just may be executing in a strange working dir.
tar: .fleek: Cannot mkdir: Read-only file system
command runs fine outside of just.  Strange

I ran the command today and fleek installed successfully without errors. ? ?

Confirmed successful install by running command directly

fixed this in fleekbrewgen directly by issuing a cd $HOME before doing tar operations.


Supply the editor with all information to automatically derive annotations

Is your feature request related to a problem? Please describe
Instead of having the Python analysis tool generate an annotations.json file, it should export all necessary information to this API editor, so the user can invoke the automatic generation of annotations in the UI.

Will be implemented for the desktop component.


jQuery Isotope issue

If i try to load the social feed inside of jQuery Isotope elements Isotopes seems not to be working.
Can you confirm this bug ?
If so - is there any hotfix to load the social feed inside Isotope ?

Dear @hostianer,
I did not try to load socialfeed with Isotope (i believe you are talking about this http://isotope.metafizzy.co/).
Could you please share a piece of code you use for the integration - so i can check it out, without starting from scratch.
I believe that if there is a problem - it can be caused by the fact that Isotope most likely expects to have a static container with elements inside, while in social-feed the elements are loaded and dynamically added. May be if you initiate Isotope after all the posts are loaded and rendered by socialfeed - it will work.

Hi Pavel,
yep this is what i am talking about.
I already figured out that this is because the ajax loading.
Heres a link:
http://<IP_ADDRESS>/
And here is the social JS file: http://<IP_ADDRESS>/assets/js/custom.js
I wrote this little code to the callback function but it seems that this function is not loading:
 $("#social-twitter-stream").each(function() {
                var $social = $(this);
                $social.social($social.data());
            });

If i execute the script manually in the dev tools console its working.

Ok,
You might try to use the callback function implemented here
https://github.com/pavelk2/social-feed/pull/80
So after all the posts are collected and rendered - you use the isotope.
Let me know how it goes.

I already used you callback function
// When all the posts are collected and displayed - this function is evoked
        callback: function(){

            $("#social-twitter-stream").each(function() {
                var $social = $(this);
                $social.social($social.data());
            });

            console.log('all posts are collected');
        }

unfortunately i dont know much about javascript so i dont know which code i have to use fom #80


httplib2 -> Request migration problem

Hi,
The last update migrating httplib2 to Request make google-cloud-bigquery library incompatible with GAE standard, and it was before.
google-cloud-bigquery==0.25.0 => Ok in GAE standard
google-cloud-bigquery==0.26.0 => Ko in GAE standard (request dependency)

Hi @sebastienmorand,
Which dependency of requests refuses to install on GAE Standard?
/cc @jonparrott

The short answer is that due to limitations in the App Engine standard environment, this library is not supported there.
The long answer(s) are over at #1893.
If a previous version of BigQuery worked for you then I would recommend pinning to that version.


Return waiting tables for managers

The waiting tables for evidence and payments were removed for managers
This returns them and [finishes #106288698]

Tested and good to merge after code review.

:+1:


TODO Features

change default zoom level for first run on Map

Rect selection docs, 4 numbers, 2 numbers
For now what are those 4 numbers? we should be able to do min_lon, max_lon, min_lat, max_lat or min_lon, min_lat, max_lon, max_lat

plot tiles in a 3d axis, LScene.

expose function to plot new points in lon,lat coordinates to be plotted on top of tile.

expose axis?

Remove white flicker between zoom levels

plot slightly larger than the area so the edges of pan/zoom are mostly already filled


feat: Add clustering for user

Please fix toast with error fetching data on clustering before merging, might be due to str(-1)


Remove duplicate component

Critical Changes
None
Changes
Remove duplicate component.
Issues Closed
#4291
New Metadata
None
Deleted Metadata
dataProviderInterfaceInterface.intf
dataProviderInterfaceInterface.intf-meta.xml
These files were not referenced by package.xml in the first place, so no change is required in that file.

Thanks @Zosoled!

**lurch: add

Tracking W-033409

@Zosoled Thank you very much for this contribution, but unfortunately we are unable to accept it. I've had our engineers review the request, and they've let me know that because the component is packaged and released, it's non-deletable and we can't remove it.
Further reading on the subject if you are interested: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_packageable_components.htm#packaging_packageable_components

@Zosoled Whoops, seems we had a bit of an internal misunderstanding of what you were referring to. We can in fact delete the dataProviderInterfaceInterface.intf file, inside the bundle. I've reopened the Issue and PR. Again, thank you for contributing this!


fix: turborepo cache

Once we updated to the latest version of turbo, we needed to have updated the remote cache settings. This PR proposes that.

What does this configs do?


Problem: no "getting started" documentation(cro-223)

@leejw51crypto I'll merge the current version, but there are a few things to improve


Removed placeholders in Contributing.md

Added year + owners to the MIT license in CONTRIBUTING.md.

Thank you for your contribution! :+1: However, this is indeed an placeholder, not an actual copyright claim.


Package as a cordova app

We want people to be able to install austingreenmap as an app and be able to view the park data offline.

[x] Get an iOS app building with Cordova
[ ] Get an Android app building with Cordova
[x] iOS icon
[ ] Android icon
[x] Splash screen
[ ] Write script to automate building/packaging
[x] Publish to App Store
[ ] Publish to Google Play

I've gotten it to run on my iPhone! It works much better there too. (I think because the app doesn't freeze waiting for the data load).
https://github.com/open-austin/austingreenmap-cordova

sweet

awesome!

yay

Yeah https://itunes.apple.com/us/app/green-map-interactive-map/id1022734155?mt=8

:confetti_ball:
Congrats you guys!


spasm-ng: 2020-08-03 -> 2022-07-03

Description of changes
Add header files that are automatically included in the SPASM-ng repo into the include directory. Also, update spasm-ng itself.
Things done

Built on platform(s)

[X] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
The Git command took so long I gave up and stopped execution. I searched the Nixpkgs repo for references to spasm-ng, and there were no other references.
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Things that can be improved further, but will not be implemented in this PR:

Add passthru.tests, which requires patchShebangs in the tests.
There is a bug introduced in this PR where running spasm without any arguments results in an error instead of the help message. This can be resolved by creating spasm-ng-unwrapped and making a custom wrapper in spasm. This is not a big issue because users can run spasm -h to get the help options anyway.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 332844 run on x86_64-darwin 1

1 package failed to build:

spasm-ng

Result of nixpkgs-review pr 332844 run on x86_64-darwin 1

1 package built:

spasm-ng

@ofborg eval


update 'src test'

Update the 'test' / debugging version (compile with make test) so it can be compiled and works.
E.g., there were fct name changes, and some updates in features (e.g. signal handling closer to bash)

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Introduce IsStarting to fix CPU load-balancer

Thanks for identifying the issue. I think we would be better off with adding a Status() api.StatusCode function added to the instance interface. Then we would only have to make one call to it to get the status and can apply specific logic where needed.
Otherwise with this approach we are ending up calling into the instance twice (well four times as its called again later).
There's been other places where something like this would have been useful to differentiate specific status codes. I'll put up a PR for this.
Thanks

I've got an alternative solution for you that avoids needing to extend the Instance interface nor changing the properties of the existing IsRunning function.
https://github.com/lxc/lxd/pull/11464


Refer to the Bruning (2019) paper

Add a reference to the Bruning (2019) paper in the README.  I found it
somewhat hard to find a detailed description of what the software
actually does (as opposed to how to use it).  The only mention of the
paper I could find was in the 0.5.0 release without a concrete citation,
I hope that I added the correct one.  Thanks for the software :)

@gerritholl thanks for the added documentation! Merging…


Only able to extract the last page even after clearing the selection and selecting other pages before clicking Auto detect.

Dec Fulton Tax Sale.pdf

Please just make your selections manually, rather than using autodetect.

Sorry, didn't think to drag the crosshatch.
Duh....
Thanks!
Jeremy B. Merrill wrote:
Please just make your selections manually, rather than using
autodetect.
—
You are receiving this because you authored the thread.
Reply to this email directly, view
it on GitHub, or mute
the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/tabulapdf/tabula","title":"tabulapdf/tabula","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/tabulapdf/tabula"}},"updates":{"snippets":[{"icon":"PERSON
","message":"@jeremybmerrill in #597: Please just make your selections manually, rather than using autodetect."}],"action":{"name":"View Issue","url":"https://github.com/tabulapdf/tabula/issues/597#issuecomment-268037170"}}}


pyam.concat / pyam.append overwrites and not updates year parameter

the concat command has issues:
IAMC_IDX = ['model', 'scenario', 'region', 'variable', 'unit']

TEST_YEARS_PROJ = [2005, 2010]
TEST_YEARS_HIST = [2000]

proj = pd.DataFrame([
    ['model_a', 'scen_a', 'reg', 'PE', 'EJ/yr', 1, 6.],
],
    columns=IAMC_IDX + TEST_YEARS_PROJ,
)
proj = pyam.IamDataFrame(proj)

hist = pd.DataFrame([
    ['source_b', 'scen_b', 'reg', 'PE', 'EJ/yr', 0.5],
],
    columns=IAMC_IDX + TEST_YEARS_HIST,
)
hist = pyam.IamDataFrame(hist)

concat = pyam.concat([hist, proj])

print(concat)
print(concat.year)

gives me
 <class 'pyam.core.IamDataFrame'>
Index dimensions:
 * model    : model_a, source_b (2)
 * scenario : scen_a, scen_b (2)
Timeseries data coordinates:
   region   : reg (1)
   variable : PE (1)
   unit     : EJ/yr (1)
   year     : 2000, 2005, 2010 (3)
Meta indicators:
   exclude (bool) False (1)

 [2000]

(the latter should be [2000, 2005 and 2010]). The issue only arises for .year

Thanks @l-welder for reporting this issue - I also noticed this last week and fixed it (silently) in #481, by pulling out the attribute-definition into an own function _set_attributes() (which is called after append() and other functions that implicitly modify the _data attribute).
Do you have a minute to take a look at #481?

Thanks @l-welder for reporting this issue - I also noticed this last week and fixed it (silently) in #481, by pulling out the attribute-definition into an own function _set_attributes() (which is called after append() and other functions that implicitly modify the _data attribute).
Do you have a minute to take a look at #481?

I am a bit short of time right now for a deeper look into the PR, but I pulled your branch and with that the issue is fixed (as you already suggested) (=

I am a bit short of time right now for a deeper look into the PR, but I pulled your branch and with that the issue is fixed (as you already suggested) (=


Use relative install path for gz tool data

🦟 Bug fix
Summary
Fixes an error when building https://github.com/gazebo-release/gz_plugin_vendor/ in the ROS buildfarm.
Similar to https://github.com/gazebosim/gz-tools/pull/137
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Duplicate of #140.


Add wrapping configuration source

The problem described in this question: https://stackoverflow.com/questions/46466300/how-to-place-a-configuration-source-to-a-certain-configuration-section-to-avoid
I think it would be handy to solve such problems with the following extension method:
var cfg = new ConfigurationBuilder()
	.AddConfiguration("Users", derivedConfigurationBuilder =>
	{
		derivedConfigurationBuilder.AddJsonFile("users.json");
	})
	.AddJsonFile("connections.json")
	.Build();

I would love to work on this some day, but without any response and guidance from the team it looks to risky

Closing this in favor of https://github.com/aspnet/Configuration/blob/dev/src/Config/ChainedBuilderExtensions.cs. If there is still value in the wrapping source that is not provided by chaining, then please elaborate and we may re-consider.


Does not support other languages

I tried language="sql". It does not work

did you import the lang somewhere in your project? Don't know how you use prismjs but maybe sth like that:
import "prismjs/components/prism-sql.js"

https://codesandbox.io/s/61yrlnlnmn
It does not work in the demo also.

It works if you import the sql lang file from prismjs.
add this line somewhere in main.js file.
import "prismjs/components/prism-sql.js"

Perfect. Thanks for the help!

I had the same problem. This issue help me to fix it. Woulb be great to put this tip on the readme.md page.

Hi. One more question about this issue. I've got problem with "php" language.
Codesandbox — https://codesandbox.io/s/vue-prism-editor-php-raise-errors-2xuse
Problem: I've seen above the solution with SQL and checked it with PHP and JSON, so I included them into main.js:
import "prismjs/components/prism-php.js"
import "prismjs/components/prism-json.js"

When using language="json" everything works good. When I try to use language="php" these 7 problems are raised:

Error in getter for watcher "content": "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in render: "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in getter for watcher "content": "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in render: "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in mounted hook: "TypeError: Cannot read property 'innerHTML' of undefined"
Error in mounted hook: "TypeError: Cannot read property 'innerHTML' of undefined"
Error in nextTick: "TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'."

I've also decided to check for prism object, so I've imported it from 'prismjs' and checked for prism.languages — php exists in this object.
Any thoughts about that?

Hi. One more question about this issue. I've got problem with "php" language.
Codesandbox — https://codesandbox.io/s/vue-prism-editor-php-raise-errors-2xuse
Problem: I've seen above the solution with SQL and checked it with PHP and JSON, so I included them into main.js:
import "prismjs/components/prism-php.js"
import "prismjs/components/prism-json.js"

When using language="json" everything works good. When I try to use language="php" these 7 problems are raised:

Error in getter for watcher "content": "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in render: "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in getter for watcher "content": "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in render: "TypeError: Cannot read property 'tokenizePlaceholders' of undefined"
Error in mounted hook: "TypeError: Cannot read property 'innerHTML' of undefined"
Error in mounted hook: "TypeError: Cannot read property 'innerHTML' of undefined"
Error in nextTick: "TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'."

I've also decided to check for prism object, so I've imported it from 'prismjs' and checked for prism.languages — php exists in this object.
Any thoughts about that?

I have encountered the same problem. How did you solve it?

Please upgrade to the new version v1.x

Hi I am on the newest version, and for CSS I get:
Error in nextTick: "TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'."

Hi I am on the newest version, and for CSS I get:
Error in nextTick: "TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'."

I got a similar error and this thread helped me


Feature/python support

Adding support for f-string in Python
Except when the string is part of a format call. e.g:
foo = 'bar {}'.format(...)

close: #5

you're awesome


[TIKA-3418] DefaultZipContainerDetector does not support loading of ZipContainerDetectors in an OSGi enviroment

Thanks for your contribution to Apache Tika! Your help is appreciated!
Before opening the pull request, please verify that

there is an open issue on the Tika issue tracker which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
the issue ID (TIKA-XXXX)

is referenced in the title of the pull request
and placed in front of your commit messages surrounded by square brackets ([TIKA-XXXX] Issue or pull request title)

commits are squashed into a single one (or few commits for larger changes)
Tika is successfully built and unit tests pass by running mvn clean test
there should be no conflicts when merging the pull request branch into the recent main branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled main branch.

We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the Tika mailing list. Thanks!

Hi
Could someone please approve the "workflow"?
Have a great weekend
Simon

I merged this and made a few modifications.  I need to figure out how to do a better job of passing tikaconfig info into DefaultZipDetector.
Thank you @simon-shlomo for opening this!


config.yml reordered options

Reordered options in hopes to make it easier to read.

@davidusb-geek , @michaelpiron , @purcell-lab Any help with this will be appreciated.
This pull request aiming to re-order the parameters as best as possible to make it easier for new users.
We can also add/remove parameters in the options: section and leave it it the schema: section if we want these parameters to be present/hidden on all add-on installs. So the design is to have the required and mainly used parameters in the options: section.
Note that all parameters are set to optional. This is because EMHASS is setup to have default values (values stored in the config_emhass.yaml) for all options if not provided.

I guess that the parameters that shuld not be optional are those tat lead to a most basic configuration.
This is a system with just deferrable loads and probably a PV production.
Right?

I've been helping with some other setups lately and each site is a little bit unique, which makes things very difficult to standardise.
One concept I have been toying with is the entity of input_number for each configuration element, that way they can be updated on the fly and you don't have these really long payloads which is where a lot of the errors occur.
The user would be responsible for ensuring each input_number is correctly setup and then the standard day-ahead or mpc call would access those input numbers for input.
I suppose we could use the existing configuration.yaml and then create a blueprint with the calls setup with input_number?
But happy to discuss some other options going forward.

Another idea I had (which would take a while to make) is a html form that would override the need for the add-on configuration tab (the configuration tab would only have url and key). This could be formatted in a way that makes parameters readable, sectioned and also dynamically hidden when certain workloads/parameters are defined.
On submission emhass could set each parameters into a option.json but could also create the necessary inputs/sensors/automations etc *(restrictions based on what we can do with the HA API) *


.= operator with || generates incorrect code

.= operator with || generates incorrect code.  For example (from CGI.pm):
$url .= $vh || server_name();

generates:
url_v = _str(url_v) + _str(vh) or server_name()

In Python, the '+' operator has higher precedence than the 'or' operator. So, the expression _str(url_v) + _str(vh) will be evaluated first, and its result will be used in the 'or' operation.  This not a correct translation of the perl.

Fixed in v1.023


OIDC-based user authentication

These changes introduce the functionality for configuring Funnel and for using any external OIDC authentication provider. It can co-exist with the existing Basic authentication solution. It is intended for the HTTP-based TES API and OIDC-based authentication is now also supported by the Funnel UI (webdash).
Overview of changes:

configuration – Server.OidcAuth.* fields for specifying the target OIDC service by configuration URL, client credentials of Funnel, and optional JWT requirements.
authentication interceptor – changes to adapt authentication to both Basic and Bearer tokens.
new endpoints:

GET /login for redirecting user to the configured OIDC-service;
GET /login/token for exposing the returned JWT authentication token to the webdash.

webdash – requires authentication at OIDC (if OIDC is enabled) but also supports Basic authentication (if OIDC is disabled)

updated existing fetch-calls to use the common fetching functionality in utils.js (which also forwards the Authorization header).

documentation – README file about configuring Funnel for OIDC-based user authentication.

JWT validation is handled by an externally developed library: github.com/lestrrat-go/jwx/v2/jwk.
Another good feature is that UserInfo is now added to the request context. It can be used for deciding user's access to resources.

I'm providing this functionality for you to evaluate and decide if it's worth to include it in the main Funnel codebase. Feel free to test and provide feedback. If necessary, I can do some additional changes.

Thank you @mrtamm! Funnel lacks robust authentication support and this has been a blocker for many collaborators — we will review the PR and update here by the end of this week.
Ideally we can then get this feature included in the next release cycle — thanks again! 🚀

Thank you for the first approval! :)
At this point, I wanted to clarify a bit this OIDC-based authentication solution.
When OIDC is configured, authentication interceptor can accept and validate Bearer tokens in the HTTP request headers. It expects an Access Token there. JWT validation includes checking signature, audience, scope, and also token validness (call to OIDC introspection endpoint).
If OIDC-based authentication is initiated through the UI (or /login endpoint), the same endpoint also stores the Access Token in a jwt session cookie, which is exposed to JavaScript through the /login/token endpoint. From there on, the JavaScript fetch() calls will use the obtained token in the Authorization header. This Access Token based authentication is also suitable for external TES API clients that have already authenticated the user at the same OIDC Identity Provider.
If OIDC is not enabled, however, Basic authentication is enabled, the /login endpoint will request Basic-authentication, and the /login/token endpoint will just provide an empty response. The fetch() calls will provide the browser-managed Basic Authorization header to the server.
Note that both Basic and Bearer authenticated user-session solutions are currently based on the browser session – if the window is closed, the credentials are forgotten. Currently, there is no logging out option for the user. It would require storing the related ID token somewhere, however, I was not sure where and how to store it, so I preferred not to do it at this point. Though, I'm open to suggestions here.
As a heads-up, I am also preparing another pull request for storing user as task owner, and restricting access to tasks based on the owner information (if enabled through configuration). That solution is based on the user info functionality provided in this pull request. (We can leave that discussion to the new PR.)


Valid sample name improvement for RNA-seq

Version info

bcbio version (bcbio_nextgen.py --version): 1.2.7
OS name and version (lsb_release -ds): Ubuntu 20.04.2 LTS

Minor issue, the sample name sanitizer should be improved to also handle dashes, which are considered illegal characters in R. I noticed this message pop up in a bcbio run:
10000-001 is not a valid R name, converting to X10000-001.

Technically, "X10000-001" is also not a valid name in R because of the hyphen. By default, the make.names() function in R convert hyphens to periods, but the current recommended best practice is to sanitize to underscores.
It may be a good idea to tweak this in the pipeline, so the sample name gets converted from "10000-001" to "X10000_001", to avoid any downstream issues in R.
Best,
Mike

Hi Mike!
Nice to hear from you - thanks for the suggestion!
We sanitize sample names for several types of projects (not for variant calling) here:
https://github.com/bcbio/bcbio-nextgen/blob/master/bcbio/pipeline/run_info.py#L956
It is an easy fix, but I doubt that many users would be happy with us automatically changing their sample names,
which are cross-referenced in sample tracking systems, work tracking systems, data analysis systems, etc.
100 > X100 is a necessary evil for bulk RNA-seq (and we are not changing the name, we are just using an X prefix),
but sample-01_ 20-01-01 => sample_01_20_01_01 could be too much of a change to bear.
Imagine also users who re-process their samples.
I'd suggest fixing this downstream in R unless there is a massive outcry to fix sample names at the level of bcbio.
Sergey

Hi @naumenko-sa , I agree that we should attempt to avoid renaming sample names, and allow for (in my opinion, bad practice) edge cases such as "sample-01_ 20-01-01" in the bcbio output. Almost every FASTQ sample I get back from a sequencing vendor is formated along the lines of "10000_001_R1_001.fastq.gz", so I deal with this issue frequently.
Originally we added the "X" prefix to bulk RNA-seq sample names to avoid some downstream issues specifically in R, since samples starting with a number aren't syntactically valid. See the make.names() documentation for details on this. So in the event of a sample such as "10001" getting converted to "X10001", this works without issue in R. But sample names containing a hyphen (e.g. "sample-01_ 20-01-01") are also considered invalid in R, and can also produce some unexpected results in packages that rely on dependencies that change column and/or row names, including the tidyverse and potentially data.table as well.
So I'm wondering if maybe we should just revert the "X" prefix addition step in the main bcbio processing pipeline, but then enforce syntactically valid R naming conventions specifically in the internal R scripts, such as bcbio2se.R. What to consider as best practice here is tricky, as many users still load into R directly from the flat file matrices, and therefore these kind of naming issues will persistent in their downstream workflows without additional sanitization steps.
We take a similar approach in bcbioRNASeq and bcbioSingleCell using our makeNames() function variant, which essentially calls the base make.names() function but returns with underscores instead of periods, which users generally prefer. Refer also to our YAML parser code defined in bcbioBase, that helps handle sample name processing inside the bcbio R packages.
I guess my point is that currently adding the "X" prefix sends a bit of a mixed message if we're still allowing hyphens in the sample names, and maybe we should just take this out to begin with?
Mike

This isn't a high priority, so safe to close