Invalid cref value "!:Texture3D" found in triple-slash-comments for Width defined in ../../stride/sources/engine/Stride.Graphics/TextureDescription.cs Line 45, ignored.
Invalid cref value "!:Texture3D" found in triple-slash-comments for Width defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 47, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for ArraySize defined in ../../stride/sources/engine/Stride.Graphics/TextureDescription.cs Line 72, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for ArraySize defined in ../../stride/sources/engine/Stride.Graphics/TextureDescription.cs Line 72, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for ArraySize defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 74, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for ArraySize defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 74, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for CubeMapFace defined in ../../stride/sources/engine/Stride.Graphics/CubeMapFace.cs Line 9, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for Height defined in ../../stride/sources/engine/Stride.Graphics/TextureDescription.cs Line 53, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for Height defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 55, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for Width defined in ../../stride/sources/engine/Stride.Graphics/TextureDescription.cs Line 45, ignored.
Invalid cref value "!:TextureCube" found in triple-slash-comments for Width defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 47, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 569, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 592, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTarget defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 268, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargetAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 186, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 281, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 293, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 312, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 212, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 224, ignored.
Invalid cref value "!:Textures+and+render+targets" found in triple-slash-comments for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 243, ignored.
Invalid cref value "!:Type.Name" found in triple-slash-comments for TypeName defined in ../../stride/sources/core/Stride.Core/Diagnostics/ExceptionInfo.cs Line 65, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 125, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 138, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 186, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 199, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 45, ignored.
Invalid cref value "!:UnorderedAccessView" found in triple-slash-comments for New defined in ../../stride/sources/engine/Stride.Graphics/Buffer.Structured.cs Line 63, ignored.
Invalid cref value "!:VertexBufferLayout" found in triple-slash-comments for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43, ignored.
Invalid cref value "!:VertexBufferLayout" found in triple-slash-comments for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43, ignored.
Invalid cref value "!:VertexBufferLayout.SlotIndex" found in triple-slash-comments for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43, ignored.
Invalid cref value "!:VertexBufferLayout.VertexClassification" found in triple-slash-comments for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43, ignored.
Invalid cref value "!:VertexBufferLayout.instanceDataStepRate" found in triple-slash-comments for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43, ignored.
Invalid cref value "!:WhitePoint" found in triple-slash-comments for Threshold defined in ../../stride/sources/engine/Stride.Rendering/Rendering/Images/BrightFilter/BrightFilter.cs Line 46, ignored.

Group 3 - Probably easy to fix
Many related to AudioListener.cs and AudioEmitter.cs
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Graphics.GraphicsDeviceFeatures.yml: warning InvalidBookmark: Invalid link: 'UpdateSubresource(GraphicsResource, int, DataBox)'. The file api/Stride.Graphics.CommandList.yml doesn't contain a bookmark named 'Stride.Graphics.CommandList.UpdateSubresource(Stride.Graphics.GraphicsResource,System.Int32,Stride.Graphics.DataBox)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListener.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListenerProcessor.yml: warning InvalidBookmark: Invalid link: 'audioSystem'. The file api/Stride.Audio.AudioListenerProcessor.yml doesn't contain a bookmark named 'Stride.Audio.AudioListenerProcessor.audioSystem'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioListenerProcessor.yml: warning InvalidBookmark: Invalid link: 'audioSystem'. The file api/Stride.Audio.AudioListenerProcessor.yml doesn't contain a bookmark named 'Stride.Audio.AudioListenerProcessor.audioSystem'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Core.Diagnostics.Profiler.yml: warning InvalidBookmark: Invalid link: 'Logger'. The file api/Stride.Core.Diagnostics.Profiler.yml doesn't contain a bookmark named 'Stride.Core.Diagnostics.Profiler.Logger'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Engine.EntityTransformExtensions.yml: warning InvalidBookmark: Invalid link: 'Remove(Scene)'. The file api/Stride.Engine.SceneInstance.yml doesn't contain a bookmark named 'Stride.Engine.SceneInstance.Remove(Stride.Engine.Scene)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitter.yml: warning InvalidBookmark: Invalid link: 'Apply3D'. The file api/Stride.Audio.IPositionableSound.yml doesn't contain a bookmark named 'Stride.Audio.IPositionableSound.Apply3D(Stride.Audio.AudioEmitter)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Audio.AudioEmitterSoundController.yml: warning InvalidBookmark: Invalid link: 'sound'. The file api/Stride.Audio.AudioEmitterSoundController.yml doesn't contain a bookmark named 'Stride.Audio.AudioEmitterSoundController.sound'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Particles.ParticleEmitter.yml: warning InvalidBookmark: Invalid link: 'requiredFields'. The file api/Stride.Particles.ParticleEmitter.yml doesn't contain a bookmark named 'Stride.Particles.ParticleEmitter.requiredFields'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Particles.ParticleEmitter.yml: warning InvalidBookmark: Invalid link: 'requiredFields'. The file api/Stride.Particles.ParticleEmitter.yml doesn't contain a bookmark named 'Stride.Particles.ParticleEmitter.requiredFields'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Core.Assets.AssetItem.yml: warning InvalidBookmark: Invalid link: 'Clone(out Dictionary<Guid, Guid>)'. The file api/Stride.Core.Assets.AssetCloner.yml doesn't contain a bookmark named 'Stride.Core.Assets.AssetCloner.Clone(System.Collections.Generic.Dictionary{System.Guid,System.Guid}@)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Core.Assets.AssetItem.yml: warning InvalidBookmark: Invalid link: 'Clone(out Dictionary<Guid, Guid>)'. The file api/Stride.Core.Assets.AssetCloner.yml doesn't contain a bookmark named 'Stride.Core.Assets.AssetCloner.Clone(System.Collections.Generic.Dictionary{System.Guid,System.Guid}@)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Graphics.Font.FontSystem.yml: warning InvalidBookmark: Invalid link: 'GraphicsDevice'. The file api/Stride.Graphics.Font.FontSystem.yml doesn't contain a bookmark named 'Stride.Graphics.Font.FontSystem.GraphicsDevice'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Streaming.StreamingTexture.yml: warning InvalidBookmark: Invalid link: 'FlushSync()'. The file api/Stride.Streaming.StreamingTexture.yml doesn't contain a bookmark named 'Stride.Streaming.StreamingTexture.FlushSync'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.UI.Controls.ScrollingText.yml: warning InvalidBookmark: Invalid link: 'ResetDisplayingText()'. The file api/Stride.UI.Controls.ScrollingText.yml doesn't contain a bookmark named 'Stride.UI.Controls.ScrollingText.ResetDisplayingText'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Engine.AudioListenerComponent.yml: warning InvalidBookmark: Invalid link: 'AddListener(AudioListenerComponent)'. The file api/Stride.Audio.AudioSystem.yml doesn't contain a bookmark named 'Stride.Audio.AudioSystem.AddListener(Stride.Engine.AudioListenerComponent)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Engine.AudioListenerComponent.yml: warning InvalidBookmark: Invalid link: 'RemoveListener(AudioListenerComponent)'. The file api/Stride.Audio.AudioSystem.yml doesn't contain a bookmark named 'Stride.Audio.AudioSystem.RemoveListener(Stride.Engine.AudioListenerComponent)'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Input.PointerDeviceState.yml: warning InvalidBookmark: Invalid link: 'invSurfaceSize'. The file api/Stride.Input.PointerDeviceState.yml doesn't contain a bookmark named 'Stride.Input.PointerDeviceState.invSurfaceSize'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Graphics.Image.yml: warning InvalidBookmark: Invalid link: 'pixelBufferArray'. The file api/Stride.Graphics.Image.yml doesn't contain a bookmark named 'Stride.Graphics.Image.pixelBufferArray'.
D:\Projects\GitHub\stride-docs-next\en\api\Stride.Graphics.Image.yml: warning InvalidBookmark: Invalid link: 'pixelBufferArray'. The file api/Stride.Graphics.Image.yml doesn't contain a bookmark named 'Stride.Graphics.Image.pixelBufferArray'.

