Fluid not working with PCF

Describe the bug
We had a requirement to push some real time data to custom PCF "power apps component framework" component. We choose fluid to utilize its abstraction to do that kind of communication specially we are using react for that
The component is working fine on the PCF local environment but when it is deployed to power apps canvas application it fails after short time with "Too Many Clients Connected to Document" exception. It seems for some reasons it went inside an infinite loop and make many calls to the fluid relay until it fails
To Reproduce
Steps to reproduce the behavior:

Create a new PCF component
Use any basic fluid sample
Deploy the solution to power apps and use it in Canvas app
Try to load fluid container

Expected behavior
Fluid should work in a normal way without opening to many fluid sessions and without failure
Logs
Fluid Log {"eventName":"fluid:telemetry:Container:CreateDetached_start","category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:CodeLoad_end","duration":0,"category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:AttachmentBlobsLoaded","count":0,"category":"generic","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:DeviceSpec","deviceMemory":8,"hardwareConcurrency":8,"category":"generic","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:ContainerLoadStats","createContainerRuntimeVersion":"1.2.5","createContainerTimestamp":1663095265354,"containerLoadDataStoreCount":0,"referencedDataStoreCount":0,"summaryNumber":0,"category":"generic","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:CreateDetached_end","duration":15,"category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Request_end","duration":1,"category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:212 Create Container
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Attach_start","category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","containerAttachState":"Detached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Attach_end","duration":1384,"category":"performance","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:219 Container attached:  7af38769-7911-49b5-b9b1-97ba3ea61c48
2FluidController.ts:307 Pushed value test
FluidController.ts:168 Fluid Log {"attempts":1,"delay":1000,"eventName":"fluid:telemetry:ConnectionManager:DeltaConnectionFailureToConnect","duration":22019,"online":"Online","connectionType":"unknown","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:127:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:586:107)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:69:20)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:500:30)","error":"socket.io (orderingServiceHandshakeTimeout): undefined","errorType":"genericNetworkError","fluidErrorCode":"-","driverVersion":"1.2.5","canRetry":true,"message":"socket.io (orderingServiceHandshakeTimeout): undefined","errorInstanceId":"e92d3676-652b-4e13-bd18-bcc045ebb761","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":0,"dmLastKnownSeqNumber":0,"connectionStateDuration":22020.5,"loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Load_start","category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:RouterliciousDriver:getWholeFlatSummary_end","treeId":"latest","size":18,"duration":691,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","driverVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"reason":"DocumentOpen_fetch","eventName":"fluid:telemetry:DeltaManager:ExtraStorageCall","early":true,"from":1,"to":0,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:CodeLoad_end","duration":0,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:AttachmentBlobsLoaded","count":0,"category":"generic","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:DeviceSpec","deviceMemory":8,"hardwareConcurrency":8,"category":"generic","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:ContainerLoadStats","createContainerRuntimeVersion":"1.2.5","createContainerTimestamp":1663095265354,"containerLoadDataStoreCount":1,"referencedDataStoreCount":1,"summaryNumber":1,"summaryFormatVersion":1,"gcVersion":1,"category":"generic","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Load_end","sequenceNumber":0,"version":"bBwAAAAAHAAAA","duration":995,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Loader:Resolve_end","duration":996,"category":"performance","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Request_end","duration":4,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:263 Get Container
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:ConnectionStateChange_CatchingUp","from":"Disconnected","duration":924,"connectionInitiationReason":"InitialConnect","pendingClientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","online":"Online","checkpointSequenceNumber":0,"quorumSize":0,"sequenceNumber":0,"socketDocumentId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","connectionMode":"write","category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"CatchingUp","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:RouterliciousDriver:getDeltas_end","from":1,"to":2001,"count":0,"duration":249,"category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"CatchingUp","driverVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:ConnectionStateChange_Connected","from":"CatchingUp","duration":882,"durationFromDisconnected":1806,"connectionInitiationReason":"InitialConnect","pendingClientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","clientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","online":"Online","quorumSize":1,"sequenceNumber":1,"socketDocumentId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","connectionMode":"write","category":"performance","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:271 Container resolved
FluidController.ts:317 Shared Map Received value undefined
FluidController.ts:283 Container connected
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:OpsSentOnReconnect","count":0,"category":"generic","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:SummaryManager:CreatingSummarizer","throttlerDelay":0,"initialDelay":5000,"startThrottlerMaxDelayMs":30000,"opsSinceLastAck":1,"opsToBypassInitialDelay":4000,"category":"generic","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","runtimeVersion":"1.2.5","clientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Load_start","category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Detached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"reason":"DocumentOpen_fetch","eventName":"fluid:telemetry:DeltaManager:ExtraStorageCall","early":true,"from":1,"to":0,"category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:CodeLoad_end","duration":0,"category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:ContainerRuntime:GarbageCollector:GarbageCollectorLoaded","gcConfigs":"{"gcEnabled":true,"sweepEnabled":false,"runGC":true,"runSweep":false,"writeAtRoot":true,"testMode":false,"inactiveTimeout":604800000,"existing":true,"trackGCState":false}","category":"generic","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","completedGCRuns":0,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:AttachmentBlobsLoaded","count":0,"category":"generic","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:DeviceSpec","deviceMemory":8,"hardwareConcurrency":8,"category":"generic","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:ContainerLoadStats","createContainerRuntimeVersion":"1.2.5","createContainerTimestamp":1663095265354,"containerLoadDataStoreCount":1,"referencedDataStoreCount":1,"summaryNumber":1,"summaryFormatVersion":1,"gcVersion":1,"category":"generic","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loading","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Load_end","sequenceNumber":0,"version":"bBwAAAAAHAAAA","duration":310,"category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:Request_end","duration":0,"category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:RouterliciousDriver:getDeltas_end","from":1,"to":2001,"count":116,"duration":197,"category":"performance","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","driverVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"error":"0x114","eventName":"fluid:telemetry:DeltaManager:GetDeltas_Exception","category":"error","stack":"Error\n    at assert (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/common-utils/lib/assert.js?:19:11)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:424:75)\n    at Generator.next ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:17:103)\n    at _next (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:194)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:364)\n    at new c.Class.derive._oncancel (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:44584)\n    at new e (https://content.powerapps.com/resource/app/nmg89fdhupvv7/publish/js/pa.core.bundle3.js:62:620397)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:97)\n    at Queue.read (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:439:7)","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":206.7999999821186,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Container:ContainerClose","category":"error","stack":"Error\n    at assert (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/common-utils/lib/assert.js?:19:11)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:424:75)\n    at Generator.next ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:17:103)\n    at _next (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:194)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:364)\n    at new c.Class.derive._oncancel (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:44584)\n    at new e (https://content.powerapps.com/resource/app/nmg89fdhupvv7/publish/js/pa.core.bundle3.js:62:620397)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:19:97)\n    at Queue.read (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/parallelRequests.js?:439:7)","error":"0x114","errorType":"genericError","fluidErrorCode":"-","untrustedOrigin":1,"message":"0x114","errorInstanceId":"33157235-c7bf-4b53-9027-6acdb7f8217b","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":209.2999999821186,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:ContainerRuntimeDisposed","isDirty":false,"lastSequenceNumber":116,"attachState":"Attached","category":"generic","stack":"Error\n    at Container.closeCore (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:721:100)\n    at DeltaManager.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:1526:12)\n    at DeltaManager.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/events/events.js?:145:5)\n    at DeltaManager.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/deltaManager.js?:549:10)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/deltaManager.js?:863:16)\n    at Generator.throw ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/deltaManager.js?:19:103)\n    at _throw (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/deltaManager.js?:21:291)\n    at Object.q [as _notify] (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:38070)\n    at Object.enter (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:41571)","error":"0x114","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"closing","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":211.2999999821186,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:Summarizer:StoppingSummarizer","onBehalfOf":"7c740d81-5927-4ccb-8b60-71eb27c4103e","reason":{"key":"0","value":{"_nextState":null,"_state":{"name":"complete_notify","done":null,"then":null},"_listeners":null,"_value":"summarizerClientDisconnected"}},"category":"generic","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"closing","containerConnectionState":"Disconnected","runtimeVersion":"1.2.5","loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:SummaryManager:RunningSummarizer_cancel","attempt":1,"category":"generic","duration":198,"stack":"Error\n    at assert (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/common-utils/lib/assert.js?:19:11)\n    at Container.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:697:73)\n    at ContainerRuntime.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:1822:528)\n    at Summarizer.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:254:18)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:235:16)\n    at Generator.next ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:23:103)\n    at _next (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:25:194)\n    at Object.p [as _notify] (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:37490)\n    at Object.enter (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:41064)","error":"0x314","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","runtimeVersion":"1.2.5","clientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":5525.9000000059605,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:SummaryManager:EndingSummarizer","reason":"exception","category":"generic","stack":"Error\n    at assert (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/common-utils/lib/assert.js?:19:11)\n    at Container.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:697:73)\n    at ContainerRuntime.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:1822:528)\n    at Summarizer.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:254:18)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:235:16)\n    at Generator.next ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:23:103)\n    at _next (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:25:194)\n    at Object.p [as _notify] (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:37490)\n    at Object.enter (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:41064)","error":"0x314","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","runtimeVersion":"1.2.5","clientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":5526.800000011921,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:SummaryManager:SummarizerException","category":"error","stack":"Error\n    at assert (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/common-utils/lib/assert.js?:19:11)\n    at Container.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:697:73)\n    at ContainerRuntime.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-loader/lib/container.js?:1822:528)\n    at Summarizer.close (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:254:18)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:235:16)\n    at Generator.next ()\n    at asyncGeneratorStep (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:23:103)\n    at _next (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/container-runtime/lib/summarizer.js?:25:194)\n    at Object.p [as _notify] (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:37490)\n    at Object.enter (https://content.powerapps.com/resource/app/s5i89talcktdc/js/winjs/base.js:2:41064)","error":"0x314","clientType":"interactive","containerId":"d106d462-6e97-4a26-b878-3ce8eef06494","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","runtimeVersion":"1.2.5","clientId":"7c740d81-5927-4ccb-8b60-71eb27c4103e","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":5527.4000000059605,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"attempts":1,"delay":1000,"eventName":"fluid:telemetry:ConnectionManager:DeltaConnectionFailureToConnect","duration":947,"online":"Online","connectionType":"unknown","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:124:12)\n    at createR11sNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:46:101)\n    at errorObjectFromSocketError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:75:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:67:85)\n    at Socket.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:493:30)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)\n    at Socket.emitEvent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:342:16)\n    at Socket.onevent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:327:12)\n    at Socket.onpacket (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:290:14)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)","error":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorType":"throttlingError","fluidErrorCode":"-","statusCode":429,"driverVersion":"1.2.5","retryAfterSeconds":300,"canRetry":true,"message":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorInstanceId":"3dd6141e-94cd-4182-9aed-758f223d9d9b","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"closed","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":947.1999999880791,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:DeltaManager:WrapError","errorInstanceId":"3dd6141e-94cd-4182-9aed-758f223d9d9b","wrappedByErrorInstanceId":"3dd6141e-94cd-4182-9aed-758f223d9d9b","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:124:12)\n    at createR11sNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:46:101)\n    at errorObjectFromSocketError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:75:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:67:85)\n    at Socket.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:493:30)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)\n    at Socket.emitEvent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:342:16)\n    at Socket.onevent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:327:12)\n    at Socket.onpacket (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:290:14)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)","error":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorType":"throttlingError","fluidErrorCode":"-","statusCode":429,"driverVersion":"1.2.5","retryAfterSeconds":300,"canRetry":true,"message":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","clientType":"noninteractive/summarizer","containerId":"9175e5a9-433d-4171-a3cb-4b86dd690a5c","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"closed","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":116,"dmLastKnownSeqNumber":116,"containerLoadedFromVersionId":"bBwAAAAAHAAAA","dmLastMsqSeqNumber":116,"dmLastMsqSeqTimestamp":1663095297151,"dmLastMsqSeqClientId":null,"connectionStateDuration":957.1999999880791,"loaderId":"b0a1a2f1-e655-425c-adff-450a35e0126e","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"attempts":2,"delay":2000,"eventName":"fluid:telemetry:ConnectionManager:DeltaConnectionFailureToConnect","duration":46044,"online":"Online","connectionType":"unknown","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:127:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:586:107)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:69:20)\n    at eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:500:30)","error":"socket.io (orderingServiceHandshakeTimeout): undefined","errorType":"genericNetworkError","fluidErrorCode":"-","driverVersion":"1.2.5","canRetry":true,"message":"socket.io (orderingServiceHandshakeTimeout): undefined","errorInstanceId":"798402ba-b45d-4177-a649-9eb94cb6f7f1","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":0,"dmLastKnownSeqNumber":0,"connectionStateDuration":46044.5,"loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"attempts":3,"delay":4000,"eventName":"fluid:telemetry:ConnectionManager:DeltaConnectionFailureToConnect","duration":50974,"online":"Online","connectionType":"unknown","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:124:12)\n    at createR11sNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:46:101)\n    at errorObjectFromSocketError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:75:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:67:85)\n    at Socket.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:493:30)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)\n    at Socket.emitEvent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:342:16)\n    at Socket.onevent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:327:12)\n    at Socket.onpacket (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:290:14)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)","error":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorType":"throttlingError","fluidErrorCode":"-","statusCode":429,"driverVersion":"1.2.5","retryAfterSeconds":300,"canRetry":true,"message":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorInstanceId":"e6eb639d-3027-4188-848a-b0933d9f0987","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":0,"dmLastKnownSeqNumber":0,"connectionStateDuration":50974.5,"loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"eventName":"fluid:telemetry:DeltaManager:WrapError","errorInstanceId":"e6eb639d-3027-4188-848a-b0933d9f0987","wrappedByErrorInstanceId":"e6eb639d-3027-4188-848a-b0933d9f0987","category":"generic","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:124:12)\n    at createR11sNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:46:101)\n    at errorObjectFromSocketError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:75:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:67:85)\n    at Socket.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:493:30)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)\n    at Socket.emitEvent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:342:16)\n    at Socket.onevent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:327:12)\n    at Socket.onpacket (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:290:14)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)","error":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorType":"throttlingError","fluidErrorCode":"-","statusCode":429,"driverVersion":"1.2.5","retryAfterSeconds":300,"canRetry":true,"message":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":0,"dmLastKnownSeqNumber":0,"connectionStateDuration":50977.90000000596,"loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}
FluidController.ts:168 Fluid Log {"error":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","eventName":"fluid:telemetry:Container:ContainerWarning","category":"error","stack":"Error\n    at createGenericNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-utils/lib/network.js?:124:12)\n    at createR11sNetworkError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:46:101)\n    at errorObjectFromSocketError (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/errorUtils.js?:75:10)\n    at R11sDocumentDeltaConnection.createErrorObject (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/routerlicious-driver/lib/documentDeltaConnection.js?:67:85)\n    at Socket.eval (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@fluidframework/driver-base/lib/documentDeltaConnection.js?:493:30)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)\n    at Socket.emitEvent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:342:16)\n    at Socket.onevent (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:327:12)\n    at Socket.onpacket (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/socket.io-client/build/esm/socket.js?:290:14)\n    at Emitter.emit (webpack://pcf_tools_652ac3f36e1e4bca82eb3c1dc44e6fad/./node_modules/@socket.io/component-emitter/index.mjs?:140:20)","errorType":"throttlingError","fluidErrorCode":"-","retryAfterSeconds":300,"innerErrorInstanceId":"e6eb639d-3027-4188-848a-b0933d9f0987","statusCode":429,"driverVersion":"1.2.5","canRetry":true,"message":"R11s socket error (connect_document_error): Too Many Clients Connected to Document","errorInstanceId":"e6eb639d-3027-4188-848a-b0933d9f0987","clientType":"interactive","containerId":"ada7ddbb-57aa-4f7c-8ca3-8095992b28ba","docId":"7af38769-7911-49b5-b9b1-97ba3ea61c48","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Disconnected","dmInitialSeqNumber":0,"dmLastProcessedSeqNumber":0,"dmLastKnownSeqNumber":0,"connectionStateDuration":50978.59999999404,"loaderId":"27c44dfd-5f9c-4e86-81a1-5ff38d3e0db2","loaderVersion":"1.2.5"}

Can you provide a sample project that demonstrates this behavior?

@tylerbutler, here is a sample https://github.com/mramadanahmed/Demo-Fluid
You need to add the tenant ID and the secret key in the following file FluidController.ts
Steps to run locally, package and deploy are same as in the pcf documentation

@kashms for visibility


[BUG] Fail to show list remote Zig versions available for download

Describe the bug
Fail to show list remote Zig versions available for download.
To Reproduce
Steps to reproduce the behavior:

Run zvm ls --all

Expected behavior
List of available versions is shown.
Desktop (please complete the following information):

OS: Ubuntu 20.04
Architecture: x64
Version: v.0.7.9

I've tried with and without VMU.
With VMU
~#@❯ zvm --version
ZVM version v0.7.9 linux/amd64
 ~#@❯ cat ~/.zvm/settings.json
{
    "versionMapUrl": "https://ziglang.org/download/index.json",
    "zlsVersionMapUrl": "https://releases.zigtools.org/",
    "useColor": true,
    "alwaysForceInstall": false
}%
~#@❯ zvm ls --all

   Help

Encountered an issue while trying to install ZLS for Zig 'master'.

Problem: ZVM v0.7.7 and v0.7.8 may have saved an invalid 'zlsVersionMapUrl' to your settings,
which causes this error. The latest version, v0.7.9, can fix this issue by using the correct URL.

To resolve this:
1. Open your ZVM settings file: '~/.zvm/settings.json'
2. Remove the 'zlsVersionMapUrl' key & value from the file (if present).
What happens next: ZVM will automatically use the correct version map the next time you run it
If the issue persists, please double-check your settings and try again, or create a GitHub Issue.

  Error

2024/10/29 14:32:56 ERRO invalid version map format: invalid character '<' looking for beginning of value

If you're experiencing a bug, run zvm upgrade. If there's a new version of ZVM, we may have already fixed your bug in a new release :)
Otherwise, please report this error as a GitHub issue.
https://github.com/tristanisham/zvm/issues/

