Android build issue with Gradle 8.0.1 and react native 0.72.1

Environment

Platforms

Versions

Android:13 33 sdk
iOS: 14
react-native-netinfo:9.4.1
"react": "18.2.0",
"react-native": "0.72.1"

Description
Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':react-native-community_netinfo:copyDebugJniLibsProjectAndLocalJars' (type 'LibraryJniLibsTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/intermediates/stripped_native_libs/debug/out'.
Reason: Task ':react-native-community_netinfo:copyDebugJniLibsProjectAndLocalJars' uses this output of task ':@react-native-community_netinfo:stripDebugDebugSymbols' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:stripDebugDebugSymbols' as an input of ':react-native-community_netinfo:copyDebugJniLibsProjectAndLocalJars'.
Declare an explicit dependency on ':@react-native-community_netinfo:stripDebugDebugSymbols' from ':react-native-community_netinfo:copyDebugJniLibsProjectAndLocalJars' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:stripDebugDebugSymbols' from ':react-native-community_netinfo:copyDebugJniLibsProjectAndLocalJars' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':react-native-community_netinfo:packageDebugResources' (type 'MergeResources').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/rs/debug'.
Reason: Task ':react-native-community_netinfo:packageDebugResources' uses this output of task ':@react-native-community_netinfo:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:compileDebugRenderscript' as an input of ':react-native-community_netinfo:packageDebugResources'.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/resValues/debug'.
Reason: Task ':react-native-community_netinfo:packageDebugResources' uses this output of task ':@react-native-community_netinfo:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:generateDebugResValues' as an input of ':react-native-community_netinfo:packageDebugResources'.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

3: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':react-native-community_netinfo:extractDeepLinksForAarDebug' (type 'ExtractDeepLinksTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/rs/debug/navigation'.
Reason: Task ':react-native-community_netinfo:extractDeepLinksForAarDebug' uses this output of task ':@react-native-community_netinfo:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:compileDebugRenderscript' as an input of ':react-native-community_netinfo:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/resValues/debug/navigation'.
Reason: Task ':react-native-community_netinfo:extractDeepLinksForAarDebug' uses this output of task ':@react-native-community_netinfo:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:generateDebugResValues' as an input of ':react-native-community_netinfo:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

4: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':react-native-community_netinfo:packageDebugAssets' (type 'MergeSourceSetFolders').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/intermediates/shader_assets/debug/out'.
Reason: Task ':react-native-community_netinfo:packageDebugAssets' uses this output of task ':@react-native-community_netinfo:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:compileDebugShaders' as an input of ':react-native-community_netinfo:packageDebugAssets'.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugShaders' from ':react-native-community_netinfo:packageDebugAssets' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugShaders' from ':react-native-community_netinfo:packageDebugAssets' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

5: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':react-native-community_netinfo:mergeDebugJavaResource' (type 'MergeJavaResourceTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/intermediates/java_res/debug/out'.
Reason: Task ':react-native-community_netinfo:mergeDebugJavaResource' uses this output of task ':@react-native-community_netinfo:processDebugJavaRes' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:processDebugJavaRes' as an input of ':react-native-community_netinfo:mergeDebugJavaResource'.
Declare an explicit dependency on ':@react-native-community_netinfo:processDebugJavaRes' from ':react-native-community_netinfo:mergeDebugJavaResource' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:processDebugJavaRes' from ':react-native-community_netinfo:mergeDebugJavaResource' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

6: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':@react-native-community_netinfo:bundleDebugAar' (type 'BundleAar').

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':@react-native-community_netinfo:bundleDebugAar' uses this output of task ':react-native-community_netinfo:processDebugManifest' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-community_netinfo:processDebugManifest' as an input of ':@react-native-community_netinfo:bundleDebugAar'.
Declare an explicit dependency on ':react-native-community_netinfo:processDebugManifest' from ':@react-native-community_netinfo:bundleDebugAar' using Task#dependsOn.
Declare an explicit dependency on ':react-native-community_netinfo:processDebugManifest' from ':@react-native-community_netinfo:bundleDebugAar' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':@react-native-community_netinfo:bundleDebugAar' uses this output of task ':react-native-community_netinfo:packageDebugResources' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-community_netinfo:packageDebugResources' as an input of ':@react-native-community_netinfo:bundleDebugAar'.
Declare an explicit dependency on ':react-native-community_netinfo:packageDebugResources' from ':@react-native-community_netinfo:bundleDebugAar' using Task#dependsOn.
Declare an explicit dependency on ':react-native-community_netinfo:packageDebugResources' from ':@react-native-community_netinfo:bundleDebugAar' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':@react-native-community_netinfo:bundleDebugAar' uses this output of task ':react-native-community_netinfo:extractDeepLinksForAarDebug' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-community_netinfo:extractDeepLinksForAarDebug' as an input of ':@react-native-community_netinfo:bundleDebugAar'.
Declare an explicit dependency on ':react-native-community_netinfo:extractDeepLinksForAarDebug' from ':@react-native-community_netinfo:bundleDebugAar' using Task#dependsOn.
Declare an explicit dependency on ':react-native-community_netinfo:extractDeepLinksForAarDebug' from ':@react-native-community_netinfo:bundleDebugAar' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':@react-native-community_netinfo:bundleDebugAar' uses this output of task ':react-native-community_netinfo:prepareLintJarForPublish' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-community_netinfo:prepareLintJarForPublish' as an input of ':@react-native-community_netinfo:bundleDebugAar'.
Declare an explicit dependency on ':react-native-community_netinfo:prepareLintJarForPublish' from ':@react-native-community_netinfo:bundleDebugAar' using Task#dependsOn.
Declare an explicit dependency on ':react-native-community_netinfo:prepareLintJarForPublish' from ':@react-native-community_netinfo:bundleDebugAar' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':@react-native-community_netinfo:bundleDebugAar' uses this output of task ':react-native-community_netinfo:prepareDebugArtProfile' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-community_netinfo:prepareDebugArtProfile' as an input of ':@react-native-community_netinfo:bundleDebugAar'.
Declare an explicit dependency on ':react-native-community_netinfo:prepareDebugArtProfile' from ':@react-native-community_netinfo:bundleDebugAar' using Task#dependsOn.
Declare an explicit dependency on ':react-native-community_netinfo:prepareDebugArtProfile' from ':@react-native-community_netinfo:bundleDebugAar' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

7: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':luu-truong_react-native-pdf:packageDebugResources' (type 'MergeResources').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/rs/debug'.
Reason: Task ':luu-truong_react-native-pdf:packageDebugResources' uses this output of task ':react-native-pdf:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:compileDebugRenderscript' as an input of ':luu-truong_react-native-pdf:packageDebugResources'.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/resValues/debug'.
Reason: Task ':luu-truong_react-native-pdf:packageDebugResources' uses this output of task ':react-native-pdf:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:generateDebugResValues' as an input of ':luu-truong_react-native-pdf:packageDebugResources'.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

8: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':luu-truong_react-native-pdf:extractDeepLinksDebug' (type 'ExtractDeepLinksTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/rs/debug/navigation'.
Reason: Task ':luu-truong_react-native-pdf:extractDeepLinksDebug' uses this output of task ':react-native-pdf:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:compileDebugRenderscript' as an input of ':luu-truong_react-native-pdf:extractDeepLinksDebug'.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:extractDeepLinksDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:extractDeepLinksDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/resValues/debug/navigation'.
Reason: Task ':luu-truong_react-native-pdf:extractDeepLinksDebug' uses this output of task ':react-native-pdf:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:generateDebugResValues' as an input of ':luu-truong_react-native-pdf:extractDeepLinksDebug'.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:extractDeepLinksDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:extractDeepLinksDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

9: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':react-native-community_netinfo:extractDeepLinksDebug' (type 'ExtractDeepLinksTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/rs/debug/navigation'.
Reason: Task ':react-native-community_netinfo:extractDeepLinksDebug' uses this output of task ':@react-native-community_netinfo:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:compileDebugRenderscript' as an input of ':react-native-community_netinfo:extractDeepLinksDebug'.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:extractDeepLinksDebug' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:compileDebugRenderscript' from ':react-native-community_netinfo:extractDeepLinksDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/generated/res/resValues/debug/navigation'.
Reason: Task ':react-native-community_netinfo:extractDeepLinksDebug' uses this output of task ':@react-native-community_netinfo:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:generateDebugResValues' as an input of ':react-native-community_netinfo:extractDeepLinksDebug'.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:extractDeepLinksDebug' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:generateDebugResValues' from ':react-native-community_netinfo:extractDeepLinksDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

10: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':luu-truong_react-native-pdf:packageDebugAssets' (type 'MergeSourceSetFolders').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/intermediates/shader_assets/debug/out'.
Reason: Task ':luu-truong_react-native-pdf:packageDebugAssets' uses this output of task ':react-native-pdf:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:compileDebugShaders' as an input of ':luu-truong_react-native-pdf:packageDebugAssets'.
Declare an explicit dependency on ':react-native-pdf:compileDebugShaders' from ':luu-truong_react-native-pdf:packageDebugAssets' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:compileDebugShaders' from ':luu-truong_react-native-pdf:packageDebugAssets' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

11: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':luu-truong_react-native-pdf:copyDebugJniLibsProjectOnly' (type 'LibraryJniLibsTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/intermediates/merged_native_libs/debug/out'.
Reason: Task ':luu-truong_react-native-pdf:copyDebugJniLibsProjectOnly' uses this output of task ':react-native-pdf:mergeDebugNativeLibs' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:mergeDebugNativeLibs' as an input of ':luu-truong_react-native-pdf:copyDebugJniLibsProjectOnly'.
Declare an explicit dependency on ':react-native-pdf:mergeDebugNativeLibs' from ':luu-truong_react-native-pdf:copyDebugJniLibsProjectOnly' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:mergeDebugNativeLibs' from ':luu-truong_react-native-pdf:copyDebugJniLibsProjectOnly' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

12: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':react-native-community_netinfo:copyDebugJniLibsProjectOnly' (type 'LibraryJniLibsTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-community/netinfo/android/build/intermediates/merged_native_libs/debug/out'.
Reason: Task ':react-native-community_netinfo:copyDebugJniLibsProjectOnly' uses this output of task ':@react-native-community_netinfo:mergeDebugNativeLibs' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:mergeDebugNativeLibs' as an input of ':react-native-community_netinfo:copyDebugJniLibsProjectOnly'.
Declare an explicit dependency on ':@react-native-community_netinfo:mergeDebugNativeLibs' from ':react-native-community_netinfo:copyDebugJniLibsProjectOnly' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:mergeDebugNativeLibs' from ':react-native-community_netinfo:copyDebugJniLibsProjectOnly' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

13: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':@react-native-async-storage_async-storage:copyDebugJniLibsProjectAndLocalJars' (type 'LibraryJniLibsTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/intermediates/stripped_native_libs/debug/out'.
Reason: Task ':@react-native-async-storage_async-storage:copyDebugJniLibsProjectAndLocalJars' uses this output of task ':react-native-async-storage_async-storage:stripDebugDebugSymbols' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:stripDebugDebugSymbols' as an input of ':@react-native-async-storage_async-storage:copyDebugJniLibsProjectAndLocalJars'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:stripDebugDebugSymbols' from ':@react-native-async-storage_async-storage:copyDebugJniLibsProjectAndLocalJars' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:stripDebugDebugSymbols' from ':@react-native-async-storage_async-storage:copyDebugJniLibsProjectAndLocalJars' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

14: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':@react-native-async-storage_async-storage:packageDebugResources' (type 'MergeResources').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/generated/res/rs/debug'.
Reason: Task ':@react-native-async-storage_async-storage:packageDebugResources' uses this output of task ':react-native-async-storage_async-storage:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:compileDebugRenderscript' as an input of ':@react-native-async-storage_async-storage:packageDebugResources'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugRenderscript' from ':@react-native-async-storage_async-storage:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugRenderscript' from ':@react-native-async-storage_async-storage:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/generated/res/resValues/debug'.
Reason: Task ':@react-native-async-storage_async-storage:packageDebugResources' uses this output of task ':react-native-async-storage_async-storage:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:generateDebugResValues' as an input of ':@react-native-async-storage_async-storage:packageDebugResources'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:generateDebugResValues' from ':@react-native-async-storage_async-storage:packageDebugResources' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:generateDebugResValues' from ':@react-native-async-storage_async-storage:packageDebugResources' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

15: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' (type 'ExtractDeepLinksTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/generated/res/rs/debug/navigation'.
Reason: Task ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' uses this output of task ':react-native-async-storage_async-storage:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:compileDebugRenderscript' as an input of ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugRenderscript' from ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugRenderscript' from ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/generated/res/resValues/debug/navigation'.
Reason: Task ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' uses this output of task ':react-native-async-storage_async-storage:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:generateDebugResValues' as an input of ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:generateDebugResValues' from ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:generateDebugResValues' from ':@react-native-async-storage_async-storage:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

16: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':@react-native-async-storage_async-storage:packageDebugAssets' (type 'MergeSourceSetFolders').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/intermediates/shader_assets/debug/out'.
Reason: Task ':@react-native-async-storage_async-storage:packageDebugAssets' uses this output of task ':react-native-async-storage_async-storage:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:compileDebugShaders' as an input of ':@react-native-async-storage_async-storage:packageDebugAssets'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugShaders' from ':@react-native-async-storage_async-storage:packageDebugAssets' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:compileDebugShaders' from ':@react-native-async-storage_async-storage:packageDebugAssets' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

17: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':@react-native-async-storage_async-storage:mergeDebugJavaResource' (type 'MergeJavaResourceTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@react-native-async-storage/async-storage/android/build/intermediates/java_res/debug/out'.
Reason: Task ':@react-native-async-storage_async-storage:mergeDebugJavaResource' uses this output of task ':react-native-async-storage_async-storage:processDebugJavaRes' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-async-storage_async-storage:processDebugJavaRes' as an input of ':@react-native-async-storage_async-storage:mergeDebugJavaResource'.
Declare an explicit dependency on ':react-native-async-storage_async-storage:processDebugJavaRes' from ':@react-native-async-storage_async-storage:mergeDebugJavaResource' using Task#dependsOn.
Declare an explicit dependency on ':react-native-async-storage_async-storage:processDebugJavaRes' from ':@react-native-async-storage_async-storage:mergeDebugJavaResource' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

18: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':luu-truong_react-native-pdf:copyDebugJniLibsProjectAndLocalJars' (type 'LibraryJniLibsTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/intermediates/stripped_native_libs/debug/out'.
Reason: Task ':luu-truong_react-native-pdf:copyDebugJniLibsProjectAndLocalJars' uses this output of task ':react-native-pdf:stripDebugDebugSymbols' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:stripDebugDebugSymbols' as an input of ':luu-truong_react-native-pdf:copyDebugJniLibsProjectAndLocalJars'.
Declare an explicit dependency on ':react-native-pdf:stripDebugDebugSymbols' from ':luu-truong_react-native-pdf:copyDebugJniLibsProjectAndLocalJars' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:stripDebugDebugSymbols' from ':luu-truong_react-native-pdf:copyDebugJniLibsProjectAndLocalJars' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

19: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' (type 'ExtractDeepLinksTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/rs/debug/navigation'.
Reason: Task ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' uses this output of task ':react-native-pdf:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:compileDebugRenderscript' as an input of ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:compileDebugRenderscript' from ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/generated/res/resValues/debug/navigation'.
Reason: Task ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' uses this output of task ':react-native-pdf:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:generateDebugResValues' as an input of ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug'.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:generateDebugResValues' from ':luu-truong_react-native-pdf:extractDeepLinksForAarDebug' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

20: Task failed with an exception.

What went wrong:
A problem was found with the configuration of task ':luu-truong_react-native-pdf:mergeDebugJavaResource' (type 'MergeJavaResourceTask').

Gradle detected a problem with the following location: '/Users/ganeshchalumuri/Documents/Archents/AcianaDocisnV2/node_modules/@luu-truong/react-native-pdf/android/build/intermediates/java_res/debug/out'.
Reason: Task ':luu-truong_react-native-pdf:mergeDebugJavaResource' uses this output of task ':react-native-pdf:processDebugJavaRes' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:processDebugJavaRes' as an input of ':luu-truong_react-native-pdf:mergeDebugJavaResource'.
Declare an explicit dependency on ':react-native-pdf:processDebugJavaRes' from ':luu-truong_react-native-pdf:mergeDebugJavaResource' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:processDebugJavaRes' from ':luu-truong_react-native-pdf:mergeDebugJavaResource' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

21: Task failed with an exception.

What went wrong:
Some problems were found with the configuration of task ':app:checkDevAarMetadata' (type 'CheckAarMetadataTask').

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':app:checkDevAarMetadata' uses this output of task ':react-native-pdf:writeDebugAarMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':react-native-pdf:writeDebugAarMetadata' as an input of ':app:checkDevAarMetadata'.
Declare an explicit dependency on ':react-native-pdf:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#dependsOn.
Declare an explicit dependency on ':react-native-pdf:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':app:checkDevAarMetadata' uses this output of task ':@react-native-async-storage_async-storage:writeDebugAarMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-async-storage_async-storage:writeDebugAarMetadata' as an input of ':app:checkDevAarMetadata'.
Declare an explicit dependency on ':@react-native-async-storage_async-storage:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-async-storage_async-storage:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Gradle detected a problem with the following location<EMAIL_ADDRESS>Reason: Task ':app:checkDevAarMetadata' uses this output of task ':@react-native-community_netinfo:writeDebugAarMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:

Declare task ':@react-native-community_netinfo:writeDebugAarMetadata' as an input of ':app:checkDevAarMetadata'.
Declare an explicit dependency on ':@react-native-community_netinfo:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#dependsOn.
Declare an explicit dependency on ':@react-native-community_netinfo:writeDebugAarMetadata' from ':app:checkDevAarMetadata' using Task#mustRunAfter.

Please refer to https://docs.gradle.org/8.0.1/userguide/validation_problems.html#implicit_dependency for more details about this problem

If libraries that cause these errors are listed in android/app/build.gradle in dependencies - remove them.
I've had to remove just this one:
dependencies {
...
//  implementation project(':@react-native-community_netinfo')
...
}

@chganesh have same issue, did you manage to solve it?

@philly25 Was on to something in my case, but I also needed to update settings.gradle. I added netinfo way back when autolinking wasn't a thing so I had:
android/app/build.gradle
dependencies {
  ...
  implementation project(":react-native-community/netinfo")
  ...
}

android/settings.gradle
...
include ":react-native-community-netinfo"
project(":react-native-community-netinfo").projectDir = new File(rootProject.projectDir, "../node_modules/@react-native-community/netinfo/android")
...

Previously gradlew/Android building didn't give an error on that, but after upgrading to Gradle 8.0.1 with RN 0.72.x it started doing so.
Simply removing the mentioned lines in both files (thus relying on autolinking) resolved the issue. I also had to do the same for other packages (like @react-native-async-storage) I added before autolinking.


Display detailed upload progress in notification

It was intended from the start to have detailed upload progress notifications for individual files.

bytes sent / bytes total
moving average bitrate
moving average ETA

There are 2 major blockers to enabling this.
The first thing that needs to be solved is this issue in the Java SDK. filestack/filestack-java#51 The base SDK was supposed to provide the necessary progress updates for this, as a stream of progress objects from the upload observable, but that isn't working. And looking at the code now, I did not understand how parallelism was working in RX. So that all needs to be sorted out but I think the idea of the RX interface is fine, it's just not straightforward to have RX be parallel. (I still might be really lacking in RX understanding here.)
The other thing is that the UploadService needs some work. The IntentService won't work with non-blocking code. If we subscribe to an observable for the upload, we won't be blocking, and the service would just quit. So instead of an IntentService we need a base Service or maybe something else. And more recent versions of Android have introduced tougher restrictions to prevent battery draining (there's now a job scheduling system, JobIntentService, other things I've skimmed in press releases) so we should conform to that.

Hi shawnmaten,
Is there any update related to progress percent while uploading file. We need this to include in our project to show progress to the user while uploading.

Added to internal tracker: https://filestack.atlassian.net/browse/FS-3356

Is there any new progress on this issue?

is there any progress @shawnmaten?

Hey just a heads up @mhswtf and @mtariquekhan I no longer work at Filestack so I wouldn't know about any internal progress on this. You might try mentioning the most recent committer or sending an inquiry through Support.


Refactor task widget

Converted the global show signal into proper methods, show/toggle/hide
No enable function, calling bling.widget.task_widget will return an object with the above methods
Added the abillity to position the widget differently each time that it is showed. This with the change listed below allows it to align to the currently hovered task widget instead of having a static positon.
Added the option to provide a wibox, widget and offset arguements to the show method, allowing to the align the task preview to another widget (possibly the hovered task widget).
This is done by the following code:

task_preview:show(client, {wibox = awful.screen.focused().wibar, widget = task_widget, offset = { y = 100}})

Minor changes:

Removed the _fn from the placement arguement to keep it consistent with other awesome wiboxes
Removed the 'widget' prefix from the arguement provided to the object.

Those 2 aren't that important and can be undone though.

User Feedback, easy to configure, works like a charm with custom widgets (i have wrapped the tasklist multiple times in containers, position can still be accuratly found, awesome!) :+1:
https://user-images.githubusercontent.com/2059141/144948685-cc31a172-5526-4885-a0fc-e34aa6ef55d7.mp4

@Kasper24 Looks good! I still have no Linux machine (laptop will come in a few days), so once I get it I'll test your PR and give it the thumbs up. Or, we can have @Nooo37 test it as well and merge.

@Kasper24 Works fine for me, just needs docs.

Merged into #99


Update Threadmarks when moving posts between threads.

If you move a post with a threadmark between threads, the state in the threadmark table isn't updated.

PR #17 attempts to address this, requires more work

Fixed by #17


Update NextJS to v7

Implicit react imports lead to an issue with babel-plugin-inline-react-svg
See https://github.com/airbnb/babel-plugin-inline-react-svg/issues/50

Fixed, it was due to using this.props in a <style jsx> tag (this was undefined).
It seems to be impossible with styled-jsx v3 used by Nextv7.


Pose Estimation Using DANNCE

In the paper on DANNCE, specific poses are able to be identified. However, I do not see any information regarding poses in any of the files generated for the DANNCE demo. Could you give me instructions on how to generate and interpret rodent poses using DANNCE?

Hello, thank you for interest in our tools!
The poses can be embedded and clustered using the code from https://github.com/jessedmarshall/CAPTURE_demo. There should be an option to selected "kyle_mouse" as an skeleton type, which will be compatible with the demo data. Embedding and clustering will work best if you predict over at least 30 minutes of video. @jessedmarshall might also have some other tips. And if you have more specific questions about the CAPTURE_demo code, we are happy to help.


Additional declarative per-resource configuration?

Hi there @daliwali :wave:
I'm reading through the guides, and I'm wondering if there's a declarative way to get these features on a per-resource basis:

non-nullable fields
createdAt meta attributes
updatedAt meta attributes
per-resource allowed HTTP methods

From the guides, it seems like the way to do this right now would be imperatively using the input hooks, and keeping all of this logic on the JS side, rather than the DB side. Is that the recommended approach?
Thanks!

I left most of that out intentionally.

this is database dependent, if you're using a relational database it should be declared but otherwise not, I left it out since I don't think it should be handled declaratively for all databases.
2, 3. this is trivial to do via the input hook, I don't understand why this needs to be special-cased.
the prototype 0.x versions had this, it was later removed after 1.0 since they tended to couple the app to the network protocol, and it was a deliberate decision to keep them as separate as possible.

this is a good idea to add this to the docs.

The motivation is to keep it as a general purpose library without assuming any specific use cases. Trying to anticipate specific use cases is always going to lead to bloat and unnecessary API. I am optimistic that programmers can figure out things on their own.
For example, the last point could be handled entirely on the application side:
var originalRequest = store.request

store.request = function (options) {
  var type = options.type
  var method = options.method

  if (method === 'delete' && type === 'payment')
    return Promise.reject(new BadRequestError('Payments may not be deleted.'))

  return originalRequest.call(this, options)
}

Thanks @daliwali ! All of this makes sense.
I'm going to close this issue out, and I'll be sure to add these common use cases to the examples I'll be working on shortly.


Update changed_attributes to attributes_in_database

This PR addresses:
https://github.com/elastic/elasticsearch-rails/issues/714
Basically changed_attributes has been deprecated in Rails 5.1.  This PR hopefully addresses that.  Please let me know if I missed anything.

Can we get this merged?

Hi @jkeam, please accept my apologies for not attending to this patch soon enough.
I've spent some time with the problem, working both through your and @Geesu's patches, and finally merged the solution. My original code using the changed_attributes was quite misleading. I've corrected it in 7815039, and also restored the compatibility with older Rails versions.
Can you please evaluate current master or 5.x branch if it solves your problem? (I've also released a new version to Rubygems.)

Just tested against the 5.x branch and everything looks good!  Thanks again @karmi and everyone else who helped on this.

Thank you for the info, @jkeam, and sorry again for such a long delay!


Updated with GOOJPRT PT-210

Added a printer I've recently tested with - great lib. Thanks.

Arabic or Turkish(ışçüğ) characters not working. I am not sure the problem is specific with this printer, I don't have any other printer to test.


The response should contain all the keys if there was not packaging yet

Task linked: DEV-3351 Fix feedback of GET /project/qfield-files/<id> when there was no packaging yet


can your st support BiDi

hi
it is possible to add  BiDirectional text support into st ?
for now bellow text show as separate alphabet in st
نوشتار فارسی
show somethings like this

No, there is no patch for this.


Recent scons update breaks build

Several from Scons.··· import * broke and need to be replaced. Also need to check direct copy of platform tools from godot-cpp: tools/build/platform

Fixed with 3eb39bd


Enable nonpersisting stub methods

This closes https://github.com/thoughtbot/factory_bot/issues/996, https://github.com/thoughtbot/factory_bot/pull/997
Overview
As described in #996, there are methods such as increment/decrement that do not persist but are disabled in FactoryBot. Going through the issues, I saw #997 fixed the issue with increment/decrement, but toggle seemed like another reasonable method to enable, so I thought of fixing toggle` myself.
It turns out after the fact that toggle was also addressed in #997. So what I did for this PR is the following:

Cherry-pick @michaelkoper's commits from #997
Update the spec test to cover the newly enabled methods

increment
decrement
toggle

I find this a clear change and the reasons behind it are explained well in this PR's description. Can this be merged?

I would love this to be merged. Please let me know if I can do anything to help this PR to move forward.

Thanks all! I squashed the commits, made one small change (is_draft -> draft) and merged as 3db8a12.
Sorry this took a while. I'm going to try to stay on top of the issues and PRs going forward.


Syntax extension: Referencing slots from UC flows

Can we allow referencing slots from UCs, so that it will be clear that we are working witn an object that is a part of another object?
For example, now we should write something like:
UC1 where User (a user) goes through repository life cycle:
...
    4. The user registers Repository(a repo);
    5. The system runs using Deployment(a deployment);

In flow 5 here I create a deployment object, and it is not clear that it actually continues the flow 4. To clarify that, I would like to say something like:
    4. The user registers Repository(a repo);
    5. The system runs using the repo.deployment;

Repository needs:
    deployment-? as Deployment,
    ...

Maybe even instantiate slots  this way:
    5. The system creates a repo.Deployment;

I am not saying it must look exactly like this, just sketching my idea of using slots references. So, the actual syntax may look different.
Slots are not very useful if they cannot be referenced from UCs. They only define object model of requirements, which is very good, however, they would a be much more powerful tool in defining consistent SRSs if they could be referenced from use case workflows.

@davvd assign someone else pls

@davvd assign someone else pls

@yegor256 OK, I will try to assign someone else

@davvd assign someone else pls

@yegor256 -30 points to your rating


Support subid for message subscription

Before this commit, message subscriptions are purely type-based,
but sometimes the subscriptions have to be determined by runtime
information (e.g., reading from config files). That is why we introduce
channel sub-ID.

Unit tests are still working-in-progress. We need more test cases for multi-subid.

Updated unit tests


Error during inference

File "waveglow/glow.py", line 212, in forward
spect, audio = forward_input
ValueError: not enough values to unpack (expected 2, got 1)

I have the same problem, did you solve this problem?

@ajaysg


"No object named 'VideoTestVimeo90KDataset' found in 'dataset' registry!"

Traceback (most recent call last):
File "basicsr/test.py", line 46, in
test_pipeline(root_path)
File "basicsr/test.py", line 29, in test_pipeline
test_set = build_dataset(dataset_opt)
File "/home/xxx/code/code2105/BasicSR/basicsr/data/init.py", line 34, in build_dataset
dataset = DATASET_REGISTRY.get(dataset_opt['type'])(dataset_opt)
File "/home/xxx/code/code2105/BasicSR/basicsr/utils/registry.py", line 65, in get
raise KeyError(f"No object named '{name}' found in '{self._name}' registry!")
KeyError: "No object named 'VideoTestVimeo90KDataset' found in 'dataset' registry!"

version：1.3.3

@JoshonSmith
Thanks for reporting the bug.
I have a quick, please check whether it has been solved. (Please use the latest master branch)
If the problem has been solved, please help to close this issue.
If you still have a problem, please let me know. Thanks : )

Thanks !
It has been solved

@xinntao Hello, I have also encountered this issue in other projects. How did you solve it? thanks


Error report: Expected "#", ":", "\n", "\r", or [ \t] but "s" found.

OS Version: linux 5.9.1-1-default
Notable Version: v1.8.4

SyntaxError: Expected "#", ":", "\n", "\r", or [ \t] but "s" found.
    at peg$buildStructuredError (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:17119)
    at Object.peg$parse [as parse] (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:31526)
    at Function.cson2json [as default] (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:11347)
    at BoostnoteProvider.getNotesRaw (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:10004)
    at BoostnoteProvider.dump (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:3430)
    at async Object.dump (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/chunk.801f2cae377ea1944a34.js:2:201681)
    at async import_Import.import (file:///tmp/.mount_NotablmRRhdm/resources/app.asar/renderer/renderer.js:2:24287)

Interesting, it looks like you were either trying to import some malformed Boostnote notes, or more likely the parser we are using isn't parsing some things correctly 🤔 I'll have to take a closer look at that.


hidden files and folder when in .gitignore

in a recent update the plugin systematicaly hidde files and folders when they are in .gitignore
i have some portions of the code i don't want to publish on the repo but i need to edit them in the IDE
for now the only solution i've found is to disable the plugin
how can i set the plugin to not hide files and folders from projet view when they are ignored ?

sorry ive found the show/hide option on right click.
i close the issue


Support Join-group API request

Integrate with OpenAPI docs
Separate router to a independent module
Separate handlers

Amazing good job em


Can`t use with Cocoapods

Thanks to your nice library.
But cannot use with Cocoapods...
is it a temporary problem or not use with Cocoapods?

try pod repo update first and then pod install.


Update Blender.xml

Pull request for issue #58

This is great, no need to make an issue for pull requests, just specify everything in the pull.
Thank you for the contribution!


feat: impl time type

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Main changes:

Adds TimeType and Time value.
Adds vectors for time types such as TimeSecondVector etc.
Some kinds of stuff that conversation between gRPC, MySQL, JSON and time vectors etc.

Fixes #1885
Checklist

[ ]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

Is there a usecase/rational behind this type? It has a value range between 0 and 24 hours so it can hardly represent any absolute time. I think in most case we use this type as duration to stored data like latency. And maybe Duration is a more accurate name (also widely used in modern APIs).

Is there a usecase/rational behind this type? I think in most case we use this type as duration to stored data like latency. And maybe Duration is a more accurate name (also widely used in modern APIs).

Duration is a different type. The time is the time part of DateTime. MySQL uses Time type as an interval type too, but it's not in PostgreSQL etc. We'll support interval or duration type in #1952 .
We won't support this type directly in the time-series table, but to be compatible with arrow datatypes and make SQL such as select currrent_time(); working.

@v0y4g3r PTAL


[Release][Java] Maven version detection in verification script may not work

Describe the bug, including details regarding any error messages, version, and platform.
Maven may use escape sequence for mvn -v. So $(mvn -v | head -n 1 | awk '{print $3}') may have a escape sequence.
Here is an example case of this:
$ x="$(mvn -v | head -n 1 | awk '{print $3}')" ruby -e 'p ENV["x"]'
"3.8.7\e[m"

Component(s)
Java

Issue resolved by pull request 41281
https://github.com/apache/arrow/pull/41281


NOT READY TO MERGE: Standalone with dumptruck-web

Following on from trying sql.js, going to use dumptruck-web instead.

As is, it works on ScraperWiki as code in a tool. Next job is get dumptruck-web running locally now.


Windows installer shouldn't assume the install location

While I admire the simplicity of the installer, it also globs it onto the C drive without asking. My C drive is a very small SSD, and while Atom isn't exactly a huge program, I'd prefer to have it on my HDD.

Check out #4859, of which this could be considered a duplicate.
Essentially the Squirrel framework being used does not currently support custom locations. It's weird and undesirable, but there you go.
However, you can use the zip version to put the application in any location you wish, as long as you don't care too much about the bells and whistles the installer gives you (context menu entries etc).

Yeah, I'm going to close this as a duplicate.  You can open up an issue on Squirrel.Windows if you want.

@Jragonmiris Do you know about mklink /D? You can use this to put folders anywhere they want but have them still think that they're on the SSD. In this case, you can definitely put C:\Users\YOURNAME\AppData\Local\atom on the HDD then Symlink to it, and everything will work (even updates will be fine)


CI: migrate to github actions

Seems to fail: https://github.com/bilelmoussaoui/gdkx11/actions/runs/320607042

Indeed, I wonder if the CI was ever working on this crate though.

Part of https://github.com/gtk-rs/gdkx11/pull/5 now


Detecting HTTP status (or HTTP response timeout) in encodeTrailers handler

Title: Detecting HTTP status (or HTTP response timeout) in encodeTrailers handler
Description:
Hi folks, I wonder if there's a reliable way to simply detect HTTP response timeout in encodeTrailers handler function of HTTP filters.
The challenge here is that we may easily check timeout by examining http status from ResponseHeaderMap (the input argument for encodeHeaders), but in ResponseTrailerMap (the input argument for encodeTrailers), it is not the case. One idea is to use a has_timeout flag to indicate if a previous request was timed out. This flag is set in encodeHeaders and read in encodeTrailers. But there could be multiple responses, and a later response could overwrite the has_timeout flag before the response comes in encodeTrailers.
Using stream local data (i.e., encoder_callbacks_->streamInfo().filterState()->getDataMutable("key_name")) leads to hashmap lookup by string key, which is not very ideal.
I also considered encoder_callbacks_->streamInfo().setResponseFlag() and then query it in encodeTrailers. But I wasn't able to find out if the response flag will be override by envoy itself before it gets to encodeTrailers or even be overwritten by a later response header of the same stream (this is similar if using stream local data) before the encodeTrailers is called.
[optional Relevant Links:]
Context, I'm implementing a custom HTTP filter, which parses some specific tag in the HTTP response. The tag unfortunately could be in either header or trailers. If the response was considered timeout, any subsequent processing for this tag should be skipped.

I also considered encoder_callbacks_->streamInfo().setResponseFlag() and then query it in encodeTrailers. But I wasn't able to find out if the response flag will be override by envoy itself before it gets to encodeTrailers or even be overwritten by a later response header of the same stream (this is similar if using stream local data) before the encodeTrailers is called.

I just recently realized that a streamInfo is per-request or per-response metadata (Stream in HTTP/2 context). There's no way for it to be override by another response. The UpstreamRequestTimeout will be set in the StreamInfo's response flag if the a timer triggers. So the solution should be simple. Just to check encoder_callbacks_->streamInfo().hasResponseFlag() would be sufficient.
Feel free to close the issue if my understanding is correct.

I think this is right - a flag should be set to indicate an error and then the filter should receive the callback with the stream info that has it. This needs to be validated, as the ordering of these things is not always consistent.


Install

Install
If you have Go installed and configured (i.e. with $GOPATH/bin in your $PATH):
go install github.com/tomnomnom/assetfinder@latest

sudo  go install github.com/tomnomnom/assetfinder@latest

try this:
cd
nano .bashrc

append the following lines at the bottom:
export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH

CTRL+S
CTRL+X
Finally type following in terminal:
 source .bashrc

and you are done:)
try reinstalling the assetfinder


[Bug] Latest version Incompatible with Bedrockify Panorama

The newest version of the mod will give a weird visual bug with Bedorckify Panoramas. It was compatible with Older Versions

I don't think there's much I can do about this. That mod is making changes to the UI and there's no real way for Mod Menu to be able to expect or account for them.


CUDA out of memory.

Hi, thank you for this sharing. I tried to run your code on GTX1650Ti (4Go), but ran out of memory.
Is there any custom settings to try your code with limited memory ? I tried --light=True, but without success. Regards,

Thanks for this clear answer. Regards,


77087 mp name and party

MP name and party can be viewed and edited. Work remaining on the MP details school postcode

@MichaelDally fixing Cypress tests on a different branch


Does not work with ver5.6.0

It doesn't seem to work with the newer inkdrop versions.
ver 5.6.0

Hey,
it should work with Inkdrop v5.6.0. I'm currently using it with v5.6.2-beta.0.
Can you check for errors in the console?

More Info

Thank you.
I found the cause.
The cause was the official plugin [breaks].
I turned it off and it worked fine.

I'm glad to hear that you were able to fix the problem.
I'll see if I can support this plugin.


Checking for None instead of falsyness

Metadata API: Checking for None instead of falsyness for unrecognized_fields
Fixes #1937
Description of the changes being introduced by the pull request:
Initialization of unrecognized_fields acts surprisingly when the input
container is empty. Hence, We're checking for None instead of falsyness.
Signed-off-by: Abhisman Sarkar<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

21 of 21 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 98.354%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
1201

Relevant Lines:
1217

💛  - Coveralls

Agreed. That does look better. I'll make the changes

I had a formatting issue earlier but I resolved that. For some reason, the signing persists error even though I've added my signature.
Could you look into this, thanks.

Closing this pr and opening a new one for this issue.

Hi @abs007, usually there is no need to close/re-open pull requests, as long as you don't need to switch the branch of the PR. I recommend reading our git history guidelines. It has some information about how to rewrite the history in a given git branch.

Thanks for the info.
I unfortunately couldn't understand a part in the example provided for rebasing commits made by @awwad on Dec 6, 2018. The third paragraph "I've fixed this using git rebase -i ..."

Could you provide resources to understand this, thanks.

Could you provide resources to understand this, thanks.

Did you check out the resources about git rebase in the git history guide I shared with you above?

Don't worry too much about @awwad's comment, it is not supposed to be a general tutorial for git rebase.

Did you check out the resources about git rebase in the git history guide I shared with you above?

Haven't gone through that. Will do.


Remove misleading main attribute from package.json

The main attribute in a package.json file has only meaning for a node module but not for an application. We should remove the attribute to prevent confusion when users think they need to simply change this attribute if they have no server.js.
Same will be done for the Paketo sample as discussed with their community, see slack.

LGTM


[SPARK-36870][SQL] Introduce INTERNAL_ERROR error class

What changes were proposed in this pull request?
Adds the INTERNAL_ERROR error class and the isInternalError API to SparkThrowable.
Removes existing error classes that are internal-only and replaces them with INTERNAL_ERROR.
Why are the changes needed?
Makes it easy for end-users to diagnose whether an error is an internal error. If an end-user encounters an internal error, it should be reported immediately. This also limits the number of error classes, making it easy to audit. We do not need high-quality error messages for internal errors, as they should not be exposed to the end-user.
Does this PR introduce any user-facing change?
Yes; this changes the error class in master.
How was this patch tested?
Unit tests

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48181/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48181/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48181/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143669/

Test build #143682 has started for PR 34123 at commit bafa473.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48196/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48196/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48196/

Test build #143682 has finished for PR 34123 at commit bafa473.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143682/

Test build #143722 has started for PR 34123 at commit 4844d84.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48233/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48233/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48233/

Test build #143722 has finished for PR 34123 at commit 4844d84.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143722/

@HyukjinKwon, it looks like the Python tests are failing; do you know why?

I think it's just flakiness

retest this please

Test build #143749 has started for PR 34123 at commit 4844d84.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48260/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/48260/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/48260/

Test build #143749 has finished for PR 34123 at commit 4844d84.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143749/

Looks like it passed. Thanks @HyukjinKwon! Is this ready to merge?

Merged to master.


How to solve the flexible job shop problem with multiple slots machines?

Hello,
In our flexible job shop problem, there are machines with 5 slots. this means one machine of this kind can do 5 tasks one time at most and these tasks in one machine must start at the same time.
I learned the cumulative constraint, but I still don't know if the problem can be modeled by it.
Is there any method or examples?
Many thanks!

I am using CP_SAT solver.

CP_SAT solver

Do all the jobs have the same duration ?

Tasks processed by the multi slot machine have the same duration.
like the job shop problem, there are multi sub-tasks in a job.
For example, Machine M has 3 slots; job A has 3 tasks and the 1st task must be processed on Machine M; job B has 4 tasks and the 2nd task must be processed on M.  Machine M can process the two tasks (maybe more) in parallel and the two tasks which have the same duration must start at the same time.

Batch scheduling is a good question.
If you know that all parallel jobs with have 'periodic' start times, you can inflate time by adding 1 timestep around each batch, and add a fixed interval var filling each boundary on each machines.
This way, jobs must fall in the batchs.
If the possible start times cannot be deduced in advance, then you need to go the long road.
Create one Boolean for each pair of jobs. Make sure that this Boolean is equivalent to the jobs overlapping. Then having this Boolean forcing the start vars to be equal.
This can be simplified into:
For a pair of intervals t1 and t2
b => start(t1) == start(t2)
not(b) => or(t1_before_t2, t2_before_t1)
t1_before_t2 <=> end(t1) <= start(t2)  # Note the equivalence
t2_before_t1 <=> end(t2) <= start(t1)
I hope this helps.


教育论文怎么写？

ADD ISSUE DESCRIPTION HERE
Version: 1.75.0
Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/109.0.1518.78
Embedder: codespaces

教育论文怎么写？

什么是爱？

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

@deepak1556 Could you please close this issue? It is absolutely a spam. Thanks.


WebUtil, and UrbanDictionary

Search functionality for Urban Dictionary.
Also, a web utility that outputs the titiles of websites.
Files
urban.coffee
web.coffee

You added a ton of the default scripts from github/hubot, was that intentional?

I went ahead and merged this.  If you can open another PR with the comments removed, that'd be awesome.


[Docs] Add Playground page

Desired State
A new page on Docs should be created describing Meshery Playground

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

I want to work on this please assign me

Can I work on this, please?

Any update @tanbirali ? We've our weekly websites call today: please sound off if you're stuck anywhere:  Add it as an agenda item in meeting minutes

May I work on this issue?

@tanbirali I see no progress here, perhaps re-assign to @goldfishdolphin ?
@tanbirali  would you sound off with your updates on this, today, on websites call? : meeting minutes

@goldfishdolphin would like to take it up?

Sure @vishalvivekm

Sure @vishalvivekm

Thanks @goldfishdolphin 🚀
would be great if we get a glimpse of your progress on it on websites call. 😎
lemme know where I can help

you can look at this PR: https://github.com/layer5io/layer5/pull/4184 @goldfishdolphin

@vishalvivekm do we have any description/information to put on the docs. Also, where should we position the playground page on the docs?

@vishalvivekm do we have any description/information to put on the docs.

Please have a look: https://6452dbce4fa0fa0530746264--layer5.netlify.app/cloud-native-management/playground
also https://play.meshery.io is a great resource.
Feel free to present it your way and then feedback on websites call would surely be helpful.

Also, where should we position the playground page on the docs?

we'd want the playground to be in overview section, however, we can ask what others in the community think about it on websites call. @goldfishdolphin // @ayushthe1

@vishalvivekm I am extremely sorry for my negligence, I am actually busy with my semester exams
@goldfishdolphin go ahead and all the best

@vishalvivekm I have made the page https://github.com/goldfishdolphin/meshery/tree/playground-page .
But I am not satisfied with the content on the page. I am using it as a placeholder.
I think it needs to be formal.

@vishalvivekm I have made the page https://github.com/goldfishdolphin/meshery/tree/playground-page . But I am not satisfied with the content on the page. I am using it as a placeholder. I think it needs to be formal.

Sounds good @goldfishdolphin, let's talk more about it on websites call, only community can suggest us better ;).
I'll add this as agenda item.

One item worth capturing, not only in this forthcoming docs page, but also potentially in the FAQs on play.meshery.io is an explanation as to why there isn't a generic demo user account that everyone can simply use.
The answer to this lie in these consideration:

Multi-player, real-time collaboration is possible when each Playground user has their own account; having individual user accounts enables two or more people to use the collaboration features within the playground. (a link or further explanation of the collaboration features would be helpful).
having your own individual account means that designs that are created or persisted, and that your work is not lost from session to session.
having individual accounts encourages accountability within the Playground to the extent that named accounts dissuade bad actors from maliciously abusing the Playground, preventing them from hiding behind an anonymous, general-use user account.

@goldfishdolphin
Meshery Playground is a web-based interactive learning environment for service mesh. It provides a sandboxed environment to experiment with different service meshes and includes various tools, tutorials, and examples that help users learn about the features of different service meshes.
With Meshery Playground, you can:

Learn about the key concepts of Service Mesh
Explore multiple Service Mesh offerings in one place
Understand how each mesh handles common use cases

It allows users to interactively explore some service meshes like Istio, Linkerd, Consul Connect etc., without having to install them on their local machines. Users can create virtual services and deploy sample applications using these meshes and observe their behavior in real-time.
Meshery Playground also has pre-built scenarios that demonstrate how to implement specific use-cases such as traffic splitting or circuit breaking across multiple Service Meshes.

@thisiskaransgit I have replaced  the above 'With Meshery Playground, you can:' with

Collaborate with other engineers, share your knowledge, and exchange ideas
Explore new cloud native tools without the need for complex setup or configuration. Simply open your browser and go.
Design new cloud native scenarios and easily deploy them in the Playground environment. Keep your designs and deploy them in your own environment when you’re ready.


Rename sample catalog source for simplicity

What does this PR do?
Renames DWO catalogsource so it's more obvious how to use it when creating a subscription manually.
What issues does this PR fix or reference?
Nitpick
Is it tested? How?
N/A
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Good catch! Updated.

/test v8-devworkspace-operator-e2e, v8-che-happy-path

/retest


Added Vagrant

Not sure if you want to include this in the main repo, but I wrote a quick vagrant setup based on the hashicorp/precise64 box to get people up and running as fast as possible.

Added to wiki: https://github.com/Netflix/Scumblr/wiki/Running-with-Vagrant
Thanks for the contribution, sorry for the delay on getting this worked in.


Add an option to re-send verification emails

Is your feature request related to a problem?
Sometimes mails do fail to send or to be received.
Describe the solution you'd like.
Option to re-send verification emails.
Describe alternatives you've considered.
None.
Other
No response

you can attempt to resend once the old email expired.
do note that emails aren't being send right now because our email provider ratelimited us, we are working on resolving that.

(Fixed the button not appearing, but the provider still won't send emails atm)


Types that can can be "empty" in a HashMap disapear when empty

See PR #199 for more

this was fixed in #199


feat: add isSsrTargetWebWorker flag to configEnvironment hook

Description
This PR adds isSsrTargetWebWorker flag to configEnvironment hook so that plugins can support ssr.target: 'webworker' correctly.
For example, this configEnvironment hook from https://github.com/sveltejs/vite-plugin-svelte/pull/1020 needs to know if ssr.target: 'webworker' is set.
https://github.com/sveltejs/vite-plugin-svelte/blob/dcec9afa2a9b1bfd5fe8f0767cc871a2b144a9d6/packages/vite-plugin-svelte/src/index.js#L71-L81
https://discord.com/channels/804011606160703521/1304311237332697098/1304350474085859338

Talking about that, I wonder if svelte will end up doing a clean cut and require Vite 6 soon after we release

Dominik is fine with that for vite-plugin-svelte, but we'll likely have to align with sveltekit and the plan could change.


javalite.io is down

Sorry to post this here, but your site is down since several days...

fixed, the hosting provider restarted the OS. Weill add a monitoring service,


[frontend search] Allow conceptual search

Add query field for concept search:
use preferred term to identify a concept: think about an UI piece to realize this
use concept Id for the actual search (in the TEI sub-document)

moved to https://github.com/anHALytics/anHALytics-frontend/issues/1


Compilation error on macOS 13 (intel cpu)

I see the following error when running cargo install typst-live:
error[E0432]: unresolved import `notify::INotifyWatcher`
 --> /Users/valentin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/typst-live-0.2.0/src/watcher.rs:3:32
  |
3 | use notify::{Event, EventKind, INotifyWatcher, RecursiveMode, Watcher};
  |                                ^^^^^^^^^^^^^^ no `INotifyWatcher` in the root

error[E0282]: type annotations needed
  --> /Users/valentin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/typst-live-0.2.0/src/watcher.rs:50:5
   |
50 |     Ok(watcher)
   |     ^^ cannot infer type of the type parameter `E` declared on the enum `Result`
   |
help: consider specifying the generic arguments
   |
50 |     Ok::<FsEventWatcher, E>(watcher)
   |       +++++++++++++++++++++

Some errors have detailed explanations: E0282, E0432.
For more information about an error, try `rustc --explain E0282`.
error: could not compile `typst-live` due to 2 previous errors
error: failed to compile `typst-live v0.2.0`, intermediate artifacts can be found at `/var/folders/8_/wzzr3w4x4p7b6pybynnrqldm0000gn/T/cargo-installg6eCgQ`

Thanks, should work now with 0.2.1, couldn't test on MacOS myself.

Cool thanks I managed to install. got another issue I'll open one


Fix detecting when Gradle is invoked from Studio

The existing idea.platform.prefix system-property approach only worked because of a Android Studio bug that leaks the system properties from Android Studio into Gradle build.

https://issuetracker.google.com/201075423

This bug was fixed in Android Studio 2023.3.1 (Jellyfish), which is why Godot fails to build on Jellyfish without this fix.
The correct way of identifying builds from Android Studio is to use the following project property (not system property):

android.injected.invoked.from.ide

Fixes #92122

Validated the fix works as expected!

PTAL.

Squashed commits. PTAL.

Thanks! And congrats for your first merged Godot contribution :tada:


Add fuzziness to knife ssh queries

PR for #3526.

:+1:

Also, my ruby force is apparently weak here -- any suggestions on how I could pull #fuzzify_query from lib/chef/knife/search? (this is where you all probably judge me :)

Also, went searching for tests that cover this part, but doesn't seem we test this level, so given that I'm not comfortable enough with starting my own test approach from scratch, I think this is just waiting on feedback on the above, then it's good to merge as far as I'm aware.

So, what I'd really like to see is knife ssh and knife node search share exactly the same code and call the same method that does fuzziness.  Eliminate code duplication and eliminate the chances that we patch in one place and not the other.

We can't merge this without considering the problem holistically, so :-1: for now.

Agree, and for the future the Manage code has a similar fuzzifier and should make sure that uses the same algo.

Totally fair. Closing for now


Added CI workflow to this repository

The purpose of this workflow is to build the project in merge requests as shown below.

It can also bumps up the ImGui.NET version and creates a ImGui.NET NuGet release when a new git tag is created. So basically, once you merge any MR, all you need to do is create a new git tag and rest of the stuff is automated as shown below.

NOTE: Git tags can be created from github UI as shown below

NOTE: Git tags can also be created via command line as shown below
git tag -a 1.86 -m "Releasing new ImGui.NET Version"
git push origin 1.86

@mellinoe  I have created a step called "List Packages" rather than "Publish Packages" because I do not know your private key and stuff. Feel free to modify "List Packages" run command to publish packages run command.

As I stated before, no idea what to do with 3rd party libs, so this MR only focuses on publishing ImGui.NET.

Merged in a slightly adjusted form.


getDragEdge() doesn't reflect StyledAttribute

Bug Found When Testing:
https://github.com/jpshelley/AndroidSwipeLayout/blob/create_test_suite/library/src/test/java/com/daimajia/swipe/SwipeLayoutTest.java#L54
Should getDrageEdge() reflect the StyledAttribute if applied here:
https://github.com/jpshelley/AndroidSwipeLayout/blob/create_test_suite/library/src/main/java/com/daimajia/swipe/SwipeLayout.java#L88
expected: if dragEdgeChoices is DRAG_LEFT then getDragEdge() equals DRAG_LEFT
actual: if dragEdgeChoices is (DRAG_LEFT or DRAG_TOP or DRAG_BOTTOM) then getDragEdge() equals DRAG_RIGHT
if so I will update the variable in my testing branch.

Can  you make sure the following code returning the correct attributes ?
https://github.com/jpshelley/AndroidSwipeLayout/blob/create_test_suite/library/src/test/java/com/daimajia/swipe/SwipeLayoutTest.java#L145

I checked the style attributes initilaize process (https://github.com/daimajia/AndroidSwipeLayout/blob/master/library/src/main/java/com/daimajia/swipe/SwipeLayout.java#L82-L111 ) , seems no problem.

@daimajia The intialization isn't a problem. I guess my question is in regards to requirments of the library.
https://github.com/daimajia/AndroidSwipeLayout/blob/master/library/src/main/java/com/daimajia/swipe/SwipeLayout.java#L1143
That ^^ should return the currentDragEdge. If you set the SwipeLayout to have a drag_edge of Left that actually is returning Right.

Yes, it's a bug.
When a drag happen, the currentDragEdge will change to the edge even if the edge can't drag.
(in checkCanDrag method).


Add readOnly property to TextInput

This adds prop type and documentation for the readOnly property (which sets the readonly attribute on the <input />).
Note that the property is already there and working, just not documented which is what this PR addresses.
You might note that the property is called readOnly, whereas the HTML/DOM attribute is called readonly. This comes from React and is the same thing as onClick vs onclick...
Merge checklist

[ ] Changed base branch to release branch
[ ] Add or update TypeScript definitions (index.d.ts) if necessary
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Thanks, for the PR @LinusU! Since the <TextInput /> will supply any prop that you provide it to the underlying <input />, do you think it would be better to point to some place like this: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react/index.d.ts#L1943
to list all of the possible props, as opposed to duplicating them one-by-one here? If you wanted to set a maximum length on your <input /> and looked at these props and didn't see maxLength listed, but saw the link above, would that be enough? Or would you want to see all of those props listed here on this page?
I think I would lean toward keeping the list here shorter, so that users don't get lost in a larger list, but providing some sort of note that the component also accepts any prop that you can provide to the underlying <input />.
cc/ @emplums has something like this come up before?

Might be a good idea 👍
I mostly added it since disabled was already there, and I was switching a disabled to readOnly when VS Code complained that there was no readOnly prop (which was fixed with ddf8d1c607b5b54bbfc31c8260d354e60a1e54ff btw, was using an old version). This lead me to the website to check and indeed it wasn't listed...
Still, a note about it supporting all input properties is probably better 👍

@LinusU thanks for this PR! I agree - I think just adding a note that says that all native input HTML attributes are supported would be better! That way we differentiate between props that are unique to the React component and props that are just native HTML attributes (something that probably isn't currently super consistent in our docs).

Should we remove all but autocomplete, theme, size, and block then? I can make a PR in that case ☺
autocomplete is also a bit strange since the component now accepts both autoComplete which is the React standard way of capitalising it, and autocomplete which is specific to TextInput. Maybe we could remove autocomplete in the next major release, and for now not document it as is already covered as autoComplete under the "accept all properties as <input />" note?

@LinusU yeah removing those sound good! Can you also remove the native HTML props from the PropTypes declaration? It doesn't feel 100% right to have those in there.
and yes, I agree we should just change autocomplete to autoComplete - I'm sure you've noticed there's a backport for that in the component already and it would be nice to just rename that prop all together in the next major version

@LinusU just a heads up @BinaryMuse ended up needing to refactor TextInput a bunch in https://github.com/primer/components/pull/581/files - so I'll have her make that autocomplete change there as well :)

I think we can close this as #581 addresses it :)