WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
While running density tests against a kubernetes cluster, we will occasionally run into nodes where the docker daemon becomes unresponsive. Symptoms include:

docker ps hangs

kernel: unregister_netdevice: waiting for veth0123456 to become free. Usage count = 1 appears in journal output

Probably an upstream issue. But I would expect kubelet to notice that its docker deamon is unhealthy and send a 'NotReady' status back up to the controller manager. Instead, it stays at 'Ready' and the scheduler assigns pods to it, which will stay stuck in Pending.

This is not quite the same as #16601 but our mitigation is the same, we're forced to reboot the node.

Issue 2:
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

test getsockopt: connection refused,

getsockopt: connection refused,

integration getsockopt: connection refused,

integration test open file limit

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

Environment:

Cloud provider or hardware configuration:

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

NAME="Ubuntu"

VERSION="16.04.1 LTS (Xenial Xerus)"

ID=ubuntu

ID_LIKE=debian

PRETTY_NAME="Ubuntu 16.04.1 LTS"

VERSION_ID="16.04"

HOME_URL="http://www.ubuntu.com/"

SUPPORT_URL="http://help.ubuntu.com/"

BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

UBUNTU_CODENAME=xenial

Kernel (e.g. uname -a): 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools:

Others:

What happened:

Basically I am trying to run integration test on my local machine - as described here https://github.com/kubernetes/kubernetes/blob/master/docs/devel/testing.md#integration-tests

Lots of them failing with:

unable to sync kubernetes service: Post http://127.0.0.1:33526/api/v1/namespaces/default/services: dial tcp 127.0.0.1:33526: getsockopt: connection refused

I have a fresh copy of the master branch - no local changes. When I attached to etcd via strace the following lines caught my attention:

futex(0x1744568, FUTEX_WAIT, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
...
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=64*1024}) = 0

Seems like I’ve reached the limit of opened files on my machine which was set to 1024. Moreover when I increased the limit to 65535 ALL test went “green”.

For a newcomer like me it was a challenging task just to get a fresh copy, compile it and run the test.

What you expected to happen:

We could improve documentation - https://github.com/kubernetes/kubernetes/blob/master/docs/devel/testing.md#integration-tests and explicitly state that one have to set resources limit to X

We could improve tests to set resources limit on behalf of a user - this requires root privileges

I haven’t checked the test code but perhaps we could make the test code more polite and limit the number of the request we are sending to the server/etcd

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

Clone the repository, compile, run integration test
Issue 1:
I think the following snippet should be possible (but it fails currently). Since &'static MyTrait can't be 0, if the first half of the layout is 0, then the enum must be the Boxed variant.

use std::mem;

pub trait MyTrait {
fn zomg(&self);
}

enum Foo {
Inline(&'static MyTrait, [usize; 2]),
Boxed(Box<MyTrait>),
}

pub fn main() {
assert_eq!(2 * mem::size_of::<&'static MyTrait>(), mem::size_of::<Foo>());
}

Issue 2:
The current implementation only handles enums of roughly the form:

enum E {
A(ALeft..., Niche, ARight...),
B,
C
}

This can be seen as a special-case, where B and C occupy 0 bytes, of:

enum E {
A(ALeft..., Niche, ARight...),
B(B...),
C(C...)
}

As long as B and C can fit before or after A's Niche, we can still apply the optimization.

Also see rust-lang/rfcs#1230 (comment) for the initial description.
Issue 1:
When a key is present in json object multiple times it doesn't raise a parse error and only last value is used. This should instead raise json_parse_exception.

Elasticsearch version: verified on 2.x, 5.0.0-alpha3

Steps to reproduce:

curl -X PUT localhost:9200/i -d '{"settings": {"number_of_replicas": 2}, "settings": {"number_of_shards": 1}}'

curl -X GET localhost:9200/i

Issue 2:
Hello guys,

This config worked in ES v1.7.2 but since i tried to use the configuration in ES v2.1 I have a error... So :

I use this mapping :

PUT /my_index/_mapping/_default_
{
"_default_": {
"dynamic_date_formats" : [
"yyyy-MM-dd HH:mm:ss",
"yyyy-MM-dd HH:mm:ss||yyyyMMdd-HH:mm:ss||yyyyMMdd-HH:mm:ss.SSS"
],
"dynamic_templates": [
{
"template_1" : {
"match" : "*",
"match_mapping_type" : "string",
"mapping" : {
"type" : "string",
"index" : "not_analyzed"
}
}
}, {
"template_2" : {
"match" : "*@expire",
"match_mapping_type" : "date",
"mapping" : {
"type" : "string",
"index" : "not_analyzed"
}
}
}
]
}
}

And after a first type insert, I get the expected result. But if I try to insert a second or third type like :

POST /my_index/my_type
{
"source":"my_source",
"country":"my_country",
"company":"my_company",
"server":"my_server",
"@timestamp":"2016-01-01 00:07:10"
}

Result return is :

{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "failed to parse [@timestamp]"
}
],
"type": "mapper_parsing_exception",
"reason": "failed to parse [@timestamp]",
"caused_by": {
"type": "illegal_argument_exception",
"reason": "Invalid format: \"2016-01-01 00:07:10\" is malformed at \" 00:07:10\""
}
},
"status": 400
}

