[DEFECT] Changing Gaussian Process Regressor default optimizer

Thank you for the defect report

[X] I am using the latest version of RAVEN.
[X] I have read the Wiki.
[X] I have created a minimum, reproducible example
that demonstrates the defect.

Defect Description
If GPR is used as a ROM and RBF kernel is used but the optimizer is not specified the default one will error out.
Steps to Reproduce
Just change the input file located at raven/tests/framework/ROM/SKLearn/gp.xml by removing the optimizer and specifying a kernel of RBF
Expected Behavior
Should not error out
Screenshots and Input Files

OS
MacOS
OS Version
No response
Dependency Manager
CONDA
For Change Control Board: Issue Review

[x] Is it tagged with a type: defect or task?
[x] Is it tagged with a priority: critical, normal or minor?
[x] If it will impact requirements or requirements tests, is it tagged with requirements?
[x] If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

[x] If the issue is a defect, is the defect fixed?
[x] If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?

issue checklist is satisfied. Issue can be closed with PR #1854


chore(main): release 5.1.0

:robot: I have created a release beep boop
5.1.0 (2023-08-31)
Features

removed source property from logger (9aaba5e)

Minor changes and bug fixes

more type annotation (2560f0f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mariusbegby/cadence-discord-bot/releases/tag/v5.1.0 :sunflower:


Execution failed for task ':react-native-onesignal:processReleaseResources'

Description:

Using "react-native-onesignal": "^3.2.4" with "react-native": "0.55.4" gives the following build error,

Execution failed for task ':react-native-onesignal:processReleaseResources'.
Error: more than one library with package name 'com.google.android.gms.license'

I have followed all the setup steps from the official site, including https://documentation.onesignal.com/docs/react-native-sdk-setup#section-adding-the-gradle-plugin
Also as mentioned in the footer comment of .../node_modules/react-native-onesignal/android/build.gradle, I have tried adding the following section to the top of .../android/app/build.gradle :-
plugins {     id 'com.onesignal.androidsdk.onesignal-gradle-plugin' version '0.8.1' }
apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
but it does not make any difference.

@avin3sh you are using an old version of the OneSignal Gradle plugin.
Please try using the new version, please remove the old Gradle plugin and add the new one the same way (at the top of app/build.gradle):
buildscript {
    repositories {
        maven { url 'https://plugins.gradle.org/m2/'}
    }
    dependencies {
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.10.0, 0.99.99]'
    }
}
apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'

@Nightsd01 Thank for the solution provide,
I having this issues as well, but it didn't work, the error still appear

Happens to me too. I've tried the latest gradle plugin, pinning the firebase library version while excluding gcm group from the android plugin, updating all the firebase libraries to version 15, but no luck so far. This was the last error I got: https://github.com/OneSignal/OneSignal-Android-SDK/issues/298, but wasn't able to move past that.
This is my react-native info. Does anything look out of place?
Environment:
  OS: macOS High Sierra 10.13
  Node: 10.3.0
  Yarn: 1.7.0
  npm: 6.1.0
  Watchman: 4.7.0
  Xcode: Not Found
  Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: ~0.55.2 => 0.55.4

Same here. I am also getting the same error. I have tried the above solution but it didn't work for me.

@Nightsd01 I already had those lines added to my build.gradle but I still face the issue.

Could you please provide us with all of the dependencies you are using? You can just post your package.json

I am having the same problem, here is my package.json
{
  "dependencies": {
    "native-base": "^2.4.3",
    "react": "16.3.2",
    "react-native": "0.55.3",
    "react-native-cookies": "^3.2.0",
    "react-native-elements": "^0.19.1",
    "react-native-haptic-feedback": "^1.1.0",
    "react-native-iphone-x-helper": "^1.0.3",
    "react-native-navigation": "^1.1.452",
    "react-native-onesignal": "^3.2.3",
    "react-native-scrollable-tab-view": "^0.8.0",
    "react-native-share": "^1.0.27",
    "react-native-vector-icons": "^4.6.0",
    "react-native-wkwebview-reborn": "^1.20.0",
    "react-native-xml2js": "^1.0.3",
    "react-redux": "^5.0.7",
    "redux": "^4.0.0",
    "redux-logger": "^3.0.6",
    "redux-persist": "^5.9.1",
    "redux-thunk": "^2.2.0",
    "rn-sliding-up-panel": "^1.2.0",
    "url-parse": "^1.4.0"
  },
  "devDependencies": {
    "babel-jest": "22.4.3",
    "babel-preset-react-native": "4.0.0",
    "jest": "22.4.3",
    "react-native-dotenv": "^0.1.1",
    "react-test-renderer": "16.3.1"
  },
  "jest": {
    "preset": "react-native"
  }
}

Here are the other parameter details
compileSdkVersion 23
    buildToolsVersion "23.0.1"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }

Don't have my build.gradle file anymore, but tried setting everything to > version 23 or version 26 and wasn't able to get either of them to work

Finally got this work
by removing the https://documentation.onesignal.com/docs/react-native-sdk-setup#section-adding-the-gradle-plugin
and insert compile "com.google.android.gms:play-services-base:12.0.1" at app/build.gradle
& add google() at android/build.gradle like below
buildscript {
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.1'
    }
}
allprojects {
    repositories {
        google()
        mavenLocal()
        jcenter()
        maven {
            url "$rootDir/../node_modules/react-native/android"
        }
    }
}

@neo125874 What are your compileSdkVersion and buildToolsVersion versions?

I had to make one more change. I changed to distributionUrl=https\://services.gradle.org/distributions/gradle-4.1-all.zip in gradle-wrapper.properties, and it worked. compileSdkVersion is 23 and buildToolsVersion is 23.0.1

@Nightsd01
Here is content of my package.json
"dependencies": {
    "native-base": "^2.3.9",
    "react": "16.3.1",
    "react-native": "0.55.4",
    "react-native-onesignal": "^3.2.4",
    "react-native-router-flux": "^4.0.0-beta.28",
    "react-native-smart-splash-screen": "^2.3.5"
  },
  "devDependencies": {
    "babel-jest": "22.4.1",
    "babel-preset-react-native": "4.0.0",
    "jest": "22.4.2",
    "react-test-renderer": "16.2.0"
  },
  "jest": {
    "preset": "react-native"
  }

And here is app/build.gradle
apply plugin: "com.android.application"
buildscript {
    repositories {
        maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
    }
    dependencies {
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.10.0, 0.99.99]'
    }
}

apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
import com.android.build.OutputFile

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

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

def enableProguardInReleaseBuilds = false

android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"

    //compileSdkVersion 27 //made no difference
    //buildToolsVersion "27.0.1" //made no difference

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

dependencies {
    compile project(':react-native-smart-splash-screen')
    compile project(':react-native-onesignal')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:23.0.1"
    compile "com.facebook.react:react-native:+"  // From node_modules
    //compile "com.google.android.gms:play-services-base:12.0.1" //github onesignal experiment
}

// 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'
}

I have tried with recommended and default buildTool and CompileSdk, and it did not make any difference.

@neo125874 your modification along with @dhamaniasad 's suggested changes for gradle-wrapper.properties worked!

@dhamaniasad i tried 23 or 26 could work fine, and happy to hear you got it worked!
@avin3sh congrats! it seems to be the google play service sth related.

@avin3sh @dhamaniasad I have tried as you have suggested but getting this error
com.android.build.gradle.tasks.factory.AndroidJavaCompile.setDependencyCacheDir(Ljava/io/File;)V
please help me resolve this thanks in advance

