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

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

Steps to reproduce

I just noticed that multi-monitor support has been removed in 0.15.2. Please add this back.

Expected behavior

Actual behavior

Screenshots

Issue 2:
Environment

Windows build number: [Version 10.0.18362.387]
PowerToys version: 0.12.0.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

I have 2 custom layouts. One for the left monitor, one for the right.

I move the mouse to the left monitor and press [WIN] ~

I choose Custom, and the left layout option.

I click Apply

I move the mouse to the right monitor and press [WIN] ~

I choose Custom, and the right layout option.

I click Apply.

The right monitor layout is applied to all monitors. I have tried also just moving the settings window before hitting apply but that doesn't work either.

I can also use the main settings window, drag to the monitor, change the layout, and the same behavior happens, both monitors are updated.

Expected behavior

Expected to be able to have a separate layout on different monitors.

Actual behavior

Identical layout applied to all monitors.

Screenshots
Issue 1:
Currently the ListItem supports a prop called initiallyOpen and an event onNestedListToggle. It would be great if it could simply accept open as a prop which overrides the internal state.

Issue 2:
I am using material-ui in a project with react router. And I want to control which ListItems show there nestedLists. This is unfortunately not possible because i can't control wether a listItem is "open" or not.

I know there is a Prop to control if its initially open. But I want to change it from my parent component after initial render, which currently does not seem to be possible. I would suggest an "open" props instead of a "initiallyOpen" one.
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

Current Behavior

Bundled dependencies do not export executables when packing.

Expected Behavior

npm pack output should include scripts under .bin to launch any executables provided by the bundled depdency.

Steps To Reproduce

Install any dependency that exposes an executable, e.g. lws.

Include this dependency in bundledDependencies

npm pack

The resulting artifact includes the bundledDependency under node_modules, but does not create a .bin directory at all, and so the depdency's executable(s) will not be available.

Environment

Win10 20H2

Node: 14.15.4

npm: 7.4.0

Issue 2:
Current Behavior:

Bundled dependencies do not export executables when packing.

Expected Behavior:

npm pack output should include scripts under .bin to launch any executables provided by the bundled depdency.

Steps To Reproduce:

Install any dependency that exposes an executable, e.g. lws.

Include this dependency in bundledDependencies

npm pack

The resulting artifact includes the bundledDependency under node_modules, but does not create a .bin directory at all, and so the depdency's executable(s) will not be available.

Environment:

WIn10 20H2

Node: 14.15.4

npm: 6.14.10

Notes

I see from #1689 that bundledDependencies does not currently do special handling of the dep's package.json, such as looking at the files field. It's probably impractical / undesirable to process the whole bin field from package.json during pack, but at least it would make sense to check the existing node_modules/.bin for scripts that exactly match the package name and include those in the output.
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:

Issue 2:
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

kubeadm master join

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

FEATURE REQUEST

A convenient command such as kubeadm config or kubeadm show to return the command for a node to join the cluster i.e. kubeadm join --token <token> <master-ip>.

(I am happy to work on this myself and contribute)
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

I am reading the docs of the website.
In this page : https://dubbo.incubator.apache.org/zh-cn/docs/user/preface/requirements.html
There is a typo.
> “ 此时需要一个服务注册中心，动态的注册和发现服务，使服务的位置透明。”

it should be(“的” ——> "地"):
> “ 此时需要一个服务注册中心，动态地注册和发现服务，使服务的位置透明。”

Issue 2:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.2

Operating System version: win7

Java version: Java1.8

Steps to reproduce this issue

ExtensionLoader类中loadClass(Map<String, Class> extensionClasses, java.net.URL resourceURL, Class clazz, String name)方法

....

String[] names = NAME_SEPARATOR.split(name);

if (ArrayUtils.isNotEmpty(names)) {

cacheActivateClass(clazz, names[0]);

for (String n : names) {

cacheName(clazz, n);

saveInExtensionClass(extensionClasses, clazz, name);

}

}

....

Expected Result

