WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
SVC's and LinearSVC's (I didn't check other classifiers) decision_function in binary classification case returns values lower than 0 when predict returns 0, and >0 when predict returns 1.

So this part of code is wrong:

pred = estimators[k].predict(X)

score = _predict_binary(estimators[k], X)

scores[:, i] += score

scores[:, j] -= score

votes[pred == 0, i] += 1

votes[pred == 1, j] += 1

In SVM case we should substract score from scores[:,i] and add to scores[:,j]

Issue 2:
In multiclass.py, function predict_ovo(estimators, classes, X), it has:

scores[:, i] += score
scores[:, j] -= score

However, I think it should be:

scores[:, i] -= score

scores[:, j] += score

I think the idea here should be, when score > 0, the positive class increase its value in 'scores by' 'score', and the negative class decrease its value by 'score'. Because in case of tie, we use 'argmax(scores)' to determine the class, so the 'scores' should represent 'how certain we are about the class'. Therefore in the original code, 'i' should represent the positive class while 'j' represents the negative class.

Since from 'pred' and 'score' you find out: when score is positive, it has the label of '1' and otherwise '0', it means '1' is the positive class label and '0' is the negative class label.

However, in _fit_ovo_binary(estimator, X, y, i, j), with 'i' and 'j' being the same as used in predict_ovo(estimators, classes, X):

y[y == i] = 0
y[y == j] = 1

We know that 'i' < 'j'. Since 1 is the positive class label, then 'j' represent the positive class. i.e. for a classifier trained between 'i' and 'j' with 'i' < 'j', 'j' is the positive class.

Back to function predict_ovo(estimators, classes, X), we see from line:

scores[:, j] -= score

If score > 0, we decrease the value corresponding to class 'j', which is incorrect.

Hope it is not too verbose.
Issue 1:
by astrange:

Running the binary distribution of go 1.2 (or any of its RCs) on our FreeBSD 9.2 servers
immediately crashes. The same applies for go_bootstrap to build it from source.

go 1.1 runs fine.

# uname -a
FreeBSD yyy 9.2-RELEASE FreeBSD 9.2-RELEASE #6: Sun Oct 13 05:14:05 EDT 2013
xxx@yyy:/usr/obj/usr/src/sys/ZZZ amd64
# setenv GOROOT `pwd`
# sysctl hw.ncpu
hw.ncpu: 16
# gdb761 ./bin/go
GNU gdb (GDB) 7.6.1 [GDB v7.6.1 for FreeBSD]
Copyright (C) 2013 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-portbld-freebsd9.2".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>;...
Reading symbols from /usr/home/astrange/go/bin/go...done.
warning: Missing auto-load scripts referenced in section .debug_gdb_scripts
of file /usr/home/astrange/go/bin/go
Use `info auto-load python [REGEXP]' to list them.
(gdb) run
Starting program: /usr/home/astrange/go/./bin/go
[New LWP 100295]
[New Thread 801407400 (LWP 100295)]

Program received signal SIGBUS, Bus error.
[Switching to Thread 801407400 (LWP 100295)]
0x0000000000476dc7 in runtime.sysctl () at
/usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s:289
289 /usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s: No such file or directory.
(gdb) bt
#0 0x0000000000476dc7 in runtime.sysctl () at
/usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s:289
#1 0x0000000000463847 in getncpu () at /usr/local/go/src/pkg/runtime/os_freebsd.c:35
#2 0x0000000000463b5a in runtime.osinit () at
/usr/local/go/src/pkg/runtime/os_freebsd.c:127
#3 0x0000000000474b00 in _rt0_go () at /usr/local/go/src/pkg/runtime/asm_amd64.s:86
#4 0x0000000000000001 in ?? ()
#5 0x00007fffffffda78 in ?? ()
#6 0x0000000000000001 in ?? ()
#7 0x00007fffffffda78 in ?? ()
#8 0x0000000800b71800 in ?? () from /libexec/ld-elf.so.1
#9 0x0000000800b83000 in ?? ()
#10 0x0000000000000000 in ?? ()
(gdb)

Issue 2:
What steps will reproduce the problem?

6g bug.go

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

Expected: should compile OK, because r1 is a named return value.

Actual:
bug.go:7: r1 declared and not used

What is your $GOOS? $GOARCH?
darwin, amd64

Which revision are you using? (hg identify)
ed4677dbdbbc tip

Please provide any additional information below.

Attachments:

bug.go (162 bytes)
Issue 1:
We now can use kv-storage in chrome with:

import storageArea from 'std:kv-storage';

How about support similar API for deno_std?

It may looks like this, and imports the std module with the same version as the deno you installed.

import { serve } from 'deno_std:http/server';

And it's good to keep the same version between deno and deno_std modules.

Issue 2:
There is a Stage 1 TC39 proposal for "built in" browser modules to make a standard library for JavaScript. It is proposing a protected namespace of "std:" for the module specifiers. We should consider adopting this for potential standard built in modules.
Issue 1:
Electron version: N/A

Operating system: Mac or Windows

I don't know how I've only discovered these methods now 😄 but anyway...

Would an app get rejected by the MAS if it used app.setLoginItemSettings for example? The Mac App Store submission guide doesn't list it as a limitation but I would assume that it isn't MAS-friendly. Although, it would be great if it was compatible. I guess it depends on how it's implemented underneath (i.e. whether it reaches out of the sandbox or not, etc.)

cc @kevinsawicki

Related: Teamwork/node-auto-launch#43

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

12.0.2

What operating system are you using?

Windows

Operating System Version

Windows 10 Home Single Language 20H2 19042.867

What arch are you using?

ia32

Last Known Working Electron version

11.4.2

Expected Behavior

This script should print to all existing printers. The printers "Microsoft XPS Document Writer" and "Microsoft Print to PDF" should block the loop and ask for file name.

Actual Behavior

All prints will return success, but print will happen always only to print set as default in system.

Testcase Gist URL

https://gist.github.com/fc8b4a9fbf986965c51e8f92b8ddb39f

Good way to run the test is to set printer "Microsoft Print To PDF" as default printer.
Issue 1:
When rapidly erasing lines from a scrolling text box, the text that should be hidden due to it being outside of the box incorrectly appears.

To reproduce:

Open Flutter gallery

Select "Material"

Select "Text Fields"

Type many lines of short text in the "Life story" section (at least 6, the more the better)

Rapidly erase the lines. The first few hidden lines will appear as the text scrolls up.

Issue 2:
After several lines, including some blank lines, are inserted in a multiline TextField, press and hold the delete key. When the blank lines are deleted the viewport's text contents suddenly and temporarily appear above the text field.

See https://youtu.be/Nx0Go-4oPRg
Issue 1:
One is in impl String in libcollections/string.rs and has the signature fn from_str(string: &str) -> String.

The other is in impl FromStr for String in libstd/from_str.rs and has the signature fn from_str(s: &str) -> Option<String>. In fact, FromStr::from_str() actually calls String::from_str().

This situation probably came about because struct String exists in libcollections, which you could conceivably have without libstd in a freestanding environment, and the FromStr trait lives in libstd.

Conceivably, FromStr could be moved to a different crate, or a dependency on libstd could be introduced to libcollections.

Issue 2:
I noticed that the docs on Iterator differ depending on if you look a core::iter::Iterator or std::iter::Iterator. In the std version the declaration of the lifetime 'r in the methods is missing.

Im not sure if this is a bug or intended but its confusing if you look at the std version and wonder where lifetime 'r comes from.
Issue 1:
Tested with this code:

app.setPath("appData", './test');
app.setPath("userData", './test');

Electron version: 0.37.2

Operating system: Windows 10

Issue 2:
I'm using app.setPath to change the location where userData and cache are stored and it works (data is saved to the new location). The problem is that even due I set the paths before the ready event, the default location (%APPDATA%/productName) is still created.

To test this, I deleted the default path and added to the top of my main.js the following lines:

var fs = require('fs');
console.log('Exists?', fs.existsSync('C:/Users/eran.t/AppData/Roaming/foo'));

The output was Exists? true, which means the directory was created by some initialization code (it looks like it comes from here).

Is it possible to move the creation of the directories to when we actually need them (lazy creation), which will give the developer time to change them?

To circumvent the issue, one can simply delete the old path using fs.rmdir after changing the path to the new location, but it's not ideal.
Issue 1:
Should we drop support for OS X 10.6 Snow Leopard in Go 1.5? In Go 1.6?

It's 5 years old and not supported by Apple anymore.

It was the last OS X to support 32-bit machines, which is why we've kept it this long.

But there are problems with cmd/cgo on these old systems that we're just never going to fix (for example #8009 and #9967).

We should still keep darwin/386 until Apple stops running 32-bit binaries on 64-bit systems, since it's useful to be able to run 386 all.bash on OS X machines.

Issue 2:
As discussed in #9495, it might be time to end our support for OS X 10.6.

I'm trying to find Apple's policy on supporting older versions of OS X, but it appears they haven't published anything publicly. (Which seems outrageous to me, but whatever.)

The major concern, I believe, is that OS X 10.6 is the newest version of OS X that runs on pre-EFI macs (or something?). I think @robpike actually has one of these old machines.
Issue 1:
When I have a structure like this:

├─┬ node_modules
│ ├── backbone@1.2.1
│ ├─┬ backbone.marionette@2.4.1
│ │ └─┬ node_modules
│ │ ├── backbone@1.1.2
│ │ └── backbone.babysitter@0.1.7
│ └── backbone.babysitter@0.1.7
└── app.js

And load these modules in my app.js like this:

import Backbone from "backbone";
import Marionette from "backbone.marionette";
import "backbone.babysitter";

Now when I watch in dev tools at the sources tab, it show that the page has loaded 2 backbones and 2 backbone.babysitters. First the self defined versions, and secondly the dependencies of Marionette:

How can I ensure that webpack provides the self defined packages to Marionette?

Issue 2:
Bug report

What is the current behavior?

When I have one entry point for a JS file, everything is fine. However, as soon as I add another entry point including a JS file (e.g. LESS file entry points won't change anything), webpack creates a chunk file (like 123.bundle.js), even though I set the LimitChunkCountPlugin maxChunks to 1. There are no common modules in these 2 entry points and no async imports.

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

module.exports = {
mode: isProd ? 'production' : 'development',

devServer: {
publicPath: '/', // webpack bug, should default to '/'
contentBase: path.join(__dirname, 'build'),
},

entry: {
public: [ src('js/public.js'), src('less/public.less') ],
video: [ src('less/video.less'), src('js/player.js') ], // adding this js is causing 'public' to code split
application: src('less/application.less'),
},

output: {
path: path.resolve(__dirname, 'build/'),
filename: 'js/[name].bundle.js'
},

module: {
rules: [{
test: /\.js$/,
exclude: /node_modules/,
use: {
loader: 'babel-loader',
options: { presets: [ [ "@babel/preset-env", { "useBuiltIns": "usage", "corejs": 3, } ] ] }
}
},
{
test: /\.less$/,
use: [
MiniCssExtractPlugin.loader,
'css-loader',
{ loader: 'postcss-loader', options: { plugins: () => isProd ? [autoprefixer(), cssnano()] : [] } },
'less-loader'
]
},
{ test: /\.eot$/, loader: 'ignore-loader' }
]
},

plugins: [
new webpack.optimize.LimitChunkCountPlugin({
maxChunks: 1
}),

new MiniCssExtractPlugin({
filename: 'css/[name].bundle.css',
chunkFilename: '[name].css',
})
]
};

What is the expected behavior?

It's expected to not create any chunks since maxChunks is set to 1.

Also I would expect it to behave consistently, no matter if I have one or many entry points.

Other relevant information:

webpack version: 5.10.3

Node.js version: v12.15.0

Operating System: Win7
Issue 1:
When you look at modified files through Command+Shift+B you may have modified multiple files with the same leaf filename. For example, in a rails project you may have lib/my_lib.rb and config/initializers/my_lib.rb. In this case only one of them shows up in the list of modified files, in my case it was the config one.

Issue 2:
Open feedback Issues as me

We have tokens for the current user now, right? Pretty sure the feedback widget is using atom-bot because @probablycorey was getting it set up fast while other things were going on. Does it still need to use atom-bot?

User: @jbarnette

Atom Version: 0.43.0

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Atom/0.43.0 Safari/537.36
Issue 1:
I'm working on a PR, #32748, for a macro wraps ccall in more Julia-like syntax. An issue that's being discussed a lot is the accommodation of varargs of different types. I had the impression from @vtjnash that this was supported by foreigncall, but in retrospect, it's possible I misunderstood what he was saying.

I'm not in a position to implement this myself without first learning Scheme and LLVM. I should really do those things, but it may not be the most efficient way to get this change in.

Issue 2:
proposal: introduce va_list type for ccall / cfunction

usage:

ccall(:abc, Int, (A, B, va_list{(C,D,E)}), a,b,c,d,e)
# int abc(A, B, ...) {}
# {
# abc(a,b,c,d,e);
# }

va = va_list(c,d,e)
ccall(:abc, Int, (A, B, va_list), a, b, va)
ccall(:abc, Int, (A, B, va_list{()}), a, b, va)
# int abc(A, B, va_list) {}
# {
# va_list ap;
# va_start(ap, X);
# abc(A,B, ap);
# }

definitions:

immutable va_list{T<:Tuple}
# opaque
va_list(args...) = (T == () ? new(magic...) : error("cannot construct a typed va_list"))
end
va_list(values...) = va_list{()}(values...)

thoughts? improvements? should I make a pull request?
Issue 1:
Desire: make docs.flutter.io an excellent resource for learning how to use Flutter.

Challenge: for some domains (e.g. Input) that do not have their own library and cut across multiple libraries, we don't seem to have an easy way to author holistic docs. We'd like a "starting point" for a concept, one that is easy to identify when visiting docs.flutter.io.

Strawman proposal: something like a @category that can be used to link various classes and libraries. We also need a way to say "this page is the home page for a @category"

(I thought we had an issue open for this, but couldn't find it on either https://github.com/dart-lang/dartdoc/issues or flutter.io/issues)

Issue 2:
As we learn from UX studies, we noticed that we don't currently have an easy way for a developer to understand in which "area" they are looking at a concept. For example, if they are looking at the Padding class in the API docs, "where" are they? What kind of conceptual thing is this?

From a current Flutter developer: "More broadly, a tricky part of onboarding was simply familiarizing with the wide range of specialized widgets. "

(Note: our library organization in the framework is too coarse-grained to convey this grouping. For example, there are a lot of conceptual areas inside the widget library.)

Vision: a user looking at a thing in the API docs should easily understand in which group/AreaOfInterest/Layer it belongs, and then easily see other related things. For example, when looking at Padding, the user can easily see "This is part of the layout area of interest. Oh, these are the other helpful layout ideas."

Strawman: a way to annotate the thing (class/function/etc) to put it in a "doc grouping". Then, the dartdoc tool could be taught how to indicate which group the thing is in.
Issue 1:
Environment

Windows build number: [run "ver" at a command prompt]
Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version (if applicable):
0.2.1831.0

Any other software?

Steps to reproduce

Change "defaultProfile" to anything other than a valid profile

Expected behavior

Defaults to an existing profile or uses a default

Actual behavior

Nothing

Issue 2:
Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior

不能切换中文输入法
Issue 1:
I ran into an issue on our cluster running v1.0 with too many rules being specified for our node security group. Basically, security groups generated by Kubernetes were not cleaned up and their references in the node security group were also left behind. We hit an API limit (seems like it was ~50 rules defined on our node security group) which prevented any more load balancers from getting created.

I started looking into this and it seems the issue still exists on master. From a cluster I built off of master (about a week ago) I was able to reproduce this issue.

The controller manager logs look like this (filtered to aws.go and cleaned up):

aws.go:1688] EnsureTCPLoadBalancer(a4981847bb57811e5b53d0ed29d18a59, us-east-1, \u003cnil\u003e, [0xc2083b5720], [])\n","stream":"stderr","time":"2016-01-13T21:58:00.802283892Z"}
aws.go:1933] Removing rule for traffic from the load balancer (sg-294fcd50) to instance (sg-a1bb39d8)\n","stream":"stderr","time":"2016-01-13T21:58:01.348864017Z"}
aws.go:1960] Revoking ingress was not needed; concurrent change? groupId=sg-a1bb39d8\n","stream":"stderr","time":"2016-01-13T21:58:01.412753316Z"}
aws.go:1796] Loadbalancer a4981847bb57811e5b53d0ed29d18a59 has DNS name a4981847bb57811e5b53d0ed29d18a59-34625035.us-east-1.elb.amazonaws.com\n","stream":"stderr","time":"2016-01-13T21:58:01.487755376Z"}
aws.go:1980] Load balancer already deleted: a492de23eb57811e5b53d0ed29d18a59\n","stream":"stderr","time":"2016-01-13T21:59:43.076849385Z"}
aws.go:1933] Removing rule for traffic from the load balancer (sg-294fcd50) to instance (sg-a1bb39d8)\n","stream":"stderr","time":"2016-01-13T21:59:44.271066717Z"}
aws.go:1960] Revoking ingress was not needed; concurrent change? groupId=sg-a1bb39d8\n","stream":"stderr","time":"2016-01-13T21:59:44.31932039Z"}
aws.go:2034] Ignoring DependencyViolation while deleting load-balancer security group (sg-294fcd50), assuming because LB is in process of deleting\n","stream":"stderr","time":"2016-01-13T21:59:44.505570103Z"}
aws.go:2053] Waiting for load-balancer to delete so we can delete security groups: a4981847bb57811e5b53d0ed29d18a59\n","stream":"stderr","time":"2016-01-13T21:59:44.505877497Z"}

The controller will loop until it hits the timeout and then bail out without having cleaned up the security group. I think the initial issue comes from Revoking ingress was not needed; concurrent change? groupId=sg-a1bb39d8. I verified through AWS console and that ingress rule was never removed. With that ingress rule still present a dependency on the security group still exists and the delete fails to happen (causing the dependency violation).

@justinsb fyi.

I'm looking into what I believe to be the culprit now and will push a PR if I find a solution.

Edit:

I have a strong suspicion that the culprit is isEqualIPPermission. It looks as if the AWS api is returning IpPermission.IpRanges while when we define the IpPermission we don't explicitly specify any IpRanges. It seems it would be reasonable to not do this check when removing ingress rules?

Issue 2:
ref #23174
Issue 1:
I know there's other projects who added RTL support to bootstrap but these are two different projects now so if a bug fix or a new feature is added in bootstrap, it's wouldn't show on the RTL project.

I had an idea, not sure if it'll work but if so, LTR and RTL can be supported from the same project without maintaining two different copies of things.

Add these variables in variables.less

@Left: left;

@right: right;

In every other .less file, whenever have use of left/right (such as margin-left) use @left/@right instead.

Compile and you'll get the same output as today.

Set @Left: right; and @right: left; and compile again. That should give RTL support.

Would that work?

Issue 2:
Would be great to have support for right-to-left languages.
Issue 1:
For some reason, numpy.remainder function is not working as defined for the following specific case:

np.remainder(.60,.04) = 0.04

0.60-np.floor(0.60/0.04)*0.04 = 0.00 (Function as defined)

This seems to be the only case for which the definition does not match the function output.

Issue 2:
This seems to be a regression in 11.0 or in master (note the values are exactly representable):

>>> np.remainder(3, 2.5)
0.49999999999999989
>>> np.__version__
'1.12.0.dev0+58263eb'

Compare to:

>>> np.remainder(3, 2.5)
0.5
>>> np.__version__
'1.10.4'
Issue 1:
Currently only the Gregorian calendar is available!

new Intl.DateTimeFormat([locales[, options]])

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/DateTimeFormat

Issue 2:
As seen in #1952 / #1636 ICU needs to be added in Deno build.

Switching this flag to true maybe: https://github.com/denoland/deno/blob/master/.gn#L50 ?

ref: https://v8.dev/docs/i18n
Issue 1:
Test allowed me to pass even though I had a typo on paragraph tag.

Challenge Name

Issue Description

Browser Information

Browser Name, Version:

Operating System:

Mobile, Desktop, or Tablet:

Your Code

// If relevant, paste all of your challenge code in here

Screenshot

Issue 2:
Challenge Waypoint: Set the Font Family of an Element has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0.

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

A camper went to the chat talking about enumerating paragraphs with this code:

<style>
.red-text {
color: red;
}

p {
font-size: 16px;
}
p { font-family: monospace}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<p1 class="red-text">Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>

<p2> Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>

The code passed the test. The problem is that he opened the paragraph as p1 but closed it as p, so the browser creates an empty paragraph to balance the tags and the final structure is something like this:

<p1>
Kitty ipsum...
<p></p>
<p2>
Purr...
<p></p>
</p2>
</p1>

In the end, there are valid paragraphs (those created by the browser) with the Monospace font.

Although the objective of this waypoint is styling the paragraphs, which it's done correctly, I think it might be important to check for cases like this too.

Possible solution: add a test for checking if the paragraphs are empty.