pod install error after including audioplayer or audioplayers

I'm using the default demo app and adding one package at a time to see which one encounter the pod install issue.  I've narrowed it down to audioplayer or audioplayers.  It doesn't matter which one but both gives the following issue.
flutter run
Launching lib/main.dart on iPhone X in debug mode...
Running pod install...                                              3.4s
CocoaPods' output:
↳
Preparing
Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Fetching external sources
-> Fetching podspec for `Flutter` from `Flutter`
-> Fetching podspec for `audioplayer` from `.symlinks/plugins/audioplayer/ios`
-> Fetching podspec for `firebase_auth` from `.symlinks/plugins/firebase_auth/ios`
firebase_auth: Using Firebase SDK version '6.33.0' defined in 'firebase_core'
-> Fetching podspec for `firebase_core` from `.symlinks/plugins/firebase_core/ios`
firebase_core: Using Firebase SDK version '6.33.0' defined in 'firebase_core'

Resolving dependencies of `Podfile`
  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_0_3_5.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/3/5/Firebase/7.3.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/3/5/Firebase/6.33.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/3/5/Firebase/6.33.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_8_b_d.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/7.3.0/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/3/5/Firebase/6.33.0/Firebase.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_6_3_6.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/6/3/6/FirebaseAuth/7.3.0/FirebaseAuth.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.3/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_0_8_4.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/7.1.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: all_pods_versions_8_3_c.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/3/c/FirebaseCoreDiagnostics/7.3.0/FirebaseCoreDiagnostics.podspec.json exists! Returning local because checking is only
  perfomed in repo update
  CDN: trunk Relative path: Specs/6/3/6/FirebaseAuth/6.9.2/FirebaseAuth.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.0/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.1/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: all_pods_versions_c_e_3.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.5.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.1/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.2/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.3/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.4/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.5/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.6/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.7/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.8/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.9/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.10/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.11/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.12/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.13/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.14/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.1.15/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.2.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.2.1/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.2.2/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.3.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.3.1/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.4.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/c/e/3/GTMSessionFetcher/1.5.0/GTMSessionFetcher.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.4/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.3/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.2/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.1/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/b/d/FirebaseCore/6.10.0/FirebaseCore.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/8/3/c/FirebaseCoreDiagnostics/1.7.0/FirebaseCoreDiagnostics.podspec.json exists! Returning local because checking is only
  perfomed in repo update
  CDN: trunk Relative path: Specs/8/3/c/FirebaseCoreDiagnostics/1.6.0/FirebaseCoreDiagnostics.podspec.json exists! Returning local because checking is only
  perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_0_6_a.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/6/a/GoogleDataTransport/8.1.0/GoogleDataTransport.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: all_pods_versions_6_1_e.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/6/1/e/nanopb/2.30907.0/nanopb.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/6/1/e/nanopb/1.30906.0/nanopb.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/6/1/e/nanopb/1.30906.0/nanopb.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/6/1/e/nanopb/1.30906.0/nanopb.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: all_pods_versions_0_b_5.txt exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.12/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/8/4/GoogleUtilities/6.7.2/GoogleUtilities.podspec.json exists! Returning local because checking is only perfomed in repo
  update
  CDN: trunk Relative path: Specs/0/6/a/GoogleDataTransport/7.5.1/GoogleDataTransport.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/0/6/a/GoogleDataTransport/7.5.0/GoogleDataTransport.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/0/6/a/GoogleDataTransport/7.4.0/GoogleDataTransport.podspec.json exists! Returning local because checking is only perfomed in
  repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.12/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.11/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.10/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.9/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.8/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.7/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.6/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.5/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.4/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.3/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.2/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2.1/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update
  CDN: trunk Relative path: Specs/0/b/5/PromisesObjC/1.2/PromisesObjC.podspec.json exists! Returning local because checking is only perfomed in repo update

Comparing resolved specification to the sandbox manifest
  A Firebase
  A FirebaseAuth
  A FirebaseCore
  A FirebaseCoreDiagnostics
  A Flutter
  A GTMSessionFetcher
  A GoogleDataTransport
  A GoogleUtilities
  A PromisesObjC
  A audioplayer
  A firebase_auth
  A firebase_core
  A nanopb

Downloading dependencies

-> Installing Firebase (6.33.0)
  > Copying Firebase from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/Firebase/6.33.0-8db6f` to `Pods/Firebase`

-> Installing FirebaseAuth (6.9.2)
  > Copying FirebaseAuth from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/FirebaseAuth/6.9.2-c92d4` to `Pods/FirebaseAuth`

-> Installing FirebaseCore (6.10.3)
  > Copying FirebaseCore from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/FirebaseCore/6.10.3-d889d` to `Pods/FirebaseCore`

-> Installing FirebaseCoreDiagnostics (1.7.0)
  > Copying FirebaseCoreDiagnostics from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/FirebaseCoreDiagnostics/1.7.0-770ac` to
  `Pods/FirebaseCoreDiagnostics`

-> Installing Flutter (1.0.0)

-> Installing GTMSessionFetcher (1.5.0)
  > Copying GTMSessionFetcher from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/GTMSessionFetcher/1.5.0-b3503` to `Pods/GTMSessionFetcher`

-> Installing GoogleDataTransport (7.5.1)
  > Copying GoogleDataTransport from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/GoogleDataTransport/7.5.1-f56af` to `Pods/GoogleDataTransport`

-> Installing GoogleUtilities (6.7.2)
  > Copying GoogleUtilities from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/GoogleUtilities/6.7.2-7f2f5` to `Pods/GoogleUtilities`

-> Installing PromisesObjC (1.2.12)
  > Copying PromisesObjC from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/PromisesObjC/1.2.12-3113f` to `Pods/PromisesObjC`

-> Installing audioplayer (0.0.1)

-> Installing firebase_auth (0.18.4-1)

-> Installing firebase_core (0.5.3)

-> Installing nanopb (1.30906.0)
  > Copying nanopb from `/Users/annief/Library/Caches/CocoaPods/Pods/Release/nanopb/1.30906.0-59317` to `Pods/nanopb`
  - Running pre install hooks

