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

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Barely. See below.

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10, Version 10.0.17134.285.

TensorFlow installed from (source or binary): Binary.

TensorFlow version (use command below): b'v1.11.0-rc2-4-gc19e29306c' 1.11.0.

Python version: Python 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 03:37:03) [MSC v.1900 64 bit (AMD64)] on win32.

CUDA/cuDNN version: CUDA V9.0.176, cuDNN v7.3.1.

GPU model and memory: Nvidia GTX 970 4 GB.

Reproduction

import tensorflow as tf
print(tf.test.is_gpu_available())

Expected behaviour

Test prints True.

Actual behaviour

The test script prints the following text and then hangs indefinitely, using 100% of one CPU core:

>>> tf.test.is_gpu_available()

2018-10-03 23:08:26.805592: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2

2018-10-03 23:08:27.171992: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1411] Found device 0 with properties:

name: GeForce GTX 970 major: 5 minor: 2 memoryClockRate(GHz): 1.253

pciBusID: 0000:01:00.0

totalMemory: 4.00GiB freeMemory: 3.31GiB

2018-10-03 23:08:27.184134: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1490] Adding visible gpu devices: 0

Issue 2:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A

TensorFlow installed from (source or binary): 1.10.0-devel-gpu-py3

TensorFlow version (use command below): 1.10.0-devel-gpu-py3

Python version: 3.5.2

Bazel version (if compiling from source): N/A

GCC/Compiler version (if compiling from source): N/A

CUDA/cuDNN version: CUDA: V9.0.176 cuDNN: V7.1.4

GPU model and memory: 2x 1080ti 11GB

Exact command to reproduce:

import tensorflow as tf

data_format = 'channels_first' if tf.test.is_gpu_available(True) \
else 'channels_last'
# At this point, all memory is allocated across all GPUs
config = tf.ConfigProto()
config.gpu_options.allow_growth = True
sess = tf.Session(config=config)
# All VRAM still allocated

Describe the problem

Using tf.test.is_gpu_available(True) to check if a system GPU is available allocates all the VRAM available.
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/2081 on 2012-03-14 by trac user taldcroft, assigned to unknown.

Using numpy devel with Python 3.2 gives an unexpected result trying to initialize an array from numpy string objects. This is a regression from previous behavior (devel prior to about two weeks ago and 1.6.1).

devel:

>>> d = np.array(['a'])
>>> np.asarray([d[0]])
array([''],
dtype='<U0')

In numpy 1.6.1:

>>> d = np.array(['a'])
>>> np.asarray([d[0]])
array(['a'],
dtype='<U1')

If one uses a longer string like "abcd" instead of "a" then the result is "ab", so it looks like the actual output length is // 2 from the desired length. Perhaps this is related to:

91f87e1

Issue 2:
Consider the following code:

from __future__ import print_function

import numpy as np

a = np.ones((3, 3, 3))
b = np.zeros((3, 3))

# Uncommenting this will make the below call to `np.r_` work.
# try:
#	np.r_['2,3', a, b]
# except ValueError:
#	print('failure')

print(np.r_[a, b.reshape((3, 3, 1))])

This fails with:

Traceback (most recent call last):
File "test.py", line 13, in <module>
print(numpy.r_[a, b.reshape((3, 3, 1))])
File "/usr/local/lib/python2.7/dist-packages/numpy/lib/index_tricks.py", line 338, in __getitem__
res = _nx.concatenate(tuple(objs), axis=self.axis)
ValueError: all the input array dimensions except for the concatenation axis must match exactly

All right as the dimensions don't match indeed. However uncommenting the above try/except block will make the second call to numpy.r_ work, just as it was numpy.r_['2,3', a, b.reshape((3, 3, 1))] instead (stacking along the last axis). So it seems that numpy.r_ still has that string from the previous failing call cached and is using it for the second call.

failure
[[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]

[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]

[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]]

Tested on:

Python 2.7.12 + numpy==1.12.0

Python 3.5.2 + numpy==1.12.0
Issue 1:
Issue Details

Electron Version:

7.0.0

Operating System:

Windows 10 (1803)

Last Known Working Electron version:

