[BUG] FirebaseCrashlytics compilation error

Describe the bug
I’m integrating Firebase Analytics into an app I’m working on and it’s not working. Perhaps these logs will help, otherwise, I can try to make a sample project to reproduce it.
I’m getting a compilation error when trying to build my app. It seems that the script is affecting the FirebaseCrashytics build.

Stack
   CocoaPods : 1.10.0
        Ruby : ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-darwin19]
    RubyGems : 3.2.1
        Host : macOS 11.2 (20D5029f)
       Xcode : 12.3 (12C33)
         Git : git version 2.29.2
Ruby lib dir : /Users/brettbest/.rbenv/versions/2.7.0/lib
Repositories : trunk - CDN - https://cdn.cocoapods.org/

Installation Source
Executable Path: /Users/brettbest/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/bin/pod

Plugins
cocoapods-deintegrate : 1.0.4
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-trunk       : 1.5.0
cocoapods-try         : 1.2.0

Podfile
load 'CatalystPodSupport/remove_ios_only_frameworks.rb'

project 'medCompanion', 'Release - Production' => :release, 'Release - Staging' => :release, 'Release - Development' => :release, 'Debug - Production' => :debug, 'Debug - Staging' => :debug, 'Debug - Development' => :debug

platform :ios, '13.1'

inhibit_all_warnings!

def reveal_sdk_pod
  # UI Debugging - Reveal-SDK isn't included in the archived version of the app.
  pod 'Reveal-SDK', :configurations => ['Debug - Production', 'Debug - Staging', "Debug - Development"]
end

def shared_pods
  # UI
  pod 'SwiftUIX', :git => 'https://github.com/Brett-Best/SwiftUIX.git', :branch => 'master'
  pod 'PureSwiftUI', :git => 'https://github.com/Brett-Best/pure-swift-ui.git', :branch => 'feature/MPP-Support'
  pod 'PureSwiftUITools', :git => 'https://github.com/Brett-Best/pure-swift-ui-tools.git', :branch => 'feature/MPP-Support-CP'

  # Networking
  pod 'Alamofire'
  pod 'AlamofireImage'
  pod 'Moya', '15.0.0-alpha.1'

  # Async Handling
  pod 'PromiseKit', :subspecs => ['CoreLocation', 'CorePromise', 'Foundation', 'UIKit']

  # Crash reporting + analytics
  pod 'Firebase', :subspecs => ['Analytics', 'Crashlytics']

  # Security
  pod 'KeychainAccess'

  reveal_sdk_pod

  # Linting
  pod 'SwiftLint'
end

target 'medCompanion iOS' do
  use_frameworks!

  shared_pods

  # UI
  pod 'QRCodeReader.swift', :git => 'https://github.com/Brett-Best/QRCodeReader.swift.git', :branch => 'fix/mac-catalyst'

  # Licenses
  pod 'LicensePlist'

  target 'medCompanion iOS Tests' do
    inherit! :search_paths
  end

  target 'medCompanion iOS UI Tests' do

  end

end

target 'medCompanion iOS Today Extension' do
  use_frameworks!

  shared_pods
end

target 'medCompanion iOS Widget Extension' do
  use_frameworks!

  shared_pods
end

target 'medCompanion iOS App Clip' do
  platform :ios, '14.0'

  use_modular_headers!

  # Linting
  pod 'SwiftLint'

  # Networking
  pod 'Alamofire'
  pod 'Kingfisher', :git => 'https://github.com/onevcat/Kingfisher.git', :branch => 'master'

  target 'medCompanion iOS App Clip Tests' do
    inherit! :search_paths
  end

  target 'medCompanion iOS App Clip UI Tests' do

  end
end

target 'medCompanion watchOS' do
  platform :watchos, '7.0'
  use_frameworks!
end

target 'medCompanion watchOS Extension' do
  platform :watchos, '7.0'
  use_frameworks!

  # UI
  pod 'SwiftUIX', :git => 'https://github.com/Brett-Best/SwiftUIX.git', :branch => 'master'
  pod 'PureSwiftUI', :git => 'https://github.com/Brett-Best/pure-swift-ui.git', :branch => 'feature/MPP-Support'
  pod 'PureSwiftUITools', :git => 'https://github.com/Brett-Best/pure-swift-ui-tools.git', :branch => 'feature/MPP-Support-CP'

  # Networking
  pod 'Alamofire'
  pod 'AlamofireImage'
  pod 'Moya', '15.0.0-alpha.1'

  # Async Handling
  pod 'PromiseKit', :subspecs => ['CoreLocation', 'CorePromise', 'Foundation']

  # Crash reporting
  pod 'Firebase', :subspecs => ['Crashlytics']

  # Security
  pod 'KeychainAccess'

  # Linting
  pod 'SwiftLint'
end

def catalyst_unsupported_pods
  ['Firebase/Analytics']
end

def debug
  true
end

post_install do |installer|
  system('./Scripts/generate-acknowledgements.sh')
  installer.configure_support_catalyst
  installer.pods_project.build_configurations.each do |config|
    config.build_settings['OTHER_SWIFT_FLAGS'] = "$(inherited) -Xfrontend -enable-experimental-concise-pound-file"
  end
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.1'
      config.build_settings['WATCHOS_DEPLOYMENT_TARGET'] = '7.0'
      config.build_settings['MACOSX_DEPLOYMENT_TARGET'] = '10.15.1'
    end
  end
end

