[LSP] Failed to handle notification textDocument/documentSymbol - System.NullReferenceException: Object reference not set to an instance of an object (and a few other errors)

This has been going on-and-off between the releases and now it's back again.
There are a few errors in the log, which results in a non-functional language server.
[Info  - 6:24:50 PM] Finding descriptor for initialize
[Info  - 6:24:50 PM] Starting: Routing Request (0) initialize
[Info  - 6:24:50 PM] Converting params for Request (0) initialize to OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Cake
[Info  - 6:24:50 PM] Loaded OmniSharp.Cake, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.DotNetTest
[Info  - 6:24:50 PM] Loaded OmniSharp.DotNetTest, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Host
[Info  - 6:24:50 PM] Loaded OmniSharp.Host, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.MSBuild
[Info  - 6:24:50 PM] Loaded OmniSharp.MSBuild, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Roslyn
[Info  - 6:24:50 PM] Loaded OmniSharp.Roslyn, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Roslyn.CSharp
[Info  - 6:24:50 PM] Loaded OmniSharp.Roslyn.CSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Script
[Info  - 6:24:50 PM] Loaded OmniSharp.Script, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] Assembly loaded: OmniSharp.Shared
[Info  - 6:24:50 PM] Loaded OmniSharp.Shared, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
[Info  - 6:24:50 PM] DotNetPath set to dotnet
[Info  - 6:24:50 PM] Located 2 MSBuild instance(s)
            1: Visual Studio Enterprise 2019 16.4.29806.167 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin"
            2: StandAlone 16.4 - "C:\Users\Yatao\AppData\Local\coc\extensions\coc-omnisharp-data\server\.msbuild\Current\Bin"
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Utilities.Core.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Utilities.Core.dll' (name-only).
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.dll' (name-only).
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.dll' (name-only).
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll' (name-only).
[Info  - 6:24:50 PM] Registered MSBuild instance: Visual Studio Enterprise 2019 16.4.29806.167 - "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin"
[Info  - 6:24:50 PM] Attempting to resolve 'Microsoft.Build.Utilities.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Utilities.Core.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Utilities.Core.dll' (name-only).
[Info  - 6:24:50 PM] Attempting to resolve 'Microsoft.Build.Framework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:50 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll
[Info  - 6:24:50 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll' (name-only).
[Info  - 6:24:50 PM] Assembly loaded: Microsoft.CodeAnalysis.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:50 PM] Assembly loaded: Microsoft.CodeAnalysis.CSharp.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:50 PM] Attempting to resolve 'Microsoft.CodeAnalysis.VisualBasic.Workspaces, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
[Info  - 6:24:50 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.CodeAnalysis.VisualBasic.Workspaces.dll'.
[Info  - 6:24:50 PM] Attempting to resolve 'Microsoft.CodeAnalysis.VisualBasic.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
[Info  - 6:24:50 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.CodeAnalysis.VisualBasic.Features.dll'.
[Info  - 6:24:50 PM] Successfully added Microsoft.CodeAnalysis.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35 to host service assemblies.
[Info  - 6:24:50 PM] Successfully added Microsoft.CodeAnalysis.CSharp.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35 to host service assemblies.
[Info  - 6:24:51 PM] Attempting to resolve 'SQLitePCLRaw.core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=1488e028ca7ab535'
[Info  - 6:24:51 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\SQLitePCLRaw.core.dll'.
[Info  - 6:24:51 PM] Configured Document Selectors { language = Cake, selector = [**/*.cake] }, { language = C#, selector = [**/*.cs], [**/*.csx] }
[Info  - 6:24:51 PM] --- Handler Definitions ---
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Types.TypeLookupHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Structure.BlockStructureHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Structure.CodeStructureHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Structure.MembersAsTreeHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Signatures.SignatureHelpHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Refactoring.RenameHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Refactoring.V2.GetCodeActionsHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Refactoring.V2.RunCodeActionsHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.FindImplementationsHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.FindSymbolsHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.FindUsagesHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.GotoDefinitionHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.GotoFileHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.GotoRegionHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.MetadataHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.NavigateUpHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Navigation.NavigateDownHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Intellisense.AutoCompleteHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Diagnostics.CodeCheckHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Buffer.ChangeBufferHandler
[Info  - 6:24:51 PM] Handler: Cake:[**/*.cake]:OmniSharp.Cake.Services.RequestHandlers.Buffer.UpdateBufferHandler
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.DebugTestClassService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.DebugTestService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.DebugTestService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.DebugTestService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.GetTestStartInfoService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.RunTestService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.DotNetTest.Services.RunTestsInClassService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Types.TypeLookupService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.TestCommands.TestCommandService
[Info  - 6:24:51 PM] Assembly loaded: Microsoft.CodeAnalysis.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Structure.BlockStructureService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Structure.CodeStructureService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Structure.MembersAsFlatService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Structure.MembersAsTreeService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Signatures.SignatureHelpService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.FixUsingService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.GetCodeActionsService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.RenameService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.RunCodeActionsService
[Info  - 6:24:51 PM] Assembly loaded: Microsoft.CodeAnalysis.CSharp.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:51 PM] Assembly loaded: Microsoft.CodeAnalysis.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:51 PM] Assembly loaded: Microsoft.CodeAnalysis.Workspaces, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.GetCodeActionsService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.RunCodeActionService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.FindImplementationsService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.FindSymbolsService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.FindUsagesService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.GotoDefinitionService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.GotoFileService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.GotoRegionService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.MetadataService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.NavigateUpService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Navigation.NavigateDownService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Intellisense.IntellisenseService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Highlighting.HighlightingService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Formatting.CodeFormatService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Formatting.FormatAfterKeystrokeService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Formatting.FormatRangeService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Files.FileCloseService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Files.FileOpenService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Files.OnFilesChangedService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Diagnostics.CodeCheckService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Diagnostics.DiagnosticsService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Diagnostics.ReAnalyzeService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Buffer.ChangeBufferService
[Info  - 6:24:51 PM] Handler: C#:[**/*.cs], [**/*.csx]:OmniSharp.Roslyn.CSharp.Services.Buffer.UpdateBufferService
[Info  - 6:24:51 PM] --- Handler Definitions ---
[Info  - 6:24:51 PM] Result was System.Threading.Tasks.Task`1[[OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022]]
[Info  - 6:24:51 PM] Response value was OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult
[Info  - 6:24:51 PM] Finished: Routing Request (0) initialize in 1253ms
[Info  - 6:24:51 PM] Finding descriptor for initialized
[Info  - 6:24:51 PM] Finding descriptor for workspace/didChangeConfiguration
[Info  - 6:24:51 PM] Unable to find workspace/didChangeConfiguration, methods found include initialize:OmniSharp.Extensions.LanguageServer.Server.LanguageServer, initialized:OmniSharp.Extensions.LanguageServer.Server.LanguageServer, shutdown:OmniSharp.Extensions.LanguageServer.Server.Handlers.ServerShutdownHandler, exit:OmniSharp.Extensions.LanguageServer.Server.Handlers.ServerExitHandler, $/cancelRequest:OmniSharp.Extensions.JsonRpc.CancelRequestHandler`1[[OmniSharp.Extensions.LanguageServer.Server.Abstractions.ILspHandlerDescriptor, OmniSharp.Extensions.LanguageServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022]], textDocument/didChange:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didOpen:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didClose:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didSave:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didChange:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didOpen:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didClose:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/didSave:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler, textDocument/definition:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDefinitionHandler, textDocument/definition:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDefinitionHandler, textDocument/hover:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpHoverHandler, textDocument/hover:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpHoverHandler, textDocument/completion:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCompletionHandler, completionItem/resolve:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCompletionHandler, textDocument/completion:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCompletionHandler, completionItem/resolve:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCompletionHandler, textDocument/signatureHelp:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpSignatureHelpHandler, textDocument/signatureHelp:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpSignatureHelpHandler, textDocument/rename:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpRenameHandler, textDocument/rename:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpRenameHandler, textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler, textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler, textDocument/references:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpReferencesHandler, textDocument/references:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpReferencesHandler, textDocument/codeLens:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCodeLensHandler, codeLens/resolve:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCodeLensHandler, textDocument/codeLens:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCodeLensHandler, codeLens/resolve:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpCodeLensHandler, textDocument/formatting:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentFormattingHandler, textDocument/rangeFormatting:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentFormatRangeHandler, textDocument/onTypeFormatting:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentOnTypeFormatHandler
[Info  - 6:24:51 PM] Starting: Routing Notification initialized
[Info  - 6:24:51 PM] Converting params for Notification initialized to OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializedParams
initialized...
[Info  - 6:24:52 PM] Detecting Cake files in 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo'.
[Info  - 6:24:52 PM] Could not find any Cake files
[Info  - 6:24:52 PM] No solution files found in 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo'
[Info  - 6:24:52 PM] Queue project update for 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo\BindingDemo.csproj'
[Info  - 6:24:52 PM] Detecting CSX files in 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo'.
[Info  - 6:24:52 PM] Could not find any CSX files
[Info  - 6:24:52 PM] Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[Info  - 6:24:52 PM] Loading project: c:\Users\Yatao\git\Avalonia\samples\BindingDemo\BindingDemo.csproj
[Info  - 6:24:52 PM] Attempting to resolve 'Microsoft.Build, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:52 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.dll
[Info  - 6:24:52 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.dll' (name-only).
[Info  - 6:24:52 PM] Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[Info  - 6:24:52 PM] Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
[Info  - 6:24:52 PM] Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200
[Info  - 6:24:52 PM] Configuration finished.
[Info  - 6:24:52 PM] Omnisharp server running using Lsp at location 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo' on host 31508.
[Info  - 6:24:52 PM] Finished: Routing Notification initialized in 361ms
[Info  - 6:24:52 PM] Finding descriptor for textDocument/didOpen
[Info  - 6:24:52 PM] Created attribute cs::file:///c%3A/Users/Yatao/git/Avalonia/samples/BindingDemo/MainWindow.xaml.cs
[Info  - 6:24:52 PM] Looking for handler for descriptors textDocument/didOpen
[Info  - 6:24:52 PM] Checking handler textDocument/didOpen:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler
[Info  - 6:24:52 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentSaveRegistrationOptions
[Info  - 6:24:52 PM] Document Selector [**/*.cake]
[Info  - 6:24:52 PM] Checking handler textDocument/didOpen:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler
[Info  - 6:24:52 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentSaveRegistrationOptions
[Info  - 6:24:52 PM] Document Selector [**/*.cs], [**/*.csx]
[Info  - 6:24:52 PM] Handler Selected: OmniSharp.LanguageServerProtocol.Handlers.OmniSharpTextDocumentSyncHandler via [**/*.cs], [**/*.csx] (targeting OmniSharp.Extensions.JsonRpc.IJsonRpcNotificationHandler`1[[OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022]])
[Info  - 6:24:52 PM] Starting: Routing Notification textDocument/didOpen
[Info  - 6:24:52 PM] Converting params for Notification textDocument/didOpen to OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams
[Info  - 6:24:52 PM] Finished: Routing Notification textDocument/didOpen in 4ms
[Info  - 6:24:52 PM] Attempting to resolve 'Microsoft.Build.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:52 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.resources.dll'.
[Info  - 6:24:52 PM] Attempting to resolve 'Microsoft.Build.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:52 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.resources.dll'.
[Info  - 6:24:53 PM] Attempting to resolve 'Microsoft.Build.Tasks.Core.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:53 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.resources.dll'.
[Info  - 6:24:53 PM] Attempting to resolve 'Microsoft.Build.Tasks.Core.resources, Version=<IP_ADDRESS>, Culture=en-US, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:53 PM] FAILURE: Could not locate 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.resources.dll'.
[Info  - 6:24:54 PM] Attempting to resolve 'Microsoft.Build.Framework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:54 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll
[Info  - 6:24:54 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Framework.dll' (name-only).
[Info  - 6:24:54 PM] Attempting to resolve 'Microsoft.Build.Tasks.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
[Info  - 6:24:54 PM] Assembly loaded from path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.dll
[Info  - 6:24:54 PM] SUCCESS: Resolved to 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\Microsoft.Build.Tasks.Core.dll' (name-only).
[Error  - 6:24:56 PM] The "GenerateAvaloniaResourcesTask" task could not be loaded from the assembly C:\Users\Yatao\git\Avalonia\build\\..\src\Avalonia.Build.Tasks\bin\Debug\netstandard2.0\Avalonia.Build.Tasks.dll. Could not load file or assembly 'C:\Users\Yatao\git\Avalonia\build\\..\src\Avalonia.Build.Tasks\bin\Debug\netstandard2.0\Avalonia.Build.Tasks.dll'. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [C:\Users\Yatao\git\Avalonia\samples\BindingDemo\BindingDemo.csproj]
[Error  - 6:24:56 PM] The command "dotnet msbuild /nodereuse:false BindingDemo.csproj /t:GenerateAvaloniaResources /p:_AvaloniaForceInternalMSBuild=true /p:Configuration=Debug /p:TargetFramework=netcoreapp2.0 /p:BuildProjectReferences=false" exited with code 1.
[Warn  - 6:24:56 PM] Failed to load project file 'c:\Users\Yatao\git\Avalonia\samples\BindingDemo\BindingDemo.csproj'.
[Error  - 6:24:56 PM] Attempted to update project that is not loaded: c:\Users\Yatao\git\Avalonia\samples\BindingDemo\BindingDemo.csproj
[Info  - 6:25:07 PM] Finding descriptor for textDocument/documentSymbol
[Info  - 6:25:07 PM] Found attributes 1, ::file:///c%3A/Users/Yatao/git/Avalonia/samples/BindingDemo/MainWindow.xaml.cs
[Info  - 6:25:07 PM] Looking for handler for descriptors textDocument/documentSymbol
[Info  - 6:25:07 PM] Checking handler textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler
[Info  - 6:25:07 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentRegistrationOptions
[Info  - 6:25:07 PM] Document Selector [**/*.cake]
[Info  - 6:25:07 PM] Checking handler textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler
[Info  - 6:25:07 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentRegistrationOptions
[Info  - 6:25:07 PM] Document Selector [**/*.cs], [**/*.csx]
[Info  - 6:25:07 PM] Handler Selected: OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler via [**/*.cs], [**/*.csx] (targeting OmniSharp.Extensions.JsonRpc.IJsonRpcRequestHandler`2[[OmniSharp.Extensions.LanguageServer.Protocol.Models.DocumentSymbolParams, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022],[OmniSharp.Extensions.LanguageServer.Protocol.Models.SymbolInformationOrDocumentSymbolContainer, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022]])
[Info  - 6:25:07 PM] Starting: Routing Request (1) textDocument/documentSymbol
[Info  - 6:25:07 PM] Converting params for Request (1) textDocument/documentSymbol to OmniSharp.Extensions.LanguageServer.Protocol.Models.DocumentSymbolParams
[Error  - 6:25:07 PM] Failed to handle notification textDocument/documentSymbol - System.NullReferenceException: Object reference not set to an instance of an object.
   at OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler.<Handle>d__4.MoveNext() in D:\a\1\s\src\OmniSharp.LanguageServerProtocol\Handlers\OmniSharpDocumentSymbolHandler.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.<Handle>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>d__6.MoveNext()
[Info  - 6:25:07 PM] Finished: Routing Request (1) textDocument/documentSymbol in 12ms
[Error  - 6:25:07 PM] Request textDocument/documentSymbol failed.
  Message: Internal Error - System.NullReferenceException: Object reference not set to an instance of an object.
   at OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler.<Handle>d__4.MoveNext() in D:\a\1\s\src\OmniSharp.LanguageServerProtocol\Handlers\OmniSharpDocumentSymbolHandler.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.<Handle>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>d__6.MoveNext()
  Code: -32602
[Info  - 6:27:05 PM] Finding descriptor for textDocument/documentSymbol
[Info  - 6:27:05 PM] Found attributes 1, ::file:///c%3A/Users/Yatao/git/Avalonia/samples/BindingDemo/MainWindow.xaml.cs
[Info  - 6:27:05 PM] Looking for handler for descriptors textDocument/documentSymbol
[Info  - 6:27:05 PM] Checking handler textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler
[Info  - 6:27:05 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentRegistrationOptions
[Info  - 6:27:05 PM] Document Selector [**/*.cake]
[Info  - 6:27:05 PM] Checking handler textDocument/documentSymbol:OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler
[Info  - 6:27:05 PM] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.TextDocumentRegistrationOptions
[Info  - 6:27:05 PM] Document Selector [**/*.cs], [**/*.csx]
[Info  - 6:27:05 PM] Handler Selected: OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler via [**/*.cs], [**/*.csx] (targeting OmniSharp.Extensions.JsonRpc.IJsonRpcRequestHandler`2[[OmniSharp.Extensions.LanguageServer.Protocol.Models.DocumentSymbolParams, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022],[OmniSharp.Extensions.LanguageServer.Protocol.Models.SymbolInformationOrDocumentSymbolContainer, OmniSharp.Extensions.LanguageProtocol, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=6d868dff454e6022]])
[Info  - 6:27:05 PM] Starting: Routing Request (2) textDocument/documentSymbol
[Info  - 6:27:05 PM] Converting params for Request (2) textDocument/documentSymbol to OmniSharp.Extensions.LanguageServer.Protocol.Models.DocumentSymbolParams
[Error  - 6:27:05 PM] Failed to handle notification textDocument/documentSymbol - System.NullReferenceException: Object reference not set to an instance of an object.
   at OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler.<Handle>d__4.MoveNext() in D:\a\1\s\src\OmniSharp.LanguageServerProtocol\Handlers\OmniSharpDocumentSymbolHandler.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.<Handle>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>d__6.MoveNext()
[Info  - 6:27:05 PM] Finished: Routing Request (2) textDocument/documentSymbol in 0ms
[Error  - 6:27:05 PM] Request textDocument/documentSymbol failed.
  Message: Internal Error - System.NullReferenceException: Object reference not set to an instance of an object.
   at OmniSharp.LanguageServerProtocol.Handlers.OmniSharpDocumentSymbolHandler.<Handle>d__4.MoveNext() in D:\a\1\s\src\OmniSharp.LanguageServerProtocol\Handlers\OmniSharpDocumentSymbolHandler.cs:line 63
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.<Handle>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>d__6.MoveNext()
  Code: -32602

any news here?

@ericdallo fixed with #2005


Stabilize and document __log.

Sometimes needs arise where one wants to deliver a custom logging statement to log crate. __log is exactly that function, but then anyone using it is risking breaking changes.
It seems to me once log API is considered stable, __log should be documented and stabilized as well.

__log and its associated struct LogLocation are explicitly designed to be unstable and undocumented forever, since we otherwise forever prevented from e.g. taking advantage of a future function!() macro to extend the location metadata.

The content of LogLocation can be extended without breaking anything, no?

I'm a bit confused - why do you need to use __log if you're not assembling your own LogLocation?

RIght. Hmm... LogLocation could be assembled eg. by a macro, that in the future would be changed to fill the missing field with a defaults ... But I guess that's too much complication for no good reason.
Will there be any other addition? I mean - one could just add function : &'static str field right away and for now fill it with "".

Who knows? function was just something I pulled from the top of my head.

Can't then log just bump version to 2.0 or something? :)

Bumping the major version of log is pretty traumatic ecosystem-wise. Until everyone upgrades you'll be losing log messages from anything that still talks to the old version. It is not a thing I want to do every time we want to add some new metadata to log events.

FYI, the only reason __log is public at all is that macros aren't hygenic with respect to privacy. It is the definition of an implementation detail.

I have a need to log things with  custom meta information using LogLocation:  https://github.com/dpc/slog-rs/blob/8ef65309610125e1ba024ae1d4f2eb4e2a0b58cb/crates/stdlog/lib.rs#L220
And it seems to me it's reasonable requirement, as "faking" line/file/module might be useful in some cases, when people don't want real information for whatever reason.
What if __log and LogLocation were stabilized, and any time anything change there, __logv2 and LogLocationv2 are created, while keeping __log and LogLocation as #[deprecated] backward compatibility forwarding things to __logv2? Macros itself will just use v2 versions.

The functionality here seems pretty reasonable to me, integrating one log system into another. Stabilizing exactly __log, however, will likely never happen. (or at least I would prefer such)
I wonder if we could perhaps explore a more first class API here? Something like:
struct LogBuilder {
    // opaque
}

impl LogBuilder {
    fn new() -> LogBuilder { ... }

    fn line(&mut self, line: u32) -> &mut LogBuilder { ... }
    fn module(&mut self, module: &str) -> &mut LogBuilder { ... }
    // other builder methods ...

    fn emit(&mut self) { ... }
}

This way slog and other libraries could programmatically build log structures and the log crate also has the ability to add more fields over time if need be. The _log method would also stay as-is today, the implementation would likely just change.
Thoughts?

We'd need to change that API a bit since line, module, etc are already required, unless we'd have emit panic which seems unfortunate.

Perhaps yeah, although we could also just add arguments to new

Anything wrong with versioned __log and LogLocation?

I personally much prefer extensible APIs to "versioned APIs". That way everyone always has the same ergonomic experience and it's not a huge diff to use new features.

Yes, normally me to. But in that case the API is kind of a backdoor anyway, and except few people noone can see it anyway.
My concerns are:

builder boilerplate could not always get completely optimized away or will get in a way of some optimizations
could there be any non-trivial changes to the logging record structure there would lead to troubes for the Builder having to support both new and old format?

If the above are not an issue, then Builder is clearly nicer.

Oh I wasn't worried about perf here because I figured that once you hit this point you've concluded "yes a log should happen" and whatever happens there will completely dwarf some code to assemble the message.
It's true yeah though that if a builder were stabilized we'd have to be very confident that it would be sufficient for an incredibly long time. I'm pretty confident in this, though, as the builders in the standard library have worked out very well so far.

Fixed by #211.


How can I include and use this library?

Hi
This seems to be an awesome effort. I really need to use pouchdb in my elm code. Is this usable?
Few concerns I was having:

Is it published on package manager?
This library is using version 5 of pouchdb which is included directly. Should one be concerned about that?

I am very new to elm world. Just been 1 week tinkering around with small pieces of code. Liking it so far though!
I have forked it. So far was able to run examples successfully except the ReplicateExample.elm.

Hi,
elm-pouchdb was only released a couple of months ago. It is quite new. It is the first real effort for mapping pouchdb in elm. Any feedback is very useful, thanks again.
It is usable( really at your own risk), 95% of the pouchdb functionalities have been mapped. I will be using it on a rather big application in December therefor I'll be paying extra attention on the quality here. Again any help from the users are very helpful.
It contains several Native code files which has the following consequences:

It has to be checked by elm team before being pushed to in the package manager.
Native package Names were named using the  pattern _user$project$Native..., but should really be named as powet$elm_pouchdb$Native..... I will be pushing this proper naming in the next version. This means that you will have to put manually elm-pouchdb in yout elm-stuff directory. This will not be handy for the users for we're stuck here till the package is validated by the elm-team.

Can you provide any error messages you have as I not been able to reproduce the bug on ReplicateExample.elm?

I am getting the following error while running ReplicateExample.elm through elm reactor in example directory.
Uncaught TypeError: Cannot read property 'ctor' of undefined
I am deciding between react-redux and elm for my next project which will require pouch/couch as the database. I am very impressed by elm language and may be it will pay off in the future if I choose elm from the start.
So the point is I would really like to use this library and as early as possible. I don't care how I include the library and if it's on packages at elm hub.
May be I can help somehow in development by providing you with stack traces during errors and try submitting any pull requests when I get used to elm and the ecosystem later on.
But for now, can you give me some quick tricks to include it in my basic boilerplate? I will try changing Native package names as you suggested. May be that will work.
Cheers!

And also I was wondering (general question, out of topic) that why is everybody (elmfire, d3 port, etc) implementing in native code, even though everywhere I read they say that it is not the best way to go about it. Are there some serious benefits? :)

Bug is now corrected in the branch
https://github.com/powet/elm-pouchdb/tree/issue1
FYI, the events(pause, active, error, denied, change, complete)  coming from replication and sync do not carry any data, although in the pouchdb js they do.  I do not find dealing with the replication data of these events really useful because you're better off listening directly to "_changes" if you need the data. Still if you need to deal with such replication events, let me know (PR) and I'll put that in my TODO list.

ReplicateExample.elm is working fine now. Thanks!
And I was able to put the whole elm-pouchdb package in my project folder and run examples smoothly. 👍

Don't hesitate if any issues or any questions.
Thanks!
On 19 September 2016 at 16:11, abhinav gupta<EMAIL_ADDRESS>wrote:

ReplicateExample.elm is working fine now. Thanks!
And I was able to put the whole elm-pouchdb package in my project folder
and run examples smoothly. 👍
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/powet/elm-pouchdb/issues/1#issuecomment-248004372,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEDX4KNq8S3214ZTcMU3jgt-Qzm4Ko-_ks5qrpgvgaJpZM4J9-cJ
.

In the first comment here, @abhinavzspace asked whether s/he should be concerned that PouchDB 5.x is wired in directly. From my limited experience with the library, it's working fine if you replace it with PouchDB 6.1. I wasn't able to upgrade TestHelpers.elm to Elm 0.18 - which would let one run the test suite and be sure there are no edge cases. For someone with more Elm skills than me, that part of the code be worth updating in case it's holding up the inclusion in the Elm package manager. There's a great post here on updating Tasks to Elm 0.18 that may help; I only got so far in my own attempts.
And, this isn't the right place, but I want to thank @powet for the beautifully written code, the inclusion of useful examples, and the prompt upgrade to 0.18.

This means that you will have to put manually elm-pouchdb in your elm-stuff directory.

I will document the steps when I interpreted the above comment. Hopefully this will help people before elm-pouchdb gets adopted as elm-package.

Use npm to install power/elm-pouchdb
Create the following directories under elm-stuff/packages: packages/powet/elm-pouchdb/<VERSION> where <VERSION> should be as documented by elm-pouchdb elm-package.json. For me that was  1.0.5.
Copy the contents of node_modules/elm-pouchdb directory to the aforementioned directory.
Add an entry to elm-stuff/exact-dependencies.json detailing the elm-pouchdb package. For me that was

  "powet/elm-pouchdb": "1.0.5"

Add a dependency  to your elm-package.json. Again for me that was

  "powet/elm-pouchdb": "1.0.0 <= v < 2.0.0"


Add Southend High School for Boys

Institution/School Name
Southend High School for Boys
Institution/School Website
http://shsb.org.uk
Email Users
Please place an x between the square brackets if yes

[x] Students
[ ] Academic/Teaching Staff
[ ] Other/Support Staff
[ ] Alumni

Education Levels
Please place an x between the square brackets if yes

[ ] Post-graduate research
[ ] Graduate School
[ ] College (University) or Undergraduate School or equivalent
[ ] Community College or equivalent
[x] High School or equivalent
[ ] Elementary School or equivalent

IT-related courses offered
A-level Computer Science (2 year) for 17-18 year olds

@james-dietz Pull request merged. Thank you!


K8SPXC-911 - increase memory limits for operator pod

Test name
Status

storage
passed

scheduled-backup
passed

recreate
passed

upgrade-haproxy
passed

big-data
passed

haproxy
passed

scaling
passed

self-healing
passed

self-healing-chaos
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

security-context
passed

init-deploy
passed

upgrade-proxysql
passed

limits
passed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

demand-backup
failed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
failed

smart-update
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
failed

pitr
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1067/commits/27b1dc554e49b10be68ec345733dcc96ae839d52
image: perconalab/percona-xtradb-cluster-operator:PR-1067-27b1dc55


Improve code quality

Use idiomatic ++
Explicitly ignore errors in benchmarks

Coverage remained the same at 100.0% when pulling bb39ce444a9381fff07e33e3a05d058379726bdc on hanzei:lint into 1a9109f8c4a1d669a78442f567dfe8eedf982793 on blang:master.

Coverage remained the same at 100.0% when pulling bb39ce444a9381fff07e33e3a05d058379726bdc on hanzei:lint into 1a9109f8c4a1d669a78442f567dfe8eedf982793 on blang:master.

Coverage remained the same at 100.0% when pulling bb39ce444a9381fff07e33e3a05d058379726bdc on hanzei:lint into 1a9109f8c4a1d669a78442f567dfe8eedf982793 on blang:master.

@blang Can we merge this?

Thanks for your contribution and long wait


Enforce awaiting on async functions (and lint the test folder)

[x] fix all await calls in src/
[x] get eslint to pass (after including the test folder)

About this PR:
@samerbuna found a random fail in the integration test which led us to find a bug related to async/await use. He enabled eslint for test folder and for that rule
PS: We will move "module mapping" to another PR


Don't hard-code @com_google_protobuf//:protoc

According to https://github.com/bazelbuild/rules_proto/discussions/213 users of Bazel 7 can now ask Bazel to resolve protoc from a toolchain.
There are two spots at HEAD:
 "_protoc": attr.label(
    default = "@com_google_protobuf//:protoc",
    executable = True,
    cfg = "exec",
),

This change would be highly appreciated. We have recently migrated to using Aspect Build's kindly-provided pre-compiled protoc toolchain (toolchains_protoc) (which seems to be the recommended approach since the new versions of rules_go, and deprecation of rules_proto) , which has sped-up all our processed significantly.
Relying on rules_buf would force us to re-introduce compilation of protoc from scratch, which is something we cannot really afford to do (any more).
It would be great if we could leverage the registered toolchain instead.


allow overriding munki pkg name

I like my cpe_remote pkg repo sorted. This helps :)

ping :)

Pong.


Error: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]: Failed to call refresh: /opt/vmware/download.sh returned 1 instead of one of [0]

Hi Criag
I'm trying to install VMware-tools on a node and getting following error when I run puppet agent on node:
# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for xxx.xxx.xxx.xxx
Info: Applying configuration version '1455887193'
Notice: /Stage[main]/Vmwaretools::Install/File[/opt/vmware]/ensure: created
Notice: /Stage[main]/Vmwaretools::Install::Archive/File[/opt/vmware/download.sh]/ensure: defined content as '{md5}8ecf04b3420ddc33af656eab813cbcd1'
Info: /Stage[main]/Vmwaretools::Install::Archive/File[/opt/vmware/download.sh]: Scheduling refresh of Exec[download_vmwaretools]
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]/returns: Download failed from url xxx.xxx.xxx.xxx:/etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/VMwareTools-latest.tar.gz
Error: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]: Failed to call refresh: /opt/vmware/download.sh returned 1 instead of one of [0]
Error: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]: /opt/vmware/download.sh returned 1 instead of one of [0]
Error: Could not find command '/usr/bin/vmware-config-tools.pl'
Error: /Stage[main]/Vmwaretools::Config_tools/Exec[vmware_config_tools]/returns: change from notrun to 0 failed: Could not find command '/usr/bin/vmware-config-tools.pl'
Notice: Finished catalog run in 7.54 seconds