Generating Pods project
  - Creating Pods project
  - Installing files into Pods project
    - Adding source files
    - Adding frameworks
    - Adding libraries
    - Adding resources
    - Adding development pod helper files
    - Linking headers
  - Installing Pod Targets
    - Installing target `Firebase` iOS 8.0
    - Installing target `FirebaseAuth` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/FirebaseAuth/FirebaseAuth.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/FirebaseAuth/FirebaseAuth-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/FirebaseAuth/FirebaseAuth-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/FirebaseAuth/FirebaseAuth-dummy.m`
    - Installing target `FirebaseCore` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/FirebaseCore/FirebaseCore.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/FirebaseCore/FirebaseCore-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/FirebaseCore/FirebaseCore-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/FirebaseCore/FirebaseCore-dummy.m`
    - Installing target `FirebaseCoreDiagnostics` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/FirebaseCoreDiagnostics/FirebaseCoreDiagnostics.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/FirebaseCoreDiagnostics/FirebaseCoreDiagnostics-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/FirebaseCoreDiagnostics/FirebaseCoreDiagnostics-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/FirebaseCoreDiagnostics/FirebaseCoreDiagnostics-dummy.m`
    - Installing target `Flutter` iOS 8.0
    - Installing target `GTMSessionFetcher` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/GTMSessionFetcher/GTMSessionFetcher-dummy.m`
    - Installing target `GoogleDataTransport` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/GoogleDataTransport/GoogleDataTransport.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/GoogleDataTransport/GoogleDataTransport-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/GoogleDataTransport/GoogleDataTransport-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/GoogleDataTransport/GoogleDataTransport-dummy.m`
    - Installing target `GoogleUtilities` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/GoogleUtilities/GoogleUtilities.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/GoogleUtilities/GoogleUtilities-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/GoogleUtilities/GoogleUtilities-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/GoogleUtilities/GoogleUtilities-dummy.m`
    - Installing target `PromisesObjC` iOS 9.0
      - Generating module map file at `Pods/Target Support Files/PromisesObjC/PromisesObjC.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/PromisesObjC/PromisesObjC-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/PromisesObjC/PromisesObjC-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/PromisesObjC/PromisesObjC-dummy.m`
    - Installing target `audioplayer` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/audioplayer/audioplayer.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/audioplayer/audioplayer-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/audioplayer/audioplayer-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/audioplayer/audioplayer-dummy.m`
    - Installing target `firebase_auth` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/firebase_auth/firebase_auth.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/firebase_auth/firebase_auth-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/firebase_auth/firebase_auth-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/firebase_auth/firebase_auth-dummy.m`
    - Installing target `firebase_core` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/firebase_core/firebase_core.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/firebase_core/firebase_core-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/firebase_core/firebase_core-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/firebase_core/firebase_core-dummy.m`
    - Installing target `nanopb` iOS 8.0
      - Generating module map file at `Pods/Target Support Files/nanopb/nanopb.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/nanopb/nanopb-umbrella.h`
      - Generating Info.plist file at `Pods/Target Support Files/nanopb/nanopb-Info.plist`
      - Generating dummy source at `Pods/Target Support Files/nanopb/nanopb-dummy.m`
  - Installing Aggregate Targets
    - Installing target `Pods-Runner` iOS 11.0
      - Generating Info.plist file at `Pods/Target Support Files/Pods-Runner/Pods-Runner-Info.plist`
      - Generating module map file at `Pods/Target Support Files/Pods-Runner/Pods-Runner.modulemap`
      - Generating umbrella header at `Pods/Target Support Files/Pods-Runner/Pods-Runner-umbrella.h`
      - Generating dummy source at `Pods/Target Support Files/Pods-Runner/Pods-Runner-dummy.m`
  - Generating deterministic UUIDs
  - Stabilizing target UUIDs
  - Running post install hooks
[!] An error occurred while processing the post-install hook of the Podfile.

undefined method `each_child' for #<Dir:0x00007fcd2edee718>
Did you mean?  each_slice

/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:54:in `block in flutter_additional_ios_build_settings'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `each'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `flutter_additional_ios_build_settings'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:39:in `block (3 levels) in from_ruby'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `each'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `block (2 levels) in from_ruby'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:179:in `post_install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:897:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:885:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:884:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:329:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:328:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:307:in `create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:299:in `generate_pods_project'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:178:in `integrate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:166:in `install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:22:in `load'
/usr/local/bin/pod:22:in `<main>'

/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:899:in `rescue in run_podfile_post_install_hook'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:896:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:885:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:884:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:329:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:328:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:307:in `create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:299:in `generate_pods_project'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:178:in `integrate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:166:in `install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:22:in `load'
/usr/local/bin/pod:22:in `<main>'

Error running pod install
Error launching application on iPhone X.
=========================================================
flutter doctor -v
[✓] Flutter (Channel master, 1.26.0-2.0.pre.250, on Mac OS X 10.14.6 18G7016 darwin-x64, locale en-US)
• Flutter version 1.26.0-2.0.pre.250 at /Users/annief/Developer/flutter
• Framework revision 1bd89a9617 (3 days ago), 2021-01-08 03:58:12 +0100
• Engine revision 2e5833b7c5
• Dart version 2.12.0 (build 2.12.0-179.0.dev)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/annief/Library/Android/sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.3.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.3.1, Build version 11C505
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] IntelliJ IDEA Community Edition (version 2017.2.3)
• IntelliJ at /Applications/IntelliJ IDEA CE.app
• Flutter plugin version 21.2.2
• Dart plugin version 172.3968.27
[✓] VS Code (version 1.52.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.18.0
[✓] Connected device (2 available)
• iPhone X (mobile) • 91B3177C-815A-4F3F-B6B3-4D80E32520D1 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-11-0 (simulator)
• Chrome (web)      • chrome                               • web-javascript • Google Chrome 87.0.4280.141
• No issues found!
pubspec.yaml
name: xylophone
description: A Xylophone Flutter application.
publish_to: 'none' # Remove this line if you wish to publish to pub.dev
version: 1.0.0+1
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
cupertino_icons: ^1.0.0
firebase: ^8.0.0
firebase_auth: ^0.18.4+1
font_awesome_flutter: ^8.11.0
flutter_spinkit: ^4.1.2+1
http: ^0.12.2
audioplayer: ^0.8.1
dev_dependencies:
flutter_test:
sdk: flutter
flutter:
uses-material-design: true
=========================================================
I'm running Mojave (10.14.6) and simulating on iOS 11.0.1
I've tried many suggestions here and on stackoverflow with cleaning cache, re-downloading dependencies and restarting Android Studio.
I really appreciate any and all help.  Thanks in advance.

@acflippo
Tried audioplayer and audioplayers using a sample app on latest master and was able to compile and build the app without any issues.

flutter doctor -v

[✓] Flutter (Channel master, 1.26.0-2.0.pre.275, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.26.0-2.0.pre.275 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision d9044a8a61 (2 days ago), 2021-01-09 04:04:04 -0500
    • Engine revision caf6a8191f
    • Dart version 2.12.0 (build 2.12.0-204.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • sdk gphone x86 64 arm64 (mobile)    • emulator-5554
      • android-x64    • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    • macOS (desktop)                     • macos
      • darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)                        • chrome
      • web-javascript • Google Chrome 87.0.4280.141

! Doctor found issues in 1 category.

Can you provide your podfile ?  Also check out this SO solution and see if it works for you.

@acflippo
Tried audioplayer and audioplayers using a sample app on latest master and was able to compile and build the app without any issues.

flutter doctor -v

[✓] Flutter (Channel master, 1.26.0-2.0.pre.275, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-IN)
    • Flutter version 1.26.0-2.0.pre.275 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision d9044a8a61 (2 days ago), 2021-01-09 04:04:04 -0500
    • Engine revision caf6a8191f
    • Dart version 2.12.0 (build 2.12.0-204.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (4 available)
    • sdk gphone x86 64 arm64 (mobile)    • emulator-5554
      • android-x64    • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)
    • macOS (desktop)                     • macos
      • darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)                        • chrome
      • web-javascript • Google Chrome 87.0.4280.141

! Doctor found issues in 1 category.

Can you provide your podfile ?  Also check out this SO solution and see if it works for you.

Here's my Podfile:
Uncomment this line to define a global platform for your project
platform :ios, '11.0'
CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
project 'Runner', {
'Debug' => :debug,
'Profile' => :release,
'Release' => :release,
}
def flutter_root
generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), FILE)
unless File.exist?(generated_xcode_build_settings_path)
raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
end
File.foreach(generated_xcode_build_settings_path) do |line|
matches = line.match(/FLUTTER_ROOT=(.*)/)
return matches[1].strip if matches
end
raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end
require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)
flutter_ios_podfile_setup
target 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
end
end

Here's my Podfile:
Uncomment this line to define a global platform for your project
platform :ios, '11.0'
CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
project 'Runner', {
'Debug' => :debug,
'Profile' => :release,
'Release' => :release,
}
def flutter_root
generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), FILE)
unless File.exist?(generated_xcode_build_settings_path)
raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
end
File.foreach(generated_xcode_build_settings_path) do |line|
matches = line.match(/FLUTTER_ROOT=(.*)/)
return matches[1].strip if matches
end
raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end
require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)
flutter_ios_podfile_setup
target 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
end
post_install do |installer|
installer.pods_project.targets.each do |target|
flutter_additional_ios_build_settings(target)
end
end

