text:
Error while installing .NET Core Debugger.

why? i am reinstall VSCode and .net core many time..
Error: /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.lock.json(1,0): warning NU1006: Dependencies in project.json were modified. Please run "dotnet restore" to generate a new lock file.
Starting 'dotnet --info'
.NET Command Line Tools (1.0.0-rc2-002392)
Product Information:
Version:     1.0.0-rc2-002392
Commit Sha:  880dcf2fc8
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.10
OS Platform: Darwin
RID:         osx.10.10-x64
Creating /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.json
log  : Restoring packages for /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.json...
info :   CACHE https://api.nuget.org/v3-flatcontainer/runtime.osx.10.10-x64.microsoft.visualstudio.clrdbg/index.json
info : Committing restore...
log  : Lock file has not changed. Skipping lock file write. Path: /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.lock.json
log  : /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.json
log  : Restore completed in 3420ms.
NuGet Config files used:
/Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/NuGet.config

Feeds used:
https://api.nuget.org/v3/index.json

Publishing
dummy for .NETCoreApp,Version=v1.0/osx.10.10-x64
Project dummy (.NETCoreApp,Version=v1.0) will be compiled because some of its inputs were newer than its oldest output.
Oldest output item:
6/27/16 7:44:54 PM: /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/bin/Debug/netcoreapp1.0/dummy.dll
Inputs newer than the oldest output item:
6/27/16 7:47:19 PM: /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.json
Compiling dummy for .NETCoreApp,Version=v1.0
Running /usr/local/share/dotnet/dotnet compile-csc @/Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/obj/Debug/netcoreapp1.0/dotnet-compile.rsp
Process ID: 687
Running /usr/local/share/dotnet/dotnet /usr/local/share/dotnet/sdk/1.0.0-rc2-002392/csc.dll -noconfig @/Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/obj/Debug/netcoreapp1.0/dotnet-compile-csc.rsp
Process ID: 688
Error: /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/project.lock.json(1,0): warning NU1006: Dependencies in project.json were modified. Please run "dotnet restore" to generate a new lock file.
Compilation succeeded.
1 Warning(s)
0 Error(s)
Time elapsed 00:00:07.1766323
publish: Publishing dummy 1.0.0 ...
Publishing file dummy.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.CSharp 4.0.1-rc2-24027 ...
Publishing file Microsoft.CSharp.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.NETCore.Platforms 1.0.1-rc2-24027 ...
publish: Publishing Microsoft.NETCore.Runtime 1.0.2-rc2-24027 ...
publish: Publishing Microsoft.NETCore.Runtime.CoreCLR 1.0.2-rc2-24027 ...
publish: Publishing Microsoft.NETCore.Runtime.Native 1.0.2-rc2-24027 ...
publish: Publishing Microsoft.NETCore.Targets 1.0.1-rc2-24027 ...
publish: Publishing Microsoft.NETCore.Windows.ApiSets 1.0.1-rc2-24027 ...
publish: Publishing
Microsoft.VisualStudio.clrdbg 14.0.25406-preview-3044032 ...
Publishing file Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator.ExpressionCompiler.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.CodeAnalysis.CSharp.ExpressionEvaluator.ResultProvider.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.CodeAnalysis.CSharp.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.CodeAnalysis.ExpressionEvaluator.ExpressionCompiler.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.CodeAnalysis.ExpressionEvaluator.ResultProvider.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.CodeAnalysis.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.DiaSymReader.PortablePdb.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.DiaSymReader.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Collections.Immutable.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Private.CompilerServices.ICastable.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Private.CoreLib.InteropServices.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Private.Interop.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Reflection.Metadata.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.VisualStudio.clrdbg.MIEngine 14.0.30610-preview-1 ...
Publishing file Microsoft.MICore.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.MIDebugEngine.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.VisualStudio.Debugger.Interop.Portable 1.0.1 ...
Publishing file Microsoft.VisualStudio.Debugger.Interop.10.0.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.Debugger.Interop.11.0.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.Debugger.Interop.12.0.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.Debugger.InteropA.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.OLE.Interop.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.VisualStudio.OpenDebugAD7 1.0.20614-preview-2
...
Publishing file Microsoft.DebugEngineHost.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file OpenDebugAD7.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing Microsoft.Win32.Primitives 4.0.1-rc2-24027 ...
publish: Publishing Microsoft.Win32.Registry 4.0.0-rc2-24027 ...
Publishing file Microsoft.Win32.Registry.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing NETStandard.Library 1.5.0-rc2-24027 ...
publish: Publishing Newtonsoft.Json 7.0.1 ...
Publishing file Newtonsoft.Json.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.AppContext 4.1.0-rc2-24027 ...
Publishing file System.AppContext.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Collections 4.0.11-rc2-24027 ...
Publishing file System.Collections.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Diagnostics.Tools 4.0.1-rc2-24027 ...
Publishing file System.Diagnostics.Tools.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Diagnostics.Tracing 4.1.0-rc2-24027 ...
Publishing file System.Diagnostics.Tracing.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Globalization 4.0.11-rc2-24027 ...
Publishing file System.Globalization.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Globalization.Calendars 4.0.1-rc2-24027
...
Publishing file System.Globalization.Calendars.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.IO 4.1.0-rc2-24027 ...
Publishing file System.IO.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Reflection 4.1.0-rc2-24027 ...
Publishing file System.Reflection.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Reflection.Extensions 4.0.1-rc2-24027 ...
Publishing file System.Reflection.Extensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Reflection.Primitives 4.0.1-rc2-24027 ...
Publishing file System.Reflection.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Resources.ResourceManager 4.0.1-rc2-24027 ...
Publishing file System.Resources.ResourceManager.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Runtime 4.1.0-rc2-24027 ...
Publishing file System.Runtime.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Runtime.Handles 4.0.1-rc2-24027 ...
Publishing file System.Runtime.Handles.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Runtime.InteropServices 4.1.0-rc2-24027
...
Publishing file System.Runtime.InteropServices.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Text.Encoding 4.0.11-rc2-24027 ...
Publishing file System.Text.Encoding.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Text.Encoding.Extensions 4.0.11-rc2-24027 ...
Publishing file System.Text.Encoding.Extensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Threading.Tasks 4.0.11-rc2-24027 ...
Publishing file System.Threading.Tasks.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.any.System.Threading.Timer 4.0.1-rc2-24027 ...
Publishing file System.Threading.Timer.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.native.System 4.0.0-rc2-24027 ...
publish: Publishing runtime.native.System.IO.Compression 4.1.0-rc2-24027 ...
publish: Publishing runtime.native.System.Net.Http 4.0.1-rc2-24027 ...
publish: Publishing runtime.native.System.Security.Cryptography 4.0.0-rc2-24027 ...
publish: Publishing runtime.osx.10.10-x64.Microsoft.NETCore.Runtime.CoreCLR 1.0.2-rc2-24027 ...
Publishing file mscorlib.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Globalization.Native.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libcoreclr.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libdbgshim.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libmscordaccore.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libmscordbi.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libsos.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file mscorlib.ni.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file sosdocsunix.txt to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.osx.10.10-x64.Microsoft.VisualStudio.clrdbg 14.0.25406-preview-3046211 ...
Publishing file Microsoft.DiaSymReader.McgInterop.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.Debugger.Engine.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.Debugger.Metadata.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.VIL.Host.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file Microsoft.VisualStudio.VIL.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file vsdebugeng.manimpl.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file clrdbg to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libclrdbg.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libvsbaseservices.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libvsdebugeng.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file libvsdebugeng.impl.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.osx.10.10-x64.runtime.native.System 1.0.1-rc2-24027 ...
Publishing file System.Native.a to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Publishing file System.Native.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.osx.10.10-x64.runtime.native.System.IO.Compression 1.0.1-rc2-24027 ...
Publishing file System.IO.Compression.Native.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.osx.10.10-x64.runtime.native.System.Net.Http 1.0.1-rc2-24027 ...
Publishing file System.Net.Http.Native.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.osx.10.10-x64.runtime.native.System.Security.Cryptography 1.0.1-rc2-24027 ...
Publishing file System.Security.Cryptography.Native.dylib to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.Microsoft.Win32.Primitives 4.0.1-rc2-24027 ...
Publishing file Microsoft.Win32.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Console 4.0.0-rc2-24027
...
Publishing file System.Console.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Diagnostics.Debug 4.0.11-rc2-24027 ...
Publishing file System.Diagnostics.Debug.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.IO.FileSystem 4.0.1-rc2-24027 ...
Publishing file System.IO.FileSystem.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Net.Primitives 4.0.11-rc2-24027 ...
Publishing file System.Net.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Net.Sockets 4.1.0-rc2-24027 ...
Publishing file System.Net.Sockets.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Private.Uri 4.0.1-rc2-24027 ...
Publishing file System.Private.Uri.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Runtime.Extensions 4.1.0-rc2-24027 ...
Publishing file System.Runtime.Extensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing runtime.unix.System.Runtime.InteropServices.RuntimeInformation 4.0.0-rc2-24027 ...
Publishing file System.Runtime.InteropServices.RuntimeInformation.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.AppContext 4.1.0-rc2-24027 ...
publish: Publishing System.Buffers 4.0.0-rc2-24027 ...
Publishing file System.Buffers.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Collections 4.0.11-rc2-24027 ...
publish: Publishing System.Collections.Concurrent 4.0.12-rc2-24027 ...
Publishing file System.Collections.Concurrent.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Collections.Immutable 1.2.0-rc2-24027 ...
Publishing file System.Collections.Immutable.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Collections.NonGeneric 4.0.1-rc2-24027 ...
Publishing file System.Collections.NonGeneric.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Collections.Specialized 4.0.1-rc2-24027 ...
Publishing file System.Collections.Specialized.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.ComponentModel 4.0.1-rc2-24027 ...
Publishing file System.ComponentModel.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.ComponentModel.Annotations 4.1.0-rc2-24027 ...
Publishing file System.ComponentModel.Annotations.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.ComponentModel.EventBasedAsync 4.0.11-rc2-24027 ...
Publishing file System.ComponentModel.EventBasedAsync.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Console 4.0.0-rc2-24027 ...
publish: Publishing System.Diagnostics.Contracts 4.0.1-rc2-24027 ...
Publishing file System.Diagnostics.Contracts.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Diagnostics.Debug 4.0.11-rc2-24027 ...
publish: Publishing System.Diagnostics.DiagnosticSource 4.0.0-rc2-24027 ...
Publishing file System.Diagnostics.DiagnosticSource.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Diagnostics.Process 4.1.0-rc2-24027 ...
Publishing file System.Diagnostics.Process.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Diagnostics.StackTrace 4.0.1-rc2-24027 ...
Publishing file System.Diagnostics.StackTrace.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Diagnostics.Tools 4.0.1-rc2-24027 ...
publish: Publishing System.Diagnostics.Tracing 4.1.0-rc2-24027 ...
publish: Publishing System.Dynamic.Runtime 4.0.11-rc2-24027
...
Publishing file System.Dynamic.Runtime.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Globalization 4.0.11-rc2-24027 ...
publish: Publishing System.Globalization.Calendars 4.0.1-rc2-24027
...
publish: Publishing System.Globalization.Extensions 4.0.1-rc2-24027
...
Publishing file System.Globalization.Extensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO 4.1.0-rc2-24027 ...
publish: Publishing System.IO.Compression 4.1.0-rc2-24027
...
Publishing file System.IO.Compression.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO.Compression.ZipFile 4.0.1-rc2-24027 ...
Publishing file System.IO.Compression.ZipFile.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO.FileSystem 4.0.1-rc2-24027 ...
publish: Publishing System.IO.FileSystem.Primitives 4.0.1-rc2-24027 ...
Publishing file System.IO.FileSystem.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO.FileSystem.Watcher 4.0.0-rc2-24027 ...
Publishing file System.IO.FileSystem.Watcher.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO.MemoryMappedFiles 4.0.0-rc2-24027 ...
Publishing file System.IO.MemoryMappedFiles.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.IO.UnmanagedMemoryStream 4.0.1-rc2-24027 ...
Publishing file System.IO.UnmanagedMemoryStream.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Linq 4.1.0-rc2-24027 ...
Publishing file System.Linq.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Linq.Expressions 4.0.11-rc2-24027 ...
Publishing file System.Linq.Expressions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Net.Http 4.0.1-rc2-24027 ...
Publishing file System.Net.Http.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Net.NameResolution 4.0.0-rc2-24027 ...
Publishing file System.Net.NameResolution.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Net.Primitives 4.0.11-rc2-24027 ...
publish: Publishing System.Net.Sockets 4.1.0-rc2-24027 ...
publish: Publishing System.ObjectModel 4.0.12-rc2-24027 ...
Publishing file System.ObjectModel.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Private.Uri 4.0.1-rc2-24027 ...
publish: Publishing System.Reflection 4.1.0-rc2-24027 ...
publish: Publishing System.Reflection.Emit 4.0.1-rc2-24027 ...
Publishing file System.Reflection.Emit.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Reflection.Emit.ILGeneration 4.0.1-rc2-24027 ...
Publishing file System.Reflection.Emit.ILGeneration.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Reflection.Emit.Lightweight 4.0.1-rc2-24027 ...
Publishing file System.Reflection.Emit.Lightweight.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Reflection.Extensions 4.0.1-rc2-24027 ...
publish: Publishing System.Reflection.Primitives 4.0.1-rc2-24027 ...
publish: Publishing System.Reflection.TypeExtensions 4.1.0-rc2-24027 ...
Publishing file System.Reflection.TypeExtensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Resources.ResourceManager 4.0.1-rc2-24027
...
publish: Publishing System.Runtime 4.1.0-rc2-24027 ...
publish: Publishing System.Runtime.Extensions 4.1.0-rc2-24027 ...
publish: Publishing System.Runtime.Handles 4.0.1-rc2-24027
...
publish: Publishing System.Runtime.InteropServices 4.1.0-rc2-24027
...
publish: Publishing System.Runtime.InteropServices.PInvoke 4.0.0-rc2-24027 ...
Publishing file System.Runtime.InteropServices.PInvoke.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Runtime.InteropServices.RuntimeInformation 4.0.0-rc2-24027 ...
publish: Publishing System.Runtime.Numerics 4.0.1-rc2-24027 ...
Publishing file System.Runtime.Numerics.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Runtime.Serialization.Primitives 4.1.1-rc2-24027
...
Publishing file System.Runtime.Serialization.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Claims 4.0.1-rc2-24027 ...
Publishing file System.Security.Claims.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.Algorithms 4.1.0-rc2-24027 ...
Publishing file System.Security.Cryptography.Algorithms.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.Cng 4.1.0-rc2-24027 ...
Publishing file System.Security.Cryptography.Cng.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.Csp 4.0.0-rc2-24027 ...
Publishing file System.Security.Cryptography.Csp.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.Encoding 4.0.0-rc2-24027 ...
Publishing file System.Security.Cryptography.Encoding.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.OpenSsl 4.0.0-rc2-24027 ...
Publishing file System.Security.Cryptography.OpenSsl.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.Primitives 4.0.0-rc2-24027 ...
Publishing file System.Security.Cryptography.Primitives.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Cryptography.X509Certificates 4.1.0-rc2-24027 ...
Publishing file System.Security.Cryptography.X509Certificates.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Principal 4.0.1-rc2-24027 ...
Publishing file System.Security.Principal.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Security.Principal.Windows 4.0.0-rc2-24027
...
Publishing file System.Security.Principal.Windows.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Text.Encoding 4.0.11-rc2-24027 ...
publish: Publishing System.Text.Encoding.Extensions 4.0.11-rc2-24027 ...
publish: Publishing System.Text.RegularExpressions 4.0.12-rc2-24027 ...
Publishing file System.Text.RegularExpressions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading 4.0.11-rc2-24027 ...
Publishing file System.Threading.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Overlapped 4.0.1-rc2-24027 ...
Publishing file System.Threading.Overlapped.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Tasks 4.0.11-rc2-24027 ...
publish: Publishing System.Threading.Tasks.Dataflow 4.6.0-rc2-24027 ...
Publishing file System.Threading.Tasks.Dataflow.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Tasks.Extensions 4.0.0-rc2-24027 ...
Publishing file System.Threading.Tasks.Extensions.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Tasks.Parallel 4.0.1-rc2-24027 ...
Publishing file System.Threading.Tasks.Parallel.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Thread 4.0.0-rc2-24027 ...
Publishing file System.Threading.Thread.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.ThreadPool 4.0.10-rc2-24027
...
Publishing file System.Threading.ThreadPool.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Threading.Timer 4.0.1-rc2-24027 ...
publish: Publishing System.Xml.ReaderWriter 4.0.11-rc2-24027 ...
Publishing file System.Xml.ReaderWriter.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Xml.XDocument 4.0.11-rc2-24027 ...
Publishing file System.Xml.XDocument.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Xml.XmlDocument 4.0.1-rc2-24027 ...
Publishing file System.Xml.XmlDocument.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Publishing System.Xml.XmlSerializer 4.0.11-rc2-24027 ...
Publishing file System.Xml.XmlSerializer.dll to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
publish: Published to /Users/visten/.vscode/extensions/ms-vscode.csharp-1.1.6/coreclr-debug/debugAdapters
Published 1/1 projects successfully

