text:
flash_attn Error

Building wheel for flash_attn (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [89 lines of output]
fatal: not a git repository (or any of the parent directories): .git
  torch.__version__  = 2.0.0+cu118

  D:\minicondaforme\envs\quiet-star\lib\site-packages\setuptools\__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
  !!

          ********************************************************************************
          Requirements should be satisfied by a PEP 517 installer.
          If you are using pip, you can try `pip install --use-pep517`.
          ********************************************************************************

  !!
    dist.fetch_build_eggs(dist.setup_requires)
  running bdist_wheel
  Guessing wheel URL:  https://github.com/Dao-AILab/flash-attention/releases/download/v2.6.3/flash_attn-2.6.3+cu118torch2.0cxx11abiFALSE-cp310-cp310-win_amd64.whl
  Precompiled wheel not found. Building from source...
  D:\minicondaforme\envs\quiet-star\lib\site-packages\torch\utils\cpp_extension.py:476: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
    warnings.warn(msg.format('we could not find ninja.'))
  running build
  running build_py
  creating build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\bert_padding.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\flash_attn_interface.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\flash_attn_triton.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\flash_attn_triton_og.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\flash_blocksparse_attention.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\flash_blocksparse_attn_interface.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\fused_softmax.py -> build\lib.win-amd64-cpython-310\flash_attn
  copying flash_attn\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn
  creating build\lib.win-amd64-cpython-310\hopper
  copying hopper\benchmark_attn.py -> build\lib.win-amd64-cpython-310\hopper
  copying hopper\flash_attn_interface.py -> build\lib.win-amd64-cpython-310\hopper
  copying hopper\setup.py -> build\lib.win-amd64-cpython-310\hopper
  copying hopper\test_flash_attn.py -> build\lib.win-amd64-cpython-310\hopper
  copying hopper\__init__.py -> build\lib.win-amd64-cpython-310\hopper
  creating build\lib.win-amd64-cpython-310\flash_attn\layers
  copying flash_attn\layers\patch_embed.py -> build\lib.win-amd64-cpython-310\flash_attn\layers
  copying flash_attn\layers\rotary.py -> build\lib.win-amd64-cpython-310\flash_attn\layers
  copying flash_attn\layers\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\layers
  creating build\lib.win-amd64-cpython-310\flash_attn\losses
  copying flash_attn\losses\cross_entropy.py -> build\lib.win-amd64-cpython-310\flash_attn\losses
  copying flash_attn\losses\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\losses
  creating build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\baichuan.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\bert.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\bigcode.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\btlm.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\falcon.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\gpt.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\gptj.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\gpt_neox.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\llama.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\opt.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\vit.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  copying flash_attn\models\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\models
  creating build\lib.win-amd64-cpython-310\flash_attn\modules
  copying flash_attn\modules\block.py -> build\lib.win-amd64-cpython-310\flash_attn\modules
  copying flash_attn\modules\embedding.py -> build\lib.win-amd64-cpython-310\flash_attn\modules
  copying flash_attn\modules\mha.py -> build\lib.win-amd64-cpython-310\flash_attn\modules
  copying flash_attn\modules\mlp.py -> build\lib.win-amd64-cpython-310\flash_attn\modules
  copying flash_attn\modules\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\modules
  creating build\lib.win-amd64-cpython-310\flash_attn\ops
  copying flash_attn\ops\activations.py -> build\lib.win-amd64-cpython-310\flash_attn\ops
  copying flash_attn\ops\fused_dense.py -> build\lib.win-amd64-cpython-310\flash_attn\ops
  copying flash_attn\ops\layer_norm.py -> build\lib.win-amd64-cpython-310\flash_attn\ops
  copying flash_attn\ops\rms_norm.py -> build\lib.win-amd64-cpython-310\flash_attn\ops
  copying flash_attn\ops\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\ops
  creating build\lib.win-amd64-cpython-310\flash_attn\utils
  copying flash_attn\utils\benchmark.py -> build\lib.win-amd64-cpython-310\flash_attn\utils
  copying flash_attn\utils\distributed.py -> build\lib.win-amd64-cpython-310\flash_attn\utils
  copying flash_attn\utils\generation.py -> build\lib.win-amd64-cpython-310\flash_attn\utils
  copying flash_attn\utils\pretrained.py -> build\lib.win-amd64-cpython-310\flash_attn\utils
  copying flash_attn\utils\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\utils
  creating build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\cross_entropy.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\k_activations.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\layer_norm.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\linear.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\mlp.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\rotary.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  copying flash_attn\ops\triton\__init__.py -> build\lib.win-amd64-cpython-310\flash_attn\ops\triton
  running build_ext
  D:\minicondaforme\envs\quiet-star\lib\site-packages\torch\utils\cpp_extension.py:359: UserWarning: Error checking compiler version for cl: [WinError 2] 系统找不到指定的文件。
    warnings.warn(f'Error checking compiler version for {compiler}: {error}')
  building 'flash_attn_2_cuda' extension
  error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for flash_attn
Running setup.py clean for flash_attn
Failed to build flash_attn
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (flash_attn)

一样的，请问你找到解决方案了吗

no..

我找到啦，你直接https://github.com/Dao-AILab/flash-attention/releases/使用.whl文件下载即可

authors: BlackTea-c maoshanwen

repo: ezelikman/quiet-star


text:
[BUG] Incorrect # of total dependencies

Describe the bug
LSP calls show an alert of 132 dependencies with NO CVEs found. The stack report show (a) a total of 9 CVEs (b) total dependencies as 289 . The # of analyzed and unknown dependencies (112,89) do not add up to total # (289)
To Reproduce
Try stack report https://gist.github.com/SriKrishnaPaparaju/58535d622dd62da1e2afe4b7c2b380e5
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Logs
If applicable, attach logs.
VSCode(please complete the following information):

OS: [e.g. macOS]
VSCode version [e.g. 1.33.1]
Dependency Analytics Version [e.g. 0.0.22]

CHE7/Theia(please complete the following information):

OS: [e.g. macOS]
Browser [e.g. chrome]
CHE/Theia version
Dependency Analytics Version [e.g. 0.0.22]

Additional context
Add any other context about the problem here.

Here is the stack analysis API response,
https://gist.github.com/arajkumar/c59acddb10ba71b7d4b153c879b2b9a5

are you able to reproduce this problem?

From the response data I could see that Total Dependencies is based on dependencies JSON field which is 289,  Analysed Dependencies is based on analysed_dependecies which is 112, Unknown Dependencies is based on unknown_dependencies which is 89.
I see the duplicates in both dependencies and analysed_dependencies fields. When I convert those arrays to sets, then counts are match,

@krishnapaparaju I think the duplicates should be handled from the API side. What's your thought?

Yes, this needs to be handled at platform level

LSP calls show an alert of 132 dependencies with NO CVEs found.

It is a know issue with property based dependency version, refer #258.

@SriKrishnaPaparaju @arajkumar - As discussed, we cannot remove those duplicates, else we loose the ability to tag a direct dependency affected by any of the transitive dependencies.
Let me know what else needs to be done on my side.

@miteshvp Ack. @arajkumar can we fix on the UI side ?

Unassigning myself. @arajkumar - you may want to assign this to yourself?

@SriKrishnaPaparaju , we no longer show Total Dependency count in the report after #330 . Do you think it is still relevant as a bug?
You can download VSIX pre-release from release page to access latest changes.

No longer relevant with new card, hence closing it.

source: gharchive/issue

authors: SriKrishnaPaparaju arajkumar miteshvp

license_type: permissive

license_source: github-api


text:
fix: [APPAI-1819] Simplified go manifest generation command

Simplified go manifest command executed during SA. Address issue raised by a user https://github.com/fabric8-analytics/fabric8-analytics-vscode-extension/issues/504

/build-and-test

Codecov Report

Merging #507 (eda2b5f) into master (a1f587c) will increase coverage by 1.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #507      +/-   ##
==========================================
+ Coverage   59.47%   60.52%   +1.05%
==========================================
  Files          18       18
  Lines         834      836       +2
  Branches      169      169
==========================================
+ Hits          496      506      +10
+ Misses        338      330       -8

Impacted Files
Coverage Δ

src/ProjectDataProvider.ts
72.22% <100.00%> (+0.31%)
:arrow_up:

src/multimanifestmodule.ts
52.23% <0.00%> (+5.97%)
:arrow_up:

Continue to review full report at Codecov.

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

source: gharchive/pull-request

authors: codecov-commenter dgpatelgit


text:
cachelib fails to build

Describe the bug
(build.sh: error: failed to build cachelib)
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/facebook/CacheLib
cd CacheLib/
./contrib/build.sh -j
See error in Screenshots section

Expected behavior
successful build
Screenshots
[ 81%] Building CXX object allocator/CMakeFiles/cachelib_allocator.dir/SlabReleaseStats.cpp.o
[ 82%] Building CXX object allocator/CMakeFiles/cachelib_allocator.dir/TempShmMapping.cpp.o
/tmp/cciWu1Ct.s: Assembler messages:
/tmp/cciWu1Ct.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
/tmp/ccVWjB2C.s: Assembler messages:
/tmp/ccVWjB2C.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
/tmp/ccQo6GYZ.s: Assembler messages:
/tmp/ccQo6GYZ.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [allocator/CMakeFiles/cachelib_allocator.dir/build.make:397: allocator/CMakeFiles/cachelib_allocator.dir/CacheAllocator.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:532: allocator/CMakeFiles/cachelib_allocator.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
build-package.sh: error: make failed
build.sh: error: failed to build cachelib
Desktop (please complete the following information):

OS:

uname -a
Linux fb-yv3-w05 5.12.0-0_fbk2_3390_g7ecb4ac46d7f #1 SMP Tue Dec 14 10:55:56 PST 2021 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/redhat-release
CentOS Stream release 8
Additional context
N/A

Hi @george-reilly-wdc Our Centos 8.1 build is green https://github.com/facebook/CacheLib/blob/main/.github/workflows/build-cachelib-centos-8-1.yml
Could you try on Centos 8.1 or 8.5?

Yes, I will build a centos-8-1 system and retry. Not sure when I will get around to doing that. Please close this ticket. Thanks.

Can we re-open this ticket or should I submit a new one?
Environment :
[root@fb-yv3-s1-n1 /]# uname -a
Linux fb-yv3-s1-n1 5.12.0-0_fbk2_3390_g7ecb4ac46d7f #1 SMP Tue Dec 14 10:55:56 PST 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@fb-yv3-s1-n1 /]# cat /etc/redhat-release
CentOS Linux release 8.1.1911 (Core)
Command :  git clone https://github.com/facebook/CacheLib.git
Fails with :
[ 82%] Building CXX object allocator/CMakeFiles/cachelib_allocator.dir/PoolRebalancer.cpp.o
/tmp/ccyAQXIu.s: Assembler messages:
/tmp/ccyAQXIu.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
/tmp/ccojqa91.s: Assembler messages:
/tmp/ccojqa91.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
/tmp/ccOLUSsf.s: Assembler messages:
/tmp/ccOLUSsf.s:5: Warning: setting incorrect section attributes for .rodata.thrift.data
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
make[2]: *** [allocator/CMakeFiles/cachelib_allocator.dir/build.make:397: allocator/CMakeFiles/cachelib_allocator.dir/CacheAllocator.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:532: allocator/CMakeFiles/cachelib_allocator.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
build-package.sh: error: make failed
build.sh: error: failed to build cachelib
Then I tried using the link you gave above with this command :
git clone https://github.com/facebook/CacheLib/blob/main/.github/workflows/build-cachelib-centos-8-1.yml
And it failed with :
[root@fb-yv3-s1-n1 /]# git clone https://github.com/facebook/CacheLib/blob/main/.github/workflows/build-cachelib-centos-8-1.yml
Cloning into 'build-cachelib-centos-8-1.yml'...
fatal: repository 'https://github.com/facebook/CacheLib/blob/main/.github/workflows/build-cachelib-centos-8-1.yml/' not found

authors: george-reilly-wdc jaesoo-fb

repo: facebook/CacheLib


text:
Added HTML tables to documentation page to improve UX.

Motivation
To create a patch to help resolve this change request: #436
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Tested by re-running server to confirm page is still rendered properly and that the page is still being correctly served. I then ran 'yarn test' and that passed all test cases.
Related PRs
https://github.com/facebook/Docusaurus/pull/508
Tests
All Yarn tests passed locally up to most recent commit

Change Impact Analysis

For #436, only Markdown code was changed to support HTML5 table elements, and some basic CSS3 styling. No other components were modified or changed.
Do any existing requirements in the baseline conflict with the proposed change?
No.
Do any other pending requirements changes conflict with the proposed change?
No.
What are the business or technical consequences of not making a change?
A less ideal UX (user experience).
Will the proposed change adversely affect performance requirements or other quality attributes?
No, for this change there will be 0 impact to performance requirements. Quality of code remains the same.
Is the proposed change feasible within known technical constraints and current staff skills?
Yes.
Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments?
No, computer resources should stay the same.
Must any tools be acquired to implement and test the change?
Contributors may use the built-in test suite to test the change using command yarn test
How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan?
No dependencies needed to be changed and no new dependencies needed to be added in order to implement this change.
Will prototyping or other use input be required to verify the proposed change?
Yes, the user may request the page that's been modified /en/docs/... and check that the changes have been rendered correctly.
How much effort that has already been invested in the project will be lost if this change is accepted?
Maybe an hour.
Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees?
No.
Will the change affect any marketing, manufacturing, training, or customer support plans?
No.

Thanks @InternetExplorer7 ! I changed the HTML to Markdown and added custom styles so that we don't have to write inline-styles in the code. Looking forward to more contributions from you!

repo: facebook/Docusaurus

license: MIT


text:
rendering of tree rows should be green

Description
In iD, a tree row is rendered in green which makes a lot of sense:

In Rapid, it's rendered as grey, which is suboptimal

Version
2.00-alpha.3.3
What browser are you seeing the problem on? What version are you running?
Firefox v108.0
Steps to reproduce

Draw a line
mark it as a tree row.

The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=EsriWorldImagery&datasets=fbRoads,msBuildings&disable_features=boundaries&map=20.65/40.76265/-111.83363

good suggestion, I just added it in 37c4f6136  🌳

authors: bhousel mvexel

repo: facebook/RapiD

license: ISC


text:
All selected line features deselected when shift-click open area

Description
When using shift-left click to select multiple features to edit them ensemble, like the line version of buildings in the attached video, if you don't click exactly on the line, the entire selection is lost.  This is particularly difficult with initially incorrect buildings saved as lines because normal buildings can be selected from an internal click.
https://github.com/facebook/Rapid/assets/24398638/baff3d5a-e304-46b9-8d10-dc995c6bc268
Version
2.0.3
What browser are you seeing the problem on? What version are you running?
Chrome v117.0
The OS you're using
win
Steps to reproduce

Select initial line feature
hold shift and slick additional features
still holding shift, "accidentally" click somewhere other than on a feature
watch all previously selected features be deselected
gnash teeth

https://github.com/facebook/Rapid/assets/24398638/9211e363-055e-46f9-99d1-db83ec7377db
The browser URL at the time you encountered the bug
https://maproulette.org/challenge/14016/task/62628601?#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&id=w1116329185&map=19.96/12.87797/14.29784
The auto-detected useragent string for your browser (leave blank if you're manually filling this form out)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36

Thanks for the report, we'll try to investigate what's going on.
I see that you're using a slightly older version 2.0.3 through the maproulette embed - I can't remember whether this is an issue that we fixed in 2.1.  🤔

authors: bhousel bradlewt

repo: facebook/Rapid


text:
unable to create react app using create-react-app

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     https://npm.community
.
.
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts has failed.

You have problem with npm itself not with create-react-app!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! https://npm.community

Maybe you don't have the required version of node which is 8.10 or above, so check your node version!

It was a proxy issue though.
I have v10.15.3 of node installed..
Thank you

authors: Keerttik iHmD

repo: facebook/create-react-app


text:
docs: add deployment workflow manual for GitHub Actions

I built a workflow to deploy docs for our project with GitHub Actions. After testing it on our repository I'm happy to share it with other Docusaurus users.
Motivation
I haven't found nice docs on deploying Docusaurus with GitHub Actions. I spent quite some time to test out such a deployment for our project. I think it's a popular deployment option and other Docusaurus users will benefit from it.
Have you read the Contributing Guidelines on pull requests?
Yes, I did.
Test Plan
These PR contributes only to documentations. I verified everything step by step in my project's repository which lead to successful deployment of documentation to GH Pages.
Here's green pipeline screenshot:

Here's a result hosted on GH pages:

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

I created a new one with requested change.

repo: facebook/docusaurus


text:
Problem with SSR frameworks (e.g. Gatsby)

Do you want to request a feature or report a bug?
:bug: BUG
What is the current behavior?
Draft.js produces errors with frameworks that do SSR (e.g. Gatsby)
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Test Repository:

Gatsby: https://github.com/MunifTanjim/draft-js-tests/tree/gatsby

Reproduction Steps:

Clone the test repository: https://github.com/MunifTanjim/draft-js-tests
Checkout gatsby branch
Install dependencies: yarn
Build: yarn build
Serve: yarn serve
Visit the site and try to write something on the editor.
Errors will be logged on console.

What is the expected behavior?
Everything should work alright? :sweat_smile:
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js version: 0.11.0-beta3
Additional Information
https://github.com/gatsbyjs/gatsby/issues/15380#issuecomment-508484676
Live Demo

Gatsby: https://gatsby--draft-js-tests.netlify.com/

Workaround One: (https://github.com/zeit/next.js/issues/1722#issuecomment-296451797)
import { Editor, EditorState } from "draft-js"
import "draft-js/dist/Draft.css"
import React, { useCallback, useEffect, useRef, useState } from "react"

function DraftEditor() {
  const editor = useRef(null)
  const [editorState, setEditorState] = useState(EditorState.createEmpty())
  const [mounted, setMounted] = useState(false)

  useEffect(() => {
    setMounted(true)
  }, [])

  const onChange = useCallback(editorState => {
    setEditorState(editorState)
  }, [])

  const focus = useCallback(() => {
    if (editor.current) editor.current.focus()
  }, [])

  return mounted ? (
    <Editor
      ref={editor}
      editorState={editorState}
      onChange={onChange}
    />
  ) : null
}

export default DraftEditor

Workaround Two: (https://github.com/zeit/next.js/issues/1722#issuecomment-354601779)
import { Editor, EditorState, convertFromRaw } from "draft-js"
import "draft-js/dist/Draft.css"
import React, { useCallback, useRef, useState } from "react"

function DraftEditor() {
  const editor = useRef(null)
  const [editorState, setEditorState] = useState(EditorState.createWithContent(emptyContentState))

  const onChange = useCallback(editorState => {
    setEditorState(editorState)
  }, [])

  const focus = useCallback(() => {
    if (editor.current) editor.current.focus()
  }, [])

  return (
    <Editor
      ref={editor}
      editorState={editorState}
      onChange={onChange}
    />
  )
}

const emptyContentState = convertFromRaw({
  entityMap: {},
  blocks: [
    {
      text: '',
      key: 'foo',
      type: 'unstyled',
      entityRanges: []
    }
  ]
})

export default DraftEditor

repo: facebook/draft-js

license: mit

license_source: bigquery


text:
Text is inserted at an incorrect position after drag and dropping text

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Text is inserted at an incorrect position after drag and dropping within the same editor instance. See the following gif:

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/gmertk/e61z7nfa/.
To reproduce it, paste multi-line HTML containing
 tags and try moving words between lines.
What is the expected behavior?
The text should be inserted at the place where the mouse is released after dragging.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js: 0.11.5
Chromium: 80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Text is inserted at an incorrect position after drag and dropping within the same editor instance. See the following gif:

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/gmertk/e61z7nfa/.
To reproduce it, paste multi-line HTML containing
 tags and try moving words between lines.
What is the expected behavior?
The text should be inserted at the place where the mouse is released after dragging.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js: 0.11.5
Chromium: 80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)

Found Any solution for this drag and drop issue?

authors: kzatin tomaskikutis


text:
convertFromHTML doesn't preserve s inside s

Let's say I have some text in the editor:
hello

we're separated by a line

and us by two

In the editor, when creating this text, I end up with 6 blocks, with the 2nd, 4th, and 5th having empty text.
The HTML I generate from this text looks like this (which is very similar to the HTML outputted during editing):

hello

we're separated by a line

and us by two

If I use convertFromHTML() on this HTML, I would expect to get 6 content blocks back. Instead, I only get 3, and all of the empty lines get collapsed. So after I load the 3 blocks, the text in the editor ends up like this:
hello
we're separated by a line
and us by two

This was discussed a bit in https://github.com/facebook/draft-js/issues/231:

This was on purpose to keep pastes of long text from having a lot of extra spaces between paragraphs. The content coming in can be pretty messy sometimes and this is one of the things we try to do to clean it up.

I have the exact issue; what trick did you use to fix it without using another module?

This was discussed a bit in #231:

This was on purpose to keep pastes of long text from having a lot of extra spaces between paragraphs. The content coming in can be pretty messy sometimes and this is one of the things we try to do to clean it up.

To do the cleanup removing the users input which is not right

I think this is not good default behavior and should be changed. The current behavior also does the align with most other RTE's.

This is awful default behavior.

authors: Smaxor5 asif-alam benbriggs facilitator999 gdehmlow scottfr


text:
Move immutable to peerDependencies

Before submitting a pull request, please make sure the following is done...

Fork the repo and create your branch from master.
If you've added code that should be tested, add tests!
If you've changed APIs, update the documentation.
Ensure that:

The test suite passes (npm test)
Your code lints (npm run lint) and passes Flow (npm run flow)
You have followed the testing guidelines

If you haven't already, complete the CLA.

Please use the simple form below as a guideline for describing your pull request.
Thanks for contributing to Draft.js!

Summary
Move "immutable": "~3.7.4" from dependencies to peerDependencies in package.json
Closes #1237
Test Plan
NA

Should it be? What if I use another package with older immutable version? My app will be completely broken and I won't be able to fix it.
What problem are you trying to solve here? It's not clear from the issue.

@TrySound it was reported issue so I made the changes, it this change not required?
@niveditc I will make the changes and update my commit

@niveditc I am getting this error on running yarn
`const missingModule = e.toString().match(EXTRACT_MODULE_NAME_REGEX)[1];
^
TypeError: Cannot read property '1' of null
at files.forEach (/Users/arshad/Arshad/workspace/opensource/hacktoberfest/draft-js/node_modules/fbjs-scripts/node/check-lib-requires.js:30:76)
at Array.forEach ()
at fs.readdir (/Users/arshad/Arshad/workspace/opensource/hacktoberfest/draft-js/node_modules/fbjs-scripts/node/check-lib-requires.js:22:9)
at FSReqWrap.oncomplete (fs.js:135:15)`

Thanks for commenting on #1237 - let's wait to see if this change is needed, since I don't have much context.

Closing since we weren't able to come up with rationale for this change. Apologies for the mislabeled issue!

authors: TrySound arshadkazmi42 niveditc


text:
Classes do not have callable signatures

Flow version: 0.94.0
Expected behavior
class Foo {}

(Foo: { (): Foo }); // This should be OK

Actual behavior
3: (Foo: { (): Foo });
    ^ Cannot cast `Foo` to object type because a callable signature is missing in statics of `Foo` [1] but exists in object type [2].
References:
1: class Foo {}
         ^ [1]
3: (Foo: { (): Foo });
         ^ [2]

This bug makes it impossible to define a type that accepts any arbitrary callable object. In my use case, I wanted to enforce that the right-hand-side of an instanceof check was callable, without restricting the type of the callable object. I get the same error if I change the type to () => void.
(Try Flow)

@talbenari1 but class isn't callable, do you mean newable ?

...What? Classes most certainly are callable, by which I mean that they have the [[Call]] internal field as described in the ECMAScript spec. Just because it's a semantic error to call them without new doesn't mean they're not callable (the algorithm for calling a function explains what I'm talking about).
Why do I care, you might ask? Well how else can I define the type of all val where typeof val === "function"? I get that nominal typing gets in the way here a bit, but there really should be a way to encode that type.

Another use case is having callable a type, say Foo, and being able to group all it's utility functions in static members of the very type, say Foo.isFootastic(value).

We don't plan to support this pattern, since it prevents us from detecting class that should be newed instead of called.

repo: facebook/flow


text:
Spread tuples into $Call in type-level

Proposal
Add argument to Function$Prototype$Apply specifying current thisof .apply, or add separate $Apply destructor which would work like this
$Apply<(a: string, b: number) => void, [string, number]>

Use case
Basically this would allow doing compose(...fns) on type-level
$Apply<
  $Compose,
  [
    (a: number) => void,
    () => number
  ]
>

declare function reduce<Fn, A, T>(Fn, A, T): $Call<
  $Apply<
    $ComposeReverse,
    $TupleMap<T, Fn>,
  >
, A>

export type _Reduce = typeof reduce

export type Reduce<Fn, A, T> = $Call<_Reduce, Fn, A, T>

declare function reduceRight<Fn, A, T>(Fn, A, T): $Call<
  $Apply<
    $Compose,
    $TupleMap<T, Fn>,
  >
, A>

export type _ReduceRight = typeof reduceRight

export type ReduceRight<Fn, A, T> = $Call<_ReduceRight, Fn, A, T>

/cc @samwgoldman

No plans for more builtin utility types


text:
updateIn using RegExps or traversing Lists

I often find myself in a situation where I would like to update a nested structure where I don't know all the keynames of a sub-structure or a sub-structure is a list. In short i'd need a function like
obj = obj.updateIn(["key1","key2", /.*/, "key3", function() {})
The third argument could be a RegExp to match all keys of an object, or a filter-function returning matching indices or keys, if it's a list.
Would such a thing be feasible?

Unfortunately not

repo: facebook/immutable-js


text:
testNamePattern typeahead polish

This is a ticket to keep track of all the polish needed for the testNamePattern typeahead.
Open questions:

What should happen when a it is already being filtered by the testFilePattern?
Do we want to update how we show each "row" of the results?
Should we use regex or fuzzy search?
How can we make sure that we show the correct number of matching tests?

cc: @cpojer @zouxuoz

My thoughts:

We should probably allow to make it so the two filters work together and potentially have a way to show that in the UI. Since we now collapse the Usage panel, we could probably print a line above that to show which filters are applied and add a way to clear them. cc @thymikee.
Maybe. You are the expert.
Fuzzy search. There is an issue for that somewhere on this tracker, I believe, and a proposal for a library. Question: should we change the file name pattern to be fuzzy as well? (probably, yes).

For the first one: we might need to amend the list of test results to add the testPath so that we can filter over them.

We should probably allow to make it so the two filters work together and potentially have a way to show that in the UI. Since we now collapse the Usage panel, we could probably print a line above that to show which filters are applied and add a way to clear them.

I'm all for that. Filters should be persistent and we need to show it to the user. They should also get cleared on Esc or Backspace (one by one?) I think.

Or c, for clear? :D

Where you guys thinking something like this for surfacing the active filters?

I think that sounds good. Is there any way to collapse both patterns and the headline into a single line and still make it useful?
"Active Filters filename: jest-cli.*watch, testname: foobar"
?

Sounds like a good idea, I'll give that a shot

Here is a quick mockup of how it could look, but I feel that the menu is starting to feel huge... I wonder if we should rethink how we show this menu

yeah, we probably should update it, although with @thymikee's work it is at least collapsing. I think your proposal is a good start.

Closing this in favor of #2595

authors: cpojer rogeliog thymikee

repo: facebook/jest


text:
Specifying multiple collectCoverageFrom paths

Do you want to request a feature or report a bug?
bug
What is the current behavior?
Calling:
jest --collectCoverageFrom foo/**/*.js bar/**/*.js

Does not assume both patterns as collectCoverageFrom. Though, this works:
jest --collectCoverageFrom foo/**/*.js --collectCoverageFrom bar/**/*.js
jest --collectCoverageFrom '["foo/**/*.js", "bar/**/*.js"]'

If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can yarn install and yarn test.
See above.
What is the expected behavior?
The expected behavior is that the first form should work. The current behavior is inconsistent with collectCoverageOnlyFrom and many other options. This is due to the collectCoverageFrom type being a string instead of an array, see https://github.com/facebook/jest/blob/8549900b8e98d5cf6c9983cdd34d4a089c9f2bed/packages/jest-cli/src/cli/args.js#L143.
Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
The jest configuration does not apply here.
Jest 22.0.0
Node: 8.9.3
npm: 5.6.0
OS: Mac

#5537

authors: SimenB satazor


text:
Add custom message support to jest-worker

Summary

Test plan

no idea what happened here 😀


text:
Refactor calculateZoomLevel to be an editor setting

Since Chrome 128 and https://chromestatus.com/feature/5198254868529152, the fix we did with calculateZoomLevel is no longer needed for later Chromium versions, however we now need a way to on/off the adjustment on demand for browser that have the blink flag on/off or are on Chrome pre-128. Currently we have calculateZoomLevel at both lexical-core level and playground. We need a way to on/off it inside core, alongside playground.

@etrepum open to suggestions on how we can handle this nicely

I would come up with a short test that can determine whether the hack is necessary or not at runtime and polyfill it accordingly
let NEEDS_MANUAL_ZOOM: boolean | undefined;
function needsManualZoom(): boolean {
  if (NEEDS_MANUAL_ZOOM === undefined) {
    if (IS_FIREFOX || !CAN_USE_DOM) {
      NEEDS_MANUAL_ZOOM = false;
    } else {
      // TODO - implement feature detection, probably create an element and set some style and measure it
      NEEDS_MANUAL_ZOOM = true;
    }
  }
  return NEEDS_MANUAL_ZOOM;
}

export function calculateZoomLevel(element: Element | null): number {
  let zoom = 1;
  if (needsManualZoom()) {
    while (element) {
      zoom *= Number(window.getComputedStyle(element).getPropertyValue('zoom'));
      element = element.parentElement;
    }
  }
  return zoom;
}

repo: facebook/lexical


text:
chore(auto-link-plugin): fix invariant message for node registration check

Fix the message when checking for the node registration in the autolink plugin.

Thanks for this! I think we need to run npm run extract-codes to update the codes.json file.

Thanks for this! I think we need to run npm run extract-codes to update the codes.json file.

Done.
In the meantime my CLA is confirmed.

authors: acywatson echarles


text:
[lexical][lexical-list][lexical-rich-text]: Fix: Preserve indentation when serializing to and from HTML

Description
This PR ensures that the indent property is preserved when importing and exporting HTML.
Closes #6082
Additionally, the following bugs are fixed:

in ParagraphNode.exportDOM the correct default value is used. It was set to an old value.
in ParagraphNode.exportDOM the indent is exported using the padding-inline-start property as used in the editor, instead of text-indent. Apparently, the person who set that did so because padding-inline-start has poor support in email clients. However, text-indent is a first-line indent, different from the lexical indent which encompasses the entire block. If someone needs to export for use in email, they should probably create their own converter.

Considerations
This PR does not include serialization of custom indent values defined in the editorConfig.theme. The problem is that the CSS variable --lexical-indent-base-value is used, but when importing html the variable is not accessible. It can be used in any context, even headless. This has already caused problems for other users:
https://github.com/facebook/lexical/issues/4583
https://github.com/facebook/lexical/issues/5062
As I see it, the solution to this would be that the indent spacing is not configured with CSS under the editorConfig theme property, but using javaScript. That would be a breaking change.
Test plan
Tests are included for Paragraphs, Quotes and Headings.

I've opened a PR fixing the indent issue here: https://github.com/facebook/lexical/pull/6693
I'll do the same for text-align soon.
If you're interested, contributions are still welcome to make HTML serialization take into account custom indentation values in editorConfig.theme.indent

I think the failed tests are flaky


text:
Request for Dark Theme with theme toggle for developers

This is just a small feature request. Would do a world good.
Introduction
I'd like to suggest implementing a Dark theme toggle switch, the same way Redux website https://redux.js.org/ and Redux Toolkit website https://redux-toolkit.js.org/ have that small toggle switch at the right upper corner of the top navbar.
Details
It really hurts your eyes when you read other Redux documents with dark theme and suddenly React Native website is bright white, especially while integrating redux.
Discussion points
Would do a lot good for the community

Hi @lopeselio, this feature and many more will be available after the Docusuaurs upgrade to V2, which is currently in progress. You can check out the #2146 issue and referenced fork for the details.

That's amazing. Really waiting ...

authors: Simek lopeselio

repo: facebook/react-native-website


text:
com.facebook.react.common.JavascriptException: undefined is not an object (evaluating 'i.readDir')

Recently, we found a problem in Android when set minifyEnabled = true , the problem's crash log as follows when start app：
08-11 16:21:01.574 17035-17067/? E/AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
Process: com.test.jpush, PID: 17035
com.facebook.react.common.JavascriptException: undefined is not an object (evaluating 'i.readDir'), stack:
@863:183
n@2:557
i@2:348
t@2:210
@862:243
n@2:557
i@2:348
t@2:210
@861:194
n@2:557
i@2:348
t@2:210
@859:350
n@2:557
i@2:348
t@2:210
@848:311
n@2:557
i@2:348
t@2:210
@847:194
n@2:557
i@2:348
t@2:210
@844:301
n@2:557
i@2:348
t@2:210
@842:325
n@2:557
i@2:348
t@2:210
@682:733
n@2:557
i@2:348
t@2:210
@675:312
n@2:557
i@2:348
t@2:210
@657:311
n@2:557
i@2:348
t@2:210
@13:322
n@2:557
i@2:348
t@2:210
@12:24
n@2:557
i@2:278
t@2:210
global code@904:9
                                                   at com.facebook.react.modules.core.ExceptionsManagerModule.showOrThrowError(ExceptionsManagerModule.java:97)
                                                   at com.facebook.react.modules.core.ExceptionsManagerModule.reportFatalException(ExceptionsManagerModule.java:81)
                                                   at java.lang.reflect.Method.invoke(Native Method)
                                                   at com.facebook.react.bridge.BaseJavaModule$JavaMethod.invoke(BaseJavaModule.java:318)
                                                   at com.facebook.react.cxxbridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:158)
                                                   at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
                                                   at android.os.Handler.handleCallback(Handler.java:751)
                                                   at android.os.Handler.dispatchMessage(Handler.java:95)
                                                   at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
                                                   at android.os.Looper.loop(Looper.java:185)
                                                   at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:196)
                                                   at java.lang.Thread.run(Thread.java:761)

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!

repo: facebook/react-native


text:
[Loader] define RCTBridgeDelegate and delegate JS loading to it

hey @tadeuzagallo - I would like to be able to control the JS loading process myself so that I can handle errors differently and implement other custom behavior. Do you have plans to do this or would you accept a PR that makes this change? The idea I have is to add a delegate to the bridge called RCTBridgeDelegate. It would look like this:
@protocol RCTBridgeDelegate
@optional
- (void)loadJavaScriptAtURL:(NSURL *)URL
                 onComplete:(void (^)(NSError *error, NSString *script))block;
@end

The default implementation of this delegate method would use the existing RCTJavaScriptLoader and it is backwards-compatible with existing code.

I'm wanting better control over this as well.  This was my hope with https://github.com/facebook/react-native/issues/1463.
I was investigating the route more like the executorClass is done.

Depending on the intent of use for the loader, another issue which is related is https://github.com/facebook/react-native/issues/1652.

Re: use cases -- another thing I wanted to do was add a progress bar to get a better visual sense of whether loading the script is slow or if the bottleneck is elsewhere.

I've filed a few issues around the loading and the bridge setup.  In my case, the code is coming off disk.  I changed the loader to page is directly, and my code is in UTF16 format.  There is no UTF8 conversion cost, no overhead allocation cost, and it helps the lex a little bit as well.  I've moved the loader creation to be earlier, so I can start the paging right away and allow the bridge to get set up in the meantime.  There is a semaphore wait in the bridge which causes a stall.  Moving some things around and allowing the bridge to do some things in parallel has dropped the stall.
My point is if you aren't downloading off the network, the bridge is adding overhead.  The majority of the time is the JS lex.
I'm processing through more performance runs to see what can be done.

:+1: this is a nice idea

Thanks @tadeuzagallo =)

authors: brentvatne ide jwyld


text:
cmd + m and rr is not working in the android emulator

[x] I have reviewed the documentation
[x] I have searched existing issues
[x] I am using the latest React Native version

Environment
Environment:
OS: macOS High Sierra 10.13.3
Node: 8.9.4
Yarn: 1.5.1
npm: 4.6.1
Watchman: Not Found
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003
Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: ^0.54.2 => 0.54.2
Steps to Reproduce

Expected Behavior
cmd + m want to show a menu and rr to refresh
Actual Behavior
nothing happened

Same thing on Linux. I'm afraid that this is emulator bug.

I had the same problem.
Recently I've installed VMWare and as it creates your virtual host, so what's happing is when I start npm start it uses the virtual host instead of the normal internet connection. So basically they are using different networks thus rn server(or expo) can't connect to the app.
One solution that I did was to disable another network adapters, so I just restart the server and it back works out well again

Had the same problem the last few days - RR just randomly stopped refreshing the app in the emulator. Seems like an emulator bug, I recreated the AVD instance and the problem was resolved.

I Fixed This By Clear The Expo App Data From Android Settings, And Making Sure The App Is In Development

Mode

This issue still exists

Same issue here @johnroest

Same problem
Environment:
  OS: macOS High Sierra 10.13.6
  Node: 11.0.0
  Yarn: 1.12.1
  npm: 6.4.1
  Watchman: 4.9.0
  Xcode: Xcode 9.4.1 Build version 9F2000
  Android Studio: 3.2 AI-181.5540.7.32.5056338

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: 0.55.4 => 0.55.4

Hello there 👋 by using the repro / the list of steps to reproduce, we can't actually see the reported bug on RN 0.59 so we'll close this issue. It may have something to do with your local setup, please double check that you are using the correct version of Android Studio / XCode / Android NDK / Yarn / etc.

for me, to resolve it, i uninstalled the expo app from the android emulator and run the app again

This is happening to me on MacOS. Uninstalling and reinstalling the app didn't help. Rebooting the emulator didn't help. Clearing emulator data didn't help. Cold booting emulator didn't help. Not really sure what to do from here, I can't debug Android!

I am currently running into this same issue running RN 0.60.4

If you are using Expo, make sure you are not using Production Mode.

If you are using Expo, make sure you are not using Production Mode.

I'm not using Expo. Just the cli.

Same using 0.61. Not using expo but am using react-native-webview which does appear to steal focus when pressing R

authors: AndrewMorsillo BenQoder Hypothesis-github JacobTBralish Oscarteg RodrigoWP laidlow michalchudziak mstosio raldred sarath-rp scriptum souhaiebtar sryze


text:
[Packager] Watchman fails silently if no root_files are found (ex. .git)

I kept getting this error:
 ERROR  Watcher took too long to load
Try running `watchman version` from your terminal
https://facebook.github.io/watchman/docs/troubleshooting.html
Error: Watcher took too long to load
Try running `watchman version` from your terminal
https://facebook.github.io/watchman/docs/troubleshooting.html
    at [object Object]._onTimeout (/Users/jaredly/clone/meditrate/node_modules/react-native/packager/react-packager/src/FileWatcher/index.js:98:16)
    at Timer.listOnTimeout (timers.js:110:15)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

And reinstalled watchman a bunch of times, restarted my mac, etc...
Digging into the sane package, and adding this patch, I was able to discover that the actual watchman error (it was working just fine) was:
resolve_projpath: none of the files listed in global config root_files are present in path `{the project root}` or any of its parent directories

Which really meant: running git init solved everything. But I wasted a lot of time wondering why things were broken.
So I think the right thing to do here is turn off enforce_root_files.

@jaredly FWIW, at FB, we require enforce_root_files to be set to avoid having folks unwittingly create overlapping watches.  Because our source trees are so large this is a very real cause of performance and reliability issues with watching the filesystem, and is in fact the reason why this feature even exists :-)
@amasad is this a side effect of using watch-project exclusively now in sane?  Do we know if the only people that are hitting this are at FB?  I don't believe that folks outside FB will have the root files restrictions enabled, and certainly not by default.  It would be great to double check what is happening there as watch-project is supposed to fall back to watching the directory of interest if we can't locate a root.

Ok -- yeah I guess it's just because of the watchman config in /etc/watchman.json.
This is an error that we should be able to detect though (as soon as sane exposes error events), and report.

I just spent half an hour on this problem. It should really be documented in the troubleshooting page.

authors: jaredly linshu123 wez


text:
Cannot create a string longer than 0x3fffffe7 characters in jest-haste-map

Description:
Getting the following error when starting my app using npx react-native start  or npx react-native run-android
I already tried clearing my caches using npx react-native start --reset-cache and cache cleaner scripts from npm
warning: the transform cache was reset.
Loading dependency graph...Failed to construct transformer:  Error: Cannot create a string longer than 0x3fffffe7 characters
    at Object.slice (buffer.js:593:37)
    at Buffer.toString (buffer.js:790:14)
    at Object.readFileSync (fs.js:403:41)
    at getContent (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:149:41)
    at Object.<anonymous> (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:199:9)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:78:24)
    at _next (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:98:9)
    at D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:103:7
    at new Promise (<anonymous>) {
  type: 'Error',
  code: 'ERR_STRING_TOO_LONG'
}
(node:1972) UnhandledPromiseRejectionWarning: Error: Cannot create a string longer than 0x3fffffe7 characters
    at Object.slice (buffer.js:593:37)
    at Buffer.toString (buffer.js:790:14)
    at Object.readFileSync (fs.js:403:41)
    at getContent (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:149:41)
    at Object.<anonymous> (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:199:9)
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:78:24)
    at _next (D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:98:9)
    at D:\MyApp\node_modules\metro\node_modules\jest-haste-map\build\worker.js:103:7
    at new Promise (<anonymous>)
