WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Challenge Waypoint: Learn how Script Tags and Document Ready Work has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 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:
Image on the side is not showing. All I see is a "?" in a blue box. I am using a Mac computer. Should this be an issue?

Challenge Size your Images has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8.

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

My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
.smaller-image {
width: 100px;
}
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<img class="smaller-image" src="https://bit.ly/fcc-relaxing-cat" alt="A cute orange cat lying on its back. ">

<p class="red-text">Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p>
<p class="red-text">Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>
Issue 1:
Terminal gets automatically closed when I try to maximize the screen on extended screen.

Issue 2:
Summary of the new feature/enhancement

Windows Terminal should support automatic scrolling when user is selecting text with the mouse, as the mouse approaches the first or last lines. This is supported in the current conhost and it is missing in Windows Terminal.

If the feature is already planned or tracked by another bug, feel free to close it.

Proposed technical implementation details (optional)
Issue 1:
What problem does this feature solve?

The 'Vue server renderer' package should pass in a URL object when creating a sandbox

What does the proposed API look like?

createBundleRenderer(bundle, {
...renderOptions,
runInNewContext: 'once',
sandbox: {
URL: URL
}
});

Issue 2:
Version

2.6.11

Reproduction link

https://jsfiddle.net/shengslogar/f4kc5vq2/32/

Steps to reproduce

Create a watcher with an async handler. Make it throw an error.

What is expected?

It's captured by Vue error handler

What is actually happening?

Not being captured by vue error handler

Shows an uncaught promise error
Issue 1:
Currently the nightly build versions are 0.6

Nightly build checks at appveyor and travis are done against 0.6, but at http://pkg.julialang.org/ all packages are shown to pass/fail 0.5 although they are not checked against 0.5 anymore.

Or does http://pkg.julialang.org/ just need some time to proceed to 0.6?

Download of version 0.5 (rc1) seems also not possible anymore from http://julialang.org/downloads/ as no link is provided (at least I can't find it).

This is not a major problem for me but maybe its confusing for some people.

Issue 2:
There seems to be now way to download a Julia 0.5 binary at the moment. The stable releaser binary is Julia 0.4.6, while the nightly build binary is Julia 0.6.
Issue 1:
I have this String literal type example

type TStyles = 'x' | 'y' | 'z';

Using IntelliSense for completion this code will be awesome:

var style:TStyles = '>>> I want to use [CTRL+J] here to offer only valid TStyles values <<<';

Issue 2:
Many JavaScript frameworks are heavily based on using string values to do many things, from getting and setting attributes via the property name in string form, to defining event handlers to handle browsing to particular URLs. TypeScript added specialized signatures in overloads as one means to help mitigate the pain associated with these types of APIs. Unfortunately for a number of patterns this is insufficient and not general enough. Rather than try to design a specific type system enhancement that could handle some or all of the many ways these frameworks use string literals we could try some simple tricks in Visual Studio to help out. Namely, when typing a string literal the editor should provide a completion list based on other string literals already used in your program. Some other tools already provide similar capabilities (ex Sublime Text).

Consider something like this in a Backbone View class:

class TodoView extends Backbone.View<TodoModel> {
initialize() {
this.listenTo(this.model, 'change', () => this.render());
this.listenTo(this.model, 'todoDescriptionChanged', () => this.render());
this.listenTo(this.model, 'destory', () => this.remove());
}

At another point I may attempt to manually trigger one of these events:

updateTodo() {
var desc = this.$input.val().trim();
var todo = this.model;
if (desc) {
todo.save({ title: desc });
// provide completion list inside this string literal showing
// todoDescriptionChanged to avoid hard to debug typos
// and speed up development
todo.trigger('todoDescriptionChanged');
}
}

This should be a relatively cheap solution to a common set of problems that we've always hoped TypeScript can improve on over JavaScript. If you did accidentally make a typo in one use of the literal this could also help you discover that when seeing 2 completion list items that are similar but slightly different.
Issue 1:
Bug report

What is the current behavior?

I met huge build time degradation in new beta release. For example, node target in prod mode took

Version: webpack 5.0.0-beta.0
Time: 231016ms

instead of

Version: webpack 4.40.2
Time: 147028ms

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

I recorded graphs via webpack.debug.ProfilingPlugin for browser and node targets in both modes (dev and prod). I tried to open it but chrome stucks in the processing phase and closes devtool after that. Could you try to open it?

https://drive.google.com/file/d/13HA58298lrtX6FjJ833YuHkPqhYSU8Fj/view?usp=sharing

Link to config: https://github.com/7rulnik/webpack-config-v5-beta-built-time-issue/pull/1/files

What is the expected behavior?

Seems that it should take same or less time

Other relevant information:

webpack version: v5.0.0-beta.0

Node.js version: v12.10.0

Operating System: macOS 10.15

Issue 2:
Bug report

What is the current behavior?

webpack 5.45.0 (latest) doesn't work with jQuery 3.6.0 (latest):

ERROR in ./node_modules/jquery/dist/jquery.js 936:9
Module parse failed: Unexpected token (936:9)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| * @param {Function} fn Passed the created element and returns a boolean result
| */
> function assert( fn ) {
| var el = document.createElement( "fieldset" );
|
@ ./assets/js/index.js 1:0-23 65:21-22 73:23-24

webpack 5.45.0 compiled with 1 error in 3015 ms

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

Install webpack, webpack-cli and jquery.

Create 1 entrypoint which should be a file that imports jQuery.

Run webpack in production mode.

What is the expected behavior?

Successful compilation (downgrade only the webpack package to 5.44.0 solves the problem).

Other relevant information:

webpack version: 5.45.0

Node.js version: 16.5.0

Operating System: Debian GNU/Linux 10.10 x64

Additional tools: -
Issue 1:
Elasticsearch version:

version[2.3.5]

Plugins installed:

[kopf, HQ]

JVM version:

$ java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

OS version:

$ uname -a
Linux <xxx> 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Description of the problem including expected versus actual behavior:

According to the reference mapping-type index page and to the associated reference meta-fields index page as well as the reference _meta field page, this was supposed to run successfully on a 2.3.x cluster:

Steps to reproduce:

DELETE /tweet

PUT /tweet

PUT /tweet/tweet/_mapping

{
"properties": {
"tweet": {
"type": "string",
"analyzer": "english",
"_meta": {
"label": "This is a tweet body."
}
},
"date": {
"type": "date"
},
"name": {
"type": "string"
},
"user_id": {
"type": "long"
},
"_meta": {
"label": "This is a tweet object."
}
},
"_meta": {
"label": "This is a tweet database."
}
}

Answer:

{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [tweet] has unsupported parameters: [_meta : {label=This is a tweet body.}]"
}
],
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [tweet] has unsupported parameters: [_meta : {label=This is a tweet body.}]"
},
"status": 400
}

Issue #9649 mentioned it, and at the end it was commented that this was implemented and available. So I'm assuming it was either removed without a doc sync or it was broken recently. However, a quick lookup at the code searching for "_meta" got me to no place where MapperRegistry was ever used to register a Mapper for "_meta" attribute. I'm looking forward to being proven wrong though.

Issue 2:
Currently, when invoking GET indexname/_mapping one gets a long list of the fields that can be expected in the index. All these have the form:

"feed": {
"type": "string",
"index": "not_analyzed"
}

For an end user, who normally cannot see the configuration, the name of the field and its properties might not be enough to understand what the field actually holds. Therefore, it would be very helpful to allow a comment field inside the object above. Here is an example:

"feed": {
"type": "string",
"index": "not_analyzed"
"comment": "feed holds the name of the feed as provided by the client side"
}
Issue 1:
Problem description

A new line is added when the value prop is set in TextField (with multiline true), and enter is pressed.

Link to minimal working code that reproduces the issue

https://www.webpackbin.com/bins/-KlGfX7Kl4Q4uqZ7MITB

Go to the textfield and press enter.

Versions

Material-UI: 0.18.1

React: 15.2

Browser: Chrome

Issue 2:
I am using a TextField for sending messages in a chat application. My implementation requires that the TextField expand, can accept newlines via shift+enter, and send a message (empty the textfield) upon hitting enter.

I am using React 15.6 and MaterialUI v0.20.1 (I'd rather use the latest version, but its not up to me unfortunately)

I have everything working as it should, with one exception. In IE11 and Edge, if the textfield is empty and I add newlines (either with the defualt behavior of the enter key, or by adding the newline to the endof the controlled value, the TextField refuses to expand until other text is entered.

This error can be replicated in the MaterialUI demo in IE and Edge, even in the current version of Material UI. It works properly in Chrome and Firefox. Is there any way to work around this? Is the issue known already?

Thanks!
Issue 1:
Bug summary

When calling plt.gca().set_aspect(-1) it leads to a infinite loop, where ValueError: 'box_aspect' and 'fig_aspect' must be positive repeatedly, until I terminate python.

Code for reproduction

import matplotlib.pyplot as plt
plt.plot()
plt.gca().set_aspect(-1)

Actual outcome

ValueError: 'box_aspect' and 'fig_aspect' must be positive is thrown repeatedly

Expected outcome

either a single Value Error, or that you get the same as if you would invert the y-axis, but with a 1:1 aspect ratio.

Additional information

No response

Operating system

iOS

Matplotlib Version

3.5.3

Matplotlib Backend

MacOSX

Python version

3.10

Jupyter version

No response

Installation

pip

Issue 2:
Duplicate uploads also fail.

I think that is OK though?

We have at least one build on main per day most days and I am not sure it is worth the logic to not get rejected on the days we do not (or on days when someone has pushed the button to run it early).

If no one minds I don't mind throwing in some additional logic to check just before the upload stage. This is pretty easy with pip index versions and some sed

$ python -m pip index \
--index-url https://pypi.anaconda.org/scipy-wheels-nightly/simple \
--pre \
versions matplotlib | \
grep matplotlib | \
sed 's/.*(\(.*\))/\1/'
WARNING: pip index is currently an experimental command. It may be removed/changed in a future release without prior warning.
3.6.0.dev1948+gd8ede1a710

So all you'd need to do would be something like

$ LAST_NIGHTLY_VERSION="$(python -m pip index \
--index-url https://pypi.anaconda.org/scipy-wheels-nightly/simple \
--pre \
versions matplotlib | \
grep matplotlib | \
sed 's/.*(\(.*\))/\1/')"
WARNING: pip index is currently an experimental command. It may be removed/changed in a future release without prior warning.
$ echo "${LAST_NIGHTLY_VERSION}"
3.6.0.dev1948+gd8ede1a710

and then just check if that shows up as version of the wheels that just got downloaded from the GitHub Actions workflow artifact

$ [ "$(find dist -type f -iname "matplotlib-${LAST_NIGHTLY_VERSION}*.whl" | wc --lines)" -gt "0" ]
$ echo $?
0

(maybe a more elegant way to do that but that's not the worst)

I'll make an Issue from this and I'm happy to PR it, unless you would prefer to avoid touching it as much as possible.

Originally posted by @matthewfeickert in #22733 (comment)
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-children-of-an-element-using-jquery has an issue. The first sentence of the text is incorrect. Many HTML elements have children elements from which they inherit properties should read Many HTML elements have children elements which inherit their properties. Children inherit from parents, not the other way around.

Issue 2:
I'm being allowed to go to the next challenge even though I am not entering the semi colons.
Issue 1:
In the bootstrap.css file there are few properties which are are repeated twice, starting at line no 719:

This is repeated [appears in line 719 & again in 729]:

.container:before,

.container:after {

display: table;

content: " ";

}

.container:after {

clear: both;

}

And this is repeated [appears in line 739 & again in 749]:

.row:before,

.row:after {

display: table;

content: " ";

}

.row:after {

clear: both;

}

The same duplication has found its way into bootstrap.min.css as well.

Issue 2:
show on bootstrap.css

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L581

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L723

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L743

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2023

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2433

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2617

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2637

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3032

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3296

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3453
Issue 1:
ISSUE TYPE

Feature Idea

COMPONENT NAME

unarchive module

ANSIBLE VERSION

ansible 2.3.1

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

need a feature to extract single/multiple files from .zip file . current unarchive module will unzip all the files to the destination folder

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

Issue 2:
ISSUE TYPE

Feature Idea

COMPONENT NAME

unarchive module

ANSIBLE VERSION

ansible 2.1.0.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
This feature idea is really more geared towards Ansible > 2.1

CONFIGURATION

export ANSIBLE_NOCOWS=1

OS / ENVIRONMENT

SUMMARY

A Java JAR file is a ZIP file with a manifest and can be extracted using unarchive. A Java JAR file can also be executed in place. It's pretty common to extract specific files from a Java JAR file (such as properties files) so that you can alter the execution environment. In the case below, I simply want to extract the icon file to add a launcher for Burp Suite to the menu.

In any case, there are many other instances when it would be convenient to unarchive a limited set of files from an archive. The "exclude" parameter provides a similar function, but wouldn't be convenient in this case as there are thousands of files and a complex directory hierarchy in this archive. Since I'm not on 2.1 yet (Xubuntu), I don't have the exclude feature yet but used the command module to run unzip instead. The only annoying aspect to this technique is that Ansible tells me I should be using the unarchive module.

Low priority but potentially very useful ... and thanks for hard work you all put in!

STEPS TO REPRODUCE

The following play extracts a single file as needed:

- name: extract the application's icon from the archive
command: unzip {{ burp_installation_directory }}/{{ burp_file }} {{ burp_icon_path }}/{{ burp_icon_file }}
chdir={{ burp_installation_directory }}
creates={{ burp_installation_directory }}/{{ burp_icon_path }}/{{ burp_icon_file }}
tags:
- burp_suite
- security

But also generates a warning that I'm using the wrong module for the job.

TASK [burp_suite : extract the application's icon from the archive] ************
changed: [localhost]
[WARNING]: Consider using unarchive module rather than running unzip

EXPECTED RESULTS

ACTUAL RESULTS
Issue 1:
$ RUST_LOG=rustc=1,::rt::backtrace rustc link_header.rs
rust: task failed at 'assertion failed: rp.is_none()', /Users/shout/Projects/rust/src/librustc/middle/typeck/collect.rs:1044
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=1,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /Users/shout/Projects/rust/src/librustc/rustc.rs:358
rust: domain main @0x7f86ba819810 root task failed

Complete contents of link_header.rs

#[ crate_type = "lib" ];

// Given a Link header, parse out the next url
// <https://api.github.com/repositories?since=364>; rel="next", <https://api.github.com/repositories{?since}>; rel="first"
fn parse(header: ~str) -> &'self str {
match header.find('<') {
Some(start) => {
match header.find('>') {
Some(end) => {
return header.slice(start + 1, end);
},
_ => { fail!("Missing >") }
}
},
_ => {fail!("Missing <") }
}
}

Issue 2:
Followup to #5219. Per that issue rpaths are frowned on by linux distros. Absolute rpaths are supposed to be worse than relative rpaths (I'm not clear on why at the moment), and they are probably relatively easy to get rid of. Nominating.
Issue 1:
Description of the problem

The fiddle is https://jsfiddle.net/dcromley/g791otyp/

This draws a line using bufferGeometry with

LineBasicMaterial( { vertexColors:THREE.VertexColors, lights:false }

As it is, it gives a correct red to blue line.

By changing "lights:false" to "lights:true", it gives the error:

Uncaught TypeError: Cannot set property 'value' of undefined

It does not give this error using Revision 73.

Maybe, "Who would want to do this"? But I stumbled across this error.

My thanks to all. Let me know how I can conform better to the threejs society.

Three.js version

r95

Browser

[x ] Chrome Version 68.0.3440.106 (Official Build) (64-bit)

OS

[x ] Windows

Hardware Requirements (graphics card, VR Device, ...)

Issue 2:
(*** This section is for bug reports and feature requests only. This is NOT a help site. Do not ask help questions here. If you need help, please use stackoverflow. ***)

Description of the problem

var starsMaterialx = new THREE.PointsMaterial( { color: 0xFFFFFF, size: 5, lights: true } );
returns
Uncaught TypeError: Cannot set property 'value' of undefined
at t (three.min.js:136)
while
var starsMaterialx = new THREE.PointsMaterial( { color: 0xFFFFFF, size: 5 } );
and
var starsMaterialx = new THREE.PointsMaterial( { color: 0xFFFFFF, size: 5, lights: false } );
works fine.

Three.js version

Dev

r82

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

Linux

Android

IOS

Hardware Requirements (graphics card, VR Device, ...)

iMac (Retina 5K, 27-inch, Late 2014)

AMD Radeon R9 M295X 4096 MB
Issue 1:
I came around this and this seemed related to #9595 but could also be a bug in the above interacting with the CategoricalIndex. Using the same example as #15470 with pandas 0.20.3:

Code Sample

s = pd.Series([2, 1, 0], index=pd.CategoricalIndex([2, 1, 0]))
s[2] # works (interpreting as label)
s.loc[2] # fails with TypeError: cannot do label indexing on <class 'pandas.core.indexes.category.CategoricalIndex'> with these indexers [2] of <class 'int'>

# of course the below works!
s = pd.Series([2, 1, 0], index=[2, 1, 0])
s[2] # works (interpreting as label)
s.loc[2] # works (interpreting as label)

Problem description

s.loc[2] shouldn't fail and should select the label '2'.

Note this happens also with a pd.DataFrame.

Issue 2:
Code Sample, a copy-pastable example if possible

>>> s = pd.Series([2, 1, 0], index=pd.CategoricalIndex([2, 1, 0]))
>>> s.index
CategoricalIndex([2, 1, 0], categories=[0, 1, 2], ordered=False, dtype='category')
>>> s[[0, 1, 2]].equals(s.loc[[0, 1, 2]]) # Should be True
False
>>> s[[0, 1, 2]].equals(s.iloc[[0, 1, 2]]) # Should be False
True

Problem description

For Series with CategoricalIndex, __getitem__ indexing behaves differently than .loc. On other-indexed series, these accessors return the same result:

>>> s = pd.Series([2, 1, 0], index=[2, 1, 0])
>>> s[[0, 1, 2]].equals(s.loc[[0, 1, 2]]) # Should be True
True
>>> s[[0, 1, 2]].equals(s.iloc[[0, 1, 2]]) # Should be True
False

Expected Output

>>> s = pd.Series([2, 1, 0], index=pd.CategoricalIndex([2, 1, 0]))
>>> s[[0, 1, 2]].equals(s.loc[[0, 1, 2]])
True

Output of pd.show_versions()

0.19.0+479.git
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18941.1001]
Windows Terminal version (if applicable): commit id c97cccb

Steps to reproduce

Open tab too fast and many of them.

Using shortcut key(default ctrl+shift+number) makes easy to open lots of tab at once

Which I was doing was holding shortcut key(crtl+shift+2 to open cmd) for few seconds.

Expected behavior

Only one tab open or Lots of tabs opens without any problem.

Actual behavior

Terminal crashes (without any error message)

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.418]
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

Open up Windows Terminal. Open up any other window. Make sure windows terminal has the useAcrylic set to tru and the opacity set to something like .5. Snap the two windows to either side. When Terminal is in focus the acrylic will work. When it's not it will not.

Expected behavior

The acrylic effect to stay whether or not terminal is in focus.

Actual behavior

The acrylic effect only appears when terminal is in focus