[issue] Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.

[Sat Jun 05 2021 14:37:43.521]  BUNDLE  ./index.tsx

[Sat Jun 05 2021 14:37:46.691]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseACL.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.693]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.694]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/arrayContainsObject.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.695]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/decode.js -> ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/decode.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.697]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/encode.js -> ../../node_modules/parse/lib/react-native/ParseACL.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.697]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/encode.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.698]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/encode.js -> ../../node_modules/parse/lib/react-native/ParseOp.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.699]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/encode.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.701]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.703]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.704]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseOp.js -> ../../node_modules/parse/lib/react-native/unique.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.708]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.709]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseQuery.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.715]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseQuery.js -> ../../node_modules/parse/lib/react-native/OfflineQuery.js -> ../../node_modules/parse/lib/react-native/equals.js -> ../../node_modules/parse/lib/react-native/ParseACL.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.718]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseQuery.js -> ../../node_modules/parse/lib/react-native/OfflineQuery.js -> ../../node_modules/parse/lib/react-native/equals.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.720]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/decode.js -> ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/canBeSerialized.js -> ../../node_modules/parse/lib/react-native/ParseRelation.js -> ../../node_modules/parse/lib/react-native/ParseQuery.js -> ../../node_modules/parse/lib/react-native/OfflineQuery.js -> ../../node_modules/parse/lib/react-native/decode.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.721]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/decode.js -> ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/decode.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.722]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/EventuallyQueue.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.722]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseACL.js -> ../../node_modules/parse/lib/react-native/ParseRole.js -> ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/ParseACL.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.722]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/SingleInstanceStateController.js -> ../../node_modules/parse/lib/react-native/ObjectStateMutations.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.723]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseObject.js -> ../../node_modules/parse/lib/react-native/unsavedChildren.js -> ../../node_modules/parse/lib/react-native/ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.724]  WARN     Require cycle: ../../node_modules/parse/lib/react-native/ParseUser.js -> ../../node_modules/parse/lib/react-native/ParseSession.js -> ../../node_modules/parse/lib/react-native/ParseUser.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Sat Jun 05 2021 14:37:46.725]  LOG      Running "MonorepoApp" with {"rootTag":351,"initialProps":{}}

Would you mind to provide more details on how you got those warnings?

These warnings come from the parse javascript. I think you can ignore the warning. This is something the maintainers will have to resolve. I dont think it belongs here;
If you dont want to see the warnings, find the following file in your node_modules directory;
\node_modules\metro\src\lib\polyfills\require.js
and comment out line 117
  // console.warn(
  //   `Require cycle: ${cycle.join(" -> ")}\n\n` +
  //     "Require cycles are allowed, but can result in uninitialized values. " +
  //     "Consider refactoring to remove the need for a cycle."
  // );

Keep in mind it will suppress this warning for everything, even require cycles you cause.

Hi... Any solution? here it only occurs when I call
Parse.setAsyncStorage(AsyncStorage);
`Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseRelation.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\decode.js -> node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\decode.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\EventuallyQueue.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\SingleInstanceStateController.js -> node_modules\parse\lib\react-native\ObjectStateMutations.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\arrayContainsObject.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unsavedChildren.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseUser.js -> node_modules\parse\lib\react-native\ParseSession.js -> node_modules\parse\lib\react-native\ParseUser.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. ERROR  TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[0], "../../../react-native/Libraries/vendor/emitter/EventEmitter").prototype.addListener')
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
BUNDLE  ./index.js
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseRelation.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\decode.js -> node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\decode.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\EventuallyQueue.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\SingleInstanceStateController.js -> node_modules\parse\lib\react-native\ObjectStateMutations.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\arrayContainsObject.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unsavedChildren.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. WARN  Require cycle: node_modules\parse\lib\react-native\ParseUser.js -> node_modules\parse\lib\react-native\ParseSession.js -> node_modules\parse\lib\react-native\ParseUser.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle. ERROR  TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[0], "../../../react-native/Libraries/vendor/emitter/EventEmitter").prototype.addListener')
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling unmountApplicationComponentAtRootTag). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
BUNDLE  ./index.js
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseRelation.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\decode.js -> node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\decode.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\EventuallyQueue.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\SingleInstanceStateController.js -> node_modules\parse\lib\react-native\ObjectStateMutations.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\arrayContainsObject.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unsavedChildren.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseUser.js -> node_modules\parse\lib\react-native\ParseSession.js -> node_modules\parse\lib\react-native\ParseUser.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
ERROR  TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[0], "../../../react-native/Libraries/vendor/emitter/EventEmitter").prototype.addListener')
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
info Reloading app...
BUNDLE  ./index.js
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseRelation.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\decode.js -> node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\decode.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\EventuallyQueue.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\SingleInstanceStateController.js -> node_modules\parse\lib\react-native\ObjectStateMutations.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\arrayContainsObject.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unsavedChildren.js -> node_modules\parse\lib\react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseUser.js -> node_modules\parse\lib\react-native\ParseSession.js -> node_modules\parse\lib\react-native\ParseUser.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
ERROR  TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[0], "../../../react-native/Libraries/vendor/emitter/EventEmitter").prototype.addListener')
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling unmountApplicationComponentAtRootTag). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.`
Helpp... Tks...

I do not think Parse.setAsyncStorage(AsyncStorage); is the real cause. In my case, even I delete this statement out it still gave the warnings.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-nat
ive\ParseACL.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib
react-native\ParseObject.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib
react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseObject.js

Would you mind to share the version of Parse JS SDK that you are using?

Hello, I just installed parse 3.3.0 freshly on react-native project and it throws the same errors mentionned about the cycle problem,

I'm truing Parse with react-native and I see that the issue is pointing to "import Parse from "parse/react-native.js";"
It's not if you are setting the async storage or not. The package throws these warnings when imported.

could you guys please try with the latest version of the parse js sdk?

I'm closing this issue. Please feel free to open it again in the case the problem persists.

@davimacedo It happens with the existing project. Actually this issue happens on Parse-SDK-JS for me. I don't use @parse/react or @parse/react-native.

In this case, would you mind to open an issue at the Parse-SDK-JS repo?

it's still a issue on Parse 3.4.0
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\encode.js -> node_modules\parse\lib\react-native\ParseRelation.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\canBeSerialized.js -> node_modules\parse\lib\react-native\ParseRelation.js -> node_modules\parse\lib\react-native\ParseQuery.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\decode.js -> node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\decode.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\EventuallyQueue.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseACL.js -> node_modules\parse\lib\react-native\ParseRole.js -> node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\ParseACL.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\SingleInstanceStateController.js -> node_modules\parse\lib\react-native\ObjectStateMutations.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\arrayContainsObject.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unique.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseObject.js -> node_modules\parse\lib\react-native\unsavedChildren.js -> node_modules\parse\lib\react-native\ParseObject.js

Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
 WARN  Require cycle: node_modules\parse\lib\react-native\ParseUser.js -> node_modules\parse\lib\react-native\ParseSession.js -> node_modules\parse\lib\react-native\ParseUser.js


