Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.

When I start to run my project I get this error in terminal.
"react-native": "^0.66.0",
"@notifee/react-native": "^5.0.2",
gradle version 7.0
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.
Searched in the following locations:
- file:/C:/test/.m2/repository/app/notifee/core/
- file:/C:/test/node_modules/react-native/android/app/notifee/core/maven-metadata.xml
- file:/C:/test/node_modules/jsc-android/dist/app/notifee/core/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/app/notifee/core/maven-metadata.xml
- https://repo.maven.apache.org/maven2/app/notifee/core/maven-metadata.xml
- https://jcenter.bintray.com/app/notifee/core/maven-metadata.xml
- https://www.jitpack.io/app/notifee/core/maven-metadata.xml
Required by:
project :app > project :notifee_react-native

Hi there @oguzhan10 - this step has been missed:
https://notifee.app/react-native/docs/installation#2-android-add-local-maven-repository
I have a "install notifee from scratch" demonstration script that shows how to do the full integration and the step is performed (via scripting) right here https://github.com/mikehardy/rnfbdemo/blob/25022e4051a759cfa9ca69ebb353db25d7927cc9/notifee-demo.sh#L50-L54
If you run notifee-demo.sh it will generate an app that works, and following the installation instructions or example should get you through this

https://notifee.app/react-native/docs/installation#2-android-add-local-maven-repository
the link no longer exists

@abewartech  it is no longer necessary in current versions because of the fine work here #414 by @bang9 - update to current version and the install is just like a normal react-native module now, even though there is an aar inside of it

:thinking: hmm - the commit was released as version 5.3.0 of the react-native module. It works for us in local testing (and for me in a commercial project)

Weird, maybe I'm missing something in the repo locations?
These are the places where they compiler searched for the deps:
Searched in the following locations:
- https://repo.maven.apache.org/maven2/app/notifee/core/maven-metadata.xml
- file:/C:/Users/skull/.m2/repository/app/notifee/core/
- file:/E:/projects/xx/node_modules/react-native/android/app/notifee/core/maven-metadata.xml
- file:/E:/projects/xx/node_modules/jsc-android/dist/app/notifee/core/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/app/notifee/core/maven-metadata.xml
- https://jcenter.bintray.com/app/notifee/core/maven-metadata.xml
- https://www.jitpack.io/app/notifee/core/maven-metadata.xml
Required by:
project :app > project :notifee_react-native

Ok, after further analyzing the error I found the problem.
Reading your response about a script here I noticed that you had a mave url manually added in the build.gradle.

sed -i -e $'s/google()/google()\\n        maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }/' android/build.gradle

Then I went to check the PR made by @bang9 #414 and indeed there's a comment here talking about a error-prone install step that could be avoided.
So with this info, I went back to my build.gradle and noticed that the installation process didn't added the line in my build.gradle.
After I added this line in my build.gradle it builded succesfully:

maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }

Okay - but the problem is, that's not supposed to be necessary anymore :laughing: - #414 was specifically about removing the need for that. Gradle should - during configuration - automatically apply it:
https://github.com/invertase/notifee/blob/4103b37efe18e8a8282afeb81c5ce078fd5658bf/packages/react-native/android/build.gradle#L90-L96
...and with 5.3.0 I was able to remove the entry I had added in my project's android/build.gradle, and the build still worked. Very confusing

@Skullcan, Which version are you using?

I'm using the latest version, 5.3.0.
React native 0.68.2.

...and with 5.3.0 I was able to remove the entry I had added in my project's android/build.gradle, and the build still worked. Very confusing

I agree, very confusing, dunno why/what's happening.
But the problem only happens in this project, I have tried in other project and a fresh example. They both build fine w/o the line in the build.gradle.

Very interesting! I am also in a monorepo but the react-native module is down at the package level so this didn't show up for me, I can see how it would though. A PR would be fantastic if you have time!

I just ran into this because we have a pretty deeply nested monorepo structure, so my build.gradle has urls like:
url("$rootDir/../../../../node_modules/react-native/android")

meaning the one set by notifee is too shallow.

Perhaps an ext variable (or maybe one already exists?) that sets the react-native root path, with the current one as the fallback/default, and we dereference based on this configured-or-default path? Could work as a PR...

Still have this issue in notifee version 7.1.0
Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.

Same issue here
react-native: 0.70.4
7.1.0

 System
System:
OS: macOS 13.0.1
CPU: (10) arm64 Apple M1 Max
Binaries:
Node: 14.19.1
Yarn: 1.22.19

react-native: 0.70.4

0.70.6 is out now, for what it's worth
You can always try the workaround: https://github.com/invertase/notifee/issues/350#issuecomment-1148969412
I'd need to see a reproduction to understand why it's happening as it doesn't seem to happen to my builds :thinking: https://stackoverflow.com/help/minimal-reproducible-example

an upgrade to 0.70.6 doesn't solve the issue.
it could be that's an issue with a combination of another package :/
the combination of https://github.com/invertase/notifee/issues/350#issuecomment-1148969412 and https://github.com/invertase/notifee/issues/561#issuecomment-1285108642 fixes the issue for me
If I find some time, I will try to create a reproduction repo

the best repro of this one might just be the steps to create, that is, something like:
1- npx react-native init NotifeeBreaksThisWay
2- cd NotifeeBreaksThisWay && yarn add @notifee/react-native
3- something something
4- yarn android
Just need to know what the something something is...

Same issues!

I also get this issue with the following error:

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

Could not resolve all task dependencies for configuration ':app:releaseRuntimeClasspath'.
Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.
Searched in the following locations:
- file:/home/p/Development/mobile-app/node_modules/react-native/android/app/notifee/core/maven-metadata.xml
- file:/home/p/Development/mobile-app/node_modules/jsc-android/dist/app/notifee/core/maven-metadata.xml
- https://repo.maven.apache.org/maven2/app/notifee/core/maven-metadata.xml
- https://dl.google.com/dl/android/maven2/app/notifee/core/maven-metadata.xml
- https://www.jitpack.io/app/notifee/core/maven-metadata.xml
Required by:
project :app > project :notifee_react-native

STILL GET THIS ISSUE, why is it still not fixed??
React-native: 0.70.6
7.2.0
It makes me stuck all day and still don't have a solution, this doesn't help: https://github.com/invertase/notifee/issues/350#issuecomment-1148969412
Please help to fix this @mikehardy

Hi @mikehardy I am facing the same error as @sangle95
I have tried lower version of notifee 4.0.0
my react native version in 0.68.0
these are my buildScript configurations:
ext {
buildToolsVersion = "30.0.3"
minSdkVersion = 21
compileSdkVersion = 31
targetSdkVersion = 31
ndkVersion = "21.4.7075529"
kotlinVersion = '1.7.20'
}

Your comment is kind of abusive, yes? It feels like yelling
Not a kind way to access help, it has certainly not motivated me to want to help

@mikehardy  Oh. I'm really sorry I couldn't contain my emotions.
I have tried many ways but still can't solve the problem. We are in dire need of pushing a new update to users who have not been able to solve it for 2 days, please help me to solve this problem.

Your comment is kind of abusive, yes? It feels like yelling
Not a kind way to access help, it has certainly not motivated me to want to help

@mikehardy Oh. I'm really sorry I couldn't contain my emotions.
I have tried many ways but still can't solve the problem. We are in dire need of pushing a new update to users, but we are stuck here for 2 days, could you please help me to solve this problem.

Here is my build.gradle:

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

buildscript {
ext {
buildToolsVersion = "31.0.0"
minSdkVersion = 21
compileSdkVersion = 31
targetSdkVersion = 31
playServicesVersion = "17.0.0"
androidMapsUtilsVersion = "2.2.4"
ndkVersion = "20.1.5948944"
supportLibVersion = "31.0.0"
kotlinVersion = '1.5.0'
    if (System.properties['os.arch'] == "aarch64") {
        // For M1 Users we need to use the NDK 24 which added support for aarch64
        ndkVersion = "24.0.8215888"
    } else {
        // Otherwise we default to the side-by-side NDK version from AGP.
        ndkVersion = "21.4.7075529"
    }
}
repositories {
    google()
    jcenter()
    mavenCentral()
}
dependencies {
    classpath("com.android.tools.build:gradle:7.2.1")
    classpath("com.facebook.react:react-native-gradle-plugin")
    classpath("de.undercouch:gradle-download-task:5.0.1")
    classpath 'com.google.gms:google-services:4.3.5'
    classpath 'com.google.firebase:firebase-crashlytics-gradle:2.7.0'
    classpath 'com.google.firebase:perf-plugin:1.4.1'
    classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion"
    // NOTE: Do not place your application dependencies here; they belong
    // in the individual module build.gradle files
}

}
allprojects {
//    configurations.all {
//        resolutionStrategy {
//            force 'com.facebook.react:react-native:0.70.6'
//        }
//    }
repositories {
mavenLocal()
mavenCentral {
// We don't want to fetch react-native from Maven Central as there are
// older versions over there.
content {
excludeGroup "com.facebook.react"
}
}
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
maven {
url "https://sdk.smartlook.com/android/release"
}
maven {
url 'https://repo.survicate.com'
}
    google()
    jcenter()
    maven { url 'https://www.jitpack.io' }
}

}

You don't appear to have the maven repository that points to the notifee nide modules directory in there. It's the workaround that will make things build for you.

Thank you for your suggestion, let me try to add maven repository that points to the notifee in my gradle.

maybe this could help someone, in my case I use jitpack repository, and the error says it get 521 response on jitpack side,

so I exclude app.notifee group on jitpack repository:
maven {
  url 'https://www.jitpack.io'

  // exclude notifee
  content {
    excludeGroup "app.notifee"
  }
}

@muhamad-rizki
I have try your solution and got this:
> Task :notifee_react-native:stripReleaseDebugSymbols NO-SOURCE
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property inputFiles with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.1/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :app:lintVitalRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Lint infrastructure error
  Caused by: java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        ...

bundle.gradle:
    repositories {

        exclusiveContent {
            filter {
                includeGroup "com.facebook.react"
            }
            forRepository {
                maven {
                    url "$rootDir/../node_modules/react-native/android"
                }
            }
        }
        google()
        jcenter()
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenCentral {
            // We don't want to fetch react-native from Maven Central as there are
            // older versions over there.
            content {
                excludeGroup "com.facebook.react"
            }
        }
        maven {
            url 'https://www.jitpack.io'
            content {
                excludeGroup "app.notifee"
            }
        }
        maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }
    }

