WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I am testing new native HTTP/2 server and got a problem while trying to handle requests asynchronously, I am just can't get the response. My code:

const listener = Deno.listenTls({
port: 2022,
certFile: "./localhost.pem",
keyFile: "./localhost-key.pem",
alpnProtocols: ["h2", "http/1.1"],
});

for await (const conn of listener) {
handleConn(conn);
}

async function handleConn(conn: Deno.Conn) {
const httpConn = Deno.serveHttp(conn);
for await (const c of httpConn) {
handleHttpConn(c);
}
}

async function handleHttpConn(conn: Deno.RequestEvent) {
await Promise.resolve(); // pretending to do some looooong job
conn.respondWith(new Response(`Responding to ${conn.request.url}`));
}

When I am using simple non-async function everything works fine.

Issue 2:
Essentially the same as what's happening in #8107, but when using Deno.listenTls(). I noticed that issue was closed but the problem is still persisting. Every once in a while, the server will output errors like,

Sending fatal alert HandshakeFailure

or

Illegal SNI hostname received [49, 53, 57, 46, 56, 57, 46, 50, 50, 46, 50, 51, 57]
Sending fatal alert DecodeError

Eventually after a while, the TLS listener will simply hang and will cease to receive new connections (the following loop will cease to progress),

const listener = Deno.listenTls(/* ... */);
for await (const connection of listener)
/* this loop freezes */

This doesn't happen with a non-TLS listener (using Deno.listen()). I belive std/http has a similar problem. Previously, this would cause the server to crash completely, so at least there was a workaround in putting the server in an infinite loop to restart whenever it crashes, but since it just causes the loop to hang, this is not really an option without resorting to something much more complicated.
Issue 1:
When concatenating empty list with a list of INTEGERS result is an array of FLOATS. Since numpy 1.12 you can not use floats (result of such concatenation) for indexing without additional convertion from float to integer.

Following example works in numpy <=1.11 and does not work in numpy >= 1.12:

array = np.arange(3)
ind0 = []
ind1 = [1]
total_ind = np.concatenate([ind0, ind1])
print array[total_ind]

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/988 on 2009-01-22 by trac user kelson, assigned to unknown.

Howdy,

After searching for this defect, perhaps nobody else has been bothered

by this behaviour, but has anybody else noticed:

concatenate ( [[1],[2],[3],[4]] ).dtype = int32

concatenate ( [[1],[2],[3],[]] ).dtype = int32

concatenate ( [[],[2],[3],[4]] ).dtype = float64

I have a lot of old-style Numeric stuff that likes to concatenate lists

of indices which then were used with take [which does not like floats]. So

below [in theory] I attach my attempt at a patch so that empty items in the sequence are

not used to influence the common type that is used by PyArray_ConvertToCommonType.

Maybe it is of some value, or maybe I didn't do this in a kosher manner and

someone else has an idea of where things should be rethought for this defect?

Cheerio.
Issue 1:
ISSUE TYPE

Feature Idea

COMPONENT NAME

group

user

ALL (almost)

ANSIBLE VERSION

N/A

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

All users need all the time to support optional parameteres when using modules. Eg for group module for gid the "" or 0 etc. are not suitable values:

group:

gid: '{{ user.gid | default("") }}'

...

user:

uid: '{{ user.uid | default("") }}'

...