I saved the gzip file under following location in puppet master:
/etc/puppetlabs/puppet/environments/production/modules/vmwaretools/manifests/init.pp
$archive_url          = 'xxx.xxx.xxx.xxx:/etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files',

I get following error when I run this manually on node:
# /usr/bin/curl -s xxx.xxx.xxx.xxx:/etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/VMwareTools-latest.tar.gz /opt/vmware/ -v
* getaddrinfo(3) failed for xxx.xxx.xxx.xxx::80
* Couldn't resolve host 'xxx.xxx.xxx.xxx:'
* Closing connection #0
* <url> malformed

But DNS works perfectly fine and can resolve hostname of the puppet server.
# cat /etc/puppetlabs/puppet/hiera.yaml
---
:backends:
  - yaml
:hierarchy:
  - "%{clientcert}"
  - "%{environment}"
  - "%{::dc}"
  - "nodes/%{::trusted.certname}"
#  - "virtual/%{::virtual}"
#  - "osfamily/%{::osfamily}"
  - "%{virtual}"
  - "%{osfamily}"
  - common

:yaml:
# datadir is empty here, so hiera uses its defaults:
# - /var/lib/hiera on *nix
# - %CommonAppData%\PuppetLabs\hiera\var on Windows
# When specifying a datadir, make sure the directory exists.
  :datadir: /var/lib/hiera
  :merge_behavior: deeper

