WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Challenge Waypoint: Clone an Element Using jQuery has an issue.

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

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

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");

});
</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:
A bug seems to be present: Chrome 46.0.2490.86 m; Windows 8.1 with respect to appendTo() function.

$("#target2").appendTo($("#right-well")); does work, but not the $("#target2").appendTo("#right-well");, the latter being suggested in the tutorial.

Hard reload and cache clearing did not seem to solve the problem.
Issue 1:
When the type of TextField is set to number and give it a initial value, once the entered number is deleted, the displayed value becomes 0. If you then enter another number, the zero will stay unless the page is refreshed.

I've checked the value received in the onChange function, which doesn't come with the leading zero.

If the 'value' attribute is not set, this issue won't occur.

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

Expected Behavior

If the entered number is deleted, it'd be better to not show the default 0 (as seen in Component Demos).

OR

Show the default 0, but remove it if the first digit entered is not 0.

Current Behavior

The leading zero won't go away.

Steps to Reproduce (for bugs)

Use a TextField and set type to number. Apply an onChange function.

In the browser, enter a number in the field, and remove it. You should see a zero now.

Enter another number. You shoud now see a the number with a leading zero.

Context

This behaviour is okay if the field is used for mobile number.

In the case where it's used for currency or quantity, it could be a bit confusing.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.12

React
15.0.0

browser
Chrome Version 60.0.3112.113

etc

Issue 2:
TablePagination is missing from exports

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

Expected Behavior

import { TablePagination } from 'material-ui/Table'; should import the component

Current Behavior

the imported is undefined

Steps to Reproduce (for bugs)

import { TablePagination } from 'material-ui/Table';
console.log(TablePagination) <--undefined

Context

it is missing in the source code as well

Your Environment

Tech
Version

Material-UI
1.0.0-beta.12

React
15.6.1

browser
chrome 61.0.3163.100 (Official Build) (64-bit)
Issue 1:
I created an extension to port Sublime keybindings to VS Code keybindings. I made a list of all the key bindings that were missing analogous commands in VS Code.

Here is the list roughly ordered by importance. Please let me know about more I missed in the comments. If an extension exists with the functionality I added it in the far right column.

Windows / Linux
Mac
Description
Issue
Extension

ctrl+left mouse click
cmd+left mouse click
Add multi cursors
#3130
None

ctrl+;
None
Go to Word
#14028
None

ctrl++
cmd++ and cmd+=
Increase Font Size
#14031
FontSize Shortcuts

ctrl+-
cmd+-
Decrease Font Size
#14031
FontSize Shortcuts

ctrl+shift+m
ctrl+shift+m
Expand selection to brackets
#14089
Bracket Selection

ctrl+shift+j
cmd+shift+j
Expand selection to indent level
#14090
None

alt+q
cmd+alt+q
Break / Wrap line
#14093
None

alt+shift+1
alt+cmd+1
Switch to single column view
#14094
None

ctrl+y
ctrl+y
Repeat
#14097
None

ctrl+shift+a
cmd+shift+a
Expand selection to tag
#14098
expand-region

ctrl+shift+space
cmd+shift+space
Expand selection to scope
#14099
expand-region

shift+f11
ctrl+shift+cmd+f
Enter distraction free mode
#12940
None

ctrl+space
ctrl+space
Select next auto complete suggestion
#14101
None

alt+shift+w
ctrl+shift+w
Wrap HTML tag
#14103
None

alt+.
cmd+alt+.
Close HTML tag
#14104
Close HTML/XML tag

ctrl+k ctrl+6
cmd+k cmd+6
Fold level 6
#14106
None

ctrl+k ctrl+7
cmd+k cmd+7
Fold level 7
#14106
None

ctrl+k ctrl+8
cmd+k cmd+8
Fold level 8
#14106
None

ctrl+k ctrl+9
cmd+k cmd+9
Fold level 9
#14106
None

alt+0
cmd+0
Select open tab index 9
#14095
None

Additionally, here are other actions that are not bound to a keyboard shortcut:

Action
Issue
Extension

Drag and drop selected text
#1046
None

Customize keybinding support in menus (see this comment #3776 (comment))

Customize keybinding support in viewlets (see this #4557)

Issue 2:
#6683 fix means the integrated terminal cannot be restarted after the process errors without reloading the window.
Issue 1:
Here's the code I'm compiling:

'use strict'

async function recurse(n) {
if (n > 0) {
console.log(n)
await recurse(n - 1)
}
}

recurse(10)

My package.json is:

{
"scripts": {
"build": "babel src --out-dir dist"
},
"devDependencies": {
"babel-cli": "6.0.15",
"babel-plugin-transform-async-to-generator": "6.0.14"
},
"babel": {
"plugins": ["transform-async-to-generator"]
}
}

The compiled code is:

'use strict';

let recurse = (function () {
var ref = _asyncToGenerator(function* recurse(n) {
if (n > 0) {
console.log(n);
yield recurse(n - 1);
}
});

return function recurse(_x) {
return ref.apply(this, arguments);
};
})();

function _asyncToGenerator(fn) { return function () { var gen = fn.apply(this, arguments); return new Promise(function (resolve, reject) { var callNext = step.bind(null, "next"); var callThrow = step.bind(null, "throw"); function step(key, arg) { try { var info = gen[key](arg); var value = info.value; } catch (error) { reject(error); return; } if (info.done) { resolve(value); } else { Promise.resolve(value).then(callNext, callThrow); } } callNext(); }); }; }

recurse(10);

Running this just prints '10', because the generated function* recurse function covers up the real function.

Issue 2:
This code worked with babel 5.x and doesn't with babel 6.x. The expectation is that countdown1 and countdown2 both produce the same results:

'use strict';

function sleep(timeout) {
return new Promise(function (resolve, reject) {
setTimeout(function () {
resolve();
}, timeout);
});
}

const countdown1 = async function (count) {
console.log(count);
await sleep(1000);
if (--count) {
await countdown1(count);
}
};

async function countdown2(count) {
console.log(count);
await sleep(1000);
if (--count) {
await countdown2(count);
}
};

countdown1(5)
.then(function () {
console.log('countdown1 done');
return countdown2(5);
})
.then(function () {
console.log('countdown2 done');
});

From the produced code, it looks like the transformed countdown2 is getting shadowed by inner functions using the same name.
Issue 1:
When using DataFrame.apply(), it would be helpful to be able to apply different functions to different columns. There's a nice workaround on StackOverflow:

import numpy as np
import pandas as pd

def multi_func(functions):
def f(col):
return functions[col.name](col)
return f

df = pd.DataFrame(np.random.random((10, 2)), columns=['A', 'B'])
results = df.apply(multi_func({'A': np.mean, 'B': np.sum}))

results
A 0.401456
B 6.845529
dtype: float64

My guess is that the changes would be made in pandas.core.frame.DataFrame, potentially adding a new _apply_X method. Any thoughts/advice?

Issue 2:
I'm trying to use pandas to speed up timezone conversions on many datetimes and I can't get around NonExistentTimeErrors. Pandas tz_localize() seems to ignore the ambiguous argument for the non existent time case.

Example:

import pytz
import pandas

tz = pytz.timezone('Europe/Warsaw')
non_existent = datetime.datetime(2015, 3, 29, 2, 30)

tz.normalize(tz.localize(non_existent))
#2015-03-29 03:30:00+02:00

tz.normalize(tz.localize(non_existent, is_dst=False))
#2015-03-29 03:30:00+02:00

pandas.Timestamp(non_existent).tz_localize(tz)
# NonExistentTimeError: 2015-03-29 02:30:00

pandas.Timestamp(non_existent).tz_localize(tz, ambiguous=0)
# NonExistentTimeError: 2015-03-29 02:30:00

It would be nice if the ambiguous argument worked the same as is_dst in pytz. As it is now, it's impossible afaik to reliably localize a series of datetimes using pandas, since any of them might cause a NonExistentTimeError and there's no way of guiding pandas what to do with such datetimes.

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.5.final.0
python-bits: 64
OS: Linux
OS-release: 3.13.0-39-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8

pandas: 0.15.1
nose: 1.3.4
Cython: None
numpy: 1.9.1
scipy: None
statsmodels: None
IPython: 2.3.1
sphinx: 1.2.2
patsy: None
dateutil: 2.2
pytz: 2013.9
bottleneck: None
tables: None
numexpr: None
matplotlib: None
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: None
httplib2: 0.9
apiclient: 1.3.1
rpy2: None
sqlalchemy: None
pymysql: None
psycopg2: 2.5.4 (dt dec pq3 ext)
Issue 1:
We could integrate a function for signal words like in windows search. So the user enter signalWord: abc and the app knows for what the user is searching for.

signal words can be:

window : search for window including browser tabs

browser : search for browser tab

app : user want to start apps

file : search for file or folder

cmd : to run command on cmd/ps/...

calc : to calculate math formula

...

Issue 2:
Summary of the new feature/enhancement

Pressing and holding Windows-Key should show the shortcuts of the curently active application instead of the windows-shortcuts only. For example when working with Lightroom show the lightroom-shortcuts but when working in Explorer show the explorer-shortcuts.

Proposed technical implementation details (optional)

The list of available-shorcuts could be read by an API (if possible). Otherwise the list could be maintained on github by the community.

See the application cheat-sheet for macos to see what this could look like
Issue 1:
VSCode Version: 1.1.0-alpha

OS Version: Windows 10

Steps to Reproduce:

Change language to German or French

Observe the file, edit, etc. menus

It seems some translations regress after alpha updates. Is this expected?

Issue 2:
VSCode Version: 1.2

OS Version: Windows 7, x65

Steps to Reproduce:

Open the terminal from within VS code

Do git log

Observe a first page of the command output (while the pager is awaiting for continuation)

Select a piece of the output text.

Attempt to copy the selected piece using Ctrl + C

Observe git log terminated.

Expected: text copied while application is still running

👍
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-a-specific-child-of-an-element-using-jquery has an issue.

The challenge will not allow the user to proceed even after posting the right solution i.e.

$('.well:nth-child(2)').addClass("animated bounce");

Currently the workaround to get ahead is to add a space after before and after the colon(Thanks to user @saadmehmood233 for pointing it out). The use of these spaces should not be binding as they are not required as per the syntax and it should be removed.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-comment-your-javascript-code has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Code "assert(editor.getValue().match(/(//)...../g)," appears on the left hand checklist.

After completing the challenge and running the code, section completion pop-up appears, and if you try to move on to the next section, the section completion pop-up will continuously appear instead of moving on to the next section.

Multi-line comments such as this do not pass the test:

/*

hello

*/
Issue 1:

Issue 2:
There is something missing in javascript after 3.0.0-rc1, versions -rc2 -wip and the latest release.

It shows a transparent background in modals when loads a single html file as remote content. There is a similar bug #10415, but this one is not related with Rails.

<html>
<head>
<link rel="stylesheet" href="//netdna.bootstrapcdn.com/bootstrap/3.0.0/css/bootstrap.min.css"/>
</head>
<body>
<a href="#myModal" data-toggle="modal" class="btn btn-primary btn-lg">Launch demo modal</a>
<a href="./test.html" data-toggle="modal" data-target="#myModal2" class="btn btn-primary btn-lg">Launch demo modal2</a>
<!-- Modal -->
<div class="modal fade" id="myModal" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title">Modal title</h4>
</div>
<div class="modal-body">
...
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="button" class="btn btn-primary">Save changes</button>
</div>
</div><!-- /.modal-content -->
</div><!-- /.modal-dialog -->
</div><!-- /.modal -->
<!-- Modal -->
<div class="modal fade" id="myModal2" tabindex="-1" role="dialog" aria-labelledby="myModalLabel" aria-hidden="true">
<div class="modal-dialog">
<div class="modal-content">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h4 class="modal-title">Modal title</h4>
</div>
<div class="modal-body">
...
</div>
<div class="modal-footer">
<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>
<button type="button" class="btn btn-primary">Save changes</button>
</div>
</div><!-- /.modal-content -->
</div><!-- /.modal-dialog -->
</div><!-- /.modal -->
<script src="//code.jquery.com/jquery.js"></script>
<!--
it only works well in 2.3.2 and 3.0.0-rc1 javascript, any other version shows transparent background
//netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/js/bootstrap.min.js
//netdna.bootstrapcdn.com/bootstrap/3.0.0-rc2/js/bootstrap.min.js
//netdna.bootstrapcdn.com/bootstrap/3.0.0-wip/js/bootstrap.min.js
-->
<script src="//netdna.bootstrapcdn.com/bootstrap/3.0.0/js/bootstrap.min.js"></script>
</body>
</html>

It fails in MAC OSX 10.8.4 and Windows 7 Professional, in Safari 6.0.5, Firefox 23.0.1, Google Chrome 29.0.1547.65 and Internet Explorer 10.0.9200.16686.
Issue 1:
OS: Windows 7 32 bit, using MinGW version suggested by wiki (because last one just fails)

Trying to compile example from website.

description:

this code works:

use core::*;

fn main() {
for ["Alice", "Bob", "Carol"].each |&name| {
do task::spawn {
io::println(name);
}
}
}

but when I add

let v = rand::Rng().shuffle([1, 2, 3]);

like

use core::*;

fn main() {
for ["Alice", "Bob", "Carol"].each |&name| {
do task::spawn {
let v = rand::Rng().shuffle([1, 2, 3]);
io::println(name);
}
}
}

it fails with error :

The procedure entry point ... rand... extension... not found in the .... dll

btw: why does rust code highlighting on github look like plain text?

Issue 2:
From ssylvan:

Consider this a very preliminary bug report, I only gave it about two

minutes because I have to run, so I could probably track this down

further with some process monitor logging. In case this is useful as

is I'll just tell you here.

On 64-bit Windows 8 RTM I get this in a message box when running the

executable produced by compiling the example on rust-lang.org.

---------------------------
helloworld.exe - Entry Point Not Found
---------------------------
The procedure entry point
_ZN4rand14__extensions__10meth_1235514gen_uint_range17_be256aac3933fdb73_04E
could not be located in the dynamic link library
D:\Programming\rust\helloworld.exe.
Issue 1:
Problem

Duplicate from stackoverflow 72375427 .

When plotting 2D scatter data on a 3D scatter plot (eg as in the example code from matplotlib website, which incidentally shows the problematic behaviour as the sin curve is obviously off by a bit), the 2D data floats "on top" or "alongside" of the 2D face it is supposed to be placed upon and therefore gives the impression to be wrongly plotted. For example, using this to show the projection of dots from the 3D space to 2D planes (3 plot faces) gives the impression that the dots are not at the correct position, because of the parallax (see plot linked below).

3D plot with 2D plots on sides, as produced by above code

3D plot with 2D plots on sides, as expected

I cannot get the planes to exactly be positioned at a specified coordinate. Setting the x_lim, y_lim and z_lim parameters only slightly improves this, but there is still a slight, seemingly random, margin added beyond the axes limits (contrary to what happens in 2D plots).

Proposed solution

I may have missed the option to do this. But it would be nice to have the possibility to overrule the automatic setting of the position of the edge planes so that setting the x_lim, y_lim and z_lim parameters fixes the planes to those specified values (for instance, or another extra parameter).

Another solution based on generating the 2D graphs as images and adding them to the 3D plot could potentially work, but probably is a messy hack more than a solution.

Issue 2:
I take an example from

https://stackoverflow.com/questions/23951230/python-axis-limit-in-matplotlib

In mplot3d, when you set, for example, set_xlim(0, 0.8), the outcome has an extra like set_xlim(0 - eps, 0.8 + eps), where eps is related to deltas.

matplotlib/lib/mpl_toolkits/mplot3d/axis3d.py

Line 187
in
6e76411

deltas = (maxs - mins) / 12.

To show the exact lims, you have to change deltas to, for example, 0 * (maxs - mins) / 12.

You need something to set exact lims without touching the inside of matplotlib.

Code for reproduction

from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt
fig = plt.figure()
ax = fig.gca(projection = '3d')
ax.set_xlim(0,0.8)
plt.show()

Actual outcome

Matplotlib version

Operating system:macOS 10.14.6

Matplotlib version: 3.1.1

Python version: 3.7.4

The problem was discussed many times in STACK OVERFLOW:

https://stackoverflow.com/questions/23951230/python-axis-limit-in-matplotlib

https://stackoverflow.com/questions/46380464/matplotlib-3d-axis-bounds-always-too-large-doesnt-set-lims-correctly

https://stackoverflow.com/questions/16488182/removing-axes-margins-in-3d-plot
Issue 1:
Hello, I have some data where inadvertently the x and y data were of different types, eventually after much troubleshooting I discovered that one was np.float32 and the other was np.float64. When trying to use least-squares minimization to fit to the data, either scipy.optimize.curve_fit or scipy.optimize.leastsq failed in a weird quasi-silent way. The failure mode is that the parameters are barely changed from the initial guess and the optimization returns even though the result is clearly not good. Below is a minimum example demonstrating the bug (from a jupyter notebook):

Reproducing code example:

%pylab inline
import numpy as np
from scipy.optimize import curve_fit

def gauss(x, A, mu, sigma):
return A/(sigma*np.sqrt(2*np.pi))*np.exp(-(np.power(x-mu,2)/(2*np.power(sigma,2))))

xdata = np.linspace(-1, 1, 20)
p_act = [1.4, 0.2, 0.2]
ydata = gauss(xdata, *p_act) + np.random.normal(loc=0, scale=0.05, size=len(xdata))
p0 = [1, 0, 0.1]

xdata = xdata.astype(dtype=np.float32)
ydata = ydata.astype(dtype=np.float64)
fit1, pcov1 = curve_fit(gauss, xdata, ydata, p0=p0)

xdata = xdata.astype(dtype=np.float32)
ydata = ydata.astype(dtype=np.float32)
fit2, pcov2 = curve_fit(gauss, xdata, ydata, p0=p0)

print(fit1)
print(fit2)

plot(xdata, ydata, 'bo')
x2 = np.linspace(xdata[0], xdata[-1], 100)
plot(x2, gauss(x2, *fit1), 'r--')
plot(x2, gauss(x2, *fit2), 'm--')

The output of the print statements are:

[1. 0.05021768 0.10987875]
[1.37911003 0.19699727 0.19586094]

Error message:

The only signature is that there is a covariance warning when fitting with the different data types:

/usr/local/lib/python3.7/site-packages/scipy/optimize/minpack.py:794: OptimizeWarning: Covariance of the parameters could not be estimated
category=OptimizeWarning)

Scipy/Numpy/Python version information:

1.1.0 1.15.1 sys.version_info(major=3, minor=7, micro=1, releaselevel='final', serial=0)

Issue 2:
I recently ran into an issue whereby curve_fit was failing to fit a function, even though the guesses were reasonable. The warning reported by Scipy was "/usr/local/depot/Python-3.5.1/lib/python3.5/site-packages/scipy/optimize/minpack.py:690: OptimizeWarning: Covariance of the parameters could not be estimated".

After hours of searching, I discovered that the problem was that I was using np.float32 arrays for the x and y data. Simply using x.astype(np.float64) resolved the issue. Though the warning provided no help or hints as to the source of the problem.

This is similar to what was reported in this (rather old) email thread: http://scipy-user.scipy.narkive.com/wSafjCiz/curve-fit-with-float32-values, which proved to be very difficult to find. It would be useful to warn in the curve_fit documentation (and other minimisation functions) about using float32 inputs, particularly as the problem only manifests itself with certain data sets.