WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
System info

Playwright Version: [v1.34]

Operating System: [macOS 13.2]

Browser: [Chromium]

Other info:

the uta site is:

[https://github.com/your_profile/playwright_issue_title]](https://bonigarcia.dev/selenium-webdriver-java/drag-and-drop.html)

Issue 2:
System info

Playwright Version: v1.33

Operating System: Windows 10

Browser: Chromium

Other info:

Issue Description

I want to verify the contents of tips when hovers over some locators.

Headed Mode

Locator is visible without scrolling: √

Locator needs scrolling & depends on hover() itself to scrollIntoView: ×

Locator needs scrolling & manually trigger scrollIntoView in advance: √

Headless Mode

First condition above: √

Last two items above: ×

Why the 3rd condition worked in Headed while not worked in Headless? How the scrollIntoVieW method works?

The element needs to be hovered is a bit special, it may not depend on :hover, having tested in Chrome DevTools: added force state to it but the content didn't appeared too, so it maybe binds to other listeners.

I wonder if there is a solution to deal with such condition? Could locator.hover()continuously triggers until expect() statements to be done?

Source code

Test file (self-contained)

await page.getBytext('other locator nearby to trigger scrollIntoView').click();
await expect(page.getByText('${tip}')).toHaveCount(0);
await page.locator('xxx-label:visible').locator('.tool-tip').hover();
await expect(page.getByText('${tip}')).toHaveCount(1);

Steps

Run the test

Expected

All passed

Actual

Headed Mode

Locator is visible without scrolling: √

Locator needs scrolling & depends on hover() itself to scrollIntoView: ×

Locator needs scrolling & manually trigger scrollIntoView in advance: √

Headless Mode

First condition above: √

Last two items above: ×
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/.):

No.

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

kubectl defaultMode

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

Bug

Doing a kubectl edit deployment <deployment> fails with the error unless the defaultMode line is deleted :

Kubernetes version (use kubectl version):

Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.1", GitCommit:"50809107cd47a1f62da362bccefdd9e6f7076145", GitTreeState:"clean", BuildDate:"", GoVersion:"", Compiler:"", Platform:""}

Environment:

Cloud provider or hardware configuration: aws

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

Kernel (e.g. uname -a): n/a

Install tools: kube-up.sh

Others:

What happened:

kubectl edit failed

error: found invalid field defaultMode for v1.DownwardAPIVolumeSource

What you expected to happen:

kubectl edit succeeded.

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

use kubectl edit deployment <deployment> with kubectl version 1.4 talking to a kubernetes 1.2 cluster for a deployment that is using the Downward API eg.

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: nginx
spec:
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
image: nginx
ports:
- containerPort: 80
volumeMounts:
# name must match the volume name below
- name: podinfo
mountPath: /mnt
readOnly: false
volumes:
- name: podinfo
downwardAPI:
items:
- path: "annotations"
fieldRef:
fieldPath: metadata.annotations

Anything else do we need to know:

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

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

Kubernetes version (use kubectl version): 1.3.8 custom build - the code seems to still be in place in master.

Environment:

Cloud provider or hardware configuration: OpenStack

OS (e.g. from /etc/os-release): VERSION="14.04.5 LTS, Trusty Tahr"

Kernel (e.g. uname -a): 4.4.0-38-generic #57~14.04.1-Ubuntu SMP Tue Sep 6 17:20:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools: Custom

Others:

What happened:

When the OpenStack Nova API is not accessible Nodes are marked as "NotReady"

The OpenStack cloud providers seems to call Nova on a schedule to get information.

If the API is not contactable, kubelet fails to call back to the masters, and gets marked as NotReady.

Masters also call the Nova API, and when it fails, it can mark all nodes as NotReady.

What you expected to happen:

Nothing - the cluster should still work, regardless of Nova's API

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

Install Kubernetes using the OpenStack provider.

