WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I originally left a comment in #4936, but I felt this might be better as a separate issue.

I completely agree with the rationale behind no backing instances and no refs for stateless components. I want to use pure stateless components as much as possible.

However, I'm running into instances where testing stateless components gets tricky. For the most part, using the shallow renderer to render a stateless component has been fine. I can then make assertions on expected props and children. To reduce the duplication, I abstract out the shallow renderer process to a helper function.

When, I want to test events, though, I have to take a different route. If my component takes an onClick prop, then I wrap it in a class component, so I can access the DOM node to simulate my click event. Again, this isn't a huge deal because I can abstract out the wrap/render process into a helper function.

I bring all this up because I feel that it would be nice to have better facilities in TestUtils for stateless components. I don't think the answer is allowing ReactDOM.findDOMNode to work on stateless components because that opens up it to abuse in normal application code. Are you open to allowing extra functions in TestUtils to simplify the process of testing stateless components? Or am I creating a code smell in my testing?

I'd be happy to create a PR for TestUtils if you think some more helper functions for stateless components would be beneficial.

Issue 2:
Hi,

I have a fairly trivial application which was running on ReactJS 0.14.x. Since I've moved it to 15rc1, it continues to work perfectly in Chrome. However, in IE11, in appears to render critical parts empty. The relevant piece of code where I'm failing is here:

https://github.com/technion/erlvulnscan/blob/master/frontend/assets/erlvulnscan.jsx#L37

There is no error output on the debug console. The DOM explorer appears to just render it with missing data.

You can see the application with the relevant behaviour running live at: https://erlvulnscan.lolware.net. Enter any network (127.0.0.0 will yield the fastest return) to see the issue.

Edit: For non IE users, you can see a SS here: http://imgur.com/i9TciqZ
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Usage of the formArrayName directive stops @ContentChildren() from finding children of the element onto which formArrayName was applied.

Expected behavior

@ContentChildren() reaches children of formArrayName.

Minimal reproduction of the problem with instructions

This plunker shows the problem. <my-component> is defined twice in the template, but the length of the found components is 1.

Please tell us about your environment:

Angular version: 2.4.7

Issue 2:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

ContentChild queries descendants but ContentChildren does not. This commit changed this behavior -> 0dc15eb

Expected behavior

ContentChild should behave like ContentChildren or better page author should decide with an option like descendats: true|false or we need to new decorators like ContentDescendant and ContentDescendants. Note that if you guys also decide to change ContentChildren to descendants:true all of a sudden, it will break whole a lot of apps. Even if you do, we need a way to customize the default behavior to restore the order back.

What is the motivation / use case for changing the behavior?

Lack of support to customize querying.

Angular version: 2.0.X

2.2
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

A React.Component should be returned when using:

private responsiveDialog = withResponsiveFullScreen({ breakpoint: 'sm' })(Dialog);

This means that withResponsiveFullScreen({ breakpoint: 'sm' }) should return a function that accepts a type and returns the new Component with responsive properties.

Current Behavior

Currently calling withResponsiveFullScreen({ breakpoint: 'sm' }) returns a React.Component. This is out of line with the expected behaviour when looking at the funciton in withResponsiveFullScreen.js.

The definition of withResponsiveFullScreen in withResponsiveFullScreen.d.ts should probably be changed to return a function.

Steps to Reproduce (for bugs)

private responsiveDialog = withResponsiveFullScreen({ breakpoint: 'sm' })(Dialog); when using typescript.

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.8

Issue 2:
When using the classes root override in the Snackbar component, it adds a wrapping div with your the css classes you define instead of overriding the root containers properties.

I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Change the style of the snackbar components root element

Current Behavior

Adds a parent div to the snackbar components root element

Steps to Reproduce (for bugs)

Here is an example I added padding to it so you can actually see what it does, if you remove the padding you will not see the changes: https://codesandbox.io/s/03l5x9klwn

Context

I'm trying to change the styling of the Snackbar component

Your Environment

Tech
Version

Material-UI
1.0.0-beta.13

React
15.5.3

browser
Chrome Version 61.0.3163.10
Issue 1:
Current Behavior:

Running npm view --json sompackage dist-tags gives an error output in case no tags exist like:

{
"shortMessage": "Command failed with exit code 1: npm view --json sompackage dist-tags",
"command": "npm view --json sompackage dist-tags",
"exitCode": 1,
"stdout": "",
"stderr": "npm ERR! code E404\nnpm ERR! 404 Not Found - GET https://registry.npmjs.org/hayden-test-repo - Not found\nnpm ERR! 404 \nnpm ERR! 404 'hayden-test-repo@latest' is not in the npm registry.\nnpm ERR! 404 You should bug the author to publish it (or use the name yourself!)\nnpm ERR! 404 \nnpm ERR! 404 Note that you can also install from a\nnpm ERR! 404 tarball, folder, http url, or git url.\n{\n \"error\": {\n \"code\": \"E404\",\n \"summary\": \"Not Found - GET https://registry.npmjs.org/hayden-test-repo - Not found\",\n \"detail\": \"\\n 'hayden-test-repo@latest' is not in the npm registry.\\nYou should bug the author to publish it (or use the name yourself!)\\n\\nNote that you can also install from a\\ntarball, folder, http url, or git url.\"\n }\n}\n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /Users/hayden/.npm/_logs/2021-04-12T14_41_53_367Z-debug.log",
"failed": true,
"timedOut": false,
"isCanceled": false,
"killed": false
}

The stderr contains the json response but also contains some text making the JSON unparsable.

Expected Behavior:

We should be able to get a valid json in stderr without the extra string.

Steps To Reproduce:

Run npm view --json sompackage dist-tags

Observe the stderr being given.

This issue on np has more detailed info in case it is needed.

Environment:

OS: Ubuntu 20.04

Node: v14.16.1

npm: 7.9.0

Issue 2:
The problem

NPM's --json option allows scripts to invoke an NPM command and receive machine-readable JSON that can be easily processed. In previous NPM versions, the JSON was written to STDOUT and all other messages were written to STDERR, making it easy for a script to extract the JSON.

With NPM 7.x, everything is mixed together on STDERR. This defeats the point of the --json feature, which was to make parsing easy. Instead, a script has to implement heuristics to guess which STDERR lines are JSON or not. Scripts developed for NPM 6 now fail because they are reading the wrong stream.

Steps To Reproduce:

Correct behavior: With NPM 6.x, invoke this command:

npm search --json

The JSON output is written to STDOUT:

{
"error": {
"code": null,
"summary": "search must be called with arguments",
"detail": ""
}
}

The console messages are written to STDERR:

npm ERR! search must be called with arguments
npm ERR! A complete log of this run can be found in:

Broken behavior: With NPM 7.5.4 (the latest version), invoke the same command. Both outputs are mixed together on STDERR. Nothing is written to STDOUT.

This regression appears to have been introduced with NPM 7.0.0.

Environment:

OS: All OS's

Node: 12.17.0

npm: 7.5.4
Issue 1:
Hello there. Are there any plans for including official community-supported translations for React docs? At @translaiton-gang we've just completed Vue.js` docs Russian translation, and we also have some progress with React ones. I believe, at least Japanese and Chinese communities would also like to have their own translations. So, could we integrate it somehow?

UPD: I see some random translation files under docs/community. Is it how it's done now? How is the document version to display being detected? I mean, I can't see any header dropdown language choice or something.

Issue 2:
We've deleted the old localized content because most of the docs changed too much.

We should set up proper infrastructure for localization because the old process was slow and ineffective.

cc @lacker
Issue 1:
Error with 2.3.0

http://fancyapps.com/fancybox/

Issue 2:
Hi,

I've just noticed that jQuery fancyBox isn't working anymore in conjunction with Bootstrap 2.3.

When reverting back to Bootstrap 2.2.2 everything is fine again.

Here are two jsfiddles to demonstrate the issue:

with Bootstrap 2.3 .js File: http://jsfiddle.net/XmDXJ/ <-- fancyBox doesn't open

without the Bootstrap js file: http://jsfiddle.net/yzJVH/ <-- fancyBox opens as it should
Issue 1:
Code Sample, a copy-pastable example if possible

import seaborn as sns
tips = sns.load_dataset("tips")
print(tips["day"].dtype)
counts = tips.groupby("size").day.value_counts().rename("count").reset_index()
print(counts["day"].dtype)

category
object

Problem description

When the categorical variable (day) becomes an index in the groupby and then gets reset, it loses its categorical metadata (and dtype). In the case of the tips dataset, this includes the proper ordering of days.

Interestingly, this isn't the case with the Series.value_counts method, which properly creates a CategoricalIndex with the order metadata.

I don't see an existing issue about this but maybe #9748 is related?

Expected Output

category
category

Output of pd.show_versions()

INSTALLED VERSIONS

commit: None

python: 3.6.2.final.0

python-bits: 64

OS: Darwin

OS-release: 16.7.0

machine: x86_64

processor: i386

byteorder: little

LC_ALL: None

LANG: en_US.UTF-8

LOCALE: en_US.UTF-8

pandas: 0.21.1

pytest: 3.2.1

