WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
There is a fiddle illustrating the problem here http://jsfiddle.net/lddubeau/kcbFY/

(It imports 3.0.0 RC2 rather than what is on the wip branch. I tried to get the fiddle to get the latest from github but jsfiddle complained. Visual inspection of the files on the wip branch tells me the issue has not disappeared since 3.0.0 RC2 .)

The following scenarios refer to the fiddle above.

Scenario 1

If you load the fiddle and click on the panel headers and don't touch the two buttons at the bottom, when expanding one panel, the other collapses. This is the expected behavior.

Scenario 2

However, if you load the fiddle and then click the "Trigger it programmatically" button. Panel B will expand without panel A collapsing. The expected behavior would be for panel A to collapse as panel B expands.

Scenario 3

If you load the fiddle and then click the "Workaround" button, panel B will expand and panel A collapse. That's the expected behavior.

Scenario 4

Load the fiddle. Click on "Panel B". Works fine. Then click on "Panel A" so that panel A is expanded and panel B collapsed. Then, hit "Trigger it programmatically". It works as expected: panel A collapses, panel B expands.

Discussion

What happens in Scenario 2 is that when the $.collapse() function is called, the element appears to be some random collapsible element not part of a group of panels that should be coordinated together. There is no information on the element itself to tell $.collapse() that there is a data-parent associated with this element.

This is confirmed by scenario 4. There, the click on the "Panel B" heading triggers click.bs.collapse.data-api, which causes the collapsible element to acquire a Collapse object which is properly initialized. From that point on, it is possible to call $.collapse() on that element and get proper behavior but that's only because the user first clicked on the heading.

This is also confirmed by the workaround which consists in duplicating the information already present in the HTML so that the Collapse object is created properly. There is another workaround in this fiddle: http://jsfiddle.net/lddubeau/6uzL6/ This fiddle contains a modified HTML where the data-parent attribute is set on both the toggles and on their targets.

If the data-parent attribute were specified on the element that actually collapses rather than on the toggle (and modify click.bs.collapse.data-api to seek the data-parent information from its target) it would avoid having to duplicate the information either in the JS or in the HTML.

Issue 2:
It seems there is something funky happening when compiling the the less files to plain old css. While porting 3.0.0-wip to Sass I noticed duplicate rules in the bootstrap.css generated by recess:

A good example is in lines 587 to 605 of bootstrap.css. The rules for .dl-horizontal dd:before and .dl-horizontal dd:after are duplicated, it seems it has something to do with the clearfix mixin. It happens to all classes making use of clearfix(). I couldn't reproduce the error when extracting the mixin and classes into a smaller testfile.
Issue 1:
I fit exactly same data to LinearRegression() function but get two slightly different model coeficients.

1st try:

3260 12/05/2018 12:41:59 PM self.ref_price_psf_model.coef_1 = 0.8927025598257011

3260 12/05/2018 12:41:59 PM self.ref_price_psf_model.coef_2 = -1.697037974902777e-05

3260 12/05/2018 12:41:59 PM self.ref_price_psf_model.coef_3 = -0.031210337831353692

3260 12/05/2018 12:41:59 PM self.ref_price_psf_model.coef_4 = 0.0021041235932400064

3260 12/05/2018 12:41:59 PM self.ref_price_psf_model.intercept_ = 19.049368273019788

2nd try:

2976 12/05/2018 12:56:50 PM self.ref_price_psf_model.coef_1 = 0.8927025598256996

2976 12/05/2018 12:56:50 PM self.ref_price_psf_model.coef_2 = -1.6970379749026318e-05

2976 12/05/2018 12:56:50 PM self.ref_price_psf_model.coef_3 = -0.031210337831354636

2976 12/05/2018 12:56:50 PM self.ref_price_psf_model.coef_4 = 0.0021041235932399926

2976 12/05/2018 12:56:50 PM self.ref_price_psf_model.intercept_ = 19.049368273019823

I am expecting then to be exactly the same. Could you tell me what could cause this? How to fix it?

Thanks

Issue 2:
LinearRegression is sometimes not deterministic, as shown by the following test:

from sklearn.linear_model import LinearRegression
from sklearn.utils.testing import assert_array_equal
from sklearn.tests.test_multioutput import generate_multilabel_dataset_with_correlations