Admin view for e-signature framework agreements (for G12 onwards)

https://trello.com/c/psi3gVdH/157-2-admins-can-view-the-new-pdf-for-g12

Simplify index page content to reduce confusion about whether an agreement needs a countersigning 'action' to happen
Change agreement list page to make it clear that no countersigning action is required (and to contact suppliers if there is a problem)
New template for showing signer details for G12+ frameworks, with link to countersigned PDF if present

Signed, but not countersigned:

Signed and countersigned (link to PDF file generated by Jenkins):

Agreement list page for an e-signature framework (eg G12):

On the Agreement list page for an e-signature framework, suggest a slight rewording of first sentence as there is no longer uploading of a file:
If there's a problem with the agreement, contact the person who signed it.

On the Agreement list page for an e-signature framework, suggest a slight rewording of first sentence as there is no longer uploading of a file:
If there's a problem with the agreement, contact the person who signed it.

Ah great spot @NoraGDS!

Woohoo thanks @gidsg !


I tried this but it's not working

Please help me it's working. I followed your all instructions on this website https://news-portal-farhan-nabeel.blogspot.com/?m=0 but it's not working please help me

You are trying to add it to a blogspot domain, use the cdn method.

How please provide me a video please sir it's humble request 🙏


Incorrect bottom inset (Android)

Description
Unistyles runtime incorrectly reports insets.bottom as 0. insets.top appears to work corrrectly.
This occurs both when calling the runtime directly and when calling the createStyleSheet runtime param
Steps to reproduce

Use Android device with bottom safe area (e.g. Pixel 7 Pro)
Compare useSafeAreaInsets() to UnistylesRuntime.insets

Snack or a link to a repository (optional)
https://snack.expo.dev/@haydenbriese/graceful-blue-sandwich
Unistyles version
2.7.1
React Native version
0.73.6
Platforms
Android
Engine
Hermes
Architecture
Paper (old)

Hey 👋
What does it mean with bottom safe area?
Do you use button or gesture navigation?
What's your version of Android?
Do you use any window flags?

I'm currently experiencing the same problem with button navigation on Android 14 with top inset working perfectly fine while bottom inset do not.
I'm using Expo with their "absolute" positioning. I'm unsure if they set the FLAG_LAYOUT_NO_LIMITS flag or not, but the navigation bar is positioned on-top of the content. You can find the native expo code here.
As I've understood it, you're not using the same logic as react-native-safe-area-context. However, in this case when I'm using "absolute" positioning of the navigation bar in expo, react-native-safe-area-context give the correct bottom inset (48px) while unistyles does not (0px).
Unistyles is by far the best styling system I've tried so far, hope you're at least able to point us in the right direction

Yes, that is the case. I'm not aware of what "absolute positioning" in Expo is doing. It would be perfect to get a minimal reproduction to patch it.

Great! You can find a minimal reproduction here. Please let me know if it's unclear or if something is missing.

@jpudysz
Thanks for creating such an amazing library!
Like the above comments have already mentioned, even we've been seeing that bottom inset from UnistylesRuntime always returns 0. And we are not setting  NavigationBar position to absolute.
Interestingly, even useSafeAreaInsets returns bottom inset as 0. Not sure what we're missing though.
Tested Devices

Pixel 6
Redmi Note 9 Pro
Samsung Galaxy S20 FE 5G

Unistyles Version
2.7.1
Platform
Android

Thanks guys! I will check the repro and try to patch it 😇

Guys, I've created a patch for expo absolute positioning. Let me know if that works for you!
How to install 2.7.2-rc.1:
yarn add react-native-unistyles@next

If anyone has another case, please create a small repro 🙏

@hbriese @Dhruv-manktala what are your cases? Did you try 2.7.2-rc.1?

I assume no reply = no issues. I will release next version today

@jpudysz hi, just installed 2.7.1 and it seems that the insets are being *2 on Android.
I'm using bare react-native with expo-modules core.
Maybe something is being picked up and it thinks that I'm using just expo and it doubles the inset value.

Android 🙄
Thanks for the feedback, will try to repro today

Hi, I noticed regression on low-end Android device (Alcatel 1B with Android 10) in bare react-native.
const { bottom } = useSafeAreaInsets // 0 :white_check_mark:
runtime.insets.bottom -> // 0<EMAIL_ADDRESS>:white_check_mark:
runtime.insets.bottom -> // 48<EMAIL_ADDRESS>⭕

@jpudysz just a side note, on emulators the insets are fine, the issue happens in real devices only, in my case Samsung S22 with A14

Thanks guys, please stay at 2.7.1. I need to rethink expo status bar support

useSafeAreaInsets():
{"left":0,"bottom":48,"right":0,"top":30.85714340209961}

UnistylesRuntime.insets
{"top":0,"bottom":0,"left":0,"right":0}

UnistylesRuntime.statusBar.height
30

UnistylesRuntime.navigationBar.height
48

I'll use useSafeAreaInsets for now since it has been tested by the masses, but I noticed that the statusBar and navigationBar height matches the insets from it.
Note: this is on version 2.5.0

Why do you use old version? Please use 2.7.1

Hey guys!
I would really appreciate checking out new implementation in 2.8.0-beta.3!
Few notes:

min required version is Expo SDK 51 / React Native 0.74
it doesn't support react-native-macos as there is no 0.74 version yet
I didn't test react-native-visionos and react-native-tvos yet
react-native-windows is not supported yet

Other notes:

switching dynamically cutout on emulator is not supported. If you change the cutout type then please reload the app
edgeToEdge layout a.k.a FLAG_LAYOUT_NO_LIMITS or expo absolute positioning is enabled by default

I will explain more with release notes. ATM I'm looking for your feedback!

@jpudysz tested on Pixel 7 Pro A14 emulator and bottom insets seems fine! Will test on real device and update.

I’ve just released version 2.8.0-rc.1 with a complete rewrite of Android and Android Insets. It includes additional improvements on top of beta.3.
Happy testing!

@jpudysz just tested it on a samsung s22 A14, it seems that they are not properly calulated, still :/
Even the Logbox warnings are being cut off on the bottom for about it's half size:

Before we rise the issue, I need to know couple things.
Do you use react-native-keyboard controller?
How are you setting margins/paddings ?
Do you have react-native-safe-area-context for the reference?
Do you use any custom flags?

Also, can you run the examples/expo on your device ? There is a "Layout" screen at the bottom with all the required information and without the noise from other libraries.

