WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Responsive Design With Bootstrap

Link to challenge

Issue Description

The first checkbox's label, "Loving", drops down to a new line. To me, it looks odd and appears as though the assignment is incorrect or that something is wrong with the student's code.

A student may hack this by removing the leading space before "Loving", but then it won't visually match the other two checkbox labels, both of which have spaces to separate them from the actual checkbox itelf.

Perhaps shortening the actual word from "Loving" to "Kind" or "Calm" would be an easy fix?

Browser Information

Appears in current versions of Chrome and Firefox. Not tested in any other browsers. Only tested on desktop.

Screenshot

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-modify-array-data-with-indexes has an issue. It seems like a bug. Thanks.
Issue 1:
Using 2.5.x-dev (7e573f4)

Duplicated property throws error in appDevDebugProjectContainer :

PHP Fatal error: Cannot redeclare appDevDebugProjectContainer::$parameters in home/vagrant/var/www/app/cache/dev/appDevDebugProjectContainer.php on line 22

Maybe coming from this line

symfony/src/Symfony/Component/DependencyInjection/Dumper/PhpDumper.php

Line 846
in
7e573f4

private \$parameters;

Issue 2:
ReflectionExtractor currently supports array mutators (add, remove) but it's not very useful as the singular method name is not being checked.

If we can use doctrine/inflector to singularize the property name, we'll be able to pick up a lot more useful information in many cases. I'll open a PR if this is desirable (looking at the composer.json of Symfony components, I understand that it has to be an optional dependency).
Issue 1:
Here you can see the problems, uncommented the bootstrap.css injection to see the errors in:

http://jsfiddle.net/26mrX/

Marker icon looks wrong when icon is draggable: (draggable: true)

Map zoom controlers looks wrong and they disappear

Much much more problems!!!!...

It is incredible that you have this lame problems, shame on you!

Issue 2:
First of all thanks for your fantastic work. It does SAVE me a lot of time.

When I put Google Maps into Bootstrap layout, img tag in Google Maps breaks because Bootstrap set img max-width to 100%. When I comment max-width, it's working find but I'm not sure whether it'll break something else in Bootstrap or not.

Bootstrap and Google Maps

http://jsfiddle.net/jhnRD/1/

Google Maps without Bootstrap

http://jsfiddle.net/aVx8L/

Cheers,
Issue 1:
tsc version 1.4.1.0 (1.3.0 work correctly)

tsc -w --out ../file.js file.ts

file.ts

/// <reference path="./interfaces.ts"/>
alert('1');

interfaces.ts

interface HashTable<T> {
[key:string]: T;
}

/*interface Test {
}*/

( multiline comment closed on last line of file, no emtpy lines after it ). compiled to

/*interface Test {
interface HashTable<T> {
[key:string]: T;
}

/*interface Test {

/// <reference path="./interfaces.ts"/>
alert('1');

last line of interfaces.ts dissapeared so comment block doesnt closed and result js file incorrect.

without reference

typescript

interface HashTable<T> {
[key:string]: T;
}
/*interface Test {
*/

js

/*interface Test {
interface HashTable<T> {
[key:string]: T;
}

/*interface Test {

Issue 2:
Hi,

TS Version: 1.4

The following code:

var x: any;
/*
var bar;
*/

Emits the following JavaScript

var x;
/*
var bar;
var x: any;
/*
var bar;

Expected

var x;
/*
var bar;
*/
Issue 1:
There are some cases where dpkg/apt can leave file like logging.yml.dpkg-dist files in /etc/elasticsearch and LogConfigurator will pick them up by default. This is bad because those files might contain garbage and break logging. Why not just pick up logging.yml? Is this something like the conf.d pattern?

Issue 2:
elasticsearch 1.3 will try to import .svn/text-base/logging.yml.text-base as json and fail to set up logging as a whole.

I think it's not reproducible with subversion 1.7+ since a new .svn-format with hash-based filenames is used. But Debian wheezy/stable is still using subversion 1.6 and is what we use.

I found https://github.com/elasticsearch/elasticsearch/blob/1.3/src/main/java/org/elasticsearch/common/logging/log4j/LogConfigurator.java#L107 which is the problematic part.

imo it should at least skip "hidden" directories, if not be limited to some more strict rules (file extension whitelist without the "catch-all" default, ...).

I thought of only ignoring the failed file, but that could lead to strange errors too.

What if you have a logging.json. Then you would have a .svn/text-base/logging.json.text-base, which could import and override the original logging.json (local modified logging.json). => quite troublesome to find out why the changes don't work until you commit them :)