Here's the output for trying Stackoverflow: error running pod install on mac
pod install --repo-update
Updating local specs repositories
Analyzing dependencies
firebase_auth: Using Firebase SDK version '6.33.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '6.33.0' defined in 'firebase_core'
Downloading dependencies
Installing Firebase (6.33.0)
Installing FirebaseAuth (6.9.2)
Installing FirebaseCore (6.10.3)
Installing FirebaseCoreDiagnostics (1.7.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (1.5.0)
Installing GoogleDataTransport (7.5.1)
Installing GoogleUtilities (6.7.2)
Installing PromisesObjC (1.2.12)
Installing audioplayer (0.0.1)
Installing firebase_auth (0.18.4-1)
Installing firebase_core (0.5.3)
Installing nanopb (1.30906.0)
Generating Pods project
[!] An error occurred while processing the post-install hook of the Podfile.

undefined method `each_child' for #<Dir:0x00007fdaba8d8938>
Did you mean?  each_slice

/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:54:in `block in flutter_additional_ios_build_settings'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `each'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `flutter_additional_ios_build_settings'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:39:in `block (3 levels) in from_ruby'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `each'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `block (2 levels) in from_ruby'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:179:in `post_install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:897:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:885:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:884:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:329:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:328:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:307:in `create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:299:in `generate_pods_project'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:178:in `integrate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:166:in `install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:22:in `load'
/usr/local/bin/pod:22:in `<main>'

Here's the output for trying Stackoverflow: error running pod install on mac
pod install --repo-update
Updating local specs repositories
Analyzing dependencies
firebase_auth: Using Firebase SDK version '6.33.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '6.33.0' defined in 'firebase_core'
Downloading dependencies
Installing Firebase (6.33.0)
Installing FirebaseAuth (6.9.2)
Installing FirebaseCore (6.10.3)
Installing FirebaseCoreDiagnostics (1.7.0)
Installing Flutter (1.0.0)
Installing GTMSessionFetcher (1.5.0)
Installing GoogleDataTransport (7.5.1)
Installing GoogleUtilities (6.7.2)
Installing PromisesObjC (1.2.12)
Installing audioplayer (0.0.1)
Installing firebase_auth (0.18.4-1)
Installing firebase_core (0.5.3)
Installing nanopb (1.30906.0)
Generating Pods project
[!] An error occurred while processing the post-install hook of the Podfile.

undefined method `each_child' for #<Dir:0x00007fdaba8d8938>
Did you mean?  each_slice

/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:54:in `block in flutter_additional_ios_build_settings'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `each'
/Users/annief/Developer/flutter/packages/flutter_tools/bin/podhelper.rb:51:in `flutter_additional_ios_build_settings'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:39:in `block (3 levels) in from_ruby'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `each'
/Users/annief/AndroidStudioProjects/xylophone/ios/Podfile:38:in `block (2 levels) in from_ruby'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-core-1.10.1/lib/cocoapods-core/podfile.rb:179:in `post_install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:897:in `run_podfile_post_install_hook'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:885:in `block in run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:884:in `run_podfile_post_install_hooks'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:329:in `block (2 levels) in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pods_project_writer.rb:61:in `write!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:328:in `block in create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:307:in `create_and_save_projects'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:299:in `generate_pods_project'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:178:in `integrate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:166:in `install!'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:22:in `load'
/usr/local/bin/pod:22:in `<main>'

@acflippo
The error says:
undefined method each_child' for #<Dir:0x00007fdaba8d8938>
Did you mean?  each_slice
It could be happening due to the Ruby version you are using 2.3.0. Try to upgrade to latest Ruby version and check again if it resolves your issue.
Also see this SO answer.

@acflippo
The error says:
undefined method each_child' for #<Dir:0x00007fdaba8d8938>
Did you mean?  each_slice
It could be happening due to the Ruby version you are using 2.3.0. Try to upgrade to latest Ruby version and check again if it resolves your issue.
Also see this SO answer.

Updating Ruby and re-installing cocoapods removed that error.  So that worked but now I'm facing another issue.  Adding new dependencies in pubspec.yaml, saving the file and clicking "Pub get" does not download the package.  It looks like this is an existing bug?  Will research some more. Thanks.

Updating Ruby and re-installing cocoapods removed that error.  So that worked but now I'm facing another issue.  Adding new dependencies in pubspec.yaml, saving the file and clicking "Pub get" does not download the package.  It looks like this is an existing bug?  Will research some more. Thanks.

This issue is fixed.  Thanks.

This issue is fixed.  Thanks.


Expose shoot infrastucture information for end users

What would you like to be added:
When a shoot is created, infrastructure (vpc, security grups and etc. ) is created by Gardener via Terraform. Though Gardener operators could find the output from infrastructures.extensions.gardener.cloud in seed cluster, we need to find a way to expose such information to customers.
Why is this needed:
Some users need infrastructure information to do some followup stuff in an automatic way.

Kind of similar to #1749

This information has already been available in the ShootState resource for the respective shoot.
I think this can be extended to mutating webhook in the provider-* extension which will inject the information in the shoot-core managedresource. At the end the shoot-info configmap (https://github.com/gardener/gardener/pull/1690) will contain the required info.
What do you think? This will be scenario targeting users without access to the Gardener API.
Or we can close this issue as it is resolved by ShootState?

I think the idea is that end-users can read it from the Gardener API, not (only) from the within the shoot cluster.

Sure. I was targeting users that do not have access to the Gardener API but only to the shoot API.

closed in favor of #3873


fix for #4

@Scrounger
As changes to this repository are currently NOT possible, adapter tractive-gps hase been moved into iobroker-community adapters area
https://github.com/iobroker-community-adapters/ioBroker.tractive-gps
Please create a PR containing your changes at this repo so that we can include it into a new release of this adapter.
Thanks in advance.
mcm1957


Remove "implicit declaration of function" warning

Recent versions of gcc will complain about all the callbacks defined in
Go and called from C are undefined functions.
We cannot use the generated "_cgo_export.h" file because it is not
present yet. Introducing intermediary C functions that will call the Go
function from a separate .c file importing "_cgo_export.h" seems
overkill. Manual declaration of function prototypes is bothersome (and
would need to be checked). Use of C preprocessor may help a bit but
won't help in correctness as only the content of "_cgo_export.h"
matters.
Therefore, it just seems easier to ignore those warnings.

This needs a rebase after the last couple PRs that were merged.

Rebased.


Allow import of existing markdown files

While simply copying existing markdown files to the wiki directory allows access to them, they are not indexed for search. Did i miss something ? Otherwise it would be a nice feature to be able to build a search index from all files on demand...

+1 for importing and including imported pages in the search index.
Ideally, reindexing would be triggered by file changes so search results are always fresh. Although, depending on the number of pages this might not be feasible.

Thanks for the suggestion, @lmichelbacher.
Listening for file changes is a large chunk of work (which I know because I've done it before on my other project, handroll). It involves adding another dependency that knows how to watch for files. I would probably use watchdog if I did that.
Watching for files is kind of a corner case if there are options to reindex. MarkWiki will already update the search index for individual pages if updates through the web interface. Since the web interface is the intended way to update pages, I'm wondering what the use cases are for listening for files.
Do you mind opening another issue on this subject so we could discuss why file watching would benefit you over the reindex option? I'd like to keep this particular issue focused on reindexing all the content.

I'd love a setup where markwiki is the main web interface to files that live in the cloud (e.g. Dropbox) and is aware of changes I make to these files via other mechanisms.
I understand this use case goes beyond the original one. I'm happy to discuss further but it would mean opening more issues ;).
I'm convinced however, that a Markdown wiki backed by cloud storage could be a great project. I'm not aware of any solution that does this properly (I've been searching for a while). StackEdit is the closest thing I could find. It's really great in terms of editing functionality (maybe a good source for inspiration?) but it's not designed as a wiki and jumping around between files is cumbersome.


"registry:dt/dragula#2.1.2+20150806040003" is deprecated

I have the issue with the deprecated version of dragula.
When I am trying to execute " typings install", there is a warning message that
typings WARN deprecated 5/10/2016: "registry:dt/dragula#2.1.2+20150806040003" is deprecated (updated, replaced or removed)
registry:dt/dragula#2.1.2+20150806040003 is set as the globalDependencies in my typings.json file as below
{
"globalDependencies": {
"dragula": "registry:dt/dragula#2.1.2+20150806040003",
"es6-shim": "github:DefinitelyTyped/DefinitelyTyped/es6-shim/es6-shim.d.ts#6697d6f7dadbf5773cb40ecda35a76027e0783b2",
"jasmine": "github:DefinitelyTyped/DefinitelyTyped/jasmine/jasmine.d.ts#4b36b94d5910aa8a4d20bdcd5bd1f9ae6ad18d3c",
"jquery": "github:DefinitelyTyped/DefinitelyTyped/jquery/jquery.d.ts#470954c4f427e0805a2d633636a7c6aa7170def8"
}
}
I have tried to get the latest version using commane "typings info dt~dragula --versions" which gave me 2 options
2.1.2+20170109141406 2.1.2                        github:DefinitelyTyped/DefinitelyTyped/dragula/index.d.ts#d3ae5ced6d5876fa65999a62f1566ac9f6958889 2017-01-09T14:14:06.000Z
2.1.2+20170109071602 2.1.2                        github:DefinitelyTyped/DefinitelyTyped/dragula/index.d.ts#4d1c1d396e7d6ce3268e0fb5d9aacea654cbe4eb 2017-01-09T07:16:02.000Z
but when I am trying any of these versions it is giving error
typings ERR! message Attempted to compile "dragula" as a global module, but it looks like an external module. You'll need to remove the global option to continue.
Can anyone has idea about to update this deprecated module.

https://github.com/typings/typings/issues/738


Set default and validate control plane host port when generating CloudStack CAPI objects

Issue #, if available:
Set Default And Validate Control Plane Host Port when generate CAPI object#1280
Description of changes:
When creating a CloudStack cluster, the endpoint provided by the user should have a port specified. This is already done for the CLI, but not for clusters created through the API yet. However, it modifies the user input in the cluster.Spec to achieve this: This PR:

Validates and sets a default control plane host port when generating the CloudStack CAPI objects. This will allow clusters created through the API to utilize a default port for the control plane endpoint if not specified, bringing it up to parity with the CLI.
Removes the side effect of editing the user input in the cluster.Spec. The cluster.Spec represents data input by the user to create the cluster. It follow good practice to not permanently modify user input, and to instead transform it into other  non user input constructs.

Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/test all

/test all

/lgtm

/lgtm

/approve


add network to toaster

now it say

Connected to {walletProvider}

I think it would be useful to have it say

Connected to {walletProvider} on the {network} network

I actually won't do this (for now anyway), because it is not trivial to do this with regards to the async nature + decoupling of these peices of information. I might have a small refactor regarding this, and at that time it will be easier and more straight forward to achieve it.
(the consequenc eof the above statement is that the prior connected wallets network could be shown instead of the newly connected wallet. I go for stability and ease-of-implementation for now)


The rancher agent isn't running but the UI show the host as active

Hi,
I have activated the rancher agent on my server it works for a few time and then the hosts disappear in the UI. I didn't have the time to investigate so I just let it like that.
Yesterday I had to kill it the hard way (see https://github.com/rancherio/rancher/issues/1081) and now the host is back in the UI and displayed as active even if the agent is not running, and obviously the UI doesn't show the reality but an old snapshot.
Like I said in the other ticket I grab all the logs if you want me to look at something.

The bug is a duplicate of #701. We're targeting to fix this in our Beta release.
As for the comment about the hosts disappearing in the UI, I'm not really sure why that would occur. Are you running the agent on the same host as server? If so, you'll need to add -e CATTLE_AGENT_IP=<server_ip> to the command in order for the rancher agent to pick up the right IP.  https://github.com/rancherio/rancher/issues/872


Having custom Object.prototype method prevents form validation

I'm running into this issue that if I set a custom Object.prototype method, it stops form validation from updating:
<!DOCTYPE html>
<html lang="en">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
		<title>Test</title>
	</head>
	<body ng-app>
		<form name="testForm" novalidate>
			<!-- type in here and field and form should turn valid -->
			<input type="text" name="test" ng-model="test" required> Field Valid? {{testForm.test.$valid | json}}
		</form>
		Form valid? {{testForm.$valid | json}}

		<script src="http://ajax.googleapis.com/ajax/libs/angularjs/1.4.0/angular.min.js"></script>
		<script>
			// remove this line and validation works again
			Object.prototype.someThing = function() {}
		</script>
	</body>
</html>

Here is a plunk http://plnkr.co/edit/XauBqEKawyDyk21RFc1r?p=preview demonstrating the behaviour (the prototype method is set in script.js). The issue seems to have started in version 1.3.0-rc.1 so that is what I have used in the plunk.

The check that there are no errors in the errors object was not checking that any of the properties comes from the Object.prototype. #12075 should take care of this


Issue templates

Addresses #51.

I'm wondering whether should we include a Question issue template?


[PE-D][Tester D] changepassword command not working

example in changepassword command in userguide not working in the application. downloaded the most recent jar file v1.3.final

Edited:
It seems I need to capitalized the P, changePassword for the command to work. Maybe need to update the user guide to match the application command format.

Labels: severity.High type.FunctionalityBug
original: syamfarh/ped#8

Resolved by other developers


Food package update to term animal_group_size MIXS:0001129

Current term details
Term name - food animal group size
Term ID - MIXS:0001129
Structured comment name - animal_group_size
Definition - The number of food animals of the same species that are maintained together as a unit, i.e. a herd or flock.
Expected value - value
Value syntax - {integer}
Example - 80
Preferred unit -
Package(s) - food-animal and animal feed ; food-farm environment

Suggested update(s)
**Term name -  host group size
Term ID - MIXS:0001129
**Structured comment name - host_group_size
Definition - The number of food animals of the same species that are maintained together as a unit, i.e. a herd or flock.
Expected value - value
Value syntax - {integer}
Example - 80
Preferred unit -
Package(s) - food-animal and animal feed ; food-farm environment

Additional context
FDA and OHE alignment work suggested this change.

Keep the term as is.
No updates.

Just thought of two Darwin Core terms that can possibly be used in pair for this perhaps?

https://dwc.tdwg.org/terms/#dwc:organismQuantity
https://dwc.tdwg.org/terms/#dwc:organismQuantityType

Only change is to remove the word drug from definition.


JMM hashing speed is very low again

Hi
I updated <IP_ADDRESS> to <IP_ADDRESS> two days ago
It seems the new <IP_ADDRESS> has the slow hashing speed issue again. The hasher.dll is also double the size again compared to what the proper ones sizes were. Any reason why the old hasher.dll is packaged with the installer again?
Earlier issue about this: #187

This was mentioned on Discord, was discovered that the x86 and x64 debug versions of hasher.dll were included in the release.


netplay no sound?

Hi bro,
i play games offline and work good with sound music normal.
but netplay no have any sound.
how i can fix it.
many thanks
cheers!

It happens sometimes. Refreshing host page may help.
What OS and browser you are using?

Windows 10, Browser Edge

This issue is connected with https://github.com/EmulatorJS/EmulatorJS/issues/879
I will fix this after that issue will be resolved.

Nice bro, i have many ideas for your project, when you have time free if we speak


Introduce Announcements

An attempt to generalize the idea of st2 posting a message to stream consumer.
It is intended to be drop-in replacement for hubot.post_results that will allow us to switch to using streams in hubot without redesigning the whole pipeline top to bottom.
It is also intended to be used as a general way of sending notifications to the public as opposed to Notification mechanic for reacting on events within st2 internally. Currently internal Notifications becoming external Announcements by means of rules. Announcements could also be called directly as a part of workflow, same way hubot.post_message and slack.post_message work right now.

To recap my Slack feedback - I see the need for this functionality (dispatching a message which is then fanned out to all the consumers on the /stream endpoint), but I'm personally not a fan of action runner approach.
I think we should expose this as an API (e.g. POST to /v1/stream). If we go with the API approach we can still create a wrapper Python runner action which simply sends data to that endpoint so the end result is the same.

For API approach, I really wonder why do you think this is a good idea. I remember the times when some of st2 internal components used REST for communication and some other were starting to use MQ. You've guys actually spend a noticeable amount of effort to make sure we now have a single channel of communication between internal components. Why do you think is a good idea for one internal component (action runner in this case) to talk to another internal component (st2api where stream resides) by means of REST calls instead of MQ? We then would have to protect this publicly accessible endpoint from actors willing to impersonate action runner and send a message to our users and this would require us to acquire an API token for every action runner. Do we want to go that far?

I'm not talking about the internal communication method, but how should an external, user visible API look like.
In this case, I think API is better and fits this model better than the runner approach. And we can still have Python runner action so as mentioned above, end result will be the same.
It's true that REST API approach adds some overhead, but it presents a better API, imo.
As far as RBAC and permissions go - if we go with the API approach we could simply add a new permission type (send_stream_message or similar).
As far as token goes - we already generate a temporary auth token which is available for duration of action execution and is passed to every runner action. Right now this token belongs to a system user, but eventually, we will tie it to the user which triggered the action (and as such, inherit those user permissions).

@Kami I'm sorry, but I still fail to see how it better fits this model when action runner needs to call st2 api directly instead of routing the message through the proper channels (which we by the way already using for live updates and simply can't stop using). I would have made sense if we were expecting external services to post an announcement in st2 stream, but I don't see why we may want to do that outside the loop "webhook-rule enforcement-announcement".
We are probably having very different models in mind.

Some thoughts -

I think we all need to agree on external APIs. I see announcements as a consume only API and not an API that receives any POSTs at this point.
The announcement concept is still opaque from an external perspective i.e. what is announced, what is the structure of an announcement and how does one control what gets announced - we can iterate.
If you compare and contrast a notification and announcement I suspect we will see some confusion here simply on the basis of the terminology so likely we think through that part as well. e.g. what is the difference between an broadcast notification and announcement. Also, if we do collapse this the terms does it make sense to have such divergent implementations?
The good part is that this builds on notifications and it is a fairly clever use of a runner. It may not be a natural use of the runner but then everything is eventually code anyway.

Although my comments seem to highlight concerns in the design/no-design here I am actually +ve of the notion of announcements.

The announcement concept is still opaque from an external perspective i.e. what is announced, what is the structure of an announcement and how does one control what gets announced - we can iterate.

The way the runner is implemented right now, you can actually send any kind of data on the channel providing you're willing to handle it yourself the other end. Any action on top of this runner would start to make it opinionated one way or the other.
For example, core.announcement expect a single parameter message of type object and will send it to general route key by default so on the consumer end, there will be an event st2.announcement__general with content:
{
  payload: {
    message: {...}
  }
}

On the other hand, new hubot.post_message also expects message, but this time is a type of string. It also expects three more parameters and defines a route to be chatops. The resulting event would be st2.announcement__chatops with content:
{
  payload: {
    message: '...',
    user: '...',
    channel: ...
  }
}

If you compare and contrast a notification and announcement I suspect we will see some confusion here simply on the basis of the terminology so likely we think through that part as well. e.g. what is the difference between an broadcast notification and announcement. Also, if we do collapse this the terms does it make sense to have such divergent implementations?

The confusion is of course to be there as the terms are pretty close to each other, although I don't see how we can collapse the terms.
Notifications are internal mechanic to let one internal component know something had happened with the other component. Like right now we're letting st2notifier know the execution has finished so it can dispatch a new trigger.
Announcements is a way for st2 to inform external component on something that happened inside stackstorm that consumer didn't specifically asked for. The closest concept is push notifications.
Notifications may be converted into Announcements by way of rules. Not all of them should, though. Notification may inform the system that one of actionrunners is mysteriously failed, but system may recover without human intervention.


[FR] Ability to change loading color in [Button]

Is your feature request related to a problem? Please describe.
When I customized bacgkroundColor or color to dark, It's hard to see a [LoadingElement] since loading color is fixed with text.basic.
https://user-images.githubusercontent.com/58724686/224252349-067be954-7f2b-438e-a255-da0b8f42401d.mov
Describe the solution you'd like
I think providing a loading styles props would be great. And how about making the [LoadingElement] have the same color as the text color?

Closes via 9179168a9db11d4f8e7601baf383edf3a4d82ad8
Released in 0.2.0-rc.11. You can use loadingColor prop to change the color of the loading.


Additional waypoint suggestion: Intro to creating tests using popular test suites

Since developers should know how to test their own code, maybe it is a good idea to include at least an intro to testing?
This I found in Udacity: https://www.udacity.com/course/javascript-testing--ud549

+1

+1

:+1:

+1

This is coming, but we need to change the way we currently run test in order to run test on test.

:+1:

Closing in favor #5847. Please continue any discussion in that thread.


fix: tauri opening links in new windows

It should be opening the links in the native browser rather than new windows.

Will merge once the builds are successful


⚠ Bofrost.com has degraded performance

In ec25948, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 739 ms

Resolved: Bofrost.com performance has improved in 445e00c after 6 minutes.


Symbol Swapper (verion 0.16)  library not working in the Sketch 54.1

Hi,
I updated my Sketch to 54.1 version  and I have some trouble with plugin Symbol Swapper.
I can not swapp libraries, if I have  many libraries in my list  ( in the Sketch).
Can you help me, please?

Confirmed. Have the same issue.

@LenaAlyanova, @nikolayzaytsev, thank you for bringing this to my attention, sorry you are having issues with the plugin. I just published an update which might fix the issue, could you please download and try version 0.17?

Thank you, @sonburn ! It works on my side now.

Thank you, @sonburn ! It works on my side now.

Thank you, @sonburn !


Introduce new storage type: prefixed map

Context
Prefixed map is a new storage available in decl_storage.
it differ from map as it stores it keys at twox_256(prefix)++map_hasher(key) instead of map_hasher(prefix ++ key).
Thus it allows to remove all key of the map using sr-io::kill_prefix.
But the final goal is to make it also iterable using https://github.com/paritytech/substrate/issues/3883
In the end this should replace linked_map as iteration is more efficient (just there is no longer ordering). and also Maps as it allows to have more functionality
To discuss:

should we directly put this in a child trie instead of behind a prefix in top trie ?

I would prefer waiting for https://github.com/paritytech/substrate/issues/3648 before having child trie in decl_storage actually.

the value is stored at twox_256(prefix)++map_hasher(key):

the first part is using twox_256 for hashing the prefix because we have to be sure that no other value share the same prefix. in case we only use twox_128 then an attacker could try to craft a key which have blake2_256(key)[0..16] == twox_128(prefix). Thus inserting a wrong value into this map.
Introducing this map has the consequence to limit the size of our hashers. introducing a hasher with an output longer than 256 bit is no longer relevant as it can already collision with this map.
If this is an issue then it can be solve in two way:

waiting for child trie
allow to remove key with a given prefix and a given size only. thus we would call sr-io::kill_prefix_with_size(MAP_PREFIX, 32+size_of_map_hasher)

the second part is map_hasher(key). currently a hasher is mandatory though it seems it could be interesting to introduce a no_hasher variant (or hasher=identity). thus value would be stored at twox_256(prefix) ++ key.encode(). The only interest I see from this is that it would avoid some hasher call.

This looks like double_map with with first key of ()?
https://github.com/paritytech/substrate/blob/ec7c6cf1779b88e75137ef6f6f7bf67ecd0f75a5/srml/system/src/lib.rs#L416

It's not so great to have a long, insecure hash as the first key as it's not inconceivable that someone could craft a module which intentionally has storage keys that collided with another module. A better way of forming the first key could be to simply append a short twox hash (8 byte, perhaps) of the item name to either the module name or a twox hash of it. This more or less guarantees it being unrealistic to craft a storage item collision, at least making it super-obvious in the module name.

So finally we will do instead of a new storage type just an optional attribute on linked_map
MyLinkedMap prefixed(): linked_map u32 => u32

stored at twox(ModuleName)++twox(MyLinkedMap)++hasher(key).
This would implemente the same trait StorageLinkedMap (though with change of the generator to have this two prefixes), also in the metadata we need a new field for the additional prefix as well (or a complete new storage variant)
(Or otherwise we could also make use of blake2hasher if we can ensure this is done at compile time but I prefer the first way)
I'll work on this starting next week after my days off

sounds good.

As we want to remove LinkedMap in the future anyway. I would propose that you add the new prefixed() attribute to StorageMap.
If it is a prefixed StorageMap, we also implement Iterator or a custom trait to make it iterable like a LinkedMap.

how far off is this? i could do with it for a PR i'm working on...

in particular, i could do with iteration on a double_map - is that already prototyped?

for double_map you want to iterate over all values?
I can implement Iterator<Item=(Key1, Key2, Value)> similarly to the incoming prefixed map it seems.
But if you want to iterate on first keys only it seems it requires new function in sr-io.

superseeded by https://github.com/paritytech/substrate/pull/4185


How are bare repositories handled on the server

The following answer is based on https://github.com/rycus86/githooks/issues/159
@mjk-gh:
The first thing to note is that bare repositories are handled the exact same way as normal repos are handled.
That means the .githooks folder can be in these locations
That means your path <bareRepo>/hooks/.githooksshould be <bareRepo>/.githooks (or <normalRepo>/.githooks).
That said its important to understand that Githooks only places wrappers inside the official Git hooks dir <bareReep>/hooks (or <normalRepo>/.git/hooks). And there is no difference in execution logic for bare repositores, its the exact same, and also the .githooks folder is at the root of the repository.
Githooks supports all hooks (almost). So for your case on the server:

You simply place individual hooks into <bareRepo>/.githooks like in the normal repository [layout case].(https://github.com/gabyx/Githooks#layout-and-options) and they get executed.
The <bareRepo>/.githooks folder does not get transmitted to the user if he clones!
For shared repositories you simply look here
Use the instruction for installing on the server.

That should get you startet pretty easily on the server. Depending on what you have, I used Gitea.
There are however some caveats which are worth noting:

On the server Githooks gets execute in parallel, so any Githooks update mechanism should be thread-safe as well (which it is not at the moment), therefore we disable Githooks updates (its better anyway as you want full control over this probably). Updating shared hooks repositories, is however threadsafe since it only uses Git!
All hooks need to be trusted on the server such that Githooks does not fail or hang (because it needs your input
On the server you need to be careful, at least for Gitea, that you might use the core.hooksPath approach described here. The problem I had was that Gitea (on creating a repository) overwrites bruteforce (not good behavior) hooks in the <bareRepo>/hooks directory which is where our Githooks run wrappers were copied (by git init launched from Gitea). This is obviousyl not good and we can not interfere this (I might probably make a PR to fix this), and therefore:

Gitea (service) hooks need to be executed as well on the server (also Bitbucket has such hooks)
Copy all service related hooks to the location where you template directory (init.templateDir) should be.
Install Githooks with --template-dir=<path> and use --use-core-hookspath to use core.hooksPath. (centralized hooks)
Then Githooks will always first execute the old hooks (service hooks) which is correct and then proceed with the Githooks logic.

The following answer is based on rycus86/githooks#159
@mjk-gh:
The first thing to note is that bare repositories are handled the exact same way as normal repos are handled.
That means the .githooks folder can be in these locations
That means your path <bareRepo>/hooks/.githooksshould be <bareRepo>/.githooks (or <normalRepo>/.githooks).

Oooooh! Okay! So for bare repositories, the project root is the bare repo's .git folder (which is its top folder), instead of the folder above that (which has nothing to do with the repo), understood.

That said its important to understand that Githooks only places wrappers inside the official Git hooks dir <bareReep>/hooks (or <normalRepo>/.git/hooks). And there is no difference in execution logic for bare repositores, its the exact same, and also the .githooks folder is at the root of the repository.

After sticking to the documentation's part about trusting all server-side githook hooks, everything works like a charm, thank you and @rycus86!
[Hints & Caveats]
Thanks a lot!

@mjk-gh I meant giving the Repository a star ;-)

Good that it works

@mjk-gh: I did not receive any star so far. If githooks is still of use for your, please consider voting it up. Thanks

@gabyx: Hm, I did star the repo, but the bash-version, as this is the version I am using:
https://github.com/rycus86/githooks
And @rycus86 wrote in rycus86/githooks#159 :

mjk-gh wrote:

I have to admit I do not fully understand how githooks on the server are supposed to work.

Same here to be honest, @gabyx implemented that part

So since you implemented that part in the bash-version, shouldn't I star the bash-version then? Sorry for my confusion, I'm not too familiar with github (yet?). :-}

Sorry, I thought you use the new version ;-). This repo is the new version ;-) which is more robust. Check it out :-)
Thanks for your support anyway.
BR

Thanks for the clarification!
Two more questions:

How is the go-based version more robust than the bash version?
As one of my use-cases is about installing githooks into users' NFS home directories, which are accessed by different CPU architectures: Can the go-based githooks work without having to compile anything?

Go is the language it was written, and the executable .exe is provided
in the release. There is nothing to be compiled when githooks runs.
As you use one githooks install and multiple CPU architecture (which is a
bit weird), you will have only one architecture installed and it does not
work for others. Best thing would be anyway to install it on every system
you are working with in your home directory...
The git repositories are not affected as they contain wrapper. I will think
about a feature where all architectures are installed into the binary
~/.githooks/bin dir. You then just need to set githooks.runner variable
on each architecture and it will work.
Am Mi., 16. Juni 2021 um 12:10 Uhr schrieb mjk-gh @.***

:

Thanks for the clarification!
Two more questions:

How is the go-based version more robust than the bash version?
As one of my use-cases is about installing githooks into users' NFS
home directories, which are accessed by different CPU architectures: Can
the go-based githooks work without having to compile anything?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gabyx/Githooks/issues/24#issuecomment-862231731, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE6CDMAHVFMCSOOE2OCCTTTTB2B7ANCNFSM45KMV5NA
.

Go is the language it was written, and the executable .exe is provided
in the release.

=:-O
So you provide a statically linked binary for all possible CPU architectures? That sounds like binding a lot of resources on your side. Or do you mean that the binary appropriate for the individual architecture will be compiled upon installation of the Go-version of githooks?
Heterogenous networks with network shares (incl. $HOME) are not weird, they are beautiful. :) My idea was that you could simply provide githooks as an interpretable script, just like bash. I just do not know if Go is suitable to be used as an interpreted language, or if it has to be compiled, because otherwise it's too slow -- or maybe there are no Go interpreters?
{ A few minutes later }
Well, there /do/ seem to be Go interpreters:

https://github.com/gijit/gi
https://pkg.go.dev/golang.org/x/tools/go/ssa/interp?utm_source=godoc

But I cannot judge their feasability in this context. Also, no Go interpreter in Debian:
$ apt-cache search go interpreter|grep -i go|grep -i interpre --color=yes
seed-webkit2 - GObject JavaScript bindings for the webkit engine - Interpreter
golang-github-robertkrimen-otto-dev - JavaScript parser and interpreter in Go
golang-starlark-dev - Interpreter for the Starlark configuration language
$

go can be run as an interpreter too. And it should actually cache the compilation  ->go run.
Installing all executable for all architecture you want is probably really easy as I already compile all architechtures...
Yes I provide binaries, see the release page in github.

I think providing a way of installing always all architectures is funny nice little feature =)

See https://github.com/gabyx/Githooks/issues/32


check if lhs of property access expression is a module

Add a check to see if the Left Hand Side expression is a module.
Needs a unit test, and E2E test.

@rkirov Please take another look.

LGTM, add the assertion and submit it.

Merged


Add snippets to lsp completions by default

As suggested by company-yasnippet documentation https://github.com/company-mode/company-mode/blob/f6974e3103497afe01da2ad4d2ea3668ad68bc27/company-yasnippet.el#L118

It's indeed noisier than I thought it would be. I'll keep that in my private config because I don't really mind, but it's probably not a good default value


