WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I'm seeing webpack in watcher mode writing truncated files. The number of bytes seems to always be either 1682 or 0 - not sure if that's significant somehow. When its 1682 bytes, it cuts off often in the middle of a variable. It seems like it just aborts writing right in the middle of things. When this happens, I see the webpack callback being called many times in a row without any errors or warnings, which my code takes to be a success. Looks like the callback is being called somewhere around 40 times repeatedly, even though I only made one change.

It seems to happen when I try to read from the bundle while its trying to write. In those cases, it would make sense to me if the file wasn't written at all, or if the system returned an error. But when no error is being given back, and the file is partially written - that doesn't make sense to me.

Sorry I don't have more good info, its a weird intermittent problem, and I don't have time to futz with things right now.

Issue 2:
Hey fellas,

I've been using webpack for a few months now, and I had an idea for an optimization plugin. Before I invested a lot of time and energy figuring out how to write it, I wanted to run the idea by you guys to make sure it was sound and hadn't been attempted (and discarded) before.

Basically, I'm wondering if webpack can construct a global strings hash table, insert all strings that are used above a certain threshold, then replace references to those strings with hash table lookups.

Say webpack generates these lines of code right now (in multiple modules that are eventually output to the same bundle):

var some_var = "some string";

var some_other_var = "some string";

var some_other_other_var = "some string";

Could it instead generate this code:

var strings = { a: "some string" };

var some_var = strings.a

var some_other_var = strings.a

var some_other_other_var = strings.a

Hoisting all strings seems like it wouldn't be wise, so I was planning on configuration options for frequency and length to determine what strings were hoisted to the lookup table.

So my questions before I dive in and get to work on something:

Is this possible with the API webpack exposes to plugins?

Has this been attempted and rejected before?

Thanks in advance!
Issue 1:
Black screen after first click on close button. Application closes after second click on close button.

Reload works fine.

electron-prebuilt 0.36.6

electron-rebuild 1.1.2

os windows 8.1

Issue 2:
[7136:0129/081452:FATAL:scoped_handle.cc(44)] Check failed: false.
Backtrace:
(No symbol) [0x00C8D517]
(No symbol) [0x00C87A57]
(No symbol) [0x00CBAEBF]
(No symbol) [0x00CBAF01]
(No symbol) [0x00CB100B]
(No symbol) [0x00CB0A0B]
(No symbol) [0x00C33318]
(No symbol) [0x00C334E7]
(No symbol) [0x00BDEF65]
(No symbol) [0x00BDF273]
v8::TypeSwitch::match [0x5A01A96E+651326]
v8::Locker::IsLocked [0x59F09D1C+804588]
v8::Locker::IsLocked [0x59F0C9CD+816029]

Steps to reproduce

$ npm install -g iron-node;
$ iron-node;
#press Ctrl+w

Just tried to reproduce but this happens only in distributed version.

Windows 10 . Electron 0.36.5.

ref.: s-a/iron-node#86
Issue 1:
I'm submitting a ... (check one with "x")

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

When setting the input type via a property the resulting value of a FormControl/FormGroup after input change is not correct

e.g.

inputType = 'number';
formControl = new FormControl(789);

<input [type]="inputType" [formControl]="formControl">

After updating the value in the input field the value of the formControl is a string and NOT a number.

When setting via type="number" the value is correct (a number).

Expected behavior

To get the value of the form control in the correct type

Minimal reproduction of the problem with instructions

In this plunker the wrong behaviour is shown:

https://plnkr.co/edit/i9Spc10kUCIwtGYx8Vkn?p=preview

Please tell us about your environment:

Angular version: 4.1.1

Browser: all

Language: TypeScript 2.2

Issue 2:
in creating a options list that allows the user to change different settings i found a problem with the type checkbox . take this component

(function(app){
app.testing=ng.core.Component({
selector:"testing",
template:"<input type='checkbox' [(ngModel)]='testing'/>"+
"<template ngFor #item [ngForOf]='list'>"+
"<input [type]='item.type' [(ngModel)]='item.value'/>"+
"</template>"
}).Class({
constructor:[function(){
this.testing=true;
this.list=[
{type:"checkbox",value:true},
{type:"text",value:"hello world"}
];
}],
});
})(window.app||(window.app={}));

because of the ngFor loop combining with the dynamic setting of inputs and their types ngModel does not work on the second checkbox although it does on the first which is not dynamically set. im guessing this is a problem with how ngModel determines that the input is type checkbox. a example of this can be found here

sorry to those of you who work in typescript i was not able to use typescript so it is in plain es5. i hope you can still interpret what its meaning and maybe someone can translate it to typescript.
Issue 1:
Version

2.6.14

Reproduction link

github.com