Without VMU
 ~#@❯ zvm --version
ZVM version v0.7.9 linux/amd64
 ~#@❯ cat ~/.zvm/settings.json
{
    "useColor": true,
    "alwaysForceInstall": false
}
 ~#@❯ zvm ls --all

   Help

Encountered an issue while trying to install ZLS for Zig 'master'.

Problem: ZVM v0.7.7 and v0.7.8 may have saved an invalid 'zlsVersionMapUrl' to your settings,
which causes this error. The latest version, v0.7.9, can fix this issue by using the correct URL.

To resolve this:
1. Open your ZVM settings file: '~/.zvm/settings.json'
2. Remove the 'zlsVersionMapUrl' key & value from the file (if present).
What happens next: ZVM will automatically use the correct version map the next time you run it
If the issue persists, please double-check your settings and try again, or create a GitHub Issue.

  Error

2024/10/29 14:36:48 ERRO invalid version map format: invalid character '<' looking for beginning of value

If you're experiencing a bug, run zvm upgrade. If there's a new version of ZVM, we may have already fixed your bug in a new release :)
Otherwise, please report this error as a GitHub issue.
https://github.com/tristanisham/zvm/issues/

Sorry, it looks like the problem in my enviroment. All is ok in case setting proxy explicitly.
 ~#@❯ HTTPS_PROXY=corp.proxy.com:8080 ZVM_DEBUG=1 zvm ls --all
