Build and push .ibm/images/Dockerfile image

What type of PR is this:
/kind tests
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6308

[x] Use a quay.io robot account

/lgtm

Ran 341 of 408 Specs in 2716.384 seconds
FAIL! -- 340 Passed | 1 Failed | 0 Pending | 67 Skipped
Ginkgo ran 1 suite in 45m21.889061934s
Test Suite Failed
exit status 1
make: *** [test-integration-cluster] Error 1

Overriding Prow tests, because test-integration-cluster is passing on IBM Cloud.
/override ci/prow/v4.11-integration-e2e


Fresh Install Android Broken on React Native 0.60 RC2

As React Native will default to AndroidX from 0.60, I want to upgrade my project to 0.60RC2 and AndroidX but I can't get it to working. I can reproduce it with a fresh project.
React Native version:
System:
    OS: macOS 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
    Memory: 67.11 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.4.0 - /usr/local/bin/node
    Yarn: 1.17.0 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
  IDEs:
    Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
    Xcode: 10.2/10E125 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.3 => 16.8.3
    react-native: 0.60.0-rc.2 => 0.60.0-rc.2
  npmGlobalPackages:
    react-native-cli: 2.0.1

Steps To Reproduce

Create a new React Native Project  react-native init testproject (it creates a project using "react-native": "0.59.9" dependency).
Make sure your emulator is running. Try to run cd /Users/Can/Desktop/testproject && react-native run-android (replace path with yours).
In my case it couldn't find the Android SDK, so I added local.properties into android folder with the content sdk.dir=/Users/Can/Library/Android/sdk (replace it with your Android SDK path)
Run react-native run-android again. It runs perfectly. It displays the default Hello World app screen on my emulator.
Open package.json and switch RN version to 0.60 RC2:  "react-native": "0.60.0-rc.2"
Run npm install to update to latest version.
Try running react-native run-android again. It errors Task :app:processDebugManifest FAILED:

* What went wrong:
Execution failed for task ':app:processDebugManifest'.
> Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91
  	is also present at [androidx.core:core:1.0.1] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory).
  	Suggestion: add 'tools:replace="android:appComponentFactory"' to <application> element at AndroidManifest.xml:7:5-117 to override.

What I've tried:

As the error message suggests, I've added tools:replace="android:appComponentFactory" to application tag in my project's root AndroidManifest.xml and tried running again. Then I got a different error:

> org.xml.sax.SAXParseException; systemId: file:/Users/Can/Desktop/testproject/android/app/src/main/AndroidManifest.xml; lineNumber: 13; columnNumber: 39; The prefix "tools" for attribute "tools:replace" associated with an element type "application" is not bound.

After a quick Googling I've found this comment where it suggests to add  xmlns:tools="http://schemas.android.com/tools" to the manifest's root tag, so I did it. When I ran, this time I got:
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
/Users/Can/Desktop/testproject/android/app/src/main/AndroidManifest.xml:6:5-25:19 Error:
	tools:replace specified at line:6 for attribute android:appComponentFactory, but no new value specified

After Googling that too I've stumbled upon a StackOverflow question regarding the same issue with this answer: It tells, if migrating to AndroidX (which RN 0.60 uses by default), to remove those tags from manifest and add the following lines to gradle.properties:
android.useAndroidX=true
android.enableJetifier=true

So I did those. Now, the build succeeds on RN 0.60, but immedieately at launch I'm getting the following error in LogCat and the app crashes on launch:
2019-06-27 23:30:34.151 8014-8047/com.testproject E/SoLoader: Error when loading lib: dlopen failed: library "libjsc.so" not found lib hash: 9f147276937ca9f5dfbf5ff8b8b470c1 search path is /data/app/com.testproject-LdIs8_kVqRM_R_hH6wP35g==/lib/x86
2019-06-27 23:30:34.152 8014-8047/com.testproject E/SoLoader: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found

    --------- beginning of crash
2019-06-27 23:30:34.156 8014-8047/com.testproject E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: com.testproject, PID: 8014
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
        at com.facebook.react.jscexecutor.JSCExecutor.<clinit>(JSCExecutor.java:19)
        at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:29)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
        at java.lang.Thread.run(Thread.java:764)

I've then Googled dlopen failed: library "libjsc.so" not found and stumbled upon someone having the same issue after upgrading to 0.60 RC2. I've tried the accepted answer and added def useIntlJsc = false to the top of app/build.gradle and the following snippet into dependencies:
   if (useIntlJsc) {
        implementation 'org.webkit:android-jsc-intl:+'
    } else {
        implementation 'org.webkit:android-jsc:+'
    }

At this point nothing changed and I keep getting the same error. In addition to the steps above, (I know the following is unreproducible but may hint to a clue) when I tried the same steps in my actual project, this last answer worked, but then I got an error saying libgnustl_shared.so instead of libjsc.so.
Describe what you expected to happen:
I expected a fresh package to run normally with 0.60.

How can I get React Native 0.60 working with Android?

I looks like you use native module that depends support-library, instead of AndroidX, and causing conflicts. Please make sure that third-party modules you use are AndroidX compatible or check out https://github.com/mikehardy/jetifier.

@dulmandakh Which third party module exactly? I am trying to run a clean, fresh, newly created project created with react-native init command. I'm not using anything third party.

I’m facing similar issue on an app porting from 0.59.9 to 0.60.0. I’ve already run npx jetify and it exits without any error message. Is there any update on this?

Why this issue closed??? i'm facing the same problem

This is also happening with React Native v0.60.0 (the full release, not an RC)

When I use react-native run-android command Metro server start. But after few seconds later its getting closed. Do we need to run it by other command or its a bug in react native 0.60.0 version

@dulmandakh Please reconsider reopening this issue, as I've said I'm not using any third party modules, and many other people here are having the same problem with me.

Same issue during the react native integration with an existing app
apply plugin: 'com.android.application'

android {
    compileSdkVersion 29
    buildToolsVersion "29.0.0"
    defaultConfig {
        applicationId "com.example.reactnativeintegration"
        minSdkVersion 16
        targetSdkVersion 29
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {
    implementation fileTree(dir: 'libs', include: ['*.jar'])
    implementation 'androidx.appcompat:appcompat:1.0.2'
    implementation 'androidx.constraintlayout:constraintlayout:1.1.3'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.2.0'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.2.0'

    implementation "com.facebook.react:react-native:0.60.0"
}

E/SoLoader: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found
W/unknown:ReactNative: Packager connection already open, nooping.

    --------- beginning of crash
E/AndroidRuntime: FATAL EXCEPTION: create_react_context
    Process: com.example.reactnativeintegration, PID: 18713
    java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found
        at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:738)
        at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:591)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:529)
        at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:484)
        at com.facebook.react.jscexecutor.JSCExecutor.<clinit>(JSCExecutor.java:19)
        at com.facebook.react.jscexecutor.JSCExecutorFactory.create(JSCExecutorFactory.java:29)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:949)
        at java.lang.Thread.run(Thread.java:919)
I/Process: Sending signal. PID: 18713 SIG: 9
Application terminated.

I'm also facing the same issue.
Getting another error along with libjscexecutor.so,
2019-07-07 18:59:28.440 10045-10076/com.mihir.reactApp E/.mihir.reactAp: No implementation found for com.facebook.react.bridge.Inspector com.facebook.react.bridge.Inspector.instance() (tried Java_com_facebook_react_bridge_Inspector_instance and Java_com_facebook_react_bridge_Inspector_instance__)
2019-07-07 18:59:28.449 10045-10076/com.mihir.reactApp E/unknown:ReactNative: Inspector doesn't work in open source yet
    java.lang.UnsatisfiedLinkError: No implementation found for com.facebook.react.bridge.Inspector com.facebook.react.bridge.Inspector.instance() (tried Java_com_facebook_react_bridge_Inspector_instance and Java_com_facebook_react_bridge_Inspector_instance__)
        at com.facebook.react.bridge.Inspector.instance(Native Method)
        at com.facebook.react.bridge.Inspector.getPages(Inspector.java:27)
        at com.facebook.react.devsupport.InspectorPackagerConnection.getPages(InspectorPackagerConnection.java:152)
        at com.facebook.react.devsupport.InspectorPackagerConnection.handleProxyMessage(InspectorPackagerConnection.java:72)
        at com.facebook.react.devsupport.InspectorPackagerConnection$Connection.onMessage(InspectorPackagerConnection.java:223)
        at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323)
        at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
        at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
        at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
        at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)

Also, I'm not using any third partly library or anything. Getting this error on fresh Android Application.

I'm also facing the same issue.
Getting another error along with libjscexecutor.so,

Yep, after doing some fixes from google get this one too

Same issue here

Same issue

