Exercise: Gradle remote setup + multi repo dependency in gradle

How to add the remote repo in artifactory
add it to Gradle
Download an artifact via gradle

This is without the artifactory plugin avaliable

@sofusalbertsen First draft is ready for sanity check in the gradle_remote_and_artifactory_plugin folder


[Request] Support HTTPS for Linux ARM 32 Bit

zapret doesn't support  HTTPS/SSL. Could you suggest a program that supports Linux ARM 32 Bit?

It does.


Executing a single test runs before blocks from other contexts

Something really strange is going on when running an individual test (using the @current tag):
public class MySpecification : Specification
{
    public MySpecification()
    {
        context["context A"] = () =>
        {
            before = () => log("before A");

            it["assertion A1"] = () => log("A1 run");
            it["assertion A2"] = () => log("A2 run");
        };

        context["context B"] = () =>
        {
            before = () => log("before B");

            it["assertion B1"] = () => log("B1 run");

            @current =
            it["assertion B2"] = () => log("B2 run");
        };;
    }
}

This should just run the context B before block and assertion B2, but it ends up running the context A before block as well!  Here's the output:
MySpecification
  context A        < should not be run
    before A       < neither should this!
  context B
    before B
    assertion B2
      B2 run

Weird!

cc @ajwgibson @ianpurdy


Hello, is there a better ways than escape dot to address nested fields?

$userStore->updateById(24, [ "address.street" => "first street" ]);
Dot is used as a functional symbol. So if i need to get a value that contains a dot, is escaping the only way to go or are there any more elegant solutions?
Thanks :)

Hi @MerryPanda
Can you please share a little bit more information?
A little example document perhaps would be nice and what you want/ try to do with it in detail.
I am sure we can solve your problem.

I am closing this issue due to the lack of information.
Feel free to reopen it if needed.


'RNCWebView' could not be found

Bug description:

To Reproduce:

ERROR  Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR  Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
Expected behavior:

Screenshots/Videos:

Environment:

OS:
OS version:
react-native version:"0.64.4"
react-native-webview version:12.0.2"

Same issue

Same issue

I found the solution:
cd ios
/opt/homebrew/Cellar/cocoapods/1.12.1/bin/pod install

# you can also use pod install if pod is available for you.

If you could not find pod, you need to find the pod via whereis pod, in my cases it is said /opt/homebrew/bin/pod, but it is actually point to /opt/homebrew/Cellar/cocoapods/1.12.1/bin/pod.

same issue with android
ios work well

Does anybody have a solution to this, experiencing the same issue on android?

I have resolved it
downgrade to v11.23.1

I have resolved it downgrade to v11.23.1

Worked for me ! Thanks @khanhtn91

If you are like me, and running your build from CLI instead of XCode directly, you can solve this by running the build once from XCode which seems to be needed to automatically link up the new Pods after updating to this newer version. Hope that helps someone.

Hi team, same issue with us.
we can not downgrade the react-native-webView version to. 11.23.1 . any other solution to resolve it?
OS: MacOS
OS version: Android 12 and Android 13
react-native version:"0.64.4"
react-native-webview version:12.0.2"
Bug description:
To Reproduce:
ERROR Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.
ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native.

Downgrading to 12.1.0 works for me.

chez moi ce qu'a causé l'erreur c'est que certaines dépendances sont incompatibles avec la version d'expo installée :
j'avais installé<EMAIL_ADDRESS>Mais quand j'ai installé<EMAIL_ADDRESS>mon code a fonctionné

Worked perfectly ! Thanks @gilluminate

If you are like me, and running your build from CLI instead of XCode directly, you can solve this by running the build once from XCode which seems to be needed to automatically link up the new Pods after updating to this newer version. Hope that helps someone.

In my case, I was on react-native: 0.66.1, and I guess the latest version of react-native-web-view is not compatible with old react-native version.
Downgrading to 11 version worked as @khanhtn91 mentioned.
yarn add react-native-webview@11
See also: https://github.com/react-native-webview/react-native-webview/pull/2686#issuecomment-1414603408

