text:
Removing files that would cause duplication when installing local pods

Description
When installing pods as a local dependency received this warning:
...
-> Pod installation complete! There are 24 dependencies from the Podfile and 43 total pods installed.

[!] [Xcodeproj] Generated duplicate UUIDs:

PBXBuildFile -- Pods.xcodeproj/targets/buildConfigurationList:buildConfigurations:baseConfigurationReference:|,buildSettings:|,displayName:|,isa:|,name:|,,baseConfigurationReference:|,buildSettings:|,displayName:|,isa:|,name:|,,defaultConfigurationIsVisible:0,defaultConfigurationName:Release,displayName:ConfigurationList,isa:XCConfigurationList,,buildPhases:buildActionMask:2147483647,displayName:Headers,files:|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,isa:PBXHeadersBuildPhase,runOnlyForDeploymentPostprocessing:0,,buildActionMask:2147483647,displayName:Sources,files:|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,|,isa:PBXSourcesBuildPhase,runOnlyForDeploymentPostprocessing:0,,buildActionMask:2147483647,displayName:Frameworks,files:|,isa:PBXFrameworksBuildPhase,runOnlyForDeploymentPostprocessing:0,,buildActionMask:2147483647,displayName:Resources,files:,isa:PBXResourcesBuildPhase,runOnlyForDeploymentPostprocessing:0,,buildRules:,dependencies:,displayName:EmbraceIO-LOCAL-iOS,isa:PBXNativeTarget,name:EmbraceIO-LOCAL-iOS,packageProductDependencies:,productName:Embrace,productReference:displayName:EmbraceIO-LOCAL-iOS,explicitFileType:wrapper.framework,includeInIndex:0,isa:PBXFileReference,name:EmbraceIO-LOCAL-iOS,path:Embrace.framework,sourceTree:BUILT_PRODUCTS_DIR,,productType:com.apple.product-type.framework,/buildPhases/buildActionMask:2147483647,displayName:Sources,files:displayName:EMBRuntimeContext.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:CrashRecording.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomViewBreadcrumbCollector.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBScreenBreadcrumbCollector.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAddCrashReportToSessionOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBBatteryLevelEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomLogBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBInternalLogBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMemoryWarningEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMessageBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitReportEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPushNotificationBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSeverityLog.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBTapBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebTerminationBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBChargingSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConcreteSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCPUPeggingSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomViewBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBInactiveSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLowPowerSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkPerformanceSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBReachabilitySpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBReactNativeBreadcrumbSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBScreenBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportEventCreator.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUserInfoMetadataProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAppGroupCrashSender.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAppGroupSessionSender.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAppGroupUploader.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAppGroupUploaderConfigDefault.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadModuleConfigDefault.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomBreadcrumbEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomBreadcrumbLogEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomLogBreadcrumbEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomViewBreadcrumbSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDefaultEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDefaultSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBOtelSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPushNotificationEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBReactNativeActionBreadcrumbSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBScreenBreadcrumbSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBTapBreadcrumbEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebBreadcrumbEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebTerminationBreadcrumbEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBBatteryLevelEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBChargingSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCPUPeggingSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBInactiveSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLowPowerSpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMemoryWarningEventPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBReachabilitySpanPayloadContent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPersistenceModule+PersistedSessions.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionRecoveryActionDefault.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionRecoveryActionLegacy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDiskUsage.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDiskUsageReport.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBActivity.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAlertController.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAPIConstants.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAppDelegate.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBAsyncOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBBinaryImageManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBBreadcrumb.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConstants.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCoordinatedFileAccess.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashlyticsWrapper.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportSenderDefault.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportSenderFactory.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomFlow+Protected.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCustomFlow.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDateFormatterProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDebugConstants.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDefaultCreateWebViewVital.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDevice.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBExceptionEventBuilder.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileAppender.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileContainer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileOverwriter.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileStreaming.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileUrlBuilder.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileUrlBuilderProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFlutterEmbrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBGetWebVitalsFromSession.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBInterval.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBJavascriptMessageHandlerFactory.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBJsException.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBJSExceptionUtils.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBKSCrashProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLaunchOptions.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLogger.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNCallbackMessageDelegateWrapper.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkBodyRule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkDomain.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkDomains.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkPerformance.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkRequest+Protected.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkRequest.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNetworkUtils.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBNRemoteConfigInterface.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPrivateConstants.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPropertyUtils.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBProxy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPurchaseFlow.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+ConfigModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+Exceptions.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+PersistenceModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+Protected.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+UploadModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceConfig.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceExtension.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceNativeInterface.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBReachability.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRegistrationFlow.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRegularExpression.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRemoveSessionDataCheck.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRNBundle.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSerializable.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSerializedGroup.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBServer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSession.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionProperties.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBShortSession.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBShouldSendSessionAction.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStackTraceUtils.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStartupMonitor.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamable.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingBreadcrumbManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingDeviceManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingFileManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingMemoryManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingMomentManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingNetworkManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingObject.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingPowerManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingProcessManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingSessionContainer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingSessionManager+PersistenceLayer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingSessionManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingStateManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingUserManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSubscriptionPurchaseFlow.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSwiftDemangler.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSystemEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSystemUtils.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBThreadSafeArray.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBThreadSafeDictionary.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUnityManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBURLConnectionProxy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBURLSessionProxy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUser.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebView.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebViewVital.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWebVitalJavascriptMessageHandler.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBWKNavigationProxy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBStreamingSessionManager+Container.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitManager.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitDiagnosticPayload.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitMetricPayload.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:MetricKitPayload+EMBMetricKitPayload.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBMetricKitUpdater.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSNumber+isBetweenMinAndMax.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBDefaultConfig.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBGlobalConfig.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLocalConfig.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRemoteConfig.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigProvider+MetricKit.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigProvider+PayloadBuilderModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigProvider+WebVitals.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigProvider.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBConfigModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBLocalConfigFetcher.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBRemoteConfigFetcher.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBGlobalConfigMerger.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPayloadBuilderModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload+Breadcrumbs.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload+InternalLogs.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload+Performance.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload+Representable.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceSessionPayload+SessionInfo.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPayloadBuilderFeatureGater.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPayloadSerializer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPersistenceModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBFileDataStore.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionFileStore.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBEventContainer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionMetadataFile.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSpanContainer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBEventResult.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSpanResult.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBEventSerializer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSpanSerializer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBIndexedDataFile.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBPersistenceInfo.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBSessionStoreInfo.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadCacheData.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadModule.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadModuleCache.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadModuleReachabilityMonitor.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadEventOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadLogImageOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadLogOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadNetworkLogOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadSessionOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBUploadStoryImageOperation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportReader.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportStoreHandler.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSArray+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSData+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSDate+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSError+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSFileManager+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSHTTPURLResponse+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSObject+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSString+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSURLConnection+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSURLRequest+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSURLSession+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSUUID+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBHostedSDKTracerState.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBOTelSpan+Validation.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBOTelSpan.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBOTelSpanEvent.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Embrace+InternalTracing.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBTracer.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:RNEmbrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:UIResponder+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:UIViewController+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:UIWindow+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:UNUserNotificationCenter+Embrace.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrash.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashC.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashCachedData.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashDoctor.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashReport.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashReportFixer.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashReportStore.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitorType.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_AppState.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_CPPException.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_Deadlock.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_MachException.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_NSException.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_Signal.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_System.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_User.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashMonitor_Zombie.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCrashSignalInfo.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCPU.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCPU_arm.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCPU_arm64.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCPU_x86_32.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCPU_x86_64.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSCxaThrowSwapper.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSDate.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSDebug.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSDemangle_CPP.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSDemangle_Swift.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSDynamicLinker.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSFileUtils.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSgetsect.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSID.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSJSONCodec.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSJSONCodecObjC.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSLogger.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSMach.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSMachineContext.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSMemory.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSObjC.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSSignalInfo.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSStackCursor.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSStackCursor_Backtrace.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSStackCursor_MachineContext.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSStackCursor_SelfThread.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSString.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSSymbolicator.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSSysCtl.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:KSThread.c,fileRef:displayName:|,includeInIndex:|,isa:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NSError+SimpleConstructor.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Context.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Demangle.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Demangler.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:ManglingUtils.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:NodePrinter.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:OldDemangler.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:Punycode.cpp,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EMBCrashReportSenderDefault.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,displayName:EmbraceIO-LOCAL-iOS-dummy.m,fileRef:displayName:|,includeInIndex:|,isa:|,lastKnownFileType:|,path:|,sourceTree:|,,isa:PBXBuildFile,,isa:PBXSourcesBuildPhase,runOnlyForDeploymentPostprocessing:0,/files/displayName:EMBCrashReportSenderDefault.m,fileRef:displayName:EMBCrashReportSenderDefault.m,includeInIndex:1,isa:PBXFileReference,lastKnownFileType:sourcecode.c.objc,path:EMBCrashReportSenderDefault.m,sourceTree:<group>,,isa:PBXBuildFile,
...

