Adding react-native-languages kills metro bundler and iOS build

Describe your environment

React-Native : 0.55.4
Platform: iOS
Device iOS Simulator "iPhone XS"
OS version : iOS 12, macOS 10.13.6 (17G65)
react-native-languages : 3.0.1
Devtools: Command Line
Android only: N/A

How to repeat issue and example
I have a fairly simple starter project that runs successfully prior to installing react-native-languages.  The project is based off of react-native-firebase.
NOTE: I do NOT actually start to use the library in my app.  This whole failure process starts just after installing the library.
I install as follows :
yarn add react-native-languages
react-native link react-native-languages
cd ios
pod install

After pod install, got this warning
Pod installation complete! There are 15 dependencies from the Podfile and 31 total pods installed.

[!] React has been deprecated

Start the metro bundler:
react-native start "--reset-cache"

Seeing all kinds of issues in the Metro bundler now
Scanning folders for symlinks in /Users/jn/Documents/Apps/MyAppName/node_modules (19ms)
┌──────────────────────────────────────────────────────────────────────────────┐
│                                                                              │
│  Running Metro Bundler on port 8081.                                         │
│                                                                              │
│  Keep Metro running while developing on any JS projects. Feel free to        │
│  close this tab and run your own Metro instance if you prefer.               │
│                                                                              │
│  https://github.com/facebook/react-native                                    │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /Users/jn/Documents/Apps/MyAppName

Metro Bundler ready.