Additional context
Podfile.lock
PODS:
  - Alamofire (5.4.0)
  - AlamofireImage (4.1.0):
    - Alamofire (~> 5.1)
  - Firebase/Analytics (7.3.0):
    - Firebase/Core
  - Firebase/Core (7.3.0):
    - Firebase/CoreOnly
    - FirebaseAnalytics (= 7.3.0)
  - Firebase/CoreOnly (7.3.0):
    - FirebaseCore (= 7.3.0)
  - Firebase/Crashlytics (7.3.0):
    - Firebase/CoreOnly
    - FirebaseCrashlytics (~> 7.3.0)
  - FirebaseAnalytics (7.3.0):
    - FirebaseCore (~> 7.0)
    - FirebaseInstallations (~> 7.0)
    - GoogleAppMeasurement (= 7.3.0)
    - GoogleUtilities/AppDelegateSwizzler (~> 7.0)
    - GoogleUtilities/MethodSwizzler (~> 7.0)
    - GoogleUtilities/Network (~> 7.0)
    - "GoogleUtilities/NSData+zlib (~> 7.0)"
    - nanopb (~> 2.30906.0)
  - FirebaseCore (7.3.0):
    - FirebaseCoreDiagnostics (~> 7.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
  - FirebaseCoreDiagnostics (7.3.0):
    - GoogleDataTransport (~> 8.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/Logger (~> 7.0)
    - nanopb (~> 2.30906.0)
  - FirebaseCrashlytics (7.3.0):
    - FirebaseCore (~> 7.0)
    - FirebaseInstallations (~> 7.0)
    - GoogleDataTransport (~> 8.0)
    - nanopb (~> 2.30906.0)
    - PromisesObjC (~> 1.2)
  - FirebaseInstallations (7.3.0):
    - FirebaseCore (~> 7.0)
    - GoogleUtilities/Environment (~> 7.0)
    - GoogleUtilities/UserDefaults (~> 7.0)
    - PromisesObjC (~> 1.2)
  - GoogleAppMeasurement (7.3.0):
    - GoogleUtilities/AppDelegateSwizzler (~> 7.0)
    - GoogleUtilities/MethodSwizzler (~> 7.0)
    - GoogleUtilities/Network (~> 7.0)
    - "GoogleUtilities/NSData+zlib (~> 7.0)"
    - nanopb (~> 2.30906.0)
  - GoogleDataTransport (8.1.0):
    - nanopb (~> 2.30906.0)
  - GoogleUtilities/AppDelegateSwizzler (7.1.1):
    - GoogleUtilities/Environment
    - GoogleUtilities/Logger
    - GoogleUtilities/Network
  - GoogleUtilities/Environment (7.1.1):
    - PromisesObjC (~> 1.2)
  - GoogleUtilities/Logger (7.1.1):
    - GoogleUtilities/Environment
  - GoogleUtilities/MethodSwizzler (7.1.1):
    - GoogleUtilities/Logger
  - GoogleUtilities/Network (7.1.1):
    - GoogleUtilities/Logger
    - "GoogleUtilities/NSData+zlib"
    - GoogleUtilities/Reachability
  - "GoogleUtilities/NSData+zlib (7.1.1)"
  - GoogleUtilities/Reachability (7.1.1):
    - GoogleUtilities/Logger
  - GoogleUtilities/UserDefaults (7.1.1):
    - GoogleUtilities/Logger
  - KeychainAccess (4.2.1)
  - Kingfisher (5.15.8)
  - LicensePlist (3.0.5)
  - Moya (15.0.0-alpha.1):
    - Moya/Core (= 15.0.0-alpha.1)
  - Moya/Core (15.0.0-alpha.1):
    - Alamofire (~> 5.0)
  - nanopb (2.30906.0):
    - nanopb/decode (= 2.30906.0)
    - nanopb/encode (= 2.30906.0)
  - nanopb/decode (2.30906.0)
  - nanopb/encode (2.30906.0)
  - PromiseKit/CoreLocation (6.13.1):
    - PromiseKit/CorePromise
  - PromiseKit/CorePromise (6.13.1)
  - PromiseKit/Foundation (6.13.1):
    - PromiseKit/CorePromise
  - PromiseKit/UIKit (6.13.1):
    - PromiseKit/CorePromise
  - PromisesObjC (1.2.11)
  - PureSwiftUI (2.0.3)
  - PureSwiftUITools (2.0.1):
    - PureSwiftUI
  - QRCodeReader.swift (10.1.0)
  - Reveal-SDK (27)
  - SwiftLint (0.42.0)
  - SwiftUIX (0.0.4)

DEPENDENCIES:
  - Alamofire
  - AlamofireImage
  - Firebase/Analytics
  - Firebase/Crashlytics
  - KeychainAccess
  - Kingfisher (from `https://github.com/onevcat/Kingfisher.git`, branch `master`)
  - LicensePlist
  - Moya (= 15.0.0-alpha.1)
  - PromiseKit/CoreLocation
  - PromiseKit/CorePromise
  - PromiseKit/Foundation
  - PromiseKit/UIKit
  - PureSwiftUI (from `https://github.com/Brett-Best/pure-swift-ui.git`, branch `feature/MPP-Support`)
  - PureSwiftUITools (from `https://github.com/Brett-Best/pure-swift-ui-tools.git`, branch `feature/MPP-Support-CP`)
  - QRCodeReader.swift (from `https://github.com/Brett-Best/QRCodeReader.swift.git`, branch `fix/mac-catalyst`)
  - Reveal-SDK
  - SwiftLint
  - SwiftUIX (from `https://github.com/Brett-Best/SwiftUIX.git`, branch `master`)

SPEC REPOS:
  trunk:
    - Alamofire
    - AlamofireImage
    - Firebase
    - FirebaseAnalytics
    - FirebaseCore
    - FirebaseCoreDiagnostics
    - FirebaseCrashlytics
    - FirebaseInstallations
    - GoogleAppMeasurement
    - GoogleDataTransport
    - GoogleUtilities
    - KeychainAccess
    - LicensePlist
    - Moya
    - nanopb
    - PromiseKit
    - PromisesObjC
    - Reveal-SDK
    - SwiftLint

EXTERNAL SOURCES:
  Kingfisher:
    :branch: master
    :git: https://github.com/onevcat/Kingfisher.git
  PureSwiftUI:
    :branch: feature/MPP-Support
    :git: https://github.com/Brett-Best/pure-swift-ui.git
  PureSwiftUITools:
    :branch: feature/MPP-Support-CP
    :git: https://github.com/Brett-Best/pure-swift-ui-tools.git
  QRCodeReader.swift:
    :branch: fix/mac-catalyst
    :git: https://github.com/Brett-Best/QRCodeReader.swift.git
  SwiftUIX:
    :branch: master
    :git: https://github.com/Brett-Best/SwiftUIX.git

CHECKOUT OPTIONS:
  Kingfisher:
    :commit: 532ee52cb32a1c28bde19867798f10ee71a46715
    :git: https://github.com/onevcat/Kingfisher.git
  PureSwiftUI:
    :commit: efdd2681a9c43db8c40c36a1d41bb7ec7e714935
    :git: https://github.com/Brett-Best/pure-swift-ui.git
  PureSwiftUITools:
    :commit: 6e8327e33dd64ad6cef597608e4ab5cb2d4445ca
    :git: https://github.com/Brett-Best/pure-swift-ui-tools.git
  QRCodeReader.swift:
    :commit: ba74f762de3f13c6ba5453cb8b031986edd0f9e6
    :git: https://github.com/Brett-Best/QRCodeReader.swift.git
  SwiftUIX:
    :commit: a6c9db6f9a271ca91e2b2e84d4d1c1aeeb8920c8
    :git: https://github.com/Brett-Best/SwiftUIX.git

SPEC CHECKSUMS:
  Alamofire: 3b6a534a3df22db367e4dedeeca73d1ddfcf0e2f
  AlamofireImage: c4a2ba349885fb3064feb74d2e547bd42ce9be10
  Firebase: 26223c695fe322633274198cb19dca8cb7e54416
  FirebaseAnalytics: 2580c2d62535ae7b644143d48941fcc239ea897a
  FirebaseCore: 4d3c72622ce0e2106aaa07bb4b2935ba2c370972
  FirebaseCoreDiagnostics: d50e11039e5984d92c8a512be2395f13df747350
  FirebaseCrashlytics: d31325312c92e2cb2f0386d589b9aa44e303d99b
  FirebaseInstallations: 971df89b48ae5ee4cc2bf6935f3857a525d28550
  GoogleAppMeasurement: 8d3c0aeede16ab7764144b5a4ca8e1d4323841b7
  GoogleDataTransport: 116c84c4bdeb76be2a7a46de51244368f9794eab
  GoogleUtilities: 3dc4ff0d5e4840e2fa8eef0889620e8c33d4218c
  KeychainAccess: 9b07f665298d13c3a85881bd3171f6f49b8151c1
  Kingfisher: a725475a625dc8049722ecf6160cf1e1042507fc
  LicensePlist: 11c638fa9dc22ddb5771cdf910242ae1ba2684da
  Moya: 101c94dfb29289736ecd20fa6e82bea665e0671b
  nanopb: 1bf24dd71191072e120b83dd02d08f3da0d65e53
  PromiseKit: 28fda91c973cc377875d8c0ea4f973013c05b6db
  PromisesObjC: 8c196f5a328c2cba3e74624585467a557dcb482f
  PureSwiftUI: e1bd50bd38dc43036e4ed305d6893249603db3a4
  PureSwiftUITools: eb7954807f9190f201d69735e9566542dcae5ca1
  QRCodeReader.swift: 373a389fe9a22d513c879a32a6f647c58f4ef572
  Reveal-SDK: 306e2880395ee396f5a8b4c485c3a86dd19866c7
  SwiftLint: 4fa9579c63416865179bc416f0a92d55f009600d
  SwiftUIX: 9147cc2f523caf0d7af030cf51809b95fc9c8a38

PODFILE CHECKSUM: 0118302b6b636fb039056a5d5542ec38d513c31a

COCOAPODS: 1.10.0

Pod install log (trimmed to relevant parts):
#### Unsupported Libraries ####
["FirebaseAnalytics", "Firebase", "FirebaseCore-iOS", "FirebaseInstallations-iOS", "GoogleAppMeasurement", "GoogleUtilities-00567490", "nanopb-iOS", "GoogleUtilities-00567490", "FirebaseCoreDiagnostics-iOS", "FirebaseCore-iOS", "PromisesObjC-iOS", "GoogleUtilities-00567490", "GoogleUtilities-00567490", "nanopb-iOS", "PromisesObjC-iOS", "GoogleUtilities-00567490", "FirebaseCoreDiagnostics-iOS", "GoogleDataTransport-iOS", "GoogleUtilities-00567490", "nanopb-iOS", "PromisesObjC-iOS", "GoogleDataTransport-iOS", "GoogleUtilities-00567490", "nanopb-iOS", "nanopb-iOS", "PromisesObjC-iOS", "nanopb-iOS", "PromisesObjC-iOS"]

#### Unsupported dependencies ####
["sqite3", "FirebaseCoreDiagnostics", "GoogleUtilities", "FirebaseAnalytics", "FirebaseCore-iOS", "FirebaseCoreDiagnostics-iOS", "FirebaseInstallations-iOS", "GoogleAppMeasurement", "GoogleDataTransport-iOS", "GoogleUtilities-00567490", "PromisesObjC-iOS", "nanopb-iOS", "FIRAnalyticsConnector", "sqlite3"]

#### Frameworks not to be included in the Archive ####
["FirebaseCoreDiagnostics.framework", "GoogleUtilities.framework", "GoogleUtilities.framework", "GoogleUtilities.framework", "FirebaseAnalytics.framework", "FirebaseCore-iOS.framework", "FirebaseCoreDiagnostics-iOS.framework", "FirebaseInstallations-iOS.framework", "GoogleAppMeasurement.framework", "GoogleDataTransport-iOS.framework", "GoogleUtilities-00567490.framework", "PromisesObjC-iOS.framework", "nanopb-iOS.framework", "FIRAnalyticsConnector.framework", "FirebaseAnalytics.framework", "GoogleAppMeasurement.framework"]

#### Resources not to be included in the Archive ####
[]

#### Flagging unsupported libraries ####
	Target: Alamofire-framework-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Alamofire-library
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: AlamofireImage-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Firebase-Analytics-Core-CoreOnly-Crashlytics
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: FirebaseAnalytics
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: FirebaseCore-iOS
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: FirebaseCoreDiagnostics-iOS
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: FirebaseCrashlytics-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: FirebaseInstallations-iOS
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: GoogleAppMeasurement
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: GoogleDataTransport-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: GoogleUtilities-00567490
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: KeychainAccess-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Kingfisher
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: LicensePlist
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Moya-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: PromiseKit-CoreLocation-CorePromise-Foundation-UIKit
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: PromisesObjC-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: PureSwiftUI-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: PureSwiftUITools-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: QRCodeReader.swift
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Reveal-SDK
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: SwiftLint-framework-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: SwiftLint-library
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: SwiftUIX-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: nanopb-iOS
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Pods-medCompanion iOS
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Succeded
		Scheme: Debug - Development
			Succeded
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Succeded
		Scheme: Release - Development
			Succeded
	Target: Pods-medCompanion iOS App Clip
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Pods-medCompanion iOS App Clip Tests
		Scheme: Debug - Production
			Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Pods-medCompanion iOS App Clip-medCompanion iOS App Clip UI Tests
		Scheme: Debug - Production
				Nothing to flag
		Scheme: Debug - Staging
			Nothing to flag
		Scheme: Debug - Development
			Nothing to flag
		Scheme: Release - Production
			Nothing to flag
		Scheme: Release - Staging
			Nothing to flag
		Scheme: Release - Development
			Nothing to flag
	Target: Pods-medCompanion iOS Tests
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Succeded
		Scheme: Debug - Development
			Succeded
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Succeded
		Scheme: Release - Development
			Succeded
	Target: Pods-medCompanion iOS Today Extension
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Succeded
		Scheme: Debug - Development
			Succeded
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Succeded
		Scheme: Release - Development
			Succeded
	Target: Pods-medCompanion iOS Widget Extension
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Succeded
		Scheme: Debug - Development
			Succeded
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Succeded
		Scheme: Release - Development
			Succeded
	Target: Pods-medCompanion iOS-medCompanion iOS UI Tests
		Scheme: Debug - Production
			Succeded
		Scheme: Debug - Staging
			Succeded
		Scheme: Debug - Development
			Succeded
		Scheme: Release - Production
			Succeded
		Scheme: Release - Staging
			Succeded
		Scheme: Release - Development
			Succeded

#### Filtering build phases ####
	Target: FirebaseCore-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: FirebaseCoreDiagnostics-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: FirebaseInstallations-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: GoogleDataTransport-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: GoogleUtilities-00567490
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: PromisesObjC-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies
	Target: nanopb-iOS
		- Filtering resources
		- Filtering compile sources
		- Filtering frameworks
		- Filtering headers
		- Filtering dependencies

#### Filtering dependencies ####
	Target: FirebaseAnalytics
		- Filtering dependencies
	Target: GoogleAppMeasurement
		- Filtering dependencies

#### Changing frameworks and resources script ####
	Target: Pods-medCompanion iOS
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Succeded
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS App Clip
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS App Clip Tests
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS App Clip-medCompanion iOS App Clip UI Tests
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS Tests
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS Today Extension
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS Widget Extension
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
	Target: Pods-medCompanion iOS-medCompanion iOS UI Tests
		-Uninstalling frameworks
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Succeded
		-Uninstalling resources
			Uninstalling for configurations: ["Release", "Debug", "Debug - Production", "Debug - Staging", "Debug - Development", "Release - Production", "Release - Staging", "Release - Development"]
			Nothing to uninstall
    - Podfile
  - Writing Xcode project file to `Pods/Pods.xcodeproj`

Pod project (with analytics subspecies) [doesn’t compile]:

Pod project (if I remove the Analytics subspec) [compiles fine]:

Hi @Brett-Best , I've modified the regex expression I use to look up dependencies, can you please try again with the updated version?
For the record, the issue is CocoaPods renames dependencies when they're part of targets with different SDKs. Same happens with different versions and frameworks vs libraries. In this particular case, FirebaseCrashlytics has a dependency called FirebaseCore which was named as FirebaseCore-iOS. The current regex expression was expecting something like iOS13.2, but not just iOS. FirebaseCore wasn't being determined as a FirebaseCrashlytics dependency and it was wrongly being removed

Thanks @fermoya, can confirm the change fixes the problem for me :D


Refactored Dsc to stand-alone file, added tests and fixes

Refactored Dsc to stand-alone file and added tests
Changes to address issue in GetUuidEntryFromUuid #15
Addressed inconsistent return values of ReadFmtStringAndEntriesFromVirtualOffset #17

@ydkhatri please merge #12 and #13 first and let me know when you did so I can fix merge conflicts.

These files appear to be +50M I'll see if I can craft a smaller one for testing.

@ydkhatri please merge #12 and #13 first and let me know when you did so I can fix merge conflicts.

All done.

@ydkhatri merged changed, this PR contains fixes for #15 and #17.

@ydkhatri PR updated, I've made an additional change based on your input.


sanitycheck: do not try platforms not in hardware map

Get list of connected hardware and filter tests to only be run on connected
hardware in cases where no platform was specified when runn the tests.  If the
platform does not exist in the hardware map, just skip it.
Fixes #29166

I had a test and I bumped into a (minor) issue.

the table is informational only, it shows you what devices are connected, and which are not.


Stake pool popup description is being cut

[Minor] Stake pool description is being violently cut even though it adheres to json schema. See original text.
Solution 1: Provide full 255 characters.
Solution 2: Add text ellipsis.

Fixed in: https://github.com/input-output-hk/daedalus/releases/tag/2.2.0-ITN1
Please upgrade your Daedalus by downloading the latest version from: https://staking.cardano.org/delegation/


Empty post data

Hey, I m new to http-client, I m trying POST request with post data. The request is POST but the data is empty.
here's the code:
Loop::run(function () {
	$client = HttpClientBuilder::buildDefault();

	$baseUrl = 'http://localhost/test.php';

	$response = yield $client->request(new Request($baseUrl, 'POST', 'test1=1&test2=2'));

	var_dump($response->getStatus());
	var_dump($response->getHeaders());
	var_dump(yield $response->getBody()->buffer());die;
});

here's test.php code:
if ($_SERVER['REQUEST_METHOD'] === 'POST') {
       // $_POST is empty, it should be "test1=1&test2=2"
       echo '<pre>';print_r($_POST);exit('POST');
} else {
       exit('GET');
}

Can you tell me how to build a post request correctly?

I found the solution by using addHeader.
$request = new Request($url, 'POST', '');
$request->setBody('test1=1&test2=2');
$request->addHeader('Content-Type', 'application/x-www-form-urlencoded');

You probably want to use FormBody instead: https://github.com/amphp/http-client/blob/4daa9998c955aa9f14ae0096946a3d78a2f32490/examples/basic/4-forms.php#L19


Use int/Integer instead of BigInteger

The data classes created by JAXB should use int and Maps should use Integer. Usage of BigInteger requires some conversions.
This can be easily fixed by using xsd:int instead of xsd:Integer in the XSD files.

Same should happen for BigDecimal, here, double or Double should be used


Improve coverage for model package

Package: https://github.com/rodrigo-brito/ninjabot/tree/main/model

I would like to work on it


Hass Agent is picking up incorrect values for the webcam and microphone

Hey there, over the past few days I've noticed Hass Agent is saying my Microphone and Webcam are being used by OBS64 even when OBS wasn't open so I uninstalled both OBS and Streamlabs to test, it's been 3 days since I uninstalled them and its still saying they're being used by OBS64. It's not stuck either, the value does change when I turn off the PC but if I don't have the service installed and It's not running in task manager, I don't  know what to make of this.
I use my Desktop Microphone sensor as part of a do not disturb mode too so I need to get this sorted.
Windows Version 22h2 Build 19045.3324
Hassagent version 2022.14.0
UI Langage English
Installed via installer
[2023-09-02] HASS.Agent_20230902.log

Is it possible that the data is comming from retained MQTT messages?
Does the sensor update with other programs? (For example does it show OBS+Discord when you launch it and join any channel)
You say that the value changes when you turn off pc - changes to what?

Is it possible that the data is comming from retained MQTT messages?
Does the sensor update with other programs? (For example does it show OBS+Discord

The process does switch when I open other microphone tools then when I close them it switches back. It's been doing the same thing with Discord now, regardless of whether I have discord open, the Microphone is on and the process is discord.
It changes to unavailable when I turn the PC off. Unsure how to go about fixing this, It didn't used to behave like this.

Installed MQTTexplorer and cleared both microphone active and microphone process. They both fell to an unknown state, I then noticed when i jumped into a discord call, they weren't changing from unknown so I restarted Hass Agent. They're now stuck in an on state and discord again despite me jumping back out of said call

I'll need to think about this...
Is the faulty state consistent across the landscape?
I mean, if it gets stuck at "discord" for example, is this also visible in the:

HA
HASS.Agent sensor config page
MQTT topics
?

I'll need to think about this... Is the faulty state consistent across the landscape? I mean, if it gets stuck at "discord" for example, is this also visible in the:

HA
HASS.Agent sensor config page
MQTT topics
?

Yes it is. Checking Home Assistant and Hass agents last known value, they're both listed as "on" and "discord" despite me not being in a call right now.
Since it's only happening on my desktop with Hass I'm thinking about doing a full system reset on the Desktop. A bit of an extreme measure with a few days to get everything installed again probably but to rule out the PC being the problem.

I don't understand what the issue was still but a complete factory reset of my PC appears to have it working again.

I am also experiencing this issue. My MicrophoneActive and MicrophoneProcess remain stuck in an old state. Resetting my PC is not an option for me.
For example, I was on a WebEx call, but have since closed the application. The MicrophoneActive shows On and the MicrophoneProcess shows CiscoCollabHost (which is WebEx) even though the application was closed and the microphone is no longer being used. If I clear the MQTT messages, the sensors change to Unknown. When I call PublishAllSensors, the microphone state return to On and CiscoCollabHost.
I tried shutting down Hass.Agent and clearing MQTT, which sets the sensor states to Unknown. However, if I call PublishAllSensores, they return to On and CiscoCollabHost again.
I even tried rebooting and clearing MQTT, but the sensors still show the incorrect state.
I decided to go through the code and found the microphone sensor in the Hass.Agent.Shared project. It's basically looking at the registry to determine the status of the microphone. I was able to find an old registry entry that looks like it was never cleared (it was even named XXXX_old!). After deleting that entry, the microphone started reporting the proper state.
The 2 registry locations it looks are are HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\ConsentStore\microphone. Look for all the keys under those for a LastUsedTimeStop with a value of 0. Deleting that value should solve the issue without resetting your PC.


Move CommitteeInfoContract to this repo

current location https://github.com/Ashuaidehao/CommitteeInfoContract

Maybe we can build a general information storage contract, not just for committee?

You mean for all candidates?

You mean for all candidates?

For all contracts

You mean for all candidates?

For all contracts

I'm confused. How is that supposed to be used?
Right now we can take a public key from the committee and look up additional information (such as name, website etc) using the CommitteeInfoContract. How does a general contract information storage going to help there?

I think it'd be nice to have all "official" (NGD/NF) public contracts available from one place (with mainnet/testnet hashes explicitly mentioned in READMEs). As is in their current state. If needed, they can improved/extended here.


This seems to have cut the time of the test suite down by a factor of 2 so I guess that is good?  Need to have a think about how to test and bench mark this for real.

Master branch ============= 470 passed, 22 skipped, 6 warnings in 686.92 seconds =============
This PR ======== 1 failed, 469 passed, 22 skipped, 6 warnings in 359.06 seconds ========
So this has taken ~330s off the test suite run time, that seems like a success to me!

On my home machine, running just the pyepics version of the tests
current master: 311.89 seconds
master right before the kind merge: in 130.26 seconds
gentle_gentle branch: 168.52 seconds (but 20 more tests than baseline)
gentle_gentle branch: 126.75 seconds (not hints or kind test, 5 less tests that paseline)
I think it is safe to say that this works.

________________________________________________________________________________________________________________ test_mca_read_attrs[pyepics] ________________________________________________________________________________________________________________

    @using_fake_epics_pv
    def test_mca_read_attrs():
        # default read_attrs
        mca = EpicsMCA(devs[0], name='test')
        default_normal_kind = ['preset_real_time', 'elapsed_real_time', 'spectrum']
>       assert set(default_normal_kind) == set(mca.read_attrs)
E       AssertionError: assert {'elapsed_rea...', 'spectrum'} == {'spectrum'}
E         Extra items in the left set:
E         'elapsed_real_time'
E         'preset_real_time'
E         Full diff:
E         - {'elapsed_real_time', 'preset_real_time', 'spectrum'}
E         + {'spectrum'}

ophyd/tests/test_mca.py:35: AssertionError

I can see this locally, but re-running it works.  Have only seen this with pyepics (not with caproto).  It is really weird that the fake pv has issues...

Please don't merge yet, this has a nasty mutating-shared-global-state bug.

This is ready to go.

both failures are caproto talking to real epics motor PVs.

The diff on this looks bigger than it really is because I moved the list proxy to be inside of Device, reviewing with white space changes suppressed may be helpful.

All passed except the nightly build. Thanks, @tacaswell for indulging me with these new tests. I am now satisfied that we have not sacrificed the laziness feature accidentally in the course of adding kind.


Add community resources: contributing guide, code of conduct, governance?

I noticed there are already some issues labeled as "good first issue", but without a contributing guide (plus a code of conduct to establish a baseline on how to interact) they can't really be good first issues, at most they can be good first issue for someone who has contributed to other projects but not yet to blackjax.
While I was here, I have no idea if there are some non-written rules about collaboration and decision making between the different projects and people involved but it may also be worth it to add a governance doc at some point, even if a couple sentences.
I will probably be able to review anything related to this on a day/week timescale but I don't think I can send a PR in the near future.

@junpenglao we should formalize all of this before v1 is released and as the library is getting more attention.

If anyone is reading this and interested to know more, this project fits in the "Houseplant" archetype and follows the BDFL model of governance with myself as the dictator. This can be re-evaluated later but no need to formalise things any further at this point.

Would it be ok if I send a PR to add a GOVERNANCE.md with:
Blackjax fits in the ["Houseplant" archetype](https://github.com/OpenTechStrategies/open-source-archetypes/blob/main/arch-houseplant.ltx)
and follows the BDFL model of governance with @rlouf as the benevolent dictator.

By all means!


Allow H5File to act as a context manager itself

This allows the H5File class to be used as a context manager, so you can write:
with H5File(...) as sensor_data:
   ...

i.e. the separate open_H5File function is no longer needed. I've left that function there in case other code is already using it, but if you know that nothing else does use it yet, we can get rid of it.

Great,
Nothing uses open_H5File in the package at least, and probably nothing outside (in theory the normal entry point should be the RunHandler class).
I would get rid of it.

Done :-)


[Searchable Snapshot] Implement the IndexInput classes for block-based storage

Is your feature request related to a problem? Please describe.

The snapshot mechanisms in OpenSearch restore the entire index including the segment files for restoring an index
Searchable snapshot adds support for searching an index without downloading the entire files to disk
The above described protocol needs a new mechanism which will download parts of the file as required by the query

Describe the solution you'd like

The IndexInput interface can be utilized to create a virtual file mechanism which will download blocks of data as needed by the query
The underlying blocks will be cached onto the disk as files which can utilize the seek mechanism to load the appropriate block in memory using the IndexInput interfaces

Describe alternatives you've considered
N/A
Additional context
#3869

POC feature commit: https://github.com/andrross/OpenSearch/pull/101

I'm working on this.


Send meetings to someone else over SMS

Present an easy way to send SMS results to someone else.

https://github.com/bmlt-enabled/yap/issues/272


Fix wrong DirAccess function in project converter

Fixes #66484
create_for_path() opens a DirAccess for root folder, e.g. for res://something/, it opens res://.

Thanks!


how to train ssd_resnet50 on new datasets?

@jay-mahadeokar Could you please share the model training script for open_nsfw?


Example with widget events

Hello,
Cloud You please give example how to use widget.event interface...
I don't clearly got it from your "lisa-ui" project.
The current case: I need to put the close-button into custom widget html.
Thank You!

Hi,
To do that nothing specific to do, create your html close button that trigger an onClose method on your widget, then just propagate the event to your master component that contain the dashboard.
And then just do:
this.dashboard.removeItemById(id); // Id of your widget

on the example app I've done it but for basic widget not a custom one https://github.com/jaumard/ngx-dashboard/blob/master/demo/src/app/app.component.ts#L52 but it's the same concept, just propagate an event from the widget to your "page" component and remove it from the dashboard

And how to subscribe on "onClose" event in parent component?
In lisa-ui project I found such example:
 ref.onChange.subscribe(widgetEvent => this.onDeviceValueChanged(widgetEvent));
That's why I asked about widget.events

If you look at what it is here https://github.com/mylisabox/lisa-ui/blob/master/src/app/components/widget/widget.component.ts#L34
You just need an EvenEmitter that will push event from your widget class:
@Output() onCloseSubject: EventEmitter<YourObjectEventYouWantToPropagate> = new EventEmitter();
....
onClose() {
    this.onCloseSubject.next(new YourObjectEventYouWantToPropagate(this.id));
}

Then on your master component just subscribe to this event like I did ref.onCloseSubject.subscribe(widgetEvent => this.data.dashboard.removeItem(widgetEvent.id));
It's pseudo code but that's the idea.

Yeap, thank You! I've got the working event (onClose) handler.

Great 👍 closing this :)


cudnn error

hello,
I've compiled sucessfully.
however when I tried on my own data, cudnn error happened while cytonMt worked well with the data and script you provided.
cuDNN Error: CUDNN_STATUS_EXECUTION_FAILED src/cytonLib/CuDropoutLayer.cu 37
cytonMt: src/cytonLib/basicHeads.cu:52: cudnnStatus_t cytonLib::checkError_(cudnnStatus_t, const char*, int): Assertion `false' failed.
and
1   the embedding size and hidden size shares one parameter, this is different for me to try different sizes.
2   is there a parameter for the deveceId ?
many thanks.

cytonMt: src/cytonLib/basicHeads.cu:52: cudnnStatus_t cytonLib::checkError_(cudnnStatus_t, const char*, int): Assertion `false' failed.

The error is a run-time error.  Re-setting the cudnn library might solve the problem.

We got no positive experimental results by using different sizes of embedding and hidden size. Maybe we should allow it to be compatible with other tools. Thank you.

code for setting deviceid is in Global.cu Global::init() cudaSetDevice(0)
Usually we do it by setting the environment variable export CUDA_VISIBLE_DEVICES=0,  export CUDA_VISIBLE_DEVICES=1, ...


No permission_xx.json when target sdk is larger than 25

I tested an App which is targeted for sdk 26 and got a empty dict from get_requested_aosp_permissions.
Is there any plan to add newer permission_xx.json?

the permission mappings are generated by axplorer, but API level 25 is the newest available :(
duplicate of #576


Why Frames have scalar Position and Force?

Is there a reason why position and force members of Interfaces.Frame are given as scalar?
This forces any other component to manually handle these components by assembling a vector every time.

I suppose it's more intuitive to adress those coordinates like x and y, rather then r[1] and r[2], resp. And similarly to forces.
@dzimmer Please comment.

I personally appreciate more the indexed version r[1] instead of rx mostly because:

you cannot directly make vectorial operations with split scalar rx and ry
other space vectors are not split in x and y (e.g. direction of Joint.Prismatic)
declaring Real r[2] requires one line instead of two like in Real rx, Real ry
the vectorial notation is convenient also for teaching, as transition to 3D space
the Modelica Standard Library uses indexed notations

This originates from the didactic legacy of the library. Since students
learned to deal with arrays on the way, I made them not part of the
connector
When transforming the library, I asked around our users whether this an
issue and whether we should change it to an array.
However everyone was fine with the x,y solution and did not see an issue
with converting into an array when needed.
So it was kept this way.
tobolar<EMAIL_ADDRESS>schrieb am Di., 1. Okt. 2019, 10:35:

I suppose it's more intuitive to adress those coordinates like x and y,
rather then r[1] and r[2], resp. And similarly to forces.
@dzimmer https://github.com/dzimmer Please comment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dzimmer/PlanarMechanics/issues/145?email_source=notifications&email_token=ABR6NBC3XUMG7FOE44KDY7LQMMDWJA5CNFSM4I3S7L32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAAOWMQ#issuecomment-536931122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABR6NBGGXPZ55ZHAD2SKDZTQMMDWJANCNFSM4I3S7L3Q
.

Ok, I understand.
Anyway, thanks for the interesting library. It will surely come in handy!


Change round_up_to_power_of_2 to be a C++11 valid constexpr

Hi,
This PR changes the more classically written "bit-twiddling" for finding the next power of 2 into a valid C++11 constexpr using a single return statement per constexpr function. This enables atomic_queue to be used in C++11 projects.

Hi Paul, thanks for your contribution, the change is quite neat.


Pages: mishandling of navigation routes with regex pattern matching

Vue devtools version
7.2.1
Link to minimal reproduction
N/A
Steps to reproduce & screenshots

Route contains a parameter with a custom regex (something like :id(\\d+))
On the Vue Devtools, go to the 'Pages' tab and click over the parameter for that specific route
A floating form will appear on the panel to fill up the parameter value
Fill with any given value (eg. 2) and press the 'Navigate' button
The app will navigate to the route .../2(/d+) which is not the desired result

What is expected?
The regex from the route config should not be included when navigating to it from the DevTools 'Pages' tab.
What is actually happening?
Path regex pattern is included when navigating to the route.
Any additional comments?
No response

Wrong repo. Sorry for the noise :(


Migrate filepath to jballerina

Purpose

Migrate filepath to jballerina

Approach

Migrate according to the practice.

Samples

N/A

Remarks

N/A

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

:exclamation: No coverage uploaded for pull request base (jballerina@93962c0). Click here to learn what that means.
The diff coverage is 56.25%.

@@              Coverage Diff              @@
##             jballerina   #15914   +/-   ##
=============================================
  Coverage              ?   19.11%
  Complexity            ?     4843
=============================================
  Files                 ?     1491
  Lines                 ?    75384
  Branches              ?     9870
=============================================
  Hits                  ?    14411
  Misses                ?    59250
  Partials              ?     1723

Impacted Files
Coverage Δ
Complexity Δ

...erinalang/stdlib/filepath/nativeimpl/Absolute.java
33.33% <33.33%> (ø)
1 <0> (?)

...lerinalang/stdlib/filepath/nativeimpl/Matches.java
50% <50%> (ø)
1 <0> (?)

...lerinalang/stdlib/filepath/nativeimpl/Resolve.java
60% <60%> (ø)
1 <0> (?)

.../java/org/ballerinalang/stdlib/filepath/Utils.java
72.72% <75%> (ø)
5 <2> (?)

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 93962c0...6b6ccdb. Read the comment docs.


add :contains(text) and others advanced selectors

made quick solution to be able to use advanced css selectors like ":contains(text)"
it's formed now as library, but what if consider adding this feature to puppeteer itself?
https://github.com/Skadabr/puppeteer-selector
example
const puppeteer = require('puppeteer');
const select = require ('puppeteer-select');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  await page.goto('https://example.com');

  await select(page).assertElementPresent('div.Tag:contains(Events) > button');
  const element = await select(page).getElement('div.Tag:contains(Events) > button');
  await element.click()

  await browser.close();
})();

this lib is using "sizzle"
all available selectors are here https://github.com/jquery/sizzle/wiki#selectors
if authors like the idea I'll make PullRequest

@Skadabr let's keep this as a third-party library for now. Once there's a wide adoption and enough demand, we'll add it in.
Thanks!


Login

Bang, password admin nya apa ?

On Mon, 6 Jul 2020 at 11.09 Skuy Ngoding<EMAIL_ADDRESS>wrote:

Bang, password admin nya apa ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/faridhasyim/ci-siakad/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEU7K7DZJLF4RVAVTFMRNLDR2FE6BANCNFSM4ORG3G3Q
.

Cek database nya aja

di encrypt kan bang,


[Proposal] Don't use the minor version number in the main development branch

Using a branch named 1.9 means that as soon as you release the minor version, all PRs need to be changed to target 1.10 (and so on).
This also means that any branch which still has PRs targetting it cannot be removed, increasing the number of useless branches in the repo.
I suggest using a single 1.x branch for the 1.x development (as done in Twig), allowing to release minor versions as often as you want without creating a mess with branches

:+1:

What about having bugfixes for latest stable 1.x and merging new features for new dev 1.x at same time ?

:-1:

1.x seems like a bad name for a branch. How does composer know what minor version it's associated with when you ask for 1.10.*@dev?

@keradus Is has a good point in that we're maintaining the current minor release along side the upcoming minor release, and the next major release at the same time. That's 3 versions, not just 2.

Some ideas:
master, 1.x, 1.8
or
master, next, current
or
master, features, bugfixes
or
...
The goal is to have one feature branch that is not changed after a new 1.(x+1) release.

I think our current branching system is just fine.

We just release more frequently than say, symfony.

We just release more frequently than say, symfony.

That is the reason, why I would like to change the branching system. ;)
Symfony is using the same system like we do here at the moment.

Goal is great!
But... following Twig is a little to less for us (after @GrahamCampbell) and I dislike idea of naming current stable as stable, bugfixes etc, not so cute as simply version and need little more fun with composer (again, as @GrahamCampbell told).
I need to think deeper about it ;)