So for group, user etc. modules there is needed to be duplicate code to support if parameter is defined or not (and module's default value should be used). Now the duplicated code would eg. use when clause to have the wanted functionality. It's bad.

Could Ansible have default value to support this?

Issue 2:
Issue Type:

Bug Report

Ansible Version:

ansible 1.6

Environment:

Mac OS X 10.7

Summary:

rules_egress was added to ec2_group in 1.6 (previous there was no rules_egress). Unfortunately it defaults to nothing in it, meaning that previous ansible scripts will not allow anything out of a security group. This breaks many security groups.

Steps To Reproduce:

Create a ec2_group (security group) with no rules_egress. Watch everything get blocked going outbound.

Expected Results:

Should default to allowing everything outbound since thats what ansible did previously.

Actual Results:

Unable to access going outbound.
Issue 1:
I am currently implementing the remember me functionality. The REMEMBERME cookie is correctly set, but the logout fails.

What happens is that the LogoutListener is first called on the GetResponseEvent, but when comming here there is no token in the context, so the remember me logout is not called and does not delete the cookie. On the same listener routine, the remember me service is called later on and thus identifies the user.

Am I doing something wrong, or the listening sequence is wrong ?

EDIT I fixed the issue here, but it was because the remember me service is not registered as a logout handler automatically.

Issue 2:
The File constraint should support the following notations for the "maxSize" option:

new File(array('maxSize' => 1234)); // bytes
new File(array('maxSize' => '2k')); // kilobytes (case insensitive)
new File(array('maxSize' => '2ki')); // kibibytes (case insensitive)
new File(array('maxSize' => '1m')); // megabytes (case insensitive)
new File(array('maxSize' => '1mi')); // mebibytes (case insensitive)

// etc.

The conversion of the passed value to the number of bytes should be done already in the constructor of File, to simplify dealing with the file constraint:

$constraint = new File(array('maxSize' => '1ki'));

assert 1024 === $constraint->maxSize;
Issue 1:
#![feature(phase)]

#[phase(syntax, link)] extern crate std;

warning: using multiple versions of crate `std`
foo.rs:1:1: 1:1 note: used here
foo.rs:1 #![feature(phase)]
^
note: crate_id: std#0.11.0-pre
foo.rs:3:24: 3:41 note: used here
foo.rs:3 #[phase(syntax, link)] extern crate std;
^~~~~~~~~~~~~~~~~
note: crate_id: std#0.11.0-pre
error: duplicate entry for `malloc`
error: duplicate entry for `free`
error: duplicate entry for `strdup_uniq`
error: duplicate entry for `eh_personality`
error: duplicate entry for `managed_heap`
error: duplicate entry for `gc`
error: aborting due to 6 previous errors

This should link in the same version of libstd, not two separate versions.

Issue 2:
My keyboard layout is french canadian and the question mark shortcut does not work properly. It seems that this line is causing the issue. To make a question mark, I use SHIFT+6, so it doesn't fire one event with a whichof 191, but two events, one with 54 (6) and one with 16 (SHIFT).
Issue 1:
System info

Playwright Version: 1.32.1

Operating System: macOS 12.6.3

Browser: All

Other info:

Source code

Config file

projects: [
{ name: 'setup', testMatch: /auth\.setup\.ts/ },
{
name: 'main tests',
use: {
...devices['Chromium'],
storageState: 'playwright/.auth/admin.json',
},
testDir: './tests',
dependencies: ['setup'],
}]

Steps

tick "show browser" in VSCode

Run the test

Expected

Works as per show browser not set

Actual

Error: browserType.connect: WebSocket error: connect ECONNREFUSED 127.0.0.1:60054
=========================== logs ===========================
<ws connecting> ws://127.0.0.1:60054/e79324c018f1f82bb758d495bb34451a
<ws error> ws://127.0.0.1:60054/e79324c018f1f82bb758d495bb34451a error connect ECONNREFUSED 127.0.0.1:60054
<ws connect error> ws://127.0.0.1:60054/e79324c018f1f82bb758d495bb34451a connect ECONNREFUSED 127.0.0.1:60054
<ws disconnected> ws://127.0.0.1:60054/e79324c018f1f82bb758d495bb34451a code=1006 reason=
============================================================

Issue 2:
System info

Playwright Version: [v1.35.1]

Test Env: MacOS 13.4.1, K8S

Browser: [Chromium]

Test Runner: Playwright test v1.45.1

Script language: Typescript

Source code

KubernetesPod.yaml

apiVersion: v1
kind: Pod
metadata:
name: playwright
spec:
imagePullSecrets:
- name: vungleregistrykey
containers:
- name: playwright
image: mcr.microsoft.com/playwright:v1.35.1-jammy
imagePullPolicy: IfNotPresent
resources:
requests:
memory: "5Gi"
cpu: "8"
limits:
memory: "10Gi"
cpu: "12"
command:
- cat
tty: true
- name: mongo
image: mongo
imagePullPolicy: IfNotPresent
resources:
requests:
memory: "128Mi"
cpu: "250m"
limits:
memory: "256Mi"
cpu: "500m"
command:
- cat
tty: true

Jenkins Pipeline

......
stage('Execute regression test on stage env') {
when {expression {params.ENV == 'STAGE'}}
steps {
withCredentials([string(credentialsId: 'MongoDB_URL_SANITIZED_RW', variable: 'MONGODB_URL')]) {
echo 'Execute regression test on stage env...'
sh 'npx playwright test --workers=10'
}
}
}
......

Repro Steps:

In my test project, I have more than 170+ test cases running in fully parallel mode(worker processes: 10). However, when I upgrade the Playwright version from v1.33.0 to v1.35.1, I notice that the test execution will hang at a random test case and lose response unless you kill the process or stop the Jenkins job, this issue is reproducible on both of my laptop and on k8s env.

If downgrade the playwright to v1.33.0, all test cases can be executed successfully to the end.
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

docker module

ANSIBLE VERSION

ansible 2.3.1.0
config file = /Users/xxxxxx/Dropbox/devel/xxxxxx/xxxxxx/ansible.cfg
configured module search path = Default w/o overrides
python version = 2.7.10 (default, Sep 30 2015, 15:50:49) [GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.0.72)]

