Compatibility with react-native-firebase

| Version     |  0.21.1  |
| Affected OS | Android |
| OS Version  | 7.0 |
Hi,
I'm trying to use this library and react-native-firebase in my project.
But when I try to compile, I get this error
* What went wrong:
Execution failed for task ':react-native-device-info:processReleaseResources'.
> Error: more than one library with package name 'com.google.android.gms.license'

If I uninstall any of the 2, then the other one works.
Does anyone know how to fix it?

Hey, did you check the troubleshooting section in the Readme?
On Mar 20, 2018 22:49, "Ricardo Favero"<EMAIL_ADDRESS>wrote:
| Version | 0.21.1 |
| Affected OS | Android |
| OS Version | 7.0 |
Hi,
I'm trying to use this library and react-native-firebase in my project.
But when I try to compile, I get this error

What went wrong:
Execution failed for task
':react-native-device-info:processReleaseResources'.> Error: more than
one library with package name 'com.google.android.gms.license'

Does anyone know how to fix it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rebeccahughes/react-native-device-info/issues/365, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASlQsBxBJmppvHVhomJ31GP9pdNz0Dkks5tgXlngaJpZM4SytTS
.

I'm running into the same issue.  I followed the troubleshooting to no avail.  I'm also use react-native-firebase
    compile(project(':react-native-device-info')) {
      exclude group: 'com.google.android.gms'    // this did not fix my issue
    }

Seeing the same issue, but am not using react-native-firebase. Tried adding the following to no avail:
    compile(project(':react-native-device-info')) {
        exclude group: 'com.google.android.gms'
    }

Add googlePlayServicesVersion = "xx.xxx" to your project gradle. For example:
ext {
    compileSdkVersion = 26
    buildToolsVersion = '26.0.1'
    googlePlayServicesVersion = "11.6.0"
}

@jurajkrivda Thanks so much for pointing me in the right direction, all I ended up needing to add was this line to my android/gradle.properties file:
googlePlayServicesVersion=11.0.4

I also didn't end up needing to exclude the com.google.android.gms group.

@CodyBrouwers This didn't seem to work for me...am i missing something?
I made the following changes:

googlePlayServicesVersion=11.6.0 in android/gradle.properties file
def googlePlayServicesVersion = project.googlePlayServicesVersion to my dependencies object in android/app/build.gradle file

@bdlee-1 maybe bad googlePlayServicesVersion?

@bdlee-1 Hmm not sure, try running cd android && ./gradlew clean to cleanup the previous build, then try building again.
Also I tried again with version 11.6.0 of googlePlayServicesVersion and it downloaded and installed that version, so maybe disregard what I put above about finding the correct version.

@CodyBrouwers @jurajkrivda
I was also using react-native-google-signin seem to be what was causing it to install v12.0.0
Seem to have got it working with 11.8.0 now
thanks for your help!

Thanks guys! Was pulling my hair out trying to figure this out :)
I have another package react-native-push-notification that has compile 'com.google.android.gms:play-services-gcm:+' and don't think there is a way to fix that. I think that dependency just needs to be updated.

@aligfl How did you update the dependency I am having the same problem and I already tried the other solutions mentioned. Thanks.

@freddiecabrera I simply added googlePlayServicesVersion=11.8.0 to gradle.properties and that did the trick for me.
Mind you, I had to remove other packages that were causing a similar issue though, maybe you're seeing the same issue? mind pasting the error?

@freddiecabrera I had to update the build.gradle file for some of the libraries in the node_modules folder
change this line compile 'com.google.android.gms:play-services-gcm:+' to be compile 'com.google.android.gms:play-services-gcm:11.8.0'

@bdlee-1 ditto for me. Had to update react-native-push-notification's gradle file as well.

What went wrong:
Execution failed for task ':react-native-google-signin:processReleaseResources'.

Error: more than one library with package name 'com.google.android.gms.license'

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

I fix the error  changing compile 'com.google.android.gms:play-services-auth:+' to compile 'com.google.android.gms:play-services-auth:11.6.0' on node_modules/react-native-google-signin/build.gradle

Hey folks, this is actually documented but hidden under Linking > Manual > Android:

@jurajkrivda @CodyBrouwers could you guys have a look and tell me if the documentation is clear enough, or if there's something to change? I'll link to this section of the manual from the Troubleshooting section.
And thank you all for this collaborative resolution :)

@aligfl I'm also using the react-native-push-notification dependency, and changed its build.gradle file. When someone else now tries to run the repo, the error will still persist due to a new npm install of the dependency.

I solved them by changing into node-modules/react-native-device-info/android/build.gradle
compile 'com.google.android.gms:play-services-gcm:11.8.0'
But now I have a more generic

What went wrong:
Execution failed for task ':app:processReleaseResources'.
Error: more than one library with package name 'com.google.android.gms.license'

How to solve this??
Thx

i think we need to update the google service version, previously i use 11.8.0 and cannot build, then i update my gms to 12.0.0 it solved,
if you using firebase or other module that need gms just update the version to 12.0.0

IF you're working with the react-native-push-notification dependency, feel free to use THIS forked project of it. Contains the changes mentioned in this issue.

This fixes it https://github.com/rebeccahughes/react-native-device-info/issues/365#issuecomment-374864471 for react-native-device-info.
Set yourcom.google.android.gms:play-services-gcm version like this in android/build.gradle:
ext {
    googlePlayServicesVersion = "11.8.0"
}

For react-native-push-notification PR is open and will be merged soon.

Hi, I am still having the same issue even though I have tried all the suggested fixes. Is anybody still getting this issue or have any other methods?

What went wrong:
Execution failed for task ':urbanairship-react-native:processReleaseResources'.

Error: more than one library with package name 'com.google.android.gms.license'

@dolo098  Is this issue solved?

cd android && ./gradlew app:dependencies --configuration compile
jot down this command it will tell you what version of Google play is used in all imported libraries. Open project in studio and  in all third party libraries replace
compile 'com.google.firebase:firebase-messaging:+' with specific version like this.
compile 'com.google.firebase:firebase-messaging:11.8.0'
you may be using other libraries not only fcm ,vison or whatever but rule of thumb is .....declare to use specific version of it it will make you life easy.
Thanks.

I follwed this post https://github.com/facebook/react-native/issues/18479#issuecomment-374849967
and it worked well for me, hope it helps someone else!

@jnrepo excellent! that fixes the issue with react-native-push-notification. Great find! Thanks!

Thank you all, guys.
@CodyBrouwers's solution solved the problem for me.

all I ended up needing to add was this line to my android/gradle.properties file:
googlePlayServicesVersion=11.0.4

I moved to PLayServices 12.0.0 (android/app/build.gradle) and I started having such issue
By downgrading back to 11.8.0 and doing the 2 things mentioned previoulsy:
add 'def googlePlayServicesVersion = project.googlePlayServicesVersion' to android/app/build.gradle
and add 'googlePlayServicesVersion=11.8.0' into gradle.properties
it worked fine.
I hope someone can help in getting this fixed soon into react-native-device-info so we can move to 12.0.0 playservices
Thank you All!!

The only thing that worked here is setting the settings below in android/build.gradle (the project level file) forcing in the app level build.gradle didnt work
In my case was the vision module, but it will work for others as well.
The thing is that when a project use module :+ as the version it will always get the latest version available, and google just released the version 12.0.0 so I got errors compiling 2 of my projects one was using react-native-camera with the vision the other is using firebase, I need to check this one tomorrow.
This is what worked for me
allprojects {
    repositories {
       configurations.all {
            resolutionStrategy {
                force 'com.google.android.gms:play-services-vision:11.8.0'
                //any other module you want to force here.

            }
        }
}

#366 was the same issue I think, worded differently.
Since I didn't experience this issue personally, I would really love if anyone could propose a PR to amend the README.md file to explain the problem, what causes it and how to get rid of it.
Any takers? 🙏

@CodyBrouwers fix worked for me as well. It wasn't working at first because support for that was only added in a recent package version, so I had to update to the latest release.

This did the trick for me with react-native-device-info:
allprojects {
    repositories {
        ...
        configurations.all {
            resolutionStrategy {
                force 'com.google.android.gms:play-services-gcm:11.6.0'
            }
        }
    }
}

And as i was using react-native-google-sign-in i had to set it like this:
allprojects {
    repositories {
        ...
        configurations.all {
            resolutionStrategy {
                force 'com.google.android.gms:play-services-gcm:11.6.0'
                force 'com.google.android.gms:play-services-auth:11.6.0'
            }
        }
    }
}

unable to solve this error:
> Task :react-native-device-info:verifyReleaseResources FAILED
Task ':react-native-device-info:verifyReleaseResources' is not up-to-date because:
  Task has failed previously.
All input files are considered out-of-date for incremental task ':react-native-device-info:verifyReleaseResources'.
Unable do incremental execution: full task run
QueuedCruncher is using /Users/alacret/Library/Android/sdk/build-tools/28.0.2/aapt

Shutdown finished in 0ms

:react-native-device-info:verifyReleaseResources (Thread[Task worker for ':' Thread 3,5,main]) completed. Took 0.498 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-device-info:verifyReleaseResources'.
> com.android.ide.common.process.ProcessException: Failed to execute aapt

* Try:
Run with --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':react-native-device-info:verifyReleaseResources'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:103)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:73)
        at org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101)
        at org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:91)
        at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
        at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:256)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:249)
        at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:238)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:663)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:597)
        at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
        at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: org.gradle.internal.UncheckedException: com.android.ide.common.process.ProcessException: Failed to execute aapt
        at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:63)
        at org.gradle.internal.UncheckedException.throwAsUncheckedException(UncheckedException.java:40)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:76)
        at org.gradle.api.internal.project.taskfactory.IncrementalTaskAction.doExecute(IncrementalTaskAction.java:50)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:124)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
        at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:113)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:95)
        ... 30 more
