Missing modules

Getting this when I run npm start.
Node 4.0.0,
npm 3.3.3,
react-native 0.11.4
Server listening at http://localhost:8080
Unable to resolve module LinkedStateMixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactComponentWithPureRenderMixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactUpdates from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module cloneWithProps from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactFragment from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module update from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactDefaultPerf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactTestUtils from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native/react-native.js
Unable to resolve module ReactChildren from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactClass from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactComponent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactCurrentOwner from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactElement from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactElementValidator from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactInstanceHandles from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactUpdates from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module deprecated from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module onlyChild from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module ReactReconciler from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNative.js
Unable to resolve module EventPluginHub from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module EventPluginUtils from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactComponentEnvironment from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactDefaultBatchingStrategy from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactEmptyComponent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactInstanceHandles from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactNativeComponent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module ReactUpdates from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDefaultInjection.js
Unable to resolve module regenerator/runtime from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/Initialization/InitializeJavaScriptAppEngine.js
Unable to resolve module ReactUpdates from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/MessageQueue.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/MessageQueue.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/MessageQueue.js
Unable to resolve module ReactPerf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/BridgeProfiling.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimersExecution.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimersExecution.js
Unable to resolve module performanceNow from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimersExecution.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/System/JSTimers/JSTimersExecution.js
Unable to resolve module ReactInstanceHandles from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Inspector/InspectorUtils.js
Unable to resolve module ReactInstanceMap from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Inspector/InspectorUtils.js
Unable to resolve module ReactElement from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module ReactPerf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module ReactReconciler from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module ReactUpdateQueue from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module ReactUpdates from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module emptyObject from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module instantiateReactComponent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module shouldUpdateReactComponent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeMount.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeTagHandles.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeTagHandles.js
Unable to resolve module ReactCurrentOwner from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/findNodeHandle.js
Unable to resolve module ReactInstanceMap from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/findNodeHandle.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/findNodeHandle.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/findNodeHandle.js
Unable to resolve module emptyFunction from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/EventEmitter.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/EventEmitter.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/EventSubscriptionVendor.js
Unable to resolve module performanceNow from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/PerformanceLogger.js
Unable to resolve module promise/setimmediate/es6-extensions from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Promise.js
Unable to resolve module promise/setimmediate/done from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Promise.js
Unable to resolve module stacktrace-parser from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/JavaScriptAppEngine/Initialization/parseErrorStack.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Geolocation/Geolocation.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Geolocation/Geolocation.js
Unable to resolve module SyntheticEvent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/IOSNativeBridgeEventPlugin.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/IOSNativeBridgeEventPlugin.js
Unable to resolve module EventConstants from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/event/EventPropagators.js
Unable to resolve module EventPluginHub from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/event/EventPropagators.js
Unable to resolve module accumulateInto from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/event/EventPropagators.js
Unable to resolve module forEachAccumulated from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/event/EventPropagators.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/core/mergeHelpers.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/core/mergeHelpers.js
Unable to resolve module ReactMultiChildUpdateTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDOMIDOperations.js
Unable to resolve module ReactPerf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeDOMIDOperations.js
Unable to resolve module CallbackQueue from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeReconcileTransaction.js
Unable to resolve module PooledClass from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeReconcileTransaction.js
Unable to resolve module Transaction from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeReconcileTransaction.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Interaction/InteractionManager.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Interaction/InteractionManager.js
Unable to resolve module isNode from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/core/Map.js
Unable to resolve module Object.assign from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeTextComponent.js
Unable to resolve module EventConstants from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module EventPluginUtils from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module ReactInstanceHandles from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module ResponderSyntheticEvent from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module ResponderTouchHistoryStore from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module accumulate from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module keyOf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/browser/eventPlugins/ResponderEventPlugin.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react/platformImplementations/universal/worker/UniversalWorkerNodeHandle.js
Unable to resolve module ReactMultiChild from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeBaseComponent.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeBaseComponent.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/NativeMethodsMixin.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/flattenStyle.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/precomputeStyle.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/MatrixMath.js
Unable to resolve module EventPluginHub from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeEventEmitter.js
Unable to resolve module ReactEventEmitterMixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeEventEmitter.js
Unable to resolve module EventConstants from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeEventEmitter.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeEventEmitter.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactNative/ReactNativeStyleAttributes.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Image/ImageStylePropTypes.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Image/ImageResizeMode.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/LayoutPropTypes.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/TransformPropTypes.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Text/TextStylePropTypes.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/View/ViewStylePropTypes.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/RCTLog.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/ActivityIndicatorIOS/ActivityIndicatorIOS.ios.js
Unable to resolve module ReactPropTypeLocations from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/StyleSheetValidation.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/StyleSheetValidation.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/View/View.js
Unable to resolve module ReactPropTypeLocationNames from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/createStrictShapeTypeChecker.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/createStrictShapeTypeChecker.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/requireNativeComponent.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/DatePicker/DatePickerIOS.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Image/Image.ios.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Image/Image.ios.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Image/Image.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/EdgeInsetsPropType.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/Dimensions.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/ListView/ListView.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/ListView/ListViewDataSource.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/ListView/ListViewDataSource.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/StyleSheet/PointPropType.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/ScrollResponder.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Modal/Modal.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigator.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigator.js
Unable to resolve module rebound from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigator.js
Unable to resolve module emptyFunction from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigation/NavigationContext.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigation/NavigationContext.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/Navigation/NavigationEvent.js
Unable to resolve module immutable from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/NavigatorBreadcrumbNavigationBar.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/NavigatorBreadcrumbNavigationBar.js
Unable to resolve module keyOf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/buildStyleInterpolator.js
Unable to resolve module onlyChild from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react_contrib/StaticContainer/StaticContainer.js
Unable to resolve module immutable from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CustomComponents/Navigator/NavigatorNavigationBar.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Navigation/NavigatorIOS.ios.js
Unable to resolve module ReactChildren from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Picker/PickerIOS.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/ProgressViewIOS/ProgressViewIOS.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/SegmentedControlIOS/SegmentedControlIOS.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/SliderIOS/SliderIOS.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/SwitchIOS/SwitchIOS.ios.js
Unable to resolve module ReactInstanceMap from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Text/Text.js
Unable to resolve module TouchEventUtils from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react_contrib/interactions/Touchable/Touchable.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react_contrib/interactions/Touchable/Touchable.js
Unable to resolve module PooledClass from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react_contrib/pooledClasses/BoundingDimensions.js
Unable to resolve module PooledClass from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/react_contrib/pooledClasses/Position.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/TextInput/TextInput.js
Unable to resolve module ReactChildren from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/TextInput/TextInput.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/TextInput/TextInput.js
Unable to resolve module emptyFunction from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/TextInput/TextInput.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/TextInput/TextInput.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/mixInEventEmitter.js
Unable to resolve module keyOf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/mixInEventEmitter.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/vendor/emitter/EventHolder.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableWithoutFeedback.js
Unable to resolve module onlyChild from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableWithoutFeedback.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/ensurePositiveDelayProps.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/ToastAndroid/ToastAndroid.ios.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableHighlight.js
Unable to resolve module cloneWithProps from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableHighlight.js
Unable to resolve module keyOf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableHighlight.js
Unable to resolve module onlyChild from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableHighlight.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/ensureComponentIsNative.js
Unable to resolve module react-timer-mixin from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js
Unable to resolve module keyOf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/Touchable/TouchableOpacity.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Animated/Animated.js
Unable to resolve module requestAnimationFrame from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Animated/Animated.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/WebView/WebView.ios.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Components/WebView/WebView.ios.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ActionSheetIOS/ActionSheetIOS.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/AlertIOS.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/AppRegistry/AppRegistry.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/renderApplication.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Inspector/ElementProperties.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/WarningBox.js
Unable to resolve module rebound from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/ReactIOS/WarningBox.js
Unable to resolve module ReactCurrentOwner from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Devtools/setupDevtools.js
Unable to resolve module ReactInstanceHandles from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Devtools/setupDevtools.js
Unable to resolve module ReactReconciler from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Devtools/setupDevtools.js
Unable to resolve module ReactDefaultPerf from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/RCTRenderingPerf.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/RCTRenderingPerf.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/AppStateIOS/AppStateIOS.ios.js
Unable to resolve module warning from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Utilities/BackAndroid.ios.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CameraRoll/CameraRoll.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/CameraRoll/CameraRoll.js
Unable to resolve module ReactPropTypes from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js
Unable to resolve module keyMirror from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/LayoutAnimation/LayoutAnimation.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/LinkingIOS/LinkingIOS.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/PushNotificationIOS/PushNotificationIOS.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Settings/Settings.ios.js
Unable to resolve module invariant from /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/Vibration/VibrationIOS.ios.js
Webpack dev server listening at  http://localhost:8082
Hash: 4d908b290aef34173fbd
Version: webpack 1.12.2
Time: 424ms
               Asset     Size  Chunks       Chunk Names
    index.android.js  15.1 kB       0       index.android
        index.ios.js  13.7 kB       1       index.ios