Loading dependency graph...jest-haste-map: @providesModule naming collision:
  Duplicate module name: DocumentSelectionState
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/document/selection/DocumentSelectionState.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/document/selection/DocumentSelectionState.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: SpringConfig
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Animated/src/SpringConfig.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Animated/SpringConfig.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Animated
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Animated/src/Animated.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Animated/Animated.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Easing
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Animated/src/Easing.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Animated/Easing.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventSubscription
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventSubscription.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventSubscription.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventHolder
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventHolder.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventHolder.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mixInEventEmitter
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/mixInEventEmitter.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/mixInEventEmitter.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventEmitterWithHolding
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventEmitterWithHolding.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventEmitterWithHolding.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventEmitter
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventEmitter.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventEmitter.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventSubscriptionVendor
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventSubscriptionVendor.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventSubscriptionVendor.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EmitterSubscription
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EmitterSubscription.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EmitterSubscription.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: bezier
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Animated/src/bezier.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Animation/bezier.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EventValidator
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/emitter/EventValidator.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/emitter/EventValidator.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Map
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/Map.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/Map.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mergeHelpers
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/mergeHelpers.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/mergeHelpers.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ErrorUtils
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/ErrorUtils.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/ErrorUtils.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: getObjectValues
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/getObjectValues.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/getObjectValues.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: _shouldPolyfillES6Collection
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/_shouldPolyfillES6Collection.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/_shouldPolyfillES6Collection.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: toIterator
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/toIterator.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/toIterator.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: isEmpty
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/isEmpty.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/isEmpty.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: merge
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/merge.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/merge.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Set
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/Set.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/Set.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: guid
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/guid.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/guid.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mergeInto
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/vendor/core/mergeInto.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/core/mergeInto.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ScrollView
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/ScrollView/ScrollView.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PickerIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Picker/PickerIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Picker/PickerIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ProgressViewIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/ProgressViewIOS/ProgressViewIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/ProgressViewIOS/ProgressViewIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ProgressBarAndroid
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/ProgressBarAndroid/ProgressBarAndroid.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/ProgressBarAndroid/ProgressBarAndroid.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StatusBarIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/StatusBar/StatusBarIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/StatusBar/StatusBarIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TextInputState
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/TextInput/TextInputState.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/TextInput/TextInputState.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TextInput
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/TextInput/TextInput.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/TextInput/TextInput.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: DatePickerIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/DatePicker/DatePickerIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/DatePicker/DatePickerIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: WebView
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/WebView/WebView.android.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/WebView/WebView.android.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: NavigatorIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Navigation/NavigatorIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Navigation/NavigatorIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Position
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/Position.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react_contrib/pooledClasses/Position.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchableOpacity
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/TouchableOpacity.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: BoundingDimensions
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/BoundingDimensions.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react_contrib/pooledClasses/BoundingDimensions.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ensureComponentIsNative
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/ensureComponentIsNative.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/ensureComponentIsNative.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchableHighlight
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/TouchableHighlight.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/TouchableHighlight.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchableNativeFeedback
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/TouchableNativeFeedback.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/TouchableNativeFeedback.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchableBounce
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/TouchableBounce.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/TouchableBounce.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Touchable
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/Touchable.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react_contrib/interactions/Touchable/Touchable.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchableWithoutFeedback
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/TouchableWithoutFeedback.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/TouchableWithoutFeedback.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ensurePositiveDelayProps
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Touchable/ensurePositiveDelayProps.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Touchable/ensurePositiveDelayProps.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TabBarIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/TabBarIOS/TabBarIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/TabBarIOS/TabBarIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TabBarItemIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/TabBarIOS/TabBarItemIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/TabBarIOS/TabBarItemIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: SegmentedControlIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/SegmentedControlIOS/SegmentedControlIOS.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/SegmentedControlIOS/SegmentedControlIOS.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: UnimplementedView
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/UnimplementedViews/UnimplementedView.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/UnimplementedViews/UnimplementedView.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: View
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/View/View.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/View/View.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ViewStylePropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/View/ViewStylePropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/View/ViewStylePropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ReactNativeViewAttributes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/View/ReactNativeViewAttributes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactNative/ReactNativeViewAttributes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ReactNativeStyleAttributes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/View/ReactNativeStyleAttributes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactNative/ReactNativeStyleAttributes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: pointsDiffer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/differ/pointsDiffer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/differ/pointsDiffer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: deepDiffer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/differ/deepDiffer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/differ/deepDiffer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: matricesDiffer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/differ/matricesDiffer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/differ/matricesDiffer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: sizesDiffer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/differ/sizesDiffer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/differ/sizesDiffer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: insetsDiffer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/differ/insetsDiffer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/differ/insetsDiffer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ListViewDataSource
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Lists/ListView/ListViewDataSource.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/CustomComponents/ListView/ListViewDataSource.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ListView
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Lists/ListView/ListView.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/CustomComponents/ListView/ListView.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: JSTimers
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Core/Timers/JSTimers.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimers.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: parseErrorStack
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Core/Devtools/parseErrorStack.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/JavaScriptAppEngine/Initialization/parseErrorStack.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: setupDevtools
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Core/Devtools/setupDevtools.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Devtools/setupDevtools.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ReactNative
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Renderer/shims/ReactNative.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactNative/ReactNative.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: createReactNativeComponentClass
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Renderer/shims/createReactNativeComponentClass.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactNative/createReactNativeComponentClass.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: NativeMethodsMixin
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Renderer/shims/NativeMethodsMixin.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactIOS/NativeMethodsMixin.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TouchHistoryMath
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Renderer/shims/TouchHistoryMath.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react/browser/eventPlugins/TouchHistoryMath.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: VibrationIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Vibration/VibrationIOS.android.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Vibration/VibrationIOS.android.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Settings
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Settings/Settings.android.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Settings/Settings.android.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ExceptionsManager
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Core/ExceptionsManager.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/JavaScriptAppEngine/Initialization/ExceptionsManager.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: React
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/react-native/React.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactNative/React.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: resolveBoxStyle
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/resolveBoxStyle.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/resolveBoxStyle.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ElementProperties
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/ElementProperties.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/ElementProperties.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: BorderBox
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/BorderBox.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/BorderBox.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: InspectorPanel
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/InspectorPanel.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/InspectorPanel.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PerformanceOverlay
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/PerformanceOverlay.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/PerformanceOverlay.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StyleInspector
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/StyleInspector.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/StyleInspector.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ElementBox
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/ElementBox.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/ElementBox.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Inspector
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/Inspector.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/Inspector.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: InspectorOverlay
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/InspectorOverlay.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/InspectorOverlay.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: BoxInspector
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Inspector/BoxInspector.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Inspector/BoxInspector.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: RCTAlertManager
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Alert/RCTAlertManager.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/BatchedBridge/BatchedBridgedModules/RCTAlertManager.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: AlertIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Alert/AlertIOS.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/AlertIOS.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ARTSerializablePath
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ART/ARTSerializablePath.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ART/ARTSerializablePath.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ReactNativeART
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ART/ReactNativeART.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ART/ReactNativeART.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: EdgeInsetsPropType
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/EdgeInsetsPropType.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/EdgeInsetsPropType.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PointPropType
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/PointPropType.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/PointPropType.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: LayoutPropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/LayoutPropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/LayoutPropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: flattenStyle
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/flattenStyle.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/flattenStyle.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StyleSheet
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/StyleSheet.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/StyleSheet.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StyleSheetPropType
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/StyleSheetPropType.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/StyleSheetPropType.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TransformPropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/TransformPropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/TransformPropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StyleSheetValidation
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/StyleSheet/StyleSheetValidation.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/StyleSheet/StyleSheetValidation.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ActionSheetIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ActionSheetIOS/ActionSheetIOS.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ActionSheetIOS/ActionSheetIOS.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: BatchedBridge
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/BatchedBridge/BatchedBridge.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/BatchedBridge/BatchedBridge.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: FormData
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Network/FormData.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Network/FormData.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: NativeModules
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/BatchedBridge/NativeModules.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/BatchedBridge/BatchedBridgedModules/NativeModules.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: MessageQueue
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/MessageQueue.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: NetInfo
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Network/NetInfo.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Network/NetInfo.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: fetch
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Network/fetch.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Fetch/fetch.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Image
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/Image.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/Image.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: AssetRegistry
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/AssetRegistry.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/AssetRegistry.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ImageSource
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/ImageSource.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/ImageSource.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: resolveAssetSource
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/resolveAssetSource.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/resolveAssetSource.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ImageStylePropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/ImageStylePropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/ImageStylePropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ImageResizeMode
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Image/ImageResizeMode.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/ImageResizeMode.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: LayoutAnimation
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/LayoutAnimation/LayoutAnimation.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: clamp
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/clamp.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react/core/clamp.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: buildStyleInterpolator
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/buildStyleInterpolator.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/buildStyleInterpolator.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: groupByEveryN
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/groupByEveryN.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/groupByEveryN.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: logError
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/logError.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/logError.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: stringifySafe
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/stringifySafe.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/stringifySafe.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mapWithSeparator
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/mapWithSeparator.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/mapWithSeparator.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: RCTLog
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/RCTLog.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/RCTLog.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PerformanceLogger
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/PerformanceLogger.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/PerformanceLogger.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mergeFast
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/mergeFast.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/mergeFast.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: mergeIntoFast
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/mergeIntoFast.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/mergeIntoFast.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: deepFreezeAndThrowOnMutationInDev
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/deepFreezeAndThrowOnMutationInDev.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/deepFreezeAndThrowOnMutationInDev.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PixelRatio
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/PixelRatio.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/PixelRatio.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Dimensions
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/Dimensions.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/Dimensions.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: dismissKeyboard
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/dismissKeyboard.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/dismissKeyboard.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: createStrictShapeTypeChecker
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/createStrictShapeTypeChecker.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/createStrictShapeTypeChecker.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: truncate
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/truncate.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/truncate.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Platform
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/Platform.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/Platform.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: MatrixMath
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Utilities/MatrixMath.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Utilities/MatrixMath.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StaticContainer.react
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/StaticContainer.react.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react_contrib/StaticContainer/StaticContainer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Subscribable
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/Subscribable.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/Subscribable.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: StaticRenderer
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/StaticRenderer.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/StaticRenderer.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ImagePickerIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/CameraRoll/ImagePickerIOS.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Image/ImagePickerIOS.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Geolocation
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Geolocation/Geolocation.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Geolocation/Geolocation.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: ScrollResponder
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Components/ScrollResponder.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Components/ScrollResponder.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: CameraRoll
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/CameraRoll/CameraRoll.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/CameraRoll/CameraRoll.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Sample
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Sample/Sample.ios.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Sample/Sample.ios.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Object.es6
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/polyfills/Object.es6.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/polyfills.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Array.prototype.es6
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/polyfills/Array.prototype.es6.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/Array.prototype.es6.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: String.prototype.es6
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/polyfills/String.prototype.es6.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/String.prototype.es6.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TextUpdateTest
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Text/TextUpdateTest.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Text/TextUpdateTest.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: console
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/polyfills/console.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/packager/react-packager/src/DependencyResolver/polyfills/console.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Text
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Text/Text.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Text/Text.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: TextStylePropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Text/TextStylePropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Text/TextStylePropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Modal
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Modal/Modal.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Modal/Modal.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: InteractionMixin
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Interaction/InteractionMixin.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Interaction/InteractionMixin.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: InteractionManager
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Interaction/InteractionManager.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Interaction/InteractionManager.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PanResponder
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Interaction/PanResponder.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/vendor/react/browser/eventPlugins/PanResponder.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: verifyPropTypes
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ReactNative/verifyPropTypes.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactIOS/verifyPropTypes.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: AppRegistry
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ReactNative/AppRegistry.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/AppRegistry/AppRegistry.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: requireNativeComponent
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ReactNative/requireNativeComponent.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/ReactIOS/requireNativeComponent.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: queryLayoutByID
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/ReactNative/queryLayoutByID.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/RKBackendNode/queryLayoutByID.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: RCTDeviceEventEmitter
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/EventEmitter/RCTDeviceEventEmitter.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Device/RCTDeviceEventEmitter.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: PushNotificationIOS
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/PushNotificationIOS/PushNotificationIOS.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/PushNotificationIOS/PushNotificationIOS.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: RCTEventEmitter
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/EventEmitter/RCTEventEmitter.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/BatchedBridge/BatchedBridgedModules/RCTEventEmitter.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: RCTNativeAppEventEmitter
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/EventEmitter/RCTNativeAppEventEmitter.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/NativeApp/RCTNativeAppEventEmitter.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: Promise
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/Libraries/Promise.js collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/Libraries/Promise.js

