WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Rogue kubelets can make N failure events (e.g., out of disk, can't mount secret, can't garbage collect) every poll loop, which can completely overload a kube-apiserver. We should rate limit these.

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/.):

Raising this bug after discussing with gmarek.

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

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

Bug Report

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"ec7364b6e3b155e78086018aa644057edbe196e5", GitTreeState:"clean"}

Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"ec7364b6e3b155e78086018aa644057edbe196e5", GitTreeState:"clean"}

Environment:

Cloud provider or hardware configuration: x86_64

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

Kernel (e.g. uname -a): 3.10.0-327.el7.x86_64

Install tools:

Others:

What happened:

I'm trying to run density tests using the following command : go run hack/e2e.go -v --test --test_args="--ginkgo.focus="Density"" and observed the following error - 'GetSigner(...) not implemented for skeleton'"}

What you expected to happen:

skeleton implementation required

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

go run hack/e2e.go -v --test --test_args="--ginkgo.focus="Density""

Anything else do we need to know:

After my discussion with Gmarek, I came to know that skeleton is not implemented in the following function - function name : func GetSigner(provider string) (ssh.Signer, @error) . Hence raising this bug.

Additionally this is being run on a local cluster and I have attached the logs as well.

nohup.txt

Thanks

@gmarek @wojtek-t and @dchen1107
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

10.4.0

What operating system are you using?

Windows

Operating System Version

windows 7

What arch are you using?

x64

Last Known Working Electron version

10.4.0

Expected Behavior

我希望 所有 electron 打包的客户端 不要产生白屏

Actual Behavior

当前偶发性的 electron 打包的客户端在开启的时候界面全部白屏 并且有错误输出 Exception thrown during bootstrapping

Error installing extension 'extensions::SafeBuiltins'.

[6108:0730/163552.511:FATAL:v8_initializer.cc(95)]

