WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

![image](https://user-images.githubusercontent.com/16064908/55133199-cdeb3e80-515f-11e9-8434-7fe364b1187b.png)
links are 404 in README

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.4.1

Operating System version: macOS

Java version: 1.8

Steps to reproduce this issue

使用 GenericService 进行泛化调用

提供者provider不可用

吞噬抛出的异常并循环继续尝试调用（不重启）

` ReferenceConfig reference = new ReferenceConfig<>();

reference.setApplication(this.applicationConfig);

reference.setRegistry(this.registryConfig);

// 接口名

reference.setInterface(interfaceClass);

// 声明为泛化接口

reference.setGeneric(true);

//禁用重试,避免某些场景产生重复数据调用

reference.setRetries(0);

ReferenceConfigCache cache = ReferenceConfigCache.getCache();
while (true) {
try {

GenericService genericService = cache.get(reference);
genericService.$invoke(methodName, paramClassPath, params);
Thread.sleep(10);

} catch (Exception e) {
e.printStackTrace();
}
}`

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

1，消费者成功注册；

2，打印异常并继续尝试调用；

3，消费者注册节点不增加；

Actual Result

1，消费者成功注册；

2，打印异常并且继续尝试调用；

3，消费者注册节点随着尝试次数的增加而增加并且无上限；

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:
web-workers/worker/application_common.ts duplicates a lot of code from core/application_common.ts. It's primarily duplicating DI bindings. I talked to @vsavkin about this today and the current plan is to move all the export all the bindings that the webworker needs to a separate file and import that file in both core/application_common.ts and web-workers/worker/application_common.ts

Issue 2:
Hello.

I have the code http://plnkr.co/edit/PNMu9bYdcH8HUNQOSKTn on angular 1.x

and I try to do the same on angular 2 - http://plnkr.co/edit/Yx51PogyCQXYE8bKM65l

but it doesn't work on angular2

maybe I made mistake?
Issue 1:
See the behavior on this fiddle when you click the button to change the state of a item: http://jsfiddle.net/oe7axeab/30/

Issue 2:
I can't find a nice way for a parent to retrieve values from child models created with v-repeat, as shown at http://jsfiddle.net/bdaglish/W9xcP/13/ . All values are set initially, but subsequent changes in the input aren't reflected in the parent.

Ideally, I'd like the first example to work, looping through a one set of keys, but binding to another object. As you can see, I have a temporary workaround, but it's not very satisfactory!
Issue 1:
When targeting ES6 with the new typescript 1.5.3, the es6-promise definitions referenced in angular2.d.ts conflict with the promise definition built in to the es6 library definitions, giving a duplicate identifier error:

$ tsc
/usr/local/lib/node_modules/typescript/bin/lib.es6.d.ts(4775,11): error TS2300: Duplicate identifier 'Promise'.
/usr/local/lib/node_modules/typescript/bin/lib.es6.d.ts(4855,13): error TS2300: Duplicate identifier 'Promise'.
typings/es6-promise/es6-promise.d.ts(11,15): error TS2300: Duplicate identifier 'Promise'.
typings/es6-promise/es6-promise.d.ts(42,16): error TS2300: Duplicate identifier 'Promise'.

If I remove the reference to es6-promise.d.ts in angular2.d.ts, everything compiles fine. I don't know what the best way is to handle situations like this, but perhaps having a separate angular2-es6.d.ts would work. This would basically be the existing definitions, without the reference to es6-promise. angular2.d.ts would then just reference es6-promise and angular2-es6.

Issue 2:
Hi @ericanderson

I'm having many problems with this change when used in practice:

Problem 1: Go To Definition

When you press Go To Definition on a property of props or state, Typescript is not able to resolve it.

interface MyComponentProps {
name: string;
}

export abstract class MyComponent extends React.Component<MyComponentProps , void> {
myMethood() {
this.props.name; //<-- Go To definition in name
}
}

Makes sense because the member is synthetically generated, but is annoying anyway.

Problem 2: Hierarchies of components (Generic P with constraints)

More important, if you make abstract component like this:

interface MyBaseProps {
onChange?: (val: any) => void;
}

export abstract class MyBase<P extends MyBaseProps> extends React.Component<P, void> {
myMethood() {
this.props.onChange!(2); //The type is S["onChange"] instead of (val: any) => void and so is not invocable.
}
}

TS is able to show that there is a property onChange, but sometimes can not discover his type.

This is the most important change since if prevents me to have hierarchies of components that share common props and functionality. It looks like a problem in TS compiler but until it's fixed.

Problem 3: Not so Readonly.

While I agree that this change captures well the functional intent of React, there are valid situations where you can modify the state imperatively, like in the constructor, and also if you change the state and call forceUpdate everithing works OK.

this.state.name = "John";
this.forceUpdate(); //Ok as long as you don't setState afterwards, but calling setState also is annoying with the callback.

Is it recomended? No.

Is it forbidden? Also not, otherwise forceUpdate won't exist.

Of course you could cast the state to S (or any) and make the change, but if it's a common pattern gets cumbersome.

Conclusion: Is it worth?

I feel sad that the new shiny feature of TS makes more problems than solutions in this case, but I honestly think this is the case here.

On the other side, the change of setState is great 👍 , didn't know about Pick<S,K>.
Issue 1:
@inline function f(A, I)
@boundscheck checkbounds(A, I)
@inbounds A[I]
end
g(A, I) = @inbounds f(A, I)

On 0.7-beta2 @code_typed g(ones(1), 1) will contain a checkbounds call.

cc: @mbauman

Issue 2:
It would be nice to be able to remove more dead code in the julia-level optimizer. Example case:

julia> function f(A)
@inbounds for I in 1:length(A)
view(A, I)
end
end
f (generic function with 1 method)

julia> @code_typed f([1])
CodeInfo(
2 1 ── %1 = Base.arraylen(%%A)::Int64 │╻ length
│ %2 = Base.sle_int(1, %1)::Bool ││╻╷╷╷ Type
│ Base.sub_int(%1, 1) │││╻ unitrange_last
│ %4 = Base.ifelse(%2, %1, 0)::Int64 ││││
│ %5 = Base.slt_int(%4, 1)::Bool ││╻╷╷ isempty
└─── goto 3 if not %5 ││
2 ── goto 4 ││
3 ── goto 4 ││
4 ┄─ %9 = φ (2 => true, 3 => false)::Bool │
│ %10 = φ (3 => 1)::Int64 │
│ %11 = φ (3 => 1)::Int64 │
│ %12 = Base.not_int(%9)::Bool │
└─── goto 16 if not %12 │
5 ┄─ %14 = φ (4 => %10, 15 => %35)::Int64 │
│ %15 = φ (4 => %11, 15 => %36)::Int64 │
3 └─── goto 10 if not false │╻ view
6 ── %17 = Core.tuple(%14)::Tuple{Int64} ││
│ %18 = Base.arraysize(%%A, 1)::Int64 ││╻╷╷╷╷ checkbounds
│ %19 = Base.slt_int(%18, 0)::Bool │││╻╷╷╷ checkbounds
│ %20 = Base.ifelse(%19, 0, %18)::Int64 ││││┃││││││ eachindex
│ %21 = Base.sle_int(1, %14)::Bool │││││╻ <=
│ %22 = Base.sle_int(%14, %20)::Bool ││││││
│ %23 = Base.and_int(%21, %22)::Bool │││││╻ &
└─── goto 8 if not %23 │││
7 ── goto 9 │││
8 ── invoke Base.throw_boundserror(%%A::Array{Int64,1}, %17::Tuple{Int64})
└─── unreachable │││
9 ── nothing │
10 ┄ goto 11 │╻ view
11 ─ %30 = Base.:===(%15, %4)::Bool ││╻ ==
└─── goto 13 if not %30 ││
12 ─ goto 14 ││
13 ─ %33 = Base.add_int(%15, 1)::Int64 ││╻ +
└─── goto 14 │╻ iterate
14 ┄ %35 = φ (13 => %33)::Int64 │
│ %36 = φ (13 => %33)::Int64 │
│ %37 = φ (12 => true, 13 => false)::Bool │
│ %38 = Base.not_int(%37)::Bool │
└─── goto 16 if not %38 │
15 ─ goto 5 │
16 ┄ return nothing │
) => Nothing

In this IR there are a couple redundant basic blocks (consisting only of a goto to the next block). There is also unreachable bounds error code (goto 10 if not false). LLVM can remove this code very easily, but it would still be useful for us to remove it (1) to cut down stored IR size, (2) for inlining heuristics, and (3) to spend less time lowering to LLVM.
Issue 1:
Neo4j Version: 2.3.1

Operating System: Ubuntu 14.10

Steps to reproduce

Creating a collection of collections, e.g.

Collect([TOINT(idn),STR(name),TOINT(status),TOINT(days_norm),TOINT(days_spent)]) as flowsteps

and later on adding up corresponding items

REDUCE (x=0, i IN flowsteps | x + TOINT(STRING(i[3]))) as normP

throws an error

Cypher error: Type mismatch: expected Float, Integer or String but was Any (line 33, column 57 (offset: 1271)) " REDUCE (x=0, i IN flowsteps | x + TOINT(TOSTRING(i[3]))) as normP

Expected behavior

If I cast something WITH TOINT(), then this should work:

REDUCE (x=0, i IN flowsteps | x + i[3]) as normP

Actual behavior

Only works with a workaround by TOINT(STR()), which is no longer works in 3.0, because STR() is no longer available.

Issue 2:
Hi,

We coding a program for make an import of our sql database to neo4j. We use HTTP API and CSV import query for import all datas

We have no probleme with MERGE on nodes but with MERGE on relationships take very very long time (take 15min just for MERGE 10 000 relations ...). We replaced it by CREATE command and it's really better faster but it's a problem because all relationships are duplicate ... and clear all of them with this command crash the server

MATCH (s:Ticket)-[r:AskOn]-(t:Project)

WITH s, t, TAIL (COLLECT (r)) as rr

FOREACH (r IN rr | DELETE r)

And more database is big and more time MERGE command take

We have lots of data, few millions of relationship and nodes

So what your recommandations ? We love neo4j but it's a real problem for us and we can't wait so much time to set up to date our neo4j database

We also coded 3 process :

One for up to date neo database everytime that we have change in our sql database, but some time we have problem and some data missing ...

On for set up first time all data from sql database to neo database, and it's very very slow, we still not succeed to insert all data :(

On for set up to date the last week data of sql database to neo4j

Thanks you for your helps ans recommandations
Issue 1:
VSCode Version: 1.0.0

OS Version: Linux

Steps to Reproduce:

Smoke test (clone https://monacotools.visualstudio.com/DefaultCollection/Samples/_git/vscode-smoketest-express)

open bin/www

Show quick outline. Note that several entries are duplicated

Issue 2:
As far as I can tell, extensions can set a LanguageConfiguration object for a language with languages.setLanguageConfiguration(), but they can't get an existing one. This would be very useful for getting information about the language of the current document.
Issue 1:
See the log below. A pod (created by a RC) failed to schedule several times. All of the failed attempts are visible along with the one that succeeded. RC's replicas is set to 1.

$ kubectl get pods --all-namespaces

NAMESPACE NAME READY STATUS RESTARTS AGE
[...]
kube-system monitoring-heapster-v7-1xljv 1/1 Running 1 1m
kube-system monitoring-heapster-v7-czp8j 0/1 InsufficientFreeCPU 0 1m
kube-system monitoring-heapster-v7-iio5r 0/1 InsufficientFreeCPU 0 1m
kube-system monitoring-heapster-v7-r1ddh 0/1 InsufficientFreeCPU 0 1m

ref: #12476

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): kubernetes endpoint namespace unique name collision

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"windows/amd64"}

Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"linux/amd64"}

