'React/RCTBridgeDelegate.h' file not found

Same error for the demo AwesomeProject.
react-native info:
info Fetching system and libraries information...
System:
OS: macOS 10.14.6
CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
Memory: 1.15 GB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.6.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
Android SDK:
API Levels: 23, 28, 29
Build Tools: 28.0.3, 29.0.1
System Images: android-28 | Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>92245
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.4 => 0.60.4
npmGlobalPackages:
react-native-cli: 2.0.1

Greetings, I am having a similar issue:
System:
    OS: macOS High Sierra 10.13.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 1.26 GB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 11.10.1 - /usr/local/bin/node
    Yarn: 1.10.1 - /usr/local/bin/yarn
    npm: 6.7.0 - /usr/local/bin/npm
    Watchman: 4.7.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    Android SDK:
      API Levels: 23, 25, 26, 27, 28
      Build Tools: 23.0.1, 26.0.2, 27.0.3, 28.0.3
      System Images: android-28 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.4 => 0.60.4
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

This is my ios/NFIBEngage/AppDelegateh file:
/**
 * Copyright (c) Facebook, Inc. and its affiliates.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

#import <React/RCTBridgeDelegate.h>
#import <UIKit/UIKit.h>

@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

The error is telling me it can't find that import:
AppDelegate.h:8:9: fatal error: 'React/RCTBridgeDelegate.h' file not found
#import <React/RCTBridgeDelegate.h>

Duplicate https://github.com/facebook/react-native/issues/25707 ?

@slavikdenis , this:
Solution:
-Install Cocoa Pods
sudo gem install cocoapods
-In your Project Folder:
cd ios
pod install
is not a solution. I already have Cocoapods installed and ran pod install. In fact, the error I have above is what I got after I added new Targets to my XCode and ran a pod deintegrate cleaned the XCode and rebuilt it and then refactored the Podfile and then successfully ran pod install.
Afterwards, when I ran react-native run-ios, thats when I started getting the following error:
AppDelegate.h:8:9: fatal error: 'React/RCTBridgeDelegate.h' file not found
#import <React/RCTBridgeDelegate.h>

The file does indeed exist in my Pods/Headers/Public directory inside of the React/ folder that is inside of React-Core/. Any help would be appreciated. Here is the MVP that looks similar to what I have:
https://github.com/ldco2016/NFIBEngage
And this is the Podfile configuration it needs:
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'DEV' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for DEV
  # pod 'AppCenter/Push', '~> 1.3.0'
  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'

  # Pods for NFIBEngage
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

  target 'NFIBEngageTests' do
    inherit! :search_paths
    # Pods for testing
  end

  use_native_modules!
end

target 'NFIBEngage-tvOS' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for NFIBEngage-tvOS

end

target 'PROD' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for PROD
  # pod 'AppCenter/Push', '~> 1.3.0'
  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'

  # Pods for NFIBEngage
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

end

target 'QA' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for QA
  # pod 'AppCenter/Push', '~> 1.3.0'
  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'

  # Pods for NFIBEngage
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

end

target 'UA' do
  # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
  # use_frameworks!

  # Pods for UA
  # pod 'AppCenter/Push', '~> 1.3.0'
  pod 'AppCenter/Crashes', '~> 2.0.1'
  pod 'AppCenter/Analytics', '~> 2.0.1'
  pod 'AppCenterReactNativeShared', '~> 2.0.0'

  # Pods for NFIBEngage
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/React'
  pod 'React-DevSupport', :path => '../node_modules/react-native/React'
  pod 'React-fishhook', :path => '../node_modules/react-native/Libraries/fishhook'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-RCTWebSocket', :path => '../node_modules/react-native/Libraries/WebSocket'

  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'

  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

end

If anyone can add the above configuration to that MVP and then run react-native run-ios and not get this error:
AppDelegate.h:8:9: fatal error: 'React/RCTBridgeDelegate.h' file not found
#import <React/RCTBridgeDelegate.h>

that is what I am trying to accomplish myself.

After install pod also not working same error occured
act/RCTBridgeDelegate.h' file not found
#import <React/RCTBridgeDelegate.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

@ldco2016 well, for me it somehow worked. Please let us know, if you find the solution for your problem. Thanks

So is this not a bug with React Native? A lot of people are reporting this same behavior.

I see “scheme” in Xcode shows React(missing)

I see “scheme” in Xcode shows React(missing)

Did you find a solution for missing React in "scheme" ?

Facing the same problem "'React/RCTBridgeDelegate.h' file not found".

You can fix this issue by installing the missing dependencies using pods.
These are the steps you should follow:
cd ios pod install
After that, re-run the project. It should build with no errors.

You can fix this issue by installing the missing dependencies using pods.
These are the steps you should follow:

cd ios
pod install

After that, re-run the project. It should build with no errors.

I see “scheme” in Xcode shows React(missing)
Did you find a solution for missing React in "scheme" ?
did you?

I change the version from 0.60 to 0.59.10

Is it a bug with v0.60? I am using 0.60.5.

I see “scheme” in Xcode shows React(missing)
Did you find a solution for missing React in "scheme" ?
did you?

I change the version from 0.60 to 0.59.10

Is it a bug with v0.60? I am using 0.60.5.

Same Version and same issue here as well!

@iamawaisakram any solution?

in Header Search Paths you should add $(inherited). This has solved the problem for me. And if you would look at warnings after pod install it does indicate that.

@dvuvne solutions solved my problem

in Header Search Paths you should add $(inherited). This has solved the problem for me. And if you would look at warnings after pod install it does indicate that.

Followed these steps still throw the same error.

If you have React missing in in your scheme, you have to add React.xcodeproj  manually.

On your Project Navigator (left panel with folders):

Click with two finger for the menu (anywhere).
Choose Add Files to "YOUR PROJECT NAME"
Navigate to node_modules/react-native/React and choose React.xcodeproj.
Clean your project and re-run.

Note: React.xcodeproj was removed from 0.61.

Facing the same problem "'React/RCTBridgeDelegate.h' file not found".
Quick fix:
$ cd ios && pod install

@AshishKapoor it works, just need install pods.

You can fix this issue by installing the missing dependencies using pods.
These are the steps you should follow:
* cd ios

* pod install

After that, re-run the project. It should build with no errors.

This fixed issue for react native v. 0.61 and xcode v. 11.0 (11A420a)

Same issue here with RN61 - mission React
pod install does not help

The same issue here when upgrading from RN59.5 to RN0.61.1.

Installing cocoa pods then installing the missing dependencies with pods sorted the issue for me here are the steps to follow:

sudo gem install cocoapods
cd ios
pod install

Close any current xcode sessions.
Close any current open simulators.
Then restart your app again

pod install in ios dir giving me ".../bin/bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory"
macos catalina 10.15 (19A602)

I still have this problem in React Native Navigation files ( any "React/..." ). A workaround I have found is changing all <React/XXXX.h> in 'XXXX.h` but I don't think it will work properly.
I have tried to add React to Schemes ( also if it shouldn't be required with 0.61...right? ), delete Derived Data, run pod install and many other things.
Is there anyone who figured it out?

Same problem. Should React .xcodeproj have been removed when library imports are still looking up to it?

I am having same issue. We're upgrading from 0.59.5 to 0.61.2.
Basically every #import <React/{ModuleName}> is not available - but it is available when requiring just “{ModuleName}”, eg:
#import <React/RCTBridgeModule.h>
# raises /node_modules/react-native-splash-screen/ios/RNSplashScreen.h:9:9: 'React/RCTBridgeModule.h' file not found

#import <RCTBridgeModule.h>
# this works however ^

I tried to start fresh with a new project ( react-native init AwesomeProject ) and then added the libReact Native Navigation  ( that was the library that was giving this issue ).
The build was successful so I tried to import all the pods and all the paths from the Header search path in XCode from there and paste in my project. After that, the problem was gone.
Unfortunately now they give me problems with Mach O-Linker so I think I will create a new project, import all the libraries and then try to make them work in the original one.

pod install does not solve it for me. Has anyone found any other solution?

@damathryx have you tried to do what I did in my last comment? Try to install the library that gives you issues with a fresh project then you should copy all the pods needed.

I had the same problem.
in my case after starting the project,
only installed react-native-camera through pods,
It hasn't worked since then.
So the first reasoning was that only in react-native-camera
I reached this place to find out the cause of the problem
[Experiment 1]
I did one experiment. When I installed the latest version
Is there a React (missing)?
Curiously, already missing existed and was running well.
[Experiment 2]
Then simply didnt set anything(ex- react-native-camera)
I tried and run ios / pod install.
In this case, only the patch worked and it worked fine.
[Experiment 3]
installed react-native-camera
I've added it to the npm install & podfile as described in the manual.
In this case,

Link Binary With Libraries, Header search, etc.
The process was excluded.

[Experiment 4]
when I added link binary with libraries and it failed.
just there was libPods-$ {projectName}.
Then

can I import react-native-camera to code?

Was my question.
So I tried to import
It worked fine.
So my conclusion is this.
Linked Frameworks and Binaries, only the libPods- * project * .a
because already pod installed other pod.
+ but, But I'm not sure it's just my judgment and my case!

roj was removed from 0.61.

What to do for 0.61 ? i m getting the same error

same issue while upgrading from RN 0.59.9 to 0.60.0, any solution? .

Hi guys, as I wrote some days ago, my problem was that React Native Navigation could not find the right pods and dependencies.
The first thing you should do is to detect the library is causing this error: do the files that give you errors belong to some library? If so, have you tried to create a new project with a brand new version of RN and import the guilty library?
I would be very happy to help you since I spent like 4-5 days on it! 😅

If you guys are upgrading from 0.59.10 or below to 0.60.0 or above, the issue seems to be with the manual linked libraries, we need to remove all the manually libraries as show here and we should instead add these manually linked libraries to our podfile for example if you have react-native-vector-icons installed, your pod file with core packages should look something like this
`
target 'YourAppName' do
pod 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
pod 'React', :path => '../node_modules/react-native/'
pod 'React-Core', :path => '../node_modules/react-native/'
pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
pod 'React-Core/RCTWebSocket', :path => '../node_modules/react-native/'
pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
pod 'ReactCommon/jscallinvoker', :path => "../node_modules/react-native/ReactCommon"
pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
pod 'Yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
#Add other pods here
pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'
post_install do |installer|
installer.pods_project.targets.each do |target|
  targets_to_ignore = %w(React yoga)

  if targets_to_ignore.include? target.name
    target.remove_from_project
  end

end

end
end
`
after removing the libraries it should look some thing like this.

At last
cd ios
pod install

i was able to solve this issue following these steps, hope it helps others.

@basha777 This works fine if all of the libraries in your project are compatible with cocoapods, but we still have some libraries that have to be manually linked. Those libraries all still fail with the same errors. Anybody found a workaround for that?

In the end i got it to work by putting this at the top of my podfile. Replace the packages with the ones that are failing for you, of course. It will create a new "project" and until the maintainers update the structure of their packages, it will be stuck.
I also believe i had to manual link the binaries
 workspace './xxxx.xcworkspace'
target 'RNSVG' do
   project '../node_modules/react-native-svg/ios/RNSVG.xcodeproj'
 end

 target 'RNMixpanel' do
   project '../node_modules/react-native-mixpanel/RNMixpanel.xcodeproj'
 end

 target 'RNViewShot' do
   project '../node_modules/react-native-view-shot/ios/RNViewShot.xcodeproj'
 end

I was facing same problem when I added a new target and did a pod install. here is the solution.
My react-native info is as below.
System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
    Memory: 701.86 MB / 12.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.16.3 - /usr/local/bin/node
    Yarn: 1.19.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
    Android SDK:
      API Levels: 22, 23, 24, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 25.0.0, 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.2, 28.0.3, 29.0.0
      System Images: android-19 | Google APIs Intel x86 Atom, android-25 | Google Play Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64
      Android NDK: 19.2.5345600
  IDEs:
    Android Studio: 3.4 AI-183.54<IP_ADDRESS>52501
    Xcode: 10.1/10B61 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.1 => 0.61.1
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-git-upgrade: 0.2.7

Hope it helps to someone

I am getting the above error and also in Xcode Product -> Edit Scheme shows --> React missing.
This is because while runnig the pod install again it removing the react from the Podfile. Kindly refer the attached image.
Anyone have any solution for this?
Also I am getting
failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening app.xcworkspace. Run CLI with --verbose flag for more details.
error Could not find the following native modules: BugsnagReactNative, react-native-camera, react-native-cookies, react-native-fast-image, react-native-fetch-blob, RNImageCropPicker, react-native-image-picker, RNImageRotate, BVLinearGradient, react-native-orientation, RNShare, RNSVG, RNVectorIcons, RNViewShot, react-native-webview, rn-fetch-blob. Did you forget to run "pod install"

Here's what I did to solve this:

cd ios && pod install.
Then go to the same screen (scheme/build)
Delete the React (missing)
click on the + on the bottom left
add React (from pods section).
Finally, check all the checkboxes and place React at the top of the list.

Now I am getting

▸ Running script '[CP] Check Pods Manifest.lock'

❌  error: The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation.

error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening helloworld.xcworkspace. Run CLI with --verbose

@nihp I think you should clean up your pods:

gem install cocoapods-deintegrate
gem install cocoapods-clean
Go to the project ios directory and run pod deintegrate
run pod clean
Run pod install

May you clarify why I am getting this error.
I have fixed this Sandbox error is resolved after removing podfile.lock and pod install
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening helloworld.xcworkspace. Run CLI with --verbose flag for more details.
User defaults from command line:
    IDEDerivedDataPathOverride = /Applications/app/ios/build/helloworld

I would still clean up pods using the steps in my previous comment.
Which command gives you this error ?

I have removed Podfile.lock and then pod install.
Then react-native run-ios
Now the Xcode shows the error which I have asked in the question(file not found)
In terminal it shows the error https://github.com/facebook/react-native/issues/25838#issuecomment-558095737

I will clean my pods and let you know.
I have a question. Shall i need to checkout the changes which is available for podfile.

I have cleaned as per your https://github.com/facebook/react-native/issues/25838#issuecomment-558093699. But again it shows the same error as in terminal and Xcode
Terminal:
error Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening helloworld.xcworkspace. Run CLI with --verbose flag for more details.
User defaults from command line:
IDEDerivedDataPathOverride = /Applications/app/ios/build/helloworld
Xcode: (While compiling AppDelegate.m)
/node_modules/bugsnag-react-native/cocoa/BugsnagReactNative.h:3:9: 'React/RCTBridgeModule.h' file not found

Here's what I did to solve this:

cd ios && pod install.
Then go to the same screen (scheme/build)
Delete the React (missing)
click on the + on the bottom left
add React (from pods section).
Finally, check all the checkboxes and place React at the top of the list.
Did you do this after cleaning pods ?

cd ios && pod install.
Then go to the same screen (scheme/build)
Delete the React (missing)
click on the + on the bottom left
add React (from pods section).
Finally, check all the checkboxes and place React at the top of the list.

Did you do this after cleaning pods ?

@Alaa-Ben I am facing the same error repeatedly. If I run pod install react is added for the first time. For the next run of Pod install, it will delete the React. So the error RCTBridgeDelegate.h arise.
If I add react and then it shows the Sandbox error.
I am facing these two errors and it gets me stuck and not able to build my apps.
Kindly provide any correct solutions with steps which need to fix the above two errors

After cleaning it will shows like below attached image.

Same problem here, pod install did not solve

While there are no solutions yet, I presume, I just downgraded my react-native version at package.json:
rm -rf node_modules/
edit package.json file:
from:
"react-native": "^0.61.4",
to
"react-native": "0.60.0",
and
npm install again.
react-native 0.60 has React.xcodeproj but it's not the correctly solution.

Anyone have any solution

@pedromelo98 In 0.60.0 there is auto-link support or manual link.
Shall I need to create react-native.config.js file here.

Here's what I did to solve this:

cd ios && pod install.
Then go to the same screen (scheme/build)
Delete the React (missing)
click on the + on the bottom left
add React (from pods section).
Finally, check all the checkboxes and place React at the top of the list.

Worked for me, thanks

@thiagofuss Which version of react-native you have upgrade

@nihp FYI, the steps i wrote worked for me when I upgrade from 0.59.10 to 0.61.1

@Alaa-Ben I did like this can you confirm did you do like this or if you have any changes or any steps need to modify kindly let me know.

1. rm -rf node_modules (here I removed rnpm and chnaged the script as per react-upgrader in package.json file
2. npm install
3. run pod install(installed pods)
4. react-native run-ios (shows error need to unlink packages)
5. unlink all packages (now my pod file is empty)
6. Again i run pod install
7. It removed React, ImagePicker packages
8. Now the product ==>Edit scheme for react is missing (There is no list of third party packages in Manage schemes)
9. Then I remove Pods and Podfile.lock (now the podfile not have any packages in its target)
10. I did clean which you mentioned above
11. Again pod install
12. It only added the Frameworks which I added above for Crashlytics and Fabric
13.Then I have reverted the Pod file and run pod install. Again it added all packages and still the issue is there.

Can you tell how the podfile will shows the packages inside target after upgrade and how it will add in Product --> Edit scheme

@Alaa-Ben I still facing the same issues
Above solution not worked for me
/Users/jesphin/work/projects/new_p/App/ios/MyApp/AppDelegate.m:11:9: 'RCTBundleURLProvider.h' file not found

@nihp I don't understand why you pod install twice (I believe step 6 is not needed)

@Alaa-Ben
Now I am facing the same error. While pod install it add 20 dependencies and shows success message.
But react-native run-ios failed with the error.
node_modules/bugsnag-react-native/cocoa/BugsnagReactNative.m:4:9: 'RCTVersion.h' file not found
I have checked the Header Search paths it have the bugsnag.
Any solution for this
I am facing three error one by one
React/RCTBridgeDelegate.h' file not found
React/RCTBundleURLProvider.h file not found
Step 10: Clean the build from Xcode
Step 6: Are you sure after unlinking the packages we not need to run pod install.
Also, I have added use_nativemodules in my podfile.
So the React is not removed after running pod install again.

@Alaa-Ben I created and checked with the another example project. These are my observations with my upgraded and example project
Before the upgrade the Header Seach path is like '(SRCTRoot/../..anypackages) same will be there after upgrade or not?
Because I have generated a new example project to check this. But I can see the difference in the Header search paths "${PODS_ROOT}/Headers/Public/BugsnagReactNative".
Also, I am facing RCTBridgeDelegate.h file and other files with extensions are not found while compiling my upgraded project.
But the example project is working fine. Can anyone suggest how can I isolate and build my existing upgraded app without a runtime error?
Note: Example app has third party packages in podfile but the existing project removed all third party packages while running react-native unlink command.

You clearly failed your migration. The fact that you didn't add use_nativemodules before shows that you didn't add everything you should when migrating. I suggest you check react native upgrader again.

@Alaa-Ben I have added use_nativemodules already it is in my podfile. I not get you what you mean.

Are you mean while migrating all the header path will change. Can you help me how can I do it again to work this. Or need to work entirely new the upgradation process. Can you kindly suggest the steps? Already I have spend lot of time here. I don't want to make any mistake again.

I've already written the steps I did to make it work. If it doesn't work for you, sorry but I have no idea what the problem is :/

Can you confirm how your Header Search Paths are like and provide a sample for me

@Alaa-Ben Can you confirm how the Header Search path is look like before and after upgrade.
In my case both shows the RCTROOT
Before the upgrade the Header Seach path is like '(SRCTRoot/../..anypackages) same will be there after upgrade?

 But I can see the difference in the Header search paths while creating a new example project "${PODS_ROOT}/Headers/Public/BugsnagReactNative".

If it's 0.61. X, I find a solution to this problem!
in Podfile add:
#添加本地封装库
install! 'cocoapods',
:integrate_targets => false#消除警告
workspace 'path/to/Workspace.xcworkspace'
#这里开始描述
target 'RCTHttpCache' do    #Set the plug-in you want to use here!
project '../node_modules/react-native-http-cache/ios/RCTHttpCache.xcodeproj'
end

same problem  rn:0.59

@basha777 your solution WORKED!  Thank you!  That took days to figure out - a diagram goes a long way - it's unbelievable how many people are having this issue and there's not set solution - I hope the good folks running RN take notice.

Check your Scheme by going to Product -> Scheme -> Edit Scheme -> Build
and if you see React(missing) in in your scheme, you have to add React.xcodeproj  manually.

On your Project Navigator (left panel with folders):

Click with two finger for the menu (anywhere).
Choose Add Files to "YOUR PROJECT NAME"
Navigate to node_modules/react-native/React and choose React.xcodeproj.
Clean your project and re-run.

Note: React.xcodeproj was removed from 0.61.

Why dislike him? this is the most logical explanation !!

I have the same error with RN 0.61.5. I removed missing React from my scheme and added React from Pods (see in image above)

I did all things:
rm -rf node-modules
rm -rf ios/Pods
rm ios/Podfile.lock
rm -rf ~Library/Developer/Xcode/DerivedData
and then yarn install + cd ios and pod install
but nothing helps
this is my podfile
platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

def my_deps
  # Pods for Placeholder
  pod 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
  pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
  pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
  pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/'
  pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
  pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-Core/RCTWebSocket', :path => '../node_modules/react-native/'
  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'ReactCommon/jscallinvoker', :path => "../node_modules/react-native/ReactCommon"
  pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
  pod 'Yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'
  pod 'boost-for-react-native', :podspec => 'https://raw.githubusercontent.com/react-native-community/boost-for-react-native/master/boost-for-react-native.podspec'
  # React-Native-Share pod
  pod 'RNShare', :path => '../node_modules/react-native-share'
  pod 'RNFirebase', :path => '../node_modules/react-native-firebase/ios'
  pod 'Firebase/Messaging', '~> 6.3.0'
  pod 'Firebase/Analytics', '~> 6.3.0'

  #target 'PlaceholderTests' do
    #inherit! :search_paths
    # Pods for testing
  #end

end

target 'Placeholder' do
  my_deps
  use_native_modules!
end

target 'Placeholder-tvOS' do
  my_deps
  use_native_modules!
end

#target 'Placeholder-tvOS' do
  # Pods for Placeholder-tvOS
  #target 'Placeholder-tvOSTests' do
    #inherit! :search_paths
    # Pods for testing
  #end
#

Upgrade from react-native 0.5x codebase to 0.61.x is a nightmare If you don't have ios/android library management experience.
I fixed by doing this:
https://github.com/facebook/react-native/issues/26665#issuecomment-571082076

Issue still happening could be fixed by a quick fix ( it works for me locally ) however when i use apppcenter which redownload the original file it doesnt have my fix...
Replace the import in RCTBridgeModule.h for:
#if __has_include("RCTDefines.h") #import "RCTDefines.h" #else #import <React/RCTDefines.h> #endif
Please commit a fix for this :)

In your project file:
rm -rf node_modules
npm install
cd ios
pod install

I added ${PODS_ROOT} recursive in Build Settings -> Search Paths -> Header Search Paths and it worked

I had the same issue, setting higher Deployment Target in the xcode project solved it in my case

My solution in this case.
First I have added React in my scheme because I had React(missing).
After this, I go to the Project -> Info -> Configurations (under Deployment target)

In this menu I found my current target and select correct Pods configurations for each others

Thanks @VladosDosvidos! your solution worked for me.
XCode:11.4
React Native:0.62.2

Me too! Nice one @VladosDosvidos

I followed these steps to fix the issue:

cd ios
pod install
Open .xcworkspace file with Xcode

Let's say you had a Scheme A, you duplicated it to Scheme B
What I found happens when you run npm install is
For every scheme except A,
Build phases settings get changed to default
To fix this unfortunately,
Delete the Scheme B
Duplicate the original scheme(A) again and make the changes to make it your scheme B

I have React with concentric circles, not a React shape of house.
If I add this does it works for me?

If you guys are upgrading from 0.59.10 or below to 0.60.0 or above, the issue seems to be with the manual linked libraries, we need to remove all the manually libraries as show here and we should instead add these manually linked libraries to our podfile for example if you have react-native-vector-icons installed, your pod file with core packages should look something like this
target 'YourAppName' do

  pod 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
  pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"
  pod 'RCTRequired', :path => "../node_modules/react-native/Libraries/RCTRequired"
  pod 'RCTTypeSafety', :path => "../node_modules/react-native/Libraries/TypeSafety"
  pod 'React', :path => '../node_modules/react-native/'
  pod 'React-Core', :path => '../node_modules/react-native/'
  pod 'React-CoreModules', :path => '../node_modules/react-native/React/CoreModules'
  pod 'React-Core/DevSupport', :path => '../node_modules/react-native/'
  pod 'React-RCTActionSheet', :path => '../node_modules/react-native/Libraries/ActionSheetIOS'
  pod 'React-RCTAnimation', :path => '../node_modules/react-native/Libraries/NativeAnimation'
  pod 'React-RCTBlob', :path => '../node_modules/react-native/Libraries/Blob'
  pod 'React-RCTImage', :path => '../node_modules/react-native/Libraries/Image'
  pod 'React-RCTLinking', :path => '../node_modules/react-native/Libraries/LinkingIOS'
  pod 'React-RCTNetwork', :path => '../node_modules/react-native/Libraries/Network'
  pod 'React-RCTSettings', :path => '../node_modules/react-native/Libraries/Settings'
  pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text'
  pod 'React-RCTVibration', :path => '../node_modules/react-native/Libraries/Vibration'
  pod 'React-Core/RCTWebSocket', :path => '../node_modules/react-native/'
  pod 'React-cxxreact', :path => '../node_modules/react-native/ReactCommon/cxxreact'
  pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi'
  pod 'React-jsiexecutor', :path => '../node_modules/react-native/ReactCommon/jsiexecutor'
  pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector'
  pod 'ReactCommon/jscallinvoker', :path => "../node_modules/react-native/ReactCommon"
  pod 'ReactCommon/turbomodule/core', :path => "../node_modules/react-native/ReactCommon"
  pod 'Yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'DoubleConversion', :podspec => '../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec'
  pod 'glog', :podspec => '../node_modules/react-native/third-party-podspecs/glog.podspec'
  pod 'Folly', :podspec => '../node_modules/react-native/third-party-podspecs/Folly.podspec'

#Add other pods here

  pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons'

  post_install do |installer|
    installer.pods_project.targets.each do |target|

      targets_to_ignore = %w(React yoga)

      if targets_to_ignore.include? target.name
        target.remove_from_project
      end

    end
  end

end

after removing the libraries it should look some thing like this.

At last
cd ios
pod install

i was able to solve this issue following these steps, hope it helps others.

save my life <3

I see “scheme” in Xcode shows React(missing)

I could solve this upgrading my Cocoapods version (1.5.3 to the 1.9.3). Then, after a pod deintegrate && pod install, in Xcode > Scheme > Edit Scheme remove the React (missing) target and add the React with the target icon:

I have React with concentric circles, not a React shape of house.
If I add this does it works for me?

Clean and build your project and will fix the React related errors.

@sanukumarNS Yes, your advice is also useful. Because I have two schemas in my project.

Still getting this error when archiving, on React 63.2

1+ year later and this still persist. Unfortunately this client doesn't want to move to Flutter yet

In my experience, if you happen to install and uninstall the wrong npm package, for example, you may irreversibly mess up your React Native project. The likely culprit is that some small - yet critical - library is removed on uninstall. In these cases, a total rebuild of the project is required. Would be nice if there's a way to restore or rollback to a previous state.

I have this problem after creating a brand new react-native project. I've gone through the miscellaneous suggestions in this thread, like running pod install, etc. Interestingly enough, I zipped up the entire project and transferred it to a friend's computer running the exact same version of Xcode (12.0.1). It built first try, with zero changes to the project or config. I'm wondering if the problem could be caused by an Xcode setting?

Updating from rn0.62 to 0.63, dont forget to include every schema in your pods. Otherwise the pods will only work for the one main schema.
https://github.com/react-native-community/upgrade-support/issues/55

here is what I did to fix this issue:

cd ios && xcodebuild clean
pod init (if you don’t have podFile already)
pod install

Embarrassed to say I fought this problem for over an hour, eventually realizing that several commits earlier, I had deleted the tvOS targets in XCode without deleting the targets in the Podfile. This caused an error during pod install, but the phrasing of the error didn't make it clear that the pod install hadn't actually completed.
Thus, although I kept thinking I was running pod install, it wasn't actually happening, which resulted in this React/RCTBridgeDelegate.h' problem.
I doubt very much anyone else here is making such a silly mistake, but I thought I'd share anyway.

Hurray!
After having troubles for multiples hours, I fixed my issue.
When going in Edit Scheme > My Scheme, I had React (missing).
I added React back (click [-] on React, click [+], search React), then I still had this error. 🤔
Then, I saw a comment that said that React must be at the top of the list (it got added on the bottom).
I moved React to the top of the list, and now the error disappeared. 🎉
But now I have ReactNativeNavigation.h not found 😂

This solution was solved my problem
joltup/rn-fetch-blob#461 (comment)

I'm currently on a lower version than react-native .60 so do not make use of pods.
I had to remove the podfiles and uninstall pods with
pod deintegrate project.xcodeproj

Definitely, not the greatest solution and is not applicable to everyone, however, these are the steps that helped me in my situation:

Remove the project repository
Clone it from the remote repository
Navigate to the project folder
npm install
cd ios
pod install
npm run ios

I had the same issue, setting higher Deployment Target in the xcode project solved it in my case

Great find, my podfiles deployment target was 11.0 and my projects was set to 10.0. Thanks.

would you guys/gals PLEASE stop suggesting pod install - jesus.


Autocomplete - Add option 'required'

In the autocomplete component we need to provide the ability to have an extra attribute called required.
By default set to false and the user can change to true.
The input field will be rendered with a required attribute, see W3C required attribute definition.
required?: boolean

Please create your branch from release/0.5
git checkout release/0.5
git pull
git checkout -b 'feature/autocomplete-required'

#308 closed the following ticket


STM32L496G_DISCO uart testing fails on single buffer read

Describe the bug
I want to use UART DMＡ　to receive data on STM32L496G_DISCO board. So I build the uart_async_api and flash download to the board. The following is the error message.
*** Booting Zephyr OS build v2.7.0-rc1-36-g0552d329c88c  ***
Running test suite uart_async_test
===================================================================
START - test_single_read_setup
 PASS - test_single_read_setup in 0.1 seconds
===================================================================
START - test_single_read
E: Unimplemented system call
E: r0/a1:  0x00000000  r1/a2:  0x00000000  r2/a3:  0x00000000
E: r3/a4:  0x00000000 r12/ip:  0x00000000 r14/lr:  0x00000000
E:  xpsr:  0x00000000
E: Faulting instruction address (r15/pc): 0x2cc393b8
E: >>> ZEPHYR FATAL ERROR 3: Kernel oops on CPU 0
E: Current thread: 0x20001000 (test_single_read)
E: Halting system

To Reproduce
west build -b stm32l496g_disco zephyr/tests/drivers/uart_async_api
west flash
Expected behavior
UART DMA with rx, tx should be working without errors .
Environment (please complete the following information):
Hardware:STM32L496G_DISCO
Linux Ubuntu 20.04.3 LTS
Zephyr SDK,-0.13.0
Zephyr SHA1 ID:bb85a55

@glin00 could you please detail the UART instance you are using and the corresponding pins on the disco board
It is important to add the uart of this board in thetests/drivers/uart/uart_async_api/src/test_uart.h
to connected Tx and Rx pins on the board
and to configure the DTS for the test case with a  tests/drivers/uart/uart_async_api/boards/stm32l496g_disco.overlay
Depending on the uart, the dma request is specified for a DMA channel of a DMA instance (1 or 2)
(like it is done for the disco_l475_iot1 board)

Because of the drivers/serial/Kconfig.stm32, the UART_ASYNC_API requires a DMA

@glin00 Is this issue still active ?

@glin00 please reopen if required.


Local config is needed

Some of the config settings are not general enough to submit into a repository but still important to keep in a local setting environment.
Examples:

Cloud storages can be set up locally, not globally.
A stage that user would like to lock. DVC files and config is probably not the best place for that.

Possible solution: store a local config .dvc/config.local which can overwrite (global) config settings and is ignored by Git.

After a bit more thinking and tinkering, I think that we should not hurry with it and leave it for consideration after the 0.9.0 release. If we do decide to implement this later, there will be no problem with backward compatibility. Closing for now.

This is going to be essential for #596 . Already working on it.


Fixed syntax in example under "Environment Namespaces" section

Fixed code syntax for it to work with Lua (5.2.4)

Either this is because of version difference, or you shouldn't forget to run your example code to make sure that at least its syntax is correct. :)

Whoops :sweat_smile:
Thank you!


Mojibake problem: ¿

Hi,
Think this one is not possible, but here it is:
U+00BF  ¿       [Po] INVERTED QUESTION MARK
SHOULD BE:
U+2011  ‑       [Pd] NON-BREAKING HYPHEN

But then in other texts:
U+00BF  ¿       [Po] INVERTED QUESTION MARK
SHOULD BE:
U+0027  '       [Po] APOSTROPHE
Or maybe:
U+2019  ’       [Pf] RIGHT SINGLE QUOTATION MARK

Example:

of UC¿TM
zo¿n beetje alle camera¿s

The second one is a huge issue, because almost all plural forms of a thing uses the quotation+s syntax in Dutch.
Is it possible to fix this?

There's probably too little information to fix this string, but I'm leaving this one open so I can try to figure out what combination of encodings made this happen.


Update test_thumbnail.py

this updates the updated functionality for the new UI zulip#23739

@rahulkoul123 please read our contributing guidelines and Git guide before opening pull requests.


Add version info to hashstore lib

Version is available in the pyproject.toml but not in code.
Suggest adding __version__ = '1.0.0' to hashstore/__init__.py and managing version info using poetry, and report the version number in the cli.
e.g. add to pyproject.toml:
[tool.poetry_bumpversion.file."src/hashstore/__init__.py"]

Then install bump_version in your local poetry environment and manage versions like:
$ poetry version patch

To update the patch etc release number.

This has been completed via the following commits in feature-133-release-prep which will be merged into develop:

Add poetry bump version code to 'pyproject.toml'
Update version to '1.1.0' via 'poetry version minor'


mistralai[patch]: Do not swallow errors

Do not swallow errors when streaming with httpx.
Update affected code if this PR gets merged to httpx: https://github.com/florimondmanca/httpx-sse/pull/25/files

Looks like we actually should consume the text in the response since that contains the full error message from the server. I'll update the code here in a bit.


[Feature Request] Enable use of gamepad in desktop mode

Currently when switching to desktop mode, the gamepad becomes unresponsive and plugging in a mouse/keyboard is required.
It would be great to have a thumbstick move the mouse cursor, and trigger buttons represent left and right click.
Not to mention having a way to bring up an on-screen keyboard with the gamepad.
I'm thinking the same way it works when switching to KDE in SteamOS on the Steam Deck.

This is a WIP. We're currently developing a new global input manager that would handle this.


feat(cli): early return on static generation with --fail-on-error

static generation with command nuxt generate --fail-on-error exits when the first error occurs.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Description

The command nuxt generate --fail-on-error returns error after all routes generation has completed even with 10,000+ routes.
However even if only 1 error occurs with any other generation succeeded the command will fail.
Thus, the command should exit early when the first error occurs.
In detail I have changed to return after the concurrency encountered the first error.
This change will save the time of user.(Resolves: #9704)
Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

I've tried to execute nuxt generate --fail-on-error with my commits locally but I can't and don't know how to do it.
any comments are appreciated!

Codecov Report

Merging #9762 (6b619e3) into dev (2ef0537) will decrease coverage by 0.00%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##              dev    #9762      +/-   ##
==========================================
- Coverage   65.17%   65.16%   -0.01%
==========================================
  Files          94       94
  Lines        4109     4111       +2
  Branches     1127     1129       +2
==========================================
+ Hits         2678     2679       +1
- Misses       1152     1153       +1
  Partials      279      279

Flag
Coverage Δ

unittests
65.16% <66.66%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

packages/cli/src/commands/generate.js
89.18% <ø> (ø)

packages/cli/src/utils/generate.js
0.00% <0.00%> (ø)

packages/generator/src/generator.js
82.19% <80.00%> (-0.30%)
:arrow_down:

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 2ef0537...6b619e3. Read the comment docs.

@clarkdo thanks for your suggestion! I'll try to implement it.
BTW, my previous commits comments are not semantic and occurs CI error.
so I close this PR and re-issue with new implement.


fix(TaskQueue): handle middle future dropped while permit acquired

Was looking at the code more and spotted this bug.

Published as 0.2.1


4n6time not working

On SIFT 3.0, 4n6time doesn't seem to start up on either an up-to-date sift-bootstrap or the appliance.
e.g.,
$ 4n6time
WARNING: file already exists but should not: /tmp/_MEI1rJccH/etc/matplotlibrc
/tmp/_MEI1rJccH/matplotlib/init.py:611: UserWarning: Could not find matplotlibrc; using defaults
/tmp/_MEI1rJccH/matplotlib/init.py:698: UserWarning: could not find rc file; returning defaults
Traceback (most recent call last):
File "", line 33, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/lib.controller.splashscreen", line 3, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/lib.controller.controller", line 40, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/lib.view.chartview", line 8, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.backends.backend_wxagg", line 20, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.figure", line 18, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.axes", line 14, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.axis", line 10, in
File "/build/pyinstaller/PyInstaller/loader/pyi_importers.py", line 270, in load_module
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.font_manager", line 1325, in
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.font_manager", line 1275, in _rebuild
File "/build/4n/build/4n6time/out00-PYZ.pyz/matplotlib.font_manager", line 962, in init
File "/build/4n/build/4n6time/out00-PYZ.pyz/posixpath", line 68, in join
AttributeError: 'NoneType' object has no attribute 'endswith'

Is 4n6time working or is it still broken?

@socialcred unfortunately this package is severely broken and with the new Plaso coming on the scene, this package will not be fixed anytime soon.


SNOW-1791556: Use docstrings folder for Index methods and properties

Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
<!---
In this section, please add a Snowflake Jira issue number.
<p>Note that if a corresponding GitHub issue exists, you should still include
the Snowflake Jira issue number. For example, for GitHub issue
https://github.com/snowflakedb/snowpark-python/issues/1400, you should
add "SNOW-1335071" here.
--->
Fixes SNOW-1791556

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code

[ ] If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing

[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency
[ ] If this is a new feature/behavior, I'm adding the Local Testing parity changes.
[ ] I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines

Please describe how your code solves the related issue.
Use docstrings folder for Index methods and properties. Docstrings for DatetimeIndex and TimedeltaIndex will be treated similarly in follow-up PRs.

@sfc-gh-joshi @sfc-gh-mvashishtha I've started moving the docstrings for Index objects to the docstrings folder. Can you please take a look at this first PR?

@sfc-gh-helmeleegy could you generate all the docs and check whether there are any diffs?
The code changes LGTM.

Thanks, Mahesh. I compared the generated docs (before and after the change) and they look the same.

LGTM, thanks! Please also check the doc HTML output like @sfc-gh-mvashishtha said, and the output of help(pd.Index.method) for at least a few methods.

Thanks, Jonathan. I ran help(...) on a few properties/methods before and after the change and they all were the same.


⚠ Cioos Pacific CKAN has degraded performance

In e3e777e, Cioos Pacific CKAN (https://catalogue.cioospacific.ca) experienced degraded performance:

HTTP code: 200
Response time: 8614 ms

Resolved: Cioos Pacific CKAN performance has improved in ac2f65d after 28 minutes.


Feature/add spatial disaggregation recipe

This PR adds the following:

a full recipe for implementing the Thrasher et al. 2012 method for spatial disaggregation that is part of the Bias Correction and Spatial Disaggregation (BCSD) daily downscaling method
structure for a new class of spatial models
a fit/predict method for spatial disaggregation using the SpatialDisaggregator class in spatial models

@dgergel - I just merged some changes in that should fix the CI for you. Go ahead and pull those in and then I'll take a look here.

@dgergel - I just merged some changes in that should fix the CI for you. Go ahead and pull those in and then I'll take a look here.

@jhamman sorry for the delay in fixing the pre-commit problems. This is finally ready for a review.

@jhamman sorry for the delay in fixing the pre-commit problems. This is finally ready for a review.

@jhamman so sorry for taking so long to get back to this. I've made the changes you suggested and added unit tests, so this is ready for another review.


client find, server added->ready->changed does not trigger query update

maybe I am misunderstanding how find should with with RXJS in Meteor.
if I have this on the client
Models

find(type): Observable<any[]> {
    return this.Models.find({});
}
constructor(){
MeteorObservable.subscribe('testCollection').subscribe();
this.Models = new MongoObservable.Collection<any>('testPublisher', {idGeneration: 'MONGO'});
}

and this on the server
Meteor.publish('testPublisher', function () {
    this.added('testCollection', 'testId', {doc: []});
    this.ready();
    this.changed('testCollection', 'testId', {doc: [{test:'test'}]});
})

shouldn't the 'this.changed' trigger the find results to return the updated model in the find query? However, I am only ever receiving the initial model from 'this.added'.
Thanks

cant even seem to get the changed doc even if I call,
let docs = new Subject();
        let sub = this.Models[type].find({})
            .observe({
                added(document, atIndex, before){
                    docs.next(document);
                },
                changed(newDocument, oldDocument)  {
                    docs.next(newDocument);
                }
            });


Setting the type of the library in Package.swift to .dynamic.

Is your feature request related to a problem? Please describe.
Yes, the feature request is related to a problem I'm facing while building a framework that leverages Rollbar. Rollbar exposes its products as a static library. However, when compiling the framework for production, the static library is embedded in the framework, causing potential issues like code duplication and increased binary size.
Describe the solution you'd like
I would like a solution that provides an option to not embed the static library when compiling the framework for production. This could be done by adding the property type: .dynamic to all libraries exposed in the products property of Package.swift. If this would not be possible please expose dynamic version of already existing libraries.
Describe alternatives you've considered
One alternative would be to manually remove the static library from the framework after it has been compiled, but this would be a cumbersome and error-prone process that would need to be repeated for each build.
Additional context
The current behavior of embedding the static library during the framework compilation may lead to issues such as code duplication and increased binary size. By providing an option to avoid embedding the static library, users of the package can have better control over their build process and avoid potential issues related to static library embedding.

I have create a PR and tested it out with our Framework and it works.
https://github.com/rollbar/rollbar-apple/pull/281

Hey @rashadatjou, Thanks for reporting this issue, and I appreciate you created a PR too. Let me ask the devs to look into it.


Modify generateToken() interface

Ref #2732

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 8915

20 of 24 (83.33%)  changed or added relevant lines in 8 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.01%) to 62.601%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/SQLRewriteEngine.java
8
9
88.89%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/PreparedStatementExecutorWrapper.java
0
1
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/StatementExecutorWrapper.java
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
3
76.0%

Totals

Change from base Build 116:
0.01%

Covered Lines:
8607

Relevant Lines:
13749

💛  - Coveralls


c.Env[*] values lost in the subrouter mapping

I may be missing somethings, need help here! My setup is quite similar to example.
// Applying middleware's here, typically manipulates and then adds object or value to c.Env[---]
goji.Use(ApplyTemplates)
goji.Use(ApplySessions)
goji.Use(ApplyDatabase)
goji.Use(ApplyAuth) // checks the session user id and populates user into c.Env["User"]

admin := web.New()
goji.Handle("/admin/*", admin)
admin.Use(middleware.SubRouter)
admin.Use(ApplyAdminAuth) // Retrieving c.Env["User"] and need check for Admin Permission
admin.Get("/", Dashboard)
goji.Get("/admin", http.RedirectHandler("/admin/", 301))

Facing issue at
admin.Use(ApplyAdminAuth) // Retrieving c.Env["User"] and need check for Admin Permission
I'm getting nil for c.Env["User"] in the ApplyAdminAuth middleware. It seems values are not made it sub path /admin/*.
Where I'm making a mistake?

Are ApplyAuth and ApplyAdminAuth potentially conflicting? Remember that all
parent router middleware is applied to the sub router. If you can post the
code for those two middleware it'll help.
You can also sprinkle log.Printf("%v", c.Env) along the way to dump the
contents of the request context to logs as well, which will help debug.
On Sat, 1 Aug 2015 at 8:22 am Jeevanandam M<EMAIL_ADDRESS>wrote:

I may be missing somethings, need help here! My setup is quite similar to
example https://github.com/zenazn/goji/blob/master/example/main.go.
// Applying middleware's here, typically manipulates and then adds object or value to c.Env[---]
goji.Use(ApplyTemplates)
goji.Use(ApplySessions)
goji.Use(ApplyDatabase)
goji.Use(ApplyAuth) // checks the session user id and populates user into c.Env["User"]
admin := web.New()
goji.Handle("/admin/*", admin)
admin.Use(middleware.SubRouter)
admin.Use(ApplyAdminAuth) // Retrieving c.Env["User"] and need check for Admin Permission
admin.Get("/", Dashboard)
goji.Get("/admin", http.RedirectHandler("/admin/", 301))
Facing issue at
admin.Use(ApplyAdminAuth) // Retrieving c.Env["User"] and need check for Admin Permission
I'm getting nil for c.Env["User"] in the ApplyAdminAuth middleware. It
seems values are not made it sub path /admin/*.
Where I'm making a mistake?
—
Reply to this email directly or view it on GitHub
https://github.com/zenazn/goji/issues/150.

Yes, that's my understanding too. Parent middleware applies to sub router.
Middleware code:
// This is parent one
func ApplyAuth(c *web.C, h http.Handler) http.Handler {
	fn := func(w http.ResponseWriter, r *http.Request) {
		session := c.Env["Session"].(*sessions.Session)
		if userId, ok := session.Values["User"].(bson.ObjectId); ok {
			dbSession := c.Env["DBSession"].(*mgo.Session)
			database := dbSession.DB(c.Env["DBName"].(string))
			log.Println("I'm inside user check")

			user := new(model.User)
			err := database.C("users").Find(bson.M{"_id": userId}).One(&user)
			if err != nil {
				log.Printf("Auth error: %v", err)
				c.Env["User"] = nil
			} else {
				c.Env["User"] = user
			}
		}
		h.ServeHTTP(w, r)
	}
	return http.HandlerFunc(fn)
}

// This one applies to sub router /admin/*
func ApplyAdminAuth(c *web.C, h http.Handler) http.Handler {
	fn := func(w http.ResponseWriter, r *http.Request) {
		log.Printf("/admin/* ==> %s", r.URL.RequestURI())
		log.Printf("ApplyAdminAuth User Info: %v", c.Env["User"])
		h.ServeHTTP(w, r)
	}
	return http.HandlerFunc(fn)
}

Any pointers would be helpful? I'm still analyzing it no luck!

That's super weird! I wrote a little testing app which seems to work:
package main

import (
	"fmt"
	"log"
	"net/http"

	"github.com/zenazn/goji"
	"github.com/zenazn/goji/web"
	"github.com/zenazn/goji/web/middleware"
)

func Outer(c *web.C, h http.Handler) http.Handler {
	fn := func(w http.ResponseWriter, r *http.Request) {
		c.Env = map[interface{}]interface{}{
			"user": "carl",
		}
		h.ServeHTTP(w, r)
	}
	return http.HandlerFunc(fn)
}

func Inner(c *web.C, h http.Handler) http.Handler {
	fn := func(w http.ResponseWriter, r *http.Request) {
		log.Print(c.Env["user"])
		h.ServeHTTP(w, r)
	}
	return http.HandlerFunc(fn)
}

func main() {
	goji.Use(Outer)
	sub := web.New()
	goji.Get("/sub/*", sub)
	sub.Use(middleware.SubRouter)
	sub.Use(Inner)
	sub.Get("/", func(w http.ResponseWriter, r *http.Request) {
		fmt.Fprintf(w, "hello world")
	})

	goji.Serve()
}

I'm not sure why this would work but your app wouldn't. Would you be able to let me look at more of the surrounding code / middleware?

Thanks @zenazn and @elithrar for your inputs. Above sample code works fine. It seems I'm doing something wrong!
I will give a one more try! if not success then I will share my code base with you.

Okay, finally my journey ended with smile :)
Week ago I was started my application based on idea from this app and improved so on. Sample project gave an idea for Go-Lang and good starting point. Since I came from Java and Objective-C background.
However I ended up with issue mentioned in this thread and also few other issues as well. Will share my  experience to the project author later.
After @zenazn sample code, I confirmed myself I'm at wrong track. Finally I have restructured my application based on example and this article.  Able to over come issues I faced.


 Also I didn't found any specific code for audio chat stream. Can you help on this part.

If you need an audio only call , you can remove video: true here
https://developers.connectycube.com/js/videocalling?id=access-local-media-stream
If you want to be able to enable video during a call, then use  video: true here as well,
and once a stream  is obtained, you can disable video track:
stream.getVideoTracks()[0].enabled = false

and then unmute later while on a call


Allow Multiple Key Bindings for Split Editor

Originally reported (and closed) in issue 29651, I'd like to be able to define separate key bindings for each split editor, ie:

alt+shift+1 collapses to 1 editor pane

alt+shift+2 expands or collapses to 2 editor panes

alt+shift+3 expands or collapses to 3 editor panes

This is how Sublime Text operates. I use the each unique binding frequently in ST, depending on the project.

@johndugan fyi there is a ST keybindings extension: https://marketplace.visualstudio.com/items?itemName=ms-vscode.sublime-keybindings
@waderyan fyi for your ST keybindings extension.

@bpasero the underlying functionality is missing in VSCode (hence the issue). You can map however many key bindings you want. They are all just pointers to the same workbench.action.splitEditor function, unlike Sublime whose comparable function takes arguments.
VSCode

Sublime

I think this could be a fun area for a PR. I can think about a new command workbench.action.editorLayout that you can pass arguments to in order to:

define the number of editor groups that should show
define their relative widths to each other
define it the editor groups are aligned vertically or horizontally

This landed as part of https://github.com/Microsoft/vscode/issues/14909#issuecomment-393870565
There is a new layoutEditorGroups command that accepts an argument to define the editor layout, for example:
{
	"key": "Cmd+0",
	"command": "layoutEditorGroups",
	"args": {
                 "orientation": 1,
		"groups": [{ "size": 0.2 }, { "size": 0.6 }, { "size": 0.2, "groups": [{}, {}] }]
	}
}

The size portion is optional but when defined, all sizes need to sum up to 1 for one direction. The groups property allows to split the grid again. The orientation can either be horizontal (0) or vertical (1).


Gradle update, project cleanup

Remove local idea configs
Update gradle scripts and version to 3.5
Fix locators
Fix tests on travis ci

@rosolko Great! Thank you. PR merged.


Flow does not refine type parameter based on type being parametrized

I'm not sure what is right correct terminology to describe this limitation, but it a major limitation that prevents flow users from splitting data & functions operating on it in favor of types with methods. While it's fine in general it becomes pretty painful when data needs to be send across thread boundaries. Here is an example code that does not work:
/* @flow */