dependencies:
"@notifee/react-native": "^5.0.3"
"react-native": "0.67.4"

@mikehardy Please take a look at this repository, in reference to your comment: https://github.com/invertase/notifee/issues/350#issuecomment-1321134063
Repository link: https://gitlab.com/pkiszka/notifeebreaksthisway
I didn't have to add any extra "something something" step, it breaks with only adding notifee dependency.
I was able to reproduce this error:
Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.

@muhamad-rizki I have try your solution and got this:
> Task :notifee_react-native:stripReleaseDebugSymbols NO-SOURCE
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property inputFiles with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.1/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :app:lintVitalRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Lint infrastructure error
  Caused by: java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        ...

bundle.gradle:
    repositories {

        exclusiveContent {
            filter {
                includeGroup "com.facebook.react"
            }
            forRepository {
                maven {
                    url "$rootDir/../node_modules/react-native/android"
                }
            }
        }
        google()
        jcenter()
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenCentral {
            // We don't want to fetch react-native from Maven Central as there are
            // older versions over there.
            content {
                excludeGroup "com.facebook.react"
            }
        }
        maven {
            url 'https://www.jitpack.io'
            content {
                excludeGroup "app.notifee"
            }
        }
        maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }
    }

dependencies: "@notifee/react-native": "^5.0.3" "react-native": "0.67.4"

can you

@muhamad-rizki I have try your solution and got this:
> Task :notifee_react-native:stripReleaseDebugSymbols NO-SOURCE
Relying on FileTrees for ignoring empty directories when using @SkipWhenEmpty has been deprecated. This is scheduled to be removed in Gradle 8.0. Annotate the property inputFiles with @IgnoreEmptyDirectories or remove @SkipWhenEmpty. Consult the upgrading guide for further information: https://docs.gradle.org/7.4.1/userguide/upgrading_version_7.html#empty_directories_file_tree

> Task :app:lintVitalRelease FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:lintVitalRelease'.
> Lint infrastructure error
  Caused by: java.lang.reflect.InvocationTargetException
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        ...

bundle.gradle:
    repositories {

        exclusiveContent {
            filter {
                includeGroup "com.facebook.react"
            }
            forRepository {
                maven {
                    url "$rootDir/../node_modules/react-native/android"
                }
            }
        }
        google()
        jcenter()
        mavenLocal()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenCentral {
            // We don't want to fetch react-native from Maven Central as there are
            // older versions over there.
            content {
                excludeGroup "com.facebook.react"
            }
        }
        maven {
            url 'https://www.jitpack.io'
            content {
                excludeGroup "app.notifee"
            }
        }
        maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" }
    }

dependencies: "@notifee/react-native": "^5.0.3" "react-native": "0.67.4"

can you show more the error log?

Hey, has this issue been fixed?
After upgrading rn from 0.67.0 to 0.70.6, I got an error Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.
Using latest notifee version: 7.3.0

I've removed these and it got worked org.gradle.daemon=true org.gradle.parallel=true org.gradle.configureondemand=true
Works for me

Just comment out only org.gradle.configureondemand=true from {Your-Project}/android/gradle.properties.
Follow for more details: Link

This worked! Thank you!

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

this worked for me

This is happening on "react-native": "0.71.4" and "@notifee/react-native": "^7.8.0"
According to this thread here where is says that in clean project it works as expected because after version 7.0.0 there's no longer need to include maven url to notifee, but I'm still facing the following issue on android build:
FAILURE: Build failed with an exception.
* What went wrong:
Could not determine the dependencies of task ':app:processRainUsStagingDebugResources'.
> Could not resolve all task dependencies for configuration ':app:rainUsStagingDebugRuntimeClasspath'.
   > Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available.
     Searched in the following locations:
       - https://repo.maven.apache.org/maven2/app/notifee/core/maven-metadata.xml
       - https://dl.google.com/dl/android/maven2/app/notifee/core/maven-metadata.xml
       - https://www.jitpack.io/app/notifee/core/maven-metadata.xml
       - https://appboy.github.io/appboy-android-sdk/sdk/app/notifee/core/maven-metadata.xml
       - https://storage.googleapis.com/logrocket-maven/app/notifee/core/maven-metadata.xml
       - https://zendesk.jfrog.io/zendesk/repo/app/notifee/core/maven-metadata.xml
       - https://oss.sonatype.org/content/repositories/snapshots/app/notifee/core/maven-metadata.xml
       - file:/Users/rafaelpadovani/Documents/nimbus/node_modules/jsc-android/dist/app/notifee/core/maven-metadata.xml
     Required by:
         project :app
         project :app > project :notifee_react-native