my app/build.gradle
`buildscript {
repositories {
maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
}
dependencies {
classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.10.0, 0.99.99]'
}
}
apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'
apply plugin: "com.android.application"
import com.android.build.OutputFile
/**

The react.gradle file registers a task for each build variant (e.g. bundleDebugJsAndAssets
and bundleReleaseJsAndAssets).
These basically call react-native bundle with the correct arguments during the Android build
cycle. By default, bundleDebugJsAndAssets is skipped, as in debug/dev mode we prefer to load the
bundle directly from the development server. Below you can see all the possible configurations
and their defaults. If you decide to add a configuration block, make sure to add it before the
apply from: "../../node_modules/react-native/react.gradle" line.

project.ext.react = [
// the name of the generated asset file containing your JS bundle
bundleAssetName: "index.android.bundle",

// the entry file for bundle generation
entryFile: "index.android.js",

// whether to bundle JS and assets in debug mode
bundleInDebug: false,

// whether to bundle JS and assets in release mode
bundleInRelease: true,

// whether to bundle JS and assets in another build variant (if configured).
// See http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Build-Variants
// The configuration property can be in the following formats
//         'bundleIn${productFlavor}${buildType}'
//         'bundleIn${buildType}'
// bundleInFreeDebug: true,
// bundleInPaidRelease: true,
// bundleInBeta: true,

// whether to disable dev mode in custom build variants (by default only disabled in release)
// for example: to disable dev mode in the staging build type (if configured)
devDisabledInStaging: true,
// The configuration property can be in the following formats
//         'devDisabledIn${productFlavor}${buildType}'
//         'devDisabledIn${buildType}'

// the root of your project, i.e. where "package.json" lives
root: "../../",

// where to put the JS bundle asset in debug mode
jsBundleDirDebug: "$buildDir/intermediates/assets/debug",

// where to put the JS bundle asset in release mode
jsBundleDirRelease: "$buildDir/intermediates/assets/release",

// where to put drawable resources / React Native assets, e.g. the ones you use via
// require('./image.png')), in debug mode
resourcesDirDebug: "$buildDir/intermediates/res/merged/debug",

// where to put drawable resources / React Native assets, e.g. the ones you use via
// require('./image.png')), in release mode
resourcesDirRelease: "$buildDir/intermediates/res/merged/release",

// by default the gradle tasks are skipped if none of the JS files or assets change; this means
// that we don't look at files in android/ or ios/ to determine whether the tasks are up to
// date; if you have any other folders that you want to ignore for performance reasons (gradle
// indexes the entire tree), add them here. Alternatively, if you have JS files in android/
// for example, you might want to remove it from here.
inputExcludes: ["android/", "ios/"],

// override which node gets called and with what additional arguments
nodeExecutableAndArgs: ["node"],

// supply additional arguments to the packager
extraPackagerArgs: []
]
*/

project.ext.react = [
entryFile: "index.js"
]
apply from: "../../node_modules/react-native/react.gradle"
/**

Set this to true to create two separate APKs instead of one:

An APK that only works on ARM devices

An APK that only works on x86 devices

The advantage is the size of the APK is reduced by about 4MB.
Upload all the APKs to the Play Store and people will download
the correct one based on the CPU architecture of their device.
*/
def enableSeparateBuildPerCPUArchitecture = false

/**

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

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

}
dependencies {
compile project(':react-native-onesignal')
compile fileTree(dir: "libs", include: ["*.jar"])
compile "com.android.support:appcompat-v7:23.0.1"
compile "com.facebook.react:react-native:+"  // From node_modules
compile "com.google.android.gms:play-services-base:12.0.1" //github onesignal experiment
}
// 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'
}
`
my gradle
`// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
jcenter()
google()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.2.3'
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
repositories {
mavenLocal()
jcenter()
google()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
}
}
`
package.json
{   "name": "onesignal",   "version": "0.1.0",   "private": true,   "devDependencies": {     "babel-preset-react-native-stage-0": "^1.0.1",     "jest": "^23.1.0",     "jest-react-native": "^18.0.0",     "react-test-renderer": "16.3.1"   },   "scripts": {     "start": "react-native start",     "android": "react-native run-android",     "ios": "react-native run-ios",     "test": "jest"   },   "jest": {     "preset": "react-native"   },   "dependencies": {     "react": "16.3.1",     "react-native": "~0.55.2",     "react-native-onesignal": "^3.2.4"   } }

@avin3sh @dhamaniasad can I get the repo of your project to compare?

@Nightsd01 please help

@davekedar did you update the gradle wrapper version?
If so, you need to update your gradle file dependencies from
classpath 'com.android.tools.build:gradle:2.2.3'
to
classpath 'com.android.tools.build:gradle:4.4' (or whatever version you are using)
Here is the article I referred to make it work. https://medium.com/@chuckyong_3313/react-native-android-build-compilation-issue-with-google-play-api-for-android-v12-0-0-ccb2f1a0fb9c

@ashishmusale which is your android studio version? I have upgraded the studio version 3.1.3
gradle-wrapper.properties
#Fri Jun 08 10:09:57 IST 2018
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip

app/build.gradle
buildscript {
    repositories {
        maven { url 'https://plugins.gradle.org/m2/' } // Gradle Plugin Portal
    }
    dependencies {
        classpath 'gradle.plugin.com.onesignal:onesignal-gradle-plugin:[0.10.0, 0.99.99]'
    }
}

apply plugin: 'com.onesignal.androidsdk.onesignal-gradle-plugin'

apply plugin: "com.android.application"

import com.android.build.OutputFile

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

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

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

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

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

android {
    compileSdkVersion 27
    buildToolsVersion '27.0.3'

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

dependencies {
    compile project(':react-native-onesignal')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:23.0.1"
    compile "com.facebook.react:react-native:+"  // From node_modules
}

// 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'
}

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

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

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

allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
    }
}

ext {
    googlePlayServicesVersion = '11.8.0'
    compileSdkVersion = 27
    buildToolsVersion = '27.0.3'
    supportLibrariesVersion = '27.1.0'
}
// Force sub libs to use the compile sdk & build tools version
subprojects { subproject ->
    afterEvaluate{
        if((subproject.plugins.hasPlugin('android') || subproject.plugins.hasPlugin('android-library'))) {
            android {
                compileSdkVersion rootProject.ext.compileSdkVersion
                buildToolsVersion rootProject.ext.buildToolsVersion
            }
        }
    }
}

and getting error

Could not find firebase-messaging.jar (com.google.firebase:firebase-messaging:12.0.0).
Searched in the following locations:
https://jcenter.bintray.com/com/google/firebase/firebase-messaging/12.0.0/firebase-messaging-12.0.0.jar

https://github.com/davekedar/onesignal-error.git this is my repo for testing can you please help to resolve ?
Thanks in Advance @ashishmusale

@davekedar I have seen some issues as of late with jcenter no longer resolving Google libraries. I recommend adding google() to your allprojects {  repositories { ... } } section which should fix this error.
allprojects {
    repositories {
        mavenLocal()
        google()
        jcenter()
        // ...
   }
}

@ashishmusale  @jkasten2  Thanks it is working now. But, it is not getting registered with One Signal
this is my app.js
import React from 'react';
import { StyleSheet, Text, View } from 'react-native';
import OneSignal from 'react-native-onesignal'; // Import package from node modules

export default class App extends React.Component {
  state = {
    device : ''
  }
  componentWillMount() {
      OneSignal.init("206a6513-b453-4807-89c1-040389fa8dea");

      OneSignal.addEventListener('received', this.onReceived);
      OneSignal.addEventListener('opened', this.onOpened);
      OneSignal.addEventListener('ids', this.onIds);
  }
  componentWillUnmount() {
      OneSignal.removeEventListener('received', this.onReceived);
      OneSignal.removeEventListener('opened', this.onOpened);
      OneSignal.removeEventListener('ids', this.onIds);
  }
  onReceived(notification) {
      console.log("Notification received: ", notification);
  }
  onOpened(openResult) {
    console.log('Message: ', openResult.notification.payload.body);
    console.log('Data: ', openResult.notification.payload.additionalData);
    console.log('isActive: ', openResult.notification.isAppInFocus);
    console.log('openResult: ', openResult);
  }
  onIds(device) {
		this.setState({device: device})
  }
  render() {
    return (
      <View style={styles.container}>
        <Text>Open up App.js to start working on your app!</Text>
        <Text>Changes you make will automatically reload.</Text>
        <Text>Shake your phone to open the developer menu.</Text>
        <Text>Device Info : {this.state.device}</Text>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: '#fff',
    alignItems: 'center',
    justifyContent: 'center',
  },
});

@ashishmusale I have commited the final compiled version if you can check

Everything is done successfully Thank you all

Glad to hear it!

can any one give me a fully confiured project , working well .... i am stuck for 2 days. nothing working for me.....................plz

@nahidmbstu tell me where you are stuck there are very strange problem with everyone, let's try to solve it for you

i am gcm lincence error on 3.1.4 and when i am trying the example project from this repo , it not working .....i need some configured project with notification working...

download from here https://github.com/davekedar/onesignal-error

getting Push token null............. on device ID. @davekedar

@nahidmbstu have you tried to build a new fresh project ?

thanks , i had a problem with google play service , that why it caused. i have solved it by follow
https://github.com/geektimecoil/react-native-onesignal/issues/387

@nahidmbstu wonderful


There is no command "Create Container App from Workspace..." in command palette

OS: All
Build Version: 20231012.2
Regression: Not a Regression
Repro Steps:

Right click one container apps environment and there is one action "Create Container App from Workspace...".

F1 to open the command palette.
Check whether there is a command "Create Container App from Workspace..." in command palette.

Expect:
There is a command "Create Container App from Workspace..." in command palette.
Actual:
There is no command "Create Container App from Workspace..." in command palette.

Closing this one as by-design.  There is only one command palette command for this series of commands:
Deploy Project from Workspace...


[DPEDE-1225] Add large header option to portal

@jllr @josecarlosgonzalezv
Need advise:

for portal, header were already large size, I set all header to base size and set the new one only to large
regarding the dropdown menus, there's no option to remove chevron

@jllr @josecarlosgonzalezv
Need advise:

for portal, header were already large size, I set all header to base size and set the new one only to large
regarding the dropdown menus, there's no option to remove chevron

Confirmed all headers should be large for portal
Dropdown menu styles applied

Also, a visual test for lg size with dropdown menu should be created (similar to this: XL Header with Navbar)

@jllr Visual test created

@emerson-pereira I will chek the chevron update when the PR builds. Thanks!


Don't Merge! PR real time test for target branch full build

Docs Build status updates of commit fd6c6f1:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit fd6c6f1:
:clock10: Full build: the average full build time is 7 min(s) 16 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit fd6c6f1:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[GC] Partition and aggregate expired addresses more efficiently

New flow:

Work on RDDs that hold expired and kept ranges/addresses together

Remove range duplicates

Compute a reasonable number of range IDs to expand per partition.
New configuration option:
lakefs.gc.address.approx_num_ranges_to_spread_per_partition

