Extractor - namedValues & loggers name template issue

Got latest repo content - used Extractor to get master template - namedValues & loggers contain \\ before template name:

Also when specifying the linkedTemplatesBaseUrl parameter from the command line - a URL now needs to end with '/' otherwise deployment is going to fail.

Hello @sakowiczm,
Will try to look at it in a few days.

@sakowiczm sorry for such a delay.
I have refactored master-template-extractor in #677, so the issue disappeared by iteself.

Regarding the linkedTemplatesBaseUrl - I didn't get your questions\bug-report. Is it happening at ARM-deployment or during resource-kit execution? In any case I would be happy, if you could create a separate issue for that trouble - it will be easier for us to fix things one by one (take advantage of github template to fill in all important information).
Thanks!


Configure awaits

ConfigureAwaits in library to prevent blocking

Hi @benaadams, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@benaadams, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;


Icon request: Code icons

Again, too many to fit in the title. This is also for specific types of code files so here they are below:

HTML file - wikiglyph-file-code-html
CSS file - wikiglyph-file-code-css
JavaScript file - wikiglyph-file-code-js
Python file - wikiglyph-file-code-python
PHP file - wikiglyph-file-code-php
Ruby file - wikiglyph-file-code-ruby
SQL file - wikiglyph-file-code-sql

+1

WikiFont has been deprecated (for a while) in favor of OOjs UI icons, closing.


Bluetooth: Audio: add babblesim test for testing removal of source from listeners by a third party

Is your enhancement proposal related to a problem? Please describe.
Issue #78166 mentions a possibility for the CAP broadcast recpetion stop not properly handling removal of a source from listeners by a third party. Although the implementation (presumably) does handle this situation, we need to confirm that this is indeed the case by adding a babblesim test.
Describe the solution you'd like
Add a babblesim test with at least 2 listeners, that start listening to a broadcast source.
Stop one of the listeners from listening
Run the broadcast reception stop procedure on both listeners; this should succeed
Describe alternatives you've considered
N/A
Additional context
N/A

It does actually not need to be a 3rd party; this also applies to cases where the scan delegator itself modifies the state during the procedure (either actively, or if it loses the PA or BIG sync).


How to restore weights of model from zoo as trainable or how to train custom model with object detection script

Hello
I'm trying to add some new outs to ssd mobilenet v2 taken from model zoo. How to restore graph and variables data to train my additional layers and fine tune mobilenet for better future extracting.
In my tries i used tf.Saver and simple import_meta_graph and restore.
Or push me to right way with using TFObjectDetection API for this task

@VladBlat ,
Please refer the links 1 and 2 and let us know if it helps,thanks!

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

Hello, I didn't find some useful info about this issue at links which u
gave. Restore variables as trainable possible using object detection Api. U
can close topic. Good luck!
вт, 8 окт. 2019 г., 15:38 Alfred Sorten Wolf<EMAIL_ADDRESS>
It has been 15 days with no activity and the awaiting response label was
assigned. Is this still an issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/32690?email_source=notifications&email_token=AKLIRM46MDZSAQBOS7E2T3TQNR5LRA5CNFSM4IYYUQZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAT7N3I#issuecomment-539490029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKLIRM5A6ZVRVSJLKTG76DDQNR5LRANCNFSM4IYYUQZA
.

Closing since the issue is resolved.Thanks!

Closing since the issue is resolved.Thanks!


Switch

Add right click option on Case to add break; Add break whenever Case is added. Can be deleted if not desired. Allow option on switch to add "default" case.

you don't need break! please explain. its internally fully different handled.
default: ok, np

or you want stop the whole switch chain, i guess.

yes just typical use. keep from falling through to next case. then you need
default case for "else"

ok, implemented:

mini update and IDE - reload via F5 is enough.

Perfect!


Request for deployment of your project.

Sir, hope you are well. Can you help me in getting the environment ready of this project since I am facing technical issue.
Hope you understand it and help me out of from this situation

commit


Upgrading Jshint to 2.13

2.13 includes support for optional chaining and other important updates.

@lcundiff Can you update the version as 2.13.4. - which is latest and it removed shell js vulnerability -https://github.com/advisories/GHSA-4rq4-32rv-6wp6

Landed.


Add description popovers to unclear setup labels

Thinking of the new option added for #38...

The only problem I see with this issue would be popovers for mobiles : I had in mind to do this on hover, but you can't hover on mobile, and clicking / tapping already focuses the input field / triggers the action for checkboxes...
Would this issue be covered by #31?

but you can't hover on mobile, and clicking / tapping already focuses the input field / triggers the action for checkboxes...

And it doesn't make sense to toggle the checkbox when tapping the label. Simply removing the label connection to the checkbox allows for hover / tapping to display a popover.


⚠ ClamAV has degraded performance

In 47924b0, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: ClamAV performance has improved in 13c8fb1.


[BUG] Docker images run failed in arm architecture

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s): 2.4.1 or latest in master

Debug logs
No response
Anything else?
The base image java:openjdk-8-jre-alpine can't support arm architecture.

And java in docker hub is deprecated.

We use openjdk:8-jre-alpine maybe better.


Release mashlib as version 1.0.0

Tim wants us to release the next stable version of solid-ui as v1.0.0.

why?


Errors installing Emscripten during setup steps on a Windows machine

Discussed in https://github.com/climateinteractive/SDEverywhere/discussions/358

Originally posted by andyhe958 September 25, 2023
Hi everyone,
I have been trying to run SDEverywhere from command prompt on a Windows machine but came across an error below when installing Emscripten. It suggests Python is not found, but in fact I do have Python 3.11 installed.

Then I went on to disable the app alias for Python as suggested, but I got a second error, which seems to contradict with the first error:

I have since managed to install Emscripten separately, not as part of the SDEverywhere setup steps, and it was installed successfully. I think I would post this here to help others potentially in a similar situation, and to help with further configuration of this tool for Windows.

Discussed in #358
Originally posted by andyhe958 September 25, 2023 Hi everyone,
I have been trying to run SDEverywhere from command prompt on a Windows machine but came across an error below when installing Emscripten. It suggests Python is not found, but in fact I do have Python 3.11 installed.

Then I went on to disable the app alias for Python as suggested, but I got a second error, which seems to contradict with the first error:

I have since managed to install Emscripten separately, not as part of the SDEverywhere setup steps, and it was installed successfully. I think I would post this here to help others potentially in a similar situation, and to help with further configuration of this tool for Windows.