type NumberDecoder = {
  kind: "number"
}

type MaybeDecoder = {
  kind: "maybe",
  decoder: Decoder
}

type Decoder = NumberDecoder | MaybeDecoder<*, a>

const decode = <out>(input: string, decoder: Decoder<out>): out => {
  switch (decoder.kind) {
    case "number": {
      const value = parseFloat(input)
      if (Number.isFinite(value)) {
        return value
        //     ^ number. This type is incompatible with the expected return type
        //     some incompatible instantiation of `out`
      } else {
        throw Error(`Not a number ${input}`)
      }
    }
    case "maybe": {
      const value = decode(input, decoder.decoder)
      if (value instanceof Error) {
        return null
        //     ^ null. This type is incompatible with the expected return type of
        //     some incompatible instantiation of `out`
      } else {
        return value
      }
    }
    default: {
      void (decoder: empty)
      throw Error(`Unknown decoder kind`)
    }
  }
}

First error reports that number is incompatible with some instantiation of out, but that should not matter as long as it's compatible with the given instantiation of out and since NumberDecoder requires out:number number should be compatible with given instigation of out.

Second error reports that  null is incompatible with some instantiation of out, but here as well it should not matter as passed decoder is narrowed down to MaybeDecoder<*, out> and given the MaybeDecoder it should be clear that out is compatible with null.

