When I tried this example. I got this errors.

VUID-VkDeviceCreateInfo-pNext-pNext(ERROR / SPEC): msgNum: -1876993556 - Validation Error: [ VUID-VkDeviceCreateInfo-pNext-pNext ] Object 0: VK_NULL_HANDLE, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x901f59ec | vkCreateDevice: pCreateInfo->pNext chain includes a structure with unknown VkStructureType<PHONE_NUMBER>); Allowed structures are [VkDeviceDeviceMemoryReportCreateInfoEXT,
[encoded data, 5567 characters]
VkPhysicalDeviceTransformFeedbackFeaturesEXT, VkPhysicalDeviceUniformBufferStandardLayoutFeatures, VkPhysicalDeviceVariablePointersFeatures, VkPhysicalDeviceVertexAttributeDivisorFeaturesEXT,
VkPhysicalDeviceVertexInputDynamicStateFeaturesEXT, VkPhysicalDeviceVulkan11Features, VkPhysicalDeviceVulkan12Features, VkPhysicalDeviceVulkan13Features, VkPhysicalDeviceVulkanMemoryModelFeatures, VkPhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR, VkPhysicalDeviceYcbcr2Plane444FormatsFeaturesEXT, VkPhysicalDeviceYcbcrImageArraysFeaturesEXT, VkPhysicalDeviceZeroInitializeWorkgroupMemoryFeatures]. This error is based on the Valid Usage documentation for version 224 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 pCreateInfo->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 VkDeviceDeviceMemoryReportCreateInfoEXT, VkDeviceDiagnosticsConfigCreateInfoNV, VkDeviceGroupDeviceCreateInfo, VkDeviceMemoryOverallocationCreateInfoAMD, VkDevicePrivateDataCreateInfo, VkPhysicalDevice16BitStorageFeatures, VkPhysicalDevice4444FormatsFeaturesEXT, VkPhysicalDevice8BitStorageFeatures, VkPhysicalDeviceASTCDecodeFeaturesEXT, VkPhysicalDeviceAccelerationStructureFeaturesKHR, VkPhysicalDeviceAmigoProfilingFeaturesSEC, VkPhysicalDeviceAttachmentFeedbackLoopLayoutFeaturesEXT, VkPhysicalDeviceBlendOperationAdvancedFeaturesEXT, VkPhysicalDeviceBorderColorSwizzleFeaturesEXT, VkPhysicalDeviceBufferDeviceAddressFeatures, VkPhysicalDeviceBufferDeviceAddressFeaturesEXT, VkPhysicalDeviceCoherentMemoryFeaturesAMD, VkPhysicalDeviceColorWriteEnableFeaturesEXT, VkPhysicalDeviceComputeShaderDerivativesFeaturesNV, VkPhysicalDeviceConditionalRenderingFeaturesEXT, VkPhysicalDeviceCooperativeMatrixFeaturesNV, VkPhysicalDeviceCornerSampledImageFeaturesNV, VkPhysicalDeviceCoverageReductionModeFeaturesNV, VkPhysicalDeviceCustomBorderColorFeaturesEXT, VkPhysicalDeviceDedicatedAllocationImageAliasingFeaturesNV, VkPhysicalDeviceDepthClipControlFeaturesEXT, VkPhysicalDeviceDepthClipEnableFeaturesEXT, VkPhysicalDeviceDescriptorIndexingFeatures, VkPhysicalDeviceDescriptorSetHostMappingFeaturesVALVE, VkPhysicalDeviceDeviceGeneratedCommandsFeaturesNV, VkPhysicalDeviceDeviceMemoryReportFeaturesEXT, VkPhysicalDeviceDiagnosticsConfigFeaturesNV, VkPhysicalDeviceDynamicRenderingFeatures, VkPhysicalDeviceExclusiveScissorFeaturesNV, VkPhysicalDeviceExtendedDynamicState2FeaturesEXT, VkPhysicalDeviceExtendedDynamicStateFeaturesEXT, VkPhysicalDeviceExternalMemoryRDMAFeaturesNV, VkPhysicalDeviceFeatures2, VkPhysicalDeviceFragmentDensityMap2FeaturesEXT, VkPhysicalDeviceFragmentDensityMapFeaturesEXT, VkPhysicalDeviceFragmentDensityMapOffsetFeaturesQCOM, VkPhysicalDeviceFragmentShaderBarycentricFeaturesKHR, VkPhysicalDeviceFragmentShaderInterlockFeaturesEXT, VkPhysicalDeviceFragmentShadingRateEnumsFeaturesNV, VkPhysicalDeviceFragmentShadingRateFeaturesKHR, VkPhysicalDeviceGlobalPriorityQueryFeaturesKHR, VkPhysicalDeviceGraphicsPipelineLibraryFeaturesEXT, VkPhysicalDeviceHostQueryResetFeatures, VkPhysicalDeviceImage2DViewOf3DFeaturesEXT, VkPhysicalDeviceImageCompressionControlFeaturesEXT, VkPhysicalDeviceImageCompressionControlSwapchainFeaturesEXT, VkPhysicalDeviceImageProcessingFeaturesQCOM, VkPhysicalDeviceImageRobustnessFeatures, VkPhysicalDeviceImageViewMinLodFeaturesEXT, VkPhysicalDeviceImagelessFramebufferFeatures, VkPhysicalDeviceIndexTypeUint8FeaturesEXT, VkPhysicalDeviceInheritedViewportScissorFeaturesNV, VkPhysicalDeviceInlineUniformBlockFeatures, VkPhysicalDeviceInvocationMaskFeaturesHUAWEI, VkPhysicalDeviceLineRasterizationFeaturesEXT, VkPhysicalDeviceLinearColorAttachmentFeaturesNV, VkPhysicalDeviceMaintenance4Features, VkPhysicalDeviceMemoryPriorityFeaturesEXT, VkPhysicalDeviceMeshShaderFeaturesNV, VkPhysicalDeviceMultiDrawFeaturesEXT, VkPhysicalDeviceMultisampledRenderToSingleSampledFeaturesEXT, VkPhysicalDeviceMultiviewFeatures, VkPhysicalDeviceMutableDescriptorTypeFeaturesVALVE, VkPhysicalDeviceNonSeamlessCubeMapFeaturesEXT, VkPhysicalDevicePageableDeviceLocalMemoryFeaturesEXT, VkPhysicalDevicePerformanceQueryFeaturesKHR, VkPhysicalDevicePipelineCreationCacheControlFeatures, VkPhysicalDevicePipelineExecutablePropertiesFeaturesKHR, VkPhysicalDevicePipelinePropertiesFeaturesEXT, VkPhysicalDevicePipelineRobustnessFeaturesEXT, VkPhysicalDevicePortabilitySubsetFeaturesKHR,
VkPhysicalDevicePresentIdFeaturesKHR, VkPhysicalDevicePresentWaitFeaturesKHR, VkPhysicalDevicePrimitiveTopologyListRestartFeaturesEXT, VkPhysicalDevicePrimitivesGeneratedQueryFeaturesEXT, VkPhysicalDevicePrivateDataFeatures, VkPhysicalDeviceProtectedMemoryFeatures, VkPhysicalDeviceProvokingVertexFeaturesEXT, VkPhysicalDeviceRGBA10X6FormatsFeaturesEXT, VkPhysicalDeviceRasterizationOrderAttachmentAccessFeaturesARM, VkPhysicalDeviceRayQueryFeaturesKHR, VkPhysicalDeviceRayTracingMaintenance1FeaturesKHR, VkPhysicalDeviceRayTracingMotionBlurFeaturesNV, VkPhysicalDeviceRayTracingPipelineFeaturesKHR, VkPhysicalDeviceRepresentativeFragmentTestFeaturesNV, VkPhysicalDeviceRobustness2FeaturesEXT, VkPhysicalDeviceSamplerYcbcrConversionFeatures, VkPhysicalDeviceScalarBlockLayoutFeatures, VkPhysicalDeviceSeparateDepthStencilLayoutsFeatures, VkPhysicalDeviceShaderAtomicFloat2FeaturesEXT, VkPhysicalDeviceShaderAtomicFloatFeaturesEXT, VkPhysicalDeviceShaderAtomicInt64Features, VkPhysicalDeviceShaderClockFeaturesKHR, VkPhysicalDeviceShaderDemoteToHelperInvocationFeatures, VkPhysicalDeviceShaderDrawParametersFeatures, VkPhysicalDeviceShaderEarlyAndLateFragmentTestsFeaturesAMD, VkPhysicalDeviceShaderFloat16Int8Features, VkPhysicalDeviceShaderImageAtomicInt64FeaturesEXT, VkPhysicalDeviceShaderImageFootprintFeaturesNV, VkPhysicalDeviceShaderIntegerDotProductFeatures, VkPhysicalDeviceShaderIntegerFunctions2FeaturesINTEL, VkPhysicalDeviceShaderModuleIdentifierFeaturesEXT, VkPhysicalDeviceShaderSMBuiltinsFeaturesNV, VkPhysicalDeviceShaderSubgroupExtendedTypesFeatures, VkPhysicalDeviceShaderSubgroupUniformControlFlowFeaturesKHR, VkPhysicalDeviceShaderTerminateInvocationFeatures, VkPhysicalDeviceShadingRateImageFeaturesNV, VkPhysicalDeviceSubgroupSizeControlFeatures, VkPhysicalDeviceSubpassMergeFeedbackFeaturesEXT, VkPhysicalDeviceSubpassShadingFeaturesHUAWEI, VkPhysicalDeviceSynchronization2Features, VkPhysicalDeviceTexelBufferAlignmentFeaturesEXT, VkPhysicalDeviceTextureCompressionASTCHDRFeatures, VkPhysicalDeviceTilePropertiesFeaturesQCOM, VkPhysicalDeviceTimelineSemaphoreFeatures, VkPhysicalDeviceTransformFeedbackFeaturesEXT, VkPhysicalDeviceUniformBufferStandardLayoutFeatures, VkPhysicalDeviceVariablePointersFeatures, VkPhysicalDeviceVertexAttributeDivisorFeaturesEXT, VkPhysicalDeviceVertexInputDynamicStateFeaturesEXT, VkPhysicalDeviceVulkan11Features, VkPhysicalDeviceVulkan12Features, VkPhysicalDeviceVulkan13Features, VkPhysicalDeviceVulkanMemoryModelFeatures, VkPhysicalDeviceWorkgroupMemoryExplicitLayoutFeaturesKHR, VkPhysicalDeviceYcbcr2Plane444FormatsFeaturesEXT, VkPhysicalDeviceYcbcrImageArraysFeaturesEXT, or VkPhysicalDeviceZeroInitializeWorkgroupMemoryFeatures (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkDeviceCreateInfo-pNext-pNext)
    Objects: 1
        [0] 0, type: 3, name: NULL