Steps to reproduce

Just follow the steps as mentioned in the repo.

What is expected?

Browser based template compiler should report error about wrong template syntax.

What is actually happening?

100% CPU usage with OS crash

This happens on Windows with CRLF line endings. The template compiler just gets stuck in an infinite loop in the browser.

Issue 2:
Version

2.5.17

Reproduction link

https://codesandbox.io/s/6j7kz64znr

Steps to reproduce

When using two tags like and in a template of a single file component, with some white space in between.

Examples (as in the link)

<div>
<br />
<a href="https://vuejs.org/">Vue.js</a>

<span>is nice</span>.
</div>

results in `Vue.jsis nice.'

What is expected?

Expected is the regular handling of white space in browsers that remove all, but one white space.

What is actually happening?

The last space is removed.

https://codepen.io/anon/pen/RqEoOr shows the regular handling of this piece of html in a browser (without other css options set).

The problem was noticed when trying to translate text with vue-gettext, where is poses an extra challenge, see Polyconseil/vue-gettext#80
Issue 1:
Challenge http://freecodecamp.com/challenges/waypoint-use-appendto-to-move-elements-with-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-create-a-javascript-slot-machine has an issue.

The four Javascript slot machine exercises all display the JS section of the code incorrectly. Presumably fccss is supposed to be <script>, and likewise fcces is supposed to be </script>.
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-serial/2221/

Failed: [k8s.io] Rescheduler [Serial] should ensure that critical pod is scheduled in case there is no resources available {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rescheduler.go:67
Expected error:
<*errors.errorString | 0xc820ac50c0>: {
s: "Error while waiting for replication controller kube-dns-v19 pods to be running: Timeout while waiting for pods with labels \"k8s-app=kube-dns,version=v19\" to be running",
}
Error while waiting for replication controller kube-dns-v19 pods to be running: Timeout while waiting for pods with labels "k8s-app=kube-dns,version=v19" to be running
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rescheduler.go:66

Previous issues for this test: #31277 #31347 #31710

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-soak-continuous-e2e-gce/6486/

Failed: [k8s.io] Rescheduler [Serial] should ensure that critical pod is scheduled in case there is no resources available {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rescheduler.go:67
Expected error:
<*errors.errorString | 0xc820b819e0>: {
s: "Error while waiting for replication controller kube-dns-v19 pods to be running: Timeout while waiting for pods with labels \"k8s-app=kube-dns,version=v19\" to be running",
}
Error while waiting for replication controller kube-dns-v19 pods to be running: Timeout while waiting for pods with labels "k8s-app=kube-dns,version=v19" to be running
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/rescheduler.go:66

Previous issues for this test: #31277 #31347
Issue 1:
In Windows 10, when Numpy has overflow it shows a wrong number without error.

In Linux it doesn't have this problem.

import numpy as np
a= [4, 7, 6, 5, 4, 5, 6, 8, 2, 8, 4, 8, 9]
print (np.prod(a))
>> -579076096

The correct one is

import numpy as np
a= [4, 7, 6, 5, 4, 5, 6, 8, 2, 8, 4, 8, 9]
print (np.prod(a, dtype='int64'))
>> 23514624000

Numpy should show some errors of overflow

Related issue

Issue 2:
This has come up before, but I'm not sure we have a canonical issue.

Historically in python 2:

builtins.int is mapped to np.int_ (C long), since builtins.int is stored as a C long

builtins.long is mapped to np.longlong (C long long), since builtins.long is infinite precision and that's the largest available integer type

# python 2.7
>>> np.dtype(int).char
'l'
>>> np.dtype(long).char
'q'

Note the above output only reflects the state of windows - other platforms have sizeof(long) == sizeof(long long), so the distinction isn't important.

In python 3, builtins.int has been removed, and builtins.long has been renamed to __builtins__.int. Yet:

# python 3.5
>>> new_long = int
>>> np.dtype(new_long).char
'l' # smaller than it was on python 2

This means that python code translated from 2 to 3 by replacing long with int will start behaving differently:

# python 2
>>> np.array(10**10, dtype=long)
array(10000000000L, dtype=int64)

# python 3 translation
>>> np.array(10**10, dtype=int)
OverflowError: Python int too large to convert to C long

Since this affects users transitioning from 2 to 3, I think it's important that we get it fixed in 1.16, which will be the last version that transitioning users can test both version of python against.

The current implementation, introduced in aa7be88 by @pv, is:

#if !defined(NPY_PY3K)
if (obj == (PyObject *)(&PyInt_Type)) {
check_num = NPY_LONG;
}
else if (obj == (PyObject *)(&PyLong_Type)) {
check_num = NPY_LONGLONG;
}
#else
if (obj == (PyObject *)(&PyLong_Type)) {
check_num = NPY_LONG;
}
#endif

I'd propose it should have been:

#if !defined(NPY_PY3K)
if (obj == (PyObject *)(&PyInt_Type)) {
check_num = NPY_LONG;
}
else
#endif
if (obj == (PyObject *)(&PyLong_Type)) {
check_num = NPY_LONGLONG;
}

Ie, treating PyLong_Type in python 3 just as we always did in python 2.
Issue 1:
Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version: 0.6.2951.0

Steps to reproduce

Set the historySize of a terminal profile to a sufficiently large number. (I modified the default profiles in my testing)

32747 or larger for powershell

32797 or larger for wsl

Create a new terminal tab using the modified profile

Record the current reported terminal size

Use $Host.UI.RawUI.WindowSize.Width; $Host.UI.RawUI.WindowSize.Height for powershell

Use tput cols; tput lines for wsl

Resize the terminal window

Record the new reported terminal size

Expected behavior

Resizing the terminal window should change the reported terminal dimensions.

Terminal resize behavior should be unaffected by historySize.

Actual behavior

When the historySize profile setting is sufficiently large resizing the terminal window does not change the reported terminal dimensions.

Issue 2:
Description of the new feature/enhancement

This one is a "nice to have", but I'd love to be able to stack tabs and tile them side-by-side (ex. a powershell tab on one half, and a WSL tab on the other half). This'd help my efficiency when I need to be testing my work on Windows and Linux at the same time.

Proposed technical implementation details (optional)

Effectively, I'd like something akin to Vivaldi's tab tiling at a minimum, but control on the tier of say, i3wm would be amazing. I should be able to drag a tab over another, and have them drop into a stack. I should then be able to (in some context menu) be able to set up the layout of the windows in the stack.
Issue 1:
@griesemer suggested this was worth looking into, as does a TODO by @rsc in syntax.go.

@josharian described some initial attempts at this last year on golang-dev. @rsc also pointed out that a nil []*Node takes up 3x as much space as a nil *NodeList, so it might be desirable to use *[]*Node for variables that are commonly nil.

I've been playing around with this with some success. One small gotcha I've noticed is that the "Phase 2" and "Phase 3" typecheck calls can append new Nodes to xtop, so those phases must not use range iterations otherwise they'll stop prematurely without iterating over the newly appended Nodes.

Filing an issue to track discussion/progress.

Issue 2:
1. What is a short input program that triggers the error?

package main
import "fmt"
func main() {
lg := 1 << 1
i := 1 << uint64(lg)
fmt.Printf("i = %v\n", i)
}

Note that the program compiles just fine if you were to inline the value of 'lg' in the
following line.

2. What is the full compiler output?

bits.go:5: internal compiler error: agen OREGISTER

3. What version of the compiler are you using? (Run it with the -V flag.)

8g version release.r57.1 8294
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

To not hide overflow of body & make things shift when scrollbar disappears.

Current Behavior

Hides overflow of body.

Steps to Reproduce (for bugs)

Have content within <body> tag that causes it to overflow or <body> has style of overflow: visible

Open select drop down

Context

It messes with styling that relies on body having overflow content. Below is a sample of what's happening on the demo site. Notice the scroll bar vanishing as soon as the menu pops up.

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.24

React
v16.2.0

browser
61.0.3163.79

Issue 2:
Description

The password field in android contains an eye icon that when clicked shows the password (until released)

Thought it should have been implemented in the material ui too.

Images & references

https://medium.com/@moyinoluwa/password-visibility-toggle-android-support-library-revision-24-2-0-98b422087e5a

Versions

Material-UI: 0.17.0

React: 15.4.2

Browser: Chrome 57.0.2987.133 (64-bit)
Issue 1:
In the following, the hue has no effect (seaborn 0.11.1 as well as current master)

tips = sns.load_dataset("tips")
sns.boxplot(data=tips, y='tip', hue='smoker')

It takes effect if something like x='sex' is added.

Thanks for creating a great package.

Issue 2:
Problem

When only y is specified to violinplot it does not consider the argument to hue.

tips = sns.load_dataset("tips")
sns.violinplot(data=tips, y='total_bill', hue='smoker')

Expected

There should be created two plots, one where smoker is yes and one where smoker is no.

Example when x is specified

tips = sns.load_dataset("tips")
sns.violinplot(data=tips, x='day', y='total_bill', hue='smoker')
Issue 1:
This was asked a long time ago, and I just ran into a similar need. It would be nice to be able to easily make a filled step plot. The solutions I've come up with are suboptimal.

http://www.mail-archive.com/matplotlib-users@lists.sourceforge.net/msg13072.html

Issue 2:
Hi,

I think the fill_between function should take a drawstyle option. It would be both handy and consistent.

Here is a post from someone else requesting the feature, with a figure illustrating why this is needed:

http://old.nabble.com/fill_between-with-drawstyle-steps--td30172277.html

thank you
Issue 1:
Challenge Use a CSS Class to Style an Element has an issue.

User Agent is: Mozilla/5.0 (Linux; Android 5.1.1; SM-T670 Build/LMY47X) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.89 Safari/537.36.

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

My code:

<style>
.red-text {
color: red;
}
</style>

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

<p>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>

I have made all required changes, but it still says the h2 element isn't red. I have tried entering the changes in a different order, and have tried clearing browser history and cache. Nothing seems to fix the issue.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-a-specific-child-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

CODE:

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

No nth-child works (have tried 0, 1, 2, 3). 2 visibly works, but "The second element in each of your well elements should bounce.

Visibly working (but not 'marked as correct'):

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
$("#target1").parent().css("background-color", "red");
$("#right-well").children().css("color", "green");
$(".well:nth-child(2)").addClass("animated bounce");
});
</script>

jQuery Playground

#left-well

#target1
#target2
#target3

#right-well

#target4
#target5
#target6
Issue 1:
Just to play safe it is better to place "use strict" inside function to avoid concat issues in future.

Original

import {a} from './a.js';

Expected

define(["exports", "./a.js"], function(exports, _a) {
"use strict";
var a = _a.a;
});

Actual

"use strict";

define(["exports", "./a.js"], function(exports, _a) {
var a = _a.a;
});

The same is for UMD.

It is possible to fix it by placing _moduleFormatter transformer after useString. But I am not sure that it is a good way.

Issue 2:
Issue originally reported by @hzoo in babel/babel-preset-env#91

{
"presets": [
"env", {
"targetPreset": "experimental-stage-3" // default to latest like it is currently,
"targets": {
"browsers": ["last 2 versions"]
},
"exclude": ["transform-regenerator"],
}
]
}

TLDR - figure out how we should include stage-3 plugins.

Oh man naming is hard: basically there's a difference between the "target javascript" you want to write in. What is currently "targets" is the list of environments you support (why didn't I just call it "environments" when the preset is preset-env lol 🤔 ).

The values of this option could potentially be any year, latest, or stage 3 (basically the current official presets that we have). In reality I think the only ones we care about would be latest and stage 3. The reason why we didn't add stage-3 earlier was because I kept thinking about the latest spec rather than forgetting that at stage-3 browser vendors will start implementations. Many projects/companies choose to target stage-3 (and if you are doing lower without codemods or serious consideration of the consequences then there will be issues and that's why we have been discussing #4914 and others).
Issue 1:
Challenge use-hex-code-to-mix-colors has an issue.

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

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

<style>
.dodger-blue-text {
color: #1e90ff;
}
</style>

<h1 class="dodger-blue-text" style="color: rgb(30, 144, 255)">I am dodger blue!</h1>

Issue 2:
Challenge use-hex-code-to-mix-colors has an issue.

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

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

<style>
.red-text {
color: #ff0000;
}
.green-text {
color: #00ff00;
}
.dodger-blue-text {
color: #1e90ff;
}
.orange-text {
color: #ffa500;
}
</style>

<h1 class="red-text">I am red!</h1>

<h1 class="green-text">I am green!</h1>

<h1 class="dodger-blue-text">I am dodger blue!</h1>

<h1 class="orange-text">I am orange!</h1>

```

Screenshot:
![image](https://cloud.githubusercontent.com/assets/3306170/18378269/47f34348-766c-11e6-8fb7-6e2da365ced7.png)
Issue 1:
Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if any

I have reproduced the issue with at least the latest released version of superset

I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

0.28.1

This bug did appear somewhere in the past 12 months or so. It's not recent, and is unrelated to the many changes that appeared in 0.28.

Expected results

There should be only one tooltip instance

Actual results

Sometimes a tooltip get "stuck". Very similar to bugs that were fixed by #2096.

Steps to reproduce

I've been unable to find a recipe for consistent reproduction, but the bug happens to me multiple times per day.

Browser: Chrome on a mac.

Issue 2:
Hi Superset people! I need your wisdom once again. Is it even a Superset issue? Or an nvd3 one?

Is there any chance for a fix or a workaround? Thanks in advance!

I have checked the superset logs for python stacktraces and included it here as text if any

I have reproduced the issue with at least the latest released version of superset

I have checked the issue tracker for the same issue and I haven't found one similar

Superset version 0.15.0 and 0.15.1

Expected results

Legend not burning into the video memory.

Actual results

Steps to reproduce

It happens almost every time if I have the mouse cursor over the chart while the chart is (re)loading.