Found a fix, this works for me (based off of the suggestion over at #25537):
Do an
npm install --save jsc-android

Then make sure to add this Android JSC block to your android/build.gradle:
allprojects {
    repositories {
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        google()
        jcenter()
    }
}

the previous fix doesn't work for me, I still have the same
couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found
issue

https://github.com/facebook/react-native/issues/25537#issuecomment-509959166 i found fix that helped me

these changes makes things working for me.
Still, I don't really know what's wrong. Because without those changes also everything works perfectly on react-native V.0.59.10.
I also don't see any official documentation regarding this.

with this https://github.com/facebook/react-native/issues/25415#issuecomment-509966579 at least now I can see the react-native component
I've just needed to add this line
implementation 'org.webkit:android-jsc:+'
but the error with the bridge is still there
2019-07-10 12:31:54.454 10143-11291/com.example.reactnativeintegration E/tiveintegratio: No implementation found for com.facebook.react.bridge.Inspector com.facebook.react.bridge.Inspector.instance() (tried Java_com_facebook_react_bridge_Inspector_instance and Java_com_facebook_react_bridge_Inspector_instance__)
2019-07-10 12:31:54.455 10143-11291/com.example.reactnativeintegration E/unknown:ReactNative: Inspector doesn't work in open source yet
    java.lang.UnsatisfiedLinkError: No implementation found for com.facebook.react.bridge.Inspector com.facebook.react.bridge.Inspector.instance() (tried Java_com_facebook_react_bridge_Inspector_instance and Java_com_facebook_react_bridge_Inspector_instance__)
        at com.facebook.react.bridge.Inspector.instance(Native Method)
        at com.facebook.react.bridge.Inspector.getPages(Inspector.java:27)
        at com.facebook.react.devsupport.InspectorPackagerConnection.getPages(InspectorPackagerConnection.java:152)
        at com.facebook.react.devsupport.InspectorPackagerConnection.handleProxyMessage(InspectorPackagerConnection.java:72)
        at com.facebook.react.devsupport.InspectorPackagerConnection$Connection.onMessage(InspectorPackagerConnection.java:223)
        at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323)
        at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
        at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
        at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
        at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)

I upgaded react-native from 0.56.0 to 0.60.0 using https://github.com/react-native-community/rn-diff-purge/compare/release/0.56.0..release/0.60.0#diff-1bcdc04ee1388d1458277d59136926e8. I did all changes as mentioned in the above link. But am getting error :
BUILD FAILED in 44s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

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

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find com.androidx.appcompat:28.0.0:.
Required by:
project :app
Could not find any matches for com.google.maps.android:android-maps-utils:0.5+ as no versions of com.google.maps.android:android-maps-utils are available.
Required by:
project :app
project :app > project :react-native-maps
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-signature-capture
Could not find any version that matches com.facebook.react:react-native:0.19.+.
Versions that do not match: 0.60.0
Required by:
project :app > project :react-native-signature-capture
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-share
project :app > project :react-native-fbsdk
project :app > project :lottie-react-native
Could not find com.facebook.android:facebook-android-sdk:4.34.0.
Required by:
project :app > project :react-native-fbsdk
Could not find com.clock.scratch:Scratch:1.0.0.
Required by:
project :app > project :react-native-scratch-card
Could not find com.airbnb.android:lottie:2.5.6.
Required by:
project :app > project :lottie-react-native
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-smart-splash-screen
Could not find com.onesignal:OneSignal:3.10.3.
Required by:
project :app > project :react-native-onesignal
Could not find any version that matches com.facebook.react:react-native:0.20.+.
Versions that do not match: 0.60.0
Required by:
project :app > project :react-native-charts-wrapper
Could not find com.itextpdf:itextg:5.5.9.
Required by:
project :app > project :react-native-image-to-pdf
Could not find com.facebook.infer.annotation:infer-annotation:0.11.2.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find javax.inject:javax.inject:1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.fresco:fresco:2.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.fresco:imagepipeline-okhttp3:2.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.soloader:soloader:0.6.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.google.code.findbugs:jsr305:3.0.2.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okhttp3:okhttp:3.12.1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okhttp3:okhttp-urlconnection:3.12.1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okio:okio:1.15.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0

I upgaded react-native from 0.56.0 to 0.60.0 using https://github.com/react-native-community/rn-diff-purge/compare/release/0.56.0..release/0.60.0#diff-1bcdc04ee1388d1458277d59136926e8. I did all changes as mentioned in the above link. But am getting error :
BUILD FAILED in 44s
error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

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

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
Could not find com.androidx.appcompat:28.0.0:.
Required by:
project :app
Could not find any matches for com.google.maps.android:android-maps-utils:0.5+ as no versions of com.google.maps.android:android-maps-utils are available.
Required by:
project :app
project :app > project :react-native-maps
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-signature-capture
Could not find any version that matches com.facebook.react:react-native:0.19.+.
Versions that do not match: 0.60.0
Required by:
project :app > project :react-native-signature-capture
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-share
project :app > project :react-native-fbsdk
project :app > project :lottie-react-native
Could not find com.facebook.android:facebook-android-sdk:4.34.0.
Required by:
project :app > project :react-native-fbsdk
Could not find com.clock.scratch:Scratch:1.0.0.
Required by:
project :app > project :react-native-scratch-card
Could not find com.airbnb.android:lottie:2.5.6.
Required by:
project :app > project :lottie-react-native
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > project :react-native-smart-splash-screen
Could not find com.onesignal:OneSignal:3.10.3.
Required by:
project :app > project :react-native-onesignal
Could not find any version that matches com.facebook.react:react-native:0.20.+.
Versions that do not match: 0.60.0
Required by:
project :app > project :react-native-charts-wrapper
Could not find com.itextpdf:itextg:5.5.9.
Required by:
project :app > project :react-native-image-to-pdf
Could not find com.facebook.infer.annotation:infer-annotation:0.11.2.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find javax.inject:javax.inject:1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find androidx.appcompat:appcompat:28.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.fresco:fresco:2.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.fresco:imagepipeline-okhttp3:2.0.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.facebook.soloader:soloader:0.6.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.google.code.findbugs:jsr305:3.0.2.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okhttp3:okhttp:3.12.1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okhttp3:okhttp-urlconnection:3.12.1.
Required by:
project :app > com.facebook.react:react-native:0.60.0
Could not find com.squareup.okio:okio:1.15.0.
Required by:
project :app > com.facebook.react:react-native:0.60.0

Anybody help me to resolve this issue.

@PravsReddy Offtopic, no one will help you here. Create new bug if you think it is

@PravsReddy
You probably had this in your build.grade
implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"
Or something similar that specifies your version to 28.0.0
Then if you followed the migration table from https://developer.android.com/jetpack/androidx/migrate you probably saw that com.android.support:appcompat-v7 was replaced with androidx.appcompat:appcompat:1.0.0 and thought that 1.0.0 should be replaced with ${rootProject.ext.supportLibVersion} or whatever dynamic versioning you had in the initial implementation. It needs to be exactly  androidx.appcompat:appcompat:1.0.0 . So, final solution:
`

implementation "com.android.support:appcompat-v7:${rootProject.ext.supportLibVersion}"

implementation "androidx.appcompat:appcompat:1.0.0"
`

Hope this helps someone who stumbles across this :)

2019-08-20 00:38:26.816 27139-27139/? E/SoLoader: couldn't find DSO to load: libjscexecutor.so
2019-08-20 00:38:27.189 27139-27188/appPackageName/SoLoader: couldn't find DSO to load: libhermes.so

if you have this error it means that you have a jsc aar missing, you can find it in node_modules\jsc-android\dist
Make sure it is included in your dependencies

I'm also facing same issue.

Have same error:
E/SoLoader: couldn't find DSO to load: libjscexecutor.so
E/SoLoader: couldn't find DSO to load: libhermes.so

Is there are any workaround for this issue?

Did anyone try to use targetSdkVersion and compileSdkVersion 28 ? With build-tools 28.0.3 ? I think react native has a problem with sdkVersion 29 because when I couldn't run with it sdkVersion 29 and I had to revert to sdkVersion 28. May be I did a bad config but you guys should try that out.

Here's a work around that helped me a lot:
Do  npm i  jsc-android
put the below lines of code in package.json
{
  "name": "ABC",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    **"postinstall": "npx jetify"**
  },
  "dependencies": {
    **"jsc-android": "^241213.0.0",**
    "react": "^16.8.6",
    "react-native": "0.60.0",
  },
  "devDependencies": {
    **"jetifier": "^1.6.4",**
  },
}

put the below lines of code in allProjects/repositories in android build.gradle file
allprojects {
    repositories {
        mavenLocal()
        maven {
            url 'https://maven.google.com/'
        }
        jcenter()
        maven {
            url "$rootDir/../node_modules/react-native/android"
        }
        **maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }**
    }
}

put the below lines of code in app build.gradle
**def useIntlJsc = true // top of the file**
apply plugin: "com.android.application"
import com.android.build.OutputFile
apply from: "../../node_modules/react-native/react.gradle"

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */

android {
    compileSdkVersion 28
    buildToolsVersion '28.0.3'

    defaultConfig {
        applicationId "com.abc"
        multiDexEnabled true
        minSdkVersion 18
        targetSdkVersion 28
        versionCode 1
        versionName "1"
        ndk {
            abiFilters "armeabi-v7a",'x86',"arm64-v8a",'x86_64'
        }
    }
    dexOptions {
        javaMaxHeapSize "4g"
    }
    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", "arm64-v8a", "x86-64"
        }
    }
    **packagingOptions {
        pickFirst '**/libjsc.so'
        pickFirst '**/libc++_shared.so'
    }**
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
    }

 }

  dependencies {
    implementation 'androidx.multidex:multidex:2.0.1'
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation 'androidx.appcompat:appcompat:1.0.0'
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation 'androidx.arch.core:core-runtime:2.0.0'
    implementation 'androidx.arch.core:core-common:2.0.0'
    **implementation "org.webkit:android-jsc:r241213"**

 }

in gradle.properties
**android.useAndroidX=true
android.enableJetifier=true**

