WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
https://console.cloud.google.com/storage/kubernetes-jenkins/logs/kubernetes-e2e-gke/7625/

Failed: [k8s.io] SSH should SSH to all nodes and run commands {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/ssh.go:93
May 23 19:12:07.338: Ran echo "Hello" on 104.154.63.130:22, got error error getting SSH client to jenkins@104.154.63.130:22: 'timed out waiting for the condition', expected <nil>

Issue 2:
Refs #9075 as @thockin wants (we all do) CoreOS documentation to be sober on 1.0 release.

@thockin @erictune @AntonioMeireles I have questions.

Care if we remove single-node instructions? I don't think this makes sense anymore, unless someone is going to use hyperkube.

master.yaml needs instrumentation to generate service-account private key file, so it will depend on openssl. Any objections?

We should add DNS integration as many examples depend on it. Objections?

We should move aws folder from getting-started-guides folder, to getting-started-guides/coreos, in order to match how it's done with azure.

Speaking of which @errordeveloper @squillace @chanezon @crossorigin do you agree with questions 1, 2 and 3? Also, can we sync effort to get it homogeneous on all different CoreOS approaches?
Issue 1:
Main page - http://twitter.github.com/bootstrap/, pressing the big "Download Bootstrap" gives you everything.

Going to customize - http://twitter.github.com/bootstrap/download.html (specifically Responsive layouts)

Having everything checked, scrolling to the bottom, and downloading - doesn't give you bootstrap-responsive.css

Wondering why all my menus were going nuts. Thanks!

Issue 2:
The default download has the responsive and non-responsive as separate files, but the customizer combines them into a single file. They should have the same file structure, so the customize should give you the responsive layouts in a separate bootstrap-responsive.css. Will make it less confusing as to whether you have a bootstrap file that has responsive layouts or not.
Issue 1:
Stefan Ocke opened SPR-8040 and commented

When using HiddenHttpMethodFilter, like for example Spring Roo generated apps do, the ServletRequest is wrappd into a HttpMethodRequestWrapper (at least in cases, where wrapping is necessary, for example for PUT requests emulated with POST and httpMethod parameter).

Later, when it comes to data binding the ServletRequestDataBinder.bind method checks for multipart requests:

MutablePropertyValues mpvs = new ServletRequestParameterPropertyValues(request);
if (request instanceof MultipartRequest) {
MultipartRequest multipartRequest = (MultipartRequest) request;
bindMultipart(multipartRequest.getMultiFileMap(), mpvs);
}
doBind(mpvs);

But if the multipart request has been wrapped into a HttpMethodRequestWrapper , this won't work anymore, since it is not an instance of MultipartRequest. Thus, no databinding for the Multipart files occurs.

NOTE: My setup ist the following:

I am using a MultipartFilter in front of the WebMethodFilter, as suggested in bold letters in the Javadoc of HiddenHttpMethodFilter

I am using binding for the uploaded files, instead of "injecting" them as parameters in the controller mehtods. For this, I register an according converter / bean editor from MultipartFile to byte array

For POST request, this setup works fine. For PUT (emulated by POST and httpMethod parameter), the problem described above arises.

Affects: 3.0.5

Issue Links:

#12451 ServletRequestDataBinder does not bind MultipartFile with HiddenHttpMethodFilter and Multipart Request ("duplicates")

Issue 2:
Arun Reddy opened SPR-2171 and commented

The form:form tag set the 'id' value to 'null' when not specified and does not take into consideration the value specified for the 'name' attribute.

For example,

i) No 'id' or 'name' attribute specified

<form:form action="actionUrl" method="post" commandName="commandObjectName"> </form:form> results in

<form id="null" name="null" method="post" action="actionUrl"></form>

ii) 'name' attribute specified

<form:form name="formName" action="actionUrl" method="post" commandName="commandObjectName"></form:form> results in

<form id="null" name="null" method="post" name="formName" action="actionUrl"></form>

iii) 'id' and 'name' attribute is specified

<form:form id="formId" name="formName" action="actionUrl" method="post" commandName="commandObjectName"></form:form> results in

