WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This section is fine and can stay, but it duplicates existing functionality of the
template package. Instead, the program could create a single template, load both the
.html files in one call to ParseFiles, and use ExecuteTemplate instead of its own map.

Would be nice to show users that the caching stuff is done for them if you ask politely.

Issue 2:
What steps will reproduce the problem?

See attached zip file for reproduction

What is the expected output? What do you see instead?

This sample passes with -compiler gc

% go test -compiler gc -v issue/...
=== RUN TestData
--- PASS: TestData (0.00 seconds)
a_test.go:6: 0 false
=== RUN TestXData
--- PASS: TestXData (0.00 seconds)
x_test.go:7: foo &{0 false }
PASS
ok issue/a 0.005s
? issue/b [no test files]

But blows up due to duplicate symbols during linking of a/a.test

ucky(~/src) % go test -compiler gccgo -v issue/...
# testmain
/tmp/go-build896181789/issue/a/_test/issue/liba.a(a.o):(.rodata.__go_tdn_issue_a..issue_a.t+0x0):
multiple definition of `__go_tdn_issue_a..issue_a.t'
/tmp/go-build896181789/issue/liba.a(a.o):(.rodata.__go_tdn_issue_a..issue_a.t+0x0):
first defined here
/tmp/go-build896181789/issue/a/_test/issue/liba.a(a.o): In function `issue_a.TestData':
/home/dfc/src/issue/a/a_test.go:5: multiple definition of `issue_a.Data'
/tmp/go-build896181789/issue/liba.a(a.o):(.bss+0x0): first defined here
/tmp/go-build896181789/issue/a/_test/issue/liba.a(a.o): In function `issue_a..import':
/home/dfc/src/issue/a/a.go:1: multiple definition of `issue_a..import'
/tmp/go-build896181789/issue/liba.a(a.o):/home/dfc/src/issue/a/a.go:1: first defined here
collect2: error: ld returned 1 exit status
FAIL issue/a [build failed]
? issue/b [no test files]

Please use labels and text to provide additional information.

Looking at the -x output for go test issue/a

gccgo -o $WORK/issue/a/_test/a.test $WORK/issue/a/_test/main.o -Wl,-( -m64
$WORK/issue/a/_test/issue/liba_test.a $WORK/issue/libb.a $WORK/issue/liba.a
$WORK/issue/a/_test/issue/liba.a -Wl,-)

liba.a is present twice, once in it's normal form, and once in it's extended (due to the
export_test.go) form.

I am guessing that the first liba.a leaks in due to the transitive import via issue/b.

Attachments:

issue.tar.gz (487 bytes)
Issue 1:
Hello

As presented here:

http://stackoverflow.com/questions/38454893/error-in-scipy-wilcoxon-signed-rank-test-for-equal-series?noredirect=1#comment64315624_38454893

(without no answer to disprove it as a mistake from me),

I wish to report that maybe there is a problem with the results of scipy.wilcoxon signed rank test;

import scipy as sp

x1=[29.39958, 29.21756, 29.350915, 29.34911, 29.212635]

sp.wilcoxon(x1,x1,zero_method="wilcox",correction=True)

returns statistic=0.0, pvalue=nan

But with zero_method="pratt", it returns statistic=0.0, pvalue=0.043114446783075355 instead.

I think there is a mistake there. The statistics (for z-score, if I am not mistaken) are the same, but the results are different for the p-value, while they should not, actually.

When both series are identical, there should be no good p-value, but this is confident with alpha=0.05.

Maybe "pratt" zero_method is wrongly implemented. It is said to be more conservative, but instead it has also constantly given better /lower p-values on a large array of test values.

edit josef

It looks like there are two issues

corner case when all differences are zero needs special handling to return nan p-value

current implementation of Pratt method is wrong if there are "zeros", if (x == y).sum() > 0

Issue 2:
Hello

As presented here:

http://stackoverflow.com/questions/38454893/error-in-scipy-wilcoxon-signed-rank-test-for-equal-series?noredirect=1#comment64315624_38454893

(without no answer to disprove it as a mistake from me),

I wish to report that maybe there is a problem with the results of scipy.wilcoxon signed rank test;

import scipy as sp

x1=[29.39958, 29.21756, 29.350915, 29.34911, 29.212635]

sp.wilcoxon(x1,x1,zero_method="wilcox",correction=True)

returns statistic=0.0, pvalue=nan

But with zero_method="pratt", it returns statistic=0.0, pvalue=0.043114446783075355 instead.

I think there is a mistake there. The statistics (for z-score, if I am not mistaken) are the same, but the results are different for the p-value, while they should not, actually.

When both series are identical, there should be no good p-value, but this is confident with alpha=0.05.

Maybe "pratt" zero_method is wrongly implemented. It is said to be more conservative, but instead it has also constantly given better /lower p-values on a large array of test values.
Issue 1:
Hi.

I have a big structure data whose content changes dynamicaly, and in which I want to observe tiny variables.

For simplicity I made a code that is triggered on a click, code that call a timeout in order to be sure that all pending works (jquery, vue, and any others) are finished. In this timeout I change a boolean variable associated to a html checkbox.

So far, it seems that the html vue is not correctly updated after change to the model from the timeout call.

Vue.js version

2.1.8

Reproduction Link

In the provided code/example, after a click on the html checkbox a timeout (set to 5s) is called, in which the checkbox variable value is changed.

Here : http://codepen.io/anon/pen/BpaXze

The code:

<script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/vue/2.1.8/vue.min.js"></script>
<div id='test'>
<input v-model='checkbox' type="checkbox" v-on:click="click()">
<BR>
{{checkbox}}
</div>
<script>
var vm = new Vue({
el: '#test',
data: {
checkbox: true
},
methods:{
click: function(){
window.setTimeout(function() {
vm.checkbox = true;
}
, 5000)
}
}
})
</script>

What is Expected?

I expect the checkbox to be updated after setting its value.

What is actually happening?

The variable itself is correctly updated, but not the html checkbox.

Issue 2:
Vue.js version

2.0.1 / 2.0.2

Reproduction Link

https://codepen.io/toxic-johann/pen/yajwRO

Steps to reproduce

use a v-for to render component

in component, you have to write a v-for with template in it but not wrapped with a root element

open console, and run test() function

What is Expected?

open console, and run success() function

What is actually happening?

throw the warning

[Vue warn]: It seems there are duplicate keys that is causing an update error. Make sure each v-for item has a unique key.

and error

Uncaught (in promise) TypeError: Cannot read property 'tag' of undefined

it's the same situation as #3810

However, that one contains only two templates with v-if in nested v-for

And this one contains three templates with v-if

And in my project, i contain with more.

So, i also want to know, if there are more template in nested v-for, will it run good?
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

When I upgraded to version @2.2.0 PrimeNG DataTable RowExpansion is not working any more if the expansion template contains content which utilizes templates (e.g. structural directives).

It was still working in @2.1.2 (you can try in the plunkr above), so I don't think it is related to PrimeNG.

Source of the PrimeNG component: https://github.com/primefaces/primeng/blob/1.0.0-rc.4/components/datatable/datatable.ts

Sorry, but I haven't have time to strip down the problem (and the plunkr) without PrimeNG.

Expected behavior

RowExpansion has the correct template variables set. Should render the template content every time correctly.

Minimal reproduction of the problem with instructions

Check out my plunkr: http://embed.plnkr.co/bJ0ln941VPbUX7KP3Mtk/

Expand the first row: the content is shown correctly. Expand the second row: the content is something different, not reflecting the data content anymore. Any subsequent expansion is not working as expected.

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

Please tell us about your environment:

Angular version: 2.2.0

With the latest 2.2.1 version it fails too. But works with 2.1.2

Browser: Chrome 54 (but I assume it is not related to the browser)

Language: TypeScript 2.0

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

Currently when I try to reuse the same TemplateRef instance for multiple items it renders wrong view

Expected behavior

It should render a separate view inside each view container

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/PZe5XnmJ2KoJ99ts33F9?p=preview

Currently you will see 2 words "Enabled".

Should be "

{ "enabled": true } Enabled

{ "enabled": false } disabled" (as in https://plnkr.co/edit/rZuCs8O7YE4fYplfI3gF?p=preview)

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

I have a slider with hundreds of slides and want to optimise DOM by using lazy DOM creation. For this I need to use template reference. Eventually it's something like this:

<lazy-slides [items]="files">
<template let-file="item">
<preview-file [src]="file.url"></preview-file>
</template>
</lazy-slides>

Then using ngFor and ngTemplateOutlet I put this template for first 5 items and when user slides I change references inside array.

Please tell us about your environment:

npm: 3.9.3

OSX EI Capitan 10.11.5

Atom

Chrome 54.0.2840.98

Angular version: 2.0.X

Reproducible starting from 2.2.0, the same in 2.3.0. Works properly in 2.2.0-rc.0 and older ( https://plnkr.co/edit/rZuCs8O7YE4fYplfI3gF?p=preview )

Browser:

Chrome 54.0.2840.98

Language: all
Issue 1:
TypeScript Version:

Version 1.8.9

The documentation here:

http://www.typescriptlang.org/docs/handbook/compiler-options.html

Lists --traceResolution as a compiler option to which I intended to use to help diagnose errors; however, it appears this was removed or changed names.

Code

tsc -p . --traceResolution

Expected behavior:

I expected this to tell me why my module cannot be found even though it is in the node_modules folder and has package.json with main and typings paths setup correctly.

Actual behavior:

error TS5023: Unknown compiler option 'traceresolution'.

Issue 2:
I am using 1.8 beta. I am also using aurelia framework inside an aspnet5 project. I have configured the module loader, SystemJS, to transpile my TS files. I do *not * want VS to build the TS files. I control this by using a tsconfig.json in the root of the aspnet5 project, which excludes "wwwroot" (along with node_modules, jspm_packages) from compilation. Unfortunately, it appears this also prevents essential flags specified - such as "experimentalDecorators" in this file from being picked up by the language service for excluded folders/files. This gives me annoying red squigglies everywhere complaining that I should specify the flag. If I comment out the wwwroot exlcusion, the squigglies go away.

Therefore, I suggest that the exclude/files directives should only apply to the compiler pass (they are under "compilerOptions" after all,) and not the ambient language service, or you should add a distinct block for controlling the language service flags in tsconfig.json, or even use a separate tsserver.json file. I need support for decorators in intellisense, but I have no intention of using the build process to compile. Make sense?
Issue 1:
Bug Report

I would like to work on a fix!

Current Behavior

A clear and concise description of the behavior.

test fails because of syntaxError

FAIL tests/App.test.js

● Test suite failed to run

SyntaxError: /Users/Jostein/Documents/jobb_Ovitas/projects/hunnor/node_modules/react-native/jest/mockComponent.js: Support for the experimental syntax 'classProperties' i

sn't currently enabled (20:24):

18 |
19 | const Component = class extends SuperClass {
> 20 | static displayName = 'Component';
| ^
21 |
22 | render() {
23 | const name =

Add @babel/plugin-proposal-class-properties (https://git.io/vb4SL) to the 'plugins' section of your Babel config to enable transformation.

Input Code

REPL or Repo link if applicable:

Jest configuration in package.json

"jest": {
"preset": "jest-expo",
"verbose": true,
"transformIgnorePatterns": [
"node_modules/(?!(react-native|my-project|react-native-button)/)"
],
"setupFiles": [
"./setupTests.js"
],
"collectCoverage": true,
"coverageReporters": [
"json",
"html"
]
},

Expected behavior/code

A clear and concise description of what you expected to happen (or code).

expect jest to run test

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

Filename: .babelrc

{
"presets": ["module:metro-react-native-babel-preset", "babel-preset-expo"],
"sourceMaps":true,
"plugins": ["@babel/plugin-proposal-class-properties"]

}

Environment

System:
OS: macOS 10.15.2
Binaries:
Node: 13.6.0 - ~/Documents/jobb_Ovitas/projects/hunnor/node_modules/.bin/node
Yarn: 1.19.2 - /usr/local/bin/yarn
npm: 6.13.6 - /usr/local/bin/npm
npmPackages:
@babel/core: ^7.8.3 => 7.8.3
@babel/plugin-proposal-class-properties: ^7.8.3 => 7.8.3
@babel/polyfill: ^7.8.3 => 7.8.3
@babel/preset-env: ^7.8.3 => 7.8.3
babel-core: ^7.0.0-bridge.0 => 7.0.0-bridge.0
babel-eslint: ^10.0.2 => 10.0.3
babel-jest: ^23.6.0 => 23.6.0
eslint: ^6.0.1 => 6.8.0
jest: ^24.9.0 => 24.9.0
react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4

Babel version(s): [e.g. v6.0.0, v7.0.0-beta.34]

Node/npm version: [e.g. Node 8/npm 5]

OS: [e.g. OSX 10.13.4, Windows 10]

Monorepo: [e.g. yes/no/Lerna]

How you are using Babel: [e.g. cli, register, loader]

Possible Solution

Additional context/Screenshots

Add any other context about the problem here. If applicable, add screenshots to help explain.

Issue 2:
Bug Report

Current Behavior

There are duplicated calls to the assertThisInitialized helper.

let Foo =
/*#__PURE__*/
function (_Bar) {
_inheritsLoose(Foo, _Bar);

function Foo() {
var _this;

_this = _Bar.call(this) || this;
something(_assertThisInitialized(_assertThisInitialized(_this)));
return _this;
}

return Foo;
}(Bar);

Input Code

class Foo extends Bar {
constructor() {
super();
something(this);
}
}

Expected behavior/code

let Foo =
/*#__PURE__*/
function (_Bar) {
_inheritsLoose(Foo, _Bar);

function Foo() {
var _this;

_this = _Bar.call(this) || this;
something(_assertThisInitialized(_this));
return _this;
}

return Foo;
}(Bar);

Environment

Babel version(s): v7.0.0-beta.48

Node/npm version: Node 8

OS: OS X

Monorepo: no

How you are using Babel: core
Issue 1:
When using --emit=dep-info in a makefile, a missing file (due to being renamed or re-factored away) will cause make to terminate the build instantly.

GCC/Clang mitigate this by using the -MP flag when creating dependencies, which emits extra rules of the form dependency: to tell make to ignore the files if they are missing.

Issue 2:
Running something like:

rustc --emit dep-info -o x.o lib.rs

will produce a depfile containing a rule like:

x.o: /path/to/lib.rs /path/to/a.rs /path/to/b.rs

This output has a problem: if a.rs is deleted from the filesystem and dependencies on it erased from lib.rs, then make will attempt to look for a rule to generate a.rs when we request that things be remade. Not finding one, it will helpfully complain that there is no rule to make a.rs and exit.

This can, of course, be worked around by clearing out your entire build directory and starting over, but this seems undesirable.

GCC has an option (-MP) to produce "phony" targets for all the dependencies of the object file; this prevents issues in cases like the above:

x.o: /path/to/lib.rs /path/to/a.rs /path/to/b.rs

/path/to/lib.rs:

/path/to/a.rs:

/path/to/b.rs:

since make now understands how to "generate" a.rs if it doesn't find it.
Issue 1:
it would be nice to have Deno catch any unhandled errors

e.g.

Deno.catch(e) { console.error(e); }

Issue 2:
I was looking for an equivalent to the Node.js "unhandledrejection" event in Deno, but it appears there isn't one on globalThis.

There does appear to be an onunhandledrejection event handler defined on workers, though.

Is there an equivalent event outside of workers, and if not, could there be? 😄
Issue 1:
#3662 is about merging a single-level index with a mi

This is is about a multi-multi merge

# example described there:
In [11]: df = pd.DataFrame(np.random.randn(10,5))
...: df1 = df[range(0, 3)].set_index([0, 2])
...: df2 = df[range(2, 5)].set_index([2, 4])
...: res = df1.join(df2, how='inner') # empty. Do I need to specify something here?
...: exp = pd.DataFrame({1: df[1], 3: df[3]})
...: exp.index = df[2]

Issue 2:
from io import StringIO
csv = r"""Physical\Flows.Solve,9,1,4,0,0,0,0,0,0
1,2,3,4,5,6,7,8,9,10
"""
csv = StringIO(csv)
pd.read_csv(csv, engine='python')

Results in:

Problem description

As can be seen the integer zeros have been cast to non-zero floats!

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.4.final.0
python-bits: 64
OS: Windows
OS-release: 7
machine: AMD64
processor: Intel64 Family 6 Model 62 Stepping 4, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
LOCALE: None.None

pandas: 0.22.0
pytest: 3.3.0
pip: 9.0.1
setuptools: 38.4.0
Cython: 0.27.3
numpy: 1.13.3
scipy: 1.0.0
pyarrow: 0.8.0
xarray: 0.10.0
IPython: 6.2.1
sphinx: 1.6.7
patsy: 0.4.1
dateutil: 2.6.1
pytz: 2017.3
blosc: 1.5.1
bottleneck: 1.2.1
tables: 3.4.2
numexpr: 2.6.4
feather: None
matplotlib: 2.1.2
openpyxl: 2.5.0b1
xlrd: 1.1.0
xlwt: 1.3.0
xlsxwriter: 1.0.2
lxml: 4.1.1
bs4: 4.6.0
html5lib: 0.9999999
sqlalchemy: 1.1.13
pymysql: 0.8.0
psycopg2: None
jinja2: 2.10
s3fs: None
fastparquet: None
pandas_gbq: None
pandas_datareader: None
Issue 1:
Previous problem #13258 seems to have gone away. The new one is:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/resize_nodes.go:546 Expected error: <*errors.errorString | 0xc208128130>: { s: "timed out waiting for the condition", } timed out waiting for the condition not to have occurred

cc @wojtek-t @ixdy @brendandburns @quinton-hoole

Issue 2:
Nodes Network when a minion node becomes unreachable [replication controller] recreates pods scheduled on the unreachable minion node AND allows scheduling of pods on a minion after it rejoins the cluster(Failed 17 times in the last 30 runs. Stability: 43 %)Failed with 0 retries
Issue 1:
System info

Playwright Version: [v1.32.3]

Operating System: [macOS 13.2.1]

Browser: [Chromium]

Command: docker run --ipc=host --rm --network host -v $(pwd):/work/ -w /work/ -it mcr.microsoft.com/playwright:v1.32.3-focal /bin/bash & npx playwright test

Config file

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'], },
},
});

Test file (self-contained)

it('should have a screenshot name ending with linux when running with the docker image mcr.microsoft.com/playwright:v1.32.3-focal', async ({ page }) => {
await expect(await page).toHaveScreenshot('test.png');
});

Expected

test-chromium-linux.png

Actual

test-chromium-darwin.png

Issue 2:
System info

Playwright Version: "@playwright/test": "^1.31.2"

Operating System: [Windows 10.]

Browser: [WebKit]

Source code

[X ] I provided exact source code that allows reproducing the issue locally.

Config file

// browser.test.ts
import { test } from "@playwright/test";

test("test browser", async ({ page }) => {
// point this to wherever you want
await page.goto("http://localhost:4200/");

// keep browser open
await page.pause();
});

**Steps**
- Run command: npx playwright test --headed --browser=webkit
- [...]

**Expected**

[Describe expected behavior]

**Actual**
![image](https://user-images.githubusercontent.com/108359768/224100947-6b557ef0-d1a1-4c20-8567-76edef5343fd.png)

[Describe actual behavior]
Issue 1:
requests 2.14+ centos7 py27

omeroweb_1 | Running setup.py egg_info for package requests
omeroweb_1 | error in requests setup command: Invalid environment marker: platform_system == "Windows" and python_version<"3.3"
omeroweb_1 | Complete output from command python setup.py egg_info:
omeroweb_1 | error in requests setup command: Invalid environment marker: platform_system == "Windows" and python_version<"3.3"

Issue 2:
Example with pip 6.1.1 (but same with pip 8.1.1):

> pip install requests
You are using pip version 6.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting requests
Using cached requests-2.14.0-py2.py3-none-any.whl
Exception:
Traceback (most recent call last):
File "D:\VEnvs\testpip\lib\site-packages\pip\basecommand.py", line 246, in main
status = self.run(options, args)
File "D:\VEnvs\testpip\lib\site-packages\pip\commands\install.py", line 342, in run
requirement_set.prepare_files(finder)
File "D:\VEnvs\testpip\lib\site-packages\pip\req\req_set.py", line 345, in prepare_files
functools.partial(self._prepare_file, finder))
File "D:\VEnvs\testpip\lib\site-packages\pip\req\req_set.py", line 290, in _walk_req_to_install
more_reqs = handler(req_to_install)
File "D:\VEnvs\testpip\lib\site-packages\pip\req\req_set.py", line 557, in _prepare_file
set(req_to_install.extras) - set(dist.extras)
File "D:\VEnvs\testpip\lib\site-packages\pip\_vendor\pkg_resources\__init__.py", line 2758, in extras
return [dep for dep in self._dep_map if dep]
File "D:\VEnvs\testpip\lib\site-packages\pip\_vendor\pkg_resources\__init__.py", line 2781, in _dep_map
self.__dep_map = self._compute_dependencies()
File "D:\VEnvs\testpip\lib\site-packages\pip\_vendor\pkg_resources\__init__.py", line 2814, in _compute_dependencies
common = frozenset(reqs_for_extra(None))
File "D:\VEnvs\testpip\lib\site-packages\pip\_vendor\pkg_resources\__init__.py", line 2811, in reqs_for_extra
if req.marker_fn(override={'extra':extra}):
File "D:\VEnvs\testpip\lib\site-packages\pip\_vendor\_markerlib\markers.py", line 113, in marker_fn
return eval(compiled_marker, environment)
File "<environment marker>", line 1, in <module>
NameError: name 'platform_system' is not defined

So, installing requests 2.14.0 implicitly requires pip >= 9.x. Should be at least in the release note as a disclaimer, or be fixed if it's not on purpose.
Issue 1:
From @kuza55 on 2016-06-30T17:33:27Z

ISSUE TYPE

Bug Report

COMPONENT NAME

ec2 module

ANSIBLE VERSION

$ ansible --version

ansible 2.1.0.0

config file = /etc/ansible/ansible.cfg

configured module search path = Default w/o overrides

OS / ENVIRONMENT

Ubuntu on Windows 10

SUMMARY

Changing the group_id value for a running instance has no effect on it's security groups

STEPS TO REPRODUCE

Run playbook that creates ec2 instance

Add extra group_id to playbook

Run playbook again

EXPECTED RESULTS

ec2 instance is in both security groups

ACTUAL RESULTS

security group of instance is not changed.

Copied from original issue: ansible/ansible-modules-core#4083

Issue 2:
Issue Type:

Feature Idea

Component Name:

ec2 module

Ansible Version:

ansible 1.8.1

Environment:

N/A

Summary:

I did not find a way to change EC2 Security Groups on an existing instance. It is possible to define the groups when creating a new instance with the "ec2" module, but nto to alter, add or remove groups on an existing instance.

Rationale: I create an instance with a limited set of security groups, so that the software cannot connect to the server yet during provisioning. Then I provision the host, and at the end I want to add a security group so that the host can start connecting to the server and process work.

Steps To Reproduce:

N/A

Expected Results:

Being able to:

Add security groups to an existing EC2 instance

Remove security groups from an existing EC2 instance

Overwrite the security groups on an existing EC2 instance

Actual Results:

N/A