2024/10/29 15:10:33 DEBU Automatic Upgrade Checker disabled=false
2024/10/29 15:10:33 DEBU Version Map url="" cmd=list/ls
2024/10/29 15:10:33 DEBU initial VMU url=""
2024/10/29 15:10:33 DEBU setting's VMU url=""
2024/10/29 15:10:33 DEBU initial ZRW func=fetchZlsTaggedVersionMap url=""
2024/10/29 15:10:33 DEBU setting's ZRW url=""
2024/10/29 15:10:33 DEBU Version Map Url (95) func=fetchZlsTaggedVersionMap url=https://releases.zigtools.org/v1/zls/index.json
0.13.0	(tagged zls)
0.12.1
0.12.0	(tagged zls)
0.11.0	(tagged zls)
0.10.1
0.10.0	(tagged zls)
0.9.1
0.9.0	(tagged zls)
0.8.1
0.8.0
0.7.1
0.7.0
0.6.0
0.5.0
0.4.0
0.3.0
0.2.0
0.1.1
master

@pkropachev Thanks for taking a time to create an issue and working on self-diagnosing it in your environment. I had a bit of a heart attack seeing your post! I thought I'd have to release a third hot fix. Glad to see it resolved itself.


cluster-scope-like behavior, autoinstall of KnativeEventingKafka as knative-eventing/knative-eventing-kafka

A port of https://github.com/openshift-knative/knative-eventing-operator/pull/45 to the Kafka operator

Do not merge just yet

@syedriko let's add something along the lines of https://github.com/openshift-knative/knative-eventing-operator/commit/d6c59b4b237a1f616527fd6bb31e6796ef712823   to give some clarification to our users

If @jcrossley3 has no concerns - :shipit:

Why so many vendor changes on this?

That's what dep ensure -update pulled in...

Why so many vendor changes on this?

That's what dep ensure -update pulled in...

You gotta be careful with that. I typically only use that to update a specific dep. In the future, whenever you feel the need to update everything, split that out into its own commit/pr, just to facilitate rolling back if need be.

Why so many vendor changes on this?

That's what dep ensure -update pulled in...

You gotta be careful with that. I typically only use that to update a specific dep. In the future, whenever you feel the need to update everything, split that out into its own commit/pr, just to facilitate rolling back if need be.

Fixed, only manifestival is updated.

Perfect, thanks!
/lgtm

@syedriko let's add something along the lines of openshift-knative/knative-eventing-operator@d6c59b4 to give some clarification to our users

Done


SPARTA-617 Example scripts do not work properly due to an incorrect syntax

Given a Sparta installation with no inputs, outputs or policies
When run the 3 scripts located at /opt/sds/sparta/examples/scripts
Then it should register 1 input, 3 outputs and 3 policies

+1

:shipit:

Comment accepted. Will treat it ASAP


[FEATURE REQ] Support push generated project to github

Context
The current Spring Initializr only suports download the generated project to local.
It would be helpful to push generated project to a source control system directly

GitHub
Azure DevOps

Goal
We should make this extendable, probably by defining a Source Control System interface, so others system besides the above two can be supported as well.
For example , Quarkus Start has a similar function.

mark as finished


Could not resolve node:fs

mdx-bundler version: 8.0.0
node version: 16.6.1
npm version: 8.1.4

Relevant code or config
import { bundleMDX } from "mdx-bundler";