I need to think deeper about it ;)

Yeah, there's no hurry. ;)

Just don't stop discussion because of it ;P

I like @stof proposal, but maybe I need to think about it deeper as well.
For example:

How does composer know what minor version it's associated with when you ask for 1.10.*@dev?

wouldn't this be possible through tags?

wouldn't this be possible through tags?

aren't tags work for @stable only ?

Afaik Composer would handle a 1.x branch like 1.x-dev.
And this could be aliased as 1.9.x-dev etc.
https://getcomposer.org/doc/articles/aliases.md#branch-alias

You may also alias a comparable version (i.e. start with numbers, and end with .x-dev), but only as a more specific version. For example, 1.x-dev could be aliased as 1.2.x-dev.

(I'm not sure if that would work..)

And this could be aliased as 1.9.x-dev etc.

You can't alias 1.x because it's already a valid version.

1.9 branch is treated as 1.9.x-dev by packagist.

by composer too

You can't alias 1.x because it's already a valid version.

Hmm, did you read the citation above?

Another idea, something like:
2.0
master (alias to 1.9.x-dev)
1.8

@gharlan Yeh, that might be a better model actually.

Hmm, did you read the citation above?

It looks wrong to me - I tried to alias a branch named 1.x fairly recently to see what happened, and it didn't work.

I tried

When? It should be possible since January: https://github.com/composer/composer/pull/3480

Not a composer issue - it was a packagist issue. Packagist was listing it aliased incorrectly.

Composer reads data from packagist doesn't it?

I think all solutions have some shortcomings.
I decided to leave it as is to have no need to aliasing the branches.
IMO the best way to manage branches is simply do not allow PR to hang too long.
Thank you all for discussion.


Update links in README

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Updates links in main README due to restructuring the chart directory

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e52994c Update links in README

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: marcelbirkner
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @marcelbirkner! It looks like this is your first PR to falcosecurity/charts 🎉

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

e52994c Update links in README

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, marcelbirkner
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: d5dbf2b328f9bcb6e8769fa8a9b8c8e2ec83c05d

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: marcelbirkner
Once this PR has been reviewed and has the lgtm label, please ask for approval from cpanato. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: marcelbirkner
Once this PR has been reviewed and has the lgtm label, please ask for approval from cpanato. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

please use rebase and not merge

Hey @cpanato
I've rebased this PR. The merge commit is now gone. PTA: and approve eventually :pray:

LGTM label has been added.  Git tree hash: 77c05dd7655dfc15532ffa191a168f2d0ea87dbf

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, marcelbirkner
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


to change cluster background

I was wondering if you could advise on the following question. I created the clustered feature layer
and used custom styles (as in this example http://esri.github.io/esri-leaflet/examples/styling-clusters.html ). I have a UI which allows a user to 'filter' clusters for by specific attribute (via .setWhere method). it works fine. Would it be possible to change the background color for those filtered clustres  as well? Thank you.

sorry i didnt see your question until now. the short answer is yes, its possible.
i couldn't figure out a more clever way to do it than looping through each and every L.markerCluster when features are reloaded and:

flagging them as dirty
assigning a different iconCreateFunction to utilize when updating their icon.

http://jsbin.com/xalaxo/edit?html,output
myClusteredFeatureLayer.cluster._featureGroup.eachLayer(function (c) {
  if (c instanceof L.MarkerCluster) {
    c._iconNeedsUpdate = true;
    c._group.options.iconCreateFunction = function (cluster) {
      var count = cluster.getChildCount();
      return new L.divIcon({
        html: count,
        className:'cluster orange-cluster',
        iconSize: null
      });
    }
    c.createIcon();
    c._updateIcon();
 }
});

as you can see, this involves traversing some private properties, so use at your own risk.


Public website does not work

I enjoyed using advise.case.edu for my first two years, but for a while the website's been down. I'm not sure what the project status is, or who I should contact, but I figured here's a good place. Does anyone know what happened?
Any information would be greatly appreciated.
Aidan Montare
rising senior
CWRU Electrical Engineering

The host VM had stopped working (presumably lost its MAC address registration) and the hosting server is now gone. Presumably this has taken any databases with it. This would need to be re-deployed from scratch. Good luck convincing ITS to provide any hosting support for a *.case.edu domain.

The host VM had stopped working (presumably lost its MAC address registration) and the hosting server is now gone. Presumably this has taken any databases with it. This would need to be re-deployed from scratch. Good luck convincing ITS to provide any hosting support for a *.case.edu domain.


Added requirements file to Django sample

Added a requirements file to show which packages are needed to be installed for the Django example to actually work.
To set up a virtual environment with these packages do the following:
virtualenv --no-site-packages virtualenv
. virtualenv/bin/activate
pip install -r requirements.txt

I signed it!

Thank you for the contribution! Please squash your commits?

Is there a plan to update the sample for later Django versions?

@nathanielmanistaatgoogle: No problem! How do I do that when I've already pushed my commits? Can't you squash when you merge?

@wasabigeek: No plan for me at least. I just wanted to help people to make it work in the first place :)

@wasabigeek @pierrei I have new Samples here: https://github.com/google/oauth2client/pull/636 , feel free to take a look/comment . I think Django samples belong more there then here since the only Django specific stuff is the auth (oauth2client used to be part of this repo). So my inclination is just to delete this sample and redirect users there. What do you think?
And @pierrei are you actually using Django 1.4? Or just trying to be helpful? Because if you are then maybe I shouldn't delete them.

Django samples have been removed.


pageMap is undefined after refreshing the page (only with _app.mdx)

Hey, recently I encountered Out Of Memory issues while building the project - what has helped was changing _app.tsx to _app.mdx.
But that introduced another issue - pageMap is undefined after refreshing the page which wasn't happening with _app.tsx. (NOTE: with client-side navigation the pageMap has correct value)

I noticed whenever I use imported components in the theme config the above error occurs.

Here is a sample repo so you can reproduce the bug: https://github.com/hubertbodek/nextra-sample-repo

@dimaMachina hey Dimitri, I sent you a slack message. But I doubt that you're in the habit of checking our connect channel :) Just wanted to let you know that this issue is related to https://www.speakeasy.com/
We're stuck on site development at the moment, and would love love your help!

Closed since I received feedback that you fixed your issue


AVRO-3069: Ignore modified files after build

Make sure you have checked all steps below.
Jira

[X] My PR addresses the following Avro Jira issues and references them in the PR title. For example, "AVRO-1234: My Avro PR"

https://issues.apache.org/jira/browse/AVRO-3069
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Build fix.
Commits

[X] My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain Javadoc that explain what it does

LGTM C++ lint check breakage is previous to this PR


gnu-netcat 0.7.1 zero-IO mode bug

Trying to execute commands such as the following doesn't work:
$ nc -vvz localhost 80
It results in the following error:
assertion "ret == 0" failed: file "core.c", line 372, function: core_tcp_connect Aborted (core dumped)
I can confirm that the aforementioned operation works with netcat 1.11.

Please make a pull request updating to netcat 1.11.


'DataTree' object does not support the context manager protocol

What is your issue?
ds = xr.Dataset(
    {"foo": (("x", "y"), np.random.rand(4, 5))},
    coords={
        "x": [10, 20, 30, 40],
        "y": pd.date_range("2000-01-01", periods=5),
        "z": ("x", list("abcd")),
    },
)
ds.to_netcdf("saved_on_disk.nc")

# works as intended
with xr.open_dataset("saved_on_disk.nc") as ds:
    print(ds)

# doesn't work
with xr.open_datatree("saved_on_disk.nc") as dtree:
    print(dtree)

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
Cell In[5], line 1
----> 1 with xr.open_datatree("saved_on_disk.nc") as dtree:
      2     print(dtree)

TypeError: 'DataTree' object does not support the context manager protocol

@TomNicholas I've first found that, after I've moved the whole tests of xradar to use contextmanager :grimacing: Is it just missing?

That is defined in DataWithCoords: https://github.com/pydata/xarray/blob/main/xarray%2Fcore%2Fcommon.py#L1467-L1471
Should be easy to add this to DataTree as well.

Thanks for raising this - I agree this should be addressed. It's actually a duplicate of https://github.com/pydata/xarray/issues/9337

Great, closing as dupe of #9337.


Update 03-loading.md - Fix missing quote in doctype

Fix missing quote in doctype
Before submitting the PR, please make sure you do the following

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint

Changesets

[ ] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts

thanks 👍


Refactor flutter command execution

This refactors the FlutterCommand class hierarchy to make it easier to understand and extend.
Fixes https://github.com/flutter/flutter/issues/333
@Hixie


Your Bangles by Dr Zeus unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> Dr-Zeus-Your-Bangles

added


Markdown lexer will sometimes not yield closing fence

(Original issue 1389 created by fredrikhl on 2017-10-31T14:41:24.780265+00:00)
When using github-style (GSM) code fences in markdown, the lexer does not yield the closing code fence when using a language hint that does not have a matching lexer.
Cause
This seems to be caused by a premature return-statement in pygments.lexers.markup on line 539 (MarkdownLexer._handle_codeblock)
Examples
Fails
GSM code fences where the language has no matching lexer:
```non-existing-language
The closing code fence (backticks) are not returned by 'get_tokens_unprocessed'
```

Works
GSM code fences where the language hint has a matching lexer:
```bash
echo "properly lexed bash code"
```

Regular markdown code fences, i.e. without a langauge hint:
```
* No lexer hint in the opening fence, so this is not handled by 'Markdown._handle_codeblock'.
* Everything wrapped in the code fences is just emitted as a single 'pygments.token.Text' item.
```

Suggested fix
The function should emit the tuple (match.start(5), String, match.group(5)) before returning, regardless of there being a lexer to process the code block content.
--- a/pygments/lexers/markup.py Mon Mar 13 19:16:03 2017 +0000
+++ b/pygments/lexers/markup.py Tue Oct 31 16:36:06 2017 +0100
@@ -536,10 +536,9 @@
         # no lexer for this language. handle it like it was a code block
         if lexer is None:
             yield match.start(4), String, code
-            return
-
-        for item in do_insertions([], lexer.get_tokens_unprocessed(code)):
-            yield item
+        else:
+            for item in do_insertions([], lexer.get_tokens_unprocessed(code)):
+                yield item

         yield match.start(5), String        , match.group(5)

There should probably also be tests that checks if the combined result of the tokens includes all text given to get_tokens_unprocessed.

(Original issue 1389 last updated on 2018-11-24T17:14:43.499241+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by fredrikhl on 2017-11-10T16:51:58.017696+00:00)
Suggested fix implemented in pull request #741

(Original comment by Anteru on 2018-11-24T17:14:42.466958+00:00)
Merged in fredrikhl/pygments-main (pull request #741)
Fix issue #1389: Markdown lexer bug
Approved-by: Anteru<EMAIL_ADDRESS>→ <<cset 6c7284e16b22>>

(Original comment by Anteru on 2018-11-24T17:14:43.490235+00:00)
Merged in fredrikhl/pygments-main (pull request #741)
Fix issue #1389: Markdown lexer bug
Approved-by: Anteru<EMAIL_ADDRESS>→ <<cset 6c7284e16b22>>


matplotlib package not installed after cantools installation

OS: Ubuntu 20.04 LTS x86_64
kernel: 5.8.0-59-generic
After cantools installation through pip install  the error appears when cantools run:
$ cantools
matplotlib package not installed. Required for producing plots.
Traceback (most recent call last):
  File "/usr/local/bin/cantools", line 8, in <module>
    sys.exit(_main())
  File "/usr/local/lib/python3.8/dist-packages/cantools/__init__.py", line 38, in _main
    from .subparsers import plot
  File "/usr/local/lib/python3.8/dist-packages/cantools/subparsers/plot.py", line 59, in <module>
    plt.rcParams["date.autoformatter.hour"] = "%H:%M"
NameError: name 'plt' is not defined

It's a little buried in the README:

Note that by default matplotlib is not installed with cantools. But it can be by specifying an extra at installation:
$ python3 -m pip install cantools[plot]

I think the first occurrence of the pip install in the readme should include matplotlib since it doesn't seem to run without it. Either that, or fix it to only require the matplotlib package if using the plot command.


return ETH symbol rather than Goerli

@hboon you mean with the special o char?

@hboon you mean with the special o char?

No. From "0.15 Görli (GÖETH)" to "0.15 Görli (ETH)".
The hardcoded string which you updated is used in the app except when displaying the list of tokens in the wallet tab. The symbol is saved into the database, once, upon creation and read to display in the Wallets tab.
But then Görli support isn't available on the app store yet, only 2-3 of us will have this problem, so maybe it's not worth doing a migration for this..

@hboon yes, not yet released. Probably best we simply do it. Will it cause a crash or simply the wrong symbol to be displayed?

Simply wrong symbol for the 2-3 of us until reinstall. No crash or error otherwise.
Probably not worth the effort to do a migration. Up to you.


fix(aws): bucket param input type

parameter bucket type should be str. I believe bucket.id is more appropriate here than bucket which is of Bucket type

parameter bucket type should be str. I believe bucket.id is more appropriate here than bucket which is of Bucket type

Thanks for the PR! Could you also make the same change to the other languages?

Thanks @viveklak . I've pushed the same fix to more AWS docs, and some to GCP - I'm not sure about other languages as I'm more familiar with Python


refactor: Time Master

refactor: using product URL
feat: add batch logic for sender
fix: report icon
feat: add date infos for logger

Codecov Report

Merging #663 (8e9f7ba) into release/0.13.1 (98b78a2) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release/0.13.1     #663   +/-   ##
===============================================
  Coverage           57.14%   57.14%
===============================================
  Files                   1        1
  Lines                  70       70
  Branches               15       15
===============================================
  Hits                   40       40
  Misses                 30       30

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 98b78a2...8e9f7ba. Read the comment docs.

CI Pass and self review


Add Pathfinder-AntennarangePatch from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of linuxgurugamer, to add Pathfinder-AntennarangePatch to CKAN.
Please direct questions about this pull request to linuxgurugamer.

Please delete this, it was superceded by the next one and I forgot to put the "Closes" into the initial comments


Test

Test comment

test

Test comment

Test comment

Test comment

testing comment

Hi @rallytime! Testing testing testing.

Hi @rallytime! Testing testing testing. This is a bot test.

Hi @rallytime! Testing testing testing. This is a bot test.

Hi @rallytime! Testing testing testing. This is a bot test.

Hi @rallytime! Testing testing testing. This is a bot test.

Hi @rallytime! Testing testing testing. This is a bot test.

Hi @rallytime! Testing testing testing. This is a bot test.


-a and -asm cannot be used together

In the README, you state the following:

All switches are optional and can be used simultaneously.
-asm Automatically reboot to Safe Mode (must be used with -a, otherwise ignored)

However, when using the flags -a and -asm together, I get the following error:

ERROR: You cannot use -a and -asm together. Pick one or the other.

These two scenarios are conflicting. Either the readme needs to be updated, or the code needs to allow both flags.

Hi @dcohen613 , good find, thanks. I've updated the documentation to correctly reflect use of the -a and -asm switches.


Destroy on resize issue

When triggering destroy event on resize (only once), result is: TypeError: this.e is null for:
/**
 * Checks window `resize` event.
 * @protected
 */
Owl.prototype.onThrottledResize = function() {
	window.clearTimeout(this.resizeTimer);
	this.resizeTimer = window.setTimeout(this.e._onResize, this.settings.responsiveRefreshRate);
};

+1 same error

any fix for this?

I need to do more test here, but why this.e becomes null after destroy?
should not get their default values instead of null?
like these:
e = {
	_onDragStart: null,
	_onDragMove: null,
	_onDragEnd: null,
	_transitionEnd: null,
	_resizer: null,
	_responsiveCall: null,
	_goToLoop: null,
	_checkVisibile: null
};

I have exactly the same problem. :(
After destroying carousel by:
$('#myCarousel').trigger('destroy.owl.carousel');

carousel is destroyed, but durring resize it's generate error
Uncaught TypeError: Cannot read property '_onResize' of null

so all JS breaks down. :(
Even if this.e should give other values (not null), why don't wrap this this into try cath?
Maybe it will be temporrary solution to avoid breaking JS.

Same problem after destroying carousel although I rebuilt it after...

The js file in the repo is not the good one, you need to clone the repo and then rebuild it with Grunt.
This version should work fine : http://codepen.io/anon/pen/GJKBrR

I went digging in the code - looks like the responsive listener (specifically _onResize) is not being destroyed properly.
Tracked it down to line 622:
this.resizeTimer = window.setTimeout(this.e._onResize, this.settings.responsiveRefreshRate);
My JS is not great so I don't trust myself to fix it - but I thought I came up with a sneaky (and dirty) fix in the meantime: the error relates to a responsive carousel so I was going to reinit the carousel with responsive: false just before destroying it... however, I cannot find any function in OwlCarousel2 to reinitialise/change options of an existing Carousel.
Any ideas re 1) a fix or 2) a reinit function?

Or could you destroy within the responsive object?
responsive: {
  0 : { [[ all options here ]] },
  768 : { [[destroy here ]] }
}

As far as I know, this is fixed in beta 3 (I think via 2064682).
Please upgrade to the newest version and if this issue still exists, we can reopen it.

Yep, can confirm that bug is no longer present in latest release - thanks @greg5green!

This is broken again in beta 2.4
When resizing the window:
owl.carousel.js:622 Uncaught TypeError: Cannot read property '_onResize' of null

@vastra beta 3 is the most recent release that has this fixed

using beta3 for  _checkVisible error causes 'Uncaught TypeError: this.$backdrop.one(...).emulateTransitionEnd is not a function' in bootstrap js

+1

@swannknani - do you mean this bug has resurfaced? The last answer from @greg5green was that it was fixed.

Should this release have the fix? https://github.com/OwlCarousel2/OwlCarousel2/releases/tag/2.0.0-beta.3
I have used this version and although it fixes the resize issue, now my carousel is blank?

Well, I'm sad to write this, but I'm using the latest version (2.0.0-beta.2.4) and this error still occurs..

I switched to slick.js, I've been writing more code to try and fix
owlcarousel than I would've writing my own plug-in. I would recommend
trying slick.js as it hasn't failed me yet, using 5 different
configurations on the same site (ecommerce, clients just love those
carousels)
On Nov 29, 2016 11:03 AM, "Simona"<EMAIL_ADDRESS>wrote:

Well, I'm sad to write this, but I'm using the latest version
(2.0.0-beta.2.4) and this error still occurs..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OwlCarousel2/OwlCarousel2/issues/485#issuecomment-263514168,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEzkS7JSOyiX_O9f6SlRgHijEGXE0wSpks5rC-pxgaJpZM4Cffd5
.


gensio: 2.1.7 -> 2.2.1, ser2net: 4.2.1 -> 4.3.0

Motivation for this change
Version bumps, organize imports, add passthru.updateScript.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108808 run on x86_64-linux 1

2 packages built:

gensio
ser2net

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108808 run on x86_64-linux 1

2 packages built:

gensio
ser2net


Measuring beam width and thickness

Hello, we are using clarius scanner L7 for a research project and part of the project requires that the beam width and thickness be known - are you able to help with this?

hi there, sorry, we have not measured beam width or thickness on our devices. One can do so with a hydrophone, water bath, and specialized software, from a company like Onda

Is it possible to know the aperture of the ultrasound above?


Give better error message when importing incorrect composeinfo

It can easily happen that the release version is bumped but not its
integrated layered products. The import fails in such case. Now there is
a clear error message explaining what the problem is.
JIRA: PDC-1033

Looks good to me.


[SP] New API getInternalCameraIntrinsics

@huningxin @jondong Please help to review. Thanks!

@DonnaWuDongxia please verify the patch to keep the bot green :)

@jondong @huningxin updated! Thanks!

@DonnaWuDongxia some nit comments.

@jondong updated, thanks!

LGTM. Thanks. @huningxin do you need to put an eye on this? :)

Leave some comments. Please take a look. Thanks!

@huningxin updated, thanks!

LGTM. Merging. Thanks for the PR!


Build Fail: ? couldn't convert the error to rusqlite::error::Error

My build fails when using rusqlite with 'csv'.
Using the examples from the csv crate and the rusqlite crate together in a test project I get the following build fail on Rust 1.39.0 on Linux.
error[E0277]: `?` couldn't convert the error to `rusqlite::error::Error`
  --> src/main.rs:63:28
   |
63 |         let record = result?;
   |                            ^ the trait `std::convert::From<csv::error::Error>` is not implemented for `rusqlite::error::Error`
   |
   = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
   = help: the following implementations were found:
             <rusqlite::error::Error as std::convert::From<std::ffi::NulError>>
             <rusqlite::error::Error as std::convert::From<std::str::Utf8Error>>
   = note: required by `std::convert::From::from`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
error: could not compile `rusqlite_test`.

Cargo.toml:
[package]
name = "rusqlite_test"
version = "0.1.0"
authors = [""]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
rusqlite = "0.20.0"
time = "0.1.42"
csv = "1.1"

main.rs
use rusqlite::types::ToSql;
use rusqlite::{Connection, Result, NO_PARAMS};
use time::Timespec;

use std::error::Error;
use std::io;
use std::process;

#[derive(Debug)]
struct Person {
    id: i32,
    name: String,
    time_created: Timespec,
    data: Option<Vec<u8>>,
}

fn test_db() -> Result<()> {
    let conn = Connection::open_in_memory()?;

    conn.execute(
        "CREATE TABLE person (
                  id              INTEGER PRIMARY KEY,
                  name            TEXT NOT NULL,
                  time_created    TEXT NOT NULL,
                  data            BLOB
                  )",
        NO_PARAMS,
    )?;
    let me = Person {
        id: 0,
        name: "Steven".to_string(),
        time_created: time::get_time(),
        data: None,
    };
    conn.execute(
        "INSERT INTO person (name, time_created, data)
                  VALUES (?1, ?2, ?3)",
        &[&me.name as &ToSql, &me.time_created, &me.data],
    )?;

    let mut stmt = conn.prepare("SELECT id, name, time_created, data FROM person")?;
    let person_iter = stmt.query_map(NO_PARAMS, |row| {
        Ok(Person {
            id: row.get(0)?,
            name: row.get(1)?,
            time_created: row.get(2)?,
            data: row.get(3)?,
        })
    })?;

    for person in person_iter {
        println!("Found person {:?}", person.unwrap());
    }
    Ok(())
}