@jpudysz Android on examples/expo fails to run, incompatibility issues with gradle 8 and target sdk 33 instead of 34 for app compat. Couldn’t spent time fixing those I was too tired last night. Will try again tonight.
I don’t use keyboard controller, just safe area context.
On the first screenshot above, it worked fine on 2.8.0, it’s an ImageBackground that stretches to the screen height, for some reason the height is reported as smaller(?) this creating the gap, the Logbox being cut in the middle as it seems pushed down contradicts this though.
The bottom insets reported by useSafeAreaInsets are the same as the UnistylesRuntime.
My bottom tab bar when user is logged in is custom and animated with reanimated, it hides and shows smoothly but there are some cases where it will jump and stay way higher than it should (on Android only). I would say it locks at the same gap as shown on first screenshot above (it’s the app’s landing page when user is not logged in).
let me know if you want to connect offline and test it out together.

Android on examples/expo fails to run, incompatibility issues with gradle 8 and target sdk 33 instead of 34 for app compat. Couldn’t spent time fixing those I was too tired last night. Will try again tonight.

Can you try with the most recent Android Studio (Koala 2024.1.1)?

The bottom insets reported by useSafeAreaInsets are the same as the UnistylesRuntime.

That's the most important thing. Safe area insets has different algorithm , but long story short I'm using WindowCompat, so it's what I get from the Android and they recevice the same value too.

it will jump and stay way higher than it should

Do you use some kind of paddingBottom or marginBottom = UnistylesRuntime.insets.bottom?
Maybe something is odd with the calculations?
Remember that insets are reported few times on Android. Maybe reainmated has the initial value when your start to animate?
Do you have same issue when you move to SafeAreaInsets.bottom?

let me know if you want to connect offline and test it out together.

Sure! Let's connect tomorrow. I guess we're in the same timezone.

hi, I see this issue is closed but I can't find the answer for me.
Is there a way to disable Unistyles edgeToEdge behavior?

No, it's not possible.
Without it, I need to use hacky listeners from Android 6.
Edge to edge means that you need to add bottom padding eg. when you use bottom bar. It's not that scary :)

No, it's not possible. Without it, I need to use hacky listeners from Android 6.
Edge to edge means that you need to add bottom padding eg. when you use bottom bar. It's not that scary :)

Thank you for quick reply!
The thing is we use at the moment SafeAreaProvider. And we do take care only about bottom insets in modals at the moment.
Since the app is on production I would love to do incremental changes to have confidence about changes.
What would you advise in this case?

Stay on v. 2.7.2, I didn't add that many new features.
Branch 2.x will only get bug fixes now, so It will be smart to integrate 3.x.


Not Found: /graphql

Afer making regular project (default settings) I got error  Not Found: /graphql
django_1    | Not Found: /graphql
django_1    | <IP_ADDRESS> - - [07/Mar/2019 15:42:20] "GET /graphql HTTP/1.1" 404 -

