WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Noticing a security vulnerability [CVE-2021-3807] when scanning the "npm" package with JFrog Xray as below:

The package cli-table3 and one of its dependency ansi-regex need to be bumped up in order to fix this issue.

Full Dependency Tree:

test-app@1.0.0
└─┬ npm@8.3.1
└─┬ cli-table3@0.6.0
└─┬ string-width@4.2.2
└─┬ strip-ansi@6.0.0
└── ansi-regex@5.0.0

This vulnerability is reported with a "High Severity".

The vulnerability is fixed with ansi-regex@6.0.1

Please advise.

Thanks in advance.

(Also see: nodejs/node#41039)

Issue 2:
Our team found an issue of npm inconsistent install while migrating from lerna to npm@7 workspaces. It looks like inability to install proper dependencies if there is previous state of node_modules when checking out between branches. The result differs if previous node_modules is present or not.

Current Behavior:

The dependencies have incorrect versions after install.

Expected Behavior:

The dependencies have correct version even after checkout between branches.

Steps To Reproduce:

Here's git bundle (I've put it to archive because of github limitations).

npm-7-migration-bug.bundle.zip

There're two commits in branch narrow1. They display broken transition we experience. To test if dependencies are broken or not I check version of axios. It should be 0.20 on first commit and 0.21.1 on second. It version is 0.20.0 on second commit, then we have a bug.

git checkout narrow1

git checkout HEAD~

npm start # here we create initial state for node_modules

head ./node_modules/axios/package.json # version = 0.20.0, correct

git checkout -

npm start # here we trying to actualize state of node_modules

head ./node_modules/axios/package.json # version = 0.20.0, incorrect, must be = 0.21.1

rm -rf ./node_modules

npm start # running from scratch yields correct state, version = 0.21.1

Environment:

OS is GNU/Linux, but we have devs with the same issue on Windows machines.

In repro I'm using node@12 and npm@7 for broken commit.
Issue 1:
Uncaught Error: EACCES, open '/home/rhocassiopeiae/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'

Atom Version: 0.158.0

System: linux 3.13.0-43-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At fs.js:75

Error: EACCES, open '/home/rhocassiopeiae/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'
at Error (native)

Issue 2:
Steps for reproduce:

Open atom

Open folder with source code

Select any source file from trreview

rigth click and duplicate file

crash

I am using Fedora 21 and atom version is 0.168.0

Here the output:

[fabio@ironhide ~]$ /usr/bin/atom: line 92: 10917 Segmentation fault (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$DOT_ATOM_DIR/nohup.out" 2>&1

[10917:0108/113744:ERROR:browser_main_loop.cc(163)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

libGL error: MESA-LOADER: could not create udev device for fd 12

libGL error: MESA-LOADER: could not create udev device for fd 12

ATTENTION: default value of option force_s3tc_enable overridden by environment.

App load time: 278ms

[10970:0108/113745:INFO:renderer_main.cc(207)] Renderer process started

[10917:0108/113746:INFO:CONSOLE(92)] "Download the React DevTools for a better development experience: http://fb.me/react-devtools", source: /usr/share/atom/resources/app/node_modules/react-atom-fork/lib/React.js (92)

[10917:0108/113747:INFO:CONSOLE(64)] "Window load time: 1968ms", source: file:///usr/share/atom/resources/app/static/index.js (64)

Crash dump id: 9cee5385-744a-4d2f-b907-388b21ff66d5
Issue 1:
import seaborn as sns;sns.set()
import matplotlib.pyplot as plt
penguins = sns.load_dataset("penguins")
# sns.displot(data=penguins, x="flipper_length_mm",label='policy_0',kind="hist")
sns.histplot(data=penguins, x="flipper_length_mm",label='policy_1')
plt.legend()
plt.savefig("test.png")

By running belowing codes, I got a figure like:

It seems to repeat the legends, could you fixed it soon? It will be pretty nice of you!

Issue 2:
Consider data points that describe:

different animal species

each specie lives across different countries

a population for each specie in each country

The current plotting histograms considers each bin (animal specie) as a full collection of data and each hue (country) as separate histograms.

Since each specie is decoupled one would like to do something like this:

sns.histplot(population, x='specie', hue='country', stat='probability')

however this will not decouple the species from each other. What would be nice if one could normalize each specie individually across the countries, aka:

sns.histplot(population, x='specie', hue='country', stat='probability', bin_norm=True, common_norm=True)

which normalizes across hues for each bin plot. This would make all bin sizes equal height of 1, but the hue for each will show the probability distribution for the specie population and clearly indicate which specie has a tendency in each country.

I agree this isn't the regular histogram, but perhaps it would fit seaborn anyways? :)
Issue 1:
Fallout of #21191. -C opt-level=2 sets CodegenOptions::opt_level but -O doesn't, and -C lto path only looks at that. Due to the fallback from LTO path, -O -C lto is currently same to -C opt-level=0 -C lto (!).

Issue 2:
-O seems to function like an alias for -C opt-level=2, but -O does not enable certain LTO LLVM optimizations (inlining?), whereas -C opt-level=2 does. This seems like a mistake.

The problem is this code in librustc_trans/back/lto.rs:

let opt = sess.opts.cg.opt_level.unwrap_or(0) as libc::c_uint;

let builder = llvm::LLVMPassManagerBuilderCreate();
llvm::LLVMPassManagerBuilderSetOptLevel(builder, opt);
llvm::LLVMPassManagerBuilderPopulateLTOPassManager(builder, pm,
/* Internalize = */ False,
/* RunInliner = */ True);
llvm::LLVMPassManagerBuilderDispose(builder);

sess.opts.cg.opt_level is the -C opt-level setting, which is None with -O.

test.rs:

pub fn test() {}

output:

$ rustc test.rs --crate-type staticlib --emit llvm-ir -C lto -O
$ ls -l test.ll
-rw-rw-r-- 1 rprichard rprichard 36920440 Feb 19 00:25 test.ll
$ rustc test.rs --crate-type staticlib --emit llvm-ir -C lto -C opt-level=2
$ ls -l test.ll
-rw-rw-r-- 1 rprichard rprichard 1312070 Feb 19 00:25 test.ll

I think we should base the LLVM optimization level on sess.opts.optimize. (Maybe it ought to use write::get_llvm_opt_level?)
Issue 1:
The control height classes listed on http://getbootstrap.com/css/#forms-control-sizes do not match the classes that actually exists in bootstrap.css and bootstrap.min.css.

.input-lg is shown in the documentation,but .input-large is configured in the css. Likewise, .input-sm is shown in the documentation, but .input-small is configured.

Issue 2:
To increase/decrease the size of form controls, you can add the classes input-lg or input-sm (at least according to the website [http://getbootstrap.com/css/#forms] - which is the most consistent solution). In the css code, however, the classes are called input-large and input-small.
Issue 1:
I was looking for a way to set a remember me cookie programmatically from inside a service. So I am not coming through a standard form login. Unfortunately all the remember me services are private and so I can not access them. Is there another way to solve this problem? I am using Symfony version 2.4.

Issue 2:
Just bringing attention to this particular issue since all the @ mentions are getting no response there. See FriendsOfSymfony/FOSUserBundle#747. If there is a better way to bring stuff like this to attention, then it would be good to know.

Quoting @stof:

The remember me services are private so they are removed from the container when optimizing it. This means that the has checks in the LoginManager will return false even when the remember me is activated for the firewall.
Issue 1:
VSCode Version: 1.2.0

OS Version: Win10

Steps to Reproduce:

Create a new file e.g. test.php

Copy this:

<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<title>Test</title>
</head>
<body>

<?php $someVar = 'hello'; ?>

<?php $someVar = 'hello';

?>

</body>
</html>

Set the language mode to PHP

Select Theme: Dark+ (default dark)

You will notice now, that there is some miss matching between a one line of code or when you expand it.

I'm not sure if this just a problem with the theme, how ever the problem appeared when I installed to update to version 1.2 today.

Issue 2:
VSCode Version: 1.2.1

OS Version: Windows 7

Commands within one single line do not appear to have the correct highlight.

Example:

<?php foreach (array() as $array) { ?>
<?php } ?>
Issue 1:
Druid indexing needs to be revisited to improve indexing performance and functional capability. Currently, v8 segments are created by IndexMerger and converted to v9. We should be able to build v9 segments directly.

Issue 2:
The indexing code is getting old and the method of updating the storage format is essentially amounting to writing in an old version and converting up multiple times. This is less than optimal and not a good sign for future maintenance.

We need to look at the indexing code and fixor it up to make it betterz.
Issue 1:
I had a deps file that looks like:

export * as React from "https://dev.jspm.io/react";
export * as ReactDOM from "https://dev.jspm.io/react-dom";

and then the file consuming it...

import { React, ReactDOM } from "./deps.js";
const rootEl = document.getElementById("root");
ReactDOM.render(<div>hello, world</div>, rootEl);

I then ran deno bundle mod.js app.bundle.js. The outputted bundle was missing the react and react-dom dependencies entirely. Changing my deps file to the below fixed the issue:

export { default as React } from "https://dev.jspm.io/react";
export { default as ReactDOM } from "https://dev.jspm.io/react-dom";

I realize they don't mean the exact same thing but for React and ReactDOM, it does. I'm not sure if I'm missing something here. Thanks!

Issue 2:
Hi,

in my tsconfig.json:

"compilerOptions": {
"lib": ["esnext", "dom", "deno.ns"]
}

...and with Deno 0.35.0:

error TS2488: Type 'Headers' must have a '[Symbol.iterator]()' method that returns an iterator.

► https://deno.land/std/http/io.ts:135:24

135 for (const [k, v] of result) {
~~~~~~

error TS2488: Type 'Headers' must have a '[Symbol.iterator]()' method that returns an iterator.

► https://deno.land/std/http/io.ts:206:30

206 for (const [key, value] of trailers) {
~~~~~~~~

error TS2488: Type 'Headers' must have a '[Symbol.iterator]()' method that returns an iterator.

► https://deno.land/std/http/io.ts:260:30

260 for (const [key, value] of headers) {
Issue 1:
I'd like to read audio file by using a sox utility directly. Currently I can do it as:

signal = torch.from_numpy(np.frombuffer(subprocess.check_output(['sox', '-V0', audio_path, '-b', '16', '-e', 'signed', '--endian', 'little', '-r', str(sample_rate), '-c', '1', '-t', 'raw', '-'], dtype = np.int16))

Is there a way to reinterpret a torch byte tensor (or python's bytearray(...)) as another type without invoking first NumPy? (or a generic numpy.view(dtype) functionality) If not, I think it'd be quite useful (mainly for integral types, but also maybe for some integer bit-tricks on float32 tensors, which can hopefully be fused by jit)

Also reported in https://discuss.pytorch.org/t/reinterpret-pytorch-array-as-a-different-dtype/24256

This probably can also be helpful for conversions between complex <-> pair or real/imag.

cc @mruberry @rgommers

Issue 2:
We support many built-in functions (Python 2, Python 3), but not all of them. Some of these need some more discussion (i.e. what about builtins that exist in Python 2 but not 3 and vice versa), but many can be done piecemeal and should be straightforward to implement. When you implement a builtin please check to see if it is a magic method.

To do

abs()

all()

any()

bin()

bool()

bytearray()

chr()

dict()

divmod()

enumerate()

float()

getattr()

hash()

hex()

int()

isinstance()

len()

list()

long() (long is deprecated in py3 builtins)

max()

min()

oct()

ord()

pow()

print()

range()

reversed()

round()

set()

slice()

sorted() (separate issue, implemented for lists)

str()

sum()

type()

Maybe to do later (when things like first class modules are in, or if we ever have something like iterators)

callable()

tuple()

complex()

delattr()

filter()

format()

frozenset()

globals()

hasattr()

issubclass()

iter()

locals()

next()

object()

property()

reduce()

setattr()

repr()

super()

vars()

zip()

Probably won't do

__import__()

basestring()

classmethod()

cmp()

compile()

dir()

eval()

execfile()

file()

help()

id()

input()

map()

memoryview()

open()

raw_input()

reload()

staticmethod()

unichr()

unicode()

xrange()

cc @suo
Issue 1:
Coming from atom/atom#2177, it seems atom retrieves pre-built libraries for atom-shell, which I'm guessing were built in Ubuntu.

Trying to build atom-shell from source fails (please see details in linked issue).

Issue 2:
We should provide a script to build libchromiumcontent and atom-shell from source code, and make use of OpenSUSE Build Service to compile and provide Linux packages.
Issue 1:
In 4.1.1, non-sharding-table SQL do not supported nested subquery,

I'm sorry for the bad reading experience. I translated the English with Google and made some adjustments.

this nested subquery has nothing to do with the table I want to sharing.

For example, if the table to be sharding is "log" ,

and a SQL String not contain "log",

like

select

*

from (select

...

from

(select

*

from user

union

select

*

from account

)t left join........

) temp where......

when I run the SQL , I will get the error message "Can not find owner from table",

related code: ProjectionsContextEngine.find(), line 197, throw new IllegalStateException("Can not find owner from table.")

This SQL does not contain the table to be sharding. Why is it parsed?

Similar to "SQLString.contains("log")?doSharding():doDefault()",

Does it have such a function? I didn't find it.

I think the SQL that are not sharding do not need to be processed by sharding-jdbc.

Issue 2:
Which version of Sharding-Jdbc do you using?（您使用的Sharding-Jdbc版本为？）

Sharding-Jdbc版本：2.0.3

Expected behavior （您预期的结果是）

希望可以集成到springboot2.0

Actual behavior （实际运行的结果是）

报错：java.lang.ClassNotFoundException: org.springframework.boot.bind.RelaxedPropertyResolver

原因springboot2.0中RelaxedPropertyResolver不再可用了
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When trying to rehydrate markup in IE11 'Argument is not optional' error is thrown. It happens only if component has dangerouslySetInnerHTML prop.

Example

https://jsfiddle.net/oy9awLtq/

What is the expected behavior?

No error should be thrown

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React version: 16

Browser: IE11

Issue 2:
Do you want to request a feature or report a bug?

bug

What is the current behavior?

React interactivity lost, React crash?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/ebsrpraL/).

Run with react-dom.development.js in IE11, not sure exactly what the exact repo steps are the fix I've attempted for IE11 was to simply pass an empty string.

var normalizeHTML = function (parent, html) {
if (!testDocument) {
testDocument = document.implementation.createHTMLDocument(""); // fix for IE11 here
}
var testElement = parent.namespaceURI === HTML_NAMESPACE ? testDocument.createElement(parent.tagName) : testDocument.createElementNS(parent.namespaceURI, parent.tagName);
testElement.innerHTML = html;
return testElement.innerHTML;
};
}

Source

react/src/renderers/dom/fiber/ReactDOMFiberComponent.js

Lines 133 to 146
in
e932ad6

var normalizeHTML = function(parent: Element, html: string) {

if (!testDocument) {

testDocument = document.implementation.createHTMLDocument();

}

var testElement = parent.namespaceURI === HTML_NAMESPACE

? testDocument.createElement(parent.tagName)

: testDocument.createElementNS(

(parent.namespaceURI: any),

parent.tagName,

);

testElement.innerHTML = html;

return testElement.innerHTML;

};

}

MDN docs here.

What is the expected behavior?

Well, that React does not crash in dev mode and that interactively continues to work.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

react@16.0.0 IE11
Issue 1:
This was fun to debug.

In [1]: import pandas as pd

In [2]: 0 in pd.Int64Index([0, 0, 1])
Out[2]: True

In [3]: 0 in pd.Int64Index([0, 1, 0])
Out[3]: True

In [4]: 0 in pd.Int64Index([0, 0, -1])
Out[4]: True

In [5]: pd.Timestamp(0) in pd.DatetimeIndex([0, 1, -1])
Out[5]: True

In [6]: pd.Timestamp(0) in pd.DatetimeIndex([0, 1, 0])
Out[6]: False # BAD

In [7]: pd.Timestamp(0) in pd.DatetimeIndex([0, 0, 1])
Out[7]: True

In [8]: pd.Timestamp(0) in pd.DatetimeIndex([0, 0, -1])
Out[8]: False # BAD

TimedeltaIndex is also broken.

The problem is in DatetimeIndexOpsMixin.__contains__, which checks the type of idx.get_loc(key) to determine whether the key was found in the index. If the index contains duplicate entries and is not monotonic increasing (for some reason, monotonic decreasing doesn't cut it), get_loc eventually falls back to Int64Engine._maybe_get_bool_indexer, which returns an ndarray of bools if the key is duplicated. Since the original __contains__ method is looking for scalars or slices, it reports that the duplicated entry is not present.

Issue 2:
Code Sample

result = pd.Series(1., pd.date_range('20170101','20181231',freq='D')).resample('B').last().to_period()

print result.index[0]
# Period('2016-12-30', 'B')

pd.Period('20170101', freq='B')
# Period('2017-01-02', 'B')

Problem description

when i have daily data that spans weekends (e.g., 1/1/2017 which is a Sunday) and try to get the last available value for a BusinessDay, the data falls back to the Friday period. This is inconsistent with the timestamp of Sunday belonging to the Monday BusinessDay period (e.g., pd.Period('20170101', 'B') goes to 1/2/2017).

Expected Output

I would expect that the result.index[0] above would return Period('2017-01-02', 'B')

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.12.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-36-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: None.None

pandas: 0.19.2

nose: 1.3.7

pip: 9.0.1

setuptools: 34.3.0

Cython: 0.24

numpy: 1.12.0

scipy: 0.18.1

statsmodels: 0.6.1

xarray: 0.9.1

IPython: 4.1.1

sphinx: None

patsy: 0.4.1

dateutil: 2.6.0

pytz: 2016.10

blosc: None

bottleneck: 1.2.0

tables: None

numexpr: 2.5

matplotlib: 1.5.1

openpyxl: 2.3.3

xlrd: 0.9.4

xlwt: 1.0.0

xlsxwriter: None

lxml: 3.5.0

bs4: 4.5.1

html5lib: None

httplib2: 0.9.2

apiclient: None

sqlalchemy: 1.0.12

pymysql: None

psycopg2: None

jinja2: 2.8

boto: 2.45.0

pandas_datareader: None
Issue 1:
Issue Type:

Feature Idea

Component Name:

core

Ansible Version:

$ ansible --version

ansible 2.0.0.2

config file = /home/damjan/sys-ops/ansible.cfg

configured module search path = Default w/o overrides

Ansible Configuration:

ask_vault_pass = true
become = true

Summary:

the ansible.cfg file has become=true and ask_vault_pass=true but in rare situations I need to run ansible without the vault or sudo requirements. It would need to have something like --no-become and --no-ask-vault-pass or --become=false to be able to revert the defaults from the config file.

Issue 2:
ISSUE TYPE

Bug Report

Feature Idea

COMPONENT NAME

lib/ansible/playbook/play_context.py

lib/ansible/playbook/become.py

ANSIBLE VERSION

devel

SUMMARY

PlayContext defined its own become attributes: https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/play_context.py#L194

but we have a Become mixin which does that: https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/become.py#L33

Is there a reason for this or should we switch PlayContext to use the mixin?

Note: the answer could be that play_context is actually not like the other objects in playbook/ at all. (In which case... we should probably be moving to separate it more rather than integrating it tighter with an abstraction that's an imperfect fit.)

STEPS TO REPRODUCE

Look at play_context.py and become.py to see that they're defining the same attributes but not

EXPECTED RESULTS

No code duplication; logical structure

ACTUAL RESULTS
Issue 1:
ISSUE TYPE

Feature Idea

ANSIBLE VERSION

ansible 2.1.0.0
config file = /home/soar/ansible2/ansible.cfg
configured module search path = Default w/o overrides

SUMMARY

When I build new project with Ansible, I place all sensitive information to vault-encrypted files. I follow KISS principles and this files are included as group_vars (or host_vars). All works perfectly. So I have files like:

├── ansible.cfg
├── inventory
│ └── projectname
│ ├── group_vars
│ │ ├── hosts.yml
│ │ ├── somegroup.yml
│ │ └── somegroup-encrypted.yml
│ └── projectname
├── playbooks
│ ├── deploy-something.yml
│ └── test.yml
└── roles
├── somerole
│ ├── defaults
│ │ └── main.yml

But recently I started to use automated tests for my Ansible projects. So after commiting to repository, I run something like:

ansible-playbook -vvv --syntax-check playbooks/test.yml
ansible-playbook -vvv --connection=local --sudo playbooks/test.yml

And check output. I want to run this tests without my encrypted data, and all variables are defined with default values in rolename/defaults/main.yml. But... I get only ERROR! Decryption failed.

I think, there should be some command-line switch, to run playbook without decryption for test purposes.

I know, that I can use vars_files or -e command-line switch, but then I should type them on every run. And I think encrypted files should be places in inventory with appropriate hosts, and not in playbooks directory.

And, of course, please don't forget about #14721

Issue 2:
In some cases diff users might want to use the same play with different access levels, being able to change vault failure to decrypt to a warning or something else allows for this.