VUID-VkImageCreateInfo-initialLayout-00993(ERROR / SPEC): msgNum:<PHONE_NUMBER> - Validation Error: [ VUID-VkImageCreateInfo-initialLayout-00993 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x4c3c1da0 | vkCreateImage(): initialLayout is VK_IMAGE_LAYOUT_DEPTH_STENCIL_ATTACHMENT_OPTIMAL, must be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED. The Vulkan spec states: initialLayout must be VK_IMAGE_LAYOUT_UNDEFINED or VK_IMAGE_LAYOUT_PREINITIALIZED (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkImageCreateInfo-initialLayout-00993)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
UNASSIGNED-CoreValidation-Shader-InconsistentSpirv(ERROR / SPEC): msgNum: 7060244 - Validation Error: [ UNASSIGNED-CoreValidation-Shader-InconsistentSpirv ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x6bbb14 | SPIR-V module not valid: Invalid capability operand: 5283
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkGraphicsPipelineCreateInfo-pDynamicStates-00749(ERROR / SPEC): msgNum: 28428915 - Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-pDynamicStates-00749 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x1b1ca73 | The line width state is static (pCreateInfos[0].pDynamicState->pDynamicStates does not contain VK_DYNAMIC_STATE_LINE_WIDTH) and
VkPhysicalDeviceFeatures::wideLines is disabled, but pCreateInfos[0].pRasterizationState->lineWidth (=0.000000) is not 1.0. The Vulkan spec states: If the pipeline is being created with pre-rasterization shader state, and the wideLines feature is not enabled, and no element of the pDynamicStates member of pDynamicState is VK_DYNAMIC_STATE_LINE_WIDTH, the lineWidth member of pRasterizationState must be 1.0 (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-pDynamicStates-00749)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkPipelineShaderStageCreateInfo-pName-00707(ERROR / SPEC): msgNum: -1282697375 - Validation Error: [ VUID-VkPipelineShaderStageCreateInfo-pName-00707 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xb38b9761 | No entrypoint found named `main` for stage VK_SHADER_STAGE_MESH_BIT_NV. The Vulkan spec states: pName must be the name of an OpEntryPoint in module with an execution model that matches stage (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkPipelineShaderStageCreateInfo-pName-00707)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkShaderModuleCreateInfo-pCode-01091(ERROR / SPEC): msgNum: -1480880714 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-01091 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xa7bb8db6 | vkCreateShaderModule(): The SPIR-V Capability (Int64) was declared, but none of the requirements were met to use it. The Vulkan spec states: If pCode
declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-01091)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkShaderModuleCreateInfo-pCode-01090(ERROR / SPEC): msgNum: 738239446 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-01090 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x2c00a3d6 | vkCreateShaderModule(): A SPIR-V Capability (Unhandled OpCapability) was declared that is not supported by Vulkan. The Vulkan spec states: pCode must not declare any capability that is not supported by the API, as described by the Capabilities section of the SPIR-V Environment appendix (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-01090)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkShaderModuleCreateInfo-pCode-04146(ERROR / SPEC): msgNum: -670416210 - Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-04146 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0xd80a42ae | vkCreateShaderModule(): A SPIR-V Extension (SPV_EXT_mesh_shader) was declared that is not supported by Vulkan. The Vulkan spec states: pCode must not declare any SPIR-V extension that is not supported by the API, as described by the Extension section of the SPIR-V Environment appendix (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-04146)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkGraphicsPipelineCreateInfo-stage-00727(ERROR / SPEC): msgNum: 461143016 - Validation Error: [ VUID-VkGraphicsPipelineCreateInfo-stage-00727 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x1b7c7be8 | Invalid Pipeline CreateInfo[0] State: Vertex Shader required. The Vulkan spec states: If the pipeline is being created with pre-rasterization shader state the stage member of one element of pStages must be VK_SHADER_STAGE_VERTEX_BIT (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkGraphicsPipelineCreateInfo-stage-00727)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL
VUID-VkPipelineShaderStageCreateInfo-stage-02091(ERROR / SPEC): msgNum: 987961089 - Validation Error: [ VUID-VkPipelineShaderStageCreateInfo-stage-02091 ] Object 0: handle = 0x14a78428130, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x3ae31701 | Invalid Pipeline CreateInfo[0] State: Mesh Shader not supported. The Vulkan spec states: If the meshShader feature is not enabled, stage must not be VK_SHADER_STAGE_MESH_BIT_NV (https://vulkan.lunarg.com/doc/view/<IP_ADDRESS>/windows/1.3-extensions/vkspec.html#VUID-VkPipelineShaderStageCreateInfo-stage-02091)
    Objects: 1
        [0] 0x14a78428130, type: 3, name: NULL

I have this ext and actual Vulkan API:

This looks like validation layers version does not recognize VK_EXT_mesh_shader. You can basically ignore the validation messages.
Does it start and run or does it crash after these messages?

This looks like validation layers version does not recognize VK_EXT_mesh_shader. You can basically ignore the validation messages. Does it start and run or does it crash after these messages?

Sorry for the very late answer :D
Well, it works and with Validation Layers is understandable.

Yes, closing this since its an validation layer issue.


Random client disconnection

Hello,
I am under Fedora 31 with php version 7.3.11-1.
I developed a mqtt client that worked very well with Fedora 29/30 for more than 2 years. Now the client connects, gives the expected information then disconnects for no apparent reason after a few minutes by giving the disconnect code 19.
I took over the complete installation of the package (Mosquitto-alpha then Mosquitto-beta) but the disconnection still occurs.
The problem is the same on a Fedora 31 workstation or Fedora 31 server version.
This problem seems to have been encountered on Raspberry.
==> Do you have an idea of the solution?
Regards

Hi,
After some research and testing, the problem seems to come from the broker (version 1.6.7). I had an extra-listener with the websocket protocol and when I removed it, I no longer have the problem of random disconnection.
The php mosquitto client works well with php version 7.3.11.
Regards


bug: eslint 8.57 problems

Provide environment information
7.23.1
Describe the bug
After running pnpm update got this error in a project:
Parsing error (You may need configure typescript-eslint-parser): project was set to `true` but couldn't find any tsconfig.json relative to '/home/../src/server/auth.ts' within<EMAIL_ADDRESS>1:1:6 eslint

I also getting this one:
Could not parse linter output due to: Expected value but found invalid token at character 1output: Error: Failed to load plugin 'react' declared in '.eslintrc.cjs » eslint-config-next/core-web-vitals » /home/.../node_modules/eslint-config-next/index.js': ENOENT: no such file or directory, open '/home/../node_modules/.pnpm/eslint-plugin-react<EMAIL_ADDRESS>from: /home/../node_modules/eslint-config-next/index.js 1:1:6 eslint_d

I will try to downgrade and see if it fixes this issue.
Reading the error and seeing the problem my guess is that there are multiple eslint version installed, I see my editor is using eslint in<EMAIL_ADDRESS>and for some reason it tries to read the tsconfig.json in that directory.
Maybe more of a problem with eslint itself. Reading a bit more the config to see how to fix it. One solution could be to add the file path in the eslint config.
Reproduction repo
none
To reproduce
pnpm update
Additional information
No response

Tried creating a new app with latest scaffolder and I have the same problem.
I guess this is something related to my editor config then.

neovim 0.10
lint via nvim-lint and eslint_d


[EOSF-889] Add noscript message if javascript is disabled

Purpose
If users do not have JavaScript enabled on their browser, ember-osf pages are displayed as blank white pages.  This will add an error message on the page that lets the user know what is happening and how to enable JavaScript to use the site.
Summary of Changes

Added <noscript> message

Ticket
https://openscience.atlassian.net/browse/EOSF-889
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md (don't have initial release yet)

Coverage remained the same at 6.931% when pulling 1a6bfb4ad5a27c5d3ef25fd927b74522032fc36a on baylee-d:feature/add-no-javascript-message into b3b7fa0f151ae075b84c7e23543d9a997308220f on CenterForOpenScience:develop.


Watch process doesn't seem to work

Checking out the plain project and running npm run dev, the file watcher is not working and manually restarting the application is needed.
System: Windows 10, Version 10.0.19042 Build 19042.
Side note: I've also had some trouble with the babel config and needed to add "loose": true, here: https://github.com/collective-soundworks/soundworks-template-build/blob/master/src/build-application.js#L81

The watcher (chokidar) works correctly when in files in ./.bulid/ are changed (because of this) but not when changing/saving things in ./src/.

The watcher (chokidar) works correctly when in files in ./.bulid/ are changed (because of this) but not when changing/saving things in ./src/.

Yes. However, it would be nice to register changes while developing the application. Is there a reason why it is how it is right now?

No there is actually no reason, the steps for the build are supposed to be:

transpile (from src to .build) when a change is seen in src
restart server if a file changed in .build/server,

This way the process is (when it works...) very simple and no possible concurrency issues.
If the server restarts when a file is saved in .build it means the transpile step does not work (which is actually weird and new). As I discovered the "loose: true" issue today too, I hope this is only a side-effect of this problem (even if on my side MacOS 11, the server restarts has expected when I save a file...).
I just pushed and published a new version 3.0.3 that fixes the "loose: true" issue and some other weirdness, let me know if it is back to normal for you

I can confirm that the solution is working - and it's sooo much faster then recompiling the whole server. Thank you.

Perfect ! Let's close that then


Include dep installation step in git instructions

Installing Haraka with NPM directly takes care of dependencies, but before you can run it out of a git repo, you have to install dependencies.  I assume npm install (installing the deps locally rather than globally) is the preferred way to do this

Yes - that's correct.


Added europe-west6 to region_params

Without defining europe-west6 in region_params terraform fails with the following message:
${var.zone == "" ? lookup(var.region_params["${var.region}"], "zone") : var.zone}

I signed it!

I signed it!


build(client): remove unused @internal re-exports

Note: api reports suggest there is an export change, but there is no public or beta export change. The report was incorrect.

The api reports look correct to me. I don't understand how this isn't a breaking change. Types were exported, but now they are not. am i missing something?

Note: api reports suggest there is an export change, but there is no public or beta export change. The report was incorrect.

Is this true? Does our rollup logic look at release tags on members of other packages? If so, does it only look at release tags of other Fluid packages? Not particularly likely, but if an external library happens to be using release tags on their APIs, we may be inadvertently applying our release tag semantics against external things, which we shouldn't be doing.

The api reports look correct to me. I don't understand how this isn't a breaking change. Types were exported, but now they are not. am i missing something?

They were not exported via any path except /internal which is not in breaking scope. (I mean anything can breaking, but these are fine.)
The API report does not understand re-exports well, but our generated "roll up" files do. Our tooling needed to make sure they weren't exporting anything extra. We don't commit our generated "roll up" files so I only manually confirmed that there is no change in any of the public.d.ts, beta.d.ts, and legacy.d.ts files. (You don't see a container-definitions.legacy.alpha.api.md change here because that report is now generated from legacy.d.ts. The change use to legacy.d.ts "roll up" for generating report is what brought this funkiness to our attention. See #21451.)

Note: api reports suggest there is an export change, but there is no public or beta export change. The report was incorrect.

Is this true? Does our rollup logic look at release tags on members of other packages? If so, does it only look at release tags of other Fluid packages? If an external library happens to be using release tags on their APIs, we may be inadvertently applying our release tag semantics against external things, which we shouldn't be doing.

It only looks for tags on things that are exported. And it does go back to the source for those. If we re-export something from a foreign package (I don't think we do), then it would be looking at those tags. We should be generating our reports from our "roll ups" to have the best reports. We can't quite do that yet though. We need some policy to make sure the right "roll up" is used and we need to fix the @packageDocumentation issue.

Note: api reports suggest there is an export change, but there is no public or beta export change. The report was incorrect.

Is this true? Does our rollup logic look at release tags on members of other packages? If so, does it only look at release tags of other Fluid packages? If an external library happens to be using release tags on their APIs, we may be inadvertently applying our release tag semantics against external things, which we shouldn't be doing.

It only looks for tags on things that are exported. And it does go back to the source for those. If we re-export something from a foreign package (I don't think we do), then it would be looking at those tags. We should be generating our reports from our "roll ups" to have the best reports. We can't quite do that yet though. We need some policy to make sure the right "roll up" is used and we need to fix the @packageDocumentation issue.

To be safe, we should probably only consider tags on items from external packages if they are one of ours. API-Extractor (at least in theory) controls this policy via the bundledPackages option. For our bespoke tooling, we can probably just filter it to fluid-framework and packages in our short list of namespaces.

To be safe, we should probably only consider tags on items from external packages if they are one of ours. API-Extractor (at least in theory) controls this policy via the bundledPackages option. For our bespoke tooling, we can probably just filter it to fluid-framework and packages in our short list of namespaces.

I don't know what that practically means. Our packages will export an API or not. For those exported APIs, we need to determine where to export it. Are you saying that we should just never export foreign APIs (effectively internal)? The alternative is always export foreign APIs (effectively public). Generally seems best not to export foreign APIs. Does seem worth a work item. Do you have a post-2.0 place to collect such work?


Update SMK and other updates to match smk-fap-fcb

link to demo deployment of your smk based app is
https://smk-fap-bcfls-rt-b16795-dev.apps.silver.devops.gov.bc.ca
Verify that it looks good, if so merge the pull request which will trigger a prod deployment, otherwise close the pull request without merging
mentions / notifications: @GuyTheFlower, @NicoledeGreef, @franTarkenton

The Vanity URL for the dev deploy is https://smk-fap-bcfls-api-gov-bc-ca.test.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @GuyTheFlower, @NicoledeGreef, @franTarkenton

Looks good but it would be great to adjust the British Columbia logo size.  It is a bit stretched at the moment, the french app https://smk-fap-fcb-api-gov-bc-ca.test.api.gov.bc.ca/ looks rightsized.

Oh yes, the logo is another to do. The image we have is very low resolution and we actually have to expand it to get the space to fill. Do you know of a source for a better quality image?

You can peruse and download all the official Province of BC marks here: https://www2.gov.bc.ca/gov/content/governments/services-for-government/policies-procedures/bc-visual-identity/download-marks

Something is broken and I can't re-run the build pipeline in this PR. I'm going to close this PR and create a new one so we get a new image built and deployed.

The Vanity URL for the dev deploy is https://smk-fap-bcfls-api-gov-bc-ca.test.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @GuyTheFlower, @NicoledeGreef, @franTarkenton

@NicoledeGreef, the logo has been updated with a higher resolution image and re-sized properly.

looks great, @dgboss.  thanks!

link to demo deployment of your smk based app is
https://smk-fap-bcfls-rt-b16795-prod.apps.silver.devops.gov.bc.ca
Verify that it looks good, if so merge the pull request which will trigger a prod deployment, otherwise close the pull request without merging
mentions / notifications: @GuyTheFlower, @NicoledeGreef, @franTarkenton

The Vanity URL for the prod deploy is https://smk-fap-bcfls.api.gov.bc.ca
If this is a dev deploy,  verify that it looks good, then merge the pull request to trigger prod deployment.
If this is a prod deployment, view your prod deploy at the url above :)
mentions / notifications: @GuyTheFlower, @NicoledeGreef, @franTarkenton


Dev

Pull request for V3's Development Branch

Pull Request closed to rename dev branch (dev > v3dev)


router push gives DOMException: Failed to execute 'replace' on 'Location': 'http://localhost:8080undefined' is not a valid URL

Using router.push(path) but get an error as in the title. When looking at the debugger, it fails at the changeLocation line:
    function push(to, data) {
        const currentState = assign({}, history.state, {
            forward: to,
            scroll: computeScrollPosition(),
        });
        changeLocation(currentState.current, currentState, true);    // this is the line that fails

I can see in the debugger that to has the correct value but currentState.current is undefined. What could be the issue?

why this problem is still confused me

Workaround:
if you use history.pushState(...)  directly alone with Vue router navigation you can avoid this problem by adding the current property yourself like this:
const new_state = {
   whatever: 'this is your data',
   current: '/'   // this is the workaround
}

window.history.pushState(new_state, '', '/next/path');

What was the problems?
I used history.pushState(...)  to keep the navigation state on the URL but this way of changing URL does not use the Vue router which sets for itself the current property every time. If you use history.pushState(...) directly it does not fail immediately but it does not set the current property. So it fails the next time you try to use the normal Vue router.


OATS tests are green even if they fail

For example, the metrics test looks for a metric named sql_client_duration_buckets which cannot exist (_bucket is singular in Prometheus), yet make oats-test succeeds. Same for the trace test, if you replace the query { .db.operation = "SELECT" } with { .db.operation = "random bla bla" } the test is still green.

This is now resolved


Argenteam

Motivation for changes:
Get the subtitle link for the release to be downloaded.
Detailed changes:

Added argenteam_subtitle entry field with the url for download this subtitle

Config
movies:
    template: [torrent]
    imdb_lookup: yes
    discover:
      what:
        - movie_list: watchlist
      from:
        - argenteam:
            force_subtitles: yes
      interval: 1 days
    quality: 720p hdtv+
    list_match:
      from:
        - movie_list: watchlist
    exec: ./argenteam_subtitle.sh '{{argenteam_subtitle}}' /downloads/transmission >> argenteam_subtitles.log

Script to download
argenteam_subtitle.sh
wget "$1" -qO subs.zip
unzip -o subs.zip -d "$2"
rm subs.zip

You should fix the merge conflict and the codacy review

@cvium done! ;)


iOS 6.1 Beta - Widget is not using images in the shared container

@vincode-io Why is this re-opened?

I had to revert the change because it wouldn't compile.


Fails on GitLab when triggering a new pipeline on a branch without new commits

Job after a merge to master: https://gitlab.com/micro-ROS/ros_tracing/tracetools_analysis/-/jobs/612272575

Detected: GitLab
on default branch 'master': will check new commits
Checking commits: 38da641ae4ed7472a814e10ac3513b0c3e5e763a..10310dbd8c3ac5e8e505a9292becaede0bfeff1a

Nightly job that was triggered a bit later (no new changes): https://gitlab.com/micro-ROS/ros_tracing/tracetools_analysis/-/jobs/612419164

Detected: GitLab
on default branch 'master': will check new commits
Checking commits:<PHONE_NUMBER>000000000000000000000000000000..10310dbd8c3ac5e8e505a9292becaede0bfeff1a
error: fatal: Invalid revision range<PHONE_NUMBER>000000000000000000000000000000..10310dbd8c3ac5e8e505a9292becaede0bfeff1a

So it would seem that this line & the CI_COMMIT_BEFORE_SHA env var give an invalid SHA: https://github.com/christophebedard/dco-check/blob/444eac10b8a8c357d1b52c662c6e6f1c13a6ee63/dco_check/dco_check.py#L619

Weird behaviour for CI_COMMIT_BEFORE_SHA, as reported here:

https://gitlab.com/gitlab-org/gitlab/-/issues/7898
https://gitlab.com/gitlab-org/gitlab/-/issues/12850

Findings:

CI_COMMIT_BEFORE_SHA is all zeros when pushing a new branch: https://gitlab.com/micro-ROS/ros_tracing/tracetools_analysis/-/jobs/613013361
works when pushing to an existing branch: https://gitlab.com/christophebedard/tracetools_analysis/-/jobs/613067025
works if I retry that job: https://gitlab.com/christophebedard/tracetools_analysis/-/jobs/613071839
all zeros if triggered by a schedule: https://gitlab.com/christophebedard/tracetools_analysis/-/jobs/613076623

So the problem seems to be schedules. It would make sense to not run dco-check or have it do nothing if it's a scheduled pipeline. A simpler solution could be to set commit_hash_base to commit_hash_head if commit_hash_base is all zeros. This way it won't check anything and is rather simple.
However, if the schedule is not on the default branch (which definitely happens), then it will try to check commits off of the default branch (given the current logic in GitlabRetriever.get_commit_range()), which still doesn't really make sense. Therefore, we could simply detect the schedule (CI_PIPELINE_SOURCE == schedule) and not do anything/set base to head and mention it in a verbose_print().


Form Controls take as much as 10 seconds to receive focus or update border css

I have been working with Bootstrap and AngularJS for a few months now.  This is the first time I have noticed this problem.  Using Bootstrap 3.3.2, I have placed about 10  controls on a page.  Most of them simple input text, one text area, and three dropdown populated using ng-options technique. I am using Chrome 40.0.2214.111 m, on a Windows Server 2008 R2 TS Remote Desktop.
The reason I am posting this as a Bootstrap issue is that when I remove Bootstrap from the equation the problem goes away.
What I was trying to do when I noticed this problem was to use Bootstrap validation css with AngularJS validation hints. So, when a field is determined to be invalid a has-error class is added to the form-group div tag.  This of course propagate the styles down to the label, and input (input, select and textarea) controls.  This works fine, in fact the labels take on the new style immediately.  However it can take as much as 10 seconds for the borders on the input control to change their styles.
The same is true when just tabbing from field to field; the focus box can take as much as 10 seconds to move.
I have searched many forums, including skimming though the issues posted here. I don't seem to see anything that address this issue I am facing.
UPDATE: Testing using Safari for Windows 5.1.7 and Firefox 35.0.1;  issue does not exist in these browsers.

Can you post a jsbin of the problem with just bootstrap. We can't support issues with third party frameworks such as Angular though. Stack overflow is best for that with the Twitter bootstrap 3 tag

UPDATE: Testing using Safari for Windows 5.1.7 and Firefox 35.0.1;  issue does not exist in these browsers.
Kirsche all you really need is the HTML.  I have proven that the AngularJS part is not the issue.  I will reproduce with an simpler example and post a JSBin.

Here is the JSBin, however, this exercise allowed me to test on more platforms.  It seems that issue only exists on the Windows Server 2008 R2 remote desktop platform.  I have now confirmed that OSx, and Windows 7 do not exhibit the same behavior; everything works as expected on these platforms.
Slow focus change example

May I suggest that what you're seeing is a problem/result of the remote desktop connection? No other user or dev in the wild has reported such a highly visible bug.

I am trying to verify that now.  I am only seeing the issue with Chrome, which, to be fair, is what we use for most of our JS development.  There were a lot of Chrome instances open on the server, so I am rebooting the server...
...Now that this server is back up and running I am no longer experiencing the problem.
I think this issue can be closed.
Thanks for coaching me through this. Now I can get back to work :)

:+1:


How to start cropper inside canvas from top position not from center

I have a requirement like, cropper which is showing inside canvas should start from top position not center alignment. Please help to resolve this.

I was tried this code inside "cropper" method,
cropper.cropPosition=null;
cropPosition = new CropPosition();
cropPosition.x = bounds.left;
cropPosition.y = 1;
cropPosition.w = bounds.right-bounds.left;
cropPosition.h = bounds.bottom-bounds.top;
it is working fine for me.


Add metadata to mark all license and copyright files to be shipped when redistributing packages

Problem
It's idiomatic to split up functionality into many (small) crates. I can easily have hundreds or thousands of dependencies (or even more?) when using Rust. This makes Rust unsuitable to create and ship binaries or packages which include binaries, because even the most liberal licenses require to include copies of the license text (which is often derived from a template) and/or additional files (e.g. a NOTICE file in case of the Apache 2.0 license).
It's practically very very hard for a single maintainer to do this, especially when a lot of dependencies are involved and when wanting to provide regular updates. There are some automated tools, such as

cargo-about
cargo-bundle-licenses

but these seem insufficient, as I explained in this post on URLO.
Moreover, it doesn't feel right to do this using a heuristic (which can fail). Corresponding metadata is missing as of today's Cargo.toml specification.
Proposed Solution
A new metadata field should be added, which is giving an exhaustive list of files to be shipped/bundled when redistributing a package (or part of a package and/or when making a derived work, e.g. when compiling a binary).
Of course this list could be wrong, but then such a crate could be marked as errorneous in a database (just like a vulnerability, because it does sort-of mislead you in a dangerous way). Ideally such a field would become mandatory at some point in future. See also my follow-up on URLO.
Notes
Related issue: #8537, see also comment. Note, however, that license-file isn't a good choice for the proposed feature. That field is meant for custom licenses, and it also wouldn't be suitable to refer to a NOTICE file (or any other file which is required for proper attribution) to be shipped in addition to a license file.
Could the authors field be used, or could something like a copyright-lines field be introduced to be able to recreate the licenses from scratch? Likely not. Many license texts are templates where the copyright holder or product name(s) are incorporated directly into the text of the license. See my comment here on URLO on that matter. For example, the MIT-Modern-Variant license template has "THE UNIVERSITY OF CALIFORNIA" as part of the template text, which is ought to be replaced if the license is used by someone other than the University of California. Thus each license can be unique and possibly must be bundled as-is (i.e. word-by-word) in order to fulfill the license requirements.

Thanks for the proposal!
I am not an expert in this topic. Just got some questions.

How a new field of exhaustive list could help the situation ecosystem-wide? Assumed people do not actively fill in the field, downstream developers still have no idea what should be bundled no matter the field is either license, license-file, include, or shiny new redistributed-include.
There is a mention of a database doing checks for incorrect lists, but how could a database infer what files should be there with the absence of that list?

Perhaps the precise version of the question is: For a downstream developer, how to figure out what to bundle even when an upstream library doesn't provide sufficient info of what must be bundled.

Personally, when it comes to license compliance like this, there are a lot of complications and nuance that I think this deserves an RFC, starting with a Pre-RFC on Internals.  In preparing the Pre-RFC and RFC, I think it would be important to work with the authors of the aforementioned tools on it and see if you can get a spread of people who deal with software legal compliance.  For example, I know of two people at prior points in their career who were the liaisons between R&D and legal for legal compliance (a lot of my caution in this area comes from speaking with one of these).  It'd be good to find multiple people like that across the community to get a breadth of experience and perspectives.  I wonder if we can get the Foundation to help consult lawyers as well.
In driving this, I would recommend stepping back a bit and re-evaluate how you are approaching other people to avoid derailing this effort.  While I've not caught up with everything, the parts of your posts I've skimmed come across with a harsh tone that might make this kind of collaboration more difficult.

As I've pointed out elsewhere, almost all licenses require that the license text be included with the software.  Assuming we're not doing something like Debian's common-licenses directory, that means that every time someone specifies a license of MIT or Apache-2.0 that some license text must be included.  My proposal was simply not to complain about the joint use of the license and license-file keywords, since encouraging people not to use both license and license-file actually encourages people to not comply with the license.  (The license keyword is useful machine-readable contexts, and license-file is useful for including the text and
copyright information.)  Those issues have unfortunately been closed, however.
This poses a practical problem for me as a distributor of Rust-based binaries in my corporate role because I have to personally extract this information out of the Git repository when it's not included in the crate, which is tedious with many such crates.  I know that when distributors such as Debian ship a crate or other Rust-based software, they must also include this information, so I'm hardly the only person who would benefit from a change.
Providing some sort of metadata where users could specify the license itself, the copyright information, and any other legally required text would be helpful, I think, and encourage license compliance.

I'd like to note that I currently don't have the time to formalize this proposal in terms of writing up an RFC, contacting the authors of the aforementioned crates, or speak to lawyers of the Foundation (I also doubt they'd be available for me, as a contributor). So if it's really necessary to make this a formal process, I'd kindly like someone else to push this issue forward. I do think that there are more people who need this (or a similar) feature.

I do think that there are more people who need this feature or a solution that solves the issue in a similar or better way.

As a reminder, Rust development is done by volunteers.  If someone doesn't step up to lead an effort like this, then it doesn't get done.

After the previous posts, I don't expect this to move forward. I wrote that notice so other people know I won't do the proposed actions regarding involving lawyers and/or doing a community-wide research to get "a breadth of experience and perspectives." Please note that I'm a volunteer too, and I'm not well connected to the Rust developer scene and/or the Foundation.
I merely pointed out some legal issues in my posts and in this issue and wrote up a feature proposal. It's nothing more, nothing less. Feel free to do the proposed actions if you think they are good to do.
It would be nice if my efforts here or elsewhere (as much or as little they may be) are being appreciated. Meta: I don't think writing a feature request or issue report is a bad thing per-se, even if you can't write a corresponding pull-request and/or start further processes needed to fix an issue.


docs: add js docs

So the approach is to add all addresses to the TS side, no matter if they are directly called by users on the Aave UI or not?

So the approach is to add all addresses to the TS side, no matter if they are directly called by users on the Aave UI or not?

Yep, adding all the somewhat relevant addresses to the ts side to have one place with all the addresses one might need when interacting with aave.


Driver.stop_db() makes database unusable

On MacOS Big Sur, Neo4j Desktop 1.4.10, connecting with the python driver and calling Driver.stop("neo4j") leads to non-usability of the DB. Calling Driver.start("neo4j") results in a neo4j.exceptions.TransientError: {code: Neo.TransientError.Database.DatabaseUnavailable} {message: Database 'neo4j' is unavailable.}
In addition, the database is not recoverable by other means, e.g. in the Neo4j Desktop interface.

This has nothing to do with the OS or the GUI. It's simply that if you stop a database, it's gonna be offline, and you can not execute a query against an offline database. Hence you have to select another database, then you can do anything, including restarting the first database. How it looks like in Cypher:
neo4j@neo4j> SHOW DATABASE neo4j;
+-------------------------------------------------------------------------------------------------------------------------------+
| name    | aliases | access       | address          | role         | requestedStatus | currentStatus | error | default | home |
+-------------------------------------------------------------------------------------------------------------------------------+
| "neo4j" | []      | "read-write" | "localhost:7687" | "standalone" | "online"        | "online"      | ""    | TRUE    | TRUE |
+-------------------------------------------------------------------------------------------------------------------------------+

1 row
ready to start consuming query after 38 ms, results consumed after another 9 ms
neo4j@neo4j> STOP DATABASE neo4j;
0 rows
ready to start consuming query after 7 ms, results consumed after another 0 ms
neo4j@neo4j> START DATABASE neo4j;
Database 'neo4j' is unavailable.
neo4j@neo4j> :use system
neo4j@system> START DATABASE neo4j;
0 rows
ready to start consuming query after 15 ms, results consumed after another 0 ms
neo4j@system> :use neo4j
neo4j@neo4j> SHOW DATABASE neo4j;
+-------------------------------------------------------------------------------------------------------------------------------+
| name    | aliases | access       | address          | role         | requestedStatus | currentStatus | error | default | home |
+-------------------------------------------------------------------------------------------------------------------------------+
| "neo4j" | []      | "read-write" | "localhost:7687" | "standalone" | "online"        | "online"      | ""    | TRUE    | TRUE |
+-------------------------------------------------------------------------------------------------------------------------------+

1 row
ready to start consuming query after 225 ms, results consumed after another 6 ms
neo4j@neo4j>

In this module it's exactly the same:
import neo4j_utils

d = neo4j_utils.Driver()
d
# <Driver neo4j://localhost:7687/neo4j>
d.current_db
# 'neo4j'
d.user
# 'neo4j'

# and now stop the database:
d.stop_db()

## by default the fallback database is also "neo4j", hence the fallback query will fail too:
d.start_db()
[2022-10-19 22:11:53.514] [neo4ju.query]                 [WARNING]  Running query against fallback database `neo4j`.
[2022-10-19 22:11:54.522] [neo4ju.query]                 [ERROR]    Failed to run query: TransientError: {code: Neo.TransientError.Database.DatabaseUnavailable} {message: Database 'neo4j' is unavailable.}

## if we switch to an online database, the command can be executed:
d.select_db('system')
d.start_db('neo4j')
d.select_db('neo4j')
d.db_status()
# 'online'

## if the fallback database is "system" it's even more seamless:
d.stop_db()
d.start_db()
# [2022-10-19 22:16:19.501] [neo4ju.query]                 [WARNING]  Running query against fallback database `system`.

It indeed makes sense to change the fallback database to system, I'll do that.

The default behaviour became more convenient since b47dfbc and a5d5dab


Chapter G: Triage

DeeFIR

Hey there! I'm tentatively setting 7/31/2022 as a milestone for publishing v1.0 of this book. We'll have the title decided in the next couple weeks which will be the first of multiple administrative tasks we'll complete in July. At this point, please let me know if you intend to have at least a working, editable version of your chapter by 7/31/2022.
If not, please know that's perfectly fine. It doesn't mean your chapter won't get published, it just won't get published in v1.0. It'll simply be added when it's ready to be published and I'll push out a new version of the book, (i.e., V1.3, v1.7, etc) with your new content. I hope we have about 10 ready to go by 7/31/2022 so we can push to publish v1.0 shortly thereafter, but I won't know that until I hear from you! So, please let me know!

Writing nearly done :)

Writing nearly done :)

Great! As of now, once this chapter is done, we'll push out v1.1!

Closing this since it's already been published!


Add header metadata to new embeds

Fixes #8813

Looks nice! :)

Please CR @gfiorav. I moved all the code to use @vizjson so this benefits from mapcapsTM

Very railish indeed 😄
Benefits is a strange word to use here 😆  but let's take care of that when it finally comes.
📦  when 🍏


[Bug]: Asserted distribution--no shape for the state of Telangana, India

Steps to reproduce the bug
1.When asserting a distribution, I can select every Indian state EXCEPT Telangana
2.Telangana has been an independent state since 2014 and needs a shape at the level of state.
3.
...

Screenshot

Expected behavior
Need to be able to select Telangana under asserted distribution.
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
version 0.35.1
Browser Used
Chrome

See also https://www.britannica.com/place/Telengana

We need to add level_2 shapes for India, this should cover Telangana.

It doesn't, it's new as of 2014.


Update PaymentRequest API for Chrome Dev 53.0.2774.4

The format of the Android Pay parameters has changed to pass in more
information or Android Pay. See the "Android Pay" sample for details.
PaymentRequest now allows merchants to collect user's contact
information: phone number and/or email address. The merchant can specify
this in options:
var options = {
requestPayerPhone: true,
requestPayerEmail: true
};
Chrome returns the contact information in the 'payerPhone' and
'payerEmail' fields in the instrument response.
The parameter type for the complete() method has changed from a boolean
to a string with two predefined values.

"success" - merchant successfully completed the transaction.
"fail" - merchant is not able to complete the transaction.

Any other string means the merchant cannot indicate either success or
failure to the user at the moment.
Chrome no longer returns the 'totalAmount' in the instrument response.

LGTM against ToT


Update http4s-blaze-client, ... to 0.21.33

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl
org.http4s:http4s-server

from 0.21.14 to 0.21.33.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #631.


I need help

If you have a experience in Django or Front-end(html, CSS, js) please, write me on my email!

UPDATE: my email you can find in my README


ImageSpec in reusable application

Hello,
is there any way how to define ImageSpec fields dynamically please? I have reusable application Photo and I would like define different photo variants per project (for example in project1 fields thumbnail, catalog and in project2 fields thumbnail and detail; in both cases there will be different crop sizes for ImageSpec fields).
I used ImageKit in past, and that time I should define effectivelly specs.py per project with own photo variants.
Is something like this possible in this new "Field API" approach please?
Thanks for any hint.

Sorry, I'm not quite understanding. Is Photo a model?

Ah, I get it now! I think what you're looking for is a proxy model. Proxy models allow you to define different behaviors (not fields!) for existing models. Since ImageSpecs don't represent actual database fields, they fall under this heading. Following your example, it might look something like this:
# project1.models
class Project1Photo(Photo):
	thumbnail = ImageSpec(...)
	catalog = ImageSpec(...)

	class Meta:
		proxy = True

# project2.models
class Project2Photo(Photo):
	thumbnail = ImageSpec(...)
	detail = ImageSpec(...)

	class Meta:
		proxy = True

Aha! Ok, thank you very much.


feat: UI improvements for the "Add to list" modal sheet

Hi everyone!
I was not satisfied with the current modal and there are many changes.
🎥 Here's a video :
https://github.com/user-attachments/assets/641bb36d-159c-49d0-b2fa-10b1e7a044eb

Items are a bit taller (+ 10 pixels) and they have a dashed divider

The Scrollbar is forced when there is something to scroll

The button to add a New list is at the bottom

The "OK" button is always clickable (but will flash red if there's already a list with this name)

There are tooltips on buttons

And the same with the dark mode:

Codecov Report
Attention: Patch coverage is 0% with 175 lines in your changes missing coverage. Please review.

Project coverage is 7.05%. Comparing base (4d9c7fc) to head (056a0e8).
Report is 434 commits behind head on develop.

Files with missing lines
Patch %
Lines

...oth_app/lib/pages/product/product_list_helper.dart
0.00%
129 Missing :warning:

...b/bottom_sheets/smooth_draggable_bottom_sheet.dart
0.00%
33 Missing :warning:

packages/smooth_app/lib/resources/app_icons.dart
0.00%
11 Missing :warning:

...om_sheets/smooth_draggable_bottom_sheet_route.dart
0.00%
1 Missing :warning:

...pages/product/product_page/new_product_footer.dart
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5804      +/-   ##
==========================================
- Coverage     9.54%   7.05%   -2.50%
==========================================
  Files          325     411      +86
  Lines        16411   22318    +5907
==========================================
+ Hits          1567    1574       +7
- Misses       14844   20744    +5900

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Enable colour output from .NET CLI in GitHub Actions

Enable coloured output to the terminal in GitHub Actions (for Linux and macOS).
Discovered via this tweet.

I did not know this! That's really cool


(Not) recognizing absolute path to command

Hi, first of all: Thanks for your work!
I noticed the following inconsistencies between Windows and Mac/Linux:
On Mac/Linux an absolute path to an executable file returns true
e.g. /usr/bin/ssh -> true
On Windows an absolute path is not accepted:
e.g. c:\Program Files\putty\plink.exe -> false
While this just seems to be an inconsistency, the following is certainly a bug:
On Mac/Linux all directories are recognized as "existing commands":
e.g. /usr -> true

I know this was last posted on over a year ago--No clue if you ever figured this out or not.
I have run into the same issue in a project of mine. After digging a bit into the code, it seems the error is because the commandExistsWindows() functions include a RegEx pattern to check for valid file names before testing if the command exists or not. This check will return false if the path given includes a :, which is normally not allowed in a Windows path, but is required for an absolute path, e.g. C:\Program Files\....
I found a better RegEx pattern for matching paths and will try to issue a pull request later today.


The "break" position in "repeat/loop" is not taken in account

Hi,
As said here there can be code before and after the "break" but the code after the "break" is still executed.
Test code :
a = 1
b = 1
#repeat
  '-------------
  'a++
  a = a + 1

  'test
  #if a ≥ 2

    'break
    #break
  #end if

  'b++
  b = b + 1
#loop
'##########
a
b

Result :
a = 1
b = 1
-------------
a++
a = a + 1 = 1 + 1 = 2

test

break

b++                        <------ should not exist
b = b + 1 = 1 + 1 = 2      <------ should not exist

##########
a = 2
b = 2                      <------ must be b = 1

Thank you for pointing this out to us. It is not expected to execute the code after #break and exit on #loop. It is expected to exit immediately on #break, so this is a serious issue. It is interesting how no one, including me, have noticed that so long. However, I fixed it in the last release v5.8.8:

If you have installed it already, unistall it, download it again and make a clean install to get it work.

I reinstalled v5.8.8 and now it works !
Your software is great, glad to help improve it.
Thank you.


React warning on TextField

Warning: TextField contains an input of type text with both value and defaultValue props. Input elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both). Decide between using a controlled or uncontrolled input element and remove one of these props. More info: https://fb.me/react-controlled-components

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I'm still seeing this with 4.1.3.

Can you post your code here?

Hmm... I was setting defaultValue={null}. Removing this fixed the warning. I assume there was a good reason I had that in there, but it doesn't seem to be necessary now.
Not sure if @advance512 is still seeing this warning - perhaps this issue can be closed.

You need to remove the defaultValue={null}.
#60

Is there any solution for this, I wanted both of them


Smoother textures in WebGL

This will make the WebGL look a bit more like the other targets.

In the lines above your change, there's already a flambe_webgl_enable_linear flag to do this.

Hm it's odd, I dont have that in my local version..


Use HTTPS instead of git:// protocol

Github has removed support of the unauthenticated/unencrypted git://
protocol in favour of encrypted protocols.
See https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git

Thank you!


Resource type metrics

Summarize the resource types once every 24 hours.
Emit a CloudWatch metric with each resource type as a different dimension.
Send as anonymous metric.
Provide opt-out in template and/or by disabling CloudWatch rule.

Hourly metrics generated for CloudWatch using 14 different resource types and stack name as dimensions.
Metrics cost about 0.10/mo which totals to about 1.40/mo US$.
Reporting Lambda sends anonymous max inventory size for past 24 hours to Solutions Builders.
Disable anonymous reporting using Mapping in template or disabling Reporting job in EventBridge.

Potential uses for cost tracking or resource management:
Configure anomaly detector alarm for resource counts to alarm when resource counts change suddenly.
Configure max alarm if no more than X channels should be created in a single account.


File writer tests v2

This v2 changes the default permission mode to 420 ( 0644 in octal )

LGTM.

Review status: 0 of 3 files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

Reviewed 3 of 3 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io

This push request was commited sucessfully


Docs Web Page is not working on https://formik.org/docs/overview

🐛 Bug report
Just as the title says. going to https://formik.org/docs/overview returns a 404.

Looks like it's up and running now.

looks better than ever 👍


Error SCRIPT1003: Expected ':'  This is when object deconstruction is used with default values as a function parameter

Example:
Open this in Edge, you will see an error in console
Fiddle: https://jsfiddle.net/c8rfL49t/4/
`
function getHelloFn() {
const helloFn = ((cacheAccessor2, { name = "foo" }) => {
});
return helloFn;
}
`
Version: Microsoft Edge 41.16299.248.0
Same works fine in other browsers (Chrome, Firefox, IE11)

Can confirm the same behavior in EdgeHTML 17 in the latest insider build. We should look into this @curtisman .

I think it is issue with arrow function. As we do reparsing due to arrow function - some of the bookkeeping went wrong.
this seems fine
let b = function(o, {name = 'foo'}) {};

Assigning it to myself.

@psavur thanks for reporting this issue.
It is fixed now.


Fix typo

Hello @dariusz-wozniak, in case you are interested, the follow-up from this project can be found here: https://github.com/WireMock-Net/WireMock.Net

Thank you for the info, @StefH. FYI, I've found the lib while updating the https://github.com/dariusz-wozniak/List-of-Testing-Tools-and-Frameworks-for-.NET. ;-)


Remove example.bundle.js from repository

It makes git diff very hard to read and messes up with pull requests reviews. Doing npm install generates it anyway so people will have it working

:+1:


beve reads empty value, that should be skipped

Hi Stephen,
this code:
#include "glaze/glaze.hpp"
#include "glaze/beve.hpp"

struct test_skip {
     std::optional<char> o_;
};

int main() {
    std::vector<test_skip> a{{},{}};
    std::string		   buffer;
    std::vector<char>      beve_buffer;

    auto err{glz::write_json(a, buffer)};
    auto beve_err{glz::write_beve(a, beve_buffer)};
    assert(!err && !beve_err);

    std::array<test_skip, 2> b{{{false}, {true}}};
    auto beve_b{b};

    err = glz::read_json(b, buffer);
    beve_err = glz::read_beve(beve_b, beve_buffer);
    assert(!err && !beve_err);

    // triggers:
    assert(b[0].o_ == beve_b[0].o_);

    return 0;
}

triggers the last assert here for gcc-14, clang-1[89] on ubuntu 24.04.
Thanks,
Karsten

Thanks for bringing this up. Right now BEVE doesn't adhere to skip_null_members, which it should. Will keep this issue alive until support has been added.

A fix:
diff --git a/include/glaze/beve/read.hpp b/include/glaze/beve/read.hpp
index a3abe46..c21ef1e 100644
--- a/include/glaze/beve/read.hpp
+++ b/include/glaze/beve/read.hpp
@@ -1108,15 +1108,8 @@ namespace glz
             GLZ_END_CHECK();
             const auto tag = uint8_t(*it);

-            if (tag == tag::null) {
+            if (tag == tag::null)
                ++it;
-               if constexpr (is_specialization_v<T, std::optional>)
-                  value = std::nullopt;
-               else if constexpr (is_specialization_v<T, std::unique_ptr>)
-                  value = nullptr;
-               else if constexpr (is_specialization_v<T, std::shared_ptr>)
-                  value = nullptr;
-            }
             else {
                if (!value) {
                   if constexpr (is_specialization_v<T, std::optional>)

So, we actually want to set the value to null if a null value is read in. The reason why your BEVE and JSON do not align right now is that by default JSON serialization uses the option skip_null_members, which means your JSON message will not set the elements to null. If you set skip_null_members to false then the JSON and BEVE would act the same.
The code you posted isn't really a fix. What is needed is skip_null_members support for BEVE so that null fields don't get written and thus don't set your optionals to null when read in.


Add support for decoding as EJson

This seems to suffice for now.
Later on, when it is supported by Quasar, we'll probably want to add another JSONMode for this, and go directly through EJson rather than through the intermediate "precise JSON" encoding. To make that work, it may be necessary to make JSONMode into a GADT, using Leibniz or something.
https://slamdata.atlassian.net/browse/SD-1573

Yeah, good thinking, that trick hadn't occurred to me for some reason, I had briefly thought about how to represent some similar cases, such as a the type of path determining the expected result type for mounts.


preserve selected value on radiolist change

preserve selected value on radiolist change if preventDeselect is set to true

If a radiolist has a selected value with preventDeselect=true, and you set it from code with the same same, the value is deselected


Proposal for @zihotki to join the team

I would like to propose that @zihotki becomes a collaborator.

His feedback on submitted PRs has been, to date, of a high quality
He has been a regular in monitoring PR requests
I think he would be a valuable member of the team.

I believe that if @quozd agrees and @zihotki accepts that this should be a done deal.
Thoughts?

Invite sent.
Welcome on board, @zihotki


Please reach a little Beyond The Bicycle: include hand-tricycles, bakfietsen, etc.

The current image for a cycle lane is a relatively slender individual riding a bicycle, wearing trousers.
When planning for cycling provision, we need to move "beyond the bicycle" and consider cargo tricycles and mobility aids for disabled cyclists.  Consider this slide from a talk at today's ESRC meeting:

Could we have images of these vehicles, with appropriate minimum widths considered?

Seems like a cool idea that promotes planning for accessibility. :+1:


chore: check for pause timeout after errors

@kohlisid - should we move this into "Ready for Review" and maybe @whynowy can review?


Incomplete Map when acessing cities in table osm_places

I have built a system based on
Mapserver 7.4.2
mapserv -v
MapServer version 7.4.2 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
Debian Stretch
Planet PBF Sep 12 10:18 planet-latest.osm.pbf
imposm version 0.8.1
postgresql vers 11
postgis
ii  postgis                              2.5.2+dfsg-1~exp1.pgdg90+1        amd64        Geographic objects support for PostgreSQL
ii  postgis-doc                          2.5.2+dfsg-1~exp1.pgdg90+1        all          Geographic objects support for PostgreSQL -- documentation
ii  postgresql-11-postgis-2.5            2.5.2+dfsg-1~exp1.pgdg90+1        amd64        Geographic objects support for PostgreSQL 11
ii  postgresql-11-postgis-2.5-scripts    2.5.2+dfsg-1~exp1.pgdg90+1        all          Geographic objects support for PostgreSQL 11 -- SQL scripts
Part of the Chinese mainland is blank when the cities class of the places layer is used with encoding utf8
When using utf-16, all cities are missing, but the map is complete.
When using ascii, all non western labels are replaced with a citycircle symbol all other ie Paris are ok.
(ie chinese and russian language labels are missing)
No errors are apparent when running the mapserver
iconv is installed
removing the cities class, the problem is not apparent.
I am unsure if this is imposm or mapserver issue.

places.map
places.map.txt

Work Around
Imposm - Loaded places using a mapping to include name and English name. (pbf appears to also have other languages in the file)
Psql - Updated name column with English name.
Result, map displays, Chinese/Russian/Arabic names are in English.
Names without a corresponding English name  are displayed as a number of small rectangles.


inter-device move failed

The error below was reported by @UberActivist, anyone else came across it so far?

Don't have time to investigate right now, so any help would be appreciated. The problem looks like it's coming from here but I'm not sure why mv fails...

@icflorescu hi, yeah. I've also came across.
if I push to the repository and wait for it to restart, then usually it fails to restart, then I wait for a while and type rhc app stop myAppName then I got the same error.

@burib @UberActivist - I think I've fixed it.
Try to recreate your applications again and let me know how it goes.
Unfortunately there's no way to upgrade your existing deployments, so you'll have to do it from scratch...

I was finally able to get my Discord bot to run using it. So yay, I believe it's fixed.

Glad to hear!

@UberActivist  I got the same error, how do you fix it?

@chenkehxx As far as I'm aware, I just recreated the app. There was an issue with an earlier version.

Yes, AFAIK there's no way to upgrade custom OpeShift cartridges, so you'll have to recreate your deployment.

@UberActivist @icflorescu  Thanks


Auth provider

Fixes #25
This is a first stab at an AuthProvider API. This has evolved a bit from the initial proposal in #25.

AuthProvider is not an abstract class, but a base implementation that is maximally generous.
okToReceive has been removed[^1], and okToSend has been renamed to okToSync.
A transform property has been added, consisting of inbound and outbound message transformers. This allows an AuthProvider to encrypt subsequent traffic as part of its authentication scheme.

Usage
These examples are all present in the tests.
Adding an AuthProvider to a repo
const permissive = new AuthProvider() // AuthProvider is maximally permissive by default

const aliceRepo = new Repo({
  network: [new MessageChannelNetworkAdapter(aliceToBob)],
  peerId: "alice" as PeerId,
  authProvider: permissive
})

Restricting access by peer
const authProvider = new AuthProvider({
  okToAdvertise: async (peerId: PeerId) => peerId !== "peer1",
})

Restricting access by document
const handle = collection.create()
const authProvider = new AuthProvider({
  okToAdvertise: async (_, documentId) => documentId !== handle.documentId,
})

Restricting access by peer and document
class NotForCharlieAuthProvider extends AuthProvider {
  excludedDocs: DocumentId[] = []

  // make sure that charlie never learns about excluded documents
  notForCharlie: SharePolicy = async (peerId, documentId) => {
    if (this.excludedDocs.includes(documentId!) && peerId === "charlie")
      return false
    return true
  }

  okToAdvertise = this.notForCharlie
  okToSync = this.notForCharlie
}

const authProvider = new NotForCharlieAuthProvider()

const notForCharlieHandle = aliceRepo.create<TestDoc>()
const notForCharlie = notForCharlieHandle.documentId
authProvider.excludedDocs.push(notForCharlie)

Maximally restrictive AuthProvider
const restrictive = new AuthProvider({
  authenticate: async () => {
    return {
      isValid: false,
      error: new Error("nope"),
    }
  },
  okToAdvertise: async () => false,
  okToSync: async () => false,
})

In the above example, the provider is customized by passing  authenticate etc. in a config object to the base class's constructor. Alternatively, a reusable custom provider can be created by extending the base class:
class RestrictiveAuthProvider extends AuthProvider {
  authenticate = async () => {
    return {
      isValid: false,
      error: new Error("nope"),
    }
  }
  okToAdvertise = async () => false
  okToSync = async () => false
}
const restrictive = new RestrictiveAuthProvider()

Using network communication
We'll make a (very insecure) password auth provider that sends a password challenge, and compares the password returned to a hard-coded password list.
class PasswordAuthProvider extends AuthProvider {
  // The auth provider is initialized with a password response, which it will provide when
  // challenged.
  constructor(private passwordResponse: string) {
    super()
  }

  #challenge = "what is the password?"

  #passwords: Record<string, string> = {
    alice: "abracadabra",
    bob: "bucaramanga",
  }

  authenticate: AuthenticateFn = async (peerId, channel) => {
    return new Promise<AuthenticationResult>(resolve => {
      // send challenge
      channel.send(new TextEncoder().encode(this.#challenge))

      channel.on("message", msg => {
        const msgText = new TextDecoder().decode(msg)
        switch (msgText) {
          case this.#challenge:
            // received challenge, send password
            channel.send(new TextEncoder().encode(this.passwordResponse))
            break

          case this.#passwords[peerId]:
            // received correct password
            resolve(AUTHENTICATION_VALID)
            break

          default:
            // received incorrect password
            resolve(authenticationError("that is not the password"))
            break
        }
      })
    })
  }
}

Transforming network traffic
The idea here is that rather than authenticate peers, the auth provider encrypts and decrypts messages using a secret key that each peer knows. No keys are revealed, but the peers can only communicate if they know the secret key.
function encryptingAuthProvider(secretKey: string) {
  return new AuthProvider({
    transform: {
      inbound: payload => {
        const decrypted = decrypt(payload.message, secretKey)
        return { ...payload, message: decrypted }
      },
      outbound: payload => {
        const encrypted = encrypt(payload.message, secretKey)
        return { ...payload, message: encrypted }
      },
    },
  })
}

[^1]: okToReceive would have misled developers to think that you could enforce write permissions that way; but the peer who shares document changes with you isn't necessarily the peer who made the changes. Write permissions would need to be implemented some other way — for example, the way crdx does, with cryptographic proof of authorship embedded into the CRDT.

I'm closing this for now; I'll rebase on latest code and resubmit.


Cascade delete Payment Allocations when related Payment is deleted

When a Payment record is deleted its related Allocations records become orphaned. This can cause incorrect GAU rollup calculations.

**lurch: attach W-027724

Tracking W-027724

Included in beta release 3.145 (Beta 32)


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/330 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit b2146a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


tell the user when a newer validator image is available, and help them move to it

atm, if you have a validator container, there's nothing to tell you it needs to be removed so you can pick one of the new ones.

and as per #257 - figure out how we detect what SolanaFoundation's today's "please use this version" is - we've hardcoded 1.10.31 for 0.4.0 :)

Feels like this one will closely be related to https://github.com/workbenchapp/solana-workbench/issues/243, since more common create/destroy containers will exacerbate the state issue


the use of methode .zero? in lib/grape/middleware/*.rb generate errors

This morning I update the grape gem (0.18.0 to 0.19.0) and after that all my API don't work.
After some test I found that error comes from last commit on lib/grape/middleware/versioner/path.rb file
https://github.com/ruby-grape/grape/commit/1f8809fad26af4382a9ceb2250b9b07b6f58f6a6#diff-22ee51f406faebc9ea629d8f8ef111e3
if i change line
if prefix && path.index(prefix).zero?
by
if prefix && path.index(prefix) == 0
all works fine ...
For information i use Rails 4.0.9 with ruby 2.1.0p0

Sorry about that. Can you please dig up where we're getting the definition of .zero? from? Would like a PR that fixes that of course.

presence of .zero? is in 2 files who had been commited 15 days ago.
the commit hash is 1f8809fad26af4382a9ceb2250b9b07b6f58f6a6

I mean where we get it from when it works, ie. ActiveSupport or something like that.
What I really want is a spec that reproduces this problem in Grape, then a fix and full understanding of why we cannot use .zero? here.

Write a spec in grape that reproduces this next.

Fixed via https://github.com/ruby-grape/grape/pull/1548.


Output instead of Open

Added an option to only output the link instead of directly opening it.
Could be interesting for other tools that want to run make-me-lol and display the output somewhere.
I didn't change the package version

@xremix yep this is a great idea man! I left one comment but will merge soon as it's addressed!
Thanks for contributing! :+1:

Oups, fixed it.
For sure, nice idea btw.


Xcode 8 beta 6

Not sure what you're asking here

If you update Xcode 8 with the version released yesterday you will see several changes are needed.

I can elaborate. Many of the issues can be fixed automatically with Editor | Fix All in Scope (Ctrl+Option+Command+F), however, the unsafe pointer syntax needs some attention and I'm not sure how to satisfy the compiler:

We fixed it for Alamofire yesterday. Please check.
https://github.com/elm4ward/Alamofire/commit/7f74c6dcdc249c7d9cf2f742441c91ad9f2f8981#diff-f2ea78e6e262089f9f5c5b13cd9121db

Thanks for your comments - I just pushed an update
Ash


Added sort and thenSort directives to FunctionCompiler

Although can use morph (new SortList<T>()) to achieve the same
function, but I think sort is a very common function, should not let
each person alone to achieve a SortList Function. So I added the sort and thenSort
directives to make it more convenient.

I signed it!

[Current coverage][cc-pull] is 98%

Merging [#66][cc-pull] into [master][cc-base-branch] will increase coverage by <1%

@@             master        #66   diff @@
==========================================
  Files            39         39
  Lines          1480       1489     +9
  Methods           0          0
  Messages          0          0
  Branches        253        253
==========================================
+ Hits           1446       1455     +9
  Misses           15         15
  Partials         19         19

[][cc-pull]

Powered by Codecov. Last updated by [3b1697c...0d6f39d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/google/agera/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/google/agera/compare/3b1697cf8a135a0d640dcc4e60791281249d8258...0d6f39de04d2382c4e96df8bd05d544c9407ec13
[cc-pull]: https://codecov.io/gh/google/agera/pull/66?src=pr

Looks pretty cool, just a few minor comments!

Thank you. I've fixed them.


Upgrade go version and dependencies

Version bumps

Realized  after opening that a version bump isn't quite needed/desired yet.


--template=tailwind  Deleting the chrome_url_overrides configuration in the manifest.json file causes an error

Implementation process
When I create a new project using the template command：
npx extension create test-extensions-tem --template=tailwind
I don't need a page to overlay the Google Chrome homepage，So I deleted the chrome_url_overrides configuration in the manifest.json file
Before deletion
{   "manifest_version": 3,   "version": "1.0",   "name": "test-extensions-tem",   "description": "An extension template using Tailwind. This template includes a new tab override.",   "icons": {     "16": "public/icons/icon_16.png",     "48": "public/icons/icon_48.png"   },   "chrome_url_overrides": {     "newtab": "newtab/index.html"   } }
After deletion
{   "manifest_version": 3,   "version": "1.0",   "name": "test-extensions-tem",   "description": "An extension template using Tailwind. This template includes a new tab override.",   "icons": {     "16": "public/icons/icon_16.png",     "48": "public/icons/icon_48.png"   } }
After deleting it, I restarted the entire project. When I opened a new tab, it prompted:

无法访问您的文件该文件可能已被移至别处、修改或删除。ERR_FILE_NOT_FOUND == Unable to access your file The file may have been moved, modified, or deleted. ERR_FILE_NOT_FOUND
Why can't I delete the chrome_url_overrides configuration? How can I solve this problem?

hi @ApacheAlpha thanks for reporting!
it seems a cache thing. what happens when you reload the extension in the browser?

@ApacheAlpha I did several updates to the project since the last message. Could you try again and let me know if it is still broken? Also, new template names in v2 https://extension.js.org/docs/getting-started/templates

Thank you for your hard work on this framework.
Here is my testing process:
First I used the command:
npx extension create test-extensions-new-react --template=new-react
The results are shown in the figure

I opened the entire project using the Vscode editor and then executed
npm run dev
When I open a new browser tab, the entire interface is displayed normally

I stopped the whole project using Ctrl + C, then went into manifest.json and deleted Configuration
"chrome_url_overrides": {
"newtab": "newtab/index.html"
},
Then I started the project using the command: npm run dev and I found the first problem
Why is the browser homepage still overwritten in the newly opened tab? I deleted the configuration of overwriting the homepage and ran the command: npm run dev to restart. Is the previously built plugin configuration still effective?

I think after restart, the files in dist folder are not updated or changed. The dist folder is not the latest extension。Why is this happening?
So I stopped the project, deleted the dist folder under the project folder, and restarted the project again using npm run dev.
When I open a new tab, I get the same problem as before

To avoid cache issues, I cleared all past browser data, so I don't think it has anything to do with cache.
无法访问您的文件该文件可能已被移至别处、修改或删除。ERR_FILE_NOT_FOUND == Unable to access your file The file may have been moved, modified, or deleted. ERR_FILE_NOT_FOUND
New findings
1、When creating a new project, first delete "chrome_url_overrides": {"newtab": "newtab/index.html"}, then execute npm run dev, the problem mentioned above will not occur. What is the reason?
2、I deleted node_modules and reinstalled it, which also solved the problem mentioned before. Why?
I hope my content is helpful to you

hey @ApacheAlpha thanks for kind words and the detailed write-up, it ended up being the very issue you found and I'm happy to say it's fixed in the current release 👍
let me know how it goes on your end!

@cezaraugusto
Thank you for your hard work. After my test, I found that the problem has not been solved. My execution process is as follows.
The first step is to execute the command:
 npx extension create test-extensions-new-react --template=new-react

The second step is to open the project file and execute the command: npm run dev

The third step is to delete the project configuration file:
  "chrome_url_overrides": {     "newtab": "newtab/index.html"   },
Use Ctrl + C to stop the project  then execute the command: rm -rf dist && npm run dev
When I open a new tab ，The problems mentioned above still exist

Sorry, I mean no harm.
New findings
I found that if I delete the node_modules file first, then install npm i and then execute the command rm -rf dist && npm run dev  There won't be any problem. So I think this problem is closely related to your Extension library.

thanks again @ApacheAlpha, that's an interesting behavior. not sure the fix yet but will update the issue title to reflect the current bug.


Too many search results

I don't know what exactly is going wrong but I noticed a pattern which may point to some bug with the search.
Expected
When searching for minutor or lutris I get 0-10 results roughly. Probably 0 since those package don't seem flatpakked yet.
Actual
When searching for minutor or lutris I get 1212 search results. Recently it changed to 1213 search results. Both strings are unlikely to be in the descriptions of all of those packages and those package pages I tried did not yield a result to CTRL+F and "minutor" or "lutris".

Searching teeworl yields the same result. Agree this should be addressed as it may turn away new users when the website seemingly fails as it tries to load over 1000 results.

For me, it loads the 1000+ results perfectly - just that I was instead expecting to either get a clear "no such package" or a list of matches. It is confusing and looks broken.

I have no idea, when it might be migrated or when/if somebody is still maintaining the old backend. Sorry.

I've checked the new site with the search you supplied and it correctly returns zero results.


Implement a bases api and rework abstract types

This PR implements the proposal in #26 and thus would close #25 and #26. I've also marked all remaining offending instances of #12 as FIXME for now as I think resolving those should be kept separate from this PR.
The remaining TODOs for this PR are then

[ ] Figure out how to reference pages in https://github.com/qojulia/QuantumOptics.jl-documentation in the docstrings here (related to #5 and #6).
[ ] Address #27.
[ ] Update QuantumOpticsBase.jl based on this branch and ensure all tests pass.
[ ] Update everything else downstream and ensure tests pass (QuantumOptics.jl, QuantumCumulants.jl, WaveguideQED.jl, CollectiveSpins.jl, QuantumSymbolics.jl, QuantumClifford.jl, QuantumSavory.jl, Gabs.jl, anything else?)
[ ] Create CHANGELOG.md and bump version to v1

@apkille  , just a heads up that this is happening and it might lightly affect Gabs.jl


Storing polygons as array is messing with $geoIntersects

When storing a polygon field as array, searching all points within the polygon, as well as intersecting 2 polygons works.
But finding all polygons including a particular point does not work when the polygon field is an array, and seems to works only when the polygon is store as GeoJSON object.
To reproduce:
db.geom.insert({"polygons":
  {"type":"Polygon",
     coordinates:
      [[[ 17.60083012593064, 78.18557739257812],
        [ 17.16834652544664, 78.19381713867188],
        [ 17.17490690610013, 78.739013671875],
        [ 17.613919673106714, 78.73489379882812],
        [ 17.60083012593064, 78.18557739257812]
      ]]
  }, "coo": [[ 17.60083012593064, 78.18557739257812],
        [ 17.16834652544664, 78.19381713867188],
        [ 17.17490690610013, 78.739013671875],
        [ 17.613919673106714, 78.73489379882812],
        [ 17.60083012593064, 78.18557739257812]
      ]
});

This works
db.geom.find({polygons:
  {$geoIntersects:
     {$geometry:{ "type" : "Point",
          "coordinates" : [ 17.3734, 78.4738 ] }
      }
  }
});

This does not work
db.geom.find({coo:
  {$geoIntersects:
     {$geometry:{ "type" : "Point",
          "coordinates" : [ 17.3734, 78.4738 ] }
      }
  }
});

A solution is to store the polygon as a geoJSON object.
Is there any reason it's stored as a plain array, or is it safe to migrate all the geo field to GeoJSON object ?

@wa0x6e yup, my bad! Let/s geoJSON em.
If you fixed, please pull request, I'll merge and release.

How do the maintainers see this working? Would the gem just switch the classes in place to use GeoJSON and leave the migration up to users? Include a rake task to migrate? Or add new field classes that read/write as GeoJSON?


[SPARK-11216][SQL][follow-up] add encoder/decoder for external row

address comments in https://github.com/apache/spark/pull/9184

Merged build triggered.

Merged build started.

Test build #44120 has started for PR 9212 at commit 705dbfb.

Test build #44120 has finished for PR 9212 at commit 705dbfb.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * case class CreateExternalRow(children: Seq[Expression]) extends Expression \n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44120/
Test PASSed.

cc @marmbrus

Thanks, merging to master.


Add authentication routes

Add authenticated routes to block access to private pages

Possible state managers:

Redux with pure component

Possible state managers:

Redux with pure component


fix for cmake issue on 2021.2 release

Description
Fixes # fixed PV reported issue for oneCCL on 2021.2
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Sample Migration (Moving sample from old repository after completing checklist established)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[X ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[ ] VSCode

Checklist for Moving samples:
Links and Details can be found in the samples WG Teams Files.

[ ] Review sample design with domain reviewers https://github.com/oneapi-src/oneAPI-samples/wiki/Reviewers-and-Domain-Experts
[ ] Implement coding guidelines and ensure code quality.
[ ] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[ ] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com
[ ] Adhere to readme template
[ ] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[ ] Enforce format via clang-format config file
[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth or Joe Oster. (GitHub User: JoeOster)
[ ] Tested using Dev Cloud when applicable
[ ] Implement fixes for ONSAM Jiras
[ ] If you have new dependencies/binaries, inform Samples Project Manager Swapna R Dontharaju (@srdontha) or @JoeOster

@louie-tsai - any ideas in regards to error messages?

couldn't reproduce in PV's machine.

OS
Machine name
Login/password

Ubuntu 18.04
nntcl38-qcht.inn.intel.com
root   spdlab

The built sample binaries are under ~/oneapi-samples/louie-tsai/oneAPI-samples/Libraries/oneCCL/oneCCL_Getting_Started/build folder.

I tried again today.  the new changes still work fine on PV machine.
Could you double check in your env and merge the PR if possible?


Missing documentation on CDS instance templates

I'm trying to find out whether it's possible to provision a CDS instance for an environment while also setting the domain at the same time. My best guess is that if it's possible, it might be through provisioning templates, but I was unable to find any documentation on what they are or how to use them.

Hi Imi,
Have a look at https://learn.microsoft.com/en-us/power-platform/admin/create-environment and https://learn.microsoft.com/en-us/power-platform/admin/create-database.
If that documentation is insufficient, then open another issue there.

Chris


Mac Issue with Mic

As i notice @WinterPu You updated the readme with an update for unreal 5 with mac.
I tried this, however, when opening the plist within unreal at the path you mentioned, there is already a mic permission mentioned there.
Unsure of what to do with that.
At the moment we have no mic access on mac.

That is used to add the Camera permission. I noticed that if you directly change the info.plist in your app, it may not work well 佛for UE5. Another way to do it is by modifying the info.plist template in the Build/Mac/Resources folder under your project.

I dont seem to have a Build/Mac/Resources in my project folder. Should i make it?

No, in this case, which version of UE are you using?

Im using UE5.2.

Post build, i have been running this:
write_note(f'Adding plist entries in: {app_path}')
os.system("/usr/libexec/PlistBuddy -c \"Add :NSCameraUsageDescription string Required for videos so others can see you\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Add :NSMicrophoneUsageDescription string Required for voice to talk to others\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Add :NSPhotoLibraryUsageDescription string Required for Avatar Manager\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Add :NSPhotoLibraryAddUsageDescription string Required for Avatar Manager\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Set :CFBundleVersion "+str(package_version)+"\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Set :CFBundleShortVersionString "+str(package_version)+"\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)
os.system("/usr/libexec/PlistBuddy -c \"Add :LSApplicationCategoryType string public.app-category.education\" "+app_path+"/Contents/Info.plist >> "+mac_log_file)

This issue still persists. Have changed the engine plist as well, changed project plist as well. Can connect to voice channel, but no one can hear me.

You could try [tccutil reset Microphone] to reset the permission and see if it works. Additionally, could you identify if this is a permission problem? Does it work in PIE (Play in Editor)？

Just tested.
tccutil reset Microphone didnt do anything for me.
However, voice did work in the editor just fine during PIE

When you changed the info.plist template of your engine, did the app you packaged have the required permission? It should have.

Hey @WinterPu
Did you manage to figure this one out? Im still crashing.

I have no idea. How did you conclude that this crash is related to the SDK?

Is libtbb.dylib not part of the agora package?
Reason: tried: '/Users/raahilkulshreshtha/Documents/Projects/Surrogate/Packages/Build5.7_2024_08_09_03/Mac/Main/Surrogate.app/Contents/UE/Engine/Binaries/Mac/CrashReportClient.app/Contents/MacOS/libtbb.dylib' (no such file), '/Users/raahilkulshreshtha/Documents/Projects/Surrogate/Packages/Build5.7_2024_08_09_03/Mac/Main/Surrogate.app/Contents/UE/Engine/Binaries/Mac/CrashReportClient.app/Contents/MacOS/libtbb.dylib' (no such file), '/Users/raahilkulshreshtha/Documents/Projects/Surrogate/Packages/Build5.7_2024_08_09_03/Mac/Main/Surrogate.app/Contents/UE/Engine/Binaries/Mac/libtbb.dylib' (no such file), '/Users/raahilkulshreshtha/Documents/Projects/Surrogate/Packages/Build5.7_2024_08_09_03/Mac/Main/Surrogate.app/Content

Doesn't seem like
https://en.wikipedia.org/wiki/Threading_Building_Blocks

This was fixed. For anyone wanting to know how, you need to update both the plist and the entitlements now.


Persistent secret key for Flask app

Current Flask secret key is dynamically generated on application startup (start/restart). Unfortunately, each time secret key generated with different value, CSRF token used in form will be invalid thus raises missing session CSRF token. Note, similar issue with secret key mismatch will also affect cookie, session, or any Flask plugin that relies on secret key.
There should be a way to use persistent value for secret key.
Things to consider:

app should support for re-using secret key from file (i.e. mounted file)
app can generate new key if there's no existing secret key
hardcoding in source code is an anti-pattern (except for development)

This issue also raised when using multiple Gunicorn workers.


Add a link to Contribution Guidelines in the README.md file

Adding a link that leads to the contribution guidelines because in case of slow network the image fails to load

please assign me to this task

Hey @bukolastella
Thanks for bringing this to our notice and welcome to our project.
After close inspection, we concluded that this problem is arising due to the network connection issues at times and it is independent of the readme's markdown code written for the repo where we have the images and as well as the link for the contributing.md guidelines.
Do let us know if there are any queries, we would be happy to help out.

Alright, I was thinking adding a link inline will be good, so in the case of screenshot above you can click on it instead of waiting for the image to load

One suggestion you could do is add alt="Mentor Name Here" and use and  <img> tag instead of Github's default image call.
@smaranjitghose what say?

@anushbhatia . That makes sense.
@bukolastella Would you like to give a PR for this?

@smaranjitghose  yes,sure


Items are lost when left in the crafting grid

Vanilla Tweaks Version:
1.4.8
MinecraftForge Version:
<IP_ADDRESS>31
Minecraft Version:
1.12.2
(Optional) Just Enough Items (JEI) Version:
<IP_ADDRESS>8
(Optional) Baubles Version:
1.12-1.5.2
Client or Server?:

[x] Client
[x] Server

Crash Report (via. Hastebin):
N/A
What happens / happened?:
Items are lost when leaving the crafting pad GUI
How can the issue be reproduced?:
Download Life in the Village modpack (version 1.12 - current as of Aug. 15, 2019). Using the crafting pad and leaving anything inside it, either an uncrafted result, or just items.
What should happen?:
The crafting pad doesn't seem to use a normal crafting GUI. For instance, JEI doesn't get dimmed, and items don't have tooltips.
Mod List:
Life in the Village modpack (version 1.12)
Hopefully the addition of a modlist should help the issue be reproduced.

Update to latest version of the mod.

This is still an issue!
With the latest version (1.5.5) for minecraft 1.12, the craftingpad still loose items left in the pad when exiting the gui.

Its an compatibility issue with a mod called real bench that i cant fix.