<form id="formId" name="null" method="post" name="formName" action="actionUrl"></form>

This behaviour is inconsistent with that in previous milestone releases.

Affects: 2.0 RC1
Issue 1:
On Windows (and Ubuntu with Unity Desktop Manager), clicking on a taskbar item with the scroll wheel button, middle mouse button, or shift + click causes a new window to be opened instead of an existing instance. VS Code does not do this.

Repro:

Open VS Code and open a folder.

Click the VS Code icon using the scroll wheel click.

Expected: A new VS Code window will open

Actual: The existing VS Code window is shown.

Issue 2:
VSCode Version: 1.0.0

OS Version: Windows 10 64bit

Steps to Reproduce:

Open any js file

Write ternary if statement

Syntax highlight will be broken.
Issue 1:
Describe the bug

I've registered to the before_update hook with:

class MyTable(Base):
id = Column("id", UUID_DB(as_uuid=True), primary_key=True, default=uuid4)

from sqlalchemy import MetaData, event
event.listen(MyTable, "before_update", modified_at_hook)

def modified_at_hook(mapper, connection, target):
...

then executing an update statement:

stmt = (
sqlalchemy.update(MyTable)
.where(table.id == obj_id)
.values(**dict_object)
.execution_options(synchronize_session="fetch")
)
async with AsyncSession(db_engine.get_engine()) as async_session:
result = await async_session.execute(stmt)
await async_session.commit()

but the hook is not being triggered.

When I am trying to use the merge function of the async_session, only before_insert hook is triggered. and there is no .update method for async session.

Further more, when using the .add method, and the entity has id, I get exception that the entity is already exist. how can I mark the entity for update without using SELECT to retrieve it first?

Optional link from https://docs.sqlalchemy.org which documents the behavior that is expected

No response

SQLAlchemy Version in Use

1.4.40

DBAPI (i.e. the database driver)

default

Database Vendor and Major Version

PostgreSQL 12

Python Version

3.11

Operating system

losx

To Reproduce

aboe

Error

no error

Additional context

No response

Issue 2:
Migrated issue, originally created by Karol Narowski

Function is not called when set in listener. before_insert and after_insert is working well but before_update and after_update are not called.

Ex.

class User(Base):
__tablename__ = 'users'

uid = Column(String(36), primary_key=True, unique=True, default=generate_uuid)
name = Column(String(15), nullable=False)
description = Column(String(25), nullable=False)
phone = Column(String(20), nullable=False)
hash = Column(String(128), nullable=True, unique=True)
created_on = Column(DateTime(), default=datetime.utcnow)
updated_on = Column(DateTime(), default=datetime.utcnow, onupdate=datetime.utcnow)
@listens_for(User, 'before_insert')
def before_insert_function(mapper, connection, target):
print(target.phone)
target.hash = "OtherInsert"

@listens_for(User, 'before_update')
def before_update_function(mapper, connection, target):
print(target.uid)
print(target.phone)
target.hash = "OtherUpdate"
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

I'm hoping that this issue will resolve the problem I'm seeing.

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

deployment, replica set, OldReplicaSets

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.4", GitCommit:"3b417cc4ccd1b8f38ff9ec96bb50a81ca0ea9d56", GitTreeState:"clean", BuildDate:"2016-10-21T02:48:38Z", GoVersion:"go1.7.1", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.5", GitCommit:"5a0a696437ad35c133c0c8493f7e9d22b0f9b81b", GitTreeState:"clean", BuildDate:"2016-10-29T01:32:42Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Google Container Engine

What happened:

I ran kubectl apply -f as usual to apply any changes to Deployment, Service, Ingress resources. The deployment did not create a new replica set with the updated container image. Going to the Kubernetes Dashboard I can confirm that the deployment was correctly updated with the new metadata.

The only difference when this issue started happening was a small code change.

I've tried multiple updates since and nothing changed. The nodes were on version 1.4.0 but I've tried updating them to 1.4.5 but still the same issue is happening.