Now there is a way to avoid these issues by using class based approach:
/* @flow */

interface Decoder {
  decode(input:string):a
}

class NumberDecoder implements Decoder<number> {
  kind: "number"
  decode(input:string):number {
    const value = parseFloat(input)
    if (Number.isFinite(value)) {
        return value
	} else {
      throw Error(`Not a number ${input}`)
    }
  }
}

class MaybeDecoder implements Decoder<?a> {
  kind: "maybe"
  decoder: Decoder
  decode(input:string):?a {
    const value = decode(input, this.decoder)
    if (value instanceof Error) {
      return null
    } else {
      return value
    }
  }
}

const decode = <out>(input: string, decoder: Decoder<out>): out =>
  decoder.decode(input)

It would be really nice if there as a way to achieve the same result as in last example but without having to attach decode implementation to a variant of the decoder.

I just noticed that using type parameters in class based approach does not seem to work either:
/* @flow */

interface Decoder {
  decode(input: string): a
}

class NumberDecoder implements Decoder {
  kind: "number"
  decode(input: string): a {
    const value = parseFloat(input)
    if (Number.isFinite(value)) {
      return value
    } else {
      throw Error(`Not a number ${input}`)
    }
  }
}

class MaybeDecoder implements Decoder {
  kind: "maybe"
  decoder: Decoder
  decode(input: string): b {
    const value = decode(input, this.decoder)
    if (value instanceof Error) {
      return null
    } else {
      return value
    }
  }
}

