text:
React-native 0.43 depends on React 16.0.0-alpha.6

Description
After running
react-native init TestLatestCode

React native creates the following dependencies within the package.json file
	"dependencies": {
		"react": "16.0.0-alpha.6",
		"react-native": "0.43.0"
	},

I would have expected a dependency on a stable release of React, instead an alpha version is currently being used.
Reproduction Steps and Sample Code
react-native init TestLatestCode

View the generated package.json file
Solution
Clarify if this react alpha dependency is safe to use in production currently. It currently seems counter intuitive to have stable release of react-native code depend on an alpha release of react.
If it is not stable, presumably this dependency will need to be downgraded? 🤔
Additional Information

React Native version:  0.43

This is intentional because the React Native releases follow the copy of RN in Facebook's repo, which also sometimes uses alpha versions of React. It is correct to depend on React 16 alpha 6.

Is it correct but it breaks? (See the more than 100 issues opened with the 0.43 tag)
What are we missing?

This is the final release and won't change until React Native 0.45 or 0.46. There are breaking changes between React 15 and 16, but React Native + React aren't broken.

@ide you mean that maybe are the deps causing the issues?

It could be, in my experience new RN projects work fine as well as projects that have updated all their code + deps to work with RN 0.43 + React 16a6.

We're using yarn; hence freezed versions. I'll try to reinstall the lock
file and deps by hand tomorrow.
On Wed, Apr 12, 2017, 20:29 James Ide notifications@github.com wrote:

It could be, in my experience new RN projects work fine as well as
projects that have updated all their code + deps to work with RN 0.43 +
React 16a6.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/13291#issuecomment-293666780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC-PYzFTcl8b3Y4aNfYnaWfZgaCVGlnuks5rvRgDgaJpZM4Myy7i
.

--
http://twitter.com/sospedra_r https://www.linkedin.com/in/sospedra
Rubén Sospedra http://sospedra.me/
frontend developer
javascript hacker
+0034 657 813 845
@   hello@sospedra.me

authors: AlanFoster ide sospedra


text:
[SectionList] Sticky headers do not stick

Description
The SectionList component does have a prop called stickySectionHeadersEnabled. However when I set it to true, the section headers do not seem to stick to the top as the documentation suggests.
Reproduction Steps and Sample Code
Snack: https://snack.expo.io/rkt7_TrzZ
Additional Information

React Native version: 0.45.0
Platform: both
Things I've tried: Adding a stickyHeaderIndices prop, using ScrollView / View as a container.

can you test with RN0.46? several related bug-fix commits have been shipped in this release

Upgrading to react-native@0.46 alone did not make it work, but in the RNTester it seems to work. From that I might be able to pinpoint the exact issue. Will look into this a bit closer as I would like to use the SectionList in my app.
I also tried AnimatedSectionList – no dice.

@JonnyBurger
Try to use

instead of

@JonnyBurger I suspect it might be fixed by https://github.com/facebook/react-native/commit/0518a0ba12e7cafc8228be0455403cc23b055a79 , which is part of the 0.46 RCs. Not sure if it's part of react-native@0.46 as that may be a different thing? (Not sure)

@mikelambert I try with RN 0.46.2 and it doesn't work.

I ran into the same issue today and it turned out that my SectionList was inside a ScrollView.
Make sure your SectionList is not a (grand)child of a ScrollView component

Now, it's works for me. @mvanroon @mikelambert

@danielfeelfine what was the problem?

It seems that my implementation was wrong @mvanroon. If you can post your code I can help you.

@danielfeelfine I already got it working mate, cheers

i have the same issue here when i use
<SectionList> <SectionList /> </SectionList>
the first section sticky header works, but inside one is not working.
i need a big sticky header and several small group sticky header, so i use sectionList in this way.
any solutions? 3ks.

I have the same issue as @chenghaohao, when nesting <SectionList>s.

@calirec can you post the code of you are using?

Hello,
I have an issue with stickyHeader and nested SectionList as @calirec.
The nested header section is not sticky.
I have made a sample here : https://snack.expo.io/By2my0VV7
Can you please check if it is a bug or not?
Thank you for your help.
May be nested SectionList and stickyHeader would require a new issue creation...?

source: gharchive/issue

authors: JonnyBurger MathieuVedana chenghaohao danielfeelfine kramer9x mikelambert mvanroon nihgwu pohy

repo: facebook/react-native

license: MIT

license_type: permissive

license_source: github-api


text:
Passing big string to WebView failed.

I am tring to pass a local file to WebView. After searching around, I think the following method is a promising approach.
Get base64 code for the local file and pass it to WebView as a string, and inside the WebView, decode base64 to file object.
However, when I use the base64 code as the parameter for webview.postMessage(base64) , nothing happened. Keep everything untouched, hard-code a short string as the parameter for postMessage(msg), everything works fine, the code in WebView part can get the value.
I don't what happened. Is there a limitation for the parameter of postMessage() ? Or a bug for RN WebView?

This issue looks like a question that would be best asked on StackOverflow.
StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
Will close this as this is really a question that should be asked on StackOverflow.

@hramos  Nope, I think it maybe a bug.
Later yesterday, I found that, the code is working fine on emulator, but failed on real device. It is wired, I spent whole afternoon working on it, just find out it may by problem with debuging on real device.

+1

+1

+1


text:
Make the default for underlineColorAndroid transparent

https://twitter.com/notbrent/status/986843528004292608
This will help reduce differences between iOS and Android, the default style is actually kind of broken right now because we no longer add extra padding on Android.
Before:

After:

The easiest implement this might be just to add underlineColorAndroid: 'transparent' to TextInput default props.

How about just making it underlineColor (with transparent default) and make it so it just adds a border bottom on iOS? I tend to underline most of my textinputs but always just make the android underline transparent so I can share the style for both platforms.

@joefazz I think the underline is more of a material design thing, and poly-filling it on iOS is out of this scope. It's actually a bit different than border, both in the way it is positioned and is affected by focus. Also it could lead to some weird things if someone uses both border and underlineColor.

It’s worth pointing out this that API doesn’t produce an underline compatible with the Material design spec for form inputs. So right now, any dev who is trying to implement material is also setting this prop to transparent and doing all the work on top of a blank slate.

I am willing to work on this one as a first issue.

@mikaoelitiana Cool! You can mention me in the PR and I'll have a look.

@shubhnik you can get back the old behaviour by setting.
<TextInput underlineColorAndroid={null} … />

See more this comment for more finding of mine on this.

authors: AndrewIngram janicduplessis joefazz martnst mikaoelitiana


text:
TouchableWithoutFeedback onLayout - Never called / triggered

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native version: https://github.com/facebook/react-native/releases
[x] Run react-native info in your terminal and paste its contents under "Environment"
[x] Let us know how to reproduce the issue. Include a code sample, share a project, or
share an app that reproduces the issue using https://snack.expo.io/

Environment
OS: Linux 4.4
Node: 9.4.0
Yarn: Not Found
npm: 6.1.0
Watchman: Not Found
Xcode: N/A
Android Studio: Not Found
Packages: (wanted => installed)
react: ^16.3.1 => 16.4.0
react-native: ^0.55.4 => 0.55.4
Note: I actually have Android Studio installed, not sure why it states "Not Found"
Description
Trying to use onMeasure within View which is a child of TouchableWithoutFeedback so I can get the width of the View.
Unfortunately onLayout is never triggered and so I never see the console log mesage.
This does however work with TouchableOpacity as the parent component.
Steps to Reproduce
Expo Snack: https://snack.expo.io/rJMkUQhl7
Or in case that doesn't work, the code for it is shown below.
import React, { Component } from 'react';
import {
  Text,
  View,
  StyleSheet,
  Modal,
  TouchableWithoutFeedback,
  Button,
} from 'react-native';
import { Constants } from 'expo';

// You can import from local files
import AssetExample from './components/AssetExample';

export default class App extends Component {
  constructor(props) {
    super(props);
    this.state = {
      showModel: false,
    };
  }

  showModel() {
    this.setState({
      showModel: true,
    });
  }

  hideModel() {
    this.setState({
      showModel: false,
    });
  }

  render() {
    return (
      <View style={styles.container}>
        <Modal
          visible={this.state.showModel}
          animationType={'fade'}
          onRequestClose={() => this.hideModel()}
          transparent>
          <TouchableWithoutFeedback onPress={() => this.hideModel()}>
            <View style={styles.modalBoxContainer}>
              <TouchableWithoutFeedback>
                <View
                  style={styles.modelBox}
                  onLayout={event => {
                    var { x, y, width, height } = event.nativeEvent.layout;
                    console.log('WIDTH: ' + width);
                  }}>
                  <Text>THIS IS AN EXAMPLE</Text>
                </View>
              </TouchableWithoutFeedback>
            </View>
          </TouchableWithoutFeedback>
        </Modal>
        <Button
          title="Show Model"
          onPress={() => {
            // test
            this.showModel();
          }}
        />
      </View>
    );
  }
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    alignItems: 'center',
    justifyContent: 'center',
    paddingTop: Constants.statusBarHeight,
    backgroundColor: '#ecf0f1',
  },
  modalBoxContainer: {
    backgroundColor: 'rgba(0, 0, 0, 0.8)',
    flexDirection: 'column',
    alignItems: 'center',
    justifyContent: 'center',
    height: '100%',
  },
  modelBox: {
    backgroundColor: '#fafafa',
    alignItems: 'center',
    justifyContent: 'center',
    borderRadius: 5,
    paddingTop: 5,
    paddingBottom: 5,
    width: 200,
    height: 100,
  },
});

Expected Behavior
Console would have the width of the View.
Actual Behavior
Nothing printed.