6.0.x

Actual Behavior

To Reproduce

I tried two ways to intall vue-devtools, but they didn't work:

Added vue-devtools manually by using chrome extension files.

Applied this lib -> https://github.com/zce/vue-devtools.

Issue 2:
Electron version: v1.7.11

Operating system: Mac OS X v10.13.3

Expected behavior

Although issue #7367 is closed, the given solution does not address when there are multiple BLE devices.

Under Google Chrome, when calling the BLE navigator.bluetooth.requestDevice(options) API, Chrome displays a special dialog (attached to the address bar) with showing all the BLE devices that meet the filters in options. You are given the option to select one of the BLE devices. When the working example with Web Bluetooth API, no special dialog is display, even when clicking the "All Devices" checkbox.

In my house I have two Apple TV devices. Running the samples from here, they show up.

Actual behavior

No special dialog allowing the selection of found BLE devices appears.

How to reproduce

Run the sample electron app from here. If there are multiple BLE devices, it is not possible to select one.
Issue 1:
Hi,

I have tried to understand the code behind the DataLoader, I think I got the global meaning.

Problem

I have noticed that while increasing the number of workers, the number of memory used increases linearly. I recall that someone told that each worker has its own replica of the dataset. I guess this is happening because when lauching a Process, the parent environment is copied for the newly created Process. It might happen differently, If I am wrong please explain me. :)

Context

My main concern here is to have only one instance of my dataset in memory. For example my reference dataset is composed with a 8 GB file, scaling with 10 workers, you can imagine how fast memory burns. This situation has no sense because the dataset is static.

I may have misinterpreted something along the way, I might not be the first one to deal with this problem.

Expected workaround

I already built a custom dataset and cannot break this 8 GB file into more pieces, but just using a reference to the object rather than copy would save my day.

Thanks

Issue 2:
When I tried to use multi-gpu trainning.

If I wrap the model forward function as follows:

def __init__(...):
self.operation_function = self._gaussian

def forward(self, x, z):
output = self.operation_function(x, z)

def _gaussian(self, x, z):
Real forward codes
...

Then

gpu_num = torch.cuda.device_count()
print('GPU NUM: {:2d}'.format(gpu_num))
if gpu_num > 1:
model = torch.nn.DataParallel(model, list(range(gpu_num))).cuda()

I get one error during the multi-gpu trainning