@visten since you closed the issue, you might have figured this out yourself, but the issue is that you still have parts of a very old .NET CLI installed on your box. Unfortunately OSX doesn't have support for actually removing pkg's.
Here is the known issue item for this: https://github.com/dotnet/core/blob/master/cli/known-issues.md#uninstallingreinstalling-the-pkg-on-os-x
What I have done is:
sudo rm -rf /usr/local/share/dotnet

And then install the new pkg

When I open my project  with code . I get same error with different log:
Starting 'dotnet --info'
.NET Command Line Tools (1.0.0-preview2-003121)

Product Information:
 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  16.04
 OS Platform: Linux
 RID:         ubuntu.16.04-x64

Creating /home/matjazmav/.vscode/extensions/ms-vscode.csharp-1.1.7/coreclr-debug/project.json
Telemetry is: Enabled

log  : Restoring packages for /home/matjazmav/.vscode/extensions/ms-vscode.csharp-1.1.7/coreclr-debug/project.json...

error: System.IO 4.1.0-rc2-24027 provides a compile-time reference assembly for System.IO on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Globalization.Calendars 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Globalization.Calendars on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Globalization 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Globalization on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Diagnostics.Tracing 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Tracing on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Diagnostics.Tools 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Tools on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Diagnostics.Debug 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Debug on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Console 4.0.0-rc2-24027 provides a compile-time reference assembly for System.Console on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.