pip: 9.0.1

setuptools: 36.5.0.post20170921

Cython: 0.26.1

numpy: 1.13.1

scipy: 0.19.1

pyarrow: None

xarray: None

IPython: 6.2.1

sphinx: 1.6.3

patsy: 0.4.1

dateutil: 2.6.1

pytz: 2017.2

blosc: None

bottleneck: 1.2.1

tables: 3.4.2

numexpr: 2.6.2

feather: None

matplotlib: 2.1.1

openpyxl: 2.4.8

xlrd: 1.1.0

xlwt: 1.2.0

xlsxwriter: 0.9.8

lxml: 3.8.0

bs4: 4.6.0

html5lib: 0.999999999

sqlalchemy: 1.1.13

pymysql: None

psycopg2: None

jinja2: 2.9.6

s3fs: None

fastparquet: None

pandas_gbq: None

pandas_datareader: None

Issue 2:
Code Sample, a copy-pastable example if possible

# Your code here

In [1]: df=pd.DataFrame(dict(payload=[-1,-2,-1,-2], col=pd.Categorical(["foo", "bar", "bar", "qux"], ordered=True)));df
Out[1]:
col payload
0 foo -1
1 bar -2
2 bar -1
3 qux -2

In [2]: df.groupby("payload").first().col.dtype
Out[2]: dtype('O')

Problem description

Grouping shouldn't coerce a categorical into object. Categorical dtypes should be preserved as long as possible for efficiency and correctness.

Expected Output

The result dtype should be CategoricalDtype(categories=['bar', 'foo', 'qux'], ordered=True), just like it is here:

In [6]: df.groupby("payload").head().col.dtype
Out[6]: CategoricalDtype(categories=['bar', 'foo', 'qux'], ordered=True

#### Output of ``pd.show_versions()``

<details>
INSTALLED VERSIONS
------------------
commit: None
python: 3.4.3.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-98-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8

pandas: 0.21.0
pytest: 3.2.5
pip: 9.0.1
setuptools: 36.5.0
Cython: 0.20.1post0
numpy: 1.13.3
scipy: 0.13.3
pyarrow: None
xarray: 0.9.6
IPython: 6.2.0
sphinx: None
patsy: None
dateutil: 2.6.1
pytz: 2017.3
blosc: None
bottleneck: None
tables: 3.1.1
numexpr: 2.6.4
feather: None
matplotlib: 1.3.1
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: 4.2.1
html5lib: 0.999
sqlalchemy: 0.8.4
pymysql: None
psycopg2: None
jinja2: 2.7.2
s3fs: 0.1.2
fastparquet: None
pandas_gbq: None
pandas_datareader: None
[paste the output of ``pd.show_versions()`` here below this line]

</details>
Issue 1:
Suppose a type declaration is used to provide a shorter name for a specific example of a generic struct

struct X<T>;

impl<T> X<T> {
fn go() -> int {-1}
}

struct A;
type Alias = X<A>;

then its not possible to call a static method via Alias

fn main() {
let a = X::<A>::go(); // Works
let b = Alias::go(); // Won't compile - error: failed to resolve. Use of undeclared module `Alias`
}

Should the compiler expand type declarations in path expressions (ie Alias => X::<T>)?

Issue 2:
Compile this:

pub mod foo {
pub mod bar {
pub mod baz {
struct Qux;

impl Qux {
pub fn new() {}
}
}
}
}

fn main() {
type Ham = foo::bar::baz::Qux;
let Foo = foo::bar::baz::Qux::new(); // works fine
let Bar = Ham::new(); // oops!
}

$ rustc ty.rs
!!! (resolving module in lexical scope) module wasn't actually a module!
ty.rs:16:14: 16:22 error: unresolved name
ty.rs:16 let Bar = Ham::new();
^~~~~~~~
ty.rs:16:14: 16:22 error: use of undeclared module `Ham`
ty.rs:16 let Bar = Ham::new();
^~~~~~~~
!!! (resolving module in lexical scope) module wasn't actually a module!
ty.rs:16:14: 16:22 error: unresolved name `Ham::new`.
ty.rs:16 let Bar = Ham::new();
^~~~~~~~
error: aborting due to 3 previous errors
task 'rustc' failed at 'explicit failure', /root/catacombs/scrap/rust/src/libsyntax/diagnostic.rs:102
task '<main>' failed at 'explicit failure', /root/catacombs/scrap/rust/src/librustc/lib.rs:392

I can't imagine that this is intentional, as it greatly limits the utility of type aliases.
Issue 1:
Bug report

Describe the bug

When using Next's new src/pages support through now dev (because I'm using now secrets) I'm getting a directory list view listing only the package.json instead of the index page.

