RCTBridge required dispatch_sync to load RCTDevLoadingView. This may lead to deadlocks

I randomly get this warning at iOS app start (i.e. not always).
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
OS:  macOS Sierra 10.12.6
Node:  6.10.2
Yarn:  1.0.2
npm:  5.4.2
Watchman:  4.7.0
Xcode:  Xcode 9.0 Build version 9A235
Android Studio:  2.1 AI-143.2915827
Packages: (wanted => installed)
react: ^16.0.0 => 16.0.0
react-native: ^0.49.3 => 0.49.3
Steps to Reproduce

Start the app

Expected Behavior
No warning
Actual Behavior

Reproducible Demo
N/A
Some packages I use
https://github.com/antoinerousseau/react-native-custom-components
https://github.com/rebeccahughes/react-native-device-info
https://github.com/evollu/react-native-fcm
https://github.com/gwmccull/react-native-polyfill
https://github.com/getsentry/react-native-sentry

Same here!

I see this as well.  Possibly related to #11196.
I believe this is what is also causing the app to crash when trying to reload; it fails with
Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'This method must not be called before the JS thread is created'

I'm also getting this error from time to time on iOS 11 and I've got no idea how to debug this to give more information. Stacktrace doesn't help at all in this case.

+1

+1

+1

+1

Please stop adding +1s, this is generating email notifications that don't add any information. Use the "add reaction" feature instead.

not sure which of the following commands fixed this for me, but I did...
rm -rf ~/.rncache/
watchman watch-del-all
npm start -- --reset-cache

and the warning disappeared for me.

Same issue. Here are the packages I use:

react-native-device-info
react-native-interactable
react-native-sensitive-info
react-native-snackbar
react-native-splash-screen
react-native-svg
react-native-vector-icons

Given the intersection with @antoinerousseau's list, the possible locations for this bug are:

A bug in react-native itself
A bug in react-native-device-info
Multiple bugs in libraries other than react-native-device-info

I just added react-native-device-info, and moved from rn 0.49 to 0.50. and now i found this bug. Don't know if it's the problem, but it's when i got this.

Same issue...
So it was not my fault ?

Same issue... Do u have any solutions ?

Same issue. The only package from the list above we use is react-native-sentry.

Same issue here today i have started a brand new app and only package i have added
"native-base": "^2.3.3",
"react": "16.0.0",
"react-native": "0.50.3",
"react-native-fcm": "^10.0.3"

+1
"react-native": "0.49.3",
anybody resolves it ??

@dantman I started seeing the issue immediately after installing react-native-device-info, so I highly suspect it is related.
The only other package I am using react-native-keychain, which I installed quite a while ago without any issues, so it seems like a good bet.

👀
https://github.com/rebeccahughes/react-native-device-info/issues/260

rebeccahughes/react-native-device-info#260 seems to have a message referring to RNDeviceInfo while this bug refers to RCTDevLoadingView. So there may be more than one spot triggering this warning.

If you would put a breakpoint on the following line:
RCTLogWarn(@"RCTBridge required dispatch_sync to load<EMAIL_ADDRESS>This may lead to deadlocks", _moduleClass);

You can see which module/stack is responsible for loading RCTDevLoadingView in my case it was RCTCxxBridge.mm which was loading the remote bundle and reporting the download progress on RCTDevLoadingView:
... onProgress:^(RCTLoadingProgress *progressData) {
#if RCT_DEV && __has_include("RCTDevLoadingView.h")
      RCTDevLoadingView *loadingView = [weakSelf moduleForClass:[RCTDevLoadingView class]];
      [loadingView updateProgress:progressData];
#endif
    }];

Here the RCTCxxBridge is using  moduleForClass which will load the module. Due to the queue used for the onProgress block RCTDevLoadingView would be loaded on a non-main queue, while RCTDevLoadingView requires a main-queue setup.
I was able to workaround the warning by optimistically load RCTDevLoadingView by returning an instance from my RCTBridgeDelegate using:
- (NSArray<id<RCTBridgeModule>> *)extraModulesForBridge:(RCTBridge *)bridge;

I was able to fix this issue by updating AppDelegate.m
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                            moduleProvider:nil
                                             launchOptions:launchOptions];
#if RCT_DEV
  [bridge moduleForClass:[RCTDevLoadingView class]];
#endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"Test"
                                            initialProperties:nil];
  ...
}

react-native: 0.50.4
same issue...

react-native: 0.51.0
same issue...

No "react-native-device-info" installed:
Issue exists in 0.54.2 :
"react": "16.3.0-alpha.2",
"react-native": "0.54.2",
"react-native-action-button": "^2.8.4",
"react-native-admob": "^2.0.0-beta.4",
"react-native-animatable": "^1.2.4",
"react-native-awesome-alerts": "^1.0.7",
"react-native-elements": "^0.19.0",
"react-native-fbsdk": "^0.7.0",
"react-native-linear-gradient": "^2.4.0",
"react-native-parallax-scroll-view": "^0.21.0",
"react-native-photo-grid": "0.0.2",
"react-native-responsive-dimensions": "^1.0.2",
"react-native-snap-carousel": "^3.6.0",
"react-native-vector-icons": "^4.5.0",
"react-navigation": "^1.5.7"

It was with the "react-native-action-button": "^2.8.4", Adding shadowStyle={{shadowOpacity: 0.9}} solved the warning..

Same issue here.

Same issue.
RN 0.54.4

same

+1

I started having this issue just now after setting up my repo from scratch and inserting the pure js code back in there. A potential difference between the previous and this new repo is that now I'm using Cocoapods.
Anyone not using Cocoapods?

This happened right after I added
react-native-blur
to a Share Extension view, nested within
react-native-modalbox

Sorry. I could not debug/console log from the Share Extension view, only the main app.

+1

@react-native-bot issue still occurring on React Native 0.55

@react-native-bot When using cocoapods to manage react native, the issue will show up.
versions I try 0.50.4 and 0.55.4

Just installed react-native-svg on React Native 0.55.3 and this issue popped up.

I am having exact same warning with a fresh new created project without any code added but only Firebase dependencies injected.
I am using :   react: 16.3.1
react-native: 0.55.4
Thank you

I am having the same issue but, for me it was because of the previous terminal window running when i rerun the build from Xcode. I just quit the terminal and the simulator and run the build again, this issue got resolved.

I also have react-native-device-info installed, but the yellow message is slightly different for me: 'RCTBridge required dispatch_sync to load RCCManagerModule...'

I was going to say I get this warning when I map over an array to return new elements or pass a style prop to custom components, but now the warning seems unpredictable.

Encountered this issue on OS11 as well.

react-navigation
react-native-vector-icons

I see a few people here that have mentioned using vector-icons.

I also had the same issue for me i have unlink and remove react-native-device-info and now that warning is not appearing.

I had the same issue after adding react-native-vector-icons, removed it and warning went away.

FYI, this warning showed up today after reload with remote debugger on. Turned remote off, did reload, no warning. Turned remote back on, did reload, no warning.

iOS 12, RN 0.57.0 same issue.

how to resolve?
or ignore is?
import { YellowBox } from 'react-native';
YellowBox.ignoreWarnings(['RCTBridge']);

Yes, I am having this issue as well, but what does it mean?

Getting same issue on iOS 12.1, RN 0.57.4 without react-native-device-info

I have some issue
"lodash": "^4.17.10",
"react": "16.4.1",
"react-native": "0.56.0",
"react-native-check-box": "^2.1.0",
"react-native-collapsible": "^1.2.1",
"react-native-elements": "^0.19.1",
"react-native-google-analytics-bridge": "^5.8.0",
"react-native-google-places-autocomplete": "^1.3.9",
"react-native-map-clustering": "^1.3.0",
"react-native-maps": "^0.21.0",
"react-native-masked-text": "^1.7.2",
"react-native-modal-picker": "0.0.16",
"react-native-onesignal": "^3.2.8",
"react-native-simple-radio-button": "^2.7.2",
"react-native-svg": "^8.0.0",
"react-native-ui-kitten": "^3.0.1",
"react-native-vector-icons": "^5.0.0",
"react-navigation": "^2.11.2",
"rn-sliding-up-panel": "^1.2.1",
"victory-native": "^30.5.0"

not working

In IOS getting "RCTBridge required dispatch_snyc to load RCTDevLoadingView This may lead to deadlocks."

Maybe you should Project -> Clean in your Xcode, then re-run your application.

I've confirmed that this comment is the solution. Thank you @mattijsf!
Find your RCTBridgeDelegate and override the extraModulesForBridge method.
Objective-C
@interface MyBridgeDelegate : NSObject <RCTBridgeDelegate>
@end

@implementation MyBridgeDelegate

- (NSArray<id<RCTBridgeModule>> *)extraModulesForBridge:(RCTBridge *)bridge
{
#if RCT_DEV
  return @[
    [bridge moduleForClass:[RCTDevLoadingView class]],
  ];
#else
  return @[];
#endif
}

@end

Swift 4
class MyBridgeDelegate: NSObject, RCTBridgeDelegate {
  func extraModules(for bridge: RCTBridge!) -> [RCTBridgeModule]! {
    if RCT_DEV == 1 {
      return [
        bridge.module(for: RCTDevLoadingView.self) as! RCTBridgeModule
      ]
    }
    return []
  }
}

Repro on iOS12, RN 0.57.8

I was able to repro this consistently on 0.57.x, but I can no longer repro this on 0.56.8.
In 0.57.x, my app would load fine on a fresh build, but I would usually see the error if I force closed the app (e.g., by swiping up on an iPhone X) and opened it again.

I was able to workaround the warning by updating AppDelegate.m
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                            moduleProvider:nil
                                             launchOptions:launchOptions];
#if RCT_DEV
  [bridge moduleForClass:[RCTDevLoadingView class]];
#endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"Test"
                                            initialProperties:nil];
  ...
}

This worked for me.

Has anyone been able to register a custom RCTBridgeDelegate while using react-native-navigation? You should be able to pass a delegate via the bridgeManagerDelegate param, but it seems broken (the RCTBridge provided to extraModulesForBridge is always nil).

I just started getting this immediately after adding react-native-device-info on RN 0.58.6 and iOS 12.

OK, this comment seems to have fixed it for me.

React Native 0.59.1
I start seeing this warning right after installing react-native-device-info as well, any real solution?

I'm seeing this randomly as well, and I have made no changes in my app code other than what's necessary (config) to make everything work again, in upgrading from RN 0.57.8 to 0.59.5. In my case, lib in question is CodePush: RCTBridge required dispatch_sync to load CodePush. This may lead to deadlocks
This issue is long. I assume nailing down the root cause is still a mystery? Let me know what other debug info I can provide to help.