Need to correctly infer if a relationship is optional or not

In Rails 5 belongs_to relationships are required by default.
However if you just have;
class Model < ApplicationRecord
  belongs_to :other_model
end

Then RailsAdmin marks this field as optional. This can be addressed in the model by doing;
class Model < ApplicationRecord
  belongs_to :other_model, required: true
end

It would be nice if RailsAdmin took into account the version of Rails when deciding if a relationship is required or not.

I think the reason is because the validation is actually getting killed somehow. I subitted an issue: https://github.com/sferik/rails_admin/issues/2785.

@ordinaryzelig nice, I will close this issue.


Broken AVD system path. Check your ANDROID_SDK_ROOT value

`Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter emulators --launch Pixel-test
exception
ProcessException: ProcessException: Process exited abnormally:
PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [C:\Android\SDK]!
Command: C:\Android\SDK\emulator\emulator.exe -avd Pixel-test
#0      RunResult.throwException (package:flutter_tools/src/base/process.dart:141:5)
#1      _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart:275:19)
<asynchronous suspension>
#2      AndroidEmulator.launch (package:flutter_tools/src/android/android_emulator.dart:52:52)
#3      EmulatorsCommand._launchEmulator (package:flutter_tools/src/commands/emulators.dart:74:31)
<asynchronous suspension>
#4      EmulatorsCommand.runCommand (package:flutter_tools/src/commands/emulators.dart:47:13)
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#6      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#7      _rootRunUnary (dart:async/zone.dart:1134:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#12     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#13     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#17     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#18     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#19     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#20     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

flutter doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.18362.657], locale pt-PT)
    • Flutter version 1.12.13+hotfix.8 at C:\flutter
    • Framework revision 0b8abb4724 (2 days ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Android\SDK
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = C:\Android\SDK
    • ANDROID_SDK_ROOT = C:\Android\SDK
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 43.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[✓] VS Code (version 1.42.0)
    • VS Code at C:\Users\AfonsoGuimarães\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.8.1

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

`
I'm getting this error even having the variables ANDROID_HOME and ANDROID_SDK_ROOT set.