File "/usr/local/lib/python2.7/dist-packages/torch/nn/modules/module.py", line 468, in __call__
result = self.forward(*input, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/torch/nn/parallel/data_parallel.py", line 123, in forward
outputs = self.parallel_apply(replicas, inputs, kwargs)
File "/usr/local/lib/python2.7/dist-packages/torch/nn/parallel/data_parallel.py", line 133, in parallel_apply
return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
File "/usr/local/lib/python2.7/dist-packages/torch/nn/parallel/parallel_apply.py", line 77, in parallel_apply
raise output
RuntimeError: Expected tensor for argument #1 'input' to have the same device as tensor for argument #2 'weight'; but device 1 does not equal 0 (while checking arguments for cudnn_convolution)

If I directly put all codes of _gaussian function under forward function. The multi-gpu trainning works

def forward(self, x, z):
Real forward codes
...

@soumith Do you have any comments about this?
Issue 1:
PUT /test_boolean
{ "mappings": {
"shops": {
"properties": {
"shop_type": {
"type": "object",
"dynamic": "strict",
"properties": {
"dealer": {"type": "boolean"},
"seller": {"type": "boolean"}
}
}
}
}
}
}

# THIS DOC SHOULD GET INDEXED
PUT test_boolean/shops/1
{
"shop_type": [
{ "dealer": true,
"seller": false
}
]
}

#THIS DOC SHOULDNOT GET INDEXED. MAPPER EXCEPTION EXPECTED
PUT test_boolean/shops/2
{
"shop_type": [
{ "dealer": true,
"seller": "No this not a seller"
}
]
}

Tried on latest: 1.7.1

According to my usecase the second document should fail by Mapper Exception telling cannot match string "No this not a seller" to boolean type.

I read though this https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-core-types.html#boolean

The doc says any string is finally treated as True. But i can see the final persisted doc contains the string as well.

GET test_boolean/shops/2

{
"_index": "test_boolean",
"_type": "shops",
"_id": "2",
"_version": 1,
"found": true,
"_source": {
"shop_type": [
{
"dealer": true,
"seller": "No this not a seller"
}
]
}
}

Is this a bug or a feature. If a feature, how can i circumvent this problem to enforce my usecase.

Issue 2:
Spinoff from #11437.

Today, most boolean settings in Elasticsearch are parsed leniently

using Booleans.parseBoolean, which interprets 0, no, off and false

as false, else true for any random strings like NO or OFF or foobar, etc.

I think this is dangerous: if the user has a typo for false, or maybe

thinks "disabled" would also mean false, they silently get true.

I think we should parse boolean settings strictly, maybe using this

awesome project: https://github.com/rmuir/booleanparser so that the

user gets a clear exception stating that the value is not recognized.

Unfortunately this is a biggish project ... I think we'd need to take

a similar approach to #11437, where for back compat if we see

un-parseable boolean settings from persisted places (cluster, index

settings), we dynamically map them to true and log a warning.
Issue 1:
npm install @types/react-router-dom

npm ERR! Unexpected end of JSON input while parsing near '...ue9VlHwQSChuoAqmIDkEG'

npm ERR! A complete log of this run can be found in:
npm ERR! \npm-cache\_logs\2019-06-11T07_28_08_137Z-debug.log

Issue 2:
While installing @types/react-router-dom getting this error

npm ERR! Unexpected end of JSON input while parsing near '...ue9VlHwQSChuoAqmIDkEG'
Issue 1:
Because of the way Next.js does initial render of the pages, and that the initial render on client-side and server-side has to be the same (see https://reactjs.org/docs/react-dom.html#hydrate ), sometimes when a page is rendered, its' query (returned i.e. by useRouter() hook) will be empty, even though it actually has query params. After the initial render, soon after there will be another render in which the query will be then populated with proper query params. ( Example described also in i.e. #7880 )

My code relies on those query params very heavily and we need to know "are those the real current query params or not yet?". (i.e. because if query params are missing or incorrect, we'd like to redirect the user to another page)

Describe the solution you'd like

I think that either:

query should be always populated with the current query params (even on initial client-side hydration that happens after a server-side render)

or, (IMO better), add a ready: boolean flag to Router, so the component can listen to this using i.e. useEffect and ignore the query params when they aren't parsed yet.

Describe alternatives you've considered

I think we'll have to go with some setTimeout or sth for now until a better solution is found.

Issue 2:
I have the following page:

import { AppInterface } from './_app'
import { withRouter } from 'next/router'

class Page extends React.Component {

static contextType = AppInterface

render() {
console.log( 'Router', this.props.router );
return(
<p>Booh!</p>
)
}

}

export default withRouter( Page )

The console tells me that Router is undefined and shows this warning:

withRouter(Page) declares both contextTypes and contextType static properties. The legacy contextTypes property will be ignored.

As soon as I comment out static contextType = AppInterface, the error disappears and the router gets logged just right...
Issue 1:
Would be great if CTRL+Space (or whatever your hotkey is for show suggestions) would show all the literal string options available for string literals.

In my case I have an <Icon> React component which takes an icon key as one of its props, and I want to limit the options that can be chosen. The string literals work great. Unfortunately because of the number of icons it's somewhat difficult to know what your options are and the intellisense is next to useless in this case because you get basically the first 3 or 4 options in the description, but nothing more. Being able to invoke suggestions and get the list would be a huge help.

Issue 2:
Many JavaScript frameworks are heavily based on using string values to do many things, from getting and setting attributes via the property name in string form, to defining event handlers to handle browsing to particular URLs. TypeScript added specialized signatures in overloads as one means to help mitigate the pain associated with these types of APIs. Unfortunately for a number of patterns this is insufficient and not general enough. Rather than try to design a specific type system enhancement that could handle some or all of the many ways these frameworks use string literals we could try some simple tricks in Visual Studio to help out. Namely, when typing a string literal the editor should provide a completion list based on other string literals already used in your program. Some other tools already provide similar capabilities (ex Sublime Text).

Consider something like this in a Backbone View class:

class TodoView extends Backbone.View<TodoModel> {
initialize() {
this.listenTo(this.model, 'change', () => this.render());
this.listenTo(this.model, 'todoDescriptionChanged', () => this.render());
this.listenTo(this.model, 'destory', () => this.remove());
}

At another point I may attempt to manually trigger one of these events:

updateTodo() {
var desc = this.$input.val().trim();
var todo = this.model;
if (desc) {
todo.save({ title: desc });
// provide completion list inside this string literal showing
// todoDescriptionChanged to avoid hard to debug typos
// and speed up development
todo.trigger('todoDescriptionChanged');
}
}

This should be a relatively cheap solution to a common set of problems that we've always hoped TypeScript can improve on over JavaScript. If you did accidentally make a typo in one use of the literal this could also help you discover that when seeing 2 completion list items that are similar but slightly different.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-create-bootstrap-wells.

The first checkmark says:

Add two div elements inside your div class="well"> element both with the class col-xs-6

...but that's not what needs to be done to accomplish the task, so it's a little confusing.

It should be more like this:

Under each of your two divs with class col-xs-6, add one div element with class "well.

And also, the 2nd checkmark is probably useless:

Nest both of your div class="col-xs-6" elements within your div class="row" element.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-create-bootstrap-wells has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
Issue 1:
For master code, git rev-parse HEAD

ec7929b

same code running for 0.12.1

batch_size:[256] batches/s:[4.76] insts/s:[1217.74]

batch_size:[256] batches/s:[5.39] insts/s:[1379.17]

batch_size:[256] batches/s:[5.11] insts/s:[1306.94]

batch_size:[256] batches/s:[5.05] insts/s:[1292.61]

for master code:

batch_size:[256] batches/s:[4.18] insts/s:[1069.37]

batch_size:[256] batches/s:[4.77] insts/s:[1220.00]

batch_size:[256] batches/s:[4.81] insts/s:[1231.52]

batch_size:[256] batches/s:[4.55] insts/s:[1164.99]

Issue 2:
See here, I wonder why no one answer my question ???
Issue 1:
Nobody should have to write cx.fcx.lcx.ccx.tcx. Everyone winces when they see it. Fix this. Put the contexts in objects that pick such things up from their parents. No functional changes, just a whole lot of shoving stuff around.

Issue 2:
When marking public functions with #[no_mangle] and then linking to the crate with the functions using -C lto, the functions will be exported in the output.

This can result in errors about duplicate definitions (when linking things linked with -C lto together) and also prevents the removal of unused functions.
Issue 1:
running lessc bootstrap.less under /less gave me following error:

at less.Parser.parser.parse.i (/Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/js/lib/less/parser.js:385:31): #grid > .core is undefined (Less::ParseError)
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/parser.rb:61:in `block in to_css'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:90:in `block in do_lock'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:88:in `call'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:88:in `Locker'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:88:in `do_lock'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:60:in `lock'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script/v8_context.rb:30:in `exec'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/java_script.rb:26:in `exec'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/lib/less/parser.rb:61:in `to_css'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/gems/less-2.2.2/bin/lessc:99:in `'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/bin/lessc:19:in `load'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/bin/lessc:19:in `'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/bin/ruby_noexec_wrapper:14:in `eval'
from /Users/ftiasch/.rvm/gems/ruby-1.9.3-p374/bin/ruby_noexec_wrapper:14:in `'

lessc -v
lessc 1.3.0 (LESS Compiler) [Ruby] 2.2.2

Issue 2:
Issue 1:
Hi, Three.js team.

I am a fan of Three.js. I had done several successful Three.js projects.

So, first of all, I would love to say, "Thank you for your dedicated library".

Description of the problem

I know that now I am commenting duplicated issue related to VTK loader.

The issue was commented in Feb, 2018. But since I VTK loading is important certainly, I decided to comment again.

So, I have one VTK file generated from one external device. It has UNSTRUCTURED_GRID dataset which is not allowed yet by VTK loader. Of course, I tried to use alternative model extensions such as .fbx, .ply, etc.

But unfortunately, my partners says it's a pain for them to convert current VTK to different extensions.

Anyway, they provided me .ply. Its external shape looks good. But the internal shape is just empty one.

This is VTK internal view:

And this is PLY internal view:

As you can see, their internal views are different.

At the moment, I'd like to ask 2 questions:

VTK loader will never work with the rest 4 vtk datasets including "UNSTRUCTURED_GRID"?

If so, how can we generate alternative model extension having same geometry as VTK?

Three npm version

0.120.1 latest

I'd love to believe you know the solution.

Thank you!

Issue 2:
I would like to ask for advice because of I have one use case where I need to load VTK file which is a BINARY DATASET STRUCTURED POINTS, which represents a segmented image.

# vtk DataFile Version 3.0
VTK File Generated by Insight Segmentation and Registration Toolkit (ITK)
BINARY
DATASET STRUCTURED_POINTS
DIMENSIONS 1040 1040 1
SPACING 2.6455026988983699e-01 2.6455026988983699e-01 1.0000000000000000e+00
ORIGIN 0.0000000000000000e+00 0.0000000000000000e+00 0.0000000000000000e+00
POINT_DATA 1081600
SCALARS scalars unsigned_short 1
LOOKUP_TABLE default

Binary data

Thank you for your help.
Issue 1:
Rick Evans opened SPR-1911 and commented

This I kinda like the related issue of documenting the beans tags, but applies to AOP only.

It includes documenting the tags, showing how to use them examples etc.

Affects: 2.0 M3

Issue 2:
Adrian Colyer opened SPR-1896 and commented

The reference documentation for the new AOP support in Spring 2.0 needs to be completed.

No further details from SPR-1896
Issue 1:
Context:

Playwright Version: 1.14.1

Operating System: Windows

Node.js version: 16.1

Browser: Chromium

Extra: Using Browser Library of Robot Framework. https://marketsquare.github.io/robotframework-browser/Browser.html

Describe the bug

I am using Robot Framework library called Browser Library which uses Playwright under the hood. It uses same selector strategy so I would imagine this bug is related to Playwright as the selector should be passed on to Playwright to find the element.

I have a form with a button that I am trying to locate and click. I would like to use the role attribute to find the element.

W3 standards say that the roles for this html should be implicit; however, Playwright is not finding the elements. My assumption is that Playwright only finds the role if it is explicitly provided.

The first selector strategy works.

css=#root >> css=form >> css=button

The second selector strategy does not work.

css=#root >> css=[role=form] >> css=[role=button]

Example HTML

<div id="root">
<form>
<button>Submit</button>
</form>
</div>

Please let me know if I am doing anything wrong. I think this would be necessary you want all implicit and explicate roles to be referenced in searching through selectors.

Issue 2:
I find dealing with both check() and uncheck() to be cumbersome and would prefer a single check method that can handle both through a parameter.

Say I have a checkbox that configures whether a customer is a "gold" member or not. I will be testing both cases so my page object needs to both check and uncheck the checkbox, which, paradoxically, is where I run into bothers.

I can either create two methods:

def is_gold_member(page):
page.check('#gold')

def is_not_gold_member(page):
page.uncheck('#gold')

Or I can create a single parameterized method that requires logic in the body:

def is_gold_member(page, value: bool):
if value:
page.check('#gold')
else:
page.uncheck('#gold')

I dislike both of these options because both replicate the selector for the checkbox (which I feel moves me in the wrong direction for maintenance), and I prefer not having logic in my page objects since that is where bugs tend to hide. Parameterizing check would solve both of these woes:

def is_gold_member(page, value):
page.check('#gold', value)

No duplication and my guys don't need to write logic. Not only do I feel this is a cleaner solution but I think it fits better with the rest of the Playwright API too since most other inputs are also parameterized. Take press for example. It takes a parameter that handles all the cases instead of creating methods for each possible key press:

# We don't do this for a reason
def press_enter()

def press_escape()

def press_control_plus_enter()

def press_F1()

# etc

This is what check and uncheck are: a method for each possible input. I'd love to see it parameterized instead. Thanks for listening!