def test_investigate_linear_regression_indeterminacy():
# Is LinearRegression deterministic?
X, Y = generate_multilabel_dataset_with_correlations()
y = Y[:, 1]
ref = LinearRegression().fit(X, y).coef_
for i in range(1000):
coef = LinearRegression().fit(X, y).coef_
assert_array_equal(ref, coef, 'iter %d' % i)

test_investigate_linear_regression_indeterminacy()

which failed at iteration 18 in this Travis job. I can't reproduce locally.

It only occurs on one Travis platform (Linux + python 3.6.2), only sometimes (iteration 18 in this test case).

Failure spotted initially in #9257 (comment)
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
yes

Symfony version
3.4 ? maybe also before

In the sulu recipe, we will add another file which adds the firewall to the existing configuration. This is not really possible without manually adding the admin key inside the security.yaml file!

@stof hopefully you will add your thought which we have at the #SymfonyConHackday2017

Issue 2:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

Symfony version
-

One of the most frustrating limitations of the Security component config is that you can't define the firewalls in different files:

InvalidConfigurationException in PrototypedArrayNode.php line 325:

You are not allowed to define new elements for path "security.firewalls". Please
define all elements for this path in one config file.

But this could be so useful! Like in this example:

# app/config/dev/security.yml
security:
firewalls:
dev:
pattern: ^/(_(profiler|wdt)|css|images|js)/
security: false

# app/config/security.yml
security:
# ...
firewalls:
main:
# ...

So, my question for those experts in the internals of the Security component: would be really hard to remove this limitation? Maybe it's a matter of changing a few lines of code but nobody really tried to do that. Thanks!
Issue 1:
There are many native features that will require listening to windows messages and alter them.

It's important to hook to the original wndproc so we'll be able to alter messages as well.

After digging in I noticed there is a PreHandleMSG in here https://github.com/atom/electron/blob/master/atom/browser/native_window_views_win.cc#L81

And after a bit of testings I managed to affect the messages a windows is receiving.

I wonder if it is the best way to hook into the wndproc

Any thoughts?

Issue 2:
There are many native Windows features that will require listening to some WM or another. Right now there isn't a great way in Atom Shell to do this. AFAICT, your best bet is to:

Create your own native node module

Include <windows.h>

Create a message-only Hwnd that is a child of your Atom window

Hook WndProc for whatever message you're interested in

Fire a callback to the JS

It would be awesome if there was a generic way to add a handler for a window message, and Atom Shell took care of the above steps natively. Something like:

messageCode = 262 # WM_SYSCHAR
browserWindow.hookWindowMessage messageCode, (wParam, lParam) ->
# Do your dirty work
Issue 1:
If you call jl_init() from a Windows application without a console, Julia 0.7 and 1.0 will abort the application after trying and failing to duplicate an invalid stdio handle. Julia 0.6 was less strict (and possibly less correct) about this but at least the apparent result was that things worked and stdout/stderr output just disappeared.

This doesn't seem like an unreasonable use case for embedding and jl_init should handle it gracefully. If it can't easily be fixed it should at least be documented.

The easiest workaround I have found is to call AllocConsole() before jl_init(), with the predictable drawback that you get a window that you might not want. As a workaround for the workaround you can hide the console window with ShowWindow(GetConsoleWindow(), SW_HIDE), but not without a brief flickering between creation and hiding.

For more details, see https://discourse.julialang.org/t/embedding-jl-init-exits-on-windows-for-julia-0-7/13819

Issue 2:
Currently, convert is used to extract the magnitude of a quantity, or alternatively to give units to a dimensionless quantity. This happens in the Dates code in Base, and the behaviour has inspired similar behaviour in SIUnits.jl and Unitful.jl.

In Base, convert is generally used to convert between values of different types, but with same meaning. Since 1 and 1 second do not represent the same quantity, the use of convert to switch between them is a pun. In addition, it can lead to surprising behaviour. Note:

julia> convert(Base.Dates.Second, 60)
60 seconds

julia> convert(Base.Dates.Minute, ans)
1 minute

julia> convert(Int, ans)
1

So we have converted an Int back to itself, but the conversion was lossy!
Issue 1:
Summary of the new feature/enhancement

Make the WM tile automatically and properly.

Allow key binding for mode select (priority or other or grid)

Allow you to group custom presets into a custom template which you can then switch to using the binding describer above.

(When opening the custom template there is an option for what template you want to use for missing descriptors.)

ps. i wasn't sure if I should create 3 Feature request or 1.

Proposed technical implementation details (optional)

Simply read the amount of apps running on the desktop - floating windows.