@saadmutahar  hi, can you help me to check my build.gradle file? I still facing the same issue
def useIntlJsc = true // top of the file
apply plugin: "com.android.application"
apply plugin: 'io.fabric'
apply from: "../../node_modules/react-native-vector-icons/fonts.gradle"
import com.android.build.OutputFile
project.ext.react = [
entryFile: "index.js",
bundleInStaging: true,       // Add this
bundleInInternalTest: true,  // Add this
enableHermes: false,  // clean and rebuild if changing
]
apply from: "../../node_modules/react-native/react.gradle"
def enableSeparateBuildPerCPUArchitecture = false
def enableProguardInReleaseBuilds = false
def jscFlavor = 'org.webkit:android-jsc:+'
def enableHermes = project.ext.react.get("enableHermes", false);
android {
compileSdkVersion rootProject.ext.compileSdkVersion
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}
defaultConfig {
    applicationId "com.testingandroid"
    minSdkVersion rootProject.ext.minSdkVersion
    targetSdkVersion rootProject.ext.targetSdkVersion
    missingDimensionStrategy 'react-native-camera', 'general'
    versionCode 1
    versionName "1"
    multiDexEnabled true
    ndk {
        abiFilters "armeabi-v7a",'x86',"arm64-v8a",'x86_64'
    }
}
dexOptions {
    javaMaxHeapSize "4g"
}
splits {
    abi {
        reset()
        enable enableSeparateBuildPerCPUArchitecture
        universalApk false  // If true, also generate a universal APK
        include "armeabi-v7a", "x86", "arm64-v8a", "x86_64"
    }
}
packagingOptions {
    pickFirst '**/libjsc.so'
    pickFirst '**/libc++_shared.so'
}
signingConfigs {
    debug {
        storeFile file('debug.keystore')
        storePassword 'android'
        keyAlias 'androiddebugkey'
        keyPassword 'android'
    }
}
buildTypes {
    debug {
        signingConfig signingConfigs.debug
    }
    release {
        // Caution! In production, you need to generate your own keystore file.
        // see https://facebook.github.io/react-native/docs/signed-apk-android.
        signingConfig signingConfigs.release
        minifyEnabled enableProguardInReleaseBuilds
        proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
    }
}

// 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:
        // https://developer.android.com/studio/build/configure-apk-splits.html
        def versionCodes = ["armeabi-v7a": 1, "x86": 2, "arm64-v8a": 3, "x86_64": 4]
        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
        }

    }
}

}
configurations.all {
resolutionStrategy {
force "com.google.android.gms:play-services-base:16.1.0"
force "com.google.android.gms:play-services-gcm:16.1.0"
force "com.google.android.gms:play-services-ads:17.2.0" }
}
dependencies {
implementation "org.webkit:android-jsc:r241213"
def multidex_version = "2.0.1"
implementation "androidx.multidex:multidex:$multidex_version"
implementation project(':react-native-firebase')
implementation project(':react-native-push-notification')
implementation project(':react-native-image-crop-picker')
implementation "com.google.android.gms:play-services-base:17.1.0"
implementation 'com.google.firebase:firebase-core:17.2.0'
implementation 'com.google.firebase:firebase-messaging:20.0.0'
implementation('com.crashlytics.sdk.android:crashlytics:2.9.9@aar') {
transitive = true
}
implementation 'me.leolin:ShortcutBadger:1.1.22@aar' // <-- Add this line if you wish to use badge on Android
implementation fileTree(dir: "libs", include: ["*.jar"])
implementation "androidx.core:core:1.1.0"
implementation "androidx.annotation:annotation:1.1.0"
implementation "androidx.appcompat:appcompat:${rootProject.ext.supportLibVersion}"
implementation "com.facebook.react:react-native:+"  // From node_modules
implementation ('com.google.android.gms:play-services-ads:16.+') { force = true; }
if (enableHermes) {
def hermesPath = "../../node_modules/hermes-engine/android/";
debugImplementation files(hermesPath + "hermes-debug.aar")
releaseImplementation files(hermesPath + "hermes-release.aar")
} else {
implementation jscFlavor
}
}
// 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 from: file("../../node_modules/@react-native-community/cli-platform-android/native_modules.gradle"); applyNativeModulesAppBuildGradle(project)
apply plugin: 'com.google.gms.google-services'

@nolife08021 It looks like you're going good with app build file, did you follow every steps as I mentioned above.

@nolife08021 It looks like you're going good with app build file, did you follow every steps as I mentioned above. If so please share your package.json file and project build file also.

@saadmutahar  here's my package.json file and project build file. Thanks
package.json
{
"name": "testingandroid",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"@react-native-community/async-storage": "^1.6.2",
"@react-native-community/netinfo": "^4.3.2",
"buffer": "^5.4.3",
"deprecated-react-native-listview": "0.0.5",
"jsc-android": "^241213.1.0",
"lottie-ios": "^3.1.3",
"lottie-react-native": "^3.2.1",
"moment": "^2.24.0",
"moment-timezone": "^0.5.26",
"react": "^16.9.0",
"react-dom": "^16.10.2",
"react-moment": "^0.9.2",
"react-native": "0.61.2",
"react-native-admob": "^2.0.0-beta.6",
"react-native-animatable": "^1.3.2",
"react-native-app-intro-slider": "^3.0.0",
"react-native-badger-android": "^1.0.4",
"react-native-camera": "^3.6.0",
"react-native-collapse-view": "^1.0.0",
"react-native-country-picker-modal": "^1.1.0",
"react-native-custom-checkbox": "^1.5.2",
"react-native-datepicker": "^1.7.2",
"react-native-device-info": "^3.1.4",
"react-native-exit-app": "^1.1.0",
"react-native-firebase": "^5.5.6",
"react-native-form-validator": "^0.2.0",
"react-native-image-crop-picker": "^0.25.3",
"react-native-image-pan-zoom": "^2.1.11",
"react-native-image-resizer": "^1.0.1",
"react-native-image-zoom-viewer": "^2.2.26",
"react-native-keyboard-aware-scroll-view": "^0.9.1",
"react-native-loading-spinner-overlay": "^1.0.1",
"react-native-material-bottom-navigation": "^1.0.4",
"react-native-material-buttons": "^0.6.0",
"react-native-md5": "^1.0.0",
"react-native-modal": "^11.4.0",
"react-native-numeric-input": "^1.8.3",
"react-native-offline": "^5.1.0",
"react-native-paper": "^2.16.0",
"react-native-permissions": "^2.0.0",
"react-native-pure-chart": "0.0.24",
"react-native-push-notification": "^3.1.9",
"react-native-qrcode-scanner": "^1.2.3",
"react-native-render-html": "^4.1.2",
"react-native-responsive-screen": "^1.3.0",
"react-native-restart": "0.0.13",
"react-native-secure-key-store": "^2.0.5",
"react-native-simple-radio-button": "^2.7.3",
"react-native-sqlite-storage": "^4.1.0",
"react-native-super-grid": "^3.1.1",
"react-native-svg": "^9.11.1",
"react-native-swipeout": "^2.3.6",
"react-native-switch": "^1.5.0",
"react-native-validation": "^1.0.2",
"react-native-vector-icons": "^6.6.0",
"react-native-web": "^0.11.7",
"react-native-webview": "^7.4.1",
"react-navigation": "^2.3.0",
"victory-native": "^33.0.0"
},
"devDependencies": {
"@babel/core": "7.6.2",
"@babel/runtime": "7.6.2",
"jetifier": "^1.6.4",
"@react-native-community/eslint-config": "0.0.3",
"babel-jest": "24.9.0",
"eslint": "6.5.1",
"jest": "24.9.0",
"metro-react-native-babel-preset": "0.51.1",
"react-test-renderer": "16.9.0"
},
"jest": {
"preset": "react-native"
}
}
root/build.gradle
`// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "28.0.3"
minSdkVersion = 19
compileSdkVersion = 28
targetSdkVersion = 28
supportLibVersion = "1.0.0-beta01"
}
repositories {
google()
jcenter()
maven {
url 'https://maven.fabric.io/public'
}
maven {
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
maven {
url 'https://maven.google.com/'
name 'Google'
}
}
dependencies {
classpath("com.android.tools.build:gradle:3.4.2")
classpath 'com.google.gms:google-services:4.3.2'
classpath 'io.fabric.tools:gradle:1.31.0' // for Firebase Crashlytics
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
mavenLocal()
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 {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
google()
jcenter()
maven { url 'https://jitpack.io' }
}
}
`

@nolife08021  please don't forgot to write   "postinstall": "npx jetify" in your package.json file.
{
"name": "testingandroid",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"postinstall": "npx jetify"
"lint": "eslint ."
},

@saadmutahar  Thanks!!!!! I am able to launch the app now. Can you please explain to me that what this code means??
"postinstall": "npx jetify"

@saadmutahar Thanks!!!!! I am able to launch the app now. Can you please explain to me that what this code means??
"postinstall": "npx jetify"

Great to hear that you able to run the app.
This is because some of your React Native modules with native Java code that isn't converted to AndroidX, and your app is AndroidX, you probably need this.

Here's a work around that fixes the issue:
Do npm i jsc-android
put the below lines of code in package.json
{
  "name": "ABC",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "postinstall": "npx jetify"
  },
  "dependencies": {
    "jsc-android": "^241213.0.0",
    "react": "^16.8.6",
    "react-native": "0.60.0",
  },
  "devDependencies": {
    "jetifier": "^1.6.4",
  },
}

put the below lines of code in allProjects/repositories in android build.gradle file
allprojects {
    repositories {
        mavenLocal()
        maven {
            url 'https://maven.google.com/'
        }
        jcenter()
        maven {
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
    }
}

put the below lines of code in app build.gradle
def useIntlJsc = true // top of the file
apply plugin: "com.android.application"
import com.android.build.OutputFile
apply from: "../../node_modules/react-native/react.gradle"

/**
 * Run Proguard to shrink the Java bytecode in release builds.
 */

android {
    compileSdkVersion 28
    buildToolsVersion '28.0.3'

    defaultConfig {
        applicationId "com.abc"
        multiDexEnabled true
        minSdkVersion 18
        targetSdkVersion 28
        versionCode 1
        versionName "1"
        ndk {
            abiFilters "armeabi-v7a",'x86',"arm64-v8a",'x86_64'
        }
    }
    dexOptions {
        javaMaxHeapSize "4g"
    }
    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", "arm64-v8a", "x86-64"
        }
    }
    packagingOptions {
        pickFirst '**/libjsc.so'
        pickFirst '**/libc++_shared.so'
    }
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
            signingConfig signingConfigs.release
        }
    }

 }

  dependencies {
    implementation 'androidx.multidex:multidex:2.0.1'
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation 'androidx.appcompat:appcompat:1.0.0'
    implementation "com.facebook.react:react-native:+"  // From node_modules
    implementation 'androidx.arch.core:core-runtime:2.0.0'
    implementation 'androidx.arch.core:core-common:2.0.0'
    implementation "org.webkit:android-jsc:r241213"

 }