What you did:
I try to do the remix blog tutorial, but instead of .md, I try to do it with .mdx files with mdx-bundler.
As soon as I import it - it is not called just imported - and run remix dev, it blows up with the message below.
What happened:
  > node_modules/mdx-bundler/node_modules/xdm/lib/integration/esbuild.js:16:29: error: Could not resolve "node:fs" (mark it as external to exclude it from the bundle)
    16 │ import {promises as fs} from 'node:fs'
       ╵                              ~~~~~~~~~

  > node_modules/mdx-bundler/node_modules/xdm/lib/integration/esbuild.js:17:20: error: Could not resolve "node:process" (mark it as external to exclude it from the bundle)
    17 │ import process from 'node:process'
       ╵                     ~~~~~~~~~~~~~~

Package.json
{
  "private": true,
  "name": "remix-app-template",
  "description": "",
  "license": "",
  "scripts": {
    "build": "remix build",
    "dev": "remix dev",
    "postinstall": "remix setup node",
    "start": "remix-serve build"
  },
  "dependencies": {
    "@remix-run/react": "^1.0.6",
    "@remix-run/serve": "^1.0.6",
    "add": "^2.0.6",
    "esbuild": "^0.14.0",
    "front-matter": "^4.0.2",
    "mdx-bundler": "^8.0.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "remix": "^1.0.6",
    "tiny-invariant": "^1.2.0"
  },
  "devDependencies": {
    "@remix-run/dev": "^1.0.6",
    "@types/react": "^17.0.24",
    "@types/react-dom": "^17.0.9",
    "typescript": "^4.1.2"
  },
  "engines": {
    "node": ">=14"
  },
  "sideEffects": false
}