If I try to insert it on the first type, this is working... Perhaps bug, or just my mistake but i do not understand.

FYI: if i swap the order of the type inserted, it is always the first that it work correctly.
Issue 1:
Hoping to get more eyes on this question: https://stackoverflow.com/questions/53348524/integrate-flutter-into-cocoatouch-sdk. Does my approach seem ok here? Is the ability to integrate flutter into iOS or Android frameworks a goal of the project?

Issue 2:
Use case

Now I have a iOS framework to be used within other apps to integrate account and use center

features. Since we have framework on both iOS and android, I want to use flutter to write some

new pages proposed.

Proposal

Now how add-to-app works is that flutter has to depend on iOS or android Lifecycles if I am correct, so in a iOS framework we have no access to host app's appDelegate or that would be additional work for our framework users. So I wonder is there a solution for that, Thank you very much and wish flutter best and cheer for the flutter team.
Issue 1:
System information (version)

OpenCV =>4.1.2-1

Operating System / Platform => Linux (Arch)

Compiler => gcc (but not relevant)

Detailed description

cap=cv2.VideoCapture (this is python 3 code!)

cap.get(cv2.CAP_PROP_POS_MSEC) does not work, if not cap.read has been called before.

The current version does not seem to read the position in milliseconds, if a cap.read() has not been issued before the query. It works in Version 4.1.1-1

Steps to reproduce

This python3 code shows the problem:

import cv2

cap=cv2.VideoCapture("set/your/file/here")
w = cap.get(cv2.CAP_PROP_FRAME_WIDTH)
cnt = cap.get(cv2.CAP_PROP_FRAME_COUNT)
print("Opencv width %d frames %d"%(w,cnt))

cap.read()
ts= cap.get(cv2.CAP_PROP_POS_MSEC)
print("ts @ frame 0 after read %.3f"%ts)

#set pos
cap.set(cv2.CAP_PROP_POS_FRAMES,5)
ts= cap.get(cv2.CAP_PROP_POS_MSEC)
print("ts @ frame 5 after setPos %.3f"%ts)

ret,frame=cap.retrieve()
ts= cap.get(cv2.CAP_PROP_POS_MSEC)
print("ts @ frame 5 after retrieve %.3f"%ts)

ret,frame=cap.read()
ts= cap.get(cv2.CAP_PROP_POS_MSEC)
print("ts @ frame 5 after read %.3f"%ts)

cap.release()

if __name__ == '__main__':
pass

Result for Version 4.1.2-1:

Opencv width 720 frames 9000
ts @ frame 0 after read 0.000
ts @ frame 5 after setPos -2969.967
ts @ frame 5 after retrieve -2969.967
ts @ frame 5 after read 520.000

Result for Version 4.1.1-1:

Opencv width 720 frames 9000
ts @ frame 0 after read 40.000
ts @ frame 5 after setPos 480.000
ts @ frame 5 after retrieve 480.000
ts @ frame 5 after read 520.000

Issue 2:
Transferred from http://code.opencv.org/issues/3006

|| Hans Meine on 2013-05-03 10:57
|| Priority: Normal
|| Affected: branch 'master' (2.4.9)
|| Category: highgui-camera
|| Tracker: Bug
|| Difficulty: None
|| PR:
|| Platform: None / None

libv4l capturing backend diverged from v4l backend

Currently, we have cap_v4l.cpp and cap_libv4l.cpp with a lot of duplicated code, but also some unwanted differences.

For instance, the recent addition of CV_CAP_PROP_POS_MSEC support to the v4l backend was not merged to the libv4l backend.