This warning is caused by a @providesModule declaration with the same name across two different files.
jest-haste-map: @providesModule naming collision:
  Duplicate module name: react-native
  Paths: /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/package.json collides with /Users/jn/Documents/Apps/MyAppName/ios/Pods/React/package.json

This warning is caused by a @providesModule declaration with the same name across two different files.
Loading dependency graph, done.

warning: the transform cache was reset.
error: bundling failed: ambiguous resolution: module `/Users/jn/Documents/Apps/MyAppName/index.js` tries to require `react-native`, but there are several files providing this module. You can delete or fix them:

  * `/Users/jn/Documents/Apps/MyAppName/ios/Pods/React/package.json`
  * `/Users/jn/Documents/Apps/MyAppName/node_modules/react-native/package.json`

 BUNDLE  [ios, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1), failed.

Now to try to run the app on device:
react-native run-ios --simulator "iPhone XS"

...
...

    cd /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/React
   export LANG=en_US.US-ASCII
   /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch x86_64 -fmessage-length=0 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu++11 -stdlib=libc++ -fmodules -fmodules-cache-path=/Users/jn/Documents/Apps/MyAppName/ios/build/ModuleCache.noindex -fmodules-prune-interval=86400 -fmodules-prune-after=345600 -fbuild-session-file=/Users/jn/Documents/Apps/MyAppName/ios/build/ModuleCache.noindex/Session.modulevalidation -fmodules-validate-once-per-build-session -Wnon-modular-include-in-framework-module -Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings -O0 -fno-common -Wno-missing-field-initializers -Wmissing-prototypes -Werror=return-type -Wdocumentation -Wunreachable-code -Werror=deprecated-objc-isa-usage -Werror=objc-root-class -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wmissing-braces -Wparentheses -Wswitch -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wshadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion -Wno-float-conversion -Wno-non-literal-null-conversion -Wno-objc-literal-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DDEBUG=1 -DRCT_DEBUG=1 -DRCT_DEV=1 -DRCT_NSASSERT=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator12.0.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -mios-simulator-version-min=8.0 -g -Wno-sign-conversion -Winfinite-recursion -Wmove -Wno-comma -Wno-block-capture-autoreleasing -Wno-strict-prototypes -Wno-range-loop-analysis -Wno-semicolon-before-method-body -index-store-path /Users/jn/Documents/Apps/MyAppName/ios/build/Index/DataStore -iquote /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/third-party-generated-files.hmap -I/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/third-party-own-target-headers.hmap -I/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/third-party-all-target-headers.hmap -iquote /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/third-party-project-headers.hmap -I/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Products/Debug-iphonesimulator/include -I/Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/boost_1_63_0 -I/Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/folly-2<IP_ADDRESS> -I/Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src -I/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/DerivedSources/x86_64 -I/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/DerivedSources -Wextra -Wall -Wno-semicolon-before-method-body -F/Users/jn/Documents/Apps/MyAppName/ios/build/Build/Products/Debug-iphonesimulator -DFOLLY_NO_CONFIG -DFOLLY_MOBILE=1 -DFOLLY_USE_LIBCPP=1 -MMD -MT dependencies -MF /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/symbolize.d --serialize-diagnostics /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/symbolize.dia -c /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src/symbolize.cc -o /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/symbolize.o