Why do you need the two TouchableWithoutFeedback elements?
Also, as you can see from the implementation of TouchableWithoutFeedback, it clones its child and sets onLayout to the onLayout prop you pass to TouchableWithoutFeedback.
Try either this:
<TouchableWithoutFeedback onPress={() => this.hideModel()}>
  <View style={styles.modalBoxContainer}>
    <View
      style={styles.modelBox}
      onLayout={event => {
        var { x, y, width, height } = event.nativeEvent.layout;
        console.log('WIDTH: ' + width);
      }}>
      <Text>THIS IS AN EXAMPLE</Text>
    </View>
  </View>
</TouchableWithoutFeedback>

Or this:
<TouchableWithoutFeedback onPress={() => this.hideModel()}>
  <View style={styles.modalBoxContainer}>
    <TouchableWithoutFeedback onLayout={event => {
      var { x, y, width, height } = event.nativeEvent.layout;
      console.log('WIDTH: ' + width);
    }}>
      <View style={styles.modelBox}>
        <Text>THIS IS AN EXAMPLE</Text>
      </View>
    </TouchableWithoutFeedback>
  </View>
</TouchableWithoutFeedback>

Also, as you can see from the implementation of TouchableWithoutFeedback, it clones its child and sets onLayout to the onLayout prop you pass to TouchableWithoutFeedback.

Why is this behaviour different from TouchableOpacity?

Great question. As far as we can tell, not for a good reason. This is something that has bit us a bunch internally and we plan to consolidate and make them consistent. We are hoping to do this within the next few releases.

That's why I opened this, felt it must have been a bug if TouchableWithoutFeedback doesn't work but TouchableOpacity does


text:
keyboardDismissMode = "on-drag" on ScrollView not working with Android

🐛 Bug Report
When scrolling in ScrollView when device keyboard active, on Android emulator keyboardDismissMode = "on-drag" does not close the keyboard
To Reproduce
<ScrollView keyboardDismissMode = "on-drag">       {content}   </ScrollView>
Expected Behavior
Keyboard should close when scrolling on Android device.
Code Example
Minimal Expo example
https://snack.expo.io/@hakkikonu/scrollview-bug
Environment
react-native info output:
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 369.48 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.1 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 15, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28
Build Tools: 19.1.0, 20.0.0, 21.1.2, 22.0.1, 25.0.0, 26.0.2, 27.0.0, 28.0.3
System Images: android-15 | Intel x86 Atom, android-19 | ARM EABI v7a, android-19 | Intel x86 Atom, android-21 | Android TV ARM EABI v7a, android-21 | Android TV Intel x86 Atom, android-21 | Android Wear ARM EABI v7a, android-21 | Android Wear Intel x86 Atom, android-21 | ARM EABI v7a, android-21 | Intel x86 Atom, android-21 | Intel x86 Atom_64, android-21 | Google APIs ARM EABI v7a, android-21 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom_64, android-22 | ARM EABI v7a, android-22 | Intel x86 Atom, android-22 | Intel x86 Atom_64, android-22 | Google APIs ARM EABI v7a, android-22 | Google APIs Intel x86 Atom, android-22 | Google APIs Intel x86 Atom_64, android-23 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom_64, android-25 | Google Play Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5199772
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: 0.58.4 => 0.58.4
npmGlobalPackages:
react-native-cli: 2.0.1

👋 there
is this issue still present on RN 59? You posted a repro (thanks for that!) but it's on Snack, which is currently based on latest Expo which is using 0.57.

I'm seeing the same issue RN v0.59.5 on iOS and Android

@kelset Yes, still I'm seeing

RN 0.59.8 still has the same issue here on Android.

Ok thanks everyone - we just released the first 0.60 RC, could anyone try the repro with that version?

@kelset Still happening on 0.60 RC, keyboard will dismiss only on tap but not on scroll.
I don't know if its related but i'm unable to show the keyboard with input.focus() as well.
On iOS everything works fine.

my workaround for now is to call Keyboard.dismiss() in my onScroll function. Its definitely annoying

Any plan for fixing this bug ?

Hi, Im experiencing the issue too , im using 0.59.10 , any work arounds?

@yasir-netlinks
this is the current workaround
onScrollBeginDrag={Keyboard.dismiss}

Repro on RN 0.60.5. FlatList with keyboardDismissMode: 'on-drag' which does dismiss keyboard on drag on iOS, but does not on Android (emulator API 26)

What about 61?

Yes, 0.61.1 too. Still need to monkey patch it.

@kelset  hello , I found why this issues happened, because of the fix in Fix for scrollview android #18785 @mistenkt added the code
this.state.isTouching, but it always return false...

@kelset Hello, I have this problem too, it would like that this problem was solved, thanks.

Hi, same problem here. It still present with React Native 0.61.5

Same problem with 0.61.5, but can confirm the current workaround works. Will be nice if it's fixed

Not fixed, stupid bot

Not fixed. Need this to work. Any updates?

hello folks - it seems that this bug has been around for quite some time but no one attempted a PR to fix it. If you have time I'd recommend you create a PR with a proper fix and link it here.

still not fixed for 0.62

TLDR
This functionality was never implemented for android and this is a feature request
LONG VERIONS
I think this functionality was never implemented on android
https://github.com/facebook/react-native/blob/9263eb5d3864a42925b699343db2c09cc8934ed0/ReactAndroid/src/main/java/com/facebook/react/views/drawer/ReactDrawerLayoutManager.java#L155
but somehow was included in the documents which should be updated..
The best way to have functionalities like this is using this workaround

No bot.
And no, there's already PR which fixes it: https://github.com/facebook/react-native/pull/26422
I'm using by monkey patching with patch-package, and it works. So merging that would be nice.

@fungilation it's working fine for both Android and IOS ? and if you can share the patch as sample it would be nice, as I am using the patch-package too

my react-native+0.63.2.patch

diff --git a/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js b/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js
index c344ac4..0f34d3c 100644
--- a/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js
+++ b/node_modules/react-native/Libraries/Components/ScrollView/ScrollView.js
@@ -969,6 +969,16 @@ class ScrollView extends React.Component<Props, State> {
     }
   }

+  _handleBeginScroll = (e: ScrollEvent) => {
+    if (
+      this.props.keyboardDismissMode === 'on-drag' &&
+      Platform.OS === 'android'
+    ) {
+      dismissKeyboard();
+    }
+    this._scrollResponder.scrollResponderHandleScrollBeginDrag(e);
+  };
+
   _handleScroll = (e: ScrollEvent) => {
     if (__DEV__) {
       if (
@@ -985,14 +995,6 @@ class ScrollView extends React.Component<Props, State> {
         );
       }
     }
-    if (Platform.OS === 'android') {
-      if (
-        this.props.keyboardDismissMode === 'on-drag' &&
-        this.state.isTouching
-      ) {
-        dismissKeyboard();
-      }
-    }
     this._scrollResponder.scrollResponderHandleScroll(e);
   };

@@ -1175,8 +1177,7 @@ class ScrollView extends React.Component<Props, State> {
         .scrollResponderHandleResponderRelease,
       onResponderTerminationRequest: this._scrollResponder
         .scrollResponderHandleTerminationRequest,
-      onScrollBeginDrag: this._scrollResponder
-        .scrollResponderHandleScrollBeginDrag,
+      onScrollBeginDrag: this._handleBeginScroll,
       onScrollEndDrag: this._scrollResponder.scrollResponderHandleScrollEndDrag,
       onScrollShouldSetResponder: this._scrollResponder
         .scrollResponderHandleScrollShouldSetResponder,

Wow this only took 2,5 year to fix. This is why I love react-native, constant hacking needed 😂

authors: ChickenAhn Collin3 MUllman SinLucifer Stormz537 andidev fabriziobertoglio1987 fungilation hakkikonu immortalx kelset lordAnari raza2022 romanakash sivashik98 williamliangwl yasir-netlinks


text:
TextInput not visible when it's height greater than some value

Description
Text input becomes invincible when it's height is a bigger value (mostly >= window.hiegth ). Tested in Android.  It's working normal for lower values.
Code to reproduce the issue
import { AppRegistry } from 'react-native';
import { name as appName } from './app.json';
import React from 'react';
import {
    SafeAreaView,
    ScrollView,
    Dimensions,
    TextInput,
} from 'react-native';

const App = () => (
    <SafeAreaView>
        <ScrollView contentInsetAdjustmentBehavior="automatic">
            <TextInput
                style={{
                    backgroundColor: "red",
                    width: Dimensions.get('window').width,
                    height: 2 * Dimensions.get('window').height,
                }}
            />
        </ScrollView>
    </SafeAreaView>
);

AppRegistry.registerComponent(appName, () => App);

React Native version:
react": "16.11.0",
react-native": "0.62.2"

Steps To Reproduce

react-native init
update above code and run

Expected Results
TextInput should not hide when it reaches to some limit

Let me just add that this is not reproducible on all devices / versions. I cannot reproduce it on my android 10 device but can reproduce on android 8 device and emulator.
Here's a snack where you can observe the problem: https://snack.expo.io/@vonovak/rn-28701

the issue is present with multiline textinput too, where this indeed is a problem
the trouble seems to be in wrapping the textinput in ScrollView. Without ScrollView the issue is not there, so perhaps this is a ScrollView problem, not a TextInput one.
I can also reproduce this in RN tester, I reproduced this on master with bf5f3c6a79fba839225576da889d3b7f835a19f6

Still facing the same issue

I have tested on Android 5-10, only happens on Android 8 and it is easy to reproduce.
Please re-open this issue.

Let me just add that this is not reproducible on all devices / versions. I cannot reproduce it on my android 10 device but can reproduce on android 8 device and emulator.
Here's a snack where you can observe the problem: https://snack.expo.io/@vonovak/rn-28701

note that the textinput is still mounted, you can interact with it, just not see it
the issue is present with multiline textinput too (if you fill it up with enough text), where this indeed is a problem
the trouble seems to be in wrapping the textinput in ScrollView. Without ScrollView the issue is not there, so perhaps this is a ScrollView problem, not a TextInput one. However, if I just change TextInput to View, it works; so some interplay between TextInput and ScrollView is causing this
I can also reproduce this on master, I tried it with RNTester on bf5f3c6

@vonovak Would you please re-open this issue?

Can verify this issue is present on RN 61.2 when running on an android 8 device.
Setting TextInput's maxHeight to screen height or less seems to "fix" it

I've created a $100 bounty for this issue. Please submit a PR if you could help.
https://issuehunt.io/r/tarouboy/react-native/issues/1

authors: Caundy msbadar msuma268 tarouboy vonovak


text:
Not Working in real device in debug mode

Description
I installed new react native project and its working well in the simulator. but when I built in real device in debug mode it was showing paseExecution error. then i found some solution that i have to change something in build phase.

In the build phase I marked for install builds only inside the Bundle React Native code and images

then it is building successfully but when the app opens it stuck at splash screen.
i got this error.

Steps to reproduce

Initialize the new react native app
npx react-native@latest init AwesomeProject

mark For install build only (Build phase > Bundle React Native code and images)

run code in real device

React Native Version
0.73.1
Affected Platforms
Runtime - iOS
Output of npx react-native info
System:
  OS: macOS 14.0
  CPU: (8) arm64 Apple M1
  Memory: 67.70 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.10.0
    path: ~/.nvm/versions/node/v20.10.0/bin/node
  Yarn: Not Found
  npm:
    version: 10.2.3
    path: ~/.nvm/versions/node/v20.10.0/bin/npm
  Watchman:
    version: 2022.11.07.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.14.3
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.2
      - iOS 17.2
      - macOS 14.2
      - tvOS 17.2
      - watchOS 10.2
  Android SDK: Not Found
IDEs:
  Android Studio: Not Found
  Xcode:
    version: 15.1/15C65
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.18
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.1
    wanted: 0.73.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
dyld[932]: Library not loaded: @rpath/OpenSSL.framework/OpenSSL
  Referenced from: <C17BD18C-F8E6-38B9-91F4-52A8CE635CFA> /private/var/containers/Bundle/Application/250C2226-652A-452C-8E9B-1892DD0840E9/AwesomeProject.app/AwesomeProject
  Reason: tried: '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/250C2226-652A-452C-8E9B-1892DD0840E9/AwesomeProject.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/250C2226-652A-452C-8E9B-1892DD0840E9/AwesomeProject.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file, not in dyld cache), '/private/preboot/Cryptexes/OS/usr/lib/swift/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/250C2226-652A-452C-8E9B-1892DD0840E9/AwesomeProject.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file), '/private/var/containers/Bundle/Application/250C2226-652A-452C-8E9B-1892DD0840E9/AwesomeProject.app/Frameworks/OpenSSL.framework/OpenSSL' (no such file)

