Moya breaks project archive when linked via CocoaPods and new Swift Build System

We are using Moya 11.0.2 linked via CocoaPods 1.5.0:
  - Moya (11.0.2):
    - Moya/Core (= 11.0.2)
  - Moya/Core (11.0.2):
    - Alamofire (~> 4.1)
    - Result (~> 3.0)

which works normally. When I switch to new Swift-based build system in Xcode 9.3, Moya will break the build with the following errors:
⚠ unexpected duplicate creator 'MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' for node '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' with prior creator 'MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' (in target 'Moya-Core')
282
    ⚠ unexpected mutating task ('SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework') with no relation to prior mutator ('SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework') (in target 'Moya')
283
    ⚠ unexpected mutating task ('SetMode u+w,go-w,a+rX /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework') with no relation to prior mutator ('SetMode u+w,go-w,a+rX /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech\ Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework') (in target 'Moya')
284
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya' on task: CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64 (in target 'Moya-Core')
285
    ⚠ duplicate output file '' on task: CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64 (in target 'Moya-Core')
286
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/module.modulemap' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/module.modulemap /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/module.modulemap (in target 'Moya-Core')
287
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers/Moya-Swift.h' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers/Moya-Swift.h /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya-Swift.h (in target 'Moya-Core')
288
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftdoc' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/armv7/Moya.swiftdoc (in target 'Moya-Core')
289
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftmodule' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/armv7/Moya.swiftmodule (in target 'Moya-Core')
290
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftdoc' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya.swiftdoc (in target 'Moya-Core')
291
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftmodule' on task: Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya.swiftmodule (in target 'Moya-Core')
292
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' on task: MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
293
    ⚠ duplicate output file '' on task: MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
294
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers' on task: MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers (in target 'Moya-Core')
295
    ⚠ duplicate output file '' on task: MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers (in target 'Moya-Core')
296
    ⚠ duplicate output file '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Info.plist' on task: ProcessInfoPlistFile /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Info.plist Application/Pods/Target Support Files/Moya-Core/Info.plist (in target 'Moya-Core')
297
    ⚠ duplicate output file '' on task: SetMode u+w,go-w,a+rX /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
298
    ⚠ duplicate output file '' on task: SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
299
    ⚠ duplicate output file '' on task: SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
300
    ⚠ duplicate output file '' on task: Touch /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework (in target 'Moya-Core')
301
    » Build system information
302
    ✗ unable to build node: '<MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers')
303
    » Build system information
304
    ✗ unable to build node: '<MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework')
305
    » Build system information
306
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers/Moya-Swift.h' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers/Moya-Swift.h /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/Objects-normal/arm64/Moya-Swift.h' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers/Moya-Swift.h /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya-Swift.h')
307
    » Build system information
308
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftmodule' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/Objects-normal/arm64/Moya.swiftmodule' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya.swiftmodule')
309
    » Build system information
310
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftdoc' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/Objects-normal/arm64/Moya.swiftdoc' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm64.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/arm64/Moya.swiftdoc')
311
    » Build system information
312
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftmodule' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/Objects-normal/armv7/Moya.swiftmodule' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftmodule /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/armv7/Moya.swiftmodule')
313
    » Build system information
314
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftdoc' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/Objects-normal/armv7/Moya.swiftdoc' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/Moya.swiftmodule/arm.swiftdoc /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/Objects-normal/armv7/Moya.swiftdoc')
315
    » Build system information
316
    ✗ unable to build node: '<Linked Binary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64')
317
    » Build system information
318
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/module.modulemap' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya.build/module.modulemap /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/module.modulemap' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Ditto /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/Moya-Core.build/module.modulemap /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Modules/module.modulemap')
319
    » Build system information
320
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Info.plist' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:ProcessInfoPlistFile /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Info.plist Application/Pods/Target Support Files/Moya/Info.plist' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:ProcessInfoPlistFile /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Info.plist Application/Pods/Target Support Files/Moya-Core/Info.plist')
321
    » Build system information
322
    ✗ unable to build node: '<Touch /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:Touch /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:Touch /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework')
323
    » Build system information
324
    ✗ unable to build node: '<SetOwner /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:SetOwnerAndGroup buddybuild:staff /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework')
325
    » Build system information
326
    ✗ unable to build node: '<SetMode /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework>' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:SetMode u+w,go-w,a+rX /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:SetMode u+w,go-w,a+rX /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework')
327
    » Build system information
328
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:CreateUniversalBinary /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Moya normal armv7 arm64')
329
    » Build system information
330
    ✗ unable to build node: '/tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers' (node is produced by multiple commands; e.g., '2c80fcec02be452153af942a6f18e06a301b9f7101111c7f706e740ea4fb9e91:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers' and '2c80fcec02be452153af942a6f18e06a4973920b968b4ddf3815c5d66c773bd4:Release:MkDir /tmp/sandbox/5773e4b939c8890100ee3f63/bbbuild/Build/Intermediates.noindex/ArchiveIntermediates/Speech Blubs/IntermediateBuildFilesPath/UninstalledProducts/iphoneos/Moya.framework/Headers')
331
    ** ARCHIVE FAILED **

This could also be an issue with CocoaPods or Build System, but always stops with Moya, so maybe something to keep an eye on.

@Legoless thanks for the report. I guess we should file a radar as it clearly works with the old build system but it doesn't with the new one. Just one question: is it using a static or dynamic framework option in a Podfile?

Dynamic, sorry, forgot to add.

Hey, coming back to you with the results of my tests @Legoless. Unfortunately, I didn't have the same result as you. I ran the following:

Create a fresh project
pod init and add pod 'Moya', '11.0.2' to the Podfile
Open *.xcworkspace
Build with the default build system (success)
Switch to the new build system
Build with the new build system (also success)

(using Xcode 9.3 and CocoaPods 1.5.0)
There might be something else to get the mentioned result, I didn't find it though. Maybe try removing all the cache/derived data and try again?


update login register UI

update UI, still in progress

When text field empty if user click to login, mus have a error notification
Use regex for check password
If login failure, mustt have notification


[CARBONDATA-1814] Fix alter stream table property issue

Fix alter stream table property issue

[x] Any interfaces changed?
no

[x] Any backward compatibility impacted?
no

[x] Document update required?
no

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
yes, added
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@QiangCai The PR for this issue has been raised #1590

@geetikagupta16
ok, I will close this PR.
can you move test case to pr1590

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1575/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/1976/

Thanks @QiangCai
Sure will move the test case


Compilation errors in the build

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=134998&view=logs&j=bd1e231b-cef9-51a2-e461-b67194c0a817&t=9cc46b07-0f4a-51e5-598b-b142e2b8a72a
Seems to start happening after this commit - https://github.com/microsoft/vscode/commit/1324397c62f1fd7b0540d74bdee09bcc8eb6c5ac

@Tyriar Pushed a fix that might unblock the builds. Hope it does not break stuff. Please feel free to revert it and push correct fix


Automatically allow non_snake_case, non_camel_case_types, non_upper_case_globals