Hi @MathSqr2

Please follow this Solution
run flutter emulators and choose the emulator you want
run flutter emulators --launch <emualtor name>

Thank you

Hi @TahaTesser , thanks for responding. The error that I previously pointed out appeared when I did what you asked, but for the sake of it I ran again. The output is has it follows:
`Flutter crash report; please file at https://github.com/flutter/flutter/issues.
command
flutter emulators --launch Pixel_2_API_29
exception
ProcessException: ProcessException: Process exited abnormally:
PANIC: Cannot find AVD system path. Please define ANDROID_SDK_ROOT
Command: C:\Android\Sdk\emulator\emulator.exe -avd Pixel_2_API_29
#0      RunResult.throwException (package:flutter_tools/src/base/process.dart:141:5)
#1      _DefaultProcessUtils.run (package:flutter_tools/src/base/process.dart:275:19)
<asynchronous suspension>
#2      AndroidEmulator.launch (package:flutter_tools/src/android/android_emulator.dart:52:52)
#3      EmulatorsCommand._launchEmulator (package:flutter_tools/src/commands/emulators.dart:74:31)
<asynchronous suspension>
#4      EmulatorsCommand.runCommand (package:flutter_tools/src/commands/emulators.dart:47:13)
#5      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:615:18)
#6      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:73:64)
#7      _rootRunUnary (dart:async/zone.dart:1134:38)
#8      _CustomZone.runUnary (dart:async/zone.dart:1031:19)
#9      _FutureListener.handleValue (dart:async/future_impl.dart:139:18)
#10     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680:45)
#11     Future._propagateToListeners (dart:async/future_impl.dart:709:32)
#12     Future._completeWithValue (dart:async/future_impl.dart:524:5)
#13     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:554:7)
#14     _rootRun (dart:async/zone.dart:1126:13)
#15     _CustomZone.run (dart:async/zone.dart:1023:19)
#16     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
#17     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:965:23)
#18     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#19     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#20     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#21     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:175:5)

flutter doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Microsoft Windows [Version 10.0.18362.657], locale pt-PT)
    • Flutter version 1.12.13+hotfix.8 at C:\flutter
    • Framework revision 0b8abb4724 (3 days ago), 2020-02-11 11:44:36 -0800
    • Engine revision e1e6ced81d
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Android\Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = C:\Android\Sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 43.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[✓] VS Code (version 1.42.0)
    • VS Code at C:\Users\AfonsoGuimarães\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.8.1

[!] Connected device
    ! No devices available

! Doctor found issues in 1 category.

`
I have both ANDROID_HOME and ANDROID_SDK_ROOT set to the same folder C:\Android\Sdk

