CocoaPods error when running app on iOS emulator

Steps to Reproduce

Launching app on iOS emulator renders error message from CocoaPods. There is no error when running the same app on an Android emulator.
Logs

Launching lib/main.dart on iPhone X in debug mode...
Running pod install...                                       1.7s
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 `.symlinks/flutter/ios`
    -> Fetching podspec for `path_provider` from `.symlinks/plugins/path_provider/ios`
    -> Fetching podspec for `sqflite` from `.symlinks/plugins/sqflite/ios`

    Resolving dependencies of `Podfile`

    Comparing resolved specification to the sandbox manifest
      A FMDB
      A Flutter
      A path_provider
      A sqflite

    Downloading dependencies

    -> Installing FMDB (2.7.2)
      > Copying FMDB from `/Users/sylvain/Library/Caches/CocoaPods/Pods/Release/FMDB/2.7.2-6198a` to `Pods/FMDB`

    -> Installing Flutter (1.0.0)

    -> Installing path_provider (0.0.1)

    -> Installing sqflite (0.0.1)
      - Running pre install hooks

    Generating Pods project
      - Creating Pods project
      - Adding source files to Pods project
      - Adding frameworks to Pods project
      - Adding libraries to Pods project
      - Adding resources to Pods project
      - Adding development pod helper files to Pods project
      - Linking headers

    ――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

### Command

/usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod install --verbose

Report
* What did you do?
* What did you expect to happen?
* What happened instead?

Stack
   CocoaPods : 1.5.3
        Ruby : ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]
    RubyGems : 2.5.2
        Host : Mac OS X 10.13.4 (17E202)
       Xcode : 9.4.1 (9F2000)
         Git : git version 2.15.2 (Apple Git-101.1)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ c378d30e3718557f9f4e0fc858e448d2f9c0674d

Plugins
cocoapods-deintegrate : 1.0.2
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.3.0
cocoapods-try         : 1.1.0

Podfile
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

def parse_KV_file(file, separator='=')
  file_abs_path = File.expand_path(file)
  if !File.exists? file_abs_path
    return [];
 end
  pods_ary = []
  skip_line_start_symbols = ["#", "/"]
  File.foreach(file_abs_path) { |line|
      next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
      plugin = line.split(pattern=separator)
      if plugin.length == 2
        podname = plugin[0].strip()
        path = plugin[1].strip()
        podpath = File.expand_path("#{path}", file_abs_path)
        pods_ary.push({:name => podname, :path => podpath});
      else
       puts "Invalid plugin specification: #{line}"
      end
  }
  return pods_ary
end

target 'Runner' do
  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')

  # Flutter Pods
  generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
  if generated_xcode_build_settings.empty?
    puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter packages get is executed first."
  end
  generated_xcode_build_settings.map { |p|
    if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
      symlink = File.join('.symlinks', 'flutter')
      File.symlink(File.dirname(p[:path]), symlink)
      pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
    end
  }

  # Plugin Pods
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.map { |p|
    symlink = File.join('.symlinks', 'plugins', p[:name])
    File.symlink(p[:path], symlink)
    pod p[:name], :path => File.join(symlink, 'ios')
  }
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

Error
    Errno::EACCES - Permission denied @ dir_s_mkdir - /Users/Development
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:253:in `mkdir'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:253:in `fu_mkdir'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:227:in `block (2 levels) in mkdir_p'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:225:in `reverse_each'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:225:in `block in mkdir_p'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:211:in `each'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:211:in `mkdir_p'
    /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/pathname.rb:576:in `mkpath'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:120:in `add_file'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:100:in `block inadd_files'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:99:in `map'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:99:in `add_files'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:164:in `block (4 levels) in link_headers'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:162:in `each'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:162:in `block (3 levels) in link_headers'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:146:in `each'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:146:in `block (2 levels) in link_headers'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:135:in `each'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:135:in `block in link_headers'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:142:in `message'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:134:in `link_headers'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:44:in `install!'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator.rb:163:in `install_file_references'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator.rb:64:in `generate!'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:184:in `block in generate_pods_project'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:64:in `section'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:183:in `generate_pods_project'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:119:in `install!'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command/install.rb:41:in `run'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:52:in `run'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/bin/pod:55:in `<top (required)>'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod:22:in `load'
    /usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod:22:in `<main>'

――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

    [!] Oh no, an error occurred.

    Search for existing GitHub issues similar to yours:
    https://github.com/CocoaPods/CocoaPods/search?q=Permission+denied+%40+dir_s_mkdir+-+%2FUsers%2FDevelopment&type=Issues

    If none exists, create a ticket, with the template displayed above, on:
    https://github.com/CocoaPods/CocoaPods/issues/new

    Be sure to first read the contributing guide for details on how to properly submit a ticket:
    https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md

    Don't forget to anonymize any private data!

    Looking for related issues on cocoapods/cocoapods...
     - Error launching Flutter App - Permission denied @ dir_s_mkdir
       https://github.com/CocoaPods/CocoaPods/issues/7927 [open] [1 comment]
       9 hours ago

Error output from CocoaPods:
↳

    [!] `<PBXGroup UUID=`97C146E51CF9000F007C117D`>` attempted to initialize an object with an unknown UUID. `CF3B75C9A7D2FA2A4C99F110` for attribute: `children`. This can be the result of a merge and  the unknown UUID is being discarded.

    [!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
Error running pod install
Error launching application on iPhone X.

No issues found! (ran in 1.7s)

[✓] Flutter (Channel beta, v0.5.1, on Mac OS X 10.13.4 17E202, locale en-CH)
    • Flutter version 0.5.1 at /Users/sylvain/development/flutter
    • Framework revision c7ea3ca377 (6 weeks ago), 2018-05-29 21:07:33 +0200
    • Engine revision 1ed25ca7b7
    • Dart version 2.0.0-dev.58.0.flutter-f981f09760

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.1)
    • Android SDK at /Users/sylvain/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[!] VS Code (version 1.25.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected devices (1 available)
    • iPhone X • 3AA71F83-0AC2-4AC9-B85F-6106E8090D68 • ios • iOS 11.4 (simulator)

! Doctor found issues in 1 category.

There seems to be an error in the log from the doctor, the Flutter VSCode plugin is installed on my machine.

I was wondering where these versions come from
    -> Installing Flutter (1.0.0)

    -> Installing path_provider (0.0.1)

    -> Installing sqflite (0.0.1)

also in flutter doctor output it mentions /Users/sylvain/development/flutter
and the error message mentions Errno::EACCES - Permission denied @ dir_s_mkdir - /Users/Development
any idea where /Users/Development might come from?

I don't know where these versions come from, the versions indicated in my pubsec.yaml file are:
  sqflite: ^0.10.0
  path_provider: ^0.4.1

And I don't know where Users/development comes from, I never specified it anywhere and as far as I know there is nothing there.
If this can be any help I encountered this error while following a tutorial, the finished app code is here: https://github.com/StephenGrider/FlutterCasts/tree/master/news

You may try opening workspace file in ios directory and check paths in build settings tab. And then in ios directory run pod deintegrate and pod install.
Last time I've moved the folder to another computer these steps fixed my problem.

I'm getting exact error, I checked by workspace file and there is no reference to /Users/Development in the build file.
Pasted my log if it helps at all.
Launching lib/main.dart on iPhone X in debug mode...
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 `.symlinks/flutter/ios`
-> Fetching podspec for `path_provider` from `.symlinks/plugins/path_provider/ios`
-> Fetching podspec for `shared_preferences` from `.symlinks/plugins/shared_preferences/ios`
Resolving dependencies of `Podfile`
Comparing resolved specification to the sandbox manifest
A Flutter
A path_provider
A shared_preferences
Downloading dependencies
-> Installing Flutter (1.0.0)
-> Installing path_provider (0.0.1)
-> Installing shared_preferences (0.0.1)
- Running pre install hooks
Generating Pods project
- Creating Pods project
- Adding source files to Pods project
- Adding frameworks to Pods project
- Adding libraries to Pods project
- Adding resources to Pods project
- Adding development pod helper files to Pods project
- Linking headers
――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
### Command

/usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod install --verbose
### Report
* What did you do?
* What did you expect to happen?
* What happened instead?
### Stack

CocoaPods : 1.5.3
Ruby : ruby 2.3.3p222 (2016-11-21 revision 56859) [universal.x86_64-darwin17]
RubyGems : 2.5.2
Host : Mac OS X 10.13.5 (17F77)
Xcode : 9.4.1 (9F2000)
Git : git version 2.10.1
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 7fe47e52a5ca6ab2956ccac9f78c26f1569f921f
### Plugins

cocoapods-deintegrate : 1.0.2
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.3.0
cocoapods-try         : 1.1.0
### Podfile
```ruby
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'
# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
def parse_KV_file(file, separator='=')
file_abs_path = File.expand_path(file)
if !File.exists? file_abs_path
return [];
end
pods_ary = []
skip_line_start_symbols = ["#", "/"]
File.foreach(file_abs_path) { |line|
next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
plugin = line.split(pattern=separator)
if plugin.length == 2
podname = plugin[0].strip()
path = plugin[1].strip()
podpath = File.expand_path("#{path}", file_abs_path)
pods_ary.push({:name => podname, :path => podpath});
else
puts "Invalid plugin specification: #{line}"
end
}
return pods_ary
end
target 'Runner' do
# Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
# referring to absolute paths on developers' machines.
system('rm -rf .symlinks')
system('mkdir -p .symlinks/plugins')
# Flutter Pods
generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
if generated_xcode_build_settings.empty?
puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter packages get is executed first."
end
generated_xcode_build_settings.map { |p|
if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
symlink = File.join('.symlinks', 'flutter')
File.symlink(File.dirname(p[:path]), symlink)
pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
end
}
# Plugin Pods
plugin_pods = parse_KV_file('../.flutter-plugins')
plugin_pods.map { |p|
symlink = File.join('.symlinks', 'plugins', p[:name])
File.symlink(p[:path], symlink)
pod p[:name], :path => File.join(symlink, 'ios')
}
end
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['ENABLE_BITCODE'] = 'NO'
end
end
end

Error
Errno::EACCES - Permission denied @ dir_s_mkdir - /Users/Development
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:253:in `mkdir'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:253:in `fu_mkdir'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:227:in `block (2 levels) in mkdir_p'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:225:in `reverse_each'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:225:in `block in mkdir_p'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:211:in `each'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/fileutils.rb:211:in `mkdir_p'
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/pathname.rb:576:in `mkpath'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:120:in `add_file'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:100:in `block in add_files'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:99:in `map'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/sandbox/headers_store.rb:99:in `add_files'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:164:in `block (4 levels) in link_headers'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:162:in `each'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:162:in `block (3 levels) in link_headers'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:146:in `each'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:146:in `block (2 levels) in link_headers'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:135:in `each'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:135:in `block in link_headers'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:142:in `message'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:134:in `link_headers'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator/file_references_installer.rb:44:in `install!'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator.rb:163:in `install_file_references'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer/xcode/pods_project_generator.rb:64:in `generate!'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:184:in `block in generate_pods_project'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/user_interface.rb:64:in `section'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:183:in `generate_pods_project'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/installer.rb:119:in `install!'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command/install.rb:41:in `run'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:52:in `run'
/usr/local/Cellar/cocoapods/1.5.3/libexec/gems/cocoapods-1.5.3/bin/pod:55:in `<top (required)>'
/usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod:22:in `load'
/usr/local/Cellar/cocoapods/1.5.3/libexec/bin/pod:22:in `<main>'

――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
[!] Oh no, an error occurred.
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=Permission+denied+%40+dir_s_mkdir+-+%2FUsers%2FDevelopment&type=Issues
If none exists, create a ticket, with the template displayed above, on:
https://github.com/CocoaPods/CocoaPods/issues/new
Be sure to first read the contributing guide for details on how to properly submit a ticket:
https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md
Don't forget to anonymize any private data!
Looking for related issues on cocoapods/cocoapods...
- Error launching Flutter App - Permission denied @ dir_s_mkdir
https://github.com/CocoaPods/CocoaPods/issues/7927 [open] [1 comment]
a day ago
Error output from CocoaPods:
↳
WARNING: CocoaPods requires your terminal to be using UTF-8 encoding.
Consider adding the following to ~/.profile:
export LANG=en_US.UTF-8

Ignoring executable-hooks-1.5.0 because its extensions are not built.  Try: gem pristine executable-hooks --version 1.5.0
Ignoring gem-wrappers-1.4.0 because its extensions are not built.  Try: gem pristine gem-wrappers --version 1.4.0
[!] Automatically assigning platform `ios` with version `8.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
Error running pod install
Error launching application on iPhone X.
Exited (sigterm)

This works for me:
cd ~
git clone https://github.com/StephenGrider/FlutterCasts.git
cd FlutterCasts/news
flutter packages get
flutter clean
cd ios
pod install
open Runner.xcworkspace
(Runner -> Targets->Runner General -> set signing)
cd ..
flutter build ios
open -a Simulator
flutter run
For UTF error add these to ~/.profile or /etc/profile
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

I'm not cloning the flutter cast tutorial like the op linked. I'm using the default flutter generator and started fresh. It originally worked (iOS simulator) on fresh project but as I started adding plugins it started producing error above.

Found a temporary fix,
Just go into /Users folder in finders, create 'Development' folder, give folder read/write access for everyone. Run flutter. Once it runs, it gets populated with only the following file
/Users/Development/flutter/bin/cache/artifacts/engine/ios/Flutter.framework' file.
But clearer this is the wrong path,
The proper path is:
/Users/*MYUSERNAME*/Development/flutter/bin/cache/artifacts/engine/ios
And this is were the flutter library is installed.
And if I go to this folder, it also has the Flutter.framework file in it. So something during the pod install for flutter process is not referencing  the flutter library directory.
my Generated.xcconfig file also refers correctly to my FLUTTER_FRAMEWORK_DIR. e.g. this is contents
// This is a generated file; do not edit or check into version control.
FLUTTER_ROOT=/Users/*MYUSERNAME*/development/flutter
FLUTTER_APPLICATION_PATH=/Users/*MYUSERNAME*/Development/hello_world
FLUTTER_TARGET=/Users/*MYUSERNAME*/Development/hello_world/lib/main.dart
FLUTTER_BUILD_MODE=debug
FLUTTER_BUILD_DIR=build
SYMROOT=${SOURCE_ROOT}/../build/ios
FLUTTER_FRAMEWORK_DIR=/Users/*MYUSERNAME*/development/flutter/bin/cache/artifacts/engine/ios
PREVIEW_DART_2=true

I don't know if this should be closed since there is something wrong in the flutter POD file or install POD step that is causing it to output to incorrect location. This was just a temporary work around.

agree I have the same error

also try clear ~/.pub-cache

I solved the problem creating the missing folder "Users" (in my case the error was Errno::EACCES - Permission denied @ dir_s_mkdir - /Users/Users) and give full permission to all users.
Thanks Anand.

Having the exact same issue here, just with a different path. My projects and flutter are all located in /Users//Projects
For whatever reason when running pod install, the user name portion is getting left out of the path. It worked the first time I ran it while adding a new plugin to my project and then it failed on subsequent runs. This is a very serious blocking issue preventing real development use of Flutter for iOS.

I just upgraded to the latest Flutter beta (0.10.2) and NOW I have this error .. never had it before.. and the path is the /Users/Development .. No idea what's going on ..

I just did a fresh install of my mac and got the exact same problem. Like @apat183 mentioned,  Flutter.framework gets installed in
/Users/Development/flutter/bin/cache/artifacts/engine/ios/Flutter.framework' file.
after /Users/Development is created with rights for everyone, instead of
/Users/*MYUSERNAME*/Development/flutter/bin/cache/artifacts/engine/ios

In my case, I had flutter installed in the folder downloads on the mac. After cloning the repository to a folder closer to the root (~/john), I also got the pod install error. It tried to create the Flutter folder in the /Users/flutter directory.
I got rid of the error by moving the repository to a directory that is higher (or on the same level) in the folder structure.. So to recap:
this structure gave me an error:
flutter location: /users/john/downloads/flutter
repo/project location: /users/john/project
this resolved the issue
flutter location: /users/john/downloads/flutter (unchanged)
repo/project location: /users/john/desktop/project
Hope this helps...

Hi,
for my case i got this error when trying to execute 'pod install' ==>
Analyzing dependencies
Fetching podspec for Flutter from .symlinks/flutter/ios
Fetching podspec for cloud_firestore from .symlinks/plugins/cloud_firestore/ios
Fetching podspec for firebase_core from .symlinks/plugins/firebase_core/ios
Downloading dependencies
Installing BoringSSL (10.0.6)
[!] Error installing BoringSSL
[!] /usr/local/bin/git clone https://github.com/google/boringssl.git /var/folders/f7/8snc5xln7cl9rqcc1hqsy4kh0000gp/T/d20181207-25102-1e0rcy3 --template=
Cloning into '/var/folders/f7/8snc5xln7cl9rqcc1hqsy4kh0000gp/T/d20181207-25102-1e0rcy3'...
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
[!] Automatically assigning platform ios with version 8.0 on target Runner because no platform was specified. Please specify a platform for this target in your Podfile. See https://guides.cocoapods.org/syntax/podfile.html#platform.
Any idea on how to resolve this ?