Bindings generated by bindgen are not expected to follow Rust naming conventions, so it's a reasonable default to automatically add #![allow(non_snake_case, non_camel_case_types, non_upper_case_globals)] to the generated module.

See also #373

Hi! If you have any questions regarding this issue, feel free to make a comment here, or ask it in the #servo channel in IRC.
If you intend to work on this issue, then add @highfive: assign me to your comment, and I'll assign this to you. :smile:

@highfive: assign me

Hey @framlog! Thanks for your interest in working on this issue. It's now assigned to you!

Have you made any progress, @framlog? Any questions?

Oh, I missed #580.

@jdm It should works imo.

I don't think we should do that given how invasive it is (see #580). Thanks @framlog, though, for coming up with a PR!


Update README.md

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[x] No

ℹ Additional Information

Summary by Sourcery
Documentation:

Correct the HTML structure in the README file.

Description by Korbit AI
What change is being made?
Correct the incorrect use of <tbody> tag by replacing it with </tbody> in the README.md file.
Why are these changes being made?
The original document incorrectly used the opening <tbody> tag instead of the closing </tbody> tag, causing potential rendering issues; this change aims to adhere to proper HTML syntax and improve document accuracy. It resolves any inadvertent coding errors for better readability and compliance with web standards.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Summary by CodeRabbit

Documentation

Streamlined the HTML structure of the README by removing empty <tbody> tags in the contributors and bots sections.

@gstraccini codacy bypass


Fix dynamics unittests involving finite difference function

This PR aims at solving issue https://github.com/Simple-Robotics/aligator/issues/127#issue-2131916127 about an error in the finite difference python function used in unittest. It also adds some missing unittest for MultibodyFreeFwdDynamics derivatives.

I'm working on this PR at the moment

Setting
x0 = space.rand()
x0[:3] = 0.

Did increase the residual. I think there's some kind of high-frequency component that 1st-order finite differences just can't capture.

We'll be switching to centered finite differences then. I'll also be scaling $\epsilon$ in the finite differences by the norms of x and u.

For further reference, here's what Crocoddyl does:

selects the finite difference parameter $\epsilon = \sqrt{2\epsilon^\text{mach}}$ where $\epsilon^\text{mach}$ is the scalar-type machine precision, which should be 2.22045e-16 for doubles according to the C standard (hence $\epsilon = 2.1\times 10^{-8}$)
tests for numerical tolerance $tol = \epsilon^{1/3}$ which is about 0.002762 for doubles (comments in the source code refer to this dead link, which I think is this file)

@jorisv would you agree with the state of this PR?
@edantec do you agree with my analysis of Crocoddyl's behaviour?

Looks good to me!

@ManifoldFR We can also look at the 5 points finite difference made in roboptim
It's maybe more precise and the code estimate the truncation error and the rounding error.

That must be very accurate, wow


Zoom (or high DPI) causes weird artifacts in the splitter

This might only affect dark mode.
100% zoom looks fine (80% zoom for me at 125% dpi):

90% at 125% dpi:

100% at 125% dpi:

110% at 125% dpi:

I suspect these might be browser issues with support for frames

Which browser is this? Which OS? have you tried other browsers or OSs?

Firefox 87.0 x64 on Windows 10 20H2.
Good thought. Chrome and Edge don't show anything at all:

Until you hold the mouse button and start moving, then Chrome and Edge look like this:

Yeah I've seen these types of issues before. Browsers just don't support this well. Unfortunately getting rid of frames would mean a full rewrite and I really don't have any time.


Move project tree to an application-driven logic

Purpose
We need to make applications easily pluggable to use Arnold as a generic way to deploy them. This means that we need to move the project tree to a structure easily overridable when using Arnold's docker image. Moreover, we need to be able to easily deploy a single application without having to comment or update group vars definitions.
Proposal

