Could not resolve all task dependencies for configuration ':app:releaseStagingCompileClasspath'.

i have three env debug, staging, production, when i run ./gradlew assembleReleaseStaging
then i got this error
environment variable
System:
OS: Linux 5.3 Ubuntu 19.10 (Eoan Ermine)
Binaries:
Node: 13.11.0
npm: 6.13.7
npmPackages:
react: 16.8.3
react-native: 0.59.1 9.1
npmGlobalPackages:
react-native: 0.61.5
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':app:compileReleaseStagingJavaWithJavac'.

Could not resolve all task dependencies for configuration ':app:releaseStagingCompileClasspath'.
Could not resolve project :react-native-audio.
Required by:
project :app
Unable to find a matching variant of project :react-native-audio:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-call-detection.
Required by:
project :app
Unable to find a matching variant of project :react-native-call-detection:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-fs.
Required by:
project :app
Unable to find a matching variant of project :react-native-fs:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-image-crop-picker.
Required by:
project :app
Unable to find a matching variant of project :react-native-image-crop-picker:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-document-picker.
Required by:
project :app
Unable to find a matching variant of project :react-native-document-picker:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-firebase.
Required by:
project :app
Unable to find a matching variant of project :react-native-firebase:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-camera.
Required by:
project :app
Unable to find a matching variant of project :react-native-camera:
- Variant 'generalDebugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'generalDebug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' and found incompatible value 'general'.
- Variant 'generalDebugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'generalDebug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' and found incompatible value 'general'.
- Variant 'generalReleaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'generalRelease' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' and found incompatible value 'general'.
- Variant 'generalReleaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'generalRelease' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' and found incompatible value 'general'.
- Variant 'mlkitDebugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'mlkitDebug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' and found compatible value 'mlkit'.
- Variant 'mlkitDebugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'mlkitDebug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' and found compatible value 'mlkit'.
- Variant 'mlkitReleaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'mlkitRelease' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' and found compatible value 'mlkit'.
- Variant 'mlkitReleaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'mlkitRelease' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' and found compatible value 'mlkit'.
Could not resolve project :react-native-version-number.
Required by:
project :app
Unable to find a matching variant of project :react-native-version-number:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-mauron85-background-geolocation.
Required by:
project :app
Unable to find a matching variant of project :react-native-mauron85-background-geolocation:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-geolocation-service.
Required by:
project :app
Unable to find a matching variant of project :react-native-geolocation-service:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-image-picker.
Required by:
project :app
Unable to find a matching variant of project :react-native-image-picker:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :appcenter-crashes.
Required by:
project :app
Unable to find a matching variant of project :appcenter-crashes:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :appcenter-analytics.
Required by:
project :app
Unable to find a matching variant of project :appcenter-analytics:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :appcenter.
Required by:
project :app
Unable to find a matching variant of project :appcenter:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-config.
Required by:
project :app
Unable to find a matching variant of project :react-native-config:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-code-push.
Required by:
project :app
Unable to find a matching variant of project :react-native-code-push:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-android-location-enabler.
Required by:
project :app
Unable to find a matching variant of project :react-native-android-location-enabler:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-file-picker.
Required by:
project :app
Unable to find a matching variant of project :react-native-file-picker:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
Could not resolve project :react-native-firebase-mlkit.
Required by:
project :app
Unable to find a matching variant of project :react-native-firebase-mlkit:
- Variant 'debugApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'debugRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'debug'.
- Found com.android.build.api.attributes.VariantAttr 'debug' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseApiElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found compatible value 'java-api'.
- Required react-native-camera 'mlkit' but no value provided.
- Variant 'releaseRuntimeElements':
- Required com.android.build.api.attributes.BuildTypeAttr 'releaseStaging' and found incompatible value 'release'.
- Found com.android.build.api.attributes.VariantAttr 'release' but wasn't required.
- Required com.android.build.gradle.internal.dependency.AndroidTypeAttr 'Aar' and found compatible value 'Aar'.
- Required org.gradle.usage 'java-api' and found incompatible value 'java-runtime'.
- Required react-native-camera 'mlkit' but no value provided.

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.

Get more help at https://help.gradle.org

Hi @Omprakash76 please open a new issue with the issue template thank you.


add faq, test=develop

add faq.

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

Can one of the admins verify this patch?


Unify Ecosystem

