primordic/IssueDupesLite huggingface dataset:
Repository: fabiolb/fabio

Issue #282: entering a bad route breaks route updates
Created: 2017-05-02T17:14:13Z
Noticed a scenario where entering a route (weight in this case) broke future route updates. Can anything be done to have reject a bad route if not in the correct format? I know the easy answer is: "Dont enter bad routes", but when teams grow, more "safety net" features become necessary.
Here is an example of a route that broke updates:
route weight myapp http://myapp.com/ weight 0.55 tags "gimme_55percent"

Duplicate issue #399: Typo in manual overrides stops Fabio from updating routes
Created: 2017-12-03T23:44:12Z
I noticed pretty weird issue:
If you add route to manual overrides with a typo, Fabio doesn't give you error message when you save it.
This message is appearing in logs:
2017/12/01 05:48:32 [WARN] line 26: syntax error: 'route add' invalid
Also it seems that Fabio stops updating routes since it has a typo in manual overrides. When services go down and come back with a new IP address Fabio keeps pointing on the old one.
Any help with this issue would be appreciated.
Cheers

Closing comment (2017-12-03T23:51:59Z): Unfortunately, this is a known issue and a duplicate of #282. Fabio should probably ignore the bad line and log the syntax error instead of blocking all updates. Neither approach is fully satisfactory but not updating the routing table at all because of a typo has the bigger impact. I'm going to close this as duplicate but please subscribe to #282 for updates.
Duplicate of #282
Repository: fabiolb/fabio

Issue #56: Support custom 404/503 error pages
Created: 2016-02-16T21:22:26Z
Hi again :)
It could be awesome to specify file or/and use consul key,
that will be used as an answer of 404 or 503 pages.
file or key value can be same as HAproxy do:
HTTP/1.0 404 NOK^M
Cache-Control: no-cache^M
Connection: close^M
Content-Type: text/html^M
^M
<html>
...
</html>

Duplicate issue #309: Allow setting custom 404 page
Created: 2017-06-21T14:31:33Z
I am using Fabio with catchall domain and it would be useful if I could show custom page when there is no matching route.

Closing comment (2017-06-21T15:19:55Z): dup of #56 I'll have another look at this.
Repository: fabiolb/fabio

Issue #168: support for adding headers
Created: 2016-09-28T08:42:22Z
Kind of like #110 but for arbitrary headers like HSTS or HPKP, etc.

Duplicate issue #671: Authorization header leaking to the backend.
Created: 2019-07-11T23:02:33Z
We're running into an issue where we have basic auth enabled on a fabio route (fabio doing the auth) ... but then fabio is passing that Authorization header to the backend as well ... and we'd like it to not do that :)
The route in question doesn't have basic auth on it, but other routes for the same domain do. Which means that your browser sends it regardless if fabio requires it for that route path.
For example domain.com requires basic auth, but domain.com/thing does not. However your browser (browsers default to this behaviour since its the same "domain") sends the header to domain.com/thing, which passes it on to the backend.
May be related to #168 which talks about removing arbitrary headers but @leprechau asked me to open a new issue.

Closing comment (2019-07-15T16:25:39Z): @tecnobrat So then this has nothing to do with fabio itself requesting authentication?  In that case yes, this is exactly the same as #168 and cab be closed.  My original understanding was that you were asking fabio to handle authentication because the backend service(s) weren't capable.
I still think there may be a case for preventing responses to fabio issued challenges from reaching the backend.  However, if this is not the issue here and (to my knowledge) hasn't been brought up by anyone else since we added that feature to fabio this issue can be closed.
Repository: fabiolb/fabio

Issue #168: support for adding headers
Created: 2016-09-28T08:42:22Z
Kind of like #110 but for arbitrary headers like HSTS or HPKP, etc.

Duplicate issue #528: ability to remove headers from the request
Created: 2018-08-06T20:24:31Z
Hi, i think it is more feature-request.
I would like to remove some of the custom headers added by my load balancer to not expose their values to the registered services. In my configuration it would be enough to set value of this headers globally. I saw few tickets about "adding headers", so decided to add my usecase. If you think that it is something you would like to add - i can try to do a PR.

Closing comment (2018-08-06T20:30:38Z): There has been quite a bit of discussion around header manipulation.
Most notably #110 and #168 which mention adding and removing headers.  I'm going to close this as a duplicate of #168 as I think that issue covers your use case.
Please feel free to on #168 with this use case.
Repository: fabiolb/fabio

Issue #676: Unable to route to websites
Created: 2019-07-19T22:45:06Z
I have multiple routes in my fabio routing tables with many services and a UI application. I can see fabio is forwarding the request correctly in the case of services but in the case of UI application the request is getting forwarded but all the resources of the web site is not getting downloaded.
Sample routing table

/myservice http://xxxx.xxx.com strip=/myservice
/uiapp http://yyy.yyy.com strip=/uiapp
In the case of uiapp I can see the index.html of the web application is hit bu the resources refered in the file are not getting downloaded.
For example

All the href links are broken.
Any help on this issues is highly appreciated.

Duplicate issue #717: Question: resources (css, js files) by multiple sites
Created: 2019-10-31T14:22:57Z
Hello,
I'm using Fabio as load balancer on my nomad cluster and have following issue, that my resources (css and js files) cannot be loaded correctly. This is how my 2 sites are configured:

urlprefix-/my-first-site strip=/my-first-site
urlprefix-/my-second-site strip=/my-second-site

I added strip because in html pages resources will be accessed i.e. <link href="/main.css"..
Question: is this a "right" approach? I checked documentation but didn't found an example with multiple sites behind fabio. I'm sure that the question is simple, but I don't get how to fix my issue :)

Closing comment (2019-10-31T14:37:49Z): Can be related to #676?
Repository: fabiolb/fabio

Issue #502: UI broken where no internet access.
Created: 2018-05-29T12:51:25Z
Hello, the UI is broken on computers where to there no internet access. Could the jquery, materialize, etc. resources be included in fabio instead of loaded from the internet? Thanks.
Loading failed for the <script> with source “https://code.jquery.com/jquery-3.3.1.min.js”.
routes:7
Loading failed for the <script> with source “https://cdnjs.cloudflare.com/ajax/libs/materialize/0.100.2/js/materialize.min.js”.
routes:10
ReferenceError: $ is not defined[Learn More]

Duplicate issue #642: Remove third-party cookie and script requirements from frontend
Created: 2019-04-16T05:56:02Z
Attempt to use the Fabio frontend with uMatrix enabled.
Ideally, Javascript and cookies would only be required from first-party sources.
Instead we see:
cookie: cloudflare.com
script: cdnjs.cloudflare.com, code.jquery.com

Closing comment (2019-04-16T07:35:38Z): Closing as duplicate of #502.
Repository: fabiolb/fabio

Issue #247: Support for routing based on path and method?
Created: 2017-03-04T16:34:30Z
Is there, or could there be, support routing based on a combination of the path and method?
As we migrate away from some legacy systems we need to just a little bit of routing magic. Right now we use haproxy with consul-template to build the config.

Duplicate issue #333: Routing Based On GET, PUT, POST, and DELETE
Created: 2017-08-11T18:47:36Z
Hi,
This is a feature request for routing traffic based on GET, PUT, POST, and DELETE.
Thanks
I am running Fabio in production and staging env and it works awesome, keep up the good work.

Closing comment (2017-08-11T19:28:42Z): I think this is a duplicate of #247.
I'm glad you like it and that it works for you. I'll do my best.
Repository: fabiolb/fabio

Issue #181: Add HTTPS upstream support
Created: 2016-10-28T01:32:01Z
Hi,
Is there any way to register https:// backends without using tcp+sni, with fabio performing ssl termination on the client side, and talking https to the backends (re-encoding traffic) ?  The reason for this is that frontend certificate is not the same as the ones that are used internally, so plain tcp+sni will not work.
Regards,
Alex

Duplicate issue #241: https support
Created: 2017-02-13T12:58:53Z
Hello
at the moment as far as I know fabio doesn't support calls https as a client - but it is our requirement
Is there any possibility to call service endpoint via https?
we use proto-https consul tag to get to know if it is http or http
Can I get contact to you Frank?
Regards
Daniel

Closing comment (2017-02-13T16:01:36Z): I'll close this as a duplicate of #181
Repository: fabric/fabric

Issue #1556: No way to force disconnect/reconnect
Created: 2017-02-01T06:10:52Z
Consider the following case:
@task
def setup():
    # ... install docker blah blah
   sudo('usermod -aG docker someuser')

@task
def download_images():
    run('docker pull ubuntu')

If you run it via fab setup download_images, you will find that it will fail with the error that the user does not have permission to use docker. Upon retrying with fab download_images, it works perfectly.
Despite searching the documentation, I've not been able to see a "force reconnection with new session".

Duplicate issue #1557: logging out and logging back in again
Created: 2017-02-02T19:55:15Z
After setting permissions e.g. "usermod -aG docker $(whoami)" it is necessary to logout and log back in again for the settings to take effect.
Can this be done using fabric without rebooting?

Closing comment (2017-02-02T19:58:21Z): dup of #1556
Repository: fabric/fabric