My package.json:
> {
>   "name": "wonderswipe",
>   "version": "0.0.1",
>   "private": true,
>   "eslintConfig": {
>     "parserOptions": {
>       "ecmaVersion": 7,
>       "sourceType": "module",
>       "ecmaFeatures": {
>         "jsx": true
>       }
>     },
>     "env": {
>       "browser": false,
>       "node": true
>     },
>     "plugins": [
>       "react",
>       "react-native",
>       "react-hooks"
>     ],
>     "rules": {
>       "comma-dangle": [
>         2,
>         "always-multiline"
>       ],
>       "semi": [
>         2,
>         "never"
>       ],
>       "react-native/no-unused-styles": 2,
>       "react-native/split-platform-components": 2,
>       "react-hooks/rules-of-hooks": "error"
>     }
>   },
>   "scripts": {
>     "start": "node node_modules/react-native/local-cli/cli.js start",
>     "postinstall": "patch-package"
>   },
>   "dependencies": {
>     "@postlight/mercury-parser": "^2.0.0",
>     "@react-native-community/async-storage": "^1.3.3",
>     "@react-native-community/viewpager": "^1.1.6",
>     "babel-plugin-idx": "^2.4.0",
>     "buffer": "^5.2.1",
>     "he": "^1.1.0",
>     "idx": "^2.5.5",
>     "lodash": "^4.17.2",
>     "moment": "^2.19.0",
>     "moment-timezone": "^0.5.10",
>     "node-summary": "../node-summary",
>     "react": "16.8.3",
>     "react-native": "^0.59.4",
>     "react-native-actionsheet": "^2.4.2",
>     "react-native-blur": "^3.2.0",
>     "react-native-cached-image": "../react-native-cached-image",
>     "react-native-cheerio": "^1.0.0-rc.4",
>     "react-native-code-push": "^5.3",
>     "react-native-custom-tabs": "^0.1.7",
>     "react-native-easy-toast": "^1.0.9",
>     "react-native-firebase": "^5.3.1",
>     "react-native-fit-image": "^1.4.8",
>     "react-native-flanimatedimage": "^0.4.0",
>     "react-native-highlight-words": "^1.0.1",
>     "react-native-keep-awake": "^4.0.0",
>     "react-native-linear-gradient": "^2.0.0",
>     "react-native-modal-dropdown": "^0.6.2",
>     "react-native-modalbox": "^1.6.0",
>     "react-native-orientation": "^3.1.3",
>     "react-native-parallax-scroll-view": "../react-native-parallax-scroll-view",
>     "react-native-rate": "^1.0.8",
>     "react-native-safari-view": "^2.0.0",
>     "react-native-sentry": "^0.42.0",
>     "react-native-sha256": "^1.1.1",
>     "react-native-status-bar-size": "^0.3.2",
>     "react-native-swiper": "^1.5.14",
>     "react-native-tooltip": "^5.2.0",
>     "react-native-tts": "^3.0.0",
>     "react-native-vector-icons": "^6.4.2",
>     "react-native-webview": "^5.7.0",
>     "react-native-webview-bridge": "^0.40.1",
>     "react-redux": "^7.0.1",
>     "redux": "^4.0.0",
>     "redux-thunk": "^2.1.0"
>   },
>   "devDependencies": {
>     "babel-eslint": "^10.0.1",
>     "eslint": "^5.15.1",
>     "eslint-plugin-react": "^7.12.4",
>     "eslint-plugin-react-hooks": "^1.0.1",
>     "eslint-plugin-react-native": "^3.6.0",
>     "patch-package": "^6.1.2",
>     "postinstall-postinstall": "^2.0.0",
>     "redux-logger": "^3.0.6"
>   },
>   "resolutions": {
>     "babel-core": "7.0.0-bridge.0"
>   }
> }

i fixed this error by @grossingdev comment. but after updating react-native to 0.59.8 version. this error has come again

At react-native 0.59.3, here is what the code should look like to workaround the problem:
  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  #if RCT_DEV
    [bridge moduleForClass:[RCTDevLoadingView class]];
  #endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"YourAppName"
                                            initialProperties:nil];

Facing the same warning after updating the AppDelegate.m file while Integrating the react-native-maps google map in ios App.

For me -- this worked ---
"react": "16.8.3",
"react-native": "0.59.9",

(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
//  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
//  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
//                                                   moduleName:@"foxmobileapp"
//                                            initialProperties:nil];
NSURL *theurl ;
#if DEBUG
theurl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
theurl = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:theurl
moduleProvider:nil
launchOptions:launchOptions];
#if RCT_DEV
[bridge moduleForClass:[RCTDevLoadingView class]];
#endif
RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
moduleName:@"foxmobileapp"
initialProperties:nil];
rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];
self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
UIViewController *rootViewController = [UIViewController new];
rootViewController.view = rootView;
self.window.rootViewController = rootViewController;
[self.window makeKeyAndVisible];
return YES;
}

My warning appears when I use backgroundColor style inside my ImageBackground component with a source image. I hope this helps anyone!

@amitkumar3968  format your comment as code

I just got similar error:

my package.json:

{
  "name": "auth",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "firebase": "^6.3.1",
    "react": "16.8.6",
    "react-native": "0.60.0"
  },
  "devDependencies": {
    "@babel/core": "7.5.0",
    "@babel/runtime": "7.5.0",
    "@react-native-community/eslint-config": "0.0.3",
    "babel-jest": "24.8.0",
    "eslint": "6.0.1",
    "jest": "24.8.0",
    "metro-react-native-babel-preset": "0.54.1",
    "react-test-renderer": "16.8.6"
  },
  "jest": {
    "preset": "react-native"
  }
}

Reload fixed it, but seems something isn't right if this happens randomly.

This issue only happens to me when I deactivate the debugger. When opening the Perf Monitor, I noticed that the RAM goes from ±100MB to ±300MB after deactivating.
With debugger:

Without debugger:

The proposed workaround does not work in my case, since it only stops displaying the warning, but it does not solve the problem with memory.

I wonder if this problem would affect the performance of the app in release mode.

The aforementioned workaround solved this problem for me as well, on React Native 0.59.10:
diff --git a/ios/Foo/AppDelegate.m b/ios/Foo/AppDelegate.m
index e446e79..2c28719 100644
--- a/ios/Foo/AppDelegate.m
+++ b/ios/Foo/AppDelegate.m
@@ -18,6 +18,11 @@

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>

+// https://github.com/facebook/react-native/issues/16376#issuecomment-350523177
+#if RCT_DEV && __has_include(<React/RCTDevLoadingView.h>)
+#import <React/RCTDevLoadingView.h>
+#endif
+
 @implementation AppDelegate

@@ -39,6 +44,13 @@ - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(

   RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
+
+  // https://github.com/facebook/react-native/issues/16376#issuecomment-350523177
+  #if RCT_DEV && __has_include(<React/RCTDevLoadingView.h>)
+  [bridge moduleForClass:[RCTDevLoadingView class]];
+  #endif
+
   RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge moduleName:@"Foo" initialProperties:nil];
   rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

The only difference here is that I matched the exact same logic for loading it (the RCT_DEV && __has_include(<React/RCTDevLoadingView.h>) part)...

Just got 2 with react-native-firebase. Happens rarely but:

I was able to re-create this issue by adding app icons to the Images.xcassets/AppIcon.appiconset directory of my newly created test project using react-native 0.61.2. Adding the lines of code mention in this issue solved the issue for me.

react-native 0.59.10
same issue.

same issue here!! any body solved this problem?

I was able to workaround the warning by updating AppDelegate.m
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                            moduleProvider:nil
                                             launchOptions:launchOptions];
#if RCT_DEV
  [bridge moduleForClass:[RCTDevLoadingView class]];
#endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"Test"
                                            initialProperties:nil];
  ...
}

this workaround solved the warning. Thank you very much.

Same issue, but if I delete block of code componentDidUpdate, this warning dissappear. But but but but I need componentDidUpdate.

first : open Xcode, normaly Xcode answer if you want install a component : click install
When you update macOS software, you must open Xcode for update

I was able to workaround the warning by updating AppDelegate.m
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                            moduleProvider:nil
                                             launchOptions:launchOptions];
#if RCT_DEV
  [bridge moduleForClass:[RCTDevLoadingView class]];
#endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"Test"
                                            initialProperties:nil];
  ...
}

@grossingdev what is the jsCodeLocation please? I know it's supposed to be a URL but what should it point to?

Just got 2 with react-native-firebase. Happens rarely but:

Firebase is causing this error for me. Mind sharing how you solved it?

@abdi4 I just ran into this too, did you manage to solve it?

no this happens randomly and im not able to recreate it

Simplest way to ignore this or any other warning is
import { YellowBox } from 'react-native';

YellowBox.ignoreWarnings([
    'RCTBridge'
]);

This issue arises for me non-deterministically. The only fix I have whenever it does, is to delete the app from my device and re-run.

Swift Solution:
let bridge = RCTBridge(bundleURL: jsCodeLocation, moduleProvider: nil, launchOptions: nil)
#if RCT_DEV
bridge?.module(for: RCTDevLoadingView.self)
#endif
let rootView = RCTRootView(bridge: bridge!, moduleName: "AppMain", initialProperties: nil)

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

Here's your activity. The warning continue to pops up in fresh new apps.

@sospedra could you provide a repo of this happening with React Native template without any external dependencies?
For the cases where it happens with third party libraries, issues should be filed with those libraries

same issue on 0.63.2 I'm not sure what is causing it, it happens randomly sometimes all interactions of the app is no longer working.

Same warning comes only with react-native-macos, not with ios, android, or windows.

Got the same warning with a Catalyst App.

I closed the simulator, killed metro, in XCode build and run Warning disappeared !

Closing the metro bundler and uninstalling the app from the simulator disappeared the warning. But not sure what's happening under the hood. warning appeared after adding thunk package.

I was able to workaround the warning by updating AppDelegate.m
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
...
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  ...
  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                            moduleProvider:nil
                                             launchOptions:launchOptions];
#if RCT_DEV
  [bridge moduleForClass:[RCTDevLoadingView class]];
#endif
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"Test"
                                            initialProperties:nil];
  ...
}

this workaround solved the warning. Thank you very much.