Steps to reproduce
[//]: # pip install "cookiecutter>=1.4.0"
[//]: # cookiecutter https://github.com/pydanny/cookiecutter-django
[//]: # docker-compose -f local.yml build
[//]: # docker-compose -f local.yml up
I never wanted to use Grahpql... why it's in my project? what happenning?

Sorry, the problem was on my side)
I had opened tab in browser with vue.js gui cli
so I'm closing this issue)


add architecture ID for NEORV32 core

According to marchid.md

Open-source project maintainers may make pull requests against this repository to request the allocation of an architecture ID.

I would like to request an architecture ID assignment (architecture ID 19) for the NEORV32 processor.
:)

I definitely don't want to jostle and maybe this belongs into a new issue, but what are the specific requirements (if there are any) a core/project/you-name-it has to met in order to obtain an official (open-source) architecture ID? 🤔 😉

@stnolting This fell through the cracks; jostling was the right move in this case.

This fell through the cracks

Anyway, thank you very much! :)


Create prowler.info.yml

Please update this file.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @mx-rrumsey, what is this about? I don´t get it. Can you explain?


Fixed #27860 -- Dropped varchar_pattern_ops/text_pattern_ops index before altering char/text field in PostgreSQL.

Ticket 27860.

I think that this PR should wait for #8136.

buildbot, test on oracle.

I rebased from master.

I'm not convinced yet that we need to drop the index. Isn't it enough to remove the constraint?

We drop the index only when field type is changing, hence after alter operation we'll never recreate it with the same operator class.

@timgraham Thanks for review.

I rebased from master.


Clean up the insertion of documents into the aggregate write buffer

This is a short preamble to refactoring agg_copy, but I'm PRing it separately because it mostly touches AggregateWriteBuffer and I'm more confident in the change. It moves agg_copy to Stripe::agg_copy and adds two new methods to AggregateWriteBuffer: add and emplace. The implementation of emplace uses placement new to create the document instead of a reinterpret cast because this is precisely what it's designed for and makes the intent crystal clear.
The two new methods also adjust the buffer position and the number of bytes pending copy. This puts directly related logic together that was previously spread out across hundreds of lines.
The AggregateWriteBuffer::add_buffer_pos method has been removed, improving encapsulation and simplifying the interface.
This also moves AggregateWriteBuffer.cc and AggregateWriteBuffer.h to src/ instead of include/ because it's an internal detail at this point, not part of the public interface.

LSan detected a leak in the ImageMagick unit test, and the AuTest ja3_fingerprint failed.

[approve ci rocky autest]

LSan detected the same leak after rerolling the CI.

[approve ci rocky]

[approve ci docs]

looks good to me.


Specific build for package

I'm trying to create an AppImage for Wine, for I'm having trouble with setting the Wine build.
When creating an AppImage with "winehq-stable" in the packages list, it will install the 2.0.2 version. If I use "winehq-stable=6.0.4~buster" instead, Wine won't be installed. If I replace "winehq-stable=6.0.4~buster" with "winehq-stable 6.0.4~buster", it installs winehq-stable 2.0.2 instead. How can I specify which package build do I want to install?
Here is a sample of the YML file:
app: Wine
binpatch: true
ingredients:
  dist: buster
  packages:
    - winehq-stable=6.0.4~buster
    - bash
    - cabextract
    - dash
    - perl
    - coreutils
    - mesa-utils
    - unionfs-fuse
  sources:
    - deb http://deb.debian.org/debian buster main contrib non-free
    - deb https://dl.winehq.org/wine-builds/debian/ buster main
script:
  - cat > ./usr/bin/winewrapper << 'EOF'
  - #!/bin/bash
  -
  - # WINE env
  - export WINEPREFIX=${WINEPREFIX:-"$HOME/.wine-appimage"}
  - export WINEDEBUG=${WINEDEBUG:-"fixme-all"}
  -
  - # DXVK env
  - export DXVK_HUD=${DXVK_HUD:-"0"}
  - export DXVK_LOG_LEVEL=${DXVK_LOG_LEVEL:-"none"}
  - export DXVK_STATE_CACHE=${DXVK_STATE_CACHE:-"0"}
  - export DXVK_CONFIG_FILE=${DXVK_CONFIG_FILE:-"$progHome/dxvk.conf"}
  -
  - # check gpu vendor
  - VENDOR=$(glxinfo -B | grep "OpenGL vendor")
  -
  - if [[ $VENDOR == *"Intel"* ]]; then
  -   export VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/intel_icd.i686.json:/usr/share/vulkan/icd.d/intel_icd.x86_64.json"
  - elif [[ $VENDOR == *"NVIDIA"* ]]; then
  -   export VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json"
  - elif [[ $VENDOR == *"Radeon"* ]]; then
  -   export VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json"
  - fi
  -
  - # Load winecfg if no arguments given
  - APPLICATION=""
  - if [ -z "$*" ] ; then
  -   APPLICATION="winecfg"
  - fi
  -
  - # Allow the AppImage to be symlinked to e.g., /usr/bin/wineserver
  - if [ -n "$APPIMAGE" ] ; then
  -   BINARY_NAME=$(basename "$ARGV0")
  - else
  -   BINARY_NAME=$(basename "$0")
  - fi
  -
  - if [ -n "$1" ] && [ -e "$APPDIR/bin/$1" ] ; then
  -   MAIN="$APPDIR/bin/$1" ; shift
  - elif [ -n "$1" ] && [ -e "$APPDIR/usr/bin/$1" ] ; then
  -   MAIN="$APPDIR/usr/bin/$1" ; shift
  - elif [ -e "$APPDIR/bin/$BINARY_NAME" ] ; then
  -   MAIN="$APPDIR/bin/$BINARY_NAME"
  - elif [ -e "$APPDIR/usr/bin/$BINARY_NAME" ] ; then
  -   MAIN="$APPDIR/usr/bin/$BINARY_NAME"
  - else
  -   MAIN="$APPDIR/usr/bin/wine"
  - fi
  -
  - if [ -z "$APPLICATION" ] ; then
  - "$MAIN" "$@" | cat
  - else
  - "$MAIN" "$APPLICATION" | cat
  - fi
  - EOF
  - chmod +x ./usr/bin/winewrapper
  - wget -q "https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks" -P ./bin && chmod +x ./bin/winetricks
  - wget -N https://source.winehq.org/git/wine.git/blob_plain/HEAD:/loader/wine.desktop
  - sed -i -e 's|Icon=wine.*|Icon=/usr/share/icons/wine.svg|g' wine.desktop
  - sed -i -e 's|Name=Wine.*|Name=Wine|g' wine.desktop
  - sed -i -e '/Name\[.*/d' wine.desktop
  - sed -i -e 's|Exec=wine.*|Exec=winewrapper|g' wine.desktop
  - echo 'Categories=Utility;Settings;' >> wine.desktop
  - mkdir -p ./usr/share/applications/
  - rm ./usr/share/applications/wine.desktop || true
  - cp ./wine.desktop ./usr/share/applications/wine.desktop
  - mkdir -p usr/share/icons
  - wget -N https://source.winehq.org/git/wine.git/blob_plain/HEAD:/dlls/wineandroid.drv/wine.svg
  - cp wine.svg usr/share/icons
  - wget -q "https://github.com/mmtrt/sommelier-core/raw/master/themes/light/light.msstyles" -P ./winedata/resources/themes/light

Please check out https://github.com/mmtrt/WINE_AppImage. This task is too complex for pkg2appimage.

I'm not asking for a Wine AppImage. I'm working on it. I tried to build an AppImage using that project, but it didn't work.
What I'm asking for is for a method to install a package with an specific version. Is that really too complex for pkg2appimage?

Just checked pkg2appimage source. It seems that, in order to have version support, the function apt-get.do-download would need to be updated accordingly. Otherwise, it will only consider the package name, but not the package version. Is that right?

Packaging WINE is too complex for kg2appimage. Trust me. I've been there.

I've managed to package Wine with pkg2appimage with ease, but I had to do some improvements in pkg2appimage to do do. I will submit a pull request later


Incompatibility with rspec --options on 6.0+

I'm using https://github.com/sj26/rspec_junit_formatter, and I am passing the following options when running tests:
-r rspec_junit_formatter
--format RspecJunitFormatter
--out tmp/rspec/junit.xml

This is supposed to produce formatted output to tmp/rspec/junit.xml. This works fine with knapsack_pro 5.7.0. As soon as I update to 6.x, the output file is no longer being created.

Thanks for looking into it! I'm using something similar with a file for the options with: knapsack_pro:rspec[--options ./.rspec]
I also have some custom reporters that might be part of the issue, but the non-custom part of the config is:
-r rspec_junit_formatter
--format RspecJunitFormatter
--out tmp/rspec/junit.xml
--format documentation

I'll take a look at some of the custom reporters I have if it can't be reproduced.

Looking further into the test output, it looks like --format documentation isn't working as expected either! So, it seems like maybe something is off with using --options.

What is your RSpec version?
I created a script to run Knapsack Pro with the RSpec --options provided, and the JUnit XML file is generated correctly.
https://github.com/KnapsackPro/rails-app-with-knapsack_pro/commit/675a1188f39cf8a67ffb447a4487db50fcf98619
I'm not sure how to reproduce the issue.
Can you share more details about your config? What's the content of rails_helper.rb/spec_helper.rb. What are your custom formatters. The full list of options that are provided to the Knapsack Pro command.
If that's private data, you can share it with the support email https://knapsackpro.com/contact
You can also look at recent changes we did in 6.x version of the knapsack_pro gem. We added a custom RSpec formatter to track tests execution time. Maybe this is causing some conflict with your formatters.

CHANGELOG https://github.com/KnapsackPro/knapsack_pro-ruby/blob/master/CHANGELOG.md#600

the new formatter added https://github.com/KnapsackPro/knapsack_pro-ruby/pull/229/files#diff-224867ff67d486513c374ab2291d9d98db5a02b567424f0e282dcc90988df458R1

Here are my versions:
RSpec 3.12
  - rspec-core 3.12.2
  - rspec-expectations 3.12.3
  - rspec-mocks 3.12.6
  - rspec-rails 6.1.0
  - rspec-support 3.12.1

Seems like something up with my particular setup in general (will dig into that more). I've trimmed down the options file to:
--format documentation

And, the output is not coming out in the "documentation" format, when run like: knapsack_pro:rspec[--options ./.rspec]. However, when run like knapsack_pro:rspec[--format documentation], it outputs as expected.

If the --format documentation is present in the ./.rspec file then the output should be in the documentation format. Is --format documentation inside of the ./.rspec file?
This is how I use options: https://github.com/KnapsackPro/rails-app-with-knapsack_pro/blob/1f217df18c71db7dae01f28f89a0e394b33a2a61/bin/knapsack_pro_queue_rspec_junit_with_rspec_custom_options#L18
Maybe you should use .rspec instead of ./.rspec. Why do you add ./?
Please try bundle exec rake  "knapsack_pro:rspec[--options .rspec]". Please remember to add "to wrap the options passed to the knapsack_pro command. Otherwise the options won't work.

Looking at the command generated by the runner:
/usr/local/bin/ruby -I/app/vendor/bundle/ruby/3.2.0/gems/rspec-core-3.12.2/lib:/app/vendor/bundle/ruby/3.2.0/gems/rspec-support-3.12.1/lib /app/vendor/bundle/ruby/3.2.0/gems/rspec-core-3.12.2/exe/rspec --format documentation --options .rspec --format progress --format KnapsackPro::Formatters::TimeTracker --default-path spec ...

It looks like an extra --format progress is getting inserted (overrides --format documentation). This doesn't yet explain my original issue, but seems like there is something different in the generated command with 6.0+ when it comes to the format options.

@irphilli I got an email notification that you were asking about:

Looking at the command generated by the runner:
/usr/local/bin/ruby -I/app/vendor/bundle/ruby/3.2.0/gems/rspec-core-3.12.2/lib:/app/vendor/bundle/ruby/3.2.0/gems/rspec-support-3.12.1/lib /app/vendor/bundle/ruby/3.2.0/gems/rspec-core-3.12.2/exe/rspec --format documentation --options .rspec --format progress --format KnapsackPro::Formatters::TimeTracker --default-path spec ...
It looks like an extra --format progress is getting inserted (overrides --format documentation). This doesn't yet explain my original issue, but seems like there is something different in the generated command with 6.0+ when it comes to the format options.

If a formatter is not detected in Regular Mode then --format progress is added as a default formatter. It seems that --options .rspec is not loaded as the RSpec configuration option, and the --format documentation could not be detected. It's something that we could improve here:
https://github.com/KnapsackPro/knapsack_pro-ruby/pull/229/files#diff-23b86e488780bfc91dda40439ac5e4f6be1c67e0739bad6c286d36bae402adf3R54
Do you see a similar issue for Queue Mode: bundle exec rake  "knapsack_pro:queue:rspec"?

I will try queue mode! I was going to follow up with some additional info, but you got to the same conclusion :).

