WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

???

ANSIBLE VERSION

ansible 2.6.0 (skipped_false 39251fc27b) last updated 2018/02/10 00:32:41 (GMT +200)
config file = None
configured module search path = ['/home/nikos/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /home/nikos/Projects/ansible/lib/ansible
executable location = /home/nikos/Projects/ansible/bin/ansible
python version = 3.6.4 (default, Jan 5 2018, 02:35:40) [GCC 7.2.1 20171224]

CONFIGURATION

Default

OS / ENVIRONMENT

Arch linux latest, tasks run against localhost

SUMMARY

It is not possible to define task vars from a dict variable

STEPS TO REPRODUCE

- hosts: localhost
tasks:
- set_fact:
dict: {'key': 'value'}
- debug:
msg: Test
vars: "{{ dict }}"

EXPECTED RESULTS

The second task should be executed successfully and the dict's contents should become available as variables in the context of the task.

ACTUAL RESULTS

ERROR! Vars in a Task must be specified as a dictionary, or a list of dictionaries

The error appears to have been in '/home/nikos/Projects/playbook.yml': line 8, column 9, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

vars:
- dict
^ here

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

lib/ansible/playbook/base.py

ANSIBLE VERSION

ansible 2.2.0.0
config file =
configured module search path = Default w/o overrides

CONFIGURATION

OS / ENVIRONMENT

N/A

SUMMARY

I am trying to set the vars for either a block: or an include_role: from a dictionary.

I get one of these messages (depending on the case):

ERROR! Vars in a Block must be specified as a dictionary, or a list of dictionaries

ERROR! Vars in a IncludeRole must be specified as a dictionary, or a list of dictionaries

STEPS TO REPRODUCE

- set_fact:
_T_m3_inv_vars:
one_setting: "{{ some_other_var1 |mandatory }}"
two_setting: "{{ some_other_var2 |mandatory }}"

- block:
- debug: msg="YYYYYYYY"
vars: "{{ _T_m3_inv_vars }}"

- include_role:
name: "some_nice_role"
static: yes
private: yes
vars: "{{ _T_m3_inv_vars }}"

EXPECTED RESULTS

I would expect a similar result as having done the following

- block:
- debug: msg="YYYYYYYY"
vars:
one_setting: "{{ some_other_var1 |mandatory }}"
two_setting: "{{ some_other_var2 |mandatory }}"

- include_role:
name: "some_nice_role"
static: yes
private: yes
vars:
one_setting: "{{ some_other_var1 |mandatory }}"
two_setting: "{{ some_other_var2 |mandatory }}"

This is because I am indeed passing a dictionary to the vars: setting.

ACTUAL RESULTS

One of these messages (obtained by running the previous snippets separatellyI

ERROR! Vars in a Block must be specified as a dictionary, or a list of dictionaries

ERROR! Vars in a IncludeRole must be specified as a dictionary, or a list of dictionaries
Issue 1:
Description of the problem

I don't know if it is expected or if I miss something, but it looks like the envmap textures generated by PMREGenerator and the renderer specified at that time cannot be re-used with another renderer.

In this example, the envmap is generated using renderer.

If the scene is rendered with renderer2, it doesn't work.

jsfiddle

Replace var pmremGenerator = new THREE.PMREMGenerator( renderer );

by var pmremGenerator = new THREE.PMREMGenerator( renderer2 );

on line 49 to check the difference.

Three.js version

Dev

r115

Browser

All of them

OS

All of them

Issue 2:
Description of the problem

Using PMREMGenerator.fromEquirectangular in multiple simultaneous three.js renderers causes only the last renderer to have a correctly functioning texture (at least for use as an envMap)

This happens even when each renderer has its own instance of pmremGenerator and calls dispose after use.

Here's a fiddle: https://jsfiddle.net/h37k2ztv/10/

I would expect that initializing a different pmremGenerator for each renderer should be sufficient, but I had to work around it by reinstantiating and recompiling the pmremGenerator immediately before each time it is used (uncomment lines 63 and 64 in the fiddle to do this)

Issue #18842 reports this same issue, but perhaps even without multiple renderers.

This merge request may have introduced the unexpected behavior.

Three.js version

Dev

r115

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS
Issue 1:
[ yes ] I've searched for any related issues and avoided creating a duplicate

issue.

Description

Announcement, it's not a bug probably。

Firstly ,I run the standard wss ( ws over https server ) code by a single js file, It worked.

and then , I copy the same code into the electron main.js, it can't be worked.

so ,i open wireshark to capture the package , and then I found the electron svr send a little bytes other then never see any piece about how to handle the upgrade handshake. :(

ps: i use the self-singed certification

Reproducible in:

version: ws ^7.1.2

Node.js version(s): v10.16.1

OS version(s): osx 10.14

Steps to reproduce:

1.server code :

const fs = require('fs');

const https = require('https');

const WebSocket = require('ws');

const path = require('path');

const hostname = 'aaa.abc.com';

const server = https.createServer({

cert: fs.readFileSync(path.resolve(certs/${hostname}.crt)),

key: fs.readFileSync(path.resolve(certs/${hostname}.key)),

// rejectUnauthorized: false

});

const wss = new WebSocket.Server({ server });

wss.on('connection', function connection(ws) {

ws.on('message', function incoming(message) {

console.log('received: %s', message);

});

ws.send('something');

});

server.listen(443,()=>{

console.log('start svr002')

});

client code

ws=new WebSocket('wss://aaa.abc.com/echo',{

rejectUnauthorized: false

});

ws.on('error',function (e) {

connectFlag=false;

console.error('error',e);

ws=null;

});

ws.on('close',function (e) {

connectFlag=false;

console.warn('close',e)

});

ws.on('open', function open() {

connectFlag=true;

console.log('connected');

ws.send('something');

ws.on('message', function incoming(data) {

console.log(data);

});

});

run in single.js : yes

node svr.js

node cli001.js or open in ie,ff,chrome

run embed in electron : not work

electrion .

node cli001.js or open in ie,ff,chrome

Issue 2:
https://i.imgur.com/mYtRTmJ.png

https://electronjs.org/docs/api/browser-window
Issue 1:
At the moment, index signature parameter type must be string or number.

Now that Typescript supports String literal types, it would be great if it could be used for index signature parameter type as well.

For example:

type MyString = "a" | "b" | "c";

var MyMap:{[id:MyString] : number} = {};
MyMap["a"] = 1; // valid
MyMap["asd"] = 2; //invalid

It would be also useful if it could also work with Enums. For example:

enum MyEnum {
a = <any>"a",
b = <any>"b",
c = <any>"c",
d = <any>"d",
}

var MyMap:{[id:MyEnum] : number} = {};
MyMap[MyEnum.a] = 1; // valid
MyMap["asd"] = 2; //invalid

var MyMap:{[id:MyEnum] : number} = {
[MyEnum.a]:1, // valid
"asdas":2, //invalid
}

Issue 2:
Typescript requires that enums have number value types (hopefully soon, this will also include string value types).

Attempting to use an enum as a key type for a hash results in this error: "Index signature parameter type much be 'string' or 'number' ".-- An enum is actually a number type.-- This shouldn't be an error.

Enums are a convenient way of defining the domain of number and string value types, in cases such as

export interface UserInterfaceColors {
[index: UserInterfaceElement]: ColorInfo;
}
export interface ColorInfo {
r: number;
g: number;
b: number;
a: number;
}
export enum UserInterfaceElement {
ActiveTitleBar = 0,
InactiveTitleBar = 1,
}
Issue 1:
So far I really like Atom 1.0 - it's got a long way to go, but it will get there. We needed an editor like this.

Anyway: the only thing bothering me was how quickly it installed itself (Windows 8.1, 64 bit). Even though that might sound like a _good_¨thing, it isn't. When I double-click the installer I get no options, no information whatsoever. Only a screen "Atom is installing and will launch when ready." For some people this might be the best approach, but for a whole lot of others it isn't.

Some options would be great. I am thinking: file association, installation directory, packages to include with installation (I for one don't need all packages that are included on default install) and so on. I could understand that file association and package control aren't included (though I'd really like that) but why not the ability to choose your own installation directory?

Issue 2:
So far I really like Atom 1.0 - it's got a long way to go, but it will get there. We needed an editor like this.

Anyway: the only thing bothering me was how quickly it installed itself (Windows 8.1, 64 bit). Even though that might sound like a _good_¨thing, it isn't. When I double-click the installer I get no options, no information whatsoever. Only a screen "Atom is installing and will launch when ready." For some people this might be the best approach, but for a whole lot of others it isn't.

Some options would be great. I am thinking: file association, installation directory, packages to include with installation (I for one don't need all packages that are included on default install) and so on. I could understand that file association and package control aren't included (though I'd really like that) but why not the ability to choose your own installation directory?
Issue 1:
Issue originally made by @xfix

Bug information

Babel version: 6.2.1

Node version: 5.1.0

npm version: 3.5.0

Options

--presets es2015

Input code

let results = []

for (let i = 0; i < 3; i++) {
switch ('x') {
case 'x':
const x = i
results.push(() => x)
}
}

for (const result of results) {
console.log(result())
}

Description

When I declare a block scoped variable in a switch block, it's not recognized as a block scoped variable for purpose of functions, even when it's declared inside a for loop. This example prints 2, 2, 2, when it should print 0, 1, 2.

(I outright apologize if this is a duplicate, finding duplicates with that bug tracker is annoying)

Issue 2:
Bug Report

Current Behavior

I am getting following error. Can't figure out solution. I found many post which looks duplicate here but, nothing work.

node_modules@babel\helper-plugin-utils\lib\index.js

throw Object.assign(err, {

Error: Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel.

Babel Configuration (.babelrc, package.json, cli command)

"dependencies": {
"express": "^4.16.4",
"isomorphic-fetch": "^2.2.1",
"react": "^16.6.3",
"react-dom": "^16.6.3",
"react-redux": "^5.1.1",
"react-router": "^4.3.1",
"react-router-config": "^1.0.0-beta.4",
"react-router-dom": "^4.3.1",
"redux": "^4.0.1",
"redux-thunk": "^2.3.0"
},
"devDependencies": {
"@babel/cli": "^7.2.3",
"@babel/core": "^7.2.2",
"@babel/plugin-proposal-class-properties": "^7.2.0",
"@babel/plugin-transform-runtime": "^7.2.0",
"@babel/preset-env": "^7.3.1",
"@babel/preset-react": "^7.0.0",
"babel-core": "^7.0.0-bridge.0",
"babel-jest": "^24.0.0",
"babel-loader": "^7.1.5",
"css-loader": "^1.0.1",
"cypress": "^3.1.3",
"enzyme": "^3.8.0",
"enzyme-adapter-react-16": "^1.7.1",
"enzyme-to-json": "^3.3.5",
"extract-text-webpack-plugin": "^4.0.0-beta.0",
"html-webpack-plugin": "^3.2.0",
"jest": "^24.0.0",
"jest-fetch-mock": "^2.0.1",
"json-loader": "^0.5.7",
"nodemon": "^1.18.9",
"npm-run-all": "^4.1.5",
"open": "0.0.5",
"redux-devtools": "^3.4.2",
"redux-mock-store": "^1.5.3",
"regenerator-runtime": "^0.13.1",
"style-loader": "^0.23.1",
"uglifyjs-webpack-plugin": "^2.0.1",
"webpack": "^4.26.1",
"webpack-cli": "^3.1.2",
"webpack-dev-server": "^3.1.14",
"webpack-node-externals": "^1.7.2"
},
"babel": {
"presets": [
"@babel/preset-env",
"@babel/preset-react"
],
"plugins": [
"@babel/plugin-transform-runtime",
"@babel/plugin-proposal-class-properties"
]
}

Environment

Babel version(s): [> v7]

Node/npm version: [Node 8.12.0/npm 6.4.1]

OS: [Windows 10]

Stackoverflow
Issue 1:
Vue.js version

2.0.0-rc.4

Reproduction Link

https://jsbin.com/rifuxuxuxa/1/edit?js,console,output

Steps to reproduce

After hitting 'Run with JS', click the 'click here' button

Wait till this.show is true(8 seconds), click the 'click here' button again

What is Expected?

In step 1, prints '2333'

In step 2, prints '2333'

What is actually happening?

In step 1, prints '2333'

In step 2, an error occurs 'o.fn is not a function'

This can only be reproduced when there is a v-show element around. I have tried to put the v-show element (in this case, the 'balabalabala' span) before the slot, after the slot, outside the div, and they all report the same error after this.show is set to true.

This may have something to do with this.

Issue 2:
I reported the same issue for v-if which got fixed in vue@2.0.0-rc.4. However, with this version the same code using v-show – which previously worked perfectly – does not work anymore.

Vue.js version

2.0.0-rc.4

Reproduction Link

http://codepen.io/analog-nico/pen/KgPKRq

Steps to reproduce

Click the link "Open popup using v-show"

A badly designed popup opens

Click the "Close" link

What is Expected?

The popup closes successfully

What is actually happening?

Vue fails to call an internal function and throws: TypeError: o.fn is not a function. (In 'o.fn(ev)', 'o.fn' is an instance of Object)

The closePopupUsingVShow function attached to the "Close" link's click event never gets called.

The popup does not close.

For reference the codepen contains the exact same implementation of the popup with the only difference that it uses v-if instead of v-show to show/hide the popup. v-if works perfectly.
Issue 1:
Description

I'd like to propose a few steps to improve the validation constraints:

Deprecate empty strings ("") currently happily passing in string constraints (e.g. Email)

https://docs.jboss.org/hibernate/stable/beanvalidation/api/javax/validation/constraints/Email.html

Deprecate non string values in NotBlank / Blank and 'whitespaced' strings passing (" ")

https://docs.jboss.org/hibernate/stable/beanvalidation/api/javax/validation/constraints/NotBlank.html

allow for null (#27876)

Consider NotEmpty / Empty as the current NotBlank / Blank constraints

https://docs.jboss.org/hibernate/stable/beanvalidation/api/javax/validation/constraints/NotEmpty.html

I dont think we should add these (but favor specific constraints) as empty in PHP is different as described above (ints, bools, etc). Not sure we should follow either one :) thus possible confusion

If this happens we'd do simply

@Email

@NotNull @Email

@NotNull @Length(min=3) @NotBlank

@NotNull @NotBlank

@Type(array) @Count(3)

Thoughts?

Issue 2:
Description

In most validators, there's a failsafe mecanism that prevent the validator from validating if it's a null value, as there's a validator for that (NotNull). I think NotBlank shouldn't bother on null values, especially as NotBlank and NotNull are used together to prevent null values too.

Not really a feature request, but not really a bug too... more like a RFC but for all versions. But I guess this would be a BC break though. :/ So maybe add a deprecated on the validator if it's a null value or something, and remove the null invalidation from the NotBlank on 5.0 ?

Currently, we need to reimplement the validator just to skip null values...

Possible Solution

Either deprecate the validation on null value in NotBlank, or do as in most validators, (if null value, then skip). But as I mentionned, this would probably be a bc break.
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1880 on 2011-06-26 by @nilswagner01, assigned to unknown.

======================================================================
FAIL: test_timedelta_scalar_construction (test_datetime.TestDateTime)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/nwagner/local/lib64/python2.6/site-packages/numpy/core/tests/test_datetime.py", line 189, in test_timedelta_scalar_construction
assert_equal(str(np.timedelta64(3, 's')), '3 seconds')
File "/home/nwagner/local/lib64/python2.6/site-packages/numpy/testing/utils.py", line 313, in assert_equal
raise AssertionError(msg)
AssertionError:
Items are not equal:
ACTUAL: '%lld seconds'
DESIRED: '3 seconds'

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1887 on 2011-06-29 by @dhomeier, assigned to unknown.

With Python versions 2.4-2.6, the output of np.timedelta only produces the format string since (probably) merging the datetime branch, like this:

>>> np.__version__
'2.0.0.dev-f7c16d7'
>>> np.timedelta64(3)
numpy.timedelta64(%lld,'generic')
>>> str(np.timedelta64(3, 's'))
'%lld seconds'

or in the most recent version

>>> np.__version__
'2.0.0.dev-192ac74'
>>> np.timedelta64(3)
numpy.timedelta64(%lld)

making the corresponding tests fail, whereas with 2.7 and 3.2 the intended output is produced:

>>> np.timedelta64(3)
numpy.timedelta64(3)
>>> str(np.timedelta64(3, 's'))
'3 seconds'

(Tested on MacOS X 10.5/ppc and 10.6/x86_64)
Issue 1:
Auto generated links are broken -- all google links points to Not Found page.

Example link from google:

https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.ttest_rel.html

working link:

https://docs.scipy.org/doc/scipy/reference/reference/generated/scipy.stats.ttest_rel.html

doubled part '/reference'

Issue 2:
The new theme seems to have introduced a duplicate reference in the URL, e.g.,

Before: https://docs.scipy.org/doc/scipy/reference/linalg.interpolative.html

After: https://docs.scipy.org/doc/scipy/reference/reference/linalg.interpolative.html

The effect was that today all SciPy search engine results I found were broken.

The search engines will update eventually. But the double /reference/reference/ in the url is unnecessary, so it might be better removed?
Issue 1:
VSCode Version: 1.0.0

OS Version: Ubuntu 16.04

Steps to Reproduce:

Ctrl+Shift+Alt+Down - default ubuntu hotkeys to move window to other desktop

I set Ctrl+Shift+D for me right now, but it will be nice to have OS dependency of hotkeys out of the box

Issue 2:
Create a new extension with yo code (just a TypeScript basic extension.

Publish to the gallery

Install on VS Code

Update the extension version and republish to the gallery

Extensions: Show Outdated Extensions

You see that a new version of the extension is available. Click Update extension.

The dropdown stays open with the Update extension button swirling. It never stops.

If you change focus, the dropdown goes away but no Restart message comes up.

If you look under .vscode/extensions, the extension folder is still there containing just the node-modules folder and the .vsixmanifest files.
Issue 1:
Is it possible to install TF in windows environment?

I checked "pip install" is not supported in windows.

Any plan for it?

Issue 2:
I was excited to see tensorflow, but as many other users, we are on Windows, would be nice to see this support happen. Will you accept Windows port contributions?

In the meantime, Microsoft recently released their Deep Learning toolkit which scales on multiple machines with GPUs for both Linux and Windows. https://github.com/Microsoft/CNTK
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.4.1

Operating System version: win7

Java version: 1.8

Java Code：

package com.ghy.www;

import com.ghy.www.dubbo.provider.service.ISayHello;

import com.ghy.www.dubbo.provider.service.SayHello;

import org.apache.dubbo.config.ApplicationConfig;

import org.apache.dubbo.config.RegistryConfig;

import org.apache.dubbo.config.ServiceConfig;

import java.io.IOException;

public class Application1 {

public static void main(String[] args) throws IOException {

SayHello helloService = new SayHello();

// 服务配置

ServiceConfig serviceConfig = new ServiceConfig();

// 设置应用名称

serviceConfig.setApplication(new ApplicationConfig("dubbo2-server"));

// 设置注册中心

serviceConfig.setRegistry(new RegistryConfig("multicast://224.5.6.7:1234?unicast=false"));

// 设置业务接口

serviceConfig.setInterface(ISayHello.class);

// 设置业务实现类

serviceConfig.setRef(helloService);

// 发布服务

serviceConfig.export();

// 进程不销毁

System.in.read();

}

}

run after show WARN：

main WARN multicast.MulticastRegistry: [DUBBO] Ignore empty notify urls for subscribe url provider://192.168.61.250:20880/com.ghy.www.dubbo.provider.service.ISayHello?anyhost=true&application=dubbo2-server&bind.ip=192.168.61.250&bind.port=20880&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&interface=com.ghy.www.dubbo.provider.service.ISayHello&methods=sayHello&pid=9900&release=2.7.4.1&side=provider&timestamp=1572321725880, dubbo version: 2.7.4.1, current host: 192.168.61.250

why ?

thank very much!

Issue 2:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.0

Operating System version: mac

Java version: 1.8

Steps to reproduce this issue

AbstractClient#initConnectStatusCheckCommand set break point at !isConnected().

AbstractClient#close() set break point here.

start client first, start provider and then shutdown provider gracefully , let method AbstractClient.close() be executed. Then select step 1 and trigger the thread to execute !isConnected, here will always try to connect the offline machine.

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

When the server goes offline, the client will not reconnect the offline machine.

Actual Result

What actually happens?

The client reconnects the offline machine every 2 seconds and causes a large number of arp packets(because ip is recycled and not available now).
Issue 1:
Compare these 1.15 docs with these 1.13 docs

Issue 2:
I'm having difficulties displaying the NumPy reference in HTML format. There seems to be some formatting shining through which isn't correctly translated to HTML, or the rendering engine can't display the content properly.

The problem shows, for example, when looking at the ndarray reference, subsection "Internal memory layout of an ndarray". Here I get garbled formulae like this:

n_{\mathrm{offset}} = \sum_{k=0}^{N-1} s_k n_k

The problem occurs both with firefox and chromium on kubuntu 18.04, the docu is version 1.15.