In file included from /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src/symbolize.cc:55:
In file included from /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src/utilities.h:73:
/Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src/base/mutex.h:105:10: fatal error: 'config.h' file not found
#include "config.h"           // to figure out pthreads support
        ^~~~~~~~~~

1 error generated.

** BUILD FAILED **

The following build commands failed:

   CompileC /Users/jn/Documents/Apps/MyAppName/ios/build/Build/Intermediates.noindex/React.build/Debug-iphonesimulator/third-party.build/Objects-normal/x86_64/symbolize.o /Users/jn/Documents/Apps/MyAppName/node_modules/react-native/third-party/glog-0.3.4/src/symbolize.cc normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

Solution
No known solution at this time.

Yes, I use Cocoapods and installed as follows:
yarn add react-native-languages
react-native link react-native-languages
pod install

@calendee Looks like a bad React pod dependency declaration.
Try using the one included with react-native instead of the obsolete one available on cocoapods.
Follow the documentation here: https://facebook.github.io/react-native/docs/integration-with-existing-apps#configuring-cocoapods-dependencies

Thanks for the suggestion.  I'll have to try this out next week.

I didn't get around to investigating this.  I'm closing for now to cleanup the issue.


[XLA] Change the number of threads per block for row reduction

This is a follow up from https://github.com/tensorflow/tensorflow/pull/36752
This change the number of blocks per threads. It is only the last commit that is the new feature from this PR. The others are already in 36752.
I didn't change anything in the code. We can start the discussion on how to fix this and I'll update the code accordingly.
The number of threads per blocks must be determined by many factors (taken from the previous PR)

More threads per blocks mean less atomic writes (as the total number of threads is constant). This is good.
One SM can't use the full bandwidth per itself. So you need enough blocks to help saturate the IO. I did very small timing, but discarded those results as the noise was too high. There is 80 SM in V100, so ideally we would like at least 80 blocks.
The last block strangler effect. If you have 81 blocks and 80 SM, then you have 1 that will cause the computation to be as long as if you had 160 blocks. More blocks mean smaller blocks, help mitigate this, as the smaller block will run faster.
Also, we need at least 64 threads per blocks if we want full occupancy. We are limited to 0.5 occupancy if we use 32 threads per blocks.
In theory, we could also add a cost model to know if we have a IO or Compute bound kernel (fusion could create compute bound kernel). And in that case we could need different best configuration, as it could be register bound... I do not want to go there.

The problem this PR currently have is that it breaks the deterministic reduction on XLA as it is expect exactly 1024 threads per blocks. Making the tree reduction opt know about the new block size is easy (already tested). But this still cause 2 tree reduction failure as now it request 1 extra reduction. This probably slowing down the current tree reduction.

Is slowing down the tree reduction acceptable for this PR? If so, I'll just update the expected answer from those tests.
One option would be to add an attribute to the XLA reduction that would specify the number of threads (example name biggest_block).

This isn't very good as this add an implementation detail as a Reduce attribute.