Caused by: com.android.ide.common.process.ProcessException: Failed to execute aapt
        at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:827)
        at com.android.build.gradle.tasks.VerifyLibraryResourcesTask.linkResources(VerifyLibraryResourcesTask.kt:206)
        at com.android.build.gradle.tasks.VerifyLibraryResourcesTask.compileAndVerifyResources(VerifyLibraryResourcesTask.kt:181)
        at com.android.build.gradle.tasks.VerifyLibraryResourcesTask.doFullTaskAction(VerifyLibraryResourcesTask.kt:129)
        at com.android.build.gradle.internal.tasks.IncrementalTask.taskAction(IncrementalTask.java:106)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
        ... 40 more
Caused by: java.util.concurrent.ExecutionException: com.android.ide.common.process.ProcessException: Error while executing process /Users/alacret/Library/Android/sdk/build-tools/28.0.2/aapt with arguments {package -f --no-crunch -I /Users/alacret/Library/Android/sdk/platforms/android-24/android.jar -M /Users/alacret/workspace/weedmatch-mobile/node_modules/react-native-device-info/android/build/intermediates/aapt_friendly_merged_manifests/release/processReleaseManifest/aapt/AndroidManifest.xml -S /Users/alacret/workspace/weedmatch-mobile/node_modules/react-native-device-info/android/build/intermediates/res/merged/release --non-constant-id -0 apk --no-version-vectors}
        at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:502)
        at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:481)
        at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:83)
        at com.android.builder.internal.aapt.AbstractAapt.link(AbstractAapt.java:34)
        at com.android.builder.core.AndroidBuilder.processResources(AndroidBuilder.java:823)
        ... 45 more
Caused by: com.android.ide.common.process.ProcessException: Error while executing process /Users/alacret/Library/Android/sdk/build-tools/28.0.2/aapt with arguments {package -f --no-crunch -I /Users/alacret/Library/Android/sdk/platforms/android-24/android.jar -M /Users/alacret/workspace/weedmatch-mobile/node_modules/react-native-device-info/android/build/intermediates/aapt_friendly_merged_manifests/release/processReleaseManifest/aapt/AndroidManifest.xml -S /Users/alacret/workspace/weedmatch-mobile/node_modules/react-native-device-info/android/build/intermediates/res/merged/release --non-constant-id -0 apk --no-version-vectors}
        at com.android.build.gradle.internal.process.GradleProcessResult.buildProcessException(GradleProcessResult.java:73)
        at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:48)
        at com.android.builder.internal.aapt.AbstractProcessExecutionAapt$1.onSuccess(AbstractProcessExecutionAapt.java:78)
        at com.android.builder.internal.aapt.AbstractProcessExecutionAapt$1.onSuccess(AbstractProcessExecutionAapt.java:74)
        at com.google.common.util.concurrent.Futures$CallbackListener.run(Futures.java:1374)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:399)
        at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:973)
        at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:821)
        at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:663)
        at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:48)
        at com.android.build.gradle.internal.process.GradleProcessExecutor$1.run(GradleProcessExecutor.java:58)
Caused by: org.gradle.process.internal.ExecException: Process 'command '/Users/alacret/Library/Android/sdk/build-tools/28.0.2/aapt'' finished with non-zero exit value 1
        at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:389)
        at com.android.build.gradle.internal.process.GradleProcessResult.assertNormalExitValue(GradleProcessResult.java:46)
        ... 9 more

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

tried:

project gradle:

ext{
    googlePlayServicesVersion="15.0.1"
}

app gradle
def googlePlayServicesVersion = project.googlePlayServicesVersion
gradle properties file:
googlePlayServicesVersion=15.0.1
Change the version directly in node_modules/react-native-device-info/android gradle file

None of this has work so far, this are my gradle files:
APP GRADLE:
android {
    compileSdkVersion 27
    buildToolsVersion '28.0.2'

    defaultConfig {
        applicationId ""
        minSdkVersion 16
        targetSdkVersion 27
        versionCode 15
        versionName "1.4.0"
        vectorDrawables.useSupportLibrary = true
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
...
dependencies {
    implementation project(':react-native-firebase')
    implementation "com.google.android.gms:play-services-base:15.0.1"
    implementation "com.google.firebase:firebase-core:15.0.2"
    implementation "com.google.firebase:firebase-messaging:15.0.2"
    implementation "com.google.firebase:firebase-auth:16.0.3"
    // implementation "com.google.firebase:firebase-notifications:15.0.2"
    implementation 'me.leolin:ShortcutBadger:1.1.21@aar'
    implementation project(':react-native-toast-native')
    implementation project(':react-native-spinkit')
    implementation project(':react-native-picker')
    implementation project(':react-native-image-crop-picker')
    implementation project(':react-native-i18n')
    implementation project(':react-native-fbsdk')
    implementation project(':react-native-device-info')
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:27.1.1"
    implementation "com.facebook.react:react-native:+"
}
}

PROJECT GRADLE
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        jcenter()
        google()
    }
    dependencies {
        classpath 'com.google.gms:google-services:3.2.1'
        classpath 'com.android.tools.build:gradle:3.2.0'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

ext{
    googlePlayServicesVersion="15.0.1"
}

allprojects {
    repositories {
        mavenLocal()
        jcenter()
        configurations.all {
            resolutionStrategy {
                force 'com.facebook.android:facebook-android-sdk:4.28.0'
                force 'com.google.android.gms:play-services-gcm:15.0.1'
            }
        }
        maven {
            url "https://maven.google.com"
        }
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            url "https://jitpack.io"
        }
        google()

    }
}

I had to delete everything and start from scratch ejecting the application, it was a version problem, i think that the support for the Build Tools 28, Google Services and Gradle Build Tools is not yet complete, this is my working configuration:
android/app/build.gradle
apply plugin: "com.android.application"

import com.android.build.OutputFile

/**
 * The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
 * and bundleReleaseJsAndAssets).
 * These basically call `react-native bundle` with the correct arguments during the Android build
 * cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
 * bundle directly from the development server. Below you can see all the possible configurations
 * and their defaults. If you decide to add a configuration block, make sure to add it before the
 * `apply from: "../../node_modules/react-native/react.gradle"` line.
 *
 * project.ext.react = [
 *   // the name of the generated asset file containing your JS bundle
 *   bundleAssetName: "index.android.bundle",
 *
 *   // the entry file for bundle generation
 *   entryFile: "index.android.js",
 *
 *   // whether to bundle JS and assets in debug mode
 *   bundleInDebug: false,
 *
 *   // whether to bundle JS and assets in release mode
 *   bundleInRelease: true,
 *
 *   // whether to bundle JS and assets in another build variant (if configured).
 *   // See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
 *   // The configuration property can be in the following formats
 *   //         'bundleIn${productFlavor}${buildType}'
 *   //         'bundleIn${buildType}'
 *   // bundleInFreeDebug: true,
 *   // bundleInPaidRelease: true,
 *   // bundleInBeta: true,
 *
 *   // whether to disable dev mode in custom build variants (by default only disabled in release)
 *   // for example: to disable dev mode in the staging build type (if configured)
 *   devDisabledInStaging: true,
 *   // The configuration property can be in the following formats
 *   //         'devDisabledIn${productFlavor}${buildType}'
 *   //         'devDisabledIn${buildType}'
 *
 *   // the root of your project, i.e. where "package.json" lives
 *   root: "../../",
 *
 *   // where to put the JS bundle asset in debug mode
 *   jsBundleDirDebug: "$buildDir/intermediates/assets/debug",
 *
 *   // where to put the JS bundle asset in release mode
 *   jsBundleDirRelease: "$buildDir/intermediates/assets/release",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in debug mode
 *   resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",
 *
 *   // where to put drawable resources / React Native assets, e.g. the ones you use via
 *   // require('./image.png')), in release mode
 *   resourcesDirRelease: "$buildDir/intermediates/res/merged/release",
 *
 *   // by default the gradle tasks are skipped if none of the JS files or assets change; this means
 *   // that we don't look at files in android/ or ios/ to determine whether the tasks are up to
 *   // date; if you have any other folders that you want to ignore for performance reasons (gradle
 *   // indexes the entire tree), add them here. Alternatively, if you have JS files in android/
 *   // for example, you might want to remove it from here.
 *   inputExcludes: ["android/**", "ios/**"],
 *
 *   // override which node gets called and with what additional arguments
 *   nodeExecutableAndArgs: ["node"],
 *
 *   // supply additional arguments to the packager
 *   extraPackagerArgs: []
 * ]
 */

project.ext.react = [
    entryFile: "index.js"
]

apply from: "../../node_modules/react-native/react.gradle"

/**
 * Set this to true to create two separate APKs instead of one:
 *   - An APK that only works on ARM devices
 *   - An APK that only works on x86 devices
 * The advantage is the size of the APK is reduced by about 4MB.
 * Upload all the APKs to the Play Store and people will download
 * the correct one based on the CPU architecture of their device.
 */
def enableSeparateBuildPerCPUArchitecture = false

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */
def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion rootProject.ext.compileSdkVersion
    buildToolsVersion rootProject.ext.buildToolsVersion

    defaultConfig {
        applicationId ""
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
        multiDexEnabled true
    }
    signingConfigs {
        release {
            if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
                storeFile file(MYAPP_RELEASE_STORE_FILE)
                storePassword MYAPP_RELEASE_STORE_PASSWORD
                keyAlias MYAPP_RELEASE_KEY_ALIAS
                keyPassword MYAPP_RELEASE_KEY_PASSWORD
            }
        }
    }
    splits {
        abi {
            reset()
            enable enableSeparateBuildPerCPUArchitecture
            universalApk false  // If true, also generate a universal APK
            include "armeabi-v7a", "x86"
        }
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
    }
    // applicationVariants are e.g. debug, release
    applicationVariants.all { variant ->
        variant.outputs.each { output ->
            // For each separate APK per architecture, set a unique version code as described here:
            // http://tools.android.com/tech-docs/new-build-system/user-guide/apk-splits
            def versionCodes = ["armeabi-v7a":1, "x86":2]
            def abi = output.getFilter(OutputFile.ABI)
            if (abi != null) {  // null for the universal-debug, universal-release variants
                output.versionCodeOverride =
                        versionCodes.get(abi) * 1048576 + defaultConfig.versionCode
            }
        }
    }
}