最后一行代码saveInExtensionClass(extensionClasses, clazz, name);中的name应该改成n？

由于dubbo中的name都是一个（没有逗号分隔），所以不会发生问题

例如：
Issue 1:
Bug Report

Current Behavior

Set up a TypeScript repository with Babel and plugin-transform-typescript. Add this code:

Input Code

export enum Foo
{
a, b, c, d
}

export namespace Foo
{
export function bar()
{
return "bar"
}
}

Expected behavior/code

It should compile just fine. In TypeScript this just works: Playground Link

Actual behavior

The compiler throws a very misguiding error:

./src/Foo.ts
SyntaxError: Foo.ts: Namespace not marked type-only declare. Non-declarative namespaces are only supported experimentally in Babel. To enable and review caveats see: https://babeljs.io/docs/en/babel-plugin-transform-typescript
4 | }
5 |
> 6 | export namespace Foo
| ^^^
7 | {
8 | export function bar()
9 | {

Changing the order of enum and namespace declarations results in this error:

./src/Foo.ts
TypeError: Foo.ts: Duplicate declaration "Foo"
8 | }
9 |
> 10 | export enum Foo
| ^^^
11 | {
12 | a, b, c, d
13 | }

Babel Configuration

The repository was created with:

yarn create react-app --template=typescript
yarn add @babel/plugin-transform-typescript react-app-rewired customize-cra

Then add this to config-overrides.js:

const {
override,
addExternalBabelPlugin
} = require("customize-cra");

module.exports = override(
addBabelPlugin([
"@babel/plugin-transform-typescript",
{ allowNamespaces: true }
])
);

Environment

Babel version(s): v7.9.0

Node/npm version: v13.13.0

OS: elementary

Monorepo: no

How you are using Babel: via react-scripts, webpack

Walkaround

If you need to keep the exact structure in your project, you can do this:

export enum Foo_
{
a, b, c, d
}

export type Foo = Foo_

export namespace Foo
{
export const a = Foo_.a
export const b = Foo_.b
export const c = Foo_.c
export const d = Foo_.d
export function bar()
{
return "bar"
}
}

(We can't use a destructuring assignment because of #11461)

Proposed Solution

At least the misleading errors should be fixed as soon as possible. Thinking that the plugin loaded incorrectly caused me a lot of pain and several wasted hours. However, the feature itself is important too and I'd really love to see it implemented.

Issue 2:
@TheLarkInn asked, and it seems like a discussion worth having.

Leaving it off by default would lead to people being more likely to get errors in things like Node by default, but it would potentially make the workflow easier for people using Webpack, since it's usually easier to add additional plugins than it is to remove them, since opting out first is more verbose, so people could do

{
presets: ['@babel/env'],
env: {
test: {
plugins: ['@babel/transform-modules-commonjs'],
}
}
}

which is a lot nicer than

{
presets: [['@babel/env', { modules: false }]],
env: {
test: {
plugins: ['@babel/transform-modules-commonjs'],
}
}
}

or even

{
presets: [['@babel/env', { modules: false }]],
env: {
test: {
presets: ['@babel/env'],
}
}
}

at least in my view?
Issue 1:
This happened after I switched branches in git, and had folder open, which was unavailable in branch that I switched to.

Atom was open in background, GitHub app was on top.

Issue 2:
Right-click in the tree view to rename a file (which is currently open in the editor) and the file gets copied/duplicated to the new name while the old file remains open. They are not symlinked as editing one does not produce changes in the other after closing/reopening.

Renaming a directory (containing a file open in the editor) has similar effect. The old directory remains, including any files currently open in the editor. Everything else is moved to the new directory, including copies of open files.

Atom 0.170 on OS X 10.10. Has been happening for a while, and happens even when all plugins are disabled. I tested by opening my Desktop folder in Atom, creating a folder and some files, and renaming the folder while with some files open.
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When importing an undefined named import, it doesn't produce any warning or error in build, but fail at runtime. I am using babel-preset-env, with modules: false.

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

a.js

import { getDef, getUndef } from './b.js';

getDef(); // works
getUndef(); // throws

b.js

export const getDef = () => 'defined';

What is the expected behavior?

I would expect webpack to produce an error, because the named import doesn't exist.

If this is a feature request, what is motivation or use case for changing the behavior?

Got bit by this many times, and I think it should be a build check instead of a runtime check.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

OS: MacOSX 10.13.2

Node: 8.10.3

Webpack: 3.10.0

babel/preset-env: 7.0.0-beta.34

Thanks in advance!

Issue 2:
I'm submitting a feature request

Webpack version:

2.1.0-beta.21

Please tell us about your environment:

Linux

Current behavior:

When I try to import a named import, it fails silently if the name import does not exist. I wish webpack would fail loudly when it cannot find the import at build time

For example:

// file1.js
const var1 = 'var1'
export { var1 }

and

// file2.js
import { var2 } from './file1'
// at this point, var2 is undefined at runtime because it was never exported from file1.js

Desired behavior:

Instead, I want it to fail at build time. Is there a webpack option or some other technique I can use to catch this error sooner?

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

This will catch typos at build time, and prevent a lot of headaches caused by undefined imports.

Browser: [all ]

Language: [ES6/7]
Issue 1:
In http://getbootstrap.com/customize/#less-variables, the nav bar on the left eases navigation in the page. However, when there is too much content and the height of the screen is too low, it becomes impossible to see the content at the end of the nav bar.

Issue 2:
On the Components page of the Bootstrap docs, the sidebar becomes too tall for the viewport when scrollspy causes the sidebar subheadings to show.

The sidebar cannot be scrolled or manipulated to show content below the viewport.

See here: http://getbootstrap.com/components/#glyphicons
Issue 1:
sum(skipmissing(x)) is reasonably fast, but since #27651 a naive implementation of sum is even faster (up to 5×). This is particularly clear when the input array does contain missing values, probably because the naive sum uses masked SIMD instructions while skipmissing relies on branching (and the presence of missing values kills prediction).

I haven't investigated this deeply, but IIUC sum(skipmissing(x)) dispatches to mapfoldl, which uses the iteration protocol to go over the input. This means we lose the benefit of @inbounds and of @simd. Maybe something like #27384 would help with @inbounds at least?

function mysum(X)
s = zero(eltype(X))
@inbounds @simd for x in X
if x !== missing
s += x
end
end
s
end

# With Vector{Int}
X1 = rand(Int, 10_000_000);
X2 = Vector{Union{Missing,Int}}(X1);
X3 = ifelse.(rand(length(X2)) .< 0.9, X2, missing);

julia> @btime mysum(X1);
5.594 ms (1 allocation: 16 bytes)

julia> @btime mysum(X2);
5.791 ms (1 allocation: 16 bytes)

julia> @btime mysum(X3);
5.681 ms (1 allocation: 16 bytes)

julia> @btime sum(skipmissing(X1));
7.316 ms (2 allocations: 32 bytes)

julia> @btime sum(skipmissing(X2));
18.175 ms (2 allocations: 32 bytes)

julia> @btime sum(skipmissing(X3));
28.240 ms (2 allocations: 32 bytes)

# With Vector{Float64}
Y1 = rand(Float64, 10_000_000);
Y2 = Vector{Union{Missing,Float64}}(Y1);
Y3 = ifelse.(rand(length(Y2)) .< 0.9, Y2, missing);

julia> @btime mysum(Y1);
5.860 ms (1 allocation: 16 bytes)

julia> @btime mysum(Y2);
13.849 ms (1 allocation: 16 bytes)

julia> @btime mysum(Y3);
17.428 ms (1 allocation: 16 bytes)

julia> @btime sum(skipmissing(Y1));
13.816 ms (2 allocations: 32 bytes)

julia> @btime sum(skipmissing(Y2));
18.254 ms (2 allocations: 32 bytes)

julia> @btime sum(skipmissing(Y3));
28.430 ms (2 allocations: 32 bytes)

Issue 2:
Unfortunately, the impressive speed boosts that were made for Julia on Linux seem to have been lost in translation. On the same machine, I get ~0.6 secs on Linux vs. ~6 on Windows.
Issue 1:
Version 0.10.10

In previous versions formatting was adding space in anonymous function like this:

function() {}

Became:

function () {}

Now it works vice versa. Is there any way to configure it?

Issue 2:
Hi

I was wondering if there's any option to change the JavaScript code formatting rules used?

I'm a big fan of code formatting but when VS code formats my code to insert spaces after my anonymous function keywords then it can really upset people that I work with who have OCD.

And thanks for the continued efforts guys!
Issue 1:
julia> a = rpad("\u2003", 5)
"  "

julia> length(a) #4 in 0.4-dev, 5 in 0.3.7
4

julia> map(x->convert(Uint32, x), collect(a)) #0.4-dev has one fewer space
4-element Array{UInt32,1}:
0x00002003
0x00000020
0x00000020
0x00000020

help?> rpad
search: rpad repeated macroexpand isdirpath tryparse normpath repmat repeat replace workspace realpath redisplay AbstractSparseArray

Base.rpad(string, n, p)

Make a string at least "n" characters long by padding on the
right with copies of "p".

help?> charwidth
search: charwidth

Base.charwidth(c)

Gives the number of columns needed to print a character.

Issue 2:
Julia compiles OpenBLAS to libopenblas.so. This may be a problem for calling libraries that link to a system libopenblas.so, because the runtime linker may substitute Julia's version instead. The problem is that Julia's version is compiled with a 64-bit interface, which is not the default, and so if an external library calls it expecting a 32-bit interface, a crash may result.

We encountered what appears to have been this problem n @alanedelman's machine (julia.mit.edu). He recently started experiencing crashes in PyPlot.plot that, with the help of valgrind, I tracked down to apparently:

==17855== Use of uninitialised value of size 8
==17855== at 0xA8B6890: dgemm_beta_NEHALEM (in /home/edelman/julia/usr/lib/libopenblas.so)
==17855== by 0xA082D72: dgemm_nn (in /home/edelman/julia/usr/lib/libopenblas.so)
==17855== by 0x9F558C8: cblas_dgemm (in /home/edelman/julia/usr/lib/libopenblas.so)
==17855== by 0x16430CA5: dotblas_matrixproduct (_dotblas.c:809)
==17855== by 0x14BAB5D4: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)

Apparently, Matplotlib is calling OpenBLAS (via NumPy: _dotblas.c is a NumPy file) with the 32-bit interface, but is getting linked at runtime into Julia's openblas library, which is compiled with a 64-bit interface. Recompiling Julia and openblas with USE_BLAS64=0 worked around the problem, but it would be better to avoid the conflict.

Can we just rename our libopenblas.so file to avoid any possible conflict in the runtime linker?
Issue 1:
Related to #10528, but for np.dtype instead of np.array

import numpy as np
import ctypes
class PackedStructure(ctypes.Structure):
_pack_ = 1
_fields_ = [
('a', ctypes.c_uint8),
('b', ctypes.c_uint16)
]
actual = np.dtype(PackedStructure)
expected = np.dtype([
('a', np.uint8),
('b', np.uint16)
])

Issue 2:
class Foo(ctypes.Structure):
_fields_ = [('one', ctypes.c_uint8), ('two', ctypes.c_uint32)]
_pack_ = 2

>>> ctypes.sizeof(Foo()) # packed to alignment 2
6
>>> np.dtype(Foo).itemsize # default alignment incorrectly used
8

Fix should be fairly straightforward by changing:

numpy/numpy/core/_dtype_ctypes.py

Lines 35 to 46
in
44810f0

def _from_ctypes_structure(t):

# TODO: gh-10533, gh-10532

fields = []

for item in t._fields_:

if len(item) > 2:

raise TypeError(

"ctypes bitfields have no dtype equivalent")

fname, ftyp = item

fields.append((fname, dtype_from_ctypes_type(ftyp)))

# by default, ctypes structs are aligned

return np.dtype(fields, align=True)
Issue 1:
I couldn't find an existing tracking issue for this feature, please mark as a duplicate if I've missed anything.

This is something that would be required for jspm support in Babel CLI, where we'd want to use dynamic import() to reference plugins directly, and so would need some kind of promise support in the configuration.

Currently an asynchronous configuration gives the following error:

Error: You appear to be using an async configuration, which your current version of Babel does not support. We may add support for this in the future, but if you're on the most recent version of @babel/core and still seeing this error, then you'll need to synchronously return your config.

And an asynchronous plugin gives the following error:

You appear to be using an async plugin, which your current version of Babel
does not support.If you're using a published plugin, you may need to upgrade your @babel/core version.

Either or both of these features would be really great to support.

The async plugin case effectively provides parity with top-level await workflows in future too. Happy to discuss further as well.

Issue 2:
Today I came across what looks like a bug.

If you try to destructure arguments to a function that's within an array it silently fails instead of giving a SyntaxError.

The failing code looks like:

const doesntCompileProperly = [
...args => console.log(args)
];

and compiles to:

var doesntCompileProperly = [].concat(_toConsumableArray(function (args) {
return console.log(args);
}));

Here's a link to a few other examples in the Babel repl: babeljs.io repl link
Issue 1:
Describe the workflow you want to enable

Currently the GeneralizedLinearRegressor module only allows a scalar alpha regularization parameter to be used for all parameters. However, sometimes the modeler would like to input different amounts of regularization on certain parameters, either for interpretation or some other prior knowledge.

Describe your proposed solution

The alpha parameter can take either a scalar value or an iterable of the same length as the number of parameters in the input matrix.

The optimization algorithm will then flow as normal with the line below in glm.py naturally doing a vector to vector dot product instead of a scalar vector multiplication.

coef_scaled = alpha * coef[offset:]

I believe the alpha parameter passed to scipy.optimize.minimize in the args parameter isn't being used anywhere.

For QA, I plan to output regression results in R or statsmodels for the same data and model specs

Describe alternatives you've considered, if relevant

No response

Additional context

I modified this as part of my dayjob and also doing this as part of my programming work at my university. This is my first PR so please let me know if I'm missing anything.

Issue 2:
Description

This is a feature request in allow flexibility in elastic net, which allows the user to apply separate penalties to each coefficient of the L1 term. The default value of this penalty factor is 1, meaning the regular elastic net behavior. If the penalty factor of a feature is Zero, it means it's not penalized at all, and that the user wants this feature to be always there in the model.

This feature is very useful in Bioinformatics and systems biology (that's why it is in Stanford's R package glmnet). With this feature, the user can run feature selection on a set of genes while making sure some genes stay in the system and not penalized (because of prior knowledge that they are involvid the system).

Here is glmnet documentation explaining the penalty factor. Mainly, it's controlling the selection weight on the lasso term:

https://web.stanford.edu/~hastie/glmnet/glmnet_alpha.html#lin

This feature is used in several papers, I've implemented in it in one of mine in scikit-learn. I've requests from other biologists to use this method in Python without having to recompile scikit-learn. I can do a pull request with this feature.

Papers using this feature:

Altarawy, Doaa, Fatma-Elzahraa Eid, and Lenwood S. Heath. "PEAK: Integrating Curated and Noisy Prior Knowledge in Gene Regulatory Network Inference." Journal of Computational Biology 24.9 (2017): 863-873.

Greenfield, Alex, Christoph Hafemeister, and Richard Bonneau. "Robust data-driven incorporation of prior knowledge into the inference of dynamic regulatory networks." Bioinformatics 29.8 (2013): 1060-1067.

Friedman, Jerome, Trevor Hastie, and Rob Tibshirani. "Regularization paths for generalized linear models via coordinate descent." Journal of statistical software 33.1 (2010): 1.