Another attribute that we could add is: "deterministic". This describe a behavior. I could implement that, by making sure we it generates only 1 blocks per row. If not possible, raise an error. It would be the responsibility of the optimizer to have this possible.

I like the last approch. It would also help prevent the AlgebraicOptimizer to interfer with the TreeReductionRewriter optimizer, as it could just not touch those graph.
If we choose this options, this open the doors to more optimization later. For example, you could remove the memset and replace the atomic update with a normal write at the end of the kernel.
@cheshire

I just pushed a new commit that make the tree reduction use the right information following the changes to XLA reduction. Now it will always use the same unroll factor and block size.
So you should be able to start the benchmark from this commit.
The reduction tests pass, but I have a strange error/warning from bazel tests. I do not understand the error information. Any idea what could be going on?
ERROR: command succeeded, but there were errors parsing the target pattern
INFO: Elapsed time: 25.840s, Critical Path: 18.46s
INFO: 39 processes: 39 local.
FAILED: Build did NOT complete successfully
//tensorflow/compiler/xla/service/gpu/tests:gpu_unrolling_test           PASSED in 5.4s
//tensorflow/compiler/xla/service/gpu/tests:reduction_degenerate_dim_remover_test PASSED in 5.0s
//tensorflow/compiler/xla/service/gpu/tests:reduction_dimension_grouper_test PASSED in 4.9s
//tensorflow/compiler/xla/service/gpu/tests:reduction_layout_normalizer_test PASSED in 5.4s
//tensorflow/compiler/xla/service/gpu/tests:tree_reduction_rewriter_test PASSED in 17.7s
//tensorflow/compiler/xla/tests:reduce_hlo_test_gpu                      PASSED in 5.5s
//tensorflow/compiler/xla/tests:reduce_precision_test_gpu                PASSED in 4.9s
//tensorflow/compiler/xla/tests:vector_ops_reduce_test_gpu               PASSED in 4.8s
//tensorflow/compiler/xla/tests:reduce_test_gpu                          PASSED in 5.5s
  Stats over 31 runs: max = 5.5s, min = 2.1s, avg = 4.2s, dev = 0.9s

Executed 9 out of 9 tests: 9 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these
are.
All tests passed but there were other errors during the build.
FAILED: Build did NOT complete successfully

I rebased this PR to resolve the conflicts.
Note, I didn't update the tests, this PR is in a good state to be benchmarked, but not merged.

Talked to @cheshire who has the most context here and agreed to take a look. I'm going to remove myself as reviewer.

@nouiz Can you please resolve conflicts? Thanks!

I have rebased it.

@cheshire Can you please review this PR ? Thanks!

@nouiz I'm generally fine with merging this. Could you add some micro-benchmarks in the commit description demonstrating a speed-up in small artificial test cases?

I'll work on this probably at the end of this week.

@nouiz  Any update on this PR? Please. Thanks!

I'm not able to repro it anymore.  I'm not sure what is going on. As the gain was only for small case, this isn't the most important and I do not have time now to investigate this.
So I'll close this PR and if I get back to it, I'll make a new one or reopen it.


Sometimes after fog, comes sunny day.

#654
#663
#661

Where could I preview changes?

It's already merged so https://nft.kodadot.xyz

hm.. don't see my changes there :/

oh seems failed builds, we will check on that! you will probably redeploy or let you know on discord:)


Allow for Processes to be deleted from the User Interface

Is your feature request related to a problem? Please describe.
Processes currently cannot be deleted from the User Interface, even though DELETE is possible from the REST API: https://github.com/DSpace/RestContract/blob/main/processes-endpoint.md#execution-deletion
Without this feature, the list of processes will just grow and grow, even though they can be deleted via the REST API.
Describe the solution you'd like
At a minimum, we should allow individual processes to be deleted (add a delete button when viewing a process).
It also might be nice to provide a way to bulk delete processes, either via a series of checkboxes, or via a new processes_cleanup script which can delete all processes which are greater than ___ days old.

I'd say that the ability to automatically remove stale process debris, rather than wasting a sysadmin's time doing this manually, is not nice but necessary.

I'd propose to add a delete button to the process detail page, and a trash can icon in the process overview list. There isn't much difference between checking a bunch of checkboxes, and clicking the same number of trashcans.
I'm hesitant to add a "delete all" button at the top, because there's currently only an endpoint to delete processes individually so that would mean the UI would have to fetch them all first, which is a bad idea. Besides in practice you usually don't want to delete them all anyway, but only all processes matching a certain query (using some script, or older than some date, etc). So that's perhaps something to look at in conjunction with a query feature on the process overview page later on.
I also like @mwoodiupui's idea of auto-expiring processes after a set duration. But that would be (almost) entirely a backend feature, so it should be moved to that repo.
Atmire would like to work on the delete buttons in the UI, as I described above though. That would take an estimated 8 hours
Since @tdonohue is on holiday, I'll assign this to myself


Add Windows Auth support in the ApplicationBuilder

I would like to configure Windows Auth, similar to how currently OAuth or JWT tokens can be configured.
Currently, Kestrel does not support Windows Auth, so IIS or HttpSys has to be used. IIS can be configured, but HttpSys is currently completely missing (is it?)
Therefore I would like to have