subprojects {
    project.configurations.all {
        afterEvaluate {project ->
            if (project.hasProperty("android")) {
                android {
                    compileSdkVersion rootProject.ext.compileSdkVersion
                    buildToolsVersion rootProject.ext.buildToolsVersion
                }
            }
        }
        resolutionStrategy.eachDependency { details ->
            if (details.requested.group == 'com.android.support'
                    && !details.requested.name.contains('multidex') ) {
                details.useVersion rootProject.ext.buildToolsVersion
            }
        }
    }
}

dependencies {
    implementation project(':react-native-firebase')
        implementation "com.google.android.gms:play-services-base:15.0.0"
        implementation "com.google.firebase:firebase-core:15.0.2"
        implementation "com.google.firebase:firebase-messaging:15.0.2"
        implementation 'me.leolin:ShortcutBadger:1.1.21@aar'
    implementation project(':react-native-toast-native')
    implementation project(':react-native-spinkit')
    implementation project(':react-native-picker')
    implementation project(':react-native-image-crop-picker')
    implementation project(':react-native-i18n')
    implementation project(':react-native-fbsdk')
    implementation project(':react-native-device-info')
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation "com.google.firebase:firebase-auth:16.0.3"
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply plugin: 'com.google.gms.google-services'

android/build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "27.0.3"
        minSdkVersion = 21
        compileSdkVersion = 27
        targetSdkVersion = 26
        supportLibVersion = "27.1.1"
    }
    repositories {
        mavenLocal()
        google()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
    }
    dependencies {
        classpath 'com.google.gms:google-services:3.2.1'
        classpath 'com.android.tools.build:gradle:3.1.2'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}
subprojects { subproject ->
    afterEvaluate{
        if((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
            android {
                compileSdkVersion rootProject.ext.compileSdkVersion
                buildToolsVersion rootProject.ext.buildToolsVersion
            }
        }
    }
}

allprojects {
    repositories {
        // Add jitpack repository (added by react-native-spinkit)
        maven { url "https://jitpack.io" }
        mavenLocal()
        google()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }

    }
}

task wrapper(type: Wrapper) {
    gradleVersion = '4.4'
    distributionUrl = distributionUrl.replace("bin", "all")
}

i think i finde my problem,,, im using react-native-maps and react-native-push-notification. in react native project. when i link bouth at sime time my app crash before start. according to documentation https://github.com/zo0r/react-native-push-notification play-service-gcm and firebase-messaging, prior to version 15 requires to have the same version number in order to work correctly at build time and at run time. To use a specific version: i change my build.gradle dependencis in react-native-push-notification.  from def firebaseVersion = project.hasProperty('firebaseVersion') ? project.firebaseVersion : DEFAULT_FIREBASE_MESSAGING_VERSION  to def firebaseVersion = project.hasProperty('firebaseVersion') ? project.firebaseVersion : '11.8.0' and i add i android/build.gradle  googlePlayServicesVersion = "11.8.0",, same version

