WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Environment

Windows build number: 1903
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Have a 1366x768 monitor

Open "Edit zones"

Realize that the window is taller than 768 pixels

Drag it down so you can resize it maybe

Realize it's not resizeable

Expected behavior

Window is resizeable and/or fits on any reasonable screen

Actual behavior

Window is too tall and not resizeable

Screenshots

Issue 2:
📝 Provide a description of the new feature

I want word meanings feature in powertoys as it is in spotlight.
Issue 1:
The documentation for the metric parameter for silhouette_score() reads:

If metric is a string, it must be one of the options allowed by metrics.pairwise.pairwise_distances. If X is the distance array itself, use metric="precomputed".

However, entering metric='l1' or metric='cosine' both lead to an error:

File "search_cluster_02.py", line 148, in

% metrics.silhouette_score(X, labels, sample_size=1000,metric="l1"))

File "C:\Anaconda\lib\site-packages\sklearn\metrics\cluster\unsupervised.py", line 84, in silhouette_score

return np.mean(silhouette_samples(X, labels, metric=metric, *_kwds))

File "C:\Anaconda\lib\site-packages\sklearn\metrics\cluster\unsupervised.py", line 143, in silhouette_samples

distances = pairwise_distances(X, metric=metric, *_kwds)

File "C:\Anaconda\lib\site-packages\sklearn\metrics\pairwise.py", line 657, in pairwise_distances

return func(X, Y, **kwds)

File "C:\Anaconda\lib\site-packages\sklearn\metrics\pairwise.py", line 244, in manhattan_distances