an option to configure HttpSys
configure Windows Auth on ISS/HttpSys.

I already started playing around with possible implementations H E R E
, but I am not at all happy with the APIs yet and would love some advice on how to do the API and pursue an implementation.
Downsides
Implementing this will create an additional dependency on the Microsoft.AspNetCore.Server.HttpSys package.

About the downside. As most of the features are on computation expressions, you could have it in a different package, adding a new extension method to the relevant CE and it would just work. That would make the feature optional yet transparent.

Ahh. Awesome. Was not aware you could extend CEs. Thanks for pointing this out!

From: Diego Esmerio<EMAIL_ADDRESS>Sent: Friday, June 1, 2018 9:12:10 PM
To: SaturnFramework/Saturn
Cc: Christian Steinert; Author
Subject: Re: [SaturnFramework/Saturn] Add Windows Auth support in the ApplicationBuilder (#62)
About the downside. As most of the features are on computation expressions, you could have it in a different package, adding a new extension method to the relevant CE and it would just work. That would make the feature optional yet transparent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SaturnFramework/Saturn/issues/62#issuecomment-393981835, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJaTxfNdcRW5nDjciIoxhNYBYBGjK3uaks5t4ZIKgaJpZM4UXF4F.

In general problem of handling "extensions" in interesting one (and it's not about only this suggestion but I've also talked with @forki  who needed Redis caching). I think what I want to do is create directory in this repo that will contain extensions in form of .fs file + paket.dependencies file - this way you can add extension with paket file ref and paket will also add deps of your extension to the project.

I have added an "extension" implementing this here. @Krzysztof-Cieslak - if you could have a look if that is what you had in mind? I also added a sample.

You also need paket.dependencies file next to .fs to make Paket's GitHub deps work - https://fsprojects.github.io/Paket/github-dependencies.html#Remote-dependencies
However, maybe just releasing NuGet packages is better idea? this way we don't couple framework with Paket.
CC: @forki @isaacabraham Any opinions?

I vote for releasing nuget packages, easier and could just have the extension on the references and Saturn would be get as a dependency. Much cleaner and friendlier.

This is what we did on Fable.Remoting before migrating it all to a computation expression based API. Worked well enough as a nuget package.

Personally I prefer github files for these kind of lightweight things - single files etc. They can be changed more easily than a nuget package, and I think is especially useful whilst we're in a kind of exploration phase. They could even be part of this repo a folder or branch with each extension in its own sub folder.

Hey, sorry for delay.
I think I we should go with NuGet packages - this way we're not tightly coupled to one Paket's feature (and I guess most of those extensions will be simple enough that if someone prefers file dependency than they should be able to use it) and makes it easier for 3rd party extensions.
@ChrSteinert, if you want to add extension to this repo put it in src/Saturn.HttpSys folder and send PR. I'll be happy to publish it from here.


Expensive CPU time for CollectMetrics

My environment:

Slackware 14.2;
Go 1.6.3;
15 devices in iostat;

This plugin when collecting /intel/linux/iostat/device/*/* in 1s intervals takes 32% CPU per collect, which seems excessive to me.
Using 'iostat -xd 1' uses 0.4%.
Don't know if this is fixable, but it appears that the job of this plugin is "just" to get the output of iostat into a snap-compatible format, right? I don't why it takes this much CPU time for this.
@IRCody, would you mind adding @intelsdi-x/plugin-maintainers to this issue? Thanks :)

@intelsdi-x/plugin-maintainers

Looks like @mjbrender beat me to it!

I've added some large test to look into this further (#24). Initial testing shows around 28s cpu time to gather metric at 1s interval 500 times. I'm not sure if this grows significantly if the number of disk increases, and I'll try to access a system with more disks for comparison.
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
  564 root      20   0   14592  12308   5068 S   3.7  0.6   0:28.86 snap-plugin-col
  199 root      20   0   35440  31352  10524 S   0.3  1.5   0:04.69 snapteld

Based on the fact the issue cannot  be reproduced (probably it's HW dependent). Please reopen that if you would like to continue discussion.


cmd/prometheus: fix remote storage fanout

@juliusv @jmcfarlane

I confirmed that this does fix the filtered metrics not being sent to influxdb-0.9 in #802


Synchronous error response must match the agreed format, i.e. use xml tags and codes

As a Market Participant submitting invalid requests* to the charges domain
I want to receive synchronous error that complies to the agreed format
So that my system may process it correctly.
* Violating:

Schema validation
Sender provided in body does not match organization in bearer token

Agreed format for a synchronous error response can be found here, see section "2.3 Validering af forespørgsler"
Currently our response is not wrapped in xml tags as seen here:

Notes:
Please investigate if we are to use the existing B2B-codes used by DataHub2 or not.
Acceptance criteria:

[ ] 1 Given a request is made that violates schema validation (both for Charges and Charge Links)
When receiving a synchronous bad request response
Then the error body is formatted according to the agreed format
And using the correct B2B-code

[ ] 1 Given a request is made that violates 'Sender mismatch' (both for Charges and Charge Links)
When receiving a synchronous bad request response
Then the error body is formatted according to the agreed format
And uses the correct B2B-code

Tested in T-001:
When violating schema - Charges & Charge Links - Reponse:
<?xml version="1.0" encoding="utf-8"?>
<Error>
  BadArgument
  <Message>The specified input does not pass schema validation.</Message>

    <Error>
      SchemaValidationError
      <Message>The element 'RequestChangeBillingMasterData_MarketDocument' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1' has invalid child element 'MktActivityRecord' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1'. List of possible elements expected: 'createdDateTime' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1'.</Message>
      <InnerError>
        <LineNumber>13</LineNumber>
        <LinePosition>6</LinePosition>
      </InnerError>
    </Error>

</Error>

:warning: BadArgument is used instead of B2B-005, when violating schema.
I suggest we place a change in the nuget package used, where we replace BadArgument with B2B-005. Let's discuss this.
When violating 'mismatch sender information' - Charge & Charge Links, response:
<Error>
  B2B-008
  <Message>The sender organization provided in the request body does not match the organization in the bearer token.</Message>
</Error>

Team agreed to pursue changing the code returned by the schema validation nuget package, so it is B2B-005 instead of BadArgument. I'll reach out to team Titans

Another test in T-001 for AC 1 :white_check_mark:
Response when violating schema (Charge):
<?xml version="1.0" encoding="utf-8"?>
<Error>
  B2B-005
  <Message>The specified input does not pass schema validation.</Message>

    <Error>
      SchemaValidationError
      <Message>The element 'RequestChangeOfPriceList_MarketDocument' in namespace 'urn:ediel.org:structure:requestchangeofpricelist:0:1' has invalid child element 'MktActivityRecord' in namespace 'urn:ediel.org:structure:requestchangeofpricelist:0:1'. List of possible elements expected: 'createdDateTime' in namespace 'urn:ediel.org:structure:requestchangeofpricelist:0:1'.</Message>
      <InnerError>
        <LineNumber>12</LineNumber>
        <LinePosition>3</LinePosition>
      </InnerError>
    </Error>

</Error>

Same, but for Charge Links:
<?xml version="1.0" encoding="utf-8"?>
<Error>
  B2B-005
  <Message>The specified input does not pass schema validation.</Message>

    <Error>
      SchemaValidationError
      <Message>The element 'RequestChangeBillingMasterData_MarketDocument' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1' has invalid child element 'businessSector.type' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1'. List of possible elements expected: 'process.processType' in namespace 'urn:ediel.org:structure:requestchangebillingmasterdata:0:1'.</Message>
      <InnerError>
        <LineNumber>7</LineNumber>
        <LinePosition>6</LinePosition>
      </InnerError>
    </Error>

</Error>


(build-tools) Fixes to policy-check and assert-short-codes handler

Description
Fix a couple of things:

Logic in the policy-check tool so we only run final() for the handlers that match the input regex if one was specified, instead of always running final() for every handler. Without this, final() would be executed even for handlers that don't match the input regex and for the assert-short-codes one this meant that the mapping file was rewritten with a completely empty map (the handler needs to run its handler() function first to populate internal data structures used by final()). Other handlers might have had issues, I didn't look at them in detail.
Logic in the assert-short-codes handler to remove leading+trailing double quotes or backticks only if they are found exactly at the beginning and end of the comment and nowhere else, so as not to mess up comments that use them differently (e.g. "somePropery" cannot be null).
Restore full text for some string values in the assert code mapping file which were incorrectly modified due to the bug in the handler.
Fix word order in docs.

Reviewer guidance
If anyone is familiar with the policy-check handlers other than assert-short-codes, it'd be good to get an idea if the bug fix around calling final() might break existing behavior that depended on it.
AB#2815

/azp run Build - client packages


Misconfiguration of stderr in diversify.utils.util.py get_args()

Hey!
Thanks for open-sourcing you project(s)!
While referencing chatgpt-robust for another project, I encountered your usage with Tee() in diversify.utils.util.py.
Snippets:
class Tee:
    def __init__(self, fname, mode="a"):
        self.stdout = sys.stdout
        self.file = open(fname, mode)

    def write(self, message):
        self.stdout.write(message)
        self.file.write(message)
        self.flush()

    def flush(self):
        self.stdout.flush()
        self.file.flush()

    sys.stdout = Tee(os.path.join(args.output, 'out.txt'))
    sys.stderr = Tee(os.path.join(args.output, 'err.txt'))

As far as I understand you mix stderr with stdout. What do you think?
Let me know if you want me to submit a PR and suggest a solution :-)

Thanks for the quick and nice comment! will do :)


Open multiple tabs with middle click while mtab stays open

Hi, I really love this extension but I feel like there really needs to be a middle click to open in another tab while still having mtab open, just like the vanilla Firefox homepage. I like to open multiple tabs at once from my homepage and I would definitely appreciate its addition as it is important to my workflow ❤.

You can press ctrl-left click to open a bookmark in a new tab and ctrl-enter to open search in a new tab.
Hope this helps.

Oh didn't know I could ctrl-left click! it sure does the trick but I would love to have middle click to open as I have muscle memorized it 😅.

Okay, I'm planning to add middle click open soon.

I added it, should middle click should work in the next release.


upgrade nikunjy/rules module

Description
I updated this module to depend on a newer version of nikunjy/rules. Prior to this, I updated nikunjy/rules to depend on antlr/v4 (antlr broke backwards compatibility)
I'm a bit uncertain if we should instead make nikunjy/rules v2 first.
I ran
go get github.com/nikunjy/rules@master; go mod tidy -compat=1.17 from master.
Pull request: https://github.com/nikunjy/rules/pull/26

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking changes (change that is not backward-compatible and/or changes current functionality)

Closes issue(s)
https://github.com/thomaspoignant/go-feature-flag/issues/348

Resolve #
Checklist

[ ] I have tested this code
[ ] I have added unit test to cover this code
[ ] I have updated the documentation (README.md and /docs)
[ ] I have followed the contributing guide

Coverage remained the same at 95.096% when pulling 3ce49677ac1f9066f5bc0d029e99e7def57950fa on juliandanciu:upgrade_nikunjy_rules_module into c6b627a0ea0ac54c2a54dc382ffdae5b3488fc72 on thomaspoignant:main.

We should probably move to nikunjy/rules v2.0.0 but we should check the compatibility first.
I'll open an issue to keep track of this when releasing the version 1.0.0.

We should probably move to nikunjy/rules v2.0.0 but we should check the compatibility first. I'll open an issue to keep track of this when releasing the version 1.0.0.

Okay. I opened a pull request for nikunjy/rules to create a v2 directory.


Made count_overflow_pixels() public and added a test for it in tests.rs

Okay, I was able to reset my git branch, and I have put the test in the tests.rs file instead of the lib.rs file. The test is rearranged to have the assertions directly after their input data.

Good job, thank you!


Rename emoji.ts to Emoji.ts

Fixing tsc lint issues.

Will be opening all changed in a single PR.


Fix exists check issue

Fix wrong position of parenthesis.
Signed-off-by: Yadong Qi<EMAIL_ADDRESS>

Building VM-Manager Code. For more details refer below link:
job/satg-aee-android-ci/job/VM-MANAGER-PR-FLOW/152/

Building VM-Manager Code. For more details refer below link:
job/satg-aee-android-ci/job/VM-MANAGER-PR-MERGE-FLOW/105/

Build successful.
job/satg-aee-android-ci/job/VM-MANAGER-PR-FLOW/152/

Please find the Deb Package Path :
artifactory/dev-automation-ba-local/vm-manager-binaries/331/PR/ac6a2e8

Build successful.
job/satg-aee-android-ci/job/VM-MANAGER-PR-MERGE-FLOW/105/

Please find the Deb Package Path :
artifactory/dev-automation-ba-local/vm-manager-binaries/331/MR/ac6a2e8


Error when calling db.collection.distinct

db.collection.distinct('category')
Error : db.alerts.distinct is not a function TypeError: db.collection.distinct is not a function at evalmachine.:1:11 at ContextifyScript.Script.runInNewContext (vm.js:18:15) at /Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/lib/modules/expression/index.js:170:23 at Promise._execute (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/debuggability.js:159:9) at Promise._resolveFromExecutor (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:460:18) at new Promise (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:76:14) at _eval (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/lib/modules/expression/index.js:140:10) at /Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/lib/modules/expression/index.js:39:9 at Promise._execute (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/debuggability.js:159:9) at Promise._resolveFromExecutor (/Users/username/Downloads/Mongotron-darwin-x64/Mongotron.app/Contents/Resources/app.asar/node_modules/bluebird/js/release/promise.js:460:18)
However, if I log into the mongo shell and execute the same query, I get the list of categories.
MongoDB shell version: 2.4.8
(NOTE: collection name and username redacted and replaced with the term "collection" and term "username")

I forgot to mention the version of Mongotron I am using is 1.0.0-alpha4

Fixed in 1.0.0-alpha.5


feat: Added card_height option

feat: create height option

Created input for height option in form (src/demo/index.php)
Update custom image height in process (src/card.php)

Description

Fixes #659
Type of change

[x] Bug fix (added a non-breaking change which fixes an issue)
[x] New feature (added a non-breaking change which adds functionality)
[ ] Updated documentation (updated the readme, templates, or other repo files)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

[x] Tested locally with a valid username
[x] Tested locally with an invalid username
[ ] Ran tests with composer test
[ ] Added or updated test cases to test new features

Checklist:

[ ] I have checked to make sure no other pull requests are open for this issue
[x] The code is properly formatted and is consistent with the existing code style
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

Screenshots

I made a small change that help with this issue.

Thanks


[SPARK-LLAP-209] Add jackson exclusions to fix SparkSession use in unit tests

What changes were proposed in this pull request?
Add jackson exclusion in 1 Tez and 1 Hive module dependency
How was this patch tested?
Existing unit tests succeed
[info] ScalaTest
[info] Run completed in 8 seconds, 262 milliseconds.
[info] Total number of tests run: 25
[info] Suites: completed 4, aborted 0
[info] Tests: succeeded 25, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[info] Passed: Total 25, Failed 0, Errors 0, Passed 25
[success] Total time: 39 s, completed May 6, 2018 8:11:43 PM

Thank you for fixing UTs, @EricWohlstadter .