WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Per @quinton-hoole's request, I'm attempting to chart a well established path such that we can address some of the larger communications issues. Hopefully this can serve as a jump point for the communications issues we wish to target in the 1.3 cycle.

Problem Statement

The overhead and data flow of the kubernetes control plane has led to a series of artificial limits, or caps (qps,max-inflight, etc), that have been placed on different system components. These caps are an attempt to limit the system from overloading the api-server, and to ensure certain SLOs are met. The core issue is not that the caps exist, but the fact that the interaction between the components can cause system overload in the first place.

This epic, targeted for 1.3, is intended to help breakdown some of the different facets of this issue as we see them today, and address each aspect independently, provided there are resources available to do so.

The higher level objective would be to fix the system where possible, in order to prevent the degenerative case of overloading from occurring... at all.

Breakdown

From operations and tests, we have witnessed the following issues which relate to this broader epic:

P1: There are a large number of connections in the system. (#21081)

Worst offenders are not quantified?

A1.1: Analyze api-server metrics, and add metrics on who is creating the most connections, investigate their usage, and optimize their workflow. Different solutions may exist depending on the situation, which in turn may become their own issues. (This is a meta-problem).

Each new connection incurs an overhead in the system (TLS+kernel+application), and there isn't a single choke-point to throttle during overloaded situations.

A1.2: Pursue http2 for internal communications, each component should have only 1, or 2 connections to the main api-server, as well as golang 1.6 for the decreased EC/TLS overhead.

P2: Components do not properly back-off under extraneous load conditions.

We can create a number of conditions which can cause the system to overload, e.g. fail-over, or aggressive loading.

A2.1: Once we've addressed P1, and have a single choke-point it's relatively trivial to back-off during loaded situations.

P3: Enconding and decoding dominate api-server load

A3.1: We've known this for a long time, and there are a series of issues around protobuf and gRPC to address. @wojtek-t has an issue list.

/cc @kubernetes/sig-scalability @jeremyeder

Issue 2:
Currently we manually convert the yaml/json files embedded in markdown files. To automate this process, we propose to add features to the kube-version-change tool:

we need to remove the default fields in the output of kube-version-change tool

we need to add a flag to kube-version-change that commands the tool to recursively convert all the .md files in a directory

Some code that maybe reused:

sampleRegexp in examples/examples_test.go matches yaml/json block in markdown files

@nikhiljindal @krousey @bgrant0607 could you @ more folks? Thank you.
Issue 1:
The file dialog opens from a renderer process, but most of the icons are missing for the files and the folders.

screenshot

Electron version: 0.37.2

Operating system: OSX 10.11.4

Issue 2:
I want to handle saving of a file to set the download path:

mainWindow.webContents.session.on('will-download', function(event, item) {
var filename = item.getFilename();
var savePath = require('dialog').showSaveDialog({
title: filename,
defaultPath: require('os').homedir() + '/' + filename
});
if (savePath) {
item.setSavePath(savePath);
} else {
item.cancel();
}
});

It's all good, except that the dialog comes out without icons for files and folders (file type icons are fine, only folder icons), and is missing the usual items in the left sidebar:

My electron version is 0.36.4, running OSX 10.11.2.

Is it possible to have the icons back and make the dialog look more native? Thanks!
Issue 1:
Examples:

class C<R>
{
value : R;
constructor(v? : R) { this.value = v }
}

// OK, no type error
var a : C<string> = new C("x");

// OK, type error
var b : C<string> = new C(1);
var c : C<string> = true ? new C("x") : new C(1);
var d : C<string> = new C(1) || new C<string>(null);
function e() : C<string> { if (false) { return new C(null) } else { return new C(1) } }

// Bad, no type error
var f : C<string> = true ? new C(null) : new C(1);
var g : C<string> = true ? new C(1) : new C(null);
var h : C<string> = (() => { if (false) { return new C(null) } else { return new C(1) } })();
var i : C<string> = new C(1) || new C(null);

Here, any time new C(1) is used it should have the type C<number> and not unify with C<string>. It seems like R not being known in new C(null) prevents these other type errors from occurring.

Issue 2:
Courtesy of @JsonFreeman

function f<T>(t: T): T { return null }
f(null);

When compiling with -noImplicitAny, we don't get an error here, even though T is implicitly inferred to be any when we call f
Issue 1:
I have a dataframe looks like this, and its column 2 is missing:

When I try to select the max date in each row, I got all NaN in return:

However, If the dataframe's type is float64, the selection work as expected.

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

df.to_sql('TableNameHere', engine, if_exists='append', chunksize=900, index=False)

Problem description

I am trying to append a large DataFrame to a SQL table. Some of the rows in the DataFrame are duplicates of those in the SQL table, some are not. But to_sql() completely stops executing if even one duplicate is detected.

It would make sense for to_sql(if_exists='append') to merely warn the user which rows had duplicate keys and just continue to add the new rows, not completely stop executing. For large datasets, you will likely have duplicates but want to ignore them.

Maybe add an argument to ignore duplicates and keep executing? Perhaps an additional if_exists option like 'append_skipdupes'?

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.0.final.0
python-bits: 64
OS: Windows
OS-release: 10
machine: AMD64
processor: Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
byteorder: little
LC_ALL: None
LANG: None
LOCALE: English_United States.1252

pandas: 0.19.2

nose: None

pip: 9.0.1

setuptools: 28.8.0

Cython: None

numpy: 1.12.0

scipy: None

statsmodels: None

xarray: None

IPython: 5.3.0

sphinx: None

patsy: None

dateutil: 2.6.0

pytz: 2016.10

blosc: None

bottleneck: None

tables: None

numexpr: None

matplotlib: None

openpyxl: None

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: 0.999999999

httplib2: None

apiclient: None

sqlalchemy: 1.1.9

pymysql: None

psycopg2: None

jinja2: 2.9.5

boto: None

pandas_datareader: None
Issue 1:
Currently, the IAM Policy template for Kubernetes master grants ec2:* permissions, which means the role have the API access to potentially terminate other instances even if they are not in the Kubernetes cluster.

{
"Effect": "Allow",
"Action": ["ec2:*"],
"Resource": ["*"]
},

https://github.com/kubernetes/kubernetes/blob/master/cluster/aws/templates/iam/kubernetes-master-policy.json#L6

A suggestion is to instead whitelist the actions required for Kubernetes Master. A list to start with would be:

ec2:Describe* to get ec2 instance metadata such as AZ information.

ec2:AttachVolume, ec2:DetachVolume to support EBS mounting.

@justinsb

Issue 2:
For example, the master currently has blanket permissions on ec2, and the minion has write access to the s3 bucket, but only needs read access.

This may entail giving objects we create a prefix to enable stricter policies.
Issue 1:
I can't think of a reason why this method shouldn't be added, but I may be missing something.

Issue 2:
I wonder whether collect() isn't always equivalent to Vector(), and could therefore be merged into it:

julia> methods(collect)
#3 methods for generic function "collect":
collect(r::Range{T<:Any}) at range.jl:753
collect{T}(::Type{T}, itr) at array.jl:217
collect(itr) at array.jl:224

The method for Range returns a vector, so it could be replaced with Array(), as both call vcat() in the end. convert(Vector, ...) currently fails and should be fixed.

The methods for general iterables are more complex, but they essentially always create an Array too. Even when they call similar(), it's on a 1:1 range, so they actually create a Vector. So the collect() machinery could be moved to Array()/Vector() to make them support conversion from any iterable.

This issue is related to discussions regarding similar() (#13731). Indeed, Julia provides a few functions which appear to behave differently, but in practice behave like Array, and callers end up depending on this assumption. This makes the API more complex and less explicit.

See also #12251 about merging full into Array.
Issue 1:
Assignees:

Windows @dbaeumer

OS X @bgashler1

Linux @joaomoreno

You can now bring up the diff editor on any 2 existing files by using the command line in the form:

code --diff <file1> <file2>

Verify this opens the diff editor on the provided files

Verify this works for when code is running or not

Verify corner cases (e.g. files do not exist, one path instead of two, etc)

Verify our rules for picking windows are respected (-r to force reuse a window is respected)

Issue 2:
It's kind of feature request. Please add support for multiple folder open on same window. It's really essential.
Issue 1:
I assumed that failing file operations (rm, 'mkdir, etc.) return a SystemError when they fail. However, under certain circumstances they return an undocumented UVError. This seems like an unintentional leak of an implementation detail:

julia> try rm("a") catch err info(typeof(err)) end
INFO: Base.UVError
julia> try chmod("a", 0) catch err info(typeof(err)) end
INFO: Base.UVError

The printed error messages look fine, but e.g. the error codes have different meanings (SystemError uses errno, UVError uses its own set of constants). Having different exception types makes it difficult to handle these errors programmatically.

Issue 2:
julia> try
run(`false`)
catch err
dump(err)
end
ErrorException
msg: ASCIIString "failed process: Process(`false`, ProcessExited(1)) [1]"

julia> try
run(`foobar`)
catch err
dump(err)
end
UVError
prefix: ASCIIString "could not spawn `foobar`"
code: Int32 -2

I feel like UVError isn't something that should be escaping the Julia internals. For one thing, I doubt anyone not involved with Julia development knows or wants to know what the UV refers to. Having different exception types thrown from the same method (from the users perspective) feels odd to me, although I think thats a much more debatable point.

It bit me recently (I had code like println(fp, err.msg), which threw an error in the error handler...) and I just saw #7822 which made me think of it again.
Issue 1:
I‘m a webgl novice.I hope get some help about mouse picking. I want to do a street view program with webgl.so,l create a SphereGeometry,and the camera position is in the SphereGeometry.on the street view texture,I want to mark the point where is picked by the mouse,but I can not get the point position maybe because the camera is in the Sphere.if I make the Sphere smaller , the raycaster.intersectObjects( scene.children) worked and get the intersect point 's position.3q

Issue 2:
Description of the problem

In r83, a loaded BufferGeometry object would receive transforms, and apply these transform matrices to their "position" Float32Array. However, in r84, these transform matrices are no longer applied.

Here's a simple example where I apply a rotation matrix to duplicate a tree:

// Load tree geometry
var geomLoader = new THREE.BufferGeometryLoader();
geomLoader.load("meshes/tree.json", geomLoaded);

function geomLoaded(geometry){
// Enlarge tree
geometry.scale(2, 2, 2);

// posArray is twice as big as the loaded vertices so it can hold two trees
var vertCount = geometry.getAttribute("position").itemSize * 2;
var posArray = new Float32Array(vertCount * 3);

// Set top tree vertices to first half posArray
posArray.set(geometry.getAttribute("position").array);

// Rotate geometry and apply new vertices to second half of posArray
geometry.rotateZ(Math.PI);
posArray.set(geometry.getAttribute("position").array, posArray.length / 2);

geometry.addAttribute("position", new THREE.BufferAttribute(posArray, 3));

pointsObject = new THREE.Points(this.geometry, this.shaderMat);
scene.add(pointsObject);
}

In r83, I got the desired effect of two trees in one BufferGeometry object:

In r84, I get the undesired effect of no scaling, and no rotating, leading to both trees stacking on top of each other:

Is this a bug, or an intentional change in behavior?

Three.js version

r84

Browser

All of them

OS

All of them

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
Describe the workflow you want to enable

In some cases you need to use OrdinalEncoder even if the dataframe contains NaN, which couldn't be done at current sklearn version. For instance, when using KNNImputer to deal with missing values you need first change categorical columns into numerical, otherwise it couldn't be done. But when using OrdinalEncoder to change categorical columns into numerical, it requires the dataframe contains no NaN. So I have to impute first. See? it's head bites it's tail, couldn't be done. I'm new to it so not sure if I'm think right.

Solution

Add "ignore_nan" parameter to it. When "ignore_nan=True" it passthrough the nan without changing it. When it's False it throws an error.

Describe alternatives you've considered, if relevant

Also with LabelEncoder.

Issue 2:
We should allow NaNs to pass-through in OrdinalEncoder. One reason is for supporting categorical features with NaNs in the HistGradientBoosting estimators:

For the native categorical support, we require categories to be encoded as done by OrdinalEncoder. Yet, OrdinalEncoder is unable to be fitted with NaNs. So we can't use the native categorical support of the Hist-GBDT if the categorical features have NaNs... Which is ironic because we do support NaNs as a native category in the Hist-GBDT code.

In terms of API, we'd need a new handle_missing={'error', 'passthrough'} parameter which would default to 'error'.

CC @ogrisel @lorentzenchr @thomasjpfan

(Note: This is a subset of the feature request from #17123)

(Marking as "Hard" because anything encoding-related is usually a headache ;) )
Issue 1:
Axios Version : 0.19.x

Custom config passed by axios.create lost in the interceptor

const client = axios.create({custom1: 'xxx'})
client.interceptors.response.use(res => {
config.custom1 // undefined
config.custom2 // xxx
return res.data
})
client.get('/xxx', {custom2: 'xxx'})

Issue 2:
Describe the bug

Custom settings are not persisted to each request

To Reproduce

var axios = require('axios')
var axios2 = axios.create({retry: true});
// should log "Retry is true"
axios2.interceptors.request.use(request => console.log('Retry is ' + request.retry));
axios2.get('http://www.blankwebsite.com/');

Expected behavior

Custom default parameters should be persisted to each request.

Environment:

Axios Version [hash a17c70c]
Issue 1:
Mike Bingham opened SPR-7714 and commented

After upgrading to Spring 3.0.5, we've encountered a regression when attempting to bind form inputs to nested map value properties with auto-grow.

To illustrate, in 3.0.5, the following test from BeanWrapperAutoGrowingTests works:

@Test

public void setPropertyValueAutoGrowMap() {

wrapper.setPropertyValue("map[A]", new Bean());

assertTrue(bean.getMap().get("A") instanceof Bean);

}

However, the following test fails:

@Test

public void setNestedPropertyValueAutoGrowMap() {

wrapper.setPropertyValue("map[A].nested", new Bean());

assertTrue(bean.getMap().get("A").getNested() instanceof Bean);

}

Both tests pass in 3.0.4.

Affects: 3.0.5

Issue Links:

#12495 DataBinder/BeanWrapper regression: Binding to a nested Map property fails in 3.0.5, works in 3.0.4 ("is duplicated by")

Issue 2:
marc schipperheyn opened SPR-8759 and commented

The getter return type (Map) is not the same as setter (Properties). Since Spring 3.1, this is a problem. I get

org.springframework.beans.NotWritablePropertyException: Invalid property 'statusCodes' of bean class [nl.project.interceptor.MySimpleExceptionResolver]: Bean property 'statusCodes' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?

at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:1057)

at org.springframework.beans.BeanWrapperImpl.setPropertyValue(BeanWrapperImpl.java:920)

This makes it impossible to configure properties for 'statusCodes' in dispatcher-servlet.xml

Affects: 3.1 RC1

Issue Links:

#13409 Impossible to set SimpleMappingExceptionResolver.statusCodes ("is duplicated by")

Referenced from: commits 5d42a62

1 votes, 1 watchers
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

Environment variables are resolved by npx instead of being left intact to be dealt with by the invoked node executable.

> npx --version
8.1.3
> npx argv-to-list $HOME '$HOME' 'price = $100'
/Users/soft # regular shell environment variable resolution
/Users/soft # why does npx resolve environment variables?
price = 00 # *ugh* this is bad...

Expected Behavior

> npx argv-to-list $HOME '$HOME' 'price = $100'
/Users/soft
$HOME
price = $100

Steps To Reproduce

cf above

Environment

npm: 8.1.3

Node: 16.13.0

OS: macOS 10.15.7 (19H1419)

platform: Darwin 19.6.0

npm config:

; "user" config from /Users/soft/.npmrc

@engine262:registry = "https://npm.pkg.github.com/"
//npm.pkg.github.com/:_authToken = (protected)
//registry.npmjs.org/:_authToken = (protected)
node_gyp = "/Users/soft/.nvm/versions/node/v14.18.0/lib/node_modules/node-gyp/bin/node-gyp.js"

; node bin location = /Users/soft/.nvm/versions/node/v16.13.0/bin/node
; cwd = /Users/soft/Desktop/swag
; HOME = /Users/soft
; Run `npm config ls -l` to show all defaults.

Issue 2:
Continuously getting this error when using NPM-cli, executing the command "npm ci":

10:58:07 + npm ci

10:58:34 npm ERR! cb() never called!

10:58:34

10:58:34 npm ERR! This is an error with npm itself. Please report this error at:

10:58:34 npm ERR! https://npm.community

Would you please take a look? This is not the first time notice that.
Issue 1:
The CSV file storing the index for the FilesystemStorage of the profiler contains duplicates for each request. Each request appears 3 times in the index. This breaks the search as limiting to 10 results only gives me 4 results.

Issue 2:
Hey guys-

After the annotations change, the doctrine:generate:entity task no longer works. There are basically 2 problems:

No annotation prefix is set on the entity in the command. This is probably easily rectified by adding:

$entityGenerator->setAnnotationPrefix('ORM\\');

source: https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/DoctrineBundle/Command/GenerateEntityDoctrineCommand.php#L103

It doesn't appear that Doctrine's EntityGenerator supports the addition of the use statements necessary in the generated class to import the ORM annotations namespace.

source: https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Tools/EntityGenerator.php#L207

Thoughts?
Issue 1:
Currently, if you call the navigate function of the router within a component constructor, 1 of 2 things happens. Either it changes the route just fine, or it throws the following runtime error:

TypeError: Cannot read property 'constructor' of undefined

An error is ONLY thrown if the project includes a custom pipe. There may be other circumstances which cause the runtime error to be thrown, but this is definitely one of them. This can be very misleading that calling navigate works fine, and then adding a custom pipe breaks this. This would lead developers to think that they have created their pipe wrong, or that somehow a custom pipe is breaking their system. Further complicating the matter is the fact that the stack trace doesn't point at the call to router.navigate

Issue 2:
When using a custom pipe inside of an ng-switch-default the pipe breaks with the exception:

EXCEPTION: TypeError: Cannot read property 'constructor' of undefined in [null]

TypeError: Cannot read property 'constructor' of undefined
at Object.implementsOnDestroy (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:7655:16)
at Function.ChangeDetectionUtil.callPipeOnDestroy (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:16480:38)
at AbstractChangeDetector.ChangeDetector_Hello_5.dehydrateDirectives (eval at <anonymous> (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:20571:14), <anonymous>:93:49)
at AbstractChangeDetector.dehydrate (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:20384:12)
at AppViewManagerUtils.dehydrateView (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:17481:35)
at AppViewManager_._viewDehydrateRecurse (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:21117:21)
at AppViewManager_._destroyViewInContainer (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:21105:12)
at AppViewManager_.destroyViewInContainer (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:21060:12)
at ViewContainerRef_.remove (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:9707:24)
at ViewContainerRef_.ViewContainerRef.clear (https://code.angularjs.org/2.0.0-alpha.45/angular2.dev.js:9632:14)BrowserDomAdapter.logError @ angular2.dev.js:21984ExceptionHandler.call @ angular2.dev.js:4439(anonymous function) @ angular2.dev.js:19685NgZone._notifyOnError @ angular2.dev.js:10746errorHandling.onError @ angular2.dev.js:10654run @ angular2.dev.js:141(anonymous function) @ angular2.dev.js:10678zoneBoundFn @ angular2.dev.js:111lib$es6$promise$asap$$flush @ angular2.dev.js:1301
2015-11-06 15:24:17.011 angular2.dev.js:21984 ERROR CONTEXT:BrowserDomAdapter.logError @ angular2.dev.js:21984ExceptionHandler.call @ angular2.dev.js:4442(anonymous function) @ angular2.dev.js:19685NgZone._notifyOnError @ angular2.dev.js:10746errorHandling.onError @ angular2.dev.js:10654run @ angular2.dev.js:141(anonymous function) @ angular2.dev.js:10678zoneBoundFn @ angular2.dev.js:111lib$es6$promise$asap$$flush @ angular2.dev.js:1301

Here is a plunker: http://plnkr.co/edit/PSRVVPtbl6MzRzNPzc2b?p=preview

When I remove the ng-switch-default template, I don't get the error.

Using Chrome 46 on Mac.
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 an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

9.0.0, 9.0.4

Operating System:

Windows 10

Last Known Working Electron version:

Expected Behavior

Ctrl - should not zoom out the window (preferred) OR

Ctrl - (using the minus that is not on the numpad) zoom out should be reversible with Ctrl + to zoom in

Actual Behavior

When you hit Ctrl + - (using the - on the keyboard, not the one on the numpad), electron causes the zoom factor to change.

To Reproduce

Run electron.exe

Click Ctrl + - (use the minus on the main keyboard, not the numpad)

The window will zoom out and you cannot zoom back in with Ctrl + +

Screenshots

Default:

Clicked Ctrl + - a few times:

Additional Information

After some debugging in the browser, I discovered that Ctrl + - on the keyboard actually seems to trigger a Ctrl + Shift + -. This might be the problem.

Potentially Related Issues:

#15496

Issue 2:
Electron version: 1.7.9

Operating system:

win7 X64

The width of the new window is 768, the height is 480, the actual open window width is 960, and the height is 600.

When I created a new window, the actual size of the window was always about 1.25 times the size of the window, and I saw that the devicePixelRatio of the window was 1.25, which was generated after the release of the electron 1.4.16.How do I do that?