minikube version: v0.11.0

Environment:

Cloud provider or hardware configuration: minikube

OS (e.g. from /etc/os-release): windows

Kernel (e.g. uname -a): minikube

Install tools: minikube

Others:

What happened:

Tried to create two endpoints with the same name, in different namespaces. The first endpoint was created successfully within the first namespace. The second endpoint was not created in a second namespace with error Error from server: error when creating "app-2/origin-endpoint.json": endpoints "origin" already exists

What you expected to happen:

The second endpoint should have been created in the second namespace

How to reproduce it (as minimally and precisely as possible):

Follow instructions here: http://kubernetes.io/docs/user-guide/services/#services-without-selectors

Create two namespaces

Create first endpoint in first namespace

Create second endpoint in second namespace <- fails due to name collision

Anything else do we need to know:
Issue 1:
Describe what you were doing when the bug occurred:

Went from Flamegraph to the ranked view.

This doesn't reproduce consistently

Please do not remove the text below this line

DevTools version: 4.2.1-3816ae7c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157108

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157054)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157577)

at vl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314907)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)

at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:107381)

at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)

at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)

at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89544)

Component stack: in vl

in div

in div

in div

in wo

in Unknown

in n

in Unknown

in div

in div

in Li

in $e

in dn

in Ca

in Pc