I would like to suggest that you unify all grape related projects into a single "organization", to make the ecosystem around it stronger.
As an example of what should be considered (I've listed the most active and still maintained projects):
Functionality

grape
grape-entity
grape-rabl
grape-cache_control
grape_ape_rails
grape-rails-cache
grape-cors
grape-active_model_serializers
grape-activerecord
grape_logging
grape-doorkeeper

Documentation

grape-swagger
grape-swagger-ui
grape-swagger-rails
grape-slate

Monitoring / Instrumentation

newrelic-grape
grape-librato
grape-appsignal

Test Helpers

grape-entity-matchers

And consider grape demodulation.
P.S. @brodock insert links to project pages, please?

@kuraga sure! I will edit the post

Thanks very much about this topic!

Generally I don't find discoverability being a problem, but I understand how the ecosystem could be stronger.
I feel torn about the unification of such things, I really like the distributed nature of open-source and I also really like that owners of gems stand behind those gems as opposed to having some centralized Soviet style "organization". I wish there was a virtual "organization" that could collect projects like this other than through a github wiki or page.
Would love to hear everyone's thoughts and suggestions!

I was more concerned of some gems being maintained as fork of a fork of a fork...
My initial suggestion is to delegate the ownership of the repositories for their respective maintainer, while having a "single point of discovery" here, and perhaps this could potentially help related gems talk to each other and collaborate in a better way.
Things like enabling gitter.im for the organization and for every project can also help with that

Hey @brodock, thanks so much for suggesting this. It's something I thought about frequently myself. The burden of maintenance is a tough question and OSS requires a group effort. I don't think discoverability is a core issue because the wiki includes a list of projects. A better suggestion to improve discoverability could be to include the link to related projects into the README. This would let people realize that grape has a thriving ecosystem and that are tools they can leverage.
However, I'm very frustrated with the state of grape-swagger-rails. If you google grape swagger rails, the first result is a fork of an earlier project:
https://github.com/BrandyMint/grape-swagger-rails
On first glance, the project looks maintained but if you look at the issues (https://github.com/BrandyMint/grape-swagger-rails/issues/50), you'll see that this an old project and that there is yet another fork!
I like your current suggestion of unifying grape tools in one particular org BUT I think your list is too long. I would prefer an org with core projects (grape, grape-swagger, grape-entity, etc) and another repo for "great to use with." For example, I'm not sure if grape-doorkeeper (I prefer wine_bouncer) should be in the umbrella org.

@whatasunnyday sure! I listed all the gems I could find that are somehow maintained and may look useful for the majority of users.
I understand that selecting the "most useful ones" (you can call it core), is a good start point... and be open to include others as soon as they become more mature and wild used.
What do you think?

I think that's a good call.

+1 to what @whatasunnyday said.
I generally like the idea of an umbrella org, because it usually comes with some quality guarantees (which of course mean more burden on maintainers).
I think especially semi-popular gems could benefit from it (or some other form of enhanced communication), since quite a few of them ignore facilities provided by grape (e.g. ignoring Helper modules and implementing a half-baked solution themselves).

+1 to what @whatasunnyday said.
I like the idea of having a "single point of discovery", with the core gems, and not to worry about using the wrong fork.

Really nice idea. I believe it would be good to include the most popular/used related projects to the org. It would also be good, if everyone who is interested in the "grape plugins" can collaborate more tightly to improve functionality of the projects.

I agree with @hobofan. I think list of extensions in Readme would be very convenient for newcomers.

I take PRs for the README that link externally. For example we have links to grape-entity and others that are commonly used and frequently needed.

Well, it's happening! We're moving to https://github.com/ruby-grape shortly.

thank you very much :)

Great news!

Happy to close this now! Please open specific work-items around community organization in https://github.com/ruby-grape/ruby-grape.github.io/issues. Also hitting Send on an announcement to the Google group.

Can someone please port the list of projects from here to https://github.com/ruby-grape/ruby-grape.github.io? See https://github.com/ruby-grape/ruby-grape.github.io/issues/3.

^^ done


right/left tree view

i see the in the code you have an if setup for right/left tree view. No option to switch in the config. Everytime i do an update i have to manually adjust the code to make my tree view on the right. Can you fix this?

Related of #1068. I close this issue.


feat: Add list page as requested in #4242

Add new page  to list all area directors and their current workload. Include links to the specific dashboards
for each area director. This new page is in doc/ad/.

Jennifer Richards writes:

   elif doc.get_state_slug('draft') == 'active' and doc.get_state_slug('draft-iesg') and doc.get_state('draft-iesg').name in ('RFC Ed Queue Internet-Draft'):

Should that be ...in ('RFC Ed Queue', 'Internet-Draft')

Actually it should be 'RFC Ed Queue' without the Internet-Draft. It
worked as 'RFC Ed Queue Internet-Draft' did include RFC Ed Queue that
is in the draft-iesg name.
The ad_dashboard_group do return "RFC Ed Queue Internet-Draft", which
was why I had cut & pasted it here.
@.***

There are other comments to consider, but I wanted to point out:
the change at 76df542 should just be to use == instead of in.
You are getting lucky that a string in parenthesis is a string, not a tuple, and it leaves a trap for the maintainer:
>>> 'foo' in 'foobar'
True
>>> 'foo' in ('foobar')
True
>>> 'foo' in ('foobar',)
False

Rather than push into Tero's branch, I'm working in https://github.com/rjsparks/datatracker/tree/ad-list-page. I'll eventually make a PR that supersedes this one.

Replaced by #4315.


Re #53; provided solution did not solve the order loading mishap

here's the newest version of my datapack.  unzip before loading.
KBPData.zip
absolutely none of the origins get modified on world start.  it's really starting to bug me.
did you mean to say "loading_order" or "loading_priority"?  you gave me conflicting information

loading_priority, I'm a derp.
Also you don't actually need to open a new issue. I get notifications from closed issues too.

ah alright. I'll test again and see if it fixed.
some devs unfollow threads that they close so I had to make sure.

yes, it's fixed.  thank you!


initPmtk3 failing - java memory issue

Hey,
I'm trying to get this running on my macbook pro running os X - 10.11.6, and matlab 2016. This is the error I get,
{
Exception in thread "BayeuxServer@618007232" Exception in thread "qtp522940303-116" Exception in thread "Explorer NavigationContext request queue" java.lang.OutOfMemoryError: GC overhead limit exceededException in thread "qtp522940303-122" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "qtp522940303-115" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "AWT-EventQueue-0" Exception in thread "qtp522940303-121" java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: GC overhead limit exceeded
}
Any help is much appreciated.

Apologies, this has nothing to do with pmtk3. I downloaded the latest version of matlab, and there is some interference with git.
You have to disable the Source Integration Tool as follows:

Home Tab > Environment > Preferences
In the preferences dialog, MATLAB > General > Source Control pane, then select None
Close MATLAB

Everything is working good now.


EAT BAGELS! HIGH PRIORITY!!

Commenting for reach

I had a half a bagel for breakfast. I think this can be closed.

Closing. Bagels have been consumed.


Seasonality and Causal effects in GCM

@kailashbuki @bloebp Hi, I would like to know if the causal influences (intrinsic causal influences, arrow strengths in GCM) that can be discovered from the data would depend on the seasonality patterns in the data or would it be independent of the seasonal trends? Also Is it a relevant assumption to consider?
--For instance, in  securities trading, the trend / seasonality in data varies based on time/day (morning, intraday and delivery etc), We are looking at estimating the causal influences in a cloud/microservices environment running trading applications which will reflect seasonal changes in the data.  The question that I have now is should we train GCM on a larger dataset (like last 3 months) that would have captured some of the seasonal patterns and If the causal influences are not dependent on seasonal patterns , Can I use a smaller dataset (last 15 days) ?.
Thanks in advance.

Hi, that's a great question. Generally, these algorithms assume IID data (i.e., no time dependencies, no hidden confounders). However, if the seasonal effects are relatively weak, these algorithms can still provide some useful results, though they should be treated with caution. Some ideas to mitigate the issue:

Introduce an additional variable representing the time, for instance, a sinus distributed over week, month etc.
Average over a higher time granularity, although some valuable information may be lost
Remove the seasonality from the data by using techniques like a seasonal decomposition
Introduce lag variables, such as adding the feature value from the previous day. In this case, the graph structure can become quite complex and large.

If there are no seasonal patterns, smaller datasets may still be useful, depending on the time granularity and size of the graph. However, if the time granularity is one data point per day, then 15 days is likely too small.

@bloebp Thanks for the inputs


fix(appeals): improvements of document types

Some improvements to typings for appeal documents. 1 small fix, the rest is typings and jsdoc.
N/A
Type of change 🧩

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

LGTM...would prefer to remove lines rather than comment out but that's personal preference :)

Yes definitely, but this was an existing web test that wasn't used, so commented out to clear up with the other guys...


Update FFmpeg, openCV, Protobuf

Update dependencies to latest versions.
Source snapshot for FFmpeg was adjusted.
Signed-off-by: Krzysztof Lecki<EMAIL_ADDRESS>

Builds:
2282811, 2282810

Builds:
2283144, 2283145

Builds: 2286805, 2286806


Don't save document before completion

Fixing the indentation from gofmt like this:

Now godef utility uses stdin instead file on disk

Looks good, thank you.


ORM or similar tooling

I wonder if its possible to use existing SQL DB tools with genji ?
https://github.com/kyleconroy/sqlc

Just takes SQL and generates the golang code. So not dependent on anything else.
Can hence be used to take migration and generate te golng code for a migration also.
The template it uses to generate the code can be easily modified to suit genji

Or https://gitea.com/xorm from gitea project ?

Good question, I haven't tried any existing ORM yet

One thing that might be a good one is Ent.
https://entgo.io/
https://entgo.io/docs/privacy/
Why ?
Its code generation based and very easy to use. Its not an ORM that takes over too much.
It enforces authz at the data layer. something genji does not do yet.
Its well used, and has facebook coders working on it.
It has the concept of nodes and edges, rather than inner join etc, and so is more aligned to a degree with genji.
It is all golang.
The thing with all the existing SQL ish tooling for go, is that genji needs a driver layer in order to use any of these tools.
If we liked Ent, then it would not be that hard to add a Ent driver for genji i think.
https://github.com/facebookincubator/ent-contrib

shows how it supports graphql easily.
shows however that other RPC mechanisms can be added if needed too.

Ent is not an ORM btw. Its a code generator.  Some devs like this and some dont.
Its all comes down to having a working github.com/genjidb/genji/sql/driver.
Like this issue addresses: https://github.com/genjidb/genji/issues/338
Then all the various golang ORM and code generators and migration tools can work with them.


Customize Module

Hi,
I was trying to customize the modules which used by aRNAPipe. For example, I want to disable the gatk module. But the documents does not provide a instructions for customize the module. When I delete the STAR module in config.txt, a error message wil appear. Like the following:
Traceback (most recent call last):
File "/home/adigioia/Documents/Matt/program/aRNAPipe/lib/wr_aRNApipe.py", line 68, in
print "  - STAR:            " + var["star"]
KeyError: 'star'
Could you tell me how to customize the modules used by aRNApipe?

Hi,
I've just realized that the wiki doesn't include specific information on how to disable/enable modules.  I've updated it in '2. aRNApipe: The main application > The config.txt file'. In order to disable a module the user has to set the first argument ('a') of the corresponding module to 0. All the customization is done through the configuration file by modifying the arguments but avoiding line deletions.

Thanks for your anwser! I tried set the a to be 0 and successfully disabled the module.


[$250] Workspace switcher - Expensify and workspace are highlighted when navigating by keyboard

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.80-9
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: n/a
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Precondition:

User has at least one workspace.
Workspace switcher is set to "Expensify".

Go to staging.new.expensify.com
Open workspace switcher.
Navigate through the workspace list via keyboard.

Expected Result:
"Expensify" filter will not be highlighted when navigating through the workspace list via keyboard.
Actual Result:
Both "Expensify" and the selected workspace are highlighted when navigating through the workspace list via keyboard.
User is also unable to move the selection from workspace list to Expensify and vice versa.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/38435837/6d652a4f-0152-4ed6-b470-11c132975670

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0120bd99e26c1b69ef
Upwork Job ID:<PHONE_NUMBER>849632061
Last Price Increase: 2024-06-07

Issue OwnerCurrent Issue Owner: @rojiphil

@tgolen FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsb

We separated Expensify option and selection list, before that Expensify option was in the list so it was only highlighted when focused. This is expected behaviour IMO.

I agree, wdyt @blimpich?

Yeah seems like intended behavior to me. And even if it isn't we shouldn't block the deploy over this.

Asked internally to double check if this is intended behavior. If people agree lets close this.


Implemented HelpManager

First running version of HelpManager

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

132 of 162 (81.48%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+53.9%) to 84.369%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/libraries/Helpm8.Core/HelpRoot.cs
1
2
50.0%

src/libraries/Helpm8.Core/ReferenceCountedProviderManager.cs
42
43
97.67%

src/libraries/Helpm8.Core/HelpExtensions.cs
22
24
91.67%

src/libraries/Helpm8.Core/HelpManager.cs
67
93
72.04%

Files with Coverage Reduction
New Missed Lines
%

src/libraries/Helpm8.Core/HelpManager.cs
1
72.07%

Totals

Change from base Build<PHONE_NUMBER>:
53.9%

Covered Lines:
373

Relevant Lines:
435

💛  - Coveralls


upgrading R on hub

Currently the hub is using R 4.0.5.  move2 and rayshader requires >= 4.1.0.  I've asked David @ Hubzero to upgrade if possible...

Hubzero will upgrade this sprint and also install additional packages that we need: move2, sf, terra, rayshader, reticulate, etc

David @ Hubzero upgraded R to 4.4.1 and installed keyring, move2 and sp packages.  he is having some problem installing the rayshader package, still trying... (see support ticket comment)


Profiles Int64 variables as float

General Information:

OS: Win 10 Enterprise
Python version: 3.9.7
Library version: 0.10.7

Describe the bug:
Int64 columns in a dataframe are treated as float, "samples" lists float values, as well as all statistics do.
data_label = FLOAIs it possible that "Int64" (capital I) is not supported?
c
To Reproduce:
Expected behavior:
treat Int64 as Int64...
Screenshots:
Additional context:

Hey @anxti, thanks for opening an issue here.
Please fill out the rest of the issue template with a code snippet to reproduce / example data you are using -- that helps us work through issues a bit quicker. Might be slightly delayed in my responses this week as well but will do my best to keep an eye on any updates here. Best!


macOS go get error  -> undefined: unix.InotifyEvent

go get github.com/tywkeene/go-fsevents
# github.com/tywkeene/go-fsevents
../github.com/tywkeene/go-fsevents/fsevents.go:35:12: undefined: unix.InotifyEvent

Inotify is a Linux kernel subsystem, and as such will not work on other kernels.
Sorry, there's really no way to fix this.

How to install this module on macOS to cross-compile for Linux?

I'm not sure what you mean by cross compile.
If you'd like to watch a directory on a mac, or develop with go-fsevents on a mac, you can use the docker desktop app for macs. Since docker desktop is actually a Linux VM under the hood, it has access to the correct libraries to build and run a program with go-fsevents. We have a few dockerfiles under the docker/ directory in the repo that you can use as a jumping off point.
Other than that, it's literally down to whether the kernel is Linux or not, and Mac obviously isn't. If you're looking for something mac native that's similar to inotify, you might try one of the other packages named similarly.

I develop an application using go that is targeted for Linux and Windows. It requires recursive file system monitoring. So I need Go modules for monitoring the filesystem for both platforms. Using environment variable (i.e. GOOS=linux) I can use Go to build a project for Linux using my macOS. Same with Windows. I can get .EXE file using Go on my mac. I have found go-fsevents module suitable for Linux version of my application, but I can not install it on my mac. I assume that I will also not be able to install it on Windows. I do not want to use two separate platforms to develop one application.

So as I mentioned in my previous comment, even if you do get this to build using GOOS=linux, the program will not function on any machine that isn't running Linux. This isn't a limitation of the package itself, but rather the fact that the inotify subsystem is specifically a Linux kernel feature.
If you need to monitor filesystems on Mac/Windows, I've had success using Docker Desktop as I mentioned before, other than that, you may need to explore other, native options for each OS.
You might have some luck with this project instead: https://github.com/fsnotify/fsnotify

Hi! Thank you for your input!
I am perfectly Ok with not be able to run this application under
macOS/Windows. Cross-compilation will produce ELF file for Linux and it
will not run under macOS/Windows in any case.
Unfortunately, my application is not containerized by design. The customer
expects it to be a native Windows/Linux service
fsnotify is not recursive, so it does not fit my needs.
пн, 19 апр. 2021 г. в 20:54, Tyrell Keene @.***>:

So as I mentioned in my previous comment, even if you do get this to build
using GOOS=linux, the program will not function on any machine that isn't
running Linux. This isn't a limitation of the package itself, but rather
the fact that the inotify subsystem is specifically a Linux kernel feature.
If you need to monitor filesystems on Mac/Windows, I've had success using
Docker Desktop as I mentioned before, other than that, you may need to
explore other, native options for each OS.
You might have some luck with this project instead:
https://github.com/fsnotify/fsnotify
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tywkeene/go-fsevents/issues/8#issuecomment-822660174,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQTV7IDQSJQIRROZ233KI3TJRU63ANCNFSM4GM64DLA
.


Support max recursion depth

@leapingfrogs these changes look great! Are you ok if I merge them in?

No worries! Ended up merging a separate PR so I'll close this for now. Thanks!


Introduce Tailable interface to allow tailing of files accessed using alternative libraries such as jCIFS or commons-vfs

I have a derivation of org.apache.commons.io.input.Tailer in our codebase which allows tailing of remote files using different user credentials via jCIFS.  It would be very nice if we could remove this duplicated code with the introduction of this Tailable interface.  It shouldalso be possible to tail files using commons-vfs e.g. HdfsRandomAccessContent,

Coverage decreased (-0.7%) to 89.348% when pulling 1c94596e18312947fc9c1926bbe44f980e8ebe9d on jonfreedman:master into 8b9fe1b01ce21003f6a6ff8391ad2a64f4d21030 on apache:master.

It appears the test cases are fragile, the travis build has failed on one test with openjdk7 which passes on oraclejdk7 and oraclejdk8
FileFilterTestCase.testAgeFilter:856->assertFiltering:64 Filter(File) org.apache.commons.io.filefilter.AgeFileFilter not false for /home/travis/build/apache/commons-io/test/io/new.txt expected:<false> but was:<true>

jira issue: https://issues.apache.org/jira/browse/IO-533

We cannot depend on jcifs IIRC, which is why it is still in the Commons VFS sandbox.

@garydgregory The title of the pull request is a bit misleading. It does not add a jcifs dependency. It adds an interfaces which the user can implement, e.g. to add tail jcifs files.

I've renamed the issue to hopefully clarify there is no jcifs or commons-vfs dependency.  For reference the pull request is functionally complete (as we've been running comparable code for a few months now).