CONFIGURATION

[defaults]

inventory = ./contrib/inventory.sh
host_key_checking = False
nocows = 1
forks = 500

OS / ENVIRONMENT

Host: macOS

Target: EC2 Ubuntu 16.04

SUMMARY

On an Ubuntu target (running on EC2) with installed docker gathering facts raises a warning about a restricted key ansible_docker_gwbridge being returned in the module data.

AFAICT this supposedly was fixed in #23919.

STEPS TO REPRODUCE

- hosts: all
gather_facts: yes
tasks:
- shell: echo bla

ansible-playbook test.yml

EXPECTED RESULTS

No warning to be shown

ACTUAL RESULTS

PLAY [all] *************************************************

TASK [Gathering Facts] *******************************************************************************
[WARNING]: Removed restricted key from module data: ansible_docker_gwbridge = {...}

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

gather_facts and/or something to do w/ docker

ANSIBLE VERSION

ansible 2.3.0.0
config file = /home/vagrant/factom/factom-ansible/ansible.cfg
configured module search path = Default w/o overrides
python version = 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609]

CONFIGURATION

none

OS / ENVIRONMENT

Ubuntu 16.04.2 LTS (under Vagrant)

SUMMARY

Getting this in the output when doing gather_facts (basically - ansible -m setup localhost)

[WARNING]: Removed restricted key from module data: ansible_docker_gwbridge = REDACTED

STEPS TO REPRODUCE

Setup docker, and make sure that the docker_gwbridge network exists.

Run ansible -m setup localhost

EXPECTED RESULTS

No warning displayed

ACTUAL RESULTS

A warning was displayed

[WARNING]: Removed restricted key from module data: ansible_docker_gwbridge = REDACTED
Issue 1:
Issue Type: Bug Report

Ansible Version: 1.6.8+

ansible 1.6.8

ansible 1.7 (devel d2a1309) last updated 2014/07/22 20:11:41 (GMT -400)

Environment:

OSX 10.9.3

RHEL 6.5

Summary:

As of 1.6.8 and later, the unarchive module fails with the erroneous error "msg: duplicate parameter: src" when the parameters are specified in k=v format

I looked into this a little, and it seems to me that both the original src argument(app.tgz) and the transformed src argument (/Users/matthewbsimon/.ansible/tmp/ansible-tmp-1406078247.21-209950653970379/source) flow into module_utils/basic.py _load_params, and then the newly introduced security fix catches it. I don't know enough to fix this - please help!

Steps To Reproduce:

file: example.yml

hosts: localhost

connection: local

gather_facts: false

tasks:

shell: "touch app.tgz"

unarchive: src=app.tgz dest=/tmp

bash$ ansible-playbook -i 'localhost,' example.yml

Expected Results:

Actual Results:

failed: [localhost] => {"failed": true}

msg: duplicate parameter: src (value=/Users/matthewbsimon/.ansible/tmp/ansible-tmp-1406127477.01-217277799953399/source)

FATAL: all hosts have already failed -- aborting

Issue 2:
vault password could keep prompting until empty password is supplied, vault file could take a list of files