in gradle.properties
android.useAndroidX=true
android.enableJetifier=true

This worked for me without "postinstall": "npx jetify"
Thanks!

This is also happening with React Native v0.61.5 (the full release, not an RC)


Resolve semver if ?semver exists

This pull request is a continuation of #1826 .
This proposal resolves the semver query if ?semver exists in the request.
This approach is safer than the previous proposal.
Thank you so much for the advice @kt3k

Background
One of the strong points of Deno compared to Node.js is the compliance of web standards. The interpreter loads ES modules with an import statement, which takes a URL string and a path string to a local file. Internally, the interpreter stores the ES modules in only one system cache directory. Hence, the interpreter reduces the occupancy of a local disk. Moreover, this is a useful feature for single-file ad-hoc scripts because the interpreter downloads the script automatically.
import abc from<EMAIL_ADDRESS>
Problem of Import Statement
Some member of deno community claims two problems about es modules.
1. Deno downloads all the versions of a module even if the version is different from a patch number only.
   Hence, a dependency tree commonly becomes a large tree. For instance, module A depends on modules B and C,
   which depend on a modules D, versions of which are 1.3.3 and 1.3.2, respectively,
   then deno downloads both modules<EMAIL_ADDRESS>and<EMAIL_ADDRESS>   Thus, the dependency tree becomes larger and larger.

2. We have to update version numbers for each update manually.
   In a simple case, if the project consists of 10 files that depend on ten external modules
   for each file, and then we have to rewrite version numbers on 100 lines.

Related Works
DSR (dsr.edjopato.de)
dsr is the original of this proposal. The service interprets some semver and redirects to deno.land. It is written in Rust and runs very fast, but the semver is partially incompatible with package.json and deno. The paths to the packages are also incompatible with deno.land, which makes it somewhat difficult for each project to migrate from deno.land.
Import Maps
Import maps are a good solution that follows web standards. By writing pointers to dependent libraries in a separate file, you can use a pre-specified short name in the source code without writing the URL. Furthermore, to update the version of a module, you can change the version at once by rewriting the import maps. However, you can't specify the version by semver like NodeJs package.json, and you can't resolve dependency-hell.
CDNs for NPM packages
Skypack, Esm.sh, and Esm.run are CDN services that convert packages uploaded on npmjs.com to ES Module and deliver them. These services compile transparently on the edge network. In addition, they compile and interpret the version directive specified in the URL and automatically deliver the most appropriate version of the package. However, We are not sure if these services will work. However, these services only deliver packages uploaded to npmjs.com, not necessarily projects registered on deno.land.
Deno Package Managers
Package managers made by deno, such as deno-udd, fall into two main categories. One is to prepare an external file, like import-maps, and install modules based on the specified version. The other is to add # to the URL and manage the version based on the directive at the end. This method is not intended to solve dependency-hell and requires a separate software installation.
Version Aliasing for Deno.land
Semver
Semver is a simple set of rules and requirements that dictate how version numbers are assigned and incremented. It is commonly used in the JavaScript community. Although we have no statistical information on how many libraries follow this specification in Deno community, we believe this is a major manner because the Deno community is close to the JavaScript community. We propose the redirection of requests based on this rule as follows.
1. The client sends HTTP request to the server to retrieve modules.

2. The server searches git tags for the closest version of the library.

3. The server rewrites the URL with the version and return the 302 redirections.

4. The client sends HTTP request to the redirected URL.

Our proposal is to implement step 2 and 3 based on deno-semver, which is compatible with package.json.
Non-semver
We also concern that some of the libraries do not follow the semver spec. Hence, the system should fall back to be compatible with the existing system. In above step 2, if the program could not found the version because the request or the library did not follow the semver, the server does not rewrite a version number. Thus, the client sends the same request to deno.land.

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

hmm dotland-fresh preview is available, but dotland preview doesn't seem available.. 🤔

It's weird. For #2078, dotland preview is available but dotland-fresh preview is not.
On the other hand, dotland-fresh preview is available for #2077  but dotland preview is not.