(node:1972) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1972) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

React Native version:
Run `react-native info` in your terminal and copy the results here.

System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
    Memory: 2.34 GB / 15.91 GB
  Binaries:
    Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.13.0 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.11.3 - ~\AppData\Roaming\npm\npm.CMD
  SDKs:
    Android SDK:
      API Levels: 24, 25, 26, 28
      Build Tools: 23.0.1, 23.0.3, 25.0.2, 26.0.1, 26.0.2, 28.0.3
  IDEs:
    Android Studio: Version  3.5.0.0 AI-191.8026.42.35.6010548
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: ^0.61.5 => 0.61.5

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Issues without reproduction steps or code are likely to stall.

Create an App named MyApp with 1 file
Copy the App to a different folder and rename all occurrences of MyApp with MyApp2

Expected Results
It launches

So the problem was that i had a folder where i kept all my assets (logos, banners, psds, ...) which was rather big and called _assets. moving that folder a level higher out of the root folder fixed the problem


text:
[PanResponder]:TOO BIG formatValueCalls 228 exceeded limit of 200

Description
my code is something like this:
      <View
        style={styles.container}
        onLayout={this.onLayout}
        {...this.panResponder.panHandlers}
      >
       ...
      </View>

and children could be ScrollView or FlatList,  in some device(for example iPhone X),  lists could not scroll up, scroll down is ok; but in iPhone 11 pro max, everything is fine, and there are logs in XCode:
2020-05-26 16:54:10.793 [info][tid:com.facebook.react.JavaScript] 888, { dispatchConfig:
{ phasedRegistrationNames:
{ bubbled: 'onStartShouldSetResponder',
captured: 'onStartShouldSetResponderCapture' },
dependencies: [ 'topTouchStart' ] },
_targetInst:
{ tag: 5,
key: null,
elementType: 'RCTText',
type: 'RCTText',
stateNode:
{ _nativeTag: 823,
_children: [ 819 ],
viewConfig:
{ validAttributes:
{ pointerEvents: true,
accessible: true,
accessibilityActions: true,
accessibilityLabel: true,
accessibilityLiveRegion: true,
accessibilityRole: true,
accessibilityState: true,
accessibilityValue: true,
accessibilityHint: true,
importantForAccessibility: true,
nativeID: true,
testID: true,
renderToHardwareTextureAndroid: true,
shouldRasterizeIOS: true,
onLayout: true,
onAccessibilityAction: true,
onAccessibilityTap: true,
onMagicTap: true,
onAccessibilityEscape: true,
collapsable: true,
needsOffscreenAlphaCompositing: true,
style:
{ display: true,
width: true,
height: true,
start: true,
end: true,
top: true,
left: true,
right: true,
bottom: true,
minWidth: true,
maxWidth: true,
minHeight: true,
maxHeight: true,
margin: true,
marginVertical: true,
marginHorizontal: true,
marginTop: true,
marginBottom: true,
marginLeft: true,
marginRight: true,
marginStart: true,
marginEnd: true,
padding: true,
paddingVertical: true,
paddingHorizontal: true,
paddingTop: true,
paddingBottom: true,
paddingLeft: true,
paddingRight: true,
paddingStart: true,
paddingEnd: true,
borderWidth: true,
borderTopWidth: true,
borderStartWidth: true,
borderEndWidth: true,
borderRightWidth: true,
borderBottomWidth: true,
borderLeftWidth: true,
position: true,
flexDirection: true,
flexWrap: true,
justifyContent: true,
alignItems: true,
alignSelf: true,
alignContent: true,
flex: true,
flexGrow: true,
flexShrink: true,
flexBasis: true,
aspectRatio: true,
zIndex: true,
direction: true,
shadowColor: { process: [Function: processColor] },
shadowOffset: { diff: [Function: sizesDiffer] },
shadowOpacity: true,
shadowRadius: true,
transform: { process: [Function: processTransform] },
transformMatrix: true,
decomposedMatrix: true,
scaleX: true,
scaleY: true,
rotation: true,
translateX: true,
translateY: true,
backgroundColor: { process: [Function: processColor] },
borderColor: { process: [Function: processColor] },
borderTopColor: { process: [Function: processColor] },
borderRightColor: { process: [Function: processColor] },
borderBottomColor: { process: [Function: processColor] },
borderLeftColor: { process: [Function: processColor] },
borderStartColor: { process: [Function: processColor] },
borderEndColor: { process: [Function: processColor] },
borderRadius: true,
borderTopLeftRadius: true,
borderTopRightRadius: true,
borderTopStartRadius: true,
borderTopEndRadius: true,
borderBottomLeftRadius: true,
borderBottomRightRadius: true,
borderBottomStartRadius: true,
borderBottomEndRadius: true,
borderStyle: true,
opacity: true,
elevation: true,
color: { process: [Function: processColor] },
fontFamily: true,
fontSize: true,
fontStyle: true,
fontWeight: true,
fontVariant: true,
textShadowOffset: true,
textShadowRadius: true,
textShadowColor: { process: [Function: processColor] },
letterSpacing: true,
lineHeight: true,
textAlign: true,
textAlignVertical: true,
includeFontPadding: true,
textDecorationLine: true,
textDecorationStyle: true,
textDecorationColor: { process: [Function: processColor] },
textTransform: true,
writingDirection: true,
resizeMode: true,
backfaceVisibility: true,
overflow: true,
tintColor: { process: [Function: processColor] },
overlayColor: { process: [Function: processColor] } },
isHighlighted: true,
numberOfLines: true,
ellipsizeMode: true,
allowFontScaling: true,
maxFontSizeMultiplier: true,
disabled: true,
selectable: true,
selectionColor: true,
adjustsFontSizeToFit: true,
minimumFontScale: true,
textBreakStrategy: true,
onTextLayout: true,
onInlineViewLayout: true,
dataDetectorType: true },
directEventTypes:
{ topTextLayout: { registrationName: 'onTextLayout' },
topInlineViewLayout: { registrationName: 'onInlineViewLayout' } },
uiViewClassName: 'RCTText' } },
return:
{ tag: 10,
key: null,
elementType:
{ '$$typeof': {},
_context:
{ '$$typeof': {},
_calculateChangedBits: null,
_currentValue: false,
_currentValue2: false,
_threadCount: 0,
Provider: [Circular],
Consumer:
{ '$$typeof': {},
_context: [Circular],
_calculateChangedBits: null },
_currentRenderer: {},
_currentRenderer2: null } },
type: [TOO BIG formatValueCalls 201 exceeded limit of 200],
stateNode: [TOO BIG formatValueCalls 202 exceeded limit of 200],
return: [TOO BIG formatValueCalls 203 exceeded limit of 200],
child: [Circular],
sibling: [TOO BIG formatValueCalls 204 exceeded limit of 200],
index: [TOO BIG formatValueCalls 205 exceeded limit of 200],
ref: [TOO BIG formatValueCalls 206 exceeded limit of 200],
pendingProps: [TOO BIG formatValueCalls 207 exceeded limit of 200],
memoizedProps: [TOO BIG formatValueCalls 208 exceeded limit of 200],
updateQueue: [TOO BIG formatValueCalls 209 exceeded limit of 200],
memoizedState: [TOO BIG formatValueCalls 210 exceeded limit of 200],
dependencies: [TOO BIG formatValueCalls 211 exceeded limit of 200],
mode: [TOO BIG formatValueCalls 212 exceeded limit of 200],
effectTag: [TOO BIG formatValueCalls 213 exceeded limit of 200],
nextEffect: [TOO BIG formatValueCalls 214 exceeded limit of 200],
firstEffect: [Circular],
lastEffect: [Circular],
expirationTime: [TOO BIG formatValueCalls 215 exceeded limit of 200],
childExpirationTime: [TOO BIG formatValueCalls 216 exceeded limit of 200],
alternate: [TOO BIG formatValueCalls 217 exceeded limit of 200],
actualDuration: [TOO BIG formatValueCalls 218 exceeded limit of 200],
actualStartTime: [TOO BIG formatValueCalls 219 exceeded limit of 200],
selfBaseDuration: [TOO BIG formatValueCalls 220 exceeded limit of 200],
treeBaseDuration: [TOO BIG formatValueCalls 221 exceeded limit of 200],
_debugID: [TOO BIG formatValueCalls 222 exceeded limit of 200],
_debugIsCurrentlyTiming: [TOO BIG formatValueCalls 223 exceeded limit of 200],
_debugSource: [TOO BIG formatValueCalls 224 exceeded limit of 200],
_debugOwner: [TOO BIG formatValueCalls 225 exceeded limit of 200],
_debugNeedsRemount: [TOO BIG formatValueCalls 226 exceeded limit of 200],
_debugHookTypes: [TOO BIG formatValueCalls 227 exceeded limit of 200] },
child: [TOO BIG formatValueCalls 228 exceeded limit of 200],
sibling: [TOO BIG formatValueCalls 229 exceeded limit of 200],
index: [TOO BIG formatValueCalls 230 exceeded limit of 200],
ref: [TOO BIG formatValueCalls 231 exceeded limit of 200],
pendingProps: [TOO BIG formatValueCalls 232 exceeded limit of 200],
memoizedProps: [TOO BIG formatValueCalls 233 exceeded limit of 200],
updateQueue: [TOO BIG formatValueCalls 234 exceeded limit of 200],
memoizedState: [TOO BIG formatValueCalls 235 exceeded limit of 200],
dependencies: [TOO BIG formatValueCalls 236 exceeded limit of 200],
mode: [TOO BIG formatValueCalls 237 exceeded limit of 200],
effectTag: [TOO BIG formatValueCalls 238 exceeded limit of 200],
nextEffect: [TOO BIG formatValueCalls 239 exceeded limit of 200],
firstEffect: [TOO BIG formatValueCalls 240 exceeded limit of 200],
lastEffect: [TOO BIG formatValueCalls 241 exceeded limit of 200],
expirationTime: [TOO BIG formatValueCalls 242 exceeded limit of 200],
childExpirationTime: [TOO BIG formatValueCalls 243 exceeded limit of 200],
alternate: [TOO BIG formatValueCalls 244 exceeded limit of 200],
actualDuration: [TOO BIG formatValueCalls 245 exceeded limit of 200],
actualStartTime: [TOO BIG formatValueCalls 246 exceeded limit of 200],
selfBaseDuration: [TOO BIG formatValueCalls 247 exceeded limit of 200],
treeBaseDuration: [TOO BIG formatValueCalls 248 exceeded limit of 200],
_debugID: [TOO BIG formatValueCalls 249 exceeded limit of 200],
_debugIsCurrentlyTiming: [TOO BIG formatValueCalls 250 exceeded limit of 200],
_debugSource: [TOO BIG formatValueCalls 251 exceeded limit of 200],
_debugOwner: [TOO BIG formatValueCalls 252 exceeded limit of 200],
_debugNeedsRemount: [TOO BIG formatValueCalls 253 exceeded limit of 200],
_debugHookTypes: [TOO BIG formatValueCalls 254 exceeded limit of 200] },
_dispatchListeners: [TOO BIG formatValueCalls 255 exceeded limit of 200],
_dispatchInstances: [TOO BIG formatValueCalls 256 exceeded limit of 200],
nativeEvent: [TOO BIG formatValueCalls 257 exceeded limit of 200],
type: [TOO BIG formatValueCalls 258 exceeded limit of 200],
target: [TOO BIG formatValueCalls 259 exceeded limit of 200],
currentTarget: [TOO BIG formatValueCalls 260 exceeded limit of 200],
eventPhase: [TOO BIG formatValueCalls 261 exceeded limit of 200],
bubbles: [TOO BIG formatValueCalls 262 exceeded limit of 200],
cancelable: [TOO BIG formatValueCalls 263 exceeded limit of 200],
timeStamp: [TOO BIG formatValueCalls 264 exceeded limit of 200],
defaultPrevented: [TOO BIG formatValueCalls 265 exceeded limit of 200],
isTrusted: [TOO BIG formatValueCalls 266 exceeded limit of 200],
touchHistory: [TOO BIG formatValueCalls 267 exceeded limit of 200],
isDefaultPrevented: [TOO BIG formatValueCalls 268 exceeded limit of 200],
isPropagationStopped: [TOO BIG formatValueCalls 269 exceeded limit of 200] }

## React Native version:

System:
OS: macOS 10.15.4
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 588.88 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 13.12.0 - /usr/local/bin/node
Yarn: 1.22.4 - ~/.yarn/bin/yarn
npm: 6.14.5 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 21, 23, 26, 27, 28
Build Tools: 23.0.1, 26.0.1, 26.0.2, 28.0.3, 29.0.2
System Images: android-28 | Google Play Intel x86 Atom, android-R | Google Play Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 3.6 AI-192.7142.36.36.6392135
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
Languages:
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.0 => 0.62.0
npmGlobalPackages:
react-native: Not Found

## Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

1.
2.

## Expected Results
lists scroll up smoothly

## Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

i see; do not use console.log() in onStartShouldSetPanResponder or something


text:
ScrollViewClass must not be undefined

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
unable to load the screen with basic ui and doesn't add any functionality

React Native version:
System:
OS: macOS 11.0.1
CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
Memory: 71.36 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.16.0 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.11 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.7042882
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 13.0.1 - /Library/Java/JavaVirtualMachines/jdk-13.0.1.jdk/Contents/Home/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Login screen created and cloned for signup screen
After completing design with common custom components which is used for login, throwing issue

Expected Results
Has to load signup screen like login.

@augustl
Can you help me out

Closing as stale + no reproduce was provided


text:
metro "refresh" - R - crashes app

Description
Getting a crash on 0.72.3 build. Just load up IOS simulator 16.4 IOS on IOS 14 Pro Max. Press "r" this is what you get
Thread 22 Crashed::  Dispatch queue: com.facebook.react.WebSocketExecutor
0   ???                           	       0x111dd59a8 ???
1   <translation info unavailable>	       0x1181aee44 ???
2   libsystem_pthread.dylib       	       0x126039ee6 pthread_kill + 263
3   libsystem_c.dylib             	       0x125dd3e58 abort + 130
4   libc++abi.dylib               	       0x11a5005f2 abort_message + 241
5   libc++abi.dylib               	       0x11a4f27b1 demangling_terminate_handler() + 241
6   libobjc.A.dylib               	       0x1204c618a _objc_terminate() + 104
7   TheClub                       	       0x1050196f5 FIRCLSTerminateHandler() + 325
8   libc++abi.dylib               	       0x11a4ffa4b std::__terminate(void (*)()) + 6
9   libc++abi.dylib               	       0x11a4ffa06 std::terminate() + 54
10  libdispatch.dylib             	       0x125cc40ed _dispatch_client_callout + 28
11  libdispatch.dylib             	       0x125ccbb23 _dispatch_lane_serial_drain + 1008
12  libdispatch.dylib             	       0x125ccc7ef _dispatch_lane_invoke + 400
13  libdispatch.dylib             	       0x125cd9475 _dispatch_workloop_worker_thread + 873
14  libsystem_pthread.dylib       	       0x126036c55 _pthread_wqthread + 327
15  libsystem_pthread.dylib       	       0x126035bbf start_wqthread + 15

React Native Version
0.72.3
Output of npx react-native info
See above
Steps to reproduce
See above
Snack, screenshot, or link to a repository
See above

Output of npx react-native info
See above

Can you please fill the issue template and provide a reproducer?

Closing as unresponsive

authors: billnbell cortinico


text:
Android TV development issues

Description
Some issues found when adapting to Android TV

There is a lack of events that define the selection of elements, such as onSelect. We need to set the card selection status based on it (with white borders, shadows, zooming in, etc.). The design effect is as follows

Can you provide a scrollview API similar to web to scroll to the center of the view when elements are focused

After adding onFocus={()=>console. log ('--------')} to the example code below, the card was selected, but the onFocus example was not triggered
`
import {Dimensions, Image, Text, Pressable, View} from 'react-native';
import LinearGradient from 'react-native-linear-gradient';
import {FoodCardProps} from './types.d';
import {baseUrl} from '@/config';
import {useNavigation} from '@react-navigation/native';
const window = Dimensions.get('window');
const scale = window.width / 1920;
export const FoodCard = (props: FoodCardProps) => {
const navigation: any = useNavigation();
return (
<Pressable
onPress={() =>
navigation.navigate('ShopView', {
id: props.data.id,
shop_id: props.data.shop_id,
name: props.data.name,
})
}
style={[
props.style,
{
position: 'relative',
marginBottom: 32 * scale,
elevation: 1,
},
]}
android_disableSound={false}
android_ripple={{foreground: true, borderless: false, color: '#0052d9'}}>

<Image
resizeMode="cover"
style={{width: 564 * scale, height: 282 * scale}}
source={{uri: baseUrl + props.data.image}}
/>
<LinearGradient
colors={['#00B1FF', '#0BCAFF', '#3EF2B6']}
start={{x: 0, y: 0}}
end={{x: 1, y: 0}}
style={{
width: 564 * scale,
height: 216 * scale,
padding: 32 * scale,
}}>
<Text
style={{
fontFamily: 'PingFangSC-Medium',
fontSize: 40 * scale,
color: '#fff',
letterSpacing: 0,
lineHeight: 50 * scale,
fontWeight: '500',
marginBottom: 10 * scale,
}}>
{props.data.name}

<View
style={{
display: 'flex',
flexDirection: 'row',
alignItems: 'center',
marginRight: 16 * scale,
}}>
{props.data.tags.map(tag => {
return (
<Text
style={{
borderWidth: 1.5 * scale,
borderRadius: 22 * scale,
borderColor: 'rgba(255,255,255,0.4)',
paddingHorizontal: 15 * scale,
paddingVertical: 6 * scale,
marginRight: 16 * scale,
color: '#fff',
}}
key={tag}>
{tag}

);
})}

<Text
style={{
fontFamily: 'PingFangSC-Medium',
fontSize: 28 * scale,
color: '#fff',
letterSpacing: 0,
lineHeight: 32 * scale,
fontWeight: '400',
marginTop: 24 * scale,
}}>
{props.data.shop_name}

   <Text
     style={{
       position: 'absolute',
       bottom: 12 * scale,
       right: 16 * scale,
       fontFamily: 'PingFangSC-Medium',
       fontSize: 44 * scale,
       color: '#fff',
       letterSpacing: 0,
       lineHeight: 44 * scale,
       fontWeight: '900',
     }}>
     ¥ {props.data.price}
   </Text>
 </LinearGradient>

);
};
`
Of course, perhaps I am not familiar with the Android TV development process. If you have better suggestions, we can communicate with you
React Native Version
0.72.3
Output of npx react-native info
no
Steps to reproduce
no
Snack, screenshot, or link to a repository
no

`import {Dimensions, Image, Text, Pressable, View} from 'react-native';
import LinearGradient from 'react-native-linear-gradient';
import {FoodCardProps} from './types.d';
import {baseUrl} from '@/config';
import {useNavigation} from '@react-navigation/native';
const window = Dimensions.get('window');
const scale = window.width / 1920;
export const FoodCard = (props: FoodCardProps) => {
const navigation: any = useNavigation();
return (
<Pressable
onFocus={() => console.log('---------')}
onPress={() =>
navigation.navigate('ShopView', {
id: props.data.id,
shop_id: props.data.shop_id,
name: props.data.name,
})
}
style={[
props.style,
{
position: 'relative',
marginBottom: 32 * scale,
elevation: 1,
},
]}
android_disableSound={false}
android_ripple={{foreground: true, borderless: false, color: '#0052d9'}}>

<Image
resizeMode="cover"
style={{width: 564 * scale, height: 282 * scale}}
source={{uri: baseUrl + props.data.image}}
/>
<LinearGradient
colors={['#00B1FF', '#0BCAFF', '#3EF2B6']}
start={{x: 0, y: 0}}
end={{x: 1, y: 0}}
style={{
width: 564 * scale,
height: 216 * scale,
padding: 32 * scale,
}}>
<Text
style={{
fontFamily: 'PingFangSC-Medium',
fontSize: 40 * scale,
color: '#fff',
letterSpacing: 0,
lineHeight: 50 * scale,
fontWeight: '500',
marginBottom: 10 * scale,
}}>
{props.data.name}

<View
style={{
display: 'flex',
flexDirection: 'row',
alignItems: 'center',
marginRight: 16 * scale,
}}>
{props.data.tags.map(tag => {
return (
<Text
style={{
borderWidth: 1.5 * scale,
borderRadius: 22 * scale,
borderColor: 'rgba(255,255,255,0.4)',
paddingHorizontal: 15 * scale,
paddingVertical: 6 * scale,
marginRight: 16 * scale,
color: '#fff',
}}
key={tag}>
{tag}

);
})}

<Text
style={{
fontFamily: 'PingFangSC-Medium',
fontSize: 28 * scale,
color: '#fff',
letterSpacing: 0,
lineHeight: 32 * scale,
fontWeight: '400',
marginTop: 24 * scale,
}}>
{props.data.shop_name}

      <Text
        style={{
          position: 'absolute',
          bottom: 12 * scale,
          right: 16 * scale,
          fontFamily: 'PingFangSC-Medium',
          fontSize: 44 * scale,
          color: '#fff',
          letterSpacing: 0,
          lineHeight: 44 * scale,
          fontWeight: '900',
        }}>
        ¥ {props.data.price}
      </Text>
    </LinearGradient>
  </View>
</Pressable>

);
};
`
代码片段

Hi @renjiali
Thanks for reporting this issue.
It seems like this issue is actually unrelated to React Native core. Please open this issue against this other repository:
https://github.com/react-native-tvos/react-native-tvos/issues
I'll be closing this but feel free to reopen if the other repo points back to us as a issue in the core of React Native.

authors: cortinico renjiali


text:
Build Failed with Expo and React Native - main.jsbundle does not exist

Description
I'm developing an app using Expo and React Native, and trying to make an iOS build using eas build -p iOS. It fails every time at Run fastlane, and the build details show the following message:
❌  error: File /Users/expo/Library/Developer/Xcode/DerivedData/freeapp-celtkelekabrvocesclaslgcuhcp/Build/Intermediates.noindex/ArchiveIntermediates/freeapp/BuildProductsPath/Release-iphoneos/freeapp.app/main.jsbundle does not exist. This must be a bug with React Native, please report it here: https://github.com/facebook/react-native/issues
React Native Version
0.72.4
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.3.1
CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
Memory: 684.48 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 14.21.2
path: ~/.nvm/versions/node/v14.21.2/bin/node
Yarn:
version: 1.22.19
path: ~/.nvm/versions/node/v14.21.2/bin/yarn
npm:
version: 6.14.17
path: ~/.nvm/versions/node/v14.21.2/bin/npm
Watchman:
version: 2023.01.30.00
path: /usr/local/bin/watchman
Managers:
CocoaPods:
version: 1.12.0
path: /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9514443
Xcode:
version: 14.3.1/14E300c
path: /usr/bin/xcodebuild
Languages:
Java: Not Found
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.72.4
wanted: 0.72.4
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
eas build -p iOS
Snack, screenshot, or link to a repository
https://github.com/expo/expo/issues/21542

If you're using Expo, please report the bugs on Expo's repository.

This must be a bug with React Native, please report it here: facebook/react-native/issues

This error message is confusing and should probably be changed by the Expo folks (cc @Kudo)

@cortinico you should did that already in f874a7e7d3639d953749643eac072f29c25525b0 😅
@tej-thambi for eas build problem. please open an issue at https://github.com/expo/expo/issues.

you should did that already in f874a7e 😅

Oh man 😅 you're so right

authors: Kudo cortinico tej-thambi


text:
[Android] Build from source in Android Studio OSX fails :ReactAndroid:buildReactNdkLib

Using the latest React Native master (a7e5312), I'm unable to build from source inside of Android Studio.
Followed the documents for building Android React Native from source at the following URL:
https://facebook.github.io/react-native/docs/android-building-from-source.html
Attempted with both Android NDK r11e and r10b with the same results.
This looks somewhat related to issue #6608 but using the same NDK version on Mac did not resolve the issue.
OS: OSX 10.11.4
Android Studio Version: 1.5.1
Branch: master
Log:
:ReactAndroid:downloadJSCHeaders UP-TO-DATE
:ReactAndroid:prepareJSC
:ReactAndroid:buildReactNdkLib
Android NDK: WARNING:/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni//react/Android.mk:reactnative: LOCAL_LDLIBS is always ignored for static libraries
Android NDK: WARNING:/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni//react/Android.mk:reactnative: LOCAL_LDLIBS is always ignored for static libraries
make: Entering directory `/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni/react/jni'
[armeabi-v7a] Compile++ thumb: reactnativejni <= JSCPerfLogging.cpp
[armeabi-v7a] Compile++ thumb: reactnativejni <= JSLogging.cpp
[armeabi-v7a] Compile++ thumb: reactnativejni <= OnLoad.cpp
[armeabi-v7a] Compile++ thumb: reactnativejni <= ProxyExecutor.cpp
[armeabi-v7a] Prebuilt       : libjsc.so <= /mySourceCodePath/node_modules/react-native/ReactAndroid/build/third-party-ndk/jsc/jni/armeabi-v7a/
[armeabi-v7a] Compile++ thumb: reactnative <= Bridge.cpp
[armeabi-v7a] Compile++ thumb: reactnative <= JSCExecutor.cpp

./OnLoad.cpp: In member function 'void facebook::react::{anonymous}::bridge::PlatformBridgeCallback::executeCallbackOnCallbackQueueThread(std::function<void(facebook::jni::ResolvedWeakReference&)>&&)':
./OnLoad.cpp:634:39: error: lambda capture initializers only available with -std=c++1y or -std=gnu++1y [-Werror]
     auto runnableWrapper = std::bind([weakCallback=weakCallback_] (std::function<void(ResolvedWeakReference&)>& runnable) {
                                       ^

[armeabi-v7a] Compile++ thumb: reactnative <= JSCHelpers.cpp

/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni//react/JSCExecutor.cpp: In member function 'void facebook::react::JSCExecutor::postMessageToOwner(JSValueRef)':
/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni//react/JSCExecutor.cpp:381:46: error: lambda capture initializers only available with -std=c++1y or -std=gnu++1y [-Werror]
   m_owner->m_messageQueueThread->runOnQueue([workerId=m_workerId, owner=m_owner, ownerIsDestroyed, msgString] () {
                                              ^
/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni//react/JSCExecutor.cpp:381:67: error: lambda capture initializers only available with -std=c++1y or -std=gnu++1y [-Werror]
   m_owner->m_messageQueueThread->runOnQueue([workerId=m_workerId, owner=m_owner, ownerIsDestroyed, msgString] () {
                                                                   ^

[armeabi-v7a] Compile++ thumb: reactnative <= Platform.cpp
[armeabi-v7a] Compile++ thumb: reactnative <= Value.cpp
[armeabi-v7a] Install        : libfolly_json.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libfolly_json.so
[armeabi-v7a] Install        : libfbjni.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libfbjni.so
[armeabi-v7a] Install        : libjsc.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libjsc.so
[armeabi-v7a] Install        : libglog_init.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libglog_init.so
[armeabi-v7a] Install        : libgnustl_shared.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libgnustl_shared.so
[armeabi-v7a] Install        : libfb.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libfb.so
[armeabi-v7a] Install        : libglog.so => /mySourceCodePath/node_modules/react-native/ReactAndroid/build/react-ndk/all/armeabi-v7a/libglog.so
[x86] Compile++      : reactnativejni <= JSCPerfLogging.cpp
[x86] Compile++      : reactnativejni <= JSLogging.cpp

cc1plus: all warnings being treated as errors
make: *** [/mySourceCodePath/node_modules/react-native/ReactAndroid/build/tmp/buildReactNdkLib/local/armeabi-v7a/objs/reactnative/JSCExecutor.o] Error 1
make: *** Waiting for unfinished jobs....
cc1plus: all warnings being treated as errors
make: *** [/mySourceCodePath/node_modules/react-native/ReactAndroid/build/tmp/buildReactNdkLib/local/armeabi-v7a/objs/reactnativejni/OnLoad.o] Error 1

make: Leaving directory `/mySourceCodePath/node_modules/react-native/ReactAndroid/src/main/jni/react/jni'
:ReactAndroid:buildReactNdkLib FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':ReactAndroid:buildReactNdkLib'.
> Process 'command '/Users/*****/Library/Android/ndk/ndk-build'' finished with non-zero exit value 2

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

@berickson1 NDK r11e is not supported. Can you try again with r10e:
Refer links here:
http://facebook.github.io/react-native/releases/next/docs/android-building-from-source.html#content

@facebook-github-bot answered

@berickson1 make sure you change the NDK path in the ANDROID_NDK variable as well as your local.properties file.

@chirag04 I've verified with that I'm using Android NDK r10e.  I've set the ANDROID_NDK environment variable properly (and set android.ndk in local.properties)
The build is failing with the aforementioned error.

@berickson1 Make sure android studio is not overriding your local.properties(it re-generates local.properties automatically) and android studio can see you environment variables.
Goto Terminal tab inside android studio and see if you have ANDROID_NDK set. otherwise set the variable in Android Studio -> Preferences -> Path Variables.

Looks like my Android Studio was overriding my NDK version and using r11b. Thanks for the help!


text:
[DOCS][MINOR][RCTImageView.m] Fixed typo in comments

Fixed spelling error in comments.

Motivation
Help fix typo in comments.
Test Plan
Did not make any code changes
Release Notes
[DOCS][MINOR][RCTImageView.m] Typo fixes in comments

Thanks for the fix!
@facebook-github-bot shipit

@nak411 Could you just sign the CLA so we can merge this?

@janicduplessis signed


text:
Fix support for --sourcemap-output path containing spaces in Xcode projects

This PR contains the changes from https://github.com/facebook/react-native/pull/30981 that got closed due to inactivity.
Many thanks to @nickdowell for this bug report & fix. We encountered this error in our project when we had an Xcode scheme that contains a space (like AppName alpha).
Summary:
This change fixes the generation of source maps for Xcode projects where the output path contains spaces.
The EXTRA_ARGS environment variable, being a plain string, would be split into arguments by whitespace - so a path containing spaces was being treated as several arguments rather than one.
This change uses an array to contain the arguments instead, allowing the proper handling of arguments that may contain spaces.
Changelog:
[iOS] [Fixed] - Fix support for --sourcemap-output path containing spaces
Test Plan:
Tested using a sample project with the following "Bundle React Native code and images" Xcode build phase
export SOURCEMAP_FILE="$CONFIGURATION_BUILD_DIR/$UNLOCALIZED_RESOURCES_FOLDER_PATH/main.jsbundle.map"
set -e
export NODE_BINARY=node
../node_modules/react-native/scripts/react-native-xcode.sh

and a CONFIGURATION_BUILD_DIR that contains spaces - ~/Library/Xcode/Derived Data. You can also try an XCode-scheme that contains a space.
Before
+ EXTRA_ARGS=
+ case "$PLATFORM_NAME" in
+ BUNDLE_PLATFORM=ios
+ EMIT_SOURCEMAP=
+ [[ ! -z /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map ]]
+ EMIT_SOURCEMAP=true
+ PACKAGER_SOURCEMAP_FILE=
+ [[ true == true ]]
+ [[ '' == true ]]
+ PACKAGER_SOURCEMAP_FILE='/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map'
+ EXTRA_ARGS=' --sourcemap-output /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map'
+ node /Users/nick/Desktop/RN064/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output '/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/main.jsbundle' --assets-dest '/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app' --sourcemap-output /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map
                    Welcome to Metro!
              Fast - Scalable - Integrated

info Writing bundle output to:, /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/main.jsbundle
info Writing sourcemap output to:, /Users/nick/Library/Developer/Xcode/Derived

Note the incorrect sourcemap output path.
After
+ EXTRA_ARGS=()
+ case "$PLATFORM_NAME" in
+ BUNDLE_PLATFORM=ios
+ EMIT_SOURCEMAP=
+ [[ ! -z /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map ]]
+ EMIT_SOURCEMAP=true
+ PACKAGER_SOURCEMAP_FILE=
+ [[ true == true ]]
+ [[ '' == true ]]
+ PACKAGER_SOURCEMAP_FILE='/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map'
+ EXTRA_ARGS+=("--sourcemap-output")
+ EXTRA_ARGS+=("$PACKAGER_SOURCEMAP_FILE")
+ node /Users/nick/Desktop/RN064/node_modules/react-native/cli.js bundle --entry-file index.js --platform ios --dev false --reset-cache --bundle-output '/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/main.jsbundle' --assets-dest '/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app' --sourcemap-output '/Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map'
                    Welcome to Metro!
              Fast - Scalable - Integrated

info Writing bundle output to:, /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/main.jsbundle
info Writing sourcemap output to:, /Users/nick/Library/Developer/Xcode/Derived Data/RN064-cpnwckdferodycbevupbrkjydate/Build/Products/Release-iphonesimulator/RN064.app/main.jsbundle.map

sourcemap output path fixed 🎉

CLA should be fine.

When will this PR be merged?

Bump

Bump

@cipolleschi any concerns with this?

The changes looks good to me, the problem is that those script are very brittle.
I remember once I landed a PR that looked innocent, it was wrapping a shell variable in " and that broke some setup because they were passing already escaped paths.
These changes seem to sanitize the params, so I'm positive in try to import and landing these.
If they break something, somebody will reach out, but I think that these changes are for the best.

Also see https://github.com/facebook/react-native/pull/41845

App is crashing for me when I add these changes.
*** Terminating app due to uncaught exception 'RCTFatalException: Unhandled JS Exception: Property 'Reproducer' doesn't exist

ReferenceError: Property 'Reproducer' doesn't exist
    at global (address at /Users/maykon/Library/Developer/CoreSimulator/Devices/A2F4DE2D-DC69-43A7-B897-744B56C8813E/data/Containers/Bundle/Application/A87E55DB-E847-458E-A806-71BA6CA1DFAF/Reproducer App.app/main.jsbundle:1:13284)', reason: 'Unhandled JS Exception: Property 'Reproducer' doesn't exist

ReferenceError: Property 'Reproducer' doesn't exist
    at global (address at /Users/maykon/Library/Developer/Core...'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000180491128 __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x000000018008412c objc_exception_throw + 56
	2   Reproducer App                      0x000000010078ed6c RCTFormatError + 0
	3   Reproducer App                      0x00000001007a4edc __28-[RCTCxxBridge handleError:]_block_invoke + 516
	4   libdispatch.dylib                   0x00000001010980f0 _dispatch_call_block_and_release + 24
	5   libdispatch.dylib                   0x000000010109993c _dispatch_client_callout + 16
	6   libdispatch.dylib                   0x00000001010a95e4 _dispatch_main_queue_drain + 1228
	7   libdispatch.dylib                   0x00000001010a9108 _dispatch_main_queue_callback_4CF + 40
	8   CoreFoundation                      0x00000001803f1a30 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12
	9   CoreFoundation                      0x00000001803ec148 __CFRunLoopRun + 1936
	10  CoreFoundation                      0x00000001803eb5a4 CFRunLoopRunSpecific + 572
	11  GraphicsServices                    0x000000018e9fbae4 GSEventRunModal + 160
	12  UIKitCore                           0x00000001852f02e4 -[UIApplication _run] + 868
	13  UIKitCore                           0x00000001852f3f5c UIApplicationMain + 124
	14  Reproducer App                      0x0000000100746530 main + 80
	15  dyld                                0x0000000101011544 start_sim + 20
	16  ???                                 0x00000001011b60e0 0x0 + 4313538784
	17  ???                                 0xaf4a000000000000 0x0 + 12630908104913977344
)
libc++abi: terminating due to uncaught exception of type NSException

Reproducible example here.
I'm setting SOURCEMAP_FILE to "$DERIVED_FILE_DIR/main.jsbundle.map" and this is probably an edge case of your code. In my case the fix was pretty simple as you can see on PR #41845.

Hi @JorenVos and @maykonmichel, thanks for your PRs.
@maykonmichel did you apply your PR (#41845) on top of this one? I'm trying to understand whether we need both or yours would be enough for everyone.

I did some tests and these are the results:

export SOURCEMAP_FILE="$CONFIGURATION_BUILD_DIR/$UNLOCALIZED_RESOURCES_FOLDER_PATH/main.jsbundle.map"

✅ #40937
✅ #41845
✅ #41845 & #40937

export SOURCEMAP_FILE="$DERIVED_FILE_DIR/main.jsbundle.map"

❌  #40937 (crashes)
✅ #41845
✅ #41845 & #40937

I have addressed and resolved all scenarios individually tested in #41845. This fix can be applied either independently or on top of #40937. In the case of #40937, there is a crash when setting SOURCEMAP_FILE="$DERIVED_FILE_DIR/main.jsbundle.map". From my analysis, it seems safe to merge only my pull request, unless there are additional issues that I may have overlooked.

authors: JorenVos NickGerleman cipolleschi cortinico maykonmichel


text:
ModuleNotFoundError: No module named 'commons'

🐛 Bug
I receive a ModuleNotFoundError for the module commons when calling infer.py for examples/mms/tts
To Reproduce

I cloned fairseq
did a pip install --editable ./
changed the directory to examples/mms/tts/
called python infer.py --model-dir model/ --wav test.wav --txt "Heute ist ein schöner Tag."

Expected behavior
I expect the wav to be generated.
Environment

fairseq Version (e.g., 1.0 or main): main
PyTorch Version (e.g., 1.0): 2.0.1
OS (e.g., Linux): Windows 10
How you installed fairseq (pip, source): pip from github
Build command you used (if compiling from source):
Python version: 3.10
CUDA/cuDNN version: 11.8
GPU models and configuration:
Any other relevant information:

How to Transcribe Audio to text (Google Colab Version)👇
Step 1: Clone the Fairseq Git Repo
import os

!git clone https://github.com/pytorch/fairseq

# Get the current working directory
current_dir = os.getcwd()

# Create the directory paths
audio_samples_dir = os.path.join(current_dir, "audio_samples")
temp_dir = os.path.join(current_dir, "temp_dir")

# Create the directories if they don't exist
os.makedirs(audio_samples_dir, exist_ok=True)
os.makedirs(temp_dir, exist_ok=True)

# Change current working directory
os.chdir('fairseq')

!pwd

Step 2: Install requirements and build
Be patient, takes some minutes
!pip install --editable ./
Step 3: Install Tensor Board
!pip install tensorboardX
Step 4: Download your preferred model
Un-comment to download any. If you're not using Google Colab pro then use a smaller model to avoid memory outrage
# # MMS-1B:FL102 model - 102 Languages - FLEURS Dataset
# !wget -P ./models_new 'https://dl.fbaipublicfiles.com/mms/asr/mms1b_fl102.pt'

# # MMS-1B:L1107 - 1107 Languages - MMS-lab Dataset
# !wget -P ./models_new 'https://dl.fbaipublicfiles.com/mms/asr/mms1b_l1107.pt'

# MMS-1B-all - 1162 Languages - MMS-lab + FLEURS + CV + VP + MLS
!wget -P ./models_new 'https://dl.fbaipublicfiles.com/mms/asr/mms1b_all.pt'

Step 5: Upload your audio(s)
Create a folder on path '/content/audio_samples/'  and upload your .wav audio files that you need to transcribe
e.g. '/content/audio_samples/small_trim4.wav'
Note: You need to make sure that the audio data you are using has a sample rate of 16000
You can easily do this with FFMPEG like the example below that converts .mp3 file to .wav and fixing the audio sample rate
ffmpeg -i .\small_trim4.mp3 -ar 16000 .\wav_formats\small_trim4.wav

Step 6: Run Inference and transcribe your audio(s)
Takes some time for long audios
import os

os.environ["TMPDIR"] = '/content/temp_dir'
os.environ["PYTHONPATH"] = "."
os.environ["PREFIX"] = "INFER"
os.environ["HYDRA_FULL_ERROR"] = "1"
os.environ["USER"] = "micro"

!python examples/mms/asr/infer/mms_infer.py --model "/content/fairseq/models_new/mms1b_all.pt" --lang "swh" --audio "/content/audio_samples/small_trim4.wav"

After this you'll get your preffered transcription
I have this Collab Example in my GitHub Repo👉 fairseq_meta_mms_Google_Colab_implementation

@padmalcom Please make sure you installed vits and do:PYTHONPATH=$PYTHONPATH:/path/to/vits python infer.py .....

@chevalierNoir Thank you, I was missing vits.

authors: chevalierNoir epk2112 padmalcom

repo: facebookresearch/fairseq


text:
Question about the queue for key encoder

Hey,
First of all, thank you for the code.
I have a doubt about updating the queue using the mini-batch. In the paper, the size of the queue is 65,536, which is basically the number of negative keys. I have confusion about the term "keys" here, does 65,536 keys mean 65,336 images or does it mean 65,536 features generated from the key encoder?

来信收到，谢谢！

it mean 65,536 features generated from the key encoder

it means 65,536 features generated from the key encoder

authors: Aikoin Rohit8y solauky

repo: facebookresearch/moco


text:
Update screenshot-2.png

Fixed English on screenshot-2.png. The original reads "See much how you have Elo points you have gained or lost in the match history". Fixed to say "See how many Elo points you have gained or lost in the match history".
Apologies if the text is misaligned, did it quickly as I did not have the original font or text to edit.

Sorry for replying now, I'm not watching this repository. Thanks a lot for spotting and fixing this! 🙇

authors: prduren timche

repo: faceit-enhancer/website


text:
🛑 expomujer.misiones.gob.ar is down

In 0e2fef3, expomujer.misiones.gob.ar (https://expomujer.misiones.gob.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: expomujer.misiones.gob.ar is back up in 9100635.