cat /var/lib/hiera/RedHat.yaml
---
vmwaretools::working_dir: /opt/vmware

# cat /var/lib/hiera/common.yaml
---
vmwaretools::version: latest

IPtables are disabled on both master and node and they are on same subnet with same OS version and on same ESXi.

Hi,
Does the file /etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/VMWareTools-latest.tar.gzfile exist?
Thanks,
Craig

Yup It does.
ls -l /etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/
total 69780
-r--r--r-- 1 root root 71451709 Feb 19 18:17 VMwareTools-10.0.0-3000743.tar.gz

Hi,
You need to pass the full version number to the module - it doesn't understand latest like the package resource does.
For example:
class { 'vmwaretools':
  version => 10.0.0-3000743,
}

Or in Hiera:
vmwaretools::version: 10.0.0-3000743

Craig

I realized soon after replying to your post that "VMWareTools-latest.tar.gz" file does not exist in that folder, so I copied existing file and created one more file in master.
ls -l /etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/
total 139560
-r--r--r-- 1 root root 71451709 Feb 19 18:17 VMwareTools-10.0.0-3000743.tar.gz
-r--r--r-- 1 root root 71451709 Feb 22 15:29 VMWareTools-latest.tar.gz
Then I updated the Hiera file as you mentioned, just to try with version number this time.
cat /var/lib/hiera/common.yaml

