profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/lucidrains/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Phil Wang lucidrains Working with Attention

EleutherAI/gpt-neo 5167

An implementation of model parallel GPT-2 and GPT-3-style models using the mesh-tensorflow library.

lucidrains/DALLE-pytorch 3092

Implementation / replication of DALL-E, OpenAI's Text to Image Transformer, in Pytorch

lucidrains/big-sleep 1151

A simple command line tool for text to image generation, using OpenAI's CLIP and a BigGAN. Technique was originally created by https://twitter.com/advadnoun

lucidrains/byol-pytorch 912

Usable Implementation of "Bootstrap Your Own Latent" self-supervised learning, from Deepmind, in Pytorch

lucidrains/alphafold2 510

To eventually become an unofficial Pytorch implementation / replication of Alphafold2, as details of the architecture get released

lucidrains/bottleneck-transformer-pytorch 496

Implementation of Bottleneck Transformer in Pytorch

lucidrains/conformer 154

Implementation of the convolutional module from the Conformer paper, for use in Transformers

lucidrains/axial-attention 116

Implementation of Axial attention - attending to multi-dimensional data efficiently

lucidrains/contrastive-learner 67

A simple to use pytorch wrapper for contrastive self-supervised learning on any neural network

lucidrains/compressive-transformer-pytorch 61

Pytorch implementation of Compressive Transformers, from Deepmind

startedlucidrains/reformer-pytorch

started time in 13 minutes

fork scilover/vit-pytorch

Implementation of Vision Transformer, a simple way to achieve SOTA in vision classification with only a single transformer encoder, in Pytorch

fork in 21 minutes

pull request commentfacebook/react-native

Remove Picker from OSS

Platform Engine Arch Size (bytes) Diff
android hermes arm64-v8a 9,106,213 +0
android hermes armeabi-v7a 8,634,629 +0
android hermes x86 9,545,285 +0
android hermes x86_64 9,511,679 +0
android jsc arm64-v8a 10,752,829 +0
android jsc armeabi-v7a 9,672,501 +0
android jsc x86 10,787,293 +0
android jsc x86_64 11,395,204 +0

Base commit: 5cb2debbea57603990f36200daab5fb981603b47

lunaleaps

comment created time in 25 minutes

pull request commentfacebook/react-native

Remove Picker from OSS

Platform Engine Arch Size (bytes) Diff
ios - universal n/a --

Base commit: 5cb2debbea57603990f36200daab5fb981603b47

lunaleaps

comment created time in 35 minutes

startedlucidrains/progen

started time in 37 minutes

issue openedfacebook/react-native

Build failed CompileSwiftSources normal x86_64

Description

I am trying to start up a react native ios app from terminal with: npx react-native run-ios --configuration Debug --scheme Development

I then get the error: ** BUILD FAILED ** The following build commands failed: CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler MergeSwiftModule normal x86_64 /Users/Library/Developer/Xcode/DerivedData/frnjcdnxmbqgcnhkwpisddivymns/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/lottie-react-native.build/Objects-normal/x86_64/lottie_react_native.swiftmodule (2 failures)

I expect the Xcode simulator to startup and run the ios app but the build fails.

npm: '6.14.11', ares: '1.16.1', brotli: '1.0.9', cldr: '37.0', icu: '67.1', llhttp: '2.1.3', modules: '83', napi: '7', nghttp2: '1.41.0', node: '14.16.0', openssl: '1.1.1j', tz: '2020a', unicode: '13.0', uv: '1.40.0', v8: '8.4.371.19-node.18', zlib: '1.2.11'

lottie-ios: '3.1.8', lottie-react-native: '3.5.0'

react-native: '0.64.2'

Xcode: '12.5'

Macbook pro 2019 2.3Ghz 8-Core Intel Core i9 macOS Big Sur v11.4

created time in 44 minutes

pull request commentfacebook/react-native

Remove Picker from OSS

<!-- 0 failure: 0 warning: 3 messages

DangerID: danger-id-Danger; -->

<table> <thead> <tr> <th width="50"></th> <th width="100%" data-danger-table="true">Messages</th> </tr> </thead> <tbody><tr> <td>:book:</td> <td>

:clipboard: Missing Changelog - <i>Can you add a Changelog? To do so, add a "## Changelog" section to your PR description. A changelog entry has the following format: [CATEGORY] [TYPE] - Message.

<details>CATEGORY may be:

  • General
  • iOS
  • Android
  • JavaScript
  • Internal (for changes that do not need to be called out in the release notes)

TYPE may be:

  • Added, for new features.
  • Changed, for changes in existing functionality.
  • Deprecated, for soon-to-be removed features.
  • Removed, for now removed features.
  • Fixed, for any bug fixes.
  • Security, in case of vulnerabilities.

MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.</details></i> </td> </tr>

<tr> <td>:book:</td> <td>:clipboard: Missing Test Plan - <i>Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.</i></td> </tr>

<tr> <td>:book:</td> <td>:clipboard: Missing Summary - <i>Can you add a Summary? To do so, add a "## Summary" section to your PR description. This is a good place to explain the motivation for making this change.</i></td> </tr> </tbody> </table>

<p align="right"> Generated by :no_entry_sign: <a href="https://danger.systems/js">dangerJS</a> against 0fb292f2ba8aac11dd835d119121444d5ba51913 </p>

lunaleaps

comment created time in an hour

pull request commentfacebook/react-native

Remove Picker from OSS

This pull request was exported from Phabricator. Differential Revision: D29124724

lunaleaps

comment created time in an hour

PR opened facebook/react-native

Remove Picker from OSS

Summary: Changelog:[General][Removed] - Remove Picker iOS code

Reviewed By: p-sun

Differential Revision: D29124724

+1 -825

0 comment

21 changed files

pr created time in an hour

startedlucidrains/byol-pytorch

started time in an hour

push eventfacebookresearch/functorch

Horace He

commit sha 793ee3c3b0e345f4811d7b2a18078342b1df64e0

Added batching rules for convolution, conv1d, conv2d, conv3d, etc.

view details

push time in 2 hours

startedlucidrains/local-attention

started time in 2 hours

startedlucidrains/linformer

started time in 2 hours

issue commentfacebook/react-native

Android Statusbar is not tranparent in 0.63.4 version

Are you using react-native-elements or some other dependency that might be overwriting your attempts to change the status bar? This is what happened to me. After updating from "react-native-elements": "^2.0.4" to "react-native-elements": "^3.4.2" I experienced this. I was able to fix it by setting the props like so inside of the react-native-elements header I was using:

statusBarProps={{ backgroundColor: 'rgb(17, 0, 233)' }}

vinaygoyal20

comment created time in 3 hours

startedlucidrains/perceiver-pytorch

started time in 3 hours

startedlucidrains/reformer-pytorch

started time in 3 hours

issue commentmobxjs/mobx

Bug: `observable` field are editable when the object is frozen with `Object.freeze`

@mweststrate Gotcha, so do we have an idiomatic way to make an instance with observables atteibute immutable of some sort?

akphi

comment created time in 3 hours

issue commentmobxjs/mobx

Bug: `observable` field are editable when the object is frozen with `Object.freeze`

Observable properties are setter / getter pairs, not simple value fields, so this is working as expected.

On Thu, 24 Jun 2021, 22:26 An Phi, ***@***.***> wrote:

I have frozen a non-plain object with Object.freeze, fields being decorated with observable are still modifiable.

I have looked around for similar issues, but I don't seem to find one that fits my description exactly, also most of those issues are rather old so this might be a problem that is introduced more recently.

Intended outcome:

I would expect the field to be non-modifiable, or an error is thrown when I attempt to change the value of the frozen field.

Actual outcome:

The observable field of the frozen object is modifiable.

How to reproduce the issue:

Please refer to this for code repro: https://github.com/akphi/issue-repo/tree/mobx-observable-ref-freeze

I have the following code:

import { makeObservable, observable, action } from "mobx"; class Person { name = ''; age = 1;

constructor() { makeObservable(this, { name: observable, setName: action, }); }

setName(val: string) { this.name = val; }} export const App = (props: {}) => { const person = new Person(); person.setName('initial'); console.log("person", person, person.name); // this will print initial for the name Object.freeze(person); person.setName('something'); // person.age = 3; // this will throw an error if uncommented console.log("person", person, person.name); // this will print something for the name return <div>{person.name}</div>;};

As you can see, person.name is still modifiable after calling Object.freeze(person). On the other hand, if we modify the non-observable field person.age, error will be thrown.

Versions

@***.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mobxjs/mobx/issues/3008, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN4NBF6PEVAVEADF7T5ZHTTUOPI3ANCNFSM47IVSW3Q .

akphi

comment created time in 3 hours

startedlucidrains/big-sleep

started time in 4 hours

issue commentlessw2020/Ranger21

adaptive gclipping: unable to process len of 5 - currently must be <= 4

Hi, I also got the same error. Did you solve the problem? Could you kindly share if you had done that!

HungYu-Wu

comment created time in 4 hours

issue commentfacebook/react-native

Error when archiving in XCode: EMFILE

@ekram21 I upgraded watchman, yarn install, and npx pod-install and I am still getting the same error. Am I missing something?

TheRealNate

comment created time in 5 hours

issue closedvisgl/react-map-gl

onClick event listener wrong scoping

I'm rendering multiple maps as such:

[a, b, c].map(mapObj => <ReactMapGL onClick={e => console.log(e)} />

and found that when I click on one of the rendered maps, the click event gets called 3 times, as many as the maps rendered in the loop, instead of just firing from the element that I actually clicked on. I think this is a bug and makes working with multiple maps quite tricky. Logging the click events shows 3 different event targets, one for each different map container.

the onMouseDownevent behaves correctly by only firing from the map that is actually being clicked, which makes me think that the onClick listener might not be behaving correctly

closed time in 5 hours

7091lapS

issue commentvisgl/react-map-gl

onClick event listener wrong scoping

Thanks for reporting. This is fixed by mjolnir.js@2.5.2. You may need to remove your lock file to upgrade the dependency.

7091lapS

comment created time in 5 hours

issue openedmobxjs/mobx

Bug: `observable` field are editable when the object is frozen with `Object.freeze`

I have frozen a non-plain object with Object.freeze, fields being decorated with observable are still modifiable.

I have looked around for similar issues, but I don't seem to find one that fits my description exactly, also most of those issues are rather old so this might be a problem that is introduced more recently.

Intended outcome:

I would expect the field to be non-modifiable, or an error is thrown when I attempt to change the value of the frozen field.

Actual outcome:

The observable field of the frozen object is modifiable.

How to reproduce the issue:

Please refer to this for code repro: https://github.com/akphi/issue-repo/tree/mobx-observable-ref-freeze

I have the following code:

import { makeObservable, observable, action } from "mobx";

class Person {
  name = '';
  age = 1;

  constructor() {
    makeObservable(this, {
      name: observable,
      setName: action,
    });
  }

  setName(val: string) {
    this.name = val;
  }
}

export const App = (props: {}) => {
  const person = new Person();
  person.setName('initial');
  console.log("person", person, person.name); // this will print `initial` for the name
  Object.freeze(person);
  person.setName('something');
  // person.age = 3; // this will throw an error if uncommented
  console.log("person", person, person.name); // this will print `something` for the name
  return <div>{person.name}</div>;
};

As you can see, person.name is still modifiable after calling Object.freeze(person). On the other hand, if we modify the non-observable field person.age, error will be thrown.

Versions

mobx@6.3.2

created time in 5 hours

startedlucidrains/vit-pytorch

started time in 5 hours

issue commentfacebook/react-native

Getting SIGABRT Crash on release build. libc.so

been able to find a solution, for me the issue was mainly caused by the inconsistent behaviour of date.toLocaleDateString function on Android. https://stackoverflow.com/a/51400372 the easiest solution I could find is to replace toLocaleDateString everywhere in the app with a custom made version.

const toLocaleDateString = date =>${date.getDate()}/${date.getMonth() < 9 ? 0${date.getMonth() + 1} : date.getMonth() + 1}/${date.getFullYear()};

afkcodes

comment created time in 6 hours

issue commentfacebook/react-native

0.61.5 android app rejected because of stability issues(StrictMode policy violation)

I have the same issue with play store with RN 0.63.1

sbatikeri

comment created time in 6 hours

issue commentmobxjs/mobx

Support concurrent features React / React 18

Reopening this as we're getting closer to a React 18 release. Progress can be followed in #3005.

At this moment, as far as initial test projects point out, mobx-react(-lite) plays fine with React 18 in Strict mode. No warnings, errors and features like startTransaction seem to work correctly.

At this moment we don't offer MobX specific concurrent features yet. Some tearing could (theoretically) still happen. And MobX might put React in de-opt mode (theoretically) in cases as well.

That being said, there are no known problems at this moment that would block mobx-react(-lite) from upgrading or using specific React features.

That conclusion is based on some pretty flimsy research, but at least it is some status update :). No known limitations or blockers for a React 18 upgrade at this moment.

mweststrate

comment created time in 6 hours

issue commentfacebook/react-native

New React Native project won't build on Xcode 13.

Can flopper be opt in and not too invasive in project code? Too much problems for nothing.

adrianbartyczak

comment created time in 6 hours

IssuesEvent