xCode fails to build new react-native init project due to 'library not found for -lDoubleConversion'

I have initiated a new react-native app with the react-native cli (react-native init newproject). The build works if I then run react-native run-ios but if I open the project in xcode (via the .xcodeproj file in the ios folder) then the build fails due to 'library not found for -lDoubleConversion'

React Native version:
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
Memory: 28.45 MB / 8.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 12.5.0 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
IDEs:
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.0 => 0.60.0
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-log-ios: 1.0.1
Steps To Reproduce

react-native init newproject
open ios/newproject.xcodeproj in xcode and build

Describe what you expected to happen:
Build to fail with warning "library not found for -lDoubleConversion"
Snack, code example, or link to a repository:

Please try this. It's work for me in error which I am getting in installing pods.
sudo xcode-select -switch <path/to/>Xcode.app

@shannonjensen Look like your project never run the 'pod install' command.
Do the below steps

go to  ios/
run 'pod install'
open ios/newproject.xcworkspace

Thank you @irshadpc.
I followed those steps and am still getting the same error.

@shannonjensen Can you please share the pod file.

Podfile:
`platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
target 'demoUpgrade' do
Pods for demoUpgrade
pod 'React', :path => '../node_modules/react-native/'
pod 'React-Core', :path => '../node_modules/react-native/React'
pod 'React-DevSupport', :path => '../node_modules/react-native/React'
pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
target 'demoUpgradeTests' do
inherit! :search_paths
# Pods for testing
end
use_native_modules!
end
target 'demoUpgrade-tvOS' do
Pods for demoUpgrade-tvOS
target 'demoUpgrade-tvOSTests' do
inherit! :search_paths
# Pods for testing
end
end
Podfile.lock
PODS:

boost-for-react-native (1.63.0)
DoubleConversion (1.1.6)
Folly (2<IP_ADDRESS>):

boost-for-react-native
DoubleConversion
Folly/Default (= 2<IP_ADDRESS>)
glog

Folly/Default (2<IP_ADDRESS>):

boost-for-react-native
DoubleConversion
glog

glog (0.3.5)
React (0.60.0):

React-Core (= 0.60.0)
React-DevSupport (= 0.60.0)
React-RCTActionSheet (= 0.60.0)
React-RCTAnimation (= 0.60.0)
React-RCTBlob (= 0.60.0)
React-RCTImage (= 0.60.0)
React-RCTLinking (= 0.60.0)
React-RCTNetwork (= 0.60.0)
React-RCTSettings (= 0.60.0)
React-RCTText (= 0.60.0)
React-RCTVibration (= 0.60.0)
React-RCTWebSocket (= 0.60.0)

React-Core (0.60.0):

Folly (= 2<IP_ADDRESS>)
React-cxxreact (= 0.60.0)
React-jsiexecutor (= 0.60.0)
yoga (= 0.60.0.React)

React-cxxreact (0.60.0):

boost-for-react-native (= 1.63.0)
DoubleConversion
Folly (= 2<IP_ADDRESS>)
glog
React-jsinspector (= 0.60.0)

React-DevSupport (0.60.0):

React-Core (= 0.60.0)
React-RCTWebSocket (= 0.60.0)

React-fishhook (0.60.0)
React-jsi (0.60.0):

boost-for-react-native (= 1.63.0)
DoubleConversion
Folly (= 2<IP_ADDRESS>)
glog
React-jsi/Default (= 0.60.0)

React-jsi/Default (0.60.0):

boost-for-react-native (= 1.63.0)
DoubleConversion
Folly (= 2<IP_ADDRESS>)
glog

React-jsiexecutor (0.60.0):

DoubleConversion
Folly (= 2<IP_ADDRESS>)
glog
React-cxxreact (= 0.60.0)
React-jsi (= 0.60.0)

React-jsinspector (0.60.0)
React-RCTActionSheet (0.60.0):

React-Core (= 0.60.0)

React-RCTAnimation (0.60.0):

React-Core (= 0.60.0)

React-RCTBlob (0.60.0):

React-Core (= 0.60.0)
React-RCTNetwork (= 0.60.0)
React-RCTWebSocket (= 0.60.0)

React-RCTImage (0.60.0):

React-Core (= 0.60.0)
React-RCTNetwork (= 0.60.0)

React-RCTLinking (0.60.0):

React-Core (= 0.60.0)

React-RCTNetwork (0.60.0):

React-Core (= 0.60.0)

React-RCTSettings (0.60.0):

React-Core (= 0.60.0)

React-RCTText (0.60.0):

React-Core (= 0.60.0)

React-RCTVibration (0.60.0):

React-Core (= 0.60.0)

React-RCTWebSocket (0.60.0):

React-Core (= 0.60.0)
React-fishhook (= 0.60.0)

yoga (0.60.0.React)

DEPENDENCIES:

DoubleConversion (from ../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec)
Folly (from ../node_modules/react-native/third-party-podspecs/Folly.podspec)
glog (from ../node_modules/react-native/third-party-podspecs/glog.podspec)
React (from ../node_modules/react-native/)
React-Core (from ../node_modules/react-native/React)
React-cxxreact (from ../node_modules/react-native/ReactCommon/cxxreact)
React-DevSupport (from ../node_modules/react-native/React)
React-fishhook (from ../node_modules/react-native/Libraries/fishhook)
React-jsi (from ../node_modules/react-native/ReactCommon/jsi)
React-jsiexecutor (from ../node_modules/react-native/ReactCommon/jsiexecutor)
React-jsinspector (from ../node_modules/react-native/ReactCommon/jsinspector)
React-RCTActionSheet (from ../node_modules/react-native/Libraries/ActionSheetIOS)
React-RCTAnimation (from ../node_modules/react-native/Libraries/NativeAnimation)
React-RCTBlob (from ../node_modules/react-native/Libraries/Blob)
React-RCTImage (from ../node_modules/react-native/Libraries/Image)
React-RCTLinking (from ../node_modules/react-native/Libraries/LinkingIOS)
React-RCTNetwork (from ../node_modules/react-native/Libraries/Network)
React-RCTSettings (from ../node_modules/react-native/Libraries/Settings)
React-RCTText (from ../node_modules/react-native/Libraries/Text)
React-RCTVibration (from ../node_modules/react-native/Libraries/Vibration)
React-RCTWebSocket (from ../node_modules/react-native/Libraries/WebSocket)
yoga (from ../node_modules/react-native/ReactCommon/yoga)

SPEC REPOS:
https://github.com/cocoapods/specs.git:
- boost-for-react-native
EXTERNAL SOURCES:
DoubleConversion:
:podspec: "../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec"
Folly:
:podspec: "../node_modules/react-native/third-party-podspecs/Folly.podspec"
glog:
:podspec: "../node_modules/react-native/third-party-podspecs/glog.podspec"
React:
:path: "../node_modules/react-native/"
React-Core:
:path: "../node_modules/react-native/React"
React-cxxreact:
:path: "../node_modules/react-native/ReactCommon/cxxreact"
React-DevSupport:
:path: "../node_modules/react-native/React"
React-fishhook:
:path: "../node_modules/react-native/Libraries/fishhook"
React-jsi:
:path: "../node_modules/react-native/ReactCommon/jsi"
React-jsiexecutor:
:path: "../node_modules/react-native/ReactCommon/jsiexecutor"
React-jsinspector:
:path: "../node_modules/react-native/ReactCommon/jsinspector"
React-RCTActionSheet:
:path: "../node_modules/react-native/Libraries/ActionSheetIOS"
React-RCTAnimation:
:path: "../node_modules/react-native/Libraries/NativeAnimation"
React-RCTBlob:
:path: "../node_modules/react-native/Libraries/Blob"
React-RCTImage:
:path: "../node_modules/react-native/Libraries/Image"
React-RCTLinking:
:path: "../node_modules/react-native/Libraries/LinkingIOS"
React-RCTNetwork:
:path: "../node_modules/react-native/Libraries/Network"
React-RCTSettings:
:path: "../node_modules/react-native/Libraries/Settings"
React-RCTText:
:path: "../node_modules/react-native/Libraries/Text"
React-RCTVibration:
:path: "../node_modules/react-native/Libraries/Vibration"
React-RCTWebSocket:
:path: "../node_modules/react-native/Libraries/WebSocket"
yoga:
:path: "../node_modules/react-native/ReactCommon/yoga"
SPEC CHECKSUMS:
boost-for-react-native: 39c7adb57c4e60d6c5479dd8623128eb5b3f0f2c
DoubleConversion: 5805e889d232975c086db112ece9ed034df7a0b2
Folly: 30e7936e1c45c08d884aa59369ed951a8e68cf51
glog: 1f3da668190260b06b429bb211bfbee5cd790c28
React: 4b3c068e793e96672dcd186a2b572fac43e4b031
React-Core: 3dc86b22920597f813c62a96db3165950b64826b
React-cxxreact: 0dacb291e59b81e7c3f22a2118bee853ba8a60d2
React-DevSupport: 4eb4135386acd10c2586cc9c759bf96b4dac035e
React-fishhook: 86ca737527bb9d860efbb943c11c729a5b69aa3d
React-jsi: 8e128c4d0d8febc2977ef617d1c09bb54326069c
React-jsiexecutor: 7a3554f703a58963ec80b860144ea0f0e9b910e1
React-jsinspector: d4ed52225912efe0019bb7f1a225aec20f23049a
React-RCTActionSheet: b27ff3cf3a68f917c46d2b94abf938b625b96570
React-RCTAnimation: 9e4708e5bd65fca8285ce7c0aa076f3f4fa5c2f8
React-RCTBlob: 6eafcc3a24f33785692a7be24918ade607bc8719
React-RCTImage: 46b965d7225b428ea11580ead08a4318aef1d6be
React-RCTLinking: d65b9f56cf0b8e171575a86764df7bb019ac28d6
React-RCTNetwork: 783ee2f430740e58f724e46adc79fe7feff64202
React-RCTSettings: aa28315aadfbfaf94206d865673ae509f1e97c07
React-RCTText: 685fca2e13b024271048e7e247ef24476f28a41e
React-RCTVibration: 4ee1cf208ab17a50fafb1c16ffe28fe594a64e4f
React-RCTWebSocket: fca087d583724aa0e5fef7d911f0f2a28d0f2736
yoga: 616fde658be980aa60a2158835170f3f9c2d04b4
PODFILE CHECKSUM: dca13e28f5c4ca875863a7288a10696a04a1c0c2
COCOAPODS: 1.7.4
`