The old pods are still operational and serving requests normally.

What you expected to happen:

The deployment should have created a new replica set with three pods, then rolled them out.

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

I don't know.

Anything else do we need to know:

I've attached a file with the deployment's current configuration, as well as the deploy script I use to deploy: files.zip

Here's the output of kubectl describe:

$ kubectl describe deployment/fika-io
Name:	fika-io
Namespace:	default
CreationTimestamp:	Sun, 16 Oct 2016 10:58:42 -0400
Labels:	app=fika-io
Selector:	app=fika-io
Replicas:	3 updated | 3 total | 3 available | 0 unavailable
StrategyType:	RollingUpdate
MinReadySeconds:	0
RollingUpdateStrategy:	1 max unavailable, 1 max surge
OldReplicaSets:	fika-io-749979362 (3/3 replicas created)
NewReplicaSet:	<none>
No events.

Note that there is no NewReplicaSet.

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/31373/kubernetes-pull-build-test-e2e-gce/56869/

Failed: [k8s.io] Downward API volume should provide podname only [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:134
Aug 31 15:48:21.680: Couldn't delete ns: "e2e-tests-downward-api-okpt6": the server could not find the requested resource
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:338

Happened on a presubmit run in #31373.
Issue 1:
Similar to atom.commands.onWillDispatch and atom.commands.onDidDispatch. This would be useful for extensions wanting to perform some action before or after a command is performed.

Being able to determine the source of the event would be useful in such an API (mouse vs keyboard vs command palette).

Issue 2:
I am building an extension for VS Code. My extension will show the key bindings associated to a recently action (I am a fan of this for helping me learn key bindings).

Looking through the documentation there seems to be a way to access the commands in the editor, but no way that I can find to listen for actions / commands as they are invoked.

I would like the ability to listen for all user actions and then react to their actions.
Issue 1:
When running fourier_uniform from SciPy's ndimage, seem to be getting an inaccurate result with SciPy 1.0.0+. The problem is not present in SciPy pre-1.0.0 (e.g. 0.19.1).

Reproducing code example:

From SciPy 0.19.1:

In [1]: import numpy as np

In [2]: import scipy.ndimage as spimg

In [3]: spimg.fourier_uniform(np.arange(5, dtype=float), 1)
Out[3]: array([ 0. , 0.93548928, 1.51365346, 2.27048019, 3.74195714])

From SciPy 1.1.0:

In [1]: import numpy as np

In [2]: import scipy.ndimage as spimg

In [3]: spimg.fourier_uniform(np.arange(5, dtype=float), 1)
Out[3]:
array([0.00000000e+000, 5.25819693e-315, 5.28483274e-315, 5.31059453e-315,
5.34108739e-315])

Scipy/Numpy/Python version information:

1.1.0 1.15.1 sys.version_info(major=3, minor=6, micro=6, releaselevel='final', serial=0)

Issue 2:
bdtr returns nan whenever n > 2**31 - 1. For example,

In [14]: import scipy

In [15]: scipy.__version__
Out[15]: '1.2.0.dev0+dfc9a9c'

In [16]: from scipy.special import bdtr

In [17]: bdtr([0, 2**30, 2**31-1], 2**31, 0.5)
Out[17]: array([nan, nan, nan])

If I use n = 2**31-1, the values are not nan:

In [18]: bdtr([0, 2**30, 2**31-1], 2**31-1, 0.5)
Out[18]: array([0. , 0.8891082, 1. ])

This is on a 64 bit system.

This looks related to #5503, but I don't know if it is a duplicate.

bdtr(k, n, p) calls incbet(n - k, k+1, 1.0-p), so the underlying problem is probably in incbet. Note that the first two arguments of incbet are double, not integers.

This problem was reported as a question on stackoverflow, where it appeared as a problem with scipy.stats.binom.cdf:

In [26]: from scipy.stats import binom

In [27]: binom.cdf([0, 2**30, 2**31-1], 2**31, 0.5)
/Users/warren/miniconda36/lib/python3.6/site-packages/scipy-1.2.0.dev0+dfc9a9c-py3.6-macosx-10.7-x86_64.egg/scipy/stats/_discrete_distns.py:60: RuntimeWarning: floating point number truncated to an integer
vals = special.bdtr(k, n, p)
Out[27]: array([nan, nan, nan])
Issue 1:
We have developed a custom server side rendering solution to allow for asynchronous data loading. Once everything is done we flush the final HTML to the browser along with all of the asynchronously loaded data written to the DOM. We are also generating a checksum the same way react does with server side rendering.

During initial mount in the browser, all of the data needed by the app is available, but our data contract layer uses Promises to provide data to those who request it. Our components don't know whether or not the data is available, but our data layer does. So components use the following pseudocode for loading data:

componentWillMount () {
SomeModel.get({ params }).then(this.setState);
}

Underneath the hood, our model layer knows whether or not the data is available and uses the data, otherwise it makes an ajax request for the data. But being that react's render is synchronous and Promises are asynchronous, there is no way for us to take advantage of the reuse-existing-markup logic within react. We have tested that if we return a synchronous Promise shim/hack, then everything works as expected - but we all know the dangers in doing this. Is there any way we can defer the checksum checks somehow? Is there a way we can render the vdom only (in memory) and then trigger the mounting logic? We don't want a detached dom with real dom nodes, we are wanting react to construct its vdom and then mount when we tell it to. Thanks.

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

A bug

What is the current behavior?

It duplicates error message to the error stack. I run react code pre-processed by webpack/babel in node virtual machine for SSR purposes. Therefore, I need to re-map the error stack to proper files/lines/columns when the error happens. A duplicated error message in error stack is not corresponding to a common error stack format which causes incorrect re-mapping and mess in the error output.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

The following error message was found both in e.message and e.stack:

Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

What is the expected behavior?

The error message should be found in e.message only.

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

react@16.8.6

webpack@4.36.1

@babel/core@7.5.5

@babel/runtime@7.5.5
Issue 1:
Version

2.3.0

Reproduction link

https://jsfiddle.net/superboy2k/50wL7mdz/38665/

Steps to reproduce

Click Init, Click Update a few times, click Add => see the error in the console

What is expected?

to update the ui correctly

What is actually happening?

TypeError: Cannot read property 'key' of undefined

at sameVnode (unpkg.com/vue@2.3.3:4769)

at updateChildren (unpkg.com/vue@2.3.3:5128)

at patchVnode (unpkg.com/vue@2.3.3:5180)

at updateChildren (unpkg.com/vue@2.3.3:5096)

at patchVnode (unpkg.com/vue@2.3.3:5180)

at updateChildren (unpkg.com/vue@2.3.3:5096)

at patchVnode (unpkg.com/vue@2.3.3:5180)

at Vue$3.patch [as patch] (unpkg.com/vue@2.3.3:5305)

at Vue$3.Vue._update (unpkg.com/vue@2.3.3:2327)

at Vue$3.updateComponent (unpkg.com/vue@2.3.3:2443)

Issue 2:
Vue.js version

2.0.0-rc5

Reproduction Link

https://jsfiddle.net/oldpig/zb4zLxkb/1/

Steps to reproduce

Click any tab to switch

What is Expected?

Tab switched, everything goes fine.

What is actually happening?

There are warnings in console, multiple times each switch.

I am aware that this warning is introduced in rc.5. But I am not sure what goes wrong.
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

It seems impossible to navigate to some path and clear any named outlets in the process. Consider this code:

this.router.navigate(['/', { outlets: { secondary: null } });

This does not remove the (secondary:) portion from the path. However this code does remove that segment:

this.router.navigate([{ outlets: { secondary: null } });

In addition this.router.navigateByUrl('/') also works.

Expected behavior

The first code should also work and remove the secondary outlet segment from the path.

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/hFsOdLLr2LCq8cJyOF6R?p=preview

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

The current behavior looks erroneous. I believe there should be an else here which sets children[outlet] to null so it is not initialized later.

Please tell us about your environment:

Angular version: 2.4.10

Code in master looks the same as in 2.4.10.

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

All browsers.

Language: [all | TypeScript X.X | ES6/7 | ES5]

I think it is a framework issue rather than a language one.

Node (for AoT issues): node --version =

Issue 2:
I'm submitting a ...

[X] bug report

Current behavior

I have some routes like:

const routes = [
{ path: "", component: HomeComponent, pathMatch: "full" },
{ path: "profile", component: ProfileComponent },
{ path: "menu", component: MenuComponent, outlet: "sidebar" },
];

When the route http://localhost/(sidebar:menu) is open, then I'm able to remove the named outlet and go to http://localhost/ by clicking an anchor like the following:

<a [routerLink]="['', {outlets: {sidebar: null}}]">
Close
</a>

What doesn't work is navigating away from the sidebar and also going to another route like http://localhost/profile.

<a [routerLink]="['/profile', {outlets: {sidebar: null}}]">
Close
</a>

The link that is rendered is http://localhost:3971/profile(sidebar:menu)

Expected behavior

The link that should be rendered is http://localhost:3971/profile.

Repro

https://github.com/tinchou/router-repro

Please tell us about your environment:

Windows 10, Visual Studio 2017

Angular version: 2.3.1 (didn't work with 2.1.0 either)

Browser: all

Language: TypeScript 2.0.10
Issue 1:
VSCode Version:1.2

OS Version: Ubunu 14.04

Steps to Reproduce:

Open vscode

Open ctrl+`

Try pasting a copied word to terminal by ctrl+shift+v

I can give more examples in case.

Issue 2:
Integrated terminal master issue: #143

Might need to use custom keybindings, ctrl+c terminates a process. Also it's probably not best to hijack ctrl+shift+c from open in new terminal.
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Two identical sub-dependencies are being included twice in the build.

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

projectA depends on libA@^2.0.0, depA and depB.

depA and depB both depend on libA@^1.0.0

This results in a directory structure like this:

projectA
- node_modules
-- libA
-- depA
---- node_modules/libA
-- depB
---- node_modules/libA

When the project is built, included in the bundle are:

libA@2.0.0
depA
depB
libA@1.0.0
libA@1.0.0

What is the expected behavior?

The included modules should be:

libA@2.0.0
depA
depB
libA@1.0.0

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

webpack@3.5.5

I have run npm dedupe but it can't fix the problem. This is understandable, because npm doesn't have anywhere to "put" this lower-version dependency that is shared by both depA and depB. Previously I believe this was solved with the DedupePlugin which has since been turned into a no-op.

Issue 2:
Bug report

What is the current behavior?

CVE-2021-27290

ssri 5.2.2-8.0.0, fixed in 8.0.1, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.

The fix is to bump ssri to 8.0.1.

The dependency path to ssri is webpack > terser-webpack-plugin > cacache > ssri

I've reported this issue in terser-webpack-plugin at webpack-contrib/terser-webpack-plugin#388

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

What is the expected behavior?

There shouldn't be any CVE's found when evaluating Webpack :)

Other relevant information:

webpack version: 4.46.0

Node.js version: all

Operating System: all
Issue 1:
This error happens in devtools (when running devtools shell), I didn't investigate it in detail, but seemingly the reason is that inside InteractionListItem.js we are trying to access commitData[commitIndex].duration however in some cases commitData is an array one index smaller than commitIndex.

Issue 2:
I think scryRenderedDOMComponentsWithClass (and all other methods starting with scry) should be deprecated in favor of more obvious names like findRenderedDOMComponentsWithClass.
Issue 1:
splitVertical is also

Issue 2:
Environment

Windows build number: winnt 10.0.18362 on x86_64
Windows Terminal version (if applicable): 0.2.1715.0

Any other software? Visual Studio 2017

Steps to reproduce

open windows terminal

click on arrow down near the plus button -> settings or directly click ctrl + ,

Visual Studio 2017 pops up

Expected behavior

I would expect to see a settings menu, definitely not vs2017

Actual behavior

vs2017 popus up