I ran into this exact problem yesterday (with the one exception that I do have to call the function, not just import it) while working through the Remix tutorial and trying to implement mdx-bundler (since it's one of the suggestions elsewhere in their docs). I ended up banging my head against it for several hours without any meaningful progress.
I tried a few versions each of node and esbuild to make sure it wasn't a compatibility issue. I also spent a good chunk of time poring over the source of Kent's own site to understand his own environment and implementation (including migrating my Remix example over to express for parity's sake), but I wasn't ever able to replicate a successful build.
For completeness, here's where my package.json ended up by the time I gave up, in case it points out an obvious issue:
{
  "private": true,
  "name": "remix-app-template",
  "description": "",
  "license": "",
  "scripts": {
    "build": "remix build",
    "dev": "remix watch",
    "postinstall": "remix setup node",
    "start": "cross-env NODE_ENV=production node server/index.js",
    "start:dev": "cross-env NODE_ENV=development node server/index.js"
  },
  "dependencies": {
    "@remix-run/express": "^1.0.6",
    "@remix-run/react": "^1.0.6",
    "compression": "^1.7.4",
    "cross-env": "^7.0.3",
    "express": "^4.17.1",
    "front-matter": "^4.0.2",
    "morgan": "^1.10.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "remix": "^1.0.6",
    "tiny-invariant": "^1.2.0"
  },
  "devDependencies": {
    "@remix-run/dev": "^1.0.6",
    "@types/react": "^17.0.24",
    "@types/react-dom": "^17.0.9",
    "typescript": "^4.1.2"
  },
  "engines": {
    "node": ">=14"
  },
  "sideEffects": false
}

Just had the issue today and found the "trick" in Kent's codebase.
Make sure to only import mdx-bundler within a file with the suffix .server.ts(x) like mdx.server.ts you can even just export { bundleMDX } from 'mdx-bundler' then in your route import from this file instead, or use it to wrap bundleMDX and predefine settings etc like Kent is doing
More at data-loading#basics

Thanks for that @CanRau! That got me where I needed to go and it seems to be working just fine now.
I had a feeling from the fact that the modules in the error were from node that it had to do with the division between server and client, but I hadn't absorbed the way the .server.{js,ts,tsx} suffix was used in Remix.

@CanRau it gives me then another error:
mdx-bundler warning: esbuild maybe unable to find its binary, if your build fails you'll need to set ESBUILD_BINARY_PATH. Learn more: https://github.com/kentcdodds/mdx-bundler/blob/main/README.md#nextjs-esbuild-enoent
There was an error running the data loader for route routes/$article
Error: No "exports" main defined in /Users/mateusz.kwiatkowski/Playground/remix-mantine/node_modules/periscopic/package.json
    at new NodeError (node:internal/errors:371:5)
    at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
    at packageExportsResolve (node:internal/modules/esm/resolve:671:7)
    at resolveExports (node:internal/modules/cjs/loader:482:36)
    at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:27)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at<EMAIL_ADDRESS>(/Users/mateusz.kwiatkowski/Playground/remix-mantine/node_modules/@mdx-js/mdx/lib/plugin/recma-document.js:42:23)
GET /dolor-lorem-ipsum-1 500 - - 161.983 ms


#2940 optional literal value for replacement

Any ideas how to improve testcases regarding yaml parsing? The following codeblock just to get a parsed instance of my recipe feels wrong:
ReplaceStringLiteralWithConstant recipe = (ReplaceStringLiteralWithConstant) RecipeSpec.defaults().recipeFromYaml("""
    type: specs.openrewrite.org/v1beta/recipe
    name: org.openrewrite.ReplaceStringLiteralWithConstantList
    recipeList:
        - org.openrewrite.java.ReplaceStringLiteralWithConstant:
            literalValue: %s
            fullyQualifiedConstantName: %s
    """.formatted("default", EXAMPLE_STRING_FQN),
  "org.openrewrite.ReplaceStringLiteralWithConstantList"
).getRecipe().getRecipeList().get(0).getRecipeList().get(0);```

I've added some review comments and one or more suggestions; Let me know how you'd want to address those, or if you'd like any of us to take that on. Thanks a lot! This makes the recipe a lot more useful.


issues/309: If fetch certificates fails, log the clientIP and clientFingerPrint.

Updates: https://github.com/komuw/ong/issues/309

Codecov Report
Patch coverage: 62.50% and project coverage change: -0.06 :warning:

Comparison is base (664be60) 73.83% compared to head (7c0c55f) 73.77%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #310      +/-   ##
==========================================
- Coverage   73.83%   73.77%   -0.06%
==========================================
  Files          42       42
  Lines        4804     4813       +9
==========================================
+ Hits         3547     3551       +4
- Misses       1008     1012       +4
- Partials      249      250       +1

Impacted Files
Coverage Δ

server/tls_conf.go
56.00% <20.00%> (-1.54%)
:arrow_down:

server/fingerprint.go
80.95% <75.00%> (+0.62%)
:arrow_up:

internal/acme/acme.go
63.72% <85.71%> (+0.62%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Problems trying to use the Recharts example

applySpread is depricated without tips what function should be used instead:

createEl just disappered:

I use createElement instead, no idea if it's correct.

It's compiled, but throws exception at runtime:

I found this ts binding https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/recharts and tried to convert it with ts2fable. The resulting code does not compile :(

Sorry for the confusion, this was done after getting some feedback at FableConf that applySpread was confusing, so now you only need to use createElement. I have fixed it and published Fable.Recharts in Nuget. You can use that or just copy the source (a single file atm).
Unfortunately the bindings are not complete. When I started them for some reason I didn't use the TS declaration. I wrote them based on Recharts documentation.

Thanks, it works!


Update usajobs.data.json file

The current usajobs.data.json file does not have CS-relevant info. Fix that.

System now finds all jobs with "internship", and all jobs with "software". Unfortunately the intersection of those two searches is currently empty.


HELM-100: allow overriding time intervals and max datapoints

This commit adds support for setting a global time interval for the PM datasource and optionally overriding it per query. Max datapoints can also be specified per query.
Allowing a global default is useful when the minimum_step setting in OpenNMS is lower than what you'd want to use for most graphs. (For example when polling certain services every 60 seconds, but everything else at a larger interval.)
One new configuration option for the PM datasource:

Two new graph query options:

I tried this out against Grafana 5.1.4, and this works as expected.
I setup a dashboard with a table panel, and the times returned for all metrics were adjusted based on the options specified for the OpenNMS Data Source. So instead of seeing one every 10 minutes, I was seeing results for a whole hour like I wanted.

Thanks for the feedback @roskens.


[ROX-13403] : Fix node -> topVuln sub resolver bug when node cves is empty

Description
Issue happens when postgres is disabled
When there are no node cves, the topVuln sub resolver passes a nil query to cveDatastore, which results in datastore returning all cves including image and platform cves. The fix avoids querying cveDatastore and returns topVuln value as nil when there are no cves in a node.
Checklist

[ ] Investigated and inspected CI test results~
~[ ] Unit test and regression tests added~
~[ ] Evaluated and added CHANGELOG entry if required~
~[ ] Determined and documented upgrade steps~
~[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)~

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Apply the same changes to getTopNodeCVEV1Query and similarly for images

Currently the check in getTopNodeCVEV1Query  is
if resolver.data.GetSetTopCvss() == nil {
    return nil, nil
}

I can change the check to if resolver.data.GetTopCvss() == 0 instead. But I am not sure if there exist a CVE that has Cvss score 0. If there is such a CVE, then we would want to return that CVE and not nil. The check if resolver.data.GetSetTopCvss() == nil does seem more accurate in that case. So I am keeping getTopNodeCVEV1Query  the same and at the caller level, just adding an extra check for nil query.
Also, I do not think we need to make any changes to images since topVuln resolver in images does not call a getTopImageCVEQuery function. They directly return nil cveResolver  when GetSetTopCvss() == nil .

Apply the same changes to getTopNodeCVEV1Query and similarly for images

Currently the check in getTopNodeCVEV1Query  is
if resolver.data.GetSetTopCvss() == nil {
    return nil, nil
}

I can change the check to if resolver.data.GetTopCvss() == 0 instead. But I am not sure if there exist a CVE that has Cvss score 0. If there is such a CVE, then we would want to return that CVE and not nil. The check if resolver.data.GetSetTopCvss() == nil does seem more accurate in that case. So I am keeping getTopNodeCVEV1Query  the same and at the caller level, just adding an extra check for nil query.
Also, I do not think we need to make any changes to images since topVuln resolver in images does not call a getTopImageCVEQuery function. They directly return nil cveResolver when GetSetTopCvss() == nil .

Member

Yes, CVEs may have a score of 0. I am confused by the flow. Evaluation of the args RawQuery must happen after knowing the fact that there are indeed a non-zero number of cves. Recommend moving the following check out of the function topVulnV2.
if resolver.data.GetSetTopCvss() == nil {
		return nil, nil
	}

/retest


Paging

[!NOTE]
Latest version: https://github.com/matt-ramotar/Paging
Will create smaller PRs once I have a version ready for review

Context:

Closes #602
Addresses @yigit feedback https://github.com/MobileNativeFoundation/Store/pull/603#discussion_r1493497989
Addresses #608

Paging Technical Design Doc
1. Motivations
Powerful and extensible solution for paging in KMP projects, under the Mobile Native Foundation. Address these Android Paging limitations:

[x] Seamless integration with Store and Mutable Store
[x] Local mutations and streaming of child items within the list of paging items
[x] Custom reducer, middleware, and post-reducer effects

2. Overview
Modular and flexible architecture. Using builder, reducer, middleware, and post-reducer effect patterns. Unidirectional
data flow. The Pager is the main component. Actions are dispatched through the Pager. The PagerBuilder creates
the Pager. It allows configuration of the paging behavior. The PagingSource defines the data loading logic. The PageFetchingStrategy determines when to fetch the next page. The PageAggregatingStrategy combines loaded pages into a single list. The PagingReducer handles state changes based on actions. When an action is dispatched, it goes through the middleware pipeline. The middleware can modify the action. The reducer then updates the state based on the action. After the reducer, we invoke post-reducer effects associated with the action and new state. The updated state is sent back the Pager and emitted to the UI.
3. The Actual Design
3.1 Key Components

Pager: The main entry point, responsible for coordinating the paging process and providing access to the paging
state and data.
PagingSource: Defines the data source and loading logic for paged data.
PagingState: Represents the current state of the paging data, including loaded pages, errors, and loading status.
PagingAction: Defines the actions that can be dispatched to modify the paging state.
PagingReducer: Reduces the paging state based on dispatched actions.
PagingMiddleware: Intercepts and modifies paging actions before they reach the reducer.
PostReducerEffect: Performs side effects after reducing the paging state.
PageFetchingStrategy: Determines when to fetch the next page of data.
PageAggregatingStrategy: Aggregates loaded pages into a single list.
MutablePagingBuffer: Efficiently stores and retrieves paging data.
JobCoordinator: Coordinates the execution of paging-related jobs.
QueueManager: Manages the queue of pages to be loaded.
PagingStreamProvider: Provides a stream of paging data.
PagingKeyFactory: Creates keys for paging data.
PagingConfig: Configures the paging behavior.
ErrorHandlingStrategy: Defines how to handle errors during the paging process.
Logger: Logs paging-related events and actions.

3.2 Customizations
Providing many extension points and customization options to tailor behavior. Main customization points:

PagingSource: Developers can implement their own PagingSource to define how paged data is loaded from the data source. This allows for integration with different data sources and loading mechanisms.
PagingMiddleware: Custom PagingMiddleware can be implemented to intercept and modify paging actions before they reach the reducer. This enables preprocessing, logging, or any other custom logic.
PagingReducer: The PagingReducer can be customized to define how the paging state is reduced based on dispatched actions. This allows for fine-grained control over the paging state transitions.
PostReducerEffect: Custom PostReducerEffect instances can be configured to perform side effects after reducing the paging state. This is useful for triggering UI updates, analytics events, or any other necessary actions.
PageFetchingStrategy: Developers can implement their own PageFetchingStrategy to determine when to fetch the next page of data based on the current state and configuration. This allows for customizing the prefetching behavior.
PageAggregatingStrategy: Custom PageAggregatingStrategy implementations can be provided to define how loaded pages are aggregated into a single list. This enables different aggregation strategies based on the specific requirements of the application.
ErrorHandlingStrategy: Developers can implement their own ErrorHandlingStrategy to define how errors during the paging process are handled. This allows for custom error handling, retry mechanisms, or fallback behaviors.

3.3 Data Flow
Unidirectional data flow. Main steps:

Pager is configured using PagerBuilder and provided an initial key, flow of anchor position, and paging config.
Pager subscribes to the PagingSource to receive paging data updates.
When a PagingAction is dispatched, it goes through the configured PagingMiddleware chain. This enables interception and modification of the action.
The modified action reaches the PagingReducer, which reduces the current PagingState based on the action and returns a new PagingState.
After reduction, any configured PostReducerEffect instances are executed, enabling side effects to be performed based on the new PagingState.
Pager updates PagingStateManager with the new PagingState.
PageFetchingStrategy determines when to fetch the next page of data based on the PagingConfig and current PagingState.
When a new page needs to be fetched, QueueManager enqueues the page key, and the JobCoordinator coordinates the execution of the paging job.
PagingSource loads the requested page and emits the loaded data through the PagingStreamProvider.
The loaded page is stored in the MutablePagingBuffer for efficient retrieval and aggregation.
The PageAggregatingStrategy aggregates the loaded pages into a single list, which is then emitted through the Pager for consumption by the UI.

4. Sample Code
Configuring the Pager using PagerBuilder:
val pager =
    PagerBuilder<Int, CollectionKey, SingleData, CustomAction, CustomError>(
        initialKey = CollectionKey(0),
        anchorPosition = anchorPositionFlow,
        pagingConfig = pagingConfig
    )
        .dispatcher(
            logger = DefaultLogger(),
        ) {

            // Use the default reducer
            defaultReducer {
                errorHandlingStrategy(ErrorHandlingStrategy.PassThrough)
                pagingBufferMaxSize(100)
            }

            middlewares(
                listOf(
                    // Add custom middleware
                )
            )

            // Add custom post reducer effects
            postReducerEffect<MyPagingState, MyPagingAction>(
                state = MyPagingState::class,
                action = MyPagingAction::class,
                effect = MyPostReducerEffect
            )

            // Use the default post reducer effects
            defaultPostReducerEffects(pagingSource = pagingSource)
        }

        .build()

Observing the paging state and dispatching actions:
pager.state.collect { state ->
    when (state) {
        is PagingState.Data.Idle -> {
            // Update UI with loaded data and provide dispatch callback
            DataView(pagingItems = state.data) { action: PagingAction.User ->
                pager.dispatch(action)
            }
        }
        is PagingState.LoadingInitial -> {
            // Show loading indicator
            InitialLoadingView()
        }
        is PagingState.Error -> {
            // Handle error state and provide dispatch callback
            InitialErrorViewCoordinator(errorState = state) { action: PagingAction.User ->
                pager.dispatch(action)
            }
        }
    }
}

@digitalbuddha @yigit - Putting this back into draft. I'm going to separate this into smaller PRs

Separated in #630 with https://github.com/MobileNativeFoundation/Store/tree/paging branch


Update to PAC crate stm32f3 version 0.7.x

Do you plan to update to PAC crate stm32f3 version 0.7.x?

Yep! I was working on it a week or so ago, but ran out of time to fix a few things. Hopefully, I can get back to it this weekend. If anyone else beats me to the punch, I’ll gladly review and merge.

Thanks! Let me know if I could anything review or test so as to help you.


Multiple item trades + #payitem feature

🚀 Feature Proposal
Describe the feature you're suggesting here, give lots of information and describe it as best you can. Please check that the feature hasn't already been suggested first, by searching the issues in this repository.
Multiple item trade: +sellto @User price1 item1 price2 item2 price3 item3 price4 item4 --cf
The 'wait' timer could be increased by 5 second every item listed so the customer would have time to check prices, the 'bot' could list like: would you like to buy item1 for price1, item2 for price2, item3 for price3? Type Buy to proceed. or a trade screen with the visual of the items could be opened with 'asking' price in the --sv value...?
&& the +payitem feature for giving out items in giveaways, even when the user is not online, could be useful! less carpals <3
if only i knew how to code right i'd code it for you :3

A version of this have now been implemented #1130 .

A version of this have now been implemented #1130 .


[Task] Explore Tailwind CSS for Project Styling

What product(s) is this story for?
Sage Monorepo
As a user, I want
As a Developer, I want to use Tailwind CSS to style my project efficiently so that I can create consistent, responsive designs with minimal custom CSS.
Description
Explore Tailwind CSS, a utility-first CSS framework that offers several benefits:

Efficiency in Development: Tailwind provides a set of utility classes that can be applied directly to HTML elements, allowing for rapid prototyping and reducing the need to write custom CSS. This can significantly speed up the development process.

Consistency: By using a predefined set of classes, Tailwind ensures a consistent design system throughout a project. This makes it easier to maintain a uniform look and feel.

Customizability: Tailwind is highly customizable. Developers can configure the framework to match their design requirements by modifying the configuration file. This includes setting up custom colors, spacing, fonts, and more.

Responsive Design: Tailwind makes it easy to create responsive designs with its built-in responsive utilities. Classes can be applied conditionally based on screen size, simplifying the process of making a website mobile-friendly.

Smaller CSS Files: Using PurgeCSS with Tailwind can remove unused CSS, resulting in smaller file sizes and faster load times. This is particularly beneficial for production environments.

Component-Friendly: Tailwind integrates well with component-based frameworks like React, Vue, and Angular. It allows for easy styling of individual components without worrying about global styles clashing.

Active Community and Ecosystem: Tailwind has a large, active community and a growing ecosystem of plugins and tools, providing plenty of resources and support for developers.

Overall, Tailwind CSS enhances productivity, promotes design consistency, and offers flexibility, making it a popular choice among modern web developers.
Acceptance criteria

I can set up Tailwind CSS in my project.
I can apply utility classes to HTML elements to style components.
I can customize the default configuration to match the project’s design requirements.
I can use responsive utility classes to ensure the design is mobile-friendly.
I can integrate Tailwind CSS with my existing component-based framework (here Angular).
I can optimize the final CSS file size for production by removing unused styles.

Tasks

[ ] Generate an app configured with Tailwind with the Nx generator for Angular
[ ] Review the files generated
[ ] Review the Acceptance criteria
[ ] Identify the pros and cons of adopting Tailwind. Are there other alternatives?
[ ] Share the insights learned with anyone who may be interested in this tool.

Anything else?
cc: @vpchung @rrchai @sagely1 @hallieswan @jay-hodgson @nickgros @JessterB
Have you linked this story to a GitHub Project?

[X] I have linked this story to a GitHub Project and set its metadata.

Now tracked in https://sagebionetworks.jira.com/browse/ARCH-298


Table Widgets render

The rendering of the little green and red squares (which I think mark a unique column or a prime key column) seems a bit odd.
The green square appears, for a unique column, on the left hand end of the row and the red square appears over the word primary.
I'm looking at this on the latest Firefox on Windows 7 and possibly it may look differently elsewhere but this is what I've got .

It's an issue with the way jsPlumb library works, nothing wrong with your browser. I am on my way towards fixing this bug, thanks for reporting.

If you are still using Visual Alchemist by any chance, I've fixed this. Please test the latest master branch and let me know.

Fixed in the latest update


cannot interact with the area below toast

Describe the bug
When showing notification there is a large space of padding (i think) that stop user from interacting on Android and iOS
To Reproduce
Steps to reproduce the behavior:

Create a bottom navigation
Create a toastification with alignment of bottomCenter
Try to click any of the navigation items

Expected behavior
User can still interact with the UI beneath notifcation
Screenshots
https://github.com/payam-zahedi/toastification/assets/61675970/7f67c55b-bd9c-4727-8943-73965d6ae7c4
Flutter information:

OS: [iOS, android]
Flutter Version: [3.22.1]
Toastification Version [2.0.0]

@payam-zahedi  can you confirm this is a bug or it was intend to be like this

@payam-zahedi  @Yukari-Tryhard Yes i did encounter this problem, do you guys found out any solution to this ? Whenever the toast appears the section underneath cant be interacted with. Happens with me in the appbar backbutton .

@payam-zahedi This happens for me too and is a pretty high priority issue for mobile users. If you swipe to dismiss a toast before the duration is over, you cannot interact with the area that the toast was displayed over until the duration passes.

@scharfschiesser
Yes, I will try to fix this as soon as possible

It is a high priority one. @payam-zahedi

I have this issue. I can't click on an action button in the top right, when my toast is displayed nowhere near it.

Hey Guys,
I fixed this on the newest version.
Please take a look and let me know if you still have the same problem.

I'll close this for now, but feel free to reopen it.


feat: Disable vibration

Hey @xmrv!
Thanks for your interest, should I consider your message as a feature request? If so, I can add a simple switch to the settings menu next week and release it in version 2.2.1. WDYT?

That would be lovely, thank you :)

@xmrv 2.2.1 is on review on both Microsoft Store and Google Play Store and should go online in about 12-24h. Otherwise downloadable binaries are in the Release section. If you will need some other features or bug fixes, just let me know. Thanks for starring a repo!


[release-0.53] Snapshot tests: Partial backport of snapshot tests skip condition change

Signed-off-by: Alex Kalenyuk<EMAIL_ADDRESS>
What this PR does / why we need it:
On 1.24 and thus OpenShift 4.11 v1beta1 is not going to be served anymore (deprecated), which means we will skip these tests.
On newer branches we had this fixed by https://github.com/kubevirt/kubevirt/pull/8173 (Can't cherry pick because its part of a bigger commit)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/lgtm
/approve

/retest-required


TODO: User Interface

I CUI interface, where it's easy to interact using startdard / vim motions keys. Gonna be done using pancurses crate.

Implemented


Typeblocking "1" should prioritize number 1

Entering 1 in the typeblocking window includes the number 1 as the last entry rather than the first. The results should probably be sorted most-least specific but it seems to be opposite. It's much more likely for a program to contain the number 1 rather than the various base conversion blocks that appear earlier in the list.
see issue #2660

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test

I found another bug while fixing this one.
when we typeblock the word "text" in any combination of lower & uppercase letter except "text" and "Text", we are not able to see the text block on top.Probably the expected behaviour is: the text block should be on top of list (ex: on top of button.text) no matter casing of characters. here is a screenshot showing that

If you can confirm this is not an expected behaviour, I can fix that as well in same PR as it's just a small change.

@devarsh-mavani-19 I will need to think about that. Usually the way I do text is to do an open double quote, e.g. " and then start typing the text. The thing I usually trip up on after this is putting the close quote, which then ends up in the text. We may want to detect if the user has typed the closing " and ignore it when generating the block if this is the case.

@devarsh-mavani-19 I will need to think about that. Usually the way I do text is to do an open double quote, e.g. " and then start typing the text. The thing I usually trip up on after this is putting the close quote, which then ends up in the text. We may want to detect if the user has typed the closing " and ignore it when generating the block if this is the case.

so I can do something like this?
if more than 1 " found
then
        ignore the first and last " and add rest as text

@devarsh-mavani-19 I will need to think about that. Usually the way I do text is to do an open double quote, e.g. " and then start typing the text. The thing I usually trip up on after this is putting the close quote, which then ends up in the text. We may want to detect if the user has typed the closing " and ignore it when generating the block if this is the case.

latest commit should solve it. can you please check this video
https://user-images.githubusercontent.com/55136047/159063509-15625b57-2b44-41da-9c38-7bfce24f4a82.mp4

@AppInventorWorkerBee retest this please


spec-file.txt - link not found error [UPDATE]

I got error for the following links and I have added the updated links-

HTTP 404 NOT FOUND for url https://conda.anaconda.org/pytorch/linux-64/pytorch-1.0.1-py3.6_cuda8.0.61_cudnn7.1.2_2.tar.bz2

https://conda.anaconda.org/pytorch/noarch/torchvision-cpu-0.2.2-py_3.tar.bz2

It seems a PyTorch issue. It would be better to look for a solution in PyTorch repo or PyTorch Forums.


Update webooks.php helper

code for #234

unassigned myself (GH slackbot was notifying every day). Please reassign when there are instructions.

closing in favor of #264 which will nullify this


Corrupt weight file

Is uploaded file git clone https://huggingface.co/feishen29/IMAGDressing correct. It seems corrupt getting this error.
Traceback (most recent call last):   File "/home/ec2-user/SageMaker/IMAGDressing/inference_IMAGdressing.py", line 154, in <module>     pipe, generator = prepare(args)   File "/home/ec2-user/SageMaker/IMAGDressing/inference_IMAGdressing.py", line 97, in prepare     model_sd = torch.load(args.model_ckpt, map_location="cpu")["module"]   File "/home/ec2-user/anaconda3/envs/JupyterSystemEnv/lib/python3.10/site-packages/torch/serialization.py", line 1114, in load     return _legacy_load(   File "/home/ec2-user/anaconda3/envs/JupyterSystemEnv/lib/python3.10/site-packages/torch/serialization.py", line 1338, in _legacy_load     magic_number = pickle_module.load(f, **pickle_load_args) _pickle.UnpicklingError: invalid load key, 'v'.

Thank you for your attention, it seems that your downloaded weights are incomplete

Excuse me~ May I ask how did you solve the problem~I met the same problem too as I run the 2 & 3 command.


Reorganize Project Structure for Improved Maintainability

As the project has grown and evolved, its structure has become a bit mixed. The current structure combines CLI tools, UI applications, and libraries within one folder. As a result, some files are using the same filename in subfolders, with similar goal but different contents, some configuration files are duplicated. Progressively restructuring the project with separation of concern would improve maintainability and extensibility.

Here are 2 options we can discuss:
option 1
tdwii-plus-examples/
├── cli/
│   ├── wrklstmgr.py
│   └── watchwrkitem.py
├── apps/
│   ├── rtbdi_creator.py
│   └── tdd.py
├── config/
│   ├── default.ini
│   └── known_ae.json
├── doc/
│   ├── cli.md
│   └── apps.md
├── tdwii_plus_examples/
│   ├── __init__.py
│   ├── basescp.py
│   └── echoscp.py
├── pyproject.toml
└── README.md

option 2
tdwii-plus-examples/
├── tdwii_plus_examples/
│   ├── __init__.py
│   ├── basescp.py
│   ├── echoscp.py
│   ├── cli/
│   │   ├── wrklstmgr.py
│   │   └── watchwrkitem.py
│   ├── apps/
│   │   ├── rtbdi_creator.py
│   │   └── tdd.py
│   ├── config/
│   │   ├── default.ini
│   │   └── known_ae.json
│   └── doc/
│       ├── cli.md
│       └── apps.md
├── pyproject.toml
└── README.md

Notes: Poetry usually uses underscores for package folder when project name contains dashes

I agree that the file structure needs reorganising.  I prefer option 2 vs option 1, but I think having a library directory that contains the reusable (and already reused) modules would be helpful.

Let's go for option 2 then 👍 I can start by duplicating the BaseSCP class from TDWII_PPVS_subscriber to the tdwii_plus_examples package folder and refactor the apps to use it, then make my way down the hierarchy of SCP classes.

I have created the pull request  (#86) that refactors BaseSCP. I will continue with its subclass EchoSCP.

The previous pull request (https://github.com/sjswerdloff/tdwii_plus_examples/pull/87) refactored EchoSCP in CEchoSCP
A new pull request (https://github.com/sjswerdloff/tdwii_plus_examples/pull/88) refactors its subclass StoreSCP in CStoreSCP
The next step is to refactor its subclass NEventReceiver


Empty selection following "Open Repository from GitHub"

It's hard to describe the problem any more -- following the first-time authentication, and having validated (through "Manage Trusted Extensions") that I'm signed-in and "Remove Repositories" can use that account, the list of repositories I'm presented with for GitHub is completely empty. No error is offered or any indication of other failure.

So when you run Open Repository... and choose Open Repository from GitHub you don't see any repositories by default? If you start typing do you see any?

Correct -- It's empty when it first opens, and remains empty even if I type stuff

Please enable output channel logging by running from Remote Repositories: Enable Debug Logging from the command palette (ctrl+shift+p or cmd+shift+p). This will enable logging to the Remote Repositories channel in the Output pane.
Once enabled, please reproduce the issue, and attach the log from the Remote Repositories channel.

Unfortunately, seems like there's no such command. I'm getting the following error:
Command 'Remote Repositories: Enable Debug Logging' resulted in an error (command 'remoteHub.enableDebugLogging' not found)

This is Remote Repositories version v0.10.1.

There is an issue where that command won't activate the extension -- if you run Remote Repositories: Open Repository... from the command palette first (that will cause the extension to activate), and then the debug logging command should work.

I'm experiencing the same issue in v0.10.1. The debug logging doesn't include much after attempting to open a repository using "Remote Repositories: Open Repository..." and then "Open Repository from GitHub":
[2021-06-23 06:11:55:654] [    4] (A) Reader(3|WorkspaceRepositories) • WorkspaceRepositories.get
[2021-06-23 06:11:55:655] [    4] (L) Reader(3|WorkspaceRepositories) waited for 0 ms • WorkspaceRepositories.get
[2021-06-23 06:11:55:655] [    4] (U) Reader(3|WorkspaceRepositories) locked for 0 ms • WorkspaceRepositories.get

Can you try to see if the issue is still reproducible in the Remote Repositories (Insiders) edition?
You can install the Remote Repositories (Insiders) edition from here.
Please be sure you are using the Insiders edition of VS Code, and to disable or uninstall the stable version of Remote Repositories first. Also note, that no data is shared between the insiders and stable editions.

Thanks, it does work with the Remote Repositories (Insiders) build!


Get terraform guidance added to MoJ Technical Guidance site

OPG have come up with some great Terraform standards.
Some of this might not work for everyone (e.g. terraform workspaces versus modules), but whatever we can extract as organisation-wide principles should feature on the MoJ Technical Guidance site.

OpsEng's role in this is more facilitation and encouragement than creating the document.

We are unsure how we can enforce these standards and feel that this requires wider discussion with a forum of those teams that are creating Terraform.
Place on hold until the next year with a view of setting up a working group.

No longer required.


fix(Slideover): wait for transition to complete to reset state

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Implements the @after-leave transition hook for reseting stage. This is an identical effort as #1618 but for Slideover component.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks @genu! 😊


missing theme context in useCommandCallback

Describe your changes
Added missing themeContext in useCommandCallback
Screenshots [Optional]
Issue ticket number and link
Closes #
Checklist before requesting a review

[x] I have performed a self-review of my code
[ ] I have added tests
[x] I have added a changeset pnpm changeset add
[ ] I have added example usage in the kitchen sink app

@sagardspeed2 what is this for? The theme is injected as an atom here https://github.com/EnsembleUI/ensemble-react/blob/main/packages/framework/src/hooks/useCommandCallback.ts#L63

@evshi I know that theme is injected as atom, but it missing the method like setTheme, and due to that is breaks the functionality related change the theme. so I added themeContext which includes that method

@sagardspeed2 add a new atom with the methods and use that instead. Prefer using atoms instead of context hooks.


Encoding does not work with the `--resampling' option and speed/effort higher than 7

Encoding does not work with the `--resampling' option and speed/effort higher than 7
-s 8 -q 30 --resampling=2
JPEG XL encoder v0.3.7 [AVX2]
Read 1473x820 image, 47.2 MP/s
Encoding [VarDCT, d6.400, kitten], 8 threads.
../lib/jxl/image_bundle.cc:62: JXL_CHECK: ec.xsize() == xs

Sometimes without error messages

We should ideally fix that or at least forbid that combination as a temporary fix.

It appears that larger (with respect to dimentions) images are not effected by this issue. I have attached two test images for which one encodes fine, and the other does not. I used cjxl -e 9 -d 25
test_images.zip

I verified that with the latest changes -e9 --resampling 2 and -e9 -d25 works.


Huge params fixes

Description
Huge params fixes
Type of change

Bug fix (non-breaking change which fixes an issue)
Refactor (refactoring code, removing useless files)
Unit tests (no changes in the code)

Testing steps
Done on CI
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Patch coverage: 97.50% and no project coverage change.

Comparison is base (cd1f238) 79.56% compared to head (898ee2a) 79.56%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #642   +/-   ##
=======================================
  Coverage   79.56%   79.56%
=======================================
  Files          15       15
  Lines        1683     1683
=======================================
  Hits         1339     1339
  Misses        243      243
  Partials      101      101

Impacted Files
Coverage Δ

server/auth.go
0.00% <0.00%> (ø)

server/cluster.go
88.88% <100.00%> (ø)

server/configuration.go
100.00% <100.00%> (ø)

server/operator.go
96.72% <100.00%> (ø)

server/profile.go
100.00% <100.00%> (ø)

server/server.go
80.00% <100.00%> (ø)

server/trigger.go
100.00% <100.00%> (ø)

storage/cluster.go
71.83% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


querydsl-codegen-utils:5.0.0 is missing in maven central

Observed vs. expected behavior
Hi, com.querydsl:querydsl-codegen-utils:jar:5.0.0 which is mentioned in querydsl-bom is not present in maven central or deployed in maven central .  But rather com.querydsl:codegen-utils:5.0.0 is. Can you please let us know if it was by mistake or intended?
Steps to reproduce
Search for com.querydsl:codegen-utils:5.0.0 in Maven central
Querydsl version: 5.0.0

@jwgmeligmeyling can you please take a look at it?

@lpandzic should we update the BOM or relocate the artefact according to convention?

I assume we should update the bom, but why have coordinates changed?

I have no clue actually. Did they change though? It appears to me as if I just didn't follow artefact naming conventions while creating the POM which you seem to have assumed I had followed while creating the BOM 😉

I also don't recall, I remember copying most of it so it's likely it could also be a simple CP error.
Anyway, I'd agree with just aligning the bom with how artifact is defined, not the other way around.

Yes, moving artifacts is quite a bit of hassle. Let's just adjust the pom

Ok I found out the reason: module is called querydsl-codegen-utils (root pom.xml) but artifact is called codegen-utils.


What's the difference between  Alink and Angel-ML angel

Alink is using flink engine，but angel-ml is spark based. Two main design points of flink are: one that is well-known is pure streaming, the other is actually iteration operator that does not been mentioned too often. Alink is the effort to leverage this iteration mechanism to improve the algorithm performance and also the machine learning become more and more real-time, so we need a realtime engine to implement those machine learning algorithm


Spaces aren't inserted correctly when formatting a card number input

STR:

Go to the demo.
In the card number field, type 12345.
Expected: The input now reads 1234 5.
Actual: The input now reads 12345.

I think this commit is the culprit: https://github.com/stripe/jquery.payment/commit/3dc241e9188407042026c6d39ee74480504c3715
After this commit, all non-digits are stripped from the number inserted after each keystroke.

12345 doesn't match any known credit card formats, so jquery.payment doesn't know how to format it. Try 4242 4242 4242 4242 for a valid fake Visa, for example. You can see some additional fake cards here: https://stripe.com/docs/testing

Ah, I was thinking that even if the user makes a mistake (resulting in the number being invalid), it'd be nice to still format the numbers in some common way (e.g. 1234 5678 9012 3456).

Actually, @courthead suggestion (4-digit groups instead of ungrouped by default) makes sense. It would be great if this behavior could be configurable.
@jenanwise: Would you guys be interested in adding something in that line?


Feature: Add Keep-Alive option

Excellent extension.
I keep getting disconnected over long periods of idle, which I'm assuming is a disconnect if idle.
Could we have an option to perform some type of keep alike activity in the background?

I get disconnected all the time....
in my ssh connections config file I specified for all hosts:
ServerAliveInterval 100
ServerAliveCountMax 60

but still after a while it disconnects...


CI builds are breaking

The CI builds are breaking. I believe a downgrade of the gym package will fix the issue. Also see, cannot import name spaces #838!
I am not sure how to resolve this properly. Is , temporarily, setting a specific gym version in setup.py a good solution?
pip install gym==0.9.5 fixes the issue

Hey, thanks for raising, yes we noticed that and will probably fix it in the memory branch, which will soon become the master

Should be fixed via , thanks again https://github.com/reinforceio/tensorforce/commit/d444deef3444dcbbf9f5f0f131748fc6ff8b7894


Creating stats "bare bone" prototype

Oh I reviewed the wrong one, please see my comments in the main repo.