Podfile:
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
target 'demoUpgrade' do
  # Pods for demoUpgrade
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'
  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
 target 'demoUpgradeTests' do
 inherit! :search_paths
# Pods for testing
end
use_native_modules!
end
target 'demoUpgrade-tvOS' do
  # Pods for demoUpgrade-tvOS
 target 'demoUpgrade-tvOSTests' do
 inherit! :search_paths
 # Pods for testing
 end
end

Thank you @irshadpc
Podfile:
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'demoUpgrade' do
  # Pods for demoUpgrade
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  target 'demoUpgradeTests' do
    inherit! :search_paths
    # Pods for testing
  end

  use_native_modules!
end

target 'demoUpgrade-tvOS' do
  # Pods for demoUpgrade-tvOS

  target 'demoUpgrade-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

Podfile.lock, in case of use:

platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'demoUpgrade' do
  # Pods for demoUpgrade
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  target 'demoUpgradeTests' do
    inherit! :search_paths
    # Pods for testing
  end

  use_native_modules!
end

target 'demoUpgrade-tvOS' do
  # Pods for demoUpgrade-tvOS

  target 'demoUpgrade-tvOSTests' do
    inherit! :search_paths
    # Pods for testing
  end

end

@shannonjensen Look like your 'podfile' and 'podfile.lock' are same. I dont know why it happen. Can you please share the code.