Expand ranges and hash-partition
We hash-partition rather than range-partition.  Range partitions work well
(give similar sizes) when Spark can compute a good "sketch" of the ranges.
However we need to reduce over object addresses.  Object addresses are
random and appear with a very unstable distribution.  So there is no
good way for Spark to find a good range partition.  Hash partitions can
have their sizes skewed by around $3\cdot\sqrt N$; even for N=1000
partitions this is very acceptable.

Directly aggregateByKey to reduce addresses and find those that appear
only in expired commits.

Also close and delete ranges and metaranges when we are done with them.
This is surprisingly difficult to do correctly in a garbage-collected
language, because it is hard to track lifetimes.  In particular, iterators
extend lifetime beyond dynamic scope.[^1]
Fixes #5612.
[^1]: It is embarrassingly easy to do this in a language with explicit
lifetimes, such as C++.  And also faster.

Reviewer: Please pay special attention to bugfix 4e3a5682dd0fcebbd4eb5dc62c37eb213a4a272b.  This is a mistake that we have managed to make on every rewrite of the code.  (Luckily this time around we have tests, but it does indicate again that caution is required when writing and reviewing this code!)

Thanks!
Pulling after doing all the easy bits you requested :-)


Partial constructor application ponyc segfault

Minimal example:
actor Main
  new create(env: Env) =>
    Main~create()

Partial application of a constructor (actor, class) segfaults with an LLVM error.

0.52.0-a48b9ddf [release]
Compiled with: LLVM 14.0.3 -- Clang-13.0.1-x86_64
Defaults: pic=true
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Segmentation fault (core dumped)

Can you build a debug version of the runtime and compiler and run the program again under a debugger and report back with a backtrace?

I've added "good first issue" to this as at the moment, the first step is triaging which is a good first issue. Depending on what is found, the label will probably come off.

Generating
 Reachability
 Selector painting
 Data prototypes
 Data types
 Function prototypes
 Functions
/ponyc/src/libponyc/codegen/genexpr.c:314: gen_assign_cast: Assertion `r_value != GEN_NOTNEEDED` failed.

Backtrace:
  /ponyc/build/debug/ponyc(ponyint_assert_fail+0x96) [0x563f11f383e6]
  /ponyc/build/debug/ponyc(gen_assign_cast+0x67) [0x563f11e55f67]
  /ponyc/build/debug/ponyc(gen_call+0x789) [0x563f11e4eb29]
  /ponyc/build/debug/ponyc(gen_expr+0x1b8) [0x563f11e55b68]
  /ponyc/build/debug/ponyc(gen_seq+0x54) [0x563f11f0a9b4]
  /ponyc/build/debug/ponyc(gen_expr+0x76) [0x563f11e55a26]
  /ponyc/build/debug/ponyc(+0x7090d3) [0x563f11f0f0d3]
  /ponyc/build/debug/ponyc(+0x7082d6) [0x563f11f0e2d6]
  /ponyc/build/debug/ponyc(genfun_method_bodies+0x99) [0x563f11f0e109]
  /ponyc/build/debug/ponyc(gentypes+0x370) [0x563f11e6e000]
  /ponyc/build/debug/ponyc(genexe+0x2c6) [0x563f11e55036]
  /ponyc/build/debug/ponyc(codegen+0xd4) [0x563f11e49b44]
  /ponyc/build/debug/ponyc(generate_passes+0x33) [0x563f11e964f3]
  /ponyc/build/debug/ponyc(+0x637b3b) [0x563f11e3db3b]
  /ponyc/build/debug/ponyc(main+0x261) [0x563f11e3d971]
  /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7fd46d5ebd90]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7fd46d5ebe40]
  /ponyc/build/debug/ponyc(_start+0x25) [0x563f11e3d645]
PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
Aborted (core dumped)

gen_assign_cast in genexpr.c fails when ast is a typeref. The error only happens when using partial application on constructors from a type, but not a variable:
class A
struct B
class Main
  new create(env: Env) =>
    Main~create() // fails
    this~create() // works
    A~create() // fails
    let a = A
    a~create() // works
    B~create() // fails
    let b = B
    b~create() // works

The types encountered before failing are Main tag, A ref, and B ref respectively.

We discussed this a bit in today's sync call.
The assertion is happening during LLVM code generation, where the code that generates a call site is trying to use the partially applied receiver as a call argument value - the assertion comes when trying to "cast" that value to the param type.
In Pony, a type by itself does not have a value, hence we get the GEN_NOTNEEDED as the value, which cannot be cast.
I believe the correct fix is to add a special case path for constructors in the part of the compiler that sugars the partial application into a lambda, such that we use the type as a receiver rather than the "value" of that type (which again, does not exist in Pony).
There's already a special code path for "bare" functions, which has some relevant code I think we can leverage, so perhaps the fix is as simple as what I've pasted below. However, I have not tested this yet.
Whoever works on this issue could use this as a starting point and reach out in Zulip or on this ticket if they need more guidance.
diff --git a/src/libponyc/expr/call.c b/src/libponyc/expr/call.c
index 6fac89e2..c2862068 100644
--- a/src/libponyc/expr/call.c
+++ b/src/libponyc/expr/call.c
@@ -795,6 +795,7 @@ static bool partial_application(pass_opt_t* opt, ast_t** astp)
   AST_GET_CHILDREN(type, cap, type_params, target_params, result);

   bool bare = ast_id(cap) == TK_AT;
+  bool is_constructor = ast_id(method_ast) == TK_NEW;

   token_id apply_cap = TK_AT;
   if(!bare)
@@ -819,7 +820,10 @@ static bool partial_application(pass_opt_t* opt, ast_t** astp)

       arg = ast_sibling(arg);
     }
+  }

