WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hi, currently scipy.integrate.ode() returns an error message indicating that the function returned a tuple when it returns an array of non-matching length. The true error message is buried above the raised ValueError here, which is misleading, as the function is not returning a tuple.

Could a better error message be surfaced?

Reproducing code example:

import scipy.integrate

def f(t, y):
return [y[0]]

scipy.integrate.ode(f).set_initial_value([1, 1]).integrate(1)

Error message:

unexpected array size: new_size=2, got array with arr_size=1
rv_cb_arr is NULL
Call-back cb_f_in_dvode__user__routines failed.
Traceback (most recent call last):
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 408, in integrate
self.f_params, self.jac_params)
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 865, in run
y1, t, istate = self.runner(*args)
SystemError: <fortran object> returned NULL without setting an error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "test.py", line 8, in <module>
scipy.integrate.ode(f).set_initial_value([1, 1]).integrate(1)
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 411, in integrate
raise ValueError('Function to integrate must not return a tuple.')
ValueError: Function to integrate must not return a tuple.

Scipy/Numpy/Python version information:

0.19.1 1.13.1 sys.version_info(major=3, minor=6, micro=1, releaselevel='final', serial=0)

Issue 2:
Hi, currently scipy.integrate.ode() returns an error message indicating that the function returned a tuple when it returns an array of non-matching length. The true error message is buried above the raised ValueError here, which is misleading, as the function is not returning a tuple.

Could a better error message be surfaced?

Reproducing code example:

import scipy.integrate

def f(t, y):
return [y[0]]

scipy.integrate.ode(f).set_initial_value([1, 1]).integrate(1)

Error message:

unexpected array size: new_size=2, got array with arr_size=1
rv_cb_arr is NULL
Call-back cb_f_in_dvode__user__routines failed.
Traceback (most recent call last):
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 408, in integrate
self.f_params, self.jac_params)
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 865, in run
y1, t, istate = self.runner(*args)
SystemError: <fortran object> returned NULL without setting an error

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "test.py", line 8, in <module>
scipy.integrate.ode(f).set_initial_value([1, 1]).integrate(1)
File "C:\Miniconda3\lib\site-packages\scipy\integrate\_ode.py", line 411, in integrate
raise ValueError('Function to integrate must not return a tuple.')
ValueError: Function to integrate must not return a tuple.

Scipy/Numpy/Python version information:

0.19.1 1.13.1 sys.version_info(major=3, minor=6, micro=1, releaselevel='final', serial=0)
Issue 1:
ISSUE TYPE

Feature Idea

COMPONENT NAME

ec2_metric_alarm

ANSIBLE VERSION

2.3.2.0

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

Amazon CloudWatch has added a setting to define how an alarm handles a missing data point (announcement, description) using:

"Treat missing data as:" in the UI

--treat-missing-data option in the AWS CLI

TreatMissingData request parameter in the API

Ansible needs a treat_missing_data option in its ec2_metric_alarm module with possible values breaching (bad), notBreaching (good), ignore, and missing.

STEPS TO REPRODUCE

- ec2_metric_alarm:
...
treat_missing_data: notBreaching
...

Also, Terraform has the treat_missing_data argument for its aws_cloudwatch_metric_alarm provider resource.

Issue 2:
ISSUE TYPE

Feature Idea

COMPONENT NAME

ec2_metric_alarm

ANSIBLE VERSION

ansible 2.2.1.0
config file = /Users/kmcnally/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

[defaults]
nocows = 1
host_key_checking = False
retry_files_enabled = False

[ssh_connection]
ssh_args = -o ControlMaster=auto -o ControlPersist=60s -o ForwardAgent=yes
pipelining=True
host_key_checking = False

OS / ENVIRONMENT

MacOS Sierra 10.12.3

SUMMARY

When creating a cloudwatch alarm using the aws cli you get the option to set --treat-missing-data to breaching | notBreaching | ignore | missing.

http://docs.aws.amazon.com/cli/latest/reference/cloudwatch/put-metric-alarm.html

It looks like this setting is not available in the module. So when creating an alarm using this module the setting will always be missing, which is default. Can you confirm if this is right or am I missing something?

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS
Issue 1:
I just noticed that the definition for the img element includes the max-width property. This seems to break the controls for the Google Maps v3 API, causing very odd graphics to load for the zoom control.

Placing in some additional CSS to overwrite the Bootstrap definition fixes the problem. The CSS I used was: .

gmnoprint img {
max-width: none
}

Issue 2:
First of all thanks for your fantastic work. It does SAVE me a lot of time.

When I put Google Maps into Bootstrap layout, img tag in Google Maps breaks because Bootstrap set img max-width to 100%. When I comment max-width, it's working find but I'm not sure whether it'll break something else in Bootstrap or not.

Bootstrap and Google Maps

http://jsfiddle.net/jhnRD/1/

Google Maps without Bootstrap

http://jsfiddle.net/aVx8L/

Cheers,
Issue 1:
IMHO FCC needs better support for commenting in code... the intructions for Delete your jQuery Functions do say delete but while working on code commenting out suspicious parts or just leaving notes is typically a good practice. FCC actively discourages this.

I commented out the code to be deleted

// $("button").addClass("animated bounce");
// $(".well").addClass("animated shake");
// $("#target3").addClass("animated fadeOut");

but FCC didn't 'PASS' the test.

Challenge Delete your jQuery Functions has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.

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

My code:

<script>
$(document).ready(function() {
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Issue 2:
The challenge description states: Return true if the string in the first element of the array contains all of the letters of the string in the second element of the array.

According to that the case: mutation(["Mary", "Aarmy"]) should return false because the first string has only one a character, therefore does not contain all of the characters of the second string.

Currently that test case returns true.
Issue 1:
when I use:

torch.onnx.export()

to convert my pytorch model to onnx model,

I can monitor the memory is used up by the converting process.

and then the process is killed.

no any other logs, just killed.

cc @houseroad @spandantiwari @lara-hdr @BowenBao @neginraoof

Issue 2:
🐛 Bug

See also #16908

After fixing INT64 issue we moved forward and stumbled upon the following:

ERROR: In node 175 (convert_axis): UNSUPPORTED_NODE: Assertion failed: axis >= 0 && axis < nbDims

This is Gather on Axis 0. Seems like it has to be another axis. Please check it out.
Issue 1:
"Put the Like, Info and Delete buttons side-by-side by nesting all three of them within one

element, then each of them within a

element"

I think the Bootstrap markup "btn-block" from the previous exercise is redundant. The buttons are supposed to be side by side in this exercise using the column grid.

I suggest part of the exercise is to remove the "btn-block" class form each button and tests be written to ensure they are removed. I would like some feedback about this suggestion before submitting a pull request.

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-use-spans-for-inline-elements has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

First line of the challenge has a typo where the word "use" comes twice:

You can use use spans to create inline elements.
Issue 1:
<input type="number" step=".01" min={1} max={9999} defaultValue={ 1.00 } />

the input Unable to enter a decimal

Issue 2:
This appears to have been introduced in a new Chrome version, but I can't find any reference to where.

Affected/Tested Browsers (OS X):

Chrome 51.0.2704.106 (64-bit)

Opera 39.0.2256.15

Unaffected Browsers:

Safari 9.1

Firefox 49

Backspacing in an input element with value or defaultValue set causes some very odd behavior. Once a decimal point is gone, it can't easily be re-added.

Example:

In this example, I simply backspaced twice. On the second backspace, when I expect 3. to be showing, the input instead reads 3 and the cursor has moved to the beginning. The next two jumps are my attempts to add another decimal point.

Fiddle: https://jsfiddle.net/kmqz6kw8/

Tested with React 15.2.

Notes: This only occurs when value or defaultValue is set. If neither is set, the input behaves properly. We are currently working around this issue by (unfortunately) setting the input value on componentDidMount via a ref.
Issue 1:
From @alexlist on 2016-04-22T03:27:34Z

I didn't find exactly this problem reported, only other bug reports related to nfs mounts.

ISSUE TYPE

Bug report

COMPONENT NAME

mount module

ANSIBLE VERSION

ansible 2.1.0
config file = /home/alex/repos/infra/ansible/ansible.cfg
configured module search path = Default w/o overrides

CONFIGURATION

Standard.

OS / ENVIRONMENT

CentOS 7 -> CentOS 7

Ubunt 15.10/16.04 -> CentOS 7

CentOS 7 -> Ubuntu 15.10/16.04

In this particular case, only CentOS 7 -> CentOS 7

SUMMARY

NFS mount point with state=mounted triggers error if already mounted.

STEPS TO REPRODUCE

Put a NFS mount stanza in a playbook and run the playbook when the mount is already mounted:

- name: configure fstab for alpha
action: mount name=/srv/foo/alpha src=fileserver:/mdarchive/alpha fstype=nfs4 opts=rw,hard,tcp,intr,nolock,rsize=1048576,wsize=1048576,_netdev state=mounted

Run the playbook, get an error:

TASK [configure fstab for alpha] ***********************************************
fatal: [cluster-node01]: FAILED! => {"changed": false, "failed": true, "msg": "Error mounting /srv/foo/alpha: mount.nfs4: /srv/foo/alpha is busy or already mounted\n"}

EXPECTED RESULTS

I expect the documented behaviour:

http://docs.ansible.com/ansible/mount_module.html

If mounted or unmounted, the device will be actively mounted or unmounted as needed and appropriately configured in fstab.

Obviously, if a mount is already mounted, mounting it again is not needed and triggers the error and further execution of the playbook.

ACTUAL RESULTS

TASK [configure fstab for alpha] ***********************************************
fatal: [cluster-node01]: FAILED! => {"changed": false, "failed": true, "msg": "Error mounting /srv/foo/alpha: mount.nfs4: /srv/foo/alpha is busy or already mounted\n"}

Copied from original issue: ansible/ansible-modules-core#3514

Issue 2:
Today I tested the devil branch a home and I found out that gathering facts failed, because a locale ('de_DE') is set.

The Problem is that the split operation on the ifconfig ouput doesn't work properly. (Line 458 in setup module)

cmd = subprocess.Popen("env LANG=\"\" /sbin/ifconfig %s" % iface, shell=True,
stdout=subprocess.PIPE, stderr=subprocess.PIPE)

I tried the code above. It fixes the issue.
Issue 1:
My app forms utilize the enter button to tab to specified fields for speed on a ten-key keyboard. When enter is hit, we do a DOM lookup and trigger focus() on the next element. This works great on text fields but I cannot understand how to accomplish this on a Select box. I can get each of the DOM elements that make up the Select structure, but triggering focus() at any level does nothing.

Note: I am able to grab the ref of the item via inputRef on the select to prevent us from traversing the DOM but it still yields no results.

Thank you in advance for any guidance!

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

Expected Behavior

Select becomes focused (but not open) when focus() is triggered manually. Expect the same behavior as hitting on the preceding element.

Current Behavior

Triggering node.focus() does nothing, nor does it trigger on any element within the select DOM structure.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/m43qqyo2zy

Select first text box.

Hit Enter key.

Notice 2nd text box is focused FTW.

Hit Enter key again.

Nothing happens.

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.1.0

browser
Chrome 62

etc

Issue 2:
Current beta is missing Slider component

[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

As per existing Material-UI

Current Behavior

Steps to Reproduce (for bugs)

Context

Currently preventing upgrading to the new generation of material-ui

Your Environment

Tech
Version

Material-UI
v1.0 beta

React
16
Issue 1:
🐛 Bug

min/max refuse to work on non-zero dimension of empty tensor.

My understanding is the "op does not have identity" issue should only apply to zero dimension.

To Reproduce

Python 3.6.9 (default, Jul 17 2020, 12:50:27)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
>>> torch.rand((0,4)).max(1)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity

Expected behavior

Empty tensor with proper size for non-zero dimensions.

Environment

Collecting environment information...
PyTorch version: 1.7.0a0+72378e9
Is debug build: No
CUDA used to build PyTorch: 11.0

OS: Ubuntu 18.04.4 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.18.1

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: Tesla V100-SXM2-32GB
GPU 1: Tesla V100-SXM2-32GB
GPU 2: Tesla V100-SXM2-32GB
GPU 3: Tesla V100-SXM2-32GB
GPU 4: Tesla V100-SXM2-32GB
GPU 5: Tesla V100-SXM2-32GB
GPU 6: Tesla V100-SXM2-32GB
GPU 7: Tesla V100-SXM2-32GB

Nvidia driver version: 440.33.01
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.0.2

Versions of relevant libraries:
[pip3] numpy==1.19.1
[pip3] torch==1.7.0a0+72378e9
[pip3] torchvision==0.8.0a0+6db1569
[conda] Could not collect

PyTorch Version (e.g., 1.0): master (1.7.0a0+72378e9)

OS (e.g., Linux): Ubuntu 18.04

How you installed PyTorch (conda, pip, source): source

Build command you used (if compiling from source): cmake+ninja+gcc-8

Python version: 3.6

CUDA/cuDNN version: 11.0/8.0

GPU models and configuration: V100

Issue 2:
🐛 Bug

Current min / max implementation is too restrictive wrt tensors with zero elements.

Indeed, min/max reduction over an empty dimension should raise an error, as they don't have an identity, but if the dimension being reduced is not of size 0 (but the tensor has 0 elements), then it should work.

To Reproduce

a = torch.rand(0, 4)
print(a.max(1))

raises

RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity

while

a = torch.rand(0, 4)
print(a.numpy().max(1))

returns

array([], dtype=float32)

PyTorch version 1.5.0.dev20200225

cc @ezyang @gchanan @zou3519 @mruberry @rgommers @heitorschueroff
Issue 1:
Description of the new feature/enhancement

VTE only rewraps the contents of the (normal screen + its scrollback buffer) on a resize event. It doesn't rewrap the contents of the alternate screen.

Rationale:

The alternate screen is used by applications which repaint it after a resize event. So it doesn't really matter.

However, in that short time window, after resizing the terminal but before the application catches up, this prevents vertical lines (e.g. the user interface of mc) from becoming ugly tilted.

Issue 2:
Paste text in a messy format
Issue 1:
Environment

Windows build number: 10.0.17763.475

Other software: Elasticsearch 6.7.0 using Java 1.8.0_172, but the behavior was
confirmed with a test batch file and executable.

Steps to reproduce

When testing the functionality of the start command within the cmd.exe shell, I found that having the /min parameter would affect the /d parameter: the path provided to the /d parameter did not seem to be acknowledged, and the command passed to the start command would not be found.

Test example:

Command shell with prompt at C:\temp

A test batch file at C:\temp\testdir\test.bat, with the content

@echo hello
pause

Running the following command would succeed:

C:\temp>start /d c:\temp\testdir test.bat

The following command would not succeed:

C:\temp>start /min /d c:\temp\testdir test.bat

If the path is set to C:\temp\testdir the following command would succeed:

C:\temp\testdir>start /min test.bat

The use of the /d and /min parameter together was previously working, and was required functionality for a commercial product.

I'm wondering if this problem is related to #271 .

Expected behavior

The /d parameter to be parsed when the /min parameter is also included to the start command.

Actual behavior

If the /min parameter is used with the /d parameter, the path used with the /d parameter does not seem to be used, and the program contained in the path referenced by the /d parameter is not found.

Issue 2:
In 1809, the way the start command (from cmd.exe) behaves has changed. You can work around it by adding /max or /min after start.

Two concrete examples:

Running something off a network share from a command prompt like:

start z:\myapp.exe

will now throw up a security warning dialog, when it did not in 1803 and earlier.

A powershell script like this:

$script={& cmd.exe /c start notepad.exe}

$job = start-job -scriptblock $script

would give you a job with state Running in 1803, until you closed notepad. In 1809, the job state is Completed before notepad is closed.

Adding /max or /min after start restores old behavior for both of these! That is crazy...

Both of these behavior changes are going to break tools/code that rely on the old behaviors of no security prompt and the powershell job not being Complete until the started program exits.

You can see how dramatically start has changed if you run procmon and filter to only cmd.exe process events. In Win10 1803, open a command prompt and do

start notepad.exe

It results in <100 events. Run in 1809 and get >1000. Add /max and it drops back to <100.
Issue 1:
I am having a lot of situations in which I am depending on some module from multiple files. I end up with the multiple occurances of that module in the output bundle, each of which has different id's. I would expect this module to occur once which is what I also need because most of these are singletons whose state I need accross the application.

So far I don't have any good starting point. Are there any typical causes for this?

Issue 2:
Why cant I set flags?

cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ webpack -v
2.1.0-beta.28
cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ cat package.json | grep webpack
"webpack": "2.1.0-beta.28",
"webpack-dev-server": "^1.16.2"
cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ webpack --display-chunks

Option '--display-chunks' not supported. Trigger 'webpack -h' for more details.

cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ webpack-dev-server --inline --hot

Option '--inline' not supported. Trigger 'webpack-dev-server -h' for more details.
^C
cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ webpack
ts-loader: Using typescript@2.1.4 and /home/cescoferraro/code/go/src/github.com/cescoferraro/spotify/tsconfig.json
^C

cescoferraro@desktop: ~/code/go/src/github.com/cescoferraro/spotify on master [+!?]
$ webpack-dev-server
[HPM] Proxy created: ** -> http://localhost:8080
http://localhost:8000/
webpack result is served from /
content is served from ./www
Issue 1:
Challenge Passing Values to Functions with Arguments has an issue.

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

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

My code:

// Example
function ourFunction(a, b) {
console.log(a - b);
}
ourFunction(10, 5); // Outputs 5

// Only change code below this line.
function myFunction(a,b) {
console.log(a + b);
}
myFunction(10, 5);

Issue 2:
Some of the instructions have duplicate information (e.g. link to twitch API), others have broken links.
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-remove-classes-from-an-element-with-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

the challenge was marked as finished even with just $("button").removeClass

it should be marked as finished with $("button").removeClass("btn-default");

Issue 2:
Challenge use-prototype-properties-to-reduce-duplicate-code has an issue.

function Dog (name) {
this.name = name;
}

let beagle = new Dog("Snoopy");
// Add your code below this line

Dog.prototype.numLegs = 4;

As seen above, this challenge wants the camper to add a shared property to the prototype of the Dog. The issue here is that it wants the camper write that expression after the Dog actually is instantiated. Since all properties on the prototype are shared by all instances, this won't cause any runtime trouble - but it's generally considered a best practice to keep definitions before they are instantiated and used.

Therefore, I suggest we swap places of the comment and the instantiation of Dog, and replace "below" with "above".

I'll submit a PR for this immediately - we can always discuss it further there.