WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Using a session object and setting the proxies dictionary does not affect the proxies used during a request.

ex: Still tries to use system proxy.

s = requests.Session()
s.proxies = {'http': None, 'https': None}
s.post(url='http://10.0.1.1', json={'test': 'data'})

Using proxies during each request works, but it would be great to set them at the session level. Specifically if you potentially have dozens or ".post()" or ".get()" calls throughout your script.

Any thoughts?

Issue 2:
Session.trust_env = False turns off the checking of environment variables for options including proxy settings (*_proxy). But urllib picks up and uses these environment proxy settings anyway. requests should pass the trust_env setting on to urllib. (Although I'm not sure if urllib has a similar override.)

(Proxy setting precedence should be sorted out here as well. They way it is now, environment proxy settings will interfere with (rather than be over-ridden by) the proxies argument in Session.request or requests.request calls and the Session.proxies config regardless of trust_env settings.)
Issue 1:
Unzip the arm prebuilt on arm linux system. Ran all Math functions and the results are shown here. The functions in red return incorrect results. We've noticed this issue all the way back to 0.32.x. 0.29.2 does not have these issues.

Issue 2:
I'm using this electron: https://github.com/atom/electron/releases/download/v0.35.4/electron-v0.35.4-linux-arm.zip

Long.js library returns different result on Raspberry Pi 2 for the following js code:

Long.fromString("13370000000").toString()

I've created proof-of-concept repo here: https://github.com/bartekn/electron-long-bug.

The problem seems to be connected with this line in Long.js:

return new Long((value % TWO_PWR_32_DBL) | 0, (value / TWO_PWR_32_DBL) | 0, unsigned);

When value of value variable is equal 13370000000, the first value passed to Long constructor ((value % TWO_PWR_32_DBL) | 0) is equal 0 on Raspberry Pi, while it's equal 485098112 on Mac OS (the correct value).

When trying to calculate 13370000000%4294967296 (TWO_PWR_32_DBL=4294967296) in the chrome dev tools console on Raspberry Pi 2 it returns correct result (485098112).

I'm not sure if it's a problem of electron or libchromiumcontent, sorry.
Issue 1:
Piping ReadableStream through TextDecoderStream leaks resource as demonstrated with following test:

Deno.test("leaks", async () => {
const res = await fetch(
"https://deno.land/std@0.186.0/json/testdata/test.jsonl"
)

const textStream = new TextDecoderStream()
const reader = res.body!.pipeThrough(textStream).getReader()
const t = await reader.read()

await reader!.cancel()
})

Run deno test stream-test.ts and you will get:

error: Leaking resources:
- A text decoder (rid 6) was created during the test, but not finished during the test. Close the text decoder by calling `textDecoder.decode('')` or `await textDecoderStream.readable.cancel()`.

Adding await t.readable.cancel() as error message suggested does not help.

A following solution with manual decoding works properly:

Deno.test("working alternative", async () => {
const res = await fetch(
"https://deno.land/std@0.186.0/json/testdata/test.jsonl"
)

const textDecoder = new TextDecoder()
const reader = res.body!.getReader()
const b = await reader.read()
const t = await textDecoder.decode(b.value!)

await reader.cancel()
})

I spent whole evening last night to make it work and ended up with latter piece. Shouldn't closing initial stream also close all subsequent ones? Either way, closing readable TextDecoderStream doesn't work too.

Deno version: 1.33.2 and 1.33.1

Issue 2:
When configuring a server with a cloudflare origin server certificate, it works perfectly when you visit the site using the url with https:

But when directly visiting the server IP using https the process stops on the server with the following error:

Would it be possible to ignore that error so that the server continues to run?

The connection may close or return an error message, but the server should continue to listen to other requests.

I hope you have a solution! regards
Issue 1:
Summary of the new feature

I would like to customize PowerToys Run's shell (used for launching commands starting with > ).

For example I would like to use Power Shell Core instead of cmd. Here's many more options might be available.

cmd

PowerShell

PowerShell Core

WSL

Custom shell (eg.: git, zsh, ...)

C:\Program Files(x86)\Myshell\customshell.exe --interactive --command "{0}"

{0} might be used for shell command.

Issue 2:
PowerToys Run is a convinient tool.

But it would be even better, if it would be possible to configure which program executes > commands.

Right now > ping github.com starts in a cmd window, but I, for example, would prefer to use Terminal.

Is it possible?
Issue 1:
Symfony version(s) affected: all

Description

When a form field is disabled but a value is submitted to it regardless, the value is silently ignored. This can be confusing to the user - when he opened the form the field was not disabled but something changed in the system while he was filling it so the field is disabled now. The value is then silently ignored but the user gets no notification about the problem.

How to reproduce

Create a form field that has the 'disabled' option active conditionally. Open the form in one window while the field is enabled, then do something in another window causing it to be disabled and then submit the form in the first window.

Possible Solution

Submitting a value into a disabled field should cause a validation error on the form field in question so that the user knows about the change.

Issue 2:
The validation of an image I have:

photo:
- Image: { maxSize: 2M, maxSizeMessage: "the size is bigger than {{ limit }}, please change the photo file." }
- NotBlank: { groups: [registration], message: "Please select an photo." }

everything works great except that the maxSizeMessage don't show, only appear the default symfony photo.

I've removed the {{ limit }} to test and still it persists
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta12

React
16

browser
Electron

etc

Issue 2:
For Fixing table Head in material 1.0.0 11 alpha

I have a table with scrolling rows but I am not able to fix the header.

Is there a property to do so as fixedHeader was in material 0.15 and up but there doesnt seem to be something similar in 1.0.0 version

Versions

Material-UI: 1.0.0-alpha 11

React: 15.4.2
Issue 1:
Bug Report

The following code cannot be compiled when using @babel/plugin-proposal-private-methods.

Output: Duplicate declaration "i".

class A {
#a() {
const i = 9
}

#b() {
const i = 8
}
}