So, I do see the same issue in queue mode, but looks like it was already like that in 5.x.
Going back to standard mode, I went ahead and got rid of our options file (passed in arguments directly), and things are working fine, even with the custom reporters. The only strange thing is that the generated rspec command still has an extra --format progress in there.

I think it is a bug in our code. The extra --format progress option is added when formatters are empty but we don't check if someone passed --format option, or --options .rspec_custom_file that has --format inside of the file.
It was introduced here for Regular Mode.
I notice also issue for Queue Mode.
I reported this in the internal ticket.
@irphilli Please use inline options. Thanks to that, the --format option is applied.
Example:
# Queue Mode (--format documentation is applied inline)
bundle exec rake "knapsack_pro:queue:rspec[--options .rspec_custom.options --format RspecJunitFormatter --out tmp/rspec.xml --format documentation]"

# Regular Mode (--format documentation is applied inline)
bundle exec rake "knapsack_pro:rspec[--options .rspec_custom.options --format RspecJunitFormatter --out tmp/rspec.xml --format documentation]"


Gui refactoring

[x] Refactor nav gui with "prev pos", and only show the latest updated amongst world/game/boat position
[x] Refactor and combine all "raw" readouts helpers into a single tab (probably Debug)
[x] Refactor some useful info into Route (maybe the same "active" position as above?) so Debug doesn't have to be shown when doing routing
[x] Refactor combat helper and level up manager into main helper (but only show them when the respective state is active)
[ ] Refactor shop/inventory tabs to have adaptive column width depending on window width?

Closing for now (with last as won't-fix).


Completing Authoring features (round 2)

[ ] Adding CodeTemplate
[ ] Editing CodeTemplate
[ ] Editing CodeTemplate (in IDE editor)
[ ] Deleting CodeTemplate
[ ] Adding CodeTemplateCommand
[ ] Adding CodeTemplateCommandWithTemplate
[ ] Adding CLICommand
[ ] Editing CLICommand
[ ] Deleting ANY Command
[ ] Adding LaunchPoint
[ ] Editing LaunchPoint
[ ] Deleting LaunchPoint

What does the experience for adding and editing code templates (and commands)  or CLI commands look like?
What does the experience for adding and editing launch points look like?
Mental Models
From an end users perspective they are either automating a code template or they are automating a CLI command.
They need to sort out when and where to do those things with a launch point.
The the CLI, these things are all individual items with complex relationships.
But to the end user, they are much simpler constructs.
You are either harvesting a code file, or running a CLI.
So to them it is logically: "Add/Edit/Delete Code Template" or "Add/Edit/Delete a CLI Command"
When they do this, they define all the pieces together, and edit only some of the pieces. They delete the whole piece.

So, lets say that we group all automation inside a virtual folder called "Auutomation".

In that virtual folder, we have (in this order):

All the LaunchPoints (alphabetically ordered) then,
All the CLI Commmands then,
All the CodeTemplatesWithCommands.

A codetemplate is a node that encapsulates the template and the command.
You can have a command without a template, so the command can be null until its created (by defining its targetpath).
We can display a codetemplate that has no command with an icon, that says we need to define a targetpath.
Deleting this node deletes both command and template.
Editing this node edits all properties of both, which we update as one or two calls.

We need to care about these cases:

[ ] A codetemplate with no referencing command
[ ] A codetemplate with a referencing command
[ ] A codetemplate with multiple referencing commands

In each of these cases, we need to display some node in the "Automation" collection, and from there, add/edit/delete the various pieces (template and command)


⚠ Bofrost.be has degraded performance

In ea32666, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1197 ms

Resolved: Bofrost.be performance has improved in 9e48253 after 23 minutes.


fix(company data): error handling

Description

remove unwanted inputs
fix crash issue if any of the values are missing in the respose
error handling

Why
change request
Issue
#887 #888 #894
Checklist
Please delete options that are not relevant.

[x] I have followed the contributing guidelines
[ ] I have performed IP checks for added or updated 3rd party libraries
[ ] I have created and linked IP issues or requested their creation by a committer
[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally
[ ] I have added tests that prove my changes work
[ ] I have checked that new and existing tests pass locally with my changes
[ ] I have commented my code, particularly in hard-to-understand areas

created new PR with release branch


Most middleware is no longer bundled with Express and must be installed separately error

Looks like you need to update the example file, maybe rework a few things.
Full error:
development/fbit/example/node_modules/express/lib/express.js:99
      throw new Error('Most middleware (like ' + name + ') is no longer bundled with Express and must be installed separately. Please see https://github.com/senchalabs/connect#middleware.');
      ^

Error: Most middleware (like bodyParser) is no longer bundled with Express and must be installed separately.

@phrozen755 the express version he's most likely using is 3.x.x whereas if you ran npm install express at the moment it will give you 4.x.x.
Try running npm install<EMAIL_ADDRESS><4.0.0" --save from the example folder and it will resolve the error you're seeing.

Thanks for answering the question @phrozen755. I've merged #13 and updated the example to use express 4.x.x.
I'm did a version bump and published to npm, so v0.3.2 has the update included.

:+1:

Thanks gentlemen! :+1:

Thanks Gentle Man

thanks man!

Thanks 👍

Thanks, Gentlemen 👍

After coming down to an earlier version of express as suggested, I faced a new error-
`router.get('/', function(req, res, next) {
^
TypeError: Cannot read property 'get' of undefined`

<EMAIL_ADDRESS><4.0.0"
run this
it woked for me

After coming down to an earlier version of express as suggested, I faced a new error-
router.get('/', function(req, res, next) {
       ^

TypeError: Cannot read property 'get' of undefined

I have same issue right now and cannot fix it

Got the Same Problem like geraldanosike :(

Got same problem

After I got this error
throw new Error('Most middleware (like ' + name + ') is no longer bundled with Express and must be installed separately. Please see https://github.com/senchalabs/connect#middleware.');
^
Error: Most middleware (like methodOverride) is no longer bundled with Express and must be installed separately.

After I got his error If I install the express greater than 4 version it is working but If I install
npm install<EMAIL_ADDRESS><4.0.0" --save I am getting following error
router.use('/ivr', twilio.webhook({validate: false}), ivrRouter);
^
TypeError: router.use is not a function

@phrozen755 the version of express @smurthas is using in this example is 3.x.x, whereas if you run npm install express at the moment it will give you 4.x.x.
Try running npm install<EMAIL_ADDRESS><4.0.0" --save from the example folder and it will resolve the error you're seeing.

thank you

(connect deprecated limit: Restrict request size at location of read app.js:24:17)
it appears after that
then how to solve this error!!

Thank you so much its working now :)


Dockerized build/test environment for tough-cookie.

Added in Istanbul code coverage reporting. A few changes to the .gitignore and the package.json as well (for the dependency and running coverage). I think this has everything we discussed. :) Please do comment and let me know if there is anything either of you would like changed/modified/updated!

Sorry, but why all the things in one commit?

Why do we need such a docker file into a repo? I mean, why it goes with vim? Very strange decision IMO. You can edit files locally with any editor and use docker only for tests. And why it's not in .npmignore?

I was being a bit too hesitant with .gitignore; thank you, I'll fix that.
I tried to split out the docker compositions so I could work in the container and use local settings; but yes, you are right, one can install and test in the container and edit on the outside. I'll make another change there and keep my local setup for my own work. In terms of why are the two in one commit, it's a simple changelist, and since its my first pull request, I thought I'd just gather up what I was doing around build and test into one pull request.
Appreciate your comments. :)

I have made quite a few changes based on your comments; users that don't use the docker image for build/test will have to globally install istanbul or use npm link if they want coverage. Thanks for the feedback; let me know what you think!

@apsavin -- please let me know if I should add a .npmignore for the Docker changes. NPM says that it relies on .gitignore when there is no .npmignore present; but if you would like me to be explicit, I'm willing to make another change. NPM on .npmignore/.gitignore:
https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package

I've tweaked on the simple request quite a bit; please let me know if you'd like me to close this and restructure my commits into one commit so the repo stays clean. I would then open a better/cleaner pull request. Thanks for the comments and questions.

I'm going to close this pull request and break it out into:
a) Istanbul coverage
b) Dockerized setup (with .npmignore)