Do we really want to maintain both completely separately?

History
Issue 1:
📝 Provide a description of the new feature

Please respect appwiz.cpl, ncpa.cpl, or gpedit.msc. Actually, anything respected in start menu should be respected in PT Run. This will pave the way to #5571 / #4203.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Summary of the new feature/enhancement

Proposed technical implementation details (optional)

The titel say almost everything here. But a funktion for saving how application is setup.

So you can add this settings back if Computer get problematic
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

A bunch of async child chunks in my application require a common dependency (which lives within my repo). The common dependency also has its own 3rd party dependencies (in node_modules). Webpack creates two output chunks which both include the 3rd party dependencies:

childA~childB~childC

vendors~childA~childB~childC

If the current behavior is a bug, please provide the steps to reproduce.

Use default chunk-splitting behavior

Have several async child chunks

Have a large common 1st party (non-node_modules) dependency between those chunks

1st party common dependency has large 3rd party dependencies

What is the expected behavior?

The 3rd party code should only be present in one chunk, not both.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Webpack: v4.0.0-beta.0

Node: 8.x

Issue 2:
Feature request

What is the expected behavior?

When using the default optimization with Webpack 4.8.2, the compiled code should be able to run on Safari 10.

However, the default UglifyJs configuration when using the default optimization with Webpack does not allow this to happen.

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

Some code will error on load on Safari 10.

How should this be implemented in your opinion?

The override that I've specified in my config to prevent this error is:

optimization: {
minimizer: [
new UglifyJsPlugin({
cache: true,
parallel: true,
uglifyOptions: {
mangle: {
safari10: true,
},
},
}),
],
},

Are you willing to work on this yourself?

possibly
Issue 1:
🚀 Feature

class A(nn.Module):
def forward(self, x):
if torch.jit.is_scripting() or not torch.jit.is_tracing():
return x + 1
else:
return x + 2

a = A()
script = torch.jit.script(a)

prints

RuntimeError:
Python builtin <built-in method _is_tracing of PyCapsule object at 0x7fd9ad2d8e70> is currently not supported in Torchscript:
File "/torch/jit/_trace.py", line 979
code with ``torch.jit.trace``) and ``False`` otherwise.
"""
return torch._C._is_tracing()
~~~~~~~~~~~~~~~~~~~~ <--- HERE
'is_tracing' is being compiled since it was called from 'A.forward'
File "a.py", line 20
def forward(self, x):
if torch.jit.is_scripting() or not torch.jit.is_tracing():
~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
return x + 1
else:

Motivation

we have some code that works in eager & scripting mode, but need a different codepath in tracing mode to handle dynamic shapes.

Workaround: this works, at the cost of duplicating the eager/scripting codeblock:

if torch.jit.is_scripting():
return x + 1
else:
if not torch.jit.is_tracing():
return x + 1
else:
return x + 2

cc @gmagogsfm

Issue 2:
The gather function gives incorrect gradients on both CPU and GPU when using repeated indices; no warnings or errors are raised, and the documentation doesn't say anything about this. I've seen this discussed a bit on slack, but couldn't find any issues for it on GitHub.

Here's a small test case (using PyTorch 0.1.12_2 on Ubuntu 16.04):

import torch
from torch.autograd import Variable

def gather_test(dtype):
x = torch.FloatTensor([0.1])
i = torch.LongTensor([0, 0])
x = Variable(x.type(dtype), requires_grad=True)
i = Variable(i.type(dtype).long())
y = x.gather(0, i)
dy = torch.FloatTensor([0.2, 0.3]).type(dtype)
y.backward(dy)
print('dtype: ', dtype)
print('x: ', x.data.cpu().numpy())
print('i: ', i.data.cpu().numpy())
print('y: ', y.data.cpu().numpy())
print('dy: ', dy.cpu().numpy())
print('dx: ', x.grad.data.cpu().numpy())

gather_test(torch.FloatTensor)
gather_test(torch.cuda.FloatTensor)

This gives the output:

dtype: <class 'torch.FloatTensor'>
x: [ 0.1]
i: [0 0]
y: [ 0.1 0.1]
dy: [ 0.2 0.30000001]
dx: [ 0.30000001]
dtype: <class 'torch.cuda.FloatTensor'>
x: [ 0.1]
i: [0 0]
y: [ 0.1 0.1]
dy: [ 0.2 0.30000001]
dx: [ 0.30000001]

For this example I expect dx to be [0.5] since the first element of x is duplicated to both elements of y; however instead of summing the elements of dy, the gather backward pass simply chooses one of the elements of dy corresponding to the element of x.

In this particular example we could use index_select instead of gather, but there are a lot of situations where index_select cannot substitute for gather; it would thus be extremely useful if gather could support repeated indices.
Issue 1:
I have noticed that running Base.runtests(["core"]) fails, but running make test-core does not. This is reproducible on linux x86_64 and macOS aarch64 on both latest master (63f5b8a as of this writing) and v1.7.0, but not on anything earlier, like 1.6.4.

These three tests fail:

julia/test/core.jl

Lines 3521 to 3523
in
63f5b8a

@test_throws ErrorException Vararg{Int, N} where N<:T where T

@test_throws ErrorException Vararg{Int, N} where N<:Integer

@test_throws ErrorException Vararg{Int, N} where N>:Integer

Intriguingly, when input directly into the REPL of a new session, these statements do not cause a problem on 1.6.4 or 1.7, although they do give different answers:

$ julia-1.7.0 -E 'Vararg{Int, N} where N<:T where T'
Vararg{Int64}
$ julia-1.6.4 -E 'Vararg{Int, N} where N<:T where T'
Vararg{Int64, N} where {T, N<:T}

I'm not sure what changes occur to the running Julia session when running make test-core. Is it expected that, at all times, these tests should cause errors?

Issue 2:
In Julia 1.5-rc1, recursive calls were easy to find in the stacktrace:

julia> @noinline countdown(x = 10) = x == 0 ? error("hi") : countdown(x - 1)
countdown (generic function with 2 methods)

julia> countdown()
ERROR: hi
Stacktrace:
[1] error(::String) at ./error.jl:33
[2] countdown(::Int64) at ./REPL[1]:1 (repeats 12 times)
[3] top-level scope at REPL[2]:1

See (repeats 12 times) in the above stacktrace.

On the other hand, in Julia 1.6.0-DEV.503, there is no indication of recursive calls:

julia> countdown()
ERROR: hi
Stacktrace:
[1] error(s::String)
@ Base ./error.jl:33
[2] countdown(x::Int64)
@ Main ./REPL[69]:1
[3] top-level scope
@ REPL[70]:1

It'd be great if we can bring back something like (repeats 12 times) in the old stacktrace printing.

cc @jkrumbiegel
Issue 1:
This clone seems to be cloning two target5 elements to the left well instead of one.

$("#target5").clone().appendTo("#left-well");

Issue 2:
Challenge Waypoint: Clone an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

Issue

I believe I've found bug in the phone simulation in Waypoint: Clone an Element Using jQuery:

I entered the code to clone target5 and append it to left-well, and now I see three target5 buttons in the phone simulator. FCC says my code is correct and advances me to the next challenge. The following challenges also show three target5 buttons:

Waypoint: Target the Parent of an Element Using jQuery

Waypoint: Target the Children of an Element Using jQuery

@qualitymanifest confirms this issue on his Linux box.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
Issue 1:
Lifecycle interfaces implementations in superclasses seem to be already supported (#4222)

It would be great for @Input(), @Output(), @HostBinding() to also be supported for reusable implementations (like behaviors in Polymer).

Issue 2:
Currently, when classes with decorators are used in an inheritance chain, the results are undefined.

Consider the following two components:

@Component({selector: 'a', inputs: ['metaFoo'])
class A {
@Input() fieldFoo;
metaFoo;
}

@Component({selector: 'b', inputs: ['metaBar']}
class B extends A {
@Input() fieldBar;
metaBar;
}

Currently, using component B in JIT mode does not cause an error, but only inputs fieldBar and metaBar will be understood by Angular. This is because the decorators result in properties being defined on the class functions, and those properties are subject to shadowing via prototypical inheritance. So B.annotations (where the @Component metadata lives) shadows A.annotations, and B.propMetadata (where the @Inputs live) shadows A.propMetadata.

If the @Input() fieldBar from B is removed, however, then B will have no property metadata, and so the lookup forB.propMetadata will reach A.propMetadata via the prototype chain and suddenly the fieldFoo input will become visible to Angular.

There is no provision in the spec for inheritance of decorator metadata. However, Angular could be made to support well-defined rules of inheritance for its own decorators.

Here is one set of rules which I believe covers most of the cases where users attempt to inherit components:

Class-level decorators (@Component and friends) have their metadata merged according to the merge rules:

Metadata objects are merged property by property.

For properties with primitive values, a subclass value, if present, overwrites a superclass value.

For properties with array values, the arrays are concatenated, superclass first.

If the subclass provides no value, the superclass value, if present, is used.

Property-level decorators (@Input, etc) on superclasses are included in compilation.

@Inputs with the same name on the superclass and subclass should have the same behavior as two @Inputs with the same name on the same class.

Applying these rules would change the behavior of the above example, so component B would have all 4 defined inputs recognized.

For JIT mode, this requires two changes to Angular.

First, the class-level decorators would be changed to check for metadata on the superclass, and perform the merging operation if present.

Secondly, the runtime compiler would need to consider superclass metadata when checking for property annotations.

For the AOT compiler, the semantics would have to be built into the compiler itself as the decorators don't execute during AOT compilation.
Issue 1:
This is the original image:

This is the image rendered using Glide and ImageView:

I'm already using the ARGB_8888 option with the following initialization code:

new GlideBuilder(this).setDecodeFormat(DecodeFormat.PREFER_ARGB_8888);

Switching to Picasso does seem to resolve the problem. What might be wrong here?

Issue 2:
Hi,

I guess, when images are loaded from cache, it sets a weird background color on a JPG wich have white background. This only happens on Samsung S3.

Thanks
Issue 1:
This is a problem with the documentation of threejs, not threejs itself, I got redirected by the IRC chat by a red colored user "bai" to place this bug here.

Steps:

go to https://threejs.org/docs/index.html#api/lights/DirectionalLight

Press middle mouse button on any link on the page, for example DirectionalLightShadow

Expection:

Since it has the pointer cursor, I expect the browser to open the page on a new tab

Reality:

The browser executes the scroll using middle mouse button interaction

Why is this a problem

This is a problem because when new developers come to the documentation, and seeing an first impression from breaking the UX flow most people are used with, is a bad sign and encourages new people to go away.

Issue 2:
Hi mrdoob/team,

Many times while going through the documentation I would like to ctrl/cmd+click on links pointing to particular class documentation to open in new tab. Because the elements don't even contain href attribute, it simply doesn't work. Similarly, I can't right click and "Open in new tab".

I'm not providing an example because you can pick any documentation page and look for any documentation-linked class name to see the problem.

The documentation of three.js is pretty good and I'm thankful! Just wondering if it'd not be too much work to perhaps update the onclick listener / setFragmentUrl function to consider if a modifier is pressed. (I understand the lack of href is because you want the doc page to be like an SPA).

Thank you for your consideration and have a great day,

Michal
Issue 1:
there is a really long line in the file

only happens when syntax highlighting

works fine as text

pastebin colors it right & fast for example

http://pastebin.com/Cx3zy9fm

thanks

Issue 2:
May be a known issue, but files with large embedded images such as github's public/enterprise/maintenance.html will often cause Atom to freeze (MacVim actually struggles as well).

Seems some of them (github's public/maintenance.html for instance) work fine when in soft wrap mode, or until you move your cursor to the long line when out of soft wrap.
Issue 1:
tabs,tab无法点击选中，组件tabs无法点击选中，只能默认选择第0个,是tabs无法得到tab的selected

Issue 2:
(I use material-ui@^0.14.4)

I just come to copy this example from your doc (http://www.material-ui.com/#/components/tabs) to my app.

I have no error in the console and neither the "console.log".

When I click on a Tab, the ripple animation works fine, but the selection is never changing. I'm stuck on the first tab.

Have I made something wrong ? Or there is a bug ?

import React from 'react';
import Tabs from 'material-ui/lib/tabs/tabs';
import Tab from 'material-ui/lib/tabs/tab';

export default class TabsExample extends React.Component {

constructor(props) {
super(props);
this.state = {
slideIndex: 0,
};
}

handleChange = (value) => {
console.log("Tab is changing to ",value);
this.setState({
slideIndex: value,
});
};

render() {

return (
<Tabs value={this.state.slideIndex} onChange={ this.handleChange } >
<Tab label="First Tab" value={0}>
<div>CONTENT 1</div>
</Tab>

<Tab label="Second Tab" value={1}>
<div>CONTENT 2</div>
</Tab>
</Tabs>
)

}
}

Thanks !