vmwaretools::version: 10.0.0-3000743
Still getting same error on node:
puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for xxx.xxx.xxx.xxx
Info: Applying configuration version '1456135702'
Notice: /Stage[main]/Vmwaretools::Install/File[/opt/vmware]/ensure: created
Notice: /Stage[main]/Vmwaretools::Install::Archive/File[/opt/vmware/download.sh]/ensure: defined content as '{md5}5cdab6dca13e1ca6cee3e8a5746bcc62'
Info: /Stage[main]/Vmwaretools::Install::Archive/File[/opt/vmware/download.sh]: Scheduling refresh of Exec[download_vmwaretools]
Notice: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]/returns: Download failed from url xxx.xxx.xxx.xxx:/etc/puppetlabs/puppet/environments/production/modules/vmwaretools/files/VMwareTools-10.0.0-3000743.tar.gz
Error: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]: Failed to call refresh: /opt/vmware/download.sh returned 1 instead of one of [0]
Error: /Stage[main]/Vmwaretools::Install::Exec/Exec[download_vmwaretools]: /opt/vmware/download.sh returned 1 instead of one of [0]
Error: Could not find command '/usr/bin/vmware-config-tools.pl'
Error: /Stage[main]/Vmwaretools::Config_tools/Exec[vmware_config_tools]/returns: change from notrun to 0 failed: Could not find command '/usr/bin/vmware-config-tools.pl'
Notice: Finished catalog run in 12.50 seconds
On node I could see /opt/vmware folder is created and download.sh also file created
download.sh..docx
pied under that dir.

Hi,
I'm not sure you understand how you should use the module or how Puppet serves files. You don't need to provide the server URL, and the Tools gzip should either be available over HTTP or via Puppet.
If you want to distribute the gzip via Puppet, all you need to do is set the version number, the rest is handled automatically.
For example:
class { 'vmwaretools':
  version => '10.0.0-3000743',
}

Craig

Thanks. It worked via puppet. I think for some reason http is not working from puppet server.
You can close the thread.
-- Anil Kumar V


Test CI

Can one of the admins verify this patch?

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Camel-k-pr/4/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Camel-k-pr/5/


AnimationDrawable are not animated on map

When im setting animation on mapObject it doesnt animated. Any directions to overcome it?

When im setting animation on mapObject it doesnt animated. Any directions to overcome it?

Hi Amir,
Trying to load the slicingtool project into the eclipse kepler, but unable to run the project properly, getting the error:

I am stuck since one week to resolve this issue, please help me out and suggest on it.
Thanks
Farman Khan


[Bug]: Contact Us Form - Name Field Validation

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The "Name" field in the Contact Us section accepts symbols and special characters, which may lead to invalid or spam submissions.
Expected behaviour
The "Name" field in the Contact Us section should only accept alphabetical letters (a-z, A-Z).
Add ScreenShots/Videos

Record

[X] I have read the Contributing Guidelines
[X] I'm a WOB'24(Winter Of Blockchain) contributor
[X] I'm a GSSOC'24 Extended contributor
[X] I'm a Hacktoberfest'24 Extended contributor
[X] I have starred the repository

@apu52 please assign me this issue.

@akash70629 u are assigned


use actual buttons

Current dependencies on/for this PR:

main

PR #269

PR #270   👈

PR #271

This comment was auto-generated by Graphite.


Expose artboard instances directly on File