fn example() -> Result<()> {
    // Build the CSV reader and iterate over each record.
    let mut rdr = csv::Reader::from_reader(io::stdin());
    for result in rdr.records() {
        // The iterator yields Result<StringRecord, Error>, so we check the
        // error here.
        let record = result?;
        println!("{:?}", record);
    }
    Ok(())
}

fn main() {
    test_db().unwrap();

    if let Err(err) = example() {
        println!("error running example: {}", err);
        process::exit(1);
    }
}

I guess you want to activate the csvtab feature:
rusqlite = {version = "0.20.0", features = ["csvtab"]}
And activate this code:
https://github.com/jgallagher/rusqlite/blob/bb3db3f877a3e8a5785d9ea5e4ae4cca0ffe46d7/src/vtab/csvtab.rs#L339

The Cargo.toml change fixed it.
Thanks.


Remove 'timezone' from customer-account-ui-extensions and export I18nTranslate

Background

Remove timezone from packages/customer-account-ui-extensions/src/extension-points/standard-api.ts, as we currently do not have support for timezone within customer-accounts-web (I mistakenly added this last week)
Properly export I18nTranslate in customer-account-ui-extensions so the interface can be imported by consumers of this library.

🎩
There is not much to Tophat here.
Checklist

[x] I have :tophat:'d these changes
[x] I have updated relevant documentation (WIP)

