WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Version

2.6.11

Reproduction link

https://github.com/TrueCarry/linktest

Steps to reproduce

What is expected?

What is actually happening?

This is a duplicate of #1176, can we reopen it please?

Issue 2:
What problem does this feature solve?

See @click="doSomething('params')", the generated code will be function($event){doSomething('params')}, no return in it. Normal syntax with method name only has the return. So I think consistent may be better.

And the use case is child component may want to manually call the event handler to get the result, not through this.$emit

What does the proposed API look like?

No added api
Issue 1:
Code Sample

import pandas as pd
import numpy as np

arrays = [['bar', 'bar', 'baz', 'baz', 'foo', 'foo', 'qux', 'qux'], ['one',
'two', 'one', 'two', 'one', 'two', 'one', 'two']]

tuples = list(zip(*arrays))
index = pd.MultiIndex.from_tuples(tuples, names=['first', 'second'])
series = pd.Series(np.random.randn(8), index=index)

print(series.to_json())

Output:

{"["bar","one"]":-0.0591166327,"["bar","two"]":0.871145093,"["baz","one"]":0.61280938,"["baz","two"]":0.3848564991,"["foo","one"]":-0.8986592304,"["foo","two"]":-0.4631529084,"["qux","one"]":-1.3482521044,"["qux","two"]":0.5209236198}

Problem description

The output contains unescaped quotation marks, which makes the output invalid json.

Expected Output

Quote marks should be escaped, for example:

{"[\"bar\",\"one\"]":-0.0591166327,"[\"bar\",\"two\"]":0.871145093,"[\"baz\",\"one\"]":0.61280938,"[\"baz\",\"two\"]":0.3848564991,"[\"foo\",\"one\"]":-0.8986592304,"[\"foo\",\"two\"]":-0.4631529084,"[\"qux\",\"one\"]":-1.3482521044,"[\"qux\",\"two\"]":0.5209236198}

Output of pd.show_versions()

I reproduced it in pandas install from master:

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.0.final.0
python-bits: 64
OS: Linux
OS-release: 4.8.8-200.fc24.x86_64
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_AU.UTF-8
LOCALE: en_AU.UTF-8

pandas: 0.19.0+401.g8452080

nose: None

pip: 9.0.1

setuptools: 27.2.0

Cython: 0.25.2

numpy: 1.12.0

scipy: None

statsmodels: None

xarray: None

IPython: None

sphinx: None

patsy: None

dateutil: 2.6.0

pytz: 2016.10

blosc: None

bottleneck: None

tables: None

numexpr: None

feather: None

matplotlib: None

openpyxl: None

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: None

httplib2: None

apiclient: None

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: None

s3fs: None

pandas_datareader: None

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

import pandas as pd
import datetime

pd.read_json(pd.DataFrame(True, index=pd.date_range(datetime.date(2017, 1, 20), datetime.date(2017, 1, 23)), columns=['foo', 'bar']).stack().to_json())

Problem description

The result of pd.DataFrame(True, index=pd.date_range(datetime.date(2017, 1, 20), datetime.date(2017, 1, 23)), columns=['foo', 'bar']).stack().to_json() contains

r'{"[1484870400000,"foo"]":true,"[1484870400000,"bar"]"',

Expected Output

Whereas it should be:

r'{"[1484870400000,\"foo\"]":true,"[1484870400000,\"bar\"]"'

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.4.5.final.0
python-bits: 32
OS: Windows
machine: AMD64
LC_ALL: None
LANG: None
LOCALE: None.None

pandas: 0.19.1

Cython: 0.25.1

numpy: 1.11.2

pandas_datareader: None
Issue 1:
When using a multi-line text field with full width the field isn't full width.

Regression of #8835 (#8825)

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

Expected Behavior

The textfield / textarea should be full width.

Current Behavior

The textfield / textarea is not full width.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/l5on3rjokl

Input field should be full width.

Context

Works in beta 18

Culprit is this change https://github.com/callemall/material-ui/pull/8835/files#diff-deaeb5c7e253bfa4f497fa8ace0b3607R67

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.19

React
15

browser
Chrome 62

Issue 2:
The <Input /> and <TextField /> component's props: spellcheck and lang should be set on the input and textfield respectively

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

Expected Behavior

I would expect that spellcheck and lang props propagates down to the input or textfield elements within the respective components.

Rendered expected html looks something like this(Simplified):

<div class="mui-root" >
<div class="muiTextArea-root">
<textarea spellcheck=true lang="nn"/>
</div>
<div/>

Current Behavior

Currently when rendered the props are set on the wrapper when using <Input /> or <TextField /> . The props are not set on the input or textfield element.