Issue 2:
Describe what you were doing when the bug occurred:

Recording with the Profiler

Clicking on the "Ranked Chart"

Please do not remove the text below this line

DevTools version: 4.2.1-3816ae7c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157108

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157054)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157577)

at vl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314907)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)

at el (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:68139)

at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:108547)

at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)

at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)

Component stack: in vl

in div

in div

in div

in wo

in Unknown

in n

in Unknown

in div

in div

in Li

in $e

in dn

in Ca

in Pc
Issue 1:
I have generated a million binomial numbers using scipy.stats.binom.rvs(n = 100, p = 0.5, size = 1000000) , and certainly did not expected a histogram to have 'gaps':

The funny thing is, that does not happen always. As I don't have the seed I generated these values with, I've attached the particular data causing this issue here: observations.txt.gz

import seaborn as sb
import pandas as pd

my_data = pd.read_csv('/tmp/observations.txt.gz')
sb.distplot(my_data, kde = False)

The versions I'm using are:

>>> import seaborn as sb
>>> sb.__version__
'0.7.1'
>>> import matplotlib as mpl
>>> mpl.__version__
'1.5.1'

The histogram is correct in a sense that all bins have their 'mass', however visually (without ticks for each value) it looks a bit off / misleading.

You can verify all values are present using e.g. pd.Series(my_data).value_counts(). I've noticed these gaps do not depend on the size of the plot.