To Reproduce

Create a new Next app npx create-next-app now-dev-src-pages

Move the pages and the components directory to an src folder in the root folder

Launch dev mode using now dev

Expected behavior

When visiting http://localhost:3000 I should see the src/pages/index.js page contents.

Screenshots

System information

OS: [macOS]

Version of Next.js: 9.1.1

Additional info

Visiting http://localhost:5000 instead, I get to see the actual expected behaviour.

Issue 2:
Running now dev while having everything the src directory does not work. next build still works.

Next.js v9.1.0.

No now.json.

Thanks!
Issue 1:
Feature Request

Charset of ShardingSphere Proxy is determined by

locale of environment

The property file.encoding

Is your feature request related to a problem?

If the charset was unset in environment, any non-ASCII characters will always be malformed.

Describe the feature you would like.

Parse Charset provides by client in protocol and store in connection scope. #13332

Intercept SQL like set names utf8 or set client_encoding to 'UTF8' and set the charset to current channel attribute. Duplicated with #12245

Issue 2:
I have a table with no sharding configuration, if I try to ask a page request with certain offset (not zero), it will always return the first page.

I took a look at class DQLMergeEngine, and found that some weird code below.

@Override public MergedResult merge() throws SQLException { if (1 == queryResults.size()) { return new IteratorStreamMergedResult(queryResults); } selectStatement.setIndexForItems(columnLabelIndexMap); return decorate(build()); }

it will always return IteratorStreamMergedResult instance even it's a select request with limit.

It's working at 3.0.0 with different logic, please take a look.
Issue 1:
Words that coincide with variable / object names in comments are inspectable as if you were inspecting the real variable. For me this occurred in a JavaScript file on Windows 10.

Issue 2:
VSCode Version: 1.2

OS Version: Debian Jessie

Steps to Reproduce:

A fresh install doesn't have this directory. Or just remove it to test.

rm -rf ~/.config/Code/User

Try installing any extension.

code --install-extension ms-vscode.csharp
Error: watch /home/vscode/.config/Code/User ENOENT
at exports._errnoException (util.js:890:11)
at FSWatcher.start (fs.js:1323:19)
at Object.fs.watch (fs.js:1351:11)
at new e (/usr/share/code/resources/app/out/vs/code/node/cliProcessMain.js:6:1245)
at m (/usr/share/code/resources/app/out/vs/code/node/cli.js:4:11378)
at t._createInstance (/usr/share/code/resources/app/out/vs/code/node/cliProcessMain.js:6:7605)
at t._createAndCacheServiceInstance (/usr/share/code/resources/app/out/vs/code/node/cliProcessMain.js:6:8580)
at t._getOrCreateServiceInstance (/usr/share/code/resources/app/out/vs/code/node/cliProcessMain.js:6:7766)
at /usr/share/code/resources/app/out/vs/code/node/cliProcessMain.js:6:7122
at Array.map (native)

Found while working on ctaggart/rusty-vscode#16.
Issue 1:
As discussed in #11332

renderer.gammaInput needs to be deprecated. We now support texture.encoding instead.

renderer.gammaOutput needs to be deprecated and replaced with renderer.outputEncoding when rendering to the screen. We already support renderTarget.texture.encoding when rendering to a render target.

WebGLPrograms.getProgramCode() needs to be updated to respond to changes in renderer.outputEncoding. Setting material.needsUpdate = true will then force the change.

Legacy warnings need to be added, and the examples need to be updated to accommodate this change.

Issue 2:
For WebVR we now use VREffect for stereo render. A camera is passed as a parameter that gets duplicated and then the scene is rendered twice, once per eye. There's redundant work that we could avoid. We have superficially discussed in the past the idea of introducing an ArrayCamera that receives a list of cameras and then the render work is organized in a more efficient way than we do now with VREffect. Before getting into the implementation weeds I would like to better understand the problem and see the solutions people have in mind. @mrdoob Can you quickly sketch out the API you had in mind and what optimizations we would do inside to kick off the conversation?
Issue 1:
Hi,

on Gentoo Linux, we see parallel build issues in all versions (including latest 1.16.x version) for Python 3.x:

Most common failure with lapack (should come close to your defaults):

build-error_py36_with_lapack.txt

However, this is not always reproducible.

Most reproducible failure is without lapack:

build-error_py36_without_lapack.txt

Downstream-Bug: https://bugs.gentoo.org/660754