Do we want to add those types here too: https://github.com/Shopify/ui-extensions/blob/main/packages/customer-account-ui-extensions-react/src/index.ts#L2
That will allow consumers of customer-account-ui-extensions-react to use them as well


Blazor runtime error. Unhandled exception disposing circuit host: Collection was modified; enumeration operation may not execute

Server-side blazor with .net core 3 preview 5. Release build. Repeated occurrence of the following exception thrown:
Unhandled exception disposing circuit host:
System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at bool System.Collections.Generic.Dictionary<TKey, TValue>+ValueCollection+Enumerator.MoveNext()
   at void Microsoft.AspNetCore.Components.Rendering.Renderer.Dispose(bool disposing)
   at void Microsoft.AspNetCore.Components.Browser.Rendering.RemoteRenderer.Dispose(bool disposing)
   at void Microsoft.AspNetCore.Components.Rendering.Renderer.Dispose()
   at async ValueTask Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost.DisposeAsync()+(?) => { }
   at void Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext+<>c__DisplayClass9_0+<<InvokeAsync>b__0>d.MoveNext()
   at async ValueTask Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost.DisposeAsync()
   at async Task Microsoft.AspNetCore.Components.Server.Circuits.CircuitRegistry.DisposeCircuitHost(CircuitHost circuitHost)