Issue #342: cd() and put(use_sudo=True) do not play nice together
Created: 2011-08-19T02:00:52Z
Description
When wrapping a put(x, y, use_sudo=True) call within a with cd(): block, the hidden sudo(mv) call inside put (which moves the file from its temp location to the final destination) is honoring the cd prefix. The mv call uses a relative path in its first argument (I assume because we didn't want to specify an absolute remote temporary location?) and is thus in the wrong directory when it actually runs.
The obvious solution is to use an absolute path for the use_sudo=True temporary location. So either assume the remote system has a /tmp, or (probably better) determine the remote user's home directory as an absolute path, and then use that explicitly instead of implicitly.
Submitted by irc user dsx4ever / Egor M.

Originally submitted by Jeff Forcier (bitprophet) on 2011-04-25 at 09:06pm EDT
Relations

Duplicated by #398: operations.put with use_sudo=True does not work inside "cd" context manager

Duplicate issue #398: operations.put with use_sudo=True does not work inside "cd" context manager
Created: 2011-08-19T02:01:22Z
Description
def config_foo():
with cd("/some/remote"):
put("/path/to/local/foo.xml", "path/foo.xml", use_sudo=True)
Commands to run: config_foo
[ec2-xxxxx.amazonaws.com] Executing task 'config_foo'
[ec2-xxxxx.amazonaws.com] put: /path/to/local/foo.xml -> /some/remote/path/foo.xml
[ec2-xxxxx.amazonaws.com] sudo: sudo -S -p 'sudo password:'  /bin/bash -l -c "cd /some/remote/ && mv "99cb46f647151bc3dbbdf53435c69f372751fca0" "/some/remote/path/foo.xml""
Fatal error: sudo() encountered an error (return code 1) while executing 'mv "99cb46f647151bc3dbbdf53435c69f372751fca0" "/some/remote/path/foo.xml"'
None
Aborting.

Originally submitted by David Arthur (mumrah) on 2011-07-27 at 06:33pm EDT
Relations

Duplicates #342: cd() and put(use_sudo=True) do not play nice together


Closed as Duplicate on 2011-07-27 at 07:16pm EDT

Closing comment (2011-08-19T02:02:16Z): Jeff Forcier (bitprophet) posted:

Sorry, this is a dupe of #342, but thanks for the report!

on 2011-07-27 at 07:16pm EDT
Repository: fabric/fabric

Issue #1968: pre-task ingores hosts and executes on localhost
Created: 2019-04-17T18:15:47Z
tasks which use the pre-task ignore the -H and execute on local host.
fab -H 'somehost' whoami2
using pre-task @task(whoami1) fails when attempting to execute whoami1
with local host context.
fab -H 'somehost' whoami1
task executes on remote host
fab -H 'somehost' whoami3
task whoami1 and whoami3 execute on remote host.
calling whoami1 inside function body.
declared sudo password in fabric.yaml
fabfile.py
from invoke import task

@task
def whoami1(ctx):
    print('task whoami1')
    ctx.run('hostname')
    ctx.run('whoami')
    ctx.sudo('whoami')

@task(whoami1)
def whoami2(ctx):
    print('task whoami2')
    ctx.run('hostname')
    ctx.run('whoami')
    ctx.sudo('whoami')

@task
def whoami3(ctx):
    print('task whoami3')
    whoami1(ctx)
    ctx.run('hostname')
    ctx.run('whoami')
    ctx.sudo('whoami')

Duplicate issue #1954: Regarding pre- and post-task execution 
Created: 2019-03-10T19:28:32Z
Really like the idea of wrapping a task in pre/post flight calls, but the execution objects are passed an Invoke context and not a Fabric connection style context -- which seems to limit somewhat unnecessarily what can be accomplished around a task.
Also as far as I can tell, there isn't any information passed with the context object which would indicate which task was called or the arguments it was called with.
Am I missing something which would help me to enable richer pre/post task behaviors? Thanks.

Closing comment (2019-12-02T12:30:09Z): /duplicate #1968
Repository: fabric/fabric

Issue #1461: Consider bumping Paramiko requirement pin once Paramiko 2.0.x is definitely stable
Created: 2016-04-30T19:35:12Z
We put out 1.10.3 and 1.11.1 with explicit paramiko<2 pinning to prevent peoples' environments from unexpectedly upgrading / breaking, a while back.
Paramiko 2.0 is now out but is fresh, presumably might be some bugs that need ironing out.
It would be nice to allow people to upgrade to Paramiko 2.0 under Fabric 1 if they explicitly want it - however I don't see a way in setuptools/pip to do this

e.g. the extras_require functionality doesn't let you override the same package/version as specified in install_requires, so we can't do pip install fabric[paramiko-2] or anything.
Hopefully there's something else we can do that I am missing, like setup.py CLI parameters - but those are also not a panacea as they do not work with wheels or any other non-sdist installation method
I'd also like to avoid having to make some terrible second PyPI entry / setup.py like fabric-paramiko2 though that is another option.


Given that Paramiko 2 is API compatible with Paramiko 1, we may want to just bump the version pin to paramiko<3 in later Fabric releases, so folks can continue getting bug/security/etc fixes from the Paramiko 2.x line

If we do this, need to remove the Crypto.atfork call in decorators.py (see #1460) and make sure no other PyCrypto baggage remains
This will still always have a chance of breaking for people who can't get the all-in-one Cryptography.io static wheel; they will upgrade Fabric and then it will explode if they lack libffi-dev or openssl-dev. So it'd be entirely sensible to never actually undo this pin, instead having folks use Fabric 2 once it's out.

Duplicate issue #1477: pycrypto is not declared as a dependency
Created: 2016-06-23T09:43:34Z
When running "pip install fabric", pycrypto is not installed :
https://github.com/fabric/fabric/blob/master/setup.py#L32-L35
However, Fabric uses it directly :
https://github.com/fabric/fabric/blob/master/fabric/decorators.py#L9
So ImportError is raised when I try to use Fabric without manually installing pycrypto.
Environment:

Python 2.7.10
Fabric 1.10.2
Paramiko 2.0.1

Closing comment (2016-06-23T21:14:15Z): Related to #1461.
Could swear I saw a ticket or PR about that Crypto import, but I can't find any right now after a brief search. Thanks for surfacing this.
As you noticed, you probably ran into this by using a not-latest Fabric version on install, which was lacking the "Paramiko<2" bit. There's not much we can do to the historical published versions to fix this, obviously :( and the latest versions for the 1.10 and 1.11 lines of course, have the paramiko pin, meaning they shouldn't run into this problem.
So I don't see any good fixes for this, if we added crypto to setup.py it wouldn't do anything that the Paramiko pin isn't already doing.
If you've got suggestions I'm all ears! Going to close as unactionable otherwise.
Repository: fabric/fabric

Issue #395: Init scripts frequently fail to start their daemons
Created: 2011-08-19T02:01:21Z
Description
I've gotten multiple reports of this on IRC, as well as a comment on #350, and now a mailing list thread.
No clear cause yet, and while it's been reported multiple times I don't expect that it is a constant problem or we'd be hearing much more about it. In some very limited testing on my end so far, I can recreate the problem maybe 30-50% of the time -- but it is reproducible.
Symptom is simply that init-style scripts responsible for starting daemons and then returning immediately, will return OK, return code of 0 and "success" status message printed to stdout -- but will not actually spin up the daemon in question.
My personal test was done via latest master targeting an Ubuntu 10.04 (Lucid) VM and the stock Apache2 package's init script.

Originally submitted by Jeff Forcier (bitprophet) on 2011-07-23 at 07:25pm EDT
Relations

Related to #350: fabric hangs up some remote command (for daemon program)

Duplicate issue #1158: Background processes with nohup needs sleep to work
Created: 2014-07-09T16:29:28Z
Something interesting I've found.
When doing:
run("nohup sleep 10 &>/dev/null & disown")
run("pgrep sleep")

it doesn't work:
[127.0.0.1] Executing task 'setup'
[127.0.0.1] run: nohup sleep 10 &>/dev/null & disown
[127.0.0.1] run: pgrep sleep

Fatal error: run() received nonzero return code 1 while executing!

Requested: pgrep sleep
Executed: /bin/bash -l -c "pgrep sleep"

Aborting.

though this does:
[127.0.0.1] Executing task 'setup'
[127.0.0.1] run: nohup sleep 10 &>/dev/null & disown; sleep 1
[127.0.0.1] run: pgrep sleep
[127.0.0.1] out: 1998

Tried adding channel.shutdown(2) before channel.close(), doesn't seem to help.
No clue.

Closing comment (2014-08-05T00:03:36Z): Duplicates #395 - is same core problem as far as I can tell.
Repository: fabric/fabric

Issue #1196: Agent forwarding hangs with latest paramiko (1.15.0)
Created: 2014-09-22T13:51:07Z
Putting this here so the next person to have this problem doesn't spend a day debugging :)
paramiko/paramiko#399

Duplicate issue #1197: ssh agent hangs on mac in fabric 1.10
Created: 2014-09-22T18:16:14Z
On a OS X 10.6.8, using fabric 1.10 and env.forward_agent = True, this command hangs forever:
run('ssh-add -l')
Using fabric 1.8.3, it correctly lists the ssh keys available to the agent.

Closing comment (2014-09-22T19:13:02Z): This duplicates #1196 and has already been fixed, please get Paramiko 1.15.1 :)
Repository: fabric/fabric

Issue #367: files.append not detecting lines present if ~ used
Created: 2011-08-19T02:01:05Z
Description
The files.append always appends the lines, whether they're present or not.
It appears a tilde in the path is a factor.
def test_append():
    files.append('~/lines', ['line1', 'line2'])

Replaced '~/lines' with 'lines' and it behaves as expected. It is the file presence detection that is failing:
Commands to run: test_append
[jaracoco@box758.bluehost.com] Executing task 'test_append'
[jaracoco@box758.bluehost.com] run: /bin/bash -l -c "test -e \"~/lines\""
[jaracoco@box758.bluehost.com] run: /bin/bash -l -c "echo 'line1' >> ~/lines"
[jaracoco@box758.bluehost.com] run: /bin/bash -l -c "test -e \"~/lines\""
[jaracoco@box758.bluehost.com] run: /bin/bash -l -c "echo 'line2' >> ~/lines"

As you can see, even after the first command is run, it fails to detect the file. I've replicated this on Ubuntu 10.04 and the redhat variant at Bluehost.

Originally submitted by Jason R. Coombs (jaraco) on 2011-06-24 at 01:55pm EDT

Duplicate issue #728: fabric.contrib.files.contains not work properly
Created: 2012-09-15T13:58:16Z
for some filename, for example "~/.ssh/authorized_keys"
you can see at https://github.com/collective/collective.hostout/blob/master/collective/hostout/fabfile.py
fabric.contrib.files.append( text=key,
filename='~%s/.ssh/authorized_keys' % owner,
use_sudo=use_sudo )
generated code by function "fabric.contrib.files.append"  not work
egrep "^ssh-rsa\ AAAAB3.......HhV9QkZ\ hostout@hostout$" "~myuser/.ssh/authorized_keys"
egrep: ~myuser/.ssh/authorized_keys: No such file or directory
but when quote will be removed for second argument
egrep "^ssh-rsa\ AAAAB3.......HhV9QkZ\ hostout@hostout$" ~myuser/.ssh/authorized_keys
this worked as expected

Closing comment (2013-05-19T00:16:51Z): After about an hour of testing and trial/error with code in contrib/files.py, this issue seems to be a duplicate of #367, was addressed with #589 (still open?), and ultimately with commit c6a4585.
Best way to get this 2 month-old bug fix seems to be by cloning and installing from the latest code.
Repository: facebook/react-devtools

Issue #323: "Inspect in react" context menu
Created: 2016-02-04T21:49:37Z
I don't know if this would be possible, but it would be awesome if there were a way to select a component on the page and have it jump to that component in the tools a la the normal chrome "inspect element":

Imagine if there was an "inspect in react" option!

Duplicate issue #543: Add "Inspect with React DevTools" to context menu
Created: 2017-02-17T14:22:09Z
Today, if I want to look at a particular component on my page, I typically right click it to show the context menu, then click Inspect, and then switch over to the React tab in the developer tools.
I would love to be able to have another option - Inspect with React DevTools that did this process for me.

Closing comment (2017-02-17T14:27:49Z): Duplicate of #323
Repository: facebook/react-devtools

Issue #132: Check for data's length in dehydrate.js will throw error if data is ImmutableJS iterable data structure
Created: 2015-08-09T03:19:14Z
I'm using ImmutableJS iterables in my project & received the following error:
iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error

In the stack trace I found that data.length was being called on an ImmutableJS iterable.

Duplicate issue #171: When using immutable if react devtools beta is enabled, an ominous warning appears.
Created: 2015-09-02T01:40:28Z
iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error
    at Record.Object.defineProperty.get (webpack:///./~/immutable/dist/immutable.js?:4602:21)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:50:21)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:57:14)
    at Array.map (native)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:56:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:178:19)
    at Array.map (native)
    at Bridge.flush (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:173:33)

If I disabled the devtools, this no longer shows up in the console.
Possibly related to #52

Closing comment (2015-09-02T02:05:36Z): Duplicate of #132, #126, #125 and #106
Repository: facebook/react-devtools

Issue #1032: Error: "Expected to find at least one React renderer."
Created: 2018-05-21T11:16:34Z
I get the following error when I try clicking on one of the elements under Inspector mode:

I've installed react-devtools following the instructions here.
react-devtools opens and connects to my app, but when I click on any element, I get the above red box error.
If this isn't a react-devtools related error, can someone please direct me where to look? Thanks in advance!
Platform: Android 5.1.1 Lollipop running on Genymotion
Host OS: Ubuntu 16.04 LTS
React Native: 0.55.4 (project created using react-native init)

Duplicate issue #1225: Expected to find at least one React Native renderer on DevTools hook.
Created: 2018-11-12T09:03:52Z
I got this error when toggle inspector. Need help !!! T_T
ios simulator 11.1
"react-native": "0.55.0"

Closing comment (2018-11-19T16:54:09Z): Inspector is part of react-native, not DevTools. At least when this was reported before (#1032) it was reported that the same bug occurred even without react-devtools.
Are you by chance using the react-native-root-toast or react-native-root-siblings libraries? Seems related: magicismight/react-native-root-toast/issues/89
Either way, I'm going to close this issue as a duplicate of #1032. Let's talk there! 😄
Repository: facebook/react-devtools

Issue #106: [New Devtools] Warnings with Immutable.js
Created: 2015-08-04T04:44:33Z
Hi,
I just tried the new React DevTools and I found that it generated a bunch of warnings as pasted below. Since I use Immutable collections as props, I'd wager that this is where the warnings are coming from.
bundle.js:2 iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error
    at le.Object.defineProperty.get (http://prakhar.me/react-surveyman/build/bundle.js:2:473)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:50:21)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:57:14)
    at Array.map (native)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:56:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:178:19)
    at Array.map (native)
    at Bridge.flush (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:173:33)

Let me know if you need any more detail for this. You can see the application live here
Thanks,

Duplicate issue #125: ImmutableJS warning: "iterable.length has been deprecated" in dehydrate.js:59
Created: 2015-08-06T04:24:15Z
I am using ImmutableJS Map as state:
  getInitialState() {
    return Map();
  },
  onChange() {
    this.replaceState(Map());
  },


iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error
    at src_Map__Map.Object.defineProperty.get (webpack:///./~/immutable/dist/immutable.js?:4602:21)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:50:21)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:178:19)
    at Array.map (native)
    at Bridge.flush (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:173:33)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:161:17)

Closing comment (2015-08-06T04:35:06Z): Dupe of #106.
Repository: facebook/react-devtools

Issue #91: Not showing up when inspecting a Chrome app
Created: 2015-05-20T08:23:29Z
I’m using React to develop the UI for a Chrome app.
I have installed the React Chrome Developer Tools, it shows up in Crome dev tools in the browser, but it doesn’t show up when I’m inspecting the Chrome app’s UI.
I imagine this use case may have not been expected/popular, but I’m still wondering if it’d be a way around it.

Duplicate issue #173: Not showing up when inspecting a popup window in chrome extension
Created: 2015-09-03T01:00:38Z
I’m building the UI of a Popup in Chrome Extension with React. If try to Inspect Popup, React Chrome Developer Tools are not there, though I can use them for inspecting websites.

Closing comment (2016-07-09T00:26:45Z): Dupe of #91 essentially, I think.
Repository: facebook/react-devtools

Issue #1282: Hooks: non-primitive state pieces are not inspectable
Created: 2019-01-20T23:01:29Z
Currently, if you put a non-primitive value in a state using hooks, like:
const [position, setPosition] = useState({x: 42, y: 13});
const [fruits, setFruits] = useState(['apple', 'banana', 'orange']);
all the DevTools (3.6.0) shows is the following:
Hooks
  State: {…}
  State: Array[3]

with no way to inspect what's inside the object or an array. This makes it significantly less useful.
See it live at https://react-l4hrmm.stackblitz.io/ (look at the Hello component in DevTools). Code at https://stackblitz.com/edit/react-l4hrmm.
Related: #1215

Duplicate issue #1305: React Dev Tools: useReducer content isn't displayed
Created: 2019-02-17T01:28:55Z
Crosspost at react
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Using useReducer with an object as state doesn't show the content of the object and is un-expandable.

Using a state with a string will show.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:
https://q8yzo2z1mj.codesandbox.io/
What is the expected behavior?
Expect the contents be expandable as with objects and arrays from traditional state.
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
React: 16.8.2
DevTools: 3.6.0
Chrome: 72.0.3626.109 (Official Build) (64-bit)

Closing comment (2019-02-27T06:33:45Z): Duplicate of #1282

#1282 is about useState(), which is resolved. This is about useReducer(), it is not duplicated.
Repository: facebook/react-devtools

Issue #90: Empty <Top Level></Top Level> in React tab
Created: 2015-05-19T14:48:19Z
The extension was working on our app until we updated to react 0.13 version, all it shows is:
<Top Level></Top Level>

Duplicate issue #82: react-devtools doesn't work with React + Meteor
Created: 2015-04-06T21:40:52Z
Hi, I don't see the React DOM in the React tab in the inspector, just an empty tab
This is a Meteor React example leaderboard

Closing comment (2015-07-08T20:57:13Z): We (Meteor) are fixing this on our end.  Related to #90.
Repository: facebook/react-devtools

Issue #126: Warnings with Immutable.js
Created: 2015-08-06T14:20:13Z
With enabled plugin, I'm seeing multiple warnings regarding the access of length property on Immutable.js objects. When I disable the extension, the warnings are gone.
It also may be an issue on my side, so please excuse in this case.
Warning message:
iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error
    at src_Map__Map.Object.defineProperty.get (/* removed */)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:50:21)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at dehydrate (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:198:2), <anonymous>:70:17)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:178:19)
    at Array.map (native)
    at Bridge.flush (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:173:33)
    at eval (eval at <anonymous> (chrome-extension://lkefdminonoajpbbbemjloccljgfaokc/build/backend.js:72:2), <anonymous>:161:17)

The warning originates at dehydrate.js?ca6a:59

Duplicate issue #132: Check for data's length in dehydrate.js will throw error if data is ImmutableJS iterable data structure
Created: 2015-08-09T03:19:14Z
I'm using ImmutableJS iterables in my project & received the following error:
iterable.length has been deprecated, use iterable.size or iterable.count(). This warning will become a silent error in a future version. Error

In the stack trace I found that data.length was being called on an ImmutableJS iterable.

Closing comment (2015-08-09T03:33:41Z): Duplicate of #126, #125 and #106
Repository: facebook/react-devtools

Issue #1297: useEffect causes unnecessary rerender
Created: 2019-02-09T14:30:38Z
The following code when used with the Chrome extension causes unnecessary re-render of the App component when browsing the node structure provided by the dev tools.
import React, { useEffect } from "react";
import ReactDOM from "react-dom";

const App = () => {
  useEffect(() => {
    console.log("useEffect");
  });

  console.log("render");

  return <div>Hello, world</div>;
};

ReactDOM.render(<App />, document.getElementById("root"));

If I remove the useEffect() call it prevents the extra re-renders.
The version of the extension is 3.6.0. Tested on Chrome 72.0.3626.53 with react@16.8.1 and react-dom@16.8.1.
Here's a video link to the issue for more clarity: https://streamable.com/q3rpn

Duplicate issue #1333: Render twice using hook component
Created: 2019-04-16T07:02:43Z
Hook components will render twice when open react devtool.
import React, { useState } from 'react';

function App() {
  const [count, setCount] = useState(0);
  const incrementCount = () => setCount(count + 1);

  console.log('render');

  return <button onClick={incrementCount}>{count}</button>;
}

export default App;
Click the button, the console will print twice 'render' message. If you close React devtool, it'll print only once.
This seems a bug of react devtool.

Closing comment (2019-06-29T23:37:03Z): Looks like it's the same as #1297
Repository: facebook/react-devtools

Issue #1282: Hooks: non-primitive state pieces are not inspectable
Created: 2019-01-20T23:01:29Z
Currently, if you put a non-primitive value in a state using hooks, like:
const [position, setPosition] = useState({x: 42, y: 13});
const [fruits, setFruits] = useState(['apple', 'banana', 'orange']);
all the DevTools (3.6.0) shows is the following:
Hooks
  State: {…}
  State: Array[3]

with no way to inspect what's inside the object or an array. This makes it significantly less useful.
See it live at https://react-l4hrmm.stackblitz.io/ (look at the Hello component in DevTools). Code at https://stackblitz.com/edit/react-l4hrmm.
Related: #1215

Duplicate issue #1301: Problems to show Hooks State in Chrome
Created: 2019-02-10T15:54:16Z
Chrome Version => 72.0
React developers Tools => 3.6.0
Does not show the state, only showing this notation and  when I touch not pass nothing

Closing comment (2019-02-10T22:19:20Z): @apenab Since it looks like a duplicate of #1282, can you close this issue?
Repository: facebook/stetho

Issue #634: SQLite console broken in Chrome 72
Created: 2019-02-05T21:05:24Z
Stetho 1.5.0, Chrome 72.x

Click on SQLite database
Type:
> SELECT 1<Enter>
Nothing happens

There are no suspicious warnings in Logcat.

Duplicate issue #635: Database console not working
Created: 2019-02-21T02:41:40Z
I am using Stetho 1.5.0
I am able to see database from resources tab of Stetho, but I am not able to query for data from database console. Say if I want to just query data
SELECT * FROM someTable LIMIT 1; 
and hit enter, it keeps going to next line while showing indicator. No data is shown.

The same problem is happening for Stetho console.

I am not sure if its a bug or any dependency I should install?

Closing comment (2019-02-24T20:03:09Z): looks to be the same as #634
Repository: facebook/stetho

Issue #49: Error: Could not bind to socket
Created: 2015-02-20T10:50:22Z
Upon starting an app, stetho fails to setup a server here:

  
    
      stetho/stetho/src/main/java/com/facebook/stetho/server/LocalSocketHttpServer.java
    
    
         Line 287
      in
      69a9ec5
    
  
  
    

        
          
           LogUtil.e(e, "Could not bind to socket."); 
        
    
  


Not sure what I am doing wrong and whether there is anything particular needed to be configured on my test device (Nexus 5/6)?

Duplicate issue #74: inspect no data ,and the log show this.why?
Created: 2015-02-25T06:49:28Z

Closing comment (2015-02-26T20:27:22Z): Duplicate of #49, which is fixed in master.  A new release is expected this week to address the issue.
Note however, that this is a harmless error and shows up even in the sample app.
Repository: facebook/stetho

Issue #607: Stetho view inspection crashing apps on Android P DP4
Created: 2018-07-16T16:07:36Z
Looks like the Stetho element inspection is crashing on the latest Android P developer preview. Using an emulator with build number sdk_gphone_x86-userdebug 9 PPP4.180612.0074860066 dev-keys, I get this crash when trying to do an inspection of my view elements:
07-16 09:04:25.244 9124-9124/? E/AndroidRuntime: FATAL EXCEPTION: main Process: com.iotas.installer, PID: 9124 java.lang.IllegalArgumentException: Invalid Region.Op - only INTERSECT and DIFFERENCE are allowed at android.graphics.Canvas.checkValidClipOp(Canvas.java:779) at android.graphics.Canvas.clipRect(Canvas.java:826) at com.facebook.stetho.inspector.elements.android.ViewHighlightOverlays$ViewHighlightOverlaysJellybeanMR2$MainHighlightDrawable.draw(ViewHighlightOverlays.java:141) at android.view.ViewOverlay$OverlayViewGroup.dispatchDraw(ViewOverlay.java:256) at android.view.View.draw(View.java:20216) at com.android.internal.policy.DecorView.draw(DecorView.java:780) at android.view.View.updateDisplayListIfDirty(View.java:19082) at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:686) at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:692) at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:801) at android.view.ViewRootImpl.draw(ViewRootImpl.java:3312) at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:3116) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2485) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1460) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7184) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:949) at android.view.Choreographer.doCallbacks(Choreographer.java:761) at android.view.Choreographer.doFrame(Choreographer.java:696) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:935) at android.os.Handler.handleCallback(Handler.java:873) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:193) at android.app.ActivityThread.main(ActivityThread.java:6669) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Let me know if there's any other way I can help! Tried this on an older build of Android with no issues.

Duplicate issue #633: App crashes android 9
Created: 2019-02-05T05:15:12Z
When starting to inspect with chrome app crashes with error:

Invalid Region.Op - only INTERSECT and DIFFERENCE are allowed

Closing comment (2019-02-25T00:21:52Z): I believe this is a duplicate of #607, however this still hasn't been released.
Repository: facebook/stetho

Issue #381: NullPointerException
Created: 2016-05-04T04:45:18Z
I'm can't reproduce it every time  (version 1.3.1)
Process: com.adoriasoft.quietping, PID: 9303
java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null
at com.facebook.stetho.inspector.elements.Document$4.store(Document.java:388)
at com.facebook.stetho.inspector.elements.ShadowDocument$Update.getChangedElements(ShadowDocument.java:297)
at com.facebook.stetho.inspector.elements.Document.applyDocumentUpdate(Document.java:372)
at com.facebook.stetho.inspector.elements.Document.updateTree(Document.java:327)
at com.facebook.stetho.inspector.elements.Document.access$1200(Document.java:30)
at com.facebook.stetho.inspector.elements.Document$ProviderListener.onPossiblyChanged(Document.java:682)
at com.facebook.stetho.inspector.elements.android.AndroidDocumentProvider$1.run(AndroidDocumentProvider.java:67)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5951)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1400)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1195)

Duplicate issue #463: App Crashes
Created: 2016-12-05T17:20:27Z
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'int java.lang.Integer.intValue()' on a null object reference
at com.facebook.stetho.inspector.elements.Document$4.store(Document.java:394)
at com.facebook.stetho.inspector.elements.ShadowDocument$Update.getChangedElements(ShadowDocument.java:297)
at com.facebook.stetho.inspector.elements.Document.applyDocumentUpdate(Document.java:378)
at com.facebook.stetho.inspector.elements.Document.updateTree(Document.java:333)
at com.facebook.stetho.inspector.elements.Document.access$1200(Document.java:30)
at com.facebook.stetho.inspector.elements.Document$ProviderListener.onPossiblyChanged(Document.java:688)
at com.facebook.stetho.inspector.elements.android.AndroidDocumentProvider$1.run(AndroidDocumentProvider.java:67)
at android.os.Handler.handleCallback(Handler.java:746)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5443)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:728)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)

Closing comment (2016-12-05T19:01:06Z): Dupe of #381
Repository: facebook/stetho

Issue #38: Support Volley usage
Created: 2015-02-19T09:00:43Z
How can I use Stetho while using Volley as a networking library?

Duplicate issue #39: How to use stetho for Volley?
Created: 2015-02-19T09:58:39Z
I use vollley as my backend-communicator. It is complete controlled by Google, how to use stetho without editing source-code of volley?

Closing comment (2015-02-19T16:15:59Z): Duplicates #38
Repository: facebook/stetho

Issue #49: Error: Could not bind to socket
Created: 2015-02-20T10:50:22Z
Upon starting an app, stetho fails to setup a server here:

  
    
      stetho/stetho/src/main/java/com/facebook/stetho/server/LocalSocketHttpServer.java
    
    
         Line 287
      in
      69a9ec5
    
  
  
    

        
          
           LogUtil.e(e, "Could not bind to socket."); 
        
    
  


Not sure what I am doing wrong and whether there is anything particular needed to be configured on my test device (Nexus 5/6)?

Duplicate issue #70: "stetho﹕ Could not bind to socket" message in log on application start
Created: 2015-02-23T20:39:13Z
"stetho﹕ Could not bind to socket" message without any other details.
Please extend this message with additional information what protocol and port was used for binding.

Closing comment (2015-02-23T21:29:23Z): Duplicates #49, already fixed in master.  Will be releasing 1.0.1 soon with this fix.
Repository: facebook/stetho

Issue #319: Memory leak in Stetho 1.2.0
Created: 2015-12-15T17:56:41Z
We've experienced a severe memory leak after we integrated Stetho into our app. Through bisection we could pin down the exact revision when we did this and could verify that - once Stetho was removed - the memory leak was gone.
The leak showed up in Android's Memory Monitor, where constantly around 20KB/s have been added on top until the limit was reached and GC kicked in. Then, from the lower level onwards, memory consumption raised again.
The way we integrated Stetho was fairly basic, we only enabled it in our custom Application instance via Stetho.initializeWithDefaults(this) for DEBUG builds.