pushed merge commit to re-trigger the preview deployment (but looks failed..

This PR optionally adds semver resolution to the registry if the url has ?semver query string.
For example, by applying this PR:

https://deno.land/x/oak@^10.0.0/mod.ts?semver resolves to<EMAIL_ADDRESS>https://deno.land/x/lume@~1.6.0/mod.ts?semver resolves to<EMAIL_ADDRESS>
I'm in favor of landing this PR and getting the feedback from the community.
Note: If the url doesn't have ?semver, this doesn't affect anything. So this shouldn't have any effect to existing code in the ecosystem.

Closing this for now. Similarly to #1826, we currently don't have a plan to add feature like this in the registry. Thank you for your efforts @tani anyway.


page.evaluate changes value of string parameter sent to it

Expected behavior
myPrintText Node:
function myPrint() {
  console.log("Hello, World!");
}

Actual behavior
info: myPrintText inside phantom page:
info: myName: John
info: myPrintText:
info: function anonymous() {
info:   console.log("Hello, World!");
info: }

I convert function myPrint() into string and assign to myPrintText var:
var myPrintText = myPrint.toString()
Then I send the variable containing function text into page evaluate() function and print contents of the text:
await page.evaluate( function( myPrintText, myName ) {
    console.log("myPrintText inside phantom page:\n");
    console.log('myName: '+ myName );
    console.log("myPrintText:\n" + myPrintText );
  }, myPrintText, myName );

Somehow, the name of function inside the sent text is changed from myPrint() into anonymous()
How evaluate() changes text variables sent to it?
Steps to reproduce the behavior
The case study code:
const phantom = require('phantom');
const Promise = require('bluebird');

function myPrint() {
  console.log("Hello, World!");
}

(async function() {
  let ph = await phantom.create();
  let page = await ph.createPage();

  await page.property('onConsoleMessage', function(msg) {
    console.log(msg);
  });

  var myName = "John";
  var myPrintText = myPrint.toString();

  console.log("myPrintText Node:\n" + myPrintText);

  await page.evaluate( function( myPrintText, myName ) {
    console.log("myPrintText inside phantom page:\n");
    console.log('myName: '+ myName );
    console.log("myPrintText:\n" + myPrintText );
  }, myPrintText, myName );

})();

Environment

OS: ubuntu, centos
Node version (node -v): 7.6.0
package version: 4.0.1

I think I know what's going on. The way phantom communicates with node is by doing exactly what you have done (call toString() and then parse the string using Function). In the shim.js, I look for function and try to deserialize back to a function. The name doesn't really matter so I strip it.
There isn't a good fix as the parsing is done all the same way. If you do
await page.evaluate( function( myPrintText, myName ) {
    console.log("myPrintText inside phantom page:\n");
    console.log('myName: '+ myName );
    console.log("myPrintText:\n" + myPrintText );
  }, '  ' + myPrintText, myName );

it will work. It's a hack, I am not proud of it so hopefully it works.

I solved that by
myPrintText = myPrintText.replace('function', '_function')
before sending to page.evaluate() and performing
myPrintText = myPrintText.replace('_function', 'function')
inside page.evaluate()
I think this condition should be mentioned in documentation of page.evaluate() as function word inside string parameter to it is kinda control sequence and should be escaped.
Thanks for your solution.


Clarify comments to match practice

I'm updating the release documentation, and it seems there are some inaccurate comments in this file.
Based on the revision history in https://github.com/helm/helm/commits/master/internal/version/version.go it does not appear we update that file for patch releases, and it does not appear we currently use any format other than vX.y, so I am removing misleading comments.
Signed-off-by: Bridget Kromhout<EMAIL_ADDRESS>

Thanks, @bacongobbler. Reinstated in https://github.com/helm/helm/pull/8452.


xtask can't install toolchain

I've had this for a long time, but I have no idea what's happening:
$ cargo test
[snip]
     Running target/debug/deps/tidy_tests-011c6372e455c154

running 6 tests
test cli::generated_tests_are_fresh ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
test docs::no_docs_comments ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
test cli::no_todo ... ok
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
error: component download failed for cargo-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_assists_are_fresh ... FAILED
error: component download failed for cargo-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_grammar_is_fresh ... FAILED
info: downloading component 'rustc'
info: installing component 'cargo'
info: installing component 'rust-std'
info: installing component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'rustfmt'
test cli::check_code_formatting ... ok

failures:

---- cli::generated_assists_are_fresh stdout ----
> rustup toolchain install stable
thread 'cli::generated_assists_are_fresh' panicked at 'process `rustup toolchain install stable` failed. Please update assists by running `cargo xtask codegen`', xtask/tests/tidy-tests/cli.rs:24:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- cli::generated_grammar_is_fresh stdout ----
> rustup toolchain install stable
thread 'cli::generated_grammar_is_fresh' panicked at 'process `rustup toolchain install stable` failed. Please update it by running `cargo xtask codegen`', xtask/tests/tidy-tests/cli.rs:10:9

failures:
    cli::generated_assists_are_fresh
    cli::generated_grammar_is_fresh

test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p xtask --test tidy-tests'

$ rustup toolchain install stable                                                                                info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'

  stable-x86_64-unknown-linux-gnu unchanged - rustc 1.41.0 (5e1a79984 2020-01-27)

$ rustup toolchain remove stable                                                                                info: uninstalling toolchain 'stable-x86_64-unknown-linux-gnu'
info: toolchain 'stable-x86_64-unknown-linux-gnu' uninstalled

$ rustup toolchain install stable                                                                                info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
info: downloading component 'rustc'
 57.9 MiB /  57.9 MiB (100 %)  19.8 MiB/s in  3s ETA:  0s
info: installing component 'cargo'
info: installing component 'rust-std'
 17.5 MiB /  17.5 MiB (100 %)  17.3 MiB/s in  1s ETA:  0s
info: installing component 'rustc'
 57.9 MiB /  57.9 MiB (100 %)  13.3 MiB/s in  4s ETA:  0s

  stable-x86_64-unknown-linux-gnu installed - rustc 1.41.0 (5e1a79984 2020-01-27)

$ cargo test -p xtask --test tidy-tests                                                                                Finished test [unoptimized] target(s) in 0.04s
     Running target/debug/deps/tidy_tests-011c6372e455c154

running 6 tests
test docs::no_docs_comments ... ok
test cli::generated_tests_are_fresh ... ok
test cli::no_todo ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: downloading component 'rustfmt'
info: downloading component 'rustfmt'
info: downloading component 'rustfmt'
info: installing component 'rustfmt'
error: component download failed for rustfmt-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_assists_are_fresh ... FAILED
error: component download failed for rustfmt-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::check_code_formatting ... FAILED
test cli::generated_grammar_is_fresh ... ok

What is the exit code of rustup toolchain install stable? (echo $?)

0 when running it separately, but xtask seems to start it three times?

Wild guess: what does
diff which cargo which rustc
says?
Perhaps rustup tries to replace cargo shim and fails?
On Wednesday, 19 February 2020, Laurențiu Nicola<EMAIL_ADDRESS>wrote:

I've had this for a long time, but I have no idea what's happening:
$ cargo test
[snip]
Running target/debug/deps/tidy_tests-011c6372e455c154
running 6 tests
test cli::generated_tests_are_fresh ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
test docs::no_docs_comments ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
test cli::no_todo ... ok
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
error: component download failed for cargo-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_assists_are_fresh ... FAILED
error: component download failed for cargo-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_grammar_is_fresh ... FAILED
info: downloading component 'rustc'
info: installing component 'cargo'
info: installing component 'rust-std'
info: installing component 'rustc'
info: downloading component 'rustfmt'
info: installing component 'rustfmt'
test cli::check_code_formatting ... ok
failures:
---- cli::generated_assists_are_fresh stdout ----

rustup toolchain install stable
thread 'cli::generated_assists_are_fresh' panicked at 'process rustup toolchain install stable failed. Please update assists by running cargo xtask codegen', xtask/tests/tidy-tests/cli.rs:24:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

---- cli::generated_grammar_is_fresh stdout ----

rustup toolchain install stable
thread 'cli::generated_grammar_is_fresh' panicked at 'process rustup toolchain install stable failed. Please update it by running cargo xtask codegen', xtask/tests/tidy-tests/cli.rs:10:9

failures:
cli::generated_assists_are_fresh
cli::generated_grammar_is_fresh
test result: FAILED. 4 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out
error: test failed, to rerun pass '-p xtask --test tidy-tests'
$ rustup toolchain install stable info: syncing channel updates for
'stable-x86_64-unknown-linux-gnu'
stable-x86_64-unknown-linux-gnu unchanged - rustc 1.41.0 (5e1a79984
2020-01-27)
$ rustup toolchain remove stable info: uninstalling toolchain
'stable-x86_64-unknown-linux-gnu'
info: toolchain 'stable-x86_64-unknown-linux-gnu' uninstalled
$ rustup toolchain install stable info: syncing channel updates for
'stable-x86_64-unknown-linux-gnu'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984
2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
info: downloading component 'rustc'
57.9 MiB / 57.9 MiB (100 %) 19.8 MiB/s in 3s ETA: 0s
info: installing component 'cargo'
info: installing component 'rust-std'
17.5 MiB / 17.5 MiB (100 %) 17.3 MiB/s in 1s ETA: 0s
info: installing component 'rustc'
57.9 MiB / 57.9 MiB (100 %) 13.3 MiB/s in 4s ETA: 0s
stable-x86_64-unknown-linux-gnu installed - rustc 1.41.0 (5e1a79984
2020-01-27)
$ cargo test -p xtask --test tidy-tests Finished test [unoptimized]
target(s) in 0.04s
Running target/debug/deps/tidy_tests-011c6372e455c154
running 6 tests
test docs::no_docs_comments ... ok
test cli::generated_tests_are_fresh ... ok
test cli::no_todo ... ok
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: downloading component 'rustfmt'
info: downloading component 'rustfmt'
info: downloading component 'rustfmt'
info: installing component 'rustfmt'
error: component download failed for rustfmt-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::generated_assists_are_fresh ... FAILED
error: component download failed for rustfmt-x86_64-unknown-linux-gnu
error: caused by: could not rename file
test cli::check_code_formatting ... FAILED
test cli::generated_grammar_is_fresh ... ok
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-analyzer/rust-analyzer/issues/3243?email_source=notifications&email_token=AANB3M4KL6IOGK7OV4XOUJLRDWQE5A5CNFSM4KYCBZS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOY3BSQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANB3M4SZ425UP3UEZXRIZ3RDWQE5ANCNFSM4KYCBZSQ
.

/usr/bin/cargo and /usr/bin/rustc. I think it's trying to install it multiple times:
strace: Process 144753 attached
[pid 144753] execve("/usr/bin/rustup", ["rustup", "toolchain", "install", "stable"], 0x7ffe373e4488 /* 80 vars */) = 0
strace: Process 144754 attached
[pid 144754] execve("/usr/bin/rustup", ["rustup", "toolchain", "install", "stable"], 0x7ffe373e4488 /* 80 vars */) = 0
strace: Process 144755 attached
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
[pid 144755] execve("/usr/bin/rustup", ["rustup", "toolchain", "install", "stable"], 0x7ffe373e4488 /* 80 vars */) = 0

And I can reproduce it with:
$ rustup toolchain install stable& rustup toolchain install stable& rustup toolchain install stable                                                             [1] 144862
[2] 144863
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
476.2 KiB / 476.2 KiB (100 %) 350.2 KiB/s in  1s ETA:  0s
info: downloading component 'rust-std'
476.2 KiB / 476.2 KiB (100 %) 318.2 KiB/s in  1s ETA:  0s
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
info: latest update on 2020-01-30, rust version 1.41.0 (5e1a79984 2020-01-27)
info: downloading component 'cargo'
info: downloading component 'rust-std'
info: downloading component 'rustc'
 57.9 MiB /  57.9 MiB (100 %)  18.0 MiB/s in  3s ETA:  0s
info: installing component 'cargo'
info: installing component 'rust-std'
 17.5 MiB /  17.5 MiB (100 %)  14.6 MiB/s in  1s ETA:  0s
 15.3 MiB /  17.5 MiB ( 87 %)   1.9 MiB/s in  6s ETA:  1sinfo: installing component 'rustc'
 17.5 MiB /  17.5 MiB (100 %)   2.5 MiB/s in  6s ETA:  0s
error: component download failed for rust-std-x86_64-unknown-linux-gnu
error: caused by: could not rename file
[1]  - 144862 exit 1     rustup toolchain install stable
 17.5 MiB /  17.5 MiB (100 %)   2.4 MiB/s in  6s ETA:  0s
error: component download failed for rust-std-x86_64-unknown-linux-gnu
error: caused by: could not rename file

Latest release also have this issue:
wget https://github.com/rust-analyzer/rust-analyzer/archive/2020-03-23.tar.gz
tar xf 2020-03-23.tar.gz
cd rust-analyzer-2020-03-23
cargo test -p xtask --test=tidy-tests

Sample output:
    Finished test [unoptimized] target(s) in 0.05s
     Running target/debug/deps/tidy_tests-b9f7d4d69054c5f5

running 5 tests
test cli::generated_tests_are_fresh ... ok
test cli::generated_assists_are_fresh ... ok
test rust_files_are_tidy ... ok
test cli::generated_grammar_is_fresh ... ok
test cli::check_code_formatting ... FAILED

failures:

---- cli::check_code_formatting stdout ----
> rustup run stable -- cargo fmt -- --check
Diff in /tmp/ra_test/rust-analyzer-2020-03-23/xtask/src/dist.rs at line 17:
     rm_rf(&dist)?;
     fs2::create_dir_all(&dist)?;

-    if let Some(ClientOpts { version, release_tag}) = client_opts {
+    if let Some(ClientOpts { version, release_tag }) = client_opts {
         dist_client(&version, &release_tag)?;
     }
     dist_server()?;
Diff in /tmp/ra_test/rust-analyzer-2020-03-23/xtask/src/main.rs at line 13:
 use pico_args::Arguments;
 use xtask::{
     codegen::{self, Mode},
-    dist::{ClientOpts, run_dist},
+    dist::{run_dist, ClientOpts},
     install::{ClientOpt, InstallCmd, ServerOpt},
     not_bash::pushd,
     pre_commit, project_root, run_clippy, run_fuzzer, run_pre_cache, run_release, run_rustfmt,
thread 'cli::check_code_formatting' panicked at 'process `rustup run stable -- cargo fmt -- --check` failed. Please format the code by running `cargo format`', xtask/tests/tidy-tests/cli.rs:30:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    cli::check_code_formatting

test result: FAILED. 4 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p xtask --test tidy-tests'

Fixed in #4219.

Fixed in #4219.


isIpEndpointStyle inconsistent with .net equivalent

The implementation of isIpEndpointStyle is inconsistent with the .net equivalent implementation here
The specific use case where I am having issue with this is that we're running azurite via docker compose and the azurite instance is accessed via the endpoint "https://devstoreaccount1.blob.azurite.local:10001/devstoreaccount1" (we use this custom domain within docker because we're also using blobfuse which only seems to work when we set up the url like this)
When using this url using the .net sdk the sdk correctly identifies this url as a local azurite url based on the the port being used, however when using this node sdk the sdk does not identify the url as an azurite one and therefore will only work when the url is "https://devstoreaccount1.blob.azurite.local:10001"
The issue I have is that I am writing a node based functions app which is using this url from both node code and .net code (via the functions runtime) and I'd rather avoid having a different url set for each runtime context.
I am not 100% sure if this is an issue with the node sdk or the .net sdk or even both, appreciate it's edge case but it would seem that they at least both need to behave the same as each other. (whatever that behaviour is)

@EmmaZhu / @jaschrep-msft / @seanmcc-msft can you folks sync once and come up with a strategy to handle this.

Seems your scenario would need JS to be able to recognize a URL with port as ip style? Will work with .Net about this.
Thanks
Emma

Hi @ksstott ,
Could you share a code sample on how you'd invoke .Net SDK and JS SDK when you meet this issue on JS SDK?
The behavior in .Net and JS SDK are different. Although, technically https://devstoreaccount1.blob.azurite.local:10001/ is not an IP style URL and the SDK should be able to get storage account from the host name,  we should get SDKs for different languages have a consistent behavior.
Thanks
Emma

https://github.com/Azure/azure-sdk-for-js/pull/22895

The fix has been released in<EMAIL_ADDRESS>Would you like to have a try?


Add stream option to text generation task

https://github.com/livebook-dev/kino_bumblebee/assets/17034772/3f2e6adc-bff3-4023-9b97-b1315cfd451b

They may want to do either in an actual application, so this way we have an example of both. I don't have a strong preference though, your call!

I would go with the simpler UI and simpler code. They can remove the option if they feel adventurous. :)


Update docker-rollout

grep successfully found "healthy" when the status was "unhealthy".

Thanks for spotting this!


Add the ability to view Military Symbology in 3D

Background:
As a user I would like to be able to view military symbology in 3D from within ArcGIS Pro.
Current State:
This feature is not currently available in our solution.
Steps to Reproduce / Requirement / Workflow:
3D capability should be available seamlessly from within ArcGIS Pro 2.x
Version:
Pro 2.2

This work will not be done inside this issue. Closing this issue.


corrected video link

corrected the video link as the formatting was wrong and would not display

Learn Build status updates of commit b1745ed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

support/azure/active-directory/pending-devices.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Patched()fix Uncaught exception in PixelStreamingInfrastructure via engine

Signed-off-by: ANDRI<EMAIL_ADDRESS>Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
events.js:292
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}