May you please rebase on master? New public and protected elements should have a Javadoc @since tag.

Is this now a candidate to be merged? It's over 4 years since I wrote this code and I've moved jobs twice since then!

We are all volunteers here... I'm taking the time to review what's outstanding this weekend. If you are no longer interested, feel free to close this PR ;-)

I still think it's a valid change, I'll refresh my memory, rebase and update the java doc, I assume you want it to say @since 2.12.0?

I still think it's a valid change, I'll refresh my memory, rebase and update the java doc, I assume you want it to say @SInCE 2.12.0?

Correct and thank you.

Not sure what's going on here, I haven't changed 466 files...
See https://github.com/apache/commons-io/compare/master...jonfreedman:master for the diff

I can't review 466 files... you might consider redoing the PR.

I will re-create my fork and submit another PR, not sure what that will do to this one.  ---- On Sun, 05 Sep 2021 22:55:11 +0100  @.***  wrote ----
I can't review 466 files... you might consider redoing the PR.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

OK, now this looks better

Hi @jonfreedman,
Thank you for the reworked PR. You will need a new unit test for each of the new methods.

I've written a load of tests for the constructor/create overloads, my test is super simple and I am observing it occasionally fail with the Tailer reading the one line from the file twice. I've commited as I figured you may want to take a look at that...