const decode = <out>(input: string, decoder: Decoder<out>): out =>
  decoder.decode(input)

So it may actually be issue related to how flow deals with type parameters rather than what I assumed initially.

It should never be possible to produce instance of type variable, because it's lower bound is not known and there is no way to specify it

@vkurchatkin Can you please try to explain it in terms that someone much less knowledgeable about type system (like myself) would be able to understand it ? Which specific example and better yet section are you referring to ?
Also is your comment relevant for the second example posted in the followup comment ? If it is not, is that example supposed to type check ? I would expect it to do so, but for whatever reason it does not.
Thanks

Here is a simple example that demonstrates this:
function test<T: number>(t: T): T {
  return 1;
}

T has an upper bound of number, i.e. T <: number. But it doesn't mean that T is number, it can be 1 | 2 | 3, for example. So, something like this never works in generic functions. You can't create instance of T out of thin air, you can only extract it from arguments somehow.

@vkurchatkin thanks for explaining, I do understand now. That being said second example does uses class NumberDecoder implements Decoder rather than  should not that be just aliasing number as a ?

should not that be just aliasing number as a

Not, it's just a default type parameter. You should write instead: class NumberDecoder implements Decoder<number> {


view the tx calldata

Hi Apoorv, there's a scenario I often used in metamask, that is press the confirm button in dapp to invoke metamask, but I just want to check the contract address and calldata.
Since impresonator-eth is for impresonator the address, but it can only view the data in dapp front page, I can't read the calldata after I click send tx button.