This allows for having multiple vault files with different keys, good for ops team having access to all vaults but qa or dev having access only to specific ones
Issue 1:
A friend of mine (https://github.com/R2-G2) noticed, that there's a strange behavior with radio buttons wrapped into labels:

If you click one for the first time, everything's fine. It gets an active class and if you you use the radio-buttons selector with a ':checked' filter via jQuery, it shows that the element is checked (or better said, it finds the element).

But if you click it for a second time, the active class stays, but the radio button isn't checked anymore.

Here's an example:

http://jsfiddle.net/aMKFq/

The following line in button.js's toggle-method seems to cause the problem:

if ($input.prop('type') === 'radio') $parent.find('.active').removeClass('active')

Better said, it's not the line, but it's position. The line is removing the active class of the parent, if the input is a radio button, which seems logical, since you don't want a radio button to be deselected and you have a toggle class at the end of the method:

this.$element.toggleClass('active')

So, first removing eventually existing active classes and then toggling it, seems useful.

The only problem is, that the checked-property is set before the active class is removed:

if ($parent.length) {
var $input = this.$element.find('input')
.prop('checked', !this.$element.hasClass('active'))
.trigger('change')
if ($input.prop('type') === 'radio') $parent.find('.active').removeClass('active')
}

Possible solution

I wrote a solution, which fixed the issue for me, while still allowing every test to pass:

Button.prototype.toggle = function () {
var $parent = this.$element.closest('[data-toggle="buttons"]')

if ($parent.length) {
var $input = this.$element.find('input')

if ($input.prop('type') === 'radio') $parent.find('.active').removeClass('active')

$input.prop('checked', !this.$element.hasClass('active'))
.trigger('change')

}

this.$element.toggleClass('active')
}

You could of course use it, if you like.

Greets

Issue 2:
The active class stays on the button, but the checked property is removed from the radio input.

http://jsfiddle.net/meleyal/dafPH/
Issue 1:
See discussion on #8384 - Running pycodestyle v2.3.1 currently reports 81 cases of E741 which is one of a set of three style checks to avoid ambiguous single letter names which look like numbers:

E741 do not use variables named ‘l’, ‘O’, or ‘I’

E742 do not define classes named ‘l’, ‘O’, or ‘I’

E743 do not define functions named ‘l’, ‘O’, or ‘I’

See https://pycodestyle.readthedocs.io/en/latest/intro.html#error-codes

The reasoning being in many fonts:

Upper case eye looks like the digit one (I vs 1)

Upper case oh looks like the digit zero (O vs 0)

Upper case el looks like the digit one (L vs 1)

Assuming #8384 or similar is merged, then as part of fixing this whitespace, the style checker settings in tox.ini should be updated to stop ignoring E741.

Issue 2:
Original ticket http://projects.scipy.org/scipy/ticket/811 on 2008-12-10 by @nilswagner01, assigned to @wnbell.

It would be nice to have an implementation of IDR in scipy. See

[http://ta.twi.tudelft.nl/nw/users/gijzen/IDR.html]

for details.
Issue 1:
What do you see as an issue?

The documentation for the template variable data_interval_end states simply that its the "End of the data interval". Initially I took that to mean the final second/microsecond (depending on precision) of the data interval, but its actually the start of the next interval.

For example, given a schedule that runs every 5 minutes, the variables are set as follows (for a simple test I just ran):

data_interval_start: 2022-07-28T16:15:00+00:00

data_interval_end: 2022-07-28T16:20:00+00:00

As opposed to:

data_interval_start: 2022-07-28T16:15:00+00:00

data_interval_end: 2022-07-28T16:19:59+00:00

It makes sense as implemented, but I'd like to see the documentation state the behavior explicitly.

Solving the problem

The documentation I read when using the template variables is https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html

I'm not sure how to word it, but it would be helpful to indicate that data_interval_end is effectively the data_interval_start of the next interval. Or that the interval the DAG is operating on, using mathematical interval notation, is [data_interval_start, data_interval_end)

Anything else

Just an explanation of how we ran into this:

We are running DAGS periodically that pull timeseries data from some API. The jobs query an api with filters like this:

timestamp >= data_interval_start

timestamp <= data_interval_end

We noticed we were getting some duplicated data, specifically data that happened exactly on the data_interval_start value. The simple fix (once we saw the behavior of the variables) was to remove the = from the second filter:

timestamp >= data_interval_start

timestamp < data_interval_end

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Issue 2:
Description

In our use case, we often import data which contains some noise which cannot be handled correctly. However, we don't want an entire task or job to fail because of it (simply because it is not critical). A warning shall be logged to the corresponding data point and the job shall carry on as usual.

The problem: a mere logging.warning() stays in the hiding when nobody looks at the logs (why should they when everything succeeded?). Also, having a separate task/job which checks for those kind of errors is adding too much complexity to the logic and makes it hard to sync to the origin.

The proposal: Add a new task return status Success with warning or simply Warning which shows at high level, what's going on in the tasks. Users can see that there is some action needed, but not immediately, without having to read each of the logs or having to setup additional monitoring levels.

If someone points me toward the relevant parts in the application logic that should be modified, I would be happy to have a shot at it myself.

Use case/motivation

Warnings in tasks should be made visible in the UI at job level (through a status flag).

Related issues

No response

Are you willing to submit a PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct
Issue 1:
TypeScript Version:

1.8.2

Background:

I have been working on trying to get https://github.com/eslint/typescript-eslint-parser, a TypeScript parser plugin for ESLint, off the ground, and the job this weekend has been to begin adding JSX support.

ESLint uses espree and so the aim of the project is to convert the output of the tsc to an AST which espree expects. We already have a solid suite of JSX tests to develop against (taken from the espree project itself), but I have come up against a tsc error in one of them so far.

My issue is that it seems currently the tsc does not accept this "namespaced attribute" JSX syntax:

Code

<a n:foo="bar"> {value} <b><c /></b></a>;

Expected behavior:

Please note the AST produced by espree (see in particular the tokens array): http://astexplorer.net/#/B46lew7I59

Actual behavior:

...compared to the one produced by the tsc (note the issues found in parseDiagnostics):

http://astexplorer.net/#/G5L3CptVNq

Removing the n: from n:foo resolves the parsing issues.

Issue 2:
Hi,

working to a few projects I've noticed some strange behaviors, because I found a few times ts compilation errors in ts for files inside the wwwroot, that by default is excluded.

I workied a bit on it and seems that the root causes were:

if I have a .d.ts that reference a ts file inside the excluded zone, it's evalutated anyway bypassing the exclude, with potential problems. This happened to me using typings: I excluded the typings/main folder, but I continued to receive errors. After this I noticed that in the typings/main.d.ts the files are referenced. excluding the main.d.ts too I solved the problem.

if inside the excluded zone I have another tsconfig.json file with a valid "files" section, the files are evalutated anyway, bypassing the exclude. This happened to me with angular2: to deploy an asp.net 5 app with angular, Currently I copy all the content of the angular 2 npm package from node_modules to wwwroot, but after this compiling I started having compilation problems for duplicate symbols.

I solved the problem, excluding in the copy task all the .ts and tsconfig.json.

Is this by design? At the beginning is a bit confusing, though solve the problem is not hard.
Issue 1:
Complains on e.g. "git.path": null,. Pops up after I edit my user settings.json and save. I'm on Win7, VSCode 0.10.8.

Incorrect type. Expected "String"

\settings.json(154,14)

Issue 2:
Hi,

After updating to version 0.10.8 i have warning in the status bar.

The only extension installed is for golang.
Issue 1:
I like this new feature... I have some suggested improvements. Open to discussion of course :)

Let's take a simple use case. I have a file .babelrc. This file is a JSON file. VS Code detects it as Plain Text. I click in the bottom right to change it to JSON. I see that there are two options "Auto Detect" and "Configure file association for .babelrc".

I try "Auto Detect". The file is still Plain Text. (1) I would expect Auto Detect to intelligently figure out I am using JSON.

I try "Configure file association for .babelrc." I am taken to settings.json. A popup explains that I may need to restart. I don't see any instructions nor do I know where to look. (2) I am not sure how to proceed.

I try setting .babelrc to JSON. This works as expected. I close the file and come back to it. Its back to Plain Text. (3) I would have expected it to stay JSON.

Couple of ideas. For (1) can we intelligently figure out what the file is? We could start with a JSON file or other common configuration files. Also, what is "Auto Detect" supposed to do? It seems like we're already auto detecting every single file. We could consider dropping it.

(2) We should provide some prompt for settings. Even a navigation and highlighting of the settings command that needs to be configured would be helpful. This could be similar to what @alexandrudima did for keybindings. As it stands, I need to know to trigger suggest to know what to type. This isn't obvious, especially for new users.

(3) What if VS Code saved a file's association automatically. For example if I set .babelrc to JSON, I would expect there to be an association and never have to do it again (at least for the workspace I am in).

Just some thoughts.

// @chrisdias

Issue 2:
file association

auto save
Issue 1:
Vue.js version

2.1.4

Reproduction Link

https://jsfiddle.net/aleksey_beskosty/zz5svy6q/

Steps to reproduce

Select element is declared as:

<select :value="val">...</select>

What is Expected?

When val is changed, select element updates its value and shows it.

What is actually happening?

val is changed but select doesn't update value property.

Issue 2:
Take the following

<div>
<select :value='something'></select>
</div>

Currently, vue-template-compiler generates the render function with {attrs:{"value":something}}. However, vue supports the v-bind:value syntax with selects. I would think that instead, it should generate with {domProps:{"value":something}} in a similar manner to inputs.

This means no bindings can take place on the select. This works with a v-model, however this causes vuex to attempt to update the store without going through a mutator.

Looks like it was caused by the fix to #4233 that filters which tag / attribute combos are bound as props.