APIcast fails CORS preflight request

When accessing an API protected by APIcast from a browser on different domain the browser is going to send CORS Preflight request. That is going to miss the authentication and not succeed.
We should investigate what would be the correct path forward (using Access-Control-Allow-Credentials, Access-Control-Allow-Headers, other ideas?) .
Source: https://stackoverflow.com/questions/44261553/cors-with-3scale

You already solved this problem, right?
https://github.com/3scale/apicast/tree/3.1-stable/examples/cors

Could be solved, but we should verify.

Works for me using the new CORS policy.


Gotify notifications support

Describe the feature request
Send notifications from gatus to gotify via api interface.
gotify
Why do you personally want this feature to be implemented?
In the last days I tried unsuccessfully to send notifications from gatus to gotify via the custom module.
The problem is that gatus can only send "body" or "headers" via the custom module.
Gotify on the other hand needs "form" or "data" as input and complains about the missing message value.
Unless I missed something I guess both tools are currently incompatible by design.
How long have you been using this project?
No response
Additional information
Since both programs are written in go, I think it should be quite easy to implement native support for gotify or at least adapt the custom module accordingly.

Hey @Tenyun!
How are you configuring your custom alerting provider?
I had a look at Gotify's API, and it should be possible to create a message. In fact, it seems like it's using JSON, but even if it doesn't, form data is actually sent using a header and the body.
Submitting this form:
<form method="POST">
  <input name="username" value="johndoe">
  <input name="password" value="hunter2">
</form>

is actually just sending a request with the following header:
Content-Type: application/x-www-form-urlencoded

and the following body:
username=johndoe&password=hunter2

Hi @TwiN
At the moment my custom alert provider looks like this.
alerting:
  custom:
   url: "http://<IP_ADDRESS>:4444/message?token=<myToken>"
   method: "POST"
   body: |
     {
             "message": "Test Message",
             "priority": 2,
             "title": "Test Title"
     }

I get the following error message:
Failed to send an alert for endpoint=Gitea: call to provider alert returned status code 400: {"error":"Bad Request","errorCode":400,"errorDescription":"Field 'message' is required"}

I think I still don't quite understand how to put together a custom alert.

Ok I just figured it out.
I was missing the correct headers entry in the gatus config.
My config now looks like this and works so far.
alerting:
  custom:
   url: "http://<IP_ADDRESS>:4444/message?token=<myToken>"
   method: "POST"
   headers:
     Content-Type: "application/json"
   body: |
     {
             "message": "[ALERT_DESCRIPTION]",
             "priority": 2,
             "title": "[ENDPOINT_NAME]"
     }

Thanks for the quick help.

@Tenyun I'm glad you figured it out!


[Feature Request] Adding Popper Media... ask user: Replace or Add To Existing

when media is already existing in a given type (back glass, DMD, etc)... if a user drag-n-drop a new file Studio is automatically adding the new media as additional file. In many cases users may want to overwrite / replace the existing file, not add to it.
Happens when a newer/better MP4  video (back glass , FullDMD, etc) gets posted.

As discussed on discord, for these media assets and additional selection dialog makes sense here.

implemented

implemented

Implemented where?  Its not working if a media file exists in a Popper media type (see screenshot) and I drag a new file to that window, Studio never asks

Implemented but not yet released. We close tickets once we have delivered.
No worries, the release is planned for this month ;)

Implemented but not yet released. We close tickets once we have delivered. No worries, the release is planned for this month ;)

this month !? that could be "days" from now.. I'm not sure I will be able to handle that... I will need a lot of distractions.... potentially both legal and not. I'll try my best

Delivered with 3.0.0


Catalyst Sentinel Support

Hello, can you add support for Laravel Catalyst Sentinel for the middleware

First of all, you are probably looking for the Laravel version of this package: https://github.com/antonioribeiro/google2fa-laravel
And, how would that support be? Curently, in Laravel, you can easily write new middlewares, so I'm also not sure if the package should cover all Auth packages around, and Sentinel is one in one hundred.
If you still have questions or input, please open an issue in the proper package repository.