I get the following error:
Errno::EACCES - Permission denied @ dir_s_mkdir - /Documents
What should I do in this case?

It appears we reference "~/development" in our install instructions:
https://flutter.dev/docs/get-started/install/macos
But I'm still not sure where the "/Users/Development" path is coming from (whether cocoapods or Flutter).

My understanding from above is that this is possibly the faulty code?
https://github.com/flutter/flutter/blob/277d5fe5f6e91a78a24118ce699ea210a6e873c7/packages/flutter_tools/templates/cocoapods/Podfile-objc#L41
Are we not being careful enough with paths?  e.g. if the FLUTTER_FRAMEWORK_DIRECTORY has/doesn't have a / at the end, or some other quirk that could cause this to get the wrong path there?

Adding customer: critical.  Given the number of responses here it seems worth someone at least spending a few minutes to triage here (a bit more than I did).

I tried to reproduce this by downgrading to Flutter 0.5.1 and CocoaPods 1.5.3.
[✓] Flutter (Channel unknown, v0.5.1, on Mac OS X 10.14.5 18F203, locale en-US)
    • Flutter version 0.5.1 at /Users/magder/Projects/flutter
    • Framework revision c7ea3ca377 (1 year ago), 2018-05-29 21:07:33 +0200
    • Engine revision 1ed25ca7b7
    • Dart version 2.0.0-dev.58.0.flutter-f981f09760

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/magder/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.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_152-release-1343-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.2.1, Build version 10E1001
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[!] VS Code (version 1.34.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected devices (1 available)
    • iPhone Xʀ • 6A677317-B714-49F1-8E1D-78AD1F3F2654 • ios • com.apple.CoreSimulator.SimRuntime.iOS-12-2 (simulator)

I couldn't reproduce with the FlutterCasts example:
$ git clone https://github.com/StephenGrider/FlutterCasts.git
$ cd FlutterCasts/news

I then opened ios/Runner.xcworkspace to change it to the legacy build system since the new build system is the default in Xcode 10.2.1.
$ flutter run
Running "flutter packages get" in news...                    0.4s
Launching lib/main.dart on iPhone Xʀ in debug mode...
Running pod install...                                       1.0s
Starting Xcode build...
 ├─Assembling Flutter resources...                    1.2s
 └─Compiling, linking and signing...                  3.1s
Xcode build done.                                            6.0s
Syncing files to device iPhone Xʀ...                         4.5s

I also created a new project and added packages and couldn't reproduce:
  sqflite: ^0.10.0
  path_provider: ^0.4.1
  rxdart: ^0.18.0

$ flutter run
Running "flutter packages get" in test_cocoapods...          0.9s
Launching lib/main.dart on iPhone Xʀ in debug mode...
Running pod install...                                       0.9s
Syncing files to device iPhone Xʀ...                         3.6s

The originator was running ios-deploy 1.9.2 and I am running 1.9.4 and the originator was running Xcode 9.4.1 and I am running Xcode 10.2.1, so maybe there's something in there?  A reliable repro case would help.

My understanding from above is that this is possibly the faulty code?
https://github.com/flutter/flutter/blob/277d5fe5f6e91a78a24118ce699ea210a6e873c7/packages/flutter_tools/templates/cocoapods/Podfile-objc#L41

The Generated.xcconfig referenced above seem to show correct FLUTTER_FRAMEWORK_DIR paths that aren't up a level into /User/Development.
This is the most suspicious thing I've found so far, but this podhelper script is only used for modules, not apps.
https://github.com/flutter/flutter/blob/v1.0.0/packages/flutter_tools/templates/module/ios/library/Flutter.tmpl/podhelper.rb#L43
Also interesting that the crash is happening when CocoaPods is trying to create the header directory, which means the Sandbox root is pointed to the wrong place.
Still looking...

It looks like as of CocoaPods 1.6.0 (the new minimum when the fix to https://github.com/flutter/flutter/issues/20685 finally merges) it no longer tries to create that directory in the add_files -> add_file HeaderStore path.  Which doesn't mean the problem is fixed, but that it will manifest in possibly other weird ways and no longer throw in the same spot.
https://github.com/CocoaPods/CocoaPods/commit/a49d2f70b11da1392f286c4575f638ceba9a268c

I wasn't able to repro with the original Flutter 0.5.1 and CocoaPods 1.5.3, even on the referenced FlutterCasts project.
Is anyone still seeing this or a similar issue on CocoaPods >1.6.0 since that's the new minimum, and CocoaPods no longer will crash in the same place?

I have a similar issue: besides versions in pubspec.yaml, CocoaPods resolves several to 0.0.1:
pubspec.yaml
environment:
sdk: ">=2.4.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
url_launcher: ^5.1.6
cupertino_icons: ^0.1.2
font_awesome_flutter: ^8.5.0
http: ^0.12.0+2
firebase_analytics: ^5.0.2
firebase_auth: ^0.14.0+5
firebase_core: ^0.4.0+9
firebase_database: ^3.0.7
firebase_storage: ^3.0.6
firebase_dynamic_links: ^0.5.0+1
google_sign_in: ^4.0.7
flutter_web_browser: ^0.11.0
path_provider: ^1.3.0
flutter_rating: ^0.0.2
image: ^2.1.4
cached_network_image: ^1.1.1
modal_progress_hud: ^0.1.3
file: ^5.1.0
connectivity: ^0.4.4
photo_view: ^0.5.0
package_info: ^0.4.0+6
flutter_html: ^0.11.0
percent_indicator: ^2.1.1+1
charts_flutter: ^0.8.1
catcher: ^0.2.4 #TODO: 0.2.7 conflitou
shared_preferences: ^0.5.3+4
uuid: ^2.0.1
device_info: ^0.4.0+3
Podfile
platform :ios, '9.0'
ENV['COCOAPODS_DISABLE_STATS'] = 'true'
project 'Runner', {
'Debug' => :debug,
'Profile' => :release,
'Release' => :release,
}
def parse_KV_file(file, separator='=')
file_abs_path = File.expand_path(file)
if !File.exists? file_abs_path
return [];
end
pods_ary = []
skip_line_start_symbols = ["#", "/"]
File.foreach(file_abs_path) { |line|
next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
plugin = line.split(pattern=separator)
if plugin.length == 2
podname = plugin[0].strip()
path = plugin[1].strip()
podpath = File.expand_path("#{path}", file_abs_path)
pods_ary.push({:name => podname, :path => podpath});
else
puts "Invalid plugin specification: #{line}"
end
}
return pods_ary
end
target 'Runner' do
system('rm -rf .symlinks')
system('mkdir -p .symlinks/plugins')
generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
if generated_xcode_build_settings.empty?
puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first."
end
generated_xcode_build_settings.map { |p|
if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
symlink = File.join('.symlinks', 'flutter')
File.symlink(File.dirname(p[:path]), symlink)
pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
end
}
plugin_pods = parse_KV_file('../.flutter-plugins')
plugin_pods.map { |p|
symlink = File.join('.symlinks', 'plugins', p[:name])
File.symlink(p[:path], symlink)
pod p[:name], :path => File.join(symlink, 'ios')
}
end
install! 'cocoapods', :disable_input_output_paths => true
post_install do |installer|
puts 'Determining pod project minimal deployment target'
pods_project = installer.pods_project
deployment_target_key = 'IPHONEOS_DEPLOYMENT_TARGET'
deployment_targets = pods_project.build_configurations.map{ |config| config.build_settings[deployment_target_key] }
minimal_deployment_target = deployment_targets.min_by{ |version| Gem::Version.new(version) }
puts 'Minimal deployment target is ' + minimal_deployment_target
puts 'Setting each pod deployment target to ' + minimal_deployment_target
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings[deployment_target_key] = minimal_deployment_target
end
end
end
Podfile.lock
PODS:

catcher (0.0.1):

Flutter

connectivity (0.0.1):

Flutter
Reachability

device_info (0.0.1):

Flutter

Firebase/Analytics (6.10.0):

Firebase/Core

Firebase/Auth (6.10.0):

Firebase/CoreOnly
FirebaseAuth (~> 6.3.0)

Firebase/Core (6.10.0):

Firebase/CoreOnly
FirebaseAnalytics (= 6.1.3)

Firebase/CoreOnly (6.10.0):

FirebaseCore (= 6.3.1)

Firebase/Database (6.10.0):

Firebase/CoreOnly
FirebaseDatabase (~> 6.1.1)

Firebase/DynamicLinks (6.10.0):

Firebase/CoreOnly
FirebaseDynamicLinks (~> 4.0.5)

Firebase/Storage (6.10.0):

Firebase/CoreOnly
FirebaseStorage (~> 3.4.1)

firebase_analytics (0.0.1):

Firebase/Analytics (~> 6.0)
Firebase/Core
Flutter

firebase_auth (0.0.1):

Firebase/Auth (~> 6.0)
Firebase/Core
Flutter

firebase_core (0.0.1):

Firebase/Core
Flutter

firebase_database (0.0.1):

Firebase/Database
Flutter

firebase_dynamic_links (0.1.0):

Firebase/DynamicLinks
Flutter

firebase_storage (0.0.1):

Firebase/Storage
Flutter

FirebaseAnalytics (6.1.3):

FirebaseCore (~> 6.3)
FirebaseInstanceID (~> 4.2)
GoogleAppMeasurement (= 6.1.3)
GoogleUtilities/AppDelegateSwizzler (~> 6.0)
GoogleUtilities/MethodSwizzler (~> 6.0)
GoogleUtilities/Network (~> 6.0)
"GoogleUtilities/NSData+zlib (~> 6.0)"
nanopb (~> 0.3.901)

FirebaseAnalyticsInterop (1.4.0)
FirebaseAuth (6.3.0):

FirebaseAuthInterop (~> 1.0)
FirebaseCore (~> 6.2)
GoogleUtilities/AppDelegateSwizzler (~> 6.2)
GoogleUtilities/Environment (~> 6.2)
GTMSessionFetcher/Core (~> 1.1)

FirebaseAuthInterop (1.0.0)
FirebaseCore (6.3.1):

FirebaseCoreDiagnostics (~> 1.0)
FirebaseCoreDiagnosticsInterop (~> 1.0)
GoogleUtilities/Environment (~> 6.2)
GoogleUtilities/Logger (~> 6.2)

FirebaseCoreDiagnostics (1.1.1):

FirebaseCoreDiagnosticsInterop (~> 1.0)
GoogleDataTransportCCTSupport (~> 1.0)
GoogleUtilities/Environment (~> 6.2)
GoogleUtilities/Logger (~> 6.2)
nanopb (~> 0.3.901)

FirebaseCoreDiagnosticsInterop (1.0.0)
FirebaseDatabase (6.1.1):

FirebaseAuthInterop (~> 1.0)
FirebaseCore (~> 6.0)
leveldb-library (~> 1.22)

FirebaseDynamicLinks (4.0.5):

FirebaseAnalyticsInterop (~> 1.3)
FirebaseCore (~> 6.2)

FirebaseInstanceID (4.2.5):

FirebaseCore (~> 6.0)
GoogleUtilities/Environment (~> 6.0)
GoogleUtilities/UserDefaults (~> 6.0)

FirebaseStorage (3.4.1):

FirebaseAuthInterop (~> 1.0)
FirebaseCore (~> 6.0)
GTMSessionFetcher/Core (~> 1.1)

Flutter (1.0.0)
flutter_local_notifications (0.0.1):

Flutter

flutter_mailer (0.0.1):

Flutter

flutter_web_browser (0.11.0):

Flutter

fluttertoast (0.0.2):

Flutter

FMDB (2.7.5):

FMDB/standard (= 2.7.5)

FMDB/standard (2.7.5)
google_sign_in (0.0.1):

Flutter
GoogleSignIn (~> 4.0)

GoogleAppMeasurement (6.1.3):

GoogleUtilities/AppDelegateSwizzler (~> 6.0)
GoogleUtilities/MethodSwizzler (~> 6.0)
GoogleUtilities/Network (~> 6.0)
"GoogleUtilities/NSData+zlib (~> 6.0)"
nanopb (~> 0.3.901)

GoogleDataTransport (3.0.1)
GoogleDataTransportCCTSupport (1.2.1):

GoogleDataTransport (~> 3.0)
nanopb (~> 0.3.901)

GoogleSignIn (4.4.0):

"GoogleToolboxForMac/NSDictionary+URLArguments (~> 2.1)"
"GoogleToolboxForMac/NSString+URLArguments (~> 2.1)"
GTMSessionFetcher/Core (~> 1.1)

GoogleToolboxForMac/DebugUtils (2.2.1):

GoogleToolboxForMac/Defines (= 2.2.1)

GoogleToolboxForMac/Defines (2.2.1)
"GoogleToolboxForMac/NSDictionary+URLArguments (2.2.1)":

GoogleToolboxForMac/DebugUtils (= 2.2.1)
GoogleToolboxForMac/Defines (= 2.2.1)
"GoogleToolboxForMac/NSString+URLArguments (= 2.2.1)"

"GoogleToolboxForMac/NSString+URLArguments (2.2.1)"
GoogleUtilities/AppDelegateSwizzler (6.3.1):

GoogleUtilities/Environment
GoogleUtilities/Logger
GoogleUtilities/Network

GoogleUtilities/Environment (6.3.1)
GoogleUtilities/Logger (6.3.1):

GoogleUtilities/Environment

GoogleUtilities/MethodSwizzler (6.3.1):

GoogleUtilities/Logger

GoogleUtilities/Network (6.3.1):

GoogleUtilities/Logger
"GoogleUtilities/NSData+zlib"
GoogleUtilities/Reachability

"GoogleUtilities/NSData+zlib (6.3.1)"
GoogleUtilities/Reachability (6.3.1):

GoogleUtilities/Logger

GoogleUtilities/UserDefaults (6.3.1):

GoogleUtilities/Logger

GTMSessionFetcher/Core (1.2.2)
leveldb-library (1.22)
nanopb (0.3.901):

nanopb/decode (= 0.3.901)
nanopb/encode (= 0.3.901)

nanopb/decode (0.3.901)
nanopb/encode (0.3.901)
package_info (0.0.1):

Flutter

path_provider (0.0.1):

Flutter

Reachability (3.2)
shared_preferences (0.0.1):

Flutter

sqflite (0.0.1):

Flutter
FMDB (~> 2.7.2)

url_launcher (0.0.1):

Flutter

I have a similar issue

What does the crash look like now?  See my above comment about not expecting the crash to happen in the same place as of CocoaPods 1.6.0.  https://github.com/flutter/flutter/issues/19338#issuecomment-499203205

CocoaPods resolves several to 0.0.1.

That's expected.  Flutter plugins' source are downloaded from pub as local "development" pods, not from CocoaPod's spec repo.  That means there's no need for real version resolution since that's already done by pub based on the requested versions in your pubspec.  That means they report as 0.0.1 from CocoaPod's perspective.

What does the crash look like now? See my above comment about not expecting the crash to happen in the same place as of CocoaPods 1.6.0. #19338 (comment)

I see, but should I do something about it?

That's expected.

Ok, thank you.

I see, but should I do something about it?

If you have a crash log similar to the originators that shows what directory is "Permission denied", that would be very helpful so I can see where it's popping up now.

I think I granted chmod 777 some months ago.
Currently the only issue was the 0.0.1, but no worries since That's expected.
Thanks

this is my flutter app
I run the "flutter run" then...
Launching lib/main.dart on iPhone Xʀ in debug mode...
Running pod install... 3.3s
CocoaPods' output:
↳
Preparing
Analyzing dependencies
Inspecting targets to integrate
Using ARCHS setting to build architectures of target Pods-Runner: (``)
Finding Podfile changes
R share_extend
M Flutter

city_pickers
fluttertoast
image_picker
local_auth
path_provider
screen
shared_preferences
tobias
url_launcher
video_player
webview_flutter

Fetching external sources
-> Fetching podspec for Flutter from .symlinks/flutter/ios
-> Fetching podspec for city_pickers from .symlinks/plugins/city_pickers/ios
-> Fetching podspec for fluttertoast from .symlinks/plugins/fluttertoast/ios
-> Fetching podspec for image_picker from .symlinks/plugins/image_picker/ios
-> Fetching podspec for local_auth from .symlinks/plugins/local_auth/ios
-> Fetching podspec for path_provider from .symlinks/plugins/path_provider/ios
-> Fetching podspec for screen from .symlinks/plugins/screen/ios
-> Fetching podspec for shared_preferences from .symlinks/plugins/shared_preferences/ios
-> Fetching podspec for tobias from .symlinks/plugins/tobias/ios
-> Fetching podspec for url_launcher from .symlinks/plugins/url_launcher/ios
-> Fetching podspec for video_player from .symlinks/plugins/video_player/ios
-> Fetching podspec for webview_flutter from .symlinks/plugins/webview_flutter/ios
Resolving dependencies of Podfile
――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
Command
/usr/local/Cellar/cocoapods/1.6.1/libexec/bin/pod install --verbose

Report

What did you do?

What did you expect to happen?

What happened instead?

Stack
   CocoaPods : 1.6.1
        Ruby : ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin18]
    RubyGems : <IP_ADDRESS>
        Host : Mac OS X 10.14.3 (18D42)
       Xcode : 10.3 (10G8)
         Git : git version 2.20.1 (Apple Git-117)
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @
fa40c3663865a308f86d49a5ca75baf88940fc2a

Plugins
cocoapods-deintegrate : 1.0.3
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.1.0
cocoapods-trunk       : 1.3.1
cocoapods-try         : 1.1.0

Podfile
# Uncomment this line to define a global platform for your project
# platform :ios, '9.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 parse_KV_file(file, separator='=')
  file_abs_path = File.expand_path(file)
  if !File.exists? file_abs_path
    return [];
  end
  pods_ary = []
  skip_line_start_symbols = ["#", "/"]
  File.foreach(file_abs_path) { |line|
      next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
      plugin = line.split(pattern=separator)
      if plugin.length == 2
        podname = plugin[0].strip()
        path = plugin[1].strip()
        podpath = File.expand_path("#{path}", file_abs_path)
        pods_ary.push({:name => podname, :path => podpath});
      else
        puts "Invalid plugin specification: #{line}"
      end
  }
  return pods_ary
end

target 'Runner' do
  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')

  # Flutter Pods
  generated_xcode_build_settings = parse_KV_file('./Flutter/Generated.xcconfig')
  if generated_xcode_build_settings.empty?
    puts "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter
    pub get is executed first."
  end
  generated_xcode_build_settings.map { |p|
    if p[:name] == 'FLUTTER_FRAMEWORK_DIR'
      symlink = File.join('.symlinks', 'flutter')
      File.symlink(File.dirname(p[:path]), symlink)
      pod 'Flutter', :path => File.join(symlink, File.basename(p[:path]))
    end
  }

  # Plugin Pods
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.map { |p|
    symlink = File.join('.symlinks', 'plugins', p[:name])
    File.symlink(p[:path], symlink)
    pod p[:name], :path => File.join(symlink, 'ios')
  }
end

# Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new
Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
  end
end

Error
Pod::StandardError - [Bug] Failed to find known source with the URL "trunk"
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-core-1.6.1/lib/cocoapods-core/source/manage
r.rb:38:in `aggregate_for_dependency'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:402:in
`aggregate_for_dependency'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:392:in
`create_set_from_sources'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:361:in
`find_cached_set'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:335:in
`specifications_for_dependency'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:142:in
`search_for'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:251:in
`block in sort_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:244:in
`each'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:244:in
`sort_by'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:244:in
`sort_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/delegates/specification
_provider.rb:53:in `block in sort_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/delegates/specification
_provider.rb:70:in `with_no_such_dependency_error_handling'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/delegates/specification
_provider.rb:52:in `sort_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:754:in
`push_state_for_requirements'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:746:in
`require_nested_dependencies_for'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:729:in
`activate_new_spec'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:686:in
`attempt_to_activate'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:254:in
`process_topmost_state'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:182:in
`resolve'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/molinillo-0.6.6/lib/molinillo/resolver.rb:43:in
`resolve'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/resolver.rb:91:in
`resolve'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer/analyzer.rb:9
09:in `block in resolve_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/user_interface.rb:64:in
`section'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer/analyzer.rb:9
07:in `resolve_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer/analyzer.rb:1
14:in `analyze'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer.rb:266:in
`analyze'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer.rb:174:in
`block in resolve_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/user_interface.rb:64:in
`section'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer.rb:173:in
`resolve_dependencies'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/installer.rb:136:in
`install!'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/command/install.rb:48:i
n `run'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/lib/cocoapods/command.rb:52:in `run'
/usr/local/Cellar/cocoapods/1.6.1/libexec/gems/cocoapods-1.6.1/bin/pod:55:in `<top (required)>'
/usr/local/Cellar/cocoapods/1.6.1/libexec/bin/pod:22:in `load'
/usr/local/Cellar/cocoapods/1.6.1/libexec/bin/pod:22:in `<main>'

――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
[!] Oh no, an error occurred.
Search for existing GitHub issues similar to yours:
https://github.com/CocoaPods/CocoaPods/search?q=[Bug]+Failed+to+find+known+source+with+the+URL+%
22trunk%22&type=Issues
If none exists, create a ticket, with the template displayed above, on:
https://github.com/CocoaPods/CocoaPods/issues/new
Be sure to first read the contributing guide for details on how to properly submit a ticket:
https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md
Don't forget to anonymize any private data!
Looking for related issues on cocoapods/cocoapods...

Pod install returning error
https://github.com/CocoaPods/CocoaPods/issues/2944 [closed] [3 comments]
15 Dec 2014
Error output from CocoaPods:
↳
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/universal-darwin18/rbconfi
g.rb:215: warning: Insecure world writable dir /Users/dwh/Desktop in PATH, mode 040777
[!] The version of CocoaPods used to generate the lockfile (1.8.4) is higher than the version of the
current executable (1.6.1). Incompatibility issues may arise.

[!] Automatically assigning platform ios with version 8.0 on target Runner because no platform
was specified. Please specify a platform for this target in your Podfile. See
https://guides.cocoapods.org/syntax/podfile.html#platform.
Error running pod install
Error launching application on iPhone Xʀ.

@aboutmydreams That looks like a different issue, you might want to file a new issue against CocoaPods as their error suggests.
Also, try upgrading CoocaPods and checking out their new CDN feature so you won't need a local trunk repo http://blog.cocoapods.org/CocoaPods-1.8.0-beta/

It's not flutter problem, Remove Some Plugins that's well be Ok

Try removing local_auth plugin.


[Task] Add Activate button on new installation

Add an Activate button when extension gets installed for the first time.

@robertohuertasm Misspelled title deliberately to see if you are watching. 👅


When the page is increase, the animation for bar stepper is working fine but when the page is decrease, the animation look very bad

Actually, there is no animation for page decreasing, it's designed like this. What animation do you want?

actually, the stepindicator in android looks the same as in IOS and on their library, they have an animation for decreasing the page. I thought that we would have this animation too. but if we don't have it, I still use it though! awesome library
stepIndicator on Android https://github.com/badoualy/stepper-indicator


Fix str-related issues with new Language setting

See the explanation in the commit messages.

Hm ... something is still not right.  Moving back to draft ...

Ah, found the other macro usage in the Search Filter

Thanks. Just noticed these.


fix: add Albala and 2wcom MIBs

:tada: This PR is included in version 1.15.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Introduction to Figma Part 1-What is Figma?

In this we need a documentation or a video tutorial showing Figma user interface and tool collection. You can show what each panel, button, and workspace area does. It's an essential first step in learning how to use Figma, so let’s get started.
Note :
Folder Structure should be UI_UX/Introduction_to_Figma/Part_1  & changes should be made to  UI_UX branch.
Issue only for GWOC'21 contributors.
Issue will be assigned on a first come first serve basis, 1 Issue == 1 PR.
In the PR, keep this issue's title as your PR's title.
Must Follow : Contributing Guidelines & Code of Conduct before start Contributing

@Debasmita-01 Can I work on this?

@Debasmita-01 Can I work on this?

Sure! you are assigned

Hey, I have created a PR, can you review it?

Can I work on this issue?

Can I contribute my skills on this issue?

Can I work on this issue?

Yes u can we will merge the best one

Can I work on this issue?

assigning but the best one will be merged

@Debasmita-01 Do you have any suggestions for changes in my current PR? I'll improve on it.

You didnt add any images right ? I think for a documentation to be
understood very clearly you should add some images also for clear
explanation ..
On Thu, Sep 16, 2021 at 11:32 AM Asmit Malakannawar <
@.***> wrote:

@Debasmita-01 https://github.com/Debasmita-01 Do you have any
suggestions for changes in my current PR? I'll improve on it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/girlscript/winter-of-contributing/issues/87#issuecomment-920603324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQI2AXZUOMVAW5I72WBEYATUCGB7FANCNFSM5EBSZ4TA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You didnt add any images right ? I think for a documentation to be understood very clearly you should add some images also for clear explanation ..

Ok sure, will make changes right now.

You didnt add any images right ? I think for a documentation to be understood very clearly you should add some images also for clear explanation ..

I made changes as requested, please go through my  PR.

You didnt add any images right ? I think for a documentation to be understood very clearly you should add some images also for clear explanation ..

I made changes as requested, please go through my PR.

PLease add demos or screenshots from your own figma account bcoz that will prove you tried on your own . I saw some screenshots which are for different accounts

You didnt add any images right ? I think for a documentation to be understood very clearly you should add some images also for clear explanation ..

I made changes as requested, please go through my PR.

PLease add demos or screenshots from your own figma account bcoz that will prove you tried on your own . I saw some screenshots which are for different accounts

Well one screenshot was for collaborations and I don't have any collaborators to work with on figma, that screenshot is from their official site, should I change that or remove it completely?

/assign

/assign

can I contribute in documentation?

Look for other issues please . This issue cant be assigned to more than 3 people .

I'll unassign myself as the PR has been merged


Add correct settings documentation

Coverage decreased (-0.03%) to 78.058% when pulling 6ea2cfc16173002c326a40758b85da05d5a6928a on eatonphil:fix-account-settings-docs into 6700c5e9c55df090acde8b6ca218141bdf27abce on linode:master.

Coverage decreased (-0.03%) to 78.058% when pulling 6ea2cfc16173002c326a40758b85da05d5a6928a on eatonphil:fix-account-settings-docs into 6700c5e9c55df090acde8b6ca218141bdf27abce on linode:master.

Coverage remained the same at 78.084% when pulling 6ec766f61428467078a18d35a0d174e5f76b8e77 on eatonphil:fix-account-settings-docs into 6700c5e9c55df090acde8b6ca218141bdf27abce on linode:master.

@abemassry nope, go ahead and squash and merge.


FILTER Clauses for Aggregates

This PR implements support for FILTER clauses in aggregations:
SELECT SUM(COL1) FILTER(WHERE COL2 > 300), AVG(COL2) FILTER (WHERE COL2 < 50) FROM MyTable WHERE COL1 > 50;
The approach implements the swim lane design highlighted in the design document by splitting at the filter operator. The implementation gets the filter block for main predicate and each filter predicate, ANDs them together and returns a combined filter operator.
The main predicate is scanned only once and reused for all filter clauses.
The implementation allows each filter swim lane to use any available indices independently.
If two or more filter clauses have the same predicate, the result will be computed only once and fed to each of the aggregates.
https://docs.google.com/document/d/1ZM-2c0jJkbeJ61m8sJF0qj19t5UYLhnTFvIAz-HCJmk/edit?usp=sharing
Performance benchmark:
3 warm up iterations per run, 5 runs in total. Data set size -- 1.5 million documents. Apple M1 Pro, 32GB RAM
X axis represents number of iterations and Y axis represents latency in MS.
FILTER query, compared to its equivalent CASE query, is 120-140% faster on average.

GROUP BY is not supported yet and will be done in a follow up PR

Codecov Report

Merging #7916 (a898d99) into master (47e49ec) will decrease coverage by 57.30%.
The diff coverage is 0.29%.

@@              Coverage Diff              @@
##             master    #7916       +/-   ##
=============================================
- Coverage     71.63%   14.32%   -57.31%
+ Complexity     4088       80     -4008
=============================================
  Files          1580     1551       -29
  Lines         81100    80528      -572
  Branches      12068    12098       +30
=============================================
- Hits          58093    11537    -46556
- Misses        19092    68135    +49043
+ Partials       3915      856     -3059

Flag
Coverage Δ

integration1
?

integration2
?

unittests1
?

unittests2
14.32% <0.29%> (-0.24%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...apache/pinot/core/operator/ProjectionOperator.java
0.00% <0.00%> (-84.62%)
:arrow_down:

.../pinot/core/operator/SwimLaneDocIdSetOperator.java
0.00% <0.00%> (ø)

...inot/core/operator/blocks/CombinedFilterBlock.java
0.00% <0.00%> (ø)

...t/core/operator/blocks/CombinedTransformBlock.java
0.00% <0.00%> (ø)

...he/pinot/core/operator/blocks/ProjectionBlock.java
0.00% <0.00%> (-60.00%)
:arrow_down:

...che/pinot/core/operator/blocks/TransformBlock.java
0.00% <0.00%> (-69.24%)
:arrow_down:

...t/core/operator/filter/CombinedFilterOperator.java
0.00% <0.00%> (ø)

...pinot/core/operator/query/AggregationOperator.java
0.00% <0.00%> (-92.00%)
:arrow_down:

.../operator/transform/CombinedTransformOperator.java
0.00% <0.00%> (ø)

...t/core/plan/AggregationGroupByOrderByPlanNode.java
0.00% <0.00%> (-45.46%)
:arrow_down:

... and 1292 more

Continue to review full report at Codecov.

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

Thanks you @atris !

@Jackie-Jiang is working on a parallel implementation, so closing this PR to avoid conflict

Discussed with @Jackie-Jiang and we will be convening on this PR itself, so reviving it. Sorry for the confusion.

@atris This is a great feature. Could you please add some release notes to the PR description which we can refer to when cutting the next release?

Is IN_SUBQUERY inside FILTER supported ?
For example:
SELECT  	SUM(value) FILTER(WHERE IN_SUBQUERY(entityId, 'SELECT ID_SET(entityId) FROM other_table WHERE cond = <thing>') = 1) FROM table

No it is not supported. For the example you give, SELECT SUM(value) WHERE IN_SUBQUERY(entityId, 'SELECT ID_SET(entityId) FROM other_table WHERE cond = <thing>') = 1 FROM table should work

Thanks for the confirmation @Jackie-Jiang
Yes that's what we're using right now, but we've got a use case where we may have hundreds of sub sub query entities, which are currently translated into hundreds of Pinot queries so I was looking for a way to improve that :)

Let me see if I can take a crack on this next week
On Sat, 9 Apr 2022, 20:54 MrNeocore, @.***> wrote:

Thanks for the confirmation @Jackie-Jiang
https://github.com/Jackie-Jiang
Yes that's what we're using right now, but we've got a use case where we
may have hundreds of sub sub query entities, which are currently translated
into hundreds of Pinot queries so I was looking for a way to improve that :)
—
Reply to this email directly, view it on GitHub
https://github.com/apache/pinot/pull/7916#issuecomment-1094066573, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANE5Y2RJWTAR3BY2G4S7S3VEGOKHANCNFSM5KGGHAHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for giving it a shot @atris

@atris did we add this to our docs?


PHPC-1294: Connections survive primary step-down

https://jira.mongodb.org/browse/PHPC-1294
Note: this builds on work done in #669.

FYI: I opened https://github.com/mongodb/specifications/pull/634 to clarify topology requirements in the spec test.

@jmikola it looks like the getMoreIteration test causes failures down the line, which unfortunately only appear when running the entire test suite. These errors disappear when skipping that test. Looking at the replica set configuration, it seems likely that there is in fact another step down sometime after running that initial step down: the first replica set member has a significantly higher priority, and in my local tests I was able to confirm that the first server becomes primary a short while after stepping down.
I'm not sure how to best fix this: giving the replica set members the same priority would definitely prevent another step down. The alternative is making the server step down for significantly longer than 5 seconds while hoping that there is no other step down during the tests. What do you think?

the first replica set member has a significantly higher priority

IIRC, the priorities were configured as such for PHPC since it had some tests that select primary or secondary nodes and assert their tags. Those are inherently fragile tests and I'm dubious of how much value they provide, but beyond that I don't think they have any relevance to PHPLIB. It's only coming up now because we evidently based the PHPLIB cluster configs on what we already had for PHPC.
I'd suggest removing the priority definitions and confirming that it has no adverse affects on the rest of the PHPLIB test suite (AFAIK, it should not). Bumping the replSetStepDown value higher may work today, but IMO it would just be kicking the can further down the road and invite a failure if our test suite runs beyond that delay.

I just realized that this was originally a PHPC ticket but you chose to implement in PHPLIB. If so, let's move the JIRA issue over to PHPLIB and revise the commit message.
It bears mentioning that we do have some existing tests in PHPC that start their own servers with MO, but those are mainly creating standalones to test fail points. I think you made the right call to use our existing cluster for these tests. This could have probably been implemented as phpt tests in PHPC, but your decision to use PHPLIB does avoid a possible conflict with fragile replica set tag tests I mentioned above, so all is well there :)


Update agora_rtm_client.dart

changed callMethodForStatic("getSdkVersion", null) to callMethodForStatic("getSdkVersion", {})

Tanks for you PR, this bug has been fixed


Ho to check the copy of a mock?

I have this mocked object in my test:
private val model: UiModel = mock { on{ status } doReturn PURCHASED }
and I want to test the return of this method:
fun refreshStatus(model: UiModel): UiModel { return model.copy(status = CANCELLED) }
I want to check if that new uiModel has updated the status, but it seems that copy method over a mock is returning null
val model = mapper.refreshStatus(uiModel)
assertEquals(model.status, CANCELLED)
Is this possible or even make sense?

You don't need a mock of your model. You should just pass in a regular model with status set to PURCHASED or am I missing something?

I was refactoring to Kotlin some clases and tests and wasn't sure if that test make sense at all. Thanks for answering anyway, I'm still learning abut kotlin and how to do proper unit tests with it's specific methods like .copy().


League/CSV Version 9

Affected Version
Silverstripe 4.3
Description
wasn't leavue/csv not upgraded to v9 in #7937

Hi @chromos33

tractorcow merged 1 commit into silverstripe:master from dhensby:pulls/5/csv-upgrade

It has been updated in master, which is a branch for SilverStripe 5.
To be in SilverStripe 4 it should have been merged into either 4.* or 4.


Custom Form Field Guide code not working

Bug, feature request, or proposal:
The code in the guide to creating custom form field seems to be broken (in Angular 5) and esp. in the provided StackBlitz
What is the expected behavior?
When opening the example in StackBlitz it should work as it does on the guide page
What is the current behavior?
First the form-field-custom-control-example.html in the StackBlitz link is empty which leads to a fatal error and second, even if the HTML provided in the guide is used, it does not show any placeholder or dashes.
What are the steps to reproduce?
Link from the guide: https://stackblitz.com/angular/pmbqmxogbyb
The problem seems to be that in Angular 5 FocusMonitor.monitor() takes three parameters, whereas only 2 are provided (line 106)

This has been fixed, the docs site now links to a working example: https://stackblitz.com/angular/earajmpqaoxx


!ledger documentation

According to the readme, the command for the ledger query should be "!let", although it is actually "!led".
The ledger function is not mentioned in the !help output

Fixed in main branch


Add config option for setting title of the blog sidebar

Motivation
This seems like one of the only (or the only) pieces of copy that I couldn't configure myself. I wanted to change the casing of the sidebar title.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Config:

Preview in UI:

Related PRs
https://github.com/facebook/Docusaurus/pull/432

@JoelMarcey nope I just put proposal in the title for meta so your team could decide if you wanted to accept it. Let me know if there's any changes you'd like from my end? I know there's no tests in here, but unless I missed them, I couldn't see any existing place in the codebase that had similar tests to which I could add.

I reran the job with SSH and Prettier was passing. Seems to be fine. Gonna merge this.


add_func_to_frame

we don't want function closures to be in boxes:
; Add a new variable/value pair to the frame.
(define add-func-to-frame
  (lambda (name closure frame)
    (list (cons name (variables frame)) (cons closure (store frame)))))

closed by #81


Update to forked sdk v0.38.2, with restart bugfix

Closes #54
While waiting for upstream fix, use confio fork, that takes in the upstream fix to the iavl/restart issue and a few minor debugging enhancements I came across.

Targeted PR against correct branch (see CONTRIBUTING.md)

[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.

[ ] Wrote tests

[ ] Updated relevant documentation (docs/)

[ ] Added  relevant godoc comments.

[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md

[ ] Re-reviewed Files changed in the Github PR explorer

For admin use:

[ ] Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
[ ] Reviewers assigned
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

Codecov Report

Merging #66 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master     #66      +/-   ##
=========================================
+ Coverage   63.44%   63.5%   +0.06%
=========================================
  Files          14      14
  Lines        1116    1118       +2
=========================================
+ Hits          708     710       +2
  Misses        341     341
  Partials       67      67

Impacted Files
Coverage Δ

app/app.go
89.09% <100%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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


Race condition between sample capture and jitdump record

I'm observing a scenario where samply has samples that are timestamped before the timestamp of the relevant jitdump record, causing the sample to not be resolved. This is on macOS, M3 Max, with CoreCLR. I frequently see samples with a timestamp that's 35µs, 75µs, etc. before the jitdump record.
My theory is that this is due to the sample interval, and with samples being timestamped with the start of their interval, instead of the end. Sequence of events that I think is happening:

samply captures get_monotonic_timestamp() for a sample in mac Sampler::run
a. (side note -- on macOS, there is clock_gettime_nsec_np(CLOCK_UPTIME_RAW) which is defined to be the same as mach_absolute_time() after appropriate timebase-info conversion; should maybe use this instead of the low-level mach functions?)
samply starts looping through tasks, calling task.sample
In the interval between get_monotonic_timestamp() and actually sampling the task's threads, the JIT finished compiling something, emitted a jitdump record, and jumped to the JIT code that is now being sampled.

If I replace the captured sample's now_mono in ThreadPorfiler::sample_impl with a call to get_monotonic_timestamp(), thus timestamping the sample with the time immediately after it was captured, all the JIT resolution issues go away.

Oh! Thanks for debugging this, I've been wondering why some of the JIT functions weren't being symbolicated properly!
I'd be happy to accept a patch to change the sample time as you described.


Ci

Why are we still building these on drone?

only the staging is on drone, I'm mostly updating to add a tag since I pull a tag on jenkins.


Guidance for Interactive rebase for removing commit

@annazietlow, @rozele and @TessFerrandez , please review this.

@annazietlow, @rozele and @TessFerrandez , please review this.


Prepare for multilanguage support

Move strings from code to resource files and replace usings.

Closed. Would be to much effort to make a full multilanguage support including the cards


refactor(semantic): update the order of visit_function and Visit fields in the builder to be consistent

#4248  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Canary Upgrades - 415: Unsupported Media Type

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[X] Upgrade
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[X] Multi Control Plane
Expected behavior
Canary Upgrades from 1.8.1 to 1.9.2 success
Steps to reproduce the bug

istioctl install --set revision=1-9-2

error log is:
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/v1.9/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
! Istio is being downgraded from 1.8.1 -> 1.9.2.This will install the Istio 1.9.2  profile with ["Istio core" "Istiod" "Ingress gateways"] components into the cluster. Proceed? (y/N) y
2021-04-02T08:40:59.803058Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//authorizationpolicies.security.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.813983Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//destinationrules.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.816998Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//envoyfilters.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.819203Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//gateways.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.820706Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//istiooperators.install.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.822282Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//peerauthentications.security.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.823921Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//requestauthentications.security.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.830659Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//serviceentries.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.858794Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//sidecars.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.866766Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//virtualservices.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.868516Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//workloadentries.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.871417Z     error   installer       failed to update resource with server-side apply for obj CustomResourceDefinition//workloadgroups.networking.istio.io: 415: Unsupported Media Type
2021-04-02T08:40:59.872403Z     error   installer       failed to update resource with server-side apply for obj ServiceAccount/istio-system/istio-reader-service-account: 415: Unsupported Media Type
2021-04-02T08:40:59.873259Z     error   installer       failed to update resource with server-side apply for obj ServiceAccount/istio-system/istiod-service-account: 415: Unsupported Media Type
2021-04-02T08:40:59.874532Z     error   installer       failed to update resource with server-side apply for obj ClusterRole//istio-reader-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.876326Z     error   installer       failed to update resource with server-side apply for obj ClusterRole//istiod-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.877394Z     error   installer       failed to update resource with server-side apply for obj ClusterRoleBinding//istio-reader-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.878281Z     error   installer       failed to update resource with server-side apply for obj ClusterRoleBinding//istiod-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.879446Z     error   installer       failed to update resource with server-side apply for obj ValidatingWebhookConfiguration//istiod-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.880425Z     error   installer       failed to update resource with server-side apply for obj Role/istio-system/istiod-istio-system: 415: Unsupported Media Type
2021-04-02T08:40:59.881441Z     error   installer       failed to update resource with server-side apply for obj RoleBinding/istio-system/istiod-istio-system: 415: Unsupported Media Type
✘ Istio core encountered an error: failed to update resource with server-side apply for obj CustomResourceDefinition//authorizationpolicies.security.istio.io: 415: Unsupported Media Type
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
istioctl version --remote  output is
client version: 1.9.2
control plane version: 1.8.1
data plane version: 1.8.1 (47 proxies)
kubectl version --short output is
Client Version: v1.15.12
Server Version: v1.19.3
How was Istio installed?
install by istioctl install command
Environment where the bug was observed (cloud vendor, OS, etc)
cloud vendor
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

Can you try kubectl apply -f manifests/charts/base/crds/crd-all.gen.yaml --server-side?
Also what type of k8s are you using? GKE, AKS, EKS, etc?

@howardjohn I use kubectl apply -f manifests/charts/base/crds/crd-all.gen.yaml --server-side, return unknown flag: --server-side
Type of k8s is KCE(KingSoft ksyun), the k8s is native not change code

can you use a newer kubectl version
On Mon, Apr 5, 2021, 7:31 PM Haiker Sun @.***> wrote:

@howardjohn https://github.com/howardjohn I use kubectl apply -f
manifests/charts/base/crds/crd-all.gen.yaml --server-side, return unknown
flag: --server-side
Type of k8s is KCE(KingSoft ksyun), the k8s is native not change code
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31867#issuecomment-813777899, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJHZD3EFTC4434MJ6TTHJXA3ANCNFSM42IQ5URA
.

I try kubectl apply -f manifests/charts/base/crds/crd-all.gen.yaml --server-side, return
Server-side apply not available on the server:  (415: Unsupported Media Type)

I think your k8s cluster had server side apply disabled?

I find server side apply disabled, istioctl install canary upgrades must enable server side apply?

Yes, in the code today. @richardwxn is it possible to check if SSA is enabled instead of checking the version?

https://github.com/istio/istio/pull/32189 fixes this


InternalServerError when trying to create an exclusive constraint at base type

EdgeDB Version: 2.1+52c90a7 (repl 2.1.0-dev.837+77d7d80)
OS Version: Mac m1 Kernel Version 21.6.0

Run this in any way edgedb migrate or manually:
CREATE MIGRATION m1tnwlplgljiafydd3xfu7ks7syxrmp6pwyzigtxv3n4ssseibzfla
    ONTO initial
{
  CREATE TYPE default::MenuItem {
      CREATE MULTI LINK children -> default::MenuItem;
      CREATE REQUIRED PROPERTY name -> std::str;
      CREATE PROPERTY page -> std::str;
  };
  CREATE TYPE default::Menu {
      CREATE CONSTRAINT std::exclusive;
      CREATE REQUIRED LINK item -> default::MenuItem;
  };
};

Output:
Error: InternalServerError: syntax error at or near "."
  Hint: This is most likely a bug in EdgeDB. Please consider opening an issue ticket at https://github.com/edgedb/edgedb/issues/new?template=bug_report.md

Oh. exclusive, when defined on a type requires an expression, e.g. exclusive on (.foo).

The confusing ISE is a bug, of course.

Oh. exclusive, when defined on a type requires an expression

That's not what the migration generator thinks.

I didn't generate the migration, EdgeDB gladly liked my .esdl and created that blob above.

That's the bug I was referring to.  Your schema should have been rejected.


Array based implementation of Queue can suffer from Integer Overflows

In the implementation of ArrayQueue.java, the data structure can suffer from INTEGER overflows because the index adjusting function head() returns integers larger than the length of the array. Hypothetically, if I choose to initialize ArrayQueue(Integer.MAX_VALUE), the data structure will suffer from overflows after a few dequeue() operations.

The issue has been fixed in the latest master branch.


disable BuildConfig generation

This is a tiny build performance improvement.
BuildConfig.java isn't generated and packaged into the aar file so client apps don't have to strip it from the final apk again.
Note, this is technically a breaking change as a public class is being removed. One that nobody should reference, but still.

Thanks, I will merge it for the next minor (or major) release


Add timestamps to top-level pipelines

This is to pass PIPELINE_TIMESTAMP to build jobs (so they can be same across platforms, which will ensure they will be part of the same 'release' set on the website).
Signed-off-by: smlambert<EMAIL_ADDRESS>

Tested out "live" with this pipeline build:
https://ci.adoptopenjdk.net/view/Pipelines/job/openjdk8_openj9_nightly_pipeline_scm/68/console

Verified that build & test jobs work, and the artifacts are properly timestamped (with the exception of the win32 build, as I forgot to update the Jenkins job config for it, updated now).
This fixes the problem we had been seeing where the api link for nightly/latest/binaries would not always return a result (because the nightly builds were not contained in the same github release object, since we changed the pipeline logic to not wait to publish nightlies unless all platforms built).  By matching the timestamps, the build artifacts are now all added to the same github release again.
When this is merged, we need to finish updating the build job configuration in Jenkins (to take the PIPELINE_TIMESTAMP as a parameter, rather than independently set the timestamp in each build job.

Updated to use yyMMdd (as per https://github.com/AdoptOpenJDK/openjdk-website-backend/pull/12).

I have updated all of the build jobs with the extra PIPELINE_TIMESTAMP parameter.

Yes, I was thinking that (common pipeline code) as I created this PR...
I am very certain we can reduce this set (version & impl can be data to these), and I also considered creating a utilities.groovy script where we can put methods like getTimeStamp

@smlambert updating the jobs has caused an issue... we won't be able to kick off jobs on their own anymore as the timestamp won't be generated...
each job will need the following code added at the top to fix this:
[ -z $PIPELINE_TIMESTAMP ] && PIPELINE_TIMESTAMP="$(date +'%Y%d%m%H%M')"

Thanks George, I forgot about the desire to run these jobs independently of the pipeline trigger, I will proceed to update the job configurations as suggested.


simplex-chat: init at 5.8.0

TODO: build from source
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@drupol does this one include the cli chat client? I'm interested aswell in using it.
I saw the upstream has a flake, maybe it is of help to get it to build from source.

Yes, this is only the CLI.
It's in draft because I would like to build it from source. I'll check the upstream flake tomorrow.

@drupol any updates on this?

I decided to not merge this PR because it can't (yet) be built from source. Feel free to re-use this PR on your own, but I prefer not to merge it in nixpkgs.


Broken Link on 'Animation Callbacks'

Last line of the Animations#Animation Callbacks page has a link that is broken.
Pointing to: https://github.com/chartjs/Chart.js/blob/master/samples/animation/progress-bar.html
I think it's supposed to be: https://github.com/chartjs/Chart.js/blob/master/samples/advanced/progress-bar.html

Resolved in #4325

@raquelguimaraes docs for master branch are updated now: http://www.chartjs.org/docs/master/configuration/animations.html


Generate signal not by playing media file

Hi guys,
I have a question about this code library, Is it possible to generate the signal list result without playing the media file? all your demo is to generate  signal when play the file.

I'm not sure exactly what you're asking. NAudio does not require you to play from audio files - you can generate your own sounds. And you don't need to play audio through the sound card. You can use it to generate audio files. Check the tutorials in the main readme for an idea of the scope of what is achievable with NAudio.


[SPARK-23779][SQL] TaskMemoryManager and UnsafeSorter related classes use MemoryBlock

What changes were proposed in this pull request?
This PR tries to use MemoryBlock in TaskMemoryManager and UnsafeSorter related classes. There are two advantages to use MemoryBlock.

Has clean API calls rather than using a Java array or PlatformMemory
Improve runtime performance of memory access instead of using Object with Platform.get/put....

How was this patch tested?
Used existing UTs

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2026/
Test PASSed.

Test build #88969 has finished for PR 20992 at commit 64c5d23.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88969/
Test FAILed.

retest this please

Test build #88995 has started for PR 20992 at commit 64c5d23.

Test build #88995 has finished for PR 20992 at commit 64c5d23.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/88995/
Test FAILed.

Test build #89016 has started for PR 20992 at commit 3d25617.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2064/
Test PASSed.

Test build #89016 has finished for PR 20992 at commit 3d25617.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89016/
Test PASSed.

Merged build finished. Test PASSed.

Test build #89021 has started for PR 20992 at commit 0e1e0a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2069/
Test PASSed.

Test build #89021 has finished for PR 20992 at commit 0e1e0a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89021/
Test PASSed.

@kiszk I did not look at the PR in detail - was curious about the commit saying 'address review comment'; but did not see any comments. Were they removed by submitter ? Or is github acting up ?

@mridulm Thank you for having an interest. Good catch. I made a mistake when I added a comment to the commit. It seems that Fix a wrong assertion is better comment.

retest this please

Test build #89147 has started for PR 20992 at commit 0e1e0a0.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/2174/
Test PASSed.

Merged build finished. Test PASSed.

Test build #89147 has finished for PR 20992 at commit 0e1e0a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/89147/
Test PASSed.

What are the performance improvements? Without additional data this seems like just an invasive change without any real benefits ...

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/15765/
Test PASSed.


Export from Gp file to Midi in Console Application

Hello. How are you.
How can I Export from Guitar Pro file to Midi file in  C# Console Application ?
Thanks.

Hey, It seems that the original author does not follow this repository anymore. I made some changes that can make this program runnable from the terminal and I have created a pull request https://github.com/alexsteb/GuitarPro-to-Midi/pull/3 . If you follow the steps there you can just convert any gp file from the terminal. Hope it helps.

Thanks.