Thought: can we make the 'default' way to use our public API to use instances?
This idea hides (or at least renames for now) access to the "raw" objects, and allows clients to create instances directly, avoiding the spring-board of the "raw" object...
file --> artboard --> artboard_instance

becomes
file --> artboard_instance

Similarly, we could apply this reasoning to LinearAnimationInstance and StateMachineInstance... but this PR just tries to tackle the artboard instances first.
I propose we don't (necessarily) need to really hide the "raw" objects (though we might consider it) -- but we make the API such that 99% of clients never even need to know about them. They just get guided directly to instances. (esp. our high-level language wrappers like Swift, Kotlin, JS)
PS -- the current new names (e.g. instanceAt, instanceNamed) are just placeholders.

I think this is a great idea! It'll drive us more and more towards defining a default state/config from the editor. Which is what we want long term anyway.

This looks like a great simplification to me!
Does artboardDefault() always return a value now? I recall trying to draw some riv files in the past that didn't appear to have a default animation.

Should return something, or null if there are zero items -- if you have a riv that returned null, let's double check that it actually had the thing you're looking for


Standard libraries should be searched for by cmake

Under Linux, cmake should look for the standard libraries before the actual build process
/usr/lib64/libcurl.so
/usr/lib64/libxslt.so
/usr/lib64/libxml2.so
This way, if not found, specific paths to the libraries could be provided to cmake.
Currently, only make throws an error, if the libraries are not found under the standard folder and name.

TiGL does not explicitly link to these libs. These are dependencies of TiXI.
Did you download some binary package of TiXI or did you compile TiXI by yourself?

We compiles Tixi ourselves. However, cmake does include these dependencies for e.g. the TIGLViewer.
Therefore, the error occurs when trying to link the TIGLViewer, even though the Tixi libraries are already compiled and available.
From: Martin Siggel<EMAIL_ADDRESS>Sent: Thursday, December 17, 2015 9:58 AM
To: DLR-SC/tigl
Cc: Deinert, Sebastian
Subject: Re: [tigl] Standard libraries should be searched for by cmake (#190)
TiGL does not explicitly link to these libs. These are dependencies of TiXI.
Did you download some binary package of TiXI or did you compile TiXI by yourself?
—
Reply to this email directly or view it on GitHub https://github.com/DLR-SC/tigl/issues/190#issuecomment-165387691 .

Hm... As I said. There is no explicit linking to these mentioned libraries, neither in TiGL nor in TiGL Viewer.
The only reason, It might try to link these libs could be, that TiXI exports these libs into INSTALL_PREFIX/lib/tixi/tixi-targets-release.cmake. This can only make problems, if you compiled tixi on a different machine and copied it over to your machine.
As a temporary workwround, you could remove all curl, libxml, libxslt entries from INSTALL_PREFIX/lib/tixi/tixi-targets-release.cmake.

@sdeinert Did you fix your problems? Can we close this issue?


TypeError: Image or Canvas expected

I get this error when trying to send the canvas to discord as an attachment:
(node:23382) UnhandledPromiseRejectionWarning: TypeError: Image or Canvas expected     at drawTextWithEmoji (/home/john/discord/CISN/main/node_modules/node-canvas-with-twemoji-and-discord-emoji/src/drawTextWithTwemoji.js:65:15)     at runMicrotasks (<anonymous>)     at processTicksAndRejections (internal/process/task_queues.js:97:5)     at async exports.fillTextWithTwemoji (/home/john/discord/CISN/main/node_modules/node-canvas-with-twemoji-and-discord-emoji/src/index.js:5:10)     at async main (eval at <anonymous> (eval at Actions.eval (/home/john/discord/CISN/main/bot.js:344:10)), <anonymous>:10:2) (node:23382) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5) (node:23382) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Here is the code (mostly the example):
https://pastebin.com/DS1wKUT1

look, I know this question was 1 year ago, but I'll still answer:
1st you are required to put the name of the attachment when it is sent
2nd you tried to create an attachment, but you didn't export the discord.js module


x/pkgsite: tag like v17.03.1 is not recognized as a version

What is the URL of the page with the issue?
https://pkg.go.dev/mod/github.com/docker/docker?tab=versions
What is your user agent?
Google Chrome  Version 80.0.3987.132 (Official Build) (64-bit)
Screenshot
n/a
What did you do?
Opened the page
What did you expect to see?
v17, v18 and v19 versions, with the latest one being  v19.03.8
What did you see instead?
v1.3.1 is shown as the latest version
v17.x, v18.x, v19.x is not shown at all.
More info
Docker (https://github.com/moby/moby aka github.com/docker/docker) has switched to date-based versions a few years ago. The latest non-date-based version was v1.3.1, and after it v17.03.0-ce-rc1 was released (see https://github.com/moby/moby/tags?after=v17.05.0-ce-rc1).
Apparently, pkg.go.dev do not recognize versions > 9, as a result it shows documentation from 2017 and there's no way to change that.
This is a regression, since godoc.org shows the latest docs.
// Cc @thaJeztah

OK it seems like the leading zero (as in 03 from v19.03.1) is the source of a problem. Not sure how to deal with it though

it only supports SemVer format, not CalVer

In addition to expecting tagging to be done on the master branch (no support for release branches) which I think is why v1.13.1 is no longer picked up (later than v1.3.1, but not tagged on master)

oh, ignore the last comment, that may be have been with go mod itself

pkg.go.dev interprets versions in the same way as the go command in module mode. The problem here seems to be that repository doesn't publish versions that are compatible to be used with the go command.

OK it seems like the leading zero (as in 03 from v19.03.1) is the source of a problem. Not sure how to deal with it though

Right, v19.03.1 is not a valid semver tag because of a leading zero in the minor version component. https://semver.org/#spec-item-2 says:

A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes.

Not sure how to deal with it though

There a few relevant issues in that project's issue tracker, you can leave a 👍 reaction to show your support:

https://github.com/moby/moby/issues/31842
https://github.com/moby/moby/issues/39302
https://github.com/moby/moby/issues/39056

/cc @julieqiu

Filed moby/moby#41382.


layoutEditorGroups keybindings do wrong thing when the editors are already in the desired layout

VS Code version: Code - Insiders 1.24.0-insider (41a7c4976ebd1f6ced20c034485300f46ab1829f, 2018-05-29T06:09:34.618Z)
OS version: Windows_NT x64 10.0.16299

#50458
Keybinding:
{
	"key": "ctrl+0",
	"command": "layoutEditorGroups",
	"args": {
		"orientation": 1,
		"groups": [
			{ "size": 0.2 },
			{ "size": 0.6 },
			{ "size": 0.2, "groups": [{"size": 0.4}, {"size": 0.6}] }
		]
	}
}

First ctrl+0:

Second ctrl+0:

Duplicate of https://github.com/Microsoft/vscode/issues/50674


Windows 10 File Associations

After upgrading to 10 pro from 7 pro, I switched out Notepad++ for Brackets, but the file associations simply didn't work.  After manually setting them with the Windows file association dialogue, everything worked except PHP files.  (Note: this does not apply to opening PHP files from within the program itself.)  Attempting to open one either from file explorer or FTP (Filezilla), it would still open in N++.
After uninstalling N++ completely, it just threw an error saying it couldn't find the N++.exe when trying to open a PHP file.  The only way to resolve this was to delete the following key in regedit:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts\Applications\brackets.exe_.php
Also note that the following keys are present (of which php is one of them):

These had already been set:

I don't think Brackets does anything with file associations so I am not sure that the issue would be something Brackets could "fix"... or were you just posting information to let others know how to workaround the issue should they get it?

Sorry about that!  I wasn't clear.  Yes, this is for reference purposes.
I don't think it has to do with N++ specifically, but with Win10 being unable to unhook file extensions from previously installed software and even if the association is overwritten, it will throw an error just because it has one stored in a key.


Revert "Enhance Remove-Item to work with OneDrive (#14902)"

This reverts commit fafc38fe5c457afbc68b379bdf9c847562e209c5.

PR Summary

PR Context

PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

/azp list

/azp list

/azp run PowerShell-CI-Windows-daily

PowerShell-CI-Windows-daily is the CI where this has been failing, so let us see if this makes that pass.

/azp run PowerShell-CI-Windows-daily

/azp run PowerShell-CI-Windows-daily

/azp help

/azp run PowerShell-CI-Windows-daily

@iSazonov #14902 caused an issue with Remove-Item, forcing us to revert it:
  Describing About help files can be found in AllUsers scope
    [-] Error occurred in Describe block 0ms
      IOException: The directory is not empty. : 'C:\Users\VssAdministrator\Documents\PowerShell\Help\'
      IOException: Cannot remove item C:\Users\VssAdministrator\Documents\PowerShell\Help\: The directory is not empty. : 'C:\Users\VssAdministrator\Documents\PowerShell\Help\'
      at <ScriptBlock>, D:\a\1\s\test\powershell\engine\Help\HelpSystem.Tests.ps1: line 267
      at Invoke-Blocks, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\SetupTeardown.ps1: line 135
      at Invoke-TestGroupSetupBlocks, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\SetupTeardown.ps1: line 121
      at DescribeImpl, D:\a\1\s\src\powershell-win-core\bin\Release\net6.0\win7-x64\publish\Modules\Pester\4.10.1\Functions\Describe.ps1: line 209

I wonder how was CIs passed in the PR. Should we fix anything in CIs?

@iSazonov No the daily CI run serially.  You should open a new PR and fix the issue in the remove-item code.


Add Sponge..

You can add sponge as well, and maybe build it from git as bleeding right now is 1.9. If you need help on how to build it, let me know.

I'm not that familiar with Sponge. Do you prefer the SpongeForge or SpongeVanilla variant?

Spongevanilla would be the easiest
On Thu, May 12, 2016, 5:59 PM Geoff Bourne<EMAIL_ADDRESS>wrote:

I'm not that familiar with Sponge. Do you prefer the SpongeForge or
SpongeVanilla variant?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/itzg/dockerfiles/issues/78#issuecomment-218926511

Just to let you know, Sponge.. though slow going.. Is a new API for minecraft plugins. A lot of developers from Bukkit, when the big blowup happened left, merged with a few other projects and created Sponge. It's a fairly nice community to work with and though it's still in it's BETA phase, has many useful plugins already offered. When Bukkit was still a thing I first tried Spigot and didn't care for their community, so when Bukkit died and Spigot took over in a sense.. Sponge was there and was a compelling alternative.

That's cool. Thanks for the background.
I didn't get a chance to work on this over the weekend.  Speaking of which, you're welcome to contribute the changes to add support.

...ok, the build is gradle based, so the remaining trickiness is mapping versions, picking the latest, etc. For the prebuilt 1.8.9 and below, we'll need to see if their site exposes a REST API to resolve versions to download URLs.

Here's the script I run to download the latest "bleeding" versions that's TypeId=2 in the URL and the stable 1.8.9 is TypeId=1
#!/usr/bin/env bash
wget https://repo.spongepowered.org/maven/org/spongepowered/spongevanilla/?buildTypeId=2 -O sponge_page

latest_sponge=$(grep -m1 "btn btn-default" ./sponge_page |cut -d'"' -f4)
wget $latest_sponge -O latest_sponge.jar

I finally got around to this...and then found their sites aren't cooperating right now

Sorry about that
https://repo.spongepowered.org/maven/org/spongepowered/spongevanilla/?buildTypeId=2
Should work now.
On Sat, May 28, 2016, 6:29 PM Geoff Bourne<EMAIL_ADDRESS>wrote:

I finally got around to this...and then found their sites aren't
cooperating right now
[image: image]
https://cloud.githubusercontent.com/assets/988985/15630880/e797faf2-2512-11e6-87ed-8bb853976794.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/itzg/dockerfiles/issues/78#issuecomment-222337579,
or mute the thread
https://github.com/notifications/unsubscribe/AAbY8hixUWN5N7BAufCBOV6903Jjl3pMks5qGOwQgaJpZM4IdhfN
.

Yep, now their servers are good :)