On the OpenStack controller stop the nova-api process.
Issue 1:
i tryin to build a port scanner with Deno

Deno.connect() need timeout for close tcp connection

i want when create connection after few seconds If did not get an answer do abort

like a nodejs:

const { Socket } = require("net");
const socket = new Socket();
socket.on("timeout", () => {
socket.destroy();
});
socket.setTimeout(200);
socket.connect(80, '8.8.8.8');

thanks

Issue 2:
Hey,

It would be really cool if Deno aligned with the web platform's cancellation primitive AbortSignal/AbortController which Deno already supports but not in most of its APIs.

Myself and a few others have been adding support for AbortSignal to all of the APIs it fits in Node.js to make it easier for people to write universal JavaScript code. For example:

Deno.readTextFile('./someFile', { signal });
Deno.writeTextFile('./someFile', { signal });

And more generally - in Deno's stream abstractions. Would you be open to adding this?

(Sorry for not being too available on Discord with the baby/health stuff/new job :))
Issue 1:
When I change app code, vendors.js will have a slight change as following image shows, this prevents me from doing long term caching.

It seems that chunk 0 refers to my app chunk, but it's unnecessary to have this in my vendors file.

How am I supposed to do to keep my vendors content same when I just change my app code?

Issue 2:
I'm trying to split my vendor code from my app code and got it all working. However, every time I change some code in my app and create a new build, the vendor file gets a new chunkhash and thus is downloaded by the clients again. The contents are exactly the same though.

Here is a fully working small example showing the problem: https://github.com/kevinrenskers/chunkhash-problem

And as you can see, the contents of these files are 100% identical even though the chunkhash keeps changing:
Issue 1:
Hi,

I was wondering if there are plans to release tensorflow for Python 3.6 and if so is there ETA?

Thank you.

Issue 2:
The current .whl does not support python 3.6. Please update to support the latest version of python. Thanks!

C:\WINDOWS\system32>python --version

Python 3.6.0

C:\WINDOWS\system32>pip install --upgrade https://storage.googleapis.com/tensorflow/windows/cpu/tensorflow-0.12.1-cp35-cp35m-win_amd64.whl

tensorflow-0.12.1-cp35-cp35m-win_amd64.whl is not a supported wheel on this platform.
Issue 1:
ss2zpk is implemented as

return tf2zpk(*ss2tf(A, B, C, D, input=input))

Please don't go through transfer-function form as it throws away numerical accuracy.

I am not sure of the best way to implement ss2zpk. The poles are easy: get the eigenvalues. Not sure about the zeros.

Related to the inverse function #5912.

Issue 2:
def ss2zpk(A, B, C, D, input=0):
return tf2zpk(*ss2tf(A, B, C, D, input=input))

I believe this has numerical stability problems, same as #3085
Issue 1:
Usually a mouse has 2 buttons but now a days many mice comes with more than 2 buttons and sometimes I need to remap those buttons.

Like the wheel button I want it to open the windows menu or the windows search, etc

And the next feature is the remapping of keys for multiple keyboards.Like if I have Two keyboards the the secondary keyboard can be completely remapped .

Issue 2:
Environment

Windows build number: 10.0.19041.329
PowerToys version: 0.19.1
PowerToy module for which you are reporting the bug (if applicable): PT Run

Run at Startup and Always Run as Administrator are both on. PowerToys Runner shows up in Task Manager.

Steps to reproduce

Make sure your keyboard shortcut to open PT run is Alt+Space

Press Alt+Space

Expected behaviour

PT run opens

Actual behaviour

Nothing
Issue 1:
Environment

Windows build number: Microsoft Windows [Versione 10.0.18362.836]
PowerToys version: 0.18.1
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Simply search

Expected behavior

Actual behavior

When used it does not search the files and the folders, only the programs.

Screenshots

Issue 2:
Environment

Windows build number: Windows 10 Home Single Language 1909
PowerToys version: 0.18.1
PowerToy module for which you are reporting the bug (if applicable): Run