Hello,
I had the same problem using git-bash environment.
I have edited the bashrc with nano
nano ~/.bashrc
to edit it and add at the end of the file this line to add it as alias
alias python3='python'
and saved. After a restart of the git-bash environment it worked.
If you use a windows terminal as CMD, I would create a python3.bat file and edit it to add these lines
@echo off
python %*
then procceed to add the folder of the bat file at the environment PATH variables in Windows settings.

Hi @MSDRL, it looks like from the first screenshots that you have installed Emscripten  separately yourself using Chocolatey, is that correct?  If so, then when you run the npm create command, you should select “no” (i.e. type “n”) when it asks if you would like to install the Emscripten SDK.  In other words, if you already have Emscripten installed, then there’s no point in having the create script do it for you, and you should skip that step (thus avoiding these Windows errors).
Note that we have recently added support for generating pure JavaScript code by default in part to avoid these issues you’re facing with Emscripten on Windows.  New users who simply want to evaluate SDEverywhere should not have to worry about these steps and can get up and running faster when Wasm is not involved.  These changes have not yet been “npm published” but will be published the week of July 8.
To summarize, you can either try my suggestion above about skipping the step, or wait a couple weeks at which point these install issues should go away.

@MSDRL: To follow up on my last comments, the changes I was referring to have been published, so now if you follow the Quick Start instructions, when it asks you if you want to use WebAssembly, select "no" (the default) and it will create a project that uses JavaScript only (no Emscripten or generation of WebAssembly required).
See the August 2024 Updates announcement for more details.
I still plan to smooth out this issue with Emscripten installation on Windows, but for most projects, the generated JavaScript code will be sufficient to get started, and compiling to WebAssembly can always be configured later if needed for faster model execution.


[awslogs] Auto-detect region and set user-agent

This pull request enhances the awslogs logging driver such that it can automatically detect the correct Amazon CloudWatch Logs region when the Docker daemon is running on an Amazon EC2 instance.

Any update here?

Hi @samuelkarp apologies for the delay, it's been busy times, so reviews are taking a bit longer than we want.
ping @calavera I saw you reviewed the original PR, perhaps you can have a look at this?

I minor comment about error handling, otherwise LGTM.

LGTM

@calavera and @moxiegirl, thanks for the review!  I've rebased on master and addressed both your comments.  (I'm seeing some failures in Jenkins, but I believe those to be unrelated to my code.)

@samuelkarp thanks! docs LGTM
ping @moxiegirl

Failures are unrelated, but I'll wait for @moxiegirl to give her :+1: before merging.

LGTM! Thank you @samuelkarp

Thanks!


Kernel Commandline edit

RancherOS Version: (ros os version)
v0.8.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
baremetal
I set for the installation the flag "rancher.password=hello" now i added SSL Keys for Public Authentication, but i dont get rid of the flag state above, where can i edit the kernel command line?

these params can be edited using
sudo system-docker run --rm -it -v /:/host alpine vi /host/boot/global.cfg

If i delete this, will i still be able to login with pub auth?

Is there any default pass i can use? Because when i used your solution, it changed to a random password and i cant login anymore... Thats not nice...

oh, I thought you set up the ssh key for the user!
the rancher.password=asfd option is a kernel boot param, so you can also set it from the Syslinux boot prompt - which is on your console for the first second or so - type any letter to stop it from booting, then type rancheros-v0.8.0 rancher.password=something to set the password to something

I set up the ssh key, but i cant login with it, it just shows after the passphrase input the password input...

odd. perhaps using ssh -vv rancher@yourserver may tell you more

Are you sure you want to continue connecting (yes/no)? yes
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: Videos/ssh keys/private.key ((nil)), explicit
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: Videos/ssh keys/private.key
debug1: key_load_private_type: incorrect passphrase supplied to decrypt private key
Enter passphrase for key 'Videos/ssh keys/private.key':
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: Next authentication method: keyboard-interactive
debug2: userauth_kbdint
debug2: we sent a keyboard-interactive packet, wait for reply
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
Thats the output i get. really weird, btw your fix above didnt work, the password is still not correct

I use rancheros-v0.8.0 rancher.password=something in Syslinux pretty much all the time during development - so that is known to work.
you can also get it to autologin with rancheros-v0.8.0 rancher.autologin=tty1..

So the password line doesnt work at all for me, i try the autologin line now

Okay AutoLogin doesnt work for me either, this becomes really annoying, this is the third time i locked myself out of this OS because of this Public Key SSH Decision.
Is there a real good, dummy safe manual for setup the public key authentication with rancheros? (With adding the key into the cloud config...)?