Known workarounds (also see https://groups.google.com/forum/#!topic/elasticsearch/8zlwEj12DjI):

Add "copy/move to logging.yml" command before startup (so that the file in .svn doesn't start with "logging.")

mount an empty directory over .svn (tmpfs, ...). Umount/mount if needed to work with svn <= that's the solution we use, since we mount it readonly over nfs and cp/mv doesn't work

I think both workarounds are quite dirty hacks and you shouldn't be forced to use those, just because you use a vcs.
Issue 1:
Issue Type:

Bug report

Ansible Version:

ansible 2.0.0.2

ansible 2.1.0 (devel 7e39634)

Ansible Configuration:

N/A

Environment:

Ubuntu 15.10

Summary:

Ansible 2.0 added a feature to use include statements together with with_items loops. When nesting include statements, (i.e. file A.yml includes B.yml, which includes C.yml) the item variable is not set properly, i.e. the inner include + with_items loop does not override the item value from the outer loop.

Steps To Reproduce:

main.yml

---
- include: include_outer.yml
with_items:
- 1
- 2
- 3

include_outer.yml

---
- debug:
msg: "Outer include: item={{ item }}"

- include: include_inner.yml
with_items:
- A
- B
- C

include_inner.yml

---
- debug:
msg: "Inner include: item={{ item }}"

Expected Results:

"msg": "Outer include: item=1"
"msg": "Inner include: item=A"
"msg": "Inner include: item=B"
"msg": "Inner include: item=C"
"msg": "Outer include: item=2"
"msg": "Inner include: item=A"
"msg": "Inner include: item=B"
"msg": "Inner include: item=C"
"msg": "Outer include: item=3"
"msg": "Inner include: item=A"
"msg": "Inner include: item=B"
"msg": "Inner include: item=C"

Actual Results:

"msg": "Outer include: item=1"
"msg": "Inner include: item=1"
"msg": "Inner include: item=1"
"msg": "Inner include: item=1"
"msg": "Outer include: item=2"
"msg": "Inner include: item=2"
"msg": "Inner include: item=2"
"msg": "Inner include: item=2"
"msg": "Outer include: item=3"
"msg": "Inner include: item=3"
"msg": "Inner include: item=3"
"msg": "Inner include: item=3"

Issue 2:
Issue Type:

Feature Idea

Ansible Version:

1.8

Environment:

N/A

Summary:

Please summarize your request in this space. You will earn bonus points for being succinct, but please add enough detail so we can understand the request. Thanks!

Steps To Reproduce:

If this is a bug ticket, please enter the steps you use to reproduce the problem in the space below. If this is a feature request, please enter the steps you would use to use the feature. If an example playbook is useful, please include a short reproducer inline, indented by four spaces. If a longer one is necessary, linking to one uploaded to gist.github.com would be great. Much appreciated!

Expected Results:

Docker 1.2 now lets you specify a restart policy (see here: https://blog.docker.com/2014/08/announcing-docker-1-2-0/). It should be configurable using the docker module in 1.8.

Actual Results:

Cannot configure the restart policy using ansible.
Issue 1:
Fast Insider Build 10.0.19008.1000.

Issue 2:
Environment

W10 Pro V1903 Build 18362.295

PowerToys: 0.11.0

Settings Screen

Windows build number: [run "ver" at a command prompt]
PowerToys version:
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Just installed and attempted to open settings. Screen is totally blank/empty.

I 'repaired - same issue.

Uninstalled, reboot and reinstall - same issue.

Expected behavior

Expect to see config options

Actual behavior

Blank window.

Screenshots

https://i.imgur.com/a7oWKgp.png
Issue 1:
why the number of vertices is being rendered 8 or 9 times more than the actual number can it be simplified or at least rendered the same? Is the WebGl taking additional resources for vertices?

Also I tried lots of simplifiers but even after simplifying still not reaching the target which is 30000 vertices.

the current number is around 260000 vertices

Issue 2:
If an instance of SkinnedMesh is cloned using the SkinnedMesh::clone() method, the resulting clone will have its bones duplicated. See the following explanation of the calling sequence:

The SkinnedMesh::clone() method will do two things:

First it will call its contructor.

Then calls theMesh::copy() method, which calls Object3D::copy().

https://github.com/mrdoob/three.js/blob/dev/src/objects/SkinnedMesh.js#L202

The constructor creates Bone objects from the geometry data and adds them to the current SkinnedMesh instance at SkinnedMesh::initBones().

The later call to Object3D::copy() -which is called with (default) recursion enabled- will clone and add new children. These bones are already children of the new SkinnedMesh instance, so we're cloning and re-adding the same bones again.

Related to the issue itself, it'd be useful to allow changing the recursive parameter from the clone/copy methods. Here's a possible patch, adding the recursive parameter:

adalessandro@272d308

Issue reported on dev branch.
Issue 1:
I'm not 100% sure if this is a numpy or python bug, but the behavior is quite weird. I've narrowed it down to two simple test cases, one which works and one which segfaults.

I can create a SharedMemory object, I can create a numpy array backed by it and read and write to it. I can do the same with a second SharedMemory object referring to the same space, created using the name. But I can't have a function return this np array, or accesses will segfault.

Reproducing code example:

from multiprocessing import shared_memory
import numpy as np

def np_array_from_shm_name(name, shape=(2,)):
shm = shared_memory.SharedMemory(name=name)
np_array = np.ndarray(shape, buffer=shm.buf, dtype=np.int32)
np_array[:] = (0,0)
print(np_array) # prints [0 0]
return np_array

if __name__ == "__main__":
shm = shared_memory.SharedMemory(create=True, size=8)
shm2 = shared_memory.SharedMemory(name=shm.name)
np_array = np.ndarray((2,), buffer=shm.buf, dtype=np.int32)
np_array[:] = (0, 0)
print(np_array) # prints [0 0]
np_array = np.ndarray((2,), buffer=shm2.buf, dtype=np.int32)
np_array[:] = (0, 0)
print(np_array) # prints [0 0]
np_array = np_array_from_shm_name(shm.name)
np_array[:] = (0, 0) # segfaults
print(np_array)
shm.unlink()
shm2.unlink()

Error message:

Thread 1 "python3-dbg" received signal SIGSEGV, Segmentation fault.

0x00007ffff692e0e9 in INT_setitem (op=0, ov=0x7ffff7491000, vap=0x7fffd68cbd60) at numpy/core/src/multiarray/arraytypes.c.src:235

235	numpy/core/src/multiarray/arraytypes.c.src: No such file or directory.

(gdb) py-bt

Traceback (most recent call first):

File "segfault_poc_simple.py", line 66, in

np_array[:] = (0, 0) # segfaults

NumPy/Python version information:

1.17.4 3.8.6 (default, Sep 25 2020, 09:36:53)

[GCC 10.2.0]

Issue 2:
This crashes in python2 and python3 with a segfault:

import mmap

# create test file
a = arange(10., dtype='f4')
a.tofile('test')

# opens it as a memmap
with open('test', 'r+b') as f:
mm = mmap.mmap(f.fileno(),0)

#view the mmap, then close it
x = np.frombuffer(mm, dtype='f4')
mm.close()
print(x) # segfault

In frombuffer mumpy uses the PEP3118 interface to the mmap to get a pointer to the data, so it seems we are using the interface incorrectly somewhere.

It seems to me that the "correct" behavior may be for it to be impossible to close the memmap while pointers to it exist; this is the behavior for memoryviews of mmaps. That is, the line mm.close() shoud raise an error BufferError: cannot close exported pointers, as in currently happens in python3:

>>> import mmap
>>> with open('test', 'r+b') as f:
>>> mm = mmap.mmap(f.fileno(),0)
>>> mv = memoryview(mm)
>>> mm.close()
BufferError: cannot close exported pointers exist

however note also that in python2 we cannot create the memoryview (mv) because of an error TypeError: cannot make memory view because object does not have the buffer interface.

Note how mmap_buffer_getbuf (link) in the mmap module takes care to keep track of any buffer access to the mmap (the exports counter). Evidently we are somehow bypassing that in numpy.
Issue 1:
Hi,

I'm editing some files which include Myanmar text. This includes diacritic characters (meaning char + char adding a diacritic (above / below / left / right) the previous char). Atom appears to give each char equal space, meaning that I need to click right of the text to select it, and the highlight appears offset right, too. Each string makes it more difficult to highlight text appearing after it on the line.

Put the text နေပြည်တော် in the middle of a long line to see what this looks like. This problem will occur with many other scripts, for example Devanagari used widely in India and Nepal - use this text: देवनागरी. Can you use HTML5 Canvas measureText() ?

Issue 2:
Halp ticket:

support/e61e5074bc3011e396a434cf997499c3

Support for Unicode is incomplete. Unicode characters are shown, but the cursor get stuck, and the navigation with the keyboard arrows stop working.

The user was using this string as an example ג׳ג׳ג׳dwdwdww

Here's a GIF of me pressing just the right arrow key to get from the beginning of the string to the end:
Issue 1:
Opening this link in Firefox only produces let foo in the left pane.

Issue 2:
I have a reproducible case where whitspace isn't preserved correctly:

var Foo = React.createClass({
render() {
return (
<span>foo</span>
);
}
});

var Bar = React.createClass({
render() {
return (
<div>
<Foo/> bar
</div>
);
}
});

When we render <Bar/> the text foobar is rendered in browser without a space character between foo and bar.

React's jsx tranformer outputs something like <span> bar</span> while 6to5 outputs <span>bar</span>.
Issue 1:
https://www.rstudio.com/wp-content/uploads/2015/02/data-wrangling-cheatsheet.pdf

I think we could pretty much rip this off exactly as is and just substitute pandas functions directly.

Further could update comparison with R a bit.

anyone up for this?

Issue 2:
I'm running into issues using bootstrap samples of the rows of a DataFrame. Example:

import pandas
import numpy

numpy.random.seed(1)
df=pandas.DataFrame({'a':numpy.random.randn(20),'b':numpy.random.randn(20)})
nrows=df.shape[0]

# make a bootstrap sample of the rows (nrows indices with replacement)
boot_indxs=numpy.random.random_integers(0,nrows-1,nrows)

# make a dataframe with sampled rows
df2=df.irow(boot_indxs)
print df2

# this complains but that's ok since row 5 of df wasn't sampled
print df2.ix[:5,:]

# this complains, but perhaps it shouldn't since I'm just asking for the first nine
# rows of the data frame
print df2.irow(range(10))

# this works however which is great
print df2.irow(slice(10))

# the problem is then accessing rows without slices
# use case: taking a random subset of the rows of the bootstrapped dataframe
# to fit a predictive model and test it on the remaining rows
print df2.irow(numpy.random.permutation(range(nrows))[:15])
Issue 1:
Here you can see that when the animation is running, the scroll bar appears. OS X 10.6.8 Chrome latest. You can also see a tiny 1px white-ish border in between the navbar and the collapsed nav items, this did not appear in RC1.

Issue 2:
On firefox 23/chrome/ie10 win7:

After the animation they diseappear on all browsers (if height <= 340px, of course)
Issue 1:
#[derive(Default)] fails on objects that contain a field of an associated type, even if that field is Default.

For example (also https://gist.github.com/4c85bcab2cf9f8c56dc2):

trait TR {
type Assoc : Clone + Copy + Default;
}

#[derive(Clone, Copy, Default)]
struct Foo<T: TR> {
thing : T::Assoc,
}

impl <T: TR> Foo<T> {
fn bar() {
// This works
let _ : T::Assoc = Default::default();
// This does not.
let _ : Foo<T> = Default::default();
}
}

This fails with "error: the trait core::default::Default is not implemented for the type T [E0277]". Except that we don't want a default T, we want a default Node.

Manually implementing Default works as a workaround:

impl<T: TR> Default for Foo<T> {
fn default() -> Self { Foo { thing : Default::default() } }
}

Happens in 1.3, beta, and nightly as of Sep. 20.

Issue 2:
In the following code:

#[derive(Copy, Clone)]
struct Y<T>(&'static fn(T));

both derives expand to impls that require the corresponding trait to be implemented on the type parameter, e.g.:

#[automatically_derived]
impl <T: ::std::marker::Copy> ::std::marker::Copy for Y<T> where
T: ::std::marker::Copy {
}

However, this isn't actually necessary, as Y<T> will still be eligible for Copy regardless of whether T is.

This may be hard to fix, given the compilation phase at which #[derive] works...
Issue 1:
Hi,

When I run an identical query on 0.90.1 and 0.90.2 I get different results:

{
"filter": {
"terms": {
"field": {
"id": "bar",
"type": "doctype",
"path": "lookupField"
}
}
},
"query": {
"match_all": {}
}
}

In 0.90.1 when filter returned no results the result of the query was also empty, i.e. 0 hits.

In 0.90.2 it returns everything. The latter behavior is probably better and more expected, but I haven't seen it documented anywhere. Did I miss something?

Issue 2:
Given the following script: https://gist.github.com/dakrone/6034875

I was expecting the same output for both queries (no documents matched), but instead I get:

∴ ./missing-filter-bug.zsh
Regular filter for null_value=true, existence=false
{
"took" : 2,
"timed_out" : false,
"_shards" : {
"total" : 1,
"successful" : 1,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [ {
"_index" : "missing-test",
"_type" : "doc",
"_id" : "1",
"_score" : 1.0, "_source" : { "id": "1" }
}, {
"_index" : "missing-test",
"_type" : "doc",
"_id" : "2",
"_score" : 1.0, "_source" : { "id": "2", "myfield": "foo" }
} ]
}
}
Filtered query with filter for null_value=true, existence=false
{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 1,
"successful" : 1,
"failed" : 0
},
"hits" : {
"total" : 0,
"max_score" : null,
"hits" : [ ]
}
}
Issue 1:
Using chrome on windows, on a fresh session, launching the modal from demo page

http://getbootstrap.com/javascript/

click "close" or "x" works fine the first time, the second time it fails to close...

Issue 2:
Hi,

The code used on last Thursday worked fine. But after updated to latest code on Monday (GMT+8), the modal dialog when clicks to dismiss for seconds onward cannot be close.

I am checking on source code line 932, if I commented out this line then it is working again.

this.$element

.removeClass('in')

.attr('aria-hidden', true)

//.off('click.dismiss.modal')

Am I missing anything...?

Sorry for the grammar. Thanks.
Issue 1:
Conversion from BigInt

gmp (78) | failed at 2021-01-19T21:39:56.822
Test Failed at /nobackup/users/vchuravy/dev/julia/test/gmp.jl:501
Expression: T(big"2" ^ (n + 1) - big"2" ^ (n - precision(T))) === T(Inf)
Evaluated: -Inf16 === Inf16

On Power9 julia -C pwr9

julia> T=Float16; n = exponent(floatmax(T))
15

julia> T(big"2" ^ (n + 1) - big"2" ^ (n - precision(T)))
Inf16

On Power9 julia -C pwr8

julia> T=Float16; n = exponent(floatmax(T))
15

julia> T(big"2" ^ (n + 1) - big"2" ^ (n - precision(T)))
-Inf16

Gist: https://gist.github.com/vchuravy/a0170b4d42e46d800aae53b3a80bb582

Duplicate of #38896 which I closed since fixing #38883 made it harder to reproduce until #39300

Upstream: https://bugs.llvm.org/show_bug.cgi?id=49092

Issue 2:
Presently calls like _jl_lapack_geqp3 are simple wrappers around calls to Lapack subroutines. They do return the info value as the value of the function call instead of a pointer argument that is modified in the subroutine. However, they do not themselves do the "double call" where the first call to the Lapack subroutine returns the desired size of the work array and the second call does the actual computation.

There have been a couple of suggestions on julia-dev on how to restructure this. One is to use Lapacke which provides C calling sequences for Lapack subroutines. However, after looking at the code for Lapacke I think it would be better to incorporate that functionality in Julia code.

I propose extending the jl_lapack* functions to perform the allocation of any work or iwork arrays, doing the double call within this function if needed.

I think it should also be possible to simplify the calling sequences by extracting the "leading dimension" arguments like lda if A is a StridedMatrix{T} argument. Many if the higher-level functions that call the jl_lapack* functions themselves do the check of stride(A,1) == 1 and extract stride(A,2) as lda To me it seems that the information on the dimensions and strides of A should be accessed within the jl_lapack* functions, not be passed to them, if A is defined to have type StridedMatrix{T}. At least I can't think of a situation where the M, N, A, LDA arguments would be other than size(A,1), size(A,2), A, stride(A, 2) when A is a StridedMatrix{T}.

I can make such changes and submit a pull request if this is deemed reasonable.
Issue 1:
In some PRs for adding validation to functions: #24924 or #25026, there will be double validation, by the function and another by the estimator. @adrinjalali and I share the same concern about keeping constraints in sync between the function and the estimator: #24924 (comment), #25026 (comment).

The test for validation is very strict about including a constraint for every parameter. I see the purpose of having this strictness is such that when a new parameter is added, then a constraint is also included.

I propose adding a parameters_to_validate to validate_params which is a collection of strings that states which parameters should be validated. This way when a new parameter is added, the default is to add a constraint for the new parameter, but it can be ignored by adding it to the parameters_to_validate list.

CC @jeremiedbb @glemaitre @adrinjalali

Issue 2:
I think we agreed that "labels" is a bad name for what it does in cross-validation. We could rename it to groups in the model-selection module, akin to what we did in #7169.

This is kind of a "now or never". It definitely has cost. I think it might be worth it (I just had a discussion where someone was looking for this exact feature but couldn't find it because of the name).

@jnothman and @GaelVaroquaux certainly have opinions ;)