Steps to reproduce

The v0.18.1 is only able to search for programs but not individual files, even when running in administrator mode.

Expected behavior

The v0.18.0 could search for all files and programs. The same was expected of the update.

For the sake of complete reporting, I went back and installed v0.18.0 and did not experience the issue, which would rule out any problem caused by settings on the device.

Actual behavior

Screenshots
Issue 1:
Let and var parameters of Javascript are not being colorized properly when used as part of a longer word/parameter inside a function.

fcamelCase = function( all, letter, lettuce, constest ) { var variance = letter.toUpperCase(); return variance; };

This is effecting the latest Alpha build (0.10.12-alpha)

Issue 2:
From @f111fei on February 23, 2016 6:14

version： 0.10.10

letter

Copied from original issue: microsoft/vscode#3270
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:

6.0.8

Operating System:

Windows 10 (Build 18362)

Last Known Working Electron version:

6.0.2

Expected Behavior

For the node-gyp to properly compile my native add on.

Actual Behavior

Getting a compiler error:

node.lib(node.exe) : fatal error LNK1112: module machine type 'ARM64' conflicts with target machine type 'x64' (this file comes from https://atom.io/download/electron)

To Reproduce

Run node-gyp for a native add on...

node-gyp build --target=6.0.8 --arch=x64 --dist-url=https://atom.io/download/electron

Screenshots

Additional Information

This is only happening on x64, ia32 is still working as intended.

Issue 2:
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:

6.0.8

Operating System:

Windows Server 2016 and 2019

Last Known Working Electron version:

6.0.7

With the 6.0.8 binaries, native module builds are now failing with:

node.lib(node.exe) : fatal error LNK1223: invalid or corrupt file: file contains invalid .pdata contributions
Issue 1:
Viewing page in chrome with basic fluid layout. After resizing browser window to minimum in width and resizing back to normal size the dropdown in nav-bar doesn't open.

Issue 2:
Minor issue but...

If you have a responsive page with navbar and a dropdown in the navbar, and you make your browser small, then click the responsive menu button to uncollapse the menu, then open your browser large again, the navbar dropdown no longer works.
Issue 1:
Environment

Windows build number: [versão 10.0.19631.1]
PowerToys version: v0.18.1
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run

Steps to reproduce

By checking Task Manager

Expected behavior

The PowerToy Run service called PowerLuncher is consuming almost half of the device's CPU and memory when running. After disabling the function, the consumption dropped to 6%, even while running IntelliJ, VSCode, Edge, and Groove at the same time. Please check the screenshots below:

Actual behavior

Screenshots

With PowerToy Run enabled:

With PowerToy disabled:

Issue 2:
PowerLauncher.exe keeps ramping up to ~60% CPU usage in task manager and then back down to 0%. It happens about every 2 seconds or so.

Environment

Windows [Version 10.0.18363.720]

PowerToys 0.18

PowerLauncher

Steps to reproduce

Start PowerToys.

Screenshots
Issue 1:
Narada Sage opened SPR-6652 and commented

Hi,

As mentioned in forum post there is a bug in the spel documentation where a method is used on the interface that in fact only exists on the concrete class. More details on the forum post.

Many thanks.

Affects: 3.0 GA

Reference URL: http://forum.springsource.org/showthread.php?t=82258

Issue Links:

#11380 Wrong example of SpEL in chapter 6.3 in reference documentation ("is duplicated by")

Issue 2:
Anders Wallgren opened SPR-5275 and commented

This method throws an exception if the linked exception's message is null. I've patched it locally as follow:

/**
* Build a descriptive exception message for the given JMSException,
* incorporating a linked exception's message if appropriate.
* @param ex the JMSException to build a message for
* @return the descriptive message String
* @see javax.jms.JMSException#getLinkedException()
*/
public static String buildExceptionMessage(JMSException ex) {
String message = ex.getMessage();
Exception linkedEx = ex.getLinkedException();
if (linkedEx != null && (linkedEx.getMessage() == null || message.indexOf(linkedEx.getMessage()) == -1)) {
message = message + "; nested exception is " + linkedEx;
}
return message;
}

Affects: 2.5.6

Issue Links:

#10005 JmsException.getMessage throws NPE if a cause doesn't have a message ("is duplicated by")

#10075 NullPointerException in JmsException ("is duplicated by")

#10455 NullPointerException in JmsUtils.buildExceptionMessage ("is duplicated by")

#10626 NullPointerException in JmsUtils.buildExceptionMessage() ("is duplicated by")

#10721 NullPointerException can occur from JmsUtils.buildException ("is duplicated by")

#10143 Possible NPE in JmsUtils.buildExceptionMessage and JmsException.getMessage ("is duplicated by")
Issue 1:
I really like the new callouts in the docs, but ask myself why they are reserved for the docs?

They look way better than the default alerts, imo they can be replaced by callouts.

Issue 2:
What about modularity in bootstrap 4?

I mean separation bootstrap into modules, for example: bootstrap-buttons, bootstrap-navbar, bootstrap-grid etc

Motivation

I have worked on some not big projects which needed customized subset of bootstrap: grid, bottons, icons.

I solved this problem in different ways:

Downloading "compiled" bootstrap (css, one js file) and customizing by my scripts - very hacky =(

Building custom bootstrap (by customizing variables). It requires to keep own fork of bootstrap or integrate build stage of bootstrap into build stage of project. It did not solve the problem that custom bootstrap had unnecessary modules.

Building necessary part of bootstrap in build stage of project (only necessary less and js files). I faced with errors when mixins was moved to subdirectory.

I think that separation bootstrap into modules will make easier the creation of custom builds without unnecessary parts and without unnecessary hacks.

Bootstrap itself can depend on all its "modules" (bower have "devDependencies" feeld) and I think that bootstrap should have compiled (css, one js) version of all its modules in "dist" folder. It allows to prototype something without build tool.
Issue 1:
Found an error:

Example 1

function safeAsync(fn) {
return async (...args) => {
try {
await fn(...args)
} catch (err) {
handleError(err)
}
}
}

async function a(q) {
console.log(q)
}

async function m() {
await safeAsync(a)(123)
}

// should print 123, but prints [Function a]
m()

But if I add console.log(args), it's working:

Example 2

function safeAsync(fn) {
return async (...args) => {
try {
console.log(args)
await fn(...args)
} catch (err) {
handleError(err)
}
}
}

async function a (q) {
console.log(q)
}

async function m() {
await safeAsync(a)(123)
}

// prints [123] 123 as expected
m()

Issue 2:
Hi,

It seems there is a bug when combining async + rest parameters syntax.

Here is a simplified version that reproduces the case with a simple async of value.

const foo = async (...msgs) => {
let t = await msgs[0];
console.log(t);
}

foo('a'); // displays "{}" instead of "a" value

Just by adding console.log(msgs), it makes it work.

const foo = async (...msgs) => {
console.log(msgs);
let t = await msgs[0];
console.log(t);
}

foo('a'); // displays "a"

Basically, adding console.log(msgs) moves the args to a distinct array:

for (var _len = arguments.length, msgs = Array(_len), _key = 0; _key < _len; _key++) {
msgs[_key] = arguments[_key];
}

In the repl:

https://babeljs.io/repl/#?experimental=true&evaluate=true&loose=false&spec=false&code=const%20asyncArg%20%3D%20async%20(msg)%20%3D%3E%20%7B%0D%0A%20%20let%20t%20%3D%20await%20msg%3B%0D%0A%20%20console.log(t)%3B%0D%0A%7D%0D%0A%0D%0Aconst%20asyncArgs%20%3D%20async%20(...msgs)%20%3D%3E%20%7B%0D%0A%20%20let%20t%20%3D%20await%20msgs%5B0%5D%3B%0D%0A%20%20console.log(t)%3B%0D%0A%7D%0D%0A%0D%0AasyncArg('1')%3B%0D%0AasyncArgs('2')%3B%0D%0A
Issue 1:
This is reproducible by deleting an index, not waiting for the response, then trying to bulk index into that index, (ie the requests were run in parallel):

[2014-01-11 14:34:30,541][INFO ][cluster.metadata ] [Justin Hammer] [test_index] creating index, cause [auto(bulk api)], shards [5]/[1], mappings []
[2014-01-11 14:34:31,007][INFO ][cluster.metadata ] [Justin Hammer] [test_index] update_mapping [test_type] (dynamic)
[2014-01-11 14:34:33,131][INFO ][cluster.metadata ] [Justin Hammer] [test_index] deleting index
[2014-01-11 14:34:33,156][DEBUG][action.bulk ] [Justin Hammer] [test_index][0], node[LthVQsuVRsyVgKZZr8_gpA], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.bulk.BulkShardRequest@cfd5855]
java.lang.NullPointerException
at org.elasticsearch.action.bulk.TransportShardBulkAction.shards(TransportShardBulkAction.java:136)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shards(TransportShardBulkAction.java:73)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performReplicas(TransportShardReplicationOperationAction.java:610)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:557)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)