index.android.js.map  23.3 kB       0       index.android
    index.ios.js.map  21.7 kB       1       index.ios
chunk    {0} index.android.js, index.android.js.map (index.android) 8.85 kB [rendered]
chunk    {1} index.ios.js, index.ios.js.map (index.ios) 7.46 kB [rendered]

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'LinkedStateMixin' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 88:22-49

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'ReactComponentWithPureRenderMixin' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 90:21-65

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'ReactUpdates' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 93:20-43

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'cloneWithProps' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 94:20-45

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'ReactFragment' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 95:20-44

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'update' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 96:12-29

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'ReactDefaultPerf' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 101:28-55

ERROR in ./~/react-native/Libraries/react-native/react-native.js
Module not found: Error: Cannot resolve module 'ReactTestUtils' in /home/ulrik/projects/MyAwesomeApp/node_modules/react-native/Libraries/react-native
 @ ./~/react-native/Libraries/react-native/react-native.js 102:33-58

Thanks for your report @ulrikaugustsson and sorry to hear about your troubles. I installed node v4.0.0, which shipped with npm 2.14.2and had no problems installing and running the app. Giving you're using a beta version of npm you may have more luck using a version of npm prior to3.x`, which is currently in beta. Cheers and good luck.

what can i do?
Module not found: Error: Can't resolve 'react-native/Libraries/EventEmitter/EventEmitter' in


Document seedImage in UI quickstart

Fix #89

Do not know if I have to talk about the hard-coded OS Version or we will talk about it once it will not hard-coded anymore.


Docs: Make scripts compatible with Python 3

https://python-future.org/compatible_idioms.html

[x] Transform with 2to3 script
[x] Review automatic transforms
[x] Optimize code
[x] Test scripts with Python 2
[ ] Test scripts with Python 3

https://jenkins01.arangodb.biz/view/Documentation/job/arangodb-ANY-examples/418/console
Python seems to be 2.7, not sure how to test 3.x on the same machine... change invocations to python3 or via shebang?

Looks like there is an encoding related error in python3:
https://jenkins01.arangodb.biz/view/Documentation/job/arangodb-ANY-examples/427/console
13:32:28 Generating swagger
13:32:28 while parsing '/work/ArangoDB/Documentation/DocuBlocks/Rest/Views/post_api_view_arangosearch.md'
13:32:28 trying to use handler 'skip_code'
13:32:28
13:32:28 while parsing file: '/work/ArangoDB/Documentation/DocuBlocks/Rest/Views/post_api_view_arangosearch.md' error: 'ascii' codec can't decode byte 0xe2 in position 1237: ordinal not in range(128)
13:32:28 Traceback (most recent call last):
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 1464, in <module>
13:32:28     getOneApi(infile, name + " - " + ', '.join(filenames), fn)
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 1311, in getOneApi
13:32:28     automat.run((infile, ''))
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 402, in run
13:32:28     raise x
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 390, in run
13:32:28     (newState, cargo) = handler(cargo)
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 1274, in skip_code
13:32:28     return comment((fp, last), r)
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 1252, in comment
13:32:28     line = fp.readline()
13:32:28   File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
13:32:28     return codecs.ascii_decode(input, self.errors)[0]
13:32:28 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1237: ordinal not in range(128)
13:32:28
13:32:28 During handling of the above exception, another exception occurred:
13:32:28
13:32:28 Traceback (most recent call last):
13:32:28   File "/work/ArangoDB/utils/generateSwagger.py", line 1467, in <module>
13:32:28     raise Exception("while parsing file '%s' error: %s" %(thisfn, x))
13:32:28 Exception: while parsing file '/work/ArangoDB/Documentation/DocuBlocks/Rest/Views/post_api_view_arangosearch.md' error: 'ascii' codec can't decode byte 0xe2 in position 1237: ordinal not in range(128)
13:32:28 FAILED!

18:39:12 Automatic merge failed; fix conflicts and then commit the result. ?!
https://jenkins01.arangodb.biz/view/Documentation/job/arangodb-ANY-examples/431/console

No errors in my test run using https://github.com/arangodb/oskar/tree/python3-compat and https://github.com/arangodb/arangodb/pull/10320/commits/426bca5acece8b6cda63d6258096f7f9ecfc6382
https://jenkins01.arangodb.biz/view/Documentation/job/arangodb-ANY-examples/449/console
https://github.com/arangodb/docs/pull/246

It looks like generateLicense.py was already broken in both Python 2 and 3?!
Fails with py2 because of str(response.read(), "utf-8", "ignore") - looks like the 3 argument variant is py3 only?
Fails with py3 because strings are passed to html.startswith(…) but html is a bytes object.

Failing in Jenkins:
[
17:41:39   "utils/generateExamples.py",
17:41:39   "--outputDir",
17:41:39   "/work/ArangoDB/Documentation/Examples",
17:41:39   "--outputFile",
17:41:39   "/work/ArangoDB/arangosh.examples.js",
17:41:39   "--arangoshSetup",
17:41:39   "/work/ArangoDB/Documentation/Scripts/setup-arangosh.js",
17:41:39   "/work/ArangoDB/Documentation/DocuBlocks",
17:41:39   "/work/ArangoDB/Documentation/Books/Manual",
17:41:39   "/work/ArangoDB/Documentation/Books/AQL",
17:41:39   "/work/ArangoDB/Documentation/Books/HTTP",
17:41:39   "--storageEngine",
17:41:39   "mmfiles",
17:41:39   "--storageEngineAgnostic",
17:41:39   false,
17:41:39   "--cluster",
17:41:39   false
17:41:39 ]
17:41:39 Traceback (most recent call last):
17:41:39   File "utils/generateExamples.py", line 738, in <module>
17:41:39     loopDirectories()
17:41:39   File "utils/generateExamples.py", line 697, in loopDirectories
17:41:39     analyzeFile(f, filename)
17:41:39   File "utils/generateExamples.py", line 281, in analyzeFile
17:41:39     for line in f:
17:41:39   File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
17:41:39     return codecs.ascii_decode(input, self.errors)[0]
17:41:39 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1237: ordinal not in range(128)
17:41:39 parsing the examples failed - aborting!
17:41:39 {
17:41:39   "pid" : 83,
17:41:39   "status" : "TERMINATED",
17:41:39   "exit" : 1
17:41:39 }

Might have to specify utf-8 encoding on open (io.open for compatibility). Does the newline option matter in generateExamples.py?

https://jenkins01.arangodb.biz/view/Documentation/job/arangodb-ANY-examples/579/

@jsteemann Jenkins run succeeded. Good enough to merge IMO. Should we get into trouble again then we can fix that later.


Use dedicated partitions for each layout

This makes it possible to use homogeneous partitions, so only the data from one particular event type ends up in a partition.
Requires #2120!
:memo: Checklist

[ ] All user-facing changes have changelog entries.
[ ] The changes are reflected on docs.tenzir.com/vast, if necessary.
[ ] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions

This makes sense. Regarding memory usage, I want to raise the concern of slicing out types from record batches that keep alive large chunks of memory while only a small fraction is ever needed. This is the detach discussion we had the other day. My intuition is that this is now amplified. I'd like to figure out a way to measure it.

@mavam We already detach the schema in table slices, so this is not a concern.

We probably should register active partitions with the meta index catalog, although I'm not quite sure if that should be part of this PR. It's not critical, but definitely warrants a follow-up story that we tackle in the short- to medium-term.

