WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-serial/1538/

Failed: [k8s.io] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:70
Jun 15 11:37:41.767: Number of replicas has changed: expected 3, got 4

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-subnet/3097/

Failed: Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:72
Jun 12 14:01:32.286: Number of replicas has changed: expected 3, got 4
Issue 1:
nyuszika7h@cadoth ~/src > git clone https://github.com/kennethreitz/requests.git
Cloning into 'requests'...
remote: Counting objects: 18867, done.
remote: Compressing objects: 100% (11/11), done.
error: object 5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8: badTimezone: invalid author/committer line - bad time zone
fatal: Error in object
fatal: index-pack failed

Issue 2:
I can't clone this repo. It complains:

$ git clone https://github.com/kennethreitz/requests
Cloning into 'requests'...
remote: Counting objects: 17048, done.
remote: Compressing objects: 100% (39/39), done.
error: object 5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8: badTimezone: invalid author/committer line - bad time zone
fatal: Error in object
fatal: index-pack failed
Issue 1:
When I change the transitions in the default variables (like: https://material-ui-1dab0.firebaseapp.com/customization/themes/#the-other-variables), the app throws me the following error:

TypeError: theme.transitions.create is not a function

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

Expected Behavior

The framework should use MY default transitions that I put on the createMuiTheme function.

Current Behavior

The app throws me the following error:

TypeError: theme.transitions.create is not a function

Steps to Reproduce (for bugs)

const materialTheme = createMuiTheme({
transitions: {
easing: {
easeInOut: 'cubic-bezier(0.6, 0, 0.2, 1)',
easeOut: 'cubic-bezier(0.0, 0, 0.2, 1)',
easeIn: 'cubic-bezier(0.6, 0, 1, 1)',
sharp: 'cubic-bezier(0.6, 0, 0.6, 1)'
},
duration: {
shortest: 150,
shorter: 200,
short: 250,
standard: 300,
complex: 375,
enteringScreen: 225,
leavingScreen: 195
}
}
});

<MuiThemeProvider theme={materialTheme}>
<Button raised color="accent">
Mui Button
</Button>
</MuiThemeProvider>

Context

The application doesn't compile.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.9

React
15.6.1

Issue 2:
Summary

There's a similar issue in #2302.

Currently, this library did not provide TextFieldBox yet. Therefore I wanted to know if the team will implement it or not. The specification can be found here.

It's appearance would look something like this :

Moreover, this design is also widely adopted in the latest Google Calendar App :

Conclusion

I hope that this component will be implemented soon, as I personally felt that it has a better UX compared to the singe-line text field.

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

I've got strange behavior for experiments. I'm working with matrix (for example b) that in result of multiplying b.T * b should be singular matrix and for inverse method should be arisen error like numpy.linalg.linalg.LinAlgError: Singular matrix. But result was high/low values.

Code below:

>>> b = np.matrix([[1,1,0], [1,0,1], [1,1,0]])
>>> b
matrix([[1, 1, 0],
[1, 0, 1],
[1, 1, 0]])
>>> np.linalg.inv(b.T * b)
matrix([[ 4.50359963e+15, -4.50359963e+15, -4.50359963e+15],
[-4.50359963e+15, 4.50359963e+15, 4.50359963e+15],
[-4.50359963e+15, 4.50359963e+15, 4.50359963e+15]])

How can be avoided this behavior?

Tests on:

win10, Python 3.5.4, numpy version '1.14.0'.

ubuntu 16.04, Python 3.5.2, numpy version '1.13.3' and '1.14.0'.

PS. I've checked via wolfram and R it's real singular matrix.

Issue 2:
I am trying to solve several independent systems of equations at the same time using numpy.linalg.solve, e.g., a has shape (N, M, M). The challenge I'm running into is how to deal with the case when, for some values of N, the last two dimensions comprise a singular matrix.

Consider this example

import numpy as np
arr = [[[1, 0], [0, 1]], [[1, 0], [0, 1]], [[0, 0], [0, 0]]]
np.linalg.solve(arr, 1)

On numpy 1.9.2, this will raise a LinAlgError, but I still would like to know the solutions for all the full-rank matrices. (I would be okay with getting back NaNs for the singular cases.) I'm aware I can compute the singular values and use fancy indexing to slice the array, but in my algorithm I have to do several slicing/filtering steps and I would prefer not to lose the alignment of a with b -- my real-world a typically has 6-7 dimensions and all the indexing arrays make the code hard to follow.

My ideal solution seems to involve masked arrays since I end up doing several other filtering steps, but it appears that most (all?) functions in the linalg family ignore array masks.

Is there an alternative solution already available, or perhaps a suggestion on how I could contribute a solution that I could package as a PR?
Issue 1:
It seems ./pavement.py has some dead code, in particular we noticed that the bootstrap task cannot run because there is a typo in the bscript name (boostrap.py, not bootstrap.py) See PR #11005

Issue 2:
Just a few notes resulting from 1.10.4 release for future reference

paver sdist must be run before paver write_release_and_log, otherwise fail.

docs are generated with paver pdf (not in documentation)

paver generates NOTES.txt, need to rename README.txt and sign for Sourceforge.

Changelog would look far better if merge commits were not included.

Results are in three directories release, dist, build_doc. That's crazy.

python setup.py sdist --formats=gztar,zip upload --sign requires a ~/.pypirc file with [server-login] entry.

If ~/.pypirc exists, twine expects [pypi] and maybe [distutils] entries.

twine wasn't working anyway. Problem may have been on pypi side.

Conclusions: paver script needs updating, documentation also, make a ~/.pypirc file. It would be nice to know why twine wasn't working, but given that pypi requires a new release every time you sneeze, I'm not going to explore the issue. The generation of the mac wheel files worked well. Pypi is an undocumented PITA.
Issue 1:
For example, 0 for markdown, large enough for code.

Issue 2:
It would be interesting to have the ability to define different word wrap values for different languages, specially if you use Code for editing normal programming languages like JavaScript, Pascal and non programming languages, like Markdown.

I tend to respect the word wrap values defined in the main IDE for a particular language (if exists/is used), and turn off word wrap for for Markdown/Log/Text files. But today, in Code I only have settings for the Editor (editor.wrappingColumn and editor.wrappingIndent).

Thanks in advance
Issue 1:
Avoid issues like the one fixed by #4204

Issue 2:
The linkchecker that we use at the moment does not seem to check external links hence #5379 and others

I tried turning on the sphinx linkchecker python make.py linkcheck which seems to work but generate a fair number of redirect warnings and errors. Perhaps it is worth turning this on pr default?

See https://gist.github.com/jenshnielsen/b3dceef10df743154942 for the present output.

The linkcheck command is broken on python 3.5 but that should be fixed in the next Sphinx point release
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I have some global installed packages which I can't see in npm -g ls. I also can't see them being outdated with npm -g outdated. These packages are eslint, yarn, semver

I tried to remove and re-install them(npm -g remove eslint yarn semver && npm -g i eslint yarn semver) But no luck, they still won't appear in npm -g ls. I also purged npm cache once before re-installation

Expected Behavior

Update/View these packages like others

Steps To Reproduce

npm -g ls

I have 20 packages in %appdata%\npm\node_modules but I only see 17

Environment

OS: Windows 10 21H1

Node: 14.18.1

npm: 8.1.0

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

I have ESLint 8.0.0 installed globally via npm install -g eslint (using Node v16.11.0 x64/npm v8.0.0, as well as with npm7.x, on win11).

The issue is that, if I run npm list -g then unfortunately ESLint is not listed (it should show: eslint@8.0.0).

For reference, all my other globally installed packages are displayed ok:

> npm list -g (or: npm list -g --depth=0)

C:\Users\Kostas\AppData\Roaming\npm
+-- npm-check-updates@11.8.5
+-- npm-gui@3.1.1
+-- prettier@2.4.1
+-- stylelint@13.13.1
+-- typescript@4.4.3
+-- web-ext@6.4.0
`-- zx@4.2.0

I have tried uninstalling+reinstalling ESLInt without any difference. I have also tried in a virtual machine (=clean install of Node) with same results.

But, with this command (using ls of 'Git for Windows' installed Bash), ESLint is included in the list:

> ls -l $(npm root -g)

Directory: C:\Users\Kostas\AppData\Roaming\npm\node_modules

Mode LastWriteTime Length Name
---- ------------- ------ ----
d---- 12/10/2021 15:40 eslint
d---- 12/10/2021 15:40 npm-check-updates
d---- 12/10/2021 15:40 npm-gui
d---- 12/10/2021 15:40 prettier
d---- 12/10/2021 15:40 stylelint
d---- 12/10/2021 15:40 typescript
d---- 12/10/2021 15:40 web-ext
d---- 12/10/2021 15:40 zx

Expected Behavior

npm list -g should show: eslint@8.0.0 .

Steps To Reproduce

In a fresh Node x64 v16.11.0/npm v8.0.0 (or v16.10.0/npm v7.24.0) install ESLint via npm install -g eslint

(no special config)

Run npm list -g (or npm list -g --depth=0)

Notice that ESLint is not listed.

Environment

OS: win 11 x64

Node: 16.10.0/16.11.0

npm: 7.24.0/8.0.0
Issue 1:
TypeScript Version:

1.8.10

OS Version:

MacOS

In fact, I just begin to learn typescript, because the angular2.0, I use the https://github.com/angular/quickstart as the begining, and I change it's file structure, add ts folder, and move the typescript file to ts folder, change npm scripts:

"start": "tsc && concurrently \"tsc -w\" \"lite-server\" ", ---->

"start": "npm run build:css && tsc --outDir ./app/scripts/ --rootDir ./app/ts/ && concurrently \"npm run tsc:w\" \"lite-server\" ",

"tsc:w": "tsc -w", ---->

"tsc:w": "tsc -w --outDir ./app/scripts/ --rootDir ./app/ts/",

I start the project by run npm start, the tsc generate related js file to app/scripts folder, but when I change some typescirpt file, instead of outputing to the --outDir folder, it outputs .js files to where the .ts file is. It just happens after changing the file, the first compilation is right.

Issue 2:
TypeScript Version:

1.8.9

The tsserver code assumes that OSX file systems are always run case insensitive. However this is not the case. When the tsserver is used on a case sensitive file system code assist and other features stop working do to file lookup misses. For all the details please see:

microsoft/vscode#5161 (comment)
Issue 1:
The WEBGL_depth_texture extension is widely supported, at least on desktop implementations of WebGL.

It would be nice to be able to use depth textures in three.js; render to depth and stencil buffers, as well as using depth textures as input.

@alteredq mentioned in #806 that he ran into some limitations when playing with depth textures, so I figured it deserves its own issue.

An alternative to supporting depth textures could be to be able to supply our own framebuffers as render target, but I suspect the refactoring necessary to do this might be the largest hurdle anyway.

Issue 2:
Hey guys, wrestled with this for days but need some help.

( THREE.js R69, Windows8, NVIDIA GeForce GTX 760, Chrome 39.0.2171.71 m )

This JSFiddle http://jsfiddle.net/Angrypickle/mbtdxazy/24/ shows a LensFlare image appear in front of the PerspectiveCamera as the camera moves away (and is looking away) from the actual lensflare position. You may have to re-run the jsfiddle to see it appear because it happens quickly.

The lensflare should only appear at position [0,0,0] but when the camera reaches a certain distance, a duplicate lensflare appears in a location opposite the original lensflare. The distance necessary to achieve the bug seems to be related to the camera's .near and .far properties.

I can circumvent the bug by setting a higher camera.near value, but I don't want to do that :) Thanks in advance for help!
Issue 1:
Version

2.5.16

Reproduction link

https://codepen.io/windyflying/pen/JvzvRb

Steps to reproduce

1.用Chrome或Firefox或Edge打开重现链接，查看结果，代码按预期工作。

2.用IE11打开重现链接，代码不能按预期运行。检查浏览器控制台，有运行时错误，如标题。

What is expected?

没有运行时错误

What is actually happening?

出现运行时错误

编译后的模板函数在IE11、 IE10和工作正常的浏览器的不一致。

Issue 2:
Version

2.5.16 / 2.5.17

Reproduction link

https://jsfiddle.net/plasmaeng/ndmjjkho/1/

Steps to reproduce

Running the code below in IE10 will result in the following error:

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>Page Title</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<script src="vue.js"></script>
</head>
<body>
<div id="app_test">
<form>
<select>
<option v-for="value in L">{{value}}</option>
</select>
</form>
</div>

<script>
var appTest = new Vue({
el: '#app_test',
data: {
L : [ '1', '2' ,'3']
}
});
</script>
</body>
</html>

Here is the error message from IE10.

[Vue warn]: Error compiling template:

<div id="app_test">
<form>
<select>
<option v-for="value in L">{{value}}</option>
</select>
</form>
</div>

invalid expression: Syntax error in Raw expression: v-for="value in L"
invalid v-for alias "" in expression: v-for="value in L"

What is expected?

<option> is generated from 1 to 3.

What is actually happening?

<option> is not generated with error !!!

I have persuaded a senior for a long time to introduce Vue.js.

If this problem is solved, we plan to reorganize the site into Vue.js.

Please solve the problem.
Issue 1:
ℹ Computer information

PowerToys version: 0.21.1

PowerToy Utility: Fancy Zones

Running PowerToys as Admin: Yes

Windows build number: [run "winver"] Windows 10 1909

I had previously setup zones for each of my 3 displays, and they were working well. In the last couple weeks, the application of my zone templates seems to have run into issues. For example if I apply the template to the left display, it will apply to all of the displays. If i try to correct one of the other displays, that template then gets applied to all 3 displays.

I have removed all my zone templates and recreated them, but the problem persists. Issue happens running in normal user mode and as an administrator.

All 3 Displays are the same make and model, Asus VS247, connected to INtel HD 520 integrated graphics card

Setting the zone on the left display using the template for that display:

Going to correct the template applied to the right display, it shows that the Left template is applied:

Issue 2:
FancyZones Zones Editor applies new layout to all monitors instead of applying this new layout to the active monitor only. Cannot use different layouts for different monitors.

ℹ Computer information

PowerToys version: 0.21.1

PowerToy Utility: FancyZones

Running PowerToys as Admin: Yes (also when No)

Windows build number: 19041.450

📝 Provide detailed reproduction steps (if any)

Press WIN+GRAVE (FancyZones Zones Editor) on monitor 1

Select new layout

✔️ Expected result

New layout applied to monitor 1, layout of monitor 2 unchanged,

❌ Actual result

Both monitors have the new layout applied. Cannot create different layouts for different monitors.

A workaround is to use 'Allow zones to span across monitors, but this would require the creation of new multi-monitor layouts and makes all 'single monitor templates' unusable.

📷 Screenshots

N/A
Issue 1:
right now it fails in list of lists but the error isn't informative.

xref: commit 5a152bd

Issue 2:
A small, complete example of the issue

a ,a ,a
1,2,3
4,5,6
7,8,9

note the white space next to the char.

>>> import pandas
>>> df = pandas.read_table('test.csv', sep=',')
>>> df.columns
Index([u'a ', u'a .1', u'a .2'], dtype='object')

again, note the white space between the char and the num.

A work around previously was to set mangle_dupe_cols to False, manually strip the columns and then clean up the column names. With pandas 0.19.0, mangle_dupe_cols=False raises a ValueError.

This issue is more of a question as to what the spec of mangle_dupe_cols is and what a full implementation, mentioned in #13262 , desires/is going to be.

Expected Output

Index([u'a', u'a.1', u'a.2'], dtype='object')

Output of pd.show_versions()

## INSTALLED VERSIONS

commit: None

python: 2.7.11.final.0

python-bits: 64

OS: Darwin

OS-release: 15.6.0

machine: x86_64

processor: i386

byteorder: little

LC_ALL: en_US.UTF-8

LANG: en_US.UTF-8

LOCALE: None.None

pandas: 0.19.0

nose: 1.3.7

pip: 8.1.2

setuptools: 23.1.0

Cython: 0.24

numpy: 1.10.4

scipy: None

statsmodels: None

xarray: None

IPython: 5.1.0

sphinx: 1.4.1

patsy: None

dateutil: 2.5.2

pytz: 2016.3

blosc: None

bottleneck: None

tables: None

numexpr: None

matplotlib: None

openpyxl: 2.4.0

xlrd: 1.0.0

xlwt: None

xlsxwriter: None

lxml: 3.6.0

bs4: 4.4.1

html5lib: 0.999

httplib2: None

apiclient: None

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: None

boto: None

pandas_datareader: None
Issue 1:
Problem description

Trying to import from material-ui/styles (any submodule actually) yields compilation errors from tsc when noImplicitAny is enabled.

(3,32): error TS7016: Could not find a declaration file for module 'material-ui/styles'. '/Users/shousper/Source/test/node_modules/material-ui/styles/index.js' implicitly has an 'any' type.
Try `npm install @types/material-ui/styles` if it exists or add a new declaration (.d.ts) file containing `declare module 'material-ui/styles';`

Steps to reproduce

yarn add material-ui@next typescript
echo 'import { createMuiTheme } from \'material-ui/styles\'' > index.ts
echo 'const x = createMuiTheme()' >> index.ts
yarn run tsc -- --noImplicitAny index.ts

Versions

Material-UI: 1.0.0-beta.6

React: N/A

Browser: N/A

Issue 2:
Problem description

@sebald In beta.6 the typescript types exist for material-ui (I see the .d.ts file in the installed package directory) however I keep getting definition errors when doing imports with import Paper from 'material-ui/Paper';

error TS7016: Could not find a declaration file for module 'material-ui/Paper'. '...' implicitly has an 'any' type. Try 'npm install @types/material-ui/Paper' if it exists or add a new declaration (.d.ts) file containing 'declare module 'material-ui/Paper';'

Im not sure why, I dont think there is anything strange with my tsconfig

{
"compilerOptions": {
"target": "es2017",
"module": "commonjs",
"jsx": "react",
"strict": true,
"baseUrl": ".",
"paths": {
"*": ["./build-tools/types/*"]
},
"inlineSourceMap": true,
"experimentalDecorators": true
}
}

Steps to reproduce

I installed beta.6 and removed my local copies of the material-ui typings (up to now Ive been keeping the typings locally)

Versions

Material-UI: 1.0.0-beta.6
Issue 1:
The example given for setting a life cycle event does not use a setter method at:

http://symfony.com/doc/current/book/doctrine.html#lifecycle-callbacks

The current example is:

/**
* @ORM\PrePersist
*/
public function setCreatedAtValue()
{
$this->createdAt = new \DateTime();
}

I assume it should be something like the following (assuming that there is a database column "createdAt" that has had getters and setters generated for it:

/**
* @ORM\PrePersist
*/
public function setCreatedAtValue()
{
$this->setCreatedAt(new \DateTime());
}

Having a "createdAt" DateTime field that does not get updated after the initial submission is a common need, and it would be nice if it were more thoroughly explained (including how to exclude it from display in a Twig template). FWIW, I still can't get this to work right, so my suggestion may be misguided or incomplete.

Issue 2:
Symfony version(s) affected: x.y.z

4.1.1

Description

By using a ChoiceType as a container for a select, and adding options dynamically in the form (e.g. from ajax request) means that the values cannot be passed in the FormType class, which inturn means validation always failed. It's impossible to modify allowed choices in a form event

How to reproduce

Create a form which uses a ChoiceType input, pass in an empty array for the choices, and dynamically populate the input in javascript: untested jquery code

$(function(){
$('#foo').append(new Option('new option', 'newoption'));
});

submit form and see failed validation for input

Possible Solution

Being able to modify the parameters that are used in the creation of the input would be great so I could fetch the permitted values from the db based upon other input and then add them to the choices.

At the moment, I'm having to do something like this in a FormEvent::SUBMIT event listener:

$input = $form->get('itemCondition');
$value = $input->getViewData();
$form->remove('itemCondition');
$obj->setItemCondition($value);

Additional context
Issue 1:
There are docstring consistency tests in test_docstring_parameters.py, but they have many modules commented out. We should fix them one by one.

Issue 2:
Continue #9206 and finish up the rest of the docstrings.

Uncomment the untested modules in sklearn/tests/test_docstring_parameters.py, fix doc inconsistencies and make all tests pass.

todo (modules)

'sklearn.cross_decomposition', (@clemkoa)

'sklearn.discriminant_analysis', (@clemkoa)

'sklearn.ensemble', (@clemkoa)

'sklearn.feature_selection', (@clemkoa)

'sklearn.kernel_approximation', (@clemkoa)

'sklearn.model_selection',

'sklearn.multioutput',

'sklearn.random_projection', #11405

'sklearn.svm' #11405
Issue 1:
🐛 Bug

To Reproduce

@torch.jit.script
def fn():
a = [1, 2, 3, 4]
return a[::-1]
fn()

RuntimeError: vector::_M_range_check The above operation failed in interpreter, with the following stack trace: at test/test_jit.py:6263:19

@torch.jit.script

def test():

a = [1, 2, 3, 4]

return a[::-1]

~~~~~~ <--- HERE

This should either give a compile error, or work (better), but it should not compile and be unsupported.

cc @suo

Issue 2:
For

def t():
x = [1,2,3]
x = x[::-1]
print(x)

torch.jit.script(t)()

it gives IndexError: vector::_M_range_check: __n (which is 18446744073709551615) >= this->size() (which is 3)

@suo

cc @ezyang @gchanan @zou3519 @bdhirsh @gmagogsfm @suo