I see the cause of the unstable tests, missed that #create starts a thread for you

I have a feeling I just lifted all the java doc from the underlying methods, they may have changed in the last 5 years and I'll also incorporate your suggestions. Regarding the constructors/factory methods, personally I would prefer to replace the whole lot with a builder but that's obviously quite a departure from the existing code, I had designed this PR to be as close as possible to the existing but I'm happy to make it 'better' if it would be accepted?  ---- On Mon, 06 Sep 2021 19:40:47 +0100  @.***  wrote ----
@garydgregory requested changes on this pull request.
@jonfreedman
Thank you for the update.
Hi, I did a review and scattered my comments throughout.
In src/main/java/org/apache/commons/io/input/Tailer.java:

    * @return  true if and only if the tailable exists;

    *          false otherwise

    */

   boolean exists();

   /**

    * Tests if this tailable is newer than the specified time reference.

    *

    * @param timeMillis the time reference measured in milliseconds since the

    *                   epoch (00:00:00 GMT, January 1, 1970).

    * @return true if this tailable has been modified after the given time reference.

    */

   boolean isFileNewer(final long timeMillis);

   /**

    * @param mode the access mode<EMAIL_ADDRESS>RandomAccessFile}

The 1st sentence is missing for this method.
In src/main/java/org/apache/commons/io/input/Tailer.java:

@@ -556,4 +784,181 @@ private long readLines(final RandomAccessFile reader) throws IOException {
return rePos;
}
}

/**

* Abstraction on<EMAIL_ADDRESS>java.io.File} which allows substitution of remote files for example using jCIFS

*

* @since 2.12.0

*/