I had the exact same issue as you, the problem is that you .android folder is located in a path with non-ascii characters ("C:\Users\AfonsoGuimarães"), I think. You need to move it.
In order to do that :

close all terminals and software related to android
you have to move the .android folder located in your user directory in another directory, let's say to "C:\Android"
open C:\Android.android\avd and edit the ini file(s) to set the correct path that you juste changed
Open the windows environment variables settings and edit or set a new variable if you don't have it :
name : "ANDROID_SDK_HOME" value : "C:\Android" (not .android !!)
Now it should work
I have no others environement variable set (no ANDROID_HOME or ANDROID_SDK_ROOT) and it works for me

I found the solution here : https://developercommunity.visualstudio.com/content/problem/1005744/panic-cannot-find-avd-system-path-please-define-an.html

I had the exact same issue as you, the problem is that you .android folder is located in a path with non-ascii characters ("C:\Users\AfonsoGuimarães"), I think. You need to move it. In order to do that :

close all terminals and software related to android
you have to move the .android folder located in your user directory in another directory, let's say to "C:\Android"
open C:\Android.android\avd and edit the ini file(s) to set the correct path that you juste changed
Open the windows environment variables settings and edit or set a new variable if you don't have it :
name : "ANDROID_SDK_HOME" value : "C:\Android" (not .android !!)
Now it should work