[x] move OpenShift object templates to the apps/ directory
[x] move ConfigMaps to the target application configmaps directory (e.g. apps/{{ app }}/configmap)
[ ] ~move secrets to the target application secrets directory (e.g. apps/{{ app }}/secret)~ edit: postponed to a future PR
[ ] ~move application-specific settings to a file (e.g. apps/{{ app }}/group_vars/main.yml)~ edit: postponed to a future PR
[x] create application objects by scanning ad hoc directories instead of hard-coding them in a configuration (i.e. apps/{{ app }}/dc/*.yml.j2 for DCs) *
[ ] ~get rid of the _common templates?~
[ ] ~update the documentation~ edit: postponed to a future PR

* we need to find a way to easily modify this mechanism for a particular environment, e.g. ignore endpoints in development.
This work is related to the following issues: #40, #44

This PR is already too big for a comfortable review. Sorry for that. I've postponed some tasks to other PRs. My first intent was to make apps "discoverable" in this work; this is now done at 80% (application secrets and vars are not implemented yet).


Unhandled Promise Rejection

Sentry Issue: KAP-9NW

macOS version:    Big Sur (11)
Kap version:      3.5.1
Unhandled Promise Rejection

TypeError: Object has been destroyed
    at updateUi (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/windows/dialog.js:46:30)
    at Object.action (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/utils/errors.js:144:21)
    at async /Applications/Kap.app/Contents/Resources/app.asar/dist-js/windows/dialog.js:59:17
    at async IpcMainImpl.listener (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/electron-better-ipc/source/main.js:90:22)

Hi, same error
Unhandled Promise Rejection TypeError: Object has been destroyed     at updateUi (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/windows/dialog.js:46:30)     at Object.action (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/utils/errors.js:138:21)     at async /Applications/Kap.app/Contents/Resources/app.asar/dist-js/windows/dialog.js:59:17     at async IpcMainImpl.listener (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/electron-better-ipc/source/main.js:90:22)

+1 I get the same. Can't make any recordings without a full reboot of my computer. Killing Kap & restarting doesn't seem to fix it.


🎉 3.0.6

ℹ About this release

Version: 3.0.6
Type: patch
Last Release: 3.0.5 (12/13/2023, 9:09:17 PM) [?]
Commits to merge: 11 [?]

📦 Dependencies

Update @prisma/client from ^5.7.0 to ^5.7.1
Update prisma from ^5.7.0 to ^5.7.1

📦 Development Dependencies

Update @qiwi/semantic-release-gh-pages-plugin from ^5.2.10 to ^5.2.11
Update @semantic-release/npm from ^11.0.1 to ^11.0.2
Update @types/node from ^20.10.2 to ^20.10.5
Update eslint from ^8.55.0 to ^8.56.0
Update eslint-plugin-jsonc from ^2.10.0 to ^2.11.2
Update ts-node from ^10.8.2 to ^10.9.2
Update typescript from ^5.3.2 to ^5.3.3

:tada: This PR is included in version 3.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
Docker container (sebbo2002/fhem-log2db:3.0.6)
v3.0.6

Your semantic-release bot :package::rocket:


Build libs for kfp v1 and v2 in the release.

Why are these changes needed?
Add building and publishing the two kfp images of kfp v1 and v2 when creating a new release.
Related issue number (if any).

Holding off merge until we closed on questions I've raised elswhere on this PR.

see my answer.

@Mohammad-nassar10 - @roytman and I spoke and agreed that

the publishing of both versions kfp versions should be handled inside kfp/Makefile
We will remove/disable the actual make build publish in the release script and handle that either manually in the new branch or with a git action somehow.

As a result I think this PR can be closed.  Another one #338 is started to address those (and your fixes made here)


Migrate from VMware implementation

Hooks to migrate from the VMware implementation are available opt-in by
passing the --migrate-from-vmware flag to the manager container. Running
with the migration hooks installed will incur a performance penalty and
should only be used while a migration is active, and then disabled.
Depends on #327

Codecov Report
Patch coverage: 55.67% and project coverage change: -3.08% :warning:

Comparison is base (d185b32) 81.53% compared to head (a1072f4) 78.46%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #336      +/-   ##
==========================================
- Coverage   81.53%   78.46%   -3.08%
==========================================
  Files          15       17       +2
  Lines        1446     1625     +179
==========================================
+ Hits         1179     1275      +96
- Misses        219      279      +60
- Partials       48       71      +23

Files Changed
Coverage Δ

dies/v1beta1/servicebinding.go
0.00% <0.00%> (ø)

controllers/webhook_controller.go
82.75% <11.11%> (-4.84%)
:arrow_down:

lifecycle/hooks.go
40.00% <40.00%> (ø)

controllers/servicebinding_controller.go
84.61% <40.74%> (-7.52%)
:arrow_down:

lifecycle/vmware/migration.go
66.41% <66.41%> (ø)

controllers/client.go
100.00% <100.00%> (ø)

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


Skip tests requiring CPU manager if feature gate is disabled

What this PR does / why we need it:
In environments where CPU manager feature gate is disabled, tests requiring it will fail.
Release note:
-->
NONE

/cc @vladikr @enp0s3

/cherry-pick release-0.26

/lgtm
/approve

/retest


all borgs can now use nukie borg modules

About the PR
made nanotrasen borgs able to have nukie modules put in them (l6c row, desword, emag)
Why / Balance
Fun!

To be honest, i like that idea.

Disabler SMG makes borgs super easy to kill

law 1 says what?

Law ^$>@&$_÷@* says "ALL CREW WHOSE CLOTHES ARE NOT ON FIRE ARE NOT CREW"
Although giving a borg who basically has free will a gun is definitely a choice I wouldn't make in a hurry.

no


Bump Onyx to v2.0.68

Details
This PR bumps Onyx to v2.0.68.
Fixed Issues

$ https://github.com/Expensify/App/issues/49147
$ https://github.com/Expensify/App/issues/48777
PROPOSAL:
Tests

[x] Verify that no errors appear in the JS console

Login to account with workspace feeds beta enabled.
Go to workspace settings.
Create a new workspace if not already created.

Enable Expensify Card.
Make sure the app doesn't crash.
Disable Expensify Card.
Make sure the app doesn't crash.

Offline tests

Same as above.
QA Steps

[x] Verify that no errors appear in the JS console

Same as above.
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/839a7340-3b98-4398-bf44-be5debcb12c5

Android: mWeb Chrome
https://github.com/user-attachments/assets/86417984-9e2d-4cc1-9d93-af91bcc93cc6

iOS: Native
https://github.com/user-attachments/assets/8bd1a891-eb6d-41c1-a86b-d1e5231a4aba

iOS: mWeb Safari
https://github.com/user-attachments/assets/1d412ab3-86fd-42b9-b381-b2b650fcc7c5

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/4412e2f6-e605-4034-916c-f64002f0b267
https://github.com/user-attachments/assets/e1629b83-c367-4a3e-be5a-5eb04c3d19a2

MacOS: Desktop
https://github.com/user-attachments/assets/be982233-515b-4e61-8d32-9881c4561f40

Reviewer Checklist

[X] I have verified the author checklist is complete (all boxes are checked off).
[X] I verified the correct issue is linked in the ### Fixed Issues section above
[X] I verified testing steps are clear and they cover the changes made in this PR

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[X] I checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[X] I verified tests pass on all platforms & I tested again on:

[X] Android: Native
[X] Android: mWeb Chrome
[X] iOS: Native
[X] iOS: mWeb Safari
[X] MacOS: Chrome / Safari
[X] MacOS: Desktop

[X] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[X] I verified proper code patterns were followed (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I verified that this PR follows the guidelines as stated in the Review Guidelines
[X] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[X] I verified that all the inputs inside a form are aligned with each other.
[X] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/e57a2e94-91c6-4288-b272-95fb9d59d60d

Android: mWeb Chrome

https://github.com/user-attachments/assets/f10a5858-e95e-4859-95e4-8f54e1a281d1

iOS: Native

https://github.com/user-attachments/assets/88cc2151-f39d-4a32-a95a-1d5b5575e485

iOS: mWeb Safari

https://github.com/user-attachments/assets/b19178c8-db8b-41c1-927a-48de67b1e16f

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/25d35272-2c77-4852-9113-e55b7b0ca84e

MacOS: Desktop

https://github.com/user-attachments/assets/b35dab42-349e-4bbd-b934-79befd84e285

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/mountiny in version: 9.0.36-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/grgia in version: 9.0.36-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[PR][CLOSED] Added jenkins script to check build status of OBS server

 Issue by geunsik-lim
Wednesday Jun 27, 2018 at 11:02 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/65

This PR is to append a script to check if OBS server generates
packages normally.
Changes proposed in this PR:

Added facility to check build error of OBS server
Updated the existing scripts to support email notification

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/65/commits

:octocat: cibot: Thank you for posting issue #89. The person in charge will reply soon.

 Comment by git-bot-sec
Wednesday Jun 27, 2018 at 11:02 GMT

:dart: cibot: @STAR has updated the pull request.


please document 'score' better

What is 'score' when I use explain_prediction_xgboost()?
I see y (score: ####) what is this number?
(I have spent about an hour reading the doc to find this ... and I can't sorry.)
Thanks!!

We think this is related to using regularization in XGBoost. It happens for regression and classification in our tests. You can see them here: https://github.com/h2oai/mli-resources/blob/master/lime_shap_treeint_compare/DRAFT-Binary-Classification-Random-One-Function.ipynb
(This test case should run for you without too much effort. Just clone the repo and install dependencies.)


fix readthedocs compilation

Similarly as in:
https://github.com/SeisSol/SeisSol/pull/853

@dmay23 can you review this PR please?

Looks good to me, this update is due to release of urllib3 2.0 on May 4th

This is  what Carsten wrote:

Read the docs was broken for SeisSol, too, due to the release of urllib3 v2. You can add “urllib3<2” to docs/requirements.txt, then read the docs should build again. See https://github.com/SeisSol/SeisSol/pull/853

@Thomas-Ulrich If there are any immediate additional Spack related changes you need to make, please re-open this PR, or PR #44 and make the changes there.


[WIP] Support publishing Windows 2022 image

Description
Dapr Windows image use Windows 1809 today, which has reached end of servicing. This PR adds a new Dapr Windows image which uses the Windows ltsc2022 base image. It is also added to the existing manifest. Note, the new Windows version also contains netapi32.dll and certoc.exe as required by Go and the entrypoint script to setup certificates.
The image will be in the following format now:
daprio/daprd:1.10.2-windows-ltsc2022-amd64

The existing 1809 image will be shipped as:
daprio/daprd:1.10.2-windows-1809-amd64

A new manifest will point to both 1809 and ltsc2022 images
daprio/daprd:1.10.2-windows-amd64

We should also follow a deprecation path for 1809 images, but it should be tracked separately.
Issue reference
Please reference the issue this PR will close: #5644
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Sample run for dapr-base-containers workflow - https://github.com/shubham1172/dapr/actions/runs/4292684625/jobs/7479428205

Verified root cert installation on Windows 2022 image using https://github.com/shubham1172/dapr-cert-tests
Nodepool: AKSWindows-2022-containerd-20348.1547.230223
Daprd image: ghcr.io/shubham1172/daprd:edge
# Without using the certs
k logs pythonapp-7dd5c58b7b-rmjtz                ⎈ dapr-aks
Defaulted container "python" out of: python, daprd
Traceback (most recent call last):
  File "main.py", line 12, in <module>
    resp = client.invoke_binding(BINDING_NAME, BINDING_OPERATION, '')
  File "C:\Python\Lib\site-packages\dapr\clients\grpc\client.py", line 308, in invoke_binding
    response, call = self._stub.InvokeBinding.with_call(req, metadata=metadata)
  File "C:\Python\Lib\site-packages\grpc\_channel.py", line 957, in with_call
    return _end_unary_response_blocking(state, call, True, None)
  File "C:\Python\Lib\site-packages\grpc\_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.INTERNAL
	details = "error invoking output binding helloworld: Get "https://<IP_ADDRESS>": x509: certificate signed by unknown authority"
	debug_error_string = "{"created":"@1677823434.587000000","description":"Error received from peer ipv4:<IP_ADDRESS>:50001","file":"src/core/lib/surface/call.cc","file_line":953,"grpc_message":"error invoking output binding helloworld: Get "https://<IP_ADDRESS>": x509: certificate signed by unknown authority","grpc_status":13}"
>

# When using the correct certs
k logs pythonapp-f4c7cf459-xr8fj                 ⎈ dapr-aks

Defaulted container "python" out of: python, daprd
INFO:root:Response: b'Hello, World! (Using HTTPS)'
INFO:root:Response: b'Hello, World! (Using HTTPS)'
INFO:root:Response: b'Hello, World! (Using HTTPS)'
INFO:root:Response: b'Hello, World! (Using HTTPS)'

Latest runs in my fork:

https://github.com/shubham1172/dapr/actions/runs/4340004114 - dapr-base-containers
https://github.com/shubham1172/dapr/actions/runs/4342570204 - dapr

@DeepanshuA @ItalyPaleAle please re-review, the comments have been addressed and I have updated the description.

OK. I also checked that the edge tag now will have 2 Windows images under it - which is what I was expecting. LGTM

@dapr/maintainers-dapr can you please trigger https://github.com/dapr/dapr/actions/workflows/dapr-base-containers.yaml to push the new base image?

Done

When/how will we be able to use the 2022 dapr base image?

When/how will we be able to use the 2022 dapr base image?

You can also try the edge builds till the next release.
docker pull daprio/daprd:edge-windows-ltsc2022-amd64


Where is the original source code?

@DavidKinder What happened to the original inform7 source code?
According to this talk:
http://inform7.com/talks/2019/06/14/narrascope.html
The original source code should be here, but the link is dead:
https://github.com/ganelson/inform
Does this repo contain all the source?  Is ganelson still around?  Is Inform7 still maintained?
Thank you!
PS.  I'm interested in using Inform7 as an engine to power a discord bot.

Graham has not yet completed the overhaul of the Inform 7 codebase described in that talk (and the Narrascope 2020 talk). It is my understanding that those repositories will be made public when he considers it ready for a public release. Until then they remain private. Inform 7 is still maintained.

@DavidKinder ahh OK.  So it's my understanding then, that this repo is a GUI editor for making Inform7 stories, and then you just pass the story to the Inform7 compiled binaries for processing into a final executable?  But you don't have access to the actual source code?

The intention of the Inform 7 project was always that the front-ends (this project is the Windows front-end) and the underlying compiler formed a whole, but yes, this project is the source for the Windows GUI front-end. The source for the actual Inform 7 compiler has never been made public, as yet.


Fixing Windows update logic.

Removing the call to Shutdown from within Signal in order to rely on waitExit handling the exit of the process.
This replaces old PR https://github.com/docker/docker/pull/22645
Signed-off-by: Stefan J. Wernli<EMAIL_ADDRESS>

@LK4D4 This one should work properly.  Turns out we don't even need the WaitGroup!

@jhowardmsft @jstarks @brian-young All checks passed. Barring any feedback, I think this is ready to merge.

LGTM. Bonus points for docker restart working with this fix :)

:+1: This fixes the races I was experiencing in my local changes.

Anyone else want to weigh in on this review?

@tiborvass @icecrime @calavera Any chance of reviewing this? This fixes a deadlock in the daemon on Windows when under load which isn't called out explicitly in the description above.

[cricket sound]

LGTM

Sweet, thanks @tiborvass!


Many changes, look at comments :)

Organized the assets folders
Fixed links for images after organizing
Added alt to all images
Worked on the Sign Up modal responsiveness
For some reason Profile kept lighting up red for me, so I looked and found that rounded was called twice in the classes
I fixed that (The red page was driving me crazy lol)

I finally was able to get the Avatars to show up :)


push version to v1.0.3

Changes Unknown when pulling 6b9e12ee95f3d09a466a56dff7d0ad8f910fbf3d on giulio/push-to-v1-0-3 into ** on master**.


S3 backend support?

I could be missing something but it appears from the examples that there is no S3 backend support. Is that the case?
I feel it's a common use case and would be a great addition here.
There is really not any competition in this area besides driftctl and it's a fantastic area to improve on Terraform.

can you provide an example of what the config.yaml file should look like then?
If my config.yaml looked like this what would I need to change?
stacks:
  - name: NAME_HERE
    path: ./
    backend: tfstate+s3://BUCKET_NAME/BUCKET_KEY/terraform.tfstate

Then I imagine my command would look like this right? Assuming my current working directory is where my terraform files are located.
./terradrift-cli --config ./config.yaml

The backend option in the config.yaml is only needed if you have a custom backend config to pass ref, otherwise terradrift should use your current configuration in the tf codebase. Required fields are Name and Path only


New version of hoe causes gem install to fail

I get the following error:
Hoe.new {...} deprecated. Switch to Hoe.spec.
(in /opt/local/lib/ruby/gems/1.8/gems/jashmenn-apriori-0.2.2)
rake aborted!
undefined method `rdoc_pattern=' for #Hoe:0x101881d08
I cloned and modified the spec to require hoe 1.7.0 and it installed fine. Just wanted to let you know.

I have the following error :
Using apriori (0.2.3) from git://github.com/jashmenn/apriori.git (at master) with native extensions
Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.
    "/home/florian/.rvm/rubies/ruby-1.9.3-p0/bin/ruby" -rubygems /home/florian/.rvm/gems/ruby-1.9.3-p0/gems/rake-0.

9.2.2/bin/rake RUBYARCHDIR=/home/florian/.rvm/gems/ruby-1.9.3-p0/bundler/gems/apriori-071f0daca909/lib RUBYLIBDIR=/home
/florian/.rvm/gems/ruby-1.9.3-p0/bundler/gems/apriori-071f0daca909/lib
rake aborted!
cannot load such file -- config/requirements
(See full trace by running task with --trace)
Gem files will remain installed in /home/florian/.rvm/gems/ruby-1.9.3-p0/bundler/gems/apriori-071f0daca909 for inspecti
on.
Results logged to /home/florian/.rvm/gems/ruby-1.9.3-p0/bundler/gems/apriori-071f0daca909/./gem_make.out
An error occured while installing apriori (0.2.3), and Bundler cannot continue.
Make sure that gem install apriori -v '0.2.3' succeeds before bundling.


Can not use 'my-api-key' on google.cloud.translate API. translate may support OAuth2 now?

I'm trying to use translate API with API-Key.
But I got error when I follow instruction on instruction of following:
Translate Doc mentioned how to use it:

https://googlecloudplatform.github.io/google-cloud-python/stable/translate-usage.html

Error:

client = translate.Client('my API Key is given')
...
DefaultCredentialsError: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS or
explicitly create credential and re-run the application. For more
information, please see
https://developers.google.com/accounts/docs/application-default-credentials.

I just guess , now only OAuth2 is supported by translate API. Because of some information. Should the Doc updates or am I wrong ?
Env:

google-cloud-translate  (0.22.0)
Python 2.7.6 on Ubuntu 14.04
pip 9.0.1

Some information:
On Translate Client Document,

https://googlecloudplatform.github.io/google-cloud-python/stable/translate-client.html

And help(translate.Client)

Help on class Client in module google.cloud.translate.client:
class Client(google.cloud.client.Client)
|  Client to bundle configuration needed for API requests.
|
...
|  :type credentials: :class:oauth2client.client.OAuth2Credentials
|  :param credentials: (Optional) The OAuth2 Credentials to use for the
|                      connection owned by this client. If not passed (and
|                      if no http object is passed), falls back to the
|                      default inferred from the environment.
...
|  Methods defined here:
|
|  init(self, target_language='en', credentials=None, http=None)

@hidehara I'm sorry you ran into trouble with this!
I'll get a PR to update the docs going right now.
Support for the API key was removed via https://github.com/GoogleCloudPlatform/google-cloud-python/pull/2823 and released in 0.22.0.
The prefered way to authenticate is with service accounts. Which we do have docs explaining how to set that up here: https://googlecloudplatform.github.io/google-cloud-python/stable/google-cloud-auth.html.

@daspecster Thanks for nice reply.
I have a question , why API-Key was removed ?
Is that based on Google Cloud Translate life cycle OR just new policy of google-cloud-python ?
If you have any information, please let's me know.
I read #2823 , so I understand that I should use OAuth2 from 0.22.0.

Anytime!
@hidehara, I believe that it was always intended that Translate use Service Accounts.
Only recently was Service Account support added to the upstream Translate service.
@jonparrott or @dhermes would know more about it I'm sure.

@daspecster , Oh, sorry about type of Account.
I succeed to use translate with 'Service Accounts' by using following sytle.

export GOOGLE_APPLICATION_CREDENTIALS="/path/to/keyfile.json"

I confused to use which type of Account , cause of  help(translate.Client). But now I'm OK to use Service Account.
If Google will still support API-Key , It's easy & best way for me (;
Thanks for kind information.

@hidehara We elected to drop support for API key auth as a "library decision" but the backend still supports it. The auth doc linked to by @daspecster should have everything needed to authenticate. It's incorrect to say you must use a service account, you can also use OAuth 2.0 based credentials for user accounts. For deployed applications however, we strongly recommend the use of a service account.
The release listed the dropped feature, though maybe this wasn't clear enough?

@dhermes Thanks for above. I'm clear now.
I got background of "library decision" and the backend still supports API Key auth.
I succeed to use a service account, so I may implement with it.


[Bug] HTTP 405 when syncing trash folder on WebDav

          I'm not using encryption.

Followed your suggestion:

Delete the folder and re-synced.
The first sync return an error on 1 file, did not understand why. Retried it a few times and the same resulted the same error
Activated the sync of the config folder, and the sync "magically" worked.
confirmed also on my iphone.
When activating "./trash" sync, returns a different error (but I think is unrelated with this topic):

remotely-secure-1702415299722: abort sync, triggerSource=manual, error while syncing

trash/: Request failed, status 405

Originally posted by @xppx99 in https://github.com/sboesen/remotely-sync/issues/57#issuecomment-1852815893

I had similar bugs and hope for further solution.

For now the workaround is to disable .trash folder sync in settings.
@sqq135 can you let me know what webdav provider you are using or software if hosted locally? Thank you!

The same parameter could work in my computer but couldn't work in android, it's really confuse. I cleaned the .trash, but it still couldn't work. Finally, I completely cleaned the app of Android and try again, it work. I don't know the main reason, but I think the bug may happen after too much alteration of the documents.
And I am using the https://teracloud.jp/en/


Parsing Issue

When parsing our logs we are not getting any query values.  I have attached a sample postgres log.
The postgresql.conf file contains the following
log_line_prefix = '%t  [%p]: [%1-1]  User:%u '
i am running the program with the following command line
pgbadger -p '%t %h [%p]: [%l-1] user=%u ' sample1.log
an abbreviated example of our logs are attached.
sample1.log

Well the problem is double: your log_line_prefix is wrong and the prefix given to pgbadger is also wrong.
Please set at minimal your log_line_prefix as follow:
log_line_prefix = '%t [%p]: User:%u '

but best would be to use the default pgBadger log_line_prefix. I don't want to force you, you may have your reasons to use this one but if you are not comfortable with pgbadger please use the default prefix with all information this will save us lot of time:
log_line_prefix = '%t [%p]: user=%u,db=%d,client=%h,app=%a '

Then use pgbadger without specifying any prefix.


Bad alignment in profile table

The profile lines are not neatly tabulated, all lines are centered on the screen. This makes it very hard to read the numbers properly.

@physicalattraction I know we need a release but have you tried the latest from master? I think this was addressed via a CSS tweak.

@avelis: Thanks for your reply. I didn't try it from the latest master, I didn't know there were differences between them. Good to hear that is has been solved already, this issue can be closed then.


Rails/TimeZone is corrected to Time.zone.new which raises NoMethodError

Expected behavior
Time.new to Time.zone.local or something.
Actual behavior

C: [Corrected] Rails/TimeZone: Do not use Time.new without zone. Use one of Time.zone.local, Time.current, Time.new.in_time_zone, Time.new.utc, Time.new.getlocal, Time.new.xmlschema, Time.new.iso8601, Time.new.jisx0301, Time.new.rfc3339, Time.new.httpdate, Time.new.to_i, Time.new.to_f instead.

Time.new(2019)

is auto corrected to
Time.zone.new(2019)

Steps to reproduce the problem
Auto correct in minimal environment:
% cat .rubocop.yml
require:
- rubocop-rails
% cat now.rb
Time.new(2019)
% rubocop -a now.rb
Inspecting 1 file
C

Offenses:

now.rb:1:1: C: [Corrected] Style/FrozenStringLiteralComment: Missing magic comment # frozen_string_literal: true.
Time.new(2019)
^
now.rb:1:6: C: [Corrected] Rails/TimeZone: Do not use Time.new without zone. Use one of Time.zone.local, Time.current, Time.new.in_time_zone, Time.new.utc, Time.new.getlocal, Time.new.xmlschema, Time.new.iso8601, Time.new.jisx0301, Time.new.rfc3339, Time.new.httpdate, Time.new.to_i, Time.new.to_f instead.
Time.new(2019)
     ^^^

1 file inspected, 2 offenses detected, 2 offenses corrected
% cat now.rb
# frozen_string_literal: true

Time.zone.new(2019)

In rails console:
Loading development environment (Rails 5.2.3)
irb(main):001:0> Time.new(2019)
=> 2019-01-01 00:00:00 +0900
irb(main):002:0> Time.zone.new(2019)
Traceback (most recent call last):
        1: from (irb):2
NoMethodError (undefined method `new' for #<ActiveSupport::TimeZone:0x00007fe02454b2d8>)
Did you mean?  now

RuboCop version
0.72.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.3 x86_64-darwin18)

and rubocop-rails (2.1.0)

Duplicate with #67 and #81. Thanks for your feedback.

I can reproduce with rubocop-rails 2.2.0 too.
I think https://github.com/rubocop-hq/rubocop-rails/issues/86 is same issue.

RuboCop Rails 2.2.1 has been released with a fix for this issue.
https://rubygems.org/gems/rubocop-rails/versions/2.2.1


Feature request: Generate Sprite2D

Hi, thank you very much for this plugin, it's super easy and intuitive to use, honestly very fun!
I think I would love to use it in future for prototyping as well as it seems so quick and easy to draw simple characters, items, environment things as placeholders. I could even imagine creating a whole game with this, but then the engine would do a lot of _draw() processing all the time.
So I was thinking if it would be possible to add functionality to save the drawing as png and generate a texture which then gets the png assigned.
Thanks again!

Hi @golddotasksquestions, thanks again for the compliments and for the feature request.
I'm not sure this is still relevant since #6 removes almost all _draw related calls in the plugin and replaces them with Line2D nodes which are significantly faster.
If you have any other reason for this feature other than performance, or still feel the performance will be significantly improved by this feature, please say so!
Otherwise i will close this in a couple of days.

Yes I have plenty of reason for this feature other than performance.
My biggest reason is how fun it is to use AnnotateCanvas node. It's so straight forward and intuitive to use, it would be awesome to use for so much more than just annotations. I honestly can very well imagine to create all the visuals for various games with just this node. Especially for jam games, this node would be super fun to use.
While I guess to some degree it would be possible to just use the node as it so create game visuals, a texture would have the benefits of being very robust established resource and able to be used at various other places in the engine. I could use it as texture for AnimatedSprites, for TextureButtons, for TextureRects, as texture for 3D Materials, as texture in shaders ... the list goes on.
Also if you adding a CanvasItem shader to a Line2D has a totally different result compared to a texture. Currently it does not seem to be possible to add a shader to the AnnotationCanvas node, even though it is a 2D node. Well it is possible, the shader just won't have any effect.


Firelocks should respond to fires

Description

One thing I've noticed now that I've mapped in firelocks on packed (and will probably map in more) is that they'd totally stop most single-canister plasma floods if they actually responded when there's a fire. In the above screenshot, someone lit a plasma fire that ordinarily would've been stopped by the firelocks immediately above it.

 Not directly from fire locks to fire.


Feature: Forms

I started implementing forms into console_engine, the objective is to allow the developer to easily create self-managed TUI forms.
They'll be enclosed in their own "form" feature. The "event" feature will also be needed in order for them to handle user input properly.
🆕 Features

Forms that can handle multiple fields simultaneously
Fields:

Text
HiddenText
Checkbox
Radio

Basic Field Validation:

NotBlank
Integer
Number
Alphabetic
Alphanumeric
Callback
CharactersCallback

This Pull Request is mostly finished, if anybody wants to review it, you're welcome !

I'd like to allow the possibility of multiple fields handling a single event

This sounds like something that could potentially be a hard-to-find problem in the future (either in development of the crate or when using the crate). And I don't really see the use case for that. The possibility could maybe implemented in an explicit way, e.g. some UI element that sends events to all of it's children.

we not only give the event to the form (so he may or may not use it) but after that we also use it afterward to handle for example form cancelling

Maybe better way to describe that was that first the program checks if it wants to do something with the event (quit, cancel, etc.) and if it decides that it doesn't then pass it forward. I think this makes more sense.
Then it could be implemented like this:
match event {
    Event::Key(KeyEvent { KeyCode::Escape, modifiers }) => {
        break;
    },
    event => form.handle_event(&event),
}

I'm just worried that this handling of events in multiple places could cause some unexpected behavior.

Right, I see your point. I'll work on that part then, that shouldn't take too much time to implement thankfully.

One more thing: I wonder if it wouldn't be better if get_result would return a Result type that would have the validation error as Err. So instead of checking first if there are any errors and the proceeding with getting the form data, this would happen at once.
Here's how I imagine it more or less.
This is more inline with Rust design (Result type was made for that). I used a separate function for getting the data from form so you can use ? operator.

One more thing: I wonder if it wouldn't be better if get_result would return a Result type that would have the validation error as Err. So instead of checking first if there are any errors and the proceeding with getting the form data, this would happen at once. Here's how I imagine it more or less. This is more inline with Rust design (Result type was made for that). I used a separate function for getting the data from form so you can use ? operator.

That's genius! I didn't think of that as those two functions were made several days apart. I'll apply this once I'm back to it. Thanks for the suggestion !

I addressed most of your comments,
I'm wondering something about validation constraints, precisely unhandled FormValue (like Nothing, Boolean, Index most of the time), should the behavior of constraints pass them through (return true even if they doesn't match the validation, to not block HashMap validation for example), or should they block (return false) ?
Starting this PR I was for the passing through, but by working on it right now I'm thinking about switching to a blocking behavior.
Any thoughts about this ?

I addressed most of your comments,
I'm wondering something about validation constraints, precisely unhandled FormValue (like Nothing, Boolean, Index most of the time), should the behavior of constraints pass them through (return true even if they doesn't match the validation, to not block HashMap validation for example), or should they block (return false) ?
Starting this PR I was for the passing through, but by working on it right now I'm thinking about switching to a blocking behavior.
Any thoughts about this ?

I think it makes sense for them to be blocking, since the user decides what constraint are applied where. And being more picky could potentially prevent some unexpected behavior (e.g. applying number constraint to a toggling button doesn't make sense so it's better if it invalidates the form).
Now I'm wondering if maybe it should be an error (rather than just not validating)? It fits Rust to be picky about types.

I addressed most of your comments,
I'm wondering something about validation constraints, precisely unhandled FormValue (like Nothing, Boolean, Index most of the time), should the behavior of constraints pass them through (return true even if they doesn't match the validation, to not block HashMap validation for example), or should they block (return false) ?
Starting this PR I was for the passing through, but by working on it right now I'm thinking about switching to a blocking behavior.
Any thoughts about this ?

I think it makes sense for them to be blocking, since the user decides what constraint are applied where. And being more picky could potentially prevent some unexpected behavior (e.g. applying number constraint to a toggling button doesn't make sense so it's better if it invalidates the form). Now I'm wondering if maybe it should be an error (rather than just not validating)? It fits Rust to be picky about types.

I'd love to see compile time errors due to missuse of constraints but that implies that we know what kind of output a given field can return, and also what kind of output a given constraint is able to validate. But I have no idea if that's possible.
I'm not sure about runtime validation, should they return a Result or an Option (if not just a bool) ? I'm leaning toward Options but I'd like your opinion on this

Yeah, compile time errors are probably not feasible. But returning an Option or a Result doesn't seem like a good solution either, since then you have to decide whether you block on None/Err or pass. Or you could leave it up to the user.
I was also thinking that maybe it could panic, but it feels kinda off too.

Maybe with a 'support' function that returns bool if the given FormValue is supported ?

How would this work?

Something around
    fn supports(&self, output: &FormValue) -> bool {
        matches!(
            output,
            FormValue::Boolean(_) | FormValue::Index(_) | FormValue::List(_)
        )
    }

I'm not sure about this idea, it feels like bypassing something alike Options
I might simply return false for now (blocking), and figure out a better way later

Leaving it for later, when you have more experience with actually using it (and maybe feedback from users of the crate), is probably the right move right now.

I think that's it,
By the way, I added a IsTrue constraint. I'll add some more later as I encounter some use-cases but I think I'll stop for this release. If you got any idea for more constraints I'll take them as well

I don't have any ideas for constraints for now

Okay, then I think we're done, unless you got anything else to do before merging ?

Nope, looks good to me!

So I'm merging this, thanks a million for your patience and all your reviews, the update looks amazing compared to my first attempts thanks to you.
By any chance, would you be interested in being a maintainer on this repository ?

Glad I could be of help!
I'm not familiar with or interested in TUI development so I don't think I'd contribute much, but feel free to mention me if you have any questions or want a code review and I'll try to help when I have the time.

If you ever need help / review / opinion, feel free to tag me too, I would gladly try to help as well !


[Bug Fix] cookie consent is popping up too often and is not persisted

Addresses: https://github.com/restarone/violet_rails/issues/1235
DEMO
https://user-images.githubusercontent.com/25191509/204212777-ab22c487-d0aa-458c-981d-6f951df7cb2a.mov

acceptance criteria:

on iOS Safari, cookie consent status should be persisted between browser sessions (eg: closing and reopening the browser) ⌛
tracking should ready as soon as cookie consent is given & tracking should happen if applicable ⌛


chore : removed featured tag from quick starts and added most popular…

Added "most popular" as a new key word. the tiles containing this key word will display as carousel in instant-observability page
… keyword
Summary
A concise description of the changes being introduced. If you are submitting a PR for a
new quickstart please review the pre merge checklist section to validate this PR is ready for review.

Pre merge checklist

[ ] Did you check you NRQL syntax? - Does it work?
[ ] Did you check your dashboard image quality? -  Do they look good?
[ ] Did you check that your alerts actually work?
[ ] Did you include an InstallPlan and Documentation reference?
[ ] Did you check your descriptive content for voice, tone, spelling and grammar errors?
[ ] Did you attach images of your dashboards to the PR so we can see them working?

Screenshots
Attach images of any visual changes, such as a dashboard here.

This PR is currently blocked from merging because of this issue:
https://github.com/newrelic/newrelic-quickstarts/issues/881


IllegalArgumentException causing offset commit failure & streaming of many duplicates

Hey!
We're using this connector to try and stream a dataset of around 3.2m rows to BigQuery (at around 6.5k messages/second). It works great at first but at some point in the dataset we're seeing it fail - when it does so, it just continues to arbitrarily stream data (looks like offsets are not commited but connector is not paused so it just continues to stream the same data?)
We see both these error messages in the log:

[2019-02-14 07:48:38,140] ERROR WorkerSinkTask{id=connector-name-0} Offset commit failed, rewinding to last committed offsets (org.apache.kafka.connect.runtime.WorkerSinkTask:386)
com.wepay.kafka.connect.bigquery.exception.BigQueryConnectException: Some write threads encountered unrecoverable errors: java.lang.IllegalArgumentException; See logs for more detail
at com.wepay.kafka.connect.bigquery.write.batch.KCBQThreadPoolExecutor.awaitCurrentTasks(KCBQThreadPoolExecutor.java:95)
at com.wepay.kafka.connect.bigquery.BigQuerySinkTask.flush(BigQuerySinkTask.java:97)
at org.apache.kafka.connect.sink.SinkTask.preCommit(SinkTask.java:125)
at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:380)
at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:210)
at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:194)
at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[2019-02-14 07:48:38,140] ERROR WorkerSinkTask{id=connector-name-0} Commit of offsets threw an unexpected exception for sequence number 3: null (org.apache.kafka.connect.runtime.WorkerSinkTask:261)
com.wepay.kafka.connect.bigquery.exception.BigQueryConnectException: Some write threads encountered unrecoverable errors: java.lang.IllegalArgumentException; See logs for more detail
at com.wepay.kafka.connect.bigquery.write.batch.KCBQThreadPoolExecutor.awaitCurrentTasks(KCBQThreadPoolExecutor.java:95)
at com.wepay.kafka.connect.bigquery.BigQuerySinkTask.flush(BigQuerySinkTask.java:97)
at org.apache.kafka.connect.sink.SinkTask.preCommit(SinkTask.java:125)
at org.apache.kafka.connect.runtime.WorkerSinkTask.commitOffsets(WorkerSinkTask.java:380)
at org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:210)
at org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:194)
at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:175)
at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:219)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

and:

[2019-02-14 07:36:14,504] ERROR Task failed with java.lang.IllegalArgumentException error: null (com.wepay.kafka.connect.bigquery.write.batch.KCBQThreadPoolExecutor:66)
Exception in thread "pool-32-thread-4" java.lang.IllegalArgumentException
at com.google.api.client.repackaged.com.google.common.base.Preconditions.checkArgument(Preconditions.java:111)
at com.google.api.client.util.Preconditions.checkArgument(Preconditions.java:37)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:135)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:172)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:172)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:145)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:172)
at com.google.api.client.json.JsonGenerator.serialize(JsonGenerator.java:106)
at com.google.api.client.http.json.JsonHttpContent.writeTo(JsonHttpContent.java:78)
at com.google.api.client.http.GZipEncoding.encode(GZipEncoding.java:49)
at com.google.api.client.http.HttpEncodingStreamingContent.writeTo(HttpEncodingStreamingContent.java:51)
at com.google.api.client.util.IOUtils.computeLength(IOUtils.java:113)
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:927)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:419)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:352)
at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:469)
at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.insertAll(HttpBigQueryRpc.java:281)
at com.google.cloud.bigquery.BigQueryImpl.insertAll(BigQueryImpl.java:445)
at com.wepay.kafka.connect.bigquery.write.row.SimpleBigQueryWriter.performWriteRequest(SimpleBigQueryWriter.java:65)
at com.wepay.kafka.connect.bigquery.write.row.BigQueryWriter.writeRows(BigQueryWriter.java:117)
at com.wepay.kafka.connect.bigquery.write.batch.TableWriter.run(TableWriter.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Is this a known issue, or one that's easy to debug through a means I'm simply missing?
There's a chance it may be a data set issue (though I'm less convinced on that because it's failing at different points on different runs), but even so, I'd expect the connector to robustly handle that. Any ideas?

Hi all,
Just an update here: we discovered the root cause which was trying to stream "Inf" into the table. This meets the IEEE spec for floats; but not the JSON spec so it's failing on Google's BigQuery API. I think it's reasonable that you fail here.
However, I do feel like there's still a weirdness here - the connector is not handling the error case correctly. It shouldn't start streaming duplicates, it should fail more catastrophically.
David

The BQ API accepts the string "Infinity" in the JSON object for cases where you want to stream the float Infinity into a table, and the BQ Java client library looks like it will correctly pass this string through. However, the BQ Java client library won't do the conversion automatically, so the client code must substitute string "Infinity" for float Infinity as appropriate.
Ideally the Java client library would do this automatically, and we can consider it for a future version. At the very least, I agree it should fail more gracefully. :-)

In case anyone found this, this should be handled now by this configuration:
convertDoubleSpecialValues
Designates whether +Infinity is converted to Double.MAX_VALUE and whether -Infinity and NaN are converted to Double.MIN_VALUE to ensure successfull delivery to BigQuery.

Type: boolean
Default: false
Importance: low


[Feature] Added a "variables" tag for the components page.

This adds the "variables" tag from automations to the integration. IT ONLY WORKS IN THE CONFIGURATION. (In the service, templates are rendered by HA. I therefore cannot give it the variables.)
This technically would make it easier for people to share pre-made components pages. Users would only have to change some variables, whilst page creators would handle the rest!
Example usage: (in the config)
- page_type: components
  variables:
    test_var: input_number.kml
  components:
    - type: image
      image_path: /config/custom_components/divoom_pixoo/img/sunpower.png
      position:
        - 2
        - 1
    - type: text
      content: "{{ states(test_var) }}"
      color: "{{ [255,175,0] if states(test)|int >= 1 else [131,131,131] }}"
      font: GICKO
      position:
        - 17
        - 8

i think i found a bug i had tried to write the progressbar as non special pages and therefore had to calculate the progressbar size but the size does not allow templates anyway it does not work
works in automations:
page_type: components
components:
  - type: image
    image_url: https://pub.inflowbogie.dev/lock_closed.png
    position:
      - 50
      - "{{ 5 * 6 }}"
    resample_mode: box
    height: 20

does not work in the configuration
- page_type: components
  components:
    - type: image
      image_url: https://pub.inflowbogie.dev/lock_closed.png
      position:
        - 50
        - "{{ 5 * 6 }}"
      resample_mode: box
      height: 20

You're right. The variables tag only works with templatable tags. There are a few that are left that don't get rendered (like the position of images). This PR basically added a parameter to the async-render method, but if it isn't called in the first time, it's obviously not going to work.

i was surprised because i thought that size and position in the rectangle, for example, already had an async-render method


Do not depend on c99 for(int

Why? It's a c11 project.

It’s the only variable defined inside the for statment and pops a warning when compiling it from other projects that dont set c99 compat. I would appreciate it

Yes it's the only change... for now.
I don't mind landing the change, but I worry we'll have to find ourselves defending the inclusion of c11 features as a requirement in the future, when this project has set c11 as the requirement from the start.
Why can't you compile QuickJS in c11 mode?

R2 target build support for old compilers, i’m gradually deprecating some and i prefer not to add extra flags when compiling C code. For example visual studio only added support for c11 in 2022 iirc.. and r2 builds on windows xp and other ancient unixes like pre-2000 AIX systems that are still running nowadays. I would like to have workarounds for portability reasons if needed. But considering this is just the only thing that compilers complain it shouldnt really harm. I can have local patches if needed. But i totally understand the qjsng requirements, and personally from the coding style pov, definining variables inside the for statement always looked a like a c++ism to me. But anyway thats just personal needs that wanted to share, whatever you choose to do with the pr im fine :)

I'm okay with landing this but it's at best temporary reprieve. I'm curious, what will you do when we merge something old compilers simply choke on?

That’s a problem for my future self (:


Reading PV (present values) of Counters

Hello,
First of all, let me congratulate, this is an awsome library!
But I have a problem. I am trying to read the present value of a counter (actually 4 counters) of a CP1L-EL, but I get always the same value (I am absolutelly sure that the counters are counting, so the value I read should change every time I read them, but they don't). Can you give me some advice on what to do?

I'm sorry for replying so late.
I'm afraid that current version doesn't support PLCs other than NX series. CP1L-EL is CP series and this library may not be able to work with it.


gh-1520 - removed hadoop-hdfs dependency from spark-library

Also fixed road traffic data loader so the data iterable can be consumed multiple times

Codecov Report

Merging #1523 into develop will increase coverage by 5.98%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #1523      +/-   ##
=============================================
+ Coverage      66.23%   72.21%   +5.98%
+ Complexity      1768      458    -1310
=============================================
  Files            731      290     -441
  Lines          24232     9071   -15161
  Branches        3129      987    -2142
=============================================
- Hits           16051     6551    -9500
+ Misses          6915     2085    -4830
+ Partials        1266      435     -831

Impacted Files
Coverage Δ
Complexity Δ

.../java/uk/gov/gchq/gaffer/jobtracker/JobStatus.java

...n/java/uk/gov/gchq/gaffer/commonutil/TextUtil.java

...on/handler/job/initialiser/AvroJobInitialiser.java

...r/parquetstore/io/writer/ParquetElementWriter.java

...affer/hdfs/operation/SampleDataForSplitPoints.java

...nutil/elementvisibilityutil/ElementVisibility.java

...chq/gaffer/commonutil/stream/GafferCollectors.java

...store/operation/resolver/DefaultScoreResolver.java

.../gov/gchq/gaffer/operation/OperationException.java

...uk/gov/gchq/gaffer/cache/AbstractCacheService.java

... and 431 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e56b277...95fec45. Read the comment docs.


Optionally allow keyboard interaction when mouse cursor is not inside the grid

When mouse cursor moves outside of the grid the grid loses focus (grid.hasFocus set to false) disabling keyboard interaction.
 Focus can also be set programmatically (grid.focus) to allow user input irrespective of mouse cursor location.

Super!


Revert "ci: use locally built pydantic-core with debug symbols

Codspeed broken with changes, temporarily reverting so we can do perf analysis in the meantime

@davidhewitt, I think we should revisit, I'm concerned this was due to v2.27.1 in pydantic-core...

Merging just so we can get codspeed going again.


[Question] Does this module suport merge image with other y,x

This module https://github.com/lukechilds/merge-images
have option to merge images at specific points
mergeImages([
  { src: 'body.png', x: 0, y: 0 },
  { src: 'eyes.png', x: 32, y: 0 },
  { src: 'mouth.png', x: 16, y: 0 }
])
  .then(b64 => ...);

can we achive that in this module ?

just use this :D
https://github.com/guhungry/react-native-photo-manipulator