Tune workload node

Since we're using hostNetwork by default in the client pod, we need to tune the workload node to establish net.ipv4.ip_local_port_range

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
ingress-performance.sh
PASS
00:04:30

etcd-perf
run_etcd_tests_fromgit.sh
PASS
00:03:04

scale-perf
run_scale_fromgit.sh
PASS
00:01:34

network-perf
smoke_test.sh
PASS
00:10:18

kube-burner
run_clusterdensity_test_fromgit.sh
PASS
00:04:49

kube-burner
run_maxnamespaces_test_fromgit.sh
PASS
00:04:13

kube-burner
run_maxservices_test_fromgit.sh
PASS
00:02:48

kube-burner
run_nodedensity_test_fromgit.sh
PASS
00:04:07

kube-burner
run_nodedensity-heavy_test_fromgit.sh
PASS
00:06:10

storage-perf
run_storage_tests_fromgit.sh
PASS
00:04:34

upgrade-perf
run_upgrade_fromgit.sh
PASS
00:00:21

router-perf
run_router_test.sh
FAIL
00:00:20

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
ingress-performance.sh
PASS
00:04:16

etcd-perf
run_etcd_tests_fromgit.sh
PASS
00:05:34

scale-perf
run_scale_fromgit.sh
PASS
00:03:35

network-perf
smoke_test.sh
PASS
00:09:45

kube-burner
run_clusterdensity_test_fromgit.sh
PASS
00:05:16

kube-burner
run_maxnamespaces_test_fromgit.sh
PASS
00:03:41

kube-burner
run_maxservices_test_fromgit.sh
PASS
00:02:56

kube-burner
run_nodedensity_test_fromgit.sh
PASS
00:09:30

kube-burner
run_nodedensity-heavy_test_fromgit.sh
PASS
00:08:54

storage-perf
run_storage_tests_fromgit.sh
PASS
00:04:34

upgrade-perf
run_upgrade_fromgit.sh
PASS
00:00:21

router-perf
run_router_test.sh
FAIL
00:00:20

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

router-perf-v2
ingress-performance.sh
PASS
00:04:25

etcd-perf
run_etcd_tests_fromgit.sh
PASS
00:03:04

scale-perf
run_scale_fromgit.sh
PASS
00:06:36

network-perf
smoke_test.sh
PASS
00:10:22

kube-burner
run_clusterdensity_test_fromgit.sh
PASS
00:04:08

kube-burner
run_maxnamespaces_test_fromgit.sh
PASS
00:03:42

kube-burner
run_maxservices_test_fromgit.sh
PASS
00:02:46

kube-burner
run_nodedensity_test_fromgit.sh
PASS
00:09:08

kube-burner
run_nodedensity-heavy_test_fromgit.sh
PASS
00:07:25

storage-perf
run_storage_tests_fromgit.sh
PASS
00:04:35

upgrade-perf
run_upgrade_fromgit.sh
PASS
00:00:21

router-perf
run_router_test.sh
FAIL
00:00:20


Add serialization / deserialization to KnowledgeDatabase

My suggestion is to use JSON so humans can also populate the database.
Now that the id is a String we do not should care about updating indexes to keep everything sorted.

Remember to only persist the first level (forget about nested attributes). And all (children) attributes should be persisted as Id only.
Knowledge Base should index all concepts using Id.

Remember to only persist the first level (forget about nested attributes). And all (children) attributes should be persisted as Id only.
Knowledge Base should index all concepts using Id.

Json libraries comparison:
https://github.com/fabienrenaud/java-json-benchmark

Json libraries comparison:
https://github.com/fabienrenaud/java-json-benchmark

Do not forget to add a test to serialize and deserialize the same knowledge base.

Also, add tests to handling databases of words since it will be a common use case.


combine proxy return types

The return types do not need to be one-per-fn, any matching return types can be combined. E.g.
enum ReturnTypes {
    A(AccountId)
    B(AccountId)
}

A and B can be combined into a single enum entry


TAMU CSCE Capstone Pull Request 11/3/2024

Pull Request with current progress on CADVentory as of 11/3/2024.
Features:

Report Generation with customization
Model Previews in Library Window
Storing directory information, tops object, and other information in  SQLite database
some testing

next goals/future improvement:

Finetuning Report Generation Formatting (landscape, text formatting, etc)
Integration Testing
and more

Hi, just tried compiling on Mac and am seeing a variety of coding issues to resolve.  They mostly seem like they're probably minor issues  -- missing headers, incorrect init ordering, unused variables and such -- but need to be reviewed to make sure some other issue isn't masked.
[  6%] Building CXX object CMakeFiles/cadventory.dir/src/CADventory.cpp.o
[  7%] Building CXX object CMakeFiles/cadventory.dir/src/FilesystemIndexer.cpp.o
[  7%] Building CXX object CMakeFiles/cadventory.dir/src/MainWindow.cpp.o
[  8%] Building CXX object CMakeFiles/cadventory.dir/src/SplashDialog.cpp.o
[  8%] Building CXX object CMakeFiles/cadventory.dir/src/Model.cpp.o
[  9%] Building CXX object CMakeFiles/cadventory.dir/src/Library.cpp.o
[  9%] Building CXX object CMakeFiles/cadventory.dir/src/LibraryWindow.cpp.o
/Volumes/X10/cadventory/src/LibraryWindow.cpp:33:5: warning: initializer order does not match the declaration order [-Wreorder-ctor]
    library(nullptr),
    ^~~~~~~~~~~~~~~~
    mainWindow(nullptr)
/Volumes/X10/cadventory/src/LibraryWindow.cpp:33:5: note: field 'library' will be initialized after field 'mainWindow'
    library(nullptr),
    ^~~~~~~~~~~~~~~~
/Volumes/X10/cadventory/src/LibraryWindow.cpp:39:5: note: field 'indexingWorker' will be initialized after field 'modelCardDelegate'
    indexingWorker(nullptr),
    ^~~~~~~~~~~~~~~~~~~~~~~