I think you need to tell us more about what you're actually typing, where, and what type of system you're working with, and how - you're getting failures with things that otherwise seem to work.
my "fastest" way to success is to `sudo ros install -d /dev/sda -f --append "rancheros.autologin=tty1"
but this assumes that you're on a system where your console is tty1.
I am wondering what kind of ssh key you're using - while debugging, I'd go for something simple and common...

Okay, also for installing, i used the "--append rancher.password=hallo" parameter.
Then i created a public and private key for the user rancher and i moved the keys to the correct location.
After that, when i logged in, i had the pub key auth AND the password auth. Then i disabled the password auth. But the password auth parameter in sshd_config gets resetet at every boot.
And now the password for rancher is random and i cant log in, if i use the kernel parameters, the system boots normal and the passwords dont work, what is really weird actually.
Im working on a baremetal server over a iLO Java Console to use the server.
The Server is DL160 G6, has a Harddrive and i installed rancher from an usb Stick.
so when i use the parameters, i press enter, and then the system boots, but the parameters i used, are getting ignored, i can make a gif when that would be helpfull (maybe i press the wrong buttons).
I used the password parameter for installation to access the os, because when i used pub key with the cloud config, nothing worked and i couldnt log in.
At the moment, im thinking about an complete reinstall with the docs.
My steps would be:

boot the os from USB
Create internet connection because there is no DHCP
Create SSH Keys
Upload SSH keys to a temporary host.
Create cloud-config.yml on my laptop with the public key
upload the cloud-config.yml and download it with the server
on the server, install it with the config
after that, everything should work am i right?

With my manual above and this post:
https://forums.rancher.com/t/problems-with-bare-metal-install-in-data-center-specifically-cloud-config-yml/2380/5
i managed to install my server a few minutes ago. Im so happy right now and im thinking about to write an "RancherOS Install for dummies" Guide.
Thank you for your help.

@RaymondSchnyder wrt a guide - do it! I'd be very happy to help you get that done - its incredibility hard for those of us working on the code to know what problems you're having, or why
wanna try out https://gitbooks.com?


Include a paginated renderer as part of the app

Thanks for this great add-on!
For some reason when I download my data in CSV format, it is returned in 2 giant rows, with all items combined on the rows.
Screenshot:
https://www.dropbox.com/s/8aecjorj658om2s/Screenshot 2014-05-22 09.47.49.png
Why is this happening and how do I get it to correctly export the rows?
Thanks,
Lyle

I think it would be a good idea to add the PaginatedCSVRenderer in https://github.com/mjumbewu/django-rest-framework-csv/blob/master/rest_framework_csv/renderers.py and ship it as part of django-rest-framework-csv — so users don't have top copy&paste it from the README to their own application but can just do
from rest_framework_csv.renderers import PaginatedCSVRenderer
should I create a separate issue for that ?

If I have globally setted
'DEFAULT_PAGINATION_CLASS': 'rest_framework.pagination.PageNumberPagination',
for all my JSON rendered endpoints, I can't see anything in my single CSV endpoint. How I can switch off pagination for exactly CSV endpoint?


vtdb.tablet client uses error codes instead of string parsing

@alainjobart @dumbunny
Some clean-up here. I think I'll use a similar structure for the VTGate clients, this was mostly testing my ideas out.
Before making the VTGate client changes, I'll be sure to add test cases to vtgateclientest.

@aaijazi FYI I'm currently making changes in vtgateclienttest and I was planning to add error test cases soon (but haven't yet). Let's coordinate on that to make sure we don't overlap.

@enisoc sounds good. I was planning on starting my changes tomorrow, so we can coordinate in person. (or just let me know when you're starting to make changes)

We want to retire tablet.py, it's the direct vttablet access we don't want to support in python. I guess now that this is done, might as well submit it :)
LGTM

Merging this now that I've made Travis pass (and there might be race conditions with Travis passing / caching). I'll fix forward if anybody has additional comments.


signInWithProvider argument mismatch

I'm getting an argument mismatch on the signInWithProvider function, expected 4, received 2.
I'm using the v3 branch.
The Java code expects 4 arguments (3 + callback/promise).
https://github.com/fullstackreact/react-native-firestack/blob/8db8b5040b90e990816ede8b749e24ca9a486a11/android/src/main/java/io/fullstack/firestack/auth/FirestackAuth.java#L161
But the JS code sends an object as first argument.
https://github.com/fullstackreact/react-native-firestack/blob/8db8b5040b90e990816ede8b749e24ca9a486a11/lib/modules/auth/index.js#L154
The link function seems to be correctly updated:
https://github.com/fullstackreact/react-native-firestack/blob/8db8b5040b90e990816ede8b749e24ca9a486a11/lib/modules/auth/index.js#L137
Changing the code to this seems to work:
signInWithCredential(credential: any): Promise<Object> {
  return promisify('signInWithProvider', FirestackAuth)(credential.provider, credential.token, credential.secret);
}

This fixed it for me too but it should be authToken in the JavaScript and in the Java as that's what it is in iOS. I'll create a pull request


Support management plane specials

break this down

General mgmt feature supported via https://github.com/Azure/autorest.java/pull/460


Narrator Does not Read Node.js Project Properties Select File Button Properly

Steps to Reproduce

Turn on windows narrator
Create a new node console app
Right click on the project in VS and go to properties.
Tab to one of the select file buttons, such as Working Directory or Node.exe Path

Expected
Narrator makes it clear this button is used to select a file for the given setting.
Actual Behavior
Narrator reads:

Button

Not so helpful.

Fixed in Update 3


0.3.0-alpha.13 fails to build on CentOS 7 (GLIBC_2.18 not found)

Hi I've been using the futures 0.3 preview crate for a while now and today I get this error when trying to compile on my CentOS 7 machine. I haven't had any issues prior with both 0.3.0-alpha.12 nor 0.3.0-alpha.13 before today.
Error message below:
error: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/cargo/debug/deps/libproc_macro_hack-76bab84eb11ae1ee.so)
  --> /home/putin/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-select-macro-preview-0.3.0-alpha.13/src/lib.rs:10:5
   |
10 | use proc_macro_hack::proc_macro_hack;
   |     ^^^^^^^^^^^^^^^

error: aborting due to previous error

error: Could not compile `futures-select-macro-preview`.

I'm using the latest nightly (nightly-2019-03-01-x86_64-unknown-linux-gnu) but it doesn't work on nightlies I've used before either. Yum reports that I'm using glibc 2.17-260.el7_6.3.
Given that I haven't had any issues prior - I think this may be a regression. If not, it might be helpful to document the minimum required glibc version. Thanks!

Figured out the issue - didn't realize I had linuxbrew installed on this system. All Cargo generated binaries seemed to depend on linuxbrew's glibc which caused this error.


WordPress.org asking for Composer Install

Hi,
Im starting a new project on which I've installed everything from scratch. After installing Timber (from WordPress.org), im getting the following error:
Fatal error: You have not run "composer install" to download required dependencies for Timber, you can read more on https://github.com/jarednova/timber#installation in /srv/www/idomlive/htdocs/wp-content/plugins/timber-library/timber.php on line 63

Oh composer. Can you provide some server details: let's start with PHP version?

Hi Jared, this is what I get with php -v:
vagrant@vvv:~$ php -v
PHP 5.5.9-1ubuntu4.7 (cli) (built: Mar 16 2015 20:47:39)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
    with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies

ugh, oh well -- thought that might lead us to an easy answer. I've verified on my side with a fresh install that things are working. However, on your end, for some reason the check for the Twig_Autoloader is failing. The only thing I can think of is that some file(s) didn't download or copy correctly. Can you take a screenshot of the file structure from /timber-library down to Twig/lib? Here's what mine (from a comparison fresh test install) looks like for comparison:

Hey Jared,
I think it's safe to assume it is fine on repo. I had other plugin complaining about failed install (it wasn't the case for Timber) and only when you mentioned that possibility I've remembered what happened when I was installing all the plugins.
If I see it happen again i'll reopen this.
Thank you for your help.


jetbrains: add support for plugins on darwin

Description of changes
This change fixes up support for installing plugins with JetBrains IDEs on macOS. Presently on master, this falls with the following:
error: attribute 'mainProgram' missing

       at /nix/store/apa072dsj782n2r23his9y40nm8nkkrm-source/pkgs/applications/editors/jetbrains/plugins/default.nix:84:15:

           83|     stdenv.mkDerivation rec {
           84|       pname = meta.mainProgram + "-with-plugins";
             |               ^
           85|       version = ide.version;

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Thanks for the feedback, @leona-ya. I've applied those suggestions.

One thing that needs to be done, before (from my side) this could be merged: Please squash all commits into one with a commit message like jetbrains: add plugins support for darwin or jetbrains: fix plugin support for darwin.
Also I think the plugin updates (d1fecc3c9d65d55dc81c8aaa217ca9354da084f0, 0af0af96a51c3a444d02bdb198148d62f878fadf and a part of c05db562799477fc45421ce713f3a33b914b9416) shouldn't be included in this PR, as they'll be adressed in #242493 and might cause strange merge conflicts then

Good point, I'd been using this locally while I waited for the original plugins PR to be merged, but that noise isn't necessary in the git changeset. I've squashed this all down to 1 commit for you, let me know how that looks.

pinging @GenericNerdyUsername for review since they initially wrote the plugin support.

Why not add meta.mainProgram to darwin builds?

I'm converting this to a draft PR (as I was suggested in the nixpkgs dev matrix room) until you start responding to questions and mark finished conversations as resolved.

Merge conflict, please rebase.

If there any update on this? Seems to still be broken on darwin

Um, I wonder why I closed the PR instead of rebasing it. I'll see what I can do.


colab cell2 dry run not working

repreoduce

open colab links

run cell 1, all good

run cell 2, error

Hi, could you provide more details about the running error?

!pip install -r requirements.txt # last time someone run is more than a year ago

run cell and vomits:
Building wheels for collected packages: pycocotools
  error: subprocess-exited-with-error

  × Building wheel for pycocotools (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  Building wheel for pycocotools (pyproject.toml) ... error
  ERROR: Failed building wheel for pycocotools
Failed to build pycocotools
ERROR: Could not build wheels for pycocotools, which is required to install pyproject.toml-based projects

Also, I tried Quickstart with the pretrained model, the experience is quite sock sniffing.

The error is caused by the update of Colab.  The pycocotools package is now installed by defaultly now in Colab, so there is no need to install it again.
Additionally, the processing speed is limited by the hardware capabilities of Colab. You can try HiSup on your local device for improved performance.

I apologize for appearing toxic or something, consider me a kid terrified by python environment.🤦


[JavaToolInstallerV0 ] Changed logic of extraction, fix inactivated Clean Destination Directory issue

Task name: JavaToolInstaller
Description:

Naming of extraction directory (each archive extracts into a directory named as 'JAVA_HOME_<archive_name>_<archive_extension>'
No extraction if it's in cache
Refactoring logic, dividing code into methods

Documentation changes required: (Y/N) Yes, #88
Added unit tests: (Y/N) No, will be done in #81
Attached related issue: (Y/N) https://github.com/microsoft/build-task-team/issues/10
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

Test Build Result: Build

After Testing by Canary Scenaries from Canary Build repo, I found some issues with Azure Blob JDK Installation.
These issues were fixed and tested again: here's the results:

Build for Azure Blob
Build for local storage


Run each ruleset in a separate asyncio task

Before the refactoring all events are processed sequentially. A
long running action will block the processing of an event from
another ruleset.
Now each ruleset is running independently in its own asyncio task.
Events from the same ruleset are still processed sequentially.
Resolves: AAP-5471

@benthomasson please review

@bzwei please rebase

@benthomasson rebase is done


Add kwarg julia_cmd to installkernel (to support JupyterHub with containers, etc.)

This PR makes it possible to specify a custom julia command via
installkernel(Julia, julia_cmd="my_custom_julia_start_script")

It also allows passing an array - this should be very helpful to people (like me :-) ) who often run Julia in Linux containers but may be forced (e.g. by using a site-wide JupyterHub) to have Jupyter running outside of the container.
For Docker, running
installkernel(
    "Julia via Docker",
    julia_cmd = [
        "docker", "run", "--rm", "--net=host",
        "--volume=/home/USERNAME/.local/share/jupyter:/home/USERNAME/.local/share/jupyter",
        "some-container", "/opt/julia-1.x/bin/julia"
    ]
)

from within a container instance now works - provided Docker has been set up in a way that supports things like this (e.g. the user is  "USERNAME" both inside and outside). I use Docker in this example because it's well known, though it is not necessarily the right runtime for such use cases (see below).
More and more scientific computing sites now offer JupyterHub instances and also support containers via runtimes like Shifter or Singularity). Like with Docker, calling Julia (or Python, for that matter) becomes a multi-part command (only simpler), e.g. ["shifter", "--image", "myimage", "/opt/julia/bin/julia"]. This typically forces users to manually fiddle with their "kernel.json" files, which is inconvenient.
Having a julia_cmd kwarg (supporting both a simple string and a vectors of strings) should make life easier.

Perhaps it would be nicer to give this as a Cmd? Or at least support that too. You can get out the string array with c.exec.
julia> c = ```
       docker run
           --rm
           --net=host
           --volume=/home/USERNAME/.local/share/jupyter:/home/USERNAME/.local/share/jupyter
           some-container
           /opt/julia-1.x/bin/julia
       ```
`docker run --rm --net=host --volume=/home/USERNAME/.local/share/jupyter:/home/USERNAME/.local/share/jupyter some-container /opt/julia-1.x/bin/julia`

julia> c.exec
7-element Array{String,1}:
 "docker"
 "run"
 "--rm"
 "--net=host"
 "--volume=/home/USERNAME/.local/share/jupyter:/home/USERNAME/.local/share/jupyter"
 "some-container"
 "/opt/julia-1.x/bin/julia"

Perhaps it would be nicer to give this as a Cmd

I thought about that, but I thought it might look inconsistent with the options argument. But if there are no objections in that regard, using a Cmd would of course be more user-friendly.

If we use Cmd, the cleanest solution might be not to support String and AbstractVector{<:AbstractString} as well, but Cmd only.
What would you guys prefer?

I'm inclined to support Cmd only.
Also, probably just call the keyword argument julia rather than julia_cmd.

I thought about that, but I thought it might look inconsistent with the options argument.

Yea, perhaps the options argument should be Cmd too.

@stevengj sounds good

Yea, perhaps the options argument should be Cmd too.

Wouldn't that be abusing Cmd a bit, though? Not having an actual command in front, I mean?

Sorry, lost track of this for a bit. I've implemented the changes now, using julia_cmd::Cmd.

Ok, now tests pass, too. :-)

@fredrikekre, @stevengj , does this look good to you now?

@fredrikekre, @stevengj , gentle bump regarding merge.

Sorry for bumping this again, @stevengj, I know you guys are busy. I have some users who could really use this.

LGTM, but as I commented above I would rather call the keyword julia rather than julia_cmd.

as I commented above I would rather call the keyword julia rather than julia_cmd.

as I commented above I would rather call the keyword julia rather than julia_cmd.

Oops, sorry @stevengj, I overlooked your comment. It's changed to julia now.

Thanks!


Update installation.adoc

This is obsolet because it is already documented in the develop branch, see a64461d7b8285d67b7cdee0f6f3819860b3fecef.


Very big rework coming

I have implemented FusionAuth at auht.castelnuovo.xyz and will begin transferring apps old clients onto that.


calicoctl doesn't give clean error messages.

While trying out the calico-docker demo, I got the following stack traces from the calicoctl executable.
core@core-01 ~ $ sudo ./calicoctl node --ip=<IP_ADDRESS>
Traceback (most recent call last):
  File "<string>", line 820, in <module>
  File "<string>", line 286, in node
  File "/code/build/calicoctl/out00-PYZ.pyz/node.adapter.datastore", line 303, in add_ip_pool
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 269, in write
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 582, in api_execute
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 600, in _handle_server_response
etcd.EtcdException: raft.Server: Not current leader

core@core-01 ~ $ sudo ./calicoctl node --ip=<IP_ADDRESS>
Traceback (most recent call last):
  File "<string>", line 820, in <module>
  File "<string>", line 286, in node
  File "/code/build/calicoctl/out00-PYZ.pyz/node.adapter.datastore", line 303, in add_ip_pool
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 269, in write
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 582, in api_execute
  File "/code/build/calicoctl/out00-PYZ.pyz/etcd.client", line 600, in _handle_server_response
etcd.EtcdException: raft.Server: Not current leader

This was useful for me, but it's probably not what we want our users seeing. Should we write generally cleaner-looking error messages?

Fixed in pull request #113, pending review.
Fix handles:

etcd errors (prints generic is etcd running message)
prints error if container not in calico network with details of why and how to fix
prints error if docker command needs sudo access

Merged in changes from #113.
Closing issue.

Another example;
$ sudo calicoctl reset
Removing all data from data store
$ sudo calicoctl pool add <IP_ADDRESS>/16
$ sudo calicoctl container add container1 <IP_ADDRESS>
Traceback (most recent call last):
  File "<string>", line 1130, in <module>
  File "<string>", line 185, in container_add
  File "/code/build/calicoctl/out00-PYZ.pyz/node.adapter.datastore", line 736, in get_default_next_hops
KeyError: 'BIRD configuration for host <hostname> not found.'

@robbrockbank Is this one you can take a look at?

Another example
+ dist/calicoctl pool add 127.a.0.1
Traceback (most recent call last):
  File "<string>", line 1109, in <module>
  File "<string>", line 1012, in validate_arguments
  File "/code/build/calicoctl/out00-PYZ.pyz/netaddr.ip", line 907, in __init__
  File "/code/build/calicoctl/out00-PYZ.pyz/netaddr.ip", line 774, in parse_ip_network
  File "/code/build/calicoctl/out00-PYZ.pyz/netaddr.strategy.ipv4", line 277, in expand_partial_address
ValueError: invalid literal for int() with base 10: 'a'
+ dist/calicoctl pool add aa:bb::zz

And another - note the error is OK, but it never returns.
sudo ./calicoctl.py node --ip=<IP_ADDRESS>
Error accessing etcd (No more machines in the cluster).  Is etcd running?

^C

^C^C^C

^C^C

Fixed in libnetwork-rebased.


4.1.0 - Update Failed Dialog doesn't have the option to close the dialog

I ran into a scenario where an update failed and the dialog displayed the appropriate info, but the dialog just hangs as if its still trying to do something and doesn't give an option to close. Checked the super.log and the script has already exited.

Do you have the new --display-hide-progress-bar feature enabled?

No I don't have the new --display-hide-progress-bar feature enabled.
I'll try making the change suggested and will report back. Thank you!

We are seeing the same behaviour with both of these notifications:

We actually do not want to display these messages at all. How can we prevent them from being displayed?

I'm aware... it's a known bug and is addressed in the next beta of super.

Fixed in https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta2 that may resolve this behavior.


response.json() hangs when chrome debugging

When using fetch to make a get to an external api, and if debugging in chrome is active, then it never reaches the second "then" until there is an interaction with the UI, such as a tap on the screen, but if debugging is turned off then this problem goes away.
fetch(requestURL)
    .then((res) => res.json())
    .then((resData) => {
        this.setState({
            suggestions: resData.Similar.Results
        });
    })
    .done()

Using React Native 0.22
Only occurs on Android (both Genymotion and on device (5.0))
Using a Mac

cc @martinbigio we were talking about this
Do sourcemaps in redbox work for you on Android when you're connected to the debugger?

Now that you mention it, nope, sourcemaps in redbox are not working when connected to the debugger.

Got the same problem on linux with the v0.22 as well.  Interacting with the debug menu breaks the logjam.
Sourcemaps stop working after a while and I start seeing the transpiled code.  That is happening when this error is occurring.  But the problem also happens after a reboot
From Stackoverflow:  http://stackoverflow.com/questions/36262456/what-could-be-causing-this-slow-fetch-in-react-native
In the following code, the first console.log message prints pretty much instantly.  Then everything just hangs (I'm initially assumed it was waiting for the body of the response to be returned).  The Body of the response is only about 26K, the time waiting seems to be indefinite UNLESS, I shake the phone and interact with the debug menu.  As soon as I interact with the debug menu, the promise resolves and everything moves along as expected.  My interactions with the debug menu can be simple, like hide inspector, show inspector, just takes something to kick the promise resolution into gear and everything is fine.
    fetch(SEARCH_URL, requestBody)
        .then((response) => {console.log(response); return response.json();})
        .then((responseData) => {
            debugger
            ...

Note:
Disconnecting from the debugger and running the code does not exhibit the slowness (and not being connected to the debugger ignores the debugger statements)
And yes, I have rebooted the computer.

@steveluscher you were looking into setTimeout issues. Could this be related?
@cpojer, @skevy have we recently made any change to the Promise implementation?
cc @bestander, @vjeux

I've been seeing ‘setTimeout never fires’ behavior intermittently as well, with timeouts > 0ms. The only clues that I had was that my Genymotion simulator clock and my system clock seem to drift apart over time. I didn't try opening the debug menu when stuck, nor have I noticed this on device yet (I haven't done anything on device in a while). That you've experienced the same behavior on device as you have in Genymotion makes me think it's not going to prove to be clock drift between the host running Chrome and the host running the app.

Takes more than opening the menu, you have to choose something from it, like hide/show inspector.  I'm not using a simulator.

I'm having the same issue on an S4 mini, except I can stop the behaviour by tapping the screen without opening the debug menu.

Got same issue with response.text() and .response.arrayBuffer(), but .response.blob() seems to work fine. Versions are:
react-native-cli: 0.2.0
react-native: 0.22.2
Android 5.1.1

Quick workaround is to add empty timeout execution:
fetch('http://example.com')
	.then(response => {
		setTimeout(() => null, 0);
		return response.text();
	})
	.then(response => {
		console.log(response);
	});

I can confirm just tapping anywhere on the screen does work around this problem.

Do we know when this regression started repro-ing? Do you guys mind sharing which version of react-native you're using? I want to make sure this is not a regression of the current RC.
cc @bestander

It was in a version installed from npm on March 24.  I don't know the version at the moment, but I can look it up tonight.

I have the same problem with 0.22 and iOS on my mac (installed 1 hour ago)

So this may have been introduced on 0.22, so not 0.23 launch blocker though we should fix asap.

This is due to our incomplete XHR2 implementation. Check this code that was added with cbc0e21926594cbe650db34c466b934fda5c13ef.
Please consult the spec before fixing stuff.

Should this be fixed in 0.24? The problem persist for me with 0.24

No, this is in 0.25-rc

Is it fixed in v0.25.0-rc? Because it persists there as well...

Actually the commit is supposed to be in 0.24.1, it has been cherry-picked into the branch https://github.com/facebook/react-native/commits/0.24-stable.
If you still reproduce the bug then the fix does not work.
cc @davidaurelio

yes - I still reproduce the error with 0.24.1 - Am I supposed to to do any changes to my code? I have not changed it since it broke around 0.22?

It seems something is off with the sourcemap, the one from my bundle has multiple sections but it seems that when we parse it we expect to be flat https://github.com/facebook/react-native/blob/master/Libraries/JavaScriptAppEngine/Initialization/SourceMap.js#L1086
The sourcemap I get using the explorer is flat:

But the one I get from my project has sections:

The promise is rejected, it seems that SourceMap does not handle sections, I updated it and got the Stacktrace in the red screen working fine after commenting in parseErrorStack, but this didn't fixed the freezing issue of the Chrome Debugger.
// if (frame.file.indexOf(sourceMap.file) !== -1 ||
//     frame.file.replace('.map', '.bundle').indexOf(
//       sourceMap.file
//     ) !== -1) {
  resolveSourceMaps(sourceMap, frame);
// }

@jrichardlai oh yes, that’s a super old version of the source map library. Using what we have in node_modules should do the trick. PR welcome. Will look into the other issue now.

i have same problem to, i use 0.25.1 and fetch problem not resolve for now. i think fetch is important part to use web service in mobile app and need to fix.
for now i just use version 0.19

Any update on this issue? Possible workarounds besides just tapping on the screen.

react-native-cli: 0.2.0
react-native: 0.25.1
Android: 5.1.1

Looking for an update. I have upgraded to:

react-native-cli: 0.2.0
react-native: 0.26.0
The problem still occured.

Still on 0.27.0

This bug is still happening on 0.27.2 !

Still on 0.28

Still on 0.29.0-rc.0

Hey guys, thanks for pinging and sorry for taking so long.
Looks like it was an error in our fork of fetch polyfill

Will be fixed in 0.30

This got reverted before 0.30 branch cut.
It should be in 0.31 next week.
Can anyone verify if the fix worked?

@bestander should we cherry-pick this to 0.30? https://github.com/facebook/react-native/issues/8586

Considering that 0.30 is just days away from being called stable and that this bug is not very critical, I would just wait for 0.31.
Afterall fetch implementation git bumped from 0.x to 1.x

@bestander - I tested it with 0.30rc and it worked for me.

Still on 0.31

Made some tests more.
When I disabled "dev mode" and remote debug, I don't notice the slow response any more, even without the setTimeout workaround.

0.31 and 0.32 should have latest fetch from whatwg-fetch npm package.
This sorted out the issue for me when I was testing it.
@pbrito, Could you create a sample github project to reproduce the issue with 0.32?

@bestander I can confirm that the problem still exists in RN 0.31. A 50ms server request usually takes 800-2000ms until it's processed from RN with remote debugging enabled. The delay is gone when JS debugging is disabled.
I've also reseted packager et al without success:
watchmen watch-del-all
rm -rf $TMPDIR/react-*
npm cache clean
rm -rf node_modules
npm install
node node_modules/react-native/local-cli/cli.js start --reset-cache

Yes, it still happens in 0.31, can confirm too.

Thanks for providing more info.
I won't be able to look at this in the next few weeks but it will be on my list.
Feel free to help me out and find the reason :)

Maybe a patch to fetch.js that would add a setTimeout if you are chrome-debugging? :)

I had this problem again after I upgraded to 0.31 and I fixed it by using the Fetch.js from 0.30rc.
Here is the code I used to replace the code in Fetch.js (node_modules/react-native/Libraries/Fetch.js)
https://gist.github.com/Thorbenandresen/d5a482863ccc0be5bfc0344340c12367

What solved it for me was making sure any async code is invoked from within a React Component. fetch doesnt seem to work if it is placed outside, and neither does setTimeout

Seems like this has been fixed now so I am closing this issue.

I still have same issue. not on iOS, but on android only ( remote debugging disabled. release build )

@lacker I still experience this issue on both iOS and Android. Contrary to @ataomega and as described in the original issue, it's only a problem for me when remote debugging in Chrome. The setTimeout(() => null, 0); workaround still fixes it. I'm using latest react-native v0.39.0.

@cooperka
I mean the release build. remote debugging is disabled. Works perfect on iOS but on android in first 3-4 minutes its super slow. after few minutes it will work fast.

@ataomega you may have a different issue than the one described here. This issue is specifically when chrome debugging.

Thanks for your reply. But chrome debugging is disabled. Its a release
build (dev === false)
On Tue, Dec 13, 2016, 8:17 PM Kevin Cooper<EMAIL_ADDRESS>wrote:

@ataomega https://github.com/ataomega you may have a different issue
than the one described here. This issue is specifically when chrome
debugging.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-266833532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQD7QY4rNjngiNQTLRQ9l7GTp4WSOC0Pks5rHu9FgaJpZM4H5YHZ
.

@ataomega Yes I understand :) Your issue is probably unrelated to this one. It seems very different from what people here are describing. I'm just letting you know.

Got the same issue with RN 0.35.0

This issue still seems to be occurring in RN 0.36.1.
Confirmed it only happens when debugger is active, and it requires some kind of screen interaction (e.g. click) to get the fetch promise to resolve. The Fetch is originating outside a React component as others have mentioned, and the setTimeout workaround works.

@lacker it seems pretty conclusive, could you re-open this issue please?

Hmmm when I read through it seems inconclusive. It seems like some people have gotten this fixed and some people have not. Maybe there is some way to make it more specific how to repro this? Like having a sample app with a specific set of repro steps that makes it happen?

Hi @lacker, good suggestion. The duplicate issue here has a good explanation of the steps, and I've created a demo repo here that very simply shows the issue. It seems to come down to calling response.json(). Commenting out that single line makes the delay go away. Repro'd using React Native v0.39.2 with no extra dependencies.

Just updated dependencies for my almost "hello world" app and I still get 6 seconds of lag for each request and I need to make 3 sequential ones when the app starts :(

Isnt that the nature of how .then works tho. Im pretty sure it can only get hit once by design.
If it was working chained together it might be against spec on older ecma engines or libs. Im pretty sure angular has it as a singleton. I could be wrong but I had experienced similar issues on angular objects then got down to the issue being a singleton.

I think I encountered the same issue using Firebase and redux-observable. I tried to add a timeout on my Firebase update:
function organizationCreateEpic($action) {
  return $action
    .ofType(UI_ORGANIZATION_CREATE_START)
    .mergeMap((action) => {
      return Observable.fromPromise(database.ref().update(action.payload))
        .timeout(3000, new Error('Timeout'))
        .map(organizationCreateActionCreator)
        .catch(err => {
          console.error('Error', err);
          return Observable.of(organizationCreateActionCreator(err));
        })
    });
}

The error on timeout is never thrown (I can repro a timeout by disabling the wifi on my laptop).
It happens only when debugging in Chrome. Like https://github.com/facebook/react-native/issues/6679#issuecomment-202853656 the timeout error is finally thrown when I tap anywhere after the duration (3 sec).
Pretty weird: it seems like there is a breaking point on the timeout duration:

Below 1090ms, I always get the error
Between 1090 and 1100ms, sometimes I get the error, sometimes not
Above 1100ms, the timeout error is never thrown (until I tap the screen)

Please note that I don't use fetch at all. The issue seems more relative to the Promise implementation (database.ref().update(action.payload) returns a Promise).

react-native 0.39.2
firebase 3.6.3
rxjs 5.0.0-rc.1
redux-observable 0.12.2

Add this issue with RN 0.39.2 on an Android device while remote debugging is on.
As @ncuillery said, I think it's more related to Promise implementation than fetch since I've lot of fetch requests working (and setTimeout() workaround is not working)

@ncuillery Is organizationCreateEpic called from inside a react component? Doing this solved the issue for me

@saberking It can't call it directly, this definition of an epic is part of the redux-observable middleware included in the redux middleware chain.

@ncuillery in that case the best option is just to give up on chrome debug and use react-native log-android

While different from the issue described originally (slowness when the debugger is open), I also experienced the same problem @dvisco and @ataomega describe. Android release mode slowness, which is manifested as:

Start a request. I have it retry if a timeout is hit, so it ends up retrying multiple times.
There are a few independent pending requests to my server (www.dancedeets.com).
Eventually this server resolves/connects, and all pending requests are sent out simultaneously (as judged by the Server's Date header that responds to them)

I am unclear what is causing the pending requests to be delayed. A few observations:

If I jump off my local wifi where this issue is 100% reproducible, the tethering to my cell network correctly allows the requests to be sent and processed immediately.
I removed all the ipv6 AAAA records for my server, leaving just the ipv4 A records, but noticed no change in behavior. Still broken.
The delays only seem to occur for http://www.dancedeets.com. Somehow https://codepush.azurewebsites.net and https://usage.trackjs.com both work fine (maybe https vs http? or maybe something specific to my server dns settings? my www.dancedeets.com server is GAE/GCE configured exactly as Google suggests).
This only occurs for my Android RN build. Android web browser and iOS RN work fine, in the exact same conditions.

The following code is very slow on ios with chrome debug
const response = await fetch('http://example.com')
const data = await response.json();

it takes almost 60 seconds to convert the response to json
this is happening on react native 39

@sibelius place that code inside a component eg. in the constructor , then it should work

this function is called inside a component, isn't that the same?

@sibelius in that case it is something else, sorry i can't help!

chrome version Version 55.0.2883.95 (64-bit)

It might be the size of your payload, or, it might be the XHR isn't
completing due to a bug that has been around way longer than expected.  Try
causing a touch event while you are waiting and you might find it completes
very quickly.
On Tue, Jan 24, 2017 at 8:44 AM, Sibelius Seraphini <
<EMAIL_ADDRESS>wrote:

chrome version Version 55.0.2883.95 (64-bit)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-274805644,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGept6L2vR1WgUKLXNUCrMvonD7iTw_ks5rVgAlgaJpZM4H5YHZ
.

yep, doing a touch event makes it very fast
any reason for a touch fix the issue?

Has something to do with Promise resolution not being checked until an
event loop action.  I found this workaround, reported the bug and left it.
I was only working on a spike and my time was limited.
On Wed, Jan 25, 2017 at 8:53 AM, Sibelius Seraphini <
<EMAIL_ADDRESS>wrote:

yep, doing a touch event makes it very fast
any reason for a touch fix the issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-275112867,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGepmHrWMXuOqdlVCPupl-A7OpDooMaks5rV1P0gaJpZM4H5YHZ
.

is there any issue open for this already?

I think so, but it is about xhr promise resolution instead of json parsing.
On Wed, Jan 25, 2017 at 10:09 AM, Sibelius Seraphini <
<EMAIL_ADDRESS>wrote:

is there any issue open for this already?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-275132398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGeppAQwN0Ke2NdO9GXCeqAiHM1uAw6ks5rV2W2gaJpZM4H5YHZ
.

@ghost could u please reopen this?, as this is still happening on RN39

Still happening for me in 3.10.6

this has always happened for me -- I just click the screen over and over.

it happens on RN41 as well

@mikelambert I'm seeing something very similar.

Android RN build on device.  Everything is operating normally.
Quickly disable and then re-enable wifi connection on the device.
For the next 3-4 minutes all requests from Android RN app will timeout.  I'm watching device network traffic with a proxy and can see other network requests going through successfully from the device.  Web browser, email etc.
After ~3-4 all pending requests from Android RN app will be sent.  Even the ones that were reported as having timed out.
Once pending requests are sent everything is back to normal.

still going on 0.42.0
This workaround still works:
fetch(url).then(response => {   setTimeout(() => null, 0);  // workaround for issue-6679   return response.json(); })

Lol, it actually works -- wish I knew that long ago so many clicks so many clicks...

I think this issue should be re-opened as it hasn't been resolved.

I have the same problem, I send image to my server processed there then send back image as json object.
There is no problem if the size of json object is small, but when my json object is   1,118 kb my app hangs, dunno if this can help to solve this issue. I'm new in Mobile app development, if this notice is not important skip it :)

it still happens on rn44!

it still happens on rn44!
+1

@sibelius because you had opened debug mode

@sibelius  Stop JS Remote Debugging

@zywj I does work without js remote debugging, but I would like to have the debug enabled

Still there in RN 0.43.3
+1 for reopening if this hasn't been fixed...

Still happening for me on 0.44.0
Is this still being investigated?

My RN app run on android always be extremely slow for the first serveral fetch requests.
Finally, I realize the reason is my LAN has turned on IPv6, but in China (it's a great LAN not support ipv6). So it's seems that android wait ipv6 timeout and change to IPv4, then everything back to normal.

Can confirm error still happens in 0.45.1

I can also confirm this behavior is still present in 0.45.1 as well.

Same here. Interestingly, I did not experience this before up to 0.43

I can also also confirm confirm this behavior is still present in 0.45.1 as well as well.

Having the same problem.  setTimeout hack works around the problem.  RN version is 0.45.1

This it's back on RN 0.45.1

@neiker Yep, can confirm!

Having this issue as well.  Very frustrating.

How does one debug React Native apps that fetch JSON? 😭 @lacker can you please re-open as this is again an issue

@danawoodman debug? Well make log lines everywhere to the console And see where iT reaches like for Every line a console.log("1"); And count up And see which logs arent found And you Got the issue where Its stuck. Use above workarounds to fix it. As there is No generaal fix for this issue.

This error still exists RN 45.1

@cablegunmaster yes, what I am saying is that without a hack you cannot troubleshoot your apps since the debugger causes this issue to fail with fetch.

I was also pulling my hair over this. Glad I've found this issue!

Didn't encounter this issue before, but once i upgrade from 0.44.0 to 0.46.0 today it pops up. the response.json() is just stuck, doesn't invoke then() nor catch(). Like some said, the fetch() was called from a utility function helper outside of React component, but is called by a react component.

Encounter this issue sometimes only through React Native versions 0.44, 0.45 & 0.46.

Yay, this appears to be fixed in 0.47 by https://github.com/facebook/react-native/commit/64825389dfb4e01d5b30cd63b0b41937a9bb431d !

Is there a workaround for those of us that are using a stable RN version?

I too had faced same issue while debugging on ios Emulator with react-native version: "0.46.4". But as @mikelambert suggested, upgrading to version "^0.47.0-rc.5" solved this issue

but it still hangs on android devices.

i'm still seeing fetch on android devices being really slow. i'm on 0.49

It's probably not slow, tap the screen and it will go fast.
On Sun, Aug 20, 2017 at 9:52 PM, Charles Lee<EMAIL_ADDRESS>wrote:

i'm still seeing fetch on android devices being really slow. i'm on 0.49
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-323634725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGepnnp5aS-0Xc7a5-5SGyCarECCAvtks5saPDqgaJpZM4H5YHZ
.

of course, why didn't i think of that

Cause it is so unobvious and is such a new bug (no wait, it's more than 2
years old....)
On Sun, Aug 20, 2017 at 9:57 PM, Charles Lee<EMAIL_ADDRESS>wrote:

of course, why didn't i think of that
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-323635295,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGepjJ16GFnf9exbcTSKdN9eCynJEDJks5saPINgaJpZM4H5YHZ
.

Just a reminder @mark0978 and @chug2k , this is fixed in the latest version of RN 0.47.

@mikelamber, nah... Fixed only for ios, android still broken.

@reactjs-bot  I am still following this post as it seems for me just a stupid bug which should be squashed ages ago,  but nobody has the time to do so.

wtf i spent 12 hours trying to adjust my code, wondering why it wont go within a .then statement of a promise only to find out its a freakin bug

Sadly, we get so used to the platform working that when the platform fails
us, we waste a lot of time on it.  And it's fixed in the next release is
beginning to sound like the repeating chorus of song that just won't end.
On Sat, Aug 26, 2017 at 1:04 AM, Penandweb<EMAIL_ADDRESS>wrote:

wtf i spent 12 hours trying to adjust my code, wondering why it wont go
within a .then statement of a promise only to find out its a freakin bug
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-325091421,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGeph4seX9aXKGw2gVUfys4u39iKzs_ks5sb7WEgaJpZM4H5YHZ
.

you can always make your own pull request to address the issue

After my experience with the jest team, no thanks.  Why waste my time to be
told, "I don't want to include a dependency, I'm just going to copy the
code from that dependency code into my project" (I believe the phrase was
"vendor it in").
On Sat, Aug 26, 2017 at 7:58 AM, JasonHenson<EMAIL_ADDRESS>wrote:

you can always make your own pull request to address the issue
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/6679#issuecomment-325124938,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGepgdYGEqDCmtYiUakfnJuPX4lRsdRks5scBaIgaJpZM4H5YHZ
.

wtf i spent 12 hours trying to adjust my code, wondering why it wont go within a .then statement of a promise only to find out its a freakin bug

same here!

@maxim-c @mikelambert , if this is only fixed for iOS, shouldn't this issue still be open for Android devs? Reading the entire issue, it seems prematurely closed by @lacker , am I wrong?

Its not fixed on Android, just some nasty work arounds.

This actually still happens on Android, and when using an emulator even tapping the screen doesn't help..