Hey the calldata is shown by expanding the "eth_sendTransactions" table:

It's really cool!
But it only works on impersonator.xyz, it's not in the plugin, the limitation is you can only use walletconnect.
The plugin take over metamask, which is more widely used.

Ohh now I get it. I'll make sure to add it to the browser extension: https://github.com/impersonator-eth/impersonator-extension


Improve track list in Android app

Hello!
Awesome app, i finally found a lightweight alternative to airsonic for streaming music to my phone.
I have lots of audio files without ID3 tags (Podcasts...). In this case the full path to the file is shown in the track list. Finding a file is difficult if the path is longer than the display space on the smartphone, since only the first characters of the path are visible.
Possible solutions to this Problem:

Truncate the start of the path instead of the end, so the filename is always visible
Show the filename only
Break the text string to multiple lines
Marquee the text string, if the length exceeds display space

I don´t know which solution is the easiest to implement...

Got you covered -- the next build will have a setting where you can specify the title ellipsis mode. https://github.com/clangen/musikcube/commit/3fb7882d89643bc9ac6af598a2883bc100686b64


(0.3.2) Merge changes from Minor Updates into Majour Updates

yeah fuck this, when i try fixing the merge conflicts it wants me to merge majour updates into minor updates... the exact opposite of what im telling it to do. doing it manually will be easier than dealing with this bs.