Issue 2:
I'm trying to build scipy 0.18.1 with Python 3.6.0, Numpy 1.12.0, GCC 6.1.0, and OpenBLAS 0.2.19 on CentOS 6.8. When I build in serial, things work just fine. But when I use -j 16, I'm seeing build errors:

/blues/gpfs/home/software/spack-0.10.0/lib/spack/env/gcc/gfortran -Wall -g -Wall -g -shared build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/scipy/integrate/_dopmodule.o build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/fortranobject.o -L/blues/gpfs/home/software/spack-0.10.0/opt/spack/linux-centos6-x86_64/gcc-6.1.0/python-3.6.0-prk6gk3ufbfetjc2bthqokmkjtjnce3j/lib -Lbuild/temp.linux-x86_64-3.6 -ldop -lpython3.6m -lgfortran -o build/lib.linux-x86_64-3.6/scipy/integrate/_dop.cpython-36m-x86_64-linux-gnu.so
build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/fortranobject.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
build/temp.linux-x86_64-3.6/build/src.linux-x86_64-3.6/fortranobject.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status

I can successfully build in parallel with Python 2.7.13, so this problem may be specific to Python 3.
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.3.5

After updating Symfony (v3.3.2 => v3.3.5) I can't shutdown local web server http://127.0.0.1:8000

How to reproduce:

install symfony 3.3.5 (reproducible on fresh Symfony)

php bin/console server:start

php bin/console server:stop

check http://127.0.0.1:8000 - it is still up and next stop commands doesnt work: "[ERROR] No web server is listening." - but it is running

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.3.5

Hello,

Despite my initial assumption, the server:stop does not actually stop the web server. It displays all-is-good message, but I can still access the app under 127.0.0.1:8000. What is more, there is no way for my to shut down the process aside from running kill PROCESS_PID.

This has changed since upgrading to 3.3.5 from 3.2.11 (PHP 7.1.7).
Issue 1:
It seems like this change #5917 unfortunately broke production for us.

We are using a proxy url that follows this scheme: http://randomstring:randomstring@eu-west-static-04.example.com:9293 (from a service that provides static IPs)

Expected Result

In 2.26.0 this still works:

>>> from requests.utils import prepend_scheme_if_needed
>>> prepend_scheme_if_needed('http://randomstring:randomstring@eu-west-static-04.example.com:9293', 'http')
'http://randomstring:randomstring@eu-west-static-04.example.com:9293'

Actual Result

In 2.27.0 it's broken:

>>> from requests.utils import prepend_scheme_if_needed
>>> prepend_scheme_if_needed('http://randomstring:randomstring@eu-west-static-04.example.com:9293', 'http')
'http://eu-west-static-04.example.com:9293'

This leads in the end to ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 407 Proxy Authentication Required'))) because the url was cut.

Reproduction Steps

>>> from requests.utils import prepend_scheme_if_needed
>>> prepend_scheme_if_needed('http://randomstring:randomstring@eu-west-static-04.example.com:9293', 'http')

System Information

{
"chardet": {
"version": null
},
"charset_normalizer": {
"version": "2.0.9"
},
"cryptography": {
"version": "36.0.1"
},
"idna": {
"version": "3.3"
},
"implementation": {
"name": "CPython",
"version": "3.9.9"
},
"platform": {
"release": "5.14.21-2-MANJARO",
"system": "Linux"
},
"pyOpenSSL": {
"openssl_version": "101010df",
"version": "21.0.0"
},
"requests": {
"version": "2.27.0"
},
"system_ssl": {
"version": "101010df"
},
"urllib3": {
"version": "1.26.7"
},
"using_charset_normalizer": true,
"using_pyopenssl": true
}

Issue 2:
When using proxies in python 3.8.12, I get an error 407. Using any other version of python works fine. I am assuming it could be to do with this https://docs.python.org/3/whatsnew/3.8.html#notable-changes-in-python-3-8-12.

I should get a status of 200.

I get a status code of 407.

import requests

r = requests.get('https://example.org/', proxies=proxies) # You will need a proxy to test with, I am using a paid service.
print(r.status_code)

System Information

{
"chardet": {
"version": null
},
"charset_normalizer": {
"version": "2.0.9"
},
"cryptography": {
"version": ""
},
"idna": {
"version": "3.3"
},
"implementation": {
"name": "CPython",
"version": "3.8.12"
},
"platform": {
"release": "5.13.0-7620-generic",
"system": "Linux"
},
"pyOpenSSL": {
"openssl_version": "",
"version": null
},
"requests": {
"version": "2.27.0"
},
"system_ssl": {
"version": "101010cf"
},
"urllib3": {
"version": "1.26.7"
},
"using_charset_normalizer": true,
"using_pyopenssl": false
}