You need to mock the module
jest.mock('react-native-webview', () => ({   default: () => jest.fn() // or any mocked component instead of native view, }))
https://github.com/react-native-webview/react-native-webview/pull/2686#issuecomment-1425865443

Same issue,
"react-native": 0.71.12,
"react-native-webview": 13.2.2,
"jest": "29.5.0"

What is the suggested Mock to interact with the component?
I tried a simple Mock passing these props
{
      goBack: jest.fn(),
      goForward: jest.fn(),
      reload: jest.fn(),
      stopLoading: jest.fn(),
      injectJavaScript: jest.fn(),
      requestFocus: jest.fn(),
      postMessage: jest.fn(),
      clearFormData: jest.fn(),
      clearCache: jest.fn(),
      clearHistory: jest.fn(),
    }

My Error just changed to
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.

I have the same issue.
react-native: 0.70.4
react-native-webview: 12.1.0

same issue
"react-native": "0.71.8"
"react-native-webview": "^13.2.2",
"expo": "~48.0.18"

I have resolved it downgrade to v11.23.1

eas build uses expo doctor  so is just upgrading it again. This makes the build crash in Testflight. Is there a way to avoid using expo doctor during eas build, or perhaps another solution?

same issue in android , downgrade to 11.23.1 isn't working.
"react": "16.11.0",
"react-native": "0.62.2",
"react-native-webview": "12.1.0"

Same issue here:

Please try with the below version of webview
"react-native-webview": "^12.4.0",

Same issue here when running my tests:
"react": "18.2.0",
"react-native": "0.71.11",
"jest": "^29.2.1",
"react-native-webview": "^13.2.2",

Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.

expo prebuild did nothing
but
npx react-native run-ios solved issue on ios
npx react-native run-android solved issue on android

expo prebuild did nothing but npx react-native run-ios solved issue on ios npx react-native run-android solved issue on android

worked for me as well - thanks!

Same issue here

Manually linking react-native-webview worked for by changing
android/app/build.gradle  android/app/src/main/java/earth/wallet/app/MainApplication.java  android/settings.gradle

I have resolved it downgrade to v11.23.1

work for me, thanks

Is there anyone to solve this issue? I have met this bug when my android targer is 33

Same issue. Tried all

When I try older version - it does not run at all. Like deprecated version - new version is community version, old one is. deprecated.

You need to mock the module
jest.mock('react-native-webview', () => ({
  default: () => jest.fn() // or any mocked component instead of native view,
}))

#2686 (comment)

This solution works for me!

Is there anyone to solve this issue? I have met this bug when my android targer is 33

Same issue on Android with the latest 13.3.1 version. iIOS works fine. Only manual linking help, but it should work without it.

Here is my mock
jest.mock('react-native-webview', () => {
  const React = require('react');
  const { View } = require('react-native');

  const WebView = props => <View {...props} />;

  return {
    WebView,
    default: WebView,
    __esModule: true,
  };
});

You need to mock the module
jest.mock('react-native-webview', () => ({
  default: () => jest.fn() // or any mocked component instead of native view,
}))

#2686 (comment)

Didn't work for me....
Instead of getting this error:
Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.
Now I get this one:
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components)
Changing to this, worked, but my snapshot now is empty...
jest.mock('react-native-webview', () => {
  const React = require('react');
  return {
    default: () => React.Fragment,
    WebView: () => React.Fragment,
  };
});

default config {
multiDexEnabled true //Add this line
}
At Path android/app/build.gradle

Here is the solution that i found which is working good for me
We're running react-native - 0.64 version and we had the same issue when we update the react-native-webview to 13.3.0. It looks like that react-native-webview is not linked correctly and what i found was to link the react-native-webview manually. But then the react native android build failed which throwed the "error source 7 does not have lambda expression". so then we got to include the JAVA version 1.8 as compile options in react-nativew-webview like the one below and include it as a patch  and rebuild it. This time it worked well 👍
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}

Here is the solution that i found which is working good for me
We're running react-native - 0.64 version and we had the same issue when we update the react-native-webview to 13.3.0. It looks like that react-native-webview is not linked correctly and what i found was to link the react-native-webview manually. But then the react native android build failed which throwed the error something like "source 7 does not have lambda expression". so then we got to include the JAVA version 1.8 as compile options in react-nativew-webview like the one below and include it as a patch and rebuild it. This time it worked well 👍
compileOptions { sourceCompatibility JavaVersion.VERSION_1_8 targetCompatibility JavaVersion.VERSION_1_8 }

Are you on a managed workflow or bare workflow? I have been battle this issue for days now. i am on a managed workflow.

Bug description:
To Reproduce:
ERROR Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary. ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native. ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native. Expected behavior:
Screenshots/Videos:
Environment:

OS:
OS version:
react-native version:"0.64.4"
react-native-webview version:12.0.2"

Any solution yet? I am using the expo managed workflow.

I have resolved it downgrade to v11.23.1

Thank You for your kind sharing it worked for me too !!
I got this error when i use recent version
Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.
and also another error when i use the other version too !! Thank you so much it works well for me when i install this version of 11.23.1

Ok same error here (on Android) with this versions :

react-native : 0.63.5
react-native-webview : 13.5.1

As @Elf2707 said this is an autolinking issue:
The docs indicates that autolinking is drived by react-native config and react-native config | jq '.dependencies."react-native-webview.android"' returns null.
In my case, react-native v0.63.5 depends on @react-native-community/cli-platform-android v^4.10.0 and in this version the code looking at react native packages only checks for classes implementing ReactPackage but the RNCWebViewPackage only extends TurboReactPackage.
To solve the issue I saw two solutions :

patching @react-native-community/cli-platform-android
patching/fixing react-native-webview to declare the missing implementation.

I've tried solution 1, picking the code which came with this commit:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 369958d..c2ff594 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -56,7 +56,18 @@ function getPackageClassName(folder) {
 }

 function matchClassName(file) {
-  return file.match(/class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/);
+  const nativeModuleMatch = file.match(
+    /class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/,
+  );
+  // We first check for implementation of ReactPackage to find native
+  // modules and then for subclasses of TurboReactPackage to find turbo modules.
+  if (nativeModuleMatch) {
+    return nativeModuleMatch;
+  } else {
+    return file.match(
+      /class\s+(\w+[^(\s]*)[\s\w():]*(\s+extends\s+|:)[\s\w():,]*[^{]*TurboReactPackage/,
+    );
+  }
 }

 //# sourceMappingURL=findPackageClassName.js.map

But once autolinking was fixed, I got errors at the react-native-webview level so I decided to fix everything with only one patch of this lib.
The error were (as #3131) :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt: (337, 27): Type mismatch: inferred type is String? but String was expected

And as mentioned by @bthiruven :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java:29: error: lambda expressions are not supported in -source 7
        return () -> {
                  ^
  (use -source 8 or higher to enable lambda expressions)

I fixed the first one by adding a check and the second one by declaring compatibility with Java 1.8.
Here is the final patch that got everything right :
diff --git a/node_modules/react-native-webview/android/build.gradle b/node_modules/react-native-webview/android/build.gradle
index 3e0dcbc..9f70621 100644
--- a/node_modules/react-native-webview/android/build.gradle
+++ b/node_modules/react-native-webview/android/build.gradle
@@ -52,6 +52,11 @@ android {
         buildConfigField "boolean", "IS_NEW_ARCHITECTURE_ENABLED", isNewArchitectureEnabled().toString()
     }

+    compileOptions {
+        sourceCompatibility JavaVersion.VERSION_1_8
+        targetCompatibility JavaVersion.VERSION_1_8
+    }
+
     sourceSets {
         main {
             if (isNewArchitectureEnabled()) {
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
index e961d92..9a9fade 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
@@ -334,7 +334,7 @@ class RNCWebViewManagerImpl {
             throw RuntimeException("Arguments for loading an url are null!")
           }
           webView.progressChangedFilter.setWaitingForCommandLoadUrl(false)
-          webView.loadUrl(args.getString(0))
+          args.getString(0)?.let { webView.loadUrl(it) }
         }
         "requestFocus" -> webView.requestFocus()
         "clearFormData" -> webView.clearFormData()
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
index 24e55ed..41af263 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
@@ -2,6 +2,7 @@ package com.reactnativecommunity.webview;

 import androidx.annotation.Nullable;

+import com.facebook.react.ReactPackage;
 import com.facebook.react.TurboReactPackage;
 import com.facebook.react.bridge.NativeModule;
 import com.facebook.react.bridge.ReactApplicationContext;
@@ -14,7 +15,7 @@ import java.util.HashMap;
 import java.util.List;
 import java.util.Map;

-public class RNCWebViewPackage extends TurboReactPackage {
+public class RNCWebViewPackage extends TurboReactPackage implements ReactPackage {

     @Override
     public List<ViewManager> createViewManagers(ReactApplicationContext reactContext) {

The commit fixing @react-native-community/cli-platform-android has been released with version 6.3.1, which is the version that goes with react-native versions greater than 0.64.0 (if we trust the README) so theoretically people using more up-to-date react-native versions should not have this bug (but there are people which commented with a 0.71.1 🤔).
So we may change the project declared compatibility or I can also turn my patch into a pull request.

@Wilmela
Sorry was away for the last few days.. To answer your question, mine was bare workflow. But since yours is a expo workflow, my suggestion would be Pls try to create a wrapper for react-native-webview in private repositories with patch-packages applied using this - https://docs.expo.dev/build-reference/private-npm-packages/  and use the private repo in your main repositories as one of the dependencies in package.json and see it works.

@Wilmela
Sorry was away for the last few days.. To answer your question, mine was bare workflow. But since yours is a expo workflow, my suggestion would be Pls try to create a wrapper for react-native-webview in a private repositorie with patch-packages applied using this - https://docs.expo.dev/build-reference/private-npm-packages/  or https://www.sitepen.com/blog/going-private-node-registry-with-eas and use the private repo in your main repositories as one of the dependencies in package.json and see it works.

Thanks for your response, I will go through your links.

Does anybody have a solution to this, experiencing the same issue on android?

I have resolved it downgrade to v11.23.1

how do that ? downgrade to v11.23.1

Manually linking react-native-webview fixed the issue in android
 android/app/build.gradle
 android/app/src/main/java/earth/wallet/app/MainApplication.java
 android/settings.gradle

This is the only method that works for me, on the latest version<EMAIL_ADDRESS>RN version 0.63.4
THANKS!

Ok same error here (on Android) with this versions :

react-native : 0.63.5
react-native-webview : 13.5.1

As @Elf2707 said this is an autolinking issue: The docs indicates that autolinking is drived by react-native config and react-native config | jq '.dependencies."react-native-webview.android"' returns null.
In my case, react-native v0.63.5 depends on @react-native-community/cli-platform-android v^4.10.0 and in this version the code looking at react native packages only checks for classes implementing ReactPackage but the RNCWebViewPackage only extends TurboReactPackage.
To solve the issue I saw two solutions :

patching @react-native-community/cli-platform-android
patching/fixing react-native-webview to declare the missing implementation.

I've tried solution 1, picking the code which came with this commit:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 369958d..c2ff594 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -56,7 +56,18 @@ function getPackageClassName(folder) {
 }

 function matchClassName(file) {
-  return file.match(/class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/);
+  const nativeModuleMatch = file.match(
+    /class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/,
+  );
+  // We first check for implementation of ReactPackage to find native
+  // modules and then for subclasses of TurboReactPackage to find turbo modules.
+  if (nativeModuleMatch) {
+    return nativeModuleMatch;
+  } else {
+    return file.match(
+      /class\s+(\w+[^(\s]*)[\s\w():]*(\s+extends\s+|:)[\s\w():,]*[^{]*TurboReactPackage/,
+    );
+  }
 }

 //# sourceMappingURL=findPackageClassName.js.map

But once autolinking was fixed, I got errors at the react-native-webview level so I decided to fix everything with only one patch of this lib.
The error were (as #3131) :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt: (337, 27): Type mismatch: inferred type is String? but String was expected

And as mentioned by @bthiruven :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java:29: error: lambda expressions are not supported in -source 7
        return () -> {
                  ^
  (use -source 8 or higher to enable lambda expressions)

I fixed the first one by adding a check and the second one by declaring compatibility with Java 1.8.
Here is the final patch that got everything right :
diff --git a/node_modules/react-native-webview/android/build.gradle b/node_modules/react-native-webview/android/build.gradle
index 3e0dcbc..9f70621 100644
--- a/node_modules/react-native-webview/android/build.gradle
+++ b/node_modules/react-native-webview/android/build.gradle
@@ -52,6 +52,11 @@ android {
         buildConfigField "boolean", "IS_NEW_ARCHITECTURE_ENABLED", isNewArchitectureEnabled().toString()
     }

+    compileOptions {
+        sourceCompatibility JavaVersion.VERSION_1_8
+        targetCompatibility JavaVersion.VERSION_1_8
+    }
+
     sourceSets {
         main {
             if (isNewArchitectureEnabled()) {
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
index e961d92..9a9fade 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
@@ -334,7 +334,7 @@ class RNCWebViewManagerImpl {
             throw RuntimeException("Arguments for loading an url are null!")
           }
           webView.progressChangedFilter.setWaitingForCommandLoadUrl(false)
-          webView.loadUrl(args.getString(0))
+          args.getString(0)?.let { webView.loadUrl(it) }
         }
         "requestFocus" -> webView.requestFocus()
         "clearFormData" -> webView.clearFormData()
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
index 24e55ed..41af263 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
@@ -2,6 +2,7 @@ package com.reactnativecommunity.webview;

 import androidx.annotation.Nullable;

+import com.facebook.react.ReactPackage;
 import com.facebook.react.TurboReactPackage;
 import com.facebook.react.bridge.NativeModule;
 import com.facebook.react.bridge.ReactApplicationContext;
@@ -14,7 +15,7 @@ import java.util.HashMap;
 import java.util.List;
 import java.util.Map;

-public class RNCWebViewPackage extends TurboReactPackage {
+public class RNCWebViewPackage extends TurboReactPackage implements ReactPackage {

     @Override
     public List<ViewManager> createViewManagers(ReactApplicationContext reactContext) {

The commit fixing @react-native-community/cli-platform-android has been released with version 6.3.1, which is the version that goes with react-native versions greater than 0.64.0 (if we trust the README) so theoretically people using more up-to-date react-native versions should not have this bug (but there are people which commented with a 0.71.1 🤔).
So we may change the project declared compatibility or I can also turn my patch into a pull request.

work for me, thank you

Hey,
I use React Native in Expo. When running in development build mode it does not work, but when I use expo go it starts working. So rebuild my likely outdated dev build with 'eas build --profile development --platform android' or you can do it locally and then the new build will work again. Hope that helps

Ok same error here (on Android) with this versions :

react-native : 0.63.5
react-native-webview : 13.5.1

As @Elf2707 said this is an autolinking issue: The docs indicates that autolinking is drived by react-native config and react-native config | jq '.dependencies."react-native-webview.android"' returns null.
In my case, react-native v0.63.5 depends on @react-native-community/cli-platform-android v^4.10.0 and in this version the code looking at react native packages only checks for classes implementing ReactPackage but the RNCWebViewPackage only extends TurboReactPackage.
To solve the issue I saw two solutions :

patching @react-native-community/cli-platform-android
patching/fixing react-native-webview to declare the missing implementation.

I've tried solution 1, picking the code which came with this commit:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 369958d..c2ff594 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -56,7 +56,18 @@ function getPackageClassName(folder) {
 }

 function matchClassName(file) {
-  return file.match(/class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/);
+  const nativeModuleMatch = file.match(
+    /class\s+(\w+[^(\s]*)[\s\w():]*(\s+implements\s+|:)[\s\w():,]*[^{]*ReactPackage/,
+  );
+  // We first check for implementation of ReactPackage to find native
+  // modules and then for subclasses of TurboReactPackage to find turbo modules.
+  if (nativeModuleMatch) {
+    return nativeModuleMatch;
+  } else {
+    return file.match(
+      /class\s+(\w+[^(\s]*)[\s\w():]*(\s+extends\s+|:)[\s\w():,]*[^{]*TurboReactPackage/,
+    );
+  }
 }

 //# sourceMappingURL=findPackageClassName.js.map

But once autolinking was fixed, I got errors at the react-native-webview level so I decided to fix everything with only one patch of this lib.
The error were (as #3131) :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt: (337, 27): Type mismatch: inferred type is String? but String was expected

And as mentioned by @bthiruven :
node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java:29: error: lambda expressions are not supported in -source 7
        return () -> {
                  ^
  (use -source 8 or higher to enable lambda expressions)

I fixed the first one by adding a check and the second one by declaring compatibility with Java 1.8.
Here is the final patch that got everything right :
diff --git a/node_modules/react-native-webview/android/build.gradle b/node_modules/react-native-webview/android/build.gradle
index 3e0dcbc..9f70621 100644
--- a/node_modules/react-native-webview/android/build.gradle
+++ b/node_modules/react-native-webview/android/build.gradle
@@ -52,6 +52,11 @@ android {
         buildConfigField "boolean", "IS_NEW_ARCHITECTURE_ENABLED", isNewArchitectureEnabled().toString()
     }

+    compileOptions {
+        sourceCompatibility JavaVersion.VERSION_1_8
+        targetCompatibility JavaVersion.VERSION_1_8
+    }
+
     sourceSets {
         main {
             if (isNewArchitectureEnabled()) {
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
index e961d92..9a9fade 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManagerImpl.kt
@@ -334,7 +334,7 @@ class RNCWebViewManagerImpl {
             throw RuntimeException("Arguments for loading an url are null!")
           }
           webView.progressChangedFilter.setWaitingForCommandLoadUrl(false)
-          webView.loadUrl(args.getString(0))
+          args.getString(0)?.let { webView.loadUrl(it) }
         }
         "requestFocus" -> webView.requestFocus()
         "clearFormData" -> webView.clearFormData()
diff --git a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
index 24e55ed..41af263 100644
--- a/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
+++ b/node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewPackage.java
@@ -2,6 +2,7 @@ package com.reactnativecommunity.webview;

 import androidx.annotation.Nullable;

+import com.facebook.react.ReactPackage;
 import com.facebook.react.TurboReactPackage;
 import com.facebook.react.bridge.NativeModule;
 import com.facebook.react.bridge.ReactApplicationContext;
@@ -14,7 +15,7 @@ import java.util.HashMap;
 import java.util.List;
 import java.util.Map;

-public class RNCWebViewPackage extends TurboReactPackage {
+public class RNCWebViewPackage extends TurboReactPackage implements ReactPackage {

     @Override
     public List<ViewManager> createViewManagers(ReactApplicationContext reactContext) {

The commit fixing @react-native-community/cli-platform-android has been released with version 6.3.1, which is the version that goes with react-native versions greater than 0.64.0 (if we trust the README) so theoretically people using more up-to-date react-native versions should not have this bug (but there are people which commented with a 0.71.1 🤔).
So we may change the project declared compatibility or I can also turn my patch into a pull request.

life saver, thanks

I have resolved it downgrade to v11.23.1

it work for me

I installed react-native-webview in the root directory, and then installed react-native-webview in the mobile folder, and this error showed up
"react": "18.2.0",
"react-native": "0.72.5",
"react-native-webview": "^13.6.3"

Use these two steps
1- change
import WebView from 'react-native-webview'; to import {WebView} from 'react-native-webview';
2- add
jest.mock('react-native-webview', () => {
  const {View} = require('react-native');
  return {
    WebView: () => View,
  };
});

Same issue here when running my tests:
"react": "18.2.0",
"react-native": "0.71.11",
"jest": "^29.2.1",
"react-native-webview": "^13.2.2",

Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNCWebView' could not be found. Verify that a module by this name is registered in the native binary.

@SofianeToumert
did you found the solution?
I face the same issue when running my test

Manually linking react-native-webview fixed the issue in android
 android/app/build.gradle
 android/app/src/main/java/earth/wallet/app/MainApplication.java
 android/settings.gradle

This worked for me on Android

If you are having this problem, just update you expo. Usually an error appers when runnig your expo, like:

@gilluminate Still getting this error on the latest release 13.6.4 with expo@50 and<EMAIL_ADDRESS>Thanks @ItaloVCosta ! Downgrading to 11.26.0 seems to fix it, idk why.

@anudit version 12.0.0 of react-native-webview introduced the changes for the support of Fabric & new archi, this is why you're getting the error only after this version!
TurboModuleRegistry is part of RN New Archi, and was simply not called before 🙂

@delphinebugner Ah thanks! I tried with the new architecture turned on and off, the build with the latest failed either way.

I have the same setup as you - react-native-webview 13.6.4 &  RN 0.73.2, with old archi, and the build works fine on Android 👌 classic question, but have you cleaned your gradle cache after doing the upgrade?
I only had the error in the tests, and a simple mock of the Native Module fixed it:
// in __mocks__/react-native-webview.ts
import { NativeModules } from 'react-native';

NativeModules.RNCWebView = {};

module.exports = require('react-native-webview');

@delphinebugner It's the expo development build that errored out with the gradle cache cleaned.

I am using the Expo online and getting this error. Is there any fix available for that?

If you are using expo, plz eas build to resolve this issue

hi guys, this worked to me, all the other solutions hasn't :
Put this mock inside the jest.setup.js I hope this helps.
"react-native-webview": "^13.2.3",
"react-native": "0.70.6",
jest.mock('react-native-webview', () => {
	const React = require('react');
	const { View } = require('react-native');

	const WebView = props => <View {...props} />;

	return {
		WebView,
		default: WebView,
		__esModule: true,
	};
});

hi guys, this worked to me, all the other solutions hasn't :
Put this mock inside the jest.setup.js I hope this helps.
"react-native-webview": "^13.2.3", "react-native": "0.70.6",
jest.mock('react-native-webview', () => {
	const React = require('react');
	const { View } = require('react-native');

	const WebView = props => <View {...props} />;

	return {
		WebView,
		default: WebView,
		__esModule: true,
	};
});

This worked for me as well! Thank!

If you develop with expo, be sure to rebuild.

Worked perfectly ! Thanks @gilluminate

If you are like me, and running your build from CLI instead of XCode directly, you can solve this by running the build once from XCode which seems to be needed to automatically link up the new Pods after updating to this newer version. Hope that helps someone.

This is your answer here!! React native just loves bugs

This solved for me.
jest.mock('react-native-webview', () => {
  const MockWebView = jest.requireActual('react-native').View;

  return {
    __esModule: true,
    WebView: MockWebView,
    default: MockWebView,
  };
});

Only getting the error when running the test.
This solved the issue for me: https://github.com/react-native-webview/react-native-webview/issues/2959#issuecomment-1900067275

I use expo and no solution works for me:
"dependencies": {
"@expo/vector-icons": "^14.0.2",
"@react-navigation/native": "^6.0.2",
"axios": "0.27",
"expo": "~51.0.22",
"expo-av": "^14.0.6",
"expo-constants": "~16.0.2",
"expo-font": "~12.0.9",
"expo-linking": "~6.3.1",
"expo-network": "~6.0.1",
"expo-router": "~3.5.18",
"expo-splash-screen": "~0.27.5",
"expo-status-bar": "~1.12.1",
"expo-system-ui": "~3.0.7",
"expo-web-browser": "~13.0.3",
"git-filter-repo": "^0.0.30",
"nativewind": "^2.0.11",
"react": "^18.2.0",
"react-dom": "18.2.0",
"react-native": "0.74.3",
"react-native-gesture-handler": "~2.16.1",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.5",
"react-native-screens": "3.31.1",
"react-native-web": "~0.19.10",
"react-native-webview": "^13.10.5",
"react-native-youtube-iframe": "^2.3.0"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@types/jest": "^29.5.12",
"@types/react": "~18.2.45",
"@types/react-test-renderer": "^18.0.7",
"eslint": "^8.57.0",
"eslint-config-expo": "^7.0.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-prettier": "^5.1.3",
"jest": "^29.2.1",
"jest-expo": "~51.0.3",
"metro": "^0.80.9",
"metro-config": "^0.80.9",
"prettier": "^3.3.2",
"react-test-renderer": "18.2.0",
"tailwindcss": "3.3.2",
"typescript": "~5.3.3"
},

I have the same issue.

Heading banging and issue persisting.
Tried downgrading to react-native-webview 11 and 12. Rebuilding dev. Still getting same TurboModuleRegistry.getEnforcing error.
"@expo/vector-icons": "^14.0.2",
"@react-navigation/native": "^6.0.2",
"expo": "~51.0.24",
"expo-constants": "~16.0.2",
"expo-font": "~12.0.9",
"expo-linking": "~6.3.1",
"expo-router": "~3.5.20",
"expo-splash-screen": "~0.27.5",
"expo-status-bar": "~1.12.1",
"expo-system-ui": "~3.0.7",
"expo-web-browser": "~13.0.3",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.74.3",
"react-native-gesture-handler": "~2.16.1",
"react-native-reanimated": "~3.10.1",
"react-native-safe-area-context": "4.10.5",
"react-native-screens": "3.31.1",
"react-native-web": "~0.19.10",
"expo-dev-client": "~4.0.21",
"react-native-webview": "13.6.3"

This issue should not be closed and still persists.

same

same

same

this issue still persists

I am also having this issue.

Same here. This for sure is still an issue

Will this mean I'll have to generative native modules because of the
prebuild command?

Message ID:
@.***
com>

I had to delete the app from the simulator, even after running npx expo prebuild --clean, but then it resolved


Implement multiprocessing next to multithreading

Hi @tblanke
Currently, ScenarioGUI allows for running the calculation of multiple scenario's in different threads. However, python does not (really) support multi-core multithreading. I guess the time saved for GHEtool running the GUI in multithreading, is rather small, since our running time is CPU bound (especially pygfunction) and not I/O bound, where multithreading shines.
Perhaps it can be usefull to implement multiprocessing instead (or next to) multithreading also?
I found some useful background information in this article: https://towardsdatascience.com/multithreading-multiprocessing-python-180d0975ab29
And also in this article: https://towardsdatascience.com/demystifying-python-multiprocessing-and-multithreading-9b62f9875a27
But in the end, I think the choise of multithreading/multiprocessing should be a choise the developer makes when creating a GUI and not the user that uses the GUI (and does not know what the difference between those two is). Therefore, perhaps it is good to remove the 'number of threads' option from the settings page and set them as a variable somewhere when developing the GUI.
What do you think?
Did you run some tests already to measure the speed improvements of multithreading?
Best,
@wouterpeere

Hi @wouterpeere ,
I have implemented an apporach to use Multiprocessing. I would like to stay with the number od threads as a variable so the user can decide how many processes should run in parallel.
With best regards
@tblanke

Hi @wouterpeere
Can you please take a look at the multiprocessing approach in the pull request?
If you are fine with it as well I will merge it.
With best regards
@tblanke

Hi @tblanke
I think this is fine. I will have to see it within GHEtool to see if it really makes that much of a difference.
No buggy behaviour noticed so far! (Except for example #97 )
Best regards,
@wouterpeere


Fixed undefined classes in GuidStringCodecTest properties

I found out these two phpDocs pointed to undefined classes. I added them as use statements.
BTW: I found this issue using my new static analysis tool PHPStan. I can send you a PR with integrating the tool in the package's build script if you're interested :)

Coverage increased (+0.2%) to 96.51% when pulling aa869f93ffc27f83545a64e5ccd16cb1c46b2cd9 on ondrejmirtes:fix into be0a40fec15740eba2e6ade85786cd7348def382 on ramsey:master.

Thanks!
We can't use PHPStan with this project, since we support 5.4+, and the next major version will support 5.6+.

You're welcome.
It'd still be possible to run it under the PHP 7-build only and have the build matrix fail if there was something wrong with the code (and just let the build step pass on lower versions).


REQ: Support Tagging on /zr

Should be able to supplant previous tag when rerolling. Or, increment a counter.

Implemented in v0.8


Vulnerabilities...

Hello, I am currently receiving warnings about a chain of dependencies leading to a package (nth-check) with a known high-severity vulnerability. (See attached.) What should I do? Note: npm audit fix --force does not resolve the issue.

After using 'npm audit fix --force', the number of vulnerabilities increased from 6 to 53.

In your package-lock.json, under "node_modules/react-scripts":

@baturkey there's a better way to override . With this method, you don't have to keep updating the package-lock manually. This object would be at the root of package.json
"overrides": {
    "react-scripts": {
      "@svgr/webpack": "8.1.0",
      "typescript": "5.0.2"
    }
  }

This tells it to override those dependencies with the specified versions when they're a child of react-scripts. I also had to override the typescript version for my upgrade, so I included that as well.

TIL, thanks @TShaunik !

This vulnerability has been around for about 10 months, is this project abandoned?

I feel like it is. Not a single version (not even a patch) has been released in 16 months. Looking at ejecting my React app from CRA to get free of react-scripts which is causing so many issues with my security updates.

Yeah 453 open pull requests isn't a good sign, weird though for Facebook, maybe that team got downsized?

Thank you all for your responses! I've resolved the issue following @TShaunik's 'override' approach.

In your package-lock.json under  "node_modules/react-scripts"
Update the version of "@svgr/webpack" from 5.5.0 to the latest version (8.1.0 as I write this)
https://www.npmjs.com/package/@svgr/webpack
Then run npm install

Trying to have something work directly to the script

This is still an issue. Overriding @svgr/webpack to several major versions above is not a proper solution. Why was this closed?

Does this manual override to several versions newer break anything? I guess it will, esp in projects with overrides etc. So its not a proper solution.

@ziaulrehman40  It's a solution to address the reality that they've not released anything since April 12, 2022.
We're going through an SOC 2 audit and I had 3 options:

Mark it as we're not going to resolve a high security alert and then try to pass the audit ignoring an item that must be resolved in 30 days
Eject react-scripts and take on managing the configs for webpack, and many other plugins ourselves and not be able to re-use react-scripts to handle that if they were to ever release a new version. Difficult to do as we're a tiny team and I'm the only one who has the prior knowledge to pick up figuring all that that would entail.
Override and test to see if things are broken

If we were to fail the audit, and we wouldn't know for 3 months (the observation window), we'd lose customers so the first option was ruled out immediately. The 2nd was considered, but I couldn't afford to be derailed to tackle the consequences of ejecting react-scripts, so I had to go with the third. We have seen no issues in our app and will deal with it if we do encounter something at some point.


Legend Rendering

Version
4.9.0
Reproduction link
https://codepen.io/ggupzhh/pen/MWbWjjK
Steps to reproduce
When using SVG to render the chart, Legend mode is scroll, and legend displays exception
当使用SVG 渲染图表 ，legend 图例模式为scroll  ，legend显示异常
What is expected?
When using SVG to render the chart, Legend mode is scroll, and legend displays exception
当使用SVG 渲染图表 ，legend 图例模式为scroll  ，legend显示异常
What is actually happening?
When using SVG to render the chart, Legend mode is scroll, and legend displays exception
当使用SVG 渲染图表 ，legend 图例模式为scroll  ，legend显示异常

When using SVG to render the chart, Legend mode is scroll, and legend displays exception
当使用SVG 渲染图表 ，legend 图例模式为scroll  ，legend显示异常

Try with 5.0 version. I cannot reproduce it.

Try with 5.0 version. I cannot reproduce it.

5.0 is fine, 4.9 is not
This is the flawed demo of 4.9
https://codepen.io/ggupzhh/pen/MWbWjjK

5.0 is fine, 4.9 is not
This is the flawed demo of 4.9
https://codepen.io/ggupzhh/pen/MWbWjjK

Yes. So please upgrade to 5.0. It is not planned to be fixed in 4.x.

okk


feat: add iter related methods for bytes and buffer

Pull Request Test Coverage Report for Build 2632
Details

5 of 13 (38.46%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 79.057%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bytes/bytes.mbt
5
6
83.33%

builtin/buffer.mbt
0
7
0.0%

Files with Coverage Reduction
New Missed Lines
%

builtin/buffer.mbt
1
42.31%

Totals

Change from base Build 2630:
-0.1%

Covered Lines:
3386

Relevant Lines:
4283

💛  - Coveralls


Typescript support is lacking and also hooks return ANY (v2)

🐛 Bug Report
Typescript type support is lacking.
In webstorm it does not recognize the xstyled items, although maybe to do with the styled component plugin

also, all the hooks take in and return "any" in typescript so there is no type checking
  const primary = useColor("primary")
  const primaryx = useTh("colors.primary")
  const theme = useTheme()

To Reproduce
See above
Expected behavior
It would be nice if it was totally compatible with typescript using the type system that it offers.

It would be nice also if you could release a small repo with a test project showing off all the features of typescript as I am not seeing much right now - but maybe I am using it wrong ?
I did create a definition file as per the instructions but was unable to get the "th" method working - seems to accept ONLY strings

and also the colors in the theming

It would be nice also if you could release a small repo with a test project showing off all the features of typescript as I am not seeing much right now - but maybe I am using it wrong ?
I did create a definition file as per the instructions but was unable to get the "th" method working - seems to accept ONLY strings

and also the colors in the theming

Make sure you also have @types/styled-components installed if you are using styled-components on top of creating the definition file.

Make sure you also have @types/styled-components installed if you are using styled-components on top of creating the definition file.

Hi @iangregsondev, typing is not supported in template string because it is not possible to do without an editor plugin. th and useTh have been forgotten. If someone want to help fixing it, it is welcome!

Hi @iangregsondev, typing is not supported in template string because it is not possible to do without an editor plugin. th and useTh have been forgotten. If someone want to help fixing it, it is welcome!

Fixed in v3.


styld

We created a new package  https://github.com/cssinjs/styled-jss

@kof I have just speak with @lttb. He will add this package soon :)

Just add styled-jss


CI: ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.24.5" found.

 For Spot and PVM it defaults to ANY, and for all other VM kinds a BALANCED policy is used. To change the default values use the `--location-policy` flag.
Note: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation.
ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.[24](https://github.com/cilium/cilium/actions/runs/3944928056/jobs/6751353282#step:12:24).5" found.
Error: Process completed with exit code 1.

ERROR: (gcloud.container.clusters.create) ResponseError: code=400, message=No valid versions with the prefix "1.[24](https://github.com/cilium/cilium/actions/runs/3944928056/jobs/6751353282#step:12:24).5" found.

Is that cilium action run link in there really there or is it a mistaken paste?

Tests are failing because 3 of the conformance test has a specific k8s version of 1.24.5 which is no longer available.
1.24.5 version is set by this commit  a77007aa448 to fix temporarily failing encryption connectivity test by @joamaki
We can revert it, which means cluster will be created with the version 1.24.7 but I am not sure encryption connectivity test is fixed with newer version. If not should we disable that particular test for now? @aanm
Available regular GKE versions
Fetching server config for us-west2-a
---
channels:
  channel: REGULAR
  validVersions:
  - 1.25.4-gke.2100
  - 1.24.8-gke.2000
  - 1.24.7-gke.900
  - 1.23.14-gke.1800
  - 1.23.14-gke.401
  - 1.22.16-gke.2000
  - 1.22.16-gke.1300
  - 1.22.15-gke.2500
  - 1.22.15-gke.1000
  - 1.21.14-gke.8500
  - 1.21.14-gke.7100
  - 1.21.14-gke.5300


Enhancement: Support for new cohere chat model family

What features would you like to see added?
New models were Command-R + by cohereand I would love to see support for them in Librechat.
specification: https://docs.cohere.com/reference/chat
More details
For some reason unknown to us, cohere's requests use POST. This is unfortunate because the extension described in librechat.yaml only supports GET, resulting in an error.
LibreChat  | {
LibreChat  |   baseURL: "https://api.cohere.ai/v1",
LibreChat  |     modelOptions.model: "command-r-plus",
LibreChat  |     modelOptions.temperature: 1,
LibreChat  |     modelOptions.top_p: 1,
LibreChat  |     modelOptions.presence_penalty: 0,
LibreChat  |     modelOptions.frequency_penalty: 0,
LibreChat  |     // 3 stop(s)
LibreChat  |     modelOptions.stop: ["||>","\nUser:","<|diff_marker|>"],
LibreChat  |     modelOptions.user: "64b80765ede492ab9fccb5fc",
LibreChat  |     modelOptions.stream: true,
LibreChat  |     // 3 message(s)
LibreChat  |     modelOptions.messages: [{"role":"user","content":"test"},{"role":"assistant","content":"405 status code (no body)"},{"role":"user","content":"test"}],
LibreChat  | }
LibreChat  | 2024-04-05T06:11:45.007Z warn: [OpenAIClient.chatCompletion][stream] API error
LibreChat  | 2024-04-05T06:11:45.010Z error: [handleAbortError] AI response error; aborting request: 405 status code (no body)
LibreChat  | 2024-04-05T06:11:45.024Z debug: [AskController] Request closed

Thank you very much for all of your work!
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

from a quick glance, I don't think this is the issue

For some reason unknown to us, cohere's requests use POST. This is unfortunate because the extension described in librechat.yaml only supports GET, resulting in an error.

it is the different "chat" endpoint they are using
v1/chat instead of v1/chat/completions
I'll see if there is a quick fix for this for easy integration.


Is Leshan affected by log4j2 CVE-2021-44228 vulnerability ?

I am using leshan version 0.1.11 which is having log4j v2.1 as dependency. As you all are aware this version of log4j  is having a severe vulnerability.
Modifying the HTTP request body seems to be the usual way to exploit this. In my case the Lehan HTTP API is not exposed outside. Only the UDP interface is public. UDP encryption is also enabled.
How vulnerable is my leshan installation? Is UDP interface also at risk?
I confirm that I will not hold you responsible for any  negative impact of your answer.
Note: If this is an inappropriate or invalid question, kindly delete

You write, you use a 5 years old (pre-) release?
I'm not sure, why you worry about vulnerabilities, if you missed 5 years to update leshan.
Leshan 0.1.11-M14 uses Californium 2.0.0-M2, so I can only very strongly recommend, that you migrate at least to the latest bugfix-release of Leshan in order to use also the latest bugfix-release of Californium.
See Security Policy.

I am using leshan version 0.1.11 which is having log4j v2.1 as dependency. As you all are aware this version of log4j is having a severe vulnerability.

There is no 0.1.11 version, only milestones one (from 0.1.11M1 to 0.1.11M14).
0.1.11M1 was released in begin of 2015 the 0.1.11M14 end of 2016.
So you are using a development version which are very very old and you worried about security issue about log4j2.
That sounds strange to me. :thinking:
Please if you are deploying Leshan in a context which needs a good level of security,  use the last stable version... currently leshan-1.3.1 (and update to the last one regularly).
You should also use the last 2.6.x version of californium. Currently there is no recent version of Leshan with last 2.6.x version but as no API break is expected, you should be able to use the last 2.6.x. About this last point, I currently don't know if I should do Leshan release just to bump this kind of version (without any leshan code changes) ...

In my case the Lehan HTTP API is not exposed outside.

If you are talking about HTTP API, I guess you also use Leshan demo which is not intended to be used in production ...

How vulnerable is my leshan installation?

About the log4j2 issue I don't know if your installation is exposed. This is not really a Leshan question because :
The only part which is intended to be reused is the Leshan library (not the demo)
The Leshan library just depends of slf4j facade.
This is up to the user to chose the slf4j back-end and version.
So you should be able to update to a more recent version of log4j2 or to switch to a recent logback.

Is UDP interface also at risk?

As I said about log4j2 issue I don't know but for reasons exposed above :

using an unmaintained, old, not stable, development version ...
reusing demo code (not production ready) in production.

I guess we can consider that your installation is risky.

Note: If this is an inappropriate or invalid question, kindly delete

Do not delete it, maybe this will help other users.

Thanks everyone for the  replies. Please note that my application is  reaching end-of-life and there is no plan/motivation to do an upgrade. My idea is to keep the application secure for the remaining few months.
I could see the following warning when I build leshan:
        [WARNING] Unused declared dependencies found:
        [WARNING]    org.apache.logging.log4j:log4j-core:jar:2.1:runtime
        [WARNING]    org.apache.logging.log4j:log4j-slf4j-impl:jar:2.1:runtime

Does it mean that log4j is not used ? Or is it just how slf4j-facade works?

My idea is to keep the application secure for the remaining few months.

My point is that there is probably several other known vulnerabilities (not linked to log4j2)  in your version.

Does it mean that log4j is not used ? Or is it just how slf4j-facade works?

I'm not able to answer without more context.
But again Leshan library is not dependent to log4j2.
So you are the only one who is able to know if you are using log4j2 as backend or something else...
If you are using it and you are worried about that point, just upgrade the version or change to another slf4j backend.

What I did for some Californium demos was to check the "with-all-dependencies.jar" if they contain  org.apache.logging.log4j. I'm not sure, but if I remember well, there is also such a jar for the leshan demo server. so check the jar you're using, if that contains org.apache.logging.log4j at all.

I built a leshan-server-demo-0.1.11-M14-jar-with-dependencies.jar and unfortunately, it contains org.apache.logging.log4j. Which version and If these classes are really used, I don't know.

Thanks Achim. I could verify from mvn dependency tree that the  version of log4j is 2.1. The fix I am going to use is to  open the jar file and remove "JndiLookup.class".

Just a sumarize for others :
Is Leshan affected by log4j2 CVE-2021-44228 vulnerability ?
Leshan Library:

:heavy_check_mark: Not affected, this is only part which is intended to be used in production and it just depends on slf4j facade.   So up to users to check which slf4j backend they are using.

Leshan Demos:  (note that demos should not be used in production).

:heavy_check_mark: Not affected since 1.0.0-M5 (January 2018),  since this milestones, logback is used as backend for demo.
:warning: Affected until 1.0.0-M4 (September 2017),  log4j v2.1 or lower are used by server and bsserver demo.

General security recommendation :

Do not use old milestones or unstable version, rather use last stable (1.x) version or 2.0.0 milestones.  (See Security)
Do not use demos in production.

You could also be interested by californium information about that : https://github.com/eclipse/californium/issues/1848

I think we can close this one.
(There is a eclipse page for all eclipse project about this :https://wiki.eclipse.org/Eclipse_and_log4j2_vulnerability_(CVE-2021-44228))


ReactiveCosmosTemplate SQL Injection Risk?

In the implementation of findById, String.format to build the query, https://github.com/Azure/azure-sdk-for-java/blob/3c5afa97be1619d39b0924c2d9c7e030d221b194/sdk/cosmos/azure-spring-data-cosmos/src/main/java/com/azure/spring/data/cosmos/core/ReactiveCosmosTemplate.java#L274 A parameterized query could be used instead to reduce the risk.

@ihcnet - thanks for creating this issue, I have fixed it in the PR.


[feature] add storm monitor

What's changed?

#992
Added Storm monitoring. Obtaining cluster summary information via HTTP request.

Checklist

[x]  I hereby agree to the terms of the HertzBeat CLA
[ ]  I have read the Contributing Guide
[ ]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

👍👍 LGTM！ We can also add authentication configuration(username password or token) later to support access to the securely protected strom api.

Sure, I'll take some time to look into it when I'm free.


JDBC live connection timeout

About You:
Name: Venkata
Company: PayPal Inc.
Your question:
When we are creating live connection to database using jdbc sdk connector, if the database is busy and the query is running for longer than 10 minutes, jdbc connector is throwing an error that "Deadline exceeded". Screenshot attached. Is there any timeout setting that we can increase to 30 minutes on JDBC connector or on tableau server. I believe this error is coming from JDBC connector as we see this error even on desktop. Attaching the desktop logs as well.
jdbcerror.txt

@saugatt @sidwray can anyone help on this? why would connector kill the query if it does not receive response from database after 10 mins

tfs 1197773

hi
with odbc connector we dont see this issue. so we are moving with odbc connector. closing this case

This says it was taking 10 minutes in com.teradata.jdbc.TeraDatabaseMetaData.getColumns(), not running a regular query, that's an unacceptable amount of time to get metadata, from a user experience.


ENH: optional ':' separator in ISO8601 strings

[X] closes #10041
[X] tests added / passed
[X] passes git diff upstream/master | flake8 --diff
[x] whatsnew entry

Includes some refactoring in the ISO8601 parser. If more tests are desired, please let me know where to put them. Same for the whatsnew entry. This is effectively my first pull request for Pandas.
cc @jreback

cc @chris-b1 can you have a look

Looks good as far as I can tell.  The partial time formats are a bit out there, but unambiguous, so I don't see any harm.
In [24]: pd.Timestamp('2015/01/01 1234')
Out[24]: Timestamp('2015-01-01 12:34:00')

can you rebase and push again

thanks @thejohnfreeman !

Thanks for the help!

I normally test on windows before merging....but alas
.................................................S.......S.........................................................................................
...................................................
======================================================================
ERROR: test_parsers_iso8601 (pandas.tseries.tests.test_tslib.TestDatetimeParsingWrappers)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\conda\Documents\pandas3.5\pandas\tseries\tests\test_tslib.py", line 736, in test_parsers_iso8601
    raise Exception(date_str)
Exception: 2005-0101

======================================================================
FAIL: test_nanosecond_string_parsing (pandas.tseries.tests.test_tslib.TestTimestampNsOperations)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Users\conda\Documents\pandas3.5\pandas\tseries\tests\test_tslib.py", line 902, in test_nanosecond_string_parsing
    self.assertEqual(ts.value, expected_value)
AssertionError:<PHONE_NUMBER>123456000 !=<PHONE_NUMBER>123456789

----------------------------------------------------------------------
Ran 9204 tests in 304.769s

FAILED (SKIP=174, errors=1, failures=1)

so if you have the ability to debug on windows, pls have a look :<

Just at a glance, the errors make it seem like my changes to the C code weren't built. I didn't have any platform-specific preprocessor guards in the C, so I would expect it to behave the same on each platform. What are the sources of differences between Windows and Linux behavior? Are the numpy and Python datetime types different on each platform? Are there platform-specific tests?

hmm, I just tested this again on windows and its ok. Why don't you rebase and push again.

ok, maybe something funny happened in the build.
thanks again!


Remove/Fix empty link

The last link (login) in the footer navigation has no text content. It's focusable with the keyboard (at least in Firefox) and might be focusable by some screen readers as well.

Yep that's a recent bug that should be fixed.


floating point exception in tf.nn.avg_pool3d and tf.nn.max_pool3dwhen ksize=0

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below):2.1.0
Python version:3.7.6
Bazel version (if compiling from source):N/A
GCC/Compiler version (if compiling from source):N/A
CUDA/cuDNN version:N/A
GPU model and memory:N/A

Describe the current behavior
floating point exception in tf.nn.avg_pool3d and tf.nn.max_pool3d when ksize=0
Describe the expected behavior
expect no crash
Standalone code to reproduce the issue
The code crashes in nightly version too. Check out the gist
tf.nn.avg_pool3d(input=tf.ones((1,1,1,1,1)), strides=1, ksize=0, padding='VALID')

tf.nn.max_pool3d(input=tf.ones((1,1,1,1,1)), strides=1, ksize=0, padding='VALID')

Output:
Floating point exception (core dumped)

@ravikyram I have created a pull request to solve this issue , which will help raise FloatingPoitnError  when ksize = 0

I have tried in colab with TF version 2.4, nightly version(2.5.0-dev20210201) and was able to reproduce the issue.Please, find the gist here. Thanks!


Change secrets API

Changes

Removes old way of getting secrets from the connection
Adds new command API, getPassword, which requests access from the user before allowing the extension to use the password. Alternatively, the user can deny an extension the password.

Checklist

[x] have tested my change
[ ] updated relevant documentation
[ ] Remove any/all console.logs I added
[ ] eslint is not complaining
[ ] have added myself to the contributors' list in CONTRIBUTING.md
[ ] for feature PRs: PR only includes one feature enhancement.

@worksofliam I added a test for good measure 😉


namespace problem with nimArray (possibly others)

nimArray is found for R execution if I define a nimbleFunction in .GlobalEnv, but not from generated conjugate samplers.  I haven't checked on nimNumeric, nimInteger, or nimMatrix.
Reproducible example 1:
Rmodel <- readBUGSmodel('birats2.bug', dir = getBUGSexampleDir('birats'), data = 'birats-data.R', inits = 'birats-inits.R')
mcmc <- buildMCMC(Rmodel)
mcmc$run(1)
##Error in samplerFunctions[[i]]$run() : could not find function "nimArray"

The error is from samplerFunctions[[4]], the conjugate Wishart sampler
Reproducible example 2:
source(system.file(file.path('tests', 'test_utils.R'), package = 'nimble'))
test_mcmc('birats', model = 'birats2.bug', inits = 'birats-inits.R',
          data = 'birats-data.R', numItsC = 1000, resampleData = TRUE)

This is the same, just demonstrating that the error appears in our test suite.  It does not seem to trigger a testing failure, so that may be why it slipped past us.
I think the simple answer will be to export(nimArray) and the others, but I'm going to assign to @danileturek to take a look too.

@perrydv I'm confused by this.
(1) on a current pull from devel branch, the NAMESPACE file includes:
export(nimArray), ..., export(nimInteger), export(nimMatrix), ..., export(nimNumeric)
(2) on a current pull and build from devel branch, both of your reproducible examples run fine (following a call to library(nimble))
Am I missing something here?   Are you talking about a different branch?

Sorry, I ended up adding the exports to devel yesterday so that other changes would work, but I forgot to update this issue.
If you want to reproduce the problem, please try master (0.5-1).
If you agree the exports are a good solution, then they’re already on devel.

On Jun 4, 2016, at 4:12 AM, Daniel Turek<EMAIL_ADDRESS>wrote:
@perrydv https://github.com/perrydv I'm confused by this.
(1) on a current pull from devel branch, the NAMESPACE file includes:
export(nimArray), ..., export(nimInteger), export(nimMatrix), ..., export(nimNumeric)
(2) on a current pull and build from devel branch, both of your reproducible examples run fine (following a call to library(nimble))
Am I missing something here? Are you talking about a different branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/nimble-dev/nimble/issues/170#issuecomment-223750149, or mute the thread https://github.com/notifications/unsubscribe/AHpCMaeXirz_SDk7g3oOeBjqMgh7_CTiks5qIV2hgaJpZM4It1Vz.

NAMESPACE is overwritten when going through the roxygen process, so I've added  these exports to CreatingExportList.R.


ShowTcg1EventLogs () while advancement is off by 1

TCG_PCR_EVENT contains 1 byte of Event data. Event size is the total amount of event data, and the advance statement does not take this into account.
Event = (TCG_PCR_EVENT *)((UINT8 *)(Event + 1) + Event->EventSize);
should be
Event = (TCG_PCR_EVENT *)((UINT8 *)(Event + 1) + Event->EventSize - 1);

@apop2 Sorry I missed this for a while. I will fix it. Thanks for reporting the issue.


[General workload issue]: Query is throttled API limitation

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
Question
Description
Hello all,
I hope you are doing well today,
I'm currently using the EPAC module to manage ALZ and AMBA alerting policys and i'm here to ask a question concerning AMBA interval alerting
I've few errors likes a ResourceHealth alerts, I regularly receive an error message {"title":"### Query is throttled",""}
I can see that most alerts have a PT5M interval, this causes an API limitation problem ->

Do you have an idea or a other time interval i can use for all alerts or maybe i can replace the custom log search deploy by policy by my own metrics alerts so that api can rest correctly.
i'm currently working with this policy assignment ->

Thanks a lot,

Maybe something like this:
let allResources = arg("").resources;
let policyThresholdString = "10000000";
let excludedResources = allResources
| where type =~ "Microsoft.Compute/virtualMachines"
| project _ResourceId = id, tags
| where parse_json(tostring(tags.AmbaDisable)) in~ ("true");
let excludedVMSSNodes = allResources
| where type =~ "Microsoft.Compute/virtualMachines"
| extend isVMSS = isnotempty(properties.virtualMachineScaleSet)
| where isVMSS
| project id, name;
let overridenResource = allResources
| where type =~ "Microsoft.Compute/virtualMachines"
| project _ResourceId = tolower(id), tags
| where tags contains "amba-WriteBytesPerSecond-Data-threshold-override";

Hello @8ast1en ,
thanks for your feedback. We recognized the need for query optimization and have added this request to our backlog for January 2025. Unfortunately, there no way to implement staggering as documented at Staggering queries since we are using API and policy ARM templates we cannot use C# code in AMBA.
Thanks,
Bruno.


Adding SSL certificates or disabling SSL for HTTPS clients?

Is there a way to add SSL certificates to the yaks image or disabling SSL when using HTTPS clients?
We are getting the following error when calling an HTTPS endpoint from the yaks base image.
I/O error on GET request for "URL": PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
This is a very basic feature when using yaks for HTTPS integration testing. It would be great if we could disable SSL verification with a configuration.

I don't think it is possible to disable the SSL verification when using the HTTPS clients as the server requests the client to use the proper certificates.
You should be able to create a K8s secret holding the certificates and volume mount that secret into the test Pod.

https://github.com/citrusframework/yaks/tree/main/examples/secrets

Regarding the yaks usage of the secrets, it appears there is a limitation on the number of secrets that can be used by yaks. If I label two secrets with the yaks.citrusframework.org/test label, only the first one gets used and loaded in the test. Is there a possibility of using more than one secret?

Yes, I have had same issue recently, too. A fix and improvement on volume mounts of secrets in YAKS is already in the making. PR is coming soon.
With that you will be able to bind multiple secrets to a test accessing the content of the secrets either via test variables or by loading files (e.g. certificates) from a secret.

See https://github.com/citrusframework/yaks/issues/504


Fix typo

Codecov Report

Merging #690 into master will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #690      +/-   ##
==========================================
- Coverage   82.95%   82.86%   -0.10%
==========================================
  Files         661      660       -1
  Lines      127902   127692     -210
==========================================
- Hits       106099   105807     -292
- Misses      21803    21885      +82

Impacted Files
Coverage Δ

pyscf/gto/basis/parse_gaussian.py
89.04% <100.00%> (ø)

pyscf/solvent/test/test_pol_embed.py
22.60% <0.00%> (-73.98%)
:arrow_down:

pyscf/solvent/__init__.py
39.58% <0.00%> (-20.84%)
:arrow_down:

pyscf/__init__.py
75.75% <0.00%> (-9.10%)
:arrow_down:

pyscf/lib/logger.py
88.49% <0.00%> (-0.89%)
:arrow_down:

pyscf/solvent/pol_embed.py

pyscf/pbc/cc/eom_kccsd_ghf.py
93.82% <0.00%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2afa717...6b366df. Read the comment docs.


Add books

Thank you for your contribution! Cheers!

You're welcome. I'm glad to hear that to contribute your awesome repository. Cheers!


Add vanilla js SDK example

A bare bones vanillajs example using the SDK

Here the idea @RolandoDrRobot is to have a pure JS approach, and it should be with 1+ version, would that be ok @RolandoDrRobot?


Herostratus doesn't elevate on first run on OS X

The first time you open the app (whether from the source or from a package), the elevation dialog is shown, but afterwards the elevated app never runs.
Repeating the process makes it run successfully.
The issue is only reproducible by waiting some minutes (until sudo password cache is clearer).

The issue can be reproduced easily by removing the sudo cache file that sudo-prompt creates:
sudo rm /var/db/sudo/$USER

The issue happens because sudoPrompt.exec returns as soon as the elevation dialog is shown, and given we have a timeout the kill the parent process, it gets killed before the user can fill the dialog.


Review by Lucas

Hello Abubakar! your project looks great! I don't see any error. Execellent Job!

@Oklukeok Thank you Lucas


⚠ SceneTime has degraded performance

In 8e615d2, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 10861 ms

Resolved: SceneTime performance has improved in e06223c.


No autocomplete for cv2 module installed by conda

Type: Bug

VS Code Version: 1.84.2
OS Version: MacOS Monterey 12.7.1

For some reason, VSCode does not provide Python autocompletions for the cv2 module installed through conda.
Steps to Reproduce:

Make sure opencv is installed by conda. (e.g. by running conda install -c conda-forge opencv=4.8.1.
Create a new .py file in VSCode and write import cv2.
Select the appropriate Python interpreter provided by conda
Write cv2.

This should trigger autocompletion, but the menu does not show up. This issue does not occur for other Python modules, such as numpy or matplotlib.
 Any updates on this issue?

Thank you for the issue. I was able to reproduce it, and it seems like a bug where type stubs are not included in the conda install. A similar issue is being tracked at https://github.com/conda-forge/opencv-feedstock/issues/374.

Hi was there any update on this issue?

@jomai1, I see that you also commented on the conda-forge issue mentioned above. That's the right place to ask. Pylance is behaving correctly here.


Log in

As an app user I want to login (username+password?) so that I can make authenticated requests.
The server needs to provide tokens so generic agents can to prove their identity to a Solid server.

Complete, and awaiting code review. It uses email and password.

@jaxoncreed when you say awaiting code review, do you mean https://github.com/solid/community-server/pull/455?


Updated default z-index value

Changed highest/default value for z-index. Modal by default stays on z-index:1 even though there are elements with higher z-indexes.

Sorry, my bad. Thanks.


Integrating libLTC

Hi there,
I was wondering whether you see any obstructions or challenges with integrating libLTC? Is it as simple as encoding every frame?
Best regards,
Jochem

Hello, i think webrtc does not support this


Workflow with duplicated sections

Right now
[A]
[A]

will trigger an error. However, when I show examples in the documentation or revise existing workflows, these duplicated sections will disable %sosrun even if the workflow has nothing to do with A.
It might be good to reduce this to a warning or silently use the second step.

The problem is that it can be confusing if we silence such an important error. For example, if in a long workflow some later section defines a different step, thing might go terribly wrong.

The %rerun magic was invented to alleviate this problem so that
---
%run
[A]
---
%rerun --different-option

can execute [A] without having to list the code again.  The problem is that it is unclear if %rerun refers to the last executed code, previous code cell in the notebook etc.
A %runcell magic might be good but there is no easy way to refer to previous cell... since execution count is quite dynamic in a notebook.


[Question] SQL Anywhere connect either without tables or "Login failed"

I try to connect DBeaver to a SQL Anywhere Database.
If I use SyBase jConnect it will connect just fine, but the folder "tables" (aka Tabellen in German) is empty. Also the log mentioning somthing along "no Metadata-Accessor found"
If I use SyBase then I'll get a Login failed detail message, the main error is "angegebene Datenbank nicht gefunden" (choosen database not found).
Maybe the last one is related to this: https://github.com/dbeaver/dbeaver/issues/1813 but the field to change the template is grayed out.
Also the .logfile only captures the SyBase jconnect attempt, for the SyBase one no entries are generated, a dbeaver-debug.log file is not present.
What can I do to help solve this problem ? Or at least change the template string, as this might already help.
Edit: I tried with the last 3.x version, where I could Change the template string. But this din't work either.  Meanwhile I also tried to use the 32 Bit version but also without success.
For the time being I can connect via ODBC, but if anyone has a bit of time to look into it, this would be helpful.

I can't reproduce this.
What do you want to change in connection URL? Usually you can just add some driver parameters.
Also you could create new driver.

Actually I do not want to change the URL I want to connect to the SQL Anywhere database :) I only assumed from reading issuse #1813 that this might help.
In Version 3.x I was able to change the template which did not help, so maybe my problem with the connect is something else.
But for the problem with the greyed out template field, see attached picture.

I guess my knowledge of Java is virtually non-existant so creating a new driver is much likely beyond my capabilities. As far as Dbeaver goes, I'm more a user than a developer. Nevertheless I like to help getting the thing running with SQL Anywhere, so I can get rid of the ODBC detour.

I think that problem in #1813 is not related to your issue.
Could you post .log and dbeaver-debug.log files? Most likely you can use only jConnect driver but by some reason it doesn't work. More details are needed.

.log.zip
attached please find the .log file. I guess the "0)" string Format exceptions are not related to the issue, i kept them in the file anyway.
The debug.log is nowhere to be found. Must it be enabled ? And if so, how ?

Thanks for logs.
I think this is the same issue:
https://stackoverflow.com/questions/20568827/jz0sj-metadata-accessor-information-was-not-found-on-this-database
https://sqlanywhere-forum.sap.com/questions/16254/javasqlsqlexception-jz0sj-metadata-accessor-information-was-not-found-on-this-database
You can try to execute
ALTER DATABASE Upgrade JCONNECT ON

In your Sybase server to enable jConnect support.
BTW I've also found and fixed the bug in the German translation using your logs.


proposing changes to files starting with SS* or SilverStripe*

Hi,
There are only a few Files left that are preceded with SS e.g SS_List, SSViewer, SSTemplateParser
can we change the names in V5?
Acceptance criteria

[ ] Classes and filenames prefixed with SS or Silverstripe are renamed to not be prefixed.
[ ] All references to those classes are updated to the new name  in the code and in the docs.
[ ] Changes are called out in the upgrade docs.

Notes

Note 100% sure how we will deal with translations for classes we rename.

The benefit isn't zero, but I'm not sure the benefit is greater than the cost.
Assuming that our upgrader code is used to do the rewrite the cost is minimal, although that's perhaps an oversimplification, and in any case I'd rather park this kind of thing until 5 had a clearer arrival date.

I agree with @sminnee, but I'm also a strong proponent of eventually achieving PSR-12 compliance, and we won't get there with underscores in our class names.

Didn't make it to CMS5.

how about 5.0.1?


[SMALLFIX] Revert ganglia

This PR reverts https://github.com/Alluxio/alluxio/pull/4214 which introduces a bad transitive dependency.

@calvinjia

LGTM


Issue when building with cross rustdoc

Maintainers note: The issue was filed wrongly initially, the real issue is using cross rustdoc
Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
When running
cross +nightly-2023-07-16-aarch64-unknown-linux-gnu rustdoc --target=aarch64-unknown-linux-gnu -p<EMAIL_ADDRESS>--  -Zunstable-options --output-format json

I get the following error:
[cross] warning: unable to get metadata for package
[cross] note: Falling back to `cargo` on the host.
qemu-aarch64: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory

If I use +nightly-2023-07-16 by itself, it runs successfully but it fallbacks to cargo on host and the build clearly isn't being done on arm64.
What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[ ] Windows
[X] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[X] docker
[ ] podman
[ ] other container engine (specify in description)

cross version
0.2.5
Example
No response
Additional information / notes
No response

This is a current limitation with our images, all our current images run with platform = linux/amd64, not linux/arm64. If you need arm64 host support you need to make the image yourself, see target.TARGET.image.toolchain
The tracking issue for overall aarch64 host support is https://github.com/cross-rs/cross/issues/751
In there there's also an example of how to use the feature

Hi I am not trying to run on an Arm64 host but to cross compile to Arm64 from x86

Aha, I see!
The toolchain you picked is not valid, it should be cross +nightly-2023-07-16-x86_64-unknown-linux-gnu ...
in never versions of cross you'll get an error message
Note:
   Overriding the toolchain in cross is only possible in CLI by specifying a channel and optional date: `+channel[-YYYY-MM-DD]`.
   To override the toolchain mounted in the image, set `target.aarch64-unknown-linux-gnu.image.toolchain = "aarch64-unknown-linux-gnu"`

Suggestion: try `cross +1.65` instead

however, I just noticed that you're trying to use rustdoc! We don't support rustdoc as a command, not sure why though.
For now, use cross doc and set env var RUSTDOCFLAGS

I think I'll explain a bit more so that it's totally clear what happened here initially!
cross uses a rust toolchain, like nightly-x86_64-unknown-linux-gnu, inside a docker container by mounting that toolchain from the system hosting the container engine. To compile for a specific target like aarch64-unknown-linux-gnu, rust specifies targets (see rustup target list). These targets are used to compile, with any "host" toolchain, for a specific target triplet. All cross does is setup a cross-compilation friendly environment so that tools needed to compile for that target is available.

I've fixed the issue with rustdoc now hopefully, can you try it out with #1342
cargo install cross --git https://github.com/cross-rs/cross --branch explain-fallback-fix-rustdoc

Hey, thanks so much! Will try now

hmm, i feel like there's some information missing here, can you post the full log? I'll try this myself later this weekend, is the project you're compiling from available? I guess maybe I can reproduce it with just a cargo.toml using<EMAIL_ADDRESS>

oh also, please try a cargo clean --target aarch64-unknown-linux-gnu then run the command again, the fact that this produces a ice is interesting though

oh and also! Generally, cross or really any cross compilation tool, isn't really needed when targeting another target, are you sure it doesn't just work with cargo +nightly-2023-07-16 rustdoc --target=aarch64-unknown-linux-gnu -p<EMAIL_ADDRESS>--  -Zunstable-options --output-format json?

hmm, i feel like there's some information missing here, can you post the full log? I'll try this myself later this weekend, is the
project you're compiling from public? I guess maybe I can reproduce it with just a cargo.toml using<EMAIL_ADDRESS>Here is the full log: https://gist.github.com/makspll/c3058a54896dd3a8f78b6b654308e9bf

Yes the project is public, the issue and context I am needing this for can be found here: https://github.com/makspll/bevy_mod_scripting/pull/77

oh and also! Generally, cross or really any cross compilation tool, isn't really needed when targeting another target, are you sure it doesn't just work with cargo +nightly-2023-07-16 rustdoc --target=aarch64-unknown-linux-gnu -p<EMAIL_ADDRESS>--  -Zunstable-options --output-format json?
The reason I was using cross was because I was getting unexpected output from cargo. Turns out I didn't realise cargo would generate under a new directory in target, specifically target/aarch64-unknown-linux-gnu which caused me to use the old rustdoc json files and hence wrong output! I just assumed I needed some sort of emulation for this to work. But also I do think I need cross for running anything with a bevy dependency as it has some dependencies:

[target.aarch64-unknown-linux-gnu]
pre-build = [
    "dpkg --add-architecture arm64 && apt-get -y update; apt-get -y install libasound2-dev:arm64 libudev-dev:arm64",
]

oh also, please try a cargo clean --target aarch64-unknown-linux-gnu then run the command again, the fact that this produces a ice is interesting though

This solved it! it run the command successfully, and after correcting for the target directory everything worked as expected!
Thanks alot!

awesome, then this is the good old issue #724 but rustdoc throwing an ICE, very nice

Ah I see, strange!


Inconsistent UI in plugin config

Wanted to separate this from #641 since that's a code issue and this is a style issue:
The UI style of the slider and number input (and text input, to a lesser extent) do not match with the rest of Desmodder/Desmos. Perhaps the slider could be made to look like an actual slider? Number inputs could perhaps use the component (or a clone) from the vanilla settings (ex. viewport bounds). Text input could also use something like that, or the rounded corner version from axis labels.
From PLUGINS.md:

Descriptions (at least in English) should complete the sentence "When installed, this plugin ..."

Plugin descriptions seem to have significantly deviated from this, most having something more like "When installed, this plugin allows you to ...". This is fine, but should probably be standardised into PLUGINS.md. Notably, Compact View does not match either of these patterns.
Capitalization also seems to be inconsistent across plugin options. Most config options are Title Case, but some are Sentence case, particularly:

Calculator Settings

Advanced styling
Author features
Show points of interest
Trace along curves
Show keypad

Wakatime

Project name

Better Evaluation View

Show list elements
Show colors
Show lists of colors

Compact View

No Separating lines

A few thoughts on this:
I definitely agree about the slider and number inputs. Right now, they're just the browser defaults. It'd be cool if they looked more in line with Desmos's style, possibly even like the exppanel sliders and inline number-only MathQuills.
As for descriptions, if you ask me, the "When installed, this plugin..." at the beginning is somewhat redundant. I think it's easy enough to make the connection that a description for a plugin describes what it lets you do if you enable it.
As for options, I'm not sure on what to do there. Title Case makes some amount of sense since these aren't sentences, they're names for these options. Funny thing is, vanilla Desmos seems to have this exact same inconsistency lol. Check this out:

As for descriptions, if you ask me, the "When installed, this plugin..." at the beginning is somewhat redundant. I think it's easy enough to make the connection that a description for a plugin describes what it lets you do if you enable it.

Not saying to make the actual description start with that, just for it to be able to complete that sentence. Ex. for calculator settings, "When installed, this plugin: Lets you toggle features..." makes sense.

Ahhh, that makes more sense, my bad.


Add "displayName" option to customize accessory name(s)

e.g., “West Bay Weather” instead of “Now”

Published to npm in v2.3.0
https://www.npmjs.com/package/homebridge-weather-plus/v/2.3.0


Transparent support of JSX syntax with Babel

Latest Babel supports the /** @jsx m */ pragma. So, transpiling to working Mithril code is elegant and easy.
Upcoming version 0.2.1 don't play well when secondary argument of the m() function is null instead of Object.
Surprisingly, it works well when supplying children elements with subsequent arguments instead of Array - I've found no docs describing the feature, so it could be undocumented or upcoming.
So, as modifying Babel to support Mithril is unlikely task, could we hope Mithril's m() function to play well with null secondary argument?

+1

I will post a PR. 5 lines in m().
On Thu, Aug 20, 2015 at 8:03 AM Asaf Yishai<EMAIL_ADDRESS>wrote:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/lhorie/mithril.js/issues/768#issuecomment-132892474.

Hope this helps: https://github.com/lhorie/mithril.js/pull/772

Sorry, but my support for the PR #772 is very slow now. Anyone feel free to complete it! It's trivial enough, don't fear! :-)

m in rewrite branch is jsx-pragma-friendly


flutter_windows_v1.12.13+hotfix.9-stable logging on every tap or when changing screens

Refering to issue #50892, christopherfujino closed the issue saying:

So, the accessibility warning was a bug that was fixed in version 13.0, unfortunately, after the latest stable was cut.
The reason this was only seen after hotfix 8 was release, was because there was a separate regression that was over-aggressively filtering logs, which was obscuring legitimate logs (such as app crashes and this accessibility warning). Hotfix 8 removed this log filtering, thus surfacing the accessibility warning.
We apologize for regressing the user experience in this way on the stable channel. This warning message has been fixed on the beta, dev, and master channels, and will be removed from the next stable release.

But even after latest release this issue hasn't been fixed as I', still getting this error on every single tap.
I've tried flutter pub cache repair and flutter clean but can't see any difference.
Here's a screenshot:

Exactly and it's pretty annoying when you debugging...I actually also raised an issue on this a couple of days ago and see the response I also get

Hi @RaiAnsar
https://github.com/flutter/flutter/issues/50892#issuecomment-593615696

will be removed from the next stable release

did you mean any new stable release, even hotfix? or new stable release which will be 1.13.0 or higher?

Hi @RaiAnsar
#50892 (comment)

will be removed from the next stable release

did you mean any new stable release, even hotfix? or new stable release which will be 1.13.0 or higher?

I meant the last hotfix which seems to be reducing it but not completely solving it.
This issue has been opened since December 3 #45928, but maintainers keep closing it without completely solving it.

Exactly and it's pretty annoying when you debugging...I actually also raised an issue on this a couple of days ago and see the response I also get

Closing without solving the issue is multiple developers to open the same issue again.

Thanks to @eseidelGoogle for suggesting temporary solution of moving to beta channel on issue #50892 :

The easiest workaround for now is to just use flutter channel beta to switch to the beta channel where we have resolved this bug. Thanks!

And after testing I can confirm that this issue has been resolved in beta release. And thanks to @pcsosinski  for mentioning that  beta  is capable of production release so I'll be closing it here,  hoping that issue will be solved in next Stable release as well.


Igesting 'tsx' is not recognized

Seems to be having an error when ingesting here is the code that I am running along with the output.
INPUT:
PS C:\Users\burnsidet\Documents\gpt4-pdf-chatbot-langchain-main> npm run ingest
OUTPUT:

<EMAIL_ADDRESS>ingest
tsx -r dotenv/config scripts/ingest-data.ts

'tsx' is not recognized as an internal or external command,
operable program or batch file.
PS C:\Users\burnsidet\Documents\gpt4-pdf-chatbot-langchain-main>

Yes, I have but, I see my issue because I never ran yarn install because I am attempting to build this out on my school computer they have disabled running scripts on this system if you have any ideas about potential workarounds about how to work around this feel free to let me know.

After looking into things a bit further this was not a school-imposed restriction but a PowerShell default setting that seemed to be set by default by my administration. The following link talks about this https:/go.microsoft.com/fwlink/?LinkID=135170
though to save some time if others run into similar issues with their PowerShell follow the next steps.

Open PowerShell and run as administrator
Run Set-ExecutionPolicy -ExecutionPolicy Unrestricted
Check that you now have by running Get-ExecutionPolicy

Hopefully, this helps

I had to make sure I had langchain installed and also used VScode to fix some other import errors related to the process object.

I am getting the same issue. Any assistance is appreciated
ExecutionPolicy is "AllSigned"

@larri-eng try installing the missing tsx dependency using
npm install tsx


Unused buffer in issue-108.test.js

While looking through the tests, I found this oddity:
https://github.com/mapbox/node-sqlite3/blob/7eda5eee0c98d8deb2a89f3d6348f8f57ec0f9e1/test/issue-108.test.js#L20
buff doesn't appear to be used, a raw string 'a' is though. Was this done intentionally?

Thanks!


#18639 sqlite fix new constraint from selection

Just reorder CHILD_TYPES of SQLiteTableManager

Thanks for the contribution! We will review your PR and let you know.

Thanks for the contribution. Passing the PR to our QA team now.

Verified


feat(transformer/jsx): escape xhtml in jsx attributes

Merge activity

Oct 29, 3:06 AM: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.


Error after upgrading and replacing mswDecorator with mswLoader - Storybook v7

I'm getting an error after upgrading to 1.7.0 and replacing the mswDecorator with mswLoader. Any help would be appreciated. If there is any more info needed to debug, let me know. Thanks.
storybook 7.0.0-beta.31
msw-storybook-addon 1.7.0
msw 0.49.3
react 18.2.0
Error: Objects are not valid as a React child (found: [object Promise]). If you meant to render a collection of children, use an array instead.
    at throwOnInvalidObjectType (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:80645:9)
    at reconcileChildFibers (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:81586:7)
    at reconcileChildren (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:84920:28)
    at mountIndeterminateComponent (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:85910:5)
    at beginWork (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:87340:16)
    at beginWork$1 (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:93179:14)
    at performUnitOfWork (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:92310:12)
    at workLoopSync (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:92219:5)
    at renderRootSync (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:92187:7)
    at recoverFromConcurrentError (http://<IP_ADDRESS>:6006/vendors-node_modules_babel_runtime_helpers_esm_asyncToGenerator_js-node_modules_babel_runtime-fa810f.iframe.bundle.js:91603:20)

Hey @ddcech thanks for reporting! Can you provide a reproduction? It sounds, to me, that somehow a promise is passed and rendered in your component, though a loader does not do that, unless your story has something with loaded. Can you figure out which story is causing that, and share the source here (or make a small reproduction)? thanks!

I'll try to make a reproduction on codesandbox or new github repo. Please notice I'm using storybook v7 beta not 6 as you have used in your docs. This could be where the issue is originating from. I'm also using CSF 3.0 to render a basic component.

Issue was on my side. I did not change the exported variable name to loaders, and kept decorators.
export const decorators = [mswDecorator]

should now be
export const loaders = [mswLoader]

@yannbf BTW the release note for 1.7.0 has a typo. you have export const loaders twice.

Thanks a lot @ddcech ! I updated so other people won't have issues with it.


chore: remove browser-sync from devdependencies

:tada: This PR is included in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: