WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Symfony version(s) affected: 4.1.5

Description

Adding <env name="SYMFONY_DEPRECATIONS_HELPER" value="disabled" /> to phpunit.xml.dist has no affect.

How to reproduce

Install the symfony skeleteon

composer create-project symfony/skeleton:4.1.* bug_app
cd bug_app
composer require --dev "symfony/phpunit-bridge:*"
php bin/phpunit

Add <env name="SYMFONY_DEPRECATIONS_HELPER" value="disabled" /> to phpunit.xml.dist as per the configuration docs.

Create a new DeprecatedTest: https://github.com/leevigraham/symonfy-phpunit-bridge/blob/master/tests/DeprecatedTest.php

<?php

namespace App\Tests;

use PHPUnit\Framework\TestCase;

class DeprecatedTest extends TestCase
{
public function testDeprecatedCode()
{
@trigger_error('This "Foo" method is deprecated.', E_USER_DEPRECATED);
@trigger_error('The second argument of the "Bar" method is deprecated.', E_USER_DEPRECATED);
}
}

Run php bin/phpunit again. Deprecation notices are shown.

Example Repo: https://github.com/leevigraham/symonfy-phpunit-bridge

Additional context

Screenshot of issue:

Running SYMFONY_DEPRECATIONS_HELPER=disabled php bin/phpunit produces expected output:

// @nicolas-grekas

Issue 2:
Symfony version(s) affected: all ?

Description

phpunit-bridge ignores the value "disabled" for the environment variable SYMFONY_DEPRECATIONS_HELPER when set in phpunit.xml. The value "weak" works as expected.

Also, setting this environment variable in the shell works as expected.

Tested with phpunit-bridge-4.1.4

How to reproduce

set in phpunit.xml

<php>
<env name="SYMFONY_DEPRECATIONS_HELPER" value="disabled" />
</php>

and run a test which will cause a deprecation warning.
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):

1.4

Environment:

Ubuntu Wily (15)

Cloud provider or hardware configuration:

local pc

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

Kernel (e.g. uname -a):

4.2.0-30-generic #35-Ubuntu SMP

Install tools:

http://kubernetes.io/docs/getting-started-guides/kubeadm/

Others:

What happened:

at the step

kubeadm init

Blocks at "waiting for the control plane to become ready" forever

What you expected to happen:

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

Anything else do we need to know:

I am following the instruction of http://kubernetes.io/docs/getting-started-guides/kubeadm/. Block for at least one day.

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

reconstructVolume calls plugin's ConstructVolumeSpec to create a volume spec and use this volume spec in plugin's NewMounter to mount the volume.

Problem is none of the plugins set fs type in ConstructVolumeSpec. As a result:

for plugins that has fsType as a string pointer (e.g. azure_dd), kubelet will crash

for other volumes, if the volume is formatted as xfs, it cannot be mounted.

@kubernetes/sig-storage @jingxu97

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 1:
Bug report

Describe the bug

When I try update production project with 100+ pages and 10+ languages to Next.js 9.0.4 and move all my routes from next-routes to built-in dynamic routes found some issue on client side routing.

In multi language sites in most cases we need to show locale code in the start of paths but with dynamic routes it cant be done right now, this will lead to an warning in console:https://github.com/zeit/next.js/blob/f41f630d19a1f87265fd77ae884b003d85915847/packages/next-server/lib/router/router.ts#L317

So if we have dynamic route like /post/[id] and try to build link component with href="/post/[id]?locale=de" and as="/de/post/${id}" we have warning in console after click on that link.

As I understand this issue was appears because route created from href does not match regex created from as, but I dont quite understand how to fix it for dynamic routes.

Need clear way to build multi language sites without using next-routes.

To Reproduce

Create dynamic route /post/[id].

Create <Link /> component with href="/post/[id]?locale=de" and as="/de/post/${id}".

Click on it and you will see warning in the console.

System information

Next.js 9.0.4

Issue 2:
Previously a thread on Spectrum.

I need to support these routes:

/posts
/posts/1
/posts/2

As mentioned in the dynamic routing RFC, a workaround can be implemented like this:

// pages/posts/[id].js
export default () => <h1>Post no. {router.query.id}</h1>

// pages/posts.js
export { default } from './posts/[id]'

However, as these are two entrypoints, it creates two bundles, so when I navigate to /posts and then to /posts/1, I am waiting for a new bundle to load.

Ideally, there would be a way to tell Next.js that all the post-related routes should be handled by a single page component. We might need to wait for non-filesystem-based routing: #8241.
Issue 1:
To reproduce:

Go to Available Updates.

Make sure you have packages that need updates.

Hit "Update All".

The Update button within the package cards will change to "☁️ Updating..." with the stripes running right to left. Leave this page open and come back 5 minutes later. It will still say updating. But if you reload Atom, the packages will be updated.

This is in the latest version. (0.208.0)

Issue 2:
Just noticed this as of Atom 0.208.0-c06d62e:

Click the Update button in an available update package card in the Updates panel

Wait a sufficiently long time so you know it should've been installed (~5 mins with an SSD, for example)

Package card will still say "Updating..."

Click another panel in Settings View

Close Settings View

Reopen Settings View

Click the Updates panel

Assuming there was only 1 update, it will report that all packages are up-to-date.

Can anyone in @atom/feedback reproduce with the same version?
Issue 1:
Electron Info

"electron-devtools-installer": "^1.1.2",
"electron-packager": "^7.0.2",
"electron-prebuilt": "^1.2.3",
"electron-rebuild": "^1.1.4",

Operating system: Mac 10.11.2

Problem:

The following code snipped runs fine in development but does not execute when packaged.

const exec = require('child_process').exec;
exec('echo $NODEPATH', (function(error, stdout, stderr){
this.log_info("hehe")
if (error) {
console.error(`exec error: ${error}`);
return;
}
console.log(`stdout: ${stdout}`);
console.log(`stderr: ${stderr}`);
}).bind(this));

Any ideas why I can't execute system commands in Electron when the app is packaged?

Issue 2:
Electron version: 0.30 - 1.0.1

Operating system: OSX Yosemite

I having a problem PATH using Electron in production. The problem I have is with "pdfinfo" (poppler). Poppler was installed with homebrew and it is in the PATH (I can execute "pdfinfo" from any folder in my terminal).

When starting my Electron app from the command line, I have no problem at all with the PATH. This will work fine, and "pdfinfo" will be found and work correctly:

./node_modules/electron-prebuilt/dist/Electron.app/Contents/MacOS/Electron ./

It's only when I start my app in production (opening the Electron.app app icon like any normal app). When spawning "pdfinfo" in this scenario, i get this:

stderr stdout: /bin/sh: pfdinfo: command not found

Notice the "/bin/sh" path.

While looking for an explanation for this problem I stumbled upon this thread: https://discuss.atom.io/t/every-spawn-task-throws-enoent-when-electron-app-packaged-for-distribution/18692

Read where "erikmellum" states:

When in production, spawn does not use your regular PATH variable to locate executables. It will basically use a PATH that includes OS bin folders (such as /usr/bin).

Which kinda seems to be related to my problem. Is this true? How can I get around this? Is there a way to tell production Electron to use the normal system PATH in production?
Issue 1:
Migrated issue, originally created by Praveen Arimbrathodiyil (@pravi)

File "/usr/lib/python2.7/dist-packages/gnukhataserver/rpc_reports.py", line 134, in xmlrpc_getLedger

grandTotal =float(balanceRow["total_CrBal"]) + float(balanceRow["curbal"])

File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/result.py", line 332, in _key_fallback

expression._string_or_unprintable(key))

sqlalchemy.exc.NoSuchColumnError: "Could not locate column in row for column 'total_CrBal'"

org.apache.xmlrpc.XmlRpcException: error

I'm packaging gnukhata (gnukhata.org) for debian and hit this error. Krishnakant Mane (core developer of gnukhata) said everything is working fine with sqlalchemy 0.7.x. Debian sid has sqlalchemy 0.9.6. He also mentioned you have promised this would be fixed in the next release. Hopefully we can get a patch sooner so it debian and ubuntu packages can be updated. Currently we are forced to create a different repository and ship 0.7.x version of sqlalchemy.

Issue 2:
Migrated issue, originally created by Ronny Pfannschmidt (@RonnyPfannschmidt)

oracle stored procedures cant be invoked by a select, instead one must call them in a anonymous block

a way to either access those via the dbapi.callproc method or generating the fit sql would be nice

currently i work around by compiling to a block on oracle and a select on postgresql

i didnt examine other databases
Issue 1:
I'm trying to combine the two-explicit-vendor-trunk example with code splitting. But cannot make it to work.

I have two pages (NOT real pages, it's an SPA using react and react-router):

/ : needs only vendor.js

/d3 : needs both vendor.js and d3.js

The goal is: when visiting /, only app.js and vendor.js are loaded. When the user navigates to /d3, d3.js is loaded as needed. Here is how I try:

webpack config:

entry: {
vendor: [
'react',
'react-dom',
'react-router',
...
],
d3: [
'd3',
],
app: [
'./src/js/index',
],
},
plugins: [
new webpack.optimize.CommonsChunkPlugin({
name: 'vendor',
minChunks: Infinity,
}),
new webpack.optimize.CommonsChunkPlugin({
name: 'd3',
minChunks: Infinity,
// not sure about the async option here, but without it error occurs
async: true,
}),
...
],

Router.jsx (I'm using react-router):

export default (
<Router history={createBrowserHistory()}>
...
<Route path="d3" getComponent={(location, callback) => {
require.ensure([], (require) => {
callback(null, require('./pages/D3'));
});
}} />
...
</Router>
);

This config doesn't work as expected since the d3.js bundle is generated but completely ignored by other bundles. And d3.js is also duplicated in chunk 1.1.js. So how can I make this to work? I need this configuration because d3 is too large and slows down initial loading on home page a lot. Furthermore I need to do long-term caching on both vendor.js and d3.js so both must be split out as vendor chunks.

Issue 2:
I'm submitting a bug report

Webpack version:

1.13.2

Please tell us about your environment:

OSX

Current behavior:

Errors in the browser console appear duplicated, regardless of the loader:

Expected/desired behavior:

The error message should not be printed twice.

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.

npm i -g create-react-app
create-react-app mystuff --scripts-version 0.5.1
cd mystuff
npm start

Then make a syntax error in src/App.js or src/App.css and inspect browser output.

You can find the config here.

What is the expected behavior?

The error message should not be printed twice.

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

Seeing it printed twice is confusing and annoying.

Browser: all

Language: all

(I file this in Webpack repo because the error string is passed to WDS already in this form.)
Issue 1:
Decide what to do with each of these

deprecate from_csv / change to be exactly like read_csv -> #17812

from_dict

from_records (see #8161)

from_items (#18529)

This is just a suggestion: DataFrame constructor already supports the things that from_dict and from_records do (from_items is not supported by the constructor, but maybe it should be?). Also from_csv does the same thing as pd.read_csv.

Since There should be one-- and preferably only one --obvious way to do it. maybe these methods should be removed/deprecated?

I know that this would cause backward incompatibility, so maybe just a deprecation warning could be displayed until a future major release that could remove them.

Issue 2:
Problem description

I was looking into how to convert dataframes to numpy arrays so that both column dtypes and names would be retained, preferably in an efficient way so that memory is not duplicated while doing this. In some way, I would like to have a view on internal data already stored by dataframes as a numpy array. I am good with all datatypes already used in dataframe, and names there.

The issue is that both as_matrix and values convert dtypes of all values. And to_records does not create a simple numpy array.

I have found two potential StackOverflow answers:

https://stackoverflow.com/questions/40554179/how-to-keep-column-names-when-converting-from-pandas-to-numpy

https://stackoverflow.com/questions/13187778/convert-pandas-dataframe-to-numpy-array-preserving-index

But it seems to me that all those solutions copy data around through intermediate data structures, and then just store them into a new numpy array.

So I would ask for a way to get data as it is, without any conversions of dtypes, as a numpy array.

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.5.2.final.0
python-bits: 64
OS: Linux
OS-release: 4.9.27-moby
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: None
LOCALE: None.None

pandas: 0.20.1

pytest: None

pip: 9.0.1

setuptools: 20.7.0

Cython: 0.25.2

numpy: 1.12.1

scipy: 0.19.0

xarray: None

IPython: None

sphinx: None

patsy: None

dateutil: 2.6.0

pytz: 2017.2

blosc: None

bottleneck: None

tables: None

numexpr: None

feather: None

matplotlib: None

openpyxl: None

xlrd: None

xlwt: None

xlsxwriter: None

lxml: None

bs4: None

html5lib: None

sqlalchemy: None

pymysql: None

psycopg2: None

jinja2: None

s3fs: None

pandas_gbq: None

pandas_datareader: None
Issue 1:
ISSUE TYPE

Bug Report and regression, this works fine in 2.1.0

ANSIBLE VERSION

ansible 2.1.1.0

STEPS TO REPRODUCE

Create a directory layout like this:

├── ansible.cfg
├── host_vars
│ └── localhost
├── inventory
│ └── hosts
└── playbooks
└── playbook.yml

Execute ansible-playbook playbooks/playbook.yml from top level directory and try to use a variable that is defined in host_vars/localhost

A testcase can be found here: https://github.com/alvaroaleman/ansible-testcase-group_vars

Issue 2:
ISSUE TYPE

Bug Report

ANSIBLE VERSION

ansible --version
ansible 2.1.1.0
config file = /stuff/ansible.cfg
configured module search path = ['./library']

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

Just upgraded to ansible 2.1.1 and noticed I could not ssh to any of my nodes anymore. Realized the ssh command that is being used to connect is not including the -o 'IdentityFile= or the -o User= flags. We set the ansible_user and ansible_ssh_private_key_file variables in group_vars for the various environments that each group of hosts is from (typically each environment has a different private_key).

Was able to get around this by setting the options on the command line.

STEPS TO REPRODUCE

Move ansible_ssh_private_key_file and ansible_user variables to a group_var for a host (mine are not in all.yml, not sure if that matters) and try to run a playbook without specifying the values on the command line.

ansible-playbook some_play -vvvv

EXPECTED RESULTS

This is the result when I add -e ansible_user=ubuntu -e ansible_ssh_private_key_file=~/.ssh/dev.pem to the ansible-playbook command

<10.64.0.218> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=360s -o StrictHostKeyChecking=no -o 'IdentityFile="/home/tkinz/.ssh/dev.pem"' -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r 10.64.0.218 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-cjlqfgwiukyslnxpcwrfediwgqapkuwh; LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python'"'"'"'"'"'"'"'"' && sleep 0'"'"''

ACTUAL RESULTS

<10.64.0.218> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=360s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/root/.ansible/cp/ansible-ssh-%h-%p-%r 10.64.0.218 '/bin/sh -c '"'"'sudo -H -S -n -u root /bin/sh -c '"'"'"'"'"'"'"'"'echo BECOME-SUCCESS-aefstgpfveqloqbmzzweiirdnbxrrtda; LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python'"'"'"'"'"'"'"'"' && sleep 0'"'"''
Issue 1:
Feature Request

In the docs, it says that:

Does not support const enums because those require type information to compile.

I don't believe that this is true. Babel should be able to transpile const enums into objects, which will achieve the same functionality as typescript, through different transpiled output.

Given this code:

const enum Direction { Left, Right, Down, Up }
console.log(Direction.Down)

tsc would compile this to:

console.log(2)

I propose that Babel compiles the enum to:

const Direction = {
Left: 0,
Right: 1,
Down: 2,
Up: 3
}
console.log(Direction.Down)

Which functions the same as the tsc output.

A minifier like terser/uglify is able to transpile that output ☝️ to the same as the tsc output.

Issue 2:
I'm currently targeting IE9+ in my project. I have to use spec.protoToAssign to get classes working. The babelHelpers.inherits helper uses __proto__, which requires the helpers to be transformed. So this forces me to either use inline helpers (a lot of duplication) or to use babel.buildExternalHelpers, which requires me to do a transform with a different set of options.

In the case of babelHelpers.inherits, and possibly even spec.protoToAssign, would it make sense to use Object.setPrototypeOf instead of __proto__ and defer the functionality to a pollyfill?
Issue 1:
I have run into a strange problem using DistributedDataParallel. I have solved it - but this looks like a bug to me.

The error I am getting is:

... in spawnv_passfds
False, False, None)
ValueError: bad value(s) in fds_to_keep

This occurs during the spawn() call from pytorch-lightning. The model I am using works in all other modes, and an identical model, trainer setup works in ddp, too.

After some hair pulling, I found the problem. During the construction of the new model, and before creating trainer, etc, I store the .data property of a Parameter:

self.class_p = nn.Parameter(torch.Tensor(np.ones(self.data.num_classes) * np.log(1.0)), requires_grad=True)
self.class_p_t = self.class_p.data # this is the offending line

I do NOT actually do anything with self.class_p_t - I assigned it in anticipation of logging these values to monitor progress of self learning curriculum learning class weights.

If the assignment above is present, I get the above failure. Without it, things work fine.

If this is something you expect, I'd appreciate knowing why - if it's a bug, thought you'd like to know.

For the record:Ubuntu 19.10, python 3.7.5, pytorch 1.4, venv, pytorch-lightning 0.7.1

Note that this is a fully up to date ubuntu ...

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar

Issue 2:
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
import torch

fig = plt.figure()
plt.plot([1,2])
fig.savefig('test.pdf')

Running this simple python code will have error *** Error in 'python': free(): invalid pointer: 0x00007f5ba8129ac0 *** (omit the backtrace output). It breaks at fig.savefig('test.pdf').

OS Ubuntu 16.04.2 LTS, Python version 2.7.12, PyTorch version 0.1.12_2, Matplotlib version 2.0.2
Issue 1:
I'm trying to run rollup with --compat flag, however I'm getting following error:

❯ deno run --compat --unstable dist/es/rollup.js
Check file:///Users/biwanczuk/dev/rollup/dist/es/rollup.js
error: TS2502 [ERROR]: 'thisArg' is referenced directly or indirectly in its own type annotation.
bind<T>(this: T, thisArg: ThisParameterType<T>): OmitThisParameter<T>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at asset:///lib.es5.d.ts:350:22

I'm not entirely sure what's the problem here, are our declarations out of date?

CC @kitsonk

Issue 2:
$ deno --version
deno 1.6.3 (release, x86_64-apple-darwin)
v8 8.8.294
typescript 4.1.3

I was attempting to import rollup in Deno and getting the following error:

$ deno run rollup.ts
Check file:///Users/craigmorten/git/cmorten/rollup/rollup.ts
error: TS2502
[ERROR]: 'thisArg' is referenced directly or indirectly in its own type annotation.
bind<T>(this: T, thisArg: ThisParameterType<T>): OmitThisParameter<T>;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at asset:///lib.es5.d.ts:350:22

Which appears to be a type definitions issue with the CallableFunction bind method definition.

REF: https://github.com/denoland/deno/blob/master/cli/dts/lib.es5.d.ts#L350

Reproduce with:

// mod.ts
import "https://unpkg.com/rollup@2.36.1/dist/rollup.browser.js";

And running deno run mod.ts.

Please advise! I'm unclear if the issue is the use of .bind(...) somewhere in the rollup code, or whether the ThisParameterType<T> type needs a fix?
Issue 1:
Some of of cuDNN's algorithms are non-deterministic, even with the seed set to X, for example

typedef enum
{
CUDNN_CONVOLUTION_BWD_FILTER_ALGO_0 = 0, // non-deterministic
CUDNN_CONVOLUTION_BWD_FILTER_ALGO_3 = 3, // non-deterministic, algo0 with workspace

typedef enum
{
CUDNN_CONVOLUTION_BWD_DATA_ALGO_0 = 0, // non-deterministic

(This list is probably non-exhaustive)

PyTorch currently provides no way for the user to select which specific algorithms to use in cuDNN. However, this is fine, since PyTorch was designed to be more high-level and abstract than some of the other frameworks.

Perhaps instead of exposing the entire cuDNN algorithm choices, a boolean variable specifying non-determinism vs determinism should be added? This would be along the lines of the current torch.backends.cudnn.enabled option.

Currently, users have to resort to CPU or disabling cuDNN for reproducibility. Some optimizers do work deterministically (at least for us) on the GPU (e.g. SGD, Adam), but Adadelta and RMSprop do not.

Issue 2:
It is totally possible to implement deterministic training with lua torch avoiding some cunn modules and cudnn algos. cutorch has atomicAdd in THIndexTensor which shouldn't pose a problem.

PyTorch should implement:

ordered parallel data loading similar to torchnet https://github.com/torchnet/torchnet/blob/master/dataset/paralleldatasetiterator.lua#L53

cudnn should allow user set deterministic mode somehow