I found the solution here : https://developercommunity.visualstudio.com/content/problem/1005744/panic-cannot-find-avd-system-path-please-define-an.html

I had the exact same issue as you, the problem is that you .android folder is located in a path with non-ascii characters ("C:\Users\AfonsoGuimarães"), I think. You need to move it. In order to do that :

close all terminals and software related to android
you have to move the .android folder located in your user directory in another directory, let's say to "C:\Android"
open C:\Android.android\avd and edit the ini file(s) to set the correct path that you juste changed
Open the windows environment variables settings and edit or set a new variable if you don't have it :
name : "ANDROID_SDK_HOME" value : "C:\Android" (not .android !!)
Now it should work

I found the solution here : https://developercommunity.visualstudio.com/content/problem/1005744/panic-cannot-find-avd-system-path-please-define-an.html

Hi...
I know it's been almost two years since this solution, but i just wanted to say thank you for this.
I was trying to solve this on my computer all day long, looking for answers everywhere. Now it's almost 10pm and I've just found your answer and finally solved my non-ascii problem.
Again... thank you! :)

Hello @MathSqr2. Can you confirm if this is still an issue?

Since I was not able to reproduce this issue, I am closing it as fixed. If you can still reproduce this issue, please comment and we can reopen it. Thank you

Hello @KedwithGod. Can you post your flutter doctor -v output as well as the error logs?


silodiff reports data sizes differences too verbosely

The output below is from some example data from Katie Lewis. One file has 32 bit ints. The other 64 bit. It reports that the global_mesh_data arrays have different member type sizes and there is no way to turn off this extra diff output. Katie would like to be able to turn off the report of differing sizes. edge83{miller86}992: /usr/gapps/silo/4.8/$SYS_TYPE/bin/silodiff -l 1 PrepareBlocking.sami fudged.silo INFO: opening PrepareBlocking.sami' as $1 INFO: opening fudged.silo' as $2 Object PrepareBlocking.sami fudged.silo _hdf5libinfo = "hdf51.8.4" "hdf51.6.5" _silolibinfo = "4.7.2" "4.6.1" global_mesh_data = 8byte data 4byte data global_mesh_data = different data sizes [8 in file A; 4 in file B] global_mesh_data[0] = (long)2592 2591 global_node_numbers = 8byte data 4byte data global_node_numbers = different data sizes [8 in file A; 4 in file B] vtxdist = 8byte data 4byte data
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 714
Status: New
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: silodiff reports data sizes differences too verbosely
Assigned to: -
Category: -
Target version: -
Author: Mark Miller
Start: 05/17/2011
Due date:
% Done: 0%
Estimated time:
Created: 05/17/2011 09:19 pm
Updated: 05/18/2011 12:26 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 4.8
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
The output below is from some example data from Katie Lewis. One file has 32 bit ints. The other 64 bit. It reports that the global_mesh_data arrays have different member type sizes and there is no way to turn off this extra diff output. Katie would like to be able to turn off the report of differing sizes. edge83{miller86}992: /usr/gapps/silo/4.8/$SYS_TYPE/bin/silodiff -l 1 PrepareBlocking.sami fudged.silo INFO: opening PrepareBlocking.sami' as $1 INFO: opening fudged.silo' as $2 Object PrepareBlocking.sami fudged.silo _hdf5libinfo = "hdf51.8.4" "hdf51.6.5" _silolibinfo = "4.7.2" "4.6.1" global_mesh_data = 8byte data 4byte data global_mesh_data = different data sizes [8 in file A; 4 in file B] global_mesh_data[0] = (long)2592 2591 global_node_numbers = 8byte data 4byte data global_node_numbers = different data sizes [8 in file A; 4 in file B] vtxdist = 8byte data 4byte data
Comments:
Adding two data files. Katie would like an option to suppress data type size mismatch messages. Currently, the only way to suppress them is to specify a difference mode of 'summary'. But, that also supresses any detailed difference messages from individual datums in an array.

0725_PrepareBlocking.sami.gz
0725_PrepareBlocking_2.sami.gz


feat(analysis/topology): locally compact spaces and the compact-open topology

TO CONTRIBUTORS:
Make sure you have:

[ ] reviewed and applied the coding style: coding, naming
[ ] make sure definitions and lemmas are put in the right files
[x] make sure definitions and lemmas are not redundant

It occurs to me that ev (in the root namespace) may not be the best choice of name, but I'm not sure what a better name would be. Should it go in some namespace? Note that ev itself doesn't depend on the topology on the mapping space.
I'm not sure how the local notation C(α, β) will be received. For me, it makes things look a bit nicer. I chose its definition to hopefully match the definition of the hom sets in Top, since that seems like it would be convenient.
I didn't make compact_open an instance since I imagine there will be other topologies one wants to put on spaces of continuous functions.

Also, as our theory of topological spaces expands, I'm not sure what the best way to divide it into files is--here I put locally compact spaces in the same file as the compact open topology, but I can imagine that it makes more sense to separate them.


Predict Safe address before creating

Closes #303

coverage: 93.053% (+0.03%) from 93.027%
when pulling 4820d51b141c54a438098fb93a8d850fe3507111 on predict-safe-address
into bdc4fd6bbd017a6954196b20ef4b07ca89b6ec0c on master.


VS Code ignores "editor.unicodeHighlight.ambiguousCharacters": false extension language setting after startup

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.95.3
OS Version: Fedora Linux 40, 6.10.12-200.fc40.x86_64

In the VS Code extension for the Lean 4 theorem prover, we set editor.unicodeHighlight.ambiguousCharacter to false for Lean documents since Lean code tends to contain lots of Unicode characters and these boxes make Unicode-heavy code very difficult to read.
Since somewhat recently, users have been reporting that despite us disabling this setting, they see boxes around Unicode symbols right after launching VS Code, i.e. in the last active editor when closing VS Code previously. These boxes disappear as soon as the full text editor state is changed (e.g. by switching the visible tab and back, or by toggling the "Render Control Characters" setting), and the issue can be worked around by also disabling this setting in the user settings.
Steps to Reproduce:

Install the Lean 4 extension (I suspect a minimal extension that contributes a language and "editor.unicodeHighlight.ambiguousCharacters": false for it will do, but I haven't tried) on blank user settings.
Open an untitled document, set the language ID to lean4 and enter the character ℝ.
Close VS Code.
Re-open VS Code.
Observe that the ℝ is now surrounded by a box.

dup https://github.com/microsoft/vscode/issues/231224


[FLINK-6124] [table] Add min/max string aggregation with retracion

This PR adds the missing retraction aggregations for strings.

Thanks for the hint @shaoxuan-wang. I added the tests and will merge this.


Cleanup old versions: WHTA.Tamara

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

The pull request contains more than one manifest. Either singleton or multi file manifest under one version directory.

Automatic Validation ended with:

The pull request contains more than one manifest. Either singleton or multi file manifest under one version directory.

...


chore(main): release 1.7.0

:robot: I have created a release beep boop
1.7.0 (2023-08-01)
Features

updates to protobuf definitions for flipt v1.24.0 (#36) (7b3491e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/flipt-io/flipt-grpc-ruby/releases/tag/v1.7.0 :sunflower: