text:
pip install breaks on python 3.12.3

$ pip install kavanoz
...
...
      [ 10%] Performing download step (verify and extract) for 'lief_utfcpp'
      -- verifying file...
           file='/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/third-party//utfcpp-3.2.1.zip'
      -- verifying file... done
      -- extracting...
           src='/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/third-party/utfcpp-3.2.1.zip'
           dst='/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/build/temp.linux-x86_64-cpython-312/lief_utfcpp-prefix/src/lief_utfcpp'
      -- extracting... [tar xfz]
      -- extracting... [analysis]
      -- extracting... [rename]
      -- extracting... [clean up]
      -- extracting... done
      [ 10%] No update step for 'lief_utfcpp'
      [ 10%] No patch step for 'lief_utfcpp'
      [ 10%] No configure step for 'lief_utfcpp'
      [ 10%] No build step for 'lief_utfcpp'
      [ 10%] No install step for 'lief_utfcpp'
      [ 10%] Completed 'lief_utfcpp'
      [ 10%] Built target lief_utfcpp
      [ 10%] Generating internal/utfcpp/utf8.h
      [ 10%] Generating include/LIEF/third-party/internal/leaf.hpp
      [ 10%] Generating include/LIEF/third-party/internal/span.hpp
      [ 10%] Generating internal/nlohmann/json.hpp
      [ 10%] Building CXX object CMakeFiles/LIB_LIEF.dir/src/errors.cpp.o
      [ 10%] Building CXX object CMakeFiles/LIB_LIEF.dir/src/hash_stream.cpp.o
      [ 11%] Building CXX object CMakeFiles/LIB_LIEF.dir/src/logging.cpp.o
      [ 11%] Building CXX object CMakeFiles/LIB_LIEF.dir/src/exception.cpp.o
      In file included from /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/src/exception.cpp:19:
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:75:38: error: expected ‘)’ before ‘offset’
         75 |   explicit read_out_of_bound(uint64_t offset, uint64_t size);
            |                             ~        ^~~~~~~
            |                                      )
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:76:38: error: expected ‘)’ before ‘offset’
         76 |   explicit read_out_of_bound(uint64_t offset);
            |                             ~        ^~~~~~~
            |                                      )
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/src/exception.cpp:50:1: error: no declaration matches ‘LIEF::read_out_of_bound::read_out_of_bound(uint64_t, uint64_t)’
         50 | read_out_of_bound::read_out_of_bound(uint64_t offset, uint64_t size) : LIEF::exception("") {
            | ^~~~~~~~~~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note: candidates are: ‘LIEF::read_out_of_bound::read_out_of_bound(LIEF::read_out_of_bound&&)’
         71 | class LIEF_API read_out_of_bound : public exception {
            |                ^~~~~~~~~~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const LIEF::read_out_of_bound&)’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound()’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const LIEF::exception&) [inherited from LIEF::exception]’
         73 |   using exception::exception;
            |                    ^~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(std::string) [inherited from LIEF::exception]’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const char*) [inherited from LIEF::exception]’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note: ‘class LIEF::read_out_of_bound’ defined here
         71 | class LIEF_API read_out_of_bound : public exception {
            |                ^~~~~~~~~~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/src/exception.cpp:58:1: error: no declaration matches ‘LIEF::read_out_of_bound::read_out_of_bound(uint64_t)’
         58 | read_out_of_bound::read_out_of_bound(uint64_t offset) : LIEF::exception("") {
            | ^~~~~~~~~~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note: candidates are: ‘LIEF::read_out_of_bound::read_out_of_bound(LIEF::read_out_of_bound&&)’
         71 | class LIEF_API read_out_of_bound : public exception {
            |                ^~~~~~~~~~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const LIEF::read_out_of_bound&)’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound()’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const LIEF::exception&) [inherited from LIEF::exception]’
         73 |   using exception::exception;
            |                    ^~~~~~~~~
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(std::string) [inherited from LIEF::exception]’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:73:20: note:                 ‘LIEF::read_out_of_bound::read_out_of_bound(const char*) [inherited from LIEF::exception]’
      /tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/include/LIEF/exception.hpp:71:16: note: ‘class LIEF::read_out_of_bound’ defined here
         71 | class LIEF_API read_out_of_bound : public exception {
            |                ^~~~~~~~~~~~~~~~~
      make[3]: *** [CMakeFiles/LIB_LIEF.dir/build.make:138: CMakeFiles/LIB_LIEF.dir/src/exception.cpp.o] Error 1
      make[2]: *** [CMakeFiles/Makefile2:411: CMakeFiles/LIB_LIEF.dir/all] Error 2
      make[1]: *** [CMakeFiles/Makefile2:472: api/python/CMakeFiles/pyLIEF.dir/rule] Error 2
      make: *** [Makefile:306: pyLIEF] Error 2
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/setup.py", line 484, in <module>
          setup(
        File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
                 ^^^^^^^^^^^^^^^^^^
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in run_command
          super().run_command(command)
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 368, in run
          self.run_command("build")
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in run_command
          super().run_command(command)
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in run_command
          super().run_command(command)
        File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/setup.py", line 98, in run
          self.build_extension(ext)
        File "/tmp/pip-install-7qn33k2v/lief_6bdd83b5549c4790bcdd6deb34543315/setup.py", line 308, in build_extension
          subprocess.check_call(['make', '-j', str(jobs), targets['python_bindings']], cwd=self.build_temp, env=env)
        File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
          raise CalledProcessError(retcode, cmd)
      subprocess.CalledProcessError: Command '['make', '-j', '1', 'pyLIEF']' returned non-zero exit status 2.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for lief
  Running setup.py clean for lief
Failed to build lief
ERROR: Could not build wheels for lief, which is required to install pyproject.toml-based projects

Is this related to kavanoz? Can you install lief on itself ?

This should be fixed with https://github.com/eybisi/kavanoz/commit/e0b495f2ee20da4cc7a12e165e607684ed8075ac . I've bumped lief version to latest, you can uninstall/install kavanoz to see changes.

authors: eybisi ruchna

repo: eybisi/kavanoz


text:
V2Ray-core 版本

现在客户端是要求 V2Ray-core 版本4.13。
如果我现在使用无效，是否可以断定是服务端版本太低呢？
请问是否有哪家服务商是支持这个高版本的 V2Ray-core ，可以的话麻烦告知

那这就属于 v2ray-core 的问题了：https://github.com/v2ray/v2ray-core/issues

source: gharchive/issue

authors: TomatoLeee eycorsican

repo: eycorsican/kitsunebi-android

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 AUR Repo is down

In 1f76417, AUR Repo (https://aur.eyenx.ch/x86_64/eyenx.db.tar.gz) was down:

HTTP code: 404
Response time: 403 ms

Resolved: AUR Repo is back up in f91c123.

repo: eyenx/upptime


text:
Fixing namespace + localName built-ins

The log:namespace and log:localName were not working correctly for some namespaces (imo):
Before:
<http://somewhere.org/test/localName> log:namespace "http://somewhere.org/test/" .
<http://somewhere.org/test/localName> log:localName "localName" .

<http://somewhere.org/test#localName> log:namespace "http://somewhere.org/" . #!
<http://somewhere.org/test#localName> log:localName "test#localName" . #!

<urn:example.org:localName> log:namespace fail #!!
<urn:example.org:localName> log:localName fail #!!

Now
<http://somewhere.org/test/localName> log:namespace "http://somewhere.org/test/" .
<http://somewhere.org/test/localName> log:localName "localName" .

<http://somewhere.org/test#localName> log:namespace "http://somewhere.org/test#" .
<http://somewhere.org/test#localName> log:localName "localName" .

<urn:example.org:localName> log:namespace "urn:example.org:"
<urn:example.org:localName> log:localName "localName"

Thank you very much Patrick!

source: gharchive/pull-request

authors: josd phochste

repo: eyereasoner/eye


text:
feat(executePipe): add issues

Hi, @fabian-hiller!
Here's a proposal I thought for #161, please let me know if there's anything that could be improved. It is worth noticing that I may need a little bit of help with testing result.issues

I think that the code is easier to unterstand if we remove issue and replace it with issues. However, since this is a little more work, I can do it on Sunday.

I have implemented the changes. With the next version it will be possible.

authors: demarchenac fabian-hiller

repo: fabian-hiller/valibot


text:
optimal command to compile from source

What would be the preferred and optimal build command be?
I used:
GO111MODULE=on CGO_ENABLED=0 go build -v -trimpath -buildmode=pie -modcacherw -tags netgo -ldflags="-s -w"

I get a fairly decent binary at 5.1M but for instance I then cannot compress it with UPX.

This repos is relying on goreleaser and and github actions to generate the releases binaries. As far as I know there is no way to use UPX with the current version. I would be happy to be proven wrong :)

I could compress your release with upx 4.02 but not build.

Oh ok, the release process is made by goreleaser. I'm not sure what parameters are used there  exactly, but I will try to figure that out. Context always help, from you other question I understand you are trying to package this as an RPM, which is actually great :)
Will get back to you asap.


text:
Update libraries, move common dependencies versions to project file

Updated Dagger and Runner libraries. I've also moved versions to the gradle.properties file, so it will be easier to update them in the future, as you will only have to change them in one place.

Thanks a lot!

authors: Kistamushken fabioCollini

repo: fabioCollini/DaggerMock

license_source: bigquery


text:
Configuration service provider pull request

Hi Fabian,
First of all I want to say thank you for Symfony components and for Silex - this is a great tools!
This service provider can be used for configure $app['autoloader'] service and for registering other service providers and controller providers with configuration file instead of defining this configuration in code.
Could you please take a look on my code?
Thank you.

you should read https://github.com/fabpot/Silex/wiki/Silex-Philosophy :)
This service provider should likely be distributed as a third party one. Btw, there is already many ones, including some for configuration: https://github.com/fabpot/Silex/wiki/Third-Party-ServiceProviders

Ok, thank you for clarification! I read only docs on silex webpage not on github.
I'll deploy this service provider in my Git repo and add it to composer.

Ok, thank you for clarification! I read only docs on silex webpage not on github.
I'll deploy this service provider in my Git repo and add it to composer.

authors: stephanoff stof

repo: fabpot/Silex

license: mit


text:
Fix markup of the bestpractice admonition

The previous way tried to replicate the behaviour of SensioHTMLTranslator.visit_admonition. However, it wasn't complete, resulting in a very weird style for the (upcoming) platform.sh builds.
I see no reason to not use SensioHTMLTranslator.visit_admonition, after changing it to this, I got the styles correct.
/cc @javiereguiluz Can you maybe verify this change?

I don't understand the changes ... but if you have tested and get the same results :+1:

@javiereguiluz I don't get the same result.
Before:

Best Practice

Use the Symfony Installer to create new Symfony-based projects.

(note: markup is not how it should be (and different from the markup on symfony.com), also 1 closing div too much, resulting in a broken page)
After:

Best Practice

Best Practice

Use the Symfony Installer to create new Symfony-based projects.

(note: markup is now equal to that of symfony.com and works as expected)

Ah, I see this has been removed previously by @xabbuh in order to support using this extension without the SensioHTMLTranslator.
However, as you can see, it creates incorrect markup. We can either improve the current way, or use what was done in this PR, based on the knowledge that the symfony docs will soon have the SensioHTMLTranslator.

I think the best solution depends on how reusable this package should be. When it needed the SensioHTMLTranslator, the best practice directive would not be usable outside of Symfony projects anymore. Probably that's not an issue, but we should be aware of it when making a decision.

This PR should be merged, as some files of the generated documentation (with the make html command of the Symfony docs) are not valid because of double closing
 tags.
After making some tests, this PR solves the issue (in an better way than my #35 PR).

Any updates on this? @fabpot

authors: Crizz0 WouterJ javiereguiluz michaelperrin wouterj xabbuh

repo: fabpot/sphinx-php


text:
Extend support in diff code to see differences in some JSON fields (user data) and in FABNetv4,6Ext properties

@kthare10 please comment if you have additional suggestions.

Fixed in #160

repo: fabric-testbed/InformationModel


text:
Segmentation fault while fetching refcount

In the following code:
template  Referent * cache_get(uint64_t node_target) {
object obj;
auto handle = get(std::to_string(node_target), obj);
if (!handle) {
obj = load(node_target, 0);
}
lock.get_read_lock(node_target);
return (Referent *)obj.target;
}
get is defined as follows:
CacheReadHandle cache::get(CacheKey key, object &obj) const {
auto handle = gcache_->find(key);
if (handle) {
std::memcpy(static_cast<void *>(&obj), handle->getMemory(), sizeof(obj));
}
}
after the return statement in cache_get, the code tries to fetch the refCount_ variable in Refcount.h in the function atomicUpdateValue. The segmentation fault is on line 471.

Basically, as soon as handle goes out of scope, a seg fault happens. Is there a way to release the handle somehow?

I somehow managed to fix this

repo: facebook/CacheLib


text:
Footer links/columns "shift" to the right when navigating through site's "sections" on mobile

Is this a bug report?
Yes.
Have you read the Contributing Guidelines on issues?
Yes.
I proudly contributed to 2 merged PRs recently—:tada:—but for this one I won't be able to directly bring a fix myself as easily (should be easy for a CSS Jedi though), hence this issue.
Environment
Observed on Linux (Linux Mint 18.3 KDE) with Firefox & Chromium browser.
Node 8.9.4 / npm 5.6.0.
Latest (1.0.7) version of Docusaurus at least.
Can also be observed on the Docusaurus public website as well in the docs part (https://docusaurus.io/docs/).
Steps to Reproduce

Have a running Docusaurus instance (e.g. the vanilla example one)
Open a browser and go to the docs part
Minimize browser width to simulate a small smartphone
Scroll down to the bottom of the page to display the footer
With the breadcrumb, select the second section of the docs
Scroll down to the bottom of the page to display the footer
With the breadcrumb, select the third section of the docs
Scroll down to the bottom of the page to display the footer

Expected Behavior
At steps 4, 6 and 8, the footer should display links & columns aligned to the left of the page.
Actual Behavior

For the first section of the docs, step 4 is OK.
Starting from the second section of the docs, step 6 is KO (links & columns are shifted to the right).
For the third section of the docs, step 8 is KO (links & columns are even more shifted to the right).

Seems that after third section, footer links & columns are still "KO" in this sense but are "as shifted as the third section's footer")
Reproducible Demo
One can directly see the the phenomenon by going to these URLs for steps 2, 5 and 7:

step 2
step 5
step 7

Or set up the example project and see it locally:

step 4:

step 5:

step 6:

step 8

See the "shifting"? :wink:

no1illuminati69@gmail.com
On Mar 6, 2018 09:43, cheercroaker notifications@github.com wrote:
Is this a bug report?
Yes.
Have you read the Contributing Guidelines on issueshttps://github.com/facebook/Docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues?
Yes.
I proudly contributed to 2 merged PRs recently—🎉—but for this one I won't be able to directly bring a fix myself as easily (should be easy for a CSS Jedi though), hence this issue.
Environment
Observed on Linux (Linux Mint 18.3 KDE) with Firefox & Chromium browser.
Node 8.9.4 / npm 5.6.0.
Latest (1.0.7) version of Docusaurus at least.
Can also be observed on the Docusaurus public website as well in the docs part (https://docusaurus.io/docs/).
Steps to Reproduce

Have a running Docusaurus instance (e.g. the vanilla example one)
Open a browser and go to the docs part
Minimize browser width to simulate a small smartphone
Scroll down to the bottom of the page to display the footer
With the breadcrumb, select the second section of the docs
Scroll down to the bottom of the page to display the footer
With the breadcrumb, select the third section of the docs
Scroll down to the bottom of the page to display the footer

Expected Behavior
At steps 4, 6 and 8, the footer should display links & columns aligned to the left of the page.
Actual Behavior

For the first section of the docs, step 4 is OK.
Starting from the second section of the docs, step 6 is KO (links & columns are shifted to the right).
For the third section of the docs, step 8 is KO (links & columns are even more shifted to the right).

Seems that after third section, footer links & columns are still "KO" in this sense but are "as shifted as the third section's footer")
Reproducible Demo
One can directly see the the phenomenon by going to these URLs for steps 2, 5 and 7:

step 2https://docusaurus.io/docs/en/installation.html
step 5https://docusaurus.io/docs/en/site-preparation.html
step 7https://docusaurus.io/docs/en/site-creation.html

Or set up the example project and see it locally:

step 4:
[01-docusaurusfirstsectionfooter]https://user-images.githubusercontent.com/18077405/37041493-a65e47ce-215c-11e8-9b9f-dc851b50f380.png

step 5:
[02-docusaurussectionselection]https://user-images.githubusercontent.com/18077405/37041533-b9e6fe58-215c-11e8-81ce-6888cf929f7a.png

step 6:
[03-docusaurussecondsectionfooter]https://user-images.githubusercontent.com/18077405/37041560-c874a628-215c-11e8-9644-1bccdf15d30e.png

step 8
[04-docusaurusthirdsectionfooter]https://user-images.githubusercontent.com/18077405/37041570-cd627b10-215c-11e8-9c64-b8020149dfc6.png

See the "shifting"? 😉
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/Docusaurus/issues/485, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiRESJ3V8rwgCOT9UfL55jnHPmLUu_l_ks5tbq6ogaJpZM4Se7om.

Can I to take up this issue

@ajomadlabs Would love a PR for this. Thank you!

authors: JoelMarcey No1illuminati ajomadlabs cheercroaker

repo: facebook/Docusaurus


text:
Hard to discern point features in Rapid Assist

I have Rapid Assist enabled and chose the address dataset in Alexandria, VA. The selected point feature is highlighted with a yellow dashed circle which is not very distinct next to the yellow address point. Could we:

Choose a different colour to highlight the currently selected feature?
Could we enlarge the selected point to make it easier to see which one is selected OR auto-zoom to the selected point. With auto-zoom the user could zoom out again if desired, but would automatically be taken to a more suitable zoom level after choosing the address.

See image below. It is quite hard to tell which address is selected.

1. Choose a different colour to highlight the currently selected feature?

yeah this is #813 , sort of..
I agree, I'd like to improve the styling of the selection halos.
When we converted from the old svg/d3 renderer, we also lost out on having that pulsing animation - it's something I'd like to reimplement to make things easier to see.

2. Could we enlarge the selected point to make it easier to see which one is selected OR auto-zoom to the selected point. With auto-zoom the user could zoom out again if desired, but would automatically be taken to a more suitable zoom level after choosing the address.

For this, you can also try the Z key to zoom in on whatever is selected - then pressing Z again will zoom back out to where you were before.

Yes this definitely closely related to #813.
The pulsating animation would help big time. I wonder if you could also draw attention to the highlighted feature by lowering the opacity of all other features in the assist layer. If that's not graphically intensive, it'd be a nice visual cue in addition to any colour changes.
Thanks for the Z hotkey tip. I don't think I have used it in Rapid before.

authors: bhousel eneerhut

repo: facebook/Rapid

license: ISC


text:
npx

npx: The term 'npx' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

What version of node/npm do you have installed on your machine? npx has been included in npm since v6+, so maybe you have an older version.

authors: mattvik threepointone

repo: facebook/create-react-app


text:
Bug: URIError: Failed to decode param '//%PUBLIC_URL%/favicon.ico'

I get a console error when I add '//' to the end of my address
React version: 17.0.2
Steps To Reproduce

add '//' to the end of the url

Adress: http://localhost:3000//
Code console error:
GET http://localhost:3000//%PUBLIC_URL%/favicon.ico 400 (Bad Request)
manifest.json:1          GET http://localhost:3000//%PUBLIC_URL%/manifest.json 400 (Bad Request)
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.

@gaearon  Hey, I have tried other tools like Docusaurus, Vue CLI and all have the same problem, not sure if this is a bug or not.
The reason for the error is that accessing // returns index.html in the public directory. Setting wepack-dev-server's static.staticOptions.index to false should avoid this problem.
Wondering if it's possible to set this in react-scripts by default? thx

Fix: if you have github, revert to the last change you did / unistall recent libraries
I updated my mac and this started happening, was killing my brain tbh. Im pretty sure it was bc i installed firebase tools and that messed up something because i updated my mac and maybe smth didnt save by mac time-machine so it was throwing a weird hidden syntax error that was preventing the app to be displayed. I tried fixing all the errors like the guys up top are saying fixing the links etc but brand new shit was popping up and I was like nahh. no way i have to recode Node to fix this shit.
Options: Revert to previous version / uninstall recent installed libraries / Create a new react app and just copy your src folder to the new app
leave a thubs up: )

create-react-app is no more maintained. Suggested to use vite

authors: await-ovo kouayip redpredator8 sanyasappadu


text:
npx create-react-app errors: spawn ENOENT

Describe the bug
Using npx create-react-app causes a "spawn enoent" error that points to my mongoDB folder. This only began after I installed mongoDB.
Did you try recovering your dependencies?
Not relevant, I can't even start a project.
Which terms did you search for in User Guide?
spawn, ENOENT, mongodb
Environment

Using Windows 10, node version 10.16.0.
$ npx create-react-app client
spawn C:\Program Files\MongoDB\Server\4.0\bin ENOENT

Seems I receive the same error using this command as well.
Steps to reproduce

(Write your steps here:)

Install mongoDB
run command 'npx create-react-app client'
receive this error:
$ npx create-react-app client
spawn C:\Program Files\MongoDB\Server\4.0\bin ENOENT

Expected behavior
I should be able to create a react app without issue.
Actual behavior
I'm receiving this error:
$ npx create-react-app --info
spawn C:\Program Files\MongoDB\Server\4.0\bin ENOENT
Reproducible demo
I have no idea how to reproduce this on another machine. I was able to install mongoDB on a separate computer and I don't have this issue. I assume the vast majority of people are able to install mongoDB on their machine without experiencing this issue.

I have no idea why create-react-app would be trying to call C:\Program Files\MongoDB\Server\4.0\bin, so something is really messed up somewhere. Maybe npm cache clean --force?

close ?

authors: Eric-Johnston Maxstgt heyimalex


text:
Add Support for nullishCoalescingOperator

Is your proposal related to a problem?
TypeScript 3.7 released today which includes https://github.com/tc39/proposal-nullish-coalescing
After turning it on with TS, CRA throws a babel error Support for the experimental syntax 'nullishCoalescingOperator' isn't currently enabled (56:22):
Add @babel/plugin-proposal-nullish-coalescing-operator (https://git.io/vb4Se) to the 'plugins' section of your Babel config to enable transformation.
Edit:
Also would like to see Support for the experimental syntax 'optionalChaining' isn't currently enabled (18:17): to be fixed as well
Describe the solution you'd like
Add the babel plugin to CRA since this is now in typescript's stable version. That we it can be used without ejecting.

There have been several PRs and issues opened for this already. You can follow the progress here: #7438.
Even though this is now supported in TypeScript and Babel, it's not fully supported by other tools like ESLint and Prettier.

Sorry about that. I promise I searched for it but githubs search leaves much to be desired...

authors: iansu zackify


text:
Merge pull request #1 from facebook/master

update 1

Motivation
(Write your motivation here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
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.)

?

authors: DONRUBAYET slorber

repo: facebook/docusaurus


text:
Fix incorrect link to docs in README.md

Link was pointing to a 404 page.

Thanks for putting up a PR to update this error in the docs! We pulled in #1802 instead, so closing this one :)

authors: niveditc pataar

repo: facebook/draft-js


text:
esproposal.class_instance_fields does not seem to work

.flowconfig
[options]
esproposal.class_instance_fields=ignore
esproposal.class_static_fields=ignore

flow giving output:
src/main/javascript/common/upload/fileInput.js:18
 18:     handleClick = (e:Event) => {
         ^^^^^^^^^^^ Unexpected identifier

ignore and warn seem to give the same result.
Using version 0.18.1 on osx

Do you, by chance, have a field declaration just before this one that doesn't end in a semicolon?
(Field declarations have to end in semicolons to remain unambiguous)

Yes indeed I had a field declaration just before without semicolon (as I thought they were optional).
Thank you.

authors: jeffmo torarnek

repo: facebook/flow


text:
Disabling Promise global type

Is there a way to disable global types in flow? I'm using the bluebird module for promises and its iflow-bluebird module for types. Per this issue I discovered that if I do the following:
import Promise from 'bluebird'

The Promise type conflicts with the global flow type. Is there a way to disable flow from using its own Promise type so my locally imported Promise type will not conflict?

@calebmer See this comment:
import BluebirdPromise from 'bluebird';
declare var Promise: BluebirdPromise;

This approach did not work globally for me, and it really shouldn't be necessary. Ideally flow would provide a way to disable globals (or detect if Promise is in scope and thus overrides the global configuration).

It isn't desirable to "disable" the global Promise type because built-in APIs will give you an instance of the built-in Promise regardless of what Promise library you use.
Consider fetch or async functions.
However, we should interoperate with Promise libraries. For example, we should support chaining Bluebird promises with native ones. We can do that by declaring an interface that describes Promises/A+ which would be compatible with the built-in Promise class and any other conforming Promise library.
We should definitely have an issue for the above, but I'm not sure if that captures your issue. Can you be more specific about the errors you're running into?

Merging with #2171

authors: STRML avikchaudhuri calebmer samwgoldman


text:
gen-flow-files generates union type declaration that confuses importer

Here is a simplified code example:
// @flow

export const requestAnimationFrame = typeof window.webkitRequestAnimationFrame === 'function' === 'function'
  ? (callback:(timestamp:number) => void):number => window.webkitRequestAnimationFrame(callback)
  : (callback:(timestamp:number) => void):number => window.RequestAnimationFrame(callback)

This generates following
// @flow

declare export var requestAnimationFrame: (callback: (timestamp: number) => void) => number | (callback: (timestamp: number) => void) => number;

Generated output also seems to confuse code importing it:
// @flow

import {requestAnimationFrame} from "./raf"

let id:number = requestAnimationFrame(() => {})

Which will produce these errors:
user.js:5
  5: let id:number = requestAnimationFrame(() => {})
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function call
  5: let id:number = requestAnimationFrame(() => {})
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ function type. This type is incompatible with
  5: let id:number = requestAnimationFrame(() => {})
            ^^^^^^ number

Found 1 error

Thanks! The bug is pretty simple here, codegen.ml should wrap each arm in parens when emitting intersection and unions. Currently it uses gen_separated_list, which doesn't have that behavior.

gen-flow-files is removed. A replacement is coming soon.

authors: Gozala TrySound samwgoldman


text:
Support higher kinded type

example :
interface Mappable<M<A>>  {
  map<B>(func: (a:A) => B): M<B>;
}

Here's another code dump that aligns more closely with the syntax we have now.
type Monoid<T> = {
  zero: T;
  append: (a: T, b: T) => T;
}

// These are fine
var sumMonoid: Monoid<number> = {
  zero: 0,
  append: (a, b) => a + b
}

var productMonoid: Monoid<number> = {
  zero: 1,
  append: (a, b) => a * b
}

// The type variable T can't be free, but this
// formulation is valid for any type T.
var arrayMonoid: Monoid<Array<T>> = {
  zero: [],
  append: (a, b) => a.concat(b)
}

// We should be able to use any type, not just
// built-ins.
type Transformation<T> = (x: T) => T;
var transformationMonoid: Monoid<Transformation<T>> = {
  zero: (x) => x,
  append: (f, g) => (x) => f(g(x))
}

Note that these "type classes" are a bit more cumbersome to use than they would be in Haskell, where the compiler will thread the dictionaries around for you, or Scala where the implicit rules will do the same.

Oddball edge case.  Given I:
interface I {
  method(): string;
  static sMethod(): string;
}

should the following an error out?
class A implements I {
  method: void => string;
  static sMethod: void => string;
  constructor() {
    this.method = function () { return "peep"; }
  }
}
A.sMethod = function () { return "peep"; }

@popham I'm not sure how that is related to HKT. Can you elaborate?

Off-topic.  Apologies.  (I'm imagineering what interface should look like, and this is the only lead I could find.  I just went to delete the prior, but then I saw your response.)

Looking for this feature as well.

Higher order types should also include recursive types. This would help in cases like Lodash's flatten.
type Flattenable<A> = Array<A> | Array<Flattenable<A>>;

declare function flatten<T>(list: Flattenable<T>): Array<T>;

@popham Your example isn't really related to HKT either. Also, recursive types should work. I think your type definition is wrong. You probably want something like this:
type Flattenable<A> = Array<A | Flattenable<A>>;
var foo: Flattenable<string> = ['a', ['a'], [['a']]]; // OK

Also, for what it's worth. Using the existential types that are on master right now, my previous example with 2 character substitutions type checks:
/* @flow */

type Monoid<T> = {
  zero: T;
  append: (a: T, b: T) => T;
}

// These are fine
var sumMonoid: Monoid<number> = {
  zero: 0,
  append: (a, b) => a + b
}

var productMonoid: Monoid<number> = {
  zero: 1,
  append: (a, b) => a * b
}

var arrayMonoid: Monoid<Array<*>> = {
  zero: [],
  append: (a, b) => a.concat(b)
}

type Transformation<T> = (x: T) => T;
var transformationMonoid: Monoid<Transformation<*>> = {
  zero: (x) => x,
  append: (f, g) => (x) => f(g(x))
}

// HKT use case
function concat<T>(array: Array<T>, monoid: Monoid<T>): T {
  return array.reduce(monoid.append, monoid.zero);
}

var ex1: number = concat([1, 2, 3], sumMonoid);
var ex2: number = concat([1, 2, 3], productMonoid);
var ex3: Array<number> = concat([[1, 2], [3, 4]], arrayMonoid);
var ex4: Transformation<number> = concat([(x) => x + 1, (x) => x - 1], transformationMonoid);

Thank you for reporting this issue and appreciate your patience. We've  notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

Any update regarding this feature? There was no response within 30 days yet this feature request is not yet closed. I'd also like to see this become reality.

Here's a (hacky) way to implement HKT: https://github.com/gcanti/flow-static-land

Thanks, @gcanti -- that seems like a reasonable workaround for now.
Just to follow up with something semi-official: There's a chance we may get to this at some point, but it's not on the near-term horizon for the core team. As we've done so far with this, we'll leave this issue open to track the request for if/when this surfaces the priority queue.

Is there still no way to do this "officially"?

@jeffmo In the year+ since your last comment, how has thinking on this by the core team changed if at all?

From what I can tell, higher-kinded types are actually supported in Flow, though they are encoded using the simple-kinded function type and the utility type $Call for type-level application. In fact, some of the utility types of Flow are using this encoding, such as the $ObjMap<T, F> type, where F is higher-kinded. Maybe this isn't official though, because I don't see it explicitly mentioned in the documentation, or I might be missing something.
The encoding is as follows:
the kind Type -> Type is encoded as the type Function
the type-level function λA.F(A) is encoded as the type <A>(A) => F(...A...)
the type-level application F T is encoded as the type $Call<F, T>
the conversion-rule is not fully supported, so some times you have to explicitly use an intermediate cast to any to view an expression of type $Call<F, T> as having the type of the β-redex F[T], so for example if we have type F = <A>(A) => Array<A>, an expression of type $Call<F, string> is not immediately typeable as Array<string>.
Not sure if there is a way to encode kinds like (Type -> Type) -> Type (e.g. for monads), maybe by using a more restricted type than Function to specify the higher kinds.

@astampoulis this is @hallettj's encoding I'm currently using in fp-ts
type Either<L, R> = { type: 'Left', value: L } | { type: 'Right', value: R }

type EitherF = <L, R>(x: [L, R]) => Either<L, R>
type ArrayF = <A>(x: [A]) => Array<A>

type ArrOfStrings = $Call<ArrayF, [string]>
type EitherOfStringNumber = $Call<EitherF, [string, number]>

;([1]: ArrOfStrings) // number. This type is incompatible with string
;({ type: 'Right', value: 'foo' }: EitherOfStringNumber) // string. This type is incompatible with number

Any updates here? It's so hard to use Flow for functional programming without this. :(

authors: Jacse PinkaminaDianePie astampoulis facebook-github-bot-2 fdecampredon gcanti impinball jasonkuhrt jeffmo pmlt popham rockymadden samwgoldman


text:
[RFC] flow-lib: JS interfaces for Flow APIs

This is a first-pass on an idea for an npm package, called flow-lib, that allows JS tooling consumers to interface easily with Flow APIs. Pending more experimentation, my hope is that this can become a stable way for JS tooling to integrate with Flow via a simple, well-versioned npm dependency.
To start out I've added JS APIs for flow check-contents, flow ast, and Flow type definitions for the AST. I also intend to add type-at-pos-like APIs as well (all of the tooling needs I can imagine right now need this more than anything else) -- but before that I need to find a good way to represent types that isn't coupled too tightly with Flow implementation details. I'm still working on this and will update when I have something more here.
NOTE: This is only an RFC while I look into more concrete use cases. I am putting this out for discussion, but I don't necessarily expect to merge it until we see it prove useful or promising for some specific tooling needs

Exciting! It'd be really awesome if we could access the inferred types from the AST as well, although possibly out of scope for this PR.

@phpnode: Yea, having a way to normatively access and refer to types (inferred and otherwise) is something I'd like to solve before moving landing this idea.
Also worth noting that this is something I intend to hack on in my free time for now, so I don't expect this to move too quickly (unless we can make a strong case for it being important) -- but I am still casually playing around here.

I would love to use well-written JS-interfaces for Flow in the JS scripts I write too! Definitely much better than my current solution of exec'ing Flow!

Since the cli is quite deep-water with secret commands (AFAIK I only found out about certain features through either flow --help, reading vim-flow or other hidden resources) ... I would like to know which commands are actually missing to make this feature complete?

@facebook-github-bot import

Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.

@ryyppy: Awesome! Let's get this landed then we can add commands on top from there.
The obvious top-priority commands after the ones added in this PR would be flow status (results of typechecking), flow coverage, flow type-at-pos, flow get-def... There are more, but we can add them as needed I guess.

Okay let's do this!

authors: facebook-github-bot-0 gabelevi jeffmo phpnode ryyppy


text:
Plot is separated from toolbar?

I have a weird visualization problem where the plot is displayed on the right side of the toolbar instead beneath it. Anyone knows why or how to fix it?

I have the same problem with you, and have you fixed it now?

I experience the same issue after updating jupyter notebook

I debugged this a bit. Attached is a screenshot of how the bk-canvas-wrapper children are laid out in Chrome. The other children of bk-canvas-wrapper have position: absolute with left: 0, but the canvas has position:absolute (from the CSS), without a left: setting. I'm not a CSS expert, and it's not clear to me if this makes sense as a configuration.
Several CSS changes I tried targeting the bk-canvas canvas fix the issue:

adding left: 0;
adding position: relative; (or inherit)

I'm not sure where this should be fixed, or what combinations of configurations produce the problem. (I installed iTorch / Torch yesterday, with Jupyter 4.3.0 on OSX [via anaconda], fwiw.)
As a workaround, if you find your jupyter installation's custom.css (for me it's lib/python2.7/site-packages/notebook/static/custom/custom.css within an anaconda tree), you can update it to add a rule like this:
 .bk-canvas-wrapper canvas.bk-canvas {
   left: 0;
 }

Graphing using bokeh via the python (2.7) kernel works on my jupyter installation, without the custom CSS rule. The canvas gets left: 0; from a rule in bokeh-0.12.5.min.css.

authors: TyGuo edpizzi ksemianov shayo

repo: facebook/iTorch


text:
mergeDeep behavior inconsistent across different versions

I am getting inconsistent results for mergeDeep.
I am using version 4.0.0-rc.9
let obj1 = Immutable.fromJS({ x: [{ a: 1 }] });
let obj2 = Immutable.fromJS({ x: [{ b: 1 }] });

let result = obj1.mergeDeep(obj2);

// expected result { x: [{ a: 1, b: 1 }] }
// produced result { x: [{ a: 1 }, { b: 1 }] }

if i downgrade to verison 3.8.2 it seems to behave correctly. Has the desired behavior changed or is there some kind of bug with version 4.0.0-rc.9?

@habibtariq That is the expected result. Concatenating lists on deep merge is a breaking change included in v4.
This issue should be closed.

authors: habibtariq lukaswelinder

repo: facebook/immutable-js


text:
False positives

Hi,
I tried to analyze https://github.com/firehol/netdata with infer.
I get 2 false positives:
src/url.c:50: error: MEMORY_LEAK
   memory dynamically allocated to buf by call to mallocz() at line 49, column 17 is not reachable after line 50, column 5
  48.
  49.       char *buf = mallocz(size);
  50. >     return url_decode_r(buf, str, size);
  51.   }
  52.
  53.

src/web_client.c:1920: error: NULL_DEREFERENCE
  pointer 0 could be null and is dereferenced by call to gettimeofday() at line 1920, column 5
  1918.
  1919.       // start timing us
  1920. >     gettimeofday(&w->tv_in, NULL);
  1921.
  1922.       if(unlikely(!hash_api)) {
  1923.

Summary of the reports

       MEMORY_LEAK: 1
  NULL_DEREFERENCE: 1

The first is false positive, since url_decode_r() returns the supplied buf: https://github.com/firehol/netdata/blob/2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f/src/url.c#L76
The second is false positive, since tv_in is a static member of w: https://github.com/firehol/netdata/blob/2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f/src/web_client.h#L72 and w is passed properly to this function.

Both of these warnings have disappeared with infer 0.15.0 and netdata version 2fffb74cab6bfe7d6b8e212afcfaf8f74113a07f.

authors: jvillard ktsaou

repo: facebook/infer


text:
Jest resolver does not follow symbolic links

I have the following tree:
.
├── app_modules
│   ├── actions
│   ├── components
│   ├── __tests__
│   ├── constants
│   ├── libs
│   ├── models
│   ├── shared -> ../../../../../js_lib/shared/
│   │   ├── components
│   │   │   └── __tests__
│   │   ├── libs
│   │   └── utils
│   └── utils
└── src
    └── main

When running npm test all tests inside the symbolic link shared are not executed by the client.
Thank you.

This is a deliberate design decision because symlinks always cause trouble. I recommend you to use the moduleNameMapper config option. See facebook.github.io/jest/docs/api.html#content

Does moduleNameMapper resolve the testPathDirs?
My issue is with test files not modules, when I run npm test from my rootDir, any test inside the symbolic link are not found:
.
├── app_modules
│   ├── actions
│   ├── components
│   ├── __tests__
│   ├── constants
│   ├── libs
│   ├── models
│   ├── shared -> ../../../../../js_lib/shared/
│   │   ├── components
│   │   │   └── __tests__  <- jest does not run tests in this folder
│   │   ├── libs
│   │   └── utils
│   └── utils
└── src
    └── main

Adding the folder <rootDir>/app_modules/shared/components/__tests__ in the testPathDirs works fine, maybe something like testPathDirMapper?
Thanks.

I recommend trying to use jest@test which is gonna be the next release of Jest.

I'll try it, thank you so much.

Do you mean npm i jest@latest? or npm i jest@test?

I understand that you don't like symlinks, however I don't follow why you would block using them within the tool.  Anyone that doesn't want to use symlinks doesn't have to, they just don't create them,  but for you to disallow symlinks within the test finder makes our setup very hard to work with, especially since all the other tools we use are completely happy with symlinks.
Our setup looks like
+- ProjectA
     +- node_modules
     +- shared(symlink)--+
+- shared               <+ <+
+- ProjectB                 |
     +- node_modules        |
     +- shared(symlink)-----

All the code shared between the 2 projects is in the real shared folder and both projects use a symlink to place that folder into both projects.
ProjectA is the main website, ProjectB is the admin website, so the shared folder is used extensively by both projects.  What I've shifted to is:
+- ProjectA
     +- node_modules
     +- shared(symlink)-----+
+- ProjectB                 |
     +- node_modules        |
     +- shared         <----+

Which will work, but is less obvious than the original layout.  All because one tool (jest) has decided that symlinks "always cause trouble", something I would debate is false.  So while it might be by design, does that design actually make sense in light of the rest of the toolchain which works just fine with symlinks?

I think everything is working just fine in Jest, except for locating test files, which imho is a reasonable trade-of for what we are doing inside of jest's haste map.

So, even though all the other tools work with symlinks, since you don't like symlinks, its perfectly acceptable for jest to explicitly ignore symlinks?  Is that what you are saying?

Feel free to send us a pull request that fixes Jest to fit your use case. If it doesn't make Jest harder to maintain and works within our constraints, I'm happy to accept it.
Personally, the only reason I get to work on Jest at Facebook is because I'm solving Facebook's problems related to JavaScript testing. This is not a problem for us so I'm not able to justify working on it myself.

@cpojer Do you think it would be easier to implement symlink support for node_modules only (instead of supporting any arbitrary symlink)?

no, I think it would make sense to support them overall. I think if you change the node crawler to support them behind a flag (that would disable watchman as well), I wouldn't stop you from adding it to the codebase, granted it is well written and tested etc.

Created a PR to solve this #4387, I'd appreciate some feedback over there.

After lots of experimenting and digging through docs, it appears one can use the roots configuration option to specify multiple directories, which are included when looking for __mocks__.  This solves my problem wonderfully.

@davesidious thanks for sharing your solution. Works on our project too.

@difelice I'm glad I could help!

Yeah, I'm working with a monorepo too, and lack of symlink support is a real pain.

authors: aleclarson cpojer davesidious difelice majelbstoat mark0978 viddo

repo: facebook/jest


text:
Jest hangs on invalid expectation(s)

🐛 Bug Report
If my there is at least one expectation in my unit test that is not fulfilled at test time, the entire test suite "hangs" instead of reporting a failed ("red") test.
(On contrary, If all my expectations are fulfilled at test time, the tests does not seem to hang.)
To Reproduce
The following test code is an example.
describe(`Demo`, () => {
  it(`Should Fail, not Hang`, () => {
    expect(1).toEqual(2);
  });
});

Run Jest from Git Bash/CMD, observe the following output:
$ yarn test
yarn run v1.6.0
(node:3316) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
$ jest -i

 RUNS  __tests__/3-1-single-array-multiple-stacks.spec.ts

Software/Package Versions:
jest: 22.4.3
ts-jest: 22.4.5

$ node --version
v10.0.0

$ npm --version
6.0.0

$ npm --version
6.0.0

$ tsc --version
Version 2.8.3

Expected behavior
The test should be reported as failing.
Run npx envinfo --preset jest
$ npx envinfo --preset jest
npx: installed 1 in 5.897s

  System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i5-3317U CPU @ 1.70GHz
  Binaries:
    Yarn: 1.6.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.0.0 - ~\AppData\Roaming\npm\npm.CMD

This seems configuration specific, can you push a repo?

@rickhanlonii you can take a look at it here. (Please notice the branch -- repro).
Thanks for quick turnaround.

@another-guy hm, this did not hang for me:

@rickhanlonii thank you for looking into it. I should try to rollback from Node.js 10.0.0 to whatever I had day before yesterday and re-check. Things seemed to be working jest a few days ago.

It hangs when I use Node 10

It does not hang on node 10.1.0, though. Maaaaybe related to https://github.com/nodejs/node/pull/20266?

@SimenB I confirm the upgrade resolved the issue. Thanks a ton!
$ node --version
v10.1.0

$ yarn test
yarn run v1.6.0
(node:2392) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use
the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
$ jest -i
(node:4552) ExperimentalWarning: The fs.promises API is experimental
(node:4552) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use
the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
 FAIL  __tests__\3-1-single-array-multiple-stacks.spec.ts
  Demo
    × Should Fail, not Hang (13ms)

  ● Demo › Should Fail, not Hang

    expect(received).toEqual(expected)

    Expected value to equal:
      2
    Received:
      1

      1 | describe(`Demo`, () => {
      2 |   it(`Should Fail, not Hang`, () => {
    > 3 |     expect(1).toEqual(2);
      4 |   });
      5 | });
      6 |

      at Object.it (__tests__/3-1-single-array-multiple-stacks.spec.ts:3:15)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        2.523s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

authors: SimenB another-guy rickhanlonii


text:
add a testTZ/testTimeZone config value like testURL but for setting a timezone tests should run in

#8497  🚀 Feature Proposal
Motivation
Enforcing a consistent timezone in an easily configurable way just like setting a base URL.
Example
// in a jest.config.js
module.exports = {
  setupFilesAfterEnv: './setup.js',
  testTZ: 'America/Denver',
  testURL: 'http://localhost',
}

Pitch
Sometimes even with mocks you run into problems of you and another dev in another timezone producing different results because of your computer timezones. You could do something like TZ=foo jest as a workaround and put that in your package.json as well but then if you have a Windows user doing dev you now need something like cross-env to work around the variables.

As of Node 13+ you can set process.env.TZ in your globalSetup function (NB I haven't tried this on Windows).

authors: ide wldcordeiro


text:
Invalid plan for CROSS JOIN UNNEST

EXPLAIN
  SELECT
    y
  FROM (
      (VALUES array[1, 2], array[3])
    UNION ALL
      (VALUES array[4, 5], array[6])
  ) t(x)
  CROSS JOIN
    UNNEST(x) u(y)
GROUP BY y

AddExchanges.visitUnnest does not exist. But it should exist and should check the preferred properties and filter the newly generated output symbol out.
Query 20151110_185357_00006_f7iy7 failed: index (0) must be less than size (0)
java.lang.IndexOutOfBoundsException: index (0) must be less than size (0)
	at com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:310)
	at com.google.common.base.Preconditions.checkElementIndex(Preconditions.java:292)
	at com.google.common.collect.RegularImmutableList.get(RegularImmutableList.java:65)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitUnion(AddExchanges.java:945)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitUnion(AddExchanges.java:173)
	at com.facebook.presto.sql.planner.plan.UnionNode.accept(UnionNode.java:133)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.planChild(AddExchanges.java:970)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitPlan(AddExchanges.java:200)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitPlan(AddExchanges.java:173)
	at com.facebook.presto.sql.planner.plan.PlanVisitor.visitUnnest(PlanVisitor.java:135)
	at com.facebook.presto.sql.planner.plan.UnnestNode.accept(UnnestNode.java:105)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.planChild(AddExchanges.java:970)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitAggregation(AddExchanges.java:246)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitAggregation(AddExchanges.java:173)
	at com.facebook.presto.sql.planner.plan.AggregationNode.accept(AggregationNode.java:180)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.planChild(AddExchanges.java:970)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitOutput(AddExchanges.java:222)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges$Rewriter.visitOutput(AddExchanges.java:173)
	at com.facebook.presto.sql.planner.plan.OutputNode.accept(OutputNode.java:81)
	at com.facebook.presto.sql.planner.optimizations.AddExchanges.optimize(AddExchanges.java:135)
	at com.facebook.presto.sql.planner.LogicalPlanner.plan(LogicalPlanner.java:101)
	at com.facebook.presto.sql.analyzer.QueryExplainer.getLogicalPlan(QueryExplainer.java:134)
	at com.facebook.presto.sql.analyzer.QueryExplainer.getPlan(QueryExplainer.java:91)
	at com.facebook.presto.sql.analyzer.StatementAnalyzer.getQueryPlan(StatementAnalyzer.java:711)
	at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitExplain(StatementAnalyzer.java:692)
	at com.facebook.presto.sql.analyzer.StatementAnalyzer.visitExplain(StatementAnalyzer.java:208)
	at com.facebook.presto.sql.tree.Explain.accept(Explain.java:54)
	at com.facebook.presto.sql.tree.AstVisitor.process(AstVisitor.java:22)
	at com.facebook.presto.sql.analyzer.Analyzer.analyze(Analyzer.java:60)
	at com.facebook.presto.execution.SqlQueryExecution.doAnalyzeQuery(SqlQueryExecution.java:259)
	at com.facebook.presto.execution.SqlQueryExecution.analyzeQuery(SqlQueryExecution.java:245)
	at com.facebook.presto.execution.SqlQueryExecution.start(SqlQueryExecution.java:209)
	at com.facebook.presto.execution.QueuedExecution.lambda$start$170(QueuedExecution.java:68)
	at com.facebook.presto.execution.QueuedExecution$$Lambda$399/184162826.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

I'll be working on this

@erichwang Is this the bug you fixed recently?

this is already fixed.

authors: erichwang haozhun yangyangyyy

repo: facebook/presto


text:
Remove skip dependency check for rpm

With air.check.skip-dependency enabled, the
maven-dependency-plugin's unpack goal was being skipped. So mvn install
-P rpmbuild failed since the unpacked presto-server artifacts were
missing.
Testing: mvn clean install and mvn clean install -P rpmbuild

Merged, thanks!

authors: anusudarsan martint


text:
SAMSUNG s6 keyboard without decimal point

Description
[FILL THIS OUT: Explain what you did, what you expected to happen, and what actually happens.]
with SAMSUNG s6 TextInput and keyboardType is numeric the decimal point don't see in the keyboard
Additional Information

React Native version: 0.38
Platform: Android SAMSUNG S6
Operating System: MacOS
Dev tools: [FILL THIS OUT: MacOS

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. 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!

authors: hramos my-love

repo: facebook/react-native


text:
client is busy with a request

Set data to view using DeviceEventEmitter.addListener by binding native mic volume level.
<Text style={styles.instructions}>
          Mic Level {this.state.micLevel}
        </Text>

DeviceEventEmitter.addListener('onMicLevelChange', (data) => {
            this.setState({micLevel:data});
        });

but I get error as follows,

How to solve this?

Not sure if this is react-native issue or a third-party library.
It also seems disrespectful to reopen your closed issue https://github.com/facebook/react-native/issues/14098 line by line, even though @hramos had closed it with a reasonable comment.

It looks like your description is missing some necessary information. 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.

Looks like this error message comes from code that lives outside React Native: https://github.com/aws/aws-sdk-android/blob/master/aws-android-sdk-lex/src/main/java/com/amazonaws/mobileconnectors/lex/interactionkit/InteractionClient.java#L818
Closing this issue for that reason, if you find that this is a bug with React Native itself then please open another issue.

authors: RiyasMeeran hey99xx ide


text:
Linking.getInitialURL() url value is null

Is this a bug report?
Yes

Have you read the Contributing Guidelines?
Yes
Environment

react-native -v: 2.0.1
node -v: 8.4.0
npm -v: 4.6.1

Then, specify:

Target Platform: Android

Development Operating System: MacOs Sierra

Build tools: Application created using create-react-native-app and then detached with support of Expo SDK

Steps to Reproduce

(Write your steps here:)

Create application using create-react-native-app
Detach application with: npm run eject (keep support of Expo SDK)
Update AndroidManifest.xml with respective deep links filters inside MainActivity

<intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="https"
              android:host="www.mydomain.com"
              android:pathPrefix="/" />
        <data android:scheme="https"
              android:host="www.mydomain.com" />
</intent-filter>

Update activity declaration with android:launchMode="singleTask"
Update application component to load url on componentDidMount:

componentDidMount() {
    Linking.getInitialURL().then((url) => {
      console.log('Inside of the function is: ' + url);
      this._handleOpenURL(url);
    }).catch(err => console.error('An error occurred', err));
}

Find url is always null

Expected Behavior

url variable populated with respective Url application was loaded with
Actual Behavior

Url is null

Experiencing this too with expo. Linking.getInitialURL works for apps created with react-native init though.

Duplicate of #15961 ?

@Minishlink , not really (similar yes, but not a duplicate). My issue has nothing similar to closing application with back button. For me it just never works at all. Regardless of the way app was killed or never started since installation...

I'm experiencing the same thing since updating from RN 0.46.4 to 0.48.4, it used to work fine before that.
Note: I'm using wix/react-native-navigation

Same issue

Any updates on this?

Solved it! I'll explain what the problem for us was, if anyone is facing the same issue as we did.
We had a custom activity called "SplashActivity" where we had added the
<intent-filter>
    <action android:name="android.intent.action.VIEW" />
    ...

In our SplashActivity.java we started the MainActivity like this:
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    Intent intent = new Intent(this, MainActivity.class);
    startActivity(intent);
    finish();
}

For RN to pick up the url from getInitialURL(), we need to pass the data and action to our MainActivity. So basically we just passed the required information to our MainActivity (in SplashActivity.java):
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    Uri data = null;
    String action = null;
    Intent currentIntent = getIntent();
    if (currentIntent != null) {
        Uri intentData = currentIntent.getData();
        if (intentData != null) {
            data = intentData;
        }

        // Get action as well.
        action = currentIntent.getAction();
    }

    Intent intent = new Intent(this, MainActivity.class);
    // Pass data and action (if available).
    if (data != null) {
        intent.setData(data);
    }
    if (action != null) {
        intent.setAction(action);
    }
    startActivity(intent);
    finish();
}

(don't forget to import android.content.Intent; and import android.net.Uri;)
This solved it for us.

I am getting null value too but on iOS.

authors: ArkadyB AuraIV Minishlink gvillenave harrycheung henebb sercand


text:
iOS 13 and above EXC_BAD_ACCESS KERN_INVALID_ADDRESS acebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_deletefacebook::react::RAMBundleRegistry >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >)

This started happening after iOS 13 was release. I started seeing a lot of crashes in productions with this in my fabric logs.
Crashed: com.apple.root.user-interactive-qos 0  member_mobile_update_prod      0x100172910 facebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 414720 1  member_mobile_update_prod      0x100172bec facebook::react::Instance::loadScriptFromString(std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, bool) + 415452 2  member_mobile_update_prod      0x1000fe1ec __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke + 4305887724 3  member_mobile_update_prod      0x100120148 facebook::react::tryAndReturnError(std::__1::function<void ()> const&) + 76856 4  member_mobile_update_prod      0x1000f8474 -[RCTCxxBridge _tryAndHandleError:] + 4305863796 5  member_mobile_update_prod      0x1000fdee8 -[RCTCxxBridge executeApplicationScript:url:async:] + 4305886952 6  member_mobile_update_prod      0x1000fdcdc -[RCTCxxBridge enqueueApplicationScript:url:onComplete:] + 4305886428 7  member_mobile_update_prod      0x1000fba20 -[RCTCxxBridge executeSourceCode:sync:] + 4305877536 8  member_mobile_update_prod      0x1000f927c __21-[RCTCxxBridge start]_block_invoke_2 + 4305867388 9  libdispatch.dylib              0x18f28fbb0 _dispatch_call_block_and_release + 32 10 (Missing)                      0x3d3a84818f291000 (Missing) 11 (Missing)                      0x0 (Missing) 12 (Missing)                      0x0 (Missing) 13 (Missing)                      0x177bf7018f2f6a00 (Missing) 14 (Missing)                      0x0 (Missing)
React Native version:
React Native Environment Info:
System:
  OS: macOS 10.14.6
  CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Memory: 33.30 MB / 16.00 GB
  Shell: 3.2.57 - /bin/bash
Binaries:
  Node: 10.8.0 - ~/.nvm/versions/node/v10.8.0/bin/node
  Yarn: 1.13.0 - ~/.nvm/versions/node/v10.8.0/bin/yarn
  npm: 6.10.2 - ~/.nvm/versions/node/v10.8.0/bin/npm
  Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
  iOS SDK:
    Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
IDEs:
  Android Studio: 3.3 AI-182.5107.16.33.5264788
  Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
npmPackages:
  react: 16.8.3 => 16.8.3
  react-native: 0.59.10 => 0.59.10
npmGlobalPackages:
  react-native-cli: 2.0.1

Steps To Reproduce

I am not able to reproduce this but similar issue was found in 0.59.5 in iOS so we upgraded to 0.59.10 thinking it will fix the issue but it is still happening in production.

I cannot updated to latest RN because of Android X changes.

I have same issue on react-native 0.61.2 on iOS 13

Can confirm, the same issue with 0.61.2

same issue with 0.59.9

iOS 13.2 fixes this issue

iOS 13.2 fixes this issue

Seems not work for my case. still crash with same reason on ios 13.2 with rn 0.59.9

It looks like you are using an older version of React Native. Please update to the latest release, v0.61 and verify if the issue still exists.

Just tested with rn 0.61.3. Still face the same problem in production only

@nikechanhk Try react-native 0.61.3. I'm on it and iOS 13.2. App looks good, don't receive any crashes anymore in crash reports

@nikechanhk Try react-native 0.61.3. I'm on it and iOS 13.2. App looks good, don't receive any crashes anymore in crash reports

using 0.61.3 already. still crash with same reason

It seems iphone 11 family have higher opportunity rate hit this issue.

@oleksandr-dziuban @nikechanhk  - we're experiencing a highly similar issue and we're on RN 0.61.4 - we get it both on iOS 12 and 13.
These are the logs:
EXC_BAD_ACCESS Attempted to dereference garbage pointer 0xe1eb70b2b0c0.
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:61:14 loadApplication
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:95:5 loadScriptFromString
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1336:29 __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke
    /Applications/Xcode_11.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/functional:1799:16 facebook::react::tryAndReturnError(std::__1::function<void ()> const&)
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:276:20 -[RCTCxxBridge _tryAndHandleError:]
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1319:3 -[RCTCxxBridge executeApplicationScript:url:async:]
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1299:3 -[RCTCxxBridge enqueueApplicationScript:url:onComplete:]
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:915:5 -[RCTCxxBridge executeSourceCode:sync:]
    /Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:390:7 __21-[RCTCxxBridge start]_block_invoke_2
    /usr/lib/system/libdispatch.dylib __dispatch_call_block_and_release
    /usr/lib/system/libdispatch.dylib __dispatch_client_callout
    /usr/lib/system/libdispatch.dylib __dispatch_root_queue_drain
    /usr/lib/system/libdispatch.dylib __dispatch_worker_thread2
    /usr/lib/system/libsystem_pthread.dylib __pthread_wqthread

The error was reported from this thread:
/Applications/Xcode_11.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/memory:3934:56facebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >)
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:95:5loadScriptFromString
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:95:5loadScriptFromString
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1336:29__51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke
/Applications/Xcode_11.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/functional:1799:16facebook::react::tryAndReturnError(std::__1::function<void ()> const&)
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:276:20-[RCTCxxBridge _tryAndHandleError:]
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1319:3-[RCTCxxBridge executeApplicationScript:url:async:]
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1299:3-[RCTCxxBridge enqueueApplicationScript:url:onComplete:]
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:915:5-[RCTCxxBridge executeSourceCode:sync:]
/Users/runner/runners/2.160.0/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:390:7__21-[RCTCxxBridge start]_block_invoke_2
/usr/lib/system/libdispatch.dylib__dispatch_call_block_and_release
/usr/lib/system/libdispatch.dylib__dispatch_client_callout
/usr/lib/system/libdispatch.dylib__dispatch_root_queue_drain
/usr/lib/system/libdispatch.dylib__dispatch_worker_thread2
/usr/lib/system/libsystem_pthread.dylib__pthread_wqthread

still having the same issue with 13.2 iOS. Was anyone able to reproduce this on a simulator?

@kennym does it crash always on load?

@nidongara yes, the crash always immediately after app load.

@kennym for me it happens 1 out out 20 times. I am not able to reproduce this in my simulator or test devices.

@nidongara it only happens for us in release mode

I tried release mode but it doesn't crash. @kennym Did you guys figure out a work around?

@nidongara we have not.

Also reported in the latest version, 0.61.5
https://github.com/facebook/react-native/issues/27363

@nidongara Would you try editing the issue description to indicate a current version of React Native, based on the reports in comments? Here's the instructions the bot gave (they're hidden behind a fold):

The "Resolution: Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

It looks like nobody at Facebook has noticed this issue -- I suspect they completely ignore issues when they have that label attached.

I met the same issue:
Crashed: com.apple.root.user-interactive-qos
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00003b57d32db480

Crashed: com.apple.root.user-interactive-qos
0  Money24H                       0x102ca10e8 facebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 61 (Instance.cpp:61)
1  Money24H                       0x102ca149c facebook::react::Instance::loadScriptFromString(std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, bool) + 1421 (string:1421)
2  Money24H                       0x102c10568 __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke + 1421 (string:1421)
3  Money24H                       0x102c14b30 facebook::react::tryAndReturnError(std::__1::function<void ()> const&) + 141168 (RCTCxxUtils.mm:141168)
4  Money24H                       0x102c0a7d0 -[RCTCxxBridge _tryAndHandleError:] + 280 (RCTCxxBridge.mm:280)
5  Money24H                       0x102c10264 -[RCTCxxBridge executeApplicationScript:url:async:] + 1336 (RCTCxxBridge.mm:1336)
6  Money24H                       0x102c10058 -[RCTCxxBridge enqueueApplicationScript:url:onComplete:] + 1292 (RCTCxxBridge.mm:1292)
7  Money24H                       0x102c0dd2c -[RCTCxxBridge executeSourceCode:sync:] + 915 (RCTCxxBridge.mm:915)
8  Money24H                       0x102c0b5d8 __21-[RCTCxxBridge start]_block_invoke_2 + 396 (RCTCxxBridge.mm:396)
9  libdispatch.dylib              0x18eaf4a38 _dispatch_call_block_and_release + 24
10 libdispatch.dylib              0x18eaf57d4 _dispatch_client_callout + 16
11 libdispatch.dylib              0x18ead8afc _dispatch_root_queue_drain + 636
12 libdispatch.dylib              0x18ead9248 _dispatch_worker_thread2 + 116
13 libsystem_pthread.dylib        0x18ecd51b4 _pthread_wqthread + 464
14 libsystem_pthread.dylib        0x18ecd7cd4 start_wqthread + 4

react-native info output:
System:
    OS: macOS Mojave 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 143.97 MB / 8.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.6.0 - ~/.nvm/versions/node/v12.6.0/bin/node
    Yarn: 1.10.1 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v12.6.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 25, 26, 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: ^0.60.3 => 0.60.6
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-pushdy: 0.0.11
    react-native-swift-cli: 2.3.0

same issue +1, And the number has risen dramatically in the last week

same issue with rn version 0.59.5

At this point it's no longer helpful to add more reports of seeing the issue on RN v0.59. I think it's no longer helpful to report seeing it even on RN v0.61, now that v0.62 is out.
What would be very helpful is a report for v0.62, the latest version. (Or better yet, the v0.63 release candidate!)
If you're looking at this thread because you're seeing this issue, and your app is using v0.62 (or later): please add a comment with details like @luatnd's https://github.com/facebook/react-native/issues/26985#issuecomment-596986763 :smile:
Until then the developers of React Native will effectively assume the issue was fixed in v0.62, and ignore it to focus on the many other things on their to-do list. That's what, as I read it, the label "Needs: Verify on Latest Version" means.
And if you're reading this in the future, and someone has already reported it on v0.62 and a newer release is out (but this thread doesn't show a fix yet): same thing applies, just increment all the version numbers in this comment.

I met the same issue:
Crashed: com.apple.root.user-interactive-qos
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x00003b57d32db480

Crashed: com.apple.root.user-interactive-qos
0  Money24H                       0x102ca10e8 facebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 61 (Instance.cpp:61)
1  Money24H                       0x102ca149c facebook::react::Instance::loadScriptFromString(std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, bool) + 1421 (string:1421)
2  Money24H                       0x102c10568 __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke + 1421 (string:1421)
3  Money24H                       0x102c14b30 facebook::react::tryAndReturnError(std::__1::function<void ()> const&) + 141168 (RCTCxxUtils.mm:141168)
4  Money24H                       0x102c0a7d0 -[RCTCxxBridge _tryAndHandleError:] + 280 (RCTCxxBridge.mm:280)
5  Money24H                       0x102c10264 -[RCTCxxBridge executeApplicationScript:url:async:] + 1336 (RCTCxxBridge.mm:1336)
6  Money24H                       0x102c10058 -[RCTCxxBridge enqueueApplicationScript:url:onComplete:] + 1292 (RCTCxxBridge.mm:1292)
7  Money24H                       0x102c0dd2c -[RCTCxxBridge executeSourceCode:sync:] + 915 (RCTCxxBridge.mm:915)
8  Money24H                       0x102c0b5d8 __21-[RCTCxxBridge start]_block_invoke_2 + 396 (RCTCxxBridge.mm:396)
9  libdispatch.dylib              0x18eaf4a38 _dispatch_call_block_and_release + 24
10 libdispatch.dylib              0x18eaf57d4 _dispatch_client_callout + 16
11 libdispatch.dylib              0x18ead8afc _dispatch_root_queue_drain + 636
12 libdispatch.dylib              0x18ead9248 _dispatch_worker_thread2 + 116
13 libsystem_pthread.dylib        0x18ecd51b4 _pthread_wqthread + 464
14 libsystem_pthread.dylib        0x18ecd7cd4 start_wqthread + 4

react-native info output:
System:
    OS: macOS Mojave 10.14.4
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Memory: 143.97 MB / 8.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.6.0 - ~/.nvm/versions/node/v12.6.0/bin/node
    Yarn: 1.10.1 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v12.6.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 23, 25, 26, 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.3/11C29 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: ^0.60.3 => 0.60.6
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native-pushdy: 0.0.11
    react-native-swift-cli: 2.3.0

I'm really having a problem.
react-native info output:
System:
    OS: macOS 10.15.4
    CPU: (4) x64 Intel(R) Core(TM) i5-5350U CPU @ 1.80GHz
    Memory: 96.43 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.18.0 - ~/.nvm/versions/node/v10.18.0/bin/node
    Yarn: 1.19.1 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v10.18.0/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.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 22, 23, 24, 25, 26, 27, 28, 29
      Build Tools: 27.0.3, 28.0.3, 29.0.2, 30.0.0
      System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7142.36.36.6392135
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_222 - /usr/bin/javac
    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.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found```

Any update on above issue ?, Facing same issue in specific IOS OS version.

I am also having this problem on 62.2

same here with version 62.2

For us, this crash didn't happen until the release where we enabled RAM bundling.

@dougcoburn
Where did you set it up?

Unfortunately I am having this issue in 62.2

Struggle is real! i can still reproduce it with versions 62.2

I was able to get this resolved by rewriting our AppDelagate.m and AppDelagate.h from scratch.
Used the react native upgrade helper to see what those files looks like for a new project, copied that in, and the went though all our native libs that had modified those files (RNN, firebase, and app auth) to set them back up.
By the time that I finished, there was about a 30 line difference. At some point we did a bad upgrade in the past or their initialization had changed, and it finally started crashing when iOS 13 came out.

@aklinker1 do you mind sharing your AppDelegate.m before and after?

Sure thing! This is before and after the fixes for RN 60, but this also worked when we did similar re-writes for RN 62. The main thing to notice is how different the RNN and Firebase setups are.
I would also recommend making these changes in XCode, you'll get errors and warnings in real time.
AppDelegate.m Before

/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 */

#import "AppDelegate.h"

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

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  [FIRApp configure];
  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"HelloWorld"
                                            initialProperties:nil];

  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

  // Fix occasional white screen on startup in release builds
  UIView* launchScreenView = [[[NSBundle mainBundle] loadNibNamed:@"LaunchScreen" owner:self options:nil] objectAtIndex:0];
  launchScreenView.frame = self.window.bounds;
  rootView.loadingView = launchScreenView;

  NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  [ReactNativeNavigation bootstrap:jsCodeLocation launchOptions:launchOptions];
  return YES;
}

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

@end

AppDelegate.m After

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

#import "AppDelegate.h"

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

#import <Firebase.h>
#import <ReactNativeNavigation/ReactNativeNavigation.h>

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
  if ([FIRApp defaultApp] == nil) {
    [FIRApp configure];
  }

  #if DEBUG
  NSURL *jsCodeLocation = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  #else
  NSURL *jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
  #endif
  [ReactNativeNavigation bootstrap:jsCodeLocation launchOptions:launchOptions];

  return YES;
}

@end

AppDelegate.h Before

/**
 * Copyright (c) 2015-present, Facebook, Inc.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

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

@interface AppDelegate : UIResponder <UIApplicationDelegate, RCTBridgeDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

AppDelegate.h After

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

#import <UIKit/UIKit.h>

@interface AppDelegate : UIResponder <UIApplicationDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

I am using "0.61.5" and this issue exists.

I was able to make updates based on the above post from @aklinker1. I've since not seen this crash show up. Our AppDelegate.mm was very similar with a few extra pieces to register for notifications, etc. Seems a bit obvious now as our code and the RNN code was creating a new RCTBridge. The updates have been in the wild for a couple of weeks now, with a much wider distribution and we have not seen this crash.

Here's one situation.
When [CxxBridge start], we call [CxxBridge invalidate] immediately.
-[RCTCxxBridge executeApplicationScript:url:async:] is on dispatch_get_global_queue(QOS_CLASS_USER_INTERACTIVE, 0), but self->_reactInstance.reset(); is on JSThread.
I think the reason is reactInstance->loadApplication called when reactInstance->reset.

Any fixes?
I have the same problem on production, but can't reproduce crash on my devices

any update on this?

@asymptotik Do you have anyidea for fix those issue
[RCTCxxBridge enqueueApplicationScript:url:onComplete:] + 1487 (RCTCxxBridge.mm:1487)
0x6e13ec -[RCTCxxBridge executeSourceCode:sync:] + 1080 (RCTCxxBridge.mm:1080)
0x6dea4c __21-[RCTCxxBridge start]_block_invoke_2 + 508 (RCTCxxBridge.mm:508)

Are folks still running into this? Seeing crash reports related to this on 0.71.1

This issue should not be closed, because there's no reason to believe it has been fixed.
The thing that's needed in order to make progress on the issue is a way to reproduce it. If anyone discovers a way to reproduce this issue, please post it — that would be a very helpful contribution.
Until there's a repro, it's unlikely anyone will fix the issue. But as long as the bug exists, it's better to have the issue thread remain open. Otherwise the result will just be that it splinters across a bunch of newly-filed issue threads as people continue running into it, and that doesn't do anyone any good.

authors: SchneiderOr XuNeal aklinker1 apklinker asafda asymptotik bemaverick djs66256 dougcoburn gnprice iagoSLima johnnyrwest kennym lklepner luatnd mydylan nidongara nikechanhk oleksandr-dziuban radhakrishnant2s rajeshsahaninmg rostislav-simonik sahilpandya seuzxh xwartz