Some notes:
https://repo.spongepowered.org/maven/org/spongepowered/spongevanilla/?buildTypeId=:buildType&startAt=:startAt

buildType

2 = bleeding
7 = beta
5 = release (but none available)
(absent) = default

startAt

(absent) = first page
Revision?

Each artifact version string is text of
body > div.container > div > div > ol.builds > li:nth-child(*) > span

Each artifact at
body > div.container > div > div > ol.builds > li:nth-child(*) > ul.build-artifacts > li.build-artifact.build-artifact-primary > a

Nice, Great Job!

I'm getting closer. I have created a little tool in Go that scrapes and converts page segments to JSON:
https://github.com/itzg/restify
Now to slice and dice it with jq...

It's certainly uglier than the grep approach, but here's a "restify | jq" solution:
restify --class builds https://repo.spongepowered.org/maven/org/spongepowered/spongevanilla/?buildTypeId=2 | \
  jq -r '.[].elements[0].elements[]|select(.class=="build-artifacts")|.elements[]|select(.class|contains("primary"))|.elements[0].href'

More restify | jq notes:
Get just the newest build's version
jq -r '.[0].elements[0].elements[] | select(.class == "build-version").text'

Produces
1.9.4-5.0.0-BETA-62

Get the URL of that build
jq -r '.[0].elements[0].elements[] | select(.class == "build-artifacts").elements[0].elements[0].href'

produces
https://repo.spongepowered.org/maven/org/spongepowered/spongevanilla/1.9.4-5.0.0-BETA-62/spongevanilla-1.9.4-5.0.0-BETA-62.jar

This may be useful, not so sure. I'm currently building this project, https://github.com/NynjaCypher/sf-version-mapper, however it's not fully operational yet so I'll keep you all posted.

Thanks @NynjaCypher and thanks for reminding me of this thread.

Is it planned to continue development of Sponge integration?

I'd still like to support Sponge but obviously it is taking way too long for me to get to it. I'll have to look around again, perhaps some of the version lookup logic is easier now.

If you agree, I can try to do it.

That would be great!

Working on it. Thanks!!

I can't push new branches!!

@itzg ??

Fork and submit a PR...

@s0rcerer88 sorry for the delay. Yes, as @NynjaCypher mentioned, you'll fork and then submit a PR via your fork. Here is Github's docs on working with forks
https://help.github.com/articles/working-with-forks/
but since you have likely cloned itzg/dockerfiles and made changes in your local clone you'll roughly follow these steps:

Fork via Github
Add your forked repo as a remote within your local cloned directory
Checkout the master branch of your repo as a new local branch
Commit changes to that local branch
Push to your repo
In Github submit a PR. It should auto suggest my repo as the destination of the PR

Ohh. Thanks for the info. My very first time using GitHub.

PR sent.

SpongeVanilla integration completed. Changes merged.
SpongeForge integration in progress.

Great news, thanks for this :P

Is any chance for SpongeForge integraftion?

@RoSulek1 oops, looks like this issue got completed successfully. I know that because I can see the code in place should make it fairly easy to add SpongeForge. Can you create a new issue for that specifically?

Done [https://github.com/itzg/dockerfiles/issues/245]
thx :)


Strange behaviour when View embedded on scrollview

If you try to scroll and swipe at the same time, sometimes it works not as expected. Actions appear only partially


Fix add a section

What is the context of this PR?
Fixes #125

sured up code that passes id's around
refactored layout out of page components and into route definition to
to make testing easier
added some tests

How to review
As per bug repro steps

@hamishtaplin There's still some weird things happening with the sidebar for me on this branch. Happy to demo.


Bug: Invalid memory access on LLVMContextDispose

I was able to "reduce" the random crash that sometimes happens on travis and CI.
To reproduce, compile this file:
require "compiler/crystal/**"

def compile
  compiler = Crystal::Compiler.new
  compiler.debug = Crystal::Debug::All
  compiler.compile([
    Crystal::Compiler::Source.new("lala.cr", ""),
  ], "lala")
end

1000.times do |i|
  puts "Start: #{i}"

  compile

  puts "Done compiling: #{i}"

  10.times { GC.collect }

  puts "End: #{i}"
end

The run it, making sure to set the CRYSTAL_PATH env var to the "src" folder of the compiler, otherwise the prelude won't be found.
The crash happens randomly, so after it prints "Start: 20" you can ctrl+c and then run it again. This is the crash I sometimes get:
Invalid memory access (signal 11) at address 0xe0
[0x1062fd23b] *CallStack::print_backtrace:Int32 +107
[0x1062d73ac] __crystal_sigfault_handler +60
[0x107d37713] sigfault_handler +35
[0x7fff91199b3a] _sigtramp +26
[0x107c7e860] _ZNK4llvm12DenseMapBaseINS_13SmallDenseMapIPvNSt3__14pairINS_12PointerUnionIPNS_15MetadataAsValueEPNS_8MetadataEEEyEELj4ENS_12DenseMapInfoIS2_EENS_6detail12DenseMapPairIS2_SB_EEEES2_SB_SD_SG_E15LookupBucketForIS2_EEbRKT_RPKSG_ +6
[0x107c770fc] _ZN4llvm12DenseMapBaseINS_13SmallDenseMapIPvNSt3__14pairINS_12PointerUnionIPNS_15MetadataAsValueEPNS_8MetadataEEEyEELj4ENS_12DenseMapInfoIS2_EENS_6detail12DenseMapPairIS2_SB_EEEES2_SB_SD_SG_E5eraseERKS2_ +18
[0x107c76f49] _ZN4llvm16MetadataTracking7untrackEPvRNS_8MetadataE +49
[0x107c7977d] _ZN4llvm9MDOperand5resetEPNS_8MetadataES2_ +35
[0x107c7ac98] _ZN4llvm6MDNode17dropAllReferencesEv +102
[0x107c673f7] _ZN4llvm15LLVMContextImplD2Ev +2715
[0x107c655a8] _ZN4llvm11LLVMContextD2Ev +22
[0x107c2b996] LLVMContextDispose +22
[0x106fb986c] *LLVM::Context#finalize:Nil +140
[0x1062e0fe1] ~proc6Proc(Pointer(Void), Pointer(Void), Nil)@src/gc/boehm.cr:142 +17
[0x1095938e0] GC_invoke_finalizers +172
[0x109593a2f] GC_notify_or_invoke_finalizers +174
[0x10958f943] GC_try_to_collect_general +203
[0x10958f973] GC_gcollect +11
[0x1063331d9] *GC::collect:Nil +9
[0x1062bed38] __crystal_main +2936
[0x1062d7218] main +40