Reproducer
https://github.com/RutvinBhanderi/react-native-reproducer
Screenshots and Videos
No response

I think maybe you should change your openssl version.Or run bundle install in your root of project.

I think maybe you should change your openssl version.Or run bundle install in your root of project.

i did bundle install but not working.
then i markled install build only ([CP] Embed Pods Frameworks,[CP] Copy Pods Resources) inside build phase but its showing library not loaded.

The same problem, there is no solution

My solution was network related. Make sure to turn off antivirus, or just open 8081 port for all network traffic in antivirus firewall settings (which solved issue for me)

Hi @RutvinBhanderi, thanks for the issue.
What is MobileVLCKit? It is not something that comes with React Native and it is that thing that is making your app fail.
It does not seem to be a React Native issue. For another issue, I just installed a React Native app on my physical devie in both Debug and Release mode.
As of today, we are aware of an issue with React Native on device but only if you run pod install with the USE_FRAMEWORKS=dynamic option turned on, which is not the default settings.
From your log, it looks like you have some dylibs... What setup are you using?

USE_FRAMEWORKS

I am using vlc media player but that is not the even if i remove the vlc library then also it is coming.
this is how my podfile looks

Can you report exactly which command you issued/what did you do to run it on device?
I did it yesterday and it worked with no issues (I only had to change the bundle id to match the provisioning profiles, of course).

Can you report exactly which command you issued/what did you do to run it on device?
I did it yesterday and it worked with no issues (I only had to change the bundle id to match the provisioning profiles, of course).
in xcode i just edit schema to debug mode and just build in my phone.
xcode version :- 15.1

getting this error :- Command PhaseScriptExecution failed with a nonzero exit code

Not working for me as well, getting Command PhaseScriptExecution failed with a nonzero exit code issue, but building to simulator with no issues. I even tried with several iOS devices.

@RutvinBhanderi I had the exact same issue and it turns out that RN was not bundling my index file because I'm using Typescript, so my bundle file is index.tsx and it expects index.js. Check that out if you're using Typescript in your project.

i am not using typescript. initially the project was generated in typescript but i changed app.tsx and index.tsx file to .js

@RutvinBhanderi can you follow the steps highlighted here to properly understand which script is failing? It is hard to help without knowing what's going on.

authors: Hao-yiwen RutvinBhanderi TomWq cipolleschi danidaryaweesh mmilvydas112


text:
is there any way fetch image base64 data from CameraRoll

i use CameraRoll to select image, but now, i don't know how to get image base64 data to upload server

i change to https://github.com/marcshilling/react-native-image-picker


text:
[iOS] uploading a non-ready iCloud image results of sending empty bytes

I am using a custom camera roll picker that allows to pick iCloud images, and when you use them in a XHR and send them to a server (using their 'descriptor object', I mean the {uri} object), they only are submitted if they are downloaded on the phone, but not if they are not in sync, in that second case, server will receives empty bytes because images was not ready.
A workaround is to define a custom ObjC code to call before submitting the form, but IMO this should be solved by RN when it 'resolves' the {uri} object to bytes.

RCT_EXPORT_METHOD(ensureImageIsReady:(NSString *)arg
                  successCallback:(RCTResponseSenderBlock)callback
                  cancelCallback:(RCTResponseSenderBlock)cancelCallback)
{
  if ([arg length]<=5 || ![[arg substringToIndex:5] isEqualToString:@"ph://"]) {
    callback(@[@(false)]);
    return;
  }
  NSString *localIdentifier = [arg substringFromIndex:5];
  PHFetchResult *fetchResult = [PHAsset fetchAssetsWithLocalIdentifiers:@[localIdentifier] options:nil];
  PHImageManager *manager = [PHImageManager defaultManager];
  PHImageRequestOptions *options = [[PHImageRequestOptions alloc] init];
  options.networkAccessAllowed = YES;
  for (PHAsset *asset in fetchResult) {
    [manager
     requestImageDataForAsset:asset
     options:options
     resultHandler:^(NSData * _Nullable imageData, NSString * _Nullable dataUTI, UIImageOrientation orientation, NSDictionary * _Nullable info) {
       if (imageData)
         callback(@[@(true)]);
       else
         cancelCallback(@[@"image failed to download"]);
     }];
  }
}

Related issue: #1885
Is iCloud support for images something that is planned to work out of the box with CameraRoll ?

Even if camera roll don't support iCloud when listing photos, I think it's
a separated concern.
To me this is still a bug that photos aren't "resolved" when uploaded and
it's in React Native network stack (the form upload that resolve the {uri}
object).
If you happen to use a react-native plugin that use iCloud files (images or
whatever) you should still be able to manipulate it with React Native.
Le jeu. 21 avr. 2016 08:46, Samuel Kraft notifications@github.com a
écrit :

Related issue: #1885
https://github.com/facebook/react-native/issues/1885
Is iCloud support for images something that is planned to work out of the
box with CameraRoll ?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/issues/7081#issuecomment-212769246

Hi gre@,
As you mentioned you are using a custom camera roll.
It is not the official one? https://facebook.github.io/react-native/docs/cameraroll.html
How could you see the the icloud image from your camera roll?
In my case, no matter which groupTypes I choose, I can't see my icloud images which have only a preview version in local.
Only after I download the original image from my Photos, I can see it in the camera roll.
Thanks!

@6061960 RN's CameraRoll have limitations as AFAIK you can only list the camera roll photos. If you want more advanced stuff, and for instance, you can use QBImagePickerController which allow to pick from iCloud and also support multi-selection (there are many other alternatives, depends on what you need, search on google).

this bug was supposed to be fix, but it is still not fixed to me unfortunately.
tested on 0.34.

Which iOS version? I've been unable to reproduce on iOS 10.
--
Ron Heft
On Sep 29, 2016, 7:17 AM -0400, Gaëtan Renaudeau notifications@github.com, wrote:

this bug was supposed to be fix, but it is still not fixed to me unfortunately.
tested on 0.34.
any idea @ronaldheft (https://github.com/ronaldheft) ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/facebook/react-native/issues/7081#issuecomment-250438065), or mute the thread (https://github.com/notifications/unsubscribe-auth/ABFxSDVS-SqdVFZE7zxeHMVrefGPn24kks5qu531gaJpZM4ILdr4).

you are right. This works in iOS 10, but it doesn't on iOS 9 (tested on sim')

Yeah, unfortunately, I don't have a good answer. The fix I implemented follows Apple's documentation. It indicates either there is a slight difference in how PhotoKit works on iOS 9; that it most likely does not trigger the progress logic correctly in React Native.
I do not have time to debug at the moment, but that's where I would start. Set some breakpoints on on the progress handler and see how React Native is handling the progress reports (or even if they're fired at all):
https://github.com/facebook/react-native/blob/34f98210b1fd9e07e7a61298c03382cad5a8a892/Libraries/CameraRoll/RCTPhotoLibraryImageLoader.m#L69

authors: 6061960 gre ronaldheft samuelkraft


text:
Add Tencent Classroom app to the Showcase

add a Tencent education app 腾讯课堂 , which is a hybrid app , It's index page use ReactNative

@facebook-github-bot shipit

@WeweTom can you sign the CLA?

It looks like this PR changes a few unrelated apps too?
Thanks for sending this pull request. According to the guidelines in that file, "infoLink" must be one of:
1/ An English-language news article discussing the app, built either by a funded startup or for a public company
2/ An English-language technical post on a funded startup or public company blog discussing React Native
I am going to close this, but if you have one of those two things, feel free to reopen with a new link.

OK I think Hector and Martin disagree. I'm going to close but if you sign the CLA I will import it

Sorry to reply late. I have signed the CLA.

source: gharchive/pull-request

authors: WeweTom hramos lacker mkonicek


text:
clarify a message in preferences.xml

Especially for newcomers, this may help since some may think the effect is immediate.

Ah, isn't the reload automatic when preferences are changed?

OK I assume you sent this PR because you needed to reload manually. Adding the hint just in case won't hurt.
@facebook-github-bot shipit

authors: mkonicek vonovak


text:
Export Animated.Node for ease of type checking

Motivation
At present, there's no uniform way of determining whether you've received an Animated value node which can be attached to an animated prop.
You can attempt to use instanceof Animated.Value, but this fails for interpolated values. You can use instanceof Animated.Interpolation, but this fails for the values that are returned from the math functions (e.g., Animated.Add).
This commit exposes the base type from which all of these value nodes derive. As such, it is now possible to do the following:
import React, { Component, PropTypes } from 'react';
import { Animated } from 'react-native';

class Widget extends Component {
  static propTypes = {
    progress: PropTypes.instanceOf(Animated.Node).isRequired,
  }
  // ...
}

Test Plan
Unnecessary for cosmetic change.

The code currently tries to google-chrome, which your changed would override for linux users to chromium. Both of them are valid, can you instead change the open logic to try the two variants somehow?

The tests are extremely flakey. Any advice on how to get them to pass? (I can guarantee that my change is not responsible for these failures.)

Should we use export type ... construction for this?
https://flow.org/blog/2015/02/18/Import-Types/

@shergin, sorry for the delay.
export type gets stripped away during compilation. The reason I'm exposing this type is to enable type checking at runtime, via instanceof.
Any other hesitations about this?

authors: jamesreggio javache shergin


text:
[template] add jsc pickFirst packagingOptions

Summary
Fixes the following build failures on Android Studio (happening when using the 0.60 template):

cc @dulmandakh
Changelog

[Android] [Fixed] - Fixed a more than one file was found... lib/x86/libjsc.so build failure with the template
Test Plan

Build is now successful and the app starts with this change:

@Salakar I am sorry to introduce this issue.
Just doubt why there are multiple lib.jsc.
Could you please provide information below the screenshot you pasted?
IIRC there will have the path to the libjsc.so.

Hey @Kudo - this was just a fresh RN init of the template currently on 0.60-stable branch (no extra changes made) - there was also nothing extra after the screenshot sorry.
Reproducible example from the template is here: https://github.com/invertase/react-native-auto-link-example (npx command there to create a template - if you remove the 2 lines that I added as part of this PR - https://github.com/invertase/react-native-auto-link-example/commit/71d2cc7685394d96549fa8ee36648e5c4c77ce73 - the error will appear)

@Salakar Yes, the problem may related to 0.59.5 release.
The react-native-0.59.5.aar still introduced libjsc.so either by maven dependency or packed x86_64/arm64-v8a lib.jsc directly.
I am sorry that cannot pair 0.60 template with 0.59 AAR.
In the mean time that 0.60-rc not published yet, maybe to generate 0.60 AAR handy ./gradlew :ReactAndroid:installArchives

@Kudo I agree that this is most likely down to 59.5 as well.
Maybe it's still worth merging this though, in case anyone downgrades their template for whatever reason (it happens)?

@Salakar IMHO, pickFirst is not reliable to choose correct JSC.
If user like to choose android-jsc-intl from 0.60 but gradle pickFirst may use the JSC from 0.59 (which is no Intl supported).
Intl not defined error happens implicitly.
I would prefer to clarify how duplicated libjsc.so happens instead of just pass the build issue.
In fact, we are trying to remove the pickFirst for libc++_shared.so as well.
https://github.com/react-native-community/jsc-android-buildscripts/pull/95

@Kudo that's fair, how would you recommend we remove pickFirst behaviour as I can do another PR for this

@Salakar I still waiting for the PR which exclude libc++_shared.so being merged and release a new version to npm.

authors: Kudo Salakar


text:
fix: Eslint on Danger not matching project config

Summary
I've been noticing this for a while now, every time that someone changes a file inside rn-tester Danger comments a bunch of warnings regarding inline styles, e.g. https://github.com/facebook/react-native/pull/34567#issuecomment-1257956893, even though that is disabled inside .eslintrc https://github.com/facebook/react-native/blob/8edf4e9e3adcc85743e3c86a25ab3748b276a3da/packages/rn-tester/.eslintrc#L3
After some investigation, I realized that the problem was that the Eslint Node.js API used by @seadub/danger-plugin-eslint was not able to locate any .eslintrc files due to the location of the directory where danger is invoked. By using process.chdir we can ensure that eslint will run from the root folder and that it will be able to find all .eslintrc files
Changelog
[Internal] [Fixed] - fix eslint config when running Danger
Test Plan
run yarn danger pr https://github.com/facebook/react-native/pull/34976
After

Before

Woah, Great finding @gabrieldonadel! I think this happened when we moved danger in a node package within the packages folder.

authors: cipolleschi gabrieldonadel


text:
Format upon build

Not Reason proper, but very related. A frequent problem I've encountered when receiving external contributions is that people don't manually call refmt, through their editor or otherwise, when submitting changes. READMEs don't help.
I'm wondering if we can just (optionally) format the whole file at each build call. This requires build system hooks (cc @bobzhang), but in general I'd like to push editor-level tooling down to lower-level (see #993). This also leaves less to maintain for editor integration authors like @freebroccolo and others.

I've heard this feedback too. Here's something we can actually do without much invasive work in build systems, and without stepping on peoples' files under them in their editor. What do you think about this:

Have -pp refmt not only parse into an AST, but then also secretly print the file and compare it to the original. If it's different, as a final step, it could inject an extension point warning that may block the build (or perhaps we have it not block the build).

We could make it only behave this way in DEV mode, so production builds and builds as a dependency are not slowed down.

The warning could have a message like this printed to the console (or merlin):

Warning: Your file is not formatted according to convention.
Run the following command to format it:
refmt /path/to/myFile.re -print .re > /path/to/myFile.re

The benefit of this approach is that it requires no intervention from build systems (no work for BuckleScript), and doesn't clober files out from under you.
I would also have printing store an AST attribute like [@refmt width = 120] at the top of the file when printing to text so that it automatically detects the last-used width without having to supply it on the command line.

Btw your unix command would erase the file, remember? =P
It's nice not needing build system intervention, but your solution (step 1) still requires manual calling of refmt in the editor/terminal?

@chenglou Okay imagine something like:
./fixMyFiles.sh

And it wouldn't be needed if you just run the formatter from within the editor.
Clobbering source files can be really bad and much worse than making people run a command line command or key command in their editor. For example if you undo, undo, undo, and then something clobbers the file contents in a source file, it destroys the redo stack! (Except in Vim, naturally).

Right, but my point was to remove the manual and editor-level need of calling refmt. Such build system behavior would be opt-in or opt-out btw.

if you undo, undo, undo, and then something clobbers the file contents in a source file, it destroys the redo stack!

That's true, yeah. But we can still make it opt-in/opt-out.

I want to believe that you could use Travis to refmt the code in the PR and diff it against the original code to make sure nothing changed.
This would only work with projects that can afford to have something like Travis though.
Since we want the least amount of commands to be ran, and the user still has to run the build command (or watch), I think it wouldn't be so bad to add it to the build system.

@chenglou @jordwalke the unix command can use the new --in-place flag!

@bobzhang would it be possible to expose a onFileChange hook in bsb? I'm thinking that it's probably not possible to have it in Ninja? What about in the watcher?
cc @rickyvetter

I worry that it would have race conditions with editors

How so? Btw it'll be opt-in

Since both editors and build systems are writing you me files

If you don't save a file, the watcher wouldn't detect the change right?
To be clear, I'm thinking to have this at the watcher level. More performant. Otherwise the build system would have to know which files you've changed, change them again, then start the build. That's what I meant by ninja maybe not supporting such thing.
Save file -> trigger watcher -> trigger save (either through watcher, or build system pre-build hook) -> format -> build

it is not that simple, since there would be delay, then it would cause concurrency and race condition

I may be missing something but I think the only way you could avoid what @bobzhang is describing would be to lock the editor document for the file to be reformatted until the operation is finished. Otherwise, even if you force a save of the document, the user might make another edit before the reformatted content is returned.
In the case of vscode, it will complain loudly if the document is dirty and the file has also been changed outside of the editor (because the two might have diverged). It will refuse to let you save the document again until you jump through several hoops. And I don't even think it's possible to lock the document with the current API, at least not in a clean way.

Sigh, just tested this workflow. Vim can't update this correctly without installing an external plugin, and atom occasionally craps out and resets the cursor to line 0 when the file's long (long for atom, aka 400 lines). Guess we can't have this =|
Thanks for the feedback folks!

Woah I really think this is a premature close here. Elm has this working on Atom, Vim (without extra deps), VS Code and others. I get that this behavior could potentially be problematic, but as an opt in feature for projects with multiple contributors this seems like it's worth pursuing.

For the record, the latest release of the Reason vscode plugin supports format-on-save as an option. That part is not problematic. The difficulty is being able to support format-on-build given the asynchronous nature of editing.
For vscode, format-on-build support would require being able to lock the document (or rather all of the documents being built) until after the build finishes. I think that in practice this would make for a pretty awkward workflow even if one could do it with the current API (currently there is no support for locking documents like this).
The only potential workaround I see for that would be to cause a build to trigger a save, then listen for the save event and stall until the build finishes. That might work, assuming that builds complete quickly enough, but part of it would have to be done synchronously (which could case lag or other issues) and it would also interfere with other save operations.
I do think that having format-on-build support is good for external tooling (especially for CI and code review stuff) but I don't think it's the right fit many editor architectures. The reality is that supporting something like this in vscode would be significantly more work and less reliable than the current approach of just calling refmt when needed.

Ahhh - my mistake. I wasn't thinking of the differences between formatting on save and on build. Makes sense to me.

One day editors will hot reload correctly without losing cursor!

authors: bobzhang bsansouci chenglou freebroccolo jordwalke rickyvetter tekknolagi

repo: facebook/reason


text:
Reference to x::x instead of ~x in label docs

Readings docs at airport so will be succinct.
In this doc there are still a few stray references to "::".
https://reasonml.github.io/guide/language/function

This is especially confusing in the note about unit () and currying. Since the function call syntax changed I don't think the explanation on why you always have to use () in the definition of a labeled function makes sense anymore.

The comment explaining why currying labels to explain why () must be passed comes before the section that introduces currying. That doesn't help to clarify the explanation.

Fixed, thanks =)

authors: chenglou faassen


text:
Fix the missing notification on WebSocket handshake response received

Now the session information can be displayed correctly

@jasta review please~

Wow, I'm so sorry about missing this!  Thanks for the fix and we'll be pushing out v1.5.1 soon with a big rollup of dangling fixes like this.

authors: jasta misakuo

repo: facebook/stetho

license: mit

license_source: bigquery


text:
Fix index size comparison, cannot be equal

The array is zero indexed, so it should not be equal to the size ever.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thanks for your pull request. I apologize for leaving this project in limbo and not addressing your concerns. I have archived this project after doing a final release to make it compatible with React v16.

repo: facebookarchive/fixed-data-table


text:
Error in { : task 1 failed - "invalid 'times' argument"

Project Robyn
Describe issue
I tried robyn_run  in the setting below;
OutputModels <- robyn_run(   InputCollect = InputCollect,   iterations = 2000,   trials = 5,   outputs = FALSE )
But I just received the error;
Error in { : task 1 failed - "invalid 'times' argument" Timing stopped at: 0.143 0.047 0.212
So please let me know how to solve it...
Provide dummy data & model configuration
Issues are often related to custom input data that is difficult to debug without. If necessary, please modify your data to mask real values and share a dataset that is able to reproduce the issue. Please also share your model configuration.
Environment & Robyn version
R version (R --version)
Please make sure you're using the latest Robyn version

The above issue was solved.
I put only one channel data. Maybe it was the reason of this error.
Let me close this issue.

repo: facebookexperimental/Robyn


text:
refactor: adjust background color of dark navbar

Related with https://github.com/facebook/docusaurus/issues/3937
Dark style of navbar should be the same color as "default" navbar when dark mode is enabled. This is the most expected and sensible behavior if the user only wants to have dark navbar  whose background color should be identical to that of the navbar in dark mode.
Before:

After:

I don't understand the explainations 😅 After looks fine though 👍

If you enable dark mode on Docusaurus website, you will notice that the navbar background has changed from white to dark color (which is expected). So I suggest using that color for dark style of navbar.

It doesn't work that way, because the background color of the navbar relies on the ifm-background-surface-color variable, which changes depending on selected color mode, meanwhile for the dark navbar we need unchanged (dark) color.

repo: facebookincubator/infima


text:
[GCS] Provide unit test for the case when a file does not exist in a bucket but it cannot be written to the bucket.

Description
The support for the GCS Filesystem does not have a test for this sequence that may fail:

The metadada for this pair (bucket:key) does not exist then proceed to the write
An object is tried to be written to the pair (bucket:key).
The write operation fails then throw an exception.

There is no unit test to cover the exception in point 3.

Could any of the maintainers assign me as owner of this enhancement please?
Thanks in advance.

repo: facebookincubator/velox


text:
sum(bigint) needs to check for overflow

Bug description
In Presto, SUM(BIGINT) checks for overflow. In Velox, it doesn't.
com.facebook.presto.spi.PrestoException: bigint addition overflow: 4098410247810426670 + 5602492956270666201
	at com.facebook.presto.type.BigintOperators.add(BigintOperators.java:75)
	at com.facebook.presto.operator.aggregation.LongSumAggregation.sum(LongSumAggregation.java:37)
	at com.facebook.presto.$gen.BigintBigintSumGroupedAccumulator_20230924_052933_4062.addInput(Unknown Source)

This issue was discovered by running AggregationFuzzer with Presto as source of truth.
CC: @laithsakka @duanmeng
System information
n/a
Relevant logs
No response

@mbasmanova It seems that there is already an overflow check for sum(bigint) in https://github.com/facebookincubator/velox/blob/main/velox/functions/prestosql/aggregates/SumAggregate.h#L152, and related test in https://github.com/facebookincubator/velox/blob/main/velox/functions/prestosql/aggregates/tests/SumTest.cpp#L596

@duanmeng You are correct. I tried reproducing this again, but can't. I'm going to close this issue and reopen if I see it again. Thanks.

authors: duanmeng mbasmanova


text:
Make Window frame negative offsets test more robust

Use a randomly generated negative offset in the test to make the test more robust.

@kagamiori : Please can you help with review and merge.

@kagamiori : Thanks for your review comment. Have updated the code. PTAL.


text:
Allow creating ConstantTypedExpr of complex-type NULL without passing an actual vector

Summary: The constructor ConstantTypedExpr(std::shared_ptr<const Type> type, variant value) allows creating a ConstantTypedExpr without passing an actual vector. This interface, however, doesn't work for complex types. There are cases where users would like to create a ConstantTypedExpr of complex-type NULL. So this diff allows creating such ConstantTypedExpr through the aforementioned interface. (Note that only null constant is supported for complex types.)
Differential Revision: D38092564

And please limit the description to 80 characters per line.

authors: kagamiori majetideepak


text:
ValueError: Sequence length 1042 above maximum sequence length of 1024.

code:
python extract.py esm1b_t33_650M_UR50S AB024414.fasta esm1b/AB024414 --repr_layers 0 32 33 --include mean
Bug description
Transferred model to GPU
Read /home1/……/AB024414.fasta with 65 sequences
Processing 1 of 11 batches (16 sequences)
Processing 2 of 11 batches (11 sequences)
Processing 3 of 11 batches (9 sequences)
Processing 4 of 11 batches (7 sequences)
Processing 5 of 11 batches (5 sequences)
Processing 6 of 11 batches (5 sequences)
Processing 7 of 11 batches (4 sequences)
Processing 8 of 11 batches (3 sequences)
Traceback (most recent call last):
File "extract.py", line 136, in
main(args)
File "extract.py", line 95, in main
out = model(toks, repr_layers=repr_layers, return_contacts=return_contacts)
File "/home1/……/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home1/……/tool/esm/esm/model.py", line 136, in forward
x = x + self.embed_positions(tokens)
File "/home1/……/anaconda3/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, **kwargs)
File "/home1/……/tool/esm/esm/modules.py", line 242, in forward
f"Sequence length {input.size(1)} above maximum "
ValueError: Sequence length 1042 above maximum sequence length of 1024.
Do I need to split my protein sequence into lengths of 1024?
Why there is an issue like this? I would be appreciated that if you could help me.

Thanks for your question!
During the training process we cropped sequences >1024 sequences, so the model (specifically the learned positional embeddings) can not handle longer sequences.
See #21 and #76 for prior discussion on this topic.

repo: facebookresearch/esm


text:
fairseq-preprocess: command not found

I have used 'pip install --editable .' to install fairseq-preprocess and it ends with no error. Yet when I run the command it still gives command not found error. And I can see that the file is under

/.local/bin

directory. I dont know why I am getting the error.
Can someone who knows help?

FYI

@ceatlinar are you on windows?

Hi. No I am on Google cloud instance, a Linux one. The problem was about the path, I corrected it and therefore closing the issue. Thankss @lematt1991

Were you ever able to find a solution for this?

repo: facebookresearch/fairseq


text:
Env seems not to read config file value after edit

Habitat-Lab and Habitat-Sim versions
Habitat-Lab: master
Habitat-Sim: v0.2.0.2021.07.25 (nightly build) (master gives me errors)
Docs and Tutorials
I checked this tutorial
https://github.com/facebookresearch/habitat-lab/blob/master/docs/pages/habitat-lab-demo.rst
❓ Questions and Help
What I need to do: I need to set MAX_EPISODE_STEPS and SIMULATOR.RGB_SENSOR.WIDTH (and height) from my python script, not from the yaml file. The yaml file has some placeholder values.
What I tried: following the tutorial, I either try to pass these variables as opts or defrost and freeze the config file after loading it, and before passing it to NavRLEnv.
What happens: MAX_EPISODE_STEPS and width / height are properly changed in the config file, but when I pass it to NavRLEnv the old value (yaml placeholder) is read.
Minimal example:
from habitat.datasets import make_dataset
from habitat_baselines.config.default import get_config
from habitat_baselines.common.environments import NavRLEnv

config_path = 'pointnav_apartment-0.yaml' # Custom yaml with ENVIRONMENT.MAX_EPISODE_STEPS set to 500

opts = ['BASE_TASK_CONFIG_PATH', config_path] # I need this or `get_config` will look for `pointnav_nomap.yaml` by default.
opts += ['ENVIRONMENT.MAX_EPISODE_STEPS', 100]

config = get_config(config_paths=config_path, opts=opts)

print(config.ENVIRONMENT.MAX_EPISODE_STEPS) # This outputs 100

dataset = make_dataset(id_dataset=config.TASK_CONFIG.DATASET.TYPE,
                       config=config.TASK_CONFIG.DATASET)

env = NavRLEnv(config=config, dataset=dataset)

print(env._env._max_episode_steps) # This outputs 500

The same happens if I try as in the tutorial
config.defrost()
config.ENVIRONMENT.MAX_EPISODE_STEPS = 100
config.freeze()

Not sure if I am doing something wrong or if it is a bug.

It should be TASK_CONFIG.ENVIRONMENT.MAX_EPISODE_STEPS

It should be TASK_CONFIG.ENVIRONMENT.MAX_EPISODE_STEPS

It works, thanks! It also works for observation width and height, awesome :)

authors: erikwijmans sparisi

repo: facebookresearch/habitat-lab


text:
[Web] Add flag to enable SIMD instructions in WASM

Motivation and Context

Adds a flag that can enable building the Web build of Habitat to use SIMD. This should speed up physics and other linalg heavy vectorization hopefully ~quite significantly~. The browser must support SIMD in WASM like modern versions of Chrome though.
To enable pass the --simd flag to build_js.sh
Also fixes a small bug with pre-commit that prevented shell check from running on build.sh and build_js.sh .

How Has This Been Tested

Locally and with CI.

Types of changes

[X] Docs change / refactoring / dependency upgrade
[X] New feature (non-breaking change which adds functionality)

Checklist

[X] My code follows the code style of this project.
[X] I have read the CONTRIBUTING document.
[X] I have completed my CLA (see CONTRIBUTING)
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

quite significantly

(With my skeptical hat on.) Do you have some numbers to back this? I'm interested in how much this helps in a codebase of this size.

@mosra Probably not on Magnum, but WASM doesn't even enable SSE2 instructions without this flag for Bullet so it should give a speed up there.

It's not as simple as "enabling SSE2" since WASM has to work on ARM as well -- and that's why I'm skeptical, because different platforms have different instructions and what could directly map to a SSE instruction might have to be emulated on NEON and vice versa.
But in any case I really want to know how this helps, seriously :) Did you try it out? I know from certain projects that hand-coded WASM SIMD can be four to six times times faster than scalar code, but have no idea about autovectorization, especially when combined with everything else we're running here. Is it 1%? 10%? 2x faster?