Issue 2:
An issue that arises when plotting histograms of discrete data with Matplotlib seems to also come up in distplot as well. That is, there are often empty bins in the histogram that are entirely artifacts of the plot. See here for an example with Poisson data:

Is there any way that distplot could try to detect this and adjust the bins automagically?
Issue 1:
I trying Native HTTP/2 web server.

I catch exception when run Deno v1.9 Native HTTP/2 sample code with debug log.

const body = new TextEncoder().encode("Hello World");
for await (const conn of Deno.listen({ port: 8000 })) {
(async () => {
for await (const res of Deno.serveHttp(conn)) {
console.log(res); // <------- Insert debug log.
res.respondWith(new Response(body));
}
})();
}

error: Uncaught (in promise) TypeError: this.url is not a function
console.log(res);
^
at Request.[Deno.customInspect] (deno:op_crates/fetch/23_request.js:395:19)

this.url() but this has url getter. So, it should not call url().

https://github.com/denoland/deno/blob/v1.9.2/op_crates/fetch/23_request.js#L395

Issue 2:
See example and link to source below.

example.ts:

const r = new Request('https://example.com');
console.log(r);

% deno run example.ts
error: Uncaught TypeError: this.url is not a function
console.log(r);
^
at Request.[Deno.customInspect] (deno:op_crates/fetch/23_request.js:395:19)
at inspectObject (deno:op_crates/console/02_console.js:925:50)
at inspectValue (deno:op_crates/console/02_console.js:481:16)
at inspectArgs (deno:op_crates/console/02_console.js:1454:19)
at console.log (deno:op_crates/console/02_console.js:1504:9)
at file:///Users/jesse/example/example.ts:2:9

% deno --version
deno 1.9.2 (release, x86_64-apple-darwin)
v8 9.1.269.5
typescript 4.2.2