However, depending on your cocoapods version, this might also generate a compilation error.
Solution
Seems like, for some reason, two files that are from the old sdk (.m and .h) were copied into the swift directory of KSCrash.
This PR just removes those two files.

[!NOTE]
Merging to master-lts as this only will affect Embrace SDK 5.x. We can remove this later in master

These should also be merged into the master branch

These should also be merged into the master branch

Yep. Will create a duplicate afterwards

authors: ArielDemarco atreat

repo: embrace-io/KSCrash


text:
Deploy Progetto

Priorità: media
Richiesta
Attualmente il sito builda su una VPS.
C'era una proposta di fare tutto con le Github Pages (credo in progress da testare).
Il backend gira su altra VPS.
Abbiamo le API su HEROKU.
Si potrebbe pensare di hostare KOBO per conto nostro.
Vogliamo discutere di una soluzione unica per tutte le esigenze?
Per ora limitiamoci ad elencare qui sotto idee e proposte poi affrontiamo la questione costi.
Grazie
Risolto?

[ ] Ho verificato che il problema è stato risolto

Ciao, per quanto riguarda build e pubblicazione del sito si potrebbe provare ad utiilizzare le GitHub actions (es https://github.com/marketplace/actions/gha-jekyll-build) e poi pubblicarlo su Github pages. Se volete posso iniziare a fare qualche prova per vedere se è fattibile.

source: gharchive/issue

authors: iltempe trampfox

license: MIT

license_type: permissive

license_source: github-api


text:
fix: Handle partial reads of messages from TCP socket

Hi,
First of all, thank you for making this library, I've found it very nice to work with for my personal SIP-based project so far.
The systems I work with are capable of producing large SDPs, which easily breaks the current assumption in tcp.go that requires all messages to be read in full. Often the headers of an INVITE would be parsed along with the first half of the SDP, and then there would be an attempt to parse the second half of the SDP as if it was a full message.
This commit introduces a mechanism to extract full SIP messages from a continuous stream of bytes.
The current tests appear to pass with this change.
HandlePartialMessages has been added as a way to turn off this functionality for now in case it is needed to work around any issues that may arise. It is enabled by default.

Hi @oystedal . First of all thnx for contributing and this cool approach of solving. I understand issue
Stream parsing I still did not found time to solve, and yes probably TCP will need different parser logic.
I had a quick look and I see there are things for improve/change (correct me if I am wrong)

No multi connection parsing (Single parser used), concurency, races
double scanning could be reduced (parse once you get CR)
callback func may be avoided, instead return once done

I would insist on some benchmarking and having performance near current parser.
If you do not mind I may take this code and tests and do above, BUT as soon I find time. :)

Regarding your comments,

No multi connection parsing

Every TCPTransport will instantiate a new PartialMessageParser, so there is no data race or concurrency issue

double scanning could be reduced (parse once you get CR)

The call to bytes.HasSuffix(currentLine, []byte{'\r', '\n'}) can indeed be simplified to something that in theory should be more efficient.

callback func may be avoided, instead return once done

True, one could return a slice of messages once we're done processing the current slice of bytes. That is probably a better interface.

I would insist on some benchmarking

I agree. I did write a benchmark that I ended up not using. The reason is that the benchmark indicated that the code was extremely performant, so much so that I did not really believe the benchmark. I suspect the Go compiler is quite smart when it comes to avoiding making copies of slices where it's not needed, so one might need to trick the compiler a little to get a useful benchmark.

If you do not mind I may take this code and tests and do above

Absolutely! Feel free to make changes to this PR as you see fit. You can also include portions of it in your own commits, all I ask is that you give me credits in the commit message in that case.

There are some other things that could/should be addressed as well, either in this PR or in the future:

Define a maximum message size (optionally adjustable at build time) so that we do not end up reading an unbounded amount of bytes from the TCP socket (possible DoS)
Right now the PartialMessageParser includes its own parser for content-length, which duplicates the existing content-length parser. Additionally, the content-length header is parsed twice. It could be that the most elegant solution to this is to integrate the current parser more tightly into PartialMessageParser (that is, parse headers as they become available).
The implementation is quite optimistic in its current form. If a message fails to parse we should ideally notify the UA to make it send a BYE and then close the connection. There probably needs to be an API to inform the application that the client has been forcefully disconnected.

Every TCPTransport will instantiate a new PartialMessageParser, so there is no data race or concurrency issue

I am not sure this is true anymore. TCPTransport is just a logic structure for creating and managing TCP connections.
Every new connection (Server or Client) starts reading. In that regard Parser must be thread/goroutine safe.
For benchmarking I think we can reuse some existing. but anyway that will be easy part.

Define a maximum message size (optionally adjustable at build time) so that we do not end up reading an unbounded amount of bytes from the TCP socket (possible DoS)
agree. Issue added #37

Right now the PartialMessageParser includes its own parser for content-length, which duplicates the existing content-length parser. Additionally, the content-length header is parsed twice. It could be that the most elegant solution to this is to integrate the current parser more tightly into PartialMessageParser (that is, parse headers as they become available).
Yes sure.
The implementation is quite optimistic in its current form. If a message fails to parse we should ideally notify the UA to make it send a BYE and then close the connection. There probably needs to be an API to inform the application that the client has been forcefully disconnected.
Not sure for this. But something to also look
https://datatracker.ietf.org/doc/html/rfc3261#section-21.5.7

I am not sure this is true anymore. TCPTransport is just a logic structure for creating and managing TCP connections.
Every new connection (Server or Client) starts reading. In that regard Parser must be thread/goroutine safe.

You are correct, I misunderstood the name. I have moved the partial parser to TCPConnection instead.
I have also updated the interface of the partial parser to return any full messages instead of the previous callback approach.