build.gradle
buildscript {
    ext {
        buildToolsVersion = "33.0.0"
        minSdkVersion = 21
        compileSdkVersion = 33
        targetSdkVersion = 33
        // We use NDK 23 which has both M1 support and is the side-by-side NDK version from AGP.
        ndkVersion = "23.1.7779620"
        kotlinVersion = "1.7.10"
        AsyncStorage_next_roomVersion = '2.4.3'
    }
    repositories {
        google()
        mavenCentral()
        jcenter()
    }
    dependencies {
        classpath("com.android.tools.build:gradle:7.3.1")
        classpath("com.facebook.react:react-native-gradle-plugin")
        // Kotlin
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion")
        // Google Services
        classpath("com.google.gms:google-services:4.3.15")
        // Crashlytics Gradle plugin
        classpath 'com.google.firebase:firebase-crashlytics-gradle:2.9.4'
        // Performance Monitoring Plugin
        classpath 'com.google.firebase:perf-plugin:1.4.2'
        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    configurations.all {
        resolutionStrategy {
            // Remove this override in 0.65+, as a proper fix is included in react-native itself.
            force "com.facebook.react:react-native:" + REACT_NATIVE_VERSION
        }
    }

    repositories {
        mavenCentral()
        google()
        maven { url 'https://www.jitpack.io' }
        maven { url "https://appboy.github.io/appboy-android-sdk/sdk" }
        maven { url "https://storage.googleapis.com/logrocket-maven/" }
        maven { url 'https://zendesk.jfrog.io/zendesk/repo' }
    }
}

Could anyone help with this?

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

I'm using expo bare workflow and I need to do this configuration to make notifee work in my project

Just comment out only org.gradle.configureondemand=true from {Your-Project}/android/gradle.properties.
Follow for more details: Link

This is the only configuration change we need. After commenting the org.gradle.configureondemand=true I was able to build the project even without adding the maven repo reference for the notifee:
maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

This does not work for me! 😂

if none of the above solutions works, check if you have, at a higher level, the following code somewhere in the settings.gradle file
dependencyResolutionManagement {
  repositoriesMode.set(RepositoriesMode.PREFER_SETTINGS) // <--- THAT

you will override the repository settings with repositoriesMode.set(RepositoriesMode.PREFER_SETTINGS... it was the case for me, due to an old custom expo config :/

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

the best solution! Thanks.

Here's a plugin that adds the above solution automatically to build.gradle : https://github.com/omedkane/notifee-expo-plugin add this to your app.json in the plugins array : "./plugins/notifee-mod.js"

Thanks. This worked. I also had to do npx expo prebuild --clean though.

Okay - but the problem is, that's not supposed to be necessary anymore 😆 - #414 was specifically about removing the need for that. Gradle should - during configuration - automatically apply it:
https://github.com/invertase/notifee/blob/4103b37efe18e8a8282afeb81c5ce078fd5658bf/packages/react-native/android/build.gradle#L90-L96
...and with 5.3.0 I was able to remove the entry I had added in my project's android/build.gradle, and the build still worked. Very confusing

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

bro thanks a lot !!!
it works for me
"react-native": "0.72.6",
@notifee/react-native": "^5.3.0",

this works by adding url "$rootDir/../node_modules/@notifee/react-native/android/libs", but how about expo? the strange thing is that on my colleague's machine building works out of the box with Expo without adding this line, for me, it doesn't work (same repo), any ideas thanks?

This issue still exists. Here is the config plugin for expo.
// withNotifeeAndroidFix.js
const { withProjectBuildGradle } = require("@expo/config-plugins");
const generateCode = require("@expo/config-plugins/build/utils/generateCode");

// https://github.com/invertase/notifee/issues/350
const notifeeAndroidWorkaroundCode = `
    maven {
        url "$rootDir/../node_modules/@notifee/react-native/android/libs"
    }
`;

/** @type {import('expo/config-plugins').ConfigPlugin} */
module.exports = (expoConfig) => {
  return withProjectBuildGradle(expoConfig, async (config) => {
    const { contents } = generateCode.mergeContents({
      newSrc: notifeeAndroidWorkaroundCode,
      tag: "notifieeAndroidWorkaround",
      src: config.modResults.contents,
      anchor: /maven\s*\{\s*url\s*'https:\/\/www\.jitpack\.io'\s*\}/,
      comment: "//",
      offset: 1,
    });

    config.modResults.contents = contents;

    return config;
  });
};

// app.json
"plugins": [
      "./withNotifeeAndroidFix",
    ],

@SohelIslamImran thanks, the strange thing is: that building it from android studio works fine, but doing it from the command line eg expo run:android fails w/o the fix, do you know why? is it because Android Studio maven knows how to reach for the lib w/o being specified in the gradle?

@SohelIslamImran thanks a lot!

@SohelIslamImran thanks, the strange thing is: that building it from android studio works fine, but doing it from the command line eg expo run:android fails w/o the fix, do you know why? is it because Android Studio maven knows how to reach for the lib w/o being specified in the gradle?

Try to add to app.json plugin like this:
`
//  [
//   "./withNotifeeAndroidFix",
//   "custom"
// ],
// Example
"plugins": [
[
"./withNotifeeAndroidFix",
"custom"
],
"expo-router",
"expo-localization",
],
`

@SohelIslamImran thanks a lot!

@SohelIslamImran thanks, the strange thing is: that building it from android studio works fine, but doing it from the command line eg expo run:android fails w/o the fix, do you know why? is it because Android Studio maven knows how to reach for the lib w/o being specified in the gradle?

Try to add to app.json plugin like this:
[
  "./withNotifeeAndroidFix",
  "custom"
],

// Example plugins in app.json

"plugins": [
  [
    "./withNotifeeAndroidFix",
    "custom"
  ],
  "expo-router",
  "expo-localization",
],

i've just add this code on android/build.gradle and worked
allprojects {
...
    repositories {
...
        maven {
            url "$rootDir/../node_modules/@notifee/react-native/android/libs"
        }
    }
}

I'm using expo bare workflow and I needed to make this configuration for the notifee to work in my project

Thank you, I also use expo bare, fixed this problem by adding the above maven url

Here's a plugin that adds the above solution automatically to build.gradle : https://github.com/omedkane/notifee-expo-plugin add this to your app.json in the plugins array : "./plugins/notifee-mod.js" Then run : npx expo prebuild --clean

Thanks , works .

Here's a plugin that adds the above solution automatically to build.gradle : https://github.com/omedkane/notifee-expo-plugin add this to your app.json in the plugins array : "./plugins/notifee-mod.js" Then run : npx expo prebuild --clean

You saved my day, thanks man <3 ! But is there a reason why we need to do this? Maybe the notifee docs are not updated?

@Goutham-dc no, there is no reason I understand - related + still open issue here with commend showing my last analysis: https://github.com/invertase/notifee/issues/799#issuecomment-2397277305
Bottom line: it is not supposed to be necessary, we have logic in the android build script that should add the repo for you.
Note from same issue you can also just use the standard expo-build-properties package and a config line and not have to use a plugin hack https://github.com/invertase/notifee/issues/799#issuecomment-2397108980

I believe that this should be explicitly stated somewhere on the docs.

@brianMxBm PRs happily merged - expo support is from the community, we need folks that use Expo - so they propose docs changes that they know actually work since they use them - to propose PRs https://github.com/invertase/notifee/blob/main/docs-react-native/react-native/docs/installation.md#expo-support

 [
      "./withNotifeeAndroidFix",
    ],

This works great for me :) thank you, however has anyone tried to wrap this code up nicely? So this widely accessible to everyone

Here's a plugin that adds the above solution automatically to build.gradle : https://github.com/omedkane/notifee-expo-plugin add this to your app.json in the plugins array : "./plugins/notifee-mod.js" Then run : npx expo prebuild --clean

This solved the problem for me. I'm using Expo SDK 52 (52.0.18) and RN 0.76.5
Thank you omedkane very much!


Preview image

Closing this and will try again - I think I started the preview image branch from the wrong local branch.


Node adapter runs server-side code when building

Describe the bug
When running yarn build with the Node adapter, the handle hook runs. It will even go so far as to call HTTP and database methods successfully (I've had an auth flow triggered during yarn build).
To Reproduce

Clone my repo.
yarn
yarn build
Check out your console for a nice banner that shouldn't be there.

Expected behavior
Creating the bundle should not run handle.
Severity
Fair, but not critical.

I found #1188, which seems to be the same or a related issue.

Closing as duplicate of https://github.com/sveltejs/kit/issues/933 as mentioned on Discord and of #1188 as mentioned above. This is partially documented in https://kit.svelte.dev/docs#modules-$app-env but it would probably be a good idea to further explain this in there or an FAQ -- again, keep that discussion in #933.


Crazy idea: lua

Hey I had an idea that will probably get rejected but I thought I'd through it out there. What are your thoughts on a spaceline variant written in lua. I'm in progress of writing space-vim-theme in lua and there's already a lua devicons.

This is planned, but recently I really don’t have time. I am working on  fix neovim built-in lsp bugs and add some new features. I am still making a new lsp plugin. So PR is welcome

I'll definitely try to land some ground work whenever I get some time. Do you think I should send a PR here or do you think it should be a different plugin like spaceline.nvim

It should be a new branch. If it is on the master, it will cause neovim to load too many files. If we use lua then only the lua folder should be loaded. So a new branch is a good choice.

I finished the space-nvim-theme. I want to look at nvim-bufferline.lua as a potential pairing with spaceline.vim, it needs a couple PRs before I think it's ready but it's written in lua and beside the highlight configurations not currently working it looks prety good.
I have looked a little at [express_line.nvim(https://github.com/tjdevries/express_line.nvim) for some ideas on writing spaceline in lua as well.

yep.I want to know why  depends on colorbuddy.vim. Maybe users don't like this way of bundling, and there is nothing complicated in making themes. Maybe you can encapsulate some simple functions yourself to remove dependencies.

I used because I liked the API, but you're definitely right. Tonight I'll work on remove components from colorbuddy and put them into the theme.

we should keep do one thing and do it best. Any upstream dependencies may cause your plugin to be unavailable.

It's strictly lua now.

@Th3Whit3Wolf  Nice work.

check https://github.com/glepnir/galaxyline.nvim


Googledoc copy paste content issue

Describe the bug
When copying the content from google doc and paste it into suneditor. some text is misplaced at last.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://docs.google.com/document/d/1y2TSDvb14JQ2uhVQxuWgASKF31YPdJ7mLWnzNAxkPcA/edit?usp=sharing'
copy the whole content
paste into suneditor
some text content is misplaced at last

Expected behavior
all content should be in correct order after pasting
Screenshots
https://www.loom.com/share/8e9736d9b96b48a493ec5c4aa8fa82d5
Desktop (please complete the following information):

OS: MacOS Big Sur
BrowserChrome
Version 2.41.0

And copy-paste content issue is happening in all the doc

The 2.41.3 version has been updated.
Thank you.


SharePoint Module link is wrong/old

SharePoint module download should link to https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-online/connect-sharepoint-online

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

ID: 51a2a070-5965-61d1-62e6-433fad2b5ecf
Version Independent ID: d54bbe0a-37b6-a6f0-0b25-e931ac537d58
Content: Get started with the SharePoint Online Management Shell
Content Source: sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md
Service: sharepoint-powershell
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: pamgreen

Hello @adamjacobsmsft
The link you provided in the issue description is the same as the article you are opening the issue for.
Both link versions to download the SPO Shell are provided.
Can you please specify which link do you think is wrong? Thanks

Sorry, I sent the wrong page. This page https://docs.microsoft.com/en-us/microsoft-365/enterprise/connect-to-all-microsoft-365-services-in-a-single-windows-powershell-window?view=o365-worldwide tells you to go to https://go.microsoft.com/fwlink/p/?LinkId=255251 to download SharePoint PowerShell module, but instead it should point to https://docs.microsoft.com/en-us/powershell/sharepoint/sharepoint-online/connect-sharepoint-online

@adamjacobsmsft Got it, it makes sense as the other modules in the bullet point go to similar pages, however, that article isn't in the repository you opened the issue for (OfficeDocs-SharePoint-PowerShell) I'll open a PR to edit the article in the other repository (microsoft-365-docs), if it is accepted and it gets merged, it will be reflected in the published version of the article.

IRM Setting status is missing in Get-SPOTenant. Does anyone have any idea?


Fix link to gnuradio blog

Find this while debugging https://github.com/manuzhang/mkdocs-htmlproofer-plugin/issues/83

Thanks. I hadn't had a chance to figure out where they had moved it to.


One of the function , toggleMobileMenu() is defined without using.

You need to call that toggleMobileMenu() function to solve this issue.

Hello @MayPyone kindly I need you to commit to my portfolio, I don't know why the changes you made yesterday is not showing in the commits and you are not a participant
https://github.com/NgachaIan/Personal_Portfolio/pull/14/


Collisions

Laravel Version: 5.6.1
Voyager Version: 1.0.15
PHP Version: 7.1.3
Database Driver & Version:

Description:
Voyager table names collide with my table names. Please add prefixes to the voyager table names.
Steps To Reproduce:
create a table named 'posts'
run 'php artisan voyager:install'

This is a much more complicated issue, and has been discussed at length in other issues and on our slack group.  We're looking at options on how to proceed, but blindly adding table prefixes is not possible at this point.


Add FirestoreGateway.createDoc tests

All updates made here will be merged in the last PR (#211), in this nested chain of collection execution PRs.


Fixed #25202 -- Removed references to deprecated GeoManager class

GeoManager has been deprecated. Docs updated to reflect this.

Please squash commits and use the commit message from the pull request title. See also our patch review checklist. Thanks!

Thanks for your help @timgraham, @charettes, I'll get onto it.

I'm not sure if the squash worked correctly. I used git rebase -i origin/master and then replaced pick with fixup.

If you look above, you'll see GitHub shows 10 commits. See https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/working-with-git/#rebasing-branches

After rebasing, I seem to have included extra commits. I'm just shooting myself in the foot at this point. I'm thinking I should start over with a new PR.

 I can do this easily, but happy to let you try it if you like.

Please do, I'll read up a bit more on how rebase works before making a mess of everthing!

Updated in https://github.com/django/django/pull/5130.

Cool, thanks very much for your help on this Tim.


Allow creating Texture from buffer

It would be nice if Texture provided a version of the init function that takes a slice and uses the stbi_load_from_memory function, instead of loading from a file.

I'll get on that in the next few days, pretty useful idea.

Added! Used in the example aswell.


DemoURL hotels.hc-demos.com is not accessible

Hi team,
The demo URL given in the GitHub repo details section is not accessible.

But I could access the Simple Example in the Readme.md. You might need to update the URL given in the repo details.

thanks for letting us know. url has been updated


Fatal error: Uncaught Error: Call to undefined function curl_init()

For the life of me, I've tried to follow every step carefully. I've watched the Tut. video and followed the text step by step but I keep encountering the same issue.
Fatal error: Uncaught Error: Call to undefined function curl_init() in C:\PHP\SalienCheat\cheat.php:643
Stack trace:
#0 C:\PHP\SalienCheat\cheat.php(399): SendGET('ITerritoryContr...', 'active_only=1&l...')
#1 C:\PHP\SalienCheat\cheat.php(63): GetFirstAvailablePlanet(Array, Array)
#2 {main}
  thrown in C:\PHP\SalienCheat\cheat.php on line 643

Any help would be appreciated.

Well you clearly didn't read the readme or watch the video.

I removed the simi-colon from ";extension=curl" and renamed the file php.in if that is what you're thinking I missed.

@ChilliHam https://youtu.be/Xx6ugBFpIlQ?t=138

@DmACKGL I figured out my issue. When saving the file as php.in using the "Save As" option, it creates a new file and you still need to delete the old one for it to work. That was the problem. It wasn't using the new file, still looking at the old one. (used notepad++)


LogstashFormatter does not allow to send no type and no host

We have an ELK stack installation (using filebeat) that automatically fills in the type field if not present. This type is generated dinamically outside the application.
The LogstashFormatter always fills the type field (using either the applicationName or the channel) and the host field, but we would like to have the option of not doing it at all.
We would like to have a way to indicate to the formatter not to fill the type field. Could this be through a new parameter in the constructor or anything like this?

To be honest, if you have such custom requirements, I would recommend extending the class and overriding format(). It's easy enough. We can't have options for every possible field someone may want or not.


.table-borderless does not remove  border

The border between <tbody> and <tfoot> is not removed when using the table-borderless class.

This is not an issue in version 2.0.0 which should be used instead.


cannot read properties of null (reading 'setupContext')

Environment
live
Reproduction

Describe the bug
when I upgrade the version to rc-8, I can start the app local successfully.
and build also is succeed. but when I start the built files on live, the error is coming out.
Additional context
No response
Logs
No response

How to solve this problem?'Uncaught (in promise) TypeError: Cannot read properties of null (reading 'setupContext')'

@HOPELESSNESSLYR Would you open an issue with a minimal reproduction? 🙏


add CLI opts to examples to pass imu prod ID

adding CLI opts allows to run examples for multiple IMUs without rebuilding.

Added 3afb0f53718552bd6d8be75aaf02b44de08815ef


As a user, I would like to have several GAU Fund Allocation reports & dashboard when I install the NPSP

not sure if we make the reports part of our package, or the separate reports unmanaged package, but we need some reports and a dashboard to show off this feature.

**lurch: attach W-007280

Tracking W-007280

Unmanaged installer.


How to define/instanciate myCroppa?

The documentation is not clear on where myCroppa is defined and how it should be instanciated.

It should be defined on the data option of the parent component.
Here is an example:
https://jsfiddle.net/jdcvpvty/2/

That's a nice example. I suggest you to add the link to the README.md and that you add to the paragraph https://github.com/zhanziyang/vue-croppa#v-model that the v-model the user provides can be a null object - at the moment, the wording does not make it obvious.

Great. Thanks for your suggestion.


Error: Unsupported interlace method.

    gulp.task('sprite', function () {
        var spriteData = gulp.src(paths.html +'/images/sprites/*.png').pipe(spritesmith({
            imgName: 'ccc.png',
            cssName: 'ccc.css'
        }));
        return spriteData.pipe(gulp.dest(paths.html + '/images/'));
    });

result in
    events.js:85
          throw er; // Unhandled 'error' event
                ^
    Error: Unsupported interlace method.
        at Stream.<anonymous> (/Users/Json/project/gongyi_proj/trunk/node_modules/gulp.spritesmith/node_modules/spritesmith/node_modules/pixelsmith/node_modules/get-pixels/node_modules/pngparse/index.js:205:28)
        at Stream.emit (events.js:107:17)
        at Object.exports.parseBuffer (/Users/Json/project/gongyi_proj/trunk/node_modules/gulp.spritesmith/node_modules/spritesmith/node_modules/pixelsmith/node_modules/get-pixels/node_modules/pngparse/index.js:529:5)
        at handlePNG (/Users/Json/project/gongyi_proj/trunk/node_modules/gulp.spritesmith/node_modules/spritesmith/node_modules/pixelsmith/node_modules/get-pixels/node-pixels.js:16:12)
        at doParse (/Users/Json/project/gongyi_proj/trunk/node_modules/gulp.spritesmith/node_modules/spritesmith/node_modules/pixelsmith/node_modules/get-pixels/node-pixels.js:103:7)
        at /Users/Json/project/gongyi_proj/trunk/node_modules/gulp.spritesmith/node_modules/spritesmith/node_modules/pixelsmith/node_modules/get-pixels/node-pixels.js:175:7
        at fs.js:334:14
        at /Users/Json/project/gongyi_proj/trunk/node_modules/gulp-watch/node_modules/chokidar/node_modules/readdirp/node_modules/graceful-fs/graceful-fs.js:104:5
        at FSReqWrap.oncomplete (fs.js:95:15)

This has been a long standing issue in grunt-spritesmith (https://github.com/Ensighten/grunt-spritesmith/issues/80).
The underlying cause is pixelsmith (default spritesmith) engine uses pngparse which doesn't currently support interlaced images (https://github.com/darkskyapp/pngparse/issues/10).
The suggested workarounds until pngparse adds this support is to:

Use a different engine (e.g. phantomjssmith)
Preprocess images into a progressive format

This can be done at export time from Photoshop or whatever image editing tool is being used to generate the original sprites
This can be done via another gulp task which runs something like gm

https://www.npmjs.com/package/gulp-gm/

okey , i have used phantomjssmith to avoid this error successfully. ths.

it work.

While the workarounds work, I would prefer to keep this issue open since it is still an unsolved problem =/

@twolfson I've been working on fixing pngjs (I preferred the structure to pngparse) and I've added 1/2/4/16 bit support and interlace.
https://github.com/lukeapage/pngjs2

Cool, I swapped pngparse with pngjs2 inside of my local copy of get-pixels and it seems to work with some test images. Are we aware of any compatibility issues that pngparse exists yet pngjs2 doesn't yet support?
// Old code in`get-pixels`
var pngparse = require('pngparse')
pngparse.parse(data, function(err, img_data) {

// New code in `get-pixels`
var pngjs2 = require('pngjs2')
var png = new pngjs2.PNG();
png.parse(data, function(err, img_data) {

cool. Give me some days - there are a couple of subtle issues in the png
suite test results I've found and I'm going to tidy up some more then
release v1. I will see if there are any tests in pngparse i can port too.

Sounds great. Thanks for working on this =)

@lukeapage @twolfson So, how the things?)

the issues i mentioned were down to gamma correction and that every browser does it differently.  pngparse ignores the gamma block, so the default behaviour won't differ (gamma correction is an optional extra in pngjs2).
I have added issues for all the things i want to do before changing the version to 1 to indicate a good stable release, its mainly code quality and a few minor features. I guess that might take a week or so.
that being said,  im pretty happy,  it now passes all the pngsuite images, if youd like to start using it.

It's been 1 year and 2 months since Ensighten/grunt-spritesmith#80 was opened. I think waiting another week for stability won't kill us.
@lukeapage Please don't feel rushed to complete it faster; I would prefer a working maintainable PNG library to a working difficult to maintain one =)

yeah fine,  the bones are there, I'm just enjoying that its a small enough project to go perfectionist on it.

I've released v1.

Are we aware of any compatibility issues that pngparse exists yet pngjs2 doesn't yet support?

No, It tests every image from the png test suite and I've ported all of png-parses test suite.
There is one difference between pngparse v2 and pngjs2 - the parsed image is always 4 channels RGBA in pngjs2. However looking at https://github.com/scijs/get-pixels/blob/master/node-pixels.js#L15 and the package.json I can see node-pixels is using pngparse v1, which returns the same output as pngjs2 - so a straight swap will work fine.
Will you make a PR against get-pixels then? Let me know if you encounter any issues.

get-pixels is for browser and node, so before its upgraded pngjs2 needs to work with browserify

get-pixels is for browser and node, so before its upgraded pngjs2 needs to work with browserify

pngparse uses zlib and stream too, so browserify must provide browser polyfills (e.g. https://github.com/devongovett/browserify-zlib). pngjs2 doesn't use any dependencies above pngparse

Afk atm but get-pixels uses its dom-pixels.js file for the browser. This
doesn't need a PNG parser as it uses canvas elements instead.
On Aug 8, 2015 12:25 PM, "Luke Page"<EMAIL_ADDRESS>wrote:

get-pixels is for browser and node, so before its upgraded pngjs2 needs to
work with browserify
pngparse uses zlib and stream too, so browserify must provide browser
polyfills (e.g. https://github.com/devongovett/browserify-zlib). pngjs2
doesn't use any dependencies above pngparse
—
Reply to this email directly or view it on GitHub
https://github.com/twolfson/gulp.spritesmith/issues/50#issuecomment-129014390
.

ah.. thanks. I raised a PR anyway.. https://github.com/scijs/get-pixels/pull/24

@lukeapage @twolfson Do you have any news?)

Nope, still waiting for the get-pixels PR to be landed. I think we can bump the issue after 14 days though (it's been 5 days). Mikola is pretty responsive/helpful.
http://issuestats.com/github/scijs/get-pixels/

@twolfson @lukeapage Ok, will be waiting

I asked for info on what it’ll take to merge https://github.com/scijs/get-pixels/pull/24 since I too am gated from using spritesmith until pixelsmith supports interlaced pngs.

@lukeapage @twolfson Is there any news?)

@artem-malko there is no news until the PR linked above gets some response

Sorry for the delay on this. The dependent PR was landed a few days ago but I got back from vacation today. I will attempt to make a release shortly.

Everything seems to work nicely. We moved to pngjs2 in<EMAIL_ADDRESS>Thanks again @lukeapage for all your work =)


differences between SUTDAnnotator and SUTDAnnotator-event?

Hello,
you mean that SUTDAnnotator-event is an annotator for event, however when I tried with SUTDAnnotator-event.py I found nothing different from SUTDAnnotator.py. So where am I wrong?

Hi insomniaCN,
Yes, the SUTDAnnotator-event is desinged for event annotation. The interface is same with SUTDAnnotator.py but with more features.  This funtion is still tuned but works well currently. I didn not have time to write readme notes for the event annotation, will try add the notes soon.
Here is a basic use introduction for event annotation:
The most importance feature is that you can give assign number for each event mention. Just select text, press number (i.e. 1, 2,...) and press the mention type shortcut (i.e. a, b,c,...), the system will assign the mention with a label and a number.
Let's see a poor example, given a sentence with two events:

Apple sued Google.  Amazon acquires Whole Foods two days ago.

You want to annotate the two events as tuple formats, like (APPLE, action, Goole) and (Amazon, action, Whole Foods). Then you can use the shortcut and number to distinguish different events by converting this text as :

[@Apple#1Subject*] [@sued#1Action*] [@Google#1Objective*].  [@Amazon#2Subject*] [@acquires#2Action*] [@Whole Foods#2Objective*] two days ago.

Here the related mentions are assigned with both label and number, where the number represent the index of events.
You can use this tool to annotate raw text into above format. For example, if you want to assign "Apple" with label "Subject" and number "1", just select "Apple" and press "1" and press "a" (the shortcut key of label "Subject").
It is quite similar with the entity annotation and is also quite efficient.

thx for your detailed reply. You can add this reply to README, it looks easy to understand.


Opening a permalink opens the URL in a browser instead of displaying it in the app.

In a channel have pasted the URL referring to another channel. When opening it, it is shown on my browser.

@taitruong  wrong project. Please report issue on Cordova project.


Add response to terms to gocheck_obsoletion_candidate

Hey, Ontobot! apply:

add GO:0042221 to subset gocheck_obsoletion_candidate
add GO:0010033 to subset gocheck_obsoletion_candidate
add GO:1901698 to subset gocheck_obsoletion_candidate
add GO:0010243 to subset gocheck_obsoletion_candidate
add GO:1901700 to subset gocheck_obsoletion_candidate
add GO:0030003 to subset gocheck_obsoletion_candidate
add GO:0016043 to subset gocheck_obsoletion_candidate

I think the subset is not in the ontology products yet.

@pgaudet instead of:

Hey, Ontobot! apply:

use:

Hey Ontobot! apply: (no comma)

I just tested this out (I also didn't capitalize "ontobot" but I think that's okay).


[Feature request] Add "Limits", "Vision 5e" and "Walled Templates" for an evolution of some spells such as Darkness.

Consider adding the following "Limits", "Vision 5e" and "Walled Templates" modules as mandatory and/or optional for an evolution of some spells such as Darkness.
Before I started writing some code I wanted to know if it was something you were interested in.
Here https://github.com/dev7355608/limits you can find some macro example of the new strategy used from dev7355608

I don't want to speak for him, but Chris has been fairly vocal about wanting to keep at least his implementation of Darkness as is (as in: a template on the canvas that does not enforce any actual vision limitation, and instead relies on player imagination).
If you want to use limits and vision 5e to create actual vision limitation, you may need to see if Mr Primate wants to add it to DDBI as he had done previously (and may well have already done again in v11 with the new modules, I just can't check).


Fixed the test flakiness

Fixed test flakiness (Ersatz update)
Upgraded Gradle and Groovy

Changes Unknown when pulling a5e904fab4c354f7ac775a5972a9a3da12cd4efb on flaky-test-fixes into ** on development**.

Changes Unknown when pulling a5e904fab4c354f7ac775a5972a9a3da12cd4efb on flaky-test-fixes into ** on development**.

Changes Unknown when pulling a5e904fab4c354f7ac775a5972a9a3da12cd4efb on flaky-test-fixes into ** on development**.


Workload IDs for non-k8s workloads

For the purpose of telemetry, workloads carry an ID so that Mixer can extract additional metadata about the workloads. For kubernetes, it's of the form kubernetes://podX.nsY. How do we deal with non-kubernetes workloads, such as VMs or mesh expansion?

Not stale. @jeffmendoza has been doing some thinking on this issue recently.

related https://github.com/istio/api/issues/610

/cc @incfly

I think it is time to close this. Mixer is no longer a going concern, and VM identity has evolved.


removed cacheFirst policy

there was unwanted code which was upgrading cache first to Cache and network.
Open scrum link

closing in favor of #398


WSGI applications warning

I missed it, but with my PR about WSGI apps, sphinx now raises this warning:
pickling environment... WARNING: cannot cache unpickable configuration value: 'screenshot_apps' (because it contains a function, class, or module object) [config.cache]

I suggest to change the format of screenshot_apps and pass python import references (for instance my.module:create_app) as values instead of a callable.
What do you think?

Thanks for your suggestion. Yes, it sounds good to me.


Release @google-cloud/dns v0.9.0

This pull request was generated using releasetool.

Release is at https://github.com/googleapis/nodejs-dns/releases/tag/v0.9.0


[bug] Moon main thread panicked while using git version 2.43.0.vfs.0.0

Describe the bug
moon main thread panicked with the installed Git version "2.43.0.vfs.0.0".
moon run app:build
Error:   × Main thread panicked.
  ├─▶ at nextgen\vcs\src\git.rs:639:36
  ╰─▶ called `Result::unwrap()` on an `Err` value: Error("unexpected character '.' after patch version number")
  help: set the `RUST_BACKTRACE=1` environment variable to display a backtrace.

Steps to reproduce

has a git installation with version 2.43.0.vfs.0.0
run any task from the root of the moon repo

Expected behavior
moon can run tasks
Environment

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
    Memory: 3.24 GB / 15.93 GB
  Binaries:
    Node: 21.5.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Managers:
    Cargo: 1.70.0 - ~\.cargo\bin\cargo.EXE
    pip3: 23.0.1 - C:\Python311\Scripts\pip3.EXE
  Utilities:
    CMake: 3.23.0
    Git: 2.43.0.
    Clang: 16.0.2 - C:\Program Files\LLVM\bin\clang.EXE
    Curl: 8.0.1 - C:\Windows\system32\curl.EXE
  Virtualization:
    Docker: 24.0.6 - C:\Program Files\Docker\Docker\resources\bin\docker.EXE
  IDEs:
    VSCode: 1.85.1 - C:\Users\p\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
    Visual Studio: 17.8.34408.163 (Visual Studio Community 2022)
  Languages:
    Bash: 5.1.4 - C:\Windows\system32\bash.EXE
    Python: 3.11.0
    Rust: 1.70.0
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.144), ChromiumDev (122.0.2348.0)
    Internet Explorer: 11.0.19041.1566

Additional context
git --version
git version 2.43.0.vfs.0.0

The issue is similar to #945 . possible source: https://github.com/huandzh/moon/blob/fb3c05016e6537acf50f7bf2a384017e89b3961f/nextgen/vcs/src/git.rs#L29-L52

btw. 2.43.0.vfs.0.0 is the version number from VFSForGit.

Fixed in 1.20


I can't enable wireframe mode

Hi,
I'm an engineer and I'm trying to use MuJoCo python bindings for my new project.
I want to make a video rendered in wireframe mode because it gives a much clearer look for my model.
Here is a code:
with mujoco.Renderer(model) as renderer:
        scene = mujoco.MjvScene()
        scene.flags[mujoco.mjtRndFlag.mjRND_WIREFRAME] = 1  # Enable wireframe mode
        duration = 10  # (seconds)
        framerate = 60  # (Hz)
        frames = []
        mujoco.mj_resetData(model, data)
        while data.time < duration:
            mujoco.mj_step(model, data)
            if len(frames) < data.time * framerate:
                renderer.update_scene(data, camera="Camera_0")
                pixels = renderer.render()
                frames.append(pixels)
renderer.close()

Those two lines with scene totally worked with mjr_render, but I don't know how to make them work with Renderer.
I would greatly appreciate it if you could let me know the way if there is any.
Thank you.

I believe this is a known issue, see #1190.

I believe this is a known issue, see #1190.

So there isn't a solution yet? It's fine then, wasn't a big deal.
Thank you.

This is not #1190 since it's got nothing to do with the viewer.


Function missing in experiments.predict_pretrained

Hi!
I'm trying to run a trained model (linear, non-struct, full) on my data while I realize "linear" is not implemented even though it is mentioned as an option in ln 15 of experiments.predict_pretrained.py
Thanks!

Take a look at this file:
https://github.com/vene/marseille/blob/master/experiments/exp_baseline_linear.py
You could expand the "predict_pretrained" functionality using this approach.
On Fri, Jun 15, 2018, 17:33 Xinyu Hua<EMAIL_ADDRESS>wrote:

Hi!
I'm trying to run a trained model (linear, non-struct, full) on my data
while I realize "linear" is not implemented even though it is mentioned as
an option in ln 15 of experiments.predict_pretrained.py
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vene/marseille/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOwUXgQtKyp_7tUTfS6fsPr7DyjgMbeks5t9CgygaJpZM4UqLQM
.

Thanks, after some work I think it's solvable now.


Security Vulnerabilities are present in this library

When we try to utilize this library we get moderate level security vulnerabilities based on the dependencies

Ran npm audit fix, should be OK now.


Open/Preview submissions from Inference v2.1

In the MLPerf Inference v2.1 round, Qualcomm and their partners submitted a number of RetinaNet results, which the Review Committee eventually accepted to the Open division under the Preview category. Also, ResNet50 and BERT results from the same systems were accepted to the Closed division under the Available category.
Given the extenuating circumstances surrounding these RetinaNet submissions, I believe it would be reasonable NOT to require ALL of such submissions to be replayed in the v3.0 round under the Available category, for example, if a system is no longer available for experimentation.

Discussed two options:

Submit in v3.0 and withdraw during review period so that preview results stay in v2.1 table.
Not submitted in v3.0, and mark v2.1 preview results as retracted/invalid (exact action TBD based on the discussion from chairs meeting)

Option 2 was chosen

David is going to propose rule changes for Preview->Available

This issue has been open for 1.5 years. Let's close it?


Why was the Windows Sandbox extension removed?

I briefly witnessed Windows Sandbox support in a Microsoft Build session but can no longer find the feature. I see multiple mentions that the Sandbox extension was removed (https://github.com/microsoft/devhome/pull/3196), but no explanation why. I don't see it on the roadmap... what's up?

Hi @AnthonyMastrean, the Sandbox team has taken ownership of the extension and is currently ironing out some issues with it. They'll release the extension when it's ready. Keep an eye out in the future for updates, Thanks!


Implement except* syntax

See: #4479.

That one error may be transient?

there's some flakiness there, a re-run should get it passing (just triggered it)


Slim Multi-Container setup, with Docker-Compose.

While keeping in-tune with the original build, I created a multi-container setup which allows you to quickly and easily spin up a Rails/MySQL docker environment. This deviates significantly from the original repo, but figured I would submit a Pull request should this be an appealing "overhaul".
This setup is based on: https://docs.docker.com/compose/rails, but the README.md outlines just the necessary steps to get an environment running on localhost:3000

@allknowingfrog Nevermind. This is kinda broken/clunky to work with. Closing it up ;)


Video below hud for Psych Engine Pre release 1.0

Describe your problem here.
Can possibly make?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

no until ShadowMario fixes his LUA

no until ShadowMario fixes his LUA to 0.6.3 LUA

How do you think in what century this will happen?

no until ShadowMario fixes his LUA to 0.6.3 LUA

That's literally not true at all you baboon.

Can possibly make?


Add Fuel Code and Type Code to System Fuel Flows

The Fuel Flow code needs to be added to the System Fuel Flows API so that it will appear in the UI
Type code needs to be added to the System Fuel Flows API so that it will appear in the UI

https://epacamd.testquality.com defect D43. Do not remove or edit.

The Fuel Code is not showiong the correct data it is showing the Unit of Measure Code instead

Original Ticket was: 898

@tdavydets this is ready for ui work as api now returns the fuelCode and systemTypeCode

Test Case: TC189

Test Passed


Reference number is missing(#5)

Hi Ao,
I think it might be more clear if you add numbers to your references, like this:
[1] Web Caching project. http://www.ircache.net.
[2] Intel Outlines Platform Innovations for More Manageable, Balanced and
Secure Enterprise Computing. Intel Press Release, February 2004.
http://www.intel.com/ca/pressroom/2004/0218b.htm.
[3] T. Abdelzaher, K. G. Shin, and N. Bhatti. Performance guarantees for Web
server end-systems: A control-theoretical approach. IEEE Transactions on
Parallel and Distributed Systems, 13(1), 2002.
[4] B. D. O. Anderson and J. B. Moore. Optimal Control: Linear Quadratic
Methods. Prentice Hall, 1989.

Again, I was just following the template.
@smiths
What's your preference?

It'll keep unchanged unless Prof. Smith thinks otherwise.

The references look fine to me.


renderTags method should not be escaped in templates

Hi,
Documentation says that we should use renderTags() method inside template like this {{ $og->renderTags() }} which I believe is not correct, at least for Laravel 5.1.
I'm new in Laravel, using 5.1 and I was able to render meta tags correctly only without escaping it like this:
{!! $og->renderTags() !!}

Maybe I'm wrong and missing something, if so let me know.
For now as I see It's just documentation problem, everything works well, thanks for this awesome package!

I have to take a more in-depth look at it - but yes, I assume you are right. The documentation needs a Laravel 5 update - urgently.

As you mentioned, in Laravel 5.x one has to use the {!! ... !!} tags. The {{ ... }} tags are old Laravel 4 style.
Updated the README: https://github.com/chriskonnertz/open-graph/commit/a540cce93a72362b709564c4a787640072014d21
Thanks for your feedback! These kind of issues are sometimes difficult to see for me. Let me now if there are any other unprecise / wrong statements in the README.


Remove RSA Public Key Complexities

Closes #306.

Do you think that an unit test could be a bad idea to have for this? @DMats, @calina-c any thoughts?

Added.


Properties window uses wrong theme

Description
When searching to see the properties of the hard disk, the data is made unreadable as there is contrast in the background and the text
Steps To Reproduce
Open files app
Left click on the hard drive (any)
Select hard drive properties
the properties window opens
Expected behavior
That the properties of the hard disk can be displayed
Files Version
Versión: <IP_ADDRESS> OS Version: 10.0.22000.176
Windows Version
Windows 11 Pro Versión	21H2  22000.176
Relevant Assets

What theme do you have set in Windows? Is it dark theme in windows but light theme in Files?

Dark Mode

I have been trying to reproduce this issue and I haven't been able to, I've tried different combinations of light/dark mode for windows and files, I've also tried different themes (both included and added manually). I've also tried restarting and not restarting Files after the changes.
This might have been solved in between <IP_ADDRESS> (the version in the issue and my version <IP_ADDRESS>).
Version: <IP_ADDRESS>
OS Version: 10.0.19042.1466

Thanks for the info, probably still not solved in 2.1.5 judging from #8083. All reports seem to be relative to windows 11.

This issue should be resolved with #8837


Impose a maximum transaction size limit?

Should we impose a limit on the overall size of a transaction, i.e. as part of transaction validation?
There are soft limits imposed by the backend database. For example, in RethinkDB:

While there is no hard limit on the size of a single document, there is a recommended limit of 16MB for memory performance reasons.

Since blocks are documents and a block can contain up to 1000 transactions, that means that the soft limit on a transaction size would be about 16MB / 1000 or about 16kB.

I don't see a reason to build this in now or any time soon.
I think we should be integrating this retroactively (if a customer demands it).

Note: In MongoDB, there's a similar limit:

The maximum BSON document size is 16 megabytes.

The maximum document size helps ensure that a single document cannot use excessive amount of RAM or, during transmission, excessive amount of bandwidth. To store documents larger than the maximum size, MongoDB provides the GridFS API. See mongofiles and the documentation for your driver for more information about GridFS.

Note that it's a limit on the BSON document size, so not the same thing as with RethinkDB.


Destructuring with default values in function argument breaks union type

Simple reproduction
When destructuring an object function argument and providing a default value to one of the keys, it appear to break union types.
In linked example someFunc takes one argument, and object, which are expected to have one property, letterSpacing. This is typed to be string | number. Calling someFunc with this property set to either string or number works fine. However, when providing a default value when destructuring, an unexpected errors is shown.

Here's a variation on typing this that throws a slightly different error - Try Flow.
type Props = {
  width?: number | string
};

const Component = ({
  width = '100%',
}: Props) => null

6:   width = '100%',
     ^ string [1] is incompatible with number [2].
   References:
   2:   width?: number | string                      ^ [1]
   2:   width?: number | string
                ^ [2]
---------------------------------------------------------------------
6:   width = '100%',
             ^ string [1] is incompatible with number [2].
   References:
   6:   width = '100%',
                ^ [1]
   2:   width?: number | string
                ^ [2]

Duplicate of #2093


playwright-sharp CLI tool does not recognize .NET 5 SDK

After installing the CLI tool in a Linux docker container that has .NET 5 SDK installed, attempting to run the tool gives the following response:
It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '3.1.0' was not found.
  - The following frameworks were found:
      5.0.0 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
  - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=3.1.0&arch=x64&rid=ubuntu.20.04-x64

We are trying to kill the global tool. What are you using it for?

Oh I see now.  Since there wasn't a link to the preferred Nuget package in the readme, I simply searched for Playwright on NuGet Gallery and ended up with the global tool.  Perhaps a link or installation instructions could be added to the readme?  I can create a PR if that would help.

We explain most scenarios here https://github.com/microsoft/playwright-sharp/blame/master/README.md#L37
What do you think about that?

That section is great, I missed the NuGet link/badge in the H1 header.


Allow the service to be manually managed

There are cases where you may want to install rabbitmq, but not start the service immediately.  For instance, when preparing an AMI for AWS, you may want to install all of the software and then when launching the instance only do the configuration.  It is also useful when you want to use systemd instead of the default initd scripts.

Can you update the chefspec to check for this also? It would be nice to have one check for it on, and one check for it off.
I'm planning on releasing another version of the rabbitmq cookbook this by end of week and i'd like this in  it.

Sorry for the delay, I'm looking into this now.

@jjasghar I've just added some tests, this is my first time messing around with kitchen/spec, but I've confirmed it works locally.  Let me know if any other changes are required or if what I did was not idiomatic.  Thanks!

Awesome, thanks!

I suspect I've done something wrong with the tests, when I just have the following test, which should error out, it still passes:
  it 'does not enable a rabbitmq service when manage_service is false' do
    node.set['rabbitmq']['manage_service'] = true
    expect(chef_run).not_to enable_service('rabbitmq-server')
  end

Output
$ kitchen test default-ubuntu-1404

...

       Finished in 0.69908 seconds
       15 examples, 0 failures
       Finished verifying <default-ubuntu-1404> (0m59.66s).

Ah, tk, runs the integration tests, you need to run chefspec which is easiest ran by: rake spec in the main directory.

@jjasghar Thanks for the help.  I had read the CONTRIBUTING.md file and completely missed the TESTING.md file.  Everything should be working now.  I'm going to have to read up on chefspec.


Add[#53]:Added new features to the Number Puzzle Master

Difficulty level selection: Players can now choose a difficulty level for the game, making it more challenging for experienced players and more accessible for new players.
Score tracking: The game now tracks the player's score, which is displayed at the end of the game. This gives players a goal to strive for and encourages them to improve their performance.
Timer: Players can now start a timer to challenge themselves to guess the correct number in a certain amount of time. This adds an element of excitement and pressure to the game.
Multiple secret numbers: The game now supports multiple secret numbers, making it more challenging and unpredictable.

@vivekvr1
Perfect.
Great work... Keep going 🚀
Have fun!


Add left/right shift operator support

I am sorry about too many commits for minor modification.

This pull request looks good at first glance. However, signedness is not yet supported in latest MazuCC, and it impractical to distinguish between logical and arithmetic shifts. I would expect there is remark in code generation.

@fakepaper56, any further changes?


SaveToken doesn't propagate client, user, scope to generateAcessToken if asyc is used

I'm using [latest version from master] (https://github.com/oauthjs/node-oauth2-server/commit/fcf78d1bde2e7628491c943e93fe0db61ec3f0df)
I found that when using my custom model generateAccessToken doesn't receive the arguments (client, user, scope)  when using async generateAcessToken.
I found a solution by binding this context to each function when declaring the array fns.
In lib/grant-type/grant-type-password.js
PasswordGrantType.prototype.saveToken = function(user, client, scope) {
  var fns = [
    this.validateScope(user, client, scope),
    this.generateAccessToken(client, user, scope).bind(this), // <- adding bind here
    this.generateRefreshToken(client, user, scope),
    this.getAccessTokenExpiresAt(),
    this.getRefreshTokenExpiresAt()
  ];

  return Promise.all(fns)
    .bind(this)
    .spread(function(scope, accessToken, refreshToken, accessTokenExpiresAt, refreshTokenExpiresAt) {
      var token = {
        accessToken: accessToken,
        accessTokenExpiresAt: accessTokenExpiresAt,
        refreshToken: refreshToken,
        refreshTokenExpiresAt: refreshTokenExpiresAt,
        scope: scope
      };

      return promisify(this.model.saveToken, 3)(token, client, user);
    });
};

If this solution is acceptable I can prepare a pull request.
I guess the same problem will apply to validateScope and generateRefreshToken,
and other grant-types
Thanks

Could you post your model's generateAccessToken?
Your solution binds this to the return value of AbstractGrantType#generateAccessToken which might or might not be a promise. In case it's not, calling .bind(this) would crash.

Thanks for quick answer,
you can reproduce the issue in master with this model implementation.
async generateAcessToken(user, client, scope) {
   debugger      // <- here arguments.length is 0, but test-token is returned correctly in the response
   return 'test-token'
}

Without async , it will work as expected.
generateAcessToken(user, client, scope) {
   debugger      // <-  arguments.length is 3
   return 'test-token'
}

Don't get me grown, in my real JWT implementation I don't use async
  generateAccessToken(client, user, scope) {
    let secret = this._accessSecret
    let expiry = this._accessExpirySeconds
    let exp = new Date()
    exp.setSeconds(expiry)
    if (user.id) {
      let payload = { iss: JWT_ISSUER, userId: user.id, exp: exp.getTime() }
      return JWT.sign(payload, secret)
    }
    throw new Error('No user id')
  }

It works fine as expected, it just happen that I accidentally found the bug
and I though that all model function should work with Promises too.

I don't know how exactly Babel is transpiling async constructs. Maybe promisify-any is misinterpreting the generated code. I'll check on that later this weekend.


diff lexer is not covered

We use accessible-pygments in the pydata-sphinx-theme and recently a user complained about the parsing of a specific lexer: diff
After changing the pygment style the styling came back so my guess is that you are not covering some of the tags related to this lexer.

See https://github.com/pydata/pydata-sphinx-theme/issues/1506 for more details.

Duplicate of #31

I'm so slow ;-)


Error running kubb: ERROR  swaggerPlugin.context.getOas is not a function

What version of kubb is running?
2.25.1
What platform is your computer?
Linux
What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)
{   "name": "my-project-next",   "version": "0.1.0",   "private": true,   "scripts": {     "dev": "next dev",     "build": "next build",     "start": "next start",     "lint": "next lint"   },   "dependencies": {     "@kubb/cli": "^2.25.1",     "@kubb/core": "^2.25.1",     "@kubb/plugin-oas": "^3.0.0-alpha.4",     "@kubb/plugin-tanstack-query": "^3.0.0-alpha.4",     "@kubb/plugin-ts": "^3.0.0-alpha.4",     "next": "14.2.6",     "react": "^18",     "react-dom": "^18"   },   "devDependencies": {     "@types/node": "^20",     "@types/react": "^18",     "@types/react-dom": "^18",     "eslint": "^8",     "eslint-config-next": "14.2.6",     "typescript": "^5"   } }
What steps can reproduce the bug?

New installation of Next.js
Installing core packages and working with TanStack Query: npm i @kubb/cli @kubb/core @kubb/plugin-oas @kubb/plugin-tanstack-query @kubb/plugin-ts
Creating the kubb configuration file kubb.config.ts at the root of the project with the content:

import { defineConfig } from '@kubb/core'
import { pluginOas } from '@kubb/plugin-oas'
import { pluginTanstackQuery } from '@kubb/plugin-tanstack-query'
import { pluginTs } from '@kubb/plugin-ts'

export default defineConfig({
  root: '.',
  input: {
    path: './.tmp/myproject-swagger-api.json',
  },
  output: {
    path: './src/gen',
    clean: true,
  },
  plugins: [
    pluginOas({}),
    pluginTs({}),
    pluginTanstackQuery({}),
  ],
})

Run the command to generate the code: kubb --config kubb.config.ts or kubb

❯ kubb --config kubb.config.ts
✔ 🔍 Config loaded(kubb.config.ts)
✖ 🚀 Build failed ./.tmp/myproject-swagger-api.json
                                                                                12:02:54 PM

  Plugins:      3 failed, 3 total
   Failed:      plugin-oas, plugin-ts, plugin-tanstack-query
Generated:      252 files
     Time:      0.875s
    Ended:      Sun Aug 25 2024 12:02:54 GMT-0300 (Brasilia Standard Time)
   Output:      .

 ERROR  swaggerPlugin.context.getOas is not a function (plugin: plugin-ts, hook: buildStart) (plugin: plugin-ts, hook: buildStart)                                                             12:02:54 PM

  at EventEmitter.<anonymous> (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/chunk-3OXCZ5DJ.js:145:19)
  at EventEmitter.emit (node:events:519:28)
  at EventEmitter.emit (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/chunk-3OXCZ5DJ.js:101:34)
  at Object.emit (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/chunk-3OXCZ5DJ.js:158:21)
  at PluginManager.catcher_fn (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/index.js:614:15)
  at /home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/index.js:406:69
  at Array.forEach (<anonymous>)
  at PluginManager.hookParallel (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/index.js:403:13)
  at async safeBuild (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/node_modules/@kubb/core/dist/index.js:787:5)
  at async generate (/home/myuser/.asdf/installs/nodejs/20.17.0/lib/node_modules/@kubb/cli/dist/chunk-VGYRBGKV.js:214:36)

How often does this bug happen?
Every time
What is the expected behavior?
Have the code generated
Swagger/OpenAPI file?
No response
Additional information
No response

The docs on Kubb were redirecting to the alpha version(v3) which makes a part of your deps being redirected to v3 instead of the stable version(v2). Best to update your package.json again with the following(see ^2.25.1):
{ "name": "my-project-next", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint" }, "dependencies": { "@kubb/cli": "^2.25.1", "@kubb/core": "^2.25.1", "@kubb/plugin-oas": "^2.25.1", "@kubb/swagger-tanstack-query": "^2.25.1", "@kubb/swagger-ts": "^2.25.1", "next": "14.2.6", "react": "^18", "react-dom": "^18" }, "devDependencies": { "@types/node": "^20", "@types/react": "^18", "@types/react-dom": "^18", "eslint": "^8", "eslint-config-next": "14.2.6", "typescript": "^5" } }


Broken tests in Selenoid with TestNG threads when Chrome node version is 124

Hi Team,
Opening this topic as you might be able to help or clarify what is wrong with our run and whether this is a problem with Selenoid or maybe Chrome or there could be something else.
We do run a lot of tests using TestNG 7... + Selenide 7.. ( its Configuration.timeout=45000 and Configuration.pageLoadTimeout = 60000) + Java 17 with jobs using Selenoid Grid and Selenoid, and Chrome node version 115 without problems in parallel having 16 cores and max number of threads up to 14 (depends on a suite) in dind.
Test suites look simple. This one as an example with parallel run and 4 threads, and a couple more tests with parallel="none" within the same suite here :

having on a BaseClass
@AfterMethod(alwaysRun = true)
Selenide.closeWebDriver();
The problem starts when we wanna switch to newer version of Chrome: and here the higher version we are using, more random  number of tests (and what is important here threads either) start failing being marked as broken with different errors related to either
session timeouts
or
invalid session id
or
org.openqa.selenium.WebDriverException: Command duration or timeout: 1 milliseconds
(maybe there are others, but I wrote down these as examples and attached some ones below)
And the main thing here is that when one test fails, all the other subsequent ones in one thread also fall like dominoes in a very short period of time.
I have tried 122 and 124 versions. So, where Chrome 115 marks tests correctly as failed and Allure takes a snapshot with an actual error after a failed step, with Chrome 124 random number of tests are marked as broken (and it may happen even to the same test in the same places, what makes me think that might be a problem with Node). Cannot blame our tests either, as they do work fine with 115 either it is Selenoid or Selenium Grid.
I have played with timeouts: -timeout 2m, -timeout 5m; -service-startup-timeout was around 1m20s (I probably had tried increasing all 4 timeout options in 2x, but with no luck);  to be honest, all test are run against chrome 115 without any additional settings at all, so here I am a bit skeptical that my changes would have helped out, and they actually have not (unless new nodes are more heavier being required more tuning).
What is weird that when the first test is broken, then the second test starts either in a defined in Selenide timeout of 45 sec or in ~5 sec (but it will be broken anyway regardless); and next test starts in 5 sec again and will fail and this is all till the moment when thread is over (I will be shown below). But we do not have those 5 secs in settings at all: I have no clue where they are coming from. I was expecting the same behavior regardless nodes and all tests being isolated, and if 1 test fails, it is marked as failed, session closed and the new test will be kicked off within a separate node, and we would have been having normal allure yellow-green report, but not with broken ones.
Chrome 115
Allure snapshots below will be probably with limit as 14 and thread-count="4":

Allure results

Chrome 124
Test 1 (the first yellow one in a thread)
The number of affected threads (yellow ones) could be different:

More than 1 broken thread (as an example that it is a random)

Test 1 content (from the snapshot there 1 thread):

Selenoid logs (test 1)
I was able to find only these 3 entries of session ID but you will see more attempts to use the same ID in a following tests below:
15:13:22 [31218] [SESSION_CREATED] [8f113074857c76c329dffdc1b432def2] [1] [1.44s]
15:14:24 [31299] [SESSION_TIMED_OUT] [8f113074857c76c329dffdc1b432def2]
15:14:24 [34422] [SESSION_DELETED] [8f113074857c76c329dffdc1b432def2]
Test 2 (the second yellow in a thread)

Take a look that sessions IDs are the same: seems like all tests starts with the same session?
4th test (as 3rd looks similar to 2nd)

I found only 1 SESSION_TIMED_OUT entry in the selenoid logs related to a common for all session as
8f113074857c76c329dffdc1b432def2. The rest look like duplicates and even being grouped under Allure Category as here:

Grid with Chrome 125
Grids compose file does not have additional timeout options at all only 14 nodes in parallel: we do have different jobs being run against the same suites on Selenoid and Grid, but the output varies drastically.
This is a recent test run against Chrome 125 on Grid, where beforeMethod failed after 1m timeout, but, at least, snapshop is taken and we are able to see the error:

Also, as I have already mentioned those 5 sec timeouts from yellow threads above look weird and they obviously do not come from Selenide nor chrome capabilities.
I am not 100% sure that chrome 115 is stable, but we do currently on it, and will see if I could switch Grid to Chrome 125 after its resent release.
What I have not tried yet is to create a chrome image with the latest chrome driver, but I do not think it would help out.
Is there a big difference in their internal settings between Selenoid and Grid when it comes to Nodes? Is there a way to stop the test/node within a defined timeout and not to start a new test with (probably) the same ID? It looks to me that an isolation does not work properly, but I could be wrong.
I really like Selenoid and I would like to switch to it considering its video’s feature, but currently blocked by unstable results. If you have any advises based on info above how to set up considering provided timeouts and settings or whether who should I contact with, it would be appreciated.
Thanks.
Kind regards

@farious2009 actually we noticed that some Chrome \ chromedriver versions are from time to time less responsive than another versions. In 1-2 versions once Chrome team fixes bugs in Chrome \ chromedriver everything could become more stable again. I would rerun freezing \ slow test cases with video recording enabled to see what's happening inside. Also I would check that your application does not rely on some new APIs when available.

I had tried checking video, but they have not even started being recorded remained with prefix selenoid_ and small size.
Do you think it would be work asking Selenide devs as maybe that framework uses something from updated Chromium there under the hood mentioning an entire engine as Edge works in the same way)?

@farious2009 if your videos are not renamed to <session-id>.mp4, then this is Selenoid misconfiguration. Selenoid images contain both webdriver binary and browser binary, so I don't think Selenide guys will help. Selenide is just a Selenium helper library on top of official Java Selenium client.

Thanks. I have asked about the same under Selenium Docker, because I am guessing it is not related to Selenoid only, because 124-125 versions are failing with different errors. but the behavior look similar (though, visible errors are different): but again, it varies from Chrome to lover Chrome.

and, by the way, regarding video: videos themselves are recorded, I am able to do so, but only against normal tests; broken ones what I am here about, as you said are marked with selenoid_... and cannot be opened (what is probably expected by the logic)

I have a feeling it is either node's issue, but I am not an expert here, of course, only what I noticed in common

@vania-pooh @farious2009  Same error for me when I switched from Chrome 105.0 to 123.0.
I created a report, but it has not been accepted yet. Read also, that newest drivers hand over more logs than previously, but even having logging disabled it had not helped me out too much.
I am still on 115...


Child theme crashing site

Hello,
I just downloaded the main bootstcore theme and the child theme.
After I installed both on my fresh Wordpress installation, I can navigate the site with the parent theme activated.
But when I activated the child theme, I can't load the website anymore.
The progress bar on the browser starts loading but gets stuck right away and won't move.
Do I need to do something else than uploading and activating the theme?
Thank you.

Hello Rhatur,
installed a fresh WordPress, bootscore, bootscore-child and activated it. Works fine. BTW a link to your site will be very helpful to help.
Please check this:

are you sure that you installed bootscore-child and not bootcommerce-child? bootcommerce-child needs WooCommerce to work.
Activate a default WP theme like Twenty Twenty-One and delete booth bootscore themes.
Download and install bootscore https://github.com/bootscore/bootscore.
Download and install bootscore-child https://github.com/bootscore/bootscore-child.
Activate it.

Does this help?

Thanks for your answer crftwrk,
I was downloading the files from my account and not directly from Github so I tried with your link.
After waiting over 20 minutes, I finally got this error on my site:
`
Call Stack
1 |<PHONE_NUMBER>2.5350 | 366256 | {main}( ) | .../index.php:0
2 |<PHONE_NUMBER>2.5350 | 366568 | require( '/Users/arthur/Sites/Local Sites/magic-bears-studio/app/public/wp-blog-header.php ) | .../index.php:17
3 |<PHONE_NUMBER>2.5350 | 2782664 | require_once( '/Users/arthur/Sites/Local Sites/magic-bears-studio/app/public/wp-includes/template-loader.php ) | .../wp-blog-header.php:19
4 |<PHONE_NUMBER>2.5350 | 2848776 | include( '/Users/arthur/Sites/Local Sites/magic-bears-studio/app/public/wp-content/themes/bootscore-main/index.php ) | .../template-loader.php:106
5 |<PHONE_NUMBER>2.5350 | 2848776 | get_header( ) | .../index.php:16
6 |<PHONE_NUMBER>2.5350 | 2849152 | locate_template( ) | .../general-template.php:48
7 |<PHONE_NUMBER>2.5350 | 2849312 | load_template( ) | .../template.php:716
8 |<PHONE_NUMBER>2.5350 | 2849952 | require_once( '/Users/arthur/Sites/Local Sites/magic-bears-studio/app/public/wp-content/themes/bootscore-main/header.php ) | .../template.php:770
9 |<PHONE_NUMBER>2.5350 | 2859360 | wp_head( ) | .../header.php:29
10 |<PHONE_NUMBER>2.5350 | 2859360 | do_action( ) | .../general-template.php:3015
11 |<PHONE_NUMBER>2.5350 | 2859736 | WP_Hook->do_action( ) | .../plugin.php:470
12 |<PHONE_NUMBER>2.5350 | 2859736 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:327
13 |<PHONE_NUMBER>2.5350 | 2862816 | wp_enqueue_scripts( ) | .../class-wp-hook.php:303
14 |<PHONE_NUMBER>2.5350 | 2862816 | do_action( ) | .../script-loader.php:2083
15 |<PHONE_NUMBER>2.5350 | 2863192 | WP_Hook->do_action( ) | .../plugin.php:470
16 |<PHONE_NUMBER>2.5350 | 2863192 | WP_Hook->apply_filters( ) | .../class-wp-hook.php:327
17 |<PHONE_NUMBER>2.5350 | 2865176 | bootscore_child_enqueue_styles( ) | .../class-wp-hook.php:303
18 |<PHONE_NUMBER>2.5350 | 2865624 | filemtime ( ) | .../functions.php:11
`

I am using Local by flywheel and out of curiosity I decided to tried on a live server and there I didn't get any issue.
Any idea on how to use the theme on a local installation?
Thanks for your help!

Maybe theme doesn't like flywheel. I use mamp for local installations and works fine.
Try one of this:

https://www.apachefriends.org/
https://www.mamp.info/
https://localwp.com

I am using https://localwp.com.

You got this error by using localwp? Please try https://www.apachefriends.org or https://www.mamp.info/ instead.

Well I am sorry but I can't change the full process for local development.
I'll dig some more information about this issue in the next weeks and get back to you.
Thanks for your help.

Thanks


Add support for the Snappy codec

This allows reading and writing snappy-compressed data using the Ruby library.
I haven't added a hard dependency on the snappy gem, as I figure people shouldn't be forced to install it if they're not using the codec anyway. However, this means that users must require the snappy gem themselves.

Please file an issue on the project tracker: https://issues.apache.org/jira/browse/AVRO/
Also please try to coordinate with the solution in #31

@busbey https://issues.apache.org/jira/browse/AVRO-1697

Can we add better detection of when the snappy gem isn't present and fail gracefully?

Sure, I'll try lazy-requiring it.

@busbey how does this look?

Merged into trunk.


Using ft!help with a command (Caesarcrypt, for example) just brings up the main page of help

read title

hmm, lemme fix this. i think i removed it when making the new help command

Fixed in 77e4904c6855de03b8191b7300a811f482b4898e

NVM, I actually didn't fix anything. You are using a category instead of an actual command

wut


Filter queues by name

Is there any way to filter which queues are returned?

This should be solved by #12


[FLINK-21857] StackOverflow for large parallelism jobs when processing EndOfChannelStateEvent

What is the purpose of the change
This commit moves draining the virtual channels at the end of recovery
out of the CheckpointedInputGate#pollNext method in to the main loop of
StreamTaskNetworkInput so that we do not build up a deeply nested stack.
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

I think the amended approach is a more natural way to handle an "end of recovery" event.
One suggestion is to add one more test for "InputStatus.END_OF_RECOVERY".
Previously this info is implicitly tested in testUpstreamResumedUponEndOfRecovery

Thanks for fixing-up! LGTM.


Help with understanding

Hi guys,
Thank you so much for this plugin, it's awesome! Would you be so kind to help me understand what is happening under the hood of Haxe compiling? As i understand Haxe is just intermediate syntax between Haxe language and c++. I mean if Haxe compiles directly to c++ why compiling time in Haxe is so short? Are we compiling C++ generated code after Haxe compilation?
Thank you, hope UE 4.12 support will be released soon. Now i have this kind of problem:
\Plugins\UE4Haxe\Source\HaxeInit\HaxeInit.Build.cs(1404,22) : error CS0619: 'UnrealBuildTool.RulesCompiler.GetModuleFilename(string)' is obsolete: 'GetModuleFilename is deprecated, use the ModuleDirectory property on any ModuleRules instead to get a path to your module.'

Hi there. Thanks for your support!
Haxe does compile to C++, and the normal compilation times are actually a bit bigger than a normal Unreal C++ project. It compiles a part of the code while compiling Haxe, and also creates a bunch of glue code that is compiled by Unreal, after Haxe compilation.
However, we support cppia, which is a virtual machine made by the same author of the C++ Haxe target. Cppia compiles in a couple of seconds at most, and allows you to achieve very fast iteration times, while allowing you to compile the final builds in C++ itself. You can read more about it at https://github.com/proletariatgames/unreal.hx/wiki/Faster-compiler-iteration-with-cppia .
Also for a cool demo of how fast it compiles when using it, you can check out this video https://www.youtube.com/v/WOK5m_D1gOc?start=3854&end=4027&version=3&autoplay=1
As for the error, we still don't support UE 4.12, but I've opened an issue about it: https://github.com/proletariatgames/unreal.hx/issues/44 . I'll close this one, but feel free to ask more questions if you need.


Fix development site

Fixes SSR after merging in the i18n branch. There was a check to window which is undefined server-side.

approved


access to the last training epoch that triggered early stopping

Description & Motivation
I wish there was a method to access when the last training epoch number was. The max_training_epoch differs from the last training epoch resulting from the early stopping.
cc @borda @carmocca @awaelchli

Hi @jaeho3690
Is this what you are looking for?
print(trainer.early_stopping_callback.stopped_epoch)

yes! I was looking for this feature  :)  thank you!


Featured posts are not listed

The title of the "Featured" section is displayed, but the articles are not listed.
All settings appear to be correct.
In the theme: show featured posts, featured posts category and number of featured posts to show.
In blog-config: show featured posts
In the blog post: assigned to the category declared in the theme parameters.

@ventoux84
Well, the problem is that you are defining the "featured" category instead of the tag. The Mundana theme filters featured articles by tag, not category.
In partials/sidebar/featured you can see the related code:
  {% for p in page.evaluate({'@taxonomy.tag':featuredposts_tag}).order('date', 'desc').slice(0,featuredposts_number) %}

The problem is that in the theme settings, "Featured posts category" appears in the featured posts config, instead of "Featured posts tag". I should fix this in the next version.
Try using the tags from your taxonomy for featured posts.

OK, featured is relative to tags and no to categories.
But "featured" seems to bee hard coded too ! The only one tag that works is "featured" and nothing else.

@ventoux84 , the featured tag is not hard coded, you have an option in theme configuration to set this:
In base.html.twig:
{% set featuredposts_tag = theme_var('featuredposts_tag')|defined('featured') %}

The problem is in theme configuration, this variable is named as featuredposts_category instead featured_tag.
I need to change this issue in theme configuration for next version

Yes, but nothing else than "featured" works.
I've entered the French word "favoris" in this variable.
Then I assigned this tag to an article by also creating the tag.
Nothing is displayed in the sidebar under the title "Featured".
If I add the "featured" tag to the same article, it's displayed in the sidebar under the "Featured" title.

@ventoux84 Can you test the featuredposts branch to see if featured posts now appear in sidebar

OK,I'll do it tomorrow; mañana, por la mañana.

I tested the featuredposts branch and i saw that featured posts now appear in sidebar.
Thanks, it's perfect.