cant enable open free registration on this script

I add to homeserver.yaml  enable_registration: true and enable_registration_without_verification: true but cant register new user from element app. it says that register not allowed on server. what am i doing wrong?

Hi, delete /etc/matrix-synapse/conf.d/register.yaml - the script adds the enable_registration: false there.


re-re-try PR 65

again, the comment doesn't re-comment even if the job succeeds

Above:

Assay WGS template hit a google api rate limit, 403 error(https://github.com/adknowledgeportal/data-models/actions/runs/8484656987/job/23247997027#step:12:461)
Biospecimen drosophila template also hit a rate limit (https://github.com/adknowledgeportal/data-models/actions/runs/8484656987/job/23247997027#step:12:461)
Biospecimen invitro had a 404 error that also looks google-related but I've never seen before (https://github.com/adknowledgeportal/data-models/actions/runs/8484656987/job/23247997027#step:12:439)

I DID IT!

Still need to troubleshoot the changed-files.txt part but the rest of this is working and the templates updated successsfully with the new platform value. Going to merge.


POP Auth

The OPK paper discusses an method for the client instance authenticating to the MFA cosigner called "POP Auth". This protocol would make it so the MFA cosigner does not blindly trust the identity presented by the PK Token (which could be presented by anybody), but instead forces the requesting party to prove they have the corresponding signing key.
The reason this hasn't been included is because the details are still being ironed out and we will add this in when the protocol is ready for implementation.

Removing v1 label as it depends on refresh and refresh is optional for v1.


nixos/lib: Support derivations in escapeSystemdExecArg

They can be transformed into their outpath string, which is useful for config generators.
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Tested e.g. on kea, where I noticed a nixos test went missing. Therefore cleaning that up in here.


Improve AttachedRoutes conformance test

What type of PR is this?

/kind test
/area conformance
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #2058
Does this PR introduce a user-facing change?:

NONE

Thanks @levikobi! This looks reasonable to me, will defer to someone else for approval though.
/lgtm
/ok-to-test

Thanks @levikobi !
/lgtm


Why does  force text-transform uppercase?

Is this in place because it serves as some kind of compatibility hack I'm not aware of? If not, it seems like title capitalization should be left to content producers instead of being forced by CSS.
This is especially troublesome when working with titles that have words that should begin with a lowercase letter. Examples:

jQuery → JQuery (incorrect)
Have a Nice Day → Have A Nice Day (incorrect)

@galengidman No hack. Just opinionated. I see your issue. I would say treat this template like a boilerplate and make your changes.

Gotcha — appreciate the update.
I'd highly suggest changing this, but obviously it's your call. Thanks for the nice template.


[BEAM-1949] Rename DoFn.Context#sideOutput to output

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Having two methods, both named output, one which takes the "main output type" and one that takes a tag to specify the type more clearly communicates the actual behavior - sideOutput isn't a "special" way to output, it's the same as output(T), just to a specified PCollection. This will help pipeline authors understand the actual behavior of outputting to a tag, and detangle it from "sideInput", which is a special way to receive input. Giving them the same name means that it's not even strange to call output and provide the main output type, which is what we want - it's a more specific way to output, but does not have different restrictions or capabilities.

In-progress: Rename all of the runner code as well, until grep -r sideOutput sdks/java runners/ shows up clean

Coverage increased (+0.01%) to 70.582% when pulling 039b399c984c8613775bbb9d80f4b0595ad5a11f on tgroh:side_output_to_output into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.

Coverage increased (+0.007%) to 70.576% when pulling 1ab6a9aef85c0414687d3549555bf9d08958d450 on tgroh:side_output_to_output into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.

retest this please

R: @davorbonaci

Coverage increased (+0.01%) to 70.58% when pulling 1ab6a9aef85c0414687d3549555bf9d08958d450 on tgroh:side_output_to_output into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.

+R: @dhalperi

Coverage decreased (-0.1%) to 70.47% when pulling 36f9d90348cb52536ab1b25947da6e8fafc1cf75 on tgroh:side_output_to_output into 571631a5ef83ef31ea9f652c5698cea3cc95ad43 on apache:master.


Pr branch

removed copy constructor used with brace initializers for visual studio compatibility
updated visual studio build files: removed glew, added text renderer, upgraded to VS2017 and cmake 3.9

Can you squash the commits, when merging it?
since only 049c467 and 0d720ec matters, I would move them at the bottom, and squash everything above into 049c467, if it's too complicated, just squash everything into 1.


Add example using AWS secrets manager

More details here https://github.com/momentohq/public-dev-docs/pull/335

Matt and Pratik can provide more context on this.


How to promote

Hello, which document should I refer, If I would like to know how to promote the BLOB, which mentioned in <Copy snapshots
> Section.

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

ID: 56e156ed-3f4c-ce74-1791-c2a8ebfe4a99
Version Independent ID: da4df3e4-2124-009f-64d5-558c427190b1
Content: Create a read-only snapshot of a blob in Azure Storage
Content Source: articles/storage/blobs/storage-blob-snapshots.md
Service: storage
GitHub Login: @tamram
Microsoft Alias: tamram

You could use Storage explorer to promote snapshots. I'd recommend checking this video, starting from 1:21 :https://www.youtube.com/watch?v=R6gonK3cYAc
It shows a step by step guide on how to promote a snapshot. Does the video answers your question?
@tamram Should we add a little section to show how to promote snapshots?

Thanks!!!
It really helped me.
However, is there any requirements to enable/active the promotion of the blob?
I got informed that my client couldn't promote the blob, due to the promotion link isn't working.

That's interesting, are they using the latest version of storage explorer ? There is one in preview via portal, but there is also one that is a software that can be downloaded via here: https://azure.microsoft.com/en-us/features/storage-explorer/
They also must ensure that the original blob is there, not sure if they are trying to promote a snapshot to another snapshot. more details would be helpful to provide you with more assistance.

I think..... this could be bug of the portal
I've tested with my environment.
When the language is in English it seems like I can promote it

However, when the language is in Japanese..... I can't promote it.

If you call this is break fix please tell me.

@KeiroKamioka0000 What specific version of Storage explorer are you using ? This could be indeed a bug. Could you also provide me with a download link of the Japanese version ?
Thanks.

@Adam-Smith-MSFT
This is Keiro, from home.
I currently out of office.
The screenshot is from the Portal, not the Storage Explorer.
Thanks

@Adam-Smith-MSFT
I'm back to office, with this account I confirm @MightKamioka Is my personal account which is accessible account from my home.
The Screen Shot is from the Portal, instead of the Storage Explorer.

@KeiroKamioka0000 I signaled the bug internally. Feel free to use the local Storage explorer as a workaround, I will update this thread if there are any updates on the bug. The portal storage explorer is still in preview, so there are potential bugs such as the one you mentioned. I'll close this issue for now, but will re-open if i get any updates from the storage explorer/portal teams.

@KeiroKamioka0000  I have some good news, a fix is scheduled to be released by mid next week :) , it should resolve the issue in portal.


Unknown bootloader CRC - 0x2739019F - please report this on GitHub issues!

Hello,
reporting this issue with a supposedly bk72xx clone chip labled as cc8000.
I was able to download the firmware from the chip but got the above warning for the bootloader crc
Result of ltchiptool -v flash info bk72xx:
D: Found Local data snapshot (v1.5.1) - /usr/local/lib/python3.11/dist-packages/ltchiptool
I: Available COM ports:
I: |-- ttyUSB0 - CP2102 USB to UART Bridge Controller - CP2102 USB to UART Bridge Controller - Silicon Labs (10C4/EA60)
I: |   |-- Selecting this port. To override, use -d/--device
I: |-- ttyS0 - ttyS0
I: Connecting to 'Beken 72xx' on /dev/ttyUSB0 @ 115200
D: Linking: stage 0
W: Unknown bootloader CRC - 0x2739019F - please report this on GitHub issues!
D: Reading 4k page at 0x011000 (0.00%)
D: BK72xx connected - protocol: BASIC_BEKEN, chip: None, bootloader: None, chip ID: None, boot version: None
D: Flash size - detecting...
D:  - Checking wraparound at 0x211000
D: Flash size detected - 0x200000
I: |-- Success! Chip info: Unknown
I: Reading chip info...
I: Chip: Unknown
I: +-----------------------+--------------+
I: | Name                  | Value        |
I: +-----------------------+--------------+
I: | Protocol Type         | BASIC_BEKEN  |
I: | Chip Type             | Unrecognized |
I: | Bootloader Type       | Unrecognized |
I: | Chip ID               | N/A          |
I: | Boot Version String   | N/A          |
I: |                       |              |
I: | Flash Size (detected) | 2 MiB        |
I: +-----------------------+--------------+
I: |-- Finished in 1.953 s

Thanks

Hi, we are aware of the clone chips. It seems they come with a variety of different bootloaders too.
Can you share the firmware you retrieved from the chip?
Does your device print anything on the UART logs? We would like to confirm the behaviour of these things.
Also, do note that neither ESPHome (LibreTiny) nor OpenBeken currently support the CC8000. Flashing the firmware will not make it boot, if it even succeeds at all.

Thanks! I am aware that neither of the firmwares work on the device.
Attached the cc8000 flash backup. The chip is installed in a bulb which works with the AiDot software. I don't have UART logs, but it general the UART logging is very limited on this firmware.  Here are some pictures of the modul: https://www.elektroda.com/rtvforum/viewtopic.php?p=21025914#21025914
cc8000.zip

Just curious, how did you read the firmware from the device? I see OpenBeken's flasher tool doesn't work, and I've heard that bk7231tools/ltchiptool had some issues as well.

Just curious, how did you read the firmware from the device? I see OpenBeken's flasher tool doesn't work, and I've heard that bk7231tools/ltchiptool had some issues as well.

ltchiptool CLI worked for me. The GUI on Ubuntu had issues as it crashed during the download
ltchiptool flash read bk72xx ./cc8000.bin
I: Available COM ports:
I: |-- ttyUSB0 - CP2102 USB to UART Bridge Controller - CP2102 USB to UART Bridge Controller - Silicon Labs (10C4/EA60)
I: |   |-- Selecting this port. To override, use -d/--device
I: |-- ttyS0 - ttyS0
I: Connecting to 'Beken 72xx' on /dev/ttyUSB0 @ 115200
W: Unknown bootloader CRC - 0x2739019F - please report this on GitHub issues!
I: |-- Success! Chip info: Unknown
I: Reading Flash (2 MiB) to './cc8000.bin'
  [################################################################]  100%
I: |-- Finished in 188.672 s

Great. Writing will not work unless you use the latest version of bk7231tools (development version, latest commit).
You can try booting ESPHome or your own code (like simple printf() in void setup()), maybe you'll get somewhere with this chip. I'm waiting for mine to arrive.

Great. Writing will not work unless you use the latest version of bk7231tools (development version, latest commit).
You can try booting ESPHome or your own code (like simple printf() in void setup()), maybe you'll get somewhere with this chip. I'm waiting for mine to arrive.

Thanks, i will not try to flash this board. as it is still usable with the bulb. I may order a separate single board with cc8000 to experiment :)

Chats about the HLK-B30:
https://discord.com/channels/967863521511608370/1229825856491491441

Chats about the HLK-B30:
https://discord.com/channels/967863521511608370/1229825856491491441

Discord link leads "NO TEXT CHANNELS" message

Oh. It's the dev board thread in the LibreTiny dumps channel on Discord


Doesn't generate field information

I have a model generated by Sequelize with the following information:
module.exports = (sequelize, DataTypes) => {
  const user = sequelize.define('test', {
    firstName: DataTypes.STRING,
    lastName: DataTypes.STRING,
    email: DataTypes.STRING,
    testField: DataTypes.STRING,
    anotherTest: DataTypes.STRING
  }, {});
  user.associate = function(models) {
    // associations can be defined here
  };
  return user;
};

Running makemigration generates the following:
'use strict';

var Sequelize = require('sequelize');

/**
 * Actions summary:
 *
 * createTable "users", deps: []
 *
 **/

var info = {
    "revision": 1,
    "name": "user",
    "created": "2019-10-20T04:47:04.496Z",
    "comment": ""
};

var migrationCommands = [{
    fn: "createTable",
    params: [
        "users",
        {

        },
        {}
    ]
}];

module.exports = {
    pos: 0,
    up: function(queryInterface, Sequelize)
    {
        var index = this.pos;
        return new Promise(function(resolve, reject) {
            function next() {
                if (index < migrationCommands.length)
                {
                    let command = migrationCommands[index];
                    console.log("[#"+index+"] execute: " + command.fn);
                    index++;
                    queryInterface[command.fn].apply(queryInterface, command.params).then(next, reject);
                }
                else
                    resolve();
            }
            next();
        });
    },
    info: info
};

Doesn't look like there is any code related to the fields. Running runmigration confirms this since it only creates the table with no fields in it.
Is it something I'm just doing wrong?

Same problem. Only table generated, no columns.

This is still a problem

if you can check, please check my pull request that fixes this specific issue, it is just that sequelize 5.x changed some attributes

@flexxnn please include @moda20 's PR, we are stuck in Sequelize 4.x

@moda20 I have issue with your fix. I changed property path to models in makemigration.js and it's worked.
#73

@moda20 I had an issue with your fix. I changed property path to models and it's worked fine with autogenerated models/index.js
#73

If you faced this problem you can download my fork fixing this issue.
https://github.com/Naddyson/sequelize-auto-migrations

This repo is dead and not being maintained anymore.
Head over to https://github.com/MRVMV/sequelize-mig fork which is being actively maintained.