For anyone using this solution, if your xcode crashes and throws an error at initWithBundleURL: jsCodeLocation, substitute jsCodeLocation = ```
[[RCTBundleURLProvider sharedSettings]
<EMAIL_ADDRESS>fallbackResource:nil]

[https://stackoverflow.com/questions/43193418/native-view-presenting-a-react-native-view](https://stackoverflow.com/questions/43193418/native-view-presenting-a-react-native-view)

This solved the issue for me

If you are getting one of these errors:
RCTBridge required dispatch_sync to load RCTDevLoadingView
Use of undeclared identifier 'jsCodeLocation'
Use of undeclared identifier 'RCTDevLoadingView'
Here's a full solution:

#import "AppDelegate.h"

// NEW CODE

// put this condition after AppDelegate.h import
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif

// END

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
...

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  // NEW CODE

  NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];

  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                              moduleProvider:nil
                                               launchOptions:launchOptions];
  #if RCT_DEV
   [bridge moduleForClass:[RCTDevLoadingView class]];
  #endif

  // END

  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"TempleWallet"
                                            initialProperties:nil];
  ...

I had this issue when an image i put in a file with a certain ending(.jpg) when i changed it to (.jpeg) the problem went.

Onboarding to RN and was surprised to hit this three and a half year old bug. Everyone has to go through this?

@unixvb in which file I have to write this code, please?

@unixvb in which file I have to write this code, please?

app-name/ios/AppName/AppDelegate.m

If that would help someone I was using react-native 0.64.0 with flipper setup with versions like that in Podfile:
use_flipper!({ 'Flipper-Folly' => '2.5.3', 'Flipper' => '0.87.0', 'Flipper-RSocket' => '1.3.1' })
I had no luck applying the fix that is suggested above getting error "Use of undeclared identifier 'RCTDevLoadingView'" and what's worked for me is downgrading flipper, changing that line to:
use_flipper!('Flipper' => '0.75.1', 'Flipper-Folly' => '2.5.3', 'Flipper-RSocket' => '1.3.1')

The same problem I have

For me I make use of react-native-firebase in my application but you can still make use of the instruction below is how inserted  code reference from @unixvb thanks
step 1: I updated react-native-navigation node package run below commands
npm uninstall  react-native-navigation --force
npm install  react-native-navigation
npx rnn-link
step 2: Edit AppDelegate.m file with below sample file as guide
// AppDelegate.m file
`#import <Firebase.h>
#import "AppDelegate.h"
// New Code start
// put this condition after AppDelegate.h import to solve RCTBridge required dispatch_sync to load lead to deadlock
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
// New Code end
#import <ReactNativeNavigation/ReactNativeNavigation.h>
#import <React/RCTBundleURLProvider.h>
#if DEBUG
#import <FlipperKit/FlipperClient.h>
#import <FlipperKitLayoutPlugin/FlipperKitLayoutPlugin.h>
#import <FlipperKitUserDefaultsPlugin/FKUserDefaultsPlugin.h>
#import <FlipperKitNetworkPlugin/FlipperKitNetworkPlugin.h>
#import <SKIOSNetworkPlugin/SKIOSNetworkAdapter.h>
#import <FlipperKitReactPlugin/FlipperKitReactPlugin.h>
static void InitializeFlipper(UIApplication *application) {
FlipperClient *client = [FlipperClient sharedClient];
SKDescriptorMapper *layoutDescriptorMapper = [[SKDescriptorMapper alloc] initWithDefaults];
[client addPlugin:[[FlipperKitLayoutPlugin alloc] initWithRootNode:application withDescriptorMapper:layoutDescriptorMapper]];
[client addPlugin:[[FKUserDefaultsPlugin alloc] initWithSuiteName:nil]];
[client addPlugin:[FlipperKitReactPlugin new]];
[client addPlugin:[[FlipperKitNetworkPlugin alloc] initWithNetworkAdapter:[SKIOSNetworkAdapter new]]];
[client start];
}
#endif
@implementation AppDelegate
// New Code start
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif
// New Code end

(BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
if ([FIRApp defaultApp] == nil) {
[FIRApp configure];
}
#if DEBUG
InitializeFlipper(application);
#endif
[ReactNativeNavigation bootstrapWithDelegate:self launchOptions:launchOptions];

// New Code start
NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];
RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
moduleProvider:nil
launchOptions:launchOptions];
#if RCT_DEV
[bridge moduleForClass:[RCTDevLoadingView class]];
#endif
// New Code end
return YES;
}

(NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

(NSArray<id> *)extraModulesForBridge:(RCTBridge *)bridge {
return [ReactNativeNavigation extraModulesForBridge:bridge];
}

@end
`
step 4: your Podfile insert below script
use_flipper!({ 'Flipper-Folly' => '2.5.3', 'Flipper' => '0.87.0', 'Flipper-RSocket' => '1.3.1' })
step 3:  pod install --project-directory=ios
step 4:  npx react-native run-ios

The same problem I have

@aarononeal only the beginning of a long journey my friend

Add this in your /ios/YourAppName/AppDelegate.m, right after #import "AppDelegate.h"
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif

If you are getting one of these errors:
RCTBridge required dispatch_sync to load RCTDevLoadingView
Use of undeclared identifier 'jsCodeLocation'
Use of undeclared identifier 'RCTDevLoadingView'
Here's a full solution:
Update the app-name/ios/AppName/AppDelegate.m file with following
#import "AppDelegate.h"

// NEW CODE

// put this condition after AppDelegate.h import
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif

// END

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
...

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  // NEW CODE

  NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];

  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                              moduleProvider:nil
                                               launchOptions:launchOptions];
  #if RCT_DEV
   [bridge moduleForClass:[RCTDevLoadingView class]];
  #endif

  // END

  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"TempleWallet"
                                            initialProperties:nil];
  ...

Feel free to open a PR for this!

If you are getting one of these errors:
RCTBridge required dispatch_sync to load RCTDevLoadingView
Use of undeclared identifier 'jsCodeLocation'
Use of undeclared identifier 'RCTDevLoadingView'
Here's a full solution:
Update the app-name/ios/AppName/AppDelegate.m file with following
#import "AppDelegate.h"

// NEW CODE

// put this condition after AppDelegate.h import
#if RCT_DEV
#import <React/RCTDevLoadingView.h>
#endif

// END

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
...

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  // NEW CODE

  NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings]<EMAIL_ADDRESS>fallbackResource:nil];

  RCTBridge *bridge = [[RCTBridge alloc] initWithBundleURL:jsCodeLocation
                                              moduleProvider:nil
                                               launchOptions:launchOptions];
  #if RCT_DEV
   [bridge moduleForClass:[RCTDevLoadingView class]];
  #endif

  // END

  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"TempleWallet"
                                            initialProperties:nil];
  ...

Doing this seems to mess up expo unimodules for me

same problem in expo dev client

@mwegener-com according to some people it is fixable modifying the App.Delegate.m. Mentioned by @safaiyeh for example. To modify this you can use the withAppDelegate from @expo/config-plugins to make the modifications. it'll look something like this.
// in your project root directory create filed named withIosAppDelegate.js
const { withAppDelegate } = require('@expo/config-plugins')
const modAppDelegate = (content) => {
// modify content of AppDelegate.m here and return it, its basic string manipulation.
// you can also console.log things here to see your code is doing
return content
}
module.exports = (config) => {
return withAppDelegate(config, async (config) => {
// the line below will feed the content of the AppDelegate.m to your function made above ^ "modAppDelegate", from there you will conduct needed manipulations and return it.
config.modResults.contents = modAppDelegate(config.modResults.contents)
return config
})
}
// in your app.js
{
"expo": {
...
"plugins": [
"./withIosAppDelegate.js"
]
}
}
then make sure you make a commit and run expo prebuild -p ios  --clean
this will apply your changes to the AppDelegate.m and if you are console logging things you will see your changes made
if the changes are made correctly go ahead and build your new build and you are set.
trying to learn how to create a plugin by reading the expo docs is very confusing but I was taught by someone who knew how to use them and I hope this helps. Basically you are passed the content of the native file you need to manipulate as a string, and you must use regex or any means to do string manipulation and add or remove the lines of code you want, then simply return the string. docs
btw I have been able to avoid any problems by first launching the dev client on the simulator or my phone and THEN pressing i on my console to run the project, this way the dev client doesn't crash.. if this works for you you wont even need to do any of the step above..

It wouldn't be my first config plugin, but have you already finished it and might share your solution?

@mwegener-com I have not created a config plug in because even though the warning comes I rarely get any rashes because of it. If you do create it I would appreciate the share

I'm getting the same error

I have no idea what the meaning of the warning is, but this makes it go away:
https://amanhimself.dev/blog/rctbridge-required-dispatch-sync-to-load-warning/

I have no idea what the meaning of the warning is, but this makes it go away:
https://amanhimself.dev/blog/rctbridge-required-dispatch-sync-to-load-warning/

This solution does not work. The iOS app is failing to build with that code added.

None of this works in 2022, on a fresh install of React Native 0.67.3

0.67.3 this does not help. What does it mean?

Hello,
Using  "react-native": "0.64.3" I am seeing this issue after installing a native module (Agora Livestreaming SDK) and running expo run:ios
I added two string values to Info.plist for the enable mic/camera permission text.
Besides that I have no other modules in project, and only imported expo libraries such as blurview for basic layout features.
I am seeing this issue now on loading the app through Metro now that I am in a bare workflow

I'm from 2030 and this still does not fix. 😏

I am experience the same issue as well

... a new created 0.70.1 project has the issue too, it's funny, my 4 years old project doesn't have this issue.


react-native-vector-icons/lib/create-icon-set.js: Missing class properties transform.

We’ve just released a major new version with significant changes and improvements. If you’re still experiencing this issue after upgrading, please open a new issue with updated details. We're closing all the very old issues to get on top of things. Thanks for your patience!


Memory leak in TextReasterizer

https://chatgpt.com/c/66970d01-6649-4e30-b70e-e43346b542ad

Use texture atlas.
Use Skyline Bin-packing.
When a texture is full, throw it away and make a new one.

Fixed in https://github.com/atty303/pob-web/commit/617519f1d64227b4effa085e5e83939d953a1898


Plugin is not sending the proper information to Domoticz.

Zigbee2MQTT version 1.21.0-dev commit: d92bdf1c
Coordinator type zStack3x0
Coordinator revision 20210708
Frontend version 0.6.0
Plugin : 3.0.1
Domoticz: Version: 2021.1 (build 13497)
Build Hash: 2c271b6d2
Compile Date: 2021-09-10 15:25:51
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
At the start of Domoticz and/or the plugin I get this info in the Domoticz.log
2021-09-15 09:16:56.355  Status: Zigbee: (Zigbee) Entering work loop.
2021-09-15 09:16:56.355  Zigbee hardware started.
2021-09-15 09:16:56.356  Status: Zigbee: (Zigbee) Started.
2021-09-15 09:16:56.640  Status: Zigbee: (Zigbee) Initialized version 3.0.1
2021-09-15 09:16:56.666  Zigbee: (Zigbee) Installing plugin custom page...
2021-09-15 09:16:56.681  Zigbee: (Zigbee) Installing plugin custom page completed.
2021-09-15 09:16:56.732  Zigbee: (Zigbee) Connected to MQTT Server: <IP_ADDRESS>:1883
2021-09-15 09:16:56.834  Zigbee: (Zigbee) Zigbee2mqtt bridge is online
2021-09-15 09:16:56.848  Zigbee: (Zigbee) Received available devices list from bridge
2021-09-15 09:16:56.863  Zigbee: (Zigbee) Joining new devices is disabled on the zigbee bridge
2021-09-15 09:16:56.913  Zigbee: (Zigbee) Received groups list from bridge
2021-09-15 09:17:00.360  Status: Incoming Domoticz connection from: <IP_ADDRESS>
2021-09-15 09:17:00.399  Status: dzVents: Info: ------ Start external script: check system temperatures.lua:, trigger: "every minute"
2021-09-15 09:17:00.419  Status: dzVents: Info: ------ Finished check system temperatures.lua
2021-09-15 09:17:00.419  Status: dzVents: Info: ------ Start external script: check utility devices.lua:, trigger: "every minute"
2021-09-15 09:17:00.423  Status: dzVents: Info: ------ Finished check utility devices.lua
2021-09-15 09:17:00.424  Status: dzVents: Info: PADO: ------ Start external script: pir activated devices off.lua:, trigger: "every minute"
2021-09-15 09:17:00.424  Error: dzVents: Error: (3.1.8) PADO: There is no device with that name or id: PIR Zolder Sensor
2021-09-15 09:17:00.424  Error: dzVents: Error: (3.1.8) PADO: An error occurred when calling event handler pir activated devices off
2021-09-15 09:17:00.424  Error: dzVents: Error: (3.1.8) PADO: ...cz/scripts/dzVents/scripts/pir activated devices off.lua:52: attempt to index a nil value
2021-09-15 09:17:00.424  Status: dzVents: Info: PADO: ------ Finished pir activated devices off.lua
2021-09-15 09:17:00.424  Status: dzVents: Info: POW: ------ Start external script: switch off appliances.lua:, trigger: "every minute"
2021-09-15 09:17:00.432  Error: dzVents: Error: (3.1.8) POW: There is no device with that name or id: 3D-Printer kWh Meter
2021-09-15 09:17:00.432  Error: dzVents: Error: (3.1.8) POW: An error occurred when calling event handler switch off appliances
2021-09-15 09:17:00.432  Error: dzVents: Error: (3.1.8) POW: ...moticz/scripts/dzVents/scripts/switch off appliances.lua:149: attempt to index a nil value (local 'device')
2021-09-15 09:17:00.432  Status: dzVents: Info: POW: ------ Finished switch off appliances.lua

Those device (PIR Zonder Sensor and 3D-Printer kWh Meter) who gave errors are present in Domoticz and in the Zigbee2MQTT GUI when I activate or reinclude the devices then they (after a few tries) starts working normally. This happens randomly (not all) to the 50+ Zigbee devices I have.

I'm not sure that there is smth I could help with from the plugin side, I only could suggest creating such issue in Domoticz repository

BTW looks very similar to #706

Oke will do.

@SargonofAssyria
I have the same error.
Perhaps a solution found?

No solution found yet. Created an issue on domoticz/domoticz


[BEAM-12164] Add javadocs to SpannerConfig

Add javadocs to settings in SpannerConfig.

Run Java PreCommit

javadoc changes look good to me!

there's a few style errors flagged by our build: https://scans.gradle.com/s/gl4wjr7echz54/console-log?task=:sdks:java:io:google-cloud-platform:checkstyleMain
Basically, end all of the fist lines in Javadoc with a period

fyi @zoercai

Run Java PreCommit

Run Java PreCommit

ok LGTM thanks @zoercai !


Simplified parallel structure

This PR improves the parallel demo by removing the extra threading to accommodate the Flask and HTTP relay server. Since the Flask server is already an HTTP server, we don't need both of them. We can simply use Flask to relay events, then allow that to block the main thread until complete.
This more closely mirrors how we'd handle things on the GUIDE.

@garrettmflynn Some conflicts for some odd reason


Don't sort list each iteration in FileBased splitting

Looks like I've discovered a minor bug which has a big performance impact for the CRAB TaskWorker component when processing large datasets (one dataset which has 160k files hangs a child process for hours). AFAICT, it makes no sense to sort the lfn list after each lfn addition.

Good catch, Emilis. The failing test is actually unstable and not related to this fix. Anyways triggering it again.

test this please


[NO ISSUE] Apache 10.0.0-RC3 updates

This will need to be picked to the 10.0.0 branch as well.

Once merged, please cherry pick to 10.0.x


Fix(react): flickering of tabs components

Issue

https://github.com/creativetimofficial/material-tailwind/issues/225

Summary
fix tab component
Description
tab contents is flickering when loading. The reason is that the unmount animation is triggered. It does not occur when build with next, and there is a problem when doing SPA with react
Fix

Add initial state animation
Add state whether it is initial state or not
Replace useEffect with useIsomorphicLayoutEffect

Screen Capture
https://user-images.githubusercontent.com/7203958/217397271-58995466-6ab8-41e6-b159-ecf8967345c4.mov

@sajadevo
I don't have permission to add reviewers. I sent you a mention.
Also, there are diffs unrelated to my work on the main and dev-main branches. Please let me know if there are any commits that need merging

@sajadevo I don't have permission to add reviewers. I sent you a mention. Also, there are diffs unrelated to my work on the main and dev-main branches. Please let me know if there are any commits that need merging

Hey @pppp606 thanks for your collaboration I'll check them and publish them together with the next update of the project.
Cheers,
Sajad


Pin Jose-dependency for Py2

python-jose had an update to 3.3.0, where support for Py2 was dropped.
Failure log: https://github.com/spulec/moto/runs/2752216996?check_suite_focus=true

Codecov Report

Merging #3989 (5340e7b) into master (5602c4e) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3989      +/-   ##
==========================================
- Coverage   94.89%   94.88%   -0.01%
==========================================
  Files         454      454
  Lines       49536    49570      +34
==========================================
+ Hits        47005    47035      +30
- Misses       2531     2535       +4

Flag
Coverage Δ

servertests
55.65% <ø> (-0.03%)
:arrow_down:

unittests
94.75% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/s3/models.py
95.72% <0.00%> (-0.01%)
:arrow_down:

moto/elbv2/models.py
89.05% <0.00%> (-0.01%)
:arrow_down:

moto/elbv2/responses.py
94.83% <0.00%> (ø)

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 5602c4e...5340e7b. Read the comment docs.

python3.5 has the same problem with python2

@passage2016 Moto doesn't officially support Python3.5, so you might have to pin this dependency in your own project to make it work


Rewrite of Dependabot Best Practice Guide

Purpose

Rewrite of Dependabot guide using new template
Generalized Dependabot guide to be more focused on GitHub Security features rather than just Dependabot alone - this allows us to expand to include more recommendations

Proposed Changes

[CHANGE] Content rewrite using new template (see issue ticket below)
[CHANGE] Additional recommendations for GitHub security beyond just Dependabot
[REMOVE] References to Python Starter Kit’s Dependabot.yml - it is largely already consistent with the default configuration provided by GitHub for Python projects

Issues

#101

Testing

Markdown rendering: https://github.com/NASA-AMMOS/slim/tree/gh-security-best-practices/docs/guides/software-lifecycle/security/github-security
Needs a manual walkthrough with a fresh repository (TO-DO)

Looks great! Quite an improvement.
I would also recommend referring readers to concrete implementations of these concepts, and one that we can use right now is the Python Starter Kit. (I realize why we disconnected from it as the primary demonstration vehicle but I am sure that readers will want to see a functioning example.)


QuickShulker support

Adds QuickShulker support for ShulkerLootCrates.

This dose not include QuickShulker by default, players will still be able to use the mod without QuickShulker installed. QuickShulker will respect if the shulker is locked or not before opening and will display your message if it is. Feel free to make any changes!

Wait this is bork, let me fix

Think it's good now.

Just an FYI, this will require Quickshulker 1.2.1, which I have not released yet. But I hope to later tonight.

Ty for adding support! I appreciate it.
I added additional support for opening chest crates via QuickShulker, if the config setting is set that chest crates should keep their inventory on break. (0b9e80472d2f74705d0252fce9c0dde010ab5d88)
What I noticed when testing it out is that LootableContainerBlockEntitys checkLootInteraction() does not run when opening the items inventory via QuickShulker (so the player has to place and open the box for new items to generate).
That would be true for vanilla shulkers, too, if an item and the placed LootableContainerBlockEntity has the tag "LootTable" set.
Since that function only exists in containers BlockEntities and not in the items adding this special case may be a bit more complicated, though...
Since I saw your comment in the second commit message: Would opening a shulker with the "LootTable" tag set may remove that tag, too? I will be able to test it tomorrow, but in the meantime, maybe you already know the answer.

Hm yeah most likely that data will get wiped if there aren't any items in the shulker. I can implement a smarter check. This would remove the need for your custom ItemStackInventory.
I can experiment with checkLootInteraction. It looks like theoretically it is possible. I haven't received any complaints of users wanting the checkLootInteraction. But I suppose it is important for this mod


added missing eric variables

Short description outlining key changes/additions
Some variables for eric-web were missing in the terraform configuration
JIRA Ticket Number
BI-13660
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

CI: No IaC security warnings found


Add gardenlinux repo to base-test container

How to categorize this PR?
/kind enhancement
/area os
/os garden-linux
What this PR does / why we need it:
This PR adds the Garden Linux Repo to the base-test container in order to install some build tools that are built in the Gitlab Pipeline and published to the Garden Linux Repo. This makes them accessible in the Garden Linux base test.
Which issue(s) this PR fixes:
Fixes https://github.com/gardenlinux/gardenlinux/issues/1349

Tried to test this PR, but ran into an error
STEP 8/12: RUN echo "deb http://deb.debian.org/debian testing main contrib non-free" > /etc/apt/sources.list      && echo "deb [signed-by=$GARDENLINUX_MIRROR_KEY] https://repo.gardenlinux.io/gardenlinux $VERSION main" >> /etc/apt/sources.list      && apt-get update      && apt-get install -y --no-install-recommends           curl           unzip           ca-certificates           less           apt-transport-https           gnupg           python3-pip           python3-pytest           vim           procps           openssh-client           inetutils-ping           wget           iproute2           libguestfs-tools           qemu-system-x86           qemu-system-arm           qemu-efi-aarch64           shellcheck           build-essential           libpython3-dev
Ign:1 https://repo.gardenlinux.io/gardenlinux today InRelease
Get:2 http://deb.debian.org/debian testing InRelease [164 kB]
Get:3 http://deb.debian.org/debian testing/main amd64 Packages [8762 kB]
Get:4 http://deb.debian.org/debian testing/non-free amd64 Packages [117 kB]
Get:5 http://deb.debian.org/debian testing/contrib amd64 Packages [52.3 kB]
Ign:1 https://repo.gardenlinux.io/gardenlinux today InRelease
Ign:1 https://repo.gardenlinux.io/gardenlinux today InRelease
Err:1 https://repo.gardenlinux.io/gardenlinux today InRelease
  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
Fetched 9094 kB in 7s (1294 kB/s)
Reading package lists...
W: https://repo.gardenlinux.io/gardenlinux/dists/today/InRelease: No system certificates available. Try installing ca-certificates.
W: http://deb.debian.org/debian/dists/testing/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/gardenlinux.asc are ignored as the file is not readable by user '_apt' executing apt-key.
W: https://repo.gardenlinux.io/gardenlinux/dists/today/InRelease: No system certificates available. Try installing ca-certificates.
W: https://repo.gardenlinux.io/gardenlinux/dists/today/InRelease: No system certificates available. Try installing ca-certificates.
W: https://repo.gardenlinux.io/gardenlinux/dists/today/InRelease: No system certificates available. Try installing ca-certificates.
W: Failed to fetch https://repo.gardenlinux.io/gardenlinux/dists/today/InRelease  Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.  Could not handshake: Error in the certificate verification. [IP: <IP_ADDRESS> 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Hey @Vincinator,
good catch. I got in touch w/ @adaevitncar and he's currently busy. Therefore, I provide a fix by commit dc3ed25 ad change from https to http for Garden Linux repository.
Reason:
We do not have any ca files (for x509 validation on https) but all gpg keys for the signed repositories. Therefore, we may switch to plain http instead. Further validation is done by GPG.


Use consistent camelCase namings

I see that a lot of properties have inconsistent naming convention, sometimes camelCased, some times two words merged into one and other times snake_cased properties. It is an idea to make them all camelCased from the F# API point of view?
For example
// FROM
layout.xaxis.showgrid false
layout.xaxis.showline true
layout.xaxis.tickfont [ ]
layout.paper_bgcolor (colors.rgb(254, 247, 234))
layout.plot_bgcolor (colors.rgb(254, 247, 234))
// TO
layout.xaxis.showGrid false
layout.xaxis.showLine true
layout.xaxis.tickFont [ ]
layout.paperBackgroundColor (colors.rgb(254, 247, 234))
layout.plotBackgroundColor (colors.rgb(254, 247, 234))

The snake case is an oversight on my part. I'm not sure how to adjust the other methods because that's how they're defined in the json schema:
...
"showline": { ... },
...

I could try to find words within the method names but I'm not sure how easy to implement and consistent it would be.

I've merged the new code that replaces the snake case with camel case.

@Shmew if there are only a couple of those then I though that having a function to convert them can be doable:
let propertyMap = function
  | "showline" -> "showLine"
  | "showgrid" -> "showGrid"
  | "tickfont" -> "tickFont"
  | property -> property

but this is asking for trouble every time we miss one property and then change it, then it is a breaking change. If there are only a couple of such cases then it is OK but otherwise maybe not a good idea


Update JWKS with a modulus length >= 2048 bits

Describe the bug
The recommended modulus length is 2048 bits for jwks. Online uses 1024 which will break the minimum required length in a lot of libraries when verifying idTokens.
To Reproduce
Steps to reproduce the behavior:

Go to https://old.online.ntnu.no/openid/jwks
Look at the "n" attribute value.
Check the length of the value
Confirm it is too short.

Expected behaviour
I expect the public key to follow the minimum requirement for jkw modulus length of 2048 bits.
Screenshots

Additional context
Without this change, it is more difficult or (maybe) sometimes impossible to use third party authentication libraries, as we do not adhere to the JWK/JWA standards.
For more information see RFC7518 section 3.3. Since Online uses RS256:
"A key of size 2048 bits or larger MUST be used with these algorithms."

Yep. Using jose to verify JWTs issued by OW fails because of this issue. Error says: RS256 modulusLength 2048 bits or larger.


contig_frac parameter in YAML config file for ResMiCo-SM

Hello, and thanks for the awesome tool your research group has developed.
I'm interested in incorporating ResMiCo to my metagenomic pipelines, so I'm following the ResMiCo-SM readme to learn how to use the tool.
The README specifies that "map" parameters are required to run the pipeline with real metagenomic datasets, however, it does not explain what the subparameter contig_frac does. The default values for contig_frac in the repo config.yaml are 1000 and 1500.
How should the parameter contig_frac be used?
Thanks in advance.

Good catch! The README needs to be updated.
contig_frac is a way to reduce the number of contigs used as a reference during the read mapping steps of the snakemake pipeline. The parameter can be used in 2 ways:

If contig_frac > 1, it acts as a length cutoff (contig_length >= contig_frac).
If contig_frac >= 0 and <=1, it acts as a subsampling mechanism: what fraction of contigs to randomly subsample and used as a reference for read mapping?

See the code.


No related document about install SingarR nuget package.

[Enter feedback here]
No related document about install SingarR nuget package.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0dd2991d-c22d-ad0f-80b6-bd1b503db8f3
Version Independent ID: 5e3fbe1d-c97f-9940-4f0c-067d4b2112b1
Content: Get started with ASP.NET Core SignalR
Content Source: aspnetcore/tutorials/signalr.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @bradygaster
Microsoft Alias: bradyg

What package specifically? The tutorial you linked shows exactly what to do to get a server setup with SignalR and how to install the javascript client library.
If you're looking for a nuget package for SignalR on the server, there isn't one.

The SignalR server library is included in the ASP.NET Core 3.1 shared framework. The JavaScript client library isn't automatically included in the project.

https://docs.microsoft.com/aspnet/core/tutorials/signalr?view=aspnetcore-5.0&tabs=visual-studio-code#add-the-signalr-client-library


Fix for multicast redistribution when using REDISTRIBUTION_ONLY policy

Fix is really a revert to old behavior on this condition

Was this causing an existing test to fail? If not, could you add a test which triggers a failure before this change and is fixed after it? At the very least, describe the use-case where it fails and maybe I can add a test.

@jbertram
Added a test for this, hope it looks good


Update npm packages, fix high level security issues

This addresses the high level issues that npm audit generates. I was able to update all packages to current except for marked, which I was able to update to 0.3.12, where all tests would still pass (the latest is 0.6.0, it doesn't seem to follow semver convention, but it's around 900 commits later).
I've removed the node 0.10 / 0.12 builds from the travis config as they're extremely outdated node versions that are most likely not in use nowadays.

It looks like this has been published (9 months ago).
Maybe close this (and update the repo)? Otherwise, it looks like this is still an issue.


Remove postgres

Why
This issue is to discuss if this is possible or not.
We got the case that a fresh setup with a local Postgres instance was conflicting with the Postgres container of the client project (port/IP).
For new members, it can be quite "implicit" and hard to debug.
Should we remove Postgres from this script and consider it as a "project dependency" instead of as a "development tool"? 🤔
Who Benefits?
Developers can reduce the risks of DB port conflicts.

@hoangmirs , I tried removing postgres from my local machine as you suggested and it worked, Thanks 🎉
I just had to make sure I opened a new iTerm window after adding PATH to .zshrc.

I just had to make sure I opened a new iTerm window after adding PATH to .zshrc

The command to reload without restarting the terminal session is source ~/.zshrc ;-)
@hoangmirs / @tyrro let's apporove & merge your PR #40 🚀


running rust role as a non-root user fails

Maybe I'm missing something obvious, but I'm trying to install rust for ssh user which ansible is using to connect to the host and it fails when doing apt cache update:
TASK [fubarhouse.rust : Rust | Update apt cache] *******************************
fatal: [mayastor-dev]: FAILED! => {"changed": false, "msg": "Failed to lock apt for exclusive operation"}

If I run the role with "become: true" (root), then rust is installed for the root user and not for the one I want.
btw isn't the apt-cache update step completely useless when rust is installed using rustup script and not by the packaging system?

no rush, it can wait. Thanks for all the work!


orocos_kdl_vendor: 0.2.0-1 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository orocos_kdl_vendor to 0.2.0-1:

upstream repository: https://github.com/ros2/orocos_kdl_vendor.git
release repository: https://github.com/ros2-gbp/orocos_kdl_vendor-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 0.1.0-1

orocos_kdl_vendor
* Install headers to include/${PROJECT_NAME} (#3 <https://github.com/ros2/orocos_kdl_vendor/issues/3>)
* Contributors: Shane Loretz

python_orocos_kdl_vendor

No changes

Superseded by #32669


MODEXPW-185 Implement pausing consumer for Kafka Job Command Listener

Purpose
Avoid poll timeouts and job cycling.
Approach

run job inside new Thread
revert spring.kafka.consumer.properties.max.poll.interval.ms to default value

Learning
MODEXPW-185
Pre-Merge Checklist:
Before merging this PR, please go through the following list and take appropriate actions.

Does this PR meet or exceed the expected quality standards?

[ ] Code coverage on new code is 80% or greater
[ ] Duplications on new code is 3% or less
[ ] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] Were any API paths or methods changed, added or removed?
[ ] Were there any schema changes?
[ ] Did any of the interface versions change?
[ ] Were permissions changed, added, or removed?
[ ] Are there new interface dependencies?
[ ] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

Some mess with coverage. Created a new PR for this changes: https://github.com/folio-org/mod-data-export-worker/pull/271


Backend dataset does not include sample(s) from create-sample process(es)

When a create-sample-like process is added to a dataset, it's samples are not included in the dataset; also (once they are included) then they need to be removed when the corresponding process is removed from the dataset.

I believe this is fixed??


IT DOESN'T BUILD

IT KEEPS GIVING ME ERRORS I HTINK MY COMPUTER IS GOING TO EXPLODE WHAT IS GOIGN ON

Already fixed

oh no, my shitposts from years ago are coming back to me :rofl:
but cool, i wanted to check it out at some point

it was my shitpost... look at #3

yeah well

omegalul


feat(data): add 3 new size token for tile

This is what I add for Tile cell fix width
sizing.2000 = 160px
sizing.2500 = 200px
sizing.3000 = 240px

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Security options not displaying correctly

I specify security options:
security:
- APIKey: []
BasicAuth: []
On the html page I see:
AUTHORIZATIONS: APIKey & OR BasicAuth

Already fixed https://github.com/Rebilly/ReDoc/issues/577
Will be available in the next release in 2-3 hours


i18n: Minor spelling errors (DE)

Correction of minor spelling errors in DE-language files

Thanks!


Villager Fear Gamerule

Feature request: Gamerule to toggle whether or not villagers should be afraid of goo players, or use the default behavior.

Yeah I guess you're right, didn't know that was already on the radar (at least I hope it is)


Unlocking Field of Dreams

How do I unlock the Field of Dreams sandbox within this game for free?

It seems that people are blind am i right?

It seems that people are blind am i right?

wat do u mean? u know how to unlock FoD???

probably a value to change in the code

The game repo does not provide instructions on how to enable the Field Of Dreams and other cheats, but it's possible. By looking into the Unity project, I discovered that the game has cheats built into it. However, in order to enable them, you have to modify the assets. Specifically, you have to modify the gameconfig asset located in resources.assets and set "EnableCheats" to true.
This can be done by following these steps:

Get UABE from https://github.com/SeriousCache/UABE.
Open AssetBundleExtractor.exe.
Go to File > Open {Your_Bad_Piggies_Folder}/Bad Piggies_data/resources.assets.
Click on resources.assets within the Files and Components manager.
Go to View > Search by name and search for "gameconfig".
Click Plugins > Export to .txt.
Open the txt file, set "EnableCheats" to true, and save it.
Click Plugins > Import from .txt.
Select the modified txt file.
Go to File > Apply and Save All and save the resources.assets-mod file.
Rename the resources.assets-mod file to resources.assets and replace the original resources.assets with the modified one.
Launch Bad Piggies, and you should see an "Open Cheats" button near the upper left corner.

To enable the Field of Dreams:

Click "Open Cheats".
Click "Unlock Field of Dreams".
Click "Back to Main Menu".
Field of Dreams should now be unlocked.

If interested, this is how I found out:
I assumed the game already had some sort of debug/cheat menu, probably in the form of a popup/menu, so it would presumably be a Unity scene. By extracting the Unity package provided in releases, I was able to look at the scenes and found 'Scene/Scenes/UI/CheatsPanel.unity'. Using this information, I found a function, 'LoadCheatsPanel()', within 'GameManager.cs', which triggers 'CheatsPanel.unity'. Then, I found something that calls that function, which was 'ProgressResetButton.cs', triggering it in 'OnGUI()' if 'Singleton.Instance.CheatsEnabled'. I realized that 'BuildCustomizationLoader.cs' obtains data from some asset called 'gameconfig', which it then uses to enable/disable the cheats menu. I was able to then find 'Assets\Resources\gameconfig.bytes', which contains some configuration options, including the cheat menu.
I think the best way to go about this is, of course, to modify and recompile the project, but I have no idea how to do so since I've never used Unity and only have basic knowledge about it.


Allow getting .min() and .max() of matrices of unsigned integers

I have also added a test to the documentation, although I'm not 100% sure that's the right place to put them.
Let me know if I can improve something for this PR.

Sure! Updated

Thanks!


Quote the encoding when creating a database, fixes error with

PostgreSQL 9.4.4 seen on OpenBSD 5.8-snapshot.
Without the quoting, I got error like the following, using the puppetdb module:
Debug: Executing '/usr/local/bin/psql -d postgres -p 5432 -t -c "CREATE DATABASE puppetdb WITH OWNER=_postgresql TEMPLATE=template0 ENCODING=UTF-8  "'
Error: Error executing SQL; psql returned pid 29760 exit 1: 'ERROR:  syntax error at or near "UTF"
LINE 1: ...b WITH OWNER=_postgresql TEMPLATE=template0 ENCODING=UTF-8
^
'
Error: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Database[puppetdb]/Postgresql_psql[Create db 'puppetdb']/
command: change from notrun to CREATE DATABASE puppetdb WITH OWNER=_postgresql TEMPLATE=template0 ENCODING=UTF-8   failed: Error executing SQL; psql returned pid
29760 exit 1: 'ERROR:  syntax error at or near "UTF"
LINE 1: ...b WITH OWNER=_postgresql TEMPLATE=template0 ENCODING=UTF-8

:+1:

I already merged that as #700


0 1 Sort Technique | C++

0 1 Sort Technique -
what will change -
A new C++ script will be added for 0 1 Sort Technique
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Please assign this issue to me.

please assign me this issue

Hey, I would like to work on this issue. Please assign it to me.


[stable/concourse] Remove nodePort in tsa addr template

What this PR does / why we need it:
Previously, the concourse.web.tsa.address template used to take
tsaNodePort (the nodePort set for the TSA endpoint in the web
service) as part of the address that the worker should use to connect to
it, but that is just wrong as the workers are fully able to connect
through regular target ports within the cluster (which is the case when
running a full deployment).
Which issue this PR fixes

Special notes for your reviewer:
Without this patch applied, try deploying Concourse with the following sample-values.yaml values file:
web:
  service:
    type: NodePort
    tsaNodePort: 32001

Which leads to workers not being able to connect to the web instances.
Now, with this patch applied, see that it works.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/lgtm


code not working anymore cause continue not supported in gdscript 2

Godot version
4.0 stable
System information
windows 10
Issue description
I have a code for finite state machine that use match to change state and after changing state use continue to skip current state codes and jump to next state, but in gdscript2 continue doesn't work the same way as before, so my code doesn't work anymore and I don't know what is the replacement for "continue" to make it work
Steps to reproduce
match currentState:
		STATES.AIR:
			sprite.play("jump")

			if is_on_floor() and velocity.y == 0:
				currentState=STATES.FLOOR
				#! lastJumpDirection = 0
				continue
			elif is_near_wall():
				currentState = STATES.WALL
				continue
			elif should_climb_ladder():
				currentState = STATES.LADDER
				continue
			# Add the gravity.
			velocity.y += gravity * delta

Minimal reproduction project
N/A

If this is inside a loop then continue should move to the next iteration, if not this is a bug, but it's not clear from your code what you want it to do exactly

But please for issues that aren't bugs, please turn to the community channels as this is for bugs only

I agree. This is not a bug, but an intentional change. There was a suggestion to replace it with some new keyword, but we did not find a word that conveys the exact meaning of the old behavior (for example, fallthrough means a little different). Also, the ability to jump to a different match branch often results in less readable code.

Closing per the above comments.


8005 heatmap style

This PR fixes #8005.

Also, it fixes the bug related with the scroll not updating the position to show the selected item.
cc @xavijam

this should be reviewed by @makella

Don't we need changes in the style generator part? I guess it should know where to find 'resolution' attribute cc @javisantana.

I don't see the map updating on the animated gif, am I the only one?

Fixed the generator part, also updated the gifcast.

ready to go man, merge :es:

@nobuti can you tell me a little more about the relationship between resolution and symbol size and how they work together?
we probably want to have a good default that works for few points and lots of points so any additional information you have would be super helpful.
thanks!

@makella I'm not a big expert at all, but I'll try. As a Heatmap map is a variation of a Torque map, any of the Torque CartoCSS properties can be applied. Since Torque maps create a grid from your data and aggregates data to each cell of that grid, this property defines the width and height of each cell, in pixels. Larger numbers display larger grids of data. Here you have a great example about it: http://andrewxhill.com/blog/2015/04/17/torque-unknown/

@nobuti
totally. love that blog by andrew! Ok, thank you. I will spend some time with the new implementation and find a good default starting point. Thanks for the info!


Development server live reload not working

I'm submitting a ...
[ *] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

What is the current behavior?

I installed a fresh Ng2 Admin version 1.0.0, everything working fine but only can't auto compile the new changes. I modified files but the webpack never reload and I have to re-run npm start again which take time.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

root@1ac0f0357366:/var/www# npm start
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
<EMAIL_ADDRESS>start /var/www
ng serve --host <IP_ADDRESS> --port 8091

** NG Live Development Server is running on http://<IP_ADDRESS>:8091 **
Hash: 2252387d4a1d6e7f04e3
Time: 49200ms
chunk    {0} 0.chunk.js, 0.chunk.js.map 2.24 MB {1} {2} {3} {4} {5} {6} {7} {8} {9} {10} [rendered]
chunk    {1} 1.chunk.js, 1.chunk.js.map 575 kB {0} {2} {3} {4} {5} {6} {7} {8} {9} {10} [rendered]
chunk    {2} 2.chunk.js, 2.chunk.js.map 94.5 kB {0} {1} {3} {4} {5} {6} {7} {8} {9} {10} [rendered]
chunk    {3} 3.chunk.js, 3.chunk.js.map 225 kB {0} {1} {2} {4} {5} {6} {7} {8} {9} {10} [rendered]
chunk    {4} 4.chunk.js, 4.chunk.js.map 38.4 kB {0} {1} {2} {3} {5} {6} {7} {8} {9} {10} [rendered]
chunk    {5} 5.chunk.js, 5.chunk.js.map 303 kB {0} {1} {2} {3} {4} {6} {7} {8} {9} {10} [rendered]
chunk    {6} 6.chunk.js, 6.chunk.js.map 554 kB {0} {1} {2} {3} {4} {5} {7} {8} {9} {10} [rendered]
chunk    {7} 7.chunk.js, 7.chunk.js.map 19.7 kB {0} {1} {2} {3} {4} {5} {6} {8} {9} {10} [rendered]
chunk    {8} 8.chunk.js, 8.chunk.js.map 9.68 kB {0} {1} {2} {3} {4} {5} {6} {7} {9} {10} [rendered]
chunk    {9} 9.chunk.js, 9.chunk.js.map 8.34 kB {0} {1} {2} {3} {4} {5} {6} {7} {8} {10} [rendered]
chunk   {10} main.bundle.js, main.bundle.js.map (main) 174 kB {14} [initial] [rendered]
chunk   {11} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 158 kB {15} [initial] [rendered]
chunk   {12} styles.bundle.js, styles.bundle.js.map (styles) 664 kB {15} [initial] [rendered]
chunk   {13} scripts.bundle.js, scripts.bundle.js.map (scripts) 1.92 MB {15} [initial] [rendered]
chunk   {14} vendor.bundle.js, vendor.bundle.js.map (vendor) 5.44 MB [initial] [rendered]
chunk   {15} inline.bundle.js, inline.bundle.js.map (inline) 0 bytes [entry] [rendered]

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Does your live reload works outside of ng2-admin ?
This issue happened to me, and it was because of @ngTools not being up to date. After that it was working fine.

Webpack doesn't notice changes done from outside the container. However file changes are picked up by Webpack once logged into to the Docker container

I added option '--poll 1000' after the command 'ng serve' then works

adding the poll option has no effect, any other ideas? thanks!


Problem with types in prompt.go

Hi,
I try to run basic examples on Mac, golang version 1.10. I got an error:
vendor/github.com/manifoldco/promptui/prompt.go:88:11: cannot use p.stdin (type io.Reader) as type io.ReadCloser in assignment: 	io.Reader does not implement io.ReadCloser (missing Close method)
When I comment this line it works fine.

This problem occurs frequently, try to fetch the latest version(master branch)

I am facing the same issue. My tests are failing. When would this be released?

Sorry for the delay, everyone. There is a new release fixing this issue: https://github.com/manifoldco/promptui/releases/tag/v0.3.0
Please re-open if you are still experiencing the problem.


Compatibility | Node Graph Assistant Alt+MiddleClick cut

I've been really enjoying the combination of AutoSizeComments, Blueprint Assist and Node Graph Assistant together however there is a minor compatibility issue between AutoSizeComments and Node Graph Assistant.
The issue occurs when trying to use Node Graph Assistant's Alt+MiddleClick drag to cut wires when inside a comment box. The tool just doesn't work. Do note that this is only when inside a comment box with AutoSizeComments enabled.
It would be great if this issue was addressed but I understand that it's not really this organisation's responsibility to fix all random compatibility issues.

I'm unsure if the owner of the NGA plugin has implemented this yet: https://github.com/pdlogingithub/UE4-Node-Graph-Assistant/issues/28 This was some time ago so there could be some changes to the engine which may have broke this fix. You will need to build the plugin again manually after changing the source code.
To build it, you can follow the instructions below. I suggest you make a copy of the marketplace plugin and change the source code after step 1: https://blueprintassist.github.io/miscellaneous/faq/#building-the-plugin-for-a-custom-unreal-version


fix: decode Http error using proto3-JSON-serializer

Using proto3-json-serializer to parse HTTP error json; example error return from http request:
const json = {
      error: {
        code: 403,
        message:
          'Cloud Translation API has not been used in project 123 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/translate.googleapis.com/overview?project=455411330361 then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.',
        status: 'PERMISSION_DENIED',
        details: [{
'@type': 'type.googleapis.com/google.rpc.ErrorInfo',
      reason: 'SERVICE_DISABLED',
      domain: 'googleapis.com',
      metadata: {
        service: 'translate.googleapis.com',
        consumer: 'projects/123',
      },}],
      },
    };

Example of error.statusDetails

example
before
after

--
statusDetails: [ {'@type': 'type.googleapis.com/google.rpc.ErrorInfo',metadata: [Object],reason: 'SERVICE_DISABLED', domain: 'googleapis.com'}]
statusDetails: [ErrorInfo {metadata: [Object], reason: 'SERVICE_DISABLED', domain: 'googleapis.com'}]

I am getting lazy to fix the Typescript Type linter issue in this PR since it raise up along with the build. But please let me know if we need to split into another PR. Thank you @alexander-fenster .

It's OK to have it here. Thank you!


Linked List: Add Two Numbers in Go

https://leetcode.com/problems/add-two-numbers/

I can do this!

I can do this!

Sure, go ahead @alecswift


Add check for long lines to extensions#whitespace

Check for lines > textwidth, disabled by default.
I choose to leave it disable by default to not change the current behaviour of vim-airline. Documentation is updated.

thanks.


feat: re-export google protos from tendermint_proto

Description
Re-exporting Google protos from tendermint_proto because I couldn't properly upgrade ibc-proto-rs to v0.48.0 in ibc-rs. Starting with v0.48, ibc-proto-rs no longer includes WKT types, which forces ibc-rs to add a tendermint-proto dependency in several crates. We're trying to decouple ibc-rs from the tendermint-rs crates (except for the ICS-07 Tendermint light client), so this feels like a step back. Ideally, ibc-rs should stay only dependant on ibc-proto-rs.
In the future, if tendermint-proto is split into a separate repository and the IBC core proto types are decoupled from the tendermint-proto dependency as well, we achieve full separation and avoid any potential dependency conflicts in ibc-rs. Though it's not urgent now, stating it as a longer term goal.

Thanks for the PR and sorry for the oversight!

Perhaps in the future we should consider extracting these wkt protos into their own crate, much like prost-types or prost-wkt.

Perhaps in the future we should consider extracting these wkt protos into their own crate, much like prost-types or prost-wkt.

Makes sense to me.


OpenAMP behaves differently for make and cmake when compiling for armv7-m

There is no problems when building with cmake for armv7-m targets, but the same configuration doesn't work with make:
./tools/configure.sh nucleo-h745zi:nsh_cm7_rptun
make -j
...
LD: nuttx
arm-none-eabi-ld: /home/raiden00/git/RTOS/nuttx/nuttx/staging/libopenamp.a(remoteproc_virtio.o): in function `metal_io_read':
/home/raiden00/git/RTOS/nuttx/nuttx/include/metal/io.h:252: undefined reference to `__atomic_load_8'
arm-none-eabi-ld: /home/raiden00/git/RTOS/nuttx/nuttx/staging/libopenamp.a(remoteproc_virtio.o): in function `metal_io_write':
/home/raiden00/git/RTOS/nuttx/nuttx/include/metal/io.h:290: undefined reference to `__atomic_store_8'
make[1]: *** [Makefile:197: nuttx] Error 1

The problem doesn't occur for armv8-m targets:
./tools/configure.sh nrf5340-dk:rptun_cpunet
make -j
...
LD: nuttx
CP: nuttx.hex
CP: nuttx.bin

it's strange that cmake and make generate the different result with the same config.

Yes, the same config. I also replaced the generated .configs but the problem persists. So there must be a subtle difference in the build systems somewhere.

The cmake does not add the implementation of toolchain atomic support: https://github.com/apache/nuttx/pull/9760,
from the break log, maybe armv7-m does not support 64-bit atomic

I have a workaround for arch armv7-m to disable toolchain atomic:
$ git diff --cached
diff --git a/openamp/libmetal.defs b/openamp/libmetal.defs
index d2df7b5b6a..8e906bd952 100644
--- a/openamp/libmetal.defs
+++ b/openamp/libmetal.defs
@@ -67,9 +67,14 @@ LIBMETAL_HDRS_SEDEXP := \
         s/@PROJECT_SYSTEM_UPPER@/nuttx/g; \
         s/@PROJECT_PROCESSOR_UPPER@/$(LIBMETAL_ARCH)/g; \
         s/@PROJECT_MACHINE_UPPER@/$(CONFIG_ARCH_CHIP)/g; \
+
+ifeq ($(CONFIG_ARCH_ARMV7M)$(CONFIG_ARCH_ARMV6M),y)
+LIBMETAL_HDRS_SEDEXP += \
         s/cmakedefine HAVE_STDATOMIC_H/include <nuttx\/compiler.h>/g; \
-        s/defined(HAVE_STDATOMIC_H)/defined(CONFIG_HAVE_ATOMICS)/g; \
-        s/cmakedefine/undef/g"
+        s/defined(HAVE_STDATOMIC_H)/defined(CONFIG_HAVE_ATOMICS)/g;
+endif
+
+LIBMETAL_HDRS_SEDEXP += s/cmakedefine/undef/g"

 ifeq ($(wildcard libmetal/.git),)
 libmetal.zip:

This issue is not fixed.

Is it possible that the cmake build uses different optimization settings? Maybe it is linked to this issue #12489.
The nrf5340-dk:rptun_cpunet builds well with make using -Os


[Bug] CurrFieldNo global variable is readonly and stay 0 when field is modifed from code

Hi,
We have the following problem : when field value is validated from RTC/Web client then CurrFieldNo variable contains current field no., if field value is validated from code then CurrFieldNo stays 0.
C/AL [working]
SomeRec.CurrFieldNo := 10;
SomeRec.Validate(Quantity,1): // inside validate function if CurrFieldNo = 10 then do smth
AL[failed]
SomeRec.CurrFieldNo := 10;
SomeRec.Validate(Quantity,1): // inside validate function if CurrFieldNo = 10 then do smth
During publishing the following error appears error CS0200: Property or indexer 'Microsoft.Dynamics.Nav.Runtime.Extensions.NavRecordExtension.CurrFieldNo' cannot be assigned to -- it is read only
The possible solution: allow to set CurrFieldNo value from AL

Thank you for your request. We are currently setting up the process around handling of issues in this new GitHub repository and you should hence expect a short delay in the processing of this request. But we will be on your case shortly!


Update Remove-TenantAllowBlockListSpoofItems.md

Docs Build status updates of commit 0a08483:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md
:white_check_mark:Succeeded
View (exchange-ps)

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

Docs Build status updates of commit 4c216fd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md
:white_check_mark:Succeeded
View (exchange-ps)

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

Docs Build status updates of commit 9c2bbd2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Remove-TenantAllowBlockListSpoofItems.md
:white_check_mark:Succeeded
View (exchange-ps)

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


Registration of kwargs in the plugin

Hi,
I used to run a piece of code 1 month ago to compute rolling OLS.
I tried to run the code again today after updating to polars_ols 0.3.3 and polars 0.20.25.
I get the following error:
"Compute error: the plugin failed with message: invalid operation: could not parse kwargs: 'decoding error: invalid type: sequence, expected usize'
Check: registration of kwargs in the plugin."
I am able to run the rolling OLS tests locally. Not sure what's going on here.
Thanks,
Adrien

I inputted a parameter as a tuple, my bad


Problem with backups

error.log
Hello to you.
I have had a problem with Backups for some time. and it's still blinding this bland. the database agrees with dbtables -> although mine is more extensive than the original one.
Greetings to the team

Do You have set privileges to includes/backups path for www-data linux account?
Beware, don't set too much privileges to avoid users download whole database from backup ;)

probably rather not ... Server I have on VPS, so the confession is not a bit harder for me to do than on the lan I did ...

Problem solved

@Nusuminat what was the problem?

Hello, Jana
I have or maybe I do not have a problem anymore ... The problem was that with a cron or even from the admin panel it was not possible to create a backup.
I solved the problem in this way: chmod -R 777 backups to the directory I gave the .htaccess file
But I do not know if this is a good solution, but only so I will start to copy the database to the VPS server.


Support AliasPath for alias

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
It'd be nice to have support for Field(alias=AliasPath(...)). Use case: Reading from nested configuration files.
class MyConfig(BaseModel):
    my_str: str | None = pydantic.Field(
        alias=pydantic.AliasPath("level1", "level2", "my_str"),
    )

This actually already works but doesn't seem to be officially supported according to the type hints.
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[X] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Selected Assignee: @lig

@jonashaag thanks for your suggestion! It sounds like a useful feature to have.

This actually already works but doesn't seem to be officially supported according to the type hints.

Could you please elaborate on the above? A working example would be really useful.

Example:
import pydantic

class MyConfig(pydantic.BaseModel):
    my_str: str | None = pydantic.Field(
        alias=pydantic.AliasPath("level1", "level2", "my_str"),
    )

m = MyConfig.model_validate({"level1": {"level2": {"my_str": "a"}}})

Of course this does not handle serialization.

Neither does alias/serialization_alias support AliasChoices/AliasPath (I don't think there's any possible way to "deconstruct/revert" it). That may be why the type hint for alias is str

Closing this - I don't think it makes sense to support this bc, as @Viicos mentioned, you can't easily decouple alias and serialization_alias.


Proposal for common .NET tokenization library

@NiklasGustafsson see https://github.com/fslaborg/FsLab/discussions/6

I suggest with sufficient feedback, we have two tokenization libraries. NOT ONE SINGLE Common tokenization library. One dedicated to adhere as closely as possible to the HuggingFace and the other will be called the e.g. common tokenization library.

We are now sorting out here, please join the discussion
The list of tokenizers considered in TorchText.Data Utils.cs are

spacy
moses ( perhaps fast-mosestokenizer )
toktok
revtok
subword (SentencePiece as used in Seq2SeqSharp)

Please, take a look at https://github.com/microsoft/BlingFire for tokenization

@NiklasGustafsson   here is a good source of HuggingFace tokenizers [Maintained by Microsoft!!!]  => Thanks @aorgish for sharing.

This will be addressed outside the scope of TorchSharp.


FIX: Import location of HF hub errors

Resolves #2097
This fix should make the import of the huggingface_hub error work with older versions of that package.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


CoreFoundation: ensure that we do not overflow the dest

This memcpy could potentially overflow if the source was smaller than
the destination.  We now trim this to the minimum of the source and dest
(similar to strlcpy).

@swift-ci please test

@parkera @tkremenek I would like to nominate this for 5.5 as well.


User Guide: use the attached pdf as the initial user guide

ezEMLmotherOverview.pdf

Added a link to this pdf on the user guide page.  Commit number #97


Move notebook storage related code into separate folder

For #12189
Move into separate folder for easier refactoring (separate PR)
To be reviewed after https://github.com/microsoft/vscode-python/pull/13143

Codecov Report

Merging #13144 into master will decrease coverage by 0.02%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##           master   #13144      +/-   ##
==========================================
- Coverage   59.63%   59.60%   -0.03%
==========================================
  Files         672      672
  Lines       36803    36803
  Branches     5170     5170
==========================================
- Hits        21946    21937       -9
- Misses      13758    13764       +6
- Partials     1099     1102       +3

Impacted Files
Coverage Δ

...ient/datascience/interactive-ipynb/nativeEditor.ts
8.44% <0.00%> (ø)

...datascience/notebookStorage/nativeEditorStorage.ts
68.59% <ø> (ø)

...science/notebookStorage/notebookStorageProvider.ts
51.72% <ø> (ø)

...datascience/interactive-common/notebookProvider.ts
53.01% <100.00%> (ø)

...ience/interactive-ipynb/nativeEditorViewTracker.ts
87.80% <100.00%> (ø)

...tascience/interactive-ipynb/trustCommandHandler.ts
80.39% <100.00%> (ø)

...ractive-window/interactiveWindowCommandListener.ts
55.96% <100.00%> (ø)

src/client/datascience/notebook/contentProvider.ts
50.00% <100.00%> (ø)

...rc/client/datascience/notebookStorage/baseModel.ts
64.95% <100.00%> (ø)

...atascience/notebookStorage/nativeEditorProvider.ts
16.90% <100.00%> (ø)

... and 5 more

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 39f2419...bcb1260. Read the comment docs.


[dv,top-level] Tighten chip_sw_pwrmgr_random_sleep_power_glitch_reset

Reduce the delay for main glitch reset so it doesn't end up occurring past the concurrent normal or deep sleep resets, or the test setup cannot handle the situation and ends up without a way to wake up the device.
Signed-off-by: Guillermo Maturana<EMAIL_ADDRESS>

@matutem does this fix resolve the SVA issue in https://github.com/lowRISC/opentitan/issues/14164?

@jeoongp , the SVA issue was fixed in https://github.com/lowRISC/opentitan/pull/16454.


Links/Samples where language auto-detection doesn't work

This issue is just to enumerate samples and things where auto-detect didn't work and why. There's likely not much that can be done beyond totally retraining the ML model... but at least we can have them in one place.
https://www.programiz.com/python-programming/examples/add-number

I've had trouble getting Python code to be recognized. For example, using code from this example site, this code remains plain text:
# Import re module
import re

# Take any string data
string = input("Enter a string value: ")
# Define the searching pattern
pattern = '^[A-Z]'

# match the pattern with input value
found = re.match(pattern, string)

# Print message based on the return value
if found:
  print("The input value is started with the capital letter")
else:
  print("You have to type string start with the capital letter")

Extension-less bazel BUILD files are detected as either Python, Javascript, Julia or Lua.
Example BUILD file:
load("//tooling/bazel:defs.bzl", "stage", "codeowners", "ecs_deploy")

stage(
    name = "stage",
    base_prefix = "{PROJECT_NAME}/{STAGE_NAME}/{PROJECT_BASE_HREF}",
    files = glob(["out/**"]),
    stamp = [
        "NODE_NAME",
    ],
    tags = ["manual"],
)

ecs_deploy(
    name = "deploy",
    images = [
        "//products/docker:container_image_push",
    ],
    tags = [
        "manual",
        "post_release_task",
    ],
)

Also, files.associations are not respected for extension-less files. It sometimes resolves the correct language but it will default back to Python 90% of the time. This does not work:
"files.associations": {
  "BUILD": "bazel"
},

I love the feature, but I had to turn it off because files.associations could not correctly enforce the lang.
"workbench.editor.languageDetection": false

@dapullar already fixed for 1.60.1. Thanks for reporting though!

This SCSS detects as CSS and doesn't recognize @mixin  or @include
https://github.com/angular/components/issues/7162#issuecomment-493953159

As discussed, here's another example, this time of HTML that VS Code thinks is an INI file.
Curiously, it flashes up HTML in the status-bar section, before changing to Ini, but that might just be because my previous window had already been manually corrected to HTML.

initially reported by @Charles-Gagnon

Open new untitled editor
Type in a T-SQL query such as SELECT * FROM sys.databases

The language auto detection identifies this as a Dockerfile instead of SQL

Oftentimes when I'm writing plain text, VS Code suddenly detects it as one or the other programming language, even though the result doesn't make sense in the detected language.
As an example, I typed the following (I did a replace of [a-z] with s before posting here):
ssss sssssss sss ssss-ssssssss ssss -> sssssss ssssssss? (sss sss ssssssssssss sssss)
sssss ssss ss ssssssss, ssss ssss & sssss ssss sss ss ssss: ssssssssssss ssssssss ss ss?

which was detected as JavaScript by VS Code, even though that results in 22 JavaScript syntax errors.

ренессанс страхование обращайтесь в автосалон is treated as INI, reported in https://github.com/microsoft/vscode/issues/150873

JS code containing Japanese comments is often recognized as an INI file.

// ゲームパラメータオブジェクト
const gameParameters = {
  ui: {
    alwaysVisible: {
      /** ストレスゲージ */
      stressGauge: 0,
    },
    /** 満腹感％ */
    satiety: 0,
    /** 鎮痛剤の血中濃度％ */
    analgesicBloodLevel: 0,
    /** プレイヤー会話成功率％ */
    playerConversationSuccessRate: 0,
  },
};

i copied from gpt
const { desktopCapturer } = require('electron').desktopCapturer;
const { nativeImage } = require('electron').nativeImage;

function captureScreenshot() {
  desktopCapturer.getSources({ types: ['screen', 'window'] }).then(async sources => {
    for (const source of sources) {
      try {
        // 获取屏幕截图
        const image = await source.thumbnail.toPNG();
        // 将Buffer转换为NativeImage
        const nativeImg = nativeImage.createFromBuffer(image);
        // 将NativeImage转换为Base64编码的字符串
        const screenshot = nativeImg.toDataURL();

        // 在前端展示图片
        displayImage(screenshot);
      } catch (e) {
        console.error(e);
      }
    }
  });
}

function displayImage(screenshot) {
  // 假设你有一个<img>元素在HTML中，id为"screenshot"
  const imgElement = document.getElementById('screenshot');
  imgElement.src = screenshot;
}

// 调用函数进行截图
captureScreenshot();

// 添加一个方法来获取截图
async function captureScreen() {
  const sources = await desktopCapturer.getSources({ types: ['screen'] });
  const screen = sources[0];

  const image = await desktopCapturer.captureScreen({
    sourceId: screen.id,
    thumbnailSize: { width: 800, height: 600 }
  });

  return image;
}
//渲染进程
const { ipcRenderer } = require('electron');

document.getElementById('captureButton').addEventListener('click', async () => {
  const image = await ipcRenderer.invoke('capture-screen');

  if (image) {
    const canvas = document.getElementById('screenshotCanvas');
    const ctx = canvas.getContext('2d');

    const img = new Image();
    img.onload = () => {
      canvas.width = img.width;
      canvas.height = img.height;
      ctx.drawImage(img, 0, 0);
    };
    img.src = image.toPNG();
  }
});

// 在 Electron 12+ 版本中，你需要注册一个处理程序来响应 IPC 请求
ipcRenderer.handle('capture-screen', async (_, ...args) => {
  const mainProcessImage = await captureScreen();
  return mainProcessImage;
});

auto: Groovy
fact: js
sometimes: ini

JSON snippets, longer than few lines are always classified as ini.
    "state": {
      "서명_탭": "선택되지_않음",
      "서명_설정_폼": {
        "서명_설정_이벤트": "대기"
      },
      "서명_문서": "문서_이미지_로딩_완료"
    }