Added benchmark, used bytes.Buffer, and made other minor changes to make it run approx. 3 times faster compared to the initial implementation.

@oystedal I appreciate changes. Looks better now. I need to recheck other parts as well.
Do you use some tools to generate this or what is your e2e testing?

No problem. I have no other changes planned at this time. Let me know if there's anything else you'd like me to change.
For e2e testing I have used a server I have written using your framework. It communicates with an enterprise grade SIP device that I have access to. All the SIP messages and the SDP I have used in the test is generated by that device, with minor changes for privacy.

@oystedal Stream parsing is now added on main branch and it is default for TCP and WS.
Pls check  and if you do some testing to confirm behavior is correct.
Once I get feedback I will see to push this new release. There is lot of fixes as well on main branch.

I did a few quick tests with your commit and it appears to work well.
require (
	github.com/emiago/sipgo v0.12.2-0.20230907182009-c9e30dc3b384
        // ...
)

Closing this PR as it is covered by https://github.com/emiago/sipgo/commit/c9e30dc3b3847d689da42241dfc7776e08b64dcd.

source: gharchive/pull-request

authors: emiago oystedal

repo: emiago/sipgo


text:
Cannot change colour of markers in callback in 1.0.11

Changing the colour of CircleMarker objects in a callback does not seem to work in 1.0.11, but it works correctly in 0.1.23. Minimal example:
from dash import Dash, html, callback, Output, Input
import dash_leaflet as dl

# Initialize the app
app = Dash(__name__)

# App layout
app.layout = html.Div([
    html.Div(children="Weird Behaviour"),
    html.Hr(),
    dl.Map(center=[0, 0], zoom=10, style={'height': '90vh'}, id='map'),
    html.Button('Break It!', id='break-button')
])

@callback(
    Output(component_id='map', component_property='children'),
    Input(component_id='break-button', component_property='n_clicks')
)
def break_map(n_clicks):
    if n_clicks is None:
        map_components = [
            dl.TileLayer(),
            dl.CircleMarker(radius=2, center=(0, 0),
                            color='rgb(255, 0, 0)'
                            ),
            dl.CircleMarker(radius=2, center=(0.1, 0),
                            color='rgb(0, 255, 0)'
                            ),
            dl.CircleMarker(radius=2, center=(0, 0.1),
                            color='rgb(0, 0, 255)'
                            ),
        ]
    else:
        map_components = [
            dl.TileLayer(),
            dl.CircleMarker(radius=2, center=(0, 0),
                            color='rgb(255, 0, 0)'
                            ),
            dl.CircleMarker(radius=2, center=(0, 0.1),
                            color='rgb(0, 0, 255)'
                            ),
        ]
    return map_components

# Run the app
if __name__ == '__main__':
    app.run(debug=True)

The marker will have the same colour as the marker in the corresponding position in map_components initially.

I have the same problem.

repo: emilhe/dash-leaflet


text:
Style feature to have label truncate by default

In some context, it would be useful to have ui.label(txt) defaults to truncate, such as we don't have to change them all for ui.add(egui::Label::new(txt).truncate(true)). Likewise, it would be nice to have a ui.label_truncated() helper (though each might be suited for different situations).
As per:

https://github.com/rerun-io/rerun/issues/4161#issuecomment-2089947539

Please also refer to #3900 and #4045 when working.

Related 3900
Related 4045

Would ui.style().truncate = Some(true); solve most of the problems @abey79, or do you still want label_trunc and label_wrap?

I think ui.style().truncate = Some(true); would actually solve this more elegantly than dedicated ui.label_trunc. It's also more in-line with the bigger CSS-like styling story.

authors: abey79 emilk rustbasic

repo: emilk/egui


text:
Fix doc directory during release-note copy.

The doc directory is just X.Y, not X.Y.Z.
Signed-off-by: Flynn flynn@datawire.io

Merging to test this fix.

repo: emissary-ingress/emissary


text:
WIP: Sync reasoner factpp

Add FaCT++ to supported reasoners accessible with sync_reasoner().

Reading the reasoned ontology from an rdflib graph back into the owlready2 triplestore needs to be implemented...

repo: emmo-repo/EMMO-python


text:
Discuss: Support Llamaindex connector for MeltanoHub, which has 500+ open source Singer data connectors

A generic interface into hub.meltano.com would be great. In that paradigm, the source connectors are called "extractors" or "taps".
There are a few different ways we could create generic connection interfaces, which I can highlight below...
Generally though, each connector would need:

The connector {variant}/{name} string combo, and/or pip_url of the connector.
The config info for the connector, which is generally passed as a JSON file, but which could be defined by users in a Python dictionary object or an array of key-value pairs.
Optionally: the stream and property selection rules, either as a glob of inclusion/selection rules, or as a Singer "catalog" JSON artifact. Perhaps not needed in a V1, but these could let users pick and choose which datasets and/or properties they are interested in.

A simple "V1" MVP might ask for a single stream name, or an array of stream names.

An example:
tap-asana - Meltano Hub
Connector info:

name: tap-asana, variant: singer
metadata: https://github.com/meltano/hub/blob/main/_data/meltano/extractors/tap-asana/singer-io.yml or (raw)
pip_url: tap-asana

Sample config:
asana_config = {
    "client_id": os.environ.get("TAP_ASANA_CLIENT_ID"),
    "client_secret": os.environ.get("TAP_ASANA_CLIENT_SECRET"),
    "refresh_token": os.environ.get("TAP_ASANA_REFRESH_TOKEN"),
}

Processing Singer output
Singer outputs data as a series of json lines, generally one record which should be easy for the libraries to parse generically.
List of connectors:
https://hub.meltano.com/extractors
This isn't a full list, since many are being created that aren't already on the Hub, but it gives a good idea of the existing depth and breadth of the ecosystem.
How to list on LLama-Hub
To not spam the index, we could just list as a single item on the LlamaHub: either as "MeltanoHub Singer Taps", or "Singer Extractors" generically, or similar.
Thinking about the "right" abstraction layer
I think this could be really powerful, since it could plug in Llamaindex, Langchain, and other GPT-like applications into a broad ecosystem of already existing connectors.
Since the vast majority of Singer connectors are already pip installable, this should fit well with existing paradigms that Llamaindex is using.
I may have some cycles to contribute to this integration but I first wanted to log this issue here to assess interest level, and discuss if there are any potential pitfalls or "gotchas" that others might see.

We'd be eager to chat about how we could help with this. The wider Singer community has put a lot of work into extractors and if we could make it easier to use them for LLM applications that'd be a huge win for everyone!

authors: aaronsteers tayloramurphy

repo: emptycrown/llama-hub


text:
SimpleDirectoryReader issue

In addition to #81, Importing the SimpleDirectoryReader from llama_index and then trying to parse certain files throughout a directory as shown in this page gives the following error: 'str' object has no attribute 'parser_config_set'. Any ideas? TIA!

Appears to be fixed, closing for now as well

authors: EmanuelCampos pruthvishetty


text:
Fix LabeledItem to pass marqueeOn prop

Enact-DCO-1.0-Signed-off-by: Roy Sutton roy.sutton@lge.com
Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
LabeledItem had no way to adjust when it would marquee. A use case existed where
it was used as a non-focusable component, so the default marqueeOn of "focus"
prevented it from being able to marquee.
Resolution
Pass marqueeOn prop to label and contents.
Additional Considerations
Another possible solution is to modify the component to detect spotlightDisabled and automatically set marqueeOn for the items.  This seemed a bit too magical and we'd need to make a similar change to all focusable components for consistency. This solution makes a very small change and gives developers the tools they need to accomplish the use case desired.
I decided to not pass along any additional marquee properties as they were not relevant to this request.
Links
ENYO-6100
Comments

Did you investigate expanding support for marqueeOn in MarqueeController? I wonder if it should have API compatibility with MarqueeDecorator as it behaves as a proxy for multiple marquees.
I'm good with the current approach as is as expanding MarqueeController would be compatible with this API but curious if we should investigate further separately.

I did think about it briefly but there is already some weird coupling between the controller and the decorator and it seemed like teasing that out right now would possibly introduce a big chance of regression.  Marquee is already one of the biggest sources of bugs and simplifying the implementation would always be great... but right now didn't seem like the time.

By coupling, I meant overlapping concerns.  Of course they're coupled since Controller is supposed to control Decorator.

repo: enactjs/enact


text:
ENYO-4068: Fix reading out aria-valuetext when initial rendering

Issue Resolved / Feature Added
The 'aria-valuetext' is triggered as soon as value is set. If aria-valuetext is set from system service value (e.g Settings App), we can hear this sound.
Resolution
Set 'slider' role when onFocus event of Slider.
Additional Considerations
Links
ENYO-4068
Comments
Enact-DCO-1.0-Signed-off-by: Bongsub Kim bongsub.kim@lgepartner.com

Superseded by #886


text:
Debug server not reloading with custom run command

The reloader isn't trigged when some source file is edited if a custom command runs the development server.
def command_run_develop(db: django_orm.Session,
                        host: str='127.0.0.1',
                        port: int=8080,
                        debug: bool=True,
                        reloader: bool=True) -> None:
    run_wsgi(app, host, port, debug, reloader)

app = App(commands=[Command('run_develop', run_develop)])

My guess is that this is related to app: App not to be injectable on custom commands. Can we inject app: App in such commands?

If we do re-introduce an apistar run at some point I think it's likely that we won't call into the codebase with python, but rather run it as a separate subprocess, and fully kill/restart the process on changes.
Closing in the meantime, since this isn't currently relevant.

authors: pslacerda tomchristie

repo: encode/apistar

license_source: bigquery


text:
Armin 302 navbar

closes #302

did the design with the background first, but there is no way to reduce padding of the navbar, as the UI elements increased b/c of the background which is bigger than the icon
changed the design to using a darker color to highlight the Scan icon (Didier first suggested to use blue, before he suggested to use a background color, the issue with blue was that it looks like Scan was already selected)

version: light blue container

version: light blue container minimum sized container, but then hardly visible

version: dark blue stroke of the scan icon, currently implemented

I have checked with @gr8Mu1 how we could remove the BottomNavigationBars padding, and we didn't manage.
I like the current version with the stroke, what do you think @brenzi?

To approach didiers design, I' d say we shold get rid of the ceremony page in the navbar now. Can we just have a dummy ceremony box with a button to the current ceremony page in the meantime, before tge box js ready?

To approach didiers design, I' d say we should get rid of the ceremony page in the navbar now. Can we just have a dummy ceremony box with a button to the current ceremony page in the meantime, before the box is ready?
About the scan highlight, I don't really care

As discussed with @brenzi we leave the ceremony tab in for now, we will remove it in the step where we swap the ceremony UX

authors: brenzi clangenb gr8Mu1

repo: encointer/encointer-wallet-flutter


text:
Config file includes app module

fix #266

[ ] tests

https://github.com/pallets/click/issues/2321

Test conflict when freeze is invoke with parameter app and app is specify in config also.

Someone with windows there?

repo: encukou/freezeyt


text:
RTMP Extension Support

Hey @eneim ,
I was wondering if and when you will support RTMP which was recently added in Exoplayer 2.5.
Thanks

I was able to retrieve a stream from an rtmp// url however the app crashes with the following error from time to time:
A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 17672 (Loader:Extracto) 02-22 20:05:53.086 509-509/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 02-22 20:05:53.086 509-509/? A/DEBUG: Build fingerprint: 'google/angler/angler:6.0.1/MMB29Q/2480792:user/release-keys' 02-22 20:05:53.087 509-509/? A/DEBUG: Revision: '0' 02-22 20:05:53.087 509-509/? A/DEBUG: ABI: 'arm64' 02-22 20:05:53.088 509-509/? A/DEBUG: pid: 17056, tid: 17672, name: Loader:Extracto >>> com.exoplayer.videoplayer <<< 02-22 20:05:53.088 509-509/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
I believe that there is not the correct Type set up in this code:
DataSource.Factory mediaDataSourceFactory = buildDataSourceFactory(transferListener);

    int type =
        Util.inferContentType(isEmpty(extension) ? mediaUri.getLastPathSegment() : "." + extension);
    switch (type) {
      case C.TYPE_SS:
        return new SsMediaSource(mediaUri, buildDataSourceFactory(transferListener),
            new DefaultSsChunkSource.Factory(mediaDataSourceFactory), handler, null);
      case C.TYPE_DASH:
        return new DashMediaSource(mediaUri, buildDataSourceFactory(transferListener),
            new DefaultDashChunkSource.Factory(mediaDataSourceFactory), handler, null);
      case C.TYPE_HLS:
        return new HlsMediaSource(mediaUri, mediaDataSourceFactory, handler, null);
      case C.TYPE_OTHER:

I think you should add a RTMP type in here:  case C.TYPE_OTHER:.
Here a few resources for the issue:
https://github.com/ant-media/LibRtmp-Client-for-Android/issues/2
https://github.com/google/ExoPlayer/tree/release-v2/extensions/rtmp

@lumyus I just release 3.1.0 last week to update ExoPlayer to 2.5.1, can you take a look. Generally I don't touch the player level, so you will get whatever ExoPlayer supports. If you need help on creating custom MediaSource I will have a deep dive into it :D.

@eneim
Thanks man! Yes I already updated to 2.5.1 however there is still some
issue. I get this in the logcat that I posted. Any idea on what might be
the problem?
Keep up the good work
Am 10.09.2017 21:15 schrieb "Nam Nguyen Hoai" notifications@github.com:

@lumyus https://github.com/lumyus I just release 3.1.0 last week to
update ExoPlayer to 2.5.1, can you take a look. Generally I don't touch the
player level, so you will get whatever ExoPlayer supports. If you need help
on creating custom MediaSource I will have a deep dive into it :D.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eneim/toro/issues/253#issuecomment-328398109, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWoWU2j-pJzuXKtpyWAB9tI1jRiyXYmmks5shJeygaJpZM4PSYEZ
.
{"api_version":"1.0","publisher":{"api_key":"
05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":
{"external_key":"github/eneim/toro","title":"eneim/toro","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/
143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","
avatar_image_url":"https://cloud.githubusercontent.com/
assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png
","action":{"name":"Open in GitHub","url":"https://github.com/eneim/toro
"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eneim in #253:
@lumyus I just release 3.1.0 last week to update ExoPlayer to 2.5.1, can
you take a look. Generally I don't touch the player level, so you will get
whatever ExoPlayer supports. If you need help on creating custom
MediaSource I will have a deep dive into it :D."}],"action":{"name":"View
Issue","url":"https://github.com/eneim/toro/issues/253#
issuecomment-328398109"}}}

@lumyus Got it. Seems that current helpers doesn't help you to create non-Default DataSource Factory. There is a plan to make my helpers more generic, seems that it is time to speed it up.

@eneim great! Ping me if you need more detailed logcat or when you are done with the more generic helpers. :D

@lumyus It turns out that ExoPlayer by default will detect your source if it is RTMP or not, and if you also include the rtmp extension (seems that you did), it will use rtmp as normal. In your case, I guess the cause is closer to the ExoPlayer/rtmp extension. Can you ask for that issue on ExoPlayer repository first? The logcat actually tells something about native code error which maybe the hardware ability to decode your stream.

Acutally the update of the Exoplayer and the extension to 2.5.2 fixed the
issue. Everything is working fine now!
Thanks for the help :)
Am 12.09.2017 06:57 schrieb "Nam Nguyen Hoai" notifications@github.com:

@lumyus https://github.com/lumyus It turns out that ExoPlayer by
default will detect your source if it is RTMP or not, and if you also
include the rtmp extension (seems that you did), it will use rtmp as
normal. In your case, I guess the cause is closer to the ExoPlayer/rtmp
extension. Can you ask for that issue on ExoPlayer repository first? The
logcat actually tells something about native code error which maybe the
hardware ability to decode your stream.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/eneim/toro/issues/253#issuecomment-328735985, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWoWU_3zv_ryeNurwZMG_IYSLNwbz8DEks5shg9PgaJpZM4PSYEZ
.
{"api_version":"1.0","publisher":{"api_key":"
05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":
{"external_key":"github/eneim/toro","title":"eneim/toro","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/
143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","
avatar_image_url":"https://cloud.githubusercontent.com/
assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png
","action":{"name":"Open in GitHub","url":"https://github.com/eneim/toro
"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eneim in #253:
@lumyus It turns out that ExoPlayer by default will detect your source if
it is RTMP or not, and if you also include the rtmp extension (seems that
you did), it will use rtmp as normal. In your case, I guess the cause is
closer to the ExoPlayer/rtmp extension. Can you ask for that issue on
ExoPlayer repository first? The logcat actually tells something about
native code error which maybe the hardware ability to decode your
stream."}],"action":{"name":"View Issue","url":"https://github.
com/eneim/toro/issues/253#issuecomment-328735985"}}}

@lumyus that sounds great!

authors: eneim lumyus

repo: eneim/toro


text:
CalTRACK Issue: Ensure that AEU includes all days in reporting period

Prerequisites

[x] Are you opening this issue in the correct repository (caltrack/grid/seat)?
[x] Did you perform a search of previous Github issues to check if this issue has been previously considered?

Article reference number in CalTRACK documentation (optional):
3.6.1 and Technical Appendix 2.4.1, Test 1, Method A item 6(c), and Method B item 3.
(Also, see original issue #100, closed during CalTRACK transition from OEE to EM2.)
Description
Background: The calculation of Avoided Energy Use (AEU) does not describe how to handle days in the reporting period with missing weather data. Our understanding is that these days may be removed ("masked") from the calculation of AEU, causing gaps, and possibly underestimating true savings. The documentation concerning weather data sufficiency during the reporting period does not appear to require coverage of all days in the reporting period.
Issue: Example impact: If a project reduces baseline/continuous energy use and 20% of the weather data is missing during the reporting period, 20% of true savings will be excluded and any associated payments will be 20% lower than deserved for that project.
Validation: We searched the current methods for reporting period weather data sufficiency requirements and identified only references to the phrase "sufficient data quality", which does not appear to be defined.
Requested CalTRACK change: If confirmed, this problem could be resolved several ways:

Require full coverage of weather data during the Reporting period; or
By truing up the reporting period energy shortfall using billing data (the "ground truth" of energy use). For example, if the summation of interval data during the reporting period does not match bill data for the same period we could scale the calculated AEU using the ratio of [Billed energy use] / [Sum of daily energy use].

Proposed test methodology

Check existing CalTRACK projects to identify projects where Reporting period data covers <100% of the days covered, and record results.
Identify the reasons for any data shortfalls discovered (e.g. missing weather data? other problem?)
Implement new methods like those listed above and rerun check (1).

Acceptance Criteria
All project AEU values cover all days in reporting periods.

Notes from working group meeting 10/23/19:

Kyle (?) asked if someone could confirm current CalTRACK methods exclude energy savings from days in the reporting period with missing weather data. Hassan responded yes, he believes this is the case.
Jon suggested this would be easy to test by deleting some weather data and looking for changes in AEU.
Kyle suggested this should be an easy update to the methods, to incorporate some interpolation or smoothing for missing days.

Agree that interpolating short periods of missing weather data should be incorporated into methods as an update. Are there currently criteria on SELECTING weather stations for use? For instance, we would probably want to avoid selecting a weather station with sporadic data in the first place.

authors: danrubado steevschmidt

repo: energy-market-methods/caltrack


text:
add (data) leak under information content security

Please discuss if leak or data-leak is better.
In IntelMQ we are using leak: https://github.com/certtools/intelmq/blob/develop/docs/Data-Harmonization.md
and data-leak would be consistent with the existing data-loss

I removed the changes in the human version entirely

On 16.09.2019, at 13:37, Sebastian notifications@github.com wrote:
I removed the changes in the human version entirely

Sebastian, did you just commit directly to the enisaeu repo after we did the v1.2 release?

On 16.09.2019, at 13:37, Sebastian @.***> wrote: I removed the changes in the human version entirely
Sebastian, did you just commit directly to the enisaeu repo after we did the v1.2 release?

No, I pushed to my fork. I don't even have write privileges for that repository.

On 16.09.2019, at 13:41, Sebastian notifications@github.com wrote:
On 16.09.2019, at 13:37, Sebastian @.***> wrote: I removed the changes in the human version entirely
Sebastian, did you just commit directly to the enisaeu repo after we did the v1.2 release?
No, I pushed to my fork. I don't even have write privileges for that repository.

Ah okay, thanks for the clarification. Yes, that makes sense. Okay, then we can merge that in at the next meeting.

authors: aaronkaplan sebix


text:
Fix/issue 748

Fixes: #748

Please let me know if I should squash this into a single commit, this is ready for another review. Very excited to have a PR merged here :smile:

Will check it out! It always fine to have a dirty commit history in a PR. It will always be squashed when merging.

authors: FrankApiyo MartijnR

repo: enketo/enketo-core


text:
The Explanation of the iCAN's implementation in tab. 4

I'm sorry to interrupt, but I noticed that the paper tab. 4 makes use of iCAN, and I'd like to ask about the implementation details.
Since the transformer-base methods use the Hungarian matching algorithm, how can the results of iCAN be introduced for assistance?
Also could you provide the corresponding code ideas, Thank you.

The transformer-based methods use the Hungarian matching algorithm only for training, not testing. Instead, in our setting, iCAN is only used to evaluate the quality of the detected boxes in the test set.
To be specific:
For the two-stage method iCAN, it is fed with {(b(h), b(o))}_{i=1}^{N} for each image in the test set, and outputs {p_{hoi}}_{i=1}^{N}. Here N is the number of candidate H-O pairs in the image, and b(h), b(o), p_{hoi} is human bbox, object bbox, hoi prediction.
Originally, {(b(h), b(o))}_{i=1}^{N} is from Fast-RCNN detection and exhaustive pairing. In Tab.4, we replace it with the output of our one-stage method, and N is fixed as query size. In the implementation, we save the output of our models and feed it into iCAN via their open-source code.
For the results in Tab.4:
The performance is better than the original iCAN because of the improved quality of H-O pairing. It is worse than the one-stage method because iCAN is not exactly trained via one-stage DETR. However, with higher-quality H-O boxes, iCAN will perform better. Thus, it can measure the quality of one-stage H-O pairing.
Hope it helps.


text:
Documentation / how to start

Hi,
thank you for programming enocean implementation for javascript. I appreciate it a lot!
I've got a 2 channel relay from NodOn and a USB300. I turned the relay into pairing mode and node-red received:
{     "payload": "550009070156d20460e405125bbd0001ffffffff3700cc",     "meta": {         "type": "radio-erp1",         "rorg": 210,         "senderId": "05125bbd",         "destinationId": "ffffffff",         "subTelNum": 1,         "rssi": 55,         "timestamp": 1564143342864,         "status": 0     },     "_msgid": "52fb21e6.6d06e" }
How do I pair them and control the relay from node-red afterwards?

here is an example flow for the nodeOn module... the module uses a bidirectional teach in method which makes it one of the more complex parts of the spec.
[{"id":"a5e956de.749b68","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"f23f04f5.51e628","type":"enocean-in","z":"a5e956de.749b68","serialport":"6f46a875.7265b8","name":"in","x":90,"y":80,"wires":[["ca588d44.5387d","eced4012.4e249"]]},{"id":"ca588d44.5387d","type":"enocean-actor","z":"a5e956de.749b68","name":"Aktor 1","channel":"10","x":280,"y":120,"wires":[["eced4012.4e249"],["fbdde8aa.bc7da8"]]},{"id":"539b496c.88c8c8","type":"inject","z":"a5e956de.749b68","name":"LRN","topic":"","payload":"{\"type\":\"LRN\",\"duration\":30}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":90,"y":160,"wires":[["ca588d44.5387d"]]},{"id":"fbdde8aa.bc7da8","type":"enocean-out","z":"a5e956de.749b68","serialport":"6f46a875.7265b8","name":"","logOutput":true,"x":580,"y":160,"wires":[[]]},{"id":"fdc10fd0.cb5ff","type":"inject","z":"a5e956de.749b68","name":"on","topic":"","payload":"{\"meta\":{\"eep\":\"d2-01-12\",\"channel\":10,\"type\":\"data\",\"data\":1},\"data\":{\"CMD\":{\"value\":1},\"I/O\":{\"value\":30},\"OV\":{\"value\":100}}}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":330,"y":200,"wires":[["fbdde8aa.bc7da8"]]},{"id":"cb982957.07f248","type":"inject","z":"a5e956de.749b68","name":"off","topic":"","payload":"{\"meta\":{\"eep\":\"d2-01-12\",\"channel\":10,\"type\":\"data\",\"data\":1},\"data\":{\"CMD\":{\"value\":1},\"I/O\":{\"value\":0},\"OV\":{\"value\":0}}}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":330,"y":240,"wires":[["fbdde8aa.bc7da8"]]},{"id":"8b144f59.4041c","type":"inject","z":"a5e956de.749b68","name":"request state","topic":"","payload":"{\"meta\":{\"eep\":\"d2-01-12\",\"channel\":10,\"type\":\"data\",\"data\":3},\"data\":{\"CMD\":{\"value\":3},\"I/O\":{\"value\":30}}}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":300,"y":280,"wires":[["fbdde8aa.bc7da8"]]},{"id":"da4ebd30.77203","type":"inject","z":"a5e956de.749b68","name":"request external interface","topic":"","payload":"{\"meta\":{\"eep\":\"d2-01-12\",\"channel\":10,\"type\":\"data\",\"data\":3},\"data\":{\"CMD\":{\"value\":12},\"I/O\":{\"value\":30}}}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":260,"y":320,"wires":[["fbdde8aa.bc7da8"]]},{"id":"1f9d94dc.02bb7b","type":"inject","z":"a5e956de.749b68","name":"delay off 2s","topic":"","payload":"{\"meta\":{\"eep\":\"d2-01-12\",\"channel\":10,\"type\":\"data\",\"data\":11},\"data\":{\"CMD\":{\"value\":11},\"I/O\":{\"value\":30},\"AOT\":{\"value\":20}}}","payloadType":"json","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":310,"y":360,"wires":[["fbdde8aa.bc7da8"]]},{"id":"eced4012.4e249","type":"debug","z":"a5e956de.749b68","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":570,"y":80,"wires":[]},{"id":"6f46a875.7265b8","type":"enocean-config-node","z":"","serialport":"/dev/ttyUSB0"}]

Something happened by putting both into pairing mode. I got this response:
{     "payload": {         "PF": {             "name": "Power Failure",             "unit": "",             "rawValue": 0,             "value": "0b0",             "description": "Power Failure Detection disabled/not supported"         },         "PFD": {             "name": "Power Failure Detection",             "unit": "",             "rawValue": 0,             "value": "0b0",             "description": "Power Failure not detected/not supported/disabled"         },         "CMD": {             "name": "Command ID",             "unit": "",             "rawValue": 4,             "value": "0x04",             "description": "ID 04"         },         "OC": {             "name": "Over current switch off",             "unit": "",             "rawValue": 0,             "value": "0b0",             "description": "Over current switch off: ready / not supported"         },         "EL": {             "name": "Error level",             "unit": "",             "rawValue": 3         },         "I/O": {             "name": "I/O channel",             "unit": "",             "rawValue": 1,             "min": "0x00",             "max": "0x1D",             "description": "Output channel (to load)",             "value": 1         },         "LC": {             "name": "Local control",             "unit": "",             "rawValue": 1         },         "OV": {             "name": "Output value",             "unit": "",             "rawValue": 0,             "value": "0x00",             "description": "Output value 0% or OFF"         }     },     "meta": {         "type": "radio-erp1",         "destinationId": "ffffffff",         "subTelNum": 1,         "rssi": 52,         "timestamp": 1564227386263,         "status": 0,         "rorg": 210,         "eep": "d2-01-12",         "payload": "046180",         "senderId": "05125bbd",         "raw": "550009070156d204618005125bbd0001ffffffff34004d",         "name": "",         "actorName": "Aktor 1"     },     "_msgid": "be29c4e8.4ef5b8" }
How do I turn on and off Channel 1 and 2?

here you can see all telegrams you can send to the device and what each value does.
https://enocean-js.github.io/enocean-js/?eep=d2-01-00
so basically to switch on/off you send cmd 1:
Where I/O value is the channel (0 or 1) and OV is the new value to switch to where 0 is off and 100 is on.
{
  "data": {
    "CMD": 1,
    "DV": 0,
    "I/O": 1,
    "OV": 0
  },
  "meta": {
    "eep": "d2-01-12",
    "channel": 10,
    "data": 1
  }
}

Thank you very much! That link is the kind of source I was looking for. Maybe you should mention it in the readme.md.
Closing ticket for now.

added link to readme.md

Hey ! this is what I do :

How do you I turn the relay into pairing mode ?

authors: Holger-Will ptorrent rollercontainer

repo: enocean-js/enocean-js


text:
ensenso_camera_node runs (with a warning), but  rosrun ensenso_camera request_data results in "Illegal instruction (core dumped)"

Jetson Nano 4G Jetpack 4.6. ROS Melodic. SDK ensenso-sdk-3.4.743-arm64.deb. NxView works.
Trying to follow this tutorial: https://wiki.ros.org/ensenso_driver/Tutorials/FirstSteps
Level beginner..
harper@nano-4G-4:~$ rosrun ensenso_camera ensenso_camera_node
[ INFO] [1694175730.456104834]: Initializing nodelet with 4 worker threads.
[ INFO] [1694175739.225077617]: Opened camera with serial number 'redacted'.
[ WARN] [1694175739.225393977]: Camera 'redacted' has an internal link (i.e. it is either extrinsically calibrated (workspace- or hand-eye) or has a link to another camera), but camera and target frame are equal, which means that neither a link nor a target frame has been provided. The images and 3d data retreived from the camera are transformed by the NxLib with the transform stored in the camera's link node, however, this transform is not known to tf. Please provide a link or target frame in order for the transform to be published.
Requesting data from the camera fails:
harper@nano-4G-4:~$ rosrun ensenso_camera request_data
Illegal instruction (core dumped)
Not sure where to look for clues.

After a quick research I think 'Illegal instruction (core dumped)' could have something to do with your memory, maybe not having enough of it. You could try to request less data from the camera and see if that works. By default, the script requests all possible data, see https://github.com/ensenso/ros_driver/blob/master/ensenso_camera/scripts/request_data.

Just to make sure: the command that crashes with the Illegal instruction message is the request_data one? The ensenso_camera_node continues to run in the background?
If so, there is probably some problem with your installation of ROS, Python or some other library that is used by those two. The request_data node is a Python script that only uses ROS functionality to query the data. The only code from this repository and the Ensenso SDK that runs in that process is that Python script, so the crash must be caused by something on a lower level.
Unfortunately I have no idea how to debug that properly, so let's confirm that the problem is with the request_data script first.

I found this issue that might very well be it: https://github.com/numpy/numpy/issues/18131
Could you try to set the environment variable OPENBLAS_CORETYPE=ARMV8 as suggested in that issue?

I tried other scripts already. e.g.
harper@nano-4G-4:~$ rosrun ensenso_camera request_data_mono
Illegal instruction (core dumped)
I also just tried lightening the load in request data to just raw images (not sure if tis is what you meant):
goal.request_raw_images = ros2py.get_param(node, "raw_images", True)
#goal.request_rectified_images = ros2py.get_param(node, "rectified_images", True)
#goal.request_disparity_map = ros2py.get_param(node, "disparity_map", True)
#goal.request_depth_image = ros2py.get_param(node, "depth_image", True)
#goal.request_point_cloud = ros2py.get_param(node, "point_cloud", True)
#goal.request_normals = ros2py.get_param(node, "normals", True)

The camera node seems to be OK, with the following topics created (but idle?):
harper@nano-4G-4:~$ rostopic list
/access_tree/cancel
/access_tree/feedback
/access_tree/goal
/access_tree/result
/access_tree/status
/calibrate_hand_eye/cancel
/calibrate_hand_eye/feedback
/calibrate_hand_eye/goal
/calibrate_hand_eye/result
/calibrate_hand_eye/status
/calibrate_workspace/cancel
/calibrate_workspace/feedback
/calibrate_workspace/goal
/calibrate_workspace/result
/calibrate_workspace/status
/camera_info
/depth/camera_info
/depth/image
/depth/projected_depth_map
/diagnostics
/disparity_map
/execute_command/cancel
/execute_command/feedback
/execute_command/goal
/execute_command/result
/execute_command/status
/fit_primitive/cancel
/fit_primitive/feedback
/fit_primitive/goal
/fit_primitive/result
/fit_primitive/status
/get_parameter/cancel
/get_parameter/feedback
/get_parameter/goal
/get_parameter/result
/get_parameter/status
/locate_pattern/cancel
/locate_pattern/feedback
/locate_pattern/goal
/locate_pattern/result
/locate_pattern/status
/point_cloud
/point_cloud_color
/project_pattern/cancel
/project_pattern/feedback
/project_pattern/goal
/project_pattern/result
/project_pattern/status
/project_telecentric/cancel
/project_telecentric/feedback
/project_telecentric/goal
/project_telecentric/result
/project_telecentric/status
/projected_point_cloud
/raw/left/camera_info
/raw/left/image
/raw/right/camera_info
/raw/right/image
/rectified/left/camera_info
/rectified/left/image
/rectified/right/camera_info
/rectified/right/image
/request_data/cancel
/request_data/feedback
/request_data/goal
/request_data/result
/request_data/status
/rosout
/rosout_agg
/set_parameter/cancel
/set_parameter/feedback
/set_parameter/goal
/set_parameter/result
/set_parameter/status
/texture_point_cloud/cancel
/texture_point_cloud/feedback
/texture_point_cloud/goal
/texture_point_cloud/result
/texture_point_cloud/status
/tf
/tf_static

That cleared the error. Thank you. Because I have Melodic which is python2 I had to change the shebang and it appears to be working! Back to the tutorial :)
harper@nano-4G-4:~$ rosrun ensenso_camera request_data
[INFO] [1694183126.632752]: Connecting to action server request_data ...
[INFO] [1694183126.851811]: Connected!
[INFO] [1694183140.185542]: Data successfully requested.
[INFO] [1694183145.596383]: Data successfully requested.

Nice :+1: You can probably fix it more permanently by installing a different version of numpy. Or just keep the variable set :wink:

authors: benthie onthesofa saierd


text:
Investigate the possibility of removing all/many of to_display_text builtins on errors

New errors should always define a to_display_text method. For some reason the convention is that they are now defined as builtin methods but often that feels like an overkill. We should just be able to define the method on the type in Enso.
This is a follow up on https://github.com/enso-org/enso/pull/6246#discussion_r1163484058

So as I was almost done moving builtins when I realized why there was one reason why it was done that way.
Take for example No_Such_Method.Error. If we do not import Errors.Common module we only rely on builtin error types. The type obviously has the constructor and such but it does not have to_display_text in scope because the latter is no longer a builtin method but a regular method.
Is that a problem in reality for users? Not really, since most of the time we import Base.Main which imports those as well. It's a bit tedious for our internal tests using micro-distribution.

repo: enso-org/enso


text:
Extension matcher documentation doesn't generate a link to the xds Matcher type

Title:  Extension matcher documentation doesn't generate a link to the xds Matcher type
Description:
In the extension matcher docs, the documentation generator doesn't generate a reference link for the xds.type.matcher.v3.Matcher.
The actual sphinx doc looks like this. Note How there is no :ref: generated for the xds.type.matcher.v3.Matcher type:
.. code-block:: json

  {
    "matcher": "{...}",
    "xds_matcher": "{...}",
    "extension_config": "{...}"
  }

.. _envoy_v3_api_field_extensions.common.matching.v3.ExtensionWithMatcher.matcher:

matcher
  (:ref:`config.common.matcher.v3.Matcher <envoy_v3_api_msg_config.common.matcher.v3.Matcher>`) The associated matcher. This is deprecated in favor of xds_matcher.

.. _envoy_v3_api_field_extensions.common.matching.v3.ExtensionWithMatcher.xds_matcher:

xds_matcher
  (.xds.type.matcher.v3.Matcher) The associated matcher.

.. _envoy_v3_api_field_extensions.common.matching.v3.ExtensionWithMatcher.extension_config:

extension_config
  (:ref:`config.core.v3.TypedExtensionConfig <envoy_v3_api_msg_config.core.v3.TypedExtensionConfig>`, *REQUIRED*) The underlying extension config.

Huh, looks like the autogenerated docs aren't WAI here:
https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/common/matching/v3/extension_matcher.proto.html
cc @adisuissa @phlax thoughts?

at a guess its because its viewed as "external" to the docs, and only the internal protos are linked
i can look into this further to confirm or otherwise
if my suspicion is correct i can possibly look at adding a dictionary of proto -> urls so we can add links to upstream protos

if my suspicion is correct i can possibly look at adding a dictionary of proto -> urls so we can add links to upstream protos

If possible, it would probably be helpful to include the docs for all the xds repository types.

@phlax can you pls no-stale this?

authors: alyssawilk jpeach phlax

repo: envoyproxy/envoy


text:
build: disable http3 does not work as specified in docs

I am running bazel build --//source/extensions/wasm_runtime/v8:enabled=false --//bazel:http3=False --define google_grpc=disabled //source/exe/..."
I see this output:
[5,451 / 7,762] Compiling source/common/common/utility.cc; 8s darwin-sandbox ... (16 actions, 15 running)
[5,470 / 7,762] Compiling source/extensions/filters/network/mongo_proxy/bson_impl.cc; 8s darwin-sandbox ... (16 actions, 15 running)
[5,484 / 7,762] Compiling source/extensions/filters/http/grpc_json_transcoder/http_body_utils.cc; 9s darwin-sandbox ... (16 actions, 15 running)
[5,497 / 7,762] Compiling quiche/http2/hpack/varint/hpack_varint_decoder.cc; 6s darwin-sandbox ... (16 actions, 15 running)
[5,541 / 7,762] Compiling quiche/http2/decoder/payload_decoders/settings_payload_decoder.cc; 7s darwin-sandbox ... (16 actions, 15 running)
[5,568 / 7,762] Compiling quiche/http2/hpack/decoder/hpack_entry_decoder.cc; 7s darwin-sandbox ... (16 actions, 15 running)
[5,619 / 7,762] Compiling quiche/http2/core/http2_trace_logging.cc; 7s darwin-sandbox ... (16 actions, 15 running)
[5,652 / 7,762] Compiling source/common/stats/symbol_table.cc; 10s darwin-sandbox ... (16 actions running)
[6,176 / 7,762] Compiling source/common/http/header_map_impl.cc; 14s darwin-sandbox ... (16 actions running)
[6,201 / 7,762] Compiling source/server/config_validation/dns.cc; 10s darwin-sandbox ... (16 actions, 15 running)
[6,239 / 7,762] Compiling quiche/quic/core/quic_alarm.cc; 8s darwin-sandbox ... (16 actions, 15 running)
[6,275 / 7,762] Compiling quiche/quic/core/quic_packets.cc; 12s darwin-sandbox ... (16 actions, 15 running)
[6,319 / 7,762] Compiling quiche/quic/core/crypto/aes_128_gcm_encrypter.cc; 10s darwin-sandbox ... (16 actions, 15 running)
[6,383 / 7,762] Compiling quiche/quic/core/quic_received_packet_manager.cc; 9s darwin-sandbox ... (16 actions, 15 running)
[6,437 / 7,762] Compiling quiche/quic/core/quic_session.cc; 17s darwin-sandbox ... (16 actions, 15 running)
[6,500 / 7,762] Compiling source/extensions/filters/common/local_ratelimit/local_ratelimit_impl.cc; 18s darwin-sandbox ... (16 actions, 15 running)

which contains quiche code that should have been disabled by --//bazel:http3=False, as specified here
Docs don't match bazel behavior.

The --//bazel:http3=false does disable HTTP3 support in HCM, while not disable quiche build. quiche is being pulled by more targets like: https://github.com/envoyproxy/envoy/blob/main/source/common/common/BUILD#L164

Oh I see. In my mind I was thinking of quiche==http3 support, but that is not the case. Also in the future, it looks like the http1 codec will come from quiche, so it probalby won't be feasible to build Envoy without pulling in this dependency.

authors: ggreenway lizan


text:
LinkCreatesNamedFile test failure

This test is consistently failing in my environment: https://github.com/envoyproxy/envoy/blob/35bf11a0f14a996d4e95b5302b0a953e0beba9f6/test/extensions/common/async_files/async_file_handle_thread_pool_test.cc#L140
Here's my attempt to explain why:
The function manager_->createAnonymousFile() relies on the underlying filesystem supporting the O_TMPFILE flag: https://github.com/envoyproxy/envoy/blob/35bf11a0f14a996d4e95b5302b0a953e0beba9f6/source/extensions/common/async_files/async_file_manager_thread_pool.cc#L135
The fallback code (a few lines below) creates a file and deletes it, without closing it, returning its file descriptor. I'm reaching this fallback code, because my filesystem doesn't support the O_TMPFILE flag.
The problem happens when a hard link is created later with linkat(): https://github.com/envoyproxy/envoy/blob/35bf11a0f14a996d4e95b5302b0a953e0beba9f6/source/extensions/common/async_files/async_file_context_thread_pool.cc#L49
It fails with ENOENT, as stated in the manual page:
ENOENT An attempt was made to link to a /proc/self/fd/NN file
              corresponding to a file that has been deleted.

As seen here: https://man7.org/linux/man-pages/man2/link.2.html
cc @ravenblackx

What sort of environment is it that exhibits this failure? (Thinking maybe an NTFS filesystem on Linux?)
I would suggest this could be fixed by having the fallback behavior create a named temporary file (unfortunately), keeping track of that file in the AsyncFileContext object, moving it in lieu of linkat or deleting it during close. It should maybe be a distinct AsyncFileContext (though perhaps a subclass of AsyncFileContextThreadPool) since the more common case works without that information. That variant could also potentially make this able to function in Windows.
(Unfortunate because it could potentially make for inconsistent behavior with any code that looks at directory contents.)

The env is a docker container running in a k8s cluster probably running in an old kernel.

I have a plan to address this, involving migrating AsyncFileManager to using Envoy::Filesystem::File, after making File have an implementation for temp files and all the other required operations.
I'd assign this issue to me but I don't think I have permission to do that.

Still working on it, bot!

authors: jwendell ravenblackx


text:
clang-tidy error in post-submit: ambiguous argument 'HEAD^'

In post-submit we see a clang-tidy error from time to time:
fatal: ambiguous argument 'HEAD^': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Running clang-tidy-diff against HEAD^ (HEAD^), current HEAD (36644db0842e2ffe6cfae85ab13401b63095f51b)
fatal: ambiguous argument 'HEAD^': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Clang-tidy failed.

Log link: https://dev.azure.com/cncf/envoy/_build/results?buildId=135368&view=logs&j=b7634614-24f3-5416-e791-4f3affaaed6c&t=21e6aa7d-f369-5abd-5e4e-e888cac18e9c&l=536

cc @phlax

this is release ci and basically a dupe of #27018

authors: adisuissa phlax


text:
How to use the RDS service to update routing configuration in envoy's thrift proxy filter

I am using envoy thrift filter to proxy thrift rpc request, but when reviewd the envoy code , I do'nt known how to use RDS to update thrift route configuration, can you give me an example about it ?

RDS is used for updates to HTTP route configuration* so I don't think that's what you want.
I as thrift is a network filter you can update thrift routes with a full LDS update but I'm not sure if there's any finer grained update
@brian-pane @zuercher
*https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/rds.proto#envoy-api-msg-routeconfiguration

authors: alyssawilk zplinuxlover