CWE-248
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

You will need to sign your commit before I can merge it: https://docs.github.com/articles/about-gpg/


I want to add a Mobile App Development work from home job/internship at Hello Reception.

Hello sir ,
I'm Raman Kumar Gupta , with GitHub Id - Ramank2002
I did the contribution by adding a new internship on Mobile App Development in the repository by following all the rules.
Kindly consider it , & for this I'll very grateful to you.
Thankyou.

we are not adding internshala internships or any third party links


Class java.util.ollectionsFactory was not found

[ERROR] Class java.util.ollectionsFactory was not found
    at java.util.Map.of(TMap.java:227)
    at io.github.mmm.property.impl.PropertyFactoryManagerImpl.<clinit>(PropertyFactoryManagerImpl.java:30)
    at io.github.mmm.property.factory.PropertyFactoryManager.get(PropertyFactoryManager.java:171)
    at io.github.mmm.bean.AbstractBean.createProperty(AbstractBean.java:191)

To me it seems as if Map.of(...) is not implemented correctly in TeaVMs TMap class.
My assumption is that in the implementation of TMap.of(...) a class named CollectionsFactory is used. As TeaVM compiler assumes for java.* classes that these are emulated by a T* class it simply cuts of the first character from the simple name of the class resulting in this strange java.util.ollectionsFactory output.
However, when I look into the latest code of TMap inside TeaVM, I can not find CollectionsFactory but only TCollections or TTemplateCollections:
https://github.com/konsoletyper/teavm/blob/master/classlib/src/main/java/org/teavm/classlib/java/util/TMap.java#L174
So maybe this was fixed but is not yet released...

To me it seems as if Map.of(...) is not implemented correctly in TeaVMs TMap class.
My assumption is that in the implementation of TMap.of(...) a class named CollectionsFactory is used. As TeaVM compiler assumes for java.* classes that these are emulated by a T* class it simply cuts of the first character from the simple name of the class resulting in this strange java.util.ollectionsFactory output.
However, when I look into the latest code of TMap inside TeaVM, I can not find CollectionsFactory but only TCollections or TTemplateCollections:
https://github.com/konsoletyper/teavm/blob/master/classlib/src/main/java/org/teavm/classlib/java/util/TMap.java#L174
So maybe this was fixed but is not yet released...

My guess is confirmed:
https://github.com/konsoletyper/teavm/blob/160fa2b1fa334c0faa3992080272db825417f29b/classlib/src/main/java/org/teavm/classlib/java/util/TMap.java#L162

My guess is confirmed:
https://github.com/konsoletyper/teavm/blob/160fa2b1fa334c0faa3992080272db825417f29b/classlib/src/main/java/org/teavm/classlib/java/util/TMap.java#L162

See this issue:
https://github.com/konsoletyper/teavm/pull/530

See this issue:
https://github.com/konsoletyper/teavm/pull/530

Fixed


App Not redirected to authenticate

For bug reporting only! If you're posting a feature request or discussion, please ignore.
Expected Behavior
I have set up app to a domain : https://domainname.cartbrain.net/
and give a redirection urI with : https://domainname.cartbrain.net/authenticate
Current Behavior
When I try to install the App, it is redirected to domain with hmac and timestamp with error message
It appears you don't have
permission to access this page.
403 Error. Forbidden.
Steps to Reproduce

Install the laravel
And followed all the step according to wiki

Please show a screenshot. This sounds like something from Shopify not the package.

Please show a screenshot. This sounds like something from Shopify not the package.

I have the same issue

I have the same issue

I have the same issues with installation.

I have the same issues with installation.

The only 403 error in the library comes from JWT implementation. If you're not using JWT, then this is a server issue. @sandeeppangeni can you confirm what you're doing?

The only 403 error in the library comes from JWT implementation. If you're not using JWT, then this is a server issue. @sandeeppangeni can you confirm what you're doing?

@osiset , Hello, I change my middleware from 'auth.shopify' to 'auth.token' to use the JWT implementation.
Now when I try to install the app on a new store, its not redirecting to the install page, it redirects to:
https://example.myshopify.com/admin/apps/c8dfgdfg0813ff9db9585c7116057764/?hmac=0ecb20543b8dfgdfg15fa7651a82f8b2d1cbdfsfsdf2s9effc5a&shop=example.myshopify.com&timestamp=1611737799,
and the pages says 'no page at this address'. Any help please?

@osiset , Hello, I change my middleware from 'auth.shopify' to 'auth.token' to use the JWT implementation.
Now when I try to install the app on a new store, its not redirecting to the install page, it redirects to:
https://example.myshopify.com/admin/apps/c8dfgdfg0813ff9db9585c7116057764/?hmac=0ecb20543b8dfgdfg15fa7651a82f8b2d1cbdfsfsdf2s9effc5a&shop=example.myshopify.com&timestamp=1611737799,
and the pages says 'no page at this address'. Any help please?

@sandeeppangeni  It's the same your issue right now

hi @sandeeppangeni please double-check the SHOPIFY_API_REDIRECT variable in the env. It should be https://domainname.cartbrain.net/authenticate

For a while got a same issue. Solution in my case was simple, I just missed to add middleware auth.shopify on my "home" routing setting inside web.php file. Config after fix below:
Route::get('/', [ShopifyController::class, 'index'])->middleware(['auth.shopify'])->name('home');

I have the same issue, followed all steps and authenticate page is not found

I have the same issue, the app is redirecting and say on same site cookie issue, Page cannot be loaded


Tweak parallelism and the instantiation benchmark

Currently the "sequential" and "parallel" benchmarks reports somewhat
different timings. For sequential it's time-to-instantiate, but for
parallel it's time-to-instantiate-10k instances. The parallelism in the
parallel benchmark can also theoretically be affected by rayon's
work-stealing. For example if rayon doesn't actually do any work
stealing at all then this ends up being a sequential test again.
Otherwise though it's possible for some threads to finish much earlier
as rayon isn't guaranteed to keep threads busy.
This commit applies a few updates to the benchmark:

First an InstancePre<T> is now used instead of a Linker<T> to
front-load type-checking and avoid that on each instantiation (and
this is generally the fastest path to instantiate right now).

Next the instantiation benchmark is changed to measure one
instantiation-per-iteration to measure per-instance instantiation to
better compare with sequential numbers.

Finally rayon is removed in favor of manually creating background
threads that infinitely do work until we tell them to stop. These
background threads are guaranteed to be working for the entire time
the benchmark is executing and should theoretically exhibit what the
situation that there's N units of work all happening at once.

I also applied some minor updates here such as having the parallel
instantiation defined conditionally for multiple modules as well as
upping the limits of the pooling allocator to handle a large module
(rustpython.wasm) that I threw at it.