I tried this on my webxr hand demo benchmark, which drops a lot of objects in a big pile and tries to step physics 60 times per second (or 16.7 ms per stepWorld() call). I repeated the benchmark 3 times with and without the --simd flag and here were the results:
without --simd:
78.76
72.60
82.87
with --simd:
79.75
84.07
83.48
These numbers are the average ms between stepWorld() calls. Note that it's trying to achieve 16.67ms per stepWorld() call but cannot keep up. So it doesn't seem like this SIMD optimization has helped much in this case.

authors: Skylion007 ldcWV mosra

repo: facebookresearch/habitat-sim


text:
Issues about testing time

I evaluate the rl_agent with Detic via:
python projects/habitat_ovmm/eval_baselines_agent.py --baseline_config_path projects/habitat_ovmm/configs/agent/rl_agent.yaml

However, it was found that the time to run 1199 episodes took 52 hours, is this correct?
I notice that #374 mentions the same issue, the test is slow and the GPU has less than 3G of memory.
I have ensured the following parameter settings in projects/habitat_ovmm/configs/env/hssd_eval.yaml
NO_GPU: 0
PRINT_IMAGES: 0

By the way, is there any way to speed up the test? Like loading Detic on another GPU.

I meet same problem, and I tried to change the yaml 'NUM_ENVIRONMENTS', but the platform seems not to support more environments.😥

repo: facebookresearch/home-robot


text:
libtorch.so.1: undefined symbol:

❓ Questions and Help
When I execute the command 'python setup.py build develop' in the Installation.md. I got the following mistakes:
Traceback (most recent call last):
File "setup.py", line 7, in
import torch
File "/home/caomeng/anaconda3/envs/maskrcnn_benchmark/lib/python3.7/site-packages/torch/init.py", line 84, in
from torch._C import *
ImportError: /home/caomeng/anaconda3/envs/maskrcnn_benchmark/lib/python3.7/site-packages/torch/lib/libtorch.so.1: undefined symbol: _ZTIN2at10TensorImplE
(maskrcnn_benchmark) caomeng@adsplab-vision:~/github/maskrcnn-benchmark$ python setup.py build develop
Traceback (most recent call last):
File "setup.py", line 7, in
import torch
File "/home/caomeng/anaconda3/envs/maskrcnn_benchmark/lib/python3.7/site-packages/torch/init.py", line 84, in
from torch._C import *
ImportError: /home/caomeng/anaconda3/envs/maskrcnn_benchmark/lib/python3.7/site-packages/torch/lib/libtorch.so.1: undefined symbol: _ZTIN2at10TensorImplE

environment:
Ubuntu 14.04
Pytorch 1.0
cuda 8.0.61
cuDNN 6.0.21

Hi,
This generally happens when your PyTorch installation is not the same as the one you used to build maskrcnn-benchmark.
Try doing the following:
import torch
print(torch.__version__)

and see if it is indeed a 1.0 release of PyTorch.
Also, please copy and paste the output from the
environment collection script from PyTorch
(or fill out the checklist below manually).
You can get the script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

PyTorch Version (e.g., 1.0):
OS (e.g., Linux):
How you installed PyTorch (conda, pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

Thank you. Actually, I create a new environment using conda and install pytorch just following the instruction in the INSTALL.md. I used to use pytorch0.4.1. But when I try to print the version of pytorch, I got the same mistake.

Can you try uninstalling maskcnn-benchmark and install it again?
Also, what is the output of print(torch.__version__), it gives the date as well if it's 1.0, so that I check if there is a bug in that particular version of pytorch

When I try to import torch, here comes the following errors:
Traceback (most recent call last):
File "", line 1, in
File "/home/caomeng/anaconda3/envs/maskrcnn_benchmark/lib/python3.7/site-packages/torch/init.py", line 84, in
from torch._C import *
ImportError: /home/caomeng/anaconda2/lib/libgio-2.0.so.0: undefined symbol: g_type_check_instance_is_fundamentally_a

You seem to have an old pytorch installation laying around that is mixing up symbols, see that you have two anacondas,
/home/caomeng/anaconda3/

and
 /home/caomeng/anaconda2/

And one is picking files from the other.

Sorry for replying late. I have removed Anaconda3. However, I still got errors as follows when I try to import torch.
Traceback (most recent call last):
File "", line 1, in
File "/home/caomeng/anaconda2/envs/pytorch1.0/lib/python3.7/site-packages/torch/init.py", line 84, in
from torch._C import *
ImportError: /home/caomeng/anaconda2/envs/pytorch1.0/bin/../lib/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var

that looks like a bugged install, where probably your anaconda2 was depending on anaconda3?

authors: fmassa rookiecm

repo: facebookresearch/maskrcnn-benchmark


text:
[flava][checkpoints] Config for lightning checkpoints

Stack from ghstack (oldest at bottom):

-> #75

Differential Revision: D37008469

@ivankobzarev has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

repo: facebookresearch/multimodal


text:
Does it support language other then english? I wanted it to try for japanese text but I cant.

KIndly let me know if there is chance or method to use it on japanese text

The dataset was mostly in english. There is some support for other latin based languages but I was unable to find data sources for non-latin script languages as japanese.
So to answer your question, no at the moment it is not possible to use nougat for japanese text.

repo: facebookresearch/nougat


text:
Inquiry on Using Custom Mesh in SS 2.0 and Related File Formats

Hi, @ChanganVR ,
I would like to seek further clarification regarding the utilization of my custom mesh in SS 2.0. I have created a quite simple mesh using the code below and generated a JSON file containing semantic labels for the mesh, such as 'floor' and 'ceiling'.
Nevertheless, it appears that these semantic labels are not functioning as expected. Despite SS being able to simulate RIRs, the absorption properties of the acoustic materials do not seem to be worked. I have modified the absorption coefficients of the acoustic materials corresponding to the semantic labels 'floor', 'ceiling', and 'wall' to 0.99 to test their functionality, but without success.
I would be grateful if you could provide guidance on the following questions:

How can I incorporate acoustic properties into my custom mesh?

Could you kindly explain the purpose of the JSON file in the mp3d data (17DRP5sb8fy)? It includes .house, _semantic.ply, and .navmesh files. To my knowledge, the PLY format does not support semantic information. I am interested in understanding the roles of .house and _semantic.ply files and the procedure for assigning semantic label information to my custom GLB mesh file.

Is there any example format of JSON to assign semantic information to my custom and simple GLB mesh?

Thank you for your time and assistance. I look forward to your insights on this matter.
p.s. I kindly request your understanding, as my primary expertise is in acoustics and audio, and I am fairly new to mesh-related concepts and formats. Any guidance or resources you could provide would be greatly appreciated.
## code for build mesh ##
import trimesh
import numpy as np

all_corners3d = np.array([
    [-3, -3, -3],
    [3, -3, -3],
    [3, 3, -3],
    [-3, 3, -3],
    [-3, -3, 3],
    [3, -3, 3],
    [3, 3, 3],
    [-3, 3, 3]
])

floor_faces = np.array([
    [0, 1, 2, 3],
])
ceiling_faces = np.array([
    [4, 5, 6, 7],
])
side_faces = np.array([
    [0, 1, 5, 4],
    [1, 2, 6, 5],
    [2, 3, 7, 6],
    [3, 0, 4, 7]
])

floor_mesh = trimesh.Trimesh(vertices=all_corners3d, faces=floor_faces)
ceiling_mesh = trimesh.Trimesh(vertices=all_corners3d, faces=ceiling_faces)
side_mesh = trimesh.Trimesh(vertices=all_corners3d, faces=side_faces)

mesh = floor_mesh + ceiling_mesh + side_mesh

metadata = {
    "floor": {
        "id": list(range(len(floor_faces))),
        "label": "floor",
    },
    "ceiling": {
        "id": list(range(len(floor_faces), len(floor_faces) + len(ceiling_faces))),
        "label": "ceiling",
    },
    "wall": {
        "id": list(range(len(floor_faces) + len(ceiling_faces), len(floor_faces) + len(ceiling_faces) + len(side_faces))),
        "label": "wall",
    }
}

mesh.metadata = metadata

mesh.export("test_mesh.glb")
with open("test_mesh_metadata.json", "w") as json_file:
    json.dump(mesh.metadata, json_file)

## code for RIR simulation ##
import quaternion
import habitat_sim.sim
import numpy as np
import matplotlib.pyplot as plt

backend_cfg = habitat_sim.SimulatorConfiguration()
backend_cfg.scene_id = 'test_mesh.glb'
backend_cfg.scene_dataset_config_file = 'test_mesh_metadata.json'
backend_cfg.load_semantic_mesh = True
backend_cfg.enable_physics = False

agent_cfg = habitat_sim.agent.AgentConfiguration()
cfg = habitat_sim.Configuration(backend_cfg, [agent_cfg])
sim = habitat_sim.Simulator(cfg)

audio_sensor_spec = habitat_sim.AudioSensorSpec()
audio_sensor_spec.uuid = "audio_sensor"
audio_sensor_spec.enableMaterials = False # make sure _semantic.ply file is in the scene folder
audio_sensor_spec.channelLayout.type = habitat_sim.sensor.RLRAudioPropagationChannelLayoutType.Mono
audio_sensor_spec.channelLayout.channelCount = 1
audio_sensor_spec.acousticsConfig.sampleRate = 8000
audio_sensor_spec.acousticsConfig.direct = False #in our src/mic configuration, we do not need direct sound
audio_sensor_spec.acousticsConfig.indirect = True
audio_sensor_spec.acousticsConfig.indirectRayCount = 5000
audio_sensor_spec.acousticsConfig.diffraction = True
# audio_sensor_spec.acousticsConfig.transmission = False
audio_sensor_spec.acousticsConfig.meshSimplification = True
audio_sensor_spec.acousticsConfig.globalVolume = 1.
audio_sensor_spec.acousticsConfig.threadCount = 8
audio_sensor_spec.position = [0., 0., 0.] #do not need sensor's position on agent robot

sim.add_sensor(audio_sensor_spec)
audio_sensor = sim.get_agent(0)._sensors["audio_sensor"]
audio_sensor.setAudioSourceTransform([0., 0., 0.]) #source position located at origin
audio_sensor.setAudioMaterialsJSON("utils/mp3d_material_config.json") # absorption coefficients of acoustic materials that has label floor, ceiling, and wall are 0.99

# ring-array microphone array that has 10 cm radius from source
mic_pos = np.array([
    [ 5.00000000e-02,  8.66025404e-02,  6.12323400e-18],
    [-5.00000000e-02,  8.66025404e-02,  6.12323400e-18],
    [-1.00000000e-01,  1.22464680e-17,  6.12323400e-18],
    [-5.00000000e-02, -8.66025404e-02,  6.12323400e-18],
    [ 5.00000000e-02, -8.66025404e-02,  6.12323400e-18],
    [ 1.00000000e-01, -2.44929360e-17,  6.12323400e-18]
])
obs = np.zeros((mic_pos.shape[0], 1024)) # [6 mics, rir_length:1024]

agent = sim.get_agent(0)
agent_state = agent.get_state()

for now_mic in range(mic_pos.shape[0]):
    agent_state.position = mic_pos[now_mic, :]
    agent.set_state(agent_state)
    obs[now_mic] = np.array(sim.get_sensor_observations()["audio_sensor"]).squeeze()[:rir_len]

for i in range(mic_pos.shape[0]):
    plt.subplot(mic_pos.shape[0], 1, i+1)
    plt.plot(obs[i, :])
plt.savefig('test_rir.png', dpi=300)

Hi @iyeon915 sorry for the late reply. To debug this, I think the first step is to make sure that the installation is correct and that you can modify the acoustics attributes for existing supported datasets. As mentioned in the other issue (we're still investigating why the materials do not work for HM3D), the material customization should work for MP3D and Gibson. And for example, if you change the coefficients for these environments, you should see the behavior changes accordingly.
Once it works, you can modify your mesh and semantic file accordingly to be close to the format of them in order to be loaded and used by SS 2.

repo: facebookresearch/sound-spaces


text:
How to show the name of pane in browser?

Hi, I have some trouble to find the way showing the name of pane. If you have more than one plots in same kind, such two histograms plot to show the distribution of train/valid datasets, it is inconvenient to distinguish each other without the name of pane.
Thanks.

I find the solution. use opts = dict(layoutopts ={'plotly': {'title': 'my_title'}}.

repo: facebookresearch/visdom


text:
Refactor keys

Move keys into a separate module and create individual classes for each type of cryptographic key.

I will make another pass through this to make sure there are no other changes necessary, but overall I think it's good to start reviewing.

repo: factomatic/py-factom-did


text:
doc: zh_CN translation

add zh_CN translation in README_zh_CN.md and a link in the original readme to it.

PTAL
I discovered this nice repo about 3 years ago, forked it, translated added a feature to denote a specific save to load using env, now I found that the original repo is evolving, and the feature I added in my fork is already implemented.
So I think it is time to amend the translation for the rest of the README file and give up my own fork.
I promise that I will update the translation regularly. PTAL

and rebased

repo: factoriotools/factorio-docker


text:
Official template

Hi faeron,
can I add it to moleculer organization as typescript project template?

Yes totally!
If you don't miss anything.

Great! I think this template is done.

I just try to give you ownership/right to change ownership to moleculer organization.

Thx, I accepted the invite, but I have no right to see the "Settings" in the repo.

Seems to be a github restriction. Collaborators only have rights to push to repository. I PMed you on gitter.

authors: faeron icebob


text:
Update index.md: add publish relative path description

添加：发布路径中的描述：可填写相对目录的使用说明。

三个修改的内容都是一样的，因为之前没这么用过GitHub，在线编辑的比较发现和使用其他Git管理软件的显示不太一样，以为出问题了，所以改了3次确保。

你这样整个文件都发生变动的，我很难接受的。

我自己改一下吧。谢谢你的贡献。

authors: javelinlin xiaoguzhu


text:
Brucemacd/mem calc

Brucemacd/mem calc

Brucemacd/mem calc


text:
Support for closing filelike response stream objects

Described more completely in #960 .

Current coverage is 95.71% (diff: 93.75%)

Merging #961 into master will decrease coverage by 4.28%

@@           master       #961   diff @@
========================================
  Files          31         31
  Lines        2031       2008    -23
  Methods         0          0
  Messages        0          0
  Branches      328        329     +1
========================================
- Hits         2031       1922   -109
- Misses          0         66    +66
- Partials        0         20    +20

Powered by Codecov. Last update f552316...6c34f7f

Hi @hozn, just following up to see if you'd be able to work on this soon? Hoping to get a new Falcon release out and it would be great to include this patch. Thanks!

Yeah, sorry, I'll take a look here and see if I can wrap this up.

Hopefully the updated doc string is more helpful.

Thanks!

authors: codecov-io hozn kgriffs

repo: falconry/falcon


text:
fix: generate maintainers.md entry for subdir maintainers

What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
What this PR does / why we need it:
Fixes the automated tool to add entries in MAINTAINERS.md for maintainers of repo subdirectories.
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 5274bb1eca382a763623b672ad154ca5c217cfef

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: jasondellaluce poiana

repo: falcosecurity/evolution


text:
fix(docs): corrected run with docker command at README

Signed-off-by: Mert Can Bilgic mert.bilgic@trendyol.com

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area tests

What this PR does / why we need it:
In the documentation for Running with Docker, the command was wrong. This PR fixes this command. You can check the screenshots below.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @leogr

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: a2d3fddd065c0ee00d7773bd485f358516dac288

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danpopSD, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danpopSD, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danpopSD, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danpopSD, Issif, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: danpopSD mertcb poiana

repo: falcosecurity/falcosidekick-ui


text:
Kafka authentication/encryption

Motivation
I would like to use the Falcosidekick Kafka output to communicate with a public Kafka endpoint. This does require authentication and encryption to secure the connection between Falcosidekick and the Kafka endpoint.
Feature
Enable authentication and encryption for Kafka in Falcosidekick. Mutual TLS seems to be a good choice, as it has already been implemented for many Falcosidekick outputs and is supported by Kafka.
Alternatives
An alternative is to create a private tunnel between the nodes running Falcosidekick and Kafka. This adds additional complexity and is not a preferred solution.

@cpanato as you integrated the Kafka output, do you want/can to work on that? 🙏

@Issif yes i can take care
just need to read something about kafka auth and encrypt. @renehonig do you have any handy docs? :)

@cpanato, we could make also a little session togther. We use, for example most of the time SASL or client cert.

Hi, I did not see this issue but I had the same problem.
I did implement SASL + TLS here : https://github.com/WaldoFR/falcosidekick however it seems that the project kafka-go is not very resilient, I got two major issues :

Topic autocreate has not been implemented :  https://github.com/segmentio/kafka-go/pull/700
When a client is created, it try to interfer with all topics on brokers : https://github.com/segmentio/kafka-go/issues/690

I'd like to reimplement the client to use confluent-kafka-go instead wich seem more reliable. If everyone is ok I'll reimplement this part to use confluent's module and realize a PR.
Regards,

@WaldoFR first implementation of kafka output by @cpanato used confluent-kafka-go but we switched to current library because we had trouble with the C libraries dependency. See #139

@WaldoFR, Question would be, if confluent-kafka-go is compatible with other kafka services too? Like Strimzi or Avien...

@dirien, @WaldoFR , Thanks for your work on this issue. I think it is compatible with other Kafka distributions too. The readme says:

Future proof - Confluent, founded by the
creators of Kafka, is building a streaming platform
with Apache Kafka at its core. It's high priority for us that client features keep
pace with core Apache Kafka and components of the [Confluent Platform](https://www.confluent.io/product/compare/

Is it based on librdkafka, which is a generic Kafka library.

There is a PR https://github.com/segmentio/kafka-go/pull/700 in kafka-go module, it's not merged yet but it might solves both issues mentioned in my last post. I'm going to verify that today, if it solve both issues the best might be to keep this module to avoid new unexpected problems from an other module.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

authors: Issif WaldoFR cpanato dirien poiana renehonig

repo: falcosecurity/falcosidekick


text:
fix(go.mod): change the module path to reflect the new repository

This PR fixes the module path for the project.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM

authors: Andreagit97 alacuku poiana


text:
Fix repository hints being ignored

Signed-off-by: Radu Andries radu.andries@sysdig.com

What type of PR is this?
/kind bug

Any specific area of the project related to this PR?
/area cfn-runtime

What this PR does / why we need it:
This bug prevents us from using external repo hints in images

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign admiral0 after the PR has been reviewed.
You can assign the PR to them by writing /assign @admiral0 in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 80371c51e981261c42068e09cca2a70a5a77df55

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

repo: falcosecurity/kilt


text:
fix(build): update latest even if higher prereleases are present

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build
What this PR does / why we need it:
If rules marked as 1.0.0, 1.0.1 and 2.0.0-rc1 are present, when 1.0.2 is released it should still be latest because 2.0.0 is not out yet. Fix the build process to consider this case (note the attached test)
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [LucaGuerra,incertum]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 22b5ec003a7e6789a2114af6f05851f22f42430a

authors: LucaGuerra poiana

repo: falcosecurity/rules


text:
Implement routing for questions route

Implements post and get requests for questions routes. Connection to database has to be achieved.

Looks good

authors: erikbarzdukas janhellmich

repo: familiar-protein/familiar-protein


text:
[Optimization] Reduce bundle size

Initial conversation: https://warpcast.com/timdaub/0x1905b4
https://www.framer.com/motion/guide-reduce-bundle-size/
npm ls framer-motion
web@0.0.0 /Users/timdaub/Projects/attestate/kiwistand/src/web
└─┬ connectkit@1.2.4
└── framer-motion@6.5.1
and so I looked into connectkit's usage of framer motion and saw some optimization potential (e.g. using "m" instead of "motion". Are you interested in me applying the changes from that blog post?
https://github.com/search?q=repo%3Afamily%2Fconnectkit framer-motion&type=code

Hey @TimDaub!
You're welcome to give optimisations a shot and we can give it a look, but worth mentioning that I've spent some time previously trying to migrate motion to m but this seemed to only save us about 20-30kbs, and it also caused some animation issues.
Worth noting that we eventually would like to look into removing framer-motion in the future to lower the file size of ConnectKit, and there's also a few other optimisations that could be done with SVGs and some minor refactoring that we have in our internal to-do list.

authors: TimDaub lochie

repo: family/connectkit


text:
Handle merge conflict with identical roots

When two roots are received from the same user pointing to the same ethereum block in the rootBlock value, the design doc says that we should keep the roots with the lowest lexicographical order. This method was chosen because it allows a deterministic way to resolve conflicts that can be performed independently by each node.
A good solution would:

Choose an algorithm for lexicographical ordering of hash values
Implement the logic to order it in the addRoot function of the engine
Write tests to validate the behavior.

The important part here is that we have defined lexicographical in a formal way such that anyone implementing this in another language knows exactly how the comparison function should work, and even knows what tests to run against such an algorithm to ensure that it is working correctly.

currently working through this. first attempt will be to model after C's strcmp which compares strings based on the ascii values of the char at each index.

ascii value comparison seems like the right approach. if javascript's native comparison does the same thing, maybe we're all set and just need to write tests to make the behavior clear.

as stated here https://stackoverflow.com/questions/56094122/compare-two-strings-with-and-operators-in-javascript it says the standard splits it into 16 bit values where as ascii uses 7. prob worth explicitly using ascii IMO

repo: farcasterxyz/node-playground


text:
GloVe embeddings

Merging this pull request will add a wrapper for pre-trained GloVe Embeddings to keras-contrib.
The code for loading the GloVe Embedding into a keras embedding was originally written by FChollet I have added in cacheing and wrapped the implementation in a function.  This has made it a lot easier for me personally to test different models using a variable size GloVeEmbedding so I decided to make a pull request.
My original repository is available here.
The pre trained GloVe Embeddings available come from here.
Supported sizes are [50,100,200,300].
Coming in the next release:

GloVeEmbeddings in from multiple data sources.

I see that there are some failing tests; I will fix those and then re-open the PR.

Re-opened pull request, added docstring and tests.

Are there some specific function of GloveEmbedding?

GloVe is an unsupervised algorithm for creating dense vector representations of words.  You can use these to prevent the need for taking the huge amount of time required to train your own embedding.
Training your own embedding makes the number of trainable parameters in a model ridiculously large causing long training times.
You get much stronger representations using pre-trained GloveEmbeddings.
If you are asking about my specific implementation then the answer is no, but it is much easier to construct a GloveEmbedding using my wrapper than it is from scratch.  Assuming you already have the embedding downloaded here is the code required to get a pre-trained embedding:
`
EMBED_SIZE = int(size)
fname = "glove.6B.300d.txt"

embeddings_index = {}
for line in open(fname):
    values = line.split()
    word = values[0]
    coefs = np.asarray(values[1:],dtype='float32')
    embeddings_index[word] = coefs

embedding_matrix=np.zeros((len(word_index)+1,EMBED_SIZE))
for word,i in word_index.items():
    vec = embeddings_index.get(word)
    if vec is not None:
        embedding_matrix[i] = vec

embedding_layer = Embedding(
        len(word_index)+1,
        EMBED_SIZE,
        weights=[embedding_matrix],
        input_length=input_length,
        trainable=False,**kwargs)`

I decided this was really repetitive for people who use lots of RNNs and decided to create this wrapper as a result of that.
TLDR:  The benefit of using pre-trained embeddings is that you can get much more valuable dense vector representations of text data while training less variables.  You can already get this functionality out of keras, it just requires ~20ish lines of code every time you want to do it and requires you to have already downloaded the embedding.

You also said that this class doesn’t contain some new attribute and call function in Embedding layer, just loading function to Glove's word embeddings and pass it to weights argument of Embedding.
I recommend creating a new utils function to load any pre-training embedding weights include Glove and word2vec/fastText format, instead of creating the new class for loading pre-trained Glove embeddings for more Keras users.


text:
Split TaskbarController large methods part07

Use instance methods to replace static methods in TaskbarShadowLauncherApps.
Extract method to generate app entries for TaskbarController.
Extract raw string to constant in TaskbarControllerTest.

Test: ./gradlew test

Thanks!

authors: farmerbb utzcoz

repo: farmerbb/Taskbar


text:
Fix Datadog timestamp mapping

Description
detected is not equivalent to acknowledgedAt.
Type of change

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

@willmarks bump reminder ;)

authors: tovbinm willmarks

repo: faros-ai/airbyte-connectors


text:
Add initial support for Cosmos.

As the title says, adds support for Cosmos-based networks.
Tested against the terra.js SDK.

Does Cosmos have any implementation other than Secp256k1? If not we can name it as just CosmosHDWallet not CosmosHDWalletSecp256k1. All of the wallets follow this naming, except Tezos which has both Secp256k1 and Ed25519 (not in this project though) implementation. Thats why it is called as TezosHDWalletSecp256k1
If cosmos doesn't have Ed25519 implemenration in use, you can name it to CosmosHDWallet

Does Cosmos have any implementation other than Secp256k1? If not we can name it as just CosmosHDWallet not CosmosHDWalletSecp256k1. All of the wallets follow this naming, except Tezos which has both Secp256k1 and Ed25519 (not in this project though) implementation. Thats why it is called as TezosHDWalletSecp256k1
If cosmos doesn't have Ed25519 implemenration in use, you can name it to CosmosHDWallet

Sounds good, I will update the PR with the rename.

@tritao Could you get the latest changes from master and do the mentioned changes above, so I can merge this.

authors: farukterzioglu tritao

repo: farukterzioglu/HDWallet


text:
导入历史数据时遇到一个error

导入历史数据时遇到一个error
2024-11-03 20:31:24,304 [ERROR] - Can't trans record: OrderedDict([('open', 1946.87), ('close', 1946.87), ('high', 1946.87), ('low', 1946.87), ('vol', 5.877471754111438e-39), ('amount', 8.105455080847458e+76), ('year', 2022), ('month', 11), ('day', 2), ('hour', 14), ('minute', 5), ('datetime', '2022-11-02 14:05'), ('up_count', 0), ('down_count', 0)])! int too big to convert [import_one_stock_data] (E:\programs\Anaconda\envs\hikyuu\lib\site-packages\hikyuu\data\pytdx_to_h5.py:308) [hikyuu::hku_error]

网络或者服务器问题，用自己tdx服务器，多导一次就是了

authors: MelvinZang fasiondog

repo: fasiondog/hikyuu