Issue 2:
Bug Report

Current behavior

Switch statements containing closures are generating broken code causing adjacent cases to run. See this minimal reproduction with the default settings:

https://babeljs.io/en/repl#?browsers=defaults&build=&builtIns=false&spec=false&loose=false&code_lz=GYewTgBAFAxiB2BnALhAhhEwIG0CMAugJQQDeAUBBIgO4CWyMAFtMmAK4CmJFVVMaRJwhsuALjKU-_BCggAjCAF4IeANxTpUEkoB8CjdKp1sUUdwVhOaANaGjceMjrwu9qgF9NEAUIjA0ABshCV4jZCYwEBoIeE4YgFEwKLAoACJ2eCs0ZjR5QM40oncIL09yLyA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=false&fileSize=false&timeTravel=false&sourceType=module&lineWrap=true&presets=env%2Creact%2Cstage-2%2Cenv&prettier=false&targets=&version=7.10.4&externalPlugins=

Input Code

for (const a of [1]) {
switch (true) {
case true: {
const b = 1;
() => b;
if (true) break;
continue;
}
case false: {
throw new Error("unreachable");
}
}
}

Output Code

for (var _i = 0, _arr = [1]; _i < _arr.length; _i++) {
var a = _arr[_i];

switch (true) {
case true:
{
var _ret = function () {
var b = 1;

(function () {
return b;
});

if (true) return "break";
return "continue";
}();

switch (_ret) {
case "break":
break;

case "continue":
continue;
}
}

case false:
{
throw new Error("unreachable");
}
}
}

Expected behavior

No error is thrown (the break statement functions as intended, and the false case does not run).

Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)

Defaults. See the REPL.

Environment

Defaults. See the REPL.

Possible Solution

If you want to use a break statement here, it needs to be a labeled break to break the outer loop.

switch (_ret) {
case "break":
break outer;

case "continue":
continue;
}

Alternatively, use an if instead of a nested switch.

if (_ret === "break") break;
if (_ret === "continue") continue;
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I run npm version and no commit or tag is created. I am not using --no-git-tag-version. F.e. just npm version major -m "...".

Under what conditions does npm version avoid creating a commit and tag?

Expected Behavior

Always commit and tag unless I specify not to.

Steps To Reproduce

git clone https://github.com/lume/lume.git
cd lume/packages/lume
npm version major -m "v%s" --ignore-scripts

After this, you will see that package.json was updated, but no commit or tag was created.

Environment

OS: Linux

Node: 14.16

npm: 7.10

Issue 2:
Current Behavior:

npm version <version> is not committing the modified package.json or package-lock.json; nor git-tagging.

We were using npm version {major|minor|patch} extensively (and successfully). It stopped working once the package was moved out of the root of the repo and into a subdirectory.

Expected Behavior:

npm version <version> should continue to create a git-commit and git-tag as indicated in the docs:

If run in a git repo, it will also create a version commit and tag. This behavior is controlled by git-tag-version (see below), and can be disabled on the command line by running npm --no-git-tag-version version. It will fail if the working directory is not clean, unless the -f or --force flag is set.

Steps To Reproduce:

initialize an npm package in the root of an initialized git repo

npm version minor successfully bumps the version, commits and tags

move the npm package into a subdirectory of the repo

npm version minor still bumps the version in package.json and package-lock.json, but git is not committed nor tagged.

Environment:

macOS 10.15.7

node: v14.13.1

npm: 6.14.8

git: git version 2.28.0

This is apparently an existing bug going as far back as npm v3: npm/npm#18795
Issue 1:
From version 0.9.0 to version 0.11.0 the "diagonal" on non quadratic pairplots is empty.

Sample Code:

import seaborn as sns
import pandas as pd
from matplotlib import pyplot as plt

test_df = pd.DataFrame({"a": [1,2,3,4], "b": [3,4,5,6], "c": [5,3,6,1]})
sns.pairplot(test_df, x_vars=["a"], y_vars=["b", "c"])
plt.show()

The top graph is empty although a scatter plot should be shown in place as the two columns have matching indices.

Issue 2:
Just updated to seaborn 0.11.0 and matplotlib 3.3.1.

Run this code:

iris = sns.load_dataset("iris")
sns.pairplot(data=iris, hue="species", y_vars='sepal_width');
sns.pairplot(data=iris, hue="species", y_vars='sepal_width', x_vars=['sepal_length', 'petal_length']);

And saw it:

And this problem appeared in all previously created pairplots, that have parameter y_vars
Issue 1:
Hello,

I tried to use the clip function on a basic Panel but it seems that the axis management is not working as expected. I believe this is an update to issue #8344

import numpy as np
import pandas as pd

data = np.random.randn(3, 4, 5)
panel = pd.Panel(data)
panel.clip(0, 1)

If I run the script with pandas 0.16.2 on python 2.7.10 and 3.4.3, I'm getting the following error:

.../pandas/core/generic.pyc in clip(self, lower, upper, out, axis)
3052 result = self
3053 if lower is not None:
-> 3054 result = result.clip_lower(lower, axis)
3055 if upper is not None:
3056 result = result.clip_upper(upper, axis)

.../pandas/core/generic.pyc in clip_lower(self, threshold, axis)
3103 raise ValueError("Cannot use an NA value as a clip threshold")
3104
-> 3105 subset = self.ge(threshold, axis=axis) | isnull(self)
3106 return self.where(subset, threshold, axis=axis)
3107

TypeError: f() got an unexpected keyword argument 'axis'

Thanks a lot for all your efforts!

Issue 2:
Let's take the following example:

d = {'Item1' : pandas.DataFrame(numpy.random.randn(4, 3)),
'Item2' : pandas.DataFrame(numpy.random.randn(4, 2))}

p = pandas.Panel(d)
p.clip(0,1)

If I run the script with pandas 0.14.1 on both python 2.7.8 and 3.4.1 I'm getting the following error:

Traceback (most recent call last):
File "Untitled.py", line 11, in <module>
p.clip(0,1)
File "/usr/local/lib/python2.7/site-packages/pandas/core/generic.py", line 2684, in clip
result = result.clip_lower(lower)
File "/usr/local/lib/python2.7/site-packages/pandas/core/generic.py", line 2722, in clip_lower
return self.where((self >= threshold) | isnull(self), threshold)
File "/usr/local/lib/python2.7/site-packages/pandas/core/ops.py", line 934, in f
self._constructor.__name__)
ValueError: Simple arithmetic with Panel can only be done with scalar values

Digging a little bit deeper showed that the following line (the | operator to be precise) raises the error:

https://github.com/pydata/pandas/blob/1d65bc89d64c71f8d36f3ca92dd57db2efad7fdb/pandas/core/generic.py#L2796
Issue 1:
pip install -U git+https://github.com/pydata/pandas.git

gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/local/lib/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -c pandas/src/generated.c -o build/temp.linux-i686-2.7/pandas/src/generated.o

gcc: error: pandas/src/generated.c: No such file or directory

Issue 2:
pip install git+https://github.com/pydata/pandas.git

does currently not work because the .pyx files are not being cythonized (not sure why). An easy fix is to include .c files in the git repo which should make it easier for people to deploy.

I used a simple try: import cython in setup.py that cythonizes if cython is installed and uses the .c files otherwise:

https://github.com/hddm-devs/hddm/blob/develop/setup.py#L4
Issue 1:
Continuing from this discussion: https://discuss.atom.io/t/double-icon-when-pinned/17320/24

I've got Atom installed on Windows 10. I open the application, then right click the icon in the taskbar, then click Pin to Taskbar. This creates a duplicate (second) icon on the taskbar. The first icon is the actual instance of the app running, and it goes away when the app is closed. The second icon stays permanently. If I click the second icon while Atom is closed, it adds the first icon back to my taskbar.

Any ideas as to what I can do to fix this?

Issue 2:
run latest Windows 10

pin either electron or atom to the taskbar

click it to open the app

=> you end up having 2 icons

=> somehow the app when started does not get associated to the pinned entry in the taskbar

=> it does not reproduce on Windows 8.x

I wonder if your change in fb6c80d could have an impact here. Imho it is used to find out if an application belongs to the same process group or not: https://msdn.microsoft.com/en-us/library/windows/desktop/dd378422(v=vs.85).aspx
Issue 1:
Do you want to request a feature or report a bug?

Not sure tbh.

What is the current behavior?

I have global handler for unhandled errors:

window.addEventListener('error', (evt) => ...)

Now when I use the componentDidCatch function it gets called correctly when render throws an exception but that global error event is also triggered - and before the componentDidCatch call.

What is the expected behavior?

Since componentDidCatch handles the error I'd prefer if the global event wasn't triggered, same as with a usual try-catch block.

Or is there at least some way to figure out from the evt object in the event handler that the exception is caught by react?

I hope this made sense...

Issue 2:
I'm trying to make use of componentDidCatch in the React 16 beta. I already had a global window error handler which was working fine, but it unexpectedly catches errors that I would expect componentDidCatch to have handled. That is, component-local errors are being treated as window-global errors in dev builds.

The problem seems to stem from invokeGuardedCallbackDev in ReactErrorUtils.js. I think that this entire __DEV__ block of code is problematic. The stated rational is:

// In DEV mode, we swap out invokeGuardedCallback for a special version
// that plays more nicely with the browser's DevTools. The idea is to preserve
// "Pause on exceptions" behavior. Because React wraps all user-provided
// functions in invokeGuardedCallback, and the production version of
// invokeGuardedCallback uses a try-catch, all user exceptions are treated
// like caught exceptions, and the DevTools won't pause unless the developer
// takes the extra step of enabling pause on caught exceptions. This is
// untintuitive, though, because even though React has caught the error, from
// the developer's perspective, the error is uncaught.

This is misguided because it's not about pausing on exceptions, it's about "pause on uncaught exceptions." However, componentDidCatch makes exceptions caught!

Rather than switching on prod vs dev and using try/catch in prod and window's error handler in dev, React should always use try/catch, but rethrow if you reach the root without hitting a componentDidCatch handler. This would preserve the correct "pause on uncaught exceptions" behavior without messing with global error handlers.
Issue 1:
From @AlecBoutin on May 18, 2016 19:55

VSCode Version: 1.1

The .tsx/.jsx auto-formatter adds an unnecessary space on the end of certain dynamic attributes.

E.g. <button id={fn()} /> becomes <button id={fn() } /> after the file is auto-formatted. A space is inserted after the closing parenthesis of the fn() call.

The problem appears to be related to having parenthesis in the attribute.

E.g. <button id={""} /> is left unchanged by auto-format. <button id={("")} /> becomes <button id={("") } /> (the space is inserted)

I have also observed the auto-formatter preserves the spaces in the id attribute of <button id={ ("") } />

Copied from original issue: microsoft/vscode#6498

Issue 2:
When I format document a space is added before closing parenthesis.

It should not be added.
Issue 1:
See the example below

>>> double = np.array([0.0], dtype=np.float64)[0]
>>> float = 0.0
>>> a = Variable(torch.FloatTensor(1))
>>> a + float
Variable containing:
1.00000e-34 *
1.3192
[torch.FloatTensor of size 1]
>>> float + a
Variable containing:
1.00000e-34 *
1.3192
[torch.FloatTensor of size 1]
>>> a + double
Variable containing:
1.00000e-34 *
1.3192
[torch.FloatTensor of size 1]
>>> double + a
array([[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[Variable containing:
1.00000e-34 *
1.3192
[torch.FloatTensor of size 1]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]], dtype=object)

Issue 2:
Pytorch shows the following inconsistent behaviour.

import numpy as np
import torch
from torch.autograd import Variable

1.0 + Variable(torch.ones(1))
# returns as expected
# Variable containing:
# 2
# [torch.FloatTensor of size 1]

np.sum(1.0) + Variable(torch.ones(1))
# returns an unexpected (depth of array is 32)
# array([[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[Variable containing:
# 2
# [torch.FloatTensor of size 1]
# ]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]], dtype=object)

# Switching their order
Variable(torch.ones(1)) + np.sum(1.0)
# returns the expected
# Variable containing:
# 2
# [torch.FloatTensor of size 1]
Issue 1:
Describe what you were doing when the bug occurred:

Opened profiler

Recorded

Switched to waterfall

Please do not remove the text below this line

DevTools version: 4.0.6-a39d9c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11442

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11388)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11921)

at xi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56:277807)

at Ha (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:55891)

at Xl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:98281)

at Hl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:84256)

at Fl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:81286)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:25364

Component stack: in xi

in div

in div

in div

in Ir

in Unknown

in n

in Unknown

in div

in div

in Wa

in ce

in be

in So

in Vl

Issue 2:
PLEASE INCLUDE REPRO INSTRUCTIONS AND EXAMPLE CODE

I got this error when I click 'Ranked'.

Please do not remove the text below this line

DevTools version: 4.0.4-3c6a219

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11441

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11387)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11920)

at _i (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56:277123)

at Ha (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:55890)

at Xl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:98280)

at Hl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:84255)

at Fl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:81285)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:25363

Component stack: in _i

in div

in div

in div

in Or

in Unknown

in n

in Unknown

in div

in div

in Ha

in le

in ve

in ko

in Ul
Issue 1:
"name": "doctrine/orm",
"version": "v2.4.8",
"source": {
"type": "git",
"url": "https://github.com/doctrine/doctrine2.git",
"reference": "464b5fdbfbbeb4a65465ac173c4c5d90960f41ff"
}

When the doctrine/ORM bundle is downloaded by composer (URL: https://api.github.com/repos/doctrine/doctrine2/zipball/464b5fdbfbbeb4a65465ac173c4c5d90960f41ff) always the default=last version is returned. I don't know if other references are faulty, too.

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

Hello the community,

A hunter from our Bug Bounty Program reported that when an input is manually changed from text to an array on the form payload, he receives a 500 instead of a proper violation.

For example, if email=bob@lamouche.com is changed to email[]=bob@lamouche.com on an email field having an EmailValidator, we end up with this exception thrown:

symfony/src/Symfony/Component/Validator/Constraints/EmailValidator.php

Lines 49 to 51
in
3e4f978

if (!is_scalar($value) && !(is_object($value) && method_exists($value, '__toString'))) {

throw new UnexpectedTypeException($value, 'string');

}

This is obvious, and not really an issue as field was manually changed, but this might create false positives on error logs / monitoring if abused. Wouldn't it be cleaner to add a violation to the field, simply telling that the value is not an email?