Allow user to set windows at floating windows with a keyboard shortcut.

Have a list ways to do the sorting. Examples Below.

Issue 2:
Be able to change the template "on the fly" by using a keyboard shortcut.

When I press the given shortcut, it activates the template associated.

Then, the next time I use "Shift-drag" to place a windows into a template area, the areas shown corresponds to newly selected template.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
Users can consume the options appropriately or pass them down to recursive Deno.inspect() calls.

Issue 2:
Edit: the current proposal is here #8099 (comment)

Probably should have thought of this when we did Deno.customInspect but we didn't. As our console output has evolved, it makes it really hard to implement the same rich output. For example if you have the following code:

const h = new Headers();
h.append("key", "value");
console.log(h);

You would get something like the following output:

Where as if you did:

console.log({ key: "value" });

You would get:

Which takes advantage of all the other benefits of the output algorithm.

Therefore if we had another symbol that returned a more structured set of information, we could use the same algorithms to colourise the output and otherwise pretty print it. I would propose that we create Symbol("Deno.richCustomInspect") which would require a return of a tuple value of two strings. The first string would be the name for the inspector and the second value would be a JSON string, which would be parsed by the inspector.

So for example if I wanted a rich output for Headers, I would do something like this:

class Headers {
[Symbol.for("Deno.richCustomInspect]() {
const output = {};
for (const [key, value] of this[headersData]) {
output[key] = value;
}
return [ "Headers", JSON.stringify(output) ];
}
}

This would allow complex modelling of the internals, but ensure serialisation to a consistent format that can be handled by the inspector.
Issue 1:
Using a samsung 7 tablet

when doing challenges, "Go to my next challenge" link does not work when tablet is in portrait mode, but works fine in landscape

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-say-hello-to-html-elements has an issue. Please describe how to reproduce it, and include links to screen shots if possible.

I was unable to access the instructions for this module because the button labeled "More Information" was unresponsive on my mobile devices (both iPhone & iPad). For both, I'm running iOS v 8.3.

The editor and display both seem to be working fine. It would be extremely useful to be able to use my mobile devices in addition to my laptop because it's easier to integrate into my daily routine.
Issue 1:
Hello,

I want to apologize first if someone ask it before, I did a lot of searches, and I didn't find an answer, so.. as I don't know if that's an issue or not, I post it there.

I have, for many events (but not all) the following issue :

My listeners are called 2 times whereas I only send it once (I'm sure about it, I did a lot of tests) when I call next({}).

An example ?

The call : https://github.com/Peekmo/angular2-leap/blob/master/src/app/components/link-element/link-element.ts#L38

The template that call the component : https://github.com/Peekmo/angular2-leap/blob/master/src/app/components/page/page.html#L7

The function that is called twice for one .next() : https://github.com/Peekmo/angular2-leap/blob/master/src/app/components/page/page.ts#L23 (note : I'm forced to do that ugly timeout to avoid to do 2 times the same thing)

Is that normal ? Do I do something wrong ? (I have some listener in the same app that are only called once, and other twice so that's weird..)

If you never heard about that, that's probably an issue into my app.

Thank you ! 👍

Issue 2:
I'm submitting a ...

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

When using <select> with <select [attr.multiple]="true"> the value for the select is not an array of values but only a single value.

Expected behavior

<select [attr.multiple]> should populate the value of the select control with an array of values.

But if I use <select multiple>, it would work.

Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0

Browser: [Chrome 54]

Language: [TypeScript 2.0]

Node (for AoT issues): node --version = 6.4
Issue 1:
Challenge Create Decimal Numbers with JavaScript has an issue.

User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

var ourDecimal = 5.7;

// Only change code below this line
var myDecimal = 1.0;

The value 1.0 contains a decimal and is thus a floating point number, yet fails the test case.

Issue 2:
Challenge Create Decimal Numbers with JavaScript has an issue.

User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

var ourDecimal = 5.7;

// Only change code below this line
var myDecimal = 1.0;

This gave an error: "myDecimal should have a decimal point". But it does have a decimal point.

The test is:

assert(myDecimal % 1 != 0, 'message: <code>myDecimal</code> should have a decimal point');

The request to "Create a variable myDecimal and give it a decimal value" should perhaps specify that the decimal part needs to be non-zero. Or the error message needs fixing.

My last issue was closed without comment. Are "nit picks" like this unwelcome in general? I'd like to help improve the site, but if you would rather I keep these issues to myself I can do.
Issue 1:
Preflight Checklist

[x ] I have read the Contributing Guidelines for this project.

[ x] I agree to follow the Code of Conduct that this project adheres to.

Issue Details

Electron Version:

8.2.1

Operating System:

window 10

Last Known Working Electron version:

Dont know.

预期行为

没有崩溃

实际行为

通过web唤醒electron的时候，electron应用报错：

Invalid package C:\Program Files (x86)\Google\Chrome\Application\81.0.4044.92\resources\app.asar

正常的情况下打包安装双击能够打开。

Issue 2:
Preflight Checklist

[x ] I have read the Contributing Guidelines for this project.

[ x] I agree to follow the Code of Conduct that this project adheres to.

Issue Details

Electron Version:

8.2.1

Operating System:

window 10

Last Known Working Electron version:

Dont know.

预期行为

没有崩溃

实际行为

通过web唤醒electron的时候，electron应用报错：

Invalid package C:\Program Files (x86)\Google\Chrome\Application\81.0.4044.92\resources\app.asar

正常的情况下打包安装双击能够打开。
Issue 1:
/tmp# ls -lt sklearn-test* | head
-rw------- 1 buildslave buildslave 213 Jan 14 01:07 sklearn-test8Yh7h6.gz
-rw------- 1 buildslave buildslave 209 Jan 14 01:07 sklearn-testbux42U.bz2
-rw------- 1 buildslave buildslave 209 Jan 14 00:50 sklearn-testpv8EZp.bz2
-rw------- 1 buildslave buildslave 208 Jan 14 00:50 sklearn-testzv3J8Y.gz
-rw------- 1 buildslave buildslave 209 Jan 14 00:49 sklearn-testn2VN9G.bz2
-rw------- 1 buildslave buildslave 213 Jan 14 00:49 sklearn-testQ2Rs8V.gz
-rw------- 1 buildslave buildslave 209 Jan 14 00:20 sklearn-testDuiS27.bz2
-rw------- 1 buildslave buildslave 208 Jan 14 00:20 sklearn-testte9W4r.gz
-rw------- 1 buildslave buildslave 213 Jan 14 00:19 sklearn-testvJ8UnC.gz
-rw------- 1 buildslave buildslave 209 Jan 14 00:19 sklearn-testYTaIeW.bz2
root@lingual:/tmp# bzcat sklearn-testbux42U.bz2 | less
# comment
# note: the next line contains a tab
1.0 3:2.5 11:-5.2 16:1.5 # and an inline comment
2.0 6:1.0 13:-3
# another comment
3.0 21:27
4.0 2:1.234567890123456e10 # double precision value
1.0 # empty line, all zeros
2.0 3:0 # explicit zeros

Issue 2:
Description

KBinsDiscretizer with strategy='quantile' is producing duplicate bins when used on data which don't have uniform distribution.

Steps/Code to Reproduce

import numpy as np
np.random.randint(1, size=(10,1))
X1 = np.random.randint(1, size=(10,1))
X2 = np.random.randint(4, size=(5,1))

X = np.concatenate([X1, X2], axis=0)

from sklearn.preprocessing import KBinsDiscretizer
transformer = KBinsDiscretizer(encode='ordinal')
transformer.fit(X)

transformer.bin_edges_
# Output: array([array([0., 0., 0., 0., 1., 3.])], dtype=object)

transformer.transform(X)
# Output:
# array([[3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [3.],
# [4.],
# [4.],
# [4.],
# [4.],
# [4.]])

Actual Results

The first three bins are duplicates. They are not used in the output. Even if I change the n_bins to 3 or 4, even then the duplicate bins are generated and then not used.

Expected Results

I understand that:

The duplicate bins are present because the 'strategy' used is 'quantile' and n_bins is fixed.

The bins are not used in output because the internal code is using numpy.isclose and numpy.digitize.

So is there a scope of removing the duplicate bins after fitting with a warning?

Versions

System:
python: 3.6.6 |Anaconda, Inc.| (default, Jun 28 2018, 17:14:51) [GCC 7.2.0]
executable: ~/anaconda3/.../bin/python
machine: Linux-4.15.0-20-generic-x86_64-with-debian-buster-sid

BLAS:
macros: SCIPY_MKL_H=None, HAVE_CBLAS=None
lib_dirs: ~/anaconda3/.../lib
cblas_libs: mkl_rt, pthread

Python deps:
pip: 18.1
setuptools: 40.2.0
sklearn: 0.20.1
numpy: 1.15.4
scipy: 1.1.0
Cython: 0.29
pandas: 0.23.4
Issue 1:
Version

2.5.13

Reproduction link

https://jsfiddle.net/6vps8vej/

Steps to reproduce

Select one of the

What is expected?

The {{ selected }} text should appear.

What is actually happening?

The selected value does not change.

The code works if the <div is="select"> is changed to a native <select>

Manually binding with @change works

Issue 2:
Version

2.5.17-beta.0

Reproduction link

https://jsfiddle.net/Pomer/vdq3wbtL/1/

Steps to reproduce

Simple you can change Vue from 2.5.17 to 2.5.17-beta and the jsfiddle will stop working.

The idea it's simple we have an array of json componen than need to be sorted via computed function.

What is expected?

array of elements sorted, instead we get an error and nothing shown.

What is actually happening?

It seems to have an infinite loop, since i can set a console.log before the return statement of the computed function and see how many times its been called this function.

stacktrace:

vue.js:597 [Vue warn]: Error in render: "RangeError: Maximum call stack size exceeded"
(found` in <Root>)
warn @ vue.js:597
logError @ vue.js:1740
globalHandleError @ vue.js:1735
handleError @ vue.js:1724
Vue._render @ vue.js:4562
updateComponent @ vue.js:2779
get @ vue.js:3144
Watcher @ vue.js:3132
mountComponent @ vue.js:2786
Vue.$mount @ vue.js:8557
Vue.$mount @ vue.js:10957
Vue._init @ vue.js:4652
Vue @ vue.js:4739
(anonymous) @ main.js:9
vue.js:1744 RangeError: Maximum call stack size exceeded
at Watcher.get (vue.js:3158)
at Watcher.getAndInvoke (vue.js:3244)
at Watcher.update (vue.js:3222)
at Dep.notify (vue.js:703)
at Array.mutator (vue.js:851)
at Vue.testSort (main.js:89)
at Watcher.get (vue.js:3144)
at Watcher.getAndInvoke (vue.js:3244)
at Watcher.update (vue.js:3222)
at Dep.notify (vue.js:703)
Issue 1:
Using a tangent space normal map and DoubleSide phong material doesn't show lighting effects on Android Chrome. (Desktop Chrome seems to be fine, changing to FrontSide also works)

Code

https://gist.github.com/nbilyk/809fc2a3fc1644a72048038e01ac6468

const planeGeo = new THREE.PlaneBufferGeometry(planeSize, planeSize);
const planeMat = new THREE.MeshPhongMaterial({
map: groundTex,
side: THREE.DoubleSide, // DoubleSide causes lighting not to be seen on android. FrontSide works fine.
});

const groundNormalText = textureLoader.load('./assets/groundNormalMap.jpg');
groundNormalText.wrapS = THREE.RepeatWrapping;
groundNormalText.wrapT = THREE.RepeatWrapping;
groundNormalText.magFilter = THREE.LinearFilter;

planeMat.normalMap = groundNormalText;
planeMat.normalMapType = THREE.TangentSpaceNormalMap;
planeMat.normalScale = new THREE.Vector2(0.8, -0.8); // Negative scaling - normal map written for a different coordinate system.

const mesh = new THREE.Mesh(planeGeo, planeMat);
mesh.receiveShadow = true;
mesh.rotation.x = Math.PI * -.5;
scene.add(mesh);

Expected:

Actual:

Platform:

Device: Pixel 2

OS: Android

Browser: Chrome 87.0.4280.141

Three.js version: r124

Issue 2:
Description of problem

Models appear to be washed out/metallic when they are loaded on certain Android devices.

From the tested devices Google Pixel and OnePlus phones display this issue.

Models are loaded in .glb format (packed with PBR textures), the scene contains an HDRI environment map.

This issue may be related to #19479

Example Screenshots

Viewers used for testing

https://gltf-viewer.donmccurdy.com/ (r123)

https://gltf.insimo.com/ (r88)

THREE.js Versions tested

r123 (issue appears)

r121.1 (issue appers)

r88 (works correctly)

Browser

All of them

Chrome

FireFox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Devices used for testing

Google Pixel 4a (Android 11, 2 separate devices) - issue appears

Google Pixel 4xl (Android 11) - issue appears

OnePlus 6 (Android 10) - issue appears

Samsung Galaxy Note 9 (Android 10)

Samsung Glaxy S20+ (Android 10)

Samsung a50 (Android 9)