Diffusers attention script update triton2.1

deepspeed/ops/transformer/inference/triton_ops.py updated from https://github.com/openai/triton/blob/release/2.1.x/python/tutorials/06-fused-attention.py
Inference time (text to image) reduced 2.6 sec to 2.49 sec on A100
model : stabilityai_stable-diffusion-2
@jithunnair-amd  @loadams @rraminen
IS_CAUSAL = False gives same image output as not using deepspeed inference engine ,
IS_CAUSAL = True gives noise as output

@lekurile  Hi Lev, this PR is based on relatively new flash attention from triton , could you review this ? it works on A100

@lekurile Hi Lev, @mrwyattii Hi Michael , this PR is based on relatively new flash attention from triton , could you review this ? it works on A100

Hi @bmedishe, thank you for the contribution! I've merged the latest master, let's wait for the tests to complete. In the meantime, I'll do some manual testing using our Stable Diffusion example,

@bmedishe fixed a few conflicts and formatting issues. Tested locally and looks good to me. Let's wait for the tests to complete.


Error with multiple timepickers

Because the framework depend on id-fields (like <div id="hour_list_id"> ) it's not possible to create multiple TimePicker objects. Not sure it this is supported/intended, but I have the following problem in my code:
I use a js templating engine where a lot of the HTML is recreated on the fly, for instance when changing between edit and read "mode."
So if I create a TimePicker like new TimePicker("my-element-id") that element might be destroyed at a later point. Since I couldn't get the Show()-function to work ( #7 ), I've tried to create new pickers when the DOM tree changes, but because the new picker creates new markup for the new picker with same ID's as the old one all functionality stops working. My workaround for now is to just manually remove the markup before recreating the picker :)
var vInputElements = null;
var vTimePicker = null;
function recreatetimepicker(){
    // Check if the first input element has been removed from the DOM (all my elements will be removed at the same time)
    if(vInputElements === null || (vInputElements && !document.contains(vInputElements[0]))){
        vInputElements = $.makeArray($(".hour-picker"));
        if(vTimePicker){
            $("._jw-tpk-container._jw-tpk-dark").remove(); // This removes the old markup
        }
        vTimePicker = new TimePicker(vInputElements, {
            theme: 'dark',
            lang: 'en'
        });
        vTimePicker.on('change', timePickerChange);
    }
}