+  if(bare || is_constructor)
+  {
     ast_t* receiver_type = ast_type(receiver);
     if(is_bare(receiver_type))
     {


RAM requirements on quantization

In the docs quantization section, it specifies how much VRAM is required to quantize models. However, my quantization process gets terminated due to excessive RAM usage, even when quantifying a relatively small model like OpenLLama-3B. I have 16 GB of RAM on my machine. Is there a way to reduce RAM usage?
There is my log:
-- Resuming job
 !! Note: Overriding options with settings from existing job
 -- Input: /home/jovyan/project/quantization/open_llama_3b_v2
 -- Output: /home/jovyan/project/quantization/tmp-open_llama
 -- Calibration dataset: /home/jovyan/project/quantization/wikitext-test.parquet, 100 / 16 (0) rows, 2048 tokens per sample
 -- Target bits per weight: 4.0 (decoder), 6 (head)
 -- Max shard size: 8192 MB
 -- Full model will be compiled to: ../open_llama_3b_v2-exl2-4bpw
 -- Quantizing...
 -- Layer: lm_head (Linear)
 -- Linear: lm_head -> 0.15:8b/0.85:6b 32g s4, 6.45 bpw
Killed

The problem is in output_states_list in quantize.py, it grows very large in size and eats up all the memory. I wonder if there any way to use tensors from this list immediately and get rid of them.


Implement Dependency RFCs 0003-0006: Dependency Management

This is the top-level tracking issue for implementing the Dependency Management RFC suite:

Overview RFC
Phase 1 RFC
Phase 2 RFC
Phase 3 RFC

Phase 1 - Adopting Federated Model
A dependency-specific top-level tracking issue for each dependency in the list can be filed on the buildpack repository of interest using the following template.

Issue Template
Title: Implement Dependency RFC 0004 for <Dependency>

Implement [Dependency Management RFC Phase 1](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md) for \<INSERT DEPENDENCY\>. Check out the RFC for more details and background.

### 1. Determine dependency source strategy
<details>
<summary>Background</summary>

When possible, dependencies should be used directly from upstream, rather than undergoing any additional compilation or modifications performed by Paketo-maintained code. For each dependency, the corresponding buildpack maintainer group will decide if the dependency can be used directly from upstream, and must identify the location from which the dependency will be pulled from. Some of the Paketo Java buildpacks perform directory stripping during the buildpack build process itself. This could be a viable alternative to performing directory modifications during the dependency management process for maintainers to consider.
</details>

- [x] Determine whether the dependency can be used directly from its upstream, rather than undergoing additional compilation/modification.
* If using directly from upstream, note where dependencies will come from
* If compiled or modified, note the decision for this
- [x] Document decision in a language-family level RFC. This decision can be combined in the RFC with the decision made for other buildpacks in the language family.

### 2. Version retrieval and metadata generation code
Please refer to the [retrieval RFC section](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#1-version-retrieval-make-retrieve) on version retrieval for details around the API and background.

- [x] Create retrieval code for the dependency
* Will live in the buildpack under: `dependency/retrieval/`
* Per [the RFC](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#transfercombine-version-retrieval-and-metadata-generation), this will be a combination of (1) discovering new dependency versions based on the `buildpack.toml`, and (2) generating metadata for each new version.
* **Note** : Per [the RFC caveat](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#caveat-compiled-dependencies) - if the dependency is to be compiled, the `SHA256` and `URI` field from the metadata should be omitted in this step.

### 3. Compilation code (if needed)
If the dependency will be compiled/modified, then refer to the [compilation RFC section](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#2-compilation) for API details and background.

- [x] Create compilation action
* Will live in the buildpack under: `dependency/actions/compile/`

### 4. Dependency testing (optional)
It's up to maintainer discretion if the dependency will be tested. It's recommended to test the dependency if it's been compiled. Check out the [testing RFC section](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#3-test-dependency-make-test) for details.

- [ ] Add tests for dependency
* Will live in the buildpack under: `dependency/test.`

### 5. Makefile Setup
When using the generalized workflows for dependency management down the line, version retrieval and dependency testing will be executed via a Makefile in order to provide the workflow a standardized way to run the code, regardless of what language it was written in. Check out the [RFC section](https://github.com/paketo-buildpacks/rfcs/blob/main/text/dependencies/rfcs/0004-dependency-management-phase-one.md#overarching-plan) for what this should look like.

- [ ] Add Makefile
* Will live in the buildpack at: `dependency/Makefile`

### 6. Leveraging the new code
This issue serves to set up all the main logic for the dependency management. The work to actually leverage this code and migrate off of the dep-server will be completed in a separate issue once workflows and infrastructure is set up.

Dependency List:

[x] bundler - https://github.com/paketo-buildpacks/bundler/issues/386
[X] composer - https://github.com/paketo-buildpacks/composer/issues/55
[X] curl - https://github.com/paketo-buildpacks/passenger/issues/254
[ ] dotnet-aspnetcore - https://github.com/paketo-buildpacks/dotnet-core-aspnet/issues/368
[ ] dotnet-runtime - https://github.com/paketo-buildpacks/dotnet-core-runtime/issues/372
[X] dotnet-sdk - https://github.com/paketo-buildpacks/dotnet-core-sdk/issues/390
[X] go - https://github.com/paketo-buildpacks/go-dist/issues/435
[x] httpd - https://github.com/paketo-buildpacks/httpd/issues/355
[X] icu - https://github.com/paketo-buildpacks/icu/issues/288
[x] nginx - https://github.com/paketo-buildpacks/nginx/issues/414
[X] node - https://github.com/paketo-buildpacks/node-engine/issues/508
[X] php - https://github.com/paketo-buildpacks/php-dist/issues/415
[X] pip - https://github.com/paketo-buildpacks/pip/issues/289
[X] pipenv - https://github.com/paketo-buildpacks/pipenv/issues/252
[x] python - https://github.com/paketo-buildpacks/cpython/issues/393
[x] poetry - https://github.com/paketo-buildpacks/poetry/issues/86
[X] ruby - https://github.com/paketo-buildpacks/mri/issues/393
[x] rust - https://github.com/paketo-community/rust-dist/issues/199
[x] tini - https://github.com/paketo-buildpacks/tini/issues/223
[X] yarn - https://github.com/paketo-buildpacks/yarn/issues/261

Phase 2 - Workflow and Github Action Generalization

[x] Create new jam command for assembly - https://github.com/paketo-buildpacks/jam/issues/104
[x] Create new dependency update workflow - https://github.com/paketo-buildpacks/github-config/issues/529

Phase 3 - Migrating to the New System

[x] (Per dependency) Disable the old update-dependencies workflow - once Phase 1 is complete for a dependency, and Phase 2 is complete, the old update-dependencies workflow can be disabled for the repository in the Github Actions UI.
[x] Remove the old update-dependencies workflow from github-config - once every dependency has been moved over to the new system, remove the old update-dependencies workflow all together.
[ ] Remove the old jam update-dependencies command - once every dependency has been moved over to the new system, the new jam command created in Phase 2 can fully replace the old command.
[ ] Archive the dep-server repository - once every dependency in the dep-server has been moved to the new system, the dep-server repository can be archived so that the workflows stop running.

At this point, the dependency management system has been implemented. The final step of spinning down the dep-server and removing related tooling is now represented by separate issues and this issue can be closed out.
https://github.com/paketo-buildpacks/dep-server/issues/270
https://github.com/paketo-buildpacks/jam/issues/196


touchedObject strange result

Way to reproduce:

Grab an object with your right controller, so touchedObject in interactTouch on right controller is this object now
Touch the object with left controller , so touchingObject in InteractableObject on the object is left controller
If I call SetActive(false) on that object, OnTriggerExit will not be called, so even ForceStopInteracting is called, the touchedObject on the right controller will stay as the object because touchingObject is the left controller, thus causing bug

Does this PR fix your issue?
https://github.com/thestonefox/SteamVR_Unity_Toolkit/pull/242

@stevenwanhk ok, what if the ForceStopTouching happens before the ForceRelease or ForceStopUsing as in this commit:
https://github.com/thestonefox/SteamVR_Unity_Toolkit/pull/242/commits/40fa57792b310b233aad4ce334809bde45346448
Does that fix it?


[Bug]: Unable to import attached json file in the airgapped image

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I try to import the attached application, I get an error to the effect unable to connect to server.
Steps To Reproduce

Take the pull of the airgapped image, and set it up without internet
Try to import the attached file [rename it to json]
Note that import does not work and error pops up.

OldApp_DSTesting1.9.24.txt

Note: The attached app has Airtable / GSheets and other SAAS plugins. Since Airgapped does not support these plugins, if thats the reason for this failure, then an appropriate message needs to be given - or there should be some way of handling that portion in the import modal.
Public Sample App
No response
Environment
Release
Issue video log
No response
Version
Self Hosted

It's because of the unsupported DS

In the current airgapped regression also we are seeing the above issue, and also, sometimes we see a broken UI, which is not such a great user experience. Though it is a case with unsupported datasources, it should be handled gracefully.
https://github.com/appsmithorg/appsmith/assets/101863839/036d9f61-a8c9-486d-8031-2c03d2341095

@btsgh  - GSheets is not supported and should not exist in Airgapped apps. Any failues because of that can be ignored.


client.get is missing

It would be nice if there was a simple get by id function

Thank you for your advice. In this project, I only added some APIs that I currently use in nestjs. If there are any APIs that do not meet your needs, you can fork them and I will merge them.
I've been busy recently. I may not have enough time to spend on it. I may spend more time dealing with Mongo.
Now you can use like this:
const findById = async () => {
  try {
    const info = await client.get({
      index: "myindex",
      id: "11",
    });
    console.log(info);
  } catch (error) {
    console.error(error);
  }
};


validate blockchain cli codegen

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

@changlong-liu since these are all cli change, you can merge it whenever you want. If you need other cli team to review as well please add them.

/azp run automation - sdk

@changlong-liu PR not update for weeks. Let me know if you want to merge it, or no longer need it.

Hi @weidongxu-microsoft , would you help to merge this? I found I don't have permission doing this. Thank you so much!


Log correlation for Go

Is your feature request related to a problem? Please describe.
Log correlation draft:
https://github.com/census-instrumentation/opencensus-specs/blob/master/trace/LogCorrelation.md
Java implementation:
https://github.com/census-instrumentation/opencensus-java/tree/master/contrib/log_correlation/log4j2
Since there's no dominant logging library in Golang(unlike Java), things are a bit more complicated here. So I wonder if there's a plan to implement  log correlation for Go?
Describe the solution you'd like
Integrated contextual logging support for popular logging libraries like logrus, zap, etc.
Describe alternatives you've considered
Related issue:
https://github.com/census-instrumentation/opencensus-specs/issues/130

It would be great if this client supporting a Logger interface as a dependency. Something like
https://godoc.org/github.com/go-kit/kit/log
type Logger interface {
    Log(keyvals ...interface{}) error
}

That way you can pass in your needed logger (go-kit native logger) or an adapter for logrus, zap, etc.


incorrect suggestion to use newtype instead of data for unlifted datatypes

Bug
type Wrap :: UnliftedType -> Type
data Wrap a = Wrap a

triggers "Use newtype instead of data" which is incorrect (this is also true for the opposite direction, i.e. Type -> UnliftedType
hlint version
λ ι hlint --version
HLint v3.5, (C) Neil Mitchell 2006-2022

Note
It is not sufficient to actually look for things suffixed with # because
a. it's a convention
b. we have a UnliftedDataTypes extension

It's OK for HLint to follow conventions, because this is really a tool about making people follow more conventions. Is this something that came up in practice for you? Or just a thought experiment?

It came up in practise. I have a data family I which can be of kind UnliftedType to Type but that has to be a data, not a newtype. It's not terribly important though as i guess it's not occurring to often


New default value for DerivedQuantities.show_units

Fixes #860 but instead of deprecating the show_units argument, I just have it default to True.
What do you think @jhdark @KulaginVladimir? I thought it'd be nice to keep the functionality in case someone doesn't want the units in (eg. they are working in moles)...

Also might be worth adding another test for all the derived quantities without units, as many aren't being test at the moment (avg_surf, avg_vol, max_surf, max_vol, min_surf, min_vol, point_value, tot_surf, tot_vol). Just to get the full coverage

@jhdark @KulaginVladimir can we merge this?


To Do: Design adapter board for 2 individual ESCs

Adrian

You may not need a board; didn't Eli say that you could get a Chinese factory to crimp cables for you? It's pretty simple to make a simple wiring adaptor for this; I can post pictures later

Oh yeah that's a pretty good idea! I must have missed where Eli suggested that. I'll look into it.


stack.startsWith is not a function

I am running into an issue where my Meteor methods are not returning errors. It appears that the agent is recording the server side error but before the error is sent to the client this happens:
W20200626-22:41:49.476(-4)? (STDERR) (node:54484) UnhandledPromiseRejectionWarning: TypeError: stack.startsWith is not a function
W20200626-22:41:49.476(-4)? (STDERR)     at formatError (internal/util/inspect.js:915:13)
W20200626-22:41:49.477(-4)? (STDERR)     at formatRaw (internal/util/inspect.js:703:14)
W20200626-22:41:49.477(-4)? (STDERR)     at formatValue (internal/util/inspect.js:591:10)
W20200626-22:41:49.482(-4)? (STDERR)     at inspect (internal/util/inspect.js:221:10)
W20200626-22:41:49.482(-4)? (STDERR)     at formatWithOptions (internal/util/inspect.js:1693:40)
W20200626-22:41:49.483(-4)? (STDERR)     at Object.Console.<computed> (internal/console/constructor.js:272:10)
W20200626-22:41:49.483(-4)? (STDERR)     at Object.log (internal/console/constructor.js:282:61)
W20200626-22:41:49.483(-4)? (STDERR)     at Object.Meteor._debug (packages\meteor.js:1055:23)
W20200626-22:41:49.484(-4)? (STDERR)     at wrapInternalException (packages/ddp-server/livedata_server.js:1741:12)
W20200626-22:41:49.484(-4)? (STDERR)     at packages/ddp-server/livedata_server.js:745:25
W20200626-22:41:49.484(-4)? (STDERR)     at C:\Users\xxxxxx\AppData\Local\.meteor\packages\promise\0.11.2\npm\node_modules\meteor-promise\fiber_pool.js:43:40
I20200626-22:41:49.484(-4)? Sending error to Elastic APM { id: '74a6c5a216950b4a1b3f85f1b141628e' }

The client never gets the method callback. This was captured by the APM agent:
{"stack":{"stack":"TypeError: Cannot read property 'email' of undefined\n at MethodInvocation.finishEnrollment (server/methods.js:391:52)\n at MethodInvocation.<anonymous> (packages/kschingiz:meteor-elastic-apm/instrumenting/methods.js:36:42)\n at maybeAuditArgumentChecks (packages/ddp-server/livedata_server.js:1771:12)\n at packages/ddp-server/livedata_server.js:719:19\n at Meteor.EnvironmentVariable.EVp.withValue (packages\\meteor.js:1234:12)\n at packages/ddp-server/livedata_server.js:717:46\n at Meteor.EnvironmentVariable.EVp.withValue (packages\\meteor.js:1234:12)\n at packages/ddp-server/livedata_server.js:715:46\n at new Promise (<anonymous>)\n at Session.method (packages/ddp-server/livedata_server.js:689:23)\n at Session.<anonymous> (packages/kschingiz:meteor-elastic-apm/instrumenting/session.js:47:25)\n at packages/ddp-server/livedata_server.js:559:43","source":"method"},"message":"Cannot read property 'email' of undefined"}

I am currently running Meteor 1.9. With the following package versions as Meteor auto added them:
kschingiz:meteor-elastic-apm  added, version 2.4.0
kschingiz:meteor-measured     added, version 1.0.3
mongo-livedata                added, version 1.0.12

Any help on this would be greatly appreciated!

@Zjcompt Hi, I've checked the apm code, seems the problem is occurred on your method function code, could you please provide some simplified function code to understand why this happened? Better some small meteor project with the steps to reproduce.
Thanks!

I'm closing this issues since we haven't heard back from @Zjcompt , feel free to re-open this issue with a reproduction.


[FLINK-11629][rpc] Stop AkkaRpcActor immediately after onStop future has been completed

What is the purpose of the change
The AkkaRcpActor should stop itself immediately after the onStop future has been completed.
Before we sent a Kill message which enqueues into the mailbox and does not overtake messages.
Now we call Context.stop(ActorRef) which directly stops the AkkaRpcActor.
Verifying this change

Added AkkaRpcActorTest#testOnStopFutureCompletionDirectlyTerminatesAkkaRpcActor.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@flinkbot approve all

Thanks for the review @StefanRRichter. Merging this PR.


RAII enable

We have enabled the exception handle due to the need of error message for c_api.
However, There still are many raw pointers in the project. Some pointers may not could free its resource while exception occurs.
For the better robustness, I think we need RAII now.

Lets' create a new branch for the re-construct

refer to #86


general behaviour in tetrads.R

Hi Joshua
I tweaked a few lines to make this mimic the original function.
The biggest changes were lines 341-398 and importer/exporter arguments were inverted (my fault!)
Line 374 can be improved but I don't exactly know how to move from
model_tetrads_vcov <- multiwayvcov::cluster.vcov(model = model_tetrads, cluster = ~ iso_o + iso_d)

to something like
model_tetrads_vcov <- multiwayvcov::cluster.vcov(model = model_tetrads, cluster = ~ c(!!sym("code_o") + !!sym("iso_d"))

or it won't work if the user has different column names

What about:
form2 <- as.formula("~ iso_o + iso_d")
model_tetrads_vcov <- multiwayvcov::cluster.vcov(model = model_tetrads, cluster = form2)

it worked as
form2 <- as.formula(sprintf("~ %s + %s", code_o, code_d))
...
model_tetrads_vcov <- multiwayvcov::cluster.vcov(model = model_tetrads, cluster = form2)

Now I understand your point!


Optionally require pytest-runner

There is a suggestion that pytest-runner only be added to setup_requires when test or pytest is in the setup.py invocation. Should be easy enough to do. Am raising it here for consideration.
ref: https://github.com/pytest-dev/pytest-runner#considerations
xref: https://github.com/conda-forge/dask-core-feedstock/issues/1

cc-ing @Horta who added pytest-runner.


Image name overridden when deploying in openshift sandbox

I'm trying to deploy a function to my sandbox cluster. I want to push the image to quay registry but the cli tries to use the private one. Is this a bug or it is normal? If so, why? Thanks :pray:
The image field in func.yaml is empty before executing the command then it gets populated by quay.io... and then overridden.
func deploy -p '/home/luca/demo-func/func2203' -i quay.io/lstocchi/func2203:latest -n lstocchi-dev
   🙌 Function image built: image-registry.openshift-image-registry.svc:5000/lstocchi-dev/func2203:latest
Error: failed to get credentials: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": failed to start dialer container: reason: ErrImagePull, message: rpc error: code = Unknown desc = reading manifest <IP_ADDRESS>-r0 in docker.io/alpine/socat: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Private cluster should be just default. If you explicitly set image by -i quay.io/lstocchi/func2203:latest then the image should be used. I seems to work for me. Could you please try with latest version?

Private cluster should be just default. If you explicitly set image by -i quay.io/lstocchi/func2203:latest then the image should be used. I seems to work for me. Could you please try with latest version?

Nope. My bad. It's not works. It's a bug.

It seems that registry -r take precedence before image in config.
See https://github.com/knative-sandbox/kn-plugin-func/issues/506
When you are on OpenShift cluster then the -r flag is defaulted to internal registry.
Workaround for now: func deploy -v -i quay.io/lstocchi/func2203:latest -r '' -- explicitly set -r to empty string.

/remove-lifecycle stale


ExecStartPre and ExecStartPost properties of SystemD unit file points to wrong path

:speaking_head: Foreword
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
:ghost: Non-existing path for ExecStartPre and ExecStartPost properties of SystemD unit file
During bootstrapping of Debian 11 node with this cookbook mysql service fails to start due to wrong path for ExecStartPre and ExecStartPost properties of SystemD unit file.
root@srv2800:~# journalctl -xe
[Brief Description](mysql.service: Failed at step EXEC spawning /usr/share/mysql/mysql-systemd-start: No such file or directory)
Subject: Process /usr/share/mysql/mysql-systemd-start could not be executed
Defined-By: systemd

root@srv2800:~# systemctl cat mysql
# /etc/systemd/system/mysql.service
[Unit]
Description=mysql_service[mysql-default]
After=syslog.target
After=network.target

[Service]
Type=simple
User=mysql
Group=mysql
PermissionsStartOnly=true
ExecStartPre=/usr/share/mysql/mysql-systemd-start pre

ExecStart=/usr/sbin/mysqld --defaults-file=/etc/mysql/my.cnf --basedir=/usr
ExecStartPost=/usr/share/mysql/mysql-systemd-start
TimeoutSec=300
Restart=on-failure
RuntimeDirectory=mysqld
RuntimeDirectoryMode=755

[Install]
WantedBy=multi-user.target

root@srv2800:~# ls -la /usr/share/mysql/mysql-systemd-start
ls: cannot access '/usr/share/mysql/mysql-systemd-start': No such file or directory

:pancakes: Cookbook version
cookbook version 11.0.5 - latest at time of submitting this issue (26th Sep 2022)
:woman_cook:  Chef-Infra Version
root@srv2800:~# chef-client -v
Chef Infra Client: 17.10.3

:tophat: Platform details
Platform detail:
root@srv2800:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

I am using recommended mysql APT repo from official mysql docs https://dev.mysql.com/doc/mysql-apt-repo-quick-guide/en/#repo-qg-apt-repo-manual-setup
root@srv2800:~# cat /etc/apt/sources.list.d/mysql.list
deb      http://repo.mysql.com/apt/debian/ bullseye mysql-8.0

:police_car: Expected behavior
It seems APT packages for mysql v8 installs SystemD unit files into path /usr/share/mysql-8.0/ and not into path /usr/share/mysql.
root@srv2800:~# ls -ald /usr/share/mysql-8.0/
drwxr-xr-x 28 root root 4096 Sep 26 12:20 /usr/share/mysql-8.0/

root@srv2800:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

The same behaviour I can confirm on Debian 10 (buster) where are unit files under /usr/share/mysql-8.0 and NOT under /usr/share/mysql:
root@srv242:~# ps -p 1
  PID TTY          TIME CMD
    1 ?        03:52:36 systemd

root@srv242:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

root@srv242:~# dpkg -l | egrep -i mysql
ii  mysql-client                          8.0.20-1debian10                                                          amd64        MySQL Client meta package depending on latest version
ii  mysql-common                          8.0.20-1debian10                                                          amd64        Common files shared between packages
ii  mysql-community-client                8.0.20-1debian10                                                          amd64        MySQL Client
ii  mysql-community-client-core           8.0.20-1debian10                                                          amd64        MySQL Client Core Binaries
ii  mysql-community-server                8.0.20-1debian10                                                          amd64        MySQL Server
ii  mysql-community-server-core           8.0.20-1debian10                                                          amd64        MySQL Server Core Binaires
ii  mysql-server                          8.0.20-1debian10                                                          amd64        MySQL Server meta package depending on latest version

root@srv242:~# dpkg -L mysql-community-client | egrep "/usr/share/mysql"
/usr/share/mysql-8.0
/usr/share/mysql-8.0/charsets
/usr/share/mysql-8.0/charsets/Index.xml
/usr/share/mysql-8.0/charsets/README
/usr/share/mysql-8.0/charsets/armscii8.xml
/usr/share/mysql-8.0/charsets/ascii.xml
/usr/share/mysql-8.0/charsets/cp1250.xml
/usr/share/mysql-8.0/charsets/cp1251.xml
..
..
..

Can you have a look at this https://github.com/sous-chefs/mysql/blob/c1b785f5e9aeb860fbef9448cc86a784987621a4/libraries/helpers.rb#L295
:heavy_plus_sign: Additional context
This is my mysql_service resource defined in my custom cookbook
mysql_service 'default' do
  error_log '/var/log/mysql/error.log'
  version '8.0'
  package_name 'mysql-server'
  package_version '8.0.30-1debian11'
  bind_address '<IP_ADDRESS>'
  initial_root_password 'SuperS3cr3tPa$$W0rd'
  action [:create, :start]
end

+1 I am experiencing this issue as well attempting to configure MySQL 8.0 on rhel7/rhel8.


[Remote rendering problem] InvalidOperationException: An error occurred: Failed (1) on Windows Standalone

When running on a Standalone Windows build of our app we got the following error at the point of connecting to an ARR session accompanied by the screen going black. We're struggling to get a solid repro for it. it's happened twice each time on a different computer.
This error repeated every frame. It's possible there was a more useful error before it, but our remote logs are capped at a certain length so we can't see before it. We'll keep trying to reproduce it locally so we can get the full logs.
InvalidOperationException: An error occurred: Failed (1)
Microsoft.Azure.RemoteRendering.NativeLibraryHelpers.CheckStatus (System.UInt64 handle, Microsoft.Azure.RemoteRendering.status value) (at <00000000000000000000000000000000>:0)
Microsoft.Azure.RemoteRendering.Unity.RemoteManagerUnity.get_IsConnected () (at <00000000000000000000000000000000>:0)
HybridRenderingPassFeature+HolographicRemotingCallbackPass.Execute (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Rendering.Universal.RenderingData& renderingData) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.ScriptableRenderer.ExecuteRenderPass (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Rendering.Universal.ScriptableRenderPass renderPass, UnityEngine.Rendering.Universal.RenderingData& renderingData) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.ScriptableRenderer.ExecuteBlock (System.Int32 blockIndex, UnityEngine.Rendering.Universal.ScriptableRenderer+RenderBlocks& renderBlocks, UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Rendering.Universal.RenderingData& renderingData, System.Boolean submit) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.ScriptableRenderer.Execute (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Rendering.Universal.RenderingData& renderingData) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.UniversalRenderPipeline.RenderSingleCamera (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Rendering.Universal.CameraData cameraData, System.Boolean anyPostProcessingEnabled) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.UniversalRenderPipeline.RenderCameraStack (UnityEngine.Rendering.ScriptableRenderContext context, UnityEngine.Camera baseCamera) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.Universal.UniversalRenderPipeline.Render (UnityEngine.Rendering.ScriptableRenderContext renderContext, UnityEngine.Camera[] cameras) (at <00000000000000000000000000000000>:0)
UnityEngine.Rendering.RenderPipelineManager.DoRenderLoop_Internal (UnityEngine.Rendering.RenderPipelineAsset pipe, System.IntPtr loopPtr, System.Collections.Generic.List`1[T] renderRequests) (at <00000000000000000000000000000000>:0)

Any thoughts appreciated.

Some more information:
One of the users to whom this happened, logged in twice with the same account so our backend gave the same ARR session out twice. This means they got "RRException: Trying to open a session while a session already exists is not supported in ARRUnityService." on one of the devices resulting in the Invalid Session. It's on our backlog to support this scenario, so we can ignore this user issue.
The other user we're still trying to get the full log for. Initially, we had discounted hardware as the issue as the user mentioned above had a known good setup, but now we wonder whether it could be because their (integrated) GPU isn't supported in some way. When we send logs we capture device information provided by Unity, perhaps there is something here that gives you a clue?
Battery level	1
Battery status	Full
Operating system	Windows 10 (10.0.19042) 64bit
Operating system family	Windows
Processor type	Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Processor frequency	2112
Processor count	8
System memory size	8071
Device model	Latitude 7490 (Dell Inc.)
Supports accelerometer	False
Supports gyroscope	False
Supports location service	False
Supports vibration	False
Supports audio	True
Device type	Desktop
Graphics memory size	4035
Graphics device name	Intel(R) UHD Graphics 620
Graphics device vendor	Intel
Graphics device ID	22807
Graphics device vendor ID	32902
Graphics device type	Direct3D11
Graphics u v starts at top	True
Graphics device version	Direct3D 11.0 [level 11.1]
Graphics shader level	50
Graphics multi threaded	True
Rendering threading mode	MultiThreaded
Has hidden surface removal on g p u	False
Has dynamic uniform array indexing in fragment shaders	True
Supports shadows	True
Supports raw shadow depth sampling	True
Supports render textures	True
Supports motion vectors	True
Supports render to cubemap	True
Supports image effects	True
Supports3 d textures	True
Supports compressed3 d textures	True
Supports2 d array textures	True
Supports3 d render textures	True
Supports cubemap array textures	True
Copy texture support	Basic, Copy3D, DifferentTypes, TextureToRT, RTToTexture
Supports compute shaders	True
Supports geometry shaders	True
Supports tessellation shaders	True
Supports render target array index from vertex shader	True
Supports instancing	True
Supports hardware quad topology	False
Supports32bits index buffer	True
Supports sparse textures	True
Supported render target count	8
Supports separated render targets blend	True
Supported random write target count	8
Supports multisampled textures	1
Supports multisampled2 d array textures	True
Supports multisample auto resolve	False
Supports texture wrap mirror once	1
Uses reversed z buffer	True
Supports stencil	1
Npot support	Full
Max texture size	16384
Max cubemap size	16384
Max compute buffer inputs vertex	128
Max compute buffer inputs fragment	128
Max compute buffer inputs geometry	128
Max compute buffer inputs domain	128
Max compute buffer inputs hull	128
Max compute buffer inputs compute	32
Max compute work group size	1024
Max compute work group size x	1024
Max compute work group size y	1024
Max compute work group size z	64
Supports async compute	False
Supports gpu recorder	False
Supports graphics fence	True
Supports async g p u readback	True
Supports ray tracing	False
Supports set constant buffer	True
Constant buffer offset alignment	256
Min constant buffer offset alignment	False
Has mip max level	True
Supports mip streaming	True
Graphics pixel fillrate	-1
Uses load store actions	False
Hdr display support flags	Supported, RuntimeSwitchable, AutomaticTonemapping
Supports conservative raster	True
Supports multiview	False
Supports store and resolve action	True
Supports vertex programs	True
Supports g p u fence	False

With regards to your points about disposing of the RemoteRenderingClient, in this users scenario under normal circumstances dispose would not have been called at any point. They started the app and attempted to connect then got this error, no previous sessions had been running.

@WikkidEdd the hardware looks fine to me. According to our docs page we require Skylake and newer CPUs on Intel platforms so the i7-8650U used here should be capable of running ARR (it supports hardware h265 and h264 decoding).
If not, the connect call would fail with error VideoCodecNotAvailable.
If you are using ARRServiceUnity, I would assume some error caused the program to execute the component Destroy method or Deinitialize was called. I'd suggest adding logging around those functions to make sure these are not executed by accident.
We will continue to look through our code to see if there are any other code paths that could potentially dispose the RemoteRenderingClient and invalidate the session object.

Hi again @WikkidEdd ,
with the latest ARR release 1.0.54 we fixed the render code to no longer spam exception in case an invalid session is set to active which should also prevent the screen from going black as a result of throwing in the render loop.
We couldn't find a clear cause for the session turning invalid but we did fix an inconsistency in the arrServiceUnity which probably triggered "RRException: Trying to open a session while a session already exists is not supported" and would result in a stopped session remaining the active session in RemoteManagerUnity (see also release anouncement above):
"ARRServiceUnity.StopSession will now set the CurrentActiveSession to null upon completion. This way StopSession / ForgetSession are the opposite operations of StartSession / OpenSession as it was originally intended."
We hope that this change will give you better logs the next time the problem appears.
Cheers,
Christopher

Great, we upgraded this afternoon :)
We're also going to improve our logging behaviour so that duplicate log lines are removed so in future we can keep hold of the import logs messages :)
I'll close this issue now as I don't think we'll get any further with it until we have more information.


Bug: Unwanted Page Reload Happens Only On Samsung Internet

Describe the bug
I have a weird problem with Vite and it only happens on Samsung Internet when I'm on development server...
Problem: page reloads automatically 3 seconds in a loop and I don't set nor write any intervals... the page reload happens at browser level.
These are unwanted reloads and I want to get rid of them.
Any Idea why it happens?
PS: build version works fine...
Reproduction
First install the app using: npm init vite@latest my-vue-app -- --template vue-ts and then run npm run dev -- --host.
After that navigate to the network IP address via a Samsung Mobile Browser
System Info
Any Samsung Browser has this bug in development network environment

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I connected a debugger in `Samsung Internet Browser and the problem was:
client.ts:28 WebSocket connection to 'ws://<local-ip>:3000/' failed: Error in connection establishment: net::ERR_SSL_PROTOCOL_ERROR

A workaround is to enable HTTPS in Vite with:
import { defineConfig } from 'vite'

export default defineConfig({
  ⋮
  server: {
    https: true,
  },
})

Thanks. It's working great now


tests: drivers: counter: counter_nrf_rtc: Add nRF54L15 to platform allow

Add nRF54L15 to platform_allow in the sample.yaml.

@adamkondraciuk: Could You take a look?

This test is passing on nrf54l15 in our CI.

@nordic-segl this test was passing because there were no instances enabled (and test was ok with that). I've opened #71415 with your commit and additional changes needed to run on instances (also added fail if there are no RTC instances).

Included in https://github.com/zephyrproject-rtos/zephyr/pull/71415 which has additional fixes and improvements.


[Error] Gulp Serve Exited with code 3

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Linux
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version: v1.16.1
Node.js version: v16.18.1
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
gulp -v

// CLI version: 2.3.0
// Local version: 4.0.2

Describe the bug / error
Getting error when running 'gulp serve'
gulp serve

Build target: DEBUG
[12:12:50] Using gulpfile ~/first-project/gulpfile.js
[12:12:50] Starting 'serve'...
[12:12:50] Starting gulp
[12:12:50] Starting subtask 'spfx-serve'...
[12:12:50] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
[12:12:50] Starting server...
[12:12:50] Finished subtask 'spfx-serve' after 94 ms
[12:12:50] Starting subtask 'pre-copy'...
[12:12:50] Finished subtask 'pre-copy' after 18 ms
[12:12:50] Starting subtask 'copy-static-assets'...
[12:12:50] Starting subtask 'sass'...
[12:12:50] Server started https://localhost:4321
[12:12:50] LiveReload started on port 35729
[12:12:50] Running server
[12:12:50] Opening https://y00pb.sharepoint.com/sites/dev/_layouts/workbench.aspx using the default OS app
[12:12:50] Finished subtask 'sass' after 524 ms
[12:12:50] Starting subtask 'lint'...
[12:12:50] [lint] eslint version: 8.7.0
[12:12:50] Starting subtask 'tsc'...
[12:12:50] [tsc] typescript version: 4.5.5
[12:12:50] 'serve' errored after 704 ms
[12:12:50] Error: Exited with code 3
    at ChildProcess.<anonymous> (/home/username/first-project/node_modules/opn/index.js:84:13)
    at Object.onceWrapper (node:events:628:26)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:552:15)
    at maybeClose (node:internal/child_process:1100:16)
    at Socket.<anonymous> (node:internal/child_process:458:11)
    at Socket.emit (node:events:513:28)
    at Socket.emit (node:domain:552:15)
    at Pipe.<anonymous> (node:net:301:12)
    at Pipe.callbackTrampoline (node:internal/async_hooks:130:17)
About to exit with code: 1
Process terminated before summary could be written, possible error in async code not continuing!
Trying to exit with exit code 1

Steps to reproduce

Install latest node version supported by spfx: nvm install v16.18.1
Install developer spfx developer tool: npm install gulp-cli yo @microsoft/generator-sharepoint --global
Generate boilerplate: yo @microsoft/sharepoint
Navigate to project, run gulp serve

Expected behavior
Project open in Sharepoint Workbench without any error

Update: The issue is fixed after changing:
{
  ...
  "initialPage": "https://sitename/sites/dev/_layouts/15/workbench.aspx"
}

->
{
  ...
  "initialPage": "https://sitename/sites/dev/_layouts/workbench.aspx"
}

Update: Apparently after restarting my pc. I am encountering the issue above again.

Update: Fix it again after running my ubuntu wsl as admin.


Add dark theme option to the Flutter UX research

I'd like to ask for a dark theme option to the Flutter UX research.
Edit
It would specially help those late night Devs that will feel more comfortable with a (probably) similar theme to what their IDE/system is set.

This cold help with https://github.com/flutter/uxr/issues/141 as well.


POC implementation of multiple routes

This PR is primiminary attempt at supporting the generation of multiple routes (from schemas) for a single class.
The configuration would look as follows:
stdClass:
    extend: foo
    routes:
        route_one:
            uri_schema: /route/to/{foo]
            token_providers:
                foo: [ bar ]
        route_two:
            uri_schema: /path/to/{foo]
            token_providers:
                foo: [ bar ]

While also supporting the current format:
stdClass:
    extend: foo
    uri_schema: /route/to/{foo]
    token_providers:
        foo: [ bar ]

Note that this is far from being in a working state.

Replaced by #62


pctl upgrade via CLI

Briefly describe the feature
Currently whenever there's a new release of pctl, the user needs to manually download and update the pctl binary in their system. Since it doesn't automatically install while installing Paralus, the user may miss out on updating pctl.
We could have a command like pctl upgrade --latest which basically downloads the latest binary for the current system and installs it.
We could also have a background check for latest version when the user types pctl. If there's a newer version, it can display a sentence like 'you're using an outdated version of pctl, please upgrade to the latest binary'
What problem does this feature solve? Please link any relevant documentation or Issues
Makes the pctl upgrade process easier and faster.

@techmaharaj It would be nice to have such feature in pctl. Although it comes with challenges in pctl upgrading itself. pctl can be installed using multiple ways on different OS/platforms like downloading binary to $PATH, brew package manager on MacOS, running in Docker container. To upgrade itself, first we need to understand its installation technique and perform necessary actions.
Although user can manage pctl upgrade by themself whenever required. Using the third-part package managers for installation is recommended those has upgrade procedure within it.
I understand currently pctl can be installing by downloading binary for Linux machines. In future we could package it for different package managers like apt, dnf etc.

Closing this as we are not planning to pick it up, if you still foresee this adding immense value please raise a separate issue.


TaskbarX not relauching when connecting to second monitor

Bug description
As you connect and disconnect a monitor on a laptop, after connecting the external display via USBC TaskBarX does not affect the taskbar on the secondary monitor, and you have to relauche TaskbarX to get it working on both displays.
To Reproduce
Steps to reproduce the behavior:

Have your laptop on
Connect a secondary display (via USBC and a dongle)
See the taskbar on the second monitor not stylized

Expected behavior
When plugin the seconday monitor, TaskbarX should affect the new taskbar and stylize it as the first one
Screenshots
The integrated display after connecting external display
The externaldisplay after connecting
Desktop (please complete the following information):

OS: Windows 10
Version <IP_ADDRESS>

Have the same bug. Older version worked fine tho. Very annoying issue. Might gonna switch to an older version

Could be the same thing as in https://github.com/ChrisAnd1998/TaskbarX/issues/946

Had the same issue on <IP_ADDRESS>. Uninstalled this version and installed <IP_ADDRESS>. Now works fine. And I don't have the #875 bug, so this downgrade isn't crucial


Proxy is trying to forward files that it has marked as '.bad', e.g. '12345.zip.bad'

stroom.proxy.util.zip.StroomZipRepository.scanForMatch line 158
throw NumberFormatException

Fix in proxy code too - proxy issue number 8


Remove outdate function registeration

Remove some functions(getarrayitem/getmapvalue/murmur3hash) which are not appeared in https://spark.apache.org/docs/latest/api/sql.
Remove corresponding UT case.

Hi @zhejiangxiaomai , I am curious , If the latest spark doesnt contain these functions, I presume the previous ones did have it - do we not intend to support those versions then ?

@kgpai  thanks for your review.
Here is my discussion with mbasmanova.
https://github.com/facebookincubator/velox/pull/3699#discussion_r1069581629
We think some functions were added incorrectly.

Though get_map_value is not listed in https://spark.apache.org/docs/latest/api/sql, but for expressions like m['key'], spark will translate it into 'GetMapValue', which is a different expression with element_at in spark.
Is there other concern to remove it ? @zhejiangxiaomai

Because it was not found in spark sql. So I don't think we will use this API anymore.  @WangGuangxin there is no other reason.

I think we should add it back, as well as 'getarrayitem'. Gluten translates 'GetMapValue' to velox's 'get_map_value' function.  what do you think? @zhztheplayer @rui-mo @PHILO-HE

I understand now. "ExpressionMappings.scala" include all the functions. spark sql does not contain some implicit conversions. I think we should add it back and fix https://github.com/facebookincubator/velox/issues/4147.

I think we should add it back, as well as 'getarrayitem'. Gluten translates 'GetMapValue' to velox's 'get_map_value' function https://github.com/oap-project/gluten/blob/main/gluten-core/src/main/scala/io/glutenproject/expression/ExpressionMappings.scala#L179. what do you think? @zhztheplayer @rui-mo @PHILO-HE

Thanks @WangGuangxin for pointing out this. Yes, get_array_item & get_map_value are actually used in spark for accessing array/map item. We should keep them. @zhejiangxiaomai, we need to add them back and please also check whether there is any compatibility issue on spark sql.

@WangGuangxin Thank you for pointing this out. Let's return these functions back and document that these are used to translate array and map accessors. Let's also check that semantics match Spark. Let's use get_array_item and get_map_value names for these.


Tk

I'm trying to install the Tk bindings for Ruby. According to the instructions building Ruby would need to be:
% ./configure --prefix=<install-dir>
  --with-tcl-dir=/opt/ActiveTcl-8.5
  --with-tk-dir=/opt/ActiveTcl-8.5
  --with-tcllib=tclstub8.5
  --with-tklib=tkstub8.5
  --enable-tcltk_stubs
  --enable-tcl-thread
  --enable-pthread
% make && make install

How can configure ruby-build to use these configure options?

You can specify them with the CONFIGURE_OPTS environment variable. E.g.:
% CONFIGURE_OPTS="--with-tcl-dir=/opt/ActiveTcl-8.5 ..." ruby-build ...

Okay. That'll work, albeit a pain to have to prepend to each build.
Actually I'd really like to create a separate "ruby" for tk, e.g.
$ rbenv local ruby-1.9.3-rc1+tk

Or something like that. Would that be possible? Maybe a future version of ruby-build?

Absolutely - you can do that now by making your own definition file. Fork this project and copy the share/ruby-build/1.9.3-rc1 file to share/ruby-build/1.9.3-rc1+tk. Then edit the new file and add export CONFIGURE_OPTS=… to the top (it's just a shell script that's sourced by ruby-build).

Try this one instead: https://gist.github.com/1319772


_WD_UpdateDriver: Support webdriver downgrades

Pull request
Proposed changes
Add ability to detect mismatches between web browser and the webdriver.
Checklist
Put an x in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!
This is simply a reminder of what we are going to look for before merging your code.

[x] I have read and noticed the CODE OF CONDUCT document
[x] I have read and noticed the CONTRIBUTING document
[ ] I have added necessary documentation or screenshots (if appropriate)

Types of changes
Please check x the type of change your PR introduces:

[ ] Bugfix (change which fixes an issue)
[x] Feature (change which adds functionality)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (functional, structural)
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
No option to downgrade web driver and no notification of mismatch.
What is the new behavior?

New $bDowngrade parameter that defaults to False. - When this parameter is True, then the existing web driver will be replaced with the correct version for the associated browser if a mismatch is detected.
When used with $bForce = Null, the function will return True is the current web driver needs to be downgraded.
Sets @error to $_WD_ERROR_Mismatch when unhandled mismatch is detected

Additional context
Add any other context about the problem here.
System under test
Please complete the following information.

OS: [e.g. Windows 10]
OS Arch.: [e.g. X64]
Browser [e.g. firefox]
Browser version [e.g. 96.0.3]

This is the script I used for testing --
#include "wd_helper.au3"
#include "wd_core.au3"

$sBrowser = 'chrome'
$bResult = _WD_UpdateDriver($sBrowser, Default, Default, Null)
;### Debug CONSOLE ↓↓↓
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $bResult = ' & $bResult & @CRLF & '>Error code: ' & @error & @CRLF)

$bResult = _WD_UpdateDriver($sBrowser, Default, Default, Null, True)
;### Debug CONSOLE ↓↓↓
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $bResult = ' & $bResult & @CRLF & '>Error code: ' & @error & @CRLF)

$bResult = _WD_UpdateDriver($sBrowser)
;### Debug CONSOLE ↓↓↓
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $bResult = ' & $bResult & @CRLF & '>Error code: ' & @error & @CRLF)

$bResult = _WD_UpdateDriver($sBrowser, Default, Default, Default, True)
;### Debug CONSOLE ↓↓↓
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $bResult = ' & $bResult & @CRLF & '>Error code: ' & @error & @CRLF)

The following is the output when starting with Chromedriver version of 115.0.5790.13 and Chrome version of 114.0.5735.110 --
    _WD_UpdateDriver ==> Success [0 / 0] : DriverCurrent = 115.0.5790.13 : DriverLatest = 114.0.5735.90
    @@ Debug(7) : $bResult = False
    >Error code: 0
    _WD_UpdateDriver ==> Success [0 / 0] : DriverCurrent = 115.0.5790.13 : DriverLatest = 114.0.5735.90
    @@ Debug(11) : $bResult = True
    >Error code: 0
    _WD_UpdateDriver ==> Version mismatch [24 / 0] : DriverCurrent = 115.0.5790.13 : DriverLatest = 114.0.5735.90
    @@ Debug(15) : $bResult = False
    >Error code: 24
    _WD_UpdateDriver ==> Success [0 / 0] : DriverCurrent = 115.0.5790.13 : DriverLatest = 114.0.5735.90
    @@ Debug(19) : $bResult = True
    >Error code: 0

After running the above, the version of Chromedriver has been downgraded to 114.0.5735.90

Hi Danp2,
Running version <IP_ADDRESS> I don't see a 5th parameter in _WD_UpdateDriver within wd_helper.au3 as you have injected into your demo script. Is there a different version somewhere that includes that extra parameter?
Thanks

I ran this after uninstalling my newer chrome and installing an older chrome to test it out but the console results don't match yours. There seems to still be a problem:

@itplainedge DriverCurrent is the version of the locally installed webdriver. DriverLatest is the version of the remote webdriver that matches your installed browser.
If you ran this code previously, then the newer copy of Chromedriver was overwritten by the v103 one. Please double check the version in the script directory and replace with the v114 copy as needed. Then retest. 😉

OK thanks for that clarification.  With that it still seems that it's incrorectly extracting the version of the locally installed webdriver since I have 3 chromedrivers I'm testing:
chromedriver-v103.exe
chromedriver-v114.exe
chromedriver.exe  (the timestamp and size still matches the latest v104) so I don't think it was automatically updated by any processes.

OK great I'll look to see about that. That sounds simple enough.  I think for my app on server situation where different users PC's have different versions of chrome. I'll have to somehow instead have the UDF save the chromedrivers with different version numbers so each user's running of the script on their PC will know which webdriver  to open without having a single chromedriver.exe that all users use.

FWIW, I updated the original code posted above to allow easier updates to the install directory.

Great, I got your code working. When I get time I'll revisit the way that I'm handling each users Chrome installation. In the educational DeepFreeze virtualization environment I'm working with, it's so much easier to run and keep Autoit app and data on the server. It also allows my users to tell me when they have an outdated browser via this Webdriver functionality since I'm the one that is doing the update on all the machines only when necessary.  It's also easier to update a single app on a server than making sure every machine has the correct app version with all the tweaks I keep adding.  95% of my other apps I don't tweak as often. Make sense?


Seperate PWM and DAC commands

Firmata Protocol doesn't specify a difference between PWM and DAC outputs (Arduino Uno does not have a DAC). We may need to look at extending the protocol in places to provide support to our feature set.
@curcuz @ntzovanis

Referenced in #26


payloads: Fix misspelling

Introduced when implementing the flavors/detail endpoint.
Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 56.955% when pulling fb34081ba45fefe00a7bcfc354af0b963448ef0e on sameo/topic/misspell-fixes into 5a7380a3ce5d630535077e99c4b47d776722347e on master.

Coverage decreased (-0.03%) to 56.907% when pulling 3bfa6538f0e5a59543d304748616b0a2709596ba on sameo/topic/misspell-fixes into ecf8a250d6ba54746d2fe37ae479145f889d854f on master.

I'm not sure why this is failing the ci.  I told github to update it to master, and then it started failing.

It's weird.  It looks like the ssntp unit tests crashed.  My guess is TestClientReconnect.  That's usually what it means when you see 'NOT RUN' in test-cases.  Of course, it could always be a bug in test-cases.  I'll update output test-cases to print stderr from go test if it panics.  Next time we see something like this we should get some more precise info.
My guess is that if the PR is regenerated the build will pass.

Coverage decreased (-0.008%) to 56.931% when pulling 4d5aec8c55489fc33e5ce6501b12a474eb255241 on sameo/topic/misspell-fixes into 09fe4a33a8ccde0b4fbc7ed53a328e6b299f134d on master.

well, you were right. It magically fixed.


Initial version of action-helm-sbom-upload (#1)

first full working version of the SBOM upload action. To be tagged version 1.0.0

This is simply merging dev (previously approved changes) into main/master

looks good

I don't see an approval button for some reason.

I don't see an approval button for some reason.

@harithamc how about now? I'm still trying to figure out "assignees" vs "reviewers" and why they are different.


Header menu

Insert a header navigation.

Awesome work! I've some suggestions

fixed top navbar, full width, menu items same width as content
remove top heading over menu, not needed anymore
brand link in menu should always be the link of the root page
add prev/next buttons to the menu, still visible on mobile
add dropdown icons, or depends this on the used bootswatch theme?

@tobiju Merge the PR and 1-3 are resolved :-)