Just a note. The recent merged PR reduced the warnings from 199 to 154.

Working on this issue, in the upcoming PR there will be 131 warnings from 154.

We are down to 90 xml comments issues from 167.

I will list the remaining here, in cose someone wants to work on them. Otherwise I will keep fixing them..
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Audio\CompressedSoundSource.cs(20,24): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(5,49): warning CS0436: The type 'PublicKeys' in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(6,49): warning CS0436: The type 'PublicKeys' in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(7,62): warning CS0436: The type 'PublicKeys' in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\a\stride-docs\stride-docs\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\a\stride-docs\stride-docs\stride\sources\assets\Stride.Core.Assets\IAssetComposite.cs(17,21): warning CS0618: 'AssetPart' is obsolete: 'This struct might be removed soon'
warning: D:\a\stride-docs\stride-docs\stride\sources\assets\Stride.Core.Assets\PackageSession.cs(1583,22): warning CS0659: 'PackageSession.PendingPackageUpgrade' overrides Object.Equals(object o) but does not override Object.GetHashCode()
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\ByteHeightStickArraySource.cs(45,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\IHeightStickArraySource.cs(26,24): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Data\HeightfieldColliderShapeDesc.cs(81,24): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(129,16): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(131,16): warning CS0618: 'UnmanagedArray<byte>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(133,16): warning CS0618: 'UnmanagedArray<float>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\ShortHeightStickArraySource.cs(45,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(42,86): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(47,86): warning CS0618: 'UnmanagedArray<byte>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(52,86): warning CS0618: 'UnmanagedArray<float>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\FloatHeightStickArraySource.cs(35,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\HeightStickArraySourceFromHeightmap.cs(34,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\a\stride-docs\stride-docs\stride\sources\engine\Stride.Physics\UnmanagedArrayExtensions.cs(18,41): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
Processing Stride.Core
Processing Stride.Core.IO
Processing Stride.Core.Mathematics
Processing Stride.Core.MicroThreading
warning: InvalidCref: Invalid cref value "!:RaiseException" found in XML documentation comment  for Exception defined in ../../stride/sources/core/Stride.Core.MicroThreading/MicroThread.cs Line [96](https://github.com/stride3d/stride-docs/actions/runs/8643227848/job/23695809560#step:6:97).
Processing Stride.Core.Serialization
Processing Stride
warning: InvalidCref: Invalid cref value "!:ParameterKeyProcessor" found in XML documentation comment  for AssemblyEffectKeysAttribute defined in ../../stride/sources/engine/Stride/Effects/AssemblyEffectKeysAttribute.cs Line 10.
warning: InvalidCref: Invalid cref value "!:EffectKeysAttribute" found in XML documentation comment  for AssemblyEffectKeysAttribute defined in ../../stride/sources/engine/Stride/Effects/AssemblyEffectKeysAttribute.cs Line 10.
warning: InvalidCref: Invalid cref value "!:IDepthStencilState" found in XML documentation comment  for CompareFunction defined in ../../stride/sources/engine/Stride/Graphics/CompareFunction.cs Line 14.
warning: InvalidCref: Invalid cref value "!:SamplerState" found in XML documentation comment  for CompareFunction defined in ../../stride/sources/engine/Stride/Graphics/CompareFunction.cs Line 14.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture1DSize" found in XML documentation comment  for Width defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 47.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture3DSize" found in XML documentation comment  for Height defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 55.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture3DSize" found in XML documentation comment  for Depth defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 63.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture1DArraySize" found in XML documentation comment  for ArraySize defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 74.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.ShaderResourceViewDescription.Texture1DResource" found in XML documentation comment  for MipLevels defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 79.
warning: InvalidCref: Invalid cref value "!:SharpDX.DXGI.Format" found in XML documentation comment  for Format defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 84.
warning: InvalidCref: Invalid cref value "!:SamplerState" found in XML documentation comment  for Border defined in ../../stride/sources/engine/Stride/Graphics/TextureAddressMode.cs Line 30.
Processing Stride.Audio
Processing Stride.Engine
warning: InvalidXmlComment: Invalid XML comment:

warning: InvalidCref: Invalid cref value "!:AudioEmitterComponent.Item(string)" found in XML documentation comment  for AudioEmitterSoundController defined in ../../stride/sources/engine/Stride.Engine/Audio/AudioEmitterSoundController.cs Line 30.
warning: InvalidCref: Invalid cref value "!:AudioEmitterComponent.Item(string)" found in XML documentation comment  for AudioEmitterComponent defined in ../../stride/sources/engine/Stride.Engine/Engine/AudioEmitterComponent.cs Line 29.
warning: InvalidCref: Invalid cref value "!:AudioEmitterComponent.Item(string)" found in XML documentation comment  for AttachSound defined in ../../stride/sources/engine/Stride.Engine/Engine/AudioEmitterComponent.cs Line 136.
D:\a\stride-docs\stride-docs\stride-docs\en\sources\engine\Stride.Engine\Engine\Entity.cs(57,1): warning: Duplicate parameter 'rotation' found in comments, the latter one is ignored.
warning: InvalidCref: Invalid cref value "!:HierarchicalProcessor" found in XML documentation comment  for Remove defined in ../../stride/sources/engine/Stride.Engine/Engine/EntityManager.cs Line 160.
warning: InvalidCref: Invalid cref value "!:InstancingProcessor" found in XML documentation comment  for BoundingBox defined in ../../stride/sources/engine/Stride.Engine/Engine/InstancingUserBuffer.cs Line 26.
warning: InvalidCref: Invalid cref value "!:EffectCompilerFactory.CreateEffectCompiler" found in XML documentation comment  for EffectCompilationMode defined in ../../stride/sources/engine/Stride.Engine/Engine/Design/EffectCompilationMode.cs Line 11.
warning: InvalidCref: Invalid cref value "!:RouterMessage" found in XML documentation comment  for ClientRouterMessage defined in ../../stride/sources/engine/Stride.Engine/Engine/Network/ClientRouterMessage.cs Line 8.
warning: InvalidCref: Invalid cref value "!:Game.GraphicsDevice.Presenter.BackBuffer" found in XML documentation comment  for RenderTarget defined in ../../stride/sources/engine/Stride.Engine/Profiling/GameProfilingSystem.cs Line 71.
warning: InvalidCref: Invalid cref value "!:T" found in XML documentation comment  for ArrayUpdateResolver defined in ../../stride/sources/engine/Stride.Engine/Updater/ArrayUpdateResolver.cs Line 11.
Processing Stride.Games
Processing Stride.Graphics
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment  for SetScissorRectangle defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 148.
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment  for SetScissorRectangles defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 160.
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment  for SetScissorRectangles defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 170.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargetAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 186.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 212.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 224.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 243.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTarget defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 268.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 281.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 293.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 312.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 569.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment  for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 592.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment  for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 44.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment  for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 55.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment  for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 67.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment  for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 80.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout" found in XML documentation comment  for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.SlotIndex" found in XML documentation comment  for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.VertexClassification" found in XML documentation comment  for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.instanceDataStepRate" found in XML documentation comment  for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout" found in XML documentation comment  for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
Processing Stride.Input
Processing Stride.Navigation
Processing Stride.Particles
Processing Stride.Rendering
warning: InvalidCref: Invalid cref value "!:CameraRendererMode" found in XML documentation comment  for IEffectMixinProvider defined in ../../stride/sources/engine/Stride.Rendering/Rendering/IEffectMixinProvider.cs Line 11.
warning: InvalidCref: Invalid cref value "!:SceneEffectRenderer" found in XML documentation comment  for IImageEffectRenderer defined in ../../stride/sources/engine/Stride.Rendering/Rendering/IImageEffectRenderer.cs Line 15.
warning: InvalidCref: Invalid cref value "!:PipelinePluginManager" found in XML documentation comment  for PipelinePluginContext defined in ../../stride/sources/engine/Stride.Rendering/Rendering/PipelinePluginContext.cs Line 7.
warning: InvalidCref: Invalid cref value "!:SceneInstance" found in XML documentation comment  for VisibilityGroup defined in ../../stride/sources/engine/Stride.Rendering/Rendering/RenderContext.cs Line 93.
warning: InvalidCref: Invalid cref value "!:RenderTargetPlugin" found in XML documentation comment  for RequireDepthStencilShaderResource defined in ../../stride/sources/engine/Stride.Rendering/Rendering/Shaders/RenderTargetKeys.cs Line 37.
warning: InvalidCref: Invalid cref value "!:WhitePoint" found in XML documentation comment  for Threshold defined in ../../stride/sources/engine/Stride.Rendering/Rendering/Images/BrightFilter/BrightFilter.cs Line 46.
Processing Stride.Shaders
warning: InvalidCref: Invalid cref value "!:Shader" found in XML documentation comment  for Data defined in ../../stride/sources/engine/Stride.Shaders/ShaderBytecode.cs Line 30.
Processing Stride.UI
Processing Stride.Video
warning: InvalidCref: Invalid cref value "!:FFmpeg.AutoGen.AVFormatContext" found in XML documentation comment  for FFmpegMedia defined in ../../stride/sources/engine/Stride.Video/FFmpeg/FFmpegMedia.cs Line 21.
Processing Stride.VirtualReality
Processing Stride.Core.Assets
warning: InvalidCref: Invalid cref value "!:ProjectBuildProfile.OutputGroupDirectories" found in XML documentation comment  for OutputGroup defined in ../../stride/sources/assets/Stride.Core.Assets/Bundle.cs Line 40.
warning: InvalidCref: Invalid cref value "!:Asset.Base" found in XML documentation comment  for Base defined in ../../stride/sources/assets/Stride.Core.Assets/OverrideUpgraderHint.cs Line 22.
warning: InvalidCref: Invalid cref value "!:Asset.BaseParts" found in XML documentation comment  for Base defined in ../../stride/sources/assets/Stride.Core.Assets/OverrideUpgraderHint.cs Line 22.
Processing Stride.Physics
Creating output...
warning: Ignore duplicated member Method:Stride.Core.Threading.Dispatcher.ForBatched``1(System.Int32,``0@,) from ../../stride/sources/core/Stride.Core/Threading/Dispatcher.cs as it already exist in ../../stride/sources/core/Stride.Core/Threading/Dispatcher.cs.
warning: Stride.Core.Threading.Dispatcher.ForBatched``1(System.Int32,``0@,) already exists in Stride.Core.Threading.Dispatcher.yml, the duplicate one Stride.Core.Threading.Dispatcher.yml will be ignored.

We are now on 122 warnings for Stride Docs API site generator with the upcoming PR from me.
We introduced 50 new by making FastList<> obsolete:
warning: D:\Projects\GitHub\stride\sources\core\Stride.Core\Collections\FastListStruct.cs(145,69): warning CS0618: 'FastList<T>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\core\Stride.Core\Collections\FastListStruct.cs(31,41): warning CS0618: 'FastList<T>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\core\Stride.Core\Collections\IndexingDictionary.cs(19,26): warning CS0618: 'FastList<T>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\core\Stride.Core\Threading\Dispatcher.cs(348,46): warning CS0618: 'FastList<T>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride\Rendering\ParameterCollection.cs(46,16): warning CS0618: 'FastList<ParameterKeyInfo>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride\Rendering\ParameterCollection.cs(20,40): warning CS0618: 'FastList<ParameterKeyInfo>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride\Rendering\ParameterCollection.cs(31,17): warning CS0618: 'FastList<ParameterKeyInfo>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Audio\CompressedSoundSource.cs(20,24): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Animations\AnimationBlender.cs(297,29): warning CS0618: 'FastList<AnimationOperation>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Rendering\LightProbes\LightProbeGenerator.cs(29,55): warning CS0618: 'FastList<Color3>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Rendering\LightProbes\LightProbeGenerator.cs(116,72): warning CS0618: 'FastList<LightProbeComponent>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Animations\AnimationCurve.cs(88,16): warning CS0618: 'FastList<KeyFrameData<T>>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Animations\AnimationProcessor.cs(16,41): warning CS0618: 'FastList<AnimationOperation>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Engine\AnimationComponent.cs(214,29): warning CS0618: 'FastList<AnimationOperation>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Animations\ComputeAnimationCurve.cs(28,17): warning CS0618: 'FastList<AnimationKeyFrame<T>>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Engine\EntityProcessor.cs(223,26): warning CS0618: 'FastList<TypeInfo>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Rendering\Compositing\ForwardRenderer.cs(42,26): warning CS0618: 'FastList<Texture>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Rendering\Compositing\ForwardRenderer.cs(43,26): warning CS0618: 'FastList<Texture>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Engine\Engine\LightProbeComponent.cs(22,16): warning CS0618: 'FastList<Color3>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Graphics\Direct3D\SwapChainGraphicsPresenter.Direct3D.cs(336,17): warning CS0618: 'FastList<Texture>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(5,49): warning CS0436: The type 'PublicKeys' in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(6,49): warning CS0436: The type 'PublicKeys' in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Properties\AssemblyInfo.cs(7,62): warning CS0436: The type 'PublicKeys' in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs' conflicts with the imported type 'PublicKeys' in 'Stride.Graphics, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'. Using the type defined in 'D:\Projects\GitHub\stride\sources\shared\SharedAssemblyInfo.cs'.
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\RenderViewStage.cs(45,16): warning CS0618: 'FastList<RenderNodeFeatureReference>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\BowyerWatsonTetrahedralization.cs(242,24): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Face>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\BowyerWatsonTetrahedralization.cs(37,26): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.HoleFace>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Compositing\RenderOutputValidator.cs(18,26): warning CS0618: 'FastList<RenderTargetDescription>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\BowyerWatsonTetrahedralization.cs(43,17): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Tetrahedron>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\BowyerWatsonTetrahedralization.cs(52,20): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Tetrahedron>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\BowyerWatsonTetrahedralization.cs(53,20): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Face>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\RenderSystem.cs(25,41): warning CS0618: 'FastList<RenderNodeFeatureReference>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\LightProbeRuntimeData.cs(34,16): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Tetrahedron>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\LightProbeRuntimeData.cs(35,16): warning CS0618: 'FastList<BowyerWatsonTetrahedralization.Face>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightGroupRendererBase.cs(54,38): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\LightProbes\LightProbeRenderer.cs(49,39): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightAmbientRenderer.cs(34,39): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightClusteredPointSpotGroupRenderer.cs(71,39): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\ForwardLightingRenderFeature.cs(616,68): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightGroupRendererShadow.cs(90,39): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightGroupRendererBase.cs(67,20): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightShaderGroupDynamic.cs(52,38): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightClusteredPointSpotGroupRenderer.cs(205,43): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\ForwardLightingRenderFeature.cs(83,26): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightGroupRendererShadow.cs(73,26): warning CS0618: 'FastList<LightShaderGroupEntry<LightGroupRendererShadow.LightGroupKey>>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightSpotGroupRenderer.cs(67,39): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\RenderLightCollection.cs(13,42): warning CS0618: 'FastList<RenderLight>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Lights\LightSpotGroupRenderer.cs(22,26): warning CS0618: 'FastList<LightShaderGroupEntry<LightSpotGroupRenderer.LightGroupKey>>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Rendering\Rendering\Images\LightShafts\LightShafts.cs(485,20): warning CS0618: 'FastList<RenderView>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Shaders\EffectReflection.cs(39,16): warning CS0618: 'FastList<EffectResourceBindingDescription>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Shaders\EffectReflection.cs(65,16): warning CS0618: 'FastList<ShaderInputAttributeDescription>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'

The remaining 73 are these:
warning: D:\Projects\GitHub\stride\sources\assets\Stride.Core.Assets\IAssetComposite.cs(17,21): warning CS0618: 'AssetPart' is obsolete: 'This struct might be removed soon'
warning: D:\Projects\GitHub\stride\sources\assets\Stride.Core.Assets\PackageSession.cs(1583,22): warning CS0659: 'PackageSession.PendingPackageUpgrade' overrides Object.Equals(object o) but does not override Object.GetHashCode()
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\IHeightStickArraySource.cs(26,24): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\HeightStickArraySourceFromHeightmap.cs(34,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\ByteHeightStickArraySource.cs(45,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(129,16): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(131,16): warning CS0618: 'UnmanagedArray<byte>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(133,16): warning CS0618: 'UnmanagedArray<float>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\ShortHeightStickArraySource.cs(45,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(42,86): warning CS0618: 'UnmanagedArray<short>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(47,86): warning CS0618: 'UnmanagedArray<byte>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Shapes\HeightfieldColliderShape.cs(52,86): warning CS0618: 'UnmanagedArray<float>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\FloatHeightStickArraySource.cs(35,31): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Data\HeightfieldColliderShapeDesc.cs(81,24): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\Engine\PhysicsConstraintProcessor.cs(17,26): warning CS0618: 'FastList<PhysicsConstraintComponent>' is obsolete: '.NET Lists can be faster in the latest .NET versions.'
warning: D:\Projects\GitHub\stride\sources\engine\Stride.Physics\UnmanagedArrayExtensions.cs(18,41): warning CS0618: 'UnmanagedArray<T>' is obsolete: 'Obtain Memory<T> using GC.Allocate*Array or a Stride-specific allocator mechanism.'
Processing Stride.Core
Processing Stride.Core.IO
Processing Stride.Core.Mathematics
Processing Stride.Core.MicroThreading
Processing Stride.Core.Serialization
Processing Stride
warning: InvalidCref: Invalid cref value "!:ParameterKeyProcessor" found in XML documentation comment for AssemblyEffectKeysAttribute defined in ../../stride/sources/engine/Stride/Effects/AssemblyEffectKeysAttribute.cs Line 10.
warning: InvalidCref: Invalid cref value "!:EffectKeysAttribute" found in XML documentation comment for AssemblyEffectKeysAttribute defined in ../../stride/sources/engine/Stride/Effects/AssemblyEffectKeysAttribute.cs Line 10.
warning: InvalidCref: Invalid cref value "!:IDepthStencilState" found in XML documentation comment for CompareFunction defined in ../../stride/sources/engine/Stride/Graphics/CompareFunction.cs Line 14.
warning: InvalidCref: Invalid cref value "!:SamplerState" found in XML documentation comment for CompareFunction defined in ../../stride/sources/engine/Stride/Graphics/CompareFunction.cs Line 14.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture1DSize" found in XML documentation comment for Width defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 47.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture3DSize" found in XML documentation comment for Height defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 55.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture3DSize" found in XML documentation comment for Depth defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 63.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.Resource.MaximumTexture1DArraySize" found in XML documentation comment for ArraySize defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 74.
warning: InvalidCref: Invalid cref value "!:SharpDX.Direct3D11.ShaderResourceViewDescription.Texture1DResource" found in XML documentation comment for MipLevels defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 79.
warning: InvalidCref: Invalid cref value "!:SharpDX.DXGI.Format" found in XML documentation comment for Format defined in ../../stride/sources/engine/Stride/Graphics/ImageDescription.cs Line 84.
warning: InvalidCref: Invalid cref value "!:SamplerState" found in XML documentation comment for Border defined in ../../stride/sources/engine/Stride/Graphics/TextureAddressMode.cs Line 30.
Processing Stride.Audio
Processing Stride.Engine
warning: InvalidCref: Invalid cref value "!:RouterMessage" found in XML documentation comment for ClientRouterMessage defined in ../../stride/sources/engine/Stride.Engine/Engine/Network/ClientRouterMessage.cs Line 8.
Processing Stride.Games
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout" found in XML documentation comment for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.SlotIndex" found in XML documentation comment for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.VertexClassification" found in XML documentation comment for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout.instanceDataStepRate" found in XML documentation comment for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
warning: InvalidCref: Invalid cref value "!:VertexBufferLayout" found in XML documentation comment for VertexElement defined in ../../stride/sources/engine/Stride.Graphics/VertexElement.cs Line 43.
Processing Stride.Input
Processing Stride.Navigation
Processing Stride.Particles
Processing Stride.Rendering
warning: InvalidCref: Invalid cref value "!:CameraRendererMode" found in XML documentation comment for IEffectMixinProvider defined in ../../stride/sources/engine/Stride.Rendering/Rendering/IEffectMixinProvider.cs Line 11.
warning: InvalidCref: Invalid cref value "!:SceneEffectRenderer" found in XML documentation comment for IImageEffectRenderer defined in ../../stride/sources/engine/Stride.Rendering/Rendering/IImageEffectRenderer.cs Line 15.
warning: InvalidCref: Invalid cref value "!:PipelinePluginManager" found in XML documentation comment for PipelinePluginContext defined in ../../stride/sources/engine/Stride.Rendering/Rendering/PipelinePluginContext.cs Line 7.
warning: InvalidCref: Invalid cref value "!:RenderTargetPlugin" found in XML documentation comment for RequireDepthStencilShaderResource defined in ../../stride/sources/engine/Stride.Rendering/Rendering/Shaders/RenderTargetKeys.cs Line 37.
warning: InvalidCref: Invalid cref value "!:WhitePoint" found in XML documentation comment for Threshold defined in ../../stride/sources/engine/Stride.Rendering/Rendering/Images/BrightFilter/BrightFilter.cs Line 46.
Processing Stride.Shaders
warning: InvalidCref: Invalid cref value "!:Shader" found in XML documentation comment for Data defined in ../../stride/sources/engine/Stride.Shaders/ShaderBytecode.cs Line 30.
Processing Stride.UI
Processing Stride.Video
warning: InvalidCref: Invalid cref value "!:FFmpeg.AutoGen.AVFormatContext" found in XML documentation comment for FFmpegMedia defined in ../../stride/sources/engine/Stride.Video/FFmpeg/FFmpegMedia.cs Line 21.
Processing Stride.VirtualReality
Processing Stride.Core.Assets
Processing Stride.Physics
Creating output...
warning: Ignore duplicated member Method:Stride.Core.Threading.Dispatcher.ForBatched``1(System.Int32,``0@,) from ../../stride/sources/core/Stride.Core/Threading/Dispatcher.cs as it already exist in ../../stride/sources/core/Stride.Core/Threading/Dispatcher.cs.
warning: Stride.Core.Threading.Dispatcher.ForBatched``1(System.Int32,``0@,) already exists in Stride.Core.Threading.Dispatcher.yml, the duplicate one Stride.Core.Threading.Dispatcher.yml will be ignored.

These should be easy to fix, once we know what Stride Docs - Manual page link should be used to reference:
Processing Stride.Graphics
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment for SetScissorRectangle defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 148.
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment for SetScissorRectangles defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 160.
warning: InvalidCref: Invalid cref value "!:Render+states" found in XML documentation comment for SetScissorRectangles defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 170.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargetAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 186.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 212.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 224.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargetsAndViewport defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 243.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTarget defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 268.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 281.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 293.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for SetRenderTargets defined in ../../stride/sources/engine/Stride.Graphics/CommandList.cs Line 312.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 569.
warning: InvalidCref: Invalid cref value "!:Textures+and+render+targets" found in XML documentation comment for Clear defined in ../../stride/sources/engine/Stride.Graphics/Direct3D/CommandList.Direct3D.cs Line 592.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 43.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 54.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 66.
warning: InvalidCref: Invalid cref value "!:Draw+a+texture" found in XML documentation comment for DrawTexture defined in ../../stride/sources/engine/Stride.Graphics/GraphicsDeviceExtensions.cs Line 79.


⚠ ClamAV has degraded performance

In 76f12fc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in 4b1b52f.


Support JSON column in SQLiteAdapter

Is there any chance of supporting JSON/JSONB column types in the SQLiteAdapter. I know Laravel's Eloquent supports them by mapping them to text which seems like a fine option to me. I'd be happy to provide a PR if you would accept such a feature.
The use case is purely for testing purposes, where I run PostgreSQL in production but want a lightweight alternative in testing. The rest of the abstraction is handled by our ORM (Yii in this case)

Since Phinx has PHINX_TYPE_JSON and PHINX_TYPE_JSONB, I wouldn't oppose it.

PR open


Add as schema extender the extra fields for select, single_choice, mu…

…ltiple_choice and from field_types, giving also option to add other schema extenders from configuration

This will be also useful for new widgets that need other fields for their configuration

can we merge this and have a new release pls?

@erral released 2.4.2
Only one thing.. please on commit, use conventional commit, prepending message with
fix:
chore:
feat:
ecc....
in this way auto-changelog will be explicative


Add strikeout support

This PR adds strikeout support.
After some digging into terminfo I found out that there actually exists a strikeout capability smxx in Miscellaneous extensions. That's a start.
However, I couldn't get any of my infocmp queries to return them without using an additional option -a which is described as:
-a   tells  `infocmp`  to  retain commented-out capabilities rather than discarding them.  Capabilities are commented by prefixing them with a period.

The only source where I found about commented-out capabilities is Termcap and Terminfo. While I'm still not sure what those are for, the -a option seems like a decent solution.
infocmp queried with -a returns way more lines of capabilities, but this doesn't seem like an issue. The only difference (apart from smxx) between the database generated by gen.sh with and without -a option was gnome-256color option MouseMode, which I believe is caused by https://github.com/gdamore/tcell/blob/b0084cc526f67fe8c7b805497680fb8e34323773/terminfo/mkinfo.go#L407-L415.
Anyway, I didn't commit the changes to the database except the smxx (strikeout) ones, because gen.sh generated about 4 slightly different properties than the existing ones even running it without -a option.
So I added strikeout attribute support and -a option to both dynamic and static terminfo generators. I chose the name strikeout instead of striketrhough because that's the way it was in the terminfo source. Let me know if you have any observations.

I'm not sure I agree with using the -a flag to infocmp -- in fact I think I specifically disagree with it.  These commented out entries are commented out for some reason, and that may be because they started from another entry that had the given capability, or it may be that the entry is unreliable or suffers from other problems.
I'm fine with adding a Strikeout capability and attribute.  It would be good to know for a fact that the terminals in question do in fact support them, particularly if infocmp doesn't report them that way by default (without the -a flag).
At some unfortunate level, I think tcell is becoming a terminal database of it's own, as we are starting to record capabilities that other terminal databases lack.  So maybe it's ok to manually just add the entries as we have them.

I’m not very happy with the -a option too. However, since it did not change anything (exexpt one MouseMode) I hoped this would be ok.
Again, none of the terminals returned the smxx without -a flag. And those that do not support strikeout did not return smxx even with -a (e. g. linux). So we have no way of knowing without the -a flag. Maybe we could do two queries - one for smxx and one for everything else? Though this is not too efficient.
Another solution would be to add \E[9m as strikeout by default, because this sequence is not used by any other terminal as far as I’ve tested. Anyway, it’s your say what to do next, I will adjust this PR.

I think I would just add this to individual terminals that we find it works on.  I would not trust -a.
It’s a new feature so I’d prefer to be conservative and only enable it on terminals it has been verified on.

I think I would just add this to individual terminals that we find it works on. I would not trust -a.

To individual physical terminals like xterm? And therefore to all xterm* terminfo entries? I thought that terminals were separated from terminfo entries though.
And would uint work for attrmask or is something more futute proof needed?

Coming back to this -- we should add entries for specific terminals that have been tested and verified to work properly.  I don't trust infocmp -a's output, as we said.
As to the mask -- we chose a value that would support being combined with 24-bit color.  That may have been a mistake.  I think we should use a 64-bit value here, or move the attributes to their own 32-bit quantity.  I'll look a little deeper.

The issue is that the Style is a 64-bit value -- and that contains the attributes in the color.  (The attributes are stashed in the upper bits of the lower 32-bit dword.)
I think we should really break this out -- we should have 32-bit colors for foreground and background, attributes, and probably also some flag bits for the color (is it RGB, is it a Theme color, etc.)  I am also wondering if 32-bits is enough for colors, because if we want to convey an alpha channel sometime, we might need back the 8 bits, so we can't store flags there.

This commit could be easily refactored now, as we have broken out the attributes into a separate 32-bit value.

All right, I'll look into it.

So instead of -a, one can use -x, which works a bit better (more like extensions than commented out entries.)


TypeError when using Redis pipeline

Laravel Version: 9.1.8
PHP Version: 8.1.2
Redis Version: 6.2.6

Description:
https://github.com/laravel/framework/blob/016b0c1801f4c6b0bb79b0d82791f4853ed19fc5/src/Illuminate/Redis/Connections/PhpRedisConnection.php#L117
This will try to get values of a Redis object instead of an array if we use the HMGET in a PIPELINE
array_values(): Argument #1 ($array) must be of type array, Redis given

detail:
#0 /var/www/html/vendor/laravel/framework/src/Illuminate/Redis/Connections/PhpRedisConnection.php(117): array_values()
#1 /var/www/html/vendor/laravel/framework/src/Illuminate/Redis/RedisManager.php(276): Illuminate\Redis\Connections\PhpRedisConnection->hmget()
#2 /var/www/html/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(337): Illuminate\Redis\RedisManager->__call()
#3 /var/www/html/routes/api.php(21): Illuminate\Support\Facades\Facade::__callStatic()

Steps To Reproduce:
use Illuminate\Support\Facades\Redis;
use Illuminate\Support\Facades\Route;

Route::get('/test', function (){
    Redis::HMSET(
        'test',
        [
            'name' => 'timndus',
            'age' => '64',
            'color' => 'green'
        ]
    );

    Redis::PIPELINE();
    Redis::HMGET('test', ['name', 'age']);
    $test = Redis::EXEC();

    return $test;
});

Please fill out the issue template when submitting issues.

Please fill out the issue template when submitting issues.

Sorry about that, I updated the issue. Can u open it or should I submit a new one? @driesvints

@driesvints I can have something ready by tonight!

Thanks. Can you maybe send in a PR for this?

Here is a PR, but honestly I'm not sure of my solution
https://github.com/laravel/framework/pull/42383

@timndus This is not the correct usage of the pipeline method, after some studying and reading into the predis test suite, this is how a pipeline should be built:
``
$pipe = Redis::pipeline();
$pipe->hmget('test', ['name', 'age', 'color']);

$results = $pipe->exec();

return $results;

``
Or you could instead use:
    Redis::pipeline(function ($pipe) {         $pipe->hmget('test', ['name', 'age']);     });
This is as how predis suggests it in their documentation. Therefore, there is no need to change the hmget() as it currently is working properly in Laravel.
Your code would not be able to work properly because the pipeline method would always return a redis object, and as it isn't yet retrieved, hmget would not function properly.

@timndus This is not the correct usage of the pipeline method

@eduance You are absolutely correct, thanks for the explanation 🙏
@driesvints This issue can be closed 🙏. And the related PR https://github.com/laravel/framework/pull/42383


No debug for NativeTlsClient

Is there a specific reason why it doesn't have a debug trait implemented? I know the direct reason is probably TlsConnector doesn't have debug. But is it just because somewhere along the line of structs, one didn't have debug and thus stopped the others from deriving debug automatically and people just didn't care to implement debug? I'm just curious, not really an issue as I don't need it, but it was just something I noticed.

Nope, it's just an oversight I think. Feel free to make a PR, or I can add it in later today otherwise!


Make agent more resilient to resource loading issues

Description
Ensure exception produced by resource construction are properly handled
Previously, exceptions could escape, making deployments hang
Traceback (most recent call last):
  File "/opt/inmanta/lib64/python3.11/site-packages/inmanta/agent/agent.py", line 737, in deploy_action
    await self.get_latest_version_for_agent(
  File "/opt/inmanta/lib64/python3.11/site-packages/inmanta/agent/agent.py", line 860, in get_latest_version_for_agent
    undeployable, resources = await self.load_resources(
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/inmanta/lib64/python3.11/site-packages/inmanta/agent/agent.py", line 1053, in load_resources
    resource: Resource = Resource.deserialize(res["attributes"])
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/inmanta/lib64/python3.11/site-packages/inmanta/resources.py", line 353, in deserialize
    obj.populate(obj_map, force_fields)
  File "/opt/inmanta/lib64/python3.11/site-packages/inmanta/resources.py", line 386, in populate
    raise Exception("Resource with id {} does not have field {}".format(fields["id"], field))

Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso7, master in 529c8fa91c9c9f72cbb04f16dc943fcf57a9c3a8

Processing #7003.


Prediction quality

Hi  tried this repo on some random room/corridor images from the net but I'm not sure if what I'm getting are the expected results as they are inferior to the example in the Readme. Can you share your opinion about the prediction quality?

Hi,
The image in the README is an annotated image (as stated in the caption). Please see the paper for results.
As with all Neural Networks the method will perform worse when faced with data outside of the training distribution.
The network is trained on synthetic data and I expect the performance will vary on real world images.
To tune the result you may adjust the mean and std of the pixel values in the config file (layout-SRW-S3D.yaml)[../blob/master/config-files/layout-SRW-S3D.yaml#L17-L18] to better match your data.
You may also decrease the (SCORE_THRESHOLD)[../blob/master/config-files/layout-SRW-S3D.yaml#89] to visualize more predictions in the images. All lines are returned in the json file together with their score.
If you want to go further you may look into papers on Domain Transfer or try to find a real world dataset with annotations you may use to fine-tune the performance using Transfer Learning.
To comment on the performance in these particular images I would say that

doesn't look that good, maybe the lamp is confusing.
Looks good to me, you may lower the SCORE_THRESHOLD to visualize the ceiling lines as well.
OK. The doors lines seem to generate a too many false positives, you can probably decrease SCORE_THRESHOLD to see the missing ceiling and floor lines.

The intended use of the method was to generate detections that could be used in a multi-view setup, so while each image does not give a full model, we hope to use detections from multiple images to generate a complete room model.
I hope that answers your question.

HI @DavidGillsjo,
Thanks for the detailed respons.
The reason I'm asking this is I'm building a Replicate (https://replicate.com/) demo for this repo where pople can run predictions online with your model and I want to make sure that the result they get are as intended.
You can view the in progress demo here https://replicate.com/davidgillsjo/srw-net and Once I finish I will add a pull request here with a the short demo script that runs online.
As you may see, the demo makes allow controlling the confidence threshold  but for the samples I attached above it didn't help much.
Do you think substructing the ImageNet mean and std instead or the input statisctics would be better here?

Wow, that looks neat!
Regarding the mean and std I'm not sure ImageNet would be representative either.
I think an indoor dataset like ScanNet or Matterport would be better.
I'll close this and answer the PR.


Rockstar for scala

Created a scala rockstar version

I am not sure if Scala programmers are cool enough to be rockstars.

@anujbahuguna thanks for PR. Merged.

Thanks anuj, merged!


No support for OnePlus Nord 2 5G yet

App Version: 2.2.0 (20)
Build Type: release
Manufacturer: OnePlus
Model: DN2101
Device: OP515BL1
Light Levels: 1
Software: Android 13 (33)

Thanks for the report.
Your phone will be excluded.


[wip][cms] add upload file deletion tracking and recovery

Coverage decreased (-24.2%) to 52.943% when pulling 0dbf4f0c9bdcec2c0123443bb19645c71d6cb264 on HiraiY:fix/fileupload_history_log into 1c71a6f339af6d4adae3fcb55f4a6098ab89317d on shirasagi:master.


mails will not be sent every time when build succeeds - only when prev…

…ious build status was FAILURE or  UNSTABLE

Jenkins please retest this


Problem with the RateLimiter

Hi,
We've faced twice during last week a failure inside RateLimiter.This is the stack trace when the exception happened.
System.Management.Automation.RemoteException
Unhandled Exception: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1.
Parameter name: dueTime
   at System.Threading.Timer.Change(Int32 dueTime, Int32 period)
   at Abot.Util.RateLimiter.ExitTimerCallback(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading._TimerCallback.PerformTimerCallback(Object state)

We're using the RateLimiter to limit the requests per second, but this only happened after days of crawling...

Hi,
Did this happen while crawling a single very long site or multiple sites?
If later, do you create new instances of all the objects for each crawl or
do you reuse them? Is rate limiting happening due to a robots.txt file
giving a crawl-delay or are you setting the
minCrawlDelayPerDomainMilliSeconds config to a value greater than 0? Trying
to get an idea of the circumstances when this occurs.
Steven
On Mon, Mar 16, 2015 at 3:13 AM, Xavi Ivars<EMAIL_ADDRESS>wrote:

Hi,
We've faced twice during last week a failure inside RateLimiter.This is
the stack trace when the exception happened.
System.Management.Automation.RemoteException
Unhandled Exception: System.ArgumentOutOfRangeException: Number must be either non-negative and less than or equal to Int32.MaxValue or -1.
Parameter name: dueTime
at System.Threading.Timer.Change(Int32 dueTime, Int32 period)
at Abot.Util.RateLimiter.ExitTimerCallback(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading._TimerCallback.PerformTimerCallback(Object state)
We're using the RateLimiter to limit the requests per second, but this
only happened after days of crawling...
—
Reply to this email directly or view it on GitHub
https://github.com/sjdirect/abot/issues/66.

Hi Steven,

This happened on a single very long site.
The rate limiting occurs because we have our own implementation of IRateLimiter (called RangeRateLimiter) that does different "request per second" limitations depending on the time of the day. This object contains a list of Abot's RateLimiter, and uses one of them appropriately.

Below you can see an extract of the code
class RangeRateLimiter: IRateLimiter
{
        public Dictionary<int, IRateLimiter> RateLimiters { get; set; }

        public void WaitToProceed()
        {
            IRateLimiter rateLimiter = GetRateLimiter(DateTime.Now);

            rateLimiter.WaitToProceed();
        }

         public IRateLimiter GetRateLimiter(DateTime dateTime)
        {
            int rate = GetRateForDateTime(dateTime);

            var secondTimeSpan = new TimeSpan(0, 0, 0, 1);
            if (!RateLimiters.ContainsKey(rate))
            {
                RateLimiters.Add(rate, new RateLimiter(rate, secondTimeSpan));
            }

            return RateLimiters[rate];
        }
}

Then, when we setup PoliteWebCrawler, we do something like
IRateLimiter rangeRateLimiter = new RangeRateLimiter();
crawler.PageCrawlStarting += (s, e) => rangeRateLimiter.WaitToProceed();

But this happened after crawling more than 900k pages, after more than 5 days of crawling (and to give you an idea, we have 2 different "rates" right now: one during the day and one at night). So the object had already been used before.

Hi,
Not really enough information to go on yet. Please keep adding details to
this and i'll take a look when after we have more details.
On Wed, Mar 18, 2015 at 12:37 PM, Xavi Ivars<EMAIL_ADDRESS>wrote:

Hi Steven,

This happened on a single very long site.
The rate limiting occurs because we have our own implementation of
IRateLimiter (called RangeRateLimiter) that does different "request per
second" limitations depending on the time of the day. This object contains
a list of Abot's RateLimiter, and uses one of them appropriately.

Below you can see an extract of the code
class RangeRateLimiter: IRateLimiter
{
public Dictionary<int, IRateLimiter> RateLimiters { get; set; }
    public void WaitToProceed()
    {
        IRateLimiter rateLimiter = GetRateLimiter(DateTime.Now);

        rateLimiter.WaitToProceed();
    }

     public IRateLimiter GetRateLimiter(DateTime dateTime)
    {
        int rate = GetRateForDateTime(dateTime);

        var secondTimeSpan = new TimeSpan(0, 0, 0, 1);
        if (!RateLimiters.ContainsKey(rate))
        {
            RateLimiters.Add(rate, new RateLimiter(rate, secondTimeSpan));
        }

        return RateLimiters[rate];
    }

}
Then, when we setup PoliteWebCrawler, we do something like
IRateLimiter rangeRateLimiter = new RangeRateLimiter();
crawler.PageCrawlStarting += (s, e) => rangeRateLimiter.WaitToProceed();
But this happened after crawling more than 900k pages, after more than 5
days of crawling (and to give you an idea, we have 2 different "rates"
right now: one during the day and one at night). So the object had already
been used before.
—
Reply to this email directly or view it on GitHub
https://github.com/sjdirect/abot/issues/66#issuecomment-83133849.

Sure.
What other details you'd like to have?

If you can artificially duplicate the issue with a isolated block of code
that would be the best. I would try to create a loop that creates
RateLimiters and callis WaitToProceed or something like that. It will be a
while until I would have time to give this a deep dive.
On Thu, Mar 19, 2015 at 12:38 PM, Xavi Ivars<EMAIL_ADDRESS>wrote:

Sure.
What other details you'd like to have?
—
Reply to this email directly or view it on GitHub
https://github.com/sjdirect/abot/issues/66#issuecomment-83735032.

I've tried to replicate it with a dozen different crawls, with the same code + configuration, crawling similar (both in size, URL structure and infrastructure, and it only failed for two of them.
I'll try to do that

Haven't heard any new info to attempt to replicate. I will be closing this issue. However if you find a way to replicate it I'll reopen.

Hi Steven,
I finally managed to reproduce (and isolate) the issue.
It seems to be related to this Danthar/RateLimiting/issues/1. Also, there are some comments on the original thread where the rate limiting code was proposed, and they suggest a fix for this.
http://www.jackleitch.net/2010/10/better-rate-limiting-with-dot-net/
There's also a comment from a Steven (maybe you?) talking about using a disposed rate limiter, with a locking proposal, and I've also found an alternative (easier) fix for the same issue here: http://stackoverflow.com/a/10526988/200472.
Does this make sense to you?


Regex find with line start matches mid-line on "find next"

VSCode Version: 1.4.0
OS Version: Mac OS X 10.11.6

Steps to Reproduce:

Open/create a document containing a line with multiple characters except {

alternatively, just fill the line with a bunch of as

Search for ^[^{]. The first character of the matching line is selected, as expected, with the find box stating something like "1 of 338"

or ^a, if you went with 1.i

Find next. Instead of going to the next matching line, the next character on the current line is selected, with the find box stating "? of 338"
Find previous works as expected

It seems as if the search is run on the substring starting after the current match; but the beginning of this substring is erroneously interpreted as "start of line".
A symmetric issue occurs with a$ and find previous.
For the moment, my workaround is searching for ^[^{].*$

Find is broken if reg ex has beginning of line pattern for some cases. When cursor is at the beginning of the line, Find next gives correct result. Otherwise not.
Because, find next takes the input from current position. If at current position, it starts with expected match then it matches it and goes into a bad state.
Simple case: ifif with reg ex ^if => Get me all lines that start with if


Rework SQL queries

SQL queries that were currently built contained bugs when paging is used together with label querying. Also they were not optimal.
The new queries work properly with paging criterias and are easier to read and also faster

Coverage decreased (-0.03%) to 89.288% when pulling 215670c65d978ea4d61967c01ca105afaceda8c2 on fix-paging into 90c021702bfc4a7ec73ac496d84465bed5eac909 on master.


As an author, posts I create can be private to another author

4/10

4

4/10

5/10

4/10

Average 4.2


Blank cells become 0

Blank cells are treated as 0 (numeric) or the Epoch "1970-01-01 00:00:00" (time), rather than NA.
Also, time values without date such as "12:34:56" becomes "1899-12-30 12:34:56".

Correction:
This behavior of blank cells is for XMLX files.
For XML files, blank cells are treated as NA, as they should be.


Support non-updating change of primary key

I understand the restriction on not changing the value of the primary key. However, it is implemented such that it cannot be set at all, even if the value is not changing. The use case for this relates to how to update objects stored in Realm. Since I may want to cancel an update, I clone the Realm object to a stand-alone one. This clone needs to include the primary key because business rule validations often require it. Updates are done on the clone, and when the user saves, I check the business rules and then need to clone back in a write transaction. I should be able to clone the primary key because its value is not actually changing, but Realm raises an exception. The need to therefore clone the primary key one way but not the other is error prone (and am I right we can no longer see if an object is already in a Realm through isValid?). Realm should only raise the exception if the oldValue and newValue differ.
Or is there a better pattern for updating an object? I assume beginWrite followed maybe or maybe not sometime later by a commitWrite/cancelWrite is a very bad idea.

Performing a check on every PK set has a non-negligible performance impact.
Since Realm doesn't override the setters for unmanaged (a.k.a. standalone) objects, it's not necessary to avoid setting their primary key property.

am I right we can no longer see if an object is already in a Realm through isValid?

That's not how you can check if an object is managed by a Realm or not. You should check the object's realm property, which is nil for unmanaged objects.

Updates are done on the clone, and when the user saves, I check the business rules and then need to clone back in a write transaction. I should be able to clone the primary key because its value is not actually changing, but Realm raises an exception.

If you update the object using Realm.create(_:value:update: true), the primary key property will just be skipped, which seems to be what you want. See RLMAddObjectToRealm() for the logic that takes care of this.

Thanks for the info. I was assuming you were using KVO to update Realm, and could just check NSKeyValueChangeOldKey vs NSKeyValueChangeNewKey and not update the database if they were the same (as opposed to re-reading the database).
And thanks for the link into the (now open) source - it's a reminder I should pull my finger out and check what the Realm code is doing myself before asking.
I'm not sure sure your answer on updating objects suits my needs - I want one copy method to do managed -> unmanaged and unmanaged -> managed to support cancelable updates. Following the paragraph above will probably sort this out.

And thanks for the link into the (now open) source - it's a reminder I should pull my finger out and check what the Realm code is doing myself before asking.

Actually realm/realm-cocoa and realm/realm-object-store have always been open source, it's realm/realm-core that was recently open sourced.


Add Fee Estimation Documentation & Best Practices

This PR is a first-draft submission for FeeEstimator documentation (including best practices). Once complete, it will close #153.
As of now, I submitted the documentation as a single file, since this will make it easier for others to read and provide comments. However, once the final edits are made, I think it would look best if I made it collapsable - like how the Blockchain Data section on the LDK Docs website has multiple sub-sections (ex: Introduction, Chain Activity, etc.). If this documentation followed that model, it would have the following sub-sections:

Overview
Fee Estimator
Confirmation Target
Best Practices
Code Example

Once we finalize the edits and align on the right format, I will update the PR to include the necessary changes to the lightningdevkit.org website so that the fee estimation documentation will be available.
Looking forward to receiving feedback!

@jkczyz - I see you added yourself as a reviewer. Let me know if you have any feedback.
One question I'm still pondering is if this documentation should be a single page (ex: Key Management) or if it should be collapsable (ex: Blockchain Data section). If it's collapsable, it would have the following sub-sections:

Overview
Fee Estimator
Confirmation Target
Best Practices
Code Example

If you or @ConorOkus have an opinion, let me know. If not, I'll probably move forward with making it collapsable and adjusting this PR to include the associated code changes to the LDK website.

Sorry about the delay. Will take a look today.
Regarding the layout, I'm somewhat indifferent. Might even consider making the "Blockchain Data" section one page. I don't mind a long page as long everything is well-delineated and doesn't come across as too intimidating (e.g., large blocks of text). And if cross referencing other sections is useful, one page may be better suited.

Thanks for the detailed comments, @jkczyz!
I've updated the docs accordingly. The only feedback I haven't incorporated yet is creating a GitHub repo with an example code base for the reader to clone/fork. If we think that's important to include before merging, I can add it in.


PRD: Auctions Page on DeFi Scan

Auctions Page on DeFi Scan (PRD)

Epic: #493

Background
Decentralised loan is slated to be released on the DeFiChain light wallet during the 2nd or 3rd week of November (TBC). To provide transparency to the community, it is important to reflect all loan-related transactions on DeFiChain through DeFi Scan.
This includes auction, which is an integral part of loan operations as it manages collaterals that are liquidated. A vault enters into an auction open vault liquidation — when the collateralisation ratio of a vault falls below its minimum. Liquidation is crucial in ensuring that all loan tokens are sufficiently over-collateralised to support its price.
Collateralization ratio =
    Total effective value of collateral /
    (Total value of tokens minted + Total interest)

Other information:

During liquidation, the entirety of loan and collateral of a vault is put up for auction. When a vault is in liquidation mode, it can no longer be used until all the loan amount is repaid before it can be reopened. Interest accrual is also stopped during liquidation process.
Collateral auction will run for 720 blocks (approximately 6 hours) with the starting price based on liquidation vault's ratio.
Anyone can participate in the auction, including the vault owner by bidding for the entirety of the auction with higher amount. To prevent unnecessary auction sniping at closing blocks, each higher bid, except the first one, has to be at least 1% higher than previous bid.

Objectives
Business/foundation objectives

To continue serving as a transparent and open-sourced community
To engage the community by providing them with a view of the activities taking place on the decentralised loans product
To attract site visitors to download the light wallet app with decentralised loan as the value proposition

Users objectives

Community: To look at the level of activity for decentralised loans within DeFiChain
Individual users: To be able to access ongoing auctions on DeFiChain (view only)

Assumptions

Users who access this feature understand the relationship between auctions and loans

To cater to this assumption, it will be useful to provide a general background on the feature to set the context for users who do not have an understanding of what auction is.

Key Success Metrics

Unique page views

User Stories
User story 1: Users want to see the list of vaults that are being auctioned
In this scenario, users are looking to browse the list of vaults that are being auctioned on DeFiChain, and have the ability to click into specific auctioned vault to find out more.
Proposed features/ interactions:

/auctions page to house all available auctions on DFC; similar to auctions page on light wallet

To set the context for users, we can include a copy on the page that explains what auctions are.

Example: "This page includes all vaults that have been entered into an auction. A vault is entered into an auction when its collateralisation ratio falls below its set minimum, which triggers liquidation. Read the pinkpaper to find out more."

To include within each auction card:

Type of auction (e.g. TSLA auction)
Rewards type (tokens) and corresponding value (in token amount and USD)
Highest bid
Time left

Clickable actions

Vault ID (which leads to /:vaultid page #450) -> This allows users to click into the auctioned vault for more information

Tasks

[ ]  /auctions page

Sign-off by:
@fuxingloh
@joeldavidw

@ngyingzhong @fuxingloh wouldn't it be easier for users to view the vaults that are in Auction from the vault's overview page? E.g. if we have the status, Empty / Healthy / At Risk / In Auction  instead of In Liquidation / Halted and we allow users to filter based on those status, then we won't even need an Auction page. User can still click on individual vault-id to view the loans that are being auctioned along with their respective information. It feels like we are making the IA more complicated than it needs to be.


The maintainer is not at the bar

Expected result
The maintainer is at the bar
Current result
The maintainer is not at the bar

Hey @AlexandreSi 👋 How are u today ?

Closing issue as it is kind of trolly


New block: Glossary Term

Add these inside Concept pages (might add a dedicated page type in the future) and brace for content errors, because the API does not know about these.

04fcd62 Allow editing of glossary terms IDs and add the option to have them auto-generated
2cdb6a8 Merge remote-tracking branch 'origin/master' into feature/glossary-terms
9e9d618 New block: Glossary Term
2cdb6a8 Merge remote-tracking branch 'origin/master' into feature/glossary-terms
0e96f78 Change content block to simple textarea element for glossary terms

Needs a key-like id field for indexing.

looks good post changes, worth checking everything aligns with what the content team want


[hotfix] Initialize UnsolicitedMessageHandler::Delegate to nullptr to avoid bu…

…ild bustage
Problem
Looks like Delegate is not set to nullptr since #5566 and it creates build/test issues.
Summary of Changes

Initialize Delegate to nullptr by default

But also, I would expect the code in Init to zero out the Delegate pointers....

OK, so after some local experimentation, assigning {} does not reliably zero out Delegate for the specific type of struct we have here.  It does for structs with other sets of members.  I haven't pinned down the exact C++ spec reasons for the difference, but the upshot is that the loop in Init should just null out Delegate, since that's the actual invariant we need to maintain.

Fixed in #5581


Meetup Support

Back in March, my co-worker and I started a TypeScript Meetup here in Portland, Oregon (see http://www.meetup.com/Portland-TypeScript-Meetup/). We're now 67 members strong with our third meeting coming up on 6/11. We're having a lot of fun building interest in the local community around TypeScript.
Any chance of getting somebody from the core team to make a trip to Portland to give a talk at one of our upcoming meetings?
Thanks for everything that you do... we love TypeScript!
Thanks,
James Churchill

Awesome to hear this. Pinging @jonathandturner since this might be in his wheelhouse sometime.

Thanks Dan. I appreciate the response.

Might also be good to have a place meetups for TypeScript and promote themselves so that other people can find them.


Use ajv

Please don't merge it yet.
Ajv has api that is similar to imjv but it is still a bit different, particularly with regards to the returned errors. So to pass tests I removed matching particular error objects. The main difference is that even with greedy option imjv still stops validation after the first error in most cases, Ajv with allErrors option collects all errors in all cases, so in case when an empty object is passed there will be many errors (one for each missing property).
So if you think that switching is something you want to do we could add actual errors returned by Ajv (but I would still only match some main properties allowing error extension). In any case it probably should be a major version change as these errors can be used.
I also had to use option validateSchema: false as some of the schemas are not valid according to JSON-Schema draft 4 and ajv validates them by default. Should be easy to fix, but it could be a part of some schema refactoring, I'll create a separate issue.

Actually, there was only one issue with schema, I fixed

will have to spend some time reviewing this and running some benchmarks and further tests on dependent libraries to assess feasibility of switching and if there is a significant value gained in performance to justify.
that's the long version of saying: "really appreciate the effort, will have to inspect in detail, but no promises :)"
replied to the question about schema refactoring.

Yes, I understand :)

Actually, maybe a better approach would be to allow to choose via options? That would make change easier (and optional) for all users/dependent libraries.

any change would have to be backward compatible of course, even if that means just wrappers around new API ...

I agree, I have an idea how...


Use universal variable naming for html/js attributes

After the latest merge, the html data attribute for the progress bar color is data-color, whereas the respective js attribute is progressBarColor.

Hints for properly resolving this issue:

also update the respective references on README.md.


nil value with lazy.nvim key setup

This is more of a support request. I have seen other people with this problem, but no solution, so I though it might be worth asking here, especially since you probably immediatedly know what's going wrong.
I'm trying to install harpoon2 with lazy like this:
return {
  "ThePrimeagen/harpoon",
  branch = "harpoon2",
  dependencies = { "nvim-lua/plenary.nvim" },
  keys = {
    {
      "<leader>h",
      function() require("harpoon"):list():add() end
    },
  }
}

When I press <leader>h I get this stracktrace:
E5108: Error executing lua: ~/.config/nvim/lua/plugins/harpoon2.lua:8: attempt to call method 'list' (a nil value)
stack traceback:
        ~/.config/nvim/lua/plugins/harpoon2.lua:8: in function <~/.config/nvim/lua/plugins/harpoon2.lua:8>

I printed out what require() returns, it's a table with setup and a few other things, but no list indeed. I tried calling setup()` before, same outcome.
What am I doing wrong here?

OS: MacOS
nvim: 0.9.5

Your config is correct.
For example, see harpoon in LazyVim
Perhaps the old harpoon version is still present?
You could try to delete your nvim folders, and download from scratch. Then, check that the correct harpoon version is in ~/.local/share/nvim/lazy.
On linux, I would remove everything with:
rm -rf ~/.local/share/nvim
rm -rf ~/.local/state/nvim
rm -rf ~/.cache/nvim

That was it! Thank you so much for taking your time to help me!


{{ item.getName }} work but not {{ item.name }}

Hello, I use the proxy and {{ item.getName }} work but not {{ item.name }}, it is possible to use .name directly with the proxy ? Thanks.

@AxelBriche is your variable $name private?

Resolved by https://github.com/KnpLabs/DoctrineBehaviors/pull/440