I suggest changing the code so that all pickers use the same markup (Created once only), or change the id's to classes and have a unique reference to each datepicker.
Might take a look at the code and create a pull request myself if I have some free time this weekend :)

I'm not sure about having a single markup. Would anyone need more than one at the same time? It doesn't seem so. What do you think?

You probably don't need more than one, as long as you can make it pop up at multiple targets. I guess what I really needed here was to swap out the elements bound to the timepicker, so maybe some functions like setTarget(target) and/or addTarget(target)?

@marza91 Would you have a time to show your suggestion in a PR?

Yeah, I didn't this weekend unfortunately, but I'll give it a try whenever I can!

Closing due to inactivity.

Hey, sorry, I haven't had the time to look any more into this...
But whenever I get the time, I'll create a PR instead (I have this on my to-do list :) )

That will be great @marza91.


Preparing 0.1.2 release

Not ready to merge yet.

I've now tested this enough to consider it a release candidate.  Would like to get opinions from a few other testers on whether this is overall an improvement from the previous BGI/2 algorithm, and whether there are any behaviors that need fixing before we release to master.

Looking good to me, but my development environment fell apart... still rebuilding it and haven't tested this personally, but I like the changes overall. Very nice.

Anything else we need before merging this to master and cutting a release?  Any reason not to do that tonight?

:+1: to release


Selecting the View Details text in the product card at the bottom of the hydrogen page has a broken outline

possibly related to https://github.com/concrete-utopia/utopia/issues/5471


[v1.12] install/kubernetes: make securityContext SELinux options configurable

Manual backport of https://github.com/cilium/cilium/pull/22721 to v1.12 because it caused conflicts in https://github.com/cilium/cilium/pull/23003, see https://github.com/cilium/cilium/pull/23003#issuecomment-1377767345

/test-backport-1.12

/test-1.22-4.9


Call strlen(nullptr)