Rendered html:

<div class="mui-root" spellcheck=true lang="nn">
<div class="muiTextArea-root">
<textarea />
</div>
<div/>

Steps to Reproduce (for bugs)

Test the html in IE: https://codepen.io/doff3n/pen/xPqgGR You may need to paste the text again

This is what I used:

<Input
spellCheck={true}
lang={language}
multiline
fullWidth={true}
value={this.state.text}
onChange={this.handleChangeText}
/>

Context

I am implementing a spellchecker where you should be able to switch between different spellchecking languages, In norway we have two different official written languages. It should also be possible to turn off the spellcheck. In chrome the value is inherited as according to spec. A solution where I could set the props directly on the input element would work for me, or that the props are inherited down to the element.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.17

React
16.0.0

browser
IE11
Issue 1:
I am trying to load my web application to electron. But many of my application functions are not working in electron. Major problem is dropdown lists are not showing up. I tried loading with window.loadurl and also using webview in index.html.

Electron version: 1.7.9

Operating system: Windows 10

Expected behavior

I like to get my web application with full functionalities working in electron

Actual behavior

Many jquery functions not working. Dropdowns not showing up...

How to reproduce

My current html is:

<html>
<head>
<title>jQuery injection into webview preload</title>
</head>
<body style="overflow:hidden;">
<webview id="webview" preload="./preload.js" src="http://www.mcgeoautomation.com" style="position:absolute;width:100%;height:100%;"></webview>
<script>
// need to have a script tag make webview work even if you don't plan to use it...
</script>
</body>
</html>

Preload.js is:

var script = document.createElement("script");
script.src = "./jquery.min.js";
document.body.appendChild(script);
};

index.js is:

const app = electron.app;
var path=require('path');
const BrowserWindow = electron.BrowserWindow;
var mainWindow;

app.on('ready',function(){
mainWindow = new BrowserWindow({
width: 1024,
height: 768,
backgroundColor: '#2e2c29',
show:false,
});

mainWindow.loadURL(`file://${__dirname}/webView.html`);
mainWindow.maximize(true);
mainWindow.once('ready-to-show',()=>{
mainWindow.show()
})

mainWindow.on('close', (e)=>{

app.quit();
});
});

Package json:

"name": "crushmate",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"start": "electron ."
},
"author": "",
"license": "ISC",
"dependencies": {
"electron": "^1.7.9",
"jquery": "^3.2.1"
},
"devDependencies": {
"electron-prebuilt": "^1.4.13"
}
}

Please help....

Regards

Issue 2:
Electron version: 1.7.3 beta

Operating system: Windows 7 x86_64 Professional

Clicking the pyramid icon on an input control associated with a data list and picking a value from the list, then evaluating value property of the input control, the value is expected to match the text chosen from the data list, which the input control is now showing.

Instead, the text returned by value property is an empty string, or at least the string that was manually typed into the input control prior.

Only manual editing of value of the input control, as you would with an ordinary text input without a n associated datalist, causes the value property to yield the same text that the input control is showing.

Using following markup to reproduce by loading up default Electron distribution and typing document.location = ...; /* path to file containing below text */ in Developer Tools console:

<!DOCTYPE html>
<html>
<body>
<input list="foobar">
<datalist id="foobar">
<option value="apple">
<option value="orange">
<option value="banana">
</datalist>
</body>
</html>
Issue 1:
Issue originally made by @zyy7259

Bug information

Babel version: 6.10.4

Node version: 5.10.1

npm version: 3.8.3

Options

query: {
presets: ['es2015'],
cacheDirectory: true,
plugins: [
'transform-es3-property-literals',
'transform-es3-member-expression-literals',
["transform-es2015-modules-commonjs", {
"loose": true
}]
]
}

Input code

export * from './mixin'

Description

The doc says:

In environments that don’t support this you can enable loose mode on es6.modules and instead of using Object.defineProperty an assignment will be used instead.

But it only works for the __esModule property.

Without loose, the output is:

Object.defineProperty(exports, "__esModule", {
value: true
});

With loose, the output is:

exports.__esModule = true;

But when I re-export a module

export * from './mixin'

The output is (with or without the loose option):

Object.keys(_mixin).forEach(function (key) {
if (key === "default") return;
Object.defineProperty(exports, key, {
enumerable: true,
get: function get() {
return _mixin[key];
}
});
});

Which will break on IE8

Issue 2:
Issue originally made by @timdorr

Bug information

Babel version: 6.7.7

Node version: 5.5.0

npm version: 3.8.7

Options

{
"presets": ["es2015-loose", "stage-1", "react"],
"plugins": [
"transform-es3-member-expression-literals",
"transform-es3-property-literals"
]
}