error: System.Collections 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Collections on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Diagnostics.Process 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Process on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Security.Cryptography.Algorithms 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Security.Cryptography.Algorithms on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.IO.MemoryMappedFiles 4.0.0-rc2-24027 provides a compile-time reference assembly for System.IO.MemoryMappedFiles on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: Microsoft.Win32.Primitives 4.0.1-rc2-24027 provides a compile-time reference assembly for Microsoft.Win32.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.AppContext 4.1.0-rc2-24027 provides a compile-time reference assembly for System.AppContext on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.IO.Compression 4.1.0-rc2-24027 provides a compile-time reference assembly for System.IO.Compression on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.IO.FileSystem 4.0.1-rc2-24027 provides a compile-time reference assembly for System.IO.FileSystem on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Net.Primitives 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Net.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Net.Sockets 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Net.Sockets on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Reflection 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Reflection on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Reflection.Extensions 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Reflection.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Reflection.Primitives 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Reflection.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Resources.ResourceManager 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Resources.ResourceManager on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Runtime 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Runtime.Extensions 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Runtime.Handles 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Runtime.Handles on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Runtime.InteropServices 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.InteropServices on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Runtime.InteropServices.RuntimeInformation 4.0.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.InteropServices.RuntimeInformation on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Text.Encoding 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Text.Encoding on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Text.Encoding.Extensions 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Text.Encoding.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Threading.Tasks 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Threading.Tasks on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: System.Threading.Timer 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Threading.Timer on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
error: One or more packages are incompatible with .NETCoreApp,Version=v1.0 (ubuntu.16.04-x64).

log  : Lock file has not changed. Skipping lock file write. Path: /home/matjazmav/.vscode/extensions/ms-vscode.csharp-1.1.7/coreclr-debug/project.lock.json

log  : /home/matjazmav/.vscode/extensions/ms-vscode.csharp-1.1.7/coreclr-debug/project.json
log  : Restore failed in 1188ms.

Error:

Error: Errors in /home/matjazmav/.vscode/extensions/ms-vscode.csharp-1.1.7/coreclr-debug/project.json
    System.IO 4.1.0-rc2-24027 provides a compile-time reference assembly for System.IO on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.

Error:     System.Globalization.Calendars 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Globalization.Calendars on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Globalization 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Globalization on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Diagnostics.Tracing 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Tracing on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Diagnostics.Tools 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Tools on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Diagnostics.Debug 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Debug on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Console 4.0.0-rc2-24027 provides a compile-time reference assembly for System.Console on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Collections 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Collections on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Diagnostics.Process 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Diagnostics.Process on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Security.Cryptography.Algorithms 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Security.Cryptography.Algorithms on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.IO.MemoryMappedFiles 4.0.0-rc2-24027 provides a compile-time reference assembly for System.IO.MemoryMappedFiles on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    Microsoft.Win32.Primitives 4.0.1-rc2-24027 provides a compile-time reference assembly for Microsoft.Win32.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.AppContext 4.1.0-rc2-24027 provides a compile-time reference assembly for System.AppContext on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.IO.Compression 4.1.0-rc2-24027 provides a compile-time reference assembly for System.IO.Compression on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.IO.FileSystem 4.0.1-rc2-24027 provides a compile-time reference assembly for System.IO.FileSystem on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Net.Primitives 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Net.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Net.Sockets 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Net.Sockets on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Reflection 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Reflection on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Reflection.Extensions 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Reflection.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Reflection.Primitives 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Reflection.Primitives on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Resources.ResourceManager 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Resources.ResourceManager on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Runtime 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Runtime.Extensions 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Runtime.Handles 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Runtime.Handles on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Runtime.InteropServices 4.1.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.InteropServices on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Runtime.InteropServices.RuntimeInformation 4.0.0-rc2-24027 provides a compile-time reference assembly for System.Runtime.InteropServices.RuntimeInformation on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Text.Encoding 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Text.Encoding on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Text.Encoding.Extensions 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Text.Encoding.Extensions on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Threading.Tasks 4.0.11-rc2-24027 provides a compile-time reference assembly for System.Threading.Tasks on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    System.Threading.Timer 4.0.1-rc2-24027 provides a compile-time reference assembly for System.Threading.Timer on .NETCoreApp,Version=v1.0, but there is no run-time assembly compatible with ubuntu.16.04-x64.
    One or more packages are incompatible with .NETCoreApp,Version=v1.0 (ubuntu.16.04-x64).

dotnet exited with error code 1

@matjazmav C# extension support for ubuntu 16 is coming soon. You can try opening your project on  ubuntu 14.

@matjazmav Ubuntu 16 is tracked with #469.

authors: gregg-miskelly matjazmav rajkumar42 visten


text:
Unable to load sample data into dotnet core app when running in debugger but runs fine in terminal

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview2-003131)
Product Information:
Version:            1.0.0-preview2-003131
Commit SHA-1 hash:  635cf40e58
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.11
OS Platform: Darwin
RID:         osx.10.11-x64
VS Code version: 1.7.1
C# Extension version: 1.4.1
Steps to reproduce
Cross posted on stackoverflow: http://stackoverflow.com/questions/40533821/unable-to-load-sample-data-into-dotnet-core-app-when-running-in-debugger-but-run
Try and load local project file for data parsing
XDocument sampleData = XDocument.Load(@"seed/Import_sampleData.xml");
Expected  behavior
Load file without error. Currently when the project is ran from the terminal using dotnet run the file is loaded correctly without error.
Actual behavior
File Exception error is returned when using the debugger to run the project
Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not find file '/Users/Chris/Google Drive/Repos/project/project.api/seed/Import_sampleData.xml'.

@chrisjmccrum is it trying to read from the path you are expecting? Does that file exist? If you modify your launch.json to set "justMyCode":false do you see any other exceptions?
I am pretty doubtful that this is an issue with the C# extension, but we can try and help you route this to the right place (CoreFX ore CoreCLR).

nevermind I figured it out... basically I have 2 library projects and then my api project all under one subfolder. So the debugger was starting at the root workspace folder that holds the three projects. I changed cwd to start in my api project since the other projects are pulled into it via dependencies and then it immediately found the xml files in my project.
Thank you for your support nevertheless!!