int element_details::Element_Node::Print_Tree(
...
int nb_free = NB_SPACES - level - (Name ? 0 : strlen(Name)); // 40 - len(Name) - len(spaces)

@tribouille shouldn't it (Name ? strlen(Name) : 0)?
(and how did I miss that... I'll test it after it is changed)

yep


[MINOR][DOCS] Fix Python code sample for StreamingQueryListener: Reporting Metrics programmatically using Asynchronous APIs

Fix Python language code sample in the docs for StreamingQueryListener:
Reporting Metrics programmatically using Asynchronous APIs section.
What changes were proposed in this pull request?
The code sample in the Reporting Metrics programmatically using Asynchronous APIs section was this:
spark = ...

class Listener(StreamingQueryListener):
    def onQueryStarted(self, event):
        print("Query started: " + queryStarted.id)

    def onQueryProgress(self, event):
        println("Query terminated: " + queryTerminated.id)

    def onQueryTerminated(self, event):
        println("Query made progress: " + queryProgress.progress)

spark.streams.addListener(Listener())

Which is not a proper Python code, and has QueryProgress and QueryTerminated prints mixed. Proposed change/fix:
spark = ...

class Listener(StreamingQueryListener):
    def onQueryStarted(self, event):
        print("Query started: " + queryStarted.id)

    def onQueryProgress(self, event):
        print("Query made progress: " + queryProgress.progress)

    def onQueryTerminated(self, event):
        print("Query terminated: " + queryTerminated.id)

spark.streams.addListener(Listener())

Why are the changes needed?
To fix docimentation errors.
Does this PR introduce any user-facing change?
Yes. -> Sample python code snippet is fixed in docs (see above).
How was this patch tested?
Checked with github's .md preview, and built the docs according to the readme.
Was this patch authored or co-authored using generative AI tooling?
No.

Just retrigger tests for completeness

Just retrigger tests for completeness

Done.

Merged to master/3.5


Using SQL expression based Custom Column as Dashboard Filter results in invalid Filter Query

A clear and concise description of what the bug is.
How to reproduce the bug

Go to 'Custom Columns' in a Dataset and add a new entry with a SQL expression like IF(1=1,1,0)
Add this new custom column as a filter to the a dashboard and load it
See error: "Cannot load filter" (column my_custom_column does not exist)

Expected results
Filter being loaded
Actual results
Error: "Cannot load filter"
Screenshots

Also this is the (boiled down) query example we see in our SQL Engine (Spark SQL):
SELECT IF(1 = 1, 1, 2) AS `foo`,
       IF(1 = 1, 1, 2) AS `foo`,
FROM
  (WITH
  ...
  SELECT *
  FROM my_table) AS `virtual_table`
GROUP BY IF(1 = 1, 1, 2)
ORDER BY `foo` ASC

Environment
(please complete the following information):

browser type and version: Version 116.0.5845.188
superset version: 2.1.0
python version: 3.9.17
node.js version: node -v
any feature flags active: nothing related IMHO

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
For some reason Superset is generating a query that uses ORDER BY with an alias with is not possible it seems: https://stackoverflow.com/a/46405611

This seems to be working fine in 3.0 and newer. Granted I was using SQLIte syntax using Shillelagh, so I had to do a CASE statement... but... it seems to work :)


extend print_tree to uops +1 line

helpful for understanding uops and rearange.
had to break one if line because it got too long

  0 ━┳ STORE
  1  ┣━━ DEFINE_GLOBAL (0, True)
  2  ┣━┳ RANGE (1, 0)
  3  ┃ ┣━━ CONST
  4  ┃ ┗━━ CONST 2
  5  ┗━┳ ALU BinaryOps.ADD
  6    ┣━┳ LOAD
  7    ┃ ┣━━ DEFINE_GLOBAL (1, False)
  8    ┃ ┗━┳ RANGE (1, 0)
  9    ┃   ┣━━ CONST
 10    ┃   ┗━━ CONST 2
 11    ┗━┳ LOAD
 12      ┣━━ DEFINE_GLOBAL (1, False)
 13      ┗━┳ RANGE (1, 0)
 14        ┣━━ CONST
 15        ┗━━ CONST 2

using hasattr 4 times is repetetive could write it as a one liner function would lead to same number of lines but more characters. arguable harder to read

yeah still nice to visualize as tree i think.
and AST is also technically a directed acyclical graph no?

yea i guess that makes sense, uop and lazyop are similar

nice example visualizing graph rewrite:

Device.DEFAULT = "CLANG"

x = Tensor([1,2])

x = x + (-x)

sched = x.schedule()
ast = sched[1].ast

renderer = Device["CLANG"].renderer
lin = get_linearizer(renderer, ast)
lin.linearize()

store = lin.uops.sinks[0]

print_tree(store)

from tinygrad.codegen.uops import constant_folder
lin.uops.nodes = {}
sink  =lin.uops.graph_rewrite(store, constant_folder)

print_tree(sink)

  0 ━┳ STORE
  1  ┣━━ DEFINE_GLOBAL (0, True)
  2  ┣━┳ RANGE (1, 0)
  3  ┃ ┣━━ CONST
  4  ┃ ┗━━ CONST 2
  5  ┗━┳ ALU BinaryOps.ADD
  6    ┣━┳ LOAD
  7    ┃ ┣━━ DEFINE_GLOBAL (1, False)
  8    ┃ ┗━┳ RANGE (1, 0)
  9    ┃   ┣━━ CONST
 10    ┃   ┗━━ CONST 2
 11    ┗━┳ ALU UnaryOps.NEG
 12      ┗━┳ LOAD
 13        ┣━━ DEFINE_GLOBAL (1, False)
 14        ┗━┳ RANGE (1, 0)
 15          ┣━━ CONST
 16          ┗━━ CONST 2
  0 ━┳ STORE
  1  ┣━━ DEFINE_GLOBAL (0, True)
  2  ┣━┳ RANGE (1, 0)
  3  ┃ ┣━━ CONST
  4  ┃ ┗━━ CONST 2
  5  ┗━━ CONST

yeah also was wondering if its planned to unify them ever?

Neat! Yea I've been thinking about unifying them.
I'd merge a PR that renames uop->op and vin->src in class UOp to match LazyOp

Neat! Yea I've been thinking about unifying them.
I'd merge a PR that renames uop->op and vin->src in class UOp to match LazyOp. That would also simplify this.

yes nice!


[v2.9] Make /v3/principal return 404 instead of 500 when principal can't be found

Issue:

https://github.com/rancher/rancher/issues/47831
Backport of #47717
Problem

Solution

Testing

Engineering Testing
Manual Testing

Automated Testing

Test types added/modified:

QA Testing Considerations

Regressions Considerations

N/A
Existing / newly added automated tests that provide evidence there are no regressions:
N/A

Note: do not merge. This should go into v2.9.5.


Remove use of legacy protobuf library

Issue description
(I'll prefix this by saying I'm not very familiar with golang's protobuf libraries, although I've spent a good chunk of today learning about the legacy and new libraries....)
LXD is currently using both the legacy/deprecated (github.com/golang/protobuf) and new (github.com/protocolbuffers/protobuf-go) versions of the protobuf library. However, the legacy version is only used in one file (lxd/bgp/server.go), that's using the deprecated ptypes library methods. (The upstream pull request has comments in the diff indicating switching to the new methods should be very easy.)
Could you please remove LXD's use of the legacy protobuf library? That will help trim down its dependency tree, and prevent possible issues when mixing the old and new protobuf libraries.
(I initially found this issue in a library down in LXD's dependency tree while preparing to package it for Debian, but the same mixing of protobuf library versions exists in LXD.)

I tried to do so but couldn't as the gobgp package itself relies on the specific use of ptypes.

I suspect we may need https://github.com/osrg/gobgp to take the first step and move away from ptypes, then we can do the same on our side. The rest of our protobuf usage was already updated to the new packages.

Ah, got it. I'll open an issue with them to make that request.

Closing as not actionable on our side currently. Also Go is complaining every time I update our gomod, so I already have a constant reminder of this ;)
Once gobgp is fixed, our build will almost certainly start failing due to type mismatch, we'll then correct it and that will take care of it.

gobgp has tagged a couple 3.0.0-rc releases that moves to the new protobuf library (https://github.com/osrg/gobgp/issues/2485). I've verified from a very simple standpoint that LXD 4.21 compiles with changes made to lxd/bgp/server.go, but as I don't have any BGP stuff setup locally, I can't test to ensure nothing's inadvertently broken LXD.

https://github.com/lxc/lxd/pull/9704


12/12: move localstore out of storage package

move localstore out of storage package

This PR is fine, even if we have problems with allocating large memory since we integrated badger to localstore. I would expect that tests are failing on master as frequent as here on ci.


[AppSec Policy Ref Guide] Commenting out SAST Policies

From the Slack conversation. Removing SAST policies from book.yml
Modified files:

docs/en/enterprise-edition/policy-reference/book.yml

Fix #
Test URLs:

Before: https://main--prisma-cloud-docs--hlxsites.hlx.page/
After: https://--prisma-cloud-docs--hlxsites.hlx.page/
Worker: https://prisma-cloud-docs-production.adobeaem.workers.dev/?branch=

cc: @tsmithv11


Bugs related to logger

TODO: Expand on the issue (Abhaas)
See:
https://github.com/CABLE-LSM/benchcab/pull/253#issuecomment-1970111682
https://github.com/CABLE-LSM/benchcab/pull/136#issuecomment-1945637413
By default, DEBUG log output is being shown

OK, to provide some additional context here, I think we need to take a look at the code that redirects printing to standard out in subprocess.py.
https://github.com/CABLE-LSM/benchcab/blob/94824588d92727aa396acf0298166dc00eacb341/benchcab/utils/subprocess.py#L60-L80
I think that we can basically remove the bits that do the standard out catches of print statements and fall back onto using the native subprocess functionality to capture output from commands.
Now that I have a better understanding of this issue, prefixing set -x && to the command is not the correct approach, particularly if we are doing a log.debug() immediately prior. We should be relying on the logger to output commands in verbose mode, and leave the subprocess module to do its thing. We get no additional benefit by printing out the statement inside the subprocess call.
@SeanBryan51 can probably provide additional context here, as I believe he is most suited to comment being the author of this chunk of code.
With these comments added, I am going to un-assign myself as I am working on other tasks and I'm not sure when I'll be available to work on this one - particularly if it becomes a blocker. @ccarouge, please feel free to re-assign me if needed. It isn't a great deal of work to address this issue.

I think the redirection of subprocess output to stdout was done so that buffering the output wasn't required (this lets us see the output of subprocess commands in real time):
https://github.com/CABLE-LSM/benchcab/blob/94824588d92727aa396acf0298166dc00eacb341/benchcab/utils/subprocess.py#L77
If the intention is to redirect the subprocess output to the logger, this SO post might be relevant: https://stackoverflow.com/questions/21953835/run-subprocess-and-print-output-to-logging
I'm not too sure exactly what the context is for this issue so I'm not sure if this helps, @abhaasgoyal can you update the issue description?

@SeanBryan51 I have added the description for the issue. Let me know if anything's unclear.


Using flutter_test 0.9.4 in combination with intl_translation 0.17.2 fails to resolve

I've got a version conflict between flutter_test and intl_translation.
pubspec.yaml:
dependencies:
  flutter:
    sdk: flutter
  intl_translation: 0.17.2

dev_dependencies:
  flutter_test:
    sdk: flutter

Running flutter packages get:
Because every version of flutter_test from sdk depends on analyzer 0.32.4 and intl_translation >=0.17.2 depends on analyzer ^0.33.0-alpha.0, flutter_test from sdk is incompatible with intl_translation >=0.17.2.
So, because kolibri depends on both intl_translation ^0.17.2 and flutter_test any from sdk, version solving failed.

Doctor:
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v0.9.4, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.2)
[✓] Android Studio (version 3.1)
[✓] Connected devices (1 available)

• No issues found!

Dart version 2.1.0-dev.5.0.flutter-a2eb050044.

The analyzer dependency in intl_translation was because of changes to support new mixin features. So I think if something actually depends on 0.17.2 and also on something that cannot use the latest analyzer, it's not going to work. If it can, it should allow an older version of intl_translation. If it can't, presumably it really depends on that, and it will need a newer version of flutter_test. I don't see anything I can do that would fix it.


More testing; Improve code quality

Codecov Report

Merging #251 (e441a6d) into master (5f2c762) will increase coverage by 0.96%.
The diff coverage is 55.31%.

@@             Coverage Diff              @@
##             master     #251      +/-   ##
============================================
+ Coverage     71.69%   72.66%   +0.96%
- Complexity      962      972      +10
============================================
  Files           121      121
  Lines          3240     3248       +8
  Branches        428      425       -3
============================================
+ Hits           2323     2360      +37
+ Misses          798      774      -24
+ Partials        119      114       -5

Impacted Files
Coverage Δ

src/main/java/safeforhall/model/ModelManager.java
94.53% <ø> (ø)

...c/main/java/safeforhall/model/event/EventDate.java
86.36% <ø> (+3.75%)
:arrow_up:

...c/main/java/safeforhall/model/event/EventTime.java
75.00% <ø> (+4.41%)
:arrow_up:

src/main/java/safeforhall/ui/MainWindow.java
0.00% <0.00%> (ø)

...java/safeforhall/logic/commands/ImportCommand.java
88.88% <85.71%> (+0.48%)
:arrow_up:

.../java/safeforhall/logic/commands/TraceCommand.java
96.36% <100.00%> (ø)

...ain/java/safeforhall/model/event/ResidentList.java
92.72% <0.00%> (+6.36%)
:arrow_up:

...ava/safeforhall/logic/commands/IncludeCommand.java
95.65% <0.00%> (+13.04%)
:arrow_up:

...in/java/safeforhall/model/util/SampleDataUtil.java
95.45% <0.00%> (+95.45%)
:arrow_up:

Continue to review full report at Codecov.

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