/Volumes/X10/cadventory/src/LibraryWindow.cpp:256:42: warning: unused parameter 'modelId' [-Wunused-parameter]
void LibraryWindow::onModelProcessed(int modelId) {
                                         ^
2 warnings generated.
[ 10%] Building CXX object CMakeFiles/cadventory.dir/src/ProcessGFiles.cpp.o
[ 10%] Building CXX object CMakeFiles/cadventory.dir/src/IndexingWorker.cpp.o
[ 11%] Building CXX object CMakeFiles/cadventory.dir/src/ModelCardDelegate.cpp.o
/Volumes/X10/cadventory/src/ModelCardDelegate.cpp:78:16: warning: unused variable 'itemPos' [-Wunused-variable]
        QPoint itemPos = pos - itemRect.topLeft();
               ^
1 warning generated.
[ 11%] Building CXX object CMakeFiles/cadventory.dir/src/ModelFilterProxyModel.cpp.o
/Volumes/X10/cadventory/src/ModelFilterProxyModel.cpp:18:14: warning: 'type' is deprecated: Use typeId() or metaType(). [-Wdeprecated-declarations]
    if (data.type() == QVariant::Bool) {
             ^
/opt/homebrew/include/QtCore/qvariant.h:431:5: note: 'type' has been explicitly marked deprecated here
    QT_DEPRECATED_VERSION_X_6_0("Use typeId() or metaType().")
    ^
/opt/homebrew/include/QtCore/qtdeprecationmarkers.h:127:44: note: expanded from macro 'QT_DEPRECATED_VERSION_X_6_0'
# define QT_DEPRECATED_VERSION_X_6_0(text) QT_DEPRECATED_X(text)
                                           ^
/opt/homebrew/include/QtCore/qtdeprecationmarkers.h:27:33: note: expanded from macro 'QT_DEPRECATED_X'
#  define QT_DEPRECATED_X(text) Q_DECL_DEPRECATED_X(text)
                                ^
/opt/homebrew/include/QtCore/qcompilerdetection.h:999:36: note: expanded from macro 'Q_DECL_DEPRECATED_X'
#  define Q_DECL_DEPRECATED_X(x) [[deprecated(x)]]
                                   ^
/Volumes/X10/cadventory/src/ModelFilterProxyModel.cpp:18:34: warning: 'Bool' is deprecated: Use QMetaType::Type instead. [-Wdeprecated-declarations]
    if (data.type() == QVariant::Bool) {
                                 ^
/opt/homebrew/include/QtCore/qvariant.h:142:10: note: 'Type' has been explicitly marked deprecated here
    enum QT_DEPRECATED_VERSION_X_6_0("Use QMetaType::Type instead.") Type
         ^
/opt/homebrew/include/QtCore/qtdeprecationmarkers.h:127:44: note: expanded from macro 'QT_DEPRECATED_VERSION_X_6_0'
# define QT_DEPRECATED_VERSION_X_6_0(text) QT_DEPRECATED_X(text)
                                           ^
/opt/homebrew/include/QtCore/qtdeprecationmarkers.h:27:33: note: expanded from macro 'QT_DEPRECATED_X'
#  define QT_DEPRECATED_X(text) Q_DECL_DEPRECATED_X(text)
                                ^
/opt/homebrew/include/QtCore/qcompilerdetection.h:999:36: note: expanded from macro 'Q_DECL_DEPRECATED_X'
#  define Q_DECL_DEPRECATED_X(x) [[deprecated(x)]]
                                   ^
2 warnings generated.
[ 12%] Building CXX object CMakeFiles/cadventory.dir/src/GeometryBrowserDialog.cpp.o
[ 12%] Building CXX object CMakeFiles/cadventory.dir/src/ReportGenerationWindow.cpp.o
/Volumes/X10/cadventory/src/ReportGenerationWindow.cpp:25:7: warning: initializer order does not match the declaration order [-Wreorder-ctor]
      model(model),
      ^~~~~~~~~~~~
      num_file(0)
/Volumes/X10/cadventory/src/ReportGenerationWindow.cpp:25:7: note: field 'model' will be initialized after field 'library'
      model(model),
      ^~~~~~~~~~~~
/Volumes/X10/cadventory/src/ReportGenerationWindow.cpp:26:7: note: field 'library' will be initialized after field 'num_file'
      library(library),
      ^~~~~~~~~~~~~~~~
/Volumes/X10/cadventory/src/ReportGenerationWindow.cpp:60:22: error: implicit instantiation of undefined template 'std::basic_ostringstream<char>'
  std::ostringstream oss;
                     ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/usr/include/c++/v1/iosfwd:131:32: note: template is declared here
    class _LIBCPP_TEMPLATE_VIS basic_ostringstream;
                               ^
1 warning and 1 error generated.
make[2]: *** [CMakeFiles/cadventory.dir/src/ReportGenerationWindow.cpp.o] Error 1
make[1]: *** [CMakeFiles/cadventory.dir/all] Error 2


requireNativeComponent is not defined

🐛 Bug Report
after I upgrade RN0.55.4 to RN0.59.2, when I run react-native run-android , the issue occurred.

System:
OS: Windows 7
CPU: (4) x64 Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz
Memory: 8.16 GB / 15.88 GB
Binaries:
Node: 8.12.0 - F:\install\nodejs\node.EXE
Yarn: 1.9.4 - C:\Users\xxxx\AppData\Roaming\npm\yarn.CMD
npm: 6.4.1 - F:\install\nodejs\npm.CMD

Hey @Jeijie, if you're still seeing this please complete the full issue template and include a way to reproduce and we'll re-open 👍

This is a really weird bug where the wrong version of react-native/Libraries/Modal/Modal.js is being included.
The version yarn (not sure about npm) is fetching is:
`/**

Copyright (c) Facebook, Inc. and its affiliates.

This source code is licensed under the MIT license found in the
LICENSE file in the root directory of this source tree.

@format
@flow
*/

'use strict';
const AppContainer = require('AppContainer');
const I18nManager = require('I18nManager');
const NativeEventEmitter = require('NativeEventEmitter');
const NativeModules = require('NativeModules');
const Platform = require('Platform');
const React = require('React');
const PropTypes = require('prop-types');
const StyleSheet = require('StyleSheet');
const View = require('View');
const RCTModalHostView = Platform.OS === 'ios' ? requireNativeComponent('RCTModalHostView') : requireNativeComponent('TranslucentModalHostView');
const ModalEventEmitter =
Platform.OS === 'ios' && NativeModules.ModalManager
? new NativeEventEmitter(NativeModules.ModalManager)
: null;
import type EmitterSubscription from 'EmitterSubscription';
import type {ViewProps} from 'ViewPropTypes';
import type {SyntheticEvent} from 'CoreEventTypes';
/**

The Modal component is a simple way to present content above an enclosing view.

See https://facebook.github.io/react-native/docs/modal.html
*/

// In order to route onDismiss callbacks, we need to uniquely identifier each
//  on screen. There can be different ones, either nested or as siblings.
// We cannot pass the onDismiss callback to native as the view will be
// destroyed before the callback is fired.
let uniqueModalIdentifier = 0;
type OrientationChangeEvent = SyntheticEvent<
$ReadOnly<{|
orientation: 'portrait' | 'landscape',
|}>,

;

type Props = $ReadOnly<{|
...ViewProps,
/**

The animationType prop controls how the modal animates.

See https://facebook.github.io/react-native/docs/modal.html#animationtype
*/
animationType?: ?('none' | 'slide' | 'fade'),

/**

The presentationStyle prop controls how the modal appears.

See https://facebook.github.io/react-native/docs/modal.html#presentationstyle
*/
presentationStyle?: ?(
| 'fullScreen'
| 'pageSheet'
| 'formSheet'
| 'overFullScreen'
),

/**

The transparent prop determines whether your modal will fill the
entire view.

See https://facebook.github.io/react-native/docs/modal.html#transparent
*/
transparent?: ?boolean,

/**

The hardwareAccelerated prop controls whether to force hardware
acceleration for the underlying window.

See https://facebook.github.io/react-native/docs/modal.html#hardwareaccelerated
*/
hardwareAccelerated?: ?boolean,

/**

The visible prop determines whether your modal is visible.

See https://facebook.github.io/react-native/docs/modal.html#visible
*/
visible?: ?boolean,

/**

The onRequestClose callback is called when the user taps the hardware
back button on Android or the menu button on Apple TV.

This is required on Apple TV and Android.

See https://facebook.github.io/react-native/docs/modal.html#onrequestclose
*/
onRequestClose?: ?(event?: SyntheticEvent) => mixed,

/**

The onShow prop allows passing a function that will be called once the
modal has been shown.

See https://facebook.github.io/react-native/docs/modal.html#onshow
*/
onShow?: ?(event?: SyntheticEvent) => mixed,

/**

The onDismiss prop allows passing a function that will be called once
the modal has been dismissed.

See https://facebook.github.io/react-native/docs/modal.html#ondismiss
*/
onDismiss?: ?() => mixed,

/**

Deprecated. Use the animationType prop instead.
*/
animated?: ?boolean,

/**

The supportedOrientations prop allows the modal to be rotated to any of the specified orientations.

See https://facebook.github.io/react-native/docs/modal.html#supportedorientations
*/
supportedOrientations?: ?$ReadOnlyArray<
| 'portrait'
| 'portrait-upside-down'
| 'landscape'
| 'landscape-left'
| 'landscape-right',

,

/**

The onOrientationChange callback is called when the orientation changes while the modal is being displayed.

See https://facebook.github.io/react-native/docs/modal.html#onorientationchange
*/
onOrientationChange?: ?(event: OrientationChangeEvent) => mixed,
|}>;

class Modal extends React.Component {
static defaultProps = {
visible: true,
hardwareAccelerated: false,
};
static contextTypes = {
rootTag: PropTypes.number,
};
_identifier: number;
_eventSubscription: ?EmitterSubscription;
constructor(props: Props) {
super(props);
Modal._confirmProps(props);
this._identifier = uniqueModalIdentifier++;
}
static childContextTypes = {
virtualizedList: PropTypes.object,
};
getChildContext() {
// Reset the context so VirtualizedList doesn't get confused by nesting
// in the React tree that doesn't reflect the native component heirarchy.
return {
virtualizedList: null,
};
}
componentDidMount() {
if (ModalEventEmitter) {
this._eventSubscription = ModalEventEmitter.addListener(
'modalDismissed',
event => {
if (event.modalID === this._identifier && this.props.onDismiss) {
this.props.onDismiss();
}
},
);
}
}
componentWillUnmount() {
if (this._eventSubscription) {
this._eventSubscription.remove();
}
}
UNSAFE_componentWillReceiveProps(nextProps: Props) {
Modal._confirmProps(nextProps);
}
static _confirmProps(props: Props) {
if (
props.presentationStyle &&
props.presentationStyle !== 'overFullScreen' &&
props.transparent
) {
console.warn(
Modal with '${           props.presentationStyle         }' presentation style and 'transparent' value is not supported.,
);
}
}
render(): React.Node {
if (this.props.visible !== true) {
return null;
}
const containerStyles = {
  backgroundColor: this.props.transparent ? 'transparent' : 'white',
};

let animationType = this.props.animationType;
if (!animationType) {
  // manually setting default prop here to keep support for the deprecated 'animated' prop
  animationType = 'none';
  if (this.props.animated) {
    animationType = 'slide';
  }
}

let presentationStyle = this.props.presentationStyle;
if (!presentationStyle) {
  presentationStyle = 'fullScreen';
  if (this.props.transparent) {
    presentationStyle = 'overFullScreen';
  }
}

const innerChildren = __DEV__ ? (
  <AppContainer rootTag={this.context.rootTag}>
    {this.props.children}
  </AppContainer>
) : (
  this.props.children
);

return (
  <RCTModalHostView
    animationType={animationType}
    presentationStyle={presentationStyle}
    transparent={this.props.transparent}
    hardwareAccelerated={this.props.hardwareAccelerated}
    onRequestClose={this.props.onRequestClose}
    onShow={this.props.onShow}
    identifier={this._identifier}
    style={styles.modal}
    onStartShouldSetResponder={this._shouldSetResponder}
    supportedOrientations={this.props.supportedOrientations}
    onOrientationChange={this.props.onOrientationChange}>
    <View style={[styles.container, containerStyles]}>{innerChildren}</View>
  </RCTModalHostView>
);

}
// We don't want any responder events bubbling out of the modal.
_shouldSetResponder(): boolean {
return true;
}
}
const side = I18nManager.isRTL ? 'right' : 'left';
const styles = StyleSheet.create({
modal: {
position: 'absolute',
},
container: {
position: 'absolute',
[side]: 0,
top: 0,
},
});
module.exports = Modal;
`
If I go to: https://github.com/facebook/react-native/tree/0.59-stable/Libraries/Modal
and copy/paste the below code into react-native/Libraries/Modal/Modal.js the crash stops happening.
`/**

Copyright (c) Facebook, Inc. and its affiliates.

This source code is licensed under the MIT license found in the
LICENSE file in the root directory of this source tree.

@format
@flow
*/

'use strict';
const AppContainer = require('AppContainer');
const I18nManager = require('I18nManager');
const NativeEventEmitter = require('NativeEventEmitter');
const NativeModules = require('NativeModules');
const Platform = require('Platform');
const React = require('React');
const PropTypes = require('prop-types');
const StyleSheet = require('StyleSheet');
const View = require('View');
const RCTModalHostView = require('RCTModalHostViewNativeComponent');
const ModalEventEmitter =
Platform.OS === 'ios' && NativeModules.ModalManager
? new NativeEventEmitter(NativeModules.ModalManager)
: null;
import type EmitterSubscription from 'EmitterSubscription';
import type {ViewProps} from 'ViewPropTypes';
import type {SyntheticEvent} from 'CoreEventTypes';
/**

The Modal component is a simple way to present content above an enclosing view.

See https://facebook.github.io/react-native/docs/modal.html
*/

// In order to route onDismiss callbacks, we need to uniquely identifier each
//  on screen. There can be different ones, either nested or as siblings.
// We cannot pass the onDismiss callback to native as the view will be
// destroyed before the callback is fired.
let uniqueModalIdentifier = 0;
type OrientationChangeEvent = SyntheticEvent<
$ReadOnly<{|
orientation: 'portrait' | 'landscape',
|}>,

;

type Props = $ReadOnly<{|
...ViewProps,
/**

The animationType prop controls how the modal animates.

See https://facebook.github.io/react-native/docs/modal.html#animationtype
*/
animationType?: ?('none' | 'slide' | 'fade'),

/**

The presentationStyle prop controls how the modal appears.

See https://facebook.github.io/react-native/docs/modal.html#presentationstyle
*/
presentationStyle?: ?(
| 'fullScreen'
| 'pageSheet'
| 'formSheet'
| 'overFullScreen'
),

/**

The transparent prop determines whether your modal will fill the
entire view.

See https://facebook.github.io/react-native/docs/modal.html#transparent
*/
transparent?: ?boolean,

/**

The hardwareAccelerated prop controls whether to force hardware
acceleration for the underlying window.

See https://facebook.github.io/react-native/docs/modal.html#hardwareaccelerated
*/
hardwareAccelerated?: ?boolean,

/**

The visible prop determines whether your modal is visible.

See https://facebook.github.io/react-native/docs/modal.html#visible
*/
visible?: ?boolean,

/**

The onRequestClose callback is called when the user taps the hardware
back button on Android or the menu button on Apple TV.

This is required on Apple TV and Android.

See https://facebook.github.io/react-native/docs/modal.html#onrequestclose
*/
onRequestClose?: ?(event?: SyntheticEvent) => mixed,

/**

The onShow prop allows passing a function that will be called once the
modal has been shown.

See https://facebook.github.io/react-native/docs/modal.html#onshow
*/
onShow?: ?(event?: SyntheticEvent) => mixed,

/**

The onDismiss prop allows passing a function that will be called once
the modal has been dismissed.

See https://facebook.github.io/react-native/docs/modal.html#ondismiss
*/
onDismiss?: ?() => mixed,

/**

Deprecated. Use the animationType prop instead.
*/
animated?: ?boolean,

/**

The supportedOrientations prop allows the modal to be rotated to any of the specified orientations.

See https://facebook.github.io/react-native/docs/modal.html#supportedorientations
*/
supportedOrientations?: ?$ReadOnlyArray<
| 'portrait'
| 'portrait-upside-down'
| 'landscape'
| 'landscape-left'
| 'landscape-right',

,

/**

The onOrientationChange callback is called when the orientation changes while the modal is being displayed.

See https://facebook.github.io/react-native/docs/modal.html#onorientationchange
*/
onOrientationChange?: ?(event: OrientationChangeEvent) => mixed,
|}>;

class Modal extends React.Component {
static defaultProps = {
visible: true,
hardwareAccelerated: false,
};
static contextTypes = {
rootTag: PropTypes.number,
};
_identifier: number;
_eventSubscription: ?EmitterSubscription;
constructor(props: Props) {
super(props);
Modal._confirmProps(props);
this._identifier = uniqueModalIdentifier++;
}
static childContextTypes = {
virtualizedList: PropTypes.object,
};
getChildContext() {
// Reset the context so VirtualizedList doesn't get confused by nesting
// in the React tree that doesn't reflect the native component heirarchy.
return {
virtualizedList: null,
};
}
componentDidMount() {
if (ModalEventEmitter) {
this._eventSubscription = ModalEventEmitter.addListener(
'modalDismissed',
event => {
if (event.modalID === this._identifier && this.props.onDismiss) {
this.props.onDismiss();
}
},
);
}
}
componentWillUnmount() {
if (this._eventSubscription) {
this._eventSubscription.remove();
}
}
UNSAFE_componentWillReceiveProps(nextProps: Props) {
Modal._confirmProps(nextProps);
}
static _confirmProps(props: Props) {
if (
props.presentationStyle &&
props.presentationStyle !== 'overFullScreen' &&
props.transparent
) {
console.warn(
Modal with '${           props.presentationStyle         }' presentation style and 'transparent' value is not supported.,
);
}
}
render(): React.Node {
if (this.props.visible !== true) {
return null;
}
const containerStyles = {
  backgroundColor: this.props.transparent ? 'transparent' : 'white',
};

let animationType = this.props.animationType;
if (!animationType) {
  // manually setting default prop here to keep support for the deprecated 'animated' prop
  animationType = 'none';
  if (this.props.animated) {
    animationType = 'slide';
  }
}

let presentationStyle = this.props.presentationStyle;
if (!presentationStyle) {
  presentationStyle = 'fullScreen';
  if (this.props.transparent) {
    presentationStyle = 'overFullScreen';
  }
}

const innerChildren = __DEV__ ? (
  <AppContainer rootTag={this.context.rootTag}>
    {this.props.children}
  </AppContainer>
) : (
  this.props.children
);

return (
  <RCTModalHostView
    animationType={animationType}
    presentationStyle={presentationStyle}
    transparent={this.props.transparent}
    hardwareAccelerated={this.props.hardwareAccelerated}
    onRequestClose={this.props.onRequestClose}
    onShow={this.props.onShow}
    identifier={this._identifier}
    style={styles.modal}
    onStartShouldSetResponder={this._shouldSetResponder}
    supportedOrientations={this.props.supportedOrientations}
    onOrientationChange={this.props.onOrientationChange}>
    <View style={[styles.container, containerStyles]}>{innerChildren}</View>
  </RCTModalHostView>
);

}
// We don't want any responder events bubbling out of the modal.
_shouldSetResponder(): boolean {
return true;
}
}
const side = I18nManager.isRTL ? 'right' : 'left';
const styles = StyleSheet.create({
modal: {
position: 'absolute',
},
container: {
position: 'absolute',
[side]: 0,
top: 0,
},
});
module.exports = Modal;
`
In the first version of the code, the method being called requireNativeComponent is not being required before it's used unlike the following version of the code where it is being required on line 23:
https://github.com/facebook/react-native/blob/0.58-stable/Libraries/Modal/Modal.js
Maybe this is a build system bug which is publishing the wrong version?

@rickhanlonii I'm pretty sure this is the same bug: https://github.com/react-native-community/react-native-modal/issues/276


jwt authentication

Do you want to request a feature or report a bug?
Feature
What did you expect to see?

Based on jwt permission authentication, when can I support it?

Hey @LincolnBruce, thanks for your interest in the project.
We're dealing with this issue in https://github.com/containous/traefik/issues/3311.

good job


Fix - update of m_isValid variable added in JointTrackingTask

Could you please add also the check in the test?

@GiulioRomualdi done. I added it to all the tests, both in IK and TSID.

Thank you @isorrentino. Let's wait for the CI


OpenSource: 3.8 Process to submit a patch to linux kernel

Description 📜
OpenSource: 6.4 Process to submit a patch to linux kernel #2271

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Open #Source

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@ashish-patwal @Aryamanz29 @adityabisoi

Please enclose code/console/commands between console  tags and remove the italics tag added before the code

done

Please enclose code/console/commands between console  tags and remove the italics tag added before the code

done

Check merge

@amitrakshar01

Update your fork repo
Put your doc inside 3.Share_Things_With_Community directory
Rename your doc 3.8_Submit_Patch_To_Linux_kernel.md

Done check

@amitrakshar01 can you please enable editing file permissions for the pr .

@amitrakshar01 can you please enable editing file permissions for the pr .

It's already allowed editing

No i can't see the option to edit file . Just for reference have you ticked the 'allow edits by maintainers' option .

No i can't see the option to edit file . Just for reference have you ticked the 'allow edits by maintainers' option .

I have

@Aryamanz29 i need to do some edits to the file . Is there any way that's possible since i am not a maintainer?

@Aryamanz29 i need to do some edits to the file . Is there any way that's possible since i am not a maintainer?

@ashish-patwal  Just clone @amitrakshar01 forked repo into your local machine, Do changes, commit and push his Opensource branch then it will reflect in this PR :)

can anyone tell me when it will be merged?

@amitrakshar01 i have made a PR to your fork of Gwoc correcting some changes . Please merge that fork . Then commit those changes to the PR you made for submitting linux kernel patch doc . We will then merge your PR .

@amitrakshar01 i have made a PR to your fork of Gwoc correcting some changes . Please merge that fork . Then commit those changes to the PR you made for submitting linux kernel patch doc . We will then merge your PR .

done plz check

LGTM @Aryamanz29 .

@Aryamanz29


Perform heuristic analysis from existing metrics

Delay Rationale: Someone from NASA Metrics deleted the original report

Performed some initial analysis and metrics for top 50 pages and how people use the pds.nasa.gov website. Getting some interesting quantitative information thus far.

No progress since last stand up

Delay rationale: Delayed due to abundance of user interviews. Progress being made on future work in parallel

July schedule status: Delayed due to increase in number of user interviews. No impact on future tasks as this can be completed in parallel with others on schedule.

Edward does not have time to work on that now.

@edwardbarraza made a good presentation to the team. The work will be presented next week.


add Model helper class

I had the need to compare model attributes within collections, so have added a helper class so you can do the following:
assert [Foo(key='value', other_key='other_value')] == List.containing(Model(key='value'))

I pushed the 0.3.0 release to PyPI last night: https://pypi.org/project/pytest-assert-utils/0.3.0/


Error: Type 'MouseCursor' not found.   final MouseCursor mouseCursor;

After upgrading to 3.13.1 im getting
/dev/mobile/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-3.13.1/lib/src/fields/form_builder_checkbox.dart:28:9: Error: Type 'MouseCursor' not found.
  final MouseCursor mouseCursor;

Flutter v1.17.5.

Kindly refer to #399.


[release-1.6] add support for selecting pods from service entries

This is an automated cherry-pick of #23216

@googlebot I consent.

@howardjohn @costinm are still discussing this on #23216. Lets hold off on merging until they are ready.

@brian-avery I have created https://github.com/istio/istio/pull/23352 to address the issues as well as fix more bugs I found. :). That PR wont merge unless this one goes in first.

@googlebot I consent

lgtm, fixes in master are merged and will be cherrypicked


Changing Background Color to Blue

Hi there, I am not going to merge this as I am not maintaining this repository anymore or using it for my demos -- If you would like to change things, you are free to clone it an add those changes to your own copy


NDLAr track unit vectors are flipped

The NDLAr enddir entries are always negative in the z direction, which seems like a bug that could just be fixed by a -1* operation. But this should be understood, assigning Jeremy in the meantime.
The direction default also appears to be zero, which feels like a very dangerous default value (seeing that it's a completely valid direction for a unit vector to have).
Whilst I'm on it, the NDLAr dir is not filled.

Attaching comparison of z unit vector for NDLAr and TMS to better illustrate the issue

I did some digging, and it looks like I already fixed this issue, but it didn't make it into the version of the ND-LAr-reco driver used for the workshop CAFs.
If there are any respins pending, we should certainly update.  Otherwise we'll pick it up the next time...

The direction default also appears to be zero, which feels like a very dangerous default value (seeing that it's a completely valid direction for a unit vector to have).

We could certainly change it to be (NaN, NaN, NaN), which I'm sure @cmmarshall  will love 😄

Whilst I'm on it, the NDLAr dir is not filled.

Yeah, that's right.  I think we added dir for you to use, actually, not because I was trying to write it out 😄   If we think it's useful to have that as well I could put it on my list to store it, but it requires adding some stuff.

I also found that many tracks that clearly have a start and end point in the NDLAr don't have the enddir field filled either; is that connected to this? See attached screenshot, where I to TTree:Scan showing the saved unit vector of the direction vector (enddir) and the start and end point of the track.

I think there's a chance this is self-resolving with my updated suite of commits, but it'll take testing to prove that.  Maybe @andrewmogan and I can make an updated file or two and see

Ok.  Andrew and I have rerun the reco on one of the files from the LBL workshop, and I verified that the negative enddir entries are resolved with the update dune-nd-lar-reco.  The missing enddir rows also do not appear to happen.  So I consider those resolved.
I have also opened #15, which will fill SRTrack::dir.  This won't do anything useful until we rerun the ND-LAr reco summary files for input, but it's now there, so once that's merged, I think we can close this issue.

I think this is now obsolete now that we're using the full ML-reco stack instead of the temporary bits I hacked together.


AWS logs are not created under IIS

Setting options.loggingOptions.logLevel = Aws::Utils::Logging::LogLevel::Trace;
Works fine in test environments. No logs created when running under IIS
What platform/OS are you using?
Windows
What compiler are you using? what version?
What's your CMake arguments?
Can you provide a TRACE level log? (sanitize any sensitive information)
No

Setting options.loggingOptions.logLevel = Aws::Utils::Logging::LogLevel::Trace;
Works fine in test environments. No logs created when running under IIS

The log exists in cwd of the program. If your program is started by other module, you should check other module's cwd. Anyway, you can set the log's location by setting log prefix to the wanted directory path.

can you send me an example for this please?
On Wed, Mar 27, 2019 at 1:57 PM Andrew Tang<EMAIL_ADDRESS>wrote:

The log exists in cwd of the program. If your program is started by other
module, you should check other module's cwd. Anyway, you can set the
log's location by setting log prefix to the wanted directory path.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi--a4qDPyZoxtu17KlzooguFt6ss3ks5va7DpgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-8qv70q4T-iOUi_k8OhVQ4lB4CYDks5va7DpgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: The log exists in cwd of the program. If your program is
started by other module, you should check other module's cwd. Anyway, you
can set the log's location by setting log prefix to the wanted directory
path."}],"action":{"name":"View Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

The problem is the dll is running from the iis folder
(C:\inetpub\wwwroot...). So I was thinking maybe this folder just does not
give permissions to any application to create new files for security
reasons. Is there any way to redirect the logging into a completely
different folder, other than cwd? If not, this feature will be very handy
in the future )
On Wed, Mar 27, 2019 at 1:57 PM Andrew Tang<EMAIL_ADDRESS>wrote:

The log exists in cwd of the program. If your program is started by other
module, you should check other module's cwd. Anyway, you can set the
log's location by setting log prefix to the wanted directory path.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi--a4qDPyZoxtu17KlzooguFt6ss3ks5va7DpgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-8qv70q4T-iOUi_k8OhVQ4lB4CYDks5va7DpgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: The log exists in cwd of the program. If your program is
started by other module, you should check other module's cwd. Anyway, you
can set the log's location by setting log prefix to the wanted directory
path."}],"action":{"name":"View Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477280664",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

SDKOptions options;
options.LoggingOption.logLevel = Aws::Utils::Logging::LogLevel::Trace;
options.LoggingOption.defaultLogPrefix = "path\\to\\your\\directory\\aws_log_";
AWS::InitAPI(options);
{
   //your logic;
}
AWS::ShutdownAPI(options);

The problem is my directory is still under C:\inetpub\wwwroot...
No logs are being created there. Have you ever done any testing for this type of architecture?

We have tested it. Show me the code.

Aws::SDKOptions options;
options.loggingOptions.logLevel = Aws::Utils::Logging::LogLevel::Trace;
Aws::InitAPI(options);
On Thu, Mar 28, 2019 at 12:33 PM Andrew Tang<EMAIL_ADDRESS>wrote:

We have tested it. Show me the code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477673020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi-z0ZeRDgpEcGIE1VMgZjLGK9Kbwzks5vbO7LgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-zQLbk6WPoDfY9P97Uk4D5O844YGks5vbO7LgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: We have tested it. Show me the code. "}],"action":{"name":"View
Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477673020"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477673020",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477673020",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

Did you see my last response with logprefix?

Yes. I have not tried that yet. Should the subfolder already be there or
will your logging function create it if necessary?
On Thu, Mar 28, 2019 at 12:44 PM Andrew Tang<EMAIL_ADDRESS>wrote:

Did you see my last response with logprefix?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477677512,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi-2_N-AXKTzqvPD4EJtBoT4rQlJHCks5vbPFsgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-7TFIp7riz-lLpG2qoesBFGix60Iks5vbPFsgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: Did you see my last response with
logprefix?"}],"action":{"name":"View Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477677512"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477677512",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477677512",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

You might have misunderstood my point. The path you specify is where you want the log to be generated, instead of your program's cwd

oh
let me try that
thx
On Thu, Mar 28, 2019 at 12:47 PM Andrew Tang<EMAIL_ADDRESS>wrote:

You might have misunderstood my point. The path you specify is where you
want the log to be generated, instead of your program's cwd
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477678591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi-6PKgPXq2EFm-Dh5N1qy0kwZSFC7ks5vbPIFgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-7EpiD5zFQbpmF2ldXvkIiCC9GmVks5vbPIFgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: You might have misunderstood my point. The path you specify is
where you want the log to be generated, instead of your program's
cwd"}],"action":{"name":"View Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477678591"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477678591",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477678591",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

The folder should be there. And make sure your service have the permission to write.

Yes, this worked. Thank you!
On Wed, Mar 27, 2019 at 2:54 PM Andrew Tang<EMAIL_ADDRESS>wrote:

SDKOptions options;
options.LoggingOption.logLevel = Aws::Utils::Logging::LogLevel::Trace;
options.LoggingOption.defaultLogPrefix = "path\to\your\directory\aws_log_";
AWS::InitAPI(options);
{
//your logic;
}
AWS::ShutdownAPI(options);
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477302678,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi--rO0vqPdeCkw1nTv1t0MsFvxcJVks5va75RgaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-xm967pF0LbW2t1ZiYXkHB8sIChzks5va75RgaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: ```\r\nSDKOptions options;\r\noptions.LoggingOption.logLevel =
Aws::Utils::Logging::LogLevel::Trace;\r\noptions.LoggingOption.defaultLogPrefix
"path\\to\\your\\directory\\aws_log_";\r\nAWS::InitAPI(options);\r\n{\r\n
//your
logic;\r\n}\r\nAWS::ShutdownAPI(options);\r\n\r\n```"}],"action":{"name":"View
Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477302678"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477302678",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477302678",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

Does this path parameter support WString?
On Thu, Mar 28, 2019 at 12:49 PM Andrew Tang<EMAIL_ADDRESS>wrote:

The folder should be there. And make sure your service have the permission
to write.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477679409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AnQi-9-WOGKb0QLmeUL_f0N2cXgkZ4uXks5vbPJ3gaJpZM4cOPw3
.[image: Web Bug from
https://github.com/notifications/beacon/AnQi-7q9qAOm5hOQRlYS22zvSGcqr_c2ks5vbPJ3gaJpZM4cOPw3.gif]
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/aws/aws-sdk-cpp","title":"aws/aws-sdk-cpp","subtitle":"GitHub
repository","main_image_url":"
https://github.githubassets.com/images/email/message_cards/header.png
","avatar_image_url":"
https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in GitHub","url":"https://github.com/aws/aws-sdk-cpp"}},"updates":{"snippets":[{"icon":"PERSON","message":"@singku
in #1101: The folder should be there. And make sure your service have the
permission to write."}],"action":{"name":"View Issue","url":"
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477679409"}}} [
{ "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477679409",
"url": "
https://github.com/aws/aws-sdk-cpp/issues/1101#issuecomment-477679409",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url": "
https://github.com" } } ]

--
Anna Siniavina
Working Papers Developer
T: 416·867·9504 x1210 | F: 416·867·1906
<EMAIL_ADDRESS>https://www.caseware.com/
https://linkedin.com/company/caseware-international-inc
https://facebook.com/CaseWare-International-Inc-54418196590/
https://twitter.com/caseware
https://youtube.com/channel/UCRlosKtcCJVii9rsOvIB5gg

Use Aws::StringUtils::FromWString to do the conversion.


ios拓展本地组件问题

,ios端拓展组件,因为weex是以库的方式集成的,拓展的组件继承不了weex的组件父类,也取不到weex的协议之类的,请问这种情况要怎么处理呢?问题太小白,麻烦大家了

没怎么看明白。
协议只是约定了一组接口而已（面向接口编程），本身并没有做任何事情。具体的实现方法，都在相应的组件里实现。

This PR/issue doesn't receive response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Implement adding elements and testing membership

Faithfully mirroring Python's set API, the methods are:

BloomFilter.add() - Add an element to the Bloom filter
BloomFilter.update() - Update the Bloom filter with the union of
itself and others
BloomFilter.__contains__() - Test whether an element has been added
to the Bloom filter
BloomFilter.clear() - Remove all elements from the Bloom filter

🐟


Copy embetterments

Preview (found under "show all checks") https://deploy-preview-31--anna-eevert-love.netlify.com/


Header: Size S

Hello @mcilurzo, is there a Figma link for this story?

Hello @mcilurzo, is there a Figma link for this story?

Hi @DavideMininni-Fincons It's on the normal Figma of lyne components, but not yet tagged. Scroll to the right side, and there the lower part is size s.
https://www.figma.com/design/9r6xSfNmEfCFxl1yFYedrj/Lyne-Components?m=auto&node-id=1220-686725


"jf config show" should also show the used config file

Is your feature request related to a problem? Please describe.
After using jfrog-cli for some years now and updating it from time to time to new versions, I have noticed the growing number of config files in ~/.jfrog/ next to the original jfrog-cli.conf: jfrog-cli.conf.v4, jfrog-cli.conf.v5, jfrog-cli.conf.v6
When analyzing user issues, it is often hard to determine the one config file, which really is taking effect now - especially, if users edited some file directly instead of using "jf c". Furthermore, we have implemented tools, which are also using jfrog-cli.conf - there it also became guess work, which of the config files is "in charge".
Describe the solution you'd like to see
"jf config show" should addtionally print a line like e.g.:
Config path:                    C:\Users<accountName>.jfrog\jfrog-cli.conf.v6
Describe alternatives you've considered
Until now, I have tried to guess and find out by deleting/renaming/trying, which config file actually takes effect.

@Rob3rtS,
The jfrog-cli.conf file is internal to the JFrog CLI, and it's preferable not to manually read or modify it without using JFrog CLI commands.
That being said, could you provide more details about your use case? What's prompting you to access its path?

My use case is: installing Debian packages from (private) Debian repositories hosted on Artifactory via apt using a script.
The script is extracting the access token from jfrog-cli.conf and creating the necessary sources.list files. Actually, I have other scripts as well, which are using the token for REST API calls, but that seems a bit outdated in the meanwhile, because there is jf rt curl (although calling a subprocess from python is not as elegant as directly issuing http requests within the script itself).

Thanks for sharing this use case, @Rob3rtS.
The challenge with relying on the jfrog-cli.conf is that it might become incompatible with future versions. Simply providing the path may not be effective if the structure changes.
My recommendation is to generate a short-lived token using the jf atc command:
# Generate an access token for 10 minutes
jf atc --expiry 600

This command generates the following JSON that you can safely parse:
{
  "scope": "applied-permissions/user",
  "access_token": "<the-new-token>",
  "expires_in": 600,
  "token_type": "Bearer",
  "token_id": "2e035eb6-3379-45c7-b8e5-32859e55cd38"
}

Another option is to store the original access token as a secret on the CI server and only expose it as an environment variable when necessary.
Please let me know if that helped.

Thank you @yahavi - I guess, I will go for the approach using jf rt atc...

@Rob3rtS
Quick note: jf rt atc relies on an outdated API. Consider using jf atc instead, if possible.


Product Addition - 'Finish' button overlays with 'Add basic details' button

What

When I am adding a new product, there seems to be overlaid on the last part of the buttons
It's inhibiting my ability to edit the basic product details when I scanned a new product
Problem arises when I add more additional photos

Expected behavior
The finish button should be at the bottom irrespective of the no of additional photos added
Why

It's annoying to come back to just edit one field

Part of

#1379

Screenshot/Mockup/Before-After

Smartphone model

Device: iPhone XR
OS: iOS 16 (beta)
App Version:  3.13.1 (Test Flight)

Additional context

cf. #2944: we would be better off with a FloatingActionButton.

Dublicate #2944

I don't think so that it's duplicate, #2944 is about the snack bar blocking the view, but this issues was more of a layout overlay problem not of snack bar

@AshAman999 You may be right but my FloatingActionButton solution would solve both.
Feel free to reopen if needed.


Curl feature

After reading https://en.wikipedia.org/wiki/CURL
I think gocurl should add new feature as curl command line tool has a lot of them
Anyone agree?
cc @vickydasta @widnyana

@christoga did you mean you want to port curl source code to golang?

No, I mean gocurl should be a tool to use curl in golang

here you go then https://github.com/andelf/go-curl


Nothing returned

Steps:

I've set up node and billing all correctly.
Using VSC, create a folder "test", ran "npm init" created a package.json, after installing "vision" lib this the package.json

{
  "name": "test",
  "version": "1.0.0",
  "description": "test",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "index.js"
  },
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@google-cloud/vision": "^0.22.1"
  }
}

According to Google's quickstart, create index.js as

// Imports the Google Cloud client library
const vision = require('@google-cloud/vision');

// Creates a client
const client = new vision.ImageAnnotatorClient();

// Performs label detection on the image file
client
  .labelDetection('label.jpg')   // .jpg file has a word art.
  .then(results => {
    const labels = results[0].labelAnnotations;

    console.log('Labels:');
    labels.forEach(label => console.log(label.description));
  })
  .catch(err => {
    console.error('ERROR:', err);
  });

set a breakpoint inside index.js run "npm start", it's not hit and DEBUG CONSOLE doesn't show any label text.

node index.js  does hit breakpoint, but after .labelDetection('./label.JPG') it goes to end of the file.

resolved, thank you.


Rename StorageClass.Provisioner.LOCAL_BLOCK

Short description:
Rename StorageClass.Provisioner.LOCAL_BLOCK to NO_PROVISIONER
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified

/approve


feat(mixin/step outputs): place each mixin/step output into its own file

place each mixin output into its own file (this enables multiline outputs)

I have a general question about how far we wanted to go with this. I was expecting a larger change, where the mixins themselves would write multiple files, instead of continuing to write key/value pairs.
It may make things easier/more natural for porter because we will be treating outputs the same throughout. But it may also make it easier for the mixins as well. Now that we allow very large complex outputs (like entire json documents and kubeconfig files, etc), writing each one to its own file, seems like it should be less confusing to look at for everyone involved when debugging.
Since this would be a big change to how mixins work, perhaps we should merge this first, then do a sweep on mixins to get them writing to separate files, then remove the logic to open the files (parsing for KEY=VALUE)? What do you think?

@carolynvs Good point.  I'd say we just go all the way (mixins place each output into sep file, as you've mentioned).  I'll refactor this changeset and work on the necessary PRs for the various mixins...

Sounds great, thanks! 💯

Oh, looks like something is wrong with the CLI tests but it wasn't immediately obvious what. Maybe something about printing the values of the outputs in the table?

Oh, looks like something is wrong with the CLI tests but it wasn't immediately obvious what. Maybe something about printing the values of the outputs in the table?

Alas, the cli test is failing on the terraform test bundle as the PR to update the porter-terraform mixin is still outstanding (https://github.com/deislabs/porter-terraform/pull/17).  I've tested locally (and will re-confirm after the latest updates).  I think we may have to merge without the cli tests passing in CI...

Gotcha, thanks how quickly I had forgotten. 😝


Update and refactoring

Hey,
thanks for this well structured and neat image 💖 . I did some updates and refactorings. If you like it give me some feedback.

I did everything as requested. Feel free to review again. :)

I upgraded so it works again with latest docker-compose.

Also applied your README suggestions.


New Component: Google Map Place Autocomplete (Geocomplete)

Add google place autocomplete component.
https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete
Since we already have Geocoding and Rev. Geocoding from Google, we should also have other google maps features like Place autocomplete etc.

This plugin https://ubilabs.github.io/geocomplete/ is now archived and no longer maintained so no point in creating a component for it.  I feel like in the world of GeoComplete not much is truly free etc so not sure its worth creating a component for....

Going to reopen this as I need this for a customer. I am going to create a Google Places based input called InputPlace


Fix GH issue #5404 (DEV)

Fixes #5404

@Ein-Tim , @MikeMcC399  Please let me know if the proposed change is OK from community point of view ?


New: Resize window on new media

What does this implement/fix? Explain your changes
Automatically resize media window on new media to media resolution
Does this close any currently open issues?
Closes #339
TODO

[x] Only resize in window mode
[x] Introduce new user option for auto-resizing
[ ] Check for problems with high DPI screens
[ ] Introduce maximum image/video resolution presets in settings. Relates to: https://github.com/AntonyCorbett/OnlyM/blob/b6fbb60073189d968c1ac8d565307a23067efc3b/OnlyM/Services/ImagesCache/ImageCache.cs#L15-L16

this pull request does not close #339. it is a totally different way of displaying media compared to the suggestion made in #339 and could coexist as another option beside it.


Expose "Last error" to other systems

mail_admin
Opbeat
Sentry

https://github.com/arteria/django-background-tasks/blob/master/background_task/tasks.py#L190
This could be done easily using Django's logging framework. See #16 as well.

@philippeowagner Until now, a task error was logged as a warning. In addition to the changes made in #16, I have raised the log level from WARNING to ERROR.

Using the logging mechanism properly this issue is no longer applicable.


summary on endpoint

hi, can you add summary on endpoint, i need it for my project.
big thanks.

Hi @riezkyfirdauz! Thanks for your suggestion. I will upload it soon in the next version. Any other suggestions, send us, please.

Hi @riezkyfirdauz! Thanks for your suggestion. I will upload it soon in the next version. Any other suggestions, send us, please.

The version 2.5.0 implemented this feature.

The version 2.5.0 implemented this feature.


Runtime States

Runtimes can be in three different states:

running
paused
stopped (or remove the runtime)

Modules can change a runtime's state.

We could add a restart method() (depends on how we implement stop() and start())


test: add node v8 and v10 to test matrix

Consistent with hexo package.

Coverage remained the same at 100.0% when pulling 8eac54198be39e97e0281165257ebfb6628ff5e6 on weyusi:node-version into 084138e8536bd0a5a2b54ebc99bb27a3c067ce3c on hexojs:master.

In another PR, it might also be nice to add appveyor ci


Visual Studio UI Updates

Just wanted to highlight that "Add Web Reference" is no longer an option in Visual Studio. Instead, I had success replicating this workflow using the Visual Studio documentation, and using the "Add Service Reference" option as described here: https://msdn.microsoft.com/en-us/library/bb628649.aspx.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f0b45f40-bb24-04a7-54b9-114d3abd083d
Version Independent ID: e888ca81-faa7-6da9-f043-6f14c7872b07
Content: Step 2 Adding a Web Reference
Content Source: docs/general-development/step-2-adding-a-web-reference.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Good catch... adding to doc update backlog.


Add UniverseSetting to Select on Calendar

Many universes don't need to updated daily, and selection could be done once per month. Minimum time in universe is a different concept ( selection is till done daily and assets are just not removed ).
Expected Behavior
Help speed up selection rather than "Universe.Unchanged" - don't perform or load the selection data. Skip until a later date.
A similar behavior could be achieved by a scheduled event flipping a UniverseUnchanged variable to null once a month.
Actual Behavior
Difficult to reduce churn frequency of universe selection. E.g. A monthly cycle of universe members all on 1st of the month. More difficult inside framework algorithms where they're returning a Universe and the filtering isn't looking for UnChanged.
Potential Solution
.# Default Calendar Daily
.UniverseSetting.RebalancePeriod = Calendar.Monthly;
Maybe https://github.com/QuantConnect/Lean/issues/3890
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Duplicate of https://github.com/QuantConnect/Lean/issues/3890


Add option for Notice's stacking-direction

The Notices in jBox can be stacked, but only in the direction down/downwards.
The added option stackDirection allows to reverse the stacking-direction to 'up'.
This allows stacking for Notices that are not placed at the 'top', but at the 'bottom'.
The default value for stackDirection is 'down' which behaves the same as before stackDirection was added.
Example usage:
new jBox('Notice', {
  content: 'some notice text...',
  stack: true,
  stackDirection: 'up',
  position: {
    y: 'bottom'
  }
});

This is nice!

Closing old pull requests as new version 0.4.0 will come out soon
Added this to my TODO list


Ambient test suite slow to cleanup

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
The ambient test suite seems to take a long time to cleanup, potentially impacting following test suites run in the post submit jobs
samples failure: https://prow.istio.io/view/gs/istio-prow/logs/integ-k8s-124_istio_postsubmit/1735702436804300800
ztunnel in particular takes a while to delete
Version
master branch

Additional Information
No response

locally the current cleanup suggests ambient suite take a few seconds to cleanup:
2023-12-15T17:24:23.659156Z	info	tf	=== BEGIN: Cleanup Istio [Suite=ambient] ===
2023-12-15T17:24:23.659221Z	info	tf	clean up cluster cluster-0
2023-12-15T17:24:25.715452Z	info	tf	=== SUCCEEDED: Cleanup Istio in 2.056273673s [Suite=ambient] ===

The next suite goes to run and is hitting a failure at install time:
2023-12-15T17:00:36.034342Z	info	tf	=== BEGIN: Test: 'helm[TestDefaultInstall]' ===
2023-12-15T17:00:36.047636Z	info	tf	Applying helm command: helm install istio-base /home/prow/go/src/istio.io/istio/manifests/charts/base --namespace istio-system -f /logs/artifacts/helm-12f0379c909740fbb3de402263/TestDefaultInstall/_test_context/helm-install-test3077193058/values.yaml --kubeconfig /home/.kube/config --timeout 2m0s
2023-12-15T17:00:37.573922Z	info	tf	(FAILED) Executing helm: helm install istio-base /home/prow/go/src/istio.io/istio/manifests/charts/base --namespace istio-system -f /logs/artifacts/helm-12f0379c909740fbb3de402263/TestDefaultInstall/_test_context/helm-install-test3077193058/values.yaml --kubeconfig /home/.kube/config --timeout 2m0s   (err: exit status 1): Error: INSTALLATION FAILED: create: failed to create: secrets "sh.helm.release.v1.istio-base.v1" is forbidden: unable to create new content in namespace istio-system because it is being terminated

    util.go:89: failed to install istio base chart: exit status 1: Error: INSTALLATION FAILED: create: failed to create: secrets "sh.helm.release.v1.istio-base.v1" is forbidden: unable to create new content in namespace istio-system because it is being terminated

When I reproduce this locally, I see that ztunnels are still around after the cleanup message is displayed as completed in the test framework logs - but ztunnels are still around, and are still Terminating when the next istiod install runs:
$ kubectl get po -n istio-system
NAME            READY   STATUS        RESTARTS   AGE
ztunnel-gmhjm   1/1     Terminating   0          9m57s
$ kubectl get po -n istio-system
NAME                     READY   STATUS              RESTARTS   AGE
istiod-5bb86cfcb-5pscv   0/1     ContainerCreating   0          0s
ztunnel-gmhjm            1/1     Terminating         0          9m59s

I added a loop here that checked and waited until the pods in the istio-system namespace were gone before completing the cleanup.
Cleanup times jump from a few seconds to almost 30 seconds for the ambient suite:
2023-12-19T01:02:00.862282Z	info	tf	waiting on pods to terminate
2023-12-19T01:02:00.865721Z	info	tf	waiting on pods to terminate
2023-12-19T01:02:00.870179Z	info	tf	waiting on pods to terminate
2023-12-19T01:02:00.913719Z	info	tf	=== SUCCEEDED: Cleanup Istio in 31.58705377s [Suite=ambient] ===

Other suites don't see nearly as big of a jump in time-to-complete.

I don't see similar wait times just running an istioctl uninstall... command on my ambient enabled istio installs so it's specific just to the test framework?

Also, only the K8S 124 post submit tests are impacted, the K8S 123 tests are not seeing the same failures

So the ztunnel Terminating time is linked to terminationGracePeriodSeconds.  Default value is 30 seconds.  Setting it to 10 maps makes the cleanup time decrease equal value:
2023-12-19T17:33:09.627333Z	info	tf	waiting on pods to terminate
2023-12-19T17:33:09.637126Z	info	tf	waiting on pods to terminate
2023-12-19T17:33:09.731296Z	info	tf	=== SUCCEEDED: Cleanup Istio in 11.887712058s [Suite=ambient] ===
ok  	istio.io/istio/tests/integration/ambient	648.231s

I'm closing because #48393 explicitly mentions that it resolves this one.


Point of View Shifting

Hi,
From the readme docs it seems clear that verb substitution with presented view is preserved. Is it possible to take an input text, and alter point of view? E.G. Book chapter is presented in 3rd person PoV -> replaCy -> book chapter rendered in 1st person PoV. If this is achievable with the present work, please give me a general list of instructions to accomplish if possible.

This may be possible, depending on scope. Do you have a few example sentences?

Hi, something like this:
3p"He walked into the room" > 1p "I walked into the room"
3p"The man walked into the room" > 1p "I walked into the room"

this is doable, but to get long-range dependencies right is not easy. What I mean is the following is easy:
The man runs to the store -> I run to the store
but with an arbitrary number of tokens in between becomes hard:
The man, who is thinking about all the work he has to do, runs to the store -> I, who am thinking about all the work I have to do, run to the store
Also, what about cases like
The man, who was thinking about his wife and her love of life and beautiful face, was content.
Does that become: I, who was thinking about my wife and my love of life and beautiful face, was content.?
It not, how is this process supposed to distinguish between 3rd persons to becomes 1st and 3rd persons that are to remain unchanged?


Update core-committers.md

@gsagula
@ethervoid
Not urgent, feel free to update your dev areas

Some of these may also need to be added to https://developers.mattermost.com/internal/rd-teams/

Sorry, I was travelling. +1 on @jwilander suggested changes, otherwise it LTGM.

@grundleborg I'll go ahead and merge as Camille is looking to submit another PR for new hires tomorrow. You can review / suggest updates if any post-merge.
Thanks @comharris for the PR!


feature-diff-editor

More needs done here but I'm finding a lot of warnings throughout the Solution. I'm going to complete this PR and revisit it later, in the meantime clean some warnings up.


[CLI] Use a higher compression ratio (slower) zstd setting by default

related: https://github.com/foxglove/mcap/issues/646

@jhurliman Is it possible to detect compression settings from an existing compressed blob?

I took a look at this. The go zstd encoder library we use is not able to achieve the compression ratios that the reference implementation can, even in the mode that compresses best. Our only option to achieve that result is to switch to the reference implementation by using https://github.com/DataDog/zstd . There are a few tradeoffs associated with this:

klauspost/compress is designed to encode and decode with zero allocations, and includes the ability to retain allocated memory between compression sessions (with the Reset(io.Writer) API). DataDog/zstd does not do this, nor is minimal allocation behavior one of its stated goals.
DataDog/zstd uses CGO, with associated compilation speed penalties and portability issues.

Because of this i'm wary of just switching implementations without fairly extensive benchmarking. The option I'd rather pursue is to add a pluggable compression API to the go MCAP API, similar to the TypeScript implementation. This allows users to choose the encoder/decoder implementation that works best for them.
I'm removing the bug label from this issue - bug is a subjective term, but my rationale is tthat at this point the paths forward look much more like new features rather than fixes.


license-documentation.rst

License documentation for Mantl. Replaces #884

not sure if i can ask but still wondering - do we really need 38 commits into 2 files?
can't we commit everything in one PR?
looks like all that will be continuously testing during 38*2hrs=76hrs
http://sethrobertson.github.io/GitBestPractices/#sausage

@ohal
If @stevendborrelli  approve, I'll squash all of them in single commit.

@avnik it will be perfect
@stevendborrelli what do you think?

I'm good with it.

Squashed everything into 2 commits, also fix mor typos.
@TanyaCouture If you need more work on this branch -- git fetch and `git reset --hard origin/feature/license-documentation  (ask me, if you have some changes which are not here or other issues, I am updated this branch with rebase and edited history, so plain  pull woudn't work)

Also I rebased this branch on top of current master

That should've squashed it into two commits (squashed commits and merge commit) and rebased onto current master.

On Mon, Jan 25, 2016 at 11:10:13AM -0800, Langston Barrett wrote:

That should've squashed it into two commits (squashed commits and merge commit) and rebased onto current master.

It what I done


chore(*) prepare vagrant for 1.0.0

Summary
Prepares kong-vagrant for Kong 1.0.0 release.

Updates from Ubuntu precise to bionic
Enables port forwarding 9000:9000 for Kong stream module
Adds KONG_STREAM_LISTEN environment variable
Adds transparent flags to KONG_PROXY_LISTEN
Ensures kong and kong_tests databases have right permissions for kong role on Postgres
Ensures that kong role can login to Postgres
Updates documentation
Installs some extra Unix tools

Here, do not merge this yet.

@bungle I approved the PR, please check my commit before merging


initial state && removal form

Title

Changes 👷♀

- item 1
How to test 🧪

- step 1 ...

Closing old PR (cleaning up PR tab).


[popconfirm] Complete Arabic Translation

Please make sure these boxes are checked before submitting your PR, thank you!

[ X ] Make sure you follow Element's contributing guide.
[ X ] Make sure you are merging your commits to dev branch.
[ X ] Add some descriptions and refer relative issues for you PR.

Popconfim text buttons wasn't translated with a comment "to be translated", i find that the proposed translation suitable as my native language is Arabic.

语句

语句


Allow to provide metric namespace

Hi,
Looking at the documentation and Application Insights dashboard, it seems metrics could be grouped by namespace.
Except if I missed something, this SDK doesn't allow to provide a namespace, and all metrics ends up in the azure.applicationinsights namespace.

Related to this. I have multiple node apps that all report to the same application insights instance in Azure. I'm using the cloud role to distinguish the apps and this works fine to separate the metrics for differents apps.
I'm also using the applicationinsights-native-metrics npm package to get native metrics, but these all end up in the same azure.applicationinsights namespace. I didn't find a way to filter them based on the cloud role in Azure, rendering them basically useless, as the metrics from separate apps are merged together. So it would be nice if one could provide a namespace to separate these native metrics into separate namespaces, or if the cloud role was somehow applied to these metrics as well.

Agree, this would be awesome.
R.E. Splitting by Cloud Role, @tomi does the option not show up using the Add Filter / Apply Splitting options? (P.S. haven't used applicationinsights-native-metrics so maybe that plugin isn't apply the context tags to it's metrics if not!).
R.E. Namespacing, looks like the .NET SDK handled this a couple of years ago (REF: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/759). This resulted in an update to the official bond schema for the Azure Monitor to add a ns namespace field which can be used by consuming SDKs.
Hence a PR into this codebase adding the same field to the bond schema, generate a new DataPoint.ts class, update data point creation (REF: https://github.com/microsoft/ApplicationInsights-node.js/blob/develop/Library/EnvelopeFactory.ts#L208) to add ns, e.g.
    private static createMetricData(telemetry: Contracts.MetricTelemetry): Contracts.Data<Contracts.MetricData> {
        var metrics = new Contracts.MetricData(); // todo: enable client-batching of these
        metrics.metrics = [];

        var metric = new Contracts.DataPoint();
        metric.count = !isNaN(telemetry.count) ? telemetry.count : 1;
        metric.kind = Contracts.DataPointType.Aggregation;
        metric.max = !isNaN(telemetry.max) ? telemetry.max : telemetry.value;
        metric.min = !isNaN(telemetry.min) ? telemetry.min : telemetry.value;
        metric.name = telemetry.name;
        metric.ns = telemetry.namespace; // Something like this here
        metric.stdDev = !isNaN(telemetry.stdDev) ? telemetry.stdDev : 0;
        metric.value = telemetry.value;

        ...

And then consumers can call track*() methods with a customnamespace/ns/metricNamespace (name TBD) property if desired? Decisions r.e. whether there is a "default" namespace / how a consumer can set a global namespace would be need to be decided - think autocollection when have multiple Telemetry Clients.
References:

Endpoint protocol: https://github.com/microsoft/ApplicationInsights-Home/blob/master/EndpointSpecs/ENDPOINT-PROTOCOL.md
Endpoint Schemas: https://github.com/microsoft/ApplicationInsights-Home/tree/master/EndpointSpecs/Schemas/Bond
DataPoint Schema: https://github.com/microsoft/ApplicationInsights-Home/blob/master/EndpointSpecs/Schemas/Bond/DataPoint.bond#L10
Azure Monitor Track Endpoint: https://docs.microsoft.com/en-us/azure/azure-monitor/faq#can-i-send-telemetry-to-the-application-insights-portal
DotNet issue: https://github.com/Microsoft/ApplicationInsights-dotnet/issues/759
DotNet PR to add namespace: https://github.com/microsoft/ApplicationInsights-dotnet/commit/f7536327fb67de7652d7c4025cd318b9c8ae7016

@asos-craigmorten yes, that seems to work! It seems I need to select Log-based metrics as the Metric namespace and then I can filter and split the data. If I choose the custom azure.applicationinsights namespace filtering and splitting is not available. So thank you, that solves my issue!

@asos-craigmorten Would you submit a PR for your namespace extension feature?
@tomi I think the root cause for the missing splitting feature with native metrics could be this one:

All metrics that you send using trackMetric or GetMetric and TrackValue API calls are automatically stored in both logs and metrics stores. However, while the log-based version of your custom metric always retains all dimensions, the pre-aggregated version of the metric is stored by default with no dimensions. You can turn on collection of dimensions of custom metrics on the usage and estimated cost tab by checking "Enable alerting on custom metric dimensions":

@markwolff are there any plans from Microsoft to implement the namespace support?

Is there a limitation in the ingestion endpoint that is preventing this feature or some other consideration that is preventing this from being implemented? It looks to me that it's just another field in the bond files and types that needs to get mapped? Are there other important things to take into consideration when you use namespaces?


If the default selected launch config is a compound, a different config is run when you click start

Open the vscode repo
Set the "Gulp Build" launch config to be hidden by adding

"presentation": {
	"hidden": true
}

Open code-insiders with a fresh user-data-dir
Open the debug viewlet, see that "Debug VS Code Main, Renderer, and EH" is selected by default in the launch config picker ✔
Click the green triangle to start debugging
The "Gulp Build" config is actually started 🐛

Great catch and great steps. Thanks a lot for filling good issues.


Serializing nullable fields takes up more bytes

The size of a class, after serialization, is larger when it contains nullable fields compared to a class with non-nullable fields.
[MemoryPackable]
[GenerateTypeScript]
public partial class MemoryPackableTestClassA
{
    public int Field1 { get; set; }

    public long Field2 { get; set; }
}

[MemoryPackable]
[GenerateTypeScript]
public partial class MemoryPackableTestClassB
{
    public int Field1 { get; set; }

    public long? Field2 { get; set; }
}

var ca = new MemoryPackableTestClassA() { Field1 =<PHONE_NUMBER>, Field2 = 22222222 };
var caLen = MemoryPackSerializer.Serialize(typeof(MemoryPackableTestClassA), ca).Length;

var cb = new MemoryPackableTestClassB() { Field1 =<PHONE_NUMBER>};
var cbLen = MemoryPackSerializer.Serialize(typeof(MemoryPackableTestClassB), cb).Length;

Log.Debug($"ca len={caLen}");   //ca len=13
Log.Debug($"cb len={cbLen}");  //cb len=21

Is this a bug?

Although it seems at first glance that making something nullable would only increase its size by 1 byte, there's a possibility for a significant increase due to padding.
In the worst-case scenario with a long, making it nullable adds 1 byte and 7 bytes of padding.

Can it be optimized? In the case of frequent transmission, there will be a lot of overhead.

Thanks, this helps me a lot!

According to your solution, i wrap the type with a new class and rewrite the operator. This works well.
[MemoryPackable]
[GenerateTypeScript]
public partial class WrapLong
{
	public long Value;

	public static implicit operator WrapLong(long value)
	{
		return new WrapLong { Value = value };
	}

	public static implicit operator long(WrapLong data)
	{
		return data.Value;
	}
}

[MemoryPackable]
[GenerateTypeScript]
public partial class MemoryPackableTestClassB
{
	public int Field1 { get; set; }

	public WrapLong Field2 { get; set; }
}


Get player click event

Hi, how can i get player who clicked on something in a book?

You can create a command when the player clicks it, then you listen for that command

Great idea, thanks.


Much lint, so wow

pip install lintrunner lintrunner-adapters
lintrunner init
lintrunner --configs .lintrunner.toml -a

is this in sync with fbcode lint? I'm trying to fix a bunch of lint while importing https://www.internalfb.com/diff/D55251989


Webpack 5

Hi,
Is there any plan to upgrade the plugin to support webpack5 ?

I've got a PR for upgrading to webpack 5 here: https://github.com/kotarella1110/cordova-plugin-webpack/pull/538 @stempora Can you see if it works for you? (Works for me currently with on device and with local browser dev-server modes)


Security Considerations

This is a placeholder issue for collecting security related topics that should be considered. The following come to my mind:

A signed Verifiable Presentation can't be modified without the verifier noticing. However, it could be swapped out for another VP that has been previously signed by the holder.

~The expiration date of a VP could be helpful to limit its use~
A storage medium like IPFS or a Blockchain with built-in guarantees solves the issue
Hashlinks that guarantee the integrity but it puts an additional burden on the client that's used by the verifier to unpack and verify the data against the has
did:webs' integrity information in the storage path would work for HTTP servers while putting an additional burden on the client that's used by the verifier

Update: an expiration date can't be used on a VP. The widely supported fields are listed here an expiration date is not part of it: https://w3c.github.io/vc-data-model/#presentations-0

RE: hashlinks

VCWG is debating a property relatedResources which is the approach we should take

We shouldn't require IPFS or blockchain but leave that available as a possible approach. If web URLs are used we should recommend the related resources thing I mention above

For relatedResources to work for this spec, my understanding is that we'd need to add a similar mechanism to the DID document service entry. Let's talk about it in the upcoming meeting a create another issue for it.


API Extractor workflow
Executed as part of the package build script, API Extractor does the following:

generate index.d.ts bundle, e.g. packages/lib-core/dist/index.d.ts
generate Markdown API report, e.g. packages/lib-core/dist/api/lib-core.api.md
generate JSON API doc model, e.g. packages/lib-core/dist/api/lib-core.api.json

Note :memo: rollup-plugin-dts is dropped in favor of the d.ts bundling feature of API Extractor. This means that Rollup is only used for generating the index.js bundle.
API reports overview

API reports are meant to improve the visibility of public APIs exposed by the given package and track public API changes through code review process. These reports are aimed at plugin SDK maintainers to better understand the impact of changes on public APIs.

API Extractor compares the currently generated API report file with one currently committed at reports directory.
If the files don't match, API Extractor fails the build and instructs the developer to copy the currently generated file to reports directory. This way, changes in API reports become part of the code review.
Note :memo: tsdoc-metadata.json is not generated since we don't need it, see here and here for details.
API docs overview

API docs are meant to document public APIs of the given package (various objects, functions, React components, etc.) from plugin SDK consumer perspective. In other words, these docs are aimed at developers of dynamic plugins as well as developers of host applications that support such plugins.

This PR adds generate-api-docs.sh script that copies all the currently generated API doc model files to docs/generated directory and then invokes API Documenter to generate Markdown API docs at docs/generated/api.
Note :memo: docs/generated directory is git-ignored which means that the docs/generated/api content isn't currently tracked in the git repo.
As a follow-up, we should create a new monorepo package with all developer oriented docs (API docs, READMEs etc.) collected and processed into static web pages ready for deployment on services like Surge.sh.
Changes due to API Extractor package analysis

internal methods in PluginLoader and PluginStore are marked as private

this causes such methods to be excluded from the generated index.d.ts bundle
as for private method testability, I generally agree with points described here - code should be tested in a way similar to how the client would use it, which is through the public interface

new API exports (lots of them) to ensure zero ae-forgotten-export warnings
added @packageDocumentation to index files of all lib packages
fixed malformed or malformatted TSDoc comments

Other changes and improvements

new runtime ESLint rule lib-restricted-external-imports which enforces imported external modules to be declared in dependencies or peerDependencies within the closest parent package.json

this effectively ensures that Rollup generated index.js bundle doesn't include any external module code

import/no-extraneous-dependencies replaced by lib-restricted-external-imports
removed replaceCode custom Rollup plugin for Lodash-specific code manipulation

not needed since lib-restricted-external-imports guards the import vs. manifest dependency consistency

downlevel-dts dropped for now since we don't need it (yet)

can be re-added once we need TypeScript 3.x compatible typings for our lib packages

dist/build-meta.json renamed to dist/build-metadata.json

@vojtechszocs I actually ran into some issues testing this in hac-core as https://github.com/openshift/hac-core/pull/108/f has not been merged yet 🤦
I'll update that PR tomorrow if you're willing to review it.

Latest commit looks good to me and tested in hac-core with hac-dev:

/lgtm


Updated man and .ini file regarding address:port parameters.

As discussed in #1610, updated the man to clarify that the address property is no longer supported and warn users that interfaces MUST be UP for xrdp to correctly start.

Thanks again - just one comment above.
When we've merged this I'll create a feature request to support IP_FREEBIND where possible, and then I think we can close #1610. Does that cover things from your perspective?

I think so. Thanks to you as well.

It turned xrdp no longer refers address in xrdp.ini since d6229df5a16a38a90593a8aa6269a8339494cce7.

Thanks for your contribution @robertoetcheverryr !


docker Singularity "proxy" to invoke singularity containers on non-Linux systems via docker

Since singularity is Linux specific, its images aren't usable on OSX/Windows.  But I wonder if there could be a docker image/container (which we could carry here as well)  with the sole purpose of "proxying" invocation to singularity inside?  Then the https://github.com/ReproNim/containers/blob/master/scripts/singularity_cmd could even do needed proxying.

on a quick try -- 2.6.1 singularity cannot work in docker
root@3dd4a262774a:/tmp# ./ReproNim-reproin-master-latest.simg
Singularity: action-suid (U=0,P=4648)> Could not virtualize file system namespace: Operation not permitted

ERROR  : Could not virtualize file system namespace: Operation not permitted
Singularity: action-suid (U=0,P=4648)> Retval = 255

ABORT  : Retval = 255
root@3dd4a262774a:/tmp# apt-cache policy singularity-container
singularity-container:
  Installed: 2.6.1-2~nd90+1
  Candidate: 2.6.1-2~nd90+1
  Version table:
 *** 2.6.1-2~nd90+1 500
        500 http://neuro.debian.net/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

but apparently it is just a matter of --privileged docker execution!  and then it works.  So we can/should workout such an adapter and just document that it requires --privileged docker execution.  Aspects to keep in mind
TODOs:

[ ] Dockerfile to produce such proxy-to-singularity docker image/container
[ ] scripts/singularity_cmd_via_docker helper

[ ] need for bind mounting paths into the docker container first to then be bind mounted into singularity... Since our helper has control over them (-W "$tmpdir" -H "$updir/binds/HOME" -B $PWD --pwd "$PWD") and we do not care to expose "outside" paths, as long as there is no more binds sneaked in into the call -- we should be all set to just bind mount $PWD, $updir/binds/HOME, and $tmpdir
[ ] (possibly?) need for mapping user ID into some internal to docker environment... may be even chmoding outputs upon completion?  I had little to no experience with that yet, besides eventually chmodding those owned by root files ;)  One approach could be to have a dedicated user within the "docker proxy" image, and bind current user to it?

related

convert singularity images to docker containers: https://github.com/vsoch/singularity2docker

singularity provides docker image with singularity  singularityware/singularity:3.1

Here is a singularity Docker image provided by Singularityware and shared on Docker Hub:
singularityware/singularity:3.1


OoT: Skip/Shorten some Boss Death Cutscenes

These are the remaining boss cutscenes that need to be skipped/Shortened in OoT:

[x] Twinrova Arguing
[x] Ganondorf death cutscene and the brief intro scene to the Ganon fight that follows after (when Link and Zelda are talking a bit, OOTR skips right to when you have control of Link after the pan over the wreckage of the Castle)
[x] Phantom Ganondorf death cutscene

Done


Need layout id feature like XML for testing app using Appium [FR]:

Is there an existing issue for this?

[X] I have searched the existing issues

Is this a feature request for one of the samples?

[X] Yes, this is a specific request related to this samples repo.

Sample app
Other (bug not related to sample app)
Describe the problem
I need to implement UI testing using Appium, Currently, I am using Xpath but XPath changes with I make any changes to the UI tree. Previously when we had an XML-based layout Id with did not have any issues adding and removing the layout from the App.
Describe the solution
Need a similar layout id feature that can be integrated into appium
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello Jolanda,
I hope this email finds you well. I wanted to follow up on the feature
request I raised on GitHub regarding the layout ID feature in Compose.
After further research, I have discovered that this feature already exists
within Compose, and I apologize for any confusion my previous request may
have caused.
I understand that many companies, including my own, have struggled with
writing test cases due to not being aware of the capability to add resource
IDs like XML within Compose. With this in mind, I would like to propose
adding these IDs to the project in order to make it easier for developers
to write test cases and improve the overall user experience.
To give you a better idea of what I'm proposing, I've included a link to an
example of XML Resource Ids in Compose:
https://gist.github.com/wajahat-iqbal/2165942e9fe0f0c0122bfba38bef7408.
Please have a look at it, it may give you more insights.
Thank you for your time and consideration. I look forward to hearing your
thoughts on this proposal.
Best regards,
Wajahat Iqbal

Hello!
We do document this behavior in our testing guide, see https://developer.android.com/jetpack/compose/testing#uiautomator-interop
Did you find this information? And if not - where did you look when you were searching for this information? We might be able to improve the documentation based on your input!

I did multiple experiments that I found on google and in the documentation that were not working for me.
While exploring UI in Appium Inspector. I saw the content-description for the Image composable appearing in Appium Inspector. I followed the same practice to implement testTagsAsResourceId.
Even doing this does not run a test you need to use "android:id" as prefix with tags

Thank you for your answer! I believe this kind of documentation should live in the Appium docs instead of the Android docs. Maybe you can raise an issue on the Appium Github repository?
As for Compose documentation, we describe how to utilize the test tags to convey information to automatic test tools such as UIAutomator, which is all I think we should do.


Update timeout for .github/workflows/_envtest_tests.yaml

This is an automated pull request to update default timeouts for all jobs in .github/workflows/_envtest_tests.yaml that do not currently contain a default timeout property.
Please review these changes closely to ensure that all jobs have sufficient time to run. If a job needs more time, please add a timeout property to that job to override the organization default.
Additionally, please be attentive to unintended changes to the workflow YAML file, as the parser is not perfect.
Lastly, note that it is up to the reviewer to merge this pull request and delete the PR branch once they are satisfied with the changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing in favour of already merged #5733


Auto-Reload after changes in code are not reflected or automaticaly updated.

Changes to React project code are not automaticaly updated when changes to the code are made.
Expected behaviour:
ReactUI should automatically update when dev-server detects changes
Current behavior:
Nothing happens
Possible workaround
After each change, you can use the Restart function in ReactUIDocument to update it manually, or you can restart game.
Other considerations

Maybe it would be useful to add Key-Bind that would work during play mode to reload the UI eg: Ctrl+Shift+R
UI Toolbar button or in Scene view a button to do that.
Both would reduce the amounts of click and a hassle to find proper ReactUI Component in the hierarchy

ReactUnity already supports HMR. It was not working because of a bug that was introduced in 0.14.3 with a change in location. Reverted now. Fixed in 0.14.5.
Other solutions you proposed may be added in the future with a comprehensive dev tools implementation.


Update to RAPIDS 24.10

Description

Closes https://github.com/nv-morpheus/MRC/issues/478
Requires https://github.com/nv-morpheus/utilities/pull/75
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

/merge


Random crashes on 1.18.1

I keep experiencing random crashes when JEA in installed
1.18.1
Forge 39.0.8
JEA 3.1.0
crash-2021-12-24_12.49.22-client.txt

Please try without OptiFine.

Crash report without optifine installed
crash-2021-12-24_15.33.59-client.txt

I am also having the same issue.

Is this a JEA problem or an Alex's Mobs problem? https://github.com/Alex-the-666/AlexsMobs/issues/832

I think this is actually an Alex's Mobs problem. Not a JEA problem.

Yes, problem was fixed in Alex's Mobs and JEA is working now


README badges linking to /Webtrends/ instead of /oracle/

The PR #108 rolled back the URL of the badges in the README.
https://github.com/oracle/wookiee/pull/108#issuecomment-349111223

Thanks for the heads up! Fixed: https://github.com/oracle/wookiee/pull/111


Feature/genai poc

What?

Create VPC in data-science account
Create ECS cluster together with a service for b2chat
Create ACM certificate
Create ALB
Create route53 record in public hosted zone

Why?

https://github.com/binbashar/le-tf-infra-aws/issues/611

References

Link to any supporting github issues or helpful documentation to add some context (e.g. stackoverflow).
Use closes #123, if this PR closes a GitHub issue #123

@martingaleano Tincho let's please use binbash.co instead of binbash.com.ar domain. Thanks!

Thanks @exequielrafaela . I've just moved the domain to binbash.co


Increase number of unicorn workers for Static

Trello

Response to outcome of load test in which frontend had some difficulty talking to static, resulting in 500s

Co-authored-by: Jonathan Kerr<EMAIL_ADDRESS>

We'll test this in a load test before merging. https://trello.com/c/kxP64gJo/700-redo-the-load-test-to-see-what-impact-weve-had-with-our-changes