Will go ahead and hit 'merge' here so I can rebase on top of it in the lazy-tables PR...


Implement $SHELL and $0 (How to identify which shell I am in)

The shell now looks identical to Bash! How can I tell which shell I am in? This morning I started in our shell, and I only noticed when git tab completion didn't work (#80) that I am not in Bash.

Some ideas:

maybe some command to run "which_shell_am_I" (but shorter)
some key binding (Ctrl-H or F1) for a nice help / about screen
maybe make the shell look different (but I like that it looks like Bash)

For shells like Bash or Zsh the shell running is always exported in the SHELL environment variable.

@awvwgk great idea! Indeed, $SHELL works, so we should just implement it and that will fix this for me.

Apparently there is also $0:
$ echo $0
-bash

For shells like Bash or Zsh the shell running is always exported in the SHELL environment variable.

I think there is a difference between $SHELL and $0, as provided here:
https://stackoverflow.com/questions/9804517/difference-between-0-and-shell#:~:text=%24SHELL gives the full path,name of your current shell.

I see. The $SHELL environment variable is a shell that the use wants to be using for future shell invocations from various programs. That's a separate feature.
The main feature I want in this issue is to determine which shell I am running right now, and for that we need to implement $0 which will print the currently running program (shell).


Search bar not correctly styled

Search bar is not at the top of the home page, and it is also not responsive

switched to using grid display on the home page.
Issue fixed.


is there a way to hide the next and prev icons

i want to hide the next/prev icons in pagination. i can only find how to modify text but no hide/show icons.
my codebase is here https://codesandbox.io/s/plentific-uo68b?eslint=1&fontsize=14
table component is under componenets/table
What i want to do is show the go to 1st and got to last but hide next/prev

sorry for lately reply and so far we don't provide any solution to hide next and prev button always. However, i check your code and I see you already hide the next and prev button


Alignchecker is missing some structures

I noticed a few map types that the alignchecker doesn't cover:

EPPolicyMap
PolicyMap
Tunnel

Is there a reason to exclude these?

Excluding policy_map was an important omission, because the alignment of these structs is otherwise not validated. For EPPolicyMap / Tunnel, they reuse endpoint_key which is validated so it's only important if in future we adjust the key/value of these map types.

Is there a reason to exclude these?

I got a list of structs to check from the old alignchecker, so that's why these were excluded.


Lazy load collection to be able to use f.association for custom inputs which does not load the collection like typeahead

At this line https://github.com/plataformatec/simple_form/blob/e81af052f4bbe9e17e38c668116cd1846c6d275c/lib/simple_form/form_builder.rb#L188 simple form does load the collection regardless of being used or not on the input.
Using a select, radio or check box input it does make sense but for custom inputs like typeahead which don't use the collection, the load must be avoided.
Example:
class TypeaheadInput < SimpleForm::Inputs::StringInput
  def input
    input_html_classes << "autocomplete"

    @builder.text_field(reflection.name, input_html_options)
  end
end

f.association :user, as: :typeahead