Issue 2:
This happened on elasticsearch 0.90.6 with JVM 1.7.0_25

Found this in logs, cannot tell what triggered this. The only thing I know is, there are lots of index/search operations going and there seems to be some cluster instability.

[2013-XX-YY 08:45:22,518][DEBUG][action.bulk ] [myNode] [logstash-2013.XX.YY][3], node[vXE6ojncQUG-foPsMjVY_w], [P], s[STARTED]: Failed to execute [org.elasticsearch.action.bulk.BulkShardRequest@28c7fa4f]
java.lang.NullPointerException
at org.elasticsearch.action.bulk.TransportShardBulkAction.shards(TransportShardBulkAction.java:138)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shards(TransportShardBulkAction.java:75)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performReplicas(TransportShardReplicationOperationAction.java:610)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:557)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
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

When ELECTRON_RUN_AS_NODE is enabled, setTimeout is basically broken. It works the first time it's used, not the second time.

Electron Version:

Every version between 6.0.0 & 9.0.0-beta12

Operating System:

macOS 10.14.6 & Ubuntu 18.04

Last Known Working Electron version:

None

Expected Behavior

setTimeout should work consistently

Actual Behavior

When ELECTRON_RUN_AS_NODE is enabled, setTimeout is basically broken. It works the first time it's used, not the second time.

To Reproduce

$ git clone https://github.com/arantes555/electron-bug-settimeout.git
$ npm install
$ npm start

This runs multiple times, with the current node & with versions of electron from 6 to 9.

For a given run, it prints IT WORKED! when setTimeout works normally, and nothing otherwise.

Additional Information

Somehow, when wrapping the setTimeout in a process.nextTick, or a setImmediate, it works.

This makes me thing that it's linked to #7079 and to the activation of the uv loop in lib/common/init.ts .

Issue 2:
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

13.1.9

What operating system are you using?

Ubuntu

Operating System Version

Ubuntu 20.04

What arch are you using?

x64

Last Known Working Electron version

11.0.5

Expected Behavior

Prints the webpage

Actual Behavior

Not printing, no error.

Testcase Gist URL

No response

Additional Information

I found issue tracker with same problem for version 5 #18123 It is working fine in 11.0.5 but no success with 12 or 13 branch.

Example:

`let printersInfo = printWindow.webContents.getPrinters();

let printer = printersInfo.filter(printer => printer.isDefault === true)[0];

const options = {

silent: true,

deviceName: printer.name

}

printWindow.webContents.print(options, () => {
printWindow = null;
});`