raise ValueError("manhattan_distance does not support sparse"

However, the documentation for metrics.pairwise.pairwise_distances indicates that sparse matrices are allowed:

Please note that support for sparse matrices is currently limited to those metrics listed in pairwise.PAIRWISE_DISTANCE_FUNCTIONS.

Looking there, on Github, we have:

PAIRWISE_DISTANCE_FUNCTIONS = {
# If updating this dictionary, update the doc in both distance_metrics()
# and also in pairwise_distances()!
'cityblock': manhattan_distances,
'cosine': cosine_distances,
'euclidean': euclidean_distances,
'l2': euclidean_distances,
'l1': manhattan_distances,
'manhattan': manhattan_distances, }

Honestly, I can't tell if this is a documentation problem (or clarity issue) or a code problem.

To reproduce this, just run the example script from this page:

http://scikit-learn.org/stable/auto_examples/document_clustering.html

and at the very bottom of the script, add the metric='l1' parameter to the call to silhouette_score.

Issue 2:
A simple case can be found here when manhattan_distances take two sparse matrices as input

https://gist.github.com/4117966

The function fails without complaining.

Seems @jakevdp https://github.com/jakevdp/pyDistances/ has many very efficient routines for computing pairwise-distances for sparse matrices, any plan for adopting some of them to sklearn?
Issue 1:
At first. Thank you all the Bootstrap 3 developers for your great work.

For icons, Bootstrap 3.0 switched from "icon-" to "glyphicon" "glyphicon-".

mbo written here #10201 (comment):

Overall, it comes down to performance. The attribute selectors we used in 2.x just don't cut it in larger projects and classes are way more performant. It also fits with our base and modifier class approach elsewhere in the project.

and here: #8332 "Remove Glyphicons"

Makes Glyphicons more readily available to the masses, with or without Bootstrap's integration.

Keeps the core project as lean as possible with regards to number of files, build processes, versioning, and more.

Enables the community to more easily swap other icon libraries in and out.

So the first target is better performance. We get it by using base class and a modifier class.

And the second target is more easily swap other icon libraries.

Using the product name "glyphicon" in the class names work against this!

It links bootstrap 3 stronger to glyphicon as ever before. It brings a lot of trouble and only ugly solutions for providers of icon sets and also for users of icon set.

See here for details: FortAwesome/Font-Awesome#940 (comment)

But why?

Using "icon" as base class and "icon-" as prefix for modifier classes (or may be "bs-icon" and "bs-icon-") would avoid many of these problems.

I beg of you the bootstrap developers, do not longer take a product name of a special icon set as default class name in bootstrap.

Is there anybody who support this wish?

Please add a vote.

ps: Sorry for my English, I still try to find the right words with a dictionary.

Issue 2:
I'm sure some where along the line there was a discussion about how icon classes should be declared, but how the current format was decided on is beyond me.

it takes forever to type by hand

impossible to switch to other icons-as-a-font libraries and keep the same code as most of them use Bootstrap 2.x .icon-

approx 17 extra bytes I don't want or need

just plain old silly

I believe it would be in the best interest of the Bootstrap community to start a serious discussion on standardizing the icon class names. More for than just for Bootstrap, too. Font-Awesome and the other icons-as-a-font libraries would benefit from standardization as well.

To me, it seems natural to stick to Bootstrap 2.x, (just .icon-), however extending with an extra .icon before it would also be better than the existing implementation.
Issue 1:
See also issue #8561.

http://play.golang.org/p/VYrNcjJ_Qo

compiles w/o a problem but leads to a guaranteed run-time failure: The method m in T1
and T2 have conflicting signatures and thus x (static type T1) cannot possibly be of
type T2.

The spec does not require that the signatures be conflict-free (
http://tip.golang.org/ref/spec#Type_assertions ):

"If T is an interface type, x.(T) asserts that the dynamic type of x implements the
interface T."

Interestingly, when it comes to interface assignments ("implements" relation),
conflicting method signatures are not permitted:

http://play.golang.org/p/QAZWsPqejr

prog.go:13: cannot use x2 (type T2) as type T1 in assignment:
T2 does not implement T1 (wrong type for m method)
have m(string)
want m(int)
prog.go:14: cannot use x1 (type T1) as type T2 in assignment:
T1 does not implement T2 (wrong type for m method)
have m(int)
want m(string)

Issue 2:
Reported by developer on IRC

lucky(~/src) % gdb ./addr
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>;...
Reading symbols from /home/dfc/src/addr...done.
(gdb) b main.main
Breakpoint 1 at 0x400c00: file /home/dfc/src/addr.go, line 9.
(gdb) r
Starting program: /home/dfc/src/addr
[New LWP 3980]
[Switching to LWP 3980]

Breakpoint 1, main.main () at /home/dfc/src/addr.go:9
9 func main() {
(gdb) goroutines
Undefined command: "goroutines". Try "help".

What is the expected output? What do you see instead?

gdb integration should work

Please use labels and text to provide additional information.
Issue 1:
In python2.6.6 (I do not have more recent versions available at work) there is a problem with scipy.special.gammaincinv with the second parameter (the quantile) set as 0.25. For example

gammaincinv(1.0, 0.25)

0.0

gammaincinv(2.0, 0.25)

0.0

gammaincinv(3.0, 0.25)

0.0

gammaincinv(3.0, 0.24)

1.6894710461335511

gammaincinv(1.0, 0.24)

0.27443684570176036

gammaincinv(1.0, 0.26)

0.30110509278392172

Issue 2:
Original ticket http://projects.scipy.org/scipy/ticket/975 on 2009-07-15 by @pierregm, assigned to @pv.

special.gammaincinv(x,y) fails when y=0.25 for any value of x.

Could it be a problem in c_misc/gammaincinv.c ?

(http://article.gmane.org/gmane.comp.python.scientific.devel/11271)
Issue 1:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.4.4

Currently the theme bootstrap_4_layout.html.twig renders checkboxes like that

<div class="form-check">
<label class="form-check-label">
<input type="checkbox" id="defaultCheck1" name="anyname" class="form-check-input" value="1"> Default checkbox
</label>
</div>

But the bootstrap 4 documentation has the following structure

<div class="form-check">
<input class="form-check-input" type="checkbox" value="" id="defaultCheck1">
<label class="form-check-label" for="defaultCheck1">
Default checkbox
</label>
</div>

The same logic for radio buttons

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
4

Hi!

I'm not sure if it is a bug or intentional, but in bootstrap4 form layout the validation errors are rendered inside the label tag see:

https://github.com/symfony/twig-bridge/blob/master/Resources/views/Form/bootstrap_4_layout.html.twig#L206

It's not exactly how bootstrap recommends it.

https://getbootstrap.com/docs/4.0/components/forms/#validation

Regards,

Marton
Issue 1:
I've updated to 2.7 and changed my choice types to use choices_as_values.

Most of my choices are simple "No" or "Yes". But they must not be preselected - the user is forced to choose. That is why none of my radio buttons is initially checked.

I tried this with 2.7:

$builder->add('aberdeenBlind', 'choice', array(
'choices' => array(
'Ja' => true,
'Nein' => false
),
'choices_as_values' => true,
'expanded' => true,
'required' => true
))

Unfortunately the second radio button (false => 'Nein') is preselected. This also happens when flipping the order of the choices. The false choice is always preselected.

I played around with other options e.g. placeholder, empty_* etc. but then I recognized:

This only seems to happen when using boolean values. The following example would not preselect any value:

$builder->add('aberdeenBlind', 'choice', array(
'choices' => array(
'Ja' => 'Y', // or '1'
'Nein' => 'N' // or '0'
),
'choices_as_values' => true,
'expanded' => true,
'required' => true
))

Possibly related:

#14712 by @maxailloud

#15573 by @imphil

Issue 2:
Using Symfony 2.8.2 or 3.0.2.

You can reproduce the problem with this simple statement:

$builder->add('participation', ChoiceType::class, array(
'choices' => [ 'yes' => true, 'no' => false ],
'placeholder' => 'Select a value',
'empty_data' => null,
'choices_as_values' => true,
));

Expected result:

<select name="filter[participation]" id="filter_participation">
<option value="">Select a value</option>
<option value="1">Yes</option>
<option selected="selected" value="0">No</option>
</select>

Actual result:

<select name="filter[participation]" id="filter_participation">
<option value="1">Yes</option>
<option selected="selected" value="">No</option>
</select>

Dump of choiceList:

As you can see, the placeholder is not rendered. If I add a new empty value in 'choices', I got an empty value in the view plus the placeholder value.
Issue 1:
Electron version: 1.4.15

Operating system: Windows 10

Actual behavior

Height is oversized by exactly 8px consistently (taskbar is set to small icons).

How to reproduce

https://github.com/adi518/electron-frameless-maximize-test

Issue 2:
Electron version: 1.4.15

Operating system: Windows 10 Pro x64

Expected behavior

Maximized window should not oversize.

Actual behavior

Maximized window is oversized.

How to reproduce

Clone following repository:

https://github.com/tonyganch/electron-oversized-test.git

and follow the README.md.

Screenshots

Unmaximized frameless

Maximized frameless

Unmaximized with frame

Maximized with frame
Issue 1:
Request parsing does not verify validity of Host header, in particular it can contain spaces.

This leads to weird possibilities like:

package main

import (
"bufio"
"bytes"
"os"
"net/http"
)

func main() {
data := []byte("GET http:/1.1 HTTP/1.1\nHost: host.com/somethingelse HTTP\n\n")
r, err := http.ReadRequest(bufio.NewReader(bytes.NewReader(data)))
if err != nil {
panic(err)
}
r.WriteProxy(os.Stdout)
}

GET http://host.com/somethingelse HTTP/1.1 HTTP/1.1
Host: host.com/somethingelse HTTP
User-Agent: Go 1.1 package http

which I guess can trick some other HTTP implementation.

go version devel +a1fe3b5 Sat Jun 13 04:33:26 2015 +0000 linux/amd64

Issue 2:
by mail@ungerik.net:

Package net returns an internal error var when a connection was closed:

var errClosing = errors.New("use of closed network connection")

To check for that error, currently the error text has to be parsed. It would be much
better be able to check for a defined error type.
Issue 1:
just like sublime does

Issue 2:
Currently VS Code prevents opening a folder more than once which makes it impossible to work on a project in multiple windows (e.g. on multiple displays).

@bpasero @dbaeumer @egamma @alexandrudima please raise any obstacles and issues you might foresee with this request.

Issues found so far:

we use the workspace path as identifier to communicate back from debug target to debug host

we need to verify cross platform that there is no code causing issues when running over the same root folder (e.g. file watchers)

Please note: Initially I've created this feature request for a specific use case: enable debugging of multiple processes.

In the meantime, debugging of multiple processes has become possible without the need for opening a folder more than once (see #13426). But instead of closing this item (as no longer necessary), I've repurposed it by removing the specific debug use case.

For transparency you can find the original comment below:

Currently it is not possible to debug more than one process from a single VS Code project (= window)

because VS Code prevents opening a folder more than once.

The workaround is to open VS code on a subfolder within the original folder, which means to restructure the project (which is not desirable).

This feature request asks for lifting the constraint and allowing to open a project folder multiple times.
Issue 1:
Challenge Counting Cards has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36.

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

My code:

var count = 0;

function cc(card) {
// Only change code below this line
switch(card){
case 2:
case 3:
case 4:
case 5:
case 6:
count += 1;
break;
case 7:
case 8:
case 9:
count = 0;
break;
case 10:
case 'J':
case 'Q':
case 'K':
case 'A':
count -= 1;
break;
}

if(count == 5){
return "5 Bet";
}

else if (count === 0){
return "0 Hold";
}

else if (count == -5){
return "-5 Hold";
}

else{
return "-1 Hold";
}

// Only change code above this line
}

// Add/remove calls to test your function.
// Note: Only the last will display
cc(2); cc(3); cc(7); cc('K'); cc('A');

I don't understand how my code solves the problem. Yet it solves all the challenges required to pass the waypoint. I sort of gamed it. I don't believe my code is right. So this waypoint is probably bugged and needs to be reframed. What do you think, guys?

Issue 2:
Challenge Counting Cards has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.97 Safari/537.36.

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

My code:

var count = 0;

function cc(card) {
// Only change code below this line
var bet = '';
if(card<=6){
count ++;
} else if (!(card<=9)){
count --;
}
bet = count > 0? ' Bet':' Hold';
return count + bet;
// Only change code above this line
}

// Add/remove calls to test your function.
// Note: Only the last will display
cc(2); cc(3); cc(7); cc('K'); cc('A');

Ambiguity for what to do when card is 7, 8, or 9

From this, campers seem pretty evenly split between thinking that count should be reset to 0 or simply should not be changed.

The only test case is:

Which will pass in either case.

This means that you can accomplish the task regardless of how you interpret the instructions, but has been leading to some confusion for people asking for help.
Issue 1:
Bug report

What is the current behavior?

On webpack 5, The global array self["webpackChunkxxx"] may contain same chunk more times when using splitChunks. When using webpack 4, it runs ok.

If the current behavior is a bug, please provide the steps to reproduce.

or see https://github.com/zphhhhh/webpack-bug only well~

we use a global array like self["webpackChunkxxx"] to cache existing chunks, but it contains same chunk more times because parentChunkLoadingFunction(data);, see the output code:

var webpackJsonpCallback = (data) => {
// ...
if (runtime) runtime(__webpack_require__);
parentChunkLoadingFunction(data);
while (resolves.length) {
resolves.shift()();
}

// add entry modules from loaded chunk to deferred list
if (executeModules) deferredModules.push.apply(deferredModules, executeModules);

// run deferred modules when all chunks ready
return checkDeferredModules();
}

var chunkLoadingGlobal = self["webpackChunkwebpack_bug"] = self["webpackChunkwebpack_bug"] || [];
var parentChunkLoadingFunction = chunkLoadingGlobal.push.bind(chunkLoadingGlobal);
chunkLoadingGlobal.push = webpackJsonpCallback;

What is the expected behavior?

The global array self["webpackChunkxxx"] should contain same chunk just one time,

and when using webpack 4, it runs ok

You could change deps to webpack 4 in the Repo https://github.com/zphhhhh/webpack-bug , then it runs ok.

Other relevant information:

webpack version: latest, 5.10.0

Node.js version: v12.18.2

Operating System: macOS 10.15.6

Additional tools:

Issue 2:
I'm submitting a feature request

webpack 2.1.0-beta.15

Windows 10

Current behavior:

webpack --color uses webpack.config.js and packs my project displaying color on the terminal

webpack packs my project, ts-loader still shows color

webpack --colors shows help and usage information

along with error "Unknown argument: colors"

Expected/desired behavior:

webpack --color shows same

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your webpack configuration.

What is the expected behavior?

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

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5 | Dart | ...]
Issue 1:
Description of the problem

I have a .obj and .mtl which load textures from .tga files. This all seems to work / look fine in 3D modeling software, but when loaded with three.js (THREE.WebGLRenderer({ antialias: true })) some of the object's children, (specifically between the knees and the calves, but not, for example, the pockets and legs), seem to have a transparent jagged gap / empty triangles. (Tried turning on antialiasing, changing the overdraw value, turning off transparency, etc.)

Demo project and files: demo.zip

Potential problem area: "Forgive my ignorance, but code starting at line 306 in OBJLoader.js seems to imply a fixed side limit/requirement for all faces. The obj file in question shows some faces with more than 4 sides. For example see line 60067 in the obj file. There are more after. It's as if a cut tool has healed cut seams with complex faces." - http://stackoverflow.com/users/3311552/radio

Screenshots and more details (including discussion): http://stackoverflow.com/questions/41154498/threejs-some-material-texture-faces-triangles-not-rendering/41257937#41257937

Three.js version

r83

Dev

r82

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

Linux

Android

IOS

Issue 2:
Description of the problem

Loader document mentions

Base class for implementing loaders.

https://threejs.org/docs/#api/en/loaders/Loader

But with #15933, no loader will inherit Loader.

And Some loaders use Loader.Handlers. We may be able to move Handlers into LoaderUtils or somewhere. CTMLoader and LegacyJSONLoader call Loader.createMaterial()/.initMaterials(), we also may be able to move these methods somewhere.

We may be able to remove Loader.

Three.js version

Dev

r102

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
I'm interested in writing a typescript transform that rewrites all of the Import declarations to named identifiers and outputs an import map. The idea being that this could be the basis for a frontend dependency management tool that could handle semver resolution and deduping transitive dependencies. As far as I can tell there's no way to pass transforms via the Compiler API. Adding the ability to do so could potentially open up a wide range of output customizations.

Alternatively I could write a tool that does that before deno is called, but I'd prefer the above approach because aking multiple passes at the source code would be slower than making a single pass

Issue 2:
In regular TypeScript projects, within a .js file with type checking enabled via // @ts-check you can import types from other files within JSDoc comments. For example…

In a.js:

// @ts-check

/**
* Description for A.
* @param {import("./b.js").default} b The B.
*/
export default function a(b) {
return b;
}

In b.js:

// @ts-check

/**
* Description for B.
* @type {boolean}
*/
export default true;

Note that the parameter type is able to be imported and checked:

With exactly the same setup in a Deno project, the parameter type cannot be imported or checked:

This not working in Deno, with no open issues about it has really made the past few days trying to get an isomorphic codebase with a mixture of .ts, .tsx, and .js files a nightmare, because it's hard to tell if it's you or Deno that's doing the wrong thing. I think if this Deno bug were fixed I'd finally have a workable solution!