source: gharchive/issue

authors: chrisjmccrum gregg-miskelly

repo: OmniSharp/omnisharp-vscode

license: mit

license_type: permissive

license_source: bigquery


text:
Using Upload by SourceURL does not return status

https://dev.onedrive.com/items/upload_url.htm
Using this feature the response when checking the returned location does not return the progress.
I've been transferring large files (~100Mb) our of Amazon S3 into my OneDrive and they have been taking a while.  The "percentageComplete" is always 0.0
Response From Header Location:
{"operation":"DownloadUrl","percentageComplete":0.0,"status":"inProgress"}.
The documentation also says the the location URL will allow me to know when the file has finished uploading.  I have not seen the status go to a completed state, I just get a 404.
When uploading a file, it stays in the "notStarted" for a long time before proceeding. In one instance from 9:50 PM to 1035 PM MST for file id=6A1237F04038E20A%21457
{"operation":"DownloadUrl","percentageComplete":0.0,"status":"notStarted"}

Another thing that I have noticed is that item report as existing through the API before they show up through the web page.
I wonder if, similar to what is mentioned with using BITS-Packet-Type: Close-Session(https://gist.github.com/rgregg/37ba8929768a62131e85) if the connection needs to be closed so that the file is moved from the temp directory into my OneDrive.

@BertCotton I apologise for the delay - I didn't notice this land on me! Are you still seeing delays in downloading the URLs?

authors: BertCotton ificator

repo: OneDrive/onedrive-api-docs


text:
Short solution needed: "How to copy table" (lua)

Please help us write most modern and shortest code solution for this issue:
How to copy table (technology: lua)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to copy table

repo: Onelinerhub/onelinerhub

license: MIT

license_source: github-api


text:
Packchk xsd option checks dependencies as well

Describe the bug
When running packchk with the --xsd option in combination with the -i option, the pdsc files given as a dependency also have their xml checked against the given schema. This causes an issue when we validate a pack using an older version of the schema with a dependency on a pack using a newer version.
To Reproduce
Run packchk with the --xsd option on a pack using an older version, e.g. V1.7.7, with a dependency passed in using the -i option that uses a newer schema, e.g. V1.7.36.
The schema validation will pass for the pdsc file being checked, but warnings will potentially be raised for the dependency pack.
Expected behavior
No warnings for the dependency pack should be raised - it is there for validation of components only.
Environment (please complete the following information):
PackChk 1.4.1
Windows 10

Change request: run schema check only for the pdsc file under test and not for the pdsc files specified using -i option.

authors: Jonny-vb jkrech

repo: Open-CMSIS-Pack/devtools


text:
Docstrings - inline code docs

Something that is still missing comparing this repository with the old openeo-processes-python are docstrings, can we consider adding them? Is there a reason why they were not ported over?
It could be also useful to point out the openEO processes version we are targeting in each process implementation.

No real reason other than the combination of:

the previous docstrings being outdated in some places and therefore not immediately portable
not having docs autogenerated with e.g. sphinx, so the utility being somewhat lower
us just not taking the time to do this properly
I think this is probably something that wants to be added gradually, feel free to add some when it's convenient.

I'll create an issue to setup docs generation, that's probably a good thing to have at some point.
About the spec version, not entirely sure about that. We could either define a version of openeo that the entire repo targets, or as you propose point it out separately in each process implementation. I feel that one version for all is much less effort for about the same benefit, just because I don't think we'd ever have multiple versions of the same process in this repo. I imagine there's a clever way of versioning/releasing this package to support separate 1.1/1.2/2.0 tracks, but given the maturity of this repo, I don't think this should be a priority anytime soon.

authors: LukeWeidenwalker clausmichele

repo: Open-EO/openeo-processes-dask


text:
Changing product card UI and adding hover effects

Changed Product Cart UI
Added hover effects
Resolved Conflicts
Made responsive

Hey @nandita27iitp changes to package-lock.json will not be accepted , please commit again ensuring no changes to package-lock.json.

But I havent made any changes to package-lock.json

ok @nandita27iitp I have fixed it now next time while making a pr you should watch which files have been changed.

ok @nandita27iitp I have fixed it now next time while making a pr you should watch which files have been changed.

Great! Will make a note of that.

source: gharchive/pull-request

repo: Open-Source-Chandigarh/Brewtopia


text:
[Build] Split Python "internal" tests into "module" and "bridge" tests

Closes #739.
A little refactoring sneaked in, especially the first few commits.
In particular, there's an update to the Conan generator we use, so that the frustrating pybind11 Conan package bug, which prevents use of pybind11 when embedding a Python interpreter (see commit message and https://github.com/OpenAssetIO/OpenAssetIO/issues/528), is fixed.

Converted to draft to address CI failures.

Quick Q - whilst we're rejigging things here - what do people think about module -> cmodule to middle disambiguate that we have module and package dirs (as package technically also contains other "modules")?

Quick Q - whilst we're rejigging things here - what do people think about module -> cmodule to disambiguate that we have module and package dirs (as package technically also contains other "modules")?

Added a commit at the end (512ed5a) to do this, but can move it to the beginning if you think the git wrangling is worthwhile.

Quick Q - whilst we're rejigging things here - what do people think about module -> cmodule to disambiguate that we have module and package dirs (as package technically also contains other "modules")?

Added a commit at the end (512ed5a) to do this, but can move it to the beginning if you think the git wrangling is worthwhile.

Im happy for this to go later. I was wondering what the final commit granularity was here too, happy to squash some of the "similar" cmake tweaks together too.

happy to squash some of the "similar" cmake tweaks together too.

I've squashed a few of the later commits together (renaming module/internal to cmodule and moving the test config to its own CMakeLists.txt).  How does that look?

authors: feltech foundrytom

repo: OpenAssetIO/OpenAssetIO


text:
🛑 OpenBB.co is down

In a1ec580, OpenBB.co (https://openbb.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OpenBB.co is back up in cf93e3e.

repo: OpenBB-finance/uptime


text:
关于许可证

Hi，我想知道具体该如何申请商用许可证，目前我们向cpm@modelbest.cn这个邮箱发送了申请，但是没有得到回复，不知道是不是我们申请的流程不符合贵公司的要求。

👋，即日起商用许可申请可通过该二维码～
@Pickpate

https://mp.weixin.qq.com/s/NvM3eTvVBX4A8IUWsh3Y9w 👋，即日起商用许可申请可通过该链接下二维码～ @Pickpate

您好，这个我们申请了下，但是发现贵方给的许可证把被许可人填写成了“填表的个人”而不是我们公司，麻烦贵方关注下这个问题吧。
另外为了方便沟通，请问贵方有比较官方的群或者其他联系方式么？很希望得到贵方的许可。

您好，我想加一个问题。关于这个条款，我有如下疑问，还请帮忙解答下吧：
If you distribute or provide MiniCPM series model materials (or any derivative works thereof), or use any product or service of them, you must (A) provide a copy of this agreement; and (B) prominently display "Built with 面壁MiniCPM" on the relevant website, user interface, blog post, about page, or product documentation. If you create, train, fine-tune, or improve an AI model using the MiniCPM series models, the model must include "MiniCPM" in its name.
请问下，当把模型部署起来对外提供服务时需要遵守全部的这3个要求么？我理解，除非对外提供API服务，一般基于模型的应用（比如一个bot）层的服务都不会对模型进行命名并对外披露该命名。另外提供协议的copy一般是在在对外分发（发送材料给别人时）模型材料，所以在基于模型对外提供服务时，也需要提供协议副本么？

authors: Cuiunbo Pickpate

repo: OpenBMB/MiniCPM-V


text:
请问MiniCPM-V能使用类似stream为True的参数来实现流式生成吗？

请问MiniCPM-V如何使用流式的方式生成？像是使用transformers的streamer之类的。
另外，好像model.chat输入temperature或top_p是不生效的，看代码是已经写死了。

感谢关注，我们近期会支持流式输出

Add this to future plan

感谢关注，我们近期会支持流式输出

现在可以了吗


text:
[BUG] ./script/run_inference.sh MiniCPM-Llama3-V-2_6 MathVista_MINI all

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
Did not detect the .env xxxxx/MiniCPM-V/eval_mm/vlmevalkit/.env, failed to load.
期望行为 | Expected Behavior
Did not detect the .env xxxxx/MiniCPM-V/eval_mm/vlmevalkit/.env, failed to load.
复现方法 | Steps To Reproduce
No response
运行环境 | Environment
- OS:
- Python:
- Transformers:
- PyTorch:
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`):

备注 | Anything else?
Did not detect the .env xxxxx/MiniCPM-V/eval_mm/vlmevalkit/.env, failed to load.

Hello, Thank you for your attention. This is a system warning, and will not affect the inference

And also you can try using the official vlmevalkit!
https://github.com/open-compass/VLMEvalKit

authors: Cuiunbo luyao-cv


text:
Some translations require plural for word "found"

v2.2.3
Some languages require two different translations (singular and plural) to word "found" in messages:
"1 listing found" and "2 listings found".
In spanish it should be:
"1 listado encontrado" and "2 listados encontrados".
This is needed in Store page and in Orders page:

@jjeffryes
Fix is not working.
I've set "countListingsFound": "%{smart_count} encontrado |||| %{smart_count} encontrados", in translation file, but it is displaying this way:

But it should be "1 anúncio encontrado" and "51 anúncios encontrados"

That's a bug in the data being sent for that translation, I found the issue and will be putting in a patch for it.
Thank you for catching that!

authors: jjeffryes rhcastilhos

repo: OpenBazaar/openbazaar-desktop


text:
Purchasing

This adds the initial code for the purchase screen, and the moderation section.
The moderation section has it's own view and collection, separate from the code used in the settings/store tab. The plan is to use this new code in a future refactor of the store tab.
The moderation section has the following functionality:

loads the listing's moderators asynchronously
if a moderator is invalid or an error is returned for that id, the moderator is loaded in an "error" state
the first valid moderator to load is selected
the moderator cards have been changed to have separate view and select buttons. The buttons can have a selected, unselected (faded select) or deselected (red X) state.
when one moderator is selected, the other moderators are deselected.
when the moderated transaction checkbox is unchecked, the moderators are deselected and the moderator is unset from the order model.
when the moderated transaction checkbox is checked again, any selected moderator from before it was checked is rechecked

This PR also includes css to set emojis to the same size as any parent text size class.
This PR adds in the code to make the message button in the moderator details modal work, which closes #408

@morebrownies you'll want to take a look at this, both when purchasing something and in the settings/store tab, for the tweaks to how selecting a moderator work.

The modal needs to handle the case of a listing having no moderators, whether that's not making the Moderated Payment checkbox and Moderator box visible or offering some type of messaging (or something else).

@rmisio this is ready for re-review, all the requested changes have been made, plus I've broken out the models with sub-collections and models, and added some CSS so emojis are sized according to the text class that affects them automatically.

@morebrownies we still need you to take a look at this, specifically the changes to how the moderator cards work.

@jjeffryes I'm attempting to add a moderator to my store and I'm running into this issue when I hit save:

Do you have a store setup with moderators already added that I can test?

@morebrownies your screenshot doesn't look like it loaded. What issue are you hitting with save?

@morebrownies well, that's not a very informative error. Have you cleared your data recently? A number of things have changed.
You can try clicking purchase on ob://QmYcZjTpcpqnMpdPSyz27zVNkfWNsGaFWByAAu1pUBBQaN/store/test

I cleared my db this morning. I'll clear it again and see if I get the same error.

Ok, issue fixed after reseting my DB.
Anyways, I think it's mostly working pretty well now. I do find it a bit strange that there's a big checkbox button next to each moderator in the moderator list. That checkbox button is really functioning like a radio button and would probably be less confusing if we used a radio button instead.
@jjeffryes I know you mentioned you coded it this way so that you could reuse logic between views. That's probably fine in the short term, but we should circle back at some point to clean this
Current

Design

@morebrownies If we switched it to a radio button, it would be a radio button in the settings/store tab too.  Is that ok?

@morebrownies If we switched it to a radio button, it would be a radio button in the settings/store tab too. Is that ok?

@jjeffryes I think Mike was fine with circling back to it. When we do, there's no reason we can't re-use the same view, but have slight differences in look / feel and behavior. Assuming there's enough commonality in the behavior that we would want to re-use (which I guess there would be based on how the content is loaded... is that correct?), we could just pass in some flags to use a radio or a checkbox. A radio selected would send a different event than the checkbox being selected, so the consumer could customize the behavior based off of that.

@morebrownies If we switched it to a radio button, it would be a radio button in the settings/store tab too. Is that ok?

no that wouldn't work. Settings should support selecting many (checkboxes) while checkout should only allow you to select one (radio buttons)

authors: jjeffryes morebrownies rmisio


text:
level-Werte für Stockwerke

Die Defikarte-App scheint den level-Wert als Freitext einzugeben, jedenfalls irgeneine Version davon, siehe https://github.com/OpenBracketsCH/defikarte.ch-app/issues/151
In den OpenStreetMap-Daten finden sich viele solche Werte, die dann nicht (einfach) maschinenlesbar sind, siehe Screenshot aus taginfo.openstreetmap.ch. Alle diese Daten stammen aus der defikarte-App.

Laut OSM Wiki sollte level mit ganzen Zahlen erfasst werden, allfälliger Freitext gehört in level:ref.
Ist es möglich, das anzupassen, dass so keine 'falschen' Daten in der OpenStreetMap-Datenbank landen, die dann immer wieder händisch korrigiert werden müssen?

Danke für die Meldung. Ich passe das an.

App now accepts only digits as input field in the level segment. also negative digits are possible. Android and iOS Apps are updated and available in the store.

authors: chnuessli elektrolytmangel habi


text:
Ran 2 more tests on Zoo dataset with High Resolution configs

Ran 2 more tests with Zoo dataset with High Resolution configs

Looks good; thank you for sharing these.

Thanks for sharing result to the community. BTW what is your machine spec? R710 with 1 or 2 CPU? and what is the storage SSD or Harddisk? What is the speed of your storage? Thanks

@sasanai 2 CPU, I have 4 SAS drives in a RAID 0. Speed is 10k

authors: coreysnipes fpolignano sasanai

repo: OpenDroneMap/odm-benchmarks


text:
🛑 Hypothèses is down

In cc6ae60, Hypothèses (https://hypotheses.org) was down:

HTTP code: 503
Response time: 564 ms

Resolved: Hypothèses is back up in 09feee1 after 17 minutes.

repo: OpenEdition/OEStatus


text:
scaleWidth计算的有问题.

首先, 文档中说传入的设计稿尺寸是物理像素值, 例如750x1334.
然后计算比例的实现是这样的:
  ///实际的dp与设计稿px的比例
  get scaleWidth => _screenWidth / instance.width;

  _screenWidth = mediaQuery.size.width;

_screenWidth是逻辑像素值, 比一个物理像素值instance.width, 这结果是有问题的.
应该这样计算:
  get scaleWidth => _screenWidth * _pixelRatio / instance.width;

最后setWidth()方法传入设计稿上的像素值, 比如设计稿上一个按钮宽40像素:
ScreenUtil.getInstance().setWidth(40)

我认为这样才是对的.
请指教.

嗯 。。。
我的注释写的是
///实际的dp与设计稿px的比例

就。。我就是想拿到一个dp与px的比值。。

不好意思, 我知道我哪想错了, fontSize、width属性接收的值的单位是dp, 我算出来的结果是px, 需要再除一个像素比, 简化一下就是您的算法.

authors: lizhuoyuan lyodooo


text:
Unsupervised Pre-training Results

Thank you for sharing your code! From my understanding, you utilize the semantic labels from multiple datasets by leveraging their corresponding CLIP features, similar to the approach in the Point Prompt Training paper. I was wondering if you might have any results for cases where you didn’t use semantic labels but instead relied solely on rendering as a pretraining task?

Hi, thanks for your question! We haven't done that yet since we build our work upon the existing codebase (pointcept). However, you could definitely try it by, for example, one head per dataset. I believe the results will not have a significant difference.

authors: HaoyiZhu YilmazKadir


text:
needed 669H7_recovery.img

Hi. Help restore the camera to the factory software. needed 699H7_recovery.img

000699H7

repo: OpenIPC/coupler


text:
Deprecate Xiongmai chips support

Due to lack of testers for XM platform (and nobody is willing to fix osmem issue discussed in Majestic Telegram group) I suggest dropping XM support from the project by end of 2022

I would extend this to anyka and mstar chips
mstar needs userspace tools from android and uclibc - highly unlikely to happen
anyka is a living antipattern of how to do things, tonns of hardcode in kernel, including hardcoded gpios ann muxctls, lack of uboot sources, non working sdk's...

Gentlemen, you forgot to mention in the removal list the GrandMedia processors that are no longer produced, Ambarella which is too expensive, Rockchip which is too complicated to understand.

I'd take Rockchip support using freed time from outdated platforms

This will be a sad day for my xm510 camera... What do you need on testing side? I can look into functionalities on my camera and fill issues like https://github.com/OpenIPC/firmware/issues/248 (where the issue is somewhere between majestic and the overlay fs).
I would be also happy to test the GPIO for the XM510, but was unable to find any documentation, how to.
Thanks

There is no documentation for XM chips, everything should be obtained from reverse engineering (like digging a lot in IDA)
For XM510, fixing overlayfs would be a good starting point

I played around with the overlayfs settings and I think this is a bug in the overlayfs implementation with 3.0.101 kernel. Based on the patch for xm510 the overlayfs version is v11, but what is the origin code for that patch?

Sad to see this, just got 40 XM530_80X30T_8M camera's and found out about this project. What can I do to help testing? I'm no programmer, just a little handy.

The best thing you can do - find developers who would be interested in Xiongmai platform

Created a pull request to fix an issue with overlayFS https://github.com/OpenIPC/microbe-web/pull/116

authors: HakGit ZigFisher dimerr schneemaier widgetii

repo: OpenIPC/firmware


text:
split os image and datablock image in sunstone

Author Name: alan zhang (alan zhang)
Original Redmine Issue: 3930, https://dev.opennebula.org/issues/3930
Original Date: 2015-08-10

when we create datablock image，we need fill in more blank. it's not easy to use.
maybe we can design datablock image like AWS  split images  and ebs.

Original Redmine Comment
Author Name: Daniel Molina (Daniel Molina)
Original Date: 2015-08-17T13:44:24Z

In OpenNebula 4.14 you will be able to resize any of the disks when a template is instatiated, would that be enough?

Seems done already

authors: OpenNebulaProject rsmontero

repo: OpenNebula/one


text:
Task: Create oauth endpoints

Chat
https://chat.openai.com/share/cd181779-6d66-4e6c-9a4c-4bfd25db80b0
Description
To offer a oauth authentication in plugins this python API will need to offer two endpoints for handling the oauth exchange.
Tasks
These tasks are set up to be used as part of the ChatGPT prompts along with any additional context required. They don't need to be strictly followed but it is encouraged to use them as a guide.

[x] GET /oauth_initialization endpoint

[ ] it will receive as params {client_id: string, client_domain: string, authorization_url: string, token_url: string, openplugin_callback_url: string, authorization_content_type: string}
[ ] the session should store all of these variables so that once the user is done authenticating at the authorization_url this session can be retrieved
[ ] use client.prepare_authorization_request and redirect the user to the authorization_url

[x] GET /oauth_token endpoint

[ ] it will receive param state and code  use these to get the current session
[ ] fetch the mongodb collection openplugin-auth by matching its domain with client_domain from the state and it will contain an object of type OpenpluginAuth, retrieve the client_secret from that.
[ ] make a post request to the token_url together with the token information received from client.prepare_token_request.  The redirect_url will be /oauth_token. make sure to use the correct headers and data depending on the authorization_content_type.
[ ] parse the response data with client.parse_request_body_response and redirect to openplugin_callback_url with the response (each of the items as URL parameters), the client_domain, and oauth_token as true passed as urlencoded params

completed df73a46

repo: OpenPluginACI/openplugin-api


text:
Whimsical and ShowMe don't work

Plugin namespace
show_me_diagrams and whimsical
Error log
It either throws an error (TypeError: Session.request() got an unexpected keyword argument 'mermaid'), or just says "As an AI text-based model, I'm unable to create visual diagrams.".
Your code
I was playing with the google colab notebook, having "Explain how a car works using a visual diagram." as the prompt.
Extra
I used gpt-4-0613 and gpt-3.5-turbo-0613 and the result is the same for both.

@weronikazak Hey so I managed to resolve it for show_me_diagrams. Granted I could not get the plugin to be called with "Explain how a car works using a visual diagram." so instead I did this https://github.com/OpenPluginACI/openplugin/blob/main/pypi-core/tests/test_e2e.py#L322-L345 . As for whimsical, it seems like they are restricting who makes API calls to them (aka I'm not whitelisted), you could reach out to them for access.

authors: CakeCrusher weronikazak

repo: OpenPluginACI/openplugin


text:
cups-browsed SEGFAULTs when cupsEnumDests() returned dest has no "device-uri" option

cups-browsed 1.20.0 crashes when starting up on Gentoo Linux.
I have a CUPS print server in my LAN that advertises printers through DNS-SD.
# cups-browsed --debug
Fri Feb  2 18:20:40 2018 Reading command line option --debug, turning on debug mode (Log on standard error).
Fri Feb  2 18:20:40 2018 cups-browsed of cups-filters version 1.20.0 starting.
Fri Feb  2 18:20:40 2018 Reading config: BrowseRemoteProtocols dnssd
Fri Feb  2 18:20:40 2018 Reading config: CreateIPPPrinterQueues All
Fri Feb  2 18:20:40 2018 No "Browse..." line at all, accept all servers ("BrowseOrder Deny,Allow").
Fri Feb  2 18:20:40 2018 main() in THREAD -1225566704
Fri Feb  2 18:20:40 2018 cups-browsed: Creating http connection to local CUPS daemon: /run/cups/cups.sock:631
Fri Feb  2 18:20:40 2018 update_netifs() in THREAD -1225566704
Fri Feb  2 18:20:40 2018 network interface at 192.168.0.38
Fri Feb  2 18:20:40 2018 cups-browsed [BrowsePoll /run/cups/cups.sock:0]: IPP-Create-Subscription
Fri Feb  2 18:20:40 2018 cups-browsed [BrowsePoll /run/cups/cups.sock:0]: subscription ID=58
Fri Feb  2 18:20:41 2018 cups-browsed (/run/cups/cups.sock): cupsEnumDests
Segmentation fault

I could debug it so far that in cups-browsed.c in get_local_printers(void) when iterating through dests, the device_uri is NULL (for some printers?).
For example:
{
  name = 0x7d714 "HP Deskjet 6940 @ Print-Server",
  instance = 0x0,
  is_default = 0,
  num_options = 5,
  options = 0x7fbe8 {
    {name = 0x7e2fc "printer-info", value = 0x7d714 "HP Deskjet 6940 @ Print-Server"},
    {name = 0x7bccc "printer-location", value = 0x7d904 "Keller"},
    {name = 0x7bd1c "printer-make-and-model", value = 0x7014c "HP Deskjet 6943 Printer"},
    {name = 0x7d144 "printer-type", value = 0x7d0fc "36894"},
    {name = 0x70a4c "printer-uri-supported", value = 0x7e314 "ipps://HP%20Deskjet%206940%20%40%20Print-Server._ipps._tcp.local/cups"}
  }
}

As a result the application segfaults in new_local_printer(device_uri, cups_browsed_controlled) on line 765, because device_uri is NULL
  printer->device_uri = strdup (device_uri);

Fixed in 3dd9b4. Thank you for your bug report.

repo: OpenPrinting/cups-filters


text:
TC Meeting 2024-02-22

The OpenRail Technical Committee is holding a weekly meeting. The agenda is prepared in issues and the protocols are stored in the meetings folder.
Please add additional topics or any other comments by commenting on this issue.
Agenda
For this meeting the maintainers of OSRD are invited as guests. The main topic of the meeting is the onboarding of OSRD as first official project of the OpenRailAssociation

Introductions
Overview of role and tasks of technical committee
Representative of OSRD in Technical Committee
Project governance
Moving the repositories to the OpenRailAssociation organization

#33

repo: OpenRailAssociation/technical-committee


text:
MIECD UAT Issues #1

Logface View

[x] For pregnancy registration (DKY) messages, when the risk category is NOT SET, simply leave it as GREY text without any box/border.  It should be greyed out, to show that it is not a categorization.

[x] Risk categorization should be clickable and should take the user to the patient view.On click of the risk category, there should be a link to open the patient view.

[x] In the logface remove SMS ID column

[x] The Back in Compartment takes the user back to the very first compartment page . This should take you back to the previous page.

Compartments View

[x] Within the compartments, change the category risk colors from orange to yellow

[x] At the end of the locations disaggregation(All the way to the commune), if there is no patient to show in the log the village level, display there is no patient in this record instead of leaving it empty.

[x] Within the compartment, the total should be clickable , and should follow similar actions to the risk categorizations. This means the total column should be highlighted and on click, the locations show according to the hierarchy

[x] In the compartment table, the area for clicking should be bigger as people are not always specific with clicking just the name of the location.  This means the whole row should be clickable.

[x] In Compartments, have the card that contains delivery due in one week to come before the deliveries due in 2 weeks. Preferred changes are to have the card with the 1 week first, then the 2 weeks, and then totals. Make the font bigger, and circles bigger. The circles should be clickable. Logface and compartments are both hard to see due to the size. Make the font size bigger. Consider having compartments (Total, 1 week, 2 weeks) broken down into 2 rows.

@hmakandi, I'm going to split this issue into smaller issues in order to be able to more easily  make smaller PRs.

This is ok. Thanks @FrankApiyo

Closed the main issue and the child issues.

authors: FrankApiyo hmakandi

repo: OpenSRP/opensrp-web


text:
class[class com.mongodb.MongoClient] before method[execute] intercept failure  java.lang.NullPointerException

ERROR 2017-10-11 17:54:36 InstMethodsInter :  class[class com.mongodb.MongoClient] before method[execute] intercept failure
java.lang.NullPointerException
ERROR 2017-10-11 17:54:36 InstMethodsInter :  class[class com.mongodb.MongoClient] after method[execute] intercept failure
java.lang.IllegalStateException: No active span.
at org.skywalking.apm.agent.core.context.TracingContext.activeSpan(TracingContext.java:342)
at org.skywalking.apm.agent.core.context.TracingContext.activeSpan(TracingContext.java:33)
at org.skywalking.apm.agent.core.context.ContextManager.activeSpan(ContextManager.java:144)
at org.skywalking.apm.agent.core.context.ContextManager.stopSpan(ContextManager.java:148)
at org.skywalking.apm.plugin.mongodb.v3.MongoDBMethodInterceptor.afterMethod(MongoDBMethodInterceptor.java:170)
at org.skywalking.apm.agent.core.plugin.interceptor.enhance.InstMethodsInter.intercept(InstMethodsInter.java:83)
at com.mongodb.Mongo.execute(Mongo.java)
at com.mongodb.Mongo$2.execute(Mongo.java:759)
at com.mongodb.OperationIterable.iterator(OperationIterable.java:47)
at com.mongodb.OperationIterable.forEach(OperationIterable.java:70)
at com.mongodb.MappingIterable.forEach(MappingIterable.java:50)
at com.mongodb.MappingIterable.into(MappingIterable.java:60)
at com.mongodb.DB.getCollectionNames(DB.java:253)
at com.mongodb.DB.collectionExists(DB.java:476)
at org.springframework.data.mongodb.core.MongoTemplate$6.doInDB(MongoTemplate.java:518)
at org.springframework.data.mongodb.core.MongoTemplate$6.doInDB(MongoTemplate.java:516)
at org.springframework.data.mongodb.core.MongoTemplate.execute(MongoTemplate.java:446)
at org.springframework.data.mongodb.core.MongoTemplate.collectionExists(MongoTemplate.java:516)
at org.springframework.data.mongodb.core.MongoTemplate.collectionExists(MongoTemplate.java:512)
at cn.ce.platform_service.admin.dao.impl.AdminDaoImpl.init(AdminDaoImpl.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:354)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:305)
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:133)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1575)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:553)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1123)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1021)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:545)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:331)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1219)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:551)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.findAutowireCandidates(DefaultListableBeanFactory.java:1199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1123)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1021)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:545)
at org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:88)
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.java:331)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1219)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:551)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:778)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:843)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:541)
at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:666)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:632)
at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:680)
at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:551)
at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:492)
at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:136)
at javax.servlet.GenericServlet.init(GenericServlet.java:158)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1183)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1099)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:989)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4931)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5241)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:752)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:728)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:988)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1860)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
mongodb 报错

@jameskypee This seems a bug of mongodb plugin. Can you provide a demo application?
cc @ascrutae

cc @bai-yang

@jameskypee 是否能提供更进一步的信息？我将保留此问题48小时，之后将关闭。

@jameskypee 因为此问题已经无更新19天，所以暂时关闭此问题。

authors: jameskypee wu-sheng

repo: OpenSkywalking/skywalking


text:
make run-prod fails

Describe the bug
In the readme is a description how to start openslides4:
https://github.com/OpenSlides/OpenSlides/blob/4484d1e4ef5274e6868fe2b1840814673d2e0282/README.md
Currently, they do not work.
How to Reproduce
$ git clone git@github.com:OpenSlides/OpenSlides.git
$ cd OpenSlides
$ git checkout openslides4-dev  # needed, until OS4 is released
$ make run-prod

This produces:
git submodule status | awk '{ gsub(/[^0-9a-f]/, "", $1); gsub("-","_",$2); print toupper($2)"_COMMIT_HASH="$1 }' > .env
docker-compose -f docker-compose.yml -f docker-compose.prod.yml build
WARNING: The OPENSLIDES_DATASTORE_READER_PORT variable is not set. Defaulting to a blank string.
WARNING: The OPENSLIDES_DATASTORE_WRITER_PORT variable is not set. Defaulting to a blank string.
WARNING: The OPENSLDIES_AUTH_SERVICE_COMMIT_HASH variable is not set. Defaulting to a blank string.
WARNING: The OPENSLDIES_AUTH_SERVICE_PORT variable is not set. Defaulting to a blank string.
ERROR: The Compose file is invalid because:
Service backend has neither an image nor a build context specified. At least one must be provided.
make: *** [Makefile:25: build-prod] Fehler 1

Expected behavior
Start OpenSlides without errors and warnings.
Could someone help me to start OpenSlides4 so I can work on #5476?

Ok. I found the information here: https://github.com/OpenSlides/OpenSlides/pull/5476/files#diff-f785e9e46b9afd2567df7a658338db17
So #5476 fixes this issue.

In #5476 it won't be fixed in the way, that it works, but it will be fixed because there is a new notice, to not use prod ;) dev is currently the way to go.
https://github.com/OpenSlides/OpenSlides/pull/5476/files#diff-04c6e90faac2675aa89e2176d2eec7d8R21

authors: FinnStutzenstein ostcar

repo: OpenSlides/OpenSlides


text:
Users cannot change their own password

Describe the bug
If the user attempts to change her/his own password, a success message displayed, but the password is not changed.
How to Reproduce

Install OpenSlides 4.0.16.
Log in with username superadmin and password that was set up during installation
Open user menu > “My account” > “Change password”
Type password that was used to login into “Old password” field
Type a different password into “New password” and “Confirm new password” fields
Click “Save”
A message “Password changed successfully!” is displayed.
Log out and attempt to log in again.

Observed behavior

Login with the password set up during installation is possible.
Login with the changed password is rejected.

Expected behavior

Login with the password set up during installation is rejected.
Login with the changed password is possible.

System information

OpenSlides version: 4.0.16
OS: Debian Linux
Browser: Firefox
Browser version: 120.0

Additional context

It seems that the message “Password changed successfully!” is always displayed, even if the original password is wrong.
The following messages are logged in the backendAction container when changing the password:

INFO:openslides_backend.shared.handlers.base_handler:Performing action user.set_password_self.
ERROR:openslides_backend.shared.handlers.base_handler:Error occured on index 0: Wrong password

Thanks for spotting this! We will fix it as soon as possible.

authors: jsangmeister mdickopp


text:
Macro option "hold repeat" does not deactivate after release of button

Expected Behavior
While using the macro activation type option "hold repeat" while having macro button held down macro should repeat until it is released then it should stop replaying the macro sequence.
Current Behavior
In current  v0.7.9 RC1 release, macro activates then does not stop, requiring to unplug the pcb.
Context

Firmware version =  v0.7.9 RC1
Board config name = GP2040-CE_0.7.9_RP2040AdvancedBreakoutBoardUSBPassthrough.uf2
Name of device = GP-2040-CE v5.6E (usb-c-usb-b)
purchased from Focusattack.com (currently unlisted/sold out)

Steps to Reproduce
Screenshot provided will explain
Screenshots & Files

Tested this on RC1.
The first test was a random setup of macros to check overall function - no issues.
The second test was a copy of the setup presented in the reported issue - was able to replicate.
The third test was changing exclusive to interruptible - no issues.
Conclusion from testing is that the combination of exclusive and hold repeat causes the loop.

Should be fixed in RC2!

Ok so with RC2 it does indeed stop upon releasing the button
problem is the macro is not executed on the initial button press, it is only fully executed if you hold the assigned button(s) for the whole duration of the macro. upon releasing the macro buttons at any time, the macro input sequence will stop at the very frame you release the macro button(s).
this is with hold repeat selected

Hi @wesleysni ,
Good catch here.  We will have to talk internally to see if this is a bug or how the original function of toggle was intended to work.

Hi @wesleysni ,
We have talked internally and this is the intended function of the modes.  The same behaviour happens on the toggle setting.
Our definitions for the various modes are:

Press - Full press of button triggers the macro once (full string)
Hold Repeat - Holding button to repeatedly triggers macro (will stop macro mid-string when released)
Toggle - Full press of button causes the macro to repeatedly trigger, another full press of the button will stop the macro from repeatedly triggering (will stop macro mid-string when toggled off)

I will update the documentation to make this more clear.

authors: TheTrainGoes arntsonl wesleysni


text:
Custom LED implementation

This is the firmware implementation for https://github.com/OpenStickCommunity/GP2040-CE/issues/107.
This PR requires https://github.com/OpenStickCommunity/WebConfigurator/pull/38 for the UI updates.
A new animation mode for Custom Theme has been added. If enabled, this mode will use the new CustomTheme and CustomThemePressed animation subclasses and configured LED options to display a customized static theme with customized button color presses, as the issues requested.
In the process of debugging I reworked how the pressed animation is created since it was only created as a fallback instead of when needed like the base animations.
If we want to do any customized themes with animations that will require a larger refactor or migration of the LED controller library.

This should be functionally ready now. Summary of changes not directly related to this feature:

Fixed excessive memory use in webconfig.cpp when deserializing POST data
Bumped stack size up to 4kb with add_compile_definitions(PICO_STACK_SIZE=0x1000) in CMakeLists.txt
Updated ArduinoJson library to v6.21.2
Fixed issue where user couldn't use the Previous Animation shortcut to cycle around the animation list (needed explicit cast to check for negative)
Pressed animations are now properly created and destroyed like normal animations
Pressed animations should flicker much less when changing animations


text:
Update jsDelivr links

jsDelivr switched to a fully automated system, that can serve files from npm and GitHub. This means all future releases will be available automatically, but will use a new link structure.
I updated the links now so you don't forget to do it when you release a new version.
You can find links for all files at https://www.jsdelivr.com/package/npm/yasgui-yasr.
Feel free to ping me if you have any questions regarding this change.

Thanks  @LukasDrgon , had no clue jsdelivr changed their API! I updated it in my build script instead (the link is dynamically updated based on the latest version)
Thanks for letting me know

authors: LaurensRietveld LukasDrgon


text:
🛑 Text-to-Speech - Piper - Ziggyai is down

In 6b78c6d, Text-to-Speech - Piper - Ziggyai (https://pipertts.ziggyai.online/status) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Text-to-Speech - Piper - Ziggyai is back up in 5f59aef.

repo: OpenVoiceOS/status


text:
Epic: PD -- TC State Step Form (Also see 5567)

For reference:
Thermocycler form field values:
// Flow Type (FormData isn't typed :( so this is just for reference)
{|
    thermocyclerFormType: 'thermocyclerState' | 'thermocyclerProfile',
    moduleId: string,

    blockIsActive: boolean,
    blockTargetTemp: string | null, // string is a string of a number eg '4'
    lidIsActive: boolean,
    lidTargetTemp: string | null,  // string is a string of a number eg '4'
    lidOpen: boolean | null // if false, closed. If null, it's the initial unknown state

    // TODO later we will add the TC Profile fields here
|}

// form initial values
{
    thermocyclerFormType: 'thermocyclerState', // since this field is disabled, might as well set it to the only possible value for now
    moduleId: null, // to be set dynamically via createPresavedStepForm (#5596)

    blockIsActive: false,
    blockTargetTemp: null,
    lidIsActive: false,
    lidTargetTemp: null,
    lidOpen: null // Still TBD as per convos on Slack, but let's start with null = unknown initial lid state

    // TODO later we will add the TC Profile fields here
|}

ThermocyclerModuleState: see https://github.com/Opentrons/opentrons/issues/5609

All tickets done!

repo: Opentrons/opentrons


text:
fix(components): update Icon to support a svg that has multiple paths

Overview
update Icon to support a svg that has multiple paths
update icon data types.
close AUTH-901 AUTH-922

Test Plan and Hands on Testing

Changelog

update Icon component
update icon-data.ts

Review requests

Risk assessment
mid because all projects use Icon component

[ ] compare this pr and edge

[ ] fix app test error

close this sicne Mel provided new svgs for new icons


text:
CQL dialect name not using "DMTF:CQL" format

I tried to execute the following CQL query:
wsman -h localhost -u user -p pass  enumerate 'http://schemas.dmtf.org/wbem/wscim/1/*'  --dialect="http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" --filter="SELECT Name, VendorName FROM CIM_PCIDevice WHERE ClassCode = 12"

If the local CIMOM is sblim-sfcb, then it works perfectly.
However, if the CIMOM is OpenPegasus, then CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED is returned.
(I tried on a Fedora 21 Server Minimal x86, tog-pegasus.i686 2:2.13.0-17.fc21, openwsman-server.i686 2.4.6-3.fc21).
The problem is, that for the ExecQuery CIM-XML call openwsman sets the query language to "CQL", while OpenPegasus expects "DMTF:CQL".
If I change it in sfcc-interface.c:1191, then the query is executed successfully.
As far as I see in version 1.0.0 of DSP202 'CIM Query Language Specification', Section 6.1  Identifying the CIM Query Language:

Following this convention, the string "DMTF:CQL" identifies the CIM Query Language.

Moreover, sblim-sfcb also accepts the DMTF:CQL format. In version 1.4.9, querystatement.c, line 277:
else if (strcasecmp(lang, "cql") == 0 || strcasecmp(lang, "cim:cql") == 0 || strcasecmp(lang, "dmtf:cql") == 0) {
  ctl.statement->lang = QL_CQL;

Of course changing this could break compatibility with other apps. Maybe it could be a configuration setting?

Thanks for the report !
Yes, this needs to be configurable since e.g. sblim-sfcb 1.3.11 (used on SUSE Linux Enterprise Serevr 11) requires CQL
Added new config option cim_client_cql, defaults to CQL

Fixed

authors: kkaempf micskeiz

repo: Openwsman/openwsman


text:
Fix bug where service fields are not being updated

Issues
RELIES ON https://github.com/OpsLevel/opslevel-go/pull/316
https://gitlab.com/jklabsinc/OpsLevel/-/issues/9963
TL;DR, if you unset a field in terraform on a service it will not remove it even thought it says it will.
Changelog

[x] Use GetOk() to check if an optional field was set before managing it, as done in https://github.com/OpsLevel/terraform-provider-opslevel/pull/162/files. We should refactor all of our update functions to do this.
[ ] Changes
[ ] Make a changie entry

Tophatting
Create a new service.
  # opslevel_service.test_svc will be created
  + resource "opslevel_service" "test_svc" {
      + id              = (known after apply)
      + language        = "ruby"
      + last_updated    = (known after apply)
      + lifecycle_alias = "beta"
      + name            = "Testing a new service"
      + tier_alias      = "tier_4"
    }

On the website, set framework = Rails and owner = platform. Run terraform again, it should not try to manage these fields. ✅
Set the owner (set in web only), framework (set in web only), tier_alias (set in TF on create) to something else in TF.

closing this, we need further investigation on handling null values in opslevel-go.

repo: OpsLevel/terraform-provider-opslevel