This seems to happen at random intervals during runtime. I can't identify a single set of tasks to reproduce...

Thanks for contacting us, @aford22.
Please provide us with a repro project, so we can investigate this.

I have faced with the next exception, which was thrown by a parallel access to an observable collection from a render thread and an another thread (async task). Invoking the concrete part (which was updating this collection) of the async task in the render thread helped to resolve the issue. Dont sure about connection between these issues, but it has the same behaviour(it happens very rarely).
But my issue doesn't stop render process, server just throws this exception and causes big memory leak. I guess it is an absolutely wrong behaviour.
.NET Core 3.0 Preview 5 Blazor Server-Side
warn: Microsoft.AspNetCore.Components.Browser.Rendering.RemoteRenderer[100]       Unhandled exception rendering component: Collection was modified; enumeration operation may not execute. System.InvalidOperationException: Collection was modified; enumeration operation may not execute.    at System.Collections.Generic.List1.Enumerator.MoveNextRare()
at Akmetron.ComponentLibrary.Blazor.Visual.GridView1.BuildRenderTree(RenderTreeBuilder builder) in C:\Users\rns\source\repos\Experimental\PriceSurfer\Akmetron.ComponentLibrary.Blazor\Visual\GridView.razor:line 29    at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__5_0(RenderTreeBuilder builder)    at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)    at Microsoft.AspNetCore.Components.Rendering.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)    at Microsoft.AspNetCore.Components.Rendering.Renderer.ProcessRenderQueue() warn: Microsoft.AspNetCore.Components.Server.ComponentHub[0]       Unhandled Server-Side exception System.InvalidOperationException: Collection was modified; enumeration operation may not execute.    at System.Collections.Generic.List1.Enumerator.MoveNextRare()
at Akmetron.ComponentLibrary.Blazor.Visual.GridView1.BuildRenderTree(RenderTreeBuilder builder) in C:\Users\rns\source\repos\Experimental\PriceSurfer\Akmetron.ComponentLibrary.Blazor\Visual\GridView.razor:line 29    at Microsoft.AspNetCore.Components.ComponentBase.<.ctor>b__5_0(RenderTreeBuilder builder)    at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)    at Microsoft.AspNetCore.Components.Rendering.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)    at Microsoft.AspNetCore.Components.Rendering.Renderer.ProcessRenderQueue()

