text:
Validation layers indicate an error in enumerate_physical_devices

Version of vulkano: 0.33.0
OS: Ubuntu 22.04.2 LTS
GPU: Mesa Intel UHD Graphics (CML GT2)
GPU Driver: i915
Vulkan API version: 1.3.204

use vulkano::VulkanLibrary;
use vulkano::instance::{Instance, InstanceExtensions};

fn main() {
    let library = VulkanLibrary::new().unwrap();
    let instance = Instance::new(library, vulkano::instance::InstanceCreateInfo {
        enabled_extensions: InstanceExtensions {
            ext_debug_utils: true,
            ..InstanceExtensions::empty()
        },
        enabled_layers: vec!["VK_LAYER_KHRONOS_validation".into()],
        ..Default::default()
    }).unwrap();
    let _ = instance.enumerate_physical_devices().unwrap();
}

Issue
This prints out validation errors due to "unknown VkStructureType" in the properties chain:
VUID-VkPhysicalDeviceProperties2-pNext-pNext(ERROR / SPEC): msgNum: -579609649 - Validation Error: [ VUID-VkPhysicalDeviceProperties2-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xdd73dbcf | vkGetPhysicalDeviceProperties2: pProperties->pNext chain includes a structure with unknown VkStructureType (1000462001); Allowed structures are [VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, VkPhysicalDeviceVulkan13Properties]. This error is based on the Valid Usage documentation for version 204 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pProperties->pNext is undefined and may not work correctly with validation enabled The Vulkan spec states: Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid instance of VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, or VkPhysicalDeviceVulkan13Properties (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPhysicalDeviceProperties2-pNext-pNext)
    Objects: 1
        [0] 0, type: 3, name: NULL
VUID-VkPhysicalDeviceProperties2-pNext-pNext(ERROR / SPEC): msgNum: -579609649 - Validation Error: [ VUID-VkPhysicalDeviceProperties2-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xdd73dbcf | vkGetPhysicalDeviceProperties2: pProperties->pNext chain includes a structure with unknown VkStructureType (1000455001); Allowed structures are [VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, VkPhysicalDeviceVulkan13Properties]. This error is based on the Valid Usage documentation for version 204 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pProperties->pNext is undefined and may not work correctly with validation enabled The Vulkan spec states: Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid instance of VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, or VkPhysicalDeviceVulkan13Properties (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPhysicalDeviceProperties2-pNext-pNext)
    Objects: 1
        [0] 0, type: 3, name: NULL
VUID-VkPhysicalDeviceProperties2-pNext-pNext(ERROR / SPEC): msgNum: -579609649 - Validation Error: [ VUID-VkPhysicalDeviceProperties2-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xdd73dbcf | vkGetPhysicalDeviceProperties2: pProperties->pNext chain includes a structure with unknown VkStructureType (1000320001); Allowed structures are [VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, VkPhysicalDeviceVulkan13Properties]. This error is based on the Valid Usage documentation for version 204 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pProperties->pNext is undefined and may not work correctly with validation enabled The Vulkan spec states: Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid instance of VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, or VkPhysicalDeviceVulkan13Properties (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPhysicalDeviceProperties2-pNext-pNext)
    Objects: 1
        [0] 0, type: 3, name: NULL
VUID-VkPhysicalDeviceProperties2-pNext-pNext(ERROR / SPEC): msgNum: -579609649 - Validation Error: [ VUID-VkPhysicalDeviceProperties2-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xdd73dbcf | vkGetPhysicalDeviceProperties2: pProperties->pNext chain includes a structure with unknown VkStructureType (1000455001); Allowed structures are [VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, VkPhysicalDeviceVulkan13Properties]. This error is based on the Valid Usage documentation for version 204 of the Vulkan header.  It is possible that you are using a struct from a private extension or an extension that was added to a later version of the Vulkan header, in which case the use of pProperties->pNext is undefined and may not work correctly with validation enabled The Vulkan spec states: Each pNext member of any structure (including this one) in the pNext chain must be either NULL or a pointer to a valid instance of VkPhysicalDeviceAccelerationStructurePropertiesKHR, VkPhysicalDeviceBlendOperationAdvancedPropertiesEXT, VkPhysicalDeviceConservativeRasterizationPropertiesEXT, VkPhysicalDeviceCooperativeMatrixPropertiesNV, VkPhysicalDeviceCustomBorderColorPropertiesEXT, VkPhysicalDeviceDepthStencilResolveProperties, VkPhysicalDeviceDescriptorIndexingProperties, VkPhysicalDeviceDeviceGeneratedCommandsPropertiesNV, VkPhysicalDeviceDiscardRectanglePropertiesEXT, VkPhysicalDeviceDriverProperties, VkPhysicalDeviceDrmPropertiesEXT, VkPhysicalDeviceExternalMemoryHostPropertiesEXT, VkPhysicalDeviceFloatControlsProperties, VkPhysicalDeviceFragmentDensityMap2PropertiesEXT, VkPhysicalDeviceFragmentDensityMapOffsetPropertiesQCOM, VkPhysicalDeviceFragmentDensityMapPropertiesEXT, VkPhysicalDeviceFragmentShadingRateEnumsPropertiesNV, VkPhysicalDeviceFragmentShadingRatePropertiesKHR, VkPhysicalDeviceIDProperties, VkPhysicalDeviceInlineUniformBlockProperties, VkPhysicalDeviceLineRasterizationPropertiesEXT, VkPhysicalDeviceMaintenance3Properties, VkPhysicalDeviceMaintenance4Properties, VkPhysicalDeviceMeshShaderPropertiesNV, VkPhysicalDeviceMultiDrawPropertiesEXT, VkPhysicalDeviceMultiviewPerViewAttributesPropertiesNVX, VkPhysicalDeviceMultiviewProperties, VkPhysicalDevicePCIBusInfoPropertiesEXT, VkPhysicalDevicePerformanceQueryPropertiesKHR, VkPhysicalDevicePointClippingProperties, VkPhysicalDevicePortabilitySubsetPropertiesKHR, VkPhysicalDeviceProtectedMemoryProperties, VkPhysicalDeviceProvokingVertexPropertiesEXT, VkPhysicalDevicePushDescriptorPropertiesKHR, VkPhysicalDeviceRayTracingPipelinePropertiesKHR, VkPhysicalDeviceRayTracingPropertiesNV, VkPhysicalDeviceRobustness2PropertiesEXT, VkPhysicalDeviceSampleLocationsPropertiesEXT, VkPhysicalDeviceSamplerFilterMinmaxProperties, VkPhysicalDeviceShaderCoreProperties2AMD, VkPhysicalDeviceShaderCorePropertiesAMD, VkPhysicalDeviceShaderIntegerDotProductProperties, VkPhysicalDeviceShaderSMBuiltinsPropertiesNV, VkPhysicalDeviceShadingRateImagePropertiesNV, VkPhysicalDeviceSubgroupProperties, VkPhysicalDeviceSubgroupSizeControlProperties, VkPhysicalDeviceSubpassShadingPropertiesHUAWEI, VkPhysicalDeviceTexelBufferAlignmentProperties, VkPhysicalDeviceTimelineSemaphoreProperties, VkPhysicalDeviceTransformFeedbackPropertiesEXT, VkPhysicalDeviceVertexAttributeDivisorPropertiesEXT, VkPhysicalDeviceVulkan11Properties, VkPhysicalDeviceVulkan12Properties, or VkPhysicalDeviceVulkan13Properties (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkPhysicalDeviceProperties2-pNext-pNext)
    Objects: 1
        [0] 0, type: 3, name: NULL

Looking up the unknown types, apparently vulkano is passing in the following:
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SHADER_MODULE_IDENTIFIER_PROPERTIES_EXT
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTENDED_DYNAMIC_STATE_3_PROPERTIES_EXT
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_GRAPHICS_PIPELINE_LIBRARY_PROPERTIES_EXT
VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_EXTENDED_DYNAMIC_STATE_3_PROPERTIES_EXT

After some debugging, it looks like the issue is somewhere in the autogenerated PropertiesFfi default implementation, which has these extensions enabled even though they are not necessarily available on every machine.  However, this does not seem to break vulkano on my machine.

Adding the LunarG repository to apt then updating fixed the issue.  Just note that this doesn't work with the latest Ubuntu release by default.  Perhaps the docs should be modified to note that the latest LunarG SDK is needed for debugging?

repo: vulkano-rs/vulkano


text:
Remove incorrect assertions

Fixes: https://github.com/vulkano-rs/vulkano/issues/758 and https://github.com/vulkano-rs/vulkano/issues/907
I could be completely misunderstanding this but it looks like these assertions are incorrect?
Given the name of the function increase_gpu_lock and the lock state is a usize, it looks like this is a non exclusive lock, so this should be fine.

I think the assertions are correct.
See this comment: https://github.com/rukai/vulkano/blob/f10175e2127317adb2aa4871df0fb2605501e0c3/vulkano/src/buffer/cpu_access.rs#L90
If the number of accesses was 0, then we should have jumped to Exclusive. If we didn't, then there's a bug in vulkano.

But thanks for checking!

Thanks for the feedback! I'll keep investigating.

I think you might be getting Exclusive and NonExclusive mixed up? The comment says that "Number of non-exclusive GPU accesses. Can be 0." Also I dont see anything like this in cpu_pool.

I mentioned this issue on irc and someone said that maybe increase_gpu_lock() is only intended to be called on already-locked CurrentGpuAccesses? Is that the case?

source: gharchive/pull-request

authors: rukai tomaka

license_type: permissive

license_source: github-api


text:
[BUG] If no Fast Vault do not present biometric fastsign

Describe the bug
When having a secure vault the option to enable biometric fastsign is possible.
Expected behavior
Implement a logic if secure vault to not present Biometric fastsign option in settings

Version 1.4.1

QA done.

source: gharchive/issue

repo: vultisig/vultisig-ios


text:
feat: reset history

Contents (#10)
Other

reset history

Uncategorised!

Fix tests and types

Pull Request Test Coverage Report for Build 9460056926
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8030172432:
0.0%

Covered Lines:
61

Relevant Lines:
61

💛  - Coveralls

Pull Request Test Coverage Report for Build 9460056786
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 8030172432:
0.0%

Covered Lines:
61

Relevant Lines:
61

💛  - Coveralls

authors: coveralls vvscode

repo: vvscode/object-chronicler

license: MIT


text:
Error while Compiling

Hello,
I am trying to get sketch working on Artix Linux (Arch Linux without systemd) with sbcl 2.1.1-1. I am having an issue while loading sketch with quicklisp. Here is what the error looks like:
compile-file-error while compiling
   #<cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2">
   [Condition of type uiop/lisp-build:compile-file-error]

Restarts:
 0: [retry] Retry compiling #<cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2">.
 1: [accept] Continue, treating compiling #<cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2"> as having been successful.
 2: [retry] Retry ASDF operation.
 3: [clear-configuration-and-retry] Retry ASDF operation after resetting the configuration.
 4: [retry] Retry ASDF operation.
 5: [clear-configuration-and-retry] Retry ASDF operation after resetting the configuration.
 --more--

Backtrace:
  0: (uiop/lisp-build:check-lisp-compile-results nil t t "~/asdf-action::format-action/" ((#<asdf/lisp-action:compile-op > . #<asdf/lisp-action:cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2">)))
  1: ((sb-pcl::emf asdf/action:perform) #<unused argument> #<unused argument> #<asdf/lisp-action:compile-op > #<asdf/lisp-action:cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2">)
  2: ((lambda nil :in asdf/action:call-while-visiting-action))
  3: ((:method asdf/action:perform-with-restarts :around (t t)) #<asdf/lisp-action:compile-op > #<asdf/lisp-action:cl-source-file "cl-opengl" "gl" "funcs-gl-glcore-gles2">) [fast-method]
  4: ((:method asdf/plan:perform-plan (t)) #<asdf/plan:sequential-plan {10147ADC63}>) [fast-method]
  5: ((flet sb-c::with-it :in sb-c::%with-compilation-unit))
  6: ((:method asdf/plan:perform-plan :around (t)) #<asdf/plan:sequential-plan {10147ADC63}>) [fast-method]
  7: ((:method asdf/operate:operate (asdf/operation:operation asdf/component:component)) #<asdf/lisp-action:load-op > #<asdf/system:system "sketch"> :plan-class nil :plan-options nil) [fast-method]
  8: ((sb-pcl::emf asdf/operate:operate) #<unused argument> #<unused argument> #<asdf/lisp-action:load-op > #<asdf/system:system "sketch"> :verbose nil)
  9: ((lambda nil :in asdf/operate:operate))
 10: ((:method asdf/operate:operate :around (t t)) #<asdf/lisp-action:load-op > #<asdf/system:system "sketch"> :verbose nil) [fast-method]
 11: ((sb-pcl::emf asdf/operate:operate) #<unused argument> #<unused argument> asdf/lisp-action:load-op "sketch" :verbose nil)
 12: ((lambda nil :in asdf/operate:operate))
 13: ((:method asdf/operate:operate :around (t t)) asdf/lisp-action:load-op "sketch" :verbose nil) [fast-method]
 14: (asdf/session:call-with-asdf-session #<function (lambda nil :in asdf/operate:operate) {10147A8F7B}> :override t :key nil :override-cache t :override-forcing nil)
 15: ((lambda nil :in asdf/operate:operate))
 16: (asdf/session:call-with-asdf-session #<function (lambda nil :in asdf/operate:operate) {101479DF6B}> :override nil :key nil :override-cache nil :override-forcing nil)
 17: ((:method asdf/operate:operate :around (t t)) asdf/lisp-action:load-op "sketch" :verbose nil) [fast-method]
 18: (asdf/operate:load-system "sketch" :verbose nil)
 19: (quicklisp-client::call-with-macroexpand-progress #<function (lambda nil :in quicklisp-client::apply-load-strategy) {101479DD3B}>)
 --more--

I think I have all of the dependencies installed needed (I went through 1-by-1 to make sure i have them installed). Is my problem a dependency problem?
Thank you for any help you are able to offer!

I figured out the issue with this: Make sure to use a clean lisp when loading the sketch package. I autoload many packages when starting up SBCL, but this caused this error it seems. I hope this helps someone!

repo: vydd/sketch

license: mit

license_source: bigquery


text:
use "cargo check" for rust projects

As "cargo check" has now made it to the stable line:
https://blog.rust-lang.org/2017/03/16/Rust-1.16.html
it would be nice to use that as the default linter. It would also be nice to check examples when in an example folder, i.e. by reading the cargo meta information (e.g. cargo check --example current_example, where the path can be extracted from the json output given by "cargo metadata").
What do you think?

That sounds like a good option for Rust users. If someone is familiar with Rust and wants to give this a go, create a pull request. It might be worth modifying the existing linter which runs carbo build and falling back on cargo build for any users who are stuck on older Rust versions.

The above has been supported since the last version of ALE.


text:
Add cmakelint support for cmake filetype

Add support for cmake filetype using cmakelint linter.

Cheers! :beers:

Awesome, thanks @w0rp. I'll be adding support for SPIR-V in the near future too.


text:
Encoding problem (MSSQL)

I tried using node-odbc to connect to our Microsoft SQL Server 2005,
After running a query i get this warning for each row:
EIO_Query => [FreeTDS][SQL Server]Some character(s) could not be converted into client's character set.  Unconverted bytes were changed to question marks ('?')
I wouldn't bother about the warnings but also all the local characters are replaced for � in result data.
My FreeTDS is configured properly with client charset set as UTF-8.
I've got no issues connecting to our mssql server with freetds under my ruby and python apps.
Am I doing something wrong or is it a bug ?
Matej Drzik

FYI: there are bug reports at Ubuntu and Debian to get a newer FreeTDS package.
https://bugs.launchpad.net/ubuntu/+source/freetds/+bug/887374
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642069

authors: wankdanker wirrareka


text:
Error: Unable to decode using the supplied passphrase Polkadot.js wallet

Hi, I wanted to make a transfer using my polkadot Wallet - but It just wont accept my password. And I am pretty sure its the right one. So I recovered everything with JSON File.. and seed words several times.. in order to change my password. But it still doesnt accept my password when doing a transaction. I updated the metadata also. I keep on getting this error in the browser extention: Unable to decode using the supplied passphrase.
Can someone help me? Thx!

Have you stored the password w/o a line break? e.g. echo -n "mySupersecretPassword" > password

I managed to solve it.. had this issue a month ago...
Best
Nathalie
Am Fr., 3. Dez. 2021 um 14:41 Uhr schrieb Philipp D. <
@.***>:

Have you stored the password w/o a line break? e.g. echo -n
"mySupersecretPassword" > password
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/w3f/polkadot-payouts/issues/46#issuecomment-985529931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVA5PGNDROI7SZ7Z6ERRSUDUPDCHVANCNFSM5GNTDTQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


text:
Dialog component's message does not have rounded corners at the top

Issue Summary
When using the dialog component with a message, the dialog's top side does not have rounded corners:

This was a regression in 55d04366f7dd57141de9ec9282d8978b3ccbd7cc when overflow: hidden; was added to .w-dialog__box in the base dialog styles.
I'm assuming that the overflow: hidden; was only removed so that we can display the close button at an offset in the userbar's accessibility checker, and not necessarily required for the generic floating version of the dialog:

Screenshot

In fact, the generic floating dialog uses the same close button styles as the other ones, so this means the overflow: hidden; was only necessary for the accessibility checker's dialog:

Screenshot

Steps to Reproduce

Spin up bakerydemo
Open Settings > Styleguide
Try the "Dialog with success/warning/error" variants of the Dialog component
See that the top side of the dialog has no rounded corners

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
The top side should be rounded like the bottom, which was how it has been before Wagtail 4.2.
Suggested fix
Reintroduce overflow: hidden; to the .w-dialog__box styles in _dialog.scss like how we had it before, and add .w-dialog__box { overflow: visible; } to the userbar's dialog override in _userbar.scss.
Alternatively, add border-top-*-radius to .w-dialog__message with the same value as the one set in .w-dialog__box.

Can I be assigned with this issue

Thanks for your interest @TheLazron! You are welcome to work on this. We do not assign issues outside of the core team - we just ask that people indicate their intention to work on an issue (as you have now done), to avoid duplicating efforts.
For further help in getting started, please see https://dev.to/lb/ten-tasty-ingredients-for-a-delicious-pull-request-hgc - you may also wish to join our #new-contributors channel on Slack.

Hey, can I try to fix this bug?

Hey @gasman , I would like to work on this issue!

@soumik-saha and @Hussain0520, please give @TheLazron some time to attempt the issue (at least a week) before asking if you can pick it up.

Sure!

Okay!

Hey @gasman can i try to fix this issue

Hii @gasman I want to work on this issue

Thanks for your interest all, as you can see above, 5 people have already expressed an interest in working on this and there is already a PR up from a 6th person. So it's likely that you would be duplicating those existing efforts. Nevertheless, if you're OK with this, you can proceed.
@sagarsangwan @sivangbagri
Additionally - please read our guide to your first contribution as it covers many of the basics for how to get involved before reaching for issues. https://github.com/wagtail/wagtail/issues/10070
I'll remove the good first issue label for now to avoid additional interest.

authors: Hussain0520 Scotchester TheLazron gasman laymonage lb- sagarsangwan sivangbagri soumik-saha

repo: wagtail/wagtail


text:
🐛 Twitter readme update

Is your proposal related to a problem?
The README file currently contains outdated references to Twitter, which has been rebranded to X. This may confuse users and doesn't reflect the current branding of the platform.
Describe the solution you'd like
Update all references to Twitter in the README file and any other relevant documentation to reflect the rebranding to X. Specifically:
Change the Twitter link from "https://twitter.com/WagtailCMS" to "https://x.com/WagtailCMS"
Update the alt text from "follow on Twitter" to "follow on X"
Update any mentions of "Twitter" in the text to "X"
If possible, update the image source to use X's current branding instead of Twitter's
Describe alternatives you've considered
Keeping the current Twitter branding, but this would be inaccurate and potentially confusing for users.
Removing the social media link entirely, but this would reduce visibility and engagement opportunities for the project.
Additional context
This change is part of a larger effort to keep the project's documentation and branding up-to-date with current social media platforms. It may be worth reviewing all documentation and templates to ensure consistency across the project.
Working on this
This task requires basic HTML knowledge and familiarity with the project's documentation structure. It's a good opportunity for newcomers to contribute to the project. The main skills needed are attention to detail and basic Git/GitHub knowledge for submitting the changes.
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you're ready to start.

I'm working on it 😀


text:
Remove sticky footer on small devices

The default layout is the mobile one and “up from mobile” gets the overlap added.
Result:

Fixes #4641

@saeed617 thanks for submitting this, along with screenshots also!
@thibaudcolas - I tested this locally, works as expected with the footer now at the bottom, will leave you to review in full.
My only thoughts are that the user might need to scroll a fair bit on a long page to get to the save button. I also agree that it can be a bit full on having the entire footer showing at all times.
Ideas for refinement

keep the action buttons 'sticky' but put the last modified/revisions text at the bottom
maybe try to fit two buttons in on mobile side by side, I think this is doable but that is assuming an english translation with the words being small and keep them sticky
harder to do - make the actions on mobile ONE dropdown (drop up on mobile)  and keep them sticky

What about this style? I think in this way it's not on screen all the times and you don't need to scroll down the page to reach buttons and with a simple scroll up you have them.  I saw this in many places and users are already familiar with it.

@saeed617 - I personally am not a fan of that style of footer (or header) as it is prone to issues and a sense of fiddly-ness. I thought maybe something akin to the wagtail user bar (smaller button, always there (sticky) but clicking it opens up a menu with options.
This means two clicks to save though, and also resorts to icons to represent things instead of text.
I probably would defer to some of the other Wagtail team for ideas though.
@wagtail/ux-design ?

@saeed617 thanks again for your work on this, we discussed this at the core meeting and agreed that your initial solution is a good way forward.
We can add improvements as we go in the future, one idea was to add a 'go to bottom' type link that floats on mobile view.
I will take another look at this soon and do another review.

Merged in via 44c1f1cab2bdbc4bec95d62a876bd87e279d7ac3


text:
Add documentation for WAGTAIL_REDIRECTS_FILE_STORAGE setting

This is a continuation of #5949 where I've added documentation for the WAGTAIL_REDIRECTS_FILE_STORAGE setting.

Thanks @marteinn! Merged in c8f493c09598d1d93e30120e076d43f4a6cb1311.

authors: gasman marteinn


text:
*.cls extension as SalesForce Apex

What problem does this feature solve?
Add support for SFDX/SalesForce development in Apex.
Please check the Chroma README and command-line tool to ensure this isn't an already solved problem.
What feature do you propose?
*.cls should be tracked as Apex, SalesForce Apex, or something similar

Hmmm, even though I don't see the support in here, the dashboard seems to show apex, so this might be done elsewhere.
If so, feel free to close this!

repo: wakatime/chroma


text:
Implement EIP1193 Provider Methods

Implement request and on per EIP1193 spec.
@petejkim one change I made here is to use es2016 so we can import the safe-emitter library.  Thoughts on whether this is ok to do?

One problem that I see here is that by implementing these methods, it might make it seem that it supports subscriptions .on("message") but it doesn't. That breaks certain apps.
This commit essentially reverts this commit:
https://github.com/walletlink/walletlink/commit/f7a62fb366b1ca7374c80bf68f3924bbfa48d997#diff-6a46db475c5a2259fb4fdda1453652bd0d687a775d9fa3a943f9f7cdda34f030
Which was removed because it was breaking feature detection.
To implement this correctly, all event emission must be implemented as well, or else there will be other side effects.

PR https://github.com/walletlink/walletlink/pull/64 to add support for subscriptions

authors: alexshoykhet petejkim vishnumad

repo: walletlink/walletlink


text:
extends requires target to be JSON/JS

After the 5.0 YAML change, things are broke.  More specifically, when specifying extends: "eslint-config-defaults/configurations/walmart/es6-node.yaml", ESlint will always treat the target as a JS module (see here and here.  This worked with JSON because require("path/to/json/file.json") works in Node.
This seems a limitation in ESlint itself, and should be fixed there.  But adding this here for now while I'm thinking of it.
Short term solution would be to revert to JSON, or to instruct users to stick to 4.x.x package versions until things are worked out.

Oooof confirmed - this is true. However, oddly I was able to run a global ESLint that pointed to the YAML in this directory and it did work. I am reverting, deprecating and revving since it seems like the bast plan until ESLint is sorted out.

Closed in #33

Still not fixed?

authors: baer divmain hax

repo: walmartlabs/eslint-config-defaults


text:
[chore] fix linter errors and warnings

Related to https://github.com/walnuthq/cairovm.codes/issues/12
To ease this process, I've added a new npm script lint:fix which calls the linter with the --fix option (using npm run lint --fix does not work because the --fix option must be before the path .).
I also removed unused code in comments as these portions of code were direclty linked to the linter warnings (useless imports, useless variables and so on).
The dynamic fee documentation part in the DocRow component was not used but as it was quite big, I removed it in a dedicated commit. If it has to be kept for a future implementation, I can comment all of this to avoid having linter errors/warnings on it.

lgtm!
@barabanovro can you take a second look as well

authors: mazurroman remybar


text:
Feat/certificate chain validation

Description

adds trust-ca.conf configuration
adds x5c-feature, disabled by default
refactors AuthController

moves endpoints to separate entities (e.g. keycloak auth, oidc auth)
activates oidc auth routes when oidc feature is enabled

adds x5c auth controller
activates x5c auth routes when x5c feature is enabled
adds X5CAccountStrategy to handle login and registration
adds X5CLogins table for binding key thumbprint to the account-id
adds X5CValidator for trust chain validation (certificate date and issuer) - wip
adds X5CValidatorTest - wip

Still in progress:

trust validation - X5CValidator currently only validates the date
X5CValidatorTest - once the implementation is ready
general checks:

thumbprint - account-id bindings
login / registration happy flows, edge cases

general cleanup

Questionable approaches:

should the trust-ca.conf store a list of pem's, rather than der's?
is this going to work always?

Fixes #677
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[ ] I have performed a self-review of my code
[ ] If it is a core feature, I have added thorough tests
[ ] Do we need to implement analytics?
[ ] Will this be part of a product update? If yes, please write one phrase about this update.
[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Note to myself:

Check if all is well regarding x5c-related wallet routes.
Tests for login & registration flows to make sure everything works as intended.

authors: cpatsonakis mikeplotean

repo: walt-id/waltid-identity


text:
大佬怎么不更新了，用了几个编辑器都没有这个好用

大佬怎么不更新了，用了几个编辑器都没有这个好用

之前丢到gitee上了，现在已经重新更新代码了

大佬，后面还维护吗


text:
设置代码块后，无法将光标定位到结尾

bug 描述
设置代码块后，如果代码块是最后面的内容，光标就无法定位在结尾
你预期的样子是？
设置代码块后，光标可以定位到代码块的后面，方便在代码块的后面添加新的内容
系统和浏览器及版本号

mac
chrome 96

wangEditor 版本
v5 0.12.8
demo 能否复现该 bug ？
能

中文 demo https://www.wangeditor.com/demo/zh-CN
English demo https://www.wangeditor.com/demo/en

最小成本的复现步骤

步骤一： 打开DEMO：https://www.wangeditor.com/demo/zh-CN/
步骤二： 输入：abc
步骤三：设置代码块

这个时候，就再也无法将光标移动到结尾

连续换行多次，即可退出。
不过这个策略目前确实有体验问题，正在考虑优化。

代码块内部我觉得应该允许连续换行。
代码块的结尾，也应该允许进行光标定位。

代码块的结尾，也应该允许进行光标定位。 —— 这是什么意思？

连续换行多次，即可退出。
不过这个策略目前确实有体验问题，正在考虑优化。

最新版本做了优化，下载安装试试


text:
插入表情后输入文字，表情与文字重叠

bug 描述

插入表情后输入文字，表情与文字重叠

你预期的样子是？

不重叠

系统和浏览器及版本号

macos 12.0.1
chrome 97.0.4692.99

wangEditor 版本

v5 官网 demo 默认模式
https://www.wangeditor.com/demo/zh-CN/

demo 能否复现该 bug ？
能

中文 demo https://www.wangeditor.com/demo/zh-CN
English demo https://www.wangeditor.com/demo/en

最小成本的复现步骤
（请告诉我们，如何最快的复现该 bug）

步骤一：打开官网 demo ：https://www.wangeditor.com/demo/zh-CN/
步骤二：用工具栏加入一个表情
步骤三：输入一个字

我也是 MacOS 12，Chrome 97 ，使用官网 demo 并没有复现。如下图：

镜像外接显示器的问题，mac 本机显示器没事


text:
列表项不能选择

版本v3
代码：
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title></title>

刚把引用的js文件换成下载的源文件试了下没有问题，应该是cdn的代码有问题

我下次发布再把cdn的代码重新更新一下。请关注新版发布动态。


text:
openvz+vmware用faketcp不通

环境：
服务器端：openvz+centos6.8_x64+kcptun
客户端：win7+openwrt12.09_x86_vmware_image_with_udp2raw_pre_installed
1.--raw-mode用faketcp不通
2.--raw-mode用udp可以通，说明整个配置是没问题的
3.用ssh服务测试的
4.-a 参数去掉也不行
5.命令是完全参照示例里写的，没有添加其它参数
6.我不确定是否和openvz有关，只是猜测

虚拟机网卡是不是桥接模式？

@wangyu-  确实是这个问题，之前是nat模式，换成桥接后好了，原来必须得桥接，谢谢！

另一个请教：后期会增加windows客户端吗？还是windows上无法实现必须得linux呢？

在windows上实现一个困难是需要改得东西比较多，维护起来麻烦。
另一个困难是windows没iptables，用什么东西替代我暂时也没有想法。
短期不会有windows原生客户端。

我这速度明显提高了很多，1080p完全没问题。
再有一个疑惑：我开启的bbr，对udp2raw-tunnel会有加速作用吗？

再有一个疑惑：我开启的bbr，对udp2raw-tunnel会有加速作用吗？

没作用。但是不冲突，可以开。

再请教，我在docker下运行，报这个错误，是不支持吗？还是哪里不对？
[2017-09-04 15:18:35][INFO]argc=10 /root/udp2raw/udp2raw_amd64 -s -l 0.0.0.0:9080 -r 127.0.0.1:443 -k dcOa145I0NoK --raw-mode faketcp
[2017-09-04 15:18:35][INFO]important variables: log_level=4:INFO raw_mode=faketcp cipher_mode=aes128cbc auth_mode=md5 key=dcOa145I0NoK local_ip=0.0.0.0 local_port=9080 remote_ip=127.0.0.1 remote_port=443 source_ip=0.0.0.0 source_port=0 socket_buf_size=1048576
[2017-09-04 15:18:35][INFO]const_id:3c1787b6
[2017-09-04 15:18:35][FATAL]SO_SNDBUFFORCE fail

你下载这个版本试一下，然后贴一下日志。
https://github.com/wangyu-/udp2raw-tunnel/files/1267468/udp2raw_amd64.zip

报错：
[2017-09-04 15:29:36][INFO]argc=10 /root/udp2raw/udp2raw_amd64 -s -l 0.0.0.0:9080 -r 127.0.0.1:443 -k dcOa145I0NoK --raw-mode faketcp
[2017-09-04 15:29:36][INFO]important variables: log_level=4:INFO raw_mode=faketcp cipher_mode=aes128cbc auth_mode=md5 key=dcOa145I0NoK local_ip=0.0.0.0 local_port=9080 remote_ip=127.0.0.1 remote_port=443 source_ip=0.0.0.0 source_port=0 socket_buf_size=1048576
[2017-09-04 15:29:36][INFO]const_id:26bdfd4a
[2017-09-04 15:29:36][FATAL]SO_SNDBUFFORCE fail  socket_buf_size=1048576  errno=Operation not permitted

这个账户是root吗？貌似你的机器不允许SO_SNDBUFFORCE这个操作。
用--sock-buf 100试一下，看是否能运行。

加了--sock-buf 100这个还是报错。docker启动没有root权限，这样不行吗？
[2017-09-04 15:35:14][INFO]argc=12 /root/udp2raw/udp2raw_amd64 -s -l 0.0.0.0:9080 -r 127.0.0.1:443 -k dcOa145I0NoK --raw-mode faketcp --sock-buf 100
[2017-09-04 15:35:14][INFO]important variables: log_level=4:INFO raw_mode=faketcp cipher_mode=aes128cbc auth_mode=md5 key=dcOa145I0NoK local_ip=0.0.0.0 local_port=9080 remote_ip=127.0.0.1 remote_port=443 source_ip=0.0.0.0 source_port=0 socket_buf_size=102400
[2017-09-04 15:35:14][INFO]const_id:abb195ae
[2017-09-04 15:35:14][FATAL]SO_SNDBUFFORCE fail  socket_buf_size=102400  errno=Operation not permitted

[2017-09-04 15:48:32][INFO][main.cpp,func:process_arg,line:2802]argc=11 /root/udp2raw/udp2raw_amd64 -s -l 0.0.0.0:9080 -r 127.0.0.1:443 -k dcOa145I0NoK --raw-mode faketcp --log-position
[2017-09-04 15:48:32][INFO][main.cpp,func:process_arg,line:3098]important variables: log_level=4:INFO raw_mode=faketcp cipher_mode=aes128cbc auth_mode=md5 key=dcOa145I0NoK local_ip=0.0.0.0 local_port=9080 remote_ip=127.0.0.1 remote_port=443 source_ip=0.0.0.0 source_port=0 socket_buf_size=1048576
[2017-09-04 15:48:32][INFO][main.cpp,func:main,line:3390]const_id:219e4ad
[2017-09-04 15:48:32][FATAL][network.cpp,func:init_raw_socket,line:204]SO_SNDBUFFORCE fail  socket_buf_size=1048576  errno=Operation not permitted

udp2raw_binaries.tar.gz

可以了，非常感谢，同时加了这个参数--seq-mode 0才稳定。

--seq-mode 0这个应该不用吧，加了这个反而会有明显的特征，容易被封掉。
你觉得这个稳定可能是运气因素造成的。
建议用--seq-mode 1或--seq-mode 2.

好的，我试试。请问1和2是什么意思？

--seq-mode 0表示关掉tcp序号的模拟。
--seq-mode 1表示模拟不丢包情况下的tcp序号。
--seq-mode 2假装有一定丢包，序号有时增长有时不涨。

我有一个nat的server，1是默认，试了很多次确实不稳定，网页一打开就断，改成0就可以了，我再试试2
我另一台非nat的服务器，没有加--seq-mode这个参数没有问题。

nat的server是说阿里云的1:1nat吗？

不是， 一个不知名的。

麻烦你把这个vps供应商的名字发到我邮箱里 wangyucn@gmail.com
哪天有时间我注册一个试试，看看是什么原因。

发你邮箱了

多谢

刚试了参数2几分钟，能打开，但感觉好像速度要慢些，不知道是否是错觉。

可以用www.speedtest.net之类的网站测速试一下。

又试了下参数1，确实不行，又断了。

又试了下参数1，确实不行，又断了。
了解了。多谢反馈。

现在的测试是：
1.一个nat server+一个docker，用0正常，用1不行，用2好像有些慢。
2.另一个普通的server，默认就正常。

我的docker的用户名和密码发你邮箱了，你先拿去测试吧，可以随意kill任何进程。

多谢，我已经连上去在测试了。

发布了一个新版。https://github.com/wangyu-/udp2raw-tunnel/releases/edit/20170906.0
预计不需要--seq-mode 0就可以正常运行。

@wangyu- 可以了，速度飞起。

@wangyu- 查看是否支持aes的命令对吗？aes的性能提升大概有多少呢？
grep -m1 -o aes /proc/cpuinfo

硬件加速版的AES有好几倍的性能提升。 具体见#15， 里面有个性能测试。
汇编加速版的也至少有50%的性能提升。
你用的是amd64的cpu是吧。你下载udp2raw_amd64_hw_aes运行一下试试，如果可以运行那就是支持了。

grep -m1 -o aes /proc/cpuinfo
这个我也不清楚。AES加速相关的代码是 @linusyang 写的，不确定是否这里显示出的AES支持就是他用的那个方法。目前最好的办法是运行一下试试，AES加速版是单独的binary，如果不支持会运行不了。

@wangyu- 试了aes版本的，可以运行，谢谢！

目前windows要开启虚拟机的方法还是稍显麻烦，有些人可能都没听说过，看到虚拟机可能就望而却步了，还是建议有更简单的直接运行的客户端。

这个已经加到 #17 的contribute guide里了。
这个需要改的东西比较多，window下的开发我自己也不熟悉，只能等别人贡献代码了。

@PHCSJC
你好，我有个问题。我上次登陆到你的docker vps上面去调试，发现 -a选项是没法添加iptables的，就算自己手动打命令运行iptables也不可以。
后来只好放弃添加iptables规则，直接运行。但是我观察到，client这端是不会收到RST包的（正常情况下只有在server端添加了iptables规则才有这样的效果）。你这个server是NAT的，我猜你大概在VPS的WEB界面上对9080配置过端口映射。现在我想问一下，你是否有通过某些办法对9080添加了udp2raw生成的iptables规则？

@wangyu- 你是否有通过某种办法对9080添加了udp2raw所需的iptables规则？没有，我只是启用了9080端口，没有其它任何配置。
这个docker没有完整的root的权限，所以使用不了iptables。

@PHCSJC 多谢，了解了。

我的路由器是斐讯k2p，刷的官改ROM，执行udp2raw时报错，是哪里操作不对吗？
root@K2P:/tmp# ./udp2raw_mips34kc -h
./udp2raw_mips34kc: line 1: syntax error: unexpected "("

./udp2raw_mips34kc: line 1: syntax error: unexpected "("

binary选择的不对。查一下cpu架构。如果没有合适的就自己编译，参考readme里面的编译教程。

mt7621是mips架构的，用udp2raw_mips34kc应该没有错吧？再就是不会编译喔。

貌似你这个路由器的CPU运行在'little endian'模式，我编译的那个是'big endian'的。
编译教程： https://github.com/wangyu-/udp2raw-tunnel/blob/master/doc/build_guide.zh-cn.md

好吧，这个对于我来说难道太大，我还是等高人适配吧。

@PHCSJC
我新发布了一版release.增加了'little endian'的mips binary.
https://github.com/wangyu-/udp2raw-tunnel/releases
文件名：udp2raw_mips24kc_be和udp2raw_mips24kc_be_asm_aes.
不保证可以用，我手上没有可测试的环境。

@wangyu-
k2p上测试的udp2raw_mips24kc_le_asm_aes，没有问题，给你点个赞！

多谢反馈。

udp2raw_mips24kc_be和udp2raw_mips24kc_be_asm_aes.

是udp2raw_mips24kc_le和udp2raw_mips24kc_le_asm_aes。
前面的写错了。

看1080p视频，CPU 9%-15%，这个负载完全可以正常使用。

小米路由器mini(mt7620)：默认参数，看1080p视频，CPU 40%-60%。单个用户没问题。

小米路由器mini（mt7620）：udp2raw_mips24kc_le_asm_aes，默认参数，看1080p视频，CPU 40%-60%。单个用户没问题。

多谢反馈。
另外，看1080p视频这样测试出来的结果可能不是最准确的。因为YouTube不会尝试一直打满你的带宽，有时候Youtube在缓冲，有时候Youtube是空闲的，测出来结果可能会偏低。
测性能可以在server 用 iperf3 -s ，在client用 iperf3 -c <server_ip>  -P30 -t100和iperf3 -c <server_ip>  -P30 -R -t100，这样iperf3会尝试打满你的带宽。

我只是用来看看视频、搜索。速度我观察了下

下载大文件观察也可以，我觉得比开Youtube观察准确。

iperf3不会用喔，抱歉。

没事，我只是顺便说下YouTube测CPU这个方法可能不是很可靠。

下载了个大文件试了下，50M带宽打满，小米路由器mini上cpu占用率40%-50%

昨天晚上server进程崩溃了，看发布了新版本20170911.0，是解决的这个问题吗？

昨天晚上server进程崩溃了

崩溃是指程序自己退出了吗？具体现象是什么。

看发布了新版本20170911.0，是解决的这个问题吗？

昨天修的那个bug会导致性能问题，极端情况下会导致server连不上，但是不会退出。过几分钟后等有问题的连接被回收掉之后server会自己活过来。

昨天晚上server进程崩溃了
我这边最近一个月都没观察到崩溃，server是vultr日本512mb内存。

建议运行一下ulimit -c unlimited，这样程序崩溃后会在当前目录产生一个core文件。把这个文件传给我，可以用它找到崩溃的原因。

kcptun，ssr都还在，就udp2raw进程没了。
今天刚更新的0911版本，目前未出现崩溃。
运行了ulimit -c unlimited，再观察看看。

在这个问题查明之前，可以用这个脚本：
# /bin/sh
while true
do
xxxxxxxxxxxxxxxxxxxxxx//运行udp2raw
sleep 10
done

这样在udp2raw退出后会自动重新运行。

好的，谢谢

@wangyu-

另一个困难是windows没iptables，用什么东西替代我暂时也没有想法。

可借鉴 finalSpeed的方法：
https://github.com/Chion82/kcptun-raw/issues/2#issue-203957142

@linhua55
好方法，收藏了。

期待早日出win版本

好像在更新0911版本后，打开网页的速度慢了。

好像在更新0911版本后，打开网页的速度慢了。

我用iperf3测了一下，结果跟之前是一样的。可能是网络本身的问题，再观察观察吧。

好的，再观察看看。

又测了一下，发现如果在看视频的同时去看别的走udp2raw的网站，延时会大，估计有0.5-2秒吧，而用kcptun+ss就不会有这么明显。

实际上建立的不是udp连接，是raw socket的连接，因为使用了信道复用(multiplex)的方法，下层连接只有一条，而且目前只能是一条。
刚看到这个，和这个是否有些关系呢？

又测了一下，发现如果在看视频的同时去看别的走udp2raw的网站，延时会大，估计有0.5-2秒吧，而用kcptun+ss就不会有这么明显。

有延迟变大本身是正常的。至于为什么更明显，这个测试过于笼统，具体原因我也无法确定。可能你额外套上udp2raw后CPU占用变高了；也可能是你用了udp2raw后视频的下载速度变快了，挤占了打开网页的带宽；也许像好像在更新0911版本后，打开网页的速度慢了一样，是网络环境本身波动造成的。

实际上建立的不是udp连接，是raw socket的连接，因为使用了信道复用(multiplex)的方法，下层连接只有一条，而且目前只能是一条。
刚看到这个，和这个是否有些关系呢？

应该不是，如果你的kcptun没特意改过相关参数的话，底层的连接也是只有一条。

authors: PHCSJC linhua55 wangyu-


text:
Intents: Ethereum "to" allowlist

Track the progress of making it possible for a user to define an allowlist of addresses that can receive tokens or be called (in the case of smart contract addresses). This is the "to" field in an Ethereum transaction.

[x] #306
[x] #307

One these are done, users will be able to write intents such as:
contains(warden.analyzer.xxx.to, ["0x123", "0x456"])

(where xxx is the address of the Ethereum analyzer)

Everything here has been done, the Ethereum analyzer can be used to track the "to" value and the shield language supports string operators and the contains() built-in

repo: warden-protocol/wardenprotocol


text:
Unit tests should be runnable

This package should be able to run unit tests in Travis/CircleCI/whatever for a full integration test suite, but also ideally have some subset available locally if the config isn't available (i.e. for external contributors)

Fixed in #20 @msluther

authors: jcrugzz msluther

repo: warehouseai/cdnup


text:
请问indicator在最左侧或最右侧能否不被挤压, 显示在seekbar范围之外, 左右预留出一些空间?

int indicatorOffset;
int arrowOffset;
if (measuredWidth / 2 + thumbCenterX > mMeasuredWidth) {
indicatorOffset = mMeasuredWidth - measuredWidth;
arrowOffset = (int) (thumbCenterX - indicatorOffset - measuredWidth / 2);
} else if (thumbCenterX - measuredWidth / 2 < 0) {
indicatorOffset = 0;
arrowOffset = -(int) (measuredWidth / 2 - thumbCenterX);
} else {
indicatorOffset = (int) (thumbCenterX - measuredWidth / 2);
arrowOffset = 0;
}

抱歉，不支持这个的。

authors: supremelife warkiz

repo: warkiz/IndicatorSeekBar


text:
introduces bind-host

Introduces bind-host to mount image snapshot base directory automatically.

Yes. I've fixed it in https://github.com/warm-metal/csi-driver-image/pull/9

repo: warm-metal/csi-driver-image


text:
[FEATURE 💡] Remove Nike from header in mobile devices

Description

Remove the nike text from the logo (Only for mobile devices)
Make the navbar a bit shorter for (Only for mobile devices)
The logo and icons must also be made smaller
The theme icon seems not aligned properly
Take reference from the original site webpage screenshots given below

Screenshots

Reference

Additional information
Make sure to read the CONTRIBUTING and SETUP docs before proceeding
Happy contributing. 💐
Star my other Repositories here

Hey @warmachine028.
I'm eager to contribute to this project. This open issue aligns with my skills and interests. If it's possible, could you kindly consider assigning this task to me? I would be grateful for the opportunity to contribute to the project. Thank you.

Okay! @sahilrw I have assigned you to this issue

Make sure to consult if any confusion arises before making a Pull Request.
I might not be available instantly, but I will address your confusion
Make sure to complete all the tasks in the Description above
Take reference from other closed PR to fill the Pull Request template
The title of your PR must be same as this issue

Thank you.

@sahilrw, please start working on this issue soon

I am having trouble removing the text from the logo. Any suggestions as to how I can do that?
Everything else is completed.

I believe the text and logo are 1 single segment, what if we display only the logo, the logo is available at this path

Yes. That is doable. Will get it done asap.

Would Like to take up this issue if not been closed yet

Yes the issue is open

would like to contribute if its still open

Someone is already assigned, please find some other ways to contribute to the project. If he's unable to solve this issue you will be assigned soon.

Hey @mehulrnsit could you please check if the Merged PR is showing in your hacktoberfest profile in Progress or not?
Example:


text:
fix: add Warp component-classes to the breadcrumbs component

Description

update the breadcrumbs component to use component-classes
color tokens work
handle nested arrays of children like in React and Vue

Additionally

render string-typed children as styled span elements with aria-current="page" on last child

 Warpify Breadcrumbs component

repo: warp-ds/elements


text:
Implement support for WasmEdge

WasmCloud could support multiple alternative wasm runtimes to take advantage of the unique features and performance characteristics of each.
I would like to propose that WasmCloud add support for the WasmEdge Runtime through WasmEdge's Rust SDK.
https://github.com/WasmEdge/WasmEdge/tree/master/bindings/rust
If there is anything we could do to help. Please let me know. Thanks.

Hey @juntao, it's been a little while! With the effort that @tessi recently just put into refactoring from wasmer to wasmtime, I think implementing wasmedge as well would really require the largest effort in writing the custom NIF. Are you aware of any efforts here? I just don't want this issue to go too stale 🙂

Hey! sorry @juanto
Wasm and with it all the different wasm engines is just moving to fast for me to maintain multiple engines. I just can't do that besides family and day job. If you or someone wants to give it a try, I'd be happy to give you an intro into the problem space and wasmex code base :)

Hey! sorry @juanto
Wasm and with it all the different wasm engines is just moving to fast for me to maintain multiple engines. I just can't do that besides family and day job. If you or someone wants to give it a try, I'd be happy to give you an intro into the problem space and wasmex code base :)

You've been putting in amazing effort. I don't think anybody would expect you to support swapping in and out of "all the engines"

No worries! Let me try to give a status update.
We have recently worked with several companies and projects to support WasmEdge together with wasmtime. The process is typically to replace wasmtime's GO or Rust SDKs with WasmEdge's. Those APIs are fairly similar. We have done it many times -- we are actually thinking about creating an abstract API on top of those SDKs to support easy switching. ;)
The typical reasons to support both runtimes are:
1 Supply chain security -- since wasmtime and WasmEdge are based on completely different tech stacks (Rust + Cranelift vs C++ + LLVM), they are unlikely to be affected by the same bugs.
2 Additional features provided by WasmEdge such as web service, database, AI inference, Kubernetes / Docker and JavaScript support.
Of course, I understand different projects have different priorities. I am not that familiar with the Erlang / Elixir ecosystem but would love learn more to understand how we can better support it! 🙏🙏🙏

😊 thanks everyone! didn't mean this to be hunting for compliments 🙈

we are actually thinking about creating an abstract API on top of those SDKs to support easy switching

sounds very interesting especially if it's not a vendor lock-in and well maintained and on-par with wasmtime!
I probably continue the port to wasmtime first and investigate further steps from there.

I [...] would love learn more to understand how we can better support it!

Is there anything specific you'd like to know? Feel free to reach out on twitter or @tessi on the elixir slack for wasmex-specifics and a more real time'ish chat and to not sidetrack this issue any further :)

We've done a whole lot of reorganization around how we're running Wasm engines, and I think for now we're going to proceed with support for wasmtime as the engine under wasmCloud. As soon as we get to rethinking pluggable / replaceable engines, I'd love to consider putting wasmedge as one of those engines

authors: autodidaddict brooksmtownsend juntao tessi

repo: wasmCloud/wasmCloud


text:
[decompiler] process-drawable-h

Also add some more offline tests and hopefully fix decompiler crashing.

Pull Request Test Coverage Report for Build 910742157

11 of 15 (73.33%)  changed or added relevant lines in 5 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.004%) to 69.504%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

decompiler/ObjectFile/ObjectFileDB_IR2.cpp
0
4
0.0%

Files with Coverage Reduction
New Missed Lines
%

game/overlord/iso.cpp
1
77.86%

decompiler/IR2/AtomicOpForm.cpp
2
67.94%

Totals

Change from base Build 910491429:
0.004%

Covered Lines:
36177

Relevant Lines:
52050

💛  - Coveralls

license: ISC


text:
can't be too strict with Browser#html spec

Since different browsers will return different page sources for the same page, this spec should be less strict.

I think this is mostly handled.

repo: watir/watirspec


text:
Project updates

This PR makes some basic updates to the project to prepare for the v1.0 release:

Add doc files to project and update Contributing
Delete car_workspace.json as it is now out of date
Update test credentials and fix tests where needed

All tests passed except for Visual Recognition -- which we know are problematic -- so I'm going to merge this.

repo: watson-developer-cloud/swift-sdk


text:
Custom awb_gains not working

I am trying to set custom gains and created the following script based on the picamera documentation
`from time import sleep
from picamera import PiCamera
from fractions import Fraction
camera = PiCamera(resolution=(1280, 720), framerate=30)
camera.iso = 100
sleep(2)
camera.shutter_speed = camera.exposure_speed
camera.exposure_mode = 'off'
g = camera.awb_gains
camera.awb_mode = 'off'
camera.awb_gains = (2.5, 2.5)
camera.capture('try.jpg')
print(camera.awb_gains)`
But whatever I put as camera.awb_gains, also with Fractions, the values returned are always very similar fractions in the range (Fraction(167, 128), Fraction(257, 128)). The images returned also always have a nice white balance and not the overly red or blue that I would expect with the provided awb_gains.
I am testing this on a rpi 3B+
Originally posted by @JolleJolles in https://github.com/waveform80/picamera/issues/318#issuecomment-516861931

I could fix it by adding sleep(0.1) after setting the awb_gains


text:
Configuration

Implement gem configuration and defaults.

I think this covers configuration. I also hard-coded the service endpoints as constants. Take a look; give feedback!

 Configuration

repo: wavetronix/adobe-dps-sdk-ruby


text:
Integrating SWEET parser

Google Summer of Code Final Submission

Student name: Himadri Bhattacharjee
Devlogs: https://lavafroth.is-a.dev/tags/google-summer-of-code

Overview

Keysym and modifier structs are replaced with respective structs from the crates
evdev keys are automatically parsed in a single pass of the parser
Commands

Command chunks inside shorthands must be escaped as and when needed. For example {a-program, b-program} is invalid since the dash will be considered a range. The only correct syntax is  {a\-program, b\-program} when using shorthands with commands.
Commands sprinked with &&-mode instructions extract the instructions as an attribute of the Definition struct during parsing

Removed manual implementation of logical errors (handled by new parser) grammar errors (handled by pest.rs)
Added small match block to translate sweet::token::Modifier variants to local Modifier variants
Unified shorthand syntax: there's at most one way to do shorthands correct

A shorthand must contain at least two variants. One should not use shorthands otherwise
Any literal like a comma or a curly brace inside a shorthand must be escaped
Literals do not need to be escaped outside shorthand contexts.
Shorthands with omissions (underscore elements) must always have a concatenator appended to each non-empty element. For example, unlike {control, super} + a, in {_, super + } a adding a plus to super inside the shorthand is the only valid syntax. This can be compared to expansions in bash

There's a 50 MiB filesize cap for the config file as a precaution against accidental actions on the user end. This filesize cap can be changed by passing an environment variable or modifying the build.rs.
The parser only accepts regular files so that the user does accidentally feed in block devices like their entire drives
All of the tests for the daemon are ported to use the grammar and are moved to the grammar crate. See tests/tests.rs

Some tests are stricter than the previous iteration due to the strict nature of the EBNF grammar itself. For example: commented out binding definitions with dangling commands are no longer valid
Temporary files for tests are handled using the temporary file architecture for the respective platform

Minor issue, we need the sweet stuff in tree. After that this pr is good to go r🚀🚢🚢🚢🚢🚢⚓

authors: Shinyzenith lavafroth

repo: waycrate/swhkd


text:
請問現在愛奇藝字幕還可以下載嗎

我測試會出現錯誤

Fixed.

repo: wayneclub/Subtitle-Downloader


text:
Add babel-plugin-transform-async-to-generator for Node 6 compatibility

Hi,
I saw the deasync branch / PR (#2), however, I'm not sure I can lend any expertise to that discussion. However, I do need to use this plugin in a Node v6 environment, which does not natively support async / await.
Hence, as an apparent stopgap, I have added babel-plugin-transform-async-to-generator to .babelrc, which appears to generate a build which works on Node v6.

Coverage remained the same at 100.0% when pulling 947ee0af9921a16b0f0d5c322351e8cfacfe5e92 on kohlmannj:master into 55679c22334d8f8bc38d0bbf050f943c1dd63e6d on wbyoung:master.

We should just change this line instead to be 6.10.11 and continue to rely on preset-env.
Please try that and open a new PR that also updates the build targets. Thanks for contributing!

authors: coveralls kohlmannj wbyoung

repo: wbyoung/babel-plugin-transform-postcss


text:
chore(webpack): improvements of build artifacts

Build of the whole project will now produce:

icons-... asset
index.html
index.min.js
index-with-dependencies.min.js
styles.min.js

Things to do

( Im putting it here because stupid github has hidden those comments )

this build entry points are not doing what you think they are doing.
index.ts imports define from skate, so as a end result. skate will be always bundled. This is not what we wanted.
What you need to do:

[ ] for prod build you have to provide externals for main index.ts packages

externals: {
  skate: 'skatejs'
}

[ ] for prod build of index-with-deps.ts that vendor import is completely unnecessary and may increase bundle size. We are using three shaking, so only used functions/imports are bundled. only thing that you need to import there are polyfills

Great job @hopkins-tk will take a look tomorrow. If everything will be OK, I'll merge it. Thx!

authors: Hotell hopkins-tk

repo: wc-catalogue/blaze-elements


text:
Upgrading to latest syn and deku versions

Just changed versions and fixed compilation issues

Thanks, could you remove the .gitignore, README.md, and .idea changes?

Ignore the failing CI, that's not related to your changes directly (except for the code coverage, but it's fine for now)

Thanks, could you remove the .gitignore, README.md, and .idea changes?

Sorry... Still don´t figure how to do it... Will try.

Thanks, could you remove the .gitignore, README.md, and .idea changes?

I think it's done. Plz, review. Thanks


text:
How to get a rotated view of StackedBarChart?

Hello, I would like to have a horizontally positioned stacked bar chart. I have tried a few things to change the view like text rotation degree, then the bars and the texts overlapped.
Thanks in advance

I would have to code this from scratch as a parameter of the chart. I'll try and prototype this today.

this is what I did to get a rotated chart (barchar)
import(
  ...
  "image/png"

  "github.com/disintegration/imaging"
  "github.com/wcharczuk/go-chart"
  "github.com/wcharczuk/go-chart/drawing"
  ...
)

func drawChart(res http.ResponseWriter, req *http.Request) {
	sbc := chart.BarChart{
		Height:     512,
		Width:      280,
		BarWidth:   30,
		BarSpacing: 10,
		XAxis: chart.Style{
			Show: true,
		},
		YAxis: chart.YAxis{
			Style: chart.Style{
				Show:                true,
				TextRotationDegrees: -90,
			},
		},
		Bars: []chart.Value{
			{
				Value: 5.25,
				Style: chart.Style{

					FillColor: drawing.Color{
						A: 255,
						B: 0,
						G: 0,
						R: 255,
					},
					Show: true,
				},
			},
			{Value: 4.88},
			{Value: 4.74},
			{Value: 3.22},
			{Value: 3},
		},
	}
	r, w := io.Pipe()

	res.Header().Set("Content-Type", "image/png")
	go func() {
		err := sbc.Render(chart.PNG, w)
		if err != nil {
			fmt.Printf("Error rendering chart: %v\n", err)
		}
	}()
	img, err := png.Decode(r)
	if err != nil {
		fmt.Printf("Error decoding png: %v\n", err)
	}
	ret := imaging.Rotate270(img)

	if err := png.Encode(res, ret); err != nil {
		fmt.Printf("failed to send rotated chart: %v\n", err)
	}
}

The key parts are:

Rotate the text on YAxis TextRotationDegrees: -90,
Then call png.Decode with the result of go-chart
Rotate it using imagin
Encode it again using png.Encode and send it to the browser

But having a built in go-chart way would be great

This worked fine until I had to add a legend, having issues rotating the legend to match the chart

Any update on this? I am willing to build and contribute a solution if there is not already a prototype branch.

I added support for horizontal stacked bar charts in #114

authors: fmpwizard iremnurtokac pdt256 wcharczuk

repo: wcharczuk/go-chart


text:
Completing Race 7 Before Unlocking Invitational Circuit Pass Doesn't Unlock Later

completing race 7 (such that one of the invitational circuit races would normally unlock) does not unlock those races once the invitational circuit pass is received.
This causes the need to complete race 7 on the corresponding circuit a 2nd time to access.

So the purpose of the invitational circuit pass is to replace the vanilla unlock methods for the invitationals. If you have the pass, you should be able to play Invitational 1, which should unlock Invitational 2 on completion and so on and so forth.
However, completing race 7 a second time should NOT be giving you a track unlock when using this unlock mode, so it does sound like there is indeed a bug.

Also to clarify, the Invitational Circuit Pass (or 3rd progressive pass) won't necessarily be given on completing a circuit. It will be anywhere in the pool that logic allows

Sorry, perhaps I poorly explained the issue.   (perhaps this is actually a client issue instead of the world)
Steps Taken:

I completed race 7 of the semi-pro circuit (which I agree shouldn't unlock the invitational race 3 until the pass has been received)
The invitational pass is received
Invitational race 3 was not accessible until I beat race 7 on semi-pro a 2nd time.

Settings:
progressive_circuits: false
invitational_circuit_pass: true

No so the way the Invitational Pass is supposed to function is as follows:

You find Invitational Circuit Pass
Invitational 1 unlocks
You play Invitational 1
Invitational 2 unlocks
You play Invitational 2
Invitational 3 unlocks
You play Invitational 3
Invitataional 4 unlocks

It is SUPPOSED to completely replace the vanilla unlock system entirely if you are using it. What I am learning from your issue is that maybe there is a secondary function the game calls to write Invitational unlocks that I have missed, and should disable when using the Invitational Circuit pass.
In short, Invitational Circuit Pass is supposed to make it function like the first three circuits, but gates the whole circuit behind getting that item. If you play with Circuit Pass without Invitational then you will have passes for Semi-Pro and Galactic and the Invitational unlocks WILL be their vanilla methods.


text:
Filtering by timestamps

Hi,
It would be useful to add the ability to filter reads by timestamp. I believe this function would be possible only for ONT. A similar tool has already been developed in Rust (1).
One last thing ... it would be interesting to add the possibility to select the number of bases to keep (from the start of the read). Much like the CROP option of Trimmomatic (2).
1- https://github.com/angelovangel/nanotimes
2- https://github.com/usadellab/Trimmomatic
thank you for sharing your work
Joel

Thank you for your suggestions.

repo: wdecoster/chopper


text:
After rotation Month calendar shows Jan 1900

After an orientation change the date of the Month calendar is set to January 1900 (the selected date is still the right one):

I'm starting the dialog this way:
    // From the ViewModel class
    public void onDateClicked() {
        Calendar cal = Calendar.getInstance();
        cal.setTime(exam.getDate());
        DatePickerDialog datePickerDialog = DatePickerDialog.newInstance(
                this,
                cal.get(Calendar.YEAR),
                cal.get(Calendar.MONTH),
                cal.get(Calendar.DAY_OF_MONTH)
        );
        dataListener.showDialogFragment(datePickerDialog, DatePickerDialog.class.getName());
    }

    // Activity class
    @Override
    public void showDialogFragment(DialogFragment dialogFragment, String tag) {
        dialogFragment.show(getFragmentManager(), tag);
        dialogFragmentTagList.add(tag);
    }

Reproducible on AVD API 24 and Nexus 6P Android 7.0.

This feels like a Nougat specific issue.
The state is properly restored, but it's not scrolling the selection into view.
I think I know how to fix this.

any solution of this bug.

I had a look at this and the potential solution I was thinking of, is actually already there.
In the mean time I have a device that runs nougat and I can't reproduce this on the master branch.
I did change the ListView to a RecyclerView there, so maybe that also fixed this.
Can you try master and report back?

I  have samsung s7 with android 7.0
yesterday I have download your master project and import to AndroidStudio,
I send you Logcat : start when pick date, and start rotate begin from time 04-20 16:02:47.895
04-20 16:02:43.733 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@e1184d[MainActivity]: ViewPostImeInputStage processPointer 0
04-20 16:02:43.805 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@e1184d[MainActivity]: ViewPostImeInputStage processPointer 1
04-20 16:02:43.844 11082-11082/com.wdullaer.materialdatetimepicker.sample D/AbsListView: Get MotionRecognitionManager
04-20 16:02:43.846 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: mSContextService = com.samsung.android.hardware.context.ISemContextService$Stub$Proxy@bbe5550
04-20 16:02:43.848 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: motionService = com.samsung.android.gesture.IMotionRecognitionService$Stub$Proxy@9e8e349
04-20 16:02:43.848 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: motionService = com.samsung.android.gesture.IMotionRecognitionService$Stub$Proxy@9e8e349
04-20 16:02:43.850 11082-11087/com.wdullaer.materialdatetimepicker.sample I/art: Do full code cache collection, code=114KB, data=122KB
04-20 16:02:43.853 11082-11087/com.wdullaer.materialdatetimepicker.sample I/art: After code cache collection, code=114KB, data=96KB
04-20 16:02:43.885 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel constructed: fd=86
04-20 16:02:43.885 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f24b281[MainActivity]: setView = DecorView@1c97f26[] touchMode=true
04-20 16:02:43.952 11082-11103/com.wdullaer.materialdatetimepicker.sample D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000,  [1098x1872]-format:1
04-20 16:02:43.966 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f24b281[MainActivity]: MSG_WINDOW_FOCUS_CHANGED 1
04-20 16:02:43.967 11082-11082/com.wdullaer.materialdatetimepicker.sample I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus
04-20 16:02:43.970 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel constructed: fd=89
04-20 16:02:43.970 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel destroyed: fd=84
04-20 16:02:44.007 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f24b281[MainActivity]: MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=1
04-20 16:02:44.082 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@e1184d[MainActivity]: MSG_WINDOW_FOCUS_CHANGED 0
04-20 16:02:47.895 11082-11082/com.wdullaer.materialdatetimepicker.sample D/AbsListView: Get MotionRecognitionManager
04-20 16:02:47.979 11082-11103/com.wdullaer.materialdatetimepicker.sample D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000,  [1908x1200]-format:1
04-20 16:02:48.002 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f24b281[MainActivity]: dispatchDetachedFromWindow
04-20 16:02:48.008 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel destroyed: fd=86
04-20 16:02:48.010 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@e1184d[MainActivity]: dispatchDetachedFromWindow
04-20 16:02:48.014 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel destroyed: fd=81
04-20 16:02:48.079 11082-11082/com.wdullaer.materialdatetimepicker.sample D/AbsListView: Get MotionRecognitionManager
04-20 16:02:48.080 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: mSContextService = com.samsung.android.hardware.context.ISemContextService$Stub$Proxy@4bfb6e5
04-20 16:02:48.081 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: motionService = com.samsung.android.gesture.IMotionRecognitionService$Stub$Proxy@978d5ba
04-20 16:02:48.081 11082-11082/com.wdullaer.materialdatetimepicker.sample D/MotionRecognitionManager: motionService = com.samsung.android.gesture.IMotionRecognitionService$Stub$Proxy@978d5ba
04-20 16:02:48.094 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel constructed: fd=81
04-20 16:02:48.094 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f706212[MainActivity]: setView = DecorView@ca76de3[] touchMode=true
04-20 16:02:48.102 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel constructed: fd=82
04-20 16:02:48.102 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@75723e0[MainActivity]: setView = DecorView@c48b699[MainActivity] touchMode=true
04-20 16:02:48.130 11082-11103/com.wdullaer.materialdatetimepicker.sample D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000,  [1908x1200]-format:1
04-20 16:02:48.151 11082-11103/com.wdullaer.materialdatetimepicker.sample D/mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000,  [1920x1080]-format:1
04-20 16:02:48.152 11082-11082/com.wdullaer.materialdatetimepicker.sample E/ViewRootImpl: sendUserActionEvent() mView == null
04-20 16:02:48.153 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f706212[MainActivity]: MSG_WINDOW_FOCUS_CHANGED 1
04-20 16:02:48.153 11082-11082/com.wdullaer.materialdatetimepicker.sample I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus
04-20 16:02:48.154 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel constructed: fd=85
04-20 16:02:48.154 11082-11082/com.wdullaer.materialdatetimepicker.sample D/InputTransport: Input channel destroyed: fd=89
04-20 16:02:48.185 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@f706212[MainActivity]: MSG_RESIZED_REPORT: ci=Rect(0, 0 - 0, 0) vi=Rect(0, 0 - 0, 0) or=2
04-20 16:02:48.186 11082-11082/com.wdullaer.materialdatetimepicker.sample D/ViewRootImpl@75723e0[MainActivity]: MSG_RESIZED_REPORT: ci=Rect(0, 72 - 0, 0) vi=Rect(0, 72 - 0, 0) or=2

04-20 16:02:43.850 11082-11087/com.wdullaer.materialdatetimepicker.sample I/art: Do full code cache collection, code=114KB, data=122KB
04-20 16:02:43.853 11082-11087/com.wdullaer.materialdatetimepicker.sample I/art: After code cache collection, code=114KB, data=96KB
04-20 16:02:43.967 11082-11082/com.wdullaer.materialdatetimepicker.sample I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus
04-20 16:02:48.152 11082-11082/com.wdullaer.materialdatetimepicker.sample E/ViewRootImpl: sendUserActionEvent() mView == null
04-20 16:02:48.153 11082-11082/com.wdullaer.materialdatetimepicker.sample I/InputMethodManager: [IMM] startInputInner - mService.startInputOrWindowGainedFocus
04-20 16:02:52.992 11082-11082/com.wdullaer.materialdatetimepicker.sample W/IInputConnectionWrapper: reportFullscreenMode on inexistent InputConnection
and
04-20 16:02:48.152 11082-11082/com.wdullaer.materialdatetimepicker.sample E/ViewRootImpl: sendUserActionEvent() mView == null
04-20 16:02:52.992 11082-11082/com.wdullaer.materialdatetimepicker.sample W/IInputConnectionWrapper: reportFullscreenMode on inexistent InputConnection
and ERROR:
04-20 16:02:48.152 11082-11082/com.wdullaer.materialdatetimepicker.sample E/ViewRootImpl: sendUserActionEvent() mView == null

Has there been any solution to this bug? I'm still having this issue as of version 4.1.0.

Like I mentioned, I am not able to reproduce this here locally.
There is code to restore the state.
Are you experiencing this on all devices?
Which features of the pickers are you using?

Looks like this is only happening on my Moto X Pure test device. Any other device I try works just fine.

Can you try the sample app?
Maybe set a breakpoint at line 323 and 456 in the onCreateViewView() method of DatePickerDialog to see what the state looks like.
Does this also happen with the Timepicker?

Here are some screenshots of the states. I can also confirm this does NOT happen with time picker.

I think the problem in 2 commits

bc9cf01d3f603bdf38d9c9981f2e1463e16487c1 The guy added to sample activity configChanges() and onConfigurationChanges() to DatePickerDialog.java and  TimePickerDialog.java
2190c958db1837f74135434d7c9465529770359a Then he removed configChanges, but still using onConfigurationChanges with really strange part
As example looking into

DatePickerDialog.java

@Override
public void onConfigurationChanged(final Configuration newConfig) {
    super.onConfigurationChanged(newConfig);
    ViewGroup viewGroup = (ViewGroup) getView();
    if (viewGroup != null) {
        viewGroup.removeAllViewsInLayout();
       //null instead of bundle with state, because of this we loosing current date!
        View view = onCreateView(getActivity().getLayoutInflater(), viewGroup, null);
        viewGroup.addView(view);
    }
}

We didn't need any onConfigurationChanged() because onSaveInstanceState() covered all cases for the state restorarion.
The bug is producing on android 7.0 only, on higher versions onConfigurationChanged() not called without configChanges.
This error is producing memmory leak and canary from sample said about that.

authors: SkyGanfor leinardi meddd vladislav-snagovskoy wdullaer

repo: wdullaer/MaterialDateTimePicker


text:
Make TalkBack only read the value changed when something changes

Thanks for the great library!
We're experiencing an issue when using the timepicker with TalkBack enabled.
If you are on for example "Hour mode" (i.e. selecting hours), and you use 2 fingers to swipe to an hour, TalkBack only reads the seconds out loud. I.e "00".
The same goes for minutes. If you are in AM/PM mode it only reads AM or PM.
I think this is related to the onValueSelected method in TimePickerDialog which sets the hours, minutes, seconds and amPmDisplay. These setters will in turn call Utils.tryAccessibilityAnnounce(mTimePicker, text);, which will try to read out the values. However, since the announcements all come at almost the same time, TalkBack will only announce the latest value. Which will either be the seconds or AM/PM.
Not sure what the best way is to fix this is. Maybe to diff the old value with the new value and only announce it if it's different?

I must say that I don't intensively test the talkback logic. It's an area that can use improvement.
I am open to suggestions here, and PRs that improve it are much appreciated.
I'll give it some thought as well, but my time to work on this library has been limited the last year.


text:
⚠ Not working with forks

Creating annotations and auto-fixes works as expected when the code is on a branch in the same repository.
Unfortunately, it currently doesn't seem work with pull requests from forks: The action has no permission to push auto-fix changes or create annotations.

It seems like this is impossible with GitHub's current token scopes.
The action needs permissions for two operations:

Permission to create annotations with GitHub's Check Runs API to display the user's linting errors
Permission to push changes with Git (if auto_fix: true)

If the action is triggered on changes to the main repository, it will work because the GITHUB_TOKEN has permissions to modify that repository. On forks, however, this becomes tricky to impossible:

push event
pull_request event

commit to main repo
Works
Works

commit to fork
Only runs after the user manually activates GitHub Actions on the fork. Even then, annotations will not display on the PR (only on the fork).
No permission to push auto-fix changes. No permission to create annotations for linting errors.

Note that the pull_request event always runs on the main repository, even for pushes to the fork. The token scopes are defined accordingly.
If anybody is aware of a workaround, I'd be very happy to hear it :)
Related: https://github.com/actions/checkout/issues/124#issuecomment-580018424

All I can do for now is document these limitations in the README and provide more helpful error messages.
If you'd also like to see these permissions changed, please submit feedback to GitHub.

Would it be possible to catch the 403 error when the PR is coming from a fork so it doesn't mark the action as having failed?

GitHub introduced a new pull_request_target  event which might help here, see https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/#improvements-for-public-repository-forks

@samuelmeuli Thanks for making this easy to use library!
Have you had any chance to consider supporting github's pull_request_target.
It would be great to have the fork support available.

@1212gmartinez There's a WIP feature branch for this which you can try: https://github.com/wearerequired/lint-action/tree/feature/pull_request_target
You should be able to use it with wearerequired/lint-action@feature/pull_request_target.

Awesome, thanks!

Seems not to be working for us
fatal: Cannot force update the current branch.
Error: Command failed: git branch --force master --track fork/master
fatal: Cannot force update the current branch.

https://github.com/Uniswap/uniswap-interface/pull/1121/checks?check_run_id=1164841104

possibly related?
https://stackoverflow.com/questions/29559053/force-update-the-current-branch-how
issue is with git branch --force master --track fork/master
is it because the fork branches are named master?
in another case the linter passes but the check status is never reported
https://github.com/Uniswap/uniswap-interface/pull/1060

Instead of using pull_request_target, we could check repo's owner to skip lint action:
    - name: Run Lint
      uses: wearerequired/lint-action@v1
      if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.owner.login == github.repository_owner }}
      with:
        github_token: ${{ secrets.github_token }}
        black: true
        flake8: true
        auto_fix: true

So that lint action would be run only on push or pull_request events within the same repository.

If you write workflow commands to stdout instead of making web API calls with the token, the authentication issue goes away and the performance may even be better.
Example from docs page (https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-a-warning-message):
echo "::warning file=app.js,line=1,col=5::Missing semicolon"

A GitHub action using this approach: https://github.com/cschleiden/jest-github-actions-reporter

pull_request_target worked very well for me. See my PR here for an example: https://github.com/join-monster/join-monster/pull/449. Read this before using this new event though, as it has security implications: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

Hey! Was this solved? I see that the pull_request_target branch has been merge and pull_request_target is being referenced in code.
But still when I try to use pull_request_target with this aciton and a fork opens a PR, I get the 404 error.
see this dependabot PR for example

@Thatkookooguy Pull requests by Dependabot don't have access to secrets anymore, see https://github.com/dependabot/dependabot-core/issues/3253#issuecomment-852541544.
You should be able to use the the default GITHUB_TOKEN secret in combination with pull_request_target. Consider also limiting the default permissions. For a working example see test-action.yml.

Please consider using workflow commands (stdout) so that tokens are not needed and pull_request_target is not needed, as mentioned above (https://github.com/wearerequired/lint-action/issues/13#issuecomment-811518586).

@ocean90 thanks for the tip! will definitely check it out.

@ocean90 I'm confused. Why did you downvote?

Please consider using workflow commands (stdout) so that tokens are not needed and pull_request_target is not needed, as mentioned above (#13 (comment)).

This particular change seems like it should not be blocked, but won't help with auto_fix: true
@samuelmeuli Will you take a PR? Seems like this piece of code needs changing:

authors: 1212gmartinez MarvinT Thatkookooguy alexbbt jnm2 moodysalem ocean90 samuelmeuli yuekui

repo: wearerequired/lint-action


text:
Fix cause of release events

Release events in history and notifications were not showing the user (e.g., "automation") or message (when supplied).
While rewriting for gitsyncness, the release event structure got a bit overcomplicated. This PR simplifies it, and makes sure that the cause (user and message) is faithfully transcribed to the event sent upstream to the service.
It also fixes a couple of minor bugs and makes a small refactor, as detailed in the first commit message.

Pretty straightforward, LGTM

authors: sambooo squaremo

repo: weaveworks/flux


text:
update chart definition to include --annotate-nodes

This PR follow up from the introduction of node annotations introduced in #296.
Here we enable that functionality in the standard helm chart via a configuration.annotateNode value property. By default the helm chart sets that value to false (in other words, it will not change any behaviors for folks using existing helm charts when they upgrade to this chart version).
Also bumps the chart version from 2.3.2 to 2.4.0

Can we use "annotateNodes" in all places? Actually the helm-parameter is named "annotateNode", but the kured-cli and the helm-doc is named "annotateNodes".

Thanks! Yep, that was unintentional. Fixed.

repo: weaveworks/kured


text:
Check if Marathon labels containers with some meaningfull names

This could be a nice a quick fix for Mesos users, then we could add it along the side with KubernetesContainerNameLabel.

It doesn't use Docker labels, but it does set MARATHON_APP_ID as an environment variable.

repo: weaveworks/scope


text:
Fix Scope arguments in Docker Compose installation docs

Fixes #2142
Introduced in https://github.com/weaveworks/scope/pull/1146 (CC @pidster )

surely this should also fix the other breakages introduced by #1146.

Thanks, I had missed those


text:
Source URL hyperlink should respect reference

For users trying to navigate to their defined source, it would make things a lot simpler if they could follow the hyperlink and that take them to the correct fetched reference - a branch, tag or semver-tag.
The URL display text could match spec.url i.e. https://github.com/stefanprodan/podinfo
The hyperlink should be informed by the status.revision of the deployed source. Crucial for the semver example.
ref.commit=<example> or ref.branch=<example> = https://github.com/stefanprodan/podinfo/tree/<example>
ref.tag=<example> or ref.semver=<example> = https://github.com/stefanprodan/podinfo/tag/<example>

Somewhat relevant issue for consideration https://github.com/weaveworks/weave-gitops/issues/2115

Which git forges are in scope for this ticket?

fair point, I see how that would increase complexity and in which case @JamWils would need to weigh in on priority order. My suggestion would be github.com > gitlab.com > gitlab on prem > ghe. Others unsupported for now.

🤔 I definitely agree on GitHub and GitLab.  Also it would be nice to be taken to the correct ref.  I think we just need to be clear about the level of scope before this gets picked up.

This has been open a long time now.  I'm going to close this for the moment as it could be some time until we get to it.

authors: JamWils ozamosi sympatheticmoose

repo: weaveworks/weave-gitops