I have this problem, when I run in the vscode , it's ok ,but when i run in the xcode ,hava the message

ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/DoubleConversion'
ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/Folly'
ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/React'
ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/glog'
ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/react-native-baidu-map'
ld: warning: directory not found for option '-L/Users/jonin/Library/Developer/Xcode/DerivedData/sale_manage-cjcaixifvcjqmghapjcngfwsxrcw/Build/Products/Debug-iphonesimulator/yoga'
ld: library not found for -lDoubleConversion
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I fond some answer in the stackoverflow
1.Add the library file to your podfile
pod 'DoubleConversion', :podspec => './../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'

2.Delete the Podfile.lock
3.Run pod install
4.Add the DoubleConversion.a in xcode Linked frameworks and libraries
5.Clean the project and build again.
but where is DoubleConversion.a  ???

I had this problem.
i resolve this  problem is open the *.xcworkspace with xcode ,not the *.xcodepro.
try it.

Ah, sorry @irshadpc, my mistake. The podfile.lock is:
PODS:
  - boost-for-react-native (1.63.0)
  - DoubleConversion (1.1.6)
  - Folly (2<IP_ADDRESS>):
    - boost-for-react-native
    - DoubleConversion
    - Folly/Default (= 2<IP_ADDRESS>)
    - glog
  - Folly/Default (2<IP_ADDRESS>):
    - boost-for-react-native
    - DoubleConversion
    - glog
  - glog (0.3.5)
  - React (0.60.0):
    - React-Core (= 0.60.0)
    - React-DevSupport (= 0.60.0)
    - React-RCTActionSheet (= 0.60.0)
    - React-RCTAnimation (= 0.60.0)
    - React-RCTBlob (= 0.60.0)
    - React-RCTImage (= 0.60.0)
    - React-RCTLinking (= 0.60.0)
    - React-RCTNetwork (= 0.60.0)
    - React-RCTSettings (= 0.60.0)
    - React-RCTText (= 0.60.0)
    - React-RCTVibration (= 0.60.0)
    - React-RCTWebSocket (= 0.60.0)
  - React-Core (0.60.0):
    - Folly (= 2<IP_ADDRESS>)
    - React-cxxreact (= 0.60.0)
    - React-jsiexecutor (= 0.60.0)
    - yoga (= 0.60.0.React)
  - React-cxxreact (0.60.0):
    - boost-for-react-native (= 1.63.0)
    - DoubleConversion
    - Folly (= 2<IP_ADDRESS>)
    - glog
    - React-jsinspector (= 0.60.0)
  - React-DevSupport (0.60.0):
    - React-Core (= 0.60.0)
    - React-RCTWebSocket (= 0.60.0)
  - React-fishhook (0.60.0)
  - React-jsi (0.60.0):
    - boost-for-react-native (= 1.63.0)
    - DoubleConversion
    - Folly (= 2<IP_ADDRESS>)
    - glog
    - React-jsi/Default (= 0.60.0)
  - React-jsi/Default (0.60.0):
    - boost-for-react-native (= 1.63.0)
    - DoubleConversion
    - Folly (= 2<IP_ADDRESS>)
    - glog
  - React-jsiexecutor (0.60.0):
    - DoubleConversion
    - Folly (= 2<IP_ADDRESS>)
    - glog
    - React-cxxreact (= 0.60.0)
    - React-jsi (= 0.60.0)
  - React-jsinspector (0.60.0)
  - React-RCTActionSheet (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTAnimation (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTBlob (0.60.0):
    - React-Core (= 0.60.0)
    - React-RCTNetwork (= 0.60.0)
    - React-RCTWebSocket (= 0.60.0)
  - React-RCTImage (0.60.0):
    - React-Core (= 0.60.0)
    - React-RCTNetwork (= 0.60.0)
  - React-RCTLinking (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTNetwork (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTSettings (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTText (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTVibration (0.60.0):
    - React-Core (= 0.60.0)
  - React-RCTWebSocket (0.60.0):
    - React-Core (= 0.60.0)
    - React-fishhook (= 0.60.0)
  - yoga (0.60.0.React)

DEPENDENCIES:
  - DoubleConversion (from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`)
  - Folly (from `../node_modules/react-native/third-party-podspecs/Folly.podspec`)
  - glog (from `../node_modules/react-native/third-party-podspecs/glog.podspec`)
  - React (from `../node_modules/react-native/`)
  - React-Core (from `../node_modules/react-native/React`)
  - React-cxxreact (from `../node_modules/react-native/ReactCommon/cxxreact`)
  - React-DevSupport (from `../node_modules/react-native/React`)
  - React-fishhook (from `../node_modules/react-native/Libraries/fishhook`)
  - React-jsi (from `../node_modules/react-native/ReactCommon/jsi`)
  - React-jsiexecutor (from `../node_modules/react-native/ReactCommon/jsiexecutor`)
  - React-jsinspector (from `../node_modules/react-native/ReactCommon/jsinspector`)
  - React-RCTActionSheet (from `../node_modules/react-native/Libraries/ActionSheetIOS`)
  - React-RCTAnimation (from `../node_modules/react-native/Libraries/NativeAnimation`)
  - React-RCTBlob (from `../node_modules/react-native/Libraries/Blob`)
  - React-RCTImage (from `../node_modules/react-native/Libraries/Image`)
  - React-RCTLinking (from `../node_modules/react-native/Libraries/LinkingIOS`)
  - React-RCTNetwork (from `../node_modules/react-native/Libraries/Network`)
  - React-RCTSettings (from `../node_modules/react-native/Libraries/Settings`)
  - React-RCTText (from `../node_modules/react-native/Libraries/Text`)
  - React-RCTVibration (from `../node_modules/react-native/Libraries/Vibration`)
  - React-RCTWebSocket (from `../node_modules/react-native/Libraries/WebSocket`)
  - yoga (from `../node_modules/react-native/ReactCommon/yoga`)

SPEC REPOS:
  https://github.com/cocoapods/specs.git:
    - boost-for-react-native

EXTERNAL SOURCES:
  DoubleConversion:
    :podspec: "../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec"
  Folly:
    :podspec: "../node_modules/react-native/third-party-podspecs/Folly.podspec"
  glog:
    :podspec: "../node_modules/react-native/third-party-podspecs/glog.podspec"
  React:
    :path: "../node_modules/react-native/"
  React-Core:
    :path: "../node_modules/react-native/React"
  React-cxxreact:
    :path: "../node_modules/react-native/ReactCommon/cxxreact"
  React-DevSupport:
    :path: "../node_modules/react-native/React"
  React-fishhook:
    :path: "../node_modules/react-native/Libraries/fishhook"
  React-jsi:
    :path: "../node_modules/react-native/ReactCommon/jsi"
  React-jsiexecutor:
    :path: "../node_modules/react-native/ReactCommon/jsiexecutor"
  React-jsinspector:
    :path: "../node_modules/react-native/ReactCommon/jsinspector"
  React-RCTActionSheet:
    :path: "../node_modules/react-native/Libraries/ActionSheetIOS"
  React-RCTAnimation:
    :path: "../node_modules/react-native/Libraries/NativeAnimation"
  React-RCTBlob:
    :path: "../node_modules/react-native/Libraries/Blob"
  React-RCTImage:
    :path: "../node_modules/react-native/Libraries/Image"
  React-RCTLinking:
    :path: "../node_modules/react-native/Libraries/LinkingIOS"
  React-RCTNetwork:
    :path: "../node_modules/react-native/Libraries/Network"
  React-RCTSettings:
    :path: "../node_modules/react-native/Libraries/Settings"
  React-RCTText:
    :path: "../node_modules/react-native/Libraries/Text"
  React-RCTVibration:
    :path: "../node_modules/react-native/Libraries/Vibration"
  React-RCTWebSocket:
    :path: "../node_modules/react-native/Libraries/WebSocket"
  yoga:
    :path: "../node_modules/react-native/ReactCommon/yoga"

SPEC CHECKSUMS:
  boost-for-react-native: 39c7adb57c4e60d6c5479dd8623128eb5b3f0f2c
  DoubleConversion: 5805e889d232975c086db112ece9ed034df7a0b2
  Folly: 30e7936e1c45c08d884aa59369ed951a8e68cf51
  glog: 1f3da668190260b06b429bb211bfbee5cd790c28
  React: 4b3c068e793e96672dcd186a2b572fac43e4b031
  React-Core: 3dc86b22920597f813c62a96db3165950b64826b
  React-cxxreact: 0dacb291e59b81e7c3f22a2118bee853ba8a60d2
  React-DevSupport: 4eb4135386acd10c2586cc9c759bf96b4dac035e
  React-fishhook: 86ca737527bb9d860efbb943c11c729a5b69aa3d
  React-jsi: 8e128c4d0d8febc2977ef617d1c09bb54326069c
  React-jsiexecutor: 7a3554f703a58963ec80b860144ea0f0e9b910e1
  React-jsinspector: d4ed52225912efe0019bb7f1a225aec20f23049a
  React-RCTActionSheet: b27ff3cf3a68f917c46d2b94abf938b625b96570
  React-RCTAnimation: 9e4708e5bd65fca8285ce7c0aa076f3f4fa5c2f8
  React-RCTBlob: 6eafcc3a24f33785692a7be24918ade607bc8719
  React-RCTImage: 46b965d7225b428ea11580ead08a4318aef1d6be
  React-RCTLinking: d65b9f56cf0b8e171575a86764df7bb019ac28d6
  React-RCTNetwork: 783ee2f430740e58f724e46adc79fe7feff64202
  React-RCTSettings: aa28315aadfbfaf94206d865673ae509f1e97c07
  React-RCTText: 685fca2e13b024271048e7e247ef24476f28a41e
  React-RCTVibration: 4ee1cf208ab17a50fafb1c16ffe28fe594a64e4f
  React-RCTWebSocket: fca087d583724aa0e5fef7d911f0f2a28d0f2736
  yoga: 616fde658be980aa60a2158835170f3f9c2d04b4

PODFILE CHECKSUM: dca13e28f5c4ca875863a7288a10696a04a1c0c2

COCOAPODS: 1.7.4

@shannonjensen Please update your cocoapods and run the pod update command. Let me see what happens.

I think you should open your project with .xcworkspace rather than .xcodeproj?

I am having the same problem, only when I try and build the tvOS build of my app in Xcode.  I can build the mobile version through the CLI and through Xcode but as soon as I try and target the tv-OS simulator.  Things I noticed as I was looking through the project/ios files:

the tvOS sub-folder didn't have a copy of the project files(appDelegate.m, etc.)...fixed...still the same error

Other linking under build settings for tvOS project in Xcode...fixed by copying the iOS portion of the podfile to the tvOS portion

I have tried pod install and pod update at various times
I have tried deleting my derived data folder

Does anyone know how to get the tvOS to build?  Any other Debugging ideas?  I can get it to run for iOS but don't know enough about react-native or iOS development to effectively change the device target without some help.

I have the same problem when I try simulate on tv-ios
with this error
ld: library not found for -lPods-reactProject-tvOS
then I found this post when I create the project from his code it works
https://github.com/danilvalov/react-native-appletv
the app runs on tv-os perfect!
@danilvalov thanks

Temp fix:
right click on products under pods,
select add files,
navigate to ../node_modules/react-native/,
add react project file,
edit scheme,
navigate to build tab,
remove React (missing),
add libReact.a,
move React to top of build order

@shannonjensen Look like your project never run the 'pod install' command.
Do the below steps

go to  ios/
run 'pod install' or 'pod update'
open ios/newproject.xcworkspace

This fixed my problem, Thank U.
Can I know from when  did pods became mandatory ?

@shannonjensen, any update on this.

For any of you guys who can be still running into this issue, try to follow @xJkit 's solution above. Also, don't forget to run pod install in /ios dir.
It worked for me! As an additional tip, try to clean Xcode's cache and/or delete .../Xcode/DerivedData contents manually.
I'm on Xcode version 11.1 (11A1027).


Add GPU drivers based on the current Dataproc documentation

Add GPU drivers based on the current Dataproc documentation.
Add GPU monitoring service using StackDriver.
Add beta support for dataproc_test_case.py:
beta: flag
GPU for master and worker
master_accelerator
worker_accelerator

Fix conflict


fix: Update crossplane aws provider location

What does this PR do?
Fixes an issue where Crossplane AWS Provider fails when it is enabled. The cause seems to be a change in the location of the upstream provider package within dockerhub as mentioned in the latest release notes. This PR updates the location to Upbound Marketplace which seems to be a better location that DockerHub.
Motivation

Resolves #1149

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs require a new example and/or doc page. In general:

Use an existing example when possible to demonstrate a new addons usage
A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

@askulkarni2 Plan workflow is failing for Crossplane otherwise we can merge this PR.

@askulkarni2 I'm curious why has the crossplane example been moved into a separate dedicated repo over at awslabs? Was is just deemed too unstable?


React-in-React issue

When adding the built webchat into another React project, the webchat is overwritten. The webchat is injected into "root" and then the parent React app injects its components into "root" as well, which overwrites the webchat. Please add something like the following to index.tsx, where the webchat container can be configured.
const defaultContainer = "root";
const defaultConfig: ConfigState = {
    serverUrl: "http://localhost:3001",
    theme: {
        isLight: true
    },
    fileAttachment: {
        enabled: true,
        maxFileSize: 16777216, // 16 MB
        acceptedExtensions: ["jpg", "jpeg", "png", "amr", "mp3", "mp4", "pdf", "txt"]
    },
    webchatContainer: defaultContainer
};

const initWebchat = async (config: ConfigState) => {
    const mergedConfig = merge({}, defaultConfig, config);
    sessionDataHandler.setEndpoint(mergedConfig.serverUrl);
    store.dispatch(initConfig(mergedConfig));
    initLogger();
    const { webchatContainer } = mergedConfig;
    const rootElement = document.getElementById(webchatContainer ?? defaultContainer);

    render(
        <Provider store={store}>
            <WebchatWidget />
        </Provider>,
        rootElement
    );
};

In the first line your defaultContainer is set to "root". Maybe that has something to do with it?

Thanks for the feedback! We can see the use-case here and we are planning to change the default container from root to something more specific that won't create any clash.
This should address the issue without the need for the extra config parameter.


Fixed minimumFractionDigits to allow 0 value

I added bower support from my branch, but if you prefer I can update the reference and point to your repository after the merge

Please, accept it!


Mongodb Update collection to support new crud operations

@VaclavObornik @arkflpc could you review this pull request?

@lnlwd insertOne is mistyped in line 307 of mongodb.d.ts.

@janmarthedal thanks!
@lnlwd thanks mate!


High memory usage for purs ide server

When I open IntelliJ in a large purescript monorepo, memory usage gradually ramps up to about 24GB before I do anything. This seems to grow as I work (~37GB at the moment)
Before doing anything else in the IDE except loading in and purs ide server starting
ps -eo rss,pid,euser,args:100 --sort %mem | grep -v grep | grep -i 'purs ide' | awk '{printf $1/1024 "MB"; $1=""; print }'
24295.2MB 18466 dsteven+ /home/...MyProfile.../...MyProject.../node_modules/.bin/purs ide server

After about an hour-ish of development, with some decent amount of jumping around
 ps -eo rss,pid,euser,args:100 --sort %mem | grep -v grep | grep -i 'purs ide' | awk '{printf $1/1024 "MB"; $1=""; print }'
36724.8MB 5885 dsteven+ /home/...MyProfile.../...MyProject.../node_modules/.bin/purs ide server

If I open IntelliJ from the command line with memory capped using GHCRTS, memory usage grows to the specified amount, but CPU usage does seem to get a bit erratic once this limit is hit. (e.g spinning at 100% for a while with no usage before quieting down, or spinning up on all cylinders similar to how it behaves when indexing/initial load when working)
Any thoughts/suggestions/recommendations here?

This doese not sound good at all!
The melmory foot print should be very stable and "small" if things are acting normally.
Probably a bug that causes the editor to parse already indexed files.
My only idea of what that could be is the type hints. Maybe, trurning them off could help, but I'm afraid that the calculations are done even if they are hidden.

I misread your issue.
If it is a issue with the purs ide server, then this is probably the wrong project to report it to.
You should probably open a ticket at the purescript repo.
In the meanwhile you can just kill the purs ide server and Intellij will start a new one.

Closing due to inactivity


Free memory from long time closed files and too large closed files

Problem
When you preview a file on editor and closes preview tab, vscode free memory allocated for that file.
On the other hand, when you close a file that was really opened (not only previewed), vscode does not free memory spent for that, what is not a problem for small and medium files, but for large files it sounds like a memory leak.
I know it is not bug. Actually, this really improves performance to open recently opened files. However, it is a pain in the neck when working on large files (you need to restart vscode in order to free memory).
Proposal
My proposal is to free memory used for files that have been closed in a long time and to free (almost) immediately memory for too large files. The problem introduced with these ideas is that it will be needed to define what may be considered long time and too large for that purpose.
If it helps, I will remind you that vscode has already some definition for large files as can be seen below.

@yagotome what you say is not true:

When you preview a file on editor and closes preview tab, vscode free memory allocated for that file.
On the other hand, when you close a file that was really opened (not only previewed), vscode does not free memory spent for that, what is not a problem for small and medium files, but for large files it sounds like a memory leak.

Closing a file will free memory.

@bpasero so it seems to be a bug in linux environment (maybe). I've just realised that this problem does not happen when file is not inside a folder opened by vscode. Try openning the containing folder of the file with vscode and then open the file by vscode explorer.

@bpasero I have done that by monitoring memory usage of vscode process (code) at htop and also at Ubuntu GNOME System Monitor.

@yagotome ok, it is well possible that Chrome or even the OS decides to not give back memory that was claimed for whatever reason. I can assure you that closing an editor will dispose its resources from our end.


Update point-and-commit.md

Docs Build status updates of commit 991580d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/point-and-commit.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


minor fix

@karlnapf
take a look at this

Changes Unknown when pulling 7c758d4580ac4638fd4535c5952b978ee3c9aad9 on yorkerlin:develop into ** on shogun-toolbox:develop**.

merging as travis is fine


Add license file

Please add a file called LICENSE to clearly indicate what the license is.

Done :)


Avoid 0.6 tests due to build failures

Node.js 0.6 does not install and PR checks always fail . Expand range to avoid the failing installation.
Fixes #19

An alternative would be to disable 0.6 upstream, or fix! I'm opening a PR for a local solution/work-around.
I could open another issue in minimist to reenable 0.6 if/when fixed upstream? Reference:

https://github.com/ljharb/actions/issues/1

I suppose this is fine, but I have this same thing on 300+ other projects and it's not much of a problem ¯\_(ツ)_/¯

Codecov Report

Merging #20 (95efa4c) into main (5784b17) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   98.75%   98.75%
=======================================
  Files           1        1
  Lines         161      161
  Branches       71       71
=======================================
  Hits          159      159
  Misses          2        2

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I really dislike failing tests.
I feel either it is worth fixing now, or better as an open issue for long-term problems. Tracking ToDos or short-comings by failing tests is noisy and detracting from the checks, and in particular from my point of view it is mental overhead for people not familiar with the underlying issue.
I am more willing to accept noise from my own failing tests that I intend to fix, so I have some sympathy with your comment!

That's what optional vs required is for :-) failing optional test are expected, failing required tests are a problem.
I am more than happy to see a fix in the action itself, but getting node 0.6 to compile on GHA is sadly not a simple task :-/

That's what optional vs required is for :-) failing optional test are expected, failing required tests are a problem.

My complaint is identifying the difference. The optional/required does affect the email notifications, but I'm finding it hard to tell the difference in the web UX.
Here are three PR. One passes all tests, one has a failing "required" test, and one has a failing "optional" test.

(Woop! Thanks. Appreciate you are willing to do something different than your other projects. 👍 )

Realistically this is a compelling argument to disable it in the shared action, until I can get it working, but I'll merge this now to make it easier


How to access transformer's prediction at each timestep, during decoding

Description
(Not an issue, so much as a question)
For my purposes, it would be extremely useful to be able to access the transformer's prediction at each timestep of decoding (e.g. in greedy search, e.g. for a trained English to German translation model). I've tinkered with the code a bit and can maybe hack something together, but wondered if there was a direct way.
Ideally, I'd like to be able to see the distribution over tokens at each timestep, in a greedy decoding, and later down the road, make a model that just returns the next logits (i.e. like the symbols_to_logits_fn function).
Thanks so much - t2t is awesome and is working super well!

+1, any ideas for this? Thanks!


disable indent line when viewing diff

as shown in the picture, the indent line highlighting doesn't match highlight for diff line,
is it possible to get the same highlight for diff lines?
or can i somehow disable the indent line when i'm opening a diff?
i'm using fugitive-vim :Gdiffsplit feature for the diff

I did something like this to disable indent-lines in diff mode, works with fugitive Gdiffsplit
augroup DiffHideIndent   autocmd!   " Disable indentline in vim diffmode   autocmd OptionSet diff IndentLinesDisable augroup end

hi @kazhala ,
i tried your solution and it only work when i open a diff,
the problem is when i close the diff, indentLine is still disabled
do you know any autocmd event or option to revert it?

based on your suggestion,
i tried something like this
augroup custom_indentLine
    autocmd!
    autocmd OptionSet diff call ToggleIndentLine()
augroup END

function! ToggleIndentLine()
    if &diff
        execute 'IndentLinesDisable'
    else
        execute 'IndentLinesEnable'
    endif
endfunction

the indent line is disabled when i open a diff, but when i close diff window, the indent line still disabled.
i have confirmed that the &diff option changed back to 0, but  it seems neovim doesn't detect when the &diff option set back to 0

do you know any autocmd event or option to revert it?

Sadly no, I remember I was facing the issue as well not being able to set it back.

Fixed.

it works, thanks

This is breaking my NERDTree startup on VimEnter because the cursor now stays on the empty buffer instead of the NERDTree window.

@koallen Fixed.


Show complete options on editable combo boxes

For a combo box with a textfield, the options should show up as completions while typing.

Implemented.


Communicate default thumb size

Fixes https://github.com/pocketbase/pocketbase/issues/287 (if you think it needs a fix to begin with!)

Before:

After:

Thanks! Will be included in the next release (v0.4.0).


job-harbor failing

Describe the bug:
the job 'job-harbor' crashes when deployed (image: otomi/tasks:v0.2.21).
See here the last part of redacted logs:
Found: secret harbor-pullsecret in namespace xxx
Deleting secret/harbor-pullsecret from xxx namespace
Found: secret harbor-pullsecret in namespace xxx
Deleting secret/harbor-pullsecret from xxx namespace
{
  errors: [
    {
      code: 'CONFLICT',
      message: 'The project member specified already exist'
    }
  ]
}
Associating "project-admin" role for "team-admin" with harbor project "xxx" > already exists.
{
  errors: [
    {
      code: 'CONFLICT',
      message: 'The project member specified already exist'
    }
  ]
}
Associating "project-admin" role for "team-admin" with harbor project "xxx" > already exists.
{
  errors: [
    {
      code: 'CONFLICT',
      message: 'The project member specified already exist'
    }
  ]
}
Associating "project-admin" role for "team-admin" with harbor project "team-xxx" > already exists.

Creating secret/harbor-pullsecret at team-xxx namespace
/app/dist/tasks/harbor/harbor.js:176
        username: robotAccount.name,
                               ^

TypeError: Cannot read property 'name' of undefined
    at ensureTeamRobotAccountSecret (/app/dist/tasks/harbor/harbor.js:176:32)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at async /app/dist/tasks/harbor/harbor.js:216:9
    at async Promise.all (index 8)
    at async main (/app/dist/tasks/harbor/harbor.js:189:5)

To Reproduce
Not sure, I logged into harbor and couldnt find any 'undefined' robot account
Expected behavior:
job-harbor to complete succesfully
Cluster(s):
AKS 1.21.2
Otomi v0.15.3

Wow, I have never seen such duplication. Each action done 6 times it seems. How on earth did you manage that?

We can only help with reports that bring reproducible steps, so if you can provide those, then please

Same issue appears today when running this job, but it doesnt succeed even after a few times. Because of this issue, the harbor-pullsecrets dont get created anymore


Import inactive projects with bitbucket repositories to Gitlab using their importer

Only those who are mercurial of course and only those which are inactive.
Candidates are: Fujo, Story of a Lost Sky, Supremacy and Goblin Camp

Using the Github Hg importer (and then the Gitlab from Github importer) worked for Fuo, Story of a Lost Sky and Goblin Camp. Github could not import Supremacy (didn't specify why).
Will try another possibility for Supremacy. See https://stackoverflow.com/questions/10710250/converting-mercurial-folder-to-a-git-repository for possibilities.

It seems Supremacy is actively developed. Conversion to Git is not needed right now. This means this issue is solved.


Multiple isolated parameters cause data race without generating compilation error or warning

Describe the bug
According to SE-0313 Improved control over actor isolation, multiple isolated parameters should generate compilation error. But as far as I tried, multiple isolated parameters do not generated any compilation error or warning even if strict concurrent check is enabled. Furthermore, multiple isolated parameters can cause data race.
Steps To Reproduce
actor Counter {
    var count: Int = 0
    func increment() { count += 1 }
}

func incrementCounters(c1: isolated Counter, c2: isolated Counter) {
    for _ in 0..<1_000 {
        c1.increment()
        c2.increment()
    }
}

@main
public struct Main {
    public static func main() async throws {
        let c1 = Counter()
        let c2 = Counter()

        let t1: Task<Void, Never> = Task.detached { await incrementCounters(c1: c1, c2: c2) }
        let t2: Task<Void, Never> = Task.detached { await incrementCounters(c1: c2, c2: c1) }
        let _ = await (t1.value, t2.value)

        await print(c1.count, c2.count)
    }
}

Output is random numbers less than 2000, for example 1853 1897.
Expected behavior
Generating error or warning on multiple isolated parameters. Otherwise, output is 2000 2000
Screenshots

Environment (please fill out the following information)

OS: macOS 12.4
Xcode 14 Beta 5

Ouch, that's an omission indeed...
It's pretty bad, allowing even completely unrelated two isolated parameters:
actor Other {
  func inc() {}
  func pass(_ f: @Sendable  (Self) async -> Void) {}
}
actor Counter {
  func inc() {}

  func pass(_ f: @Sendable  (Self) async -> Void) {}
}

@available(SwiftStdlib 5.1, *)
func testDoubleIsolatedParams(
  a: isolated Counter,
  b: isolated Other
) async {
  a.inc()
  a.inc()
}

func taaaa() async {
  await Counter().pass { isoC in
    await Other().pass { isoO in
      await testDoubleIsolatedParams(a: isoC, b: isoO)
    }
  }
}

this CAN'T work correctly.

Oh well, I gave it a shot here: https://github.com/apple/swift/pull/60483
Though not sure if the check wouldn't be betted pulled into isolation checker

fixed in https://github.com/apple/swift/pull/61862


BulkDelete where in ...

Is it possible to make such a?
dbConnection.BulkDelete<Asset>(statement => statement
  .Where($"{nameof(Asset.Id) IN ...")
  .WithParameters(new { ... = assets});

I think you are missing a bracket..
What is the raw sql query you are trying to use, in full?

Raw dapper equivalent. Only example. Full case I have described here
interface IEntity{
     long Id {get;set;}
}

public void EntityBulkDelete(IEnumerable<IEntity> entities){
      db.Execute($"DELETE FROM assets WHERE Id IN @Ids",
                new {Ids = entities.Select(e => e.Id).ToArray()});
}

but we need to know tablename for raw sql.
EntityBulkDelete<T> is impossible in my case, so I can not use OrmConfiguration.GetDefaultEntityMapping<T>()

Hmm, so we are back a little to the previous issue, that your IoC is not injecting with Generics.
have you tried the syntax's on the wiki: https://github.com/MoonStorm/Dapper.FastCRUD/wiki/SQL-statements-and-clauses.
i.e. {nameof(Asset.Id):C}
You can probably do some tests with the sqlbuilder to get it right. After all FastCRUD is just creating queries for you...

Let's forget about the IoC and generics problem in this issue.
If we can
db.BulkDelete<Asset>(
                stmt =>
                    stmt.Where($"{nameof(Asset.Id)} IN @Ids")
                        .WithParameters(new { Ids = idList }));

why not add a useful feature?
db.BulkDelete<Asset>(assets);

which delete records by primary key.
FastCrud is micro-orm and we have db.Insert(entity) and db.Delete(entity) and even db.Delete(entity), but why we have no method db.BulkDelete(entities)?

Your right :-)
You can add it yourself to the project and do a pull request? Otherwise we will have to wait til MoonStorm is back...
Sorry I could not help more...

If I understand correctly, you want FastCrud to support bulk delete by primary key?
I don't think this is necessary in this library. The bulk delete method already expose the where clause/parameters for you to wrap it to create any other methods you need.
Besides, FastCrud support composite primary key, how would you go able supporting bulk delete with composite primary key? I'm sure it can be done, but I bet it's going to be complex/messy.
In the end, I think it's up to you to write custom wrapper (extension) methods to help do what you need in your application.

@ducman

you want FastCrud to support bulk delete by primary key?

Yes, and why not? We can do all things through raw dapper. FastCRUD extends Dapper for more comfortable work with "entities".  Is the mass deletion of entities by primary key is a rare operation? I do not think so.

delete with composite primary key

Nothing. I just will not call BulkDelete in this case. And I would not be surprised if I get an exception "Composite keys is not supported".

I think it's up to you to write custom wrapper (extension) methods to help do what you need in your application.

You are right. But I think the mass deletion of entities is enough common operation to be in FastCRUD and not be an extension, which is copied to every project.

I agree with you but if the author decides to do it, he/she has to write it to support composite primary keys since the library support it.

We have reviewed all the existing CRUD methods for 3.0 and made several critical improvements. Please check the list of changes here. We'll update the wiki shortly.


Obj importing materials with wrong roughness

Godot version:
3.0.x and master branch

OS/device including version:

Solus OS
Issue description:

My use case: For fast prototyping I like to use premade 3D models, most of them from itch.io and kenney.nl
Most of this models come in OBJ format. And as far as I've seen all OBJ models I've used are imported way too metallic. Here you can see the OBJ imported by Godot on the left and a DAE exported with blender on the right.

And just for sake of comparison, the same OBJ imported in Unity3D.

Now as I said this is just for prototyping and usually for production one can really tweak what is needed on blender. But this could be an issue for newcomers and sometimes is really not cool:

Minimal reproduction project:

obj_import_test.zip

You don't like metallic trees?
Just to make sure, is this fixed by #20787? (we merged about 6 hours before this issue was opened)

~Actually metallic trees sounds like a good game theme~
Yes it has been fixed. We can close this. Thank you :)


doc fix: Update nft-minting.md to fix formatting

What changed? Why?
Apologies for another commit onto an patch that was already merged. I noticed that there was a formatting issue at the bottom due to a missing space. I just fixed it.
Please merge this as well. Thanks once again
Notes to reviewers
Same as above
How has it been tested?
Tested preview

@wbnns @zencephalon sorry for tagging once again, just fixed a minor issue. Can you please merge? Thanks once again

@rohit-710 Thanks for the quick fix!


Woah. GUI bug when showing in game crash report

I am using MultiMC, and it seems to have changed all the text characters to parts of the yellow gear icon... somehow...
this gear:

Mac does have some video issues from my experience, so it could just be that...
crash report: the crash is irrelevent, but here it is anyways: crash-2019-10-14_14.03.20-client.txt
log: latest.log

try again but with Forgelin installed

Unacceptable. No commits as of May, no releases as of LAST YEAR! so bad.

@MasterBuilder747 but did you install forgelin as asked?

@MasterBuilder747 Then do it yourself. VanillaFix is a free mod, and we have no obligation to provide you updates. You can't say something you paid 0$ for is "unacceptable". Normally, 0$ gets you nothing, but here you got a mod that works apart for this small bug.