@aford22 I tried a couple of things and I am unable to reproduce the stack trace that you produced. Dispose happens inside of the sync context, I am unable to find a code path where the state is modified in a concurrent way that would reproduce this problem.
@defend your stack trace looks like an issue with the 3rd party package. I'd recommend following up with them.


Adjust bridge for use with AMD

This makes it easy to load the built-in bridge as an AMD module when loading QUnit through AMD.
I can add some documentation for this if this looks good. I've tested this against a local branch of jQuery UI which has been modified to load QUnit and all tests through AMD. After loading QUnit and the bridge via AMD, I'm using the following code to apply the bridge (let me know if you'd like more context):
if ( /PhantomJS/.test( navigator.userAgent ) ) {
	bridge();
}

I can add a test as well, but I'm not sure if you want an actual AMD loader in the dev dependencies. Adding a test will also require a new release of QUnit (plus https://github.com/jquery/qunit/pull/791). Getting proper AMD tests in jQuery UI has opened quite the rabbit hole ;-)

Good to use the w=1 to catch the significant diffs here.

Looks good, simple enough.


Generate JWT while working with auth API when non is configured

Working with auth api service, if no token is configure generate one. we assume that the service require authentication and in the case we configure a shared secret between the two this token can be used.
Upgrade jwt package to v4. Remove the use of deprecated API
Logging error when auth api fail to perform operations

There's some deprecated code issues the CI raised, other than that loved it! just one non-blocker comment!

I'll reverse some of the changes so there is no change in JWT compatibility with current tokens.


[Upgrade policy for attributes packages] Version upgrade policy & Docker Engine upgrade

Is your feature request related to a problem? Please describe.
In order to apply the Go Modules based build system, our current Docker Engine (v17.xx.xx) is too old to be compatible with other packages. In addition to that, this version (v17.xx.xx) has some issue from its dedicate community to Archive since it is too old (https://github.com/docker/go-docker/issues/21). Meanwhile, it is a bit troublesome to adopt the latest version of Docker Engine, because it is not yet touching the maturity level.

This issue is also linked to #206

Describe the solution you'd like
Update the current Docker Engine to at least v19.xx.xx and establish the official upgrade policy (annual basis in the regular release) about Docker Engine and other relying attributes packages from other open source projects.
Suggestion: LET US discuss this issue in the upcoming TSC online meeting in January 2021!!!

This project is related to other open source projects such as docker, edgexfoundry at the moment.
It would be nice if we have an annual version update period for the upstream projects.

This project is related to other open source projects such as docker, edgexfoundry at the moment.
It would be nice if we have an annual version update period for the upstream projects.

@t25kim Thank you for supporting this idea! Plus, we should publish a document from GitHub and/or the dedicated Wiki aout that dependency metrics in terms of correlated open source projects (libraries) and their referencing version as well. If we get enough consent, I will draft that as well.

I completely agree! Thank you @t25kim! The only thing I would like is that we first fix bugs in testing packages within the project and add automated testing.

I completely agree! Thank you @t25kim! The only thing I would like is that we first fix bugs in testing packages within the project and add automated testing.

It is resolved after the PR merger of #210, so closed. Thank you all.


Log Level DEBUG differences

When a nodeserver starts up in Debug log_level I do not see these messages, but if I change to Info, then back to Debug I see them?
2021-08-21 16:18:10,380 Thread-65  udi_interface.node DEBUG    node:setDriver: No change in GV1's value

Is there some specific steps to reproduce this?
My attempts so far have all resulted in the debug messages in the node class getting output to the log as expected.  Maybe a change in a recent version fixed this?

I think it's working now but will verify again


Remove ofPorts from lastRealized.podOFPorts after deleting an OF rule

@jianjuns out-of-curiosity, was this causing any user-facing issue beyond leaking memory?

@jianjuns out-of-curiosity, was this causing any user-facing issue beyond leaking memory?

Nothing. I just found it when making other changes.

/test-all


[Question] Does this help make it easier to build offline app and also with syncing with a centralized database?

I read the blogpost https://jlongster.com/future-sql-web and i suppose absurd makes it way faster to read and write to IndexedDB for offline web apps.
But I guess, syncing with centralized database like a postgres, is out of scope for this.
AM I right?

That is out of scope for this, yes. It's up to you to still figure out how to send changes to some kind of service that helps sync. In the future, if someone proposes a need to expose certain methods to help with that, I'd be happy to work with them.
This just persists it locally; I recommend something like CRDTs to actually communicate changes in a way that can be synced.


Allow fixture to return multiple compose files

As described in https://docs.docker.com/compose/extends/, docker compose
can be passed multiple compose files that are then merged.  This change
allows the docker_compose_file fixture to make use of this by
returning e.g. a list or a tuple.

Coverage remained the same at 100.0% when pulling 31eee04513fa7bf721116dc9dde9193f00e1a791 on gdetrez:multiple-compose-files into 643211eb2c38ebafcb45b65223771467b7b359d5 on AndreLouisCaron:master.

Coverage remained the same at 100.0% when pulling e898132429860780de38e7e32b5d4c8ff1ed39d8 on gdetrez:multiple-compose-files into 643211eb2c38ebafcb45b65223771467b7b359d5 on AndreLouisCaron:master.

Coverage remained the same at 100.0% when pulling e898132429860780de38e7e32b5d4c8ff1ed39d8 on gdetrez:multiple-compose-files into 643211eb2c38ebafcb45b65223771467b7b359d5 on AndreLouisCaron:master.

Nice!  Thanks for contributing this!

Just released this on PyPI: https://pypi.org/project/pytest-docker/0.6.0/