Duplicate issue #504: with stetho i got Activity has leaked window com.android.internal.policy.PhoneWindow
Created: 2017-03-02T08:40:07Z
i got this error when I show a dialog while doing an api request  with this,is it my bad or it's a bug。 I just compile stetho today and then the error appears

Closing comment (2017-03-10T15:19:31Z): Duplicates #319
Repository: facebook/stetho

Issue #193: Dialogs and DialogFragment are not shown in Elements tab
Created: 2015-05-21T19:01:08Z
Dialogs are invisible to the Elements tab which currently only considers the Activity window's decor view and all subviews.  This finds most normal fragments, but not dialogs due to the fact that dialogs used their own window and therefore have a separate decor view.
We can add support for this in a similar fashion to adb shell dumpsys activity top which visualizes both the Activity view tree and also all detached fragment's view trees separately.

Duplicate issue #240: Element tab should have a way to inspect dialogs
Created: 2015-08-03T19:32:10Z
Currently Dialogs and Dialog Fragments are not inspectable.

Closing comment (2015-08-03T21:33:25Z): Duplicates #193; solved in master
Repository: facebookarchive/WebDriverAgent

Issue #399: Web Driver agent remains in state Listening on USB and the appium tests never start in real device.
Created: 2016-12-06T14:39:06Z
The problem
Web Driver agent remains in state Listening on USB and the appium tests never start in real device.
Environment
Appium version 1.6.2:
I start the appium programatically in order to run test in real device using XCuiTest:
You can find attached the logs from test and WebDriverAgent as well
Session-2016-12-06_15:48:18-DNbfdC.txt
testLog.txt
The following desired capabilities are also set:
realDeviceLogger=usr/local/lib/node_modules/deviceconsole/deviceconsole
xcodeConfigFile=/usr/local/lib/node_modules/appium/node_modules/appium-xcuitest-driver/WebDriverAgent/driverAgent.xcconfig

Duplicate issue #398: Test block Continuing to run tests in the background with task ID 1
Created: 2016-12-06T13:12:45Z
When I try to launch my Appium(1.6.2) test with this WDA (from master) with my real device(iPhone 7)
test blocked...
[debug] [WebDriverAgent] Device: Dec 5 10:20:09 iPhoneQA5SBlanc XCTRunner[4277] : Continuing to run tests in the background with task ID 1

Closing comment (2016-12-07T12:36:37Z): Duplicate of #399