I veto this approach. The catalog has no business with active partitions and it must stay that way. We want to be able to run the active and passive parts of the database on different nodes, and such a change would only add communication overhead.
I think the query should get sent to each active partition, but the lookup function should consult the active partition synopsis. This is completely orthogonal though and it should not be done in this PR.

This is completely orthogonal though and it should not be done in this PR.

👆 That. Exactly. Let's not couple things together can operate in a decoupled manner.
For this PR, it's completely fine to not run queries over active partitions (or "partition builders").

I approve of @dominiklohmann 's changes as well.


Factory constructor of 'A' class delegated to a constructor of 'B' class returns instance of 'A' class instead of 'B'

Factory constructor of 'A' class delegated to a constructor of 'B' class returns instance of 'A' class instead of 'B'
So this code cannot be compiled (A value of type 'A' can't be returned from a function with return type 'B'):
B createInstance() {
  return A.myFactoryMethod();
}

class A {
  A._();

  factory A.myFactoryMethod() = B;
}

class B extends A {
  B(): super._();
}

Can be reproduced when 'null safety' enabled only. It's unexpected behaviour and breaks the behaviour worked in previous versions of 'not null safe' Dart.
I often used previous behavior when used Freezed classes with factory constructors.
Dart SDK 2.12.2
Windows

This is working as intended - implicit down-casts are disabled in null safe Dart.
You have to cast explicitly: A.myFactoryMethod() as B.

It doesn't make the language friendly.
From the perspective of a developer, I just delegated creating of new instance to another constructor. So I don't understand why compiler cannot get the type of instance out of there but not from original class. All necessary information is already stored in the factory constructor.
I don't suggest to downcast type. I suggest originally store correct information about factory constructor type.

I suggest originally store correct information about factory constructor type.

Constructors on class A return instances of A. There is no difference between:
class A {
  factory A.redirecting() = B;
}

and
class A {
  factory A.redirecting() => B();
}

The whole idea with redirecting factories is that they allow you to hide the implementation - so it does not make sense to have a different (more specific) return type.
Furthermore: such change is going to break things in strange ways. Consider for example:
class A {
  factory A.x() = X;
  factory A.y() = Y;
}

class X extends A { }
class Y extends A { }

final list = [A.x()];
list.add(A.y());  // (*)

Line marked with (*) will be a compile time error if A.x has return type X.
If you know that A.myFactoryMethod delegates to B then you should either cast or even better just invoke B directly:
B createInstance() {
  return B();
}

IIRC Freezed generates public classes for your variants - so this will work just fine.

Yes, Freezed generates public classes and I can use them, but it means that I cannot use factory constructors directly (or I have to cast every time). Sounds bad.
As for your example with
final list = [A.x()];
list.add(A.y())

the same behaviour will be with any type of constructors, so I don't see a problem here.
final list = [X()];
list.add(Y())

The same expected compile-time error and it's ok.
I don't see disadvantages of my suggestion, but I see disadvantages of current behaviour + it brokes the behaviour existed before.

The same expected compile-time error and it's ok.

It's not okay because it is a breaking change (as it changes inferred type of [A.x()], think that A it can be some common class in the SDK like Map which uses redirecting factories to hide implementation) and breaking changes have very high bar.
Furthermore, as I have said above, this violates the following fundamental properties of constructors:

Constructors on A return A.
Factories hide implementation allowing you to change implementation without breaking user code.
Redirecting factories are just convenience shorthand for factories.

I let @lrhn @eernstg @leafpetersen pass actual judgement here, but I'd say fairly confidently based on the arguments above that there is absolutely no chance that return type of the redirecting factory would be changed to expose actual implementation type.

Thank you for your answer

@mraleph is correct. The intended model is that a redirecting factory constructor is an abstraction (all factory constructors are), and it's considered an implementation detail which object it actually returns. You should be able to change the actual returned type at any time without changing the program's types.
If you really intend to make A.something() return a B every time, just make it a static method instead of a constructor:
class A {
  A._();

  static B myFactoryMethod() => B();
}

@lrhn I have a vague memory that we have discussed allowing factory constructors to have an explicit return type which is different than the enclosing class type, do I remember this correctly?  Do we have a request for it?

We can use a type alias to achieve a similar redirection as a redirecting factory constructor. We can't use the same name for the type alias and for the class, so it's not an alternative to having the redirecting factory with a different return type: it just serves to illustrate the associated inference task:
// Needs `--enable-experiment=nonfunction-type-aliases` until 2.13.

abstract class A<X> {
  X get x;
  // The typedef below pseudo-emulates this factory:
  // factory A(X x, X y) = B<X, X>;
}

typedef A_typedef<X> = B<X, X>;

class B<X, Y> implements A<X> {
  X x;
  Y y;
  B(this.x, this.y);
}

void main() {
  // `A_typedef(..., ...)` would have been `A(..., ...)` if we had those factories.
  var x1 = A_typedef(2, 3); // Type `B<int, int>`.
  print(++x1.y); // So we can use `B` members; prints '4'.
  var x2 = A_typedef(2, 2.71828); // How about arguments with different types?
  print(x2.runtimeType); // 'B<num, num>'.
}

If we had factories with user-specified return types, A<T>(..., ...) should yield an object whose type is a subtype of A<T>, for any T. So for inference on A(2, 3) we must use a T such that int <: T, and we get int as expected, and the type of A(2, 3) is B<int, int>. But with A(2, 2.71828) we must satisfy int <: T and double <: T, and we get B<num, num>, not B<int, double>.
So even though it might look like we can just "macro expand" the redirecting factory at the call site and then perform inference, it's a bit more involved than that.

I don't think we have a request for constructor return types (or restricted constructor type arguments, as it would be).
It could be something like:
class Heap<T> {
  Heap(int Function(T, T) compare) : ...
  Heap<R extends Comparable<R>>.comparable() : ...
}

That would be better than what we do now in some places, where compare is optional, but if you omit it, it dynamically calls compare on the elements. The "solution" is to use a static factory function instead: static Heap<R> comparable<R>() => Heap<R>(defaultCompare);, but it would be nicer to have an actual constructor.
Or, wait for generic constructors, and allow them to declare the type parameters:
class Map<K, V> {
  factory Map<X, X>.self<X>() = Map<X, X>;
  ...
}

It's not entirely clear how to solve for the constraints of such non-linear types.


How does one color text without violating inline-html rule?

Question:
Is there a way to color text without using inline html and violating MD033?

CommonMark does not have a notion of text color changes, so no.


CorsixTH

Motivation for this change
This is a Nix port for the CorsixTH. This has been developed in https://github.com/CorsixTH/CorsixTH/pull/1881 and accepted by maintainers on CorsixTH branch. This PR makes minor changes to fit Nixpkgs guidelines.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[ ] Fits CONTRIBUTING.md.

Thank you for the thorough review. I've applied the manual changes + the nixpkgs formatting. Let me know if there are additional changes that you noticed!
Have a good day.

Seems, something is going on in other PRs:

https://github.com/NixOS/nixpkgs/pull/241203
https://github.com/NixOS/nixpkgs/pull/250674

nix run nixpkgs#corsix-th
already works for me under nixos-unstable, yay!

Closing as dead and solved.


Extract railroad generator to reusable class

Here's my proposal for a Java API for railroad diagram generation. So why should RR have one? Personally, I plan to use it to create a Maven plugin for RR, but I imagine that having a Java API could make RR useful for a wide variety of other applications.
Notes

The original generation code and logic is unchanged, only moved around and split. I verified that the output files for all three modes (regular, png, md) stay identical to master.
The new RailroadGenerator class uses the same default settings as the CLI.
The CLI's boolean options for choosing the output type are mapped to a single enum.
Some setter names deviate from the previous variables in the hope of making their meaning more obvious:

color ➞ setBaseColor()
spread ➞ setColorOffset()
inline ➞ setInlineLiterals()
keep ➞ setKeepEpsilon()

The new RailroadGenerator class is free of CLI-specific assumptions and defaults:

Colors are passed as java.awt.Color values instead of a hex strings.
The grammar is passed as a string which allows e.g. reading it directly from a UI component; existing decoding logic is kept in Railroad.
Exception: output still defaults to System.out even in RailroadGenerator, not only set by the CLI. The reason is that I'm not yet sure how the API for specifying outputs should look like.

Background: I'm toying with the idea of a working on a PR that introduces an XHTML & PNG mode which writes individual files instead of one zip. This would not involve one specific output stream, but more likely some form of "output strategy".

Caveats

Some of the default settings documented in the new RailroadGenerator class are not implemented in that class, but in the XQuery files. This leads to some ambiguities regarding null. However, I think those are not really relevant.
I noticed that usage() does not list the padding and strokewidth CLI options. I didn't change that as doing so is arguably not within the scope of this PR. Also, the omission may have been intentional.

Looking forward to reading your opinion on this! I hope you find this work acceptable - if not, please just tell me what to change.

Here's my proposal for a Java API for railroad diagram generation. So why should RR have one? Personally, I plan to use it to create a Maven plugin for RR, but I imagine that having a Java API could make RR useful for a wide variety of other applications

I'm also interested to integrate this library in https://kroki.io/
@GuntherRademacher I would suggest to add additional maintainers to help you move this project forward. Maybe @bannmann would be interested? What do you think?

Thanks for sending this PR. I have no objections. Sorry for the delay.


Added tests

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/retest

/retest

/retest

/retest

/retest

/retest

Resolved in #635


Theme of navbar does not switch on mobile view[bug]

The theme change in navbar does not work for mobile view.
This issue can be seen in gif below.

Please assign this issue to me.

@Shivangi-ch Go Ahead


Make scan preserve end value

Scan was clobbering the stream end value by substituting the last value in the stream for the end value.  This makes scan propagate the end value.  As a bonus, it also simplifies the code slightly.
Fix #162

cc @jasonkuhrt

Thanks!


Active-active and no data loss. Is it possible?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

We would like to have pulsar clusters in two data centers. They are active and active. And we would like to replicate messages from one site to the other. i.e. the subscriber from one site will receive messages from publishers at two sites. And no message loss. If one site is down, the other site can continue to work.
We are thinking of geo replication. But since geo replication is asynchronous, we are worried about message loss. Every single message cannot be lost.
Then we are thinking to have synchronous replication, at bookkeeper level, cross two sites. First difficulty is there is no examples of how to do it without global zookeeper. If we use two clusters to manage each site, we need a global configuration store to manage two sites information which becomes a single point failure. If we use global zookeeper, one zookeeper for two sites, due to zookeeper cluster has to be 2*n+1 nodes, it means if the site with n+1 node fails, the other site also stops working.
Is my understanding right? Is there a possible solution with Pulsar for us? Thanks.

We are thinking of geo replication. But since geo replication is asynchronous, we are worried about message loss. Every single message cannot be lost.

Is the message replication guaranteed?
The replication state is stored in a cursor(ledger backend) -> Does this mean it is stored in bookie? What if this bookie crashes?

Yes, it is stored in bookies(data is replicated in the certain bookies). So you can increase the data replicas to avoid data loss.

Yes, it is stored in bookies(data is replicated in the certain bookies). So you can increase the data replicas to avoid data loss.

Thank you. So I understand from you that there is a mechanism to trace or manage which message is replicated and make sure all messages are replicated. That is great.
Is there a mechanism to trace which is message replicated and received by the target cluster/site?
I am also trying if possible to use grafana and prometheus to validate if there is message loss. Any advice here?

Yes, the metrics related to the replication is described at https://pulsar.apache.org/docs/en/reference-metrics/#replication-metrics-1, and https://github.com/streamnative/apache-pulsar-grafana-dashboard already contains message replication related dashboards. You can checkout and try it.

Yes, the metrics related to the replication is described at https://pulsar.apache.org/docs/en/reference-metrics/#replication-metrics-1, and https://github.com/streamnative/apache-pulsar-grafana-dashboard already contains message replication related dashboards. You can checkout and try it.

Thanks. Was trying this dashboard. Had some problems and will figure out why.

Would like to clarify for geo-replication message delivery. Is it more like TCP, every message got acknowledged when it is replicated successfully to the other site, or more like UDP, fire and forget?


category expand not showing correctly

Environment
Docker
Version
0.15.10
Describe the problem
expanding the category is not showing correctly
create 2 or more category and add some icon into each category
everytime this category expand it, the category is not showing correctly. below the category also not moving.
Logs
No response
Context

Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

Duplicate of #676


MimeTypes!

Basic MimeTypes.
Source for MimeTypes: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types

When will we be seeing 3.0?

@NunoAlexandre suggestion was added. getValue() -> to getContentType() value -> contentType

@wherkamp if you can add SVG and we'll merge this. I'll have to rework most of what I have in my stash anyways so there's no point in keeping this stuff frozen.

@LordFokas https://github.com/NanoHttpd/nanohttpd/pull/499/files#diff-6dbbc038ff7d75dc3b7c644ef0831160R59 Already added

Coverage decreased (-1.3%) to 83.92% when pulling 3f8a2e1118db3625d32903cc450e349d570f5adc on wherkamp:master into fd80618e93d17f8f05e11006eaa048a22213714d on NanoHttpd:master.

I have three remarks still:

The current commit messages are not very constructive. They could be:

Add MimeType module
Add toString() function to MimeType
Rename MimeType value field to contentType

instead of

MimeTypes!
toString()
Update MimeTypes.java

There is no reason to have both getContentType() and toString()

This branch adds this module but doesn't use it anywhere. What would be the added value then? Shouldn't it be plugged in?

@wherkamp you have to leave the default toString(), it's not the same thing as the content type.
@NunoAlexandre something may be missing but the MimeType is indeed used.

@NunoAlexandre it is meant to be plugged in here:
https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/org/nanohttpd/protocols/http/response/Response.java#L132
And yes, as I suspected, things are missing, and some other semi-related things are horribly wrong because of course they are. Fixing this library is a job for masochists.

So what needs to get changed for this PR to be accepted?

@NunoAlexandre you could squash and merge if you're not so happy with these commit messages showing up in history. Plus, 5 commits with such small changes don't make sense.

@LordFokas @crearo I am not a member of this project, my feedback is merely suggestive.
Now, those commits are bad, but it's up to the members of the project to reconsider the standard.
@crearo, these should just be squashed indeed!

@NunoAlexandre being "just some guy" with "merely suggestive" but good feedback is how I became a member in the first place 😉
And just because you're not a member that doesn't mean I don't want to hear what you have to say, of course, and I'll be even more willing once I see you commit good stuff and giving more good feedback. I don't exactly disagree with what you've said above (about the toString()) but I do want to keep things simple for the devs but also the users, and semantic / suggestive names are crucial (trust me, I've been mucking with this code for years!).
Not everything the community sends PRs for is good (damn I've fought some battles to keep some nasty crap from being pulled in the past) but I also have the responsibility to drive the community to do things and PR them, so as long as what's coming in is better than what we currently have it's already a great start. This PR for instance matches what I want for 3.0 so I'm glad to have it, even though not everything is perfect (and of course I won't forget to squash).
Small progress is better than no progress 😄

@LordFokas is this ok?

but I do want to keep things simple for the devs but also the users, and semantic/suggestive names are crucial

Right, but you better reconsider what you consider simple and good naming.
We are talking about the MimeType type here. If I read mimeType.toString(), it's simple and clear, while mimeType.getContentType() isn't. What's the content type of a mime type? It's mixing things up: https://stackoverflow.com/questions/48691415/content-type-vs-mime-type.

@wherkamp I don't think so.

MimeTypes should be MimeType (singular)
The private String contentType attribute better be mimetype or value was it was before.
Drop the getContentType() and bring the toString back (see discussion above)
Added evgk/patch-1 tells us nothing of what the commit does. Could you rename it to something like Integrate MimeType

You can git rebase -i origin/master to ammend your commits title and changes in this branch.

@LordFokas  said
@wherkamp you have to leave the default toString(), it's not the same thing as the content type.
I do have to say I have been and very few prs but this is the most intense pr for one Enum.

I am done. Here use it if you want I don't care.  Just because you know how to code and use git doesn't mean you know how to handle what goes on on GitHub. And just because you wanted to nitpick every little detail that's one less user willing to get stuff done. Great job.

Ok in @NunoAlexandre 's defence, there was nothing wrong in what he said. I hate lousy commit messages, and enums typed in plural.

having raised a couple issues before I know @LordFokas you prefer quality code. Better to prefer that than a larger community trotting bad code + history everywhere.

A. few things that class was a copy of some I used in my own projects.
B. 3.0 is it going to be a rewrite?

3.0 is meant to be a refactoring. A massive one.
But boy, does it have a good structure. I might have to redo all of it, step by step to get it to decent working condition.


Add Helm support for local repos in desktop mode

Description

Motivation and Context

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Docs update
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have followed the guidelines in CONTRIBUTING.md, including the required formatting of the commit message

Rebased and included the api package changes


node-bluetooth-hci-socket not support macOS?

I see not support macOS Darwin?

@buitronghieu that's correct. macOS/darwin does not have a concept of Bluetooth HCI sockets.
This module can be manually installed on macOS darwin and use USB Bluetooth adapters directly once the driver has been removed.

@sandeepmistry so exactly how to install manually?

@sandeepmistry so exactly how to install manually?


Question: New Release ?

Hey guys, don't you think its time for a new release?  If so I think it is due to the package js design and they want autopublish only rebuild a package if the release number changes

would also like to use some bug fixes which are not released yet. Would be great if you could provide us a new release! :)

Yeah getting the bug-fixes would be great :+1:

For meteor, if someone submits a pr for package js updating the semver with a minor release number it will trigger a meteor package release.

Here is a pull: https://github.com/Dogfalo/materialize/pull/1521

@dcworldwide Are you sure this should be done by hand ?
There seems to be a grunt task for upgrading the version number, check:
https://github.com/Dogfalo/materialize/blob/v0.96.1/Gruntfile.js#L415

From my understanding of how meteor autopublish works. I do agree that ideally dogfalo should bump version via grunt.

We are working on releasing a new version today


Support SendGrid categories

This makes it possible to attach categories:
|> put_provider_option(:categories, ["hello", ...])

awesome :) sure https://sendgrid.com/docs/API_Reference/api_v3.html

Ah I meant in the code as a comment for future references :) Thanks

Actually it's in the module doc. My bad.

@stevedomin I'm going to merge this one, the first one I merge as a collaborator. Let me know if there is anything I missed.

Thanks @malmovich.
All good @princemaple, thanks for taking care of it!

Cool, no worries. 👍


Night mode

Please add night mode

It's already in the cheat...

I have a question, this cheat of changing the map color would be what?

@Evilhelder Isn't that cheat a private cheat called FlowHooks? I know a Youtube CS:GO cheater, Boring/Noobdog, uses it and it looks awfully similar.

@Evilhelder Isn't that an extremely private cheat called FlowHooks? I know a Youtube CS:GO cheater, Boring/Noobdog, uses it and it looks awfully similar.

Yes it's him, but I've seen this kind of cheat that changes the color of the map texture instead of just putting a color over it ...

@Evilhelder Yeah, I have no idea at this point.

@Evilhelder Does the old alpha version of Flowhooks have it? If you we can convert it and eventually make a pull request to try to paste it.

@Evilhelder Does the old alpha version of Flowhooks have it? If it does then we can convert it and eventually make a pull request to try to paste it.

Good idea, I'll look for it.

Visuals tab> look for world colour..


patche to account for URLs with #fragments

Because the OSM API requires you pass things like "/api/0.6/[node|way|relation]/#id".
No comment.

merging & will patch it a little to correctly work if the fragment starts with a '0'


Initial Implementation

Expose three ways to use JQ:

[ ] Add description to the readme
[ ] add deployment to the Clojars
[ ] cover implementation with tests
[ ] add linter
[ ] add deps checker

(let [jq (time (lmgrep.jq/jq-processor ".a[] |= sqrt"))]
  (quick-bench (jq "{\"a\":[10,2,3,4,5],\"b\":\"hello\"}")))


Interpolate (upsample) non-equispaced timeseries into equispaced 18.0rc1

I want to interpolate (upscale) nonequispaced time-series to obtain equispaced time-series.
Currently I am doing it in following way:

take original timeseries.
create new timeseries with  NaN values at each 30 seconds intervals ( using resample('30S').asfreq() )
concat original timeseries and new timeseries
sort the timeseries to restore order of times (This I do not like - sorting has complexity of O = n log(n) )
interpolate
remove original points from the timeseries

is there a more simple way? like in matlab you have original timeseries and you pass new times as a parameter to the interpolate() function to receive values at desired times.  Ideally I would like to have a function such as
origTimeSeries.interpolate(newIndex=newTimeIndex, method='spline')
I remark that times of original timeseries might not be be a subset of the times of desired timeseries.
import numpy as np
import pandas as pd
import matplotlib.pyplot as plt

values = [271238, 329285, 50, 260260, 263711]
timestamps = pd.to_datetime(['2015-01-04 08:29:4',
                             '2015-01-04 08:37:05',
                             '2015-01-04 08:41:07',
                             '2015-01-04 08:43:05',
                             '2015-01-04 08:49:05'])

ts = pd.Series(values, index=timestamps)
ts
ts[ts==-1] = np.nan
newFreq=ts.resample('60S').asfreq()

new=pd.concat([ts,newFreq]).sort_index()
new=new.interpolate(method='time')

ts.plot(marker='o')
new.plot(marker='+',markersize=15)

new[newFreq.index].plot(marker='.')

lines, labels = plt.gca().get_legend_handles_labels()
labels = ['original values (nonequispaced)', 'original + interpolated at new frequency (nonequispaced)', 'interpolated values without original values (equispaced!)']
plt.legend(lines, labels, loc='best')
plt.show()

use ordered_merge rather than concat and sort
http://pandas.pydata.org/pandas-docs/stable/merging.html#merging-ordered-data

It would be nice to do it without need of merge altogether since I do not really need the merged time series, I only need the resultant equispaced time series. Is the way I described (enhanced with the ordered_merge) the most efficient way to do such? Maybe using spicy directly would be better then
http://docs.scipy.org/doc/scipy-0.14.0/reference/tutorial/interpolate.html#d-interpolation-interp1d
scipy allows to do it in Matlab style, keep the original timeseries, and pass new index to obtain new timeseries.

this gets you pretty close
In [42]: ts.reindex(ts.resample('60s').asfreq().index, method='nearest', tolerance=pd.Timedelta('60s')).interpolate('time')
Out[42]:
2015-01-04 08:29:00<PHONE_NUMBER>00
2015-01-04 08:30:00<PHONE_NUMBER>00
2015-01-04 08:31:00<PHONE_NUMBER>71
2015-01-04 08:32:00<PHONE_NUMBER>43
2015-01-04 08:33:00<PHONE_NUMBER>14
2015-01-04 08:34:00<PHONE_NUMBER>86
2015-01-04 08:35:00<PHONE_NUMBER>57
2015-01-04 08:36:00<PHONE_NUMBER>29
2015-01-04 08:37:00<PHONE_NUMBER>00
2015-01-04 08:38:00<PHONE_NUMBER>00
2015-01-04 08:39:00<PHONE_NUMBER>00
2015-01-04 08:40:00<PHONE_NUMBER>00
2015-01-04 08:41:00        50.000000
2015-01-04 08:42:00        50.000000
2015-01-04 08:43:00<PHONE_NUMBER>00
2015-01-04 08:44:00<PHONE_NUMBER>00
2015-01-04 08:45:00<PHONE_NUMBER>00
2015-01-04 08:46:00<PHONE_NUMBER>00
2015-01-04 08:47:00<PHONE_NUMBER>00
2015-01-04 08:48:00<PHONE_NUMBER>00
2015-01-04 08:49:00<PHONE_NUMBER>00
Freq: 60S, dtype: float64


Mount as network share, instead of drive letter

"Microsoft Windows provides a different filesystem type for network and fixed drives. It optimises access on the assumption fixed disk drives are fast and reliable, while network drives have relatively high latency and less reliability. Some settings can also be differentiated between the two types, for example that Windows Explorer should just display icons and not create preview thumbnails for image and video files on network drives."

Tried with this:
options.Options = DokanOptions.WriteProtection | DokanOptions.NetworkDrive
But didn't notice a difference in performance. Thumbnails for folders still appear to load.


SDK review meeting scheduler - Update Triage work item

There was not much to do here because of https://github.com/Azure/azure-sdk-tools/issues/6819


Add emoji reactions to messages in develop environment.

Addresses part of issue 14991.
Testing Plan:

Added a unit test to test_bulk_create.py. Made sure 100% of the code I added is covered.

Checked manually emoji reactions are present in develop environment:

start dev environment ./tools/run-dev.py
in a separate terminal, run python manage.py populate_db
go to localhost:9991 in browser and select Aaron user
scroll up in messages until you see the first emoji reactions

GIFs or Screenshots:

@galbwe thanks for working on this!  This is promising; I posted a comment on how we may want to tweak the algorithm.

Still need to add tests.

@galbwe is this ready for a review?  I just noticed you updated this a couple weeks ago, but didn't post a comment, which I think led to nobody looking at this again.

@timabbott Yes this is ready for review. That's my bad for not leaving a comment.

@galbwe thanks for working on this!  I fixed several bugs and cleaned up the code, and pushed the changes back to this PR.  My changes broke your automated tests.  I'm not sure how easy to fix this will be; if it proves exceedingly difficult with the new random.choice() based algorithm, I'm OK with marking this code as # nocoverage; fundamentally, it's tested by populate_db outside the unit tests.
Once this is done, we should do profiling to make sure that we haven't dramatically slowed down manage.py populate_db --num-users=10000 -n 10000.

@timabbot thank you for the review! I will try updating the tests and then work on profiling.

@timabbott here is the profiling data I've collected so far:
master:
Ran populate_db with n=10000 in<PHONE_NUMBER>390137 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>043091 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>8609924 sec.
Average populate_db runtime of 3 runs with n=10000:<PHONE_NUMBER>098073 sec.

feature:
Ran populate_db with n=10000 in<PHONE_NUMBER>279999 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>7464294 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>7264404 sec.
Average populate_db runtime of 3 runs with n=10000:<PHONE_NUMBER>2509564 sec.

That last one had me concerned, so here are some more runs:
Ran populate_db with n=10000 in<PHONE_NUMBER>5823975 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>577362 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>7506714 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>8147583 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>047699 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>049225 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>4265137 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>1223755 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>7409973 sec.
Ran populate_db with n=10000 in<PHONE_NUMBER>711731 sec.
Average populate_db runtime of 10 runs with n=10000:<PHONE_NUMBER>182373 sec.

Maybe Tim's comments are already suggesting what I'm about to suggest, but just to state it in my own words, I would choose this approach.

Generate messages and users first.
_ Get a set of message_ids and user_ids
Do all the reaction stuff after users/messages are generated, instead of during the process
Have two nested loops.
Have users be the outer loop.

Then, basically, for each user, have them randomly upvote a subset of messages, and then have them randomly sprinkle other emojis across various messages.
This makes it impossible to have the duplicate-user problem, so I think a little bit of complexity will just melt away here.

To elaborate on the prior message, if you do every thing in bulk, the code looks something like this:
for user_id in user_ids:
    num_upvote_msg_ids = ...
    num_emoji_ids = ...
    num_emoji_msg_ids = ...

    for msg_id in random.sample(message_ids, num_upvote_msg_ids)
        reactions.append(upvote_helper(user_id, msg_id))

    for emoji_id in random.sample(message_ids, num_emojis):
        for msg_id in random.sample(message_ids, num_upvote_msg_ids):
            reactions.append(reaction_helper(user_id, msg_id, emoji_id)

If the algorithm can be that simple, I'd even argue that automated test might be overkill.

I think Steve's proposed approach would probably be nicer, but the version we have here is simple enough that I think it's reasonable to merge it.  I've tested and it doesn't seem to obviously have a performance regression.

Merged as 9645959ac4dd0a2ddafd1fa10263e74530bf1411, thanks @galbwe!
I'd encourage you to proceed through the other parts of #14991.  I think we should probably not invest further in adding automated tests to the populate_db process; it has such good manual testing coverage that I'm not convinced they are a good use of time.  We should instead focus on manual testing to make sure it's right, and use # nocoverage tags where necessary.

(And if you're interested in trying the refactor Steve describes to simplify this further, be encouraged to!)


Floyd's Cycle Finding Algorithm

Added the solution for finding the cycle or loop in the linked list using floyd's cycle finding algorithm.

Hi @Saikat2407 , please merge this PR.

Hi @Saikat2407 , Please merge this PR.


bump compat

Codecov Report

Merging #31 (e655f1f) into main (1a472b2) will decrease coverage by 1.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
- Coverage   97.87%   96.64%   -1.23%
==========================================
  Files           1        1
  Lines         188      179       -9
==========================================
- Hits          184      173      -11
- Misses          4        6       +2

Impacted Files
Coverage Δ

src/TravelingSalesmanExact.jl
96.64% <0.00%> (-1.23%)
:arrow_down:

Continue to review full report at Codecov.

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


prepare release 2.0.0

Codecov Report

Merging #5572 into 2.0 will decrease coverage by 0.08%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##                2.0    #5572      +/-   ##
============================================
- Coverage     82.79%   82.71%   -0.09%
+ Complexity    11617    11600      -17
============================================
  Files          1382     1382
  Lines         44929    44929
  Branches       5580     5580
============================================
- Hits          37200    37164      -36
- Misses         5138     5163      +25
- Partials       2591     2602      +11

Impacted Files
Coverage Δ
Complexity Δ

core/src/main/java/io/crate/Version.java
71.42% <100%> (-1.59%)
12 <0> (ø)

...arch/indices/recovery/BlobStartPrefixResponse.java
66.66% <0%> (-33.34%)
3% <0%> (-2%)

...in/java/io/crate/lucene/match/CrateRegexQuery.java
43.47% <0%> (-30.44%)
4% <0%> (-4%)

...a/io/crate/exceptions/ContextMissingException.java
81.81% <0%> (-18.19%)
1% <0%> (-1%)

...o/crate/analyze/SafeExpressionToStringVisitor.java
83.33% <0%> (-16.67%)
7% <0%> (-1%)

...transport/executionphases/ExecutionPhasesTask.java
82.56% <0%> (-8.26%)
21% <0%> (-3%)

...peration/collect/BatchIteratorCollectorBridge.java
65.78% <0%> (-7.9%)
2% <0%> (ø)

...main/java/io/crate/blob/v2/BlobIndicesService.java
69.86% <0%> (-5.48%)
21% <0%> (-2%)

...io/crate/protocols/postgres/types/VarCharType.java
91.66% <0%> (-4.17%)
10% <0%> (ø)

...or/transport/distributed/DistributingConsumer.java
79.16% <0%> (-4.17%)
20% <0%> (ø)

... and 24 more

Continue to review full report at Codecov.

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


OLS-702: Copy license file into container

Description
Copy license file into container
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[x] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.45%. Comparing base (ab8cb14) to head (0bf46ec).
Report is 10 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1134   +/-   ##
=======================================
  Coverage   95.45%   95.45%
=======================================
  Files          56       56
  Lines        2374     2374
=======================================
  Hits         2266     2266
  Misses        108      108

/retest

/lgtm

/approve


Platform Selector Parsing for V0 Recipe Files

This PR adds a new class that is capable of parsing selector statements, without evaluating Python statements as code.
For now the purpose of this work is to determine which Platforms (OS + Architecture combinations) apply to a given selector. Future work will use this to determine which recipes are noarch candidates.
In the future, we may also expand on these capabilities to determine which Python versions a recipe may be apply to.
Also introduces a new IsModifiable base class to reduce repeated code in parsers.
Note that not all Platforms/Architectures/Operating Systems recognized by conda are covered at this time.
@markan & @jmlphd for visibility

It looks like I accidentally used some 3.12 features not available in 3.11 which are breaking the tests.
As a side note, I think we're at the point where we can add 3.12 to the test matrix.


.5 pBTC is not distinguishable after sending through the wormhole eth to solana #426 #1086

Leo  I hate to keep opening new issues but I don't seem to be getting any tracktion.  Trying to give all relevent info but having troub;le finding all the info.
https://github.com/solana-labs/oyster/issues/370

Can you please take a look at this issue that you have seen previously and commented that the token picker was the issue.  I have worked at getting this fixed many times by sending it back through v1 but the problem is the pBTC is no longer distinguishable.  The token picker will only choose a token that it has been configured to choose.  This token is no longer recognizable as a one of the tokens configured in the v1 token picker.
You will find info at the links
https://github.com/certusone/wormhole/issues/1086
https://github.com/solana-labs/oyster/issues/543

Leoluc has worked on this issue previously trying to tag him but can't seem to get it right.  As far as sending the pBTC back through v1.  That's not working as there is no way to pick a token that has not been previously configured.  Having said that, I am NOT a devloper.  So what I have said or observed is speculation.  I have spent much time tring to figure out how to resolve the issue but as stated.  NOT a developer, I only play one on TV.  After working on this and trying to figure out how to fix this, that is all I am qulified for.  This is going to take some real developer time and probably coding.  Even if I was able to choose the token, I'm afraid of what to do next.  And even if I did get it to go back through there is no gaurantee that it would come out on the other side as btc.  `

Talk to a Solana Support on the Live support page so that your issue can be looked into.

@apollo711, I was able to recreate your issue and think your pBTC is still recoverable. Take a look at this run-through:
pBTC_recovery.pdf
Let me know if you are interested in instructions on spinning up your own UI and transferring your pBTC from solana back to ethereum.

I have been in contact with Susu from Wormhole discord for some time. I have tried to make it clear many times that the v1 UI will never be able to select the token in it's current state. I will paste in here what my latest response to Susu.
All of this information is also in the github issue log. Probably in two different places as over the period of time I was redirected by Developer leoluk to contact a different github repository. I think this originated in certusone/wormhole repository and Leo advised me to solana-labs/oyster. Anyway there are issues open in both repositories with all info. But you should be able to possibly make some concussions based on the following response to Susu.
Crypto-BANG — 07/05/2022
Bro do you know how many times I have tried to send the token back through. This has been addressed so many times.  I KNOW THIS BECAUSE I SPENT ENDLESS HOURS TRYING TO DO THIS!! Not a one of you guys have even read the issue and the details. the v1 token picker can NOT pick the token because it is no longer reckegnized. The v1 protocol was designed specifically for a set of tokens. The formerly pBTC no longer looks like pBTC, therefore the protocol will never be able to select the token in it's current state. Atleast not without what I would think would be some serious coding. I have made many attempts at trying to make this known. What I do know is that for every wrapped token, there is the original somewhere on a blockchain waiting for the time when the wrapped token will be unwrapped. Is this correct? If it is, like I think it is, why doesn't someone do some coordination, find out where the original is and return it to me! All the info should be in all of the blockchain exploreres that I have previously provided. I have been very patient with trying to get this resolved and all I have gotten is the run around. I want to bring this to someone at Sol or wormhole or Saber or pBTC or all all of the above that can understand what has been going on for coming up on two years. This needs to be brought to someone with authority.  You yourself on a daily basis help things along. If it were not for you and many others these things would never work, 95% of all what is said to be decentralized are so far away from decentralization and most will never be. otherwise the protocols would just simply cease to operate. Please, please bring this to someone with authority who will take a few minutes to review the issue and understand what the problem is. This will not go away, I promise you it will be resolved. These things need to be solved internally. We the community need to self-regulate. If things like this are left to politicians or regulators...we will all be in a world of hurt, going down a path of regulation that we DO NOT want. Not sure why so many do not get this!! Please HELP!!
Crypto-BANG — 07/06/2022
Crypto-BANG — Today at 12:33 AM
Have you heard anything from the dev's. I recieved an email Monday from someone at solana-labs/oyster basically asking me if I am interested in spinning up my own UI and transfering the pBTC from Solana back to ethereum. Sound familair? Yes I would love to transfer the pBTC back to Ethereum. I hate to sound like a broken record but one more time. The pBTC no longer looks like pBTC. So spinning up my own UI, oh and by the way, I'm not a developer so even if I was able to spin up a UI, I'm guessing it will basically be v1 wormhole. As near as I can tell, not being a developer and all, the v1 token picker can NOT pick the token because it is no longer reckegnized. Again assuming the The v1 protocol was designed specifically for a set of tokens, and it was. The formerly pBTC no longer looks like pBTC, therefore the protocol will never be able to select the token in it's current state. I am going to reply to the email with my post that I made to you on 07/05/2022. Also Is this the righrt github solana-labs/oyster ? I never really understood that whole thing with the issue. Please let me know if you have heard anything. The Dev's should be back from there time off? (edited)
July 7, 2022
I look forward to your response that will bring resolution to this very old issue.
CB
Sent with Proton Mail secure email.
------- Original Message -------
On Monday, July 18th, 2022 at 12:52 PM, ckeun @.***> wrote:

@.***(https://github.com/apollo711), I was able to recreate your issue and think your pBTC is still recoverable. Take a look at this run-through:
pBTC_recovery.pdf
Let me know if you are interested in instructions on spinning up your own UI and transferring your pBTC from solana back to ethereum.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Failure to set DefaultConfigurationMode causes performance issues during client construction

Describe the bug
This is a follow up to #1996 and is possibly related to #2000
Following an update to the SDK, the initial construction of the client on a network request increased to more than 30 seconds. I've spent some more time on this issue and my findings are below.
Expected Behavior
Client construction should be under 2 seconds.
Current Behavior
Client construction takes more than 30 seconds as you can see in the call tree:

Reproduction Steps

Create a .NET 6 API with AWSSDK.Extensions.NETCore.Setup + AWSSDK.S3.
Configure an AWS profile and set the configuration in appsettings.json
Ensure no Environment variables or other settings cause DefaultsMode to be set.
Configure DI:

 services.AddDefaultAWSOptions(Configuration.GetAWSOptions());
 services.AddAWSService<IAmazonS3>();

Request IAmazonS3 in a controller.

Possible Solution
Stepping through the problem, the cause is this check:
https://github.com/aws/aws-sdk-net/blob/c957aa1d8d8e1cd52813a9f7f6d3e028b1dd3e80/extensions/src/AWSSDK.Extensions.NETCore.Setup/ClientFactory.cs#L238-L240
When the getter is called on DefaultConfigurationMode, if it hasn't already been set it and is not available locally, it ends up calling this.DefaultConfiguration which then results in the call tree above.
Setting "DefaultsMode": "Standard" in appsettings resolves the problem.
DefaultsMode/DefaultConfigurationMode is not well documented in regards to the .NET SDK and I don't see it in the examples, thus I would consider this unexpected behavior for the majority of consumers.
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.S3 <IP_ADDRESS>
AWSSDK.Extensions.NETCore.Setup 3.7.2
Targeted .NET Platform
.NET 6
Operating System and version
Windows 11

I am seeing a similar issue. For me this manifests itself as a severe delay in startup performance when under load.

New ECS task started in the EC2 cluster
New ECS task passes first health check and is deemed ready
New ECS task is placed into the target group
New ECS task starts receiving traffic from the load balancer
New ECS task does not respond to any traffic due to the lock
New ECS task does not respond to health checks from the load balancer
New ECS task is deemed unhealthy and is removed (this process is then repeated over and over)

+1 cost me 4 hours of debugging

I recommend that it be set to Standard by default without needing to traverse an entire tree for 30 seconds to find the best thing to be.

Sorry for the delay in the response, but do you still see the problem in the latest version of the AWSSDK.Extensions.NETCore.Setup and AWSSDK.S3 packages? I haven't been able to reproduce it locally, but at the same time I couldn't find a specific PR / commit fixing this issue... (so it's likely I'm missing something).

@dscpinheiro I came across a reddit thread of someone running into this issue just last week so it's still an issue in v3. I noticed this codepath got rewritten in v4 so I assume it won't be an issue there.
I can check again but if that getter behaviour hasn't been touched I should be able to reproduce it.

We have made changes in V3 to avoid accidently triggering the DefaultConfigurationMode resolution prematurely. In V4 which is currently in preview we have rewritten this code to get rid of the reflection and have the default config in AWSSDK.Extensions.NETCore.Setup not directly inherit from the ClientConfig in the SDK and instead use a simple type that ensures this regression won't happen again.


[HOTFIX] Fixed S3 metrics issue.

Problem: When data read from s3 it shows the data read as more than the size of carbon data total size.
Reason: It happens because carbondata uses dataInputStream.skip but in s3 interface it cannot handle properly it reads in a loop and reads more data than required.
Solution: Use FSDataInputStream.seek instead of skip to fix this issue.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/637/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/833/

Build Failed  with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8902/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/645/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8908/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/840/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/681/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/875/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/8943/

LGTM


Ignore backup files

Files ending with a tilde suffix are backups.

Thanks! Yes that file shouldn't have been commited.


Ensure caching works properly for repeated calls with the same dir.

preflightCheck tries to cache its results, but it did so in a way that is incorrect. It works fine with a cache miss, but a cache hit results in resetting the cache to undefined.
This is the ultimate cause of https://github.com/eventualbuddha/decaffeinate/issues/106.

nice, thanks – I wonder if this is the cause of #26 as well. Will push out a new release so we can find out

@Rich-Harris looks like it fixed the issue for me both in decaffeinate and esnext. Thanks for the release!


Your browser doesn't support innerText, so it is not supported. Yet.

Firefox is a pretty major browser.  You should probably work on supporting this before posting to HN.

(but other than that, I like the concept and unique design)

Pushed a workaround.. Not super comfortable with it, but it looks like it's
working.
Thanks for opening an issue, Timothy
On Thu, Jul 23, 2015 at 2:56 PM, Timothy Farrell<EMAIL_ADDRESS>wrote:

(but other than that, I like the concept and unique design)
—
Reply to this email directly or view it on GitHub
https://github.com/andreineculau/tastebin/issues/1#issuecomment-124086720
.

--
andreineculau.com http://www.andreineculau.com

You'll probably be more comfortable with this:
http://stackoverflow.com/questions/1359469/innertext-works-in-ie-but-not-in-firefox

I don't know if I'm missing something, but I guess you're talking about the
answer linking to
http://perfectionkills.com/the-poor-misunderstood-innerText/
I read through it before my fix, but couldn't find a solution i.e.
workaround. It basically only reminded me of
http://www.ex-parrot.com/pdw/Mail-RFC822-Address.html :)
Testing my fix briefly, I didn't see any problems, so I can't file a new
issue, or reopen this one.
But for future reference, this is a candidate:
https://github.com/duckinator/innerText-polyfill
On Thu, Jul 23, 2015 at 4:16 PM, Timothy Farrell<EMAIL_ADDRESS>wrote:

You'll probably be more comfortable with this:
http://stackoverflow.com/questions/1359469/innertext-works-in-ie-but-not-in-firefox
—
Reply to this email directly or view it on GitHub
https://github.com/andreineculau/tastebin/issues/1#issuecomment-124120931
.

--
andreineculau.com http://www.andreineculau.com

I was referring to HTMLElement.textContent but it heavily depends on the whitespace differences.  I didn't read into your code so much as to see how you were using it.


Waystones getting mixed up with oneanother or resetting

We have Waystones installed on a server and I have about a half dozen discovered. They are now all mixed up. None of the ones I named take me to the right place, one of them reverted back to its original name, and one of them I can't even get to now.

i have the same issue, mine is on a private server, where i do have access to the files....
my issue is mostly where one waystone location is still there and several of them just send me to a random other discovered waystone

Still happens in the latest version

I don't understand how a bug like this exists...

Just from a brief look at the code, it appears the dat file (waystone database) is set to use the waystone name as it's id for waystones. This doesn't seem like a good idea since the name of the waystone can change. It would be better for the waystone to use the location of the waystone (x,y,z combined by hash?) so that it is unique and doesn't change over the lifetime of the waystone:
                String id;
                if (waystone != null) {
                    id = waystone.name;
                } else {
                    id = Utils.generateWaystoneName("");
                }

Has anyone experienced the problem of mixed up waystones without changing the original name of any of the waystones?

Does anyone have a server or something I can test this on? I've tried multiple times but I haven't been able to recreate the bug.
My discord is DH#9367

Fixed 👍

Fixed 👍


Display box for commenting after all the comments

I believe it's a good idea for people to at least glance at all the comments before replying, but I may be wrong.
Anyway, I managed to find a quick and dirty solution here:
https://github.com/dmerejkowsky/isso/commit/0da5aa225956a611712524866344845327bdd4bc
But I'm wondering if:

there's a better way to do it
it should be configurable
I could achieve the same thing using CSS

Just curious, I'm happy with my hack for now :)

Nearly ten months and no response? ...apart from referencing this issue from my other similar one.

I could achieve the same thing using CSS

Yup, you can set containers as display: flex and re-order them at will.

it should be configurable

Isso is already quite configurable and at some point, all the available options will simply overwhelm even seasoned admins.

This is something that can be set via CSS. I remain convinced introducing yet another config option for this would further complicate Isso and make maintenance harder.


Hotfix/fix php 8.1 warnings

Fix PHP 8.1 warngins as per #104
Description
Fixing PHP 8.1 warnings as peer #104
Closes #104
Checklist:

[ ] I've added tests for my changes or tests are not applicable
[ ] I've changed documentation or changes are not required
[x] I've added my changes to CHANGELOG.md

@Messhias I think something with the branches was messed up…

@Messhias I think something with the branches was messed up…

Yes, a lot conflicts and etc, I'm thinking to merge into main, but it's very specific for PHP 8.1
What do you suggest to proceed with? Solve the conflicts in the current branch or something else?

@Messhias I think something with the branches was messed up…

Yes, a lot conflicts and etc, I'm thinking to merge into main, but it's very specific for PHP 8.1
What do you suggest to proceed with? Solve the conflicts in the current branch or something else?

Seems like you've accidently chose wrong branch as target, I've changed it to master

I suggest a different approach and not merge this immediately:

in the still 1.x code base, add the ReturnTypeWillChange annotations. This makes the code comaptible but gets rid of the PHP Deprecated warnings in PHP 8 and beyond
decide when it's time to fork 2.0 of the main branch and change the return types for real

But IMHO there is more discuss before moving forward; depending on when we think 2.0 can be released, we might consider removing PHP 7.4 and below entirely as its EOL on 2022-11-28 (this year) already …etc
TL;DR: I vote for less obtrusive changes first which can be done to the 1.* release without breaking anything
Edit: a word ;)

Ok, I keep this PR open to the 2.0 branch as a target or it's better to close it and open it again in the future?

@Messhias the type changes need to be postponed until we've a 2.0 branch in place, see the discussion in https://github.com/PHP-Open-Source-Saver/jwt-auth/discussions/76#discussioncomment-2012665
As for #104 , the warnings can be fixed without creating the backward incompatible changes, see my PR #108

@Messhias the type changes need to be postponed until we've a 2.0 branch in place, see the discussion in #76 (reply in thread)
As for #104 , the warnings can be fixed without creating the backward incompatible changes, see my PR #108

Ok, I saw the PR and the discussion, for now, I'll close the PR and in the future, I'll open it again and we can see what path we'll choose.


Bug report: SidebarMobile background get transparent unexpectedly in version 0.28.1

In Admin mobile view ( django-unfold==0.28.1), sidebarMobile overlays the main body with a transparent background, which messes up the views of both two layers.
After noticing this issue, I tried to re-install previous versions, such as 0.26.0、0.27.0、0.28.0， those seem work fine.

https://github.com/unfoldadmin/django-unfold/issues/499


Added FixAltEnter

[X] The mod id matches the harmony id if used by the mod and starts with the same id as your author folder
[X] All used links are valid
[X] Your ResoniteMod.Version must match the version being added in the manifest
[X] Your AssemblyVersion should match the mod version
[X] You have included an accurate sha256 hash for each artifact
[X] Do not remove old mods. Instead, use the deprecated flag
[X] Follow the Resonite Policies and Guidelines and Mod Submission Guidelines

btw repo description hasn't been updated


Only works with bash

This plugin only works with bash, and not other shells (e.g. zsh), because it looks for bash specifically:
https://github.com/zeit/hyperpower/blob/master/index.js#L16
if (/bash: wow: command not found/.test(data)) {

I see there is a relevant PR at #1.

Fixed