public interface Tailable {

   /**

    * @return  The name of the file denoted by this tailable

The 1st sentence is missing for this method.
In src/main/java/org/apache/commons/io/input/Tailer.java:

   /**

    * @param mode the access mode<EMAIL_ADDRESS>RandomAccessFile}

    * @return a random access file stream to read from

    * @throws FileNotFoundException if the tailable object does not exist

    */

   RandomAccessTailable getRandomAccess(final String mode) throws FileNotFoundException;

}

/**

* Abstraction on<EMAIL_ADDRESS>java.io.RandomAccessFile} which allows substitution of remote files for example using jCIFS

*

* @since 2.12.0

*/

public interface RandomAccessTailable extends Closeable {

   /**

    * Returns the current offset in this tailable.

"Returns" -> "Gets"
In src/main/java/org/apache/commons/io/input/Tailer.java:

    * @exception  IOException  if an I/O error occurs.

    */

   long getFilePointer() throws IOException;

   /**

    * Sets the file-pointer offset, measured from the beginning of this

    * tailable, at which the next read or write occurs.  The offset may be

    * set beyond the end of the tailable. Setting the offset beyond the end

    * of the tailable does not change the tailable length.  The tailable

    * length will change only by writing after the offset has been set beyond

    * the end of the tailable.

    *

    * @param      pos   the offset position, measured in bytes from the

    *                   beginning of the tailable, at which to set the

    *                   tailable pointer.

    * @exception  IOException  if<EMAIL_ADDRESS>pos} is less than

@." -> @."
In src/main/java/org/apache/commons/io/input/Tailer.java:

*/

public interface Tailable {

   /**

    * @return  The name of the file denoted by this tailable

    */

   String getName();

   /**

    * @return  The full path of this tailable

    */

   String getPath();

   /**

    * Returns the length of this tailable

    *

    * @return  The length, in bytes, of this tailable, or 0L

foo -> @.*** foo}
In src/main/java/org/apache/commons/io/input/Tailer.java:

    * @param timeMillis the time reference measured in milliseconds since the

    *                   epoch (00:00:00 GMT, January 1, 1970).

    * @return true if this tailable has been modified after the given time reference.

    */

   boolean isFileNewer(final long timeMillis);

   /**

    * @param mode the access mode<EMAIL_ADDRESS>RandomAccessFile}

    * @return a random access file stream to read from

    * @throws FileNotFoundException if the tailable object does not exist

    */

   RandomAccessTailable getRandomAccess(final String mode) throws FileNotFoundException;

}

/**

* Abstraction on<EMAIL_ADDRESS>java.io.RandomAccessFile} which allows substitution of remote files for example using jCIFS

Sentences should end in a period.
In src/main/java/org/apache/commons/io/input/Tailer.java:

/**

* Abstraction on<EMAIL_ADDRESS>java.io.File} which allows substitution of remote files for example using jCIFS

*

* @since 2.12.0

*/

public interface Tailable {

   /**

    * @return  The name of the file denoted by this tailable

    */

   String getName();

   /**

    * @return  The full path of this tailable

    */

   String getPath();

Confusing API name because it does not return a Path; either rename the API or make it return a Path.
In src/main/java/org/apache/commons/io/input/Tailer.java:

@@ -556,4 +784,181 @@ private long readLines(final RandomAccessFile reader) throws IOException {
return rePos;
}
}

/**

* Abstraction on<EMAIL_ADDRESS>java.io.File} which allows substitution of remote files for example using jCIFS

*

* @since 2.12.0

*/

public interface Tailable {

   /**

    * @return  The name of the file denoted by this tailable

    */