deno/op_crates/fetch/23_request.js

Lines 389 to 398
in
2400ecb

[Symbol.for("Deno.customInspect")](inspect) {

const inner = {

bodyUsed: this.bodyUsed,

headers: this.headers,

method: this.method,

redirect: this.redirect,

url: this.url(),

};

return `Request ${inspect(inner)}`;

}
Issue 1:
by robert.swiecki:

It prints:

prog.go:55: undefined: closed
prog.go:56: undefined: closed

Issue 2:
by hanbing.liu:

What steps will reproduce the problem?
1. Check http://golang.org/doc/go_mem.html

On "is allowed to observe":

"""
A read r of a variable v is allowed to observe a write w to v if both of the following
hold:

w happens before r.
There is no other write w' to v that happens after w but before r.
"""

What is the expected output?
"""
A read r of a variable v is allowed to observe a write w to v if
both of the following hold:
1. w happens before r.
2. There is no other write w' to v that happens after w but before r.

A read r of a variable v is also allowed to observe a write w to v if w happens concurrently with r.

If a w does not fit into either of these two cases, a read r of
variable v is not allowed to observe the write w to v.
"""

What do you see instead?

"""
A read r of a variable v is allowed to observe a write w to v if both of the following
hold:

w happens before r.
There is no other write w' to v that happens after w but before r.
"""

Which compiler are you using (5g, 6g, 8g, gccgo)?

N/A

Which operating system are you using?
N/A

Which revision are you using? (hg identify)
N/A

Please provide any additional information below.

The existing statement concerning "is allowed to observe" meant to define what
are the possible set of w that may provide the value seen by the r.

Broadly there are three types of w. (1) those w that happens-before r (2) those w that w
happens-after s (3) those w that happens concurrently with r.

The existing statement only says what subset of w from (1) is allowed to by observed by
r.

My revision, will be more explicit on the intended definition of "is allowed to
observe".

Thanks.
Issue 1:
Currently this code compiles, but it shouldn't:

trait MyMul<RHS, Res>
{
fn mul(&self, rhs: &RHS) -> Res;
}

fn foo<T: MyMul<f64, f64>>(a: &T, b: f64) -> f64
{
a * b
}

fn main()
{

}

Issue 2:
use t::T;
mod t {
pub trait T {}
}

struct S;

impl T for S {}

impl T {} // oops

fn main() {}

a.rs:8:5: 8:6 error: T is not a trait
a.rs:8 impl T for S {}
^

This should show better error message. If trait T is not in mod, rustc prints "duplicate definition of module T".
Issue 1:
This works:

let strOrArray: Array<string> | string;
let str: string;
if (typeof strOrArray === 'string') {
// No error
str = strOrArray;
}

But not this:

interface Data {
strOrArray: Array<string> | string;
}
let data: Data;
let str: string;
if (typeof data.strOrArray === 'string') {
// Error:
// Type 'string[] | string' is not assignable to type 'string'.
// Type 'string[]' is not assignable to type 'string'.
str = data.strOrArray;
}

Tested with tsc 1.7.5 and Visual Studio Code 0.10.6

Issue 2:
I just found out that property access expressions doesn't work on type predicate functions and instanceof type guards.

class A {
propA: number;
}

class B {
propB: number;
}
class C {
propC: A;
}

declare function isA(p1: any): p1 is D;

interface D {
a: A | B
b: A | C;
}

let d: D;
if (isA(d.b)) {
d.b.propA; //error
}

function foo(d: D) {
if (d.b instanceof A) {
d.b.propA // error
}
}

I'm not sure if there is an easy fix on this problem. We are provided just a symbol when narrowing. That symbol represent the left most expression and then we walk up the if statement. There is no easy way of controlling symbol by symbol on each namespace in a property access expression in the if-statement-body. Because there is no info about the property access expression provided in getTypeOfSymbolAtLocation(symbol: Symbol, node: Node).

I also found that type assertion expressions are also not working in type predicate functions. But I will land a fix on that.

if (isA(<A>union)) {
a = union;
}
if (isA(union as A)) {
a = union;
}