Sometimes the trace is a bit different.
This happens when passing Crystal::Debug::All for the debug info. It doesn't happen with Crystal::Debug::None. It seems to be related to disposing an llvm MDNode twice, or something like that.
I have no idea why it happens. Our code makes sure that an LLVM::Context is disposed only once. Maybe our custom bindings to the LLVM C++ debug API has bugs, I don't know. I also tried to trace this in LLVM's source code but it's huge and it's written in C++.
The "good" thing is that this is very unlikely to happen when compiling one file. But there's a chance it happens in tests, and then we have to restart CI from time to time and hope it passes.
Any help finding the cause of this would be greatly appreciated! :-)

I can't reproduce, so I can't tell for sure, but:
The DIBuilder is attached to a Module or Context, doesn't it? Would it be possible that we dispose of the module/context before we dispose of the DIBuilder but the DIBuilder dispose method needs to access it?

I thought so, yes, but we never dipose DIBuilders ¯_(ツ)_/¯


Fast typing leads to cursor lag

If you type really quickly, especially if you delete a lot and then type immediately after, the cursor will sometimes lag behind by one position. A lot of actions are being done on every change to the text-editor, it may just not be able to keep up with high wpm, but it is very annoying. Look into a way to mitigate this.

Always happens after selection


Fix missing diagnostics about the lack of initializers in cross-module inheritance scenarios

When a class inherits a superclass from another module, and that superclass has non-public designated initializers, two important diagnostics were being suppressed:

The diagnostic about any required initializers in the superclass that couldn't be synthesized in the subclass, and
The diagnostic about the lack of any initializers in the subclass.

Between the two, it became possible to create a class that could not be initialized statically (doing so would produce an error), but that could be dynamically created via the required initializer---without initializing the subclass's storage. Introduce diagnostics for both, staging them in via warnings in Swift 5 and becoming errors in Swift 6.
Fixes https://github.com/apple/swift/issues/69965

@swift-ci please smoke test

@swift-ci please smoke test Linux

@swift-ci please smoke test macOS

Ah, it looks like we have a few other instances of this pattern in our test suite that I'll need to fix up.

I'm splitting this into two different PRs. The most critical fix is the required initializer change, because that's a proper soundness hole in the system, and is now covered by https://github.com/apple/swift/pull/70236.
The second fix (of the "no constructors of class...") needs more work.


Traceroute collector

Extracting traceroute information into metrics and dimensions for hops and ips on the way. You can then visualise this data by getting the percentage of RTT spent in each hop and get a graph representing a slice per hop, so you can easily detect when you have network issue where they are coming from.

lgtm. ship it.

All minors comments. +1

I'm going to patch this for paris-traceroute -nq 1 instead of mtr -rnc 1 as soon as you ship. sorry.

This is not really super important but I am kinda wary of super long methods (I know I have repeated this argument enough number of times elsewhere).
Splitting a method is not only about code reusability, it is about readability also. It allows reader to scan code quickly without reading each line carefully. For example:
def collect(self):
  read_mtr_config()
  parse_hop_data()

It is still same logic but it allows the brain to abstract certain part of code and assume it does what the method name says it does, without getting into specific of implementation details.
Currently I see a big collect method that does everything and reader must read each line carefully to understand what it does.

@gnufied as for big methods, as you mentioned it is a matter of taste and perspective :) tbh for me this stricture is less convoluted and easier to read through and debug without jumping into and out of scopes and functions. Also there is no re-usability vector that I can easily spot within the collector.
Would you be so kind and make this a non blocking issue?

It is not a blocker @tsheasha . Just good software design principle and subject to opinion of course. I would urge you to read - https://sourcemaking.com/refactoring/smells/long-method

@yeled paris-traceroute is now being used instead of mtr.

I have removed the default value of the bin path and hence it is required by the user to define this in their config file.
The reason is, for libparistraceroute1 you can compile it as the paris-traceroute binary or traceroute. Both of which produce the same output so the parsing will not fail, however this make it impossible to define a sane default bin path, so I decided to leave that as an exercise for the user.

lgtm. +1


Download multiple OSM way fields using "infrastructure" parameter in graph_from_* (e.g. "cycleway", "surface", "bicycle")?

Question description
I would like to be able to download multiple OSM way fields, including for example, "cycleway", "bicycle", "surface", etc. (a) Can this be done in a single ox.graph_from_* call in the infrastructure parameter? (b) If not, and you must make multiple ox.graph_from_* calls with different infrastructure parameters, are there methods to join/merge the multiple resulting graphs (i.e. by osm_id) to a single graph with all of the relevant infrastructure fields included?
Code that illustrates the question
# This attempt to return both the highway and the cycleway fields doesn't work.
# Perhaps I'm using the wrong syntax? I've tried this in a couple different ways
# and haven't had any success.
gilbert_multiple_fields = ox.graph_from_place(query = 'Gilbert, Arizona, USA',
                                       network_type='bike',
                                       infrastructure = 'way["highway", "cycleway"]')

# Returns the graph (street network) contained within the polygon of Tempe and
# neighboring cities' boundaries and the highway field
gilbert_highway = ox.graph_from_place(query = 'Gilbert, Arizona, USA',
                                       network_type='bike',
                                       infrastructure = 'way["highway"]')

# Returns the graph (street network) contained within the polygon of Tempe and
# neighboring cities' boundaries and the cycleway field
gilbert_cycleway = ox.graph_from_place(query = 'Gilbert, Arizona, USA',
                                       network_type='bike',
                                       infrastructure = 'way["cycleway"]')

# How best to merge/join?

@cgthigpen This is a useful question to unpack as others might also have it. OSMnx's network_type paradigm operates by filtering things out. That is, if you request network_type='bike', OSMnx returns all the ways with a highway tag, filtering out all the ways that you cannot bike on: https://github.com/gboeing/osmnx/blob/3befcf62feef48ee434cc11b4ec57c59cffbaff1/osmnx/core.py#L555
But remember that highways and cycleways aren't different infrastructure types on OSM. All paths, streets, cycleways, etc are types of highways: https://wiki.openstreetmap.org/wiki/Highways
The latest release of OSMnx includes the ability to use custom query filters, which was added in this PR: https://github.com/gboeing/osmnx/pull/139 For example, see the custom filter documentation for graph_from_place: https://osmnx.readthedocs.io/en/stable/osmnx.html#osmnx.core.graph_from_place Specifically, what you pass as infrastructure and custom_filter will get inserted into an Overpass query here: https://github.com/gboeing/osmnx/blob/3befcf62feef48ee434cc11b4ec57c59cffbaff1/osmnx/core.py#L670
So you can customize it however you like. That said, part of the value-add of OSMnx's network_types is that you can avoid the pain of working with the Overpass Query Language... but for complicated tasks or mixed infrastructure types, the custom_filter argument offers the most power. Language resources:

https://wiki.openstreetmap.org/wiki/Overpass_API/Language_Guide
https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL

Now, to get cycleways with OSMnx...
Something like this should get you everything where highway=cycleway:
G = ox.graph_from_place(query = 'Gilbert, Arizona, USA',
                        infrastructure = 'way["highway"]',
                        custom_filter='["highway"~"cycleway"]')

Whereas something like this gets you everything with a cycleway key, regardless of its value:
G = ox.graph_from_place(query = 'Gilbert, Arizona, USA',
                        infrastructure = 'way["cycleway"]')

And this gets you everything you "can" bike on, even if it's not dedicated bike infrastructure:
G = ox.graph_from_place(query = 'Gilbert, Arizona, USA', network_type='bike')

Finally, if you want a graph comprising everything with either a cycleway key or highway=cycleway:
import osmnx as ox
useful_tags = ox.settings.useful_tags_path + ['cycleway']
ox.config(use_cache=True, log_console=True, useful_tags_path=useful_tags)
G = ox.graph_from_place(query = 'Gilbert, Arizona, USA', network_type='bike', simplify=False)
non_cycleways = [(u, v, k) for u, v, k, d in G.edges(keys=True, data=True) if not ('cycleway' in d or d['highway']=='cycleway')]
G.remove_edges_from(non_cycleways)
G = ox.remove_isolated_nodes(G)
G = ox.simplify_graph(G)

That is, we permissively downloaded more than we needed using the query. Then we found all the non-cycleways and removed them from the graph. Then we remove any nodes left isolated by that action, before finally simplifying the graph's topology. Throwing useful_tags into the config makes sure OSMnx retains the values of that tag as graph edge attributes.
To summarize, the OSMnx paradigm is to query liberally then filter things out.

Thank you for the detailed and clear explanation, @gboeing.
I ended up just using the useful_tags = ox.settings.useful_tags_path + ['cycleway'] functionality you pointed out, which served my needs of downloading additional OSM fields for use in my analysis.

In case anyone else comes along here looking for information, please note that the old infrastructure parameter was deprecated and replaced by the custom_filter parameter and that the old useful_tags_path setting was replaced by the useful_tags_way setting in recent releases.

My first time with OSM Data, I am trying to compare bike infrastructure to car infrastructure. The example from above does not nearly provide all bike lanes in my hometown. It reports a total of 170 km edge length.
I added a third filter on the bicycle=designated tag, that gave me more realistic results, a total edge length of 455 km. But still not every bike infrastructure. I can see a lot more on https://www.opencyclemap.org/. A quick look in the OSM source data told me that many streets are not tagged for cycling altough they carry official bike routes. Yeah, kind of difficult to decide here what is bike infrastructure and what is just a normal street/forest path with some signs for bikers.
My quick and dirty working example:
import osmnx as ox
useful_tags = ox.settings.useful_tags_way + ['cycleway'] + ['bicycle']
ox.utils.config(use_cache=True, log_console=True, useful_tags_way=useful_tags)
G = ox.graph_from_place(query = 'Berlin, Deutschland', network_type='bike', simplify=False,  retain_all=True)