In that example, I do not need to load any user in memory (in some cases I can't load due to the table size).
Also I can't use f.input :user because I do need the reflection on the custom input.
I thought in collection being a method on the input which only loads the collection when called, makes sense?

Not applicable for master anymore since all returns a relation on rails 4, closing.


nnbd preparation

Do you know if this will cause retrocompatibility issues on older Dart versions?

This will definitely cause issues if someone's project is too old)
I tried to use the flutter 1.12.0 but the first error was
The current Dart SDK version is 2.7.0.

Because artemis depends on gql_http_link >=0.2.9 which requires SDK version >=2.7.2 <3.0.0, version solving failed.

The nearest flutter with 2.8+ version is 1.17.0

So 1.17 (beginning of May) was the stable release just after 1.12. I think we're good with a three-month old version.


Add Organizations to Readme

To close #19

I edited around the readme, you may benefit from reading it over like a new text from my branch, here.

I changed the Our contributions part. It was in past tense which I converted to present tense and converted applicability to application. The former is probably better but also a much more difficult word.

Feel free to merge whenever you want

Slightly changed the code of conduct title, merging now.


Re-enable background location trigger

Permissions and user setting all can be re-enabled by just uncommenting out the UI in the settings view. But need to check what it would take to make the background tasks run again

done


PowerShell command does not include Windows 10 OS

Please update the PowerShell cmdlet to include Windows 10 PCs for WIA support

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

ID: 3d6a8f34-a392-d1f2-fb61-0d34bca5ab0d
Version Independent ID: a6cb49c5-2ac2-77e8-7f39-493713f7e9a8
Content: Configuring intranet forms-based authentication for devices that do not support WIA
Content Source: WindowsServerDocs/identity/ad-fs/operations/Configure-intranet-forms-based-authentication-for-devices-that-do-not-support-WIA.md
Product: windows-server-threshold
Technology: identity-adfs
GitHub Login: @billmath
Microsoft Alias: billmath

Does the PowerShell cmdlet applicable for Windows Server 2012, if not how can it be enabled on Windows Server 2012.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Don't block sbt exit forever on bg service shutdown

Some of the sbt scripted tests somewhat frequently hang in CI. I added a
patch that printed a stack trace of the sbt process every 30 seconds. I
discovered that the main thread was stuck in DefaultBackgroundJobService
shutdown. To avoid the hangs, I updated the awaitTermination methods to
take a timeout parameter and we timeout shutdown if 10 seconds have
elapsed.

Should hopefully fix #5643

Just wanted to follow up that I updated the .travis.yml to run the build that does the nio/* scripted tests and ran it 6 times with no hangs. That meant that the tests ran 30 times. Before making this change, 2 of the 5 builds in the first run hung.


[Sluggable] shouldRegenerateSlugOnUpdate should be public

https://github.com/KnpLabs/DoctrineBehaviors/blob/97bd87ef835c09307bd1477949035aabe544f3be/src/Model/Sluggable/SluggableMethodsTrait.php#L54
Should this not be public function shouldRegenerateSlugOnUpdate(): bool ?

Why do you need it to be public?

Well, imagine a scenario where you want a user to select if the slug should be automatically generated or not... You could achieve it by overriding this method. I mean what is the point in having a private method returning always true or false?

Could you provide some code snippet that demonstrates that?

Yes, okay, it is actually not needed. Sorry. Thanks.


Add lowercase aliases for currency units

Fixes #441
i didn't add  myr/rm because they conflict with milliyear/ rontometer respectively, not sure whether to special-case these ones to resolve to the currencies instead

Thank you!

Would be great if we could add eur as well.


research docker implementation/get containers set up

References user story #434

[x] begin research on setting up project in Docker container(s)
[x] initial docker setup (containers launch)

logged about 10 hours on this so far - lots of searching - lots of waiting when forcing a clean build

tack another 4-6 hours of experimentation  with configuration


Include full text of license

Hi @aidenybai. This tool looks very promising, however in order for many projects to use it legally, the full text of MIT license must be included in the project. It is not enough to mention the license name, its full text must be there in the repository. Can you make sure to add it, please?

fixed, will be released soon


it's worse than react-native-background-timer

yes, it is not working on lock screen after 1 minute. react-native-background-timer had more minutes for it

I've been using this library in production for more than a year on thousands of devices and multiple apps and this has not been my experience.
If you have a reproducible demo or a specific device or use case where the issue that you describe is present I will be willing to investigate. Otherwise, continue using the original version if that "gives you more minutes" or whatever.


Behavior for links

Describe the issue
I like md-editor very much. I'm coming from a different Markdown processor, which opens links (in the preview section) in a new browser tab. I have a lot of links in my existing Markdown content. My users got used to opening them by default in a new browser tab.
Would it be possible to have this behavior to open links configurable in md-editor? The default could still be the current behavior, which opens a link in the same browser window. By option, it should be possible to get links opened in a new browser tab. This would require to generate the corresponding HTM for links withL with target="_blank", if this config option is chosen.
Thanks for looking into this.
Procedure version
Newest version
Reproduction link
No response

I have an example that only requires a simple configuration: https://github.com/imzbf/md-editor-v3/blob/dev-docs/src/main.ts#L34

Thanks a lot! Addressed the issue by using this Link Attributes plugin. Wonderful!


build: delete benchmarks

@devversion I'd have to check in with Jeremy or Miles but I think so

that would be great, thanks

I have no problems with killing the rule as well, its in the version history if we  ever need to bring it back


Add --version flag to print ashuffle version

It would be nice if users with ashuffle binaries could easily obtain the version from the binary itself. This issue tracks that feature.

Released as v3.11.0.


Missing definitions for "default" meeting metrics

There's a handful of meeting metrics (e.g. TotalNoDoubleBooked) that you can add to the meeting query (via the organizational attribute selection interface, weirdly) that used to be "default metrics" that were returned to the query. It looks like we're missing their definitions - these metrics can also be used to filter meetings or customize a meeting metric in the person query.

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

ID: e59345bb-9abb-9e5d-8613-01c0226dfc2e
Version Independent ID: 493ac915-2a6a-a271-825a-43f40d1863e8
Content: Workplace Analytics metric definitions - Workplace Analytics Office 365
Content Source: WorkplaceAnalytics/Use/Metric-definitions.md
Product: wpa
GitHub Login: @paul9955
Microsoft Alias: v-midehm

@juchacz -Because we're working with you via email to get this updated, I'm going to close it here. Thanks for helping us keep the docs up-to-date!


Close profile airdrop popup on select

Fixes an issue @xgess noted where the popup remained even after a selection.

@keybase/picnicsquad


Multiple GPU option

I extended the code to multiple GPU training, but the GPU usage is extremely imbalanced. The root cause is that we collect all outputs back and calculate loss on one GPU. I tried to put loss calculation inside model.forward() as following:
class RNNModel(nn.Module):
        def init(...):
                super(RNNModel, self).init()
                from splitcross import SplitCrossEntropyLoss
                splits = [2800, 20000, 76000]
                self.criterion = SplitCrossEntropyLoss(ninp, splits=splits, verbose=False)
                ... ...
        def forward(...)
                ... ...
                result = output
                # calculate loss
                result = result.view(result.size(0)*result.size(1), -1)
                raw_loss = self.criterion(decoder_weight, decoder_bias, result, target)
                loss = raw_loss
                # activation regularization
                if args.alpha: loss = loss + sum(args.alpha * dropped_rnn_h.pow(2).mean() for dropped_rnn_h in outputs[-1:])
                # Temporal Activation Regularization (slowness)
                if args.beta: loss = loss + sum(args.beta * (rnn_h[1:] - rnn_h[:-1]).pow(2).mean() for rnn_h in raw_outputs[-1:])
                # expand loss to two dimensional space so it can be gathered via the second dimension
                loss = loss.unsqueeze(1)
                raw_loss = raw_loss.unsqueeze(1)
                if return_h:
                        return raw_loss, loss, hidden, raw_outputs, outputs
                return raw_loss, loss, hidden
Then, in my main.py, I collect the loss and use loss.mean().backward() to update parameters. The interesting thing is, I can successfully finish the first round loss.mean().backward() but failed the second round with error:
RuntimeError: invalid argument 3: Index tensor must have same dimensions as input tensor at
/pytorch/torch/lib/THC/generic/THCTensorScatterGather.cu:199
Can anyone help?
Thanks in advance!

I think I need to wrap a module into DataParallel in order to split target in dim=1 as well. I'm not able to make it so far. Can anyone help?
Thanks in advance!

Finally I resolved this issue. I need to reshape output after being collected, instead of reshape output in the forward function. Otherwise, the target is not the correct one for every timestamp.

The error message is still hard to track. However, I found a workaround. Mount the Criterion on multiple GPUs separately, replicate model.decoder.weights and model.decoder.bias, and feed to Criterion will work. The GPU memory usage is still a little unpredictable but much more balanced now.

Hey Songyu, I got the same imbalanced situation as you. Can you tell me how you achieved the workaround? Thanks

Hey Songyu, I got the same imbalanced situation as you. Can you tell me how you achieved the workaround? Thanks

put your loss calculation inside forward() will mitigate the issue but can't completely resolve it. Probably migrate to Tensorflow:P

Thanks I will try it :)


Authorisation Prompt freezing after selecting Google-Account

I installed the library as described in the documentation and also created a client-id for my package. I think my setup is generally supposed to be right, because I could successfully authenticate to google fit on my emulator (Android 9.0) and on my Samsung S6 (Android 7.0).
But when I run my App on my Nexus Phone (Android 8.1.0), I somehow can't authenticate. After selecting my Google-Account, the authorisation-promt is kind of freezing and only shows a loading indicator:

I can't find any helpful debug information, because the promise just doesn't seem to resovle. I also doesn't reject / throw any errors. It just doesn't do anything. Also in logcat I couldn't find any related logs / warnings. I tried using client_secrets for debug and release, both didn't help. Does anyone have an idea what could be the issue here, or how to debug further?
I am using RN Version 0.59.5 with the latest version of this package (0.9.14).
Thanks for your help!

Update: Today I found out this issues doesn't seem to be related with my phone, but with my google accout. I can also authorize on my phone when i'm using my test-account, but it freezes when I'm trying to auth with my private google accout. Closing this issue because I guess it's more a OAuth / Google problem and not related to this library. Still, any comments and ideas how to fix it would be welcome :)

In case this might help someone else:
The problem was indeed related to my private google account. It was because I was still using my<EMAIL_ADDRESS>account suffix (because it was the official suffix in germany in the past). I swichted my account to<EMAIL_ADDRESS>and now it is working fine.

I have problems with autorize as well. I keep getting "Autorisation cancelled" as soon as I select my Google account. The problem for me is for both simulators and real devices. Also I have created credentials in the Google Console for both the debug keystore and the release keystore.
I've also created the consent screen mentioned there.
What can I do?

Hi there, I am facing the same issue as the above screenshot, dialog is keep loading and loading. I am using my @gmail.com account but still having this issue, still not fixed. Any help would be appreciated.

Hi there, I am facing the same issue as the above screenshot, dialog is keep loading and loading. I am using my @gmail.com account but still having this issue, still not fixed. Any help would be appreciated.

I am seeing the same behaviour.


Upgarde 2to3 to 0.5.1

There is a new release with 2to3 0.5.1, which has a patch with hooks.
https://github.com/helm/helm-2to3/releases/tag/v0.5.1

going with a ping


Improve documentation to explain how file can be loaded from URL

The following page could be updated: https://kitware.github.io/paraview-glance/doc/index.html
to include information of https://discourse.paraview.org/t/automatically-load-data-into-paraview-glance/1539
See https://github.com/Kitware/paraview-glance/issues/232

feel free to do the edits here


How to get latest RTSP frame using gstreamer (without OpenCV)?

Hi @dusty-nv
I am connecting my Jetson Nano to a RTSP stream (Dahua camera).
The Jetson Nano is processing frames at roughly 10 FPS (9.8 - 10.2 FPS). The IP camera RTSP stream is fixed at 30 FPS. Currently the gstreamer query gets the "next" frame in the sequence, meaning that the Jetson Nano is always processing old images. For example, after 10 seconds the IP Camera RTSP stream has 300 images in the buffer, and the Jetson Nano is still processing image #100.
With OpenCV there are ways around this. For example: # https://stackoverflow.com/questions/43665208/how-to-get-the-latest-frame-from-capture-device-camera-in-opencv
But we avoid using OpenCV with the jetson-inference repo, for performance reasons.
Any suggestions for how I can configure gstreamer to get the latest image from the RTSP stream?

Hi @leenremm, the videoSource interface always returns to you the latest frame that it got from GStreamer, so the latency is coming from inside the GStreamer pipeline.  Can you try adding drop-on-latency=true to the rtspsrc element?
https://github.com/dusty-nv/jetson-utils/blob/0d3f59f5c0967a108ec1cd58a518ee5ad817d35b/codec/gstDecoder.cpp#L527
Try changing this to:  ss << " latency=" << mOptions.rtspLatency << " drop-on-latency=true";
Then run:
cd /path/to/your/jetson-inference/build
cmake ../
make
sudo make install

If that helps fix it, please let me know.

Hi,
I have tried it, but the delay is still there....
video-viewer --input-rtsp-latency=0 --input-codec=h264 rtsp//...........


No build for powerpc

Comment:
This is no build for powerpc because the build takes too long and will not complete with the time limits on any of our current (March 2023) infrastructure (Azure, TravisCI).

Probably powerpc will return when CUDA 12 is released for this feedstock.

@conda-forge-admin, please add bot automerge


[WIP] Add constant folding context menu for literals

What's new

AST Evaluation for Literals
Ability to convert literals hex-dec-bin

TODO:

[x] Remove conversions which are already in the code. Ex. 0x10 in code, remove 0x10 from the context menu.
[x] Remove context for double if it's a literal
[x] Add short and byte support
[ ] Fix int/long literals exceeding range and throwing Exception

No box type support will be given, as it also adds the need to evaluate Number#intValue() for example, which just way too much for this "simple" constant folding functionality.

Very handy addition, merged 👍


[BEAM-9010] Proper TableRow size calculation via TableRowJsonCoder

Fixes https://issues.apache.org/jira/projects/BEAM/issues/BEAM-9010
org.apache.beam.sdk.io.gcp.testing.TableContainer and org.apache.beam.sdk.io.gcp.bigquery.BigQueryServicesImpl should not rely on toString() to calculate row size. It should rely on TableRowJsonCoder.
CC: @reuvenlax

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Java PostCommit

Run Java HadoopFormatIO Performance Test

Run BigQueryIO Streaming Performance Test Java

Run Dataflow ValidatesRunner

Run Spark ValidatesRunner

Run SQL Postcommit

R: @reuvenlax

Run BeamSQL_ZetaSQL PreCommit

Thank you for this fix!

LGTM

Thank you for review.


[chore] update Go to 1.21, and update relevant pkgs

Desired Behaviour
Need to update Go to 1.21 in go.mod and in Dockerfile, and also Makefile

Minor chore on updating meshkit and meshery-adapter-library

@saurabh100ni  I would like to take on it.

@Ghat0tkach can you assign @ptdatta to the issue ?

Please assign me this issue @saurabh100ni and @Ghat0tkach

Go on @harsh098 😎✨🚀

@ptdatta do you have any updates with this, if not then we can hand over it to @harsh098

@saurabh100ni I made a PR 2 months ago for this still it not reviewed.

I have added a review to the PR @theBeginner86


Add codecov badge to README

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #77   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           6      6
  Lines         123    123
  Branches        5      5
=====================================
  Hits          123    123


Fix flaky test runFlowOnJobStatusConditionNull_2

The previous fix in #1940 did not cover the case where all the jobs have finished early before the null condition takes effect.
This fix will make sure the condition of jobC is set to null first and then evaluated.

Pull Request Test Coverage Report for Build 4052

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.01%) to 36.073%

Files with Coverage Reduction
New Missed Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/jmx/JmxJobMBeanManager.java
1
72.73%

azkaban-exec-server/src/main/java/azkaban/execapp/event/FlowWatcher.java
1
93.75%

azkaban-common/src/main/java/azkaban/executor/ExecutableFlowBase.java
1
80.42%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
1
76.67%

Totals

Change from base Build 4048:
-0.01%

Covered Lines:
10503

Relevant Lines:
29116

💛  - Coveralls