   String getName();

The name of... what? the base file name? The full file name?
In src/main/java/org/apache/commons/io/input/Tailer.java:

@@ -191,6 +203,18 @@ public Tailer(final File file, final TailerListener listener, final long delayMi
this(file, listener, delayMillis, false);
}

/**

There are way too many new factory APIs here IMO. For the first cut, let's add one and see what other use-cases require in the future. If a delay is provided, please make that a Duration, not a long. I'll redo the internals after this PR comes in to use a Duration instead of a long. If you add a constructor, make it private or package private.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

If you want to provide a builder, that's fine with me. Just be aware that we CANNOT break binary compatibility (mvn clean package japicmp:cmp)

@jonfreedman
I redid the guts to use a Duration instead of a long.
May you rebase on master please with your builder impl?

Hi @jonfreedman,
Thank you for your patience.
Please see git master for the new implementation. I committed the changes from this PR combined with:

Use Objects.requireNonNull() instead manual checks.
Normalize Javadoc.
Add missing Javadoc.
Add missing Javadoc tags.
Sort members.
Don't initialize ivars to defaults.
Renamed some types, ivars, and params.
Fix some Javadoc.
No need to use FQCNs in Javadoc @link.
Use {@code} instead of .
YAGNI: Remove some methods that are not tested and never called.
Re-implement some internals using NIO.
Add some constructor parameter validation.
Add a toString() method.

May you please make sure your use case is satisfied?
If you want the code to do more, please rebase on master or provide a new PR.
TY.

Thanks for finally getting the change in there, it's a bit of a shame you weren't able to merge but the project has improved so I'll take what I can get.


Wilker

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


Consistent use of 'Condition' (vs 'Disease')

Noting that we use both terms 'condition' and 'disease' in attribute names and class/attribute descriptions, across the different statement profile files.  I assume that the inconsistent use of the terms in attribute names and class/attribute descriptions across various profiles is unintentional.
I recommend that we update these to use the broadest term  'condition' in all cases (unless there is reason to sue a more specific term like 'disease' or 'tumor') - so that we are clear and consistent here.  Esp since our model makes an explicit distinction between Condition and Disease classes.

I agree with the recommendation. To be clear though, the term Condition is specifically defined to be either a Disease a Phenotype or a TraitSet. And a TraitSet is a term from clinvar that can be 2 or more items of a Disease and/or Phenotype.  If we are going to do any major redefining of Condition let's coordinate this with the clinvar implementation so we do not break it.

Hi Larry.  This is how I understand things as well.  I will make a PR with updates to labels and text to be consistent with the modeling.

I think we've sorted this out with the latest Condition, TraitSet domain-entities in VA-spec.


api_server_dns setting to support alternate DNS for k8s API server

api_server_dns setting to support alternate DNS for k8s API server.
See issue https://github.com/vitobotta/hetzner-k3s/issues/238

Looks awesome, thanks! Do you remind renaming the setting to api_server_hostname since DNS might suggest that it's a DNS server setting? Thanks!

Updated the fieldname per your recommendation.

Hi @mgalesloot, thanks a lot for the PR! Looks like a very useful change. I am planning on making a new release this coming weekend if possible.

Merged, thanks for another useful contribution!


Can YOLOOP be used to predict loops in low-coverage data?

Hi,
Thank you for your excellent work.
I am wondering can YOLOOP be used to predict loops in low-coverage data?
When I analyzed on the GM12878 data with 5kb resolution and 500M coverage using your software, I noticed that the number of detected loops was relatively low. Could you please advise on how to adjust the software or parameters to improve loop detection in such cases?
The script that I used:
#!/bin/bash
YOLOOPDIR="./YOLOOP"
cd $YOLOOPDIR

##---------------------------
## Parameters
##---------------------------

RESOL=5000
cover="frac0.125"
THRESHOLD=0.0
BALANCE="false"
OUTPATH="./yoloop_GM12878_500M"

##---------------------------
## Fixed Parameters
##---------------------------

PYTHONFILE="${YOLOOPDIR}/detect.py"
MODELPATH="${YOLOOPDIR}/models/gm12878_hic_10kb.pt"
COOLPATH="./4DNFIXP4QG5B_Rao2014_GM12878_${cover}.hg38.mapq_10.1000.mcool"

##--------------------------------------------------
## Create the OUTPATH directory if it doesn't exist
##--------------------------------------------------

if [ ! -d "$OUTPATH" ]; then
    mkdir -p "$OUTPATH"
fi

##--------------------------------------------------
## Run
##--------------------------------------------------

echo "Starting chromosome processing..."

if [ "$BALANCE" == "false" ]; then

    python $PYTHONFILE --cm $COOLPATH -r $RESOL -m $MODELPATH --out $OUTPATH -t $THRESHOLD

elif [ "$BALANCE" == "true" ]; then

    python $PYTHONFILE --cm $COOLPATH -r $RESOL -m $MODELPATH --out $OUTPATH -t $THRESHOLD -b

fi

echo "Done."

cd -

The result: yoloop_pred_4DNFIXP4QG5B_Rao2014_GM12878_frac0.125.hg38.mapq_10.1000.zip
Thank you for your time and guidance.
Best regards,
Yusen

Hi Yusen,
It seems like you are applying YOLOOP on the low-coverage data. I can see that the input file is the GM12878 cell line in 5kb resolution but with 500M coverage.
When applying the model with bulk-trained data, it might not perform well. I've uploaded a weight file trained on scHi-C data, which is trained in an extremely low-coverage situation. It might be able to help in your situation.
In the meantime, would you point out the source link of your 4DNFIXP4QG5B_Rao2014_GM12878 with 500MB coverage? We might look into that.
Thank you.

Hi Frank,
Thank you for your suggestion.
The weight file you provided works on low coverage Hi-C data. I'm currently benchmarking some of the top methods for loop detection. The data I'm using is directly downsampled from the original GM12878 dataset. You can access the original data here: 4DNFIXP4QG5B.
Thanks again!


contact page doesn't work

No webpage was found for the web address: https://synshop.org/contact/

I mentioned this in discord, this is because redirects and 404s, and
several other functions, are built specific for CoudFlare and won't work if
you port the site to another server as it. This is why I want to finish the
migration tuesday.
On Sun, Oct 1, 2023 at 8:57 PM Ashley @.***> wrote:

No webpage was found for the web address: https://synshop.org/contact/
—
Reply to this email directly, view it on GitHub
https://github.com/synshop/synshop.org/issues/38, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFYAQS2SSE3SXDHA3NTX5I3SNANCNFSM6AAAAAA5O23AOM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

gotcha!
Noting that it's 404 on the CF site too https://synshop-org.pages.dev/contact/ with the trailing slash as linked to in top nav.  If you drop the trailing slash it redirects to /about/


Expose vault path as option

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 85.356%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
204

Relevant Lines:
239

💛  - Coveralls


csv: update csv version to 4.16

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] Pending release notes updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

Please update the csv as well by running the make gen-csv cmd, as a separate commit.

missed that, added it now. Thanks

/cherry-pick release-1.16

/cherry-pick release-4.16


Not able to exit program with a node-rdkafka producer without calling process.exit explicitly

I am writing a pino transport using node-rdkafka. The following code works, messages got pushed to kafka queue without issues. However, in the following app.js program, it won't exit without calling process.exit(0) explicitly. Can someone tell me why process.exit is needed here to terminate the program? Thanks.
/// app.js

const pino = require('pino')
const targets = [
  {
    target: 'pino/file',
    options: {
      destination: 1
    }
  },
  {
    target: './kafkaTransport.js',
    options: {
      topic: 'some-topic',
      'client.id': 'some-id',
      'metadata.broker.list': 'some-kafka-hosts',
    }
  }
]

const logger = pino({
  transport: { targets }
})

logger.info('This is a test')
setTimeout(() => {
  console.log('bye')
  // the program would not exit without the following line
  // process.exit(0)
}, 1000)

/// kafkaTransport.js
const build = require('pino-abstract-transport')
const Kafka = require('node-rdkafka')

module.exports = function (opts) {
  let kafkaReady = false

  const { topic, ...kafkaOpts } = opts
  const producer = new Kafka.Producer(kafkaOpts)
  producer.connect()
  producer.on('ready', () => {
    kafkaReady = true
  })
  producer.on('error', err => {
    console.log(err.message)
  })
  producer.setPollInterval(1000)

  return build(
    function (source) {
      source.on('data', function (obj) {
        if (!kafkaReady) {
          return
        }
        producer.produce(
          topic,
          null,
          Buffer.from(JSON.stringify(obj)),
          null,
          Date.now()
        )
      })
    },
    {
      close (err, cb) {
        process._rawDebug('To close kafka producder')
        if (err) {
          console.error(err.message)
        }
        producer.disconnect(() => {
          process._rawDebug('Kafka producder disconnected')
          cb()
        })
      }
    }
  )
}

Does the disconnect() callback fires at all?

Thanks for checking, without process.exit, neither "To close kafka producder" or "Kafka producder disconnected" is printed. The later debug line was just added to help debugging.

And this works without the Kafka add-on, right? can you push it all to a repo, including a docket-compose to spin up a Kafka cluster? I’d also need a client to poll the messages.

And this works without the Kafka add-on, right?
 Do you know why?

Unfortunately I've exhausted the time I can dedicate to this issue.
What is happening is that the worker_thread is exiting with exit code of 1 but no errors are being logged or produced.
I might recommend to try with a pure-js implementation (kafkajs) because there is likely something odd happening in C++ land in rdkafka

FATAL ERROR: v8::HandleScope::CreateHandle() Cannot create a handle without a HandleScope
1: 0x10053b52c node::Abort() [/Users/matteo/.nvm/versions/node/v16.20.0/bin/node]

It might have something to do with the node version. It runs without issues with node 20 or up

I might recommend to try with a pure-js implementation (kafkajs) because there is likely something odd happening in C++ land in rdkafka

You are right kafkajs doesn't have this issue but the reason I am using node-rdkafka is due to performance requirements: the application I am developing requires a very fast producing performance (dumping request logs to a kafka topic for our microservice application). I chose node-rdkafka because it can do batch-producing with ease (batch handling is handled internally inside node-rdkafka). To be fair kafkajs can do batch producing as well but that requires batching to be handled inside my application code:
await kafkaProducer.sendBatch({
            topicMessages: topicMessages,  // messages are received from requests one by one, they are
                                           // then batched into topicMessages somehow
            acks: -1 // all insync replic
        });

Sounds like this is something related to the rdkafka lib. I will now close the issue. Thanks for investigating the issue @mcollina


training data. same text with different entity names

**Rasa NLU version 0.12.0a1
Used backend / pipeline (spacy_sklearn, ...):
**Operating system osx
Issue:
training data. The same text with different entity names
However, both of them were confused during the dialogue.
Content of configuration file (if used & relevant):
  {
        "text": "shenzhen",
        "intent": "travel",
        "entities": [
          {
            "start": 0,
            "end": 8,
            "value": "shenzhen",
            "entity": "departureCity"
          }
        ]
      },
      {
        "text": "shenzhen",
        "intent": "travel",
        "entities": [
          {
            "start": 0,
            "end": 8,
            "value": "shenzhen",
            "entity": "terminusCity"
          }
        ]
      },

The reason for this is that those are just single words, there is no difference at all between the sentences and so you shouldn't label them as the same entities. If you want this distinction you have to provide sentence examples for both, like:
- I am going to [shenzhen](terminusCity)
- I am departing from [shenzhen](departureCity)

If you have just the text "shenzhen" then I would have a third entity called just City and just handle this accordingly in an action or your stories.

thank you !


set initial/default screen params

I haven't figured out a way to do this yet.
Example use case:
import { TabNavigator, TabView } from 'react-navigation';
import Ionicons from 'react-native-vector-icons/Ionicons';
import Search from './Search';

const MyTabNavigator = TabNavigator({
  Search: {
    screen: Search,
    params: {
      iconName: 'ios-search-outline'
    }
}, {
  navigationOptions: {
    tabBar: ({ state }) => ({
      icon: ({ tintColor, focused }) => (<Ionicons name={state.params.iconName} color={tintColor} />)
    })
  },
  tabBarComponent: TabView.TabBarBottom
});

Explanation: if I am using default navigationOptions (0c99035) to create a generic handler for tabBar.icon, I would like to provide some initial/default screen params to the generic handler. in this simple example, i would define iconName as an initial screen param so that the tabBar.icon handler can get the correct icon to render.
Thoughts? or alternatives?

You could do this:
import { TabNavigator, TabView } from 'react-navigation';
import Ionicons from 'react-native-vector-icons/Ionicons';
import Search from './Search';

function routeNameToIcon(routeName) {
  switch (routeName) {
    case 'Search':  return 'ios-search-outline';
    default: return 'default-icon';
  }
}

const MyTabNavigator = TabNavigator({
  Search: {
    screen: Search,
}, {
  navigationOptions: {
    tabBar: ({ state }) => ({
      icon: ({ tintColor, focused }) => (<Ionicons name={routeNameToIcon(state.routeName)} color={tintColor} />)
    })
  },
  tabBarComponent: TabView.TabBarBottom
});

Closing for now but feel free to keep discussion going or open more specific issues

hi @ericvicenti, thanks for chiming in. yep that is exactly what my current solution is.
i would be interested in hearing more opinions about whether this is a useful feature to develop.
currently, the only way I am aware of to pass params is via the navigation prop which is injected into components, ie. this.props.navigation.navigate('ScreenName', { myProp: 'value'});. this allows myProp to be passed from one component to another component.
however, my use case presents a situation where no navigation has taken place; the tabBar.icon is utilized immediately on first render. in these cases, it would be nice to be able to define initial screen params.

@thurt Did you figure out a way to define the initial/default screen params? I'm trying to pass an initial param from launchOptions to the initial scene but I'm not sure how to do that.
I've created a new issue to address this directly #634 as well.
Thanks!


Example for restoring database from multiple .bak files

Hi Team,
We have multiple .bak files for database in storage account.
When in ssms i can select multiple files. How to put that in command line?
Regards,
Vishal

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

ID: cc04e819-4cfd-5b23-404b-8d4ed41afd21
Version Independent ID: d254a232-e05d-0d52-0e25-7e83866f12e6
Content: SQL Server Backup to URL - SQL Server
Content Source: docs/relational-databases/backup-restore/sql-server-backup-to-url.md
Product: sql
Technology: backup-restore
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@vishalaj1 -- Vishal, thank you for your feedback.  You may find answers here:

DBA Stack Exchange
Stack Overflow

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Drop table helper for new "drops" syntax

Also added methods to get MaterialParts by name or regex pattern

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


Add Play/Pause Audio Using EarPhones Feature

Hi, I want to work on this feature

Ok, go ahead

Already implemented

Yes.....I am extremely sorry.I totally forgot about it.

no problem


CHEBI:85621, please CHECK

Hi Gareth and Steve,
I need CHEBI:85621, 3-oxoalanine residue for a Rhea reaction so I would greatly appreciate it if you would CHECK this entry. The structure looks a little strange with a G attached to the *. I don't know if this has any significance.
Cheers,
Kristian

Hi Kristian,
Do you need the L isomer (as the structure shows) or the one with no stereochemistry specified? I have changed the name to "L-3-oxoalanine residue" so that it matches the structure, will create the corresponding residue with unspecified stereochemistry if you wish.
Cheers,
Gareth

Hi Gareth,
The L-isomer is just fine, so no need to create an additional entry.
Cheers,
Kristian

That's good! I'll close the ticket.
Cheers,
Gareth


add ssh-proxy properties for specifying allowed cipher,mac,kex algorithms

Signed-off-by: Fabio Berchtold<EMAIL_ADDRESS>

Thanks, @JamesClonk! Makes sense given the other PRs to the diego-ssh repo. Prioritizing for the team to review and pull in.
Best,
Eric


All the cities in a continent organised by largest population to smallest.

this wont get done, prioritizing other areas of the project.


stow: 2.2.0 -> 2.2.2

Motivation for this change
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

http://git.savannah.gnu.org/cgit/stow.git/tree/NEWS
CC @the-kenny @jgeerds

Merged as 8f7b525


Fix lang load timing

Addressing issue where some messages in the default language were not loading, and the keys were showing. I determined this was because the i18n locale was not set in the appropriate place. It was set during the creation of the languauge menu, and when the language was changed, but not on initial loading of the i18n for the default language and reloading the page with that information. This PR fixes that language.
I checked a few different configs and loaded the pages a few times to verify that this was the only solution required.

Question: is the language displayed supposed to return to default if you press the page refresh button? It currently returns to the default language, but I can't remember if it did that before I started changing things.

Question: is the language displayed supposed to return to default if you press the page refresh button? It currently returns to the default language, but I can't remember if it did that before I started changing things.

It has always done that (you may not have noticed since the default language was English), and I think it is fine. Refreshing the page to reset everything is a well understood usage pattern.


Theme and mode 404 when using minified/bundled js and workerPath

I'm using requirejs, as as such, all JS gets concatenated into a single file. I'm setting workerPath to the correct folder containing Ace, but theme and mode don't seem to get picked up. Even specifying paths for both have no effect.

Any thoughts on how to correctly get theme and mode working with a requirejs / concatenated / uglified / set up?
Relevant config:
    $scope.uiAceConfig =
      theme: 'chrome'
      mode: 'html'
      onLoad: $scope.aceLoaded
      workerPath: '/public/lib/ace-builds/src-min-noconflict'

Thanks!

+1

+1

+1

I'd say this is a big need for apps inside compiled deployments (crazy, right?). I had to get around this by using the CDN url for the workerPath
<div ui-ace="{
      workerPath: 'https://cdnjs.cloudflare.com/ajax/libs/ace/1.2.2',
      useWrapMode: 'true',
      showGutter: 'true',
      mode: 'json'
    }">

Is there any other way to solve this ?

This literally makes ui-ace useless for me.

+1

Has anyone found a usable workaround?

If you place the files where its expecting the files to be present then it might work (you have to copy all the files modes/themes)

if you are using
"../ace-builds/src-min-noconflict",
place
ace.require("ace/edit_session").EditSession.prototype.$startWorker = function(){}
before the function in which you are using ui-ace
if you are using
"../ace-builds/src-min-noconflict",
place
require("ace/edit_session").EditSession.prototype.$startWorker = function(){}
for example
(function () {
    'use strict';

    angular
        .module('app.template')
        .controller('TemplateController', TemplateController);

    TemplateController.$inject = [ ];

    // Quick-fix that allows to omit ACE problem with loading html and css workers
    ace.require("ace/edit_session").EditSession.prototype.$startWorker = function(){};

    // Here you will use ui-ace
    function TemplateController() {
        var vm = this;
    }
    }
})();

https://github.com/ajaxorg/ace/issues/732

+1

I found that I needed to set the properties as @lahdo mentioned:
ui-ace="{
       ...
       workerPath: '/.../ace-builds/src-min-noconflict',
       modePath: '/.../ace-builds/src-min-noconflict',
       themePath: '/.../ace-builds/src-min-noconflict',
       basePath: '/.../ace-builds/src-min-noconflict'
}"

But the ui-ace setOptions() function needs to be modified, too.  It's missing the ability to set all of these paths (I'm not sure why it isn't written more generically to do a set on all properties provided that aren't specifically handled in this function):
    var setOptions = function(acee, session, opts) {

      // sets the ace worker path, if running from concatenated
      // or minified source
      if (angular.isDefined(opts.workerPath)) {
        var config = window.ace.require('ace/config');
        config.set('workerPath', opts.workerPath);
      }
      if (angular.isDefined(opts.modePath)) {
        var config = window.ace.require('ace/config');
        config.set('modePath', opts.modePath);
      }
      if (angular.isDefined(opts.themePath)) {
        var config = window.ace.require('ace/config');
        config.set('themePath', opts.themePath);
      }
      if (angular.isDefined(opts.basePath)) {
        var config = window.ace.require('ace/config');
        config.set('basePath', opts.basePath);
      }