@machour this should be closed - the whole react-native ecosystem moved to a consistent version specification style that eliminates these conflicts, and this module handles that style well (basically like this comment https://github.com/rebeccahughes/react-native-device-info/issues/365#issuecomment-374919093 - and other modules have all (or all currently) converting so these won't happen going forward and there's no action here)
A PR for the README to make sure people know to put the version in their app in an ext block and implement a gradle function safeExtGet to use it could be useful


Save images or videos in headless mode

Hey! I'm trying to use iGibson 2.0 on a headless server. My installation and everything went fine but I just wanted to know if there's any way i can save images or videos from the simulator (either robot's ego or 3rd person perspective). Sorry if this is a very naive question, I'm pretty new to this. Thanks!

Hi, definitely - if you just want to get them from the robot's perspective as you run simulation using the Environment APIs, you can simply get the observation returned by env.step(), pick out the camera image, and save that as an image using PIL.Image APIs.
If you want to dive deeper and be able to manipulate the camera outside the typical robotics environment context (e.g. no robot, no physics, just photos with a particular purpose) you can take a look at this example: https://github.com/StanfordVL/iGibson/blob/1f52c347210628cbab4d6cdf5a3b4945aa60d38f/igibson/utils/derivative_dataset/pipeline.py#L157-L189 (this is unmerged development code, but you can do this in your own code - it's just to give you an idea)
Essentially the simulator.renderer.render() function gives you the image as a numpy array. You can use PIL or cv2 to save that in your desired format.
For videos, you can either just save all your frames in a directory and run ffmpeg offline later to combine them into a video, or you can use cv2's VideoWriter to write a video on the fly. I'd recommend ffmpeg.
I'm closing this now but feel free to reopen if you have more questions.


Ilrepack deps

remove

Refers to: build/MSBuildExtensionPackage.targets:35 in 0b49e50. [](commit_id = 0b49e508bd39c4299a83b98555444ece3d1e5130, deletion_comment = False)


fix: add missing dep on google-auth-library

We use this at runtime.
Ref: https://github.com/googleapis/nodejs-logging-bunyan/issues/277

The error system test needed a kick to pass. I this there still a spurious flake in there 😭.
Not holding back this PR tho.


GitHub always returns 401 bad credentials

Hi! Trying to import GitHub resources. Any idea what I'm doing wrong? I created a PAT with all permissions.
% GITHUB_TOKEN="ghp_xxx" terraformer import github --resources=members,organization_blocks,organization_projects,organization_webhooks,repositories,teams,user_ssh_keys --owner="iron-security"
2021/09/16 09:39:37 github importing organization iron-security
2021/09/16 09:39:37 github importing... members
2021/09/16 09:39:38 GET https://api.github.com/orgs/iron-security/members?per_page=100: 401 Bad credentials []
2021/09/16 09:39:38 github done importing members
2021/09/16 09:39:38 github importing... organization_blocks
2021/09/16 09:39:38 GET https://api.github.com/orgs/iron-security/blocks?per_page=100: 401 Bad credentials []
2021/09/16 09:39:38 github done importing organization_blocks
2021/09/16 09:39:38 github importing... organization_projects
2021/09/16 09:39:38 GET https://api.github.com/orgs/iron-security/projects?per_page=100: 401 Bad credentials []
2021/09/16 09:39:38 github done importing organization_projects
2021/09/16 09:39:38 github importing... organization_webhooks
2021/09/16 09:39:38 GET https://api.github.com/orgs/iron-security/hooks?per_page=100: 401 Bad credentials []
2021/09/16 09:39:38 github done importing organization_webhooks
2021/09/16 09:39:38 github importing... repositories
2021/09/16 09:39:39 GET https://api.github.com/orgs/iron-security/repos?per_page=100: 401 Bad credentials []
2021/09/16 09:39:39 github done importing repositories
2021/09/16 09:39:39 github importing... teams
2021/09/16 09:39:39 GET https://api.github.com/orgs/iron-security/teams?per_page=1: 401 Bad credentials []
2021/09/16 09:39:39 github done importing teams
2021/09/16 09:39:39 github importing... user_ssh_keys
2021/09/16 09:39:39 GET https://api.github.com/user/keys?per_page=100: 401 Bad credentials []
...

Seems to work if I use --token=xxx, but not if using the GITHUB_TOKEN env variable.

up ?

up


Add docs for user management and invitations (#3837)

Summary
Details:

Add conceptual docs on projects, document how to create new projects, because I was there
Add role requirements to how-to prereqs
Clarify one role per project
Rewrite adding users to describe invitations
Undo excessive prettier formatting
Update docs/docs/how-to/create_project.md
Switch naming from Stacklok (vendor) to Minder (project) in documentation where I missed it.

Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[x] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.231% (-0.004%) from 54.235%
when pulling 77dfd47a60a312e976e1712488dac3dabd100d2c on 3795-add-docs-for-user-management-and-invitations
into ab3988568f02368a8acce1f654785822cc54640a on main.


Azure complains about not havning a clustered index on the NotFoundRequests table

Added ExexuteScalar to DB layer.
Added clustered index to NotFoundRequests table, Azure complains about not having one.
Added using to DataSet, performance warning in CA.
I did these changes on an older version, before GitHub. So please double check.

Thanks, we'll look into this, and see if we can merge it.

PR merged, will be part of next release (expected in a week or so) when we add support for 410 Deleted status on urls.


feat: linter and formatter

Closes https://github.com/weaviate/weaviate-javascript-client/issues/124
Closes https://github.com/weaviate/weaviate-javascript-client/issues/125
Adds eslint and prettier with TypeScript plugins. All configuration is adopted from https://github.com/stripe/stripe-node with some smaller modifications (e.g. changing errors to warnings, personal format preferences). Fixed all issues given by the linter, but there are still 57 warnings left (besides use of any).
This pull request also moves most of the source code into src/ for better separation of project artifacts (https://github.com/weaviate/weaviate-javascript-client/commit/bbdf28a952e42248d8d8e89938b25ce8ec592201).
@dirkkul - can you assist with the CI and precommit integration? I can add it if I get some pointers 🙂
@parkerduckworth - I just noticed the another repo (https://github.com/weaviate/typescript-client) you created, but what's the purpose of this when this repo is now also TypeScript?

Hey @mloenow , thanks for this contribution!
We just introduced the typescript client repo today, and will soon archive this project. Can you target your changes to the new project instead?
The head of the default branch is exactly the same as that of this repository, so it should be simple.
Sorry for the hassle, you caught us before we had a chance to update the README here. (Which I am about to do now)
Also, I will create a copy of each of these issues you are targeting in the new repo.

The head of the default branch is exactly the same as that of this repository

I just realized this is no longer true, but the changes made since this was true are minimal.

I think I managed to recreate it with some cherry picking. Closing this one.


Request for option to suppress warning associated with #1

May I please request a package option that suppresses the warning associated with ho-tex/hypdoc/issues/1 related to the loading of hyperref? Give that hypdoc is loaded by doc and ltxdoc I don't know if this is possible. I understand that the warning is harmless but it would be nice to not have any warnings in general use when a document is successfully "compiled."

Well hypdoc can't know if the compilation was successful. If you loaded  hyperref previously with different options something could be missing.  The best would be if you wouldn't load hyperref manually.

I am not loading hyperref manually. It is being loaded by tcolorbox's documentation library. I need hypdoc to make page numbers in my Change History hyperlinks. Perhaps just changing the message text so it doesn't show up in the log or console as an actual "Warning" would be easier.

medium (or even short) term, if we move hyperref to the new package option handler in the format, option clashes should mostly be a thing of the past.

medium (or even short) term, if we move hyperref to the new package option handler in the format, option clashes should mostly be a thing of the past.

Yes, but it wouldn't solve this problem: you would then get warnings from the keyval handler that there is a try to load hyperref again with a load-only option (hyperindex=false).
Imho the best here currently is to load tcolorbox later.
\AddToHook{begindocument/before}{\usepackage[listings,documentation]{tcolorbox}}

I was wondering whether or not a hook solution might be appropriate, but I wasn't sure where it would have to go. I've been studying the source code for dot/ltxdoc, hypdoc, and tcolorbox's documentation and the interplay is rather complex.

Or redirect that warning to info, rather than suppress it.

May I please request a package option that suppresses the warning associated with ho-tex/hypdoc/issues/1 related to the loading of hyperref?

@heafnerj

Currently: a package warning is raised
Your (original) proposal: a package option to suppress the warning
Mine: a package option to redirect warning to info (\PackageInfo{<pkg>}{<msg>}) which is ignored by some LaTeX editors' log analyzers.

Ah yes. That's precisely what I meant in the last sentence of my initial post. I didn't know the correct terms to use. That would certainly address my concern.


Improve UI flow for adding cross references.

Why: double actions required when inserting new cite
What: auto open reference selector when inserting new cite as proposed in #374

Merci.


HTTP Server: Set session ID cookie

On HTTP server we have to set session (ssid) cookie.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie


Document that missed_frame_build_budget_count is misleading

Fixes https://github.com/flutter/flutter/issues/109745

test-exempt: docs only (with minor code reformatting)


Kiki P1.5 - Extra padding at bottom of instruction set

Right now, the [Less^] button often encroaches on the last line of an instruction.  Can we add just a .25em or so to make sure it clears?

@kiki-lee can you add a screenshot?

Closing because this will be part of the general tutorial redesign


Add inline / stacked varients to radios component

This PR:

makes the default example an inline variant as it's a yes / no question
adds a stacked variant
adds associated content to explain when to use

It's been usable for some time but not documented in the Design System.

You can preview this change here:
Built with commit 6913af4c209c7bad89388d653e619457ca149d66
https://deploy-preview-265--govuk-design-system-preview.netlify.com

Merged, thanks


Updated way cooler background comment

We definitely support image backgrounds, looks like this comment slipped through the cracks.

Coverage remained the same at 57.795% when pulling 7ca07cf210af828d06d98b9006ca0af9e4bb37b8 on lua-comment-update into 2130d4677947c5bedfe2d021b6da364bc494630b on master.


Multiple issues with species.name_usage(data='vernacularNames')

I noticed a few issues when trying to do species.name_usage(key=1, language="FRENCH", data='vernacularNames') (example from the documentation, I just changed the key to get some results).

Doc issue: there's no mention of the possible values for languages ("FRENCH"? "FR"? "fr"? ,"fra"?, ...). We should ideally list the possible values or link to an existing standard.
The documentation mentions "english" is the default language, but species.name_usage(key=1, data='vernacularNames') returns data in 17 different languages.
species.name_usage(key=1, language="FRENCH", data='vernacularNames') also returns vernacular names in the 17 languages (the parameter seems ignored).

According to GBIF's API documentation, the vernacularName endpoint doesn't support the LANGUAGE parameter.
We can either:

Drop this example from the documentation, and specify which options of name_usage() accept the LANGUAGE parameter.
Implement language filtering in the function, on GBIF's response. In theory, we should implement pagination first (in case there are more than 1000 results returned, and the requested language appears on a page > 1).

Thanks. I've opened an issue in the gbif forum  https://discourse.gbif.org/t/language-and-the-species-api/2188

Thanks!
The last column of the table "Working with Name Usages" at https://www.gbif.org/developer/species gives information on which endpoint accepts which parameter. Maybe we should make sure pygbif documentation is in sync (or just point users there, to avoid duplication information)?

Right. It's not that much information though, so I think we can point out what routes language works with. And we should make sure to tell users how to specify language. In that forum thread Matt said:

Enumeration for all ISO 639-1 language codes using 2 lower case letters. The enumeration maps to 3 letter codes and Locales.

so language expects a 2 letter iso code, e..g.,
https://api.gbif.org/v1/species/5231190?language=de


fix issue HAWQ-1656 by hardcode installation procedure for bison

This PR is to fix issue
https://issues.apache.org/jira/browse/HAWQ-1656

LGTM +1

+1

any idea when this will be merged down?

@eschizoid This already been merged to master, please check.

Since this has already been merged, can someone with commit access close this PR please? @lavjain?

@ginobiliwang Please close this PR as only the person who opened the request can close it.


How should I install tracing and persist the data to Elasticsearch  whih IstioOperator

Now I install the tracing image as all-in-one, and the data is stored in the pod. How can I ensure the data is persistent?
install-tracing.yaml:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  addonComponents:
    tracing:
      enabled: true

istioctl manifest apply -f  install-tracing.yaml

maybe you can try this:
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  addonComponents:
    tracing:
      enabled: true
      spec:
        persist: true
        storageClassName: "xxx"

more  config details about tracing is in manifests/istio-telemetry/tracing/values.yaml.
I haven't apply install-tracing.yaml actually,  only read the definition of ExternalComponentSpec in istio.io/api/operator/v1alpha1/component.pb.go

@fujianan I haven't used the IstioOperator yet, but the instructions here (option 1b) should still apply in terms of the configuration options that need to be set.

Closing for now, please continue on discuss.istio.io if needed.


Simplify usage of CLI

What feature do you want to see added?
The CLI interface has too much parameter and we mix action and option.
I would suggest to have 1st grade command like
plugin-modernizer list
plugin-modernizer dry-run
plugin-modernizer run
plugin-modernizer fetch-metadata
plugin-modernizer validate
etc
This issue can be implemented in several PR
Upstream changes
No response

Partially implemented by https://github.com/jenkins-infra/plugin-modernizer-tool/pull/423
Need cleanup with option


Xamarin and Xeeny

Hi ,
First of all , this is a fantastic solution . I tried to use for xamarin (Android - Windows) communication. It almost worked. I can connect from adnroid (Tcp and http) to a windows host , but the methode call does not work. When i call a function from the client it will run on the server , but never return on the client and it will be freez.
I used " async await " methode call on xamarin.
Did you try it ever ?
Thank you ,
Karesz

yes It is tested on Android and Windows, could you please post your code


[ANNOUCEMENT] Bareflank Community Call - 3pm UTC on 6/12/2020

AIS will be holding a Bareflank Community Call at 3pm UTC on 6/12/2020 via Zoom. Or goal with the community call is to:

Provide users with an opportunity to ask questions and meet the team.
Learn more about the future of the Bareflank projects including the hypervisor, Boxy/MicroV, the BSL, PAL and the Standalone C++ library.

If you have a topic that you would like to discuss, please add it to this issue.  As we get closer to the call, I will post the Zoom info as well as draft a rough agenda based on the feedback we get here. Everyone is welcome to join and add items to the agenda.

The biggest thing that I would like to see talked about during the call are the changes coming to the hypevisor and MicroV repos based on the conversations in the Bareflank 3.0 issue. This includes the addition of the microkernel, the removal of some of the APIs, how we plan to support Libc++ (for those who really want this) as well as other languages in the VMM like Rust and Python, etc...

AMD and maybe even ARM support is another topic I think we should discuss.

@rianquinn AMD would be very interesting :) 3mdeb will definitely participate.

@rianquinn AMD would be very interesting :) 3mdeb will definitely participate.

Looking forward to seeing you there.

We should probably also talk about some of the Xen work we are doing, and our plans for how we plan to open source it (hopefully with the Xen community). There will likely be a larger discussion on this at the Xen Summit.

Ok, based on a bunch of feedback that we have gotten, this is the agenda for next week. Feel free to continue to add to this list if you would like something else to be discussed

[ ] Introductions

How are you using the project?

[ ] Microkernel Architecture
[ ] Separating the loader/kernel from the virtualization extensions library

Preference for Bareflank/hypervisor

[ ] Plans for Boxy/MicroV

Xen Hypercall Support
Working with the Xen Community

[ ] PAL
[ ] AMD/ARM Support
[ ] AUTOSAR Support

Here is the Zoom information for tomorrow's meeting
Rian Quinn is inviting you to a scheduled ZoomGov meeting.
Topic: Bareflank Community Call
Time: This is a recurring meeting Meet anytime
Join ZoomGov Meeting
https://ainfosec.zoomgov.com/j/1600996390?pwd=SUpxK1d1SDdYQWFrLzN0Ni9zOERSZz09
Meeting ID:<PHONE_NUMBER>
Password: 068712
One tap mobile
+16692545252,,1600996390#,,1#,068712# US (San Jose)
+16468287666,,1600996390#,,1#,068712# US (New York)
Dial by your location
+1<PHONE_NUMBER> US (San Jose)
+1<PHONE_NUMBER> US (New York)
Meeting ID:<PHONE_NUMBER>
Password: 068712
Find your local number: https://ainfosec.zoomgov.com/u/abWobTnADy

Thanks everyone for a great Community Call. If you have any questions between now and our next call in 3 months, let us know.


Perspective not corrected

I checked out your code, adapted to my purposes, and noticed that the perspective doesn't seem to be corrected in the vertex shader. The lines further away from camera are indeed getting thinner. I then cloned your repo, played a bit with the view and projection matrices, and noticed that it does the same thing. Any idea what's going on and how to correct for perspective and have lines with constant width?

Also, my code is here https://github.com/skrat/webgl-line-rendering

All right in case anyone ever needs this:
// vertex shader
float t = u_thickness*currentProjected;

// fragment, if you do your own anti-aliasing in fragment shader
float t = u_thickness/gl_FragCoord.w;


Make Sonos a platform rather than an accessory

Replaces the Sonos accessory with a Platform that will pick up and set up all Sonos boxes on the network automatically. Previously the Sonos accessory code would pick up only one of the Sonos boxes in an unpredictable way.

I think this is the correct approach. I will try this at home today!

I added a missing line of code. Should actually work now!

Newbie here. I have Sonos working as an accessory but trying to convert to a platform
I have added the platform info into the config file for sonos. I am not sure how I create a sonos.js, sonos platform handler and delete as an accessory. Is that down by placing all three sets of code into the config file of do I do that somewhere else thru terminal commands?
Sorry about the newbie simple questions

Newbie here. I have Sonos working as an accessory but trying to convert to a platform
I have added the platform info into the config file for sonos. I am not sure how I create a sonos.js, sonos platform handler and delete as an accessory. Is that down by placing all three sets of code into the config file of do I do that somewhere else thru terminal commands?
Sorry about the newbie simple questions


Cuda Version

Hi, great work!
How to enable cuda because I found:
if self.config.use_cuda:
try:
from mamba_ssm.ops.selective_scan_interface import selective_scan_fn # I did not find mamba_ssm in this repo
self.selective_scan_cuda = selective_scan_fn
except ImportError:
print("Failed to import mamba_ssm. Falling back to mamba.py.")
self.config.use_cuda = False
Looking forward to your response.
Thanks !

Hello, thanks!
To enable the CUDA version you have to set use_cuda to True when creating a MambaConfig.
Make sure you have installed in CUDA version before doing so (https://github.com/state-spaces/mamba/)

Thanks for reply.
Is there any performance discrepancy with and without using CUDA version ?

Yes, that's the first graph on the README ;) There is also a detailed section also on the README : https://github.com/alxndrTL/mamba.py?tab=readme-ov-file#performances
Note also that memory consumption is considerably higher with the non CUDA version (having fused operations really helps to manage memory efficiently).
Hope this helps.

Thanks!!! Have you tested other metrics except for Time? For example, accuracy

Memory is to be tested precisely.
As for accuracy, of course both versions are numerically equivalent.


Configure Dependabot to update Cargo and GitHub Action dependencies

Description of change
This change means we'll pick up new dependency updates on a regular basis for both crate dependencies in Mountpoint as well as our CI.
Relevant issues:

Closes #268

Tested in fork: https://github.com/dannycjones/mountpoint-s3/pulls?q=is%3Apr+is%3Aclosed+author%3Aapp%2Fdependabot
Does this change impact existing behavior?
No change to Mountpoint itself.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

CI is giving this error - "Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/opt/actions-runner/_work/mountpoint-s3/mountpoint-s3/.github/actions/install-dependencies'. Did you forget to run actions/checkout before running your local action?"
It is looking right as per the example given by gihub for dependabot.yml. I am not sure about the issue here.

I originally created the branch on an old commit, so integration tests was searching for a file that didn't exist. Re-base should fix it.


Could not run 'c10d::allreduce_' with arguments from the 'Meta' backend.

I try to start a large version of the model using docker:
docker run -p 10249:80 -e RUST_BACKTRACE=full  -e FLASH_ATTENTION=1 -e CUDA_VISIBLE_DEVICES=4,7 --privileged  --security-opt="seccomp=unconfined" -v /download:/data ghcr.io/huggingface/text-generation-inference:0.5 --model-id /data/llama-13b-hf --num-shard 2  --max-total-tokens 2048
can be initialized
Details

2023-04-18T08:00:20.891953Z  INFO text_generation_launcher: Args { model_id: "/data/llama-13b-hf", revision: None, sharded: None, num_shard: Some(2), quantize: false, max_concurrent_requests: 128, max_best_of: 2, max_stop_sequences: 4, max_input_length: 1000, max_total_tokens: 2048, max_batch_size: 32, max_waiting_tokens: 20, port: 80, shard_uds_path: "/tmp/text-generation-server", master_addr: "localhost", master_port: 29500, huggingface_hub_cache: Some("/data"), weights_cache_override: None, disable_custom_kernels: false, json_output: false, otlp_endpoint: None, cors_allow_origin: [], watermark_gamma: None, watermark_delta: None }
2023-04-18T08:00:20.891982Z  INFO text_generation_launcher: Sharding model on 2 processes
2023-04-18T08:00:20.892328Z  INFO text_generation_launcher: Starting shard 0
2023-04-18T08:00:20.892328Z  INFO text_generation_launcher: Starting shard 1
2023-04-18T08:00:26.396665Z  INFO text_generation_launcher: Shard 0 ready in 5.503382395s
2023-04-18T08:00:26.396665Z  INFO text_generation_launcher: Shard 1 ready in 5.503381293s
2023-04-18T08:00:26.495656Z  INFO text_generation_launcher: Starting Webserver
2023-04-18T08:00:27.467600Z  WARN text_generation_router: router/src/main.rs:134: no pipeline tag found for model /data/llama-13b-hf
2023-04-18T08:00:27.472098Z  INFO text_generation_router: router/src/main.rs:149: Connected

but an error occurred when calling
2023-04-18T08:00:33.236816Z ERROR shard-manager: text_generation_launcher: "Method Prefill encountered an error.
Traceback (most recent call last):
  File \"/opt/miniconda/envs/text-generation/bin/text-generation-server\", line 8, in <module>
    sys.exit(app())
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/typer/main.py\", line 311, in __call__
    return get_command(self)(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/click/core.py\", line 1130, in __call__
    return self.main(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/typer/core.py\", line 778, in main
    return _main(
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/typer/core.py\", line 216, in _main
    rv = self.invoke(ctx)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/click/core.py\", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/click/core.py\", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/click/core.py\", line 760, in invoke
    return __callback(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/typer/main.py\", line 683, in wrapper
    return callback(**use_params)  # type: ignore
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/cli.py\", line 55, in serve
    server.serve(model_id, revision, sharded, quantize, uds_path)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/server.py\", line 135, in serve
    asyncio.run(serve_inner(model_id, revision, sharded, quantize))
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/asyncio/runners.py\", line 44, in run
    return loop.run_until_complete(main)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/asyncio/base_events.py\", line 634, in run_until_complete
    self.run_forever()
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/asyncio/base_events.py\", line 601, in run_forever
    self._run_once()
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/asyncio/base_events.py\", line 1905, in _run_once
    handle._run()
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/asyncio/events.py\", line 80, in _run
    self._context.run(self._callback, *self._args)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/grpc_interceptor/server.py\", line 153, in invoke_intercept_method
    return await self.intercept(
> File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/interceptor.py\", line 20, in intercept
    return await response
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py\", line 82, in _unary_interceptor
    raise error
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py\", line 73, in _unary_interceptor
    return await behavior(request_or_iterator, context)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/server.py\", line 46, in Prefill
    generations, next_batch = self.model.generate_token(batch)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/contextlib.py\", line 79, in inner
    return func(*args, **kwds)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/models/flash_causal_lm.py\", line 278, in generate_token
    out, present = self.forward(
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/models/flash_causal_lm.py\", line 262, in forward
    return self.model.forward(
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 607, in forward
    hidden_states, present = self.model(
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/torch/nn/modules/module.py\", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 523, in forward
    hidden_states = self.embed_tokens(input_ids)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/torch/nn/modules/module.py\", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 221, in forward
    torch.distributed.all_reduce(out, group=self.process_group)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/torch/distributed/distributed_c10d.py\", line 1436, in wrapper
    return func(*args, **kwargs)
  File \"/opt/miniconda/envs/text-generation/lib/python3.9/site-packages/torch/distributed/distributed_c10d.py\", line 1687, in all_reduce
    work = group.allreduce([tensor], opts)
NotImplementedError: Could not run 'c10d::allreduce_' with arguments from the 'Meta' backend. This could be because the operator doesn't exist for this backend, or was omitted during the selective/custom build process (if using custom build). If you are a Facebook employee using PyTorch on mobile, please visit https://fburl.com/ptmfixes for possible resolutions. 'c10d::allreduce_' is only available for these backends: [CPU, CUDA, SparseCPU, SparseCUDA, BackendSelect, Python, FuncTorchDynamicLayerBackMode, Functionalize, Named, Conjugate, Negative, ZeroTensor, ADInplaceOrView, AutogradOther, AutogradCPU, AutogradCUDA, AutogradXLA, AutogradMPS, AutogradXPU, AutogradHPU, AutogradLazy, AutogradMeta, Tracer, AutocastCPU, AutocastCUDA, FuncTorchBatched, FuncTorchVmapMode, Batched, VmapMode, FuncTorchGradWrapper, PythonTLSSnapshot, FuncTorchDynamicLayerFrontMode, PythonDispatcher].

same error here

I think maybe the llama weights you are trying to load do not have the correct layout. Are you sure they are hf compatible?

Yes, I can do inference with transformers and accelerate

I think maybe the llama weights you are trying to load do not have the correct layout. Are you sure they are hf compatible?
I transfer the llama weights with this file and find the same bug.
https://github.com/huggingface/transformers/blob/main/src/transformers/models/llama/convert_llama_weights_to_hf.py

same problem with bigscience/bloomz-mt


Add username in event

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

GitHub release
v1.1.0

Your semantic-release bot :package::rocket:


Support client tests with podman

Closes #232
Use query that is compatible with both docker and podman to check
example client test results.
Signed-off-by: Steven Royer<EMAIL_ADDRESS>

Case when a test fails:
++ docker-compose ps
++ grep example-network-client
++ awk '{print $1}'
+ NETWORK_CLIENT_NAME=integration_example-network-client_1
++ docker inspect --format '{{.State.ExitCode}}' integration_example-network-client_1
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
+ NETWORK_CLIENT_RC=1
+ '[' 1 '!=' 0 ']'
+ echo 'example-network-client failed:'
example-network-client failed:
+ docker logs integration_example-network-client_1
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
-------------- GetFeature --------------
Traceback (most recent call last):
  File "/grpc-1.14.x/examples/python/route_guide/route_guide_client.py", line 119, in <module>
    run()
  File "/grpc-1.14.x/examples/python/route_guide/route_guide_client.py", line 109, in run
    guide_get_feature(stub)
  File "/grpc-1.14.x/examples/python/route_guide/route_guide_client.py", line 46, in guide_get_feature
    guide_get_one_feature(stub,
  File "/grpc-1.14.x/examples/python/route_guide/route_guide_client.py", line 34, in guide_get_one_feature
    feature = stub.GetFeature(point)
  File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 946, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/local/lib/python3.10/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
    raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
	status = StatusCode.UNAVAILABLE
	details = "failed to connect to all addresses; last error: UNKNOWN: Failed to connect to remote host: Connection refused"
	debug_error_string = "UNKNOWN:Failed to pick subchannel {created_time:"2022-08-01T19:59:20.415073585+00:00", children:[UNKNOWN:failed to connect to all addresses; last error: UNKNOWN: Failed to connect to remote host: Connection refused {grpc_status:14, created_time:"2022-08-01T19:59:20.415068582+00:00"}]}"
>
+ exit 1

Case when tests pass:
++ docker-compose ps
++ awk '{print $1}'
++ grep example-network-client
+ NETWORK_CLIENT_NAME=integration-example-network-client-1
++ docker inspect --format '{{.State.ExitCode}}' integration-example-network-client-1
+ NETWORK_CLIENT_RC=0
+ '[' 0 '!=' 0 ']'
++ docker-compose ps
++ grep example-network-client
++ awk '{print $1}'
+ STORAGE_CLIENT_NAME=integration-example-network-client-1
++ docker inspect --format '{{.State.ExitCode}}' integration-example-network-client-1
+ STORAGE_CLIENT_RC=0
+ '[' 0 '!=' 0 ']'


Got "invalid response status 403" when building docker image

What's your CLI version?
1.4.3
Description & steps to reproduce
On some machines, using ImageBuildSpec to build images fails with the following error:
There was an error validating Starlark code
Error while validating final environment of script
	Caused by: Failed to build the required image 'foo'.
	Caused by: Image build for 'foo' failed with the following output:
{"id":"moby.buildkit.trace","aux":"Cm8KR3NoYTI1NjpkOGU1MDU3NjEyOWVlYjZjMDg2OGNiZjhhNjY2M2I4ZjZiZjYyYjI2MzRlNTI3M2VmN2Y5NzU3ODgxYWQ0MDdkGiRbaW50ZXJuYWxdIGxvYWQgcmVtb3RlIGJ1aWxkIGNvbnRleHQ="}
{"id":"moby.buildkit.trace","aux":"Cn0KR3NoYTI1NjpkOGU1MDU3NjEyOWVlYjZjMDg2OGNiZjhhNjY2M2I4ZjZiZjYyYjI2MzRlNTI3M2VmN2Y5NzU3ODgxYWQ0MDdkGiRbaW50ZXJuYWxdIGxvYWQgcmVtb3RlIGJ1aWxkIGNvbnRleHQqDAjkoZa7BhCZ+YmOAg=="}
{"id":"moby.buildkit.trace","aux":"CqgBCkdzaGEyNTY6ZDhlNTA1NzYxMjllZWI2YzA4NjhjYmY4YTY2NjNiOGY2YmY2MmIyNjM0ZTUyNzNlZjdmOTc1Nzg4MWFkNDA3ZBokW2ludGVybmFsXSBsb2FkIHJlbW90ZSBidWlsZCBjb250ZXh0KgwI5KGWuwYQmfmJjgIyDAjkoZa7BhDWv4GsAjobaW52YWxpZCByZXNwb25zZSBzdGF0dXMgNDAz"}
{"errorDetail":{"message":"failed to read downloaded context: failed to load cache key: invalid response status 403"},"error":"failed to read downloaded context: failed to load cache key: invalid response status 403"}
 --- at /home/circleci/project/container-engine-lib/lib/backend_impls/docker/docker_manager/docker_manager.go:1478 (DockerManager.BuildImage) ---
Container images used in this run:
> foo - locally built
Error encountered running Starlark code.

This behaviour can be reproduced with the following script:
#!/usr/bin/env bash

package_dir=error403

mkdir -p $package_dir

# Any dockerfile will do
cat <<EOF > $package_dir/Dockerfile
FROM badouralix/curl-jq:latest
EOF

# Needed for this to be a valid Kurtosis package
echo 'name: "github.com/foo/bar"' > $package_dir/kurtosis.yml

# This is the script that triggers the error
cat <<EOF > $package_dir/main.star
def run(plan, args={}):
    plan.add_service(
        "foo",
        config=ServiceConfig(
            image=ImageBuildSpec(
                image_name="foo",
                build_context_dir=".",
            ),
            entrypoint=["sleep", "99999"],
            description="Triggering 403 error",
        ),
    )
EOF

echo "Created Kurtosis package"

# This fails
kurtosis run --enclave error403 $package_dir

echo "Ran Kurtosis package. Cleaning up..."

# Clean up enclave, images, and package
kurtosis enclave rm -f error403
docker rmi foo
rm -rf error403

Building the image manually with docker, which causes the build to be skipped in Kurtosis, avoids the issue.
Desired behavior
I expected the image to be built
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
CLI: the Command Line Interface

Hey @MegaRedHand ! What machine are you running on?

Also getting this error on macbook pro m1
Darwin Samuels-MacBook-Pro.local 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000 arm64

Might be related to https://github.com/moby/moby/issues/47717

Turning off the Docker Desktop option "Use containerd for pulling and storing images" seems to fix this, as per https://github.com/pulumi/pulumi-docker/issues/967

Yep that fixed it for me. Would be nice if there was a way to disable this feature on a per-project basis though.

Thanks for the find @MegaRedHand - I had that option off and image builds were working but when I turn it on it stops working.


Routes order

Is there a reason why static routes are checked before any non-static ones?
The question is related to this sample: ( $directoryPath is the PodePath)
# Start Pode server
Start-PodeServer -ScriptBlock {

    Add-PodeEndpoint -Address localhost -Port 8080 -Protocol Http -Default
   Add-PodeRoute -Method Get -Path '/LICENSE.txt' -ScriptBlock {
        $value=@"
Don't be kidding. Nobody will believe that you want to read this legalise nonsense.
I want to be kind; this is a summary of the content:

Nothing to report :D
"@
        Write-PodeTextResponse -Value $value
    }
    Add-PodeStaticRouteGroup -FileBrowser  -Routes {
        Add-PodeStaticRoute -Path '/' -Source $using:directoryPath -FileBrowser
    }
}

in theory, the code should hide the LICENSE.TXT file, but today, this code is not working because Static routes are checked before
anything else.
It is a problem if we switch the order Static->Anything else to Anything else ->Static. Or at least make this configurable.
I did some tests and cannot see any side effects from changing that.
@Badgerati, what are your thoughts?
Thanks

The order is static routes first, then normal non-static routes.
It is configurable - https://badgerati.github.io/Pode/Tutorials/Routes/Utilities/StaticContent/#static-routes-order


Login handler supports providing the frontend app schema via endpoint

ACs

It's JSON
Doesn't need to be publicly accessible, can 404
Think about how this could work in a headless approach, or just use sticky sessions?
It takes the member from the session store for context
Add a fetch to the frontend app for this endpoint
Style has contributed to choosing loading indicator, note we wouldn't be using anything from admin at this point
There is handling if the API fails, with a message to the user. Note this is for system errors, not for failing authentication - that needs more thought
Return an empty object - writing the schema should be separate from this issue

PR at #10 .
This has implemented the back-end side. I assume that integration with the front-end app is not considered part of this issue.


"out of bounds memory access" on memory.fill after memory.grow

Test case:
(module
  (type (func))
  (func $_start
    (memory.grow (i32.const 1))
    drop
    (memory.fill (i32.const 65536) (i32.const 0) (i32.const 10))
  )
  (memory 1)
  (export "memory" (memory 0))
  (export "_start" (func $_start))
)

Run this small WAT with iwasm. You will get:

Exception: out of bounds memory access

https://github.com/bytecodealliance/wasm-micro-runtime/pull/2898 fixes it.

#2898 has landed.


Extract AST nodes into classes

This pull request introduces the following classes:

Masamune::AbstractSyntaxTree::Node
Masamune::AbstractSyntaxTree::DataNode
Masamune::AbstractSyntaxTree::NodeRegistry

Extracting this information from Masamune::AbstractSyntaxTree will help to understand what types of nodes exist within the tree and how different types are handled since they each have their own structure. The search function is pretty cluttered right now too, so I'm hoping it will be easier to read after finishing this pull request.

There's a lot here, but I'm really happy with how it's turning out. The original search method was an absolute mess, but I was still getting familiar with the types of nodes that exist and how to retrieve data nodes from them.
Things are a lot easier to manage now, so I can focus on the type of data I want to return. After things are settled with that, the next step is to move on to the code replacement class, and then the plan is to actually use this gem in an actual project.


Weave mesh comments

talk to @miolini -- I think that he and the weave team in general would have a fascinating conversation.

So right now mesh requires the knowledge of a single node-- why not bootstrap this from bittorrent DHT while using a PSK or certificate to ensure that no neer-do-well's show up and crash your party?  Would require knowledge of zero nodes, and enable glorious networked chaos.

What happens @ >100 nodes?

:).
BTW, here's an issue list mostly made by @miolini:
https://github.com/meshbird/meshbird/issues/created_by/miolini
Yeah, he's that awesome.

So right now mesh requires the knowledge of a single node-- why not bootstrap this from bittorrent DHT

Why not? Because knowledge of a single peer is much easier in many respects :) But this is an interesting approach. How would it fare in restricted networks? Knowledge of a single peer is nice in that it's easy to explain and orchestrate in the face of firewalls, VPCs with SGs, etc.

Given these are more questions than requests or bugs, I'll close the issue for now. Please feel free to follow up in Slack!


CPS-???? | Cardano Wallet Connectors [Draft]

This problem statement is concerned with the issues surrounding Cardano's current and future wallet-web bridges.
These interfaces are difficult to define and historically have been even harder to iterate upon.
We wish to provide a comprehensive catalog of the current offerings; and their drawbacks to be able to make suggestions on future standards.
I thought it important that such a problem statement is open for much community input, so have started this as a draft PR.
Todo

[ ] Enrich context subsection
[ ] Add to open questions section

📰 Rendered Problem Statement (on fork)

@Ryun1 looks promising so far.  I'll happily leave it to you when to mark Ready for review and/or kick it off at the CIP meeting agenda.


Stop animation and other bugs

Hi! 😃
This PR addresses the following bugs in issue #8478

Frame Input should not reposition Playhead. (The input now indicates the frame to put a keyframe or edit the value)
Connect the value box to Playhead change. (When value changes in value input the keyframe updates its value)

The following even though they stop the animation because the bug on playing the animation still feels weird. So I think the best option is to fix the play animation bug in the next PR.

Stop animation on Loop button click (The animation stops on clicking the loop button or changing frames per second.
The weird play animation bug is still there.
Stop animation after clicking Playhead. (The weird play animation bug is still there)

These we low hanging fruits to solve.

Remove Size animation type on "create a new animation". (Also reorder the list alphabetically)
Graph action controls hide sometimes. Should be visible all times (Used to be hidden, now only disabled if there is not animation selected)

@toledoal The value input still does not work... Basically in edit putting a value of
We can not delete the content to put another value like going from 1 to 2 ->

It does not display the current value (currently 1 where curve shows 5) ->

Changing the value does not change the value to the requested one ->

I ll put this back into the list. You should test those behavior before the next PR in edit as well.

Ok. Thanks. I'll verify this. The value scale is currently wrong. I'll work on that bug as well. The problem with this particular bug is it actually connected to other issues.

Makes much more sense so the main issue becomes the deletion and the fact that it still tries to change value on playhead position at start


Tbw add binanceus

Adding Binance US Exchange

This one was pretty straight forward.  I, ultimately, copied the binance exchange, and simply changed the name to binanceus, and added the required conf-sample content.
I’m very new to zenbot, only having found it this weekend.  I’m enjoying the project so far. I cut my teeth on trading bots with WolfBot, but faced far too many bugs.
Some of the features there have me thinking about investing some time into zenbot dev.  Most notably:

Multi-Exchange support
Multi-Currency Pair Support

I raise this, mostly, to determine if anyone else has work of this fashion going.  Any ideas?
From: Chase<EMAIL_ADDRESS>Sent: Monday, September 21, 2020 11:15 AM
To: DeviaVir/zenbot<EMAIL_ADDRESS>Cc: Tony Baker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [DeviaVir/zenbot] Tbw add binanceus (#2394)
@DeviaVir approved this pull request.
👍 Nice work.
offtopic: I wonder if there's a more generic ccxt exchange we could write that would work with any of the exchanges ccxt supports.. but I'd guess they all have their own quirks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DeviaVir/zenbot/pull/2394#pullrequestreview-492720907, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGZBVXPS2LVDYF4WSCH5SFLSG5UV3ANCNFSM4RTX7HPQ.


Better CentOS 5, 6, 7 support

Added 9.4 rpms for CentOS 5,6.
Fixed CentOS Init for CentOS 7+.
Fixed Architecture check (For wrong response).

I've run this PR on my project with postgres 9.3 on both centos6.5 and centos6.6 and neither will successfully converge. It still

I've run this PR on my project with postgres 9.3 on both centos6.5 and centos6.6 and neither will successfully converge. It still gives the Error executing action restart on resource 'service[postgresql]' error

Can you post your vars & recipe list?
Also you have loading yum_pgdg_postgresql recipe or its attribute enable_pgdg_yum is true?

Ah, i see error. Seems that something in config.
You have looked into postgresql log?

Attributes:
include_attribute 'postgresql'

# Set PostgreSQL data
node.default['postgresql']['version'] = '9.3'
case node['platform_family']
  when 'ubuntu'
    node.default['postgresql']['enable_pgdg_apt'] = true
  when 'redhat', 'rhel', 'centos'
    node.default['postgresql']['enable_pgdg_yum'] = true
end
node.default['postgresql']['config']['listen_addresses'] = '*'
node.default['postgresql']['contrib']['packages'] = [
    'pgadmin3'
]
node.default['postgresql']['contrib']['extensions'] = [
    'adminpack'
]

The recipe runs include_recipe 'postgresql::server', then simply creates a DB user and a DB. The DB resource call includes notifies :restart, "service[#{node['postgresql']['server']['service_name']}]", :immediately, which is where this fails.

I have this one in my cookbook db::provider on install step:
case node['platform_family']
when 'debian', 'ubuntu'
node.default['postgresql']['enable_pgdg_apt'] = true
when 'rhel', 'fedora', 'suse'
node.default['postgresql']['enable_pgdg_yum'] = true
end
run_context.include_recipe 'postgresql::contrib'
run_context.include_recipe 'postgresql::config_initdb'
run_context.include_recipe 'postgresql::config_pgtune'
run_context.include_recipe 'postgresql::ruby'

I'll try your suggestions shortly.

Also you can try to make provider specially for DB. In provider you can run such things like:
`run_context.include_recipe 'postgresql::contrib'```
Not in runtime.

Tried yours, same result :(

@ozzyogkush Can you look into Postgresql log?(data folder)

Just calling postgresql::server gets me:
[vagrant@database-centos-65 ~]$ sudo cat /var/lib/pgsql/data/pg_log/postgresql-Sat.log
LOG:  database system was shut down at 2015-05-30 22:59:04 UTC
LOG:  database system is ready to accept connections
LOG:  autovacuum launcher started
LOG:  received fast shutdown request
LOG:  aborting any active transactions
LOG:  autovacuum launcher shutting down
LOG:  shutting down
LOG:  database system is shut down
LOG:  invalid authentication method "peer"
CONTEXT:  line 28 of configuration file "/var/lib/pgsql/data/pg_hba.conf"
FATAL:  could not load pg_hba.conf
LOG:  invalid authentication method "peer"
CONTEXT:  line 28 of configuration file "/var/lib/pgsql/data/pg_hba.conf"
FATAL:  could not load pg_hba.conf

line 28 of /var/lib/pgsql/data/pg_hba.conf: local   all             all                                     peer

Try this config for peer:
{
  "postgresql": {
    "pg_hba": [
      {
        "type": "local",
        "db": "all",
        "user": "postgres",
        "addr": null,
        "method": "ident"
      },
      {
        "type": "local",
        "db": "all",
        "user": "all",
        "addr": null,
        "method": "ident"
      },
      {
        "type": "host",
        "db": "all",
        "user": "all",
        "addr": "<IP_ADDRESS>/32",
        "method": "md5"
      },
      {
        "type": "host",
        "db": "all",
        "user": "all",
        "addr": "::1/128",
        "method": "md5"
      }
    ]
  }
}

https://github.com/hw-cookbooks/postgresql/blob/develop/templates/default/pg_hba.conf.erb automatically includes that line:
<% elsif node['postgresql']['version'].to_f >= 9.1 -%>
local   all             all                                     peer
<% end -%>

Just do it with overriding attribute :) Higher priority.

I'm not sure what you mean by that. I'm installing PG 9.3, so that line will always run.
I add to the pg_hba attribute like so:
node.default['postgresql']['pg_hba'].push(
    {
        :type => 'host',
        :db => 'all',
        :user => 'all',
        :addr => '<IP_ADDRESS>/32',
        :method => 'md5'
    },
    {
        :type => 'host',
        :db => 'all',
        :user => 'all',
        :addr => '<IP_ADDRESS>/24',
        :method => 'md5'
    }
);

I'm use for this: node.override. Because this is array.

So as i see now, you have trouble with configuration of pg_hba.

My method works just fine. Final output of /var/lib/pgsql/data/pg_hba.conf is
[vagrant@database-centos-65 ~]$ sudo cat /var/lib/pgsql/data/pg_hba.conf
# This file was automatically generated and dropped off by Chef!

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.

# TYPE  DATABASE        USER            ADDRESS                 METHOD

###########
# Other authentication configurations taken from chef node defaults:
###########

local   all             postgres                                ident

local   all             all                                     ident

host    all             all             <IP_ADDRESS>/32            md5

host    all             all             ::1/128                 md5

host    all             all             <IP_ADDRESS>/32             md5

host    all             all             <IP_ADDRESS>/24           md5

# "local" is for Unix domain socket connections only
local   all             all                                     peer

Haha, glad to hear! :+1: Cheers!

Yes it's definitely a problem with that, hence LOG:  invalid authentication method "peer" <--- this is what I don't get though. I'm looking through the PG docs and it definitely is a valid method for 9.3 :/

Ok, I've checked and its actually only installing 8.4 of postgresql, which makes sense. I figured out why it's doing it - derived attributes! Even though I set the version to 9.3 in my attributes file, it's already creating the default['postgresql']['server']['packages'] = ["postgresql#{node['postgresql']['version'].split('.').join}-server"] attribute based on the original version defined in this cookbook. It needs to use lazy attributes, using the % operator instead of #

Any way only this way works within CentOS 7 & SystemD

Is this  change going to be merged ?

That's up to the owners of the repo https://github.com/orgs/hw-cookbooks/people, but I'd hope so.


⚠ Node - de-592cc6ef.yalaso.top has degraded performance

In 5fae982, Node - de-592cc6ef.yalaso.top (http://de-592cc6ef.yalaso.top/api/v1/ping) experienced degraded performance:

HTTP code: 200
Response time: 16827 ms

Resolved: Node - de-592cc6ef.yalaso.top performance has improved in 6b94669 after 31 minutes.


ci: Added dotnet clean and replaced nuget with dotnet

:tada: This PR is included in version 1.2.0-dev.2 :tada:
The release is available on:

GitHub release
v1.2.0-dev.2
v1.2.0-dev.2

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

GitHub release
v1.3.0
v1.3.0

Your semantic-release bot :package::rocket:


[WIP] Support native sticky

Here is a PR to use native position: sticky if browser supports it.
I think it's good to share my work on that and iterate with maintainers to get at a consensus.
This could bring performance improvements as a majority of browsers support sticky
https://caniuse.com/#feat=css-sticky
Here is the current test results on this branch:
1..182
# tests 182
# pass  181
# skip  0
# fail  1

I haven't add new tests yet.
I try to be the most compatible with the existing interface unfortunately there is some limitations:

sticky element aren't suppose to go out of it's parent
https://stackoverflow.com/questions/46913063/positionsticky-does-not-leave-parent
which result with inconsistency between old/new behavior.
For example, in the dummy app elements "not sticky to bottom" can't go out of their containers.

old

new

[EDIT] sticky element doesn't go well with overflow: hidden. So this may breaks layouts that work today. That's why I need to remove row class from the dummy app.
https://stackoverflow.com/questions/43909940/why-does-overflowhidden-prevent-positionsticky-from-working

I would like your thoughts on this.

One solution to not break compatibility could be to add this as an opt-in feature.

@ctjhoa first thanks for your effort here, and sorry for the late response!
Before getting into details, can you explain the motivation for this change? I guess it's mainly about performance, right? But as the native template also includes the trigger components (to continue supporting the yielded isSticky* states I guess), which adds the scroll listeners/InteractionObserver from ember-in-viewport, I wonder if we really get any noticeable performance improvement?

position: fixed always relative to browser window, if i will want start ember application in some container - position: fixed, it will break my app.


Update formatting changes and add landing page

Description:

Update formatting changes for following docs:

Amazonlambda Connector example.md
ISO8583 Connector example.md

Add landing page for the Salesforce Connector

These docs are already updated. Please reopen if needed.


Conditional type (ReturnType) not correctly infered when used to create an union from a Record type values

TypeScript Version<EMAIL_ADDRESS>
Search Terms:
deep return type
deep ReturnType
conditional return type
Code
type Fn = (...args: any[]) => any;
type SelfOrReturnType2Levels<T> = T extends Fn ?
    ReturnType<T> extends Fn ?
        ReturnType<ReturnType<T>> :
        ReturnType<T> :
    T;
type ReturnType2Levels<T extends Fn> = ReturnType<T> extends Fn ? ReturnType<ReturnType<T>> : ReturnType<T>;

const action1 = (age: number) => ({ age });
const action2 = (id: string) => (name: string) => ({ id, name });

//type payload1 = SelfOrReturnType2Levels<typeof action1>; // ok
//type payload2 = SelfOrReturnType2Levels<typeof action2>; // ok
//type ActionUnion<T extends Record<string, Fn>> = SelfOrReturnType2Levels<T[keyof T]>;
//const actions = { action1, action2 };
//type Action = ActionUnion<typeof actions> // ok

type payload1 = ReturnType2Levels<typeof action1>; // ok
type payload2 = ReturnType2Levels<typeof action2>; // ok
type ActionUnion<T extends Record<string, Fn>> = ReturnType2Levels<T[keyof T]>;
const actions = { action1, action2 };
type Action = ActionUnion<typeof actions> // ko

Expected behavior:
The type Action should be
type Action = {
    age: number;
} | {
    id: string;
    name: string;
}

like it does in the commented case.
Actual behavior:
The type Action is
type Action = {
    age: number;
} | ((name: string) => {
    id: string;
    name: string;
})

Playground Link:
http://www.typescriptlang.org/play/#src=type Fn %3D (...args%3A any[]) %3D> any%3B
type SelfOrReturnType2Levels<T> %3D T extends Fn %3F
    ReturnType<T> extends Fn %3F
        ReturnType<ReturnType<T>> %3A
        ReturnType<T> %3A
    T%3B
type ReturnType2Levels<T extends Fn> %3D ReturnType<T> extends Fn %3F ReturnType<ReturnType<T>> %3A ReturnType<T>%3B
%2F%2F circular types not allowed
%2F%2Ftype DeepReturnType<T extends Fn> %3D ReturnType<T> extends Fn %3F DeepReturnType<<ReturnType<T>> %3A ReturnType<T>%3B

const action1 %3D (age%3A number) %3D> ({ age })%3B
const action2 %3D (id%3A string) %3D> (name%3A string) %3D> ({ id%2C name })%3B

%2F%2Ftype payload1 %3D SelfOrReturnType2Levels<typeof action1>%3B %2F%2F ok
%2F%2Ftype payload2 %3D SelfOrReturnType2Levels<typeof action2>%3B %2F%2F ok
%2F%2Ftype ActionUnion<T extends Record<string%2C Fn>> %3D SelfOrReturnType2Levels<T[keyof T]>%3B
%2F%2Fconst actions %3D { action1%2C action2 }%3B
%2F%2Ftype Action %3D ActionUnion<typeof actions> %2F%2F ok

type payload1 %3D ReturnType2Levels<typeof action1>%3B %2F%2F ok
type payload2 %3D ReturnType2Levels<typeof action2>%3B %2F%2F ok
type ActionUnion<T extends Record<string%2C Fn>> %3D ReturnType2Levels<T[keyof T]>%3B
const actions %3D { action1%2C action2 }%3B
type Action %3D ActionUnion<typeof actions> %2F%2F ko

A conditional type is distributive iff it is written using a naked type parameter.. in other words type A<T> = T extends cond ? ture : flase is distributive, but type B<T> = ReturnType<T> extends cond ? true : false is not.
you can write your type as a series of two references to ensure it is distributive. e.g.
type ReturnType2Levels<T extends Fn> = ReturnTypeOrSelf<ReturnType<T>>;
type ReturnTypeOrSelf<T> = T extends Fn ? ReturnType<T> : T;

Ha Ok thanks good to know. Should I just close the issue then ?


What's wrong with me ?

Initializing the variables of the model
Initialization finished
[-] init_model : 1.16156 sec, which is 0.01936 mins, which is 0.00032 hours
Traceback (most recent call last):
File "main.py", line 19, in
main()
File "main.py", line 15, in main
agent.run()
File "/media/arch760/My Passport/TFSegmentation/utils/misc.py", line 18, in timed
result = f(*args, **kwargs)
File "/media/arch760/My Passport/TFSegmentation/agent.py", line 88, in run
self.operator = self.operator(self.args, self.sess, self.model, self.model)
File "/media/arch760/My Passport/TFSegmentation/train/train.py", line 50, in init
super().init(args, sess, train_model, test_model)
File "/media/arch760/My Passport/TFSegmentation/train/basic_train.py", line 39, in init
save_relative_paths=True)
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1338, in init
self.build()
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1347, in build
self._build(self._filename, build_save=True, build_restore=True)
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1384, in _build
build_save=build_save, build_restore=build_restore)
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 813, in _build_internal
saveables = self._ValidateAndSliceInputs(names_to_saveables)
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 661, in _ValidateAndSliceInputs
names_to_saveables = BaseSaverBuilder.OpListToDict(names_to_saveables)
File "/home/arch760/.local/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 638, in OpListToDict
name)
ValueError: At least two variables have the same name: network/conv1_x/bn1/mu

Which version tensorflow do you use? I've faced the same issue when I was trying to run with v1.7.1 .

@erolrecep
1.12.0 ...

On requirements files they say 1.3.0 for tensorflow-gpu, 1.4.0 for tensorflow.


drone.io is not triggered on mirrored repos

Is it possible to trigger drone.io also on pushes that are "imported" by mirrored repo ?

Merge this issue to https://github.com/gogits/gogs/issues/4528.


How to implement infinite scroll use GridView？

I want to implement infinite scroll use GridView, now using GestureDetector(content=GridView(...)), but it seems GridView cant scroll inside a GestureDetector, is it a bug or just a error usage?

Closing as a dup of https://github.com/flet-dev/flet/issues/747
I'm going to implement that once Flet 0.6.0 released.


Improve error logging

we should create custom error messages to better communicate errors to the user, especially related to external services
example:
if connection to Kafka REST proxy fails, log a helpful error message explaining what happened
connection to Kafka REST proxy failed:
...

instead of
connection refused http://host:port/xyz

These issues are related to each other https://github.com/bakdata/kpops/issues/101

improve ambiguous error message from KEDA autoscaler when input topic is not defined:
RuntimeError: Error: unable to build kubernetes objects from release manifest:
error validating "": error validating data: ValidationError(ScaledObject.spec):
missing required field "triggers" in sh.keda.v1alpha1.ScaledObject.spec

We should explain the errors of the module field in more detail. In some cases, it is not clear that we have to import the classes in the init.py file of the given module, even when the user gave the correct module. So if the module is not found, we can write a hint. For example:
Could not find module blablabla
Hint: Don't forget to import your classes to the __init__.py file

Another way to prevent mistakes is to check the user's input string. Some tend to write the module as a path. We can add an extra check and catch the error. For instance:
If the user types /path/to/module
Error: The provided module format is incorrect.
Please notice that the module is not a path. Consider changing your input to path.to.module

Moreover, we can add on the field description of the module an example input.


BUG: optimize: check for NaN optimum in BFGS

New take on #5125 to fix #4793, at least for BFGS. Ping @pv, @josef-pkt. (GitHub wouldn't let me reopen the old PR after a force-push.) The solution turns out to be very simple.

looks good to me for bfgs.
However, I thought this could also go into the minimize top function itself it improves consistency across optimizers. (to make sure all have success == False)

@josef-pkt Fixing it in minimize would leave fmin_bfgs, fmin_l_bfgs_b and fmin_cg without the check.

Merged and made a new issue for the other optimizers.