non_cyc = []
for u,v,k,d in G.edges(keys=True, data=True):
    bi = False
    if "bicycle" in d: #kind of uggly but not every edge has the bicycle tag
        if d['bicycle']=='designated':
            bi = True

    if d['highway']=='cycleway':
        pass
    elif 'cycleway' in d:
        pass
    elif bi:
        pass
    else:
        non_cyc.append((u,v,k))

G.remove_edges_from(non_cyc)
G = ox.utils_graph.remove_isolated_nodes(G)
G = ox.simplify_graph(G)
stats = ox.stats.basic_stats(G)
print(stats["edge_length_total"])
fig, ax = ox.plot_graph(G)
```

Yeah, just my 5 Cents for somebody with the same "problem" watching this issue here.


[BUG]

Describe the bug
The program doesnt start properly. The error code appears to be about a bad variable declare.
I think it could be a kind of mismatch of version, but, Ive triple check it, and all dependancies are satisfied

root@Inspiron-5548:/opt/halinuxcompanion# python3 -m halinuxcompanion -c config.json
/usr/lib/python3/dist-packages/requests/init.py:89: RequestsDependencyWarning: urllib3 (1.25.8) or chardet (5.2.0) doesn't match a supported version!
warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/opt/halinuxcompanion/halinuxcompanion/main.py", line 2, in
from halinuxcompanion.dbus import Dbus
File "/opt/halinuxcompanion/halinuxcompanion/dbus.py", line 79, in
class Dbus:
File "/opt/halinuxcompanion/halinuxcompanion/dbus.py", line 82, in Dbus
interfaces: dict[str, ProxyInterface] = {}
TypeError: 'type' object is not subscriptable
root@Inspiron-5548:/opt/halinuxcompanion#

To Reproduce
Steps to reproduce the behavior:
I just follow instructions on README.
used pip3 to install (and recheck) all dependencies
copy config.example.json to config.json and have it edited.
Expected behavior
App doesnt start and give the error messages above
Application Logs
I couldnt find any log in app directory or /var/log
Home Assistant Logs
as long as it doesnt even started (or connect), the HA server could`t register any log about it.
Additional context
Dist: ZorinOS 16.3

The stack trace contains File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main, so it sounds like you're trying to run it on Python 3.8. The README says that Python 3.10 is a requirement, while the tests currently run on Python 3.11: https://github.com/muniter/halinuxcompanion/blob/7a65b6f6e7341d031d8e16a042112ffc7f726056/.github/workflows/build.yml#L20
So I think you need to at least start by updating your Python version.

Hi,
my error is similar.
chef@PC:~/halinuxcompanion$ python3 -V
Python 3.12.3
chef@PC:~/halinuxcompanion$ python3.12 -m halinuxcompanion --config config.json
INFO:halinuxcompanion:Reading configuration file config.json
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/home/chef/halinuxcompanion/halinuxcompanion/main.py", line 104, in
loop.run_until_complete(main())
File "/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/home/chef/halinuxcompanion/halinuxcompanion/main.py", line 64, in main
companion = Companion(config)  # Companion objet where configuration is stored
^^^^^^^^^^^^^^^^^
File "/home/chef/halinuxcompanion/halinuxcompanion/companion.py", line 99, in init
parsed = CompanionConfig.model_validate(config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: type object 'CompanionConfig' has no attribute 'model_validate'
Can anybody help me?
Thanks

That looks like a completely different error to me, I would suggest opening a new issue.

Agreed, previous error was about wrong python version, if the error persists @MatzeP feel free to create a new issue.


Unable to configure SSD1306 connected to Mega2560

Hi!
I'm running OpenDeck 4.1.1 on a Mega2560 (a DIYMore Mega2560 Strong - very easy to hook up, so I recommend). I found some spare SSD1306 OLEDs in a parts box and thought I'd try and connecting one to the board, but the configuration stage is failing.
Going to the Display tab, both controller and resolution show 'Invalid':

I set them accordingly (note, here I've not enabled it - that makes no difference):

Now, when I try to go to another tab, the details are blank:

The DevTools console has an angular error showing - Possibly unhandled rejection: {"errNumber":7}.
Returning to the Display tab, that's completely empty now as well:

Clicking on the ℹ button at the bottom then throws the configurator back to the 'Searching for OpenDeck board' screen, but it's much darker than normal because a modal has tried to open, and the configurator is completely unresponsive. It also seems to crash the code on the board, as refreshing the configurator sees it unable to progress past the searching screen. The board needs to be unplugged and plugged back in before being able to use the configurator again.
This happens whether or not the OLED is actually attached, and as soon as the resolution is modified (even if set back to Invalid). Tested on Chrome and the standalone configurator on Windows.

I'll take a look on it as soon as I wrap up MIDI bootloader thing.

Should be resolved now, can you verify? Changes are on master currenty, you will need to build the firmware:
make TARGETNAME=mega2560
make flash PORT=some_port

I won't be able to until Monday - I'll let you know then!

OK, I built and flashed the master branch on my Linux box, which was successful. The two displays I tried are both 128x64 (but the boards are completely different) - neither of them would display anything. After trying to get that set up, the configurator stopped connecting to the board at all (using the github.io hosted version of it - didn't have time to try a local version). In the end I had to reflash the 4.1.2 firmware to be able to get the configurator to connect to anything, and when I did that the display tab was completely blank, and the log on the left side repeated Error a load of times).
I made sure the OLEDs were working by running the Adafruit SSD1306 Arduino library example code (like I said, I found them in a box of spares, and didn't know their state). They worked fine, however I had to change the I2C address from what was set in the example (0x3D for Adafruit's 128x64 OLED to 0x3C).
I'll try and look into it more, however we've had a death in the family today and I'm not sure what happens next with the Covid-19 lockdown in place 😟

It's most likely an address issue then, I need to take a look at I2C driver since it can block the entire app currently (not good!) on wrong address. Works fine for the displays I'm using so haven't bothered to look into that yet, but I will. I have some generic I2C SSD1306 displays from eBay.
So sorry for your loss! :( Hope you're doing okay.

Yeah, just about ok. Didn't come as a shock, but the timing is horrible. Anyway, trying to keep my mind on other things.
If your display has 0x78 on the silkscreen on the back, that's probably one of the same displays as I've got. As I understand it, 0x78 is an 8-bit address (01111000) and 0x3C is its 7-bit equivalent (00111100) but I'm pretty far from an expert there 😉 I'll triple check the wiring set up later on with a logic probe to see if I can figure out what's going on.

Update!

I've totally reworked I2C API - if anything is messed up it won't halt the MCU anymore. https://github.com/paradajz/OpenDeck/commit/3754b7d9c3738e42c3bfdcca91c57b5ceb6f3f18
I've added the ability to define I2C address for display - it's currently exposed in Web interface.

Amazing 🙂 I'll get it installed on Tuesday and see how it goes (I won't be
in my work area until then, otherwise I'd be at it now!)
--
Steve Anderson - Irregular Shed
Sent from my Ouija board
On Sun, 24 May 2020, 14:10 paradajz<EMAIL_ADDRESS>wrote:

Update!

I've totally reworked I2C API - if anything is messed up it won't
halt the MCU anymore. 3754b7d
https://github.com/paradajz/OpenDeck/commit/3754b7d9c3738e42c3bfdcca91c57b5ceb6f3f18
I've added the ability to define I2C address for display - it's
currently exposed in Web interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/paradajz/OpenDeck/issues/28#issuecomment-633228800,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABONL6TUDYYW55IE3K6FELRTEMFPANCNFSM4MXBONMQ
.

Still not working for me, sorry. I just built and flashed the 5.0.0 firmware (checked on the info page) and then tried to enable a display. Nothing seemed to be happening so I disconnected and reconnected. Now the configurator thinks I've got 247 rotary encoders (first part of screen shown), and the log says ERROR WISH a lot:

And the version has gone completely wrong, showing either v0.247.undefined or v1.247.undefined

247 keeps coming up!
I haven't changed the bootloader on the 16u2 since I had it working, before I started trying to get displays hooked up. I'm assuming nothing has changed in there that could cause this, but will try reflashing that when I get some time.

Weird, works fine on my end with multiple boards. Try reflashing both 16u2 and 2560.

Sorry , I'll close this. Works fine here with multiple boards, and it works even on STM32F4 Discovery board. Don't really know what is wrong in your setup.

No problem. I've got WAY too much going on in life right this second to look into it, thanks for everything 👍


v0.0 does not work

I cannot for the life of me get the 0.0 version working as I need IE9 support. I get the following error:
Cannot read property 'flow' of undefined
Which occurs here:

Any ideas on how I can fix this? Great work on this btw!

Same problem here. I adapted the HTML code from the Holy Grail Demo:

A

B

C

D

I see the panels and their content, but I cannot move the sliders, and I get an error at ui.layout.js:50

Can you create a JSBin reproducing this issue?

Closing issue, no follow up, and supporting the 0.0 version isn't on the agenda for this project.