[4840:0730/163552.836:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot read propert

y 'instance' of undefined", source: devtools://devtools/bundled/devtools_app.htm

l?remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@85104d2dfc

96eac92da3f8019998debdcc240d0d/&can_dock=true&toolbarColor=rgba(223,223,223,1)&t

extColor=rgba(0,0,0,1)&experiments=true (1)

Testcase Gist URL

No response

Additional Information

相关环境 vue 2.0 webpack

Issue 2:
Expected behavior

Should be able to develope andoid apps using electron
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

gather_facts

ANSIBLE VERSION

ansible 2.3.0.0
config file =
configured module search path = Default w/o overrides
python version = 2.7.12 (default, Jul 1 2016, 15:12:24) [GCC 5.4.0 20160609]

CONFIGURATION

Default configuration (no local ansible.cfg)

OS / ENVIRONMENT

OS = Ubuntu 16.04.2 LTS

SUMMARY

If a playbook consists of multiple play, each of which affects distinct set of hosts, when only a subset of play is selected for running, Ansible still tries to gather facts from unaffected hosts. This might be related to #21528

STEPS TO REPRODUCE

Run the following playbook ansible-playbook -i dev sample.yml --tags=db

---

- hosts: mysql
tags: db
tasks:
- debug: msg=hello

- hosts: app
tags: app
tasks:
- debug: msg=world

EXPECTED RESULTS

Facts are not gathered for app hosts

ACTUAL RESULTS

Facts are gathered for all hosts

PLAY [mysql] ******************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ********************************************************************************************************************************************************************************************
ok: [172.31.2.4]

TASK [debug] ******************************************************************************************************************************************************************************************************
ok: [172.31.2.4] => {
"changed": false,
"msg": "hello"
}

PLAY [app] ********************************************************************************************************************************************************************************************************

TASK [Gathering Facts] ********************************************************************************************************************************************************************************************
ok: [172.31.1.4]

PLAY RECAP ********************************************************************************************************************************************************************************************************
172.31.1.4 : ok=1 changed=0 unreachable=0 failed=0
172.31.2.4 : ok=2 changed=0 unreachable=0 failed=0

Issue 2:
FreeBSD seems very fond of "rc-style" configuration files, which have the following format:

# Comment
SOMETHING=somevalue

Examples of this are make.conf, sysctl.conf, rc.conf and many others.

The format is close, but not exactly the INI-format, which makes the ini_file module unusable. The lineinfile module works but is wordy and makes the playbook look cumbersome.

I'd like to see an rc_file module, that would help in configuring values for such files.

I'm nearly volunteering to write one myself, but there is a gotcha. At least the service module contains code that manipulates rc.conf directly to set (some of the values) there. Would it be important to refactor that code into a centralized location and if so, what would that place be? I am not overly familiar with Ansible internals.
Issue 1:
bug

After updating from 15.3.2 to 15.4.0, the error is showing up in previously working code. The app fails to load in IE11 on Win 7 with the following error:

SCRIPT5022: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of App. File: bundle.js, Line: 13847, Column: 6

It continues to work fine in all other browsers.

Thanks

Issue 2:
Do you want to request a feature or report a bug?

BUG

What is the current behavior?

App doesn't render in IE11 and below.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

Build React app with Webpack

Launch IE11 or below (not an emulator)

You will see a blank screen or half-compiled React app with the following error:

What is the expected behavior?

To render as it does in Chrome, Firefox, etc.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

We've temporarily shrink-wrapped our dependencies so that we can continue to serve our app. We're starting to believe that it's coming from a dependency that react, apollo or webpack may be relying on...

Shrink-wrapped versions of our dependencies (left is the new one that's broken and the right one is the old one that continues to work across all browsers) https://www.diffchecker.com/SyaJUcsk
Issue 1:
Do you want to request a feature or report a bug?

Report a possible bug

What is the current behavior?

When Component A renders Component B with a children prop that is a react component / JSX fragment any render of component A will recreate said children prop

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

Example Code:

import React from 'react';

class ComponentWithChildren extends React.PureComponent {
render() {
console.log("RENDER COMP")
return <span>Hello{this.props.children}</span>
}
}

class Children extends React.PureComponent {
render() {
return (
<div>
these are children
<span>nested</span>
</div>
)
}
}

class App extends React.PureComponent {

update = () => this.setState({ count: this.state.count + 1 })

state = {
count: 0
}

render() {
console.log("RENDER APP")
return (
<div>
<button onClick={this.update}>Update</button>
<ComponentWithChildren>
<Children />
</ComponentWithChildren>
</div>
)
}
}

export default App;

What is the expected behavior?

I would expect ComponentWithChildren not to re-render because none of its props actually changed

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React 15.4.1

Issue 2:
If you have

componentWillReceiveProps: function() {
this.setState({x: this.state.x + 1});
this.setState({x: this.state.x + 1});
}

then x will only be incremented once because the new state will just be stored in _pendingState until receiveProps finishes. After my refactoring in #115, this will never increment twice, which is probably confusing.

Maybe this isn't a bug. We can fix this behavior by instead updating this.state immediately (but still updating the UI later). Right now I can't think of any situations where having this.state out of sync with the UI is a problem.

@vjeux suggested I open an issue, so here I am. Probably easiest for me to fix while updating #115 though.
Issue 1:
Veracode is reporting that all versions of axios (up to and including 0.19.0-beta.1) contain a XSS vulnerability. (CVSSv3: 6.1)

Very limited details available:

https://www.sourceclear.com/vulnerability-database/security/sca/vulnerability/sid-21679/summary

I suspect it is a false positive based on comments here. Would value any thoughts / input

Thanks

Issue 2:
Describe the bug

A Fortify Scan finds a critical Cross-Site Scripting vulnerability in Axios here:

https://github.com/axios/axios/blob/master/lib/helpers/isURLSameOrigin.js#L30

urlParsingNode.setAttribute('href', href);

The method resolveURL() sends unvalidated data to a web browser, which can result in the browser executing malicious code.

This issue has been reported previously, but then it was closed as 0.19.0 was supposed to provide a fix.

We ran a Fortify scan on 0.19.0 and got the same error; the source code still contains the problematic line above and the issue remains.
Issue 1:
I've set axios.defaults.headers.post['Content-Type'] = 'application/x-www-form-urlencoded'; and using the same instance doesn't affect at any request at all. It is very annoying because every POST request to API is useless.

In addition, v: 0.12.0, no interceptor, pure default + post request.

Issue 2:
Describe the issue

This might be duplicated question, but I have tried all possible research on google and blogs, StackOverflow to get a solution to fix it, but no luck so if you already know the answer please help me.

I am trying to send an array of objects to Axios post request, but the payload empty array even if I have the data in array as I checked with console.log

Example Code

Code snippet to illustrate your question

axios.post("/api/videos", {
ytVideosList,
data: {
customFunction: "AddVideoList"
}
})

Expected behavior, if applicable

where ytVideoList is [{json-obj1},{json-obj2}, .....] etc which is empty [] at payload side, so i am not able to insert data in my database table. I hope everything is clear if you know the answer please respond as soon as possible.

Environment

Axios Version 0.24.0

Adapter HTTP

Browser Chrome

Browser Version 22+

Node.js Version 13+

React 16.7+

Additional context/Screenshots

It's general simple data sending issue so no need to add screenshot i think so
Issue 1:
The Qhull library used for the Voronoi diagram calculation has floating number imprecision. If the points differ only 5 digits after the decimal point (e.g. geographic coordinates), only one region is determined.

These imprecisions are already mentioned in the Qhull documentation.

Is a note/warning in the documentation appropriate? Maybe with a link to the correct Qhull flag Or could a check be added to get a warning, if there are probably imprecison?

Reproducing code example:

from scipy.spatial import voronoi_plot_2d, Voronoi
import numpy as np
import matplotlib.pyplot as plt

data_x = 40 + np.random.random(50) / 1000
data_y = 10 + np.random.random(50) / 1000
points = list(zip(data_x, data_y))

vor = Voronoi(points)
voronoi_plot_2d(vor)
plt.show()

Scipy/Numpy/Python version information:

1.3.0 1.17.0rc1 sys.version_info(major=3, minor=7, micro=3, releaselevel='final', serial=0)

Issue 2:
A little context: We're trying to use Voronoi diagrams with points in GIS shapefiles, which have coordinates with large numbers like [470121.0, 5118838.0999999996]

When I run scipy.spatial.Voronoi() on raw points I get:

And this is is weird to me. There are shapes but they are really sparse.

If I shift everything closer to the origin and retry I get:

That second case is what I expect. This is my first time using this library so I'm not 100% sure I'm not at fault here.

Is this known behavior? Should I just transform my points every time I want to use this?
Issue 1:
Pavla Nováková opened SPR-6373 and commented

It would be useful to be able to use validation groups in spring MVC as specified by JSR-303. With the improvement it should be possible to write something like:

@RequestMapping("/foo", method=RequestMethod.POST)

public void processFoo(@Valid(groups={Default.class, MyValidationGroup.class}) Foo foo) { ... }

Affects: 3.0 RC2

Issue Links:

#11035 Support for 'groups' in addition to @Valid for @MVC Controllers ("is duplicated by")

#11722 Add Group Class support to JSR-303 Validation using @Valid ("is duplicated by")

#12504 ValidationUtils: add support for Validation group interfaces

Referenced from: commits 0013317, 49a2aaf

54 votes, 53 watchers

Issue 2:
Roman Shevchenko opened SPR-3785 and commented

A defaultObject property of JndiObjectFactoryBean is not available via otherwise perfect jee:jndi-lookup tag and this makes it unusable when looking for optional JNDI settings.

Affects: 2.0.6

Issue Links:

#8692 jee:jndi-lookup do not provide a way to define a default object ("duplicates")

1 votes, 5 watchers
Issue 1:
Elasticsearch version: 2.1.2 or newest

PUT store
{
"mappings": {
"performance": {
"_source": {
"enabled": false
},
"properties": {
"host": {
"store": true,
"type": "long"
},
"time": {
"format": "epoch_millis",
"store": true,
"type": "date"
}
}
}
}
}
POST store/performance
{
"host":1234,
"time":1479264717
}

GET store/_search
{
"fields": [
"*",
"_source"
],
"fielddata_fields": [
"time"
]
}

query result:

"time": [
"1479144300000",
1479144300000
]

But expect result:

"time": [
1479144300000
]

Yes, setting the store the timestamp field does not make any sense ,but most ES users do not use the

ES very well ,so there is an inappropriate way to use it .However,I think that ES should consider this situation,to tolerate or compatible with this imappropriate use:

This setting can be ignored when setting the index type mappings.

Or to return to the search results,ignore the duplication of the results, take the value of the field from on place.

I'm from China, my English is not very good ,can understand what I mean?

Issue 2:
At least with master (did not check other branches) I see this:

[WARNING] Some problems were encountered while building the effective model for org.elasticsearch:elasticsearch:jar:2.0.0-SNAPSHOT

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin @ line 1104, column 21

[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.apache.maven.plugins:maven-resources-plugin @ line 1367, column 21

[WARNING]

[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.

[WARNING]

[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
Issue 1:
Bootstrap components are defined as constructor functions in a private scope. While they are exposed globally within $.fn, they are called with references to those constructors within that private scope.

That means that there's no way to replace or wrap the code within the constructor function from 3rd party code. The use case that I'm imagining: modifying the behavior of the stock components without maintaining a fork of Bootstrap.

The design that seems appropriate is moving the code from within the constructor functions into an init method on the constructor's prototype, leaving all constructor functions looking something like this:

var Affix = function (element, options) {
this.init(element, options);
}

That would allow global access to override the init method, via $.fn.affix.Constructor.init which would also affect the reference to the constructor as Affix within its private scope. The change should not affect any functionality or the API beyond exposing the constructor function for manipulation. If this sounds good, I'll be happy to make a PR.

I apologize if this is revisiting an old question that's been resolved - I wasn't able to find historical work on this, but I know that doesn't mean it's not out there!

Issue 2:
Dropdowns experience the same clipping problems as tooltips, so one solution would be to allow specifying data-container="body", as you can with tooltips.

This means the .dropdown-menu would have to be positioned with JS, like the tooltip, and I don't know what problems would be introduced by shipping the ul.dropdown-menu elsewhere in the DOM, even temporarily.

The wrath of overflow: hidden...
Issue 1:
🐛 Bug

The tensor.clamp function returns the upper bound when applied to a nan array on the GPU. On the CPU it returns nan instead.

To Reproduce

Steps to reproduce the behavior:

import numpy as np
import torch
t = torch.FloatTensor([np.nan])
t.clamp(-10, 10)

Out[26]: tensor([nan])

t.cuda().clamp(-10, 10)

Out[25]: tensor([10.], device='cuda:0')

Expected behavior

I would expect to have the behavior be agnostic to the computational substrate. Regardless, returning the upper bound on nan is completely arbitrary and can't possibly be the preferred solution.

Environment

PyTorch version: 1.0.0

Is debug build: No

CUDA used to build PyTorch: 8.0.61

OS: Ubuntu 18.10

GCC version: (Ubuntu 8.2.0-7ubuntu1) 8.2.0

CMake version: Could not collect

Python version: 3.7

Is CUDA available: Yes

CUDA runtime version: Could not collect

GPU models and configuration: GPU 0: GeForce GTX 1080 Ti

Nvidia driver version: 415.27

cuDNN version: Could not collect

Versions of relevant libraries:

[pip3] numpy==1.15.4

[pip3] numpydoc==0.8.0

[pip3] torch==1.0.0

[pip3] torchvision==0.2.1

[conda] blas 1.0 mkl

[conda] cuda80 1.0 0 soumith

[conda] cuda90 1.0 h6433d27_0 pytorch

[conda] cuda91 1.0 h4c16780_0 pytorch

[conda] libmklml 2018.0.3 0

[conda] mkl 2019.1 144

[conda] mkl-dnn 0.14 2 intel

[conda] mkl-service 1.1.2 py37he904b0f_5

[conda] mkl_fft 1.0.6 py37hd81dba3_0

[conda] mkl_random 1.0.2 py37hd81dba3_0

[conda] pytorch 1.0.0 py3.7_cuda8.0.61_cudnn7.1.2_1 [cuda80] pytorch

[conda] torchvision 0.2.1 py_2 pytorch

[conda] torchvision 0.2.1

Issue 2:
The behavior of clamp is not consistent on CPU and GPU when nan's are involved. See the following code snippet

import torch
a = torch.tensor([float('nan')])
print(a.clamp(0, 1)) # prints nan
print(a.cuda().clamp(0, 1)) # prints 1

This doesn't happen if we clamp only with a min or max, but only when both are passed.

I believe the problem is in

pytorch/aten/src/THC/THCTensorMathPointwise.cuh

Line 309
in
517c7c9

T val = THCNumerics<T>::lt(*in, maxValue) ? *in : maxValue;

. If we compare it to the CPU implementation in

pytorch/aten/src/TH/generic/THTensorMath.cpp

Line 122
in
517c7c9

rp[i] = (tp[i] < min_value) ? min_value : (tp[i] > max_value ? max_value : tp[i]);

, we see that the order of the ternary operator is inversed, which doesn't propagate nans on the CUDA case.

A simple fix would be to invert the order of the ternary operator in the CUDA kernel.

Thanks @fmassa for helping me out identifying the root cause of the issue.
Issue 1:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Stock example script.

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): CentOS Linux release 7.6.1810 (Core)

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: On my laptop,

TensorFlow installed from (source or binary): From source for c++ application.

TensorFlow version (use command below): v1.8.0

Python version: 2.7

Bazel version (if compiling from source): 0.15.1

GCC/Compiler version (if compiling from source): g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)

CUDA/cuDNN version: CPU only

GPU model and memory: None.

Describe the current behavior

I have a Standalone c++ build process for ubuntu and it works fine with my own code as well as with the c++ example code on tensorflow.

But when i run the same code on CentOS platform. I get following runtime error message and the executable core dumps:

2019-07-11 10:20:42.027023: F tensorflow/core/framework/function.cc:1329] Check failed: GetOpGradFactory()->insert({op, func}).second Duplicated gradient for MapAccumulate
Aborted (core dumped)

My compilation command is as:

g++ -std=gnu++11 -Wl,-rpath='$ORIGIN/lib' -fPIC -Iinclude -Llib example.cc -ltensorflow_cc -ltensorflow_framework -o example

Code to reproduce the issue

Provide a reproducible test case that is the bare minimum necessary to generate the problem.

Please follow the steps provided on blog.

Issue 2:
System information

OS Platform and Distribution : windows10

TensorFlow installed from : source

TensorFlow version: 1.11.0

Python version: Python 3.6.3 :: Anaconda custom (64-bit)

Installed using virtualenv? pip? conda?: conda

Bazel version (if compiling from source): 0.19.0 not from source

only cpu version.

I followed the instruction from tensorflow official site.

When I entered bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package

An error occurred

WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
d:\tensorflow-1.11.0/.bazelrc
d:\tensorflow-1.11.0/tools/bazel.rc
ERROR: SymlinkDirectories(C:\Users\Administrator/_bazel_Administrator/install/46e308c2aba33f6ef6ad7b7f2c018098, c:\users\administrator\_bazel_administrator\buk4ctdf/install): CreateJunction:
FATAL: failed to create installation symlink 'c:\users\administrator\_bazel_administrator\buk4ctdf/install': success