Input code

export { foo, bar } from './baz'

Description

Apologies if this has been discussed before. T2322 is tangentially related and fixed by add-module-exports.

When using the above input code, you get something like this as output:

var _baz = require('./baz');

Object.defineProperty(exports, 'foo', {
enumerable: true,
get: function get() {
return _baz.foo;
}
});
Object.defineProperty(exports, 'bar', {
enumerable: true,
get: function get() {
return _baz.bar;
}
});

While core-js/babel-polyfill can add in defineProperty support, it cannot do getters. I'm not sure why defineProperty is used, so pardon my ignorance if I'm missing something super-obvious. But can't a simple property assignment be used instead? It's enumerable anyways, so I'm not sure of the practical difference.

It appears the code template remains untouched since the original 6.0.0 release, so perhaps it needs to be touched up a bit? I'm happy to submit a PR.
Issue 1:
Test case:

trait T<X> { }

fn foo<I:T<&'self int>>() { }

fn main() { }

Transcript:

% RUST_LOG=rustc=1 rustc --version
/Users/pnkfelix/opt/rust-dbg/bin/rustc 0.8-pre (dd5c737 2013-09-08 12:05:55 -0700)
host: x86_64-apple-darwin
% RUST_LOG=rustc=1 rustc /tmp/baz.rs
task <unnamed> failed at 'assertion failed: rp.is_none()', /Users/pnkfelix/Dev/Mozilla/rust.git/src/librustc/middle/typeck/collect.rs:1108
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=1 to get further details and report the results to github.com/mozilla/rust/issues
task <unnamed> failed at 'explicit failure', /Users/pnkfelix/Dev/Mozilla/rust.git/src/librustc/rustc.rs:376

Issue 2:
Compile:

// Example #1
mod mod_a {
mod sub_a {
pub struct InnerA;
}
pub type A = sub_a::InnerA;
}

use mod_a::A;

fn main() {
let a=A;
}

error[E0425]: unresolved name `A`
--> test.rs:12:11
|
12 | let a=A;
| ^ unresolved name

Yet A is quite obviously imported. The same error appears in a different place when compiling:

// Example #2
mod mod_a {
mod sub_a {
pub struct InnerA;
}
pub type A = sub_a::InnerA;

pub fn make_a() -> A {
A
}
}

use mod_a::{A,make_a};

fn main() {
let a: A=make_a();
}

error[E0425]: unresolved name `A`
--> test.rs:9:9
|
9 | A
| ^ unresolved name

This compiles:

// Example #3
mod mod_a {
mod sub_a {
pub struct InnerA;
}
pub type A = sub_a::InnerA;

pub fn make_a() -> A {
sub_a::InnerA
}
}

use mod_a::{A,make_a};

fn main() {
let a: A=make_a();
}

But wait, I thought in example no. 1, we couldn't resolve A from main()?

Using pub use instead makes example no. 1 work:

// Example #4
mod mod_a {
mod sub_a {
pub struct InnerA;
}
pub use self::sub_a::InnerA as A;
}

use mod_a::A;

fn main() {
let a=A;
}

For completeness, here is the tuple-struct version:

// Example #5
mod mod_a {
mod sub_a {
pub struct InnerA(pub u8);
}
pub type A = sub_a::InnerA;
}

use mod_a::A;

fn main() {
let a=A(0);
}

error[E0425]: unresolved name `A`
--> test.rs:12:11
|
12 | let a=A(0);
| ^ unresolved name

And the regular struct version (compiles without errors):

// Example #6
mod mod_a {
mod sub_a {
pub struct InnerA {pub i:u8}
}
pub type A = sub_a::InnerA;
}

use mod_a::A;

fn main() {
let a=A{i:0};
}

It seems like structure expressionsconstructors are handled differently from other uses of types with regards to aliases. Also, the phrase pub type does not appear in the Rust Book or the Rust Reference.

I propose the following:

Improve the error message in cases 1, 2 and 5 above

Improve documentation on public type aliases

Improve documentation on structure expressionsconstructors involving type aliases
Issue 1:
Can not be run properly because when broken output of --module system.

Version of tsc problems occur 1.7.5 and 1.8.0.

// bug.ts
export var test = false;

if (!test) {
test = false;
}

tsc --module system bug.ts

// bug.js
System.register([], function(exports_1) {
var test;
return {
setters:[],
execute: function() {
exports_1("test", test = false);
if (exports_1("test", !test)) { // <- broken output
exports_1("test", test = false); // <- broken output
}
}
}
});

Issue 2:
Don't understand why this code:

import { enableProdMode } from 'angular2/core';

export var DEBUG: boolean = false;

if (!DEBUG) {
enableProdMode();
}

Transpiles to this one, which in fact makes DEBUG to be true at the end! (tried also with export const DEBUG: boolean = false; with exactly the same result)

System.register(['angular2/core'], function(exports_1) {
var core_1;
var DEBUG;
return {
setters:[
function (core_1_1) {
core_1 = core_1_1;
}],
execute: function() {
exports_1("DEBUG", DEBUG = false);
if (exports_1("DEBUG", !DEBUG)) {
core_1.enableProdMode();
}
}
}
});

And this one:

import { enableProdMode } from 'angular2/core';

export var DEBUG: boolean = false;

if (DEBUG == false) {
enableProdMode();
}

Transpiles to this one which is the correct one:

System.register(['angular2/core'], function(exports_1) {
var core_1;
var DEBUG;
return {
setters:[
function (core_1_1) {
core_1 = core_1_1;
}],
execute: function() {
exports_1("DEBUG", DEBUG = false);
if (DEBUG == false) {
core_1.enableProdMode();
}
}
}
});

Here are my typescript options (gulp-typescript):

var tsOptions = {
outDir: PATHS.outDir,
target: "ES5",
module: "system",
moduleResolution: "node",
sourceMap: false,
emitDecoratorMetadata: true,
experimentalDecorators: true,
removeComments: true,
noImplicitAny: false,
noExternalResolve: true
};
Issue 1:
I'm using bootstrap v2.3.0, when I am using data-backdrop="static" in html and using javascript modal('hide') to hide the modal, the javascript occured error:

Uncaught TypeError: Cannot call method 'remove' of undefined bootstrap.min.js:6

Below is my solution:

change:

removeBackdrop: function () {

this.$backdrop.remove()

this.$backdrop = null

}

to:

removeBackdrop: function () {

if(this.$backdrop){

this.$backdrop.remove()

this.$backdrop = null

}

}

Thanks guys.

Issue 2:
With options { backdrop: false }, this.$backdrop.remove() is still being called which results in an exception as this.$backdrop is null.

hideModal: function () {
var that = this
this.$element.hide()
this.backdrop(function () {
that.removeBackdrop()
that.$element.trigger('hidden')
})
}

removeBackdrop: function () {
this.$backdrop.remove()
this.$backdrop = null
}
Issue 1:
Output of node_modules/.bin/electron --version: 3.0.0-beta.8

Operating System (Platform and Version): Mac OSX Mojave

Expected Behavior

There should be an option to accept mouse events when a window is unfocused.

Actual behavior

WIndows don't accept any hover CSS states or events while unfocused.

Additional Information

I know about this ticket: #2797, but it was already closed and I'm not sure why. It's actually a requirement for desktop apps that want to feel native, as electron hopes to provide.

I understand this would need to be enabled in Chromium, hoping to hear if there's been any progress here, perhaps the latest builds enable it, or even just tips on where to look to make these changes.

Issue 2:
Repro:

Add something with a hover style in CSS

Focus another window

Hover over the unfocused Electron window

Usually the hover style will be seen for a split second before disappearing

This sounds like a small thing, and it is - but it's actually quite frustrating in our particular UI as we have buttons that appear on hover which you accidentally click when focusing. It also looks buggy as the hover style visually flashes.

Note: On Windows this works as expected, showing the hover styles in the Electron window continuously even when unfocused.
Issue 1:
Leoš Bitto opened SPR-5610 and commented

It would be nice if Spring Framework would reject any Map or Set which contain duplicate entries by throwing some exception. It would be perfect if that could be the default behaviour with the upcoming version 3.0, and optional in the currect versions 2.x (where it could be too disruptive if made default). There are two main reasons: First is that the current behaviour, which tolerates duplicates, can easily cover a configuration mistake (consider especially Map with more entries with the same key and different values). Second is that if the used Map or Set implementation is order-preserving, it is unclear how are the duplicates going to be ordered.

Affects: 2.5.6, 3.0 M2

Reference URL: http://forum.springsource.org/showthread.php?p=233277

Issue 2:
Tomasz Blachowicz opened SPR-7972 and commented

Currently the PUT methods on RestTemplate are void. I'm aware that in typical scenarios PUT does not return any value, but there are some cases where methods putForObject and/or putForEntity are required.

Prime example is connectivity with Apache CouchDB that return revision number of the document when updating the document using PUT method.

More details can be seen here: http://wiki.apache.org/couchdb/HTTP_Document_API#PUT

Affects: 3.0.5

Issue Links:

#15256 Please add a putForEntity and a putForLocation method to RestTemplate ("duplicates")

#15256 Please add a putForEntity and a putForLocation method to RestTemplate ("is duplicated by")

3 votes, 5 watchers
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

Some code does not show due to bad filename/path.

Expected/desired behavior

Example code shown

Reproduction of the problem

Go to https://angular.io/docs/ts/latest/tutorial/toh-pt6.html

What is the expected behavior?

Shown code

Please tell us about your environment:

Chrome 52.0.2743.116 (64 bit)

Issue 2:
A number of snippet links from the Angular2 tour of heroes page https://angular.io/docs/ts/latest/tutorial/toh-pt6.html are broken. For example:

app/hero.service.ts (post)

BAD FILENAME: ../../../_fragments/toh-6/ts/app/hero.service-post.ts.md Current path: docs,ts,latest,tutorial,toh-pt6 PathToDocs: ../../../

I raised this initially as angular/angular#11127, but then Eric Martinez asked me to raise it in this issues repo. I noted an issues like this were previously opened and closed in the same angular issues repo - search issues for "BAD FILENAME".
Issue 1:
As noticed here: https://circleci.com/gh/pytorch/pytorch/219276?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link/console

cc: @goldsborough

Nov 11 02:46:56 [ FAILED ] 1 test, listed below:
Nov 11 02:46:56 [ FAILED ] DataLoaderTest.EnforcesOrderingAmongThreadsWhenConfigured
Nov 11 02:46:56
Nov 11 02:46:56 1 FAILED TEST
Nov 11 02:46:56 + cleanup

Issue 2:
I got this on my PR which is unrelated with C++ dataloader:

Nov 06 19:49:10 [ RUN ] DataLoaderTest.EnforcesOrderingAmongThreadsWhenConfigured
Nov 06 19:49:10 /var/lib/jenkins/workspace/test/cpp/api/dataloader.cpp:864: Failure
Nov 06 19:49:10 Expected equality of these values:
Nov 06 19:49:10 value
Nov 06 19:49:10 Which is: 1
Nov 06 19:49:10 index++
Nov 06 19:49:10 Which is: 0
Nov 06 19:49:10 [ FAILED ] DataLoaderTest.EnforcesOrderingAmongThreadsWhenConfigured (1 ms)

log: https://circleci.com/gh/pytorch/pytorch/190910

cc @goldsborough
Issue 1:
Version

2.6.10

Reproduction link

https://codesandbox.io/s/vue-template-7x6nl

Steps to reproduce

Use v-slot directive with "is" attribute

What is expected?

similar behavior with the old syntax of slots

What is actually happening?

scoped slot not working with dynamic component

Issue 2:
What problem does this feature solve?

When using mapGetters from vuex it would be nice to be able to provide the store namespace from a prop.

The use case for us is, that we have several store modules whose interfaces basically look the same. If we could provide the store namespace as a prop we could rely on that interface from a specific component without having to duplicate the mapGetters calls in all parent components that use the component.

What does the proposed API look like?

computed: {
...mapGetters(this.storeNamespace, {'item': 'myGetter' })
}

See the following Codepen for a full example:

https://codepen.io/dmnk_bln/pen/yMvpLq/
Issue 1:
There should be a clear mention if the tooltip (and also for other components) can be activated just by including the corresponding css attribute on the element and including the v3 js file, or it does need to be called from a js file of the page.

Issue 2:
The v2.3.2 docs had the following notice, which is missing from the new docs yet is still applicable AFAICT:

For performance reasons, the tooltip and popover data-apis are opt in, meaning you must initialize them yourself.
Issue 1:
When an accented character (e.g. åäö, but probably other unicode characters as well) is used in a file name the git implementation in Atom on OS X thinks that the file is new, even though it exists on github. You can test with this repo (small, markdown files only):

git clone https://github.com/morberg/recept.git

Open root folder in atom and look at the incorrect status in the left tree navigation.

Problem is seen with Atom 0.158.0 on OS X 10.10.1:

Problem is not seen with Atom 0.158.0 on Windows 7 SP 1.

Issue 2:
Halp ticket:

support/6c407d52c9f711e38a0cc47a4027f259

Git support does not handle files with accented characters correctly, declaring them as new. See e.g spec/fixtures/subdir/áccéntéd.svg in atom/markdown-preview or lloeki/svg-preview plugins.

Steps to reproduce:

$ git clone https://github.com/lloeki/svg-preview
$ cd svg-preview
$ atom .

Notice that there's a file marked as new in the tree view -- spec/fixtures/subdir/áccéntéd.svg.

However, I can't reproduce this issue with the markdown-preview repository which has a file with the same name.