WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bug report

Bug summary

The marker edges are not painted nicely on the edge of the marker.

Code for reproduction

import matplotlib.pyplot as plt
x = [42,43,44]
y=[42,43,44]
plt.scatter(x,y,alpha=0.7,sizes=[500], linewidths=[15], marker='s')
plt.savefig('sample.pdf')

Actual outcome

Expected outcome

The edges should go cleanly around the marker boundary.

Matplotlib version

MacOS 10.14.5

Matplotlib v3.1.1

Matplotlib backend: MacOSX

Python 3.6.7

Issue 2:
Bug report

Bug summary

Marker edge overlaps with marker and the edge appears to be double the width specified. This becomes obvious when you use alpha transparency and a very larger point marker with a large edge width or in the case where I noticed it a small figure (about 2 inches wide) with the default rcParams.

Code for reproduction

Case 1: very large point with a large edge width

plt.figure()
plt.plot(1, '.', ms=200, mew=50, alpha=0.5)

Case 2: very small figure with default rcParams: markersize = 8, markeredgewidth=1.0

plt.figure(figsize=(1,1), dpi=600)
plt.plot(1, '.', alpha=0.5)

Actual outcome

In this figure I have markersize=200 and markeredgewith=50. There is an ugly ring and it looks as if the marker edges are two times wider (100 instead of 50) than I asked.

Now in this figure I have markersize=200 and markeredgewidth=99. There is a single pixel in the center that is faded blue thus the markeredges are definitely twice what I asked for. If I set the markeredgewith to 100 I get a solid core.

Expected outcome

I would expect that the marker edge would line up perfectly with the marker core. In this plot I set markersize to 300 (200 plus 2*50 edges) to get the same size as the original without the ugly ring.

Matplotlib version

Operating system: macOS 10.13

Matplotlib version: 3.0.2

Matplotlib backend: both with Qt and PGF backends

Python version: 3.7.2

matplotlib installed via pip
Issue 1:
Bug.

If I put several input type="radio" with same name (as in jsfiddle example below) onChange handler triggered only once for individual input when mouse click on input happen.

<input type="radio" name="some" onChange={...} />
<input type="radio" name="some" onChange={...} />
...

Example: https://jsfiddle.net/Bacher/jxrar3ke/7/

Try to click on different radio inputs several times. Next clicks has no console.log output.

I expect trigger onChange every time when I click on non-selected radio input.

Bug reproduces in several latest versions of React, at least 15.6.0 and 15.6.1.

My OS is Ubuntu. I try in latest Chrome and latest Firefox.

Issue 2:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

In React 15.6.1, this behaviour is changed; In 15.5.4, it fires the change event reliably.

15.6.1 - https://codesandbox.io/embed/VPA42ZnRo

15.5.4 - https://codesandbox.io/embed/JZ0mnE5oy

You'll need to have the console open to get the debugger statement.

In 15.6.1, the first change fires, but all subsequent changes do not fire. In 15.5.4, all changes fire.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

React 15.6.1 vs React 15.5.4; Chrome latest stable.
Issue 1:
Description of the new feature/enhancement

If some link is shown in the terminal, it would be nice to allow open it whether clicking over it.

Proposed technical implementation details (optional)

Maybe ctrl+left mouse key as default combination could produce a similar behaviour like VSCode integrated terminal.

If the link uses a file path such as C:\myfile.txt, clicking opens it.

If the link is an URL, then default system browser will open it in a new tab.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.476]
Windows Terminal version (if applicable): Windows Terminal (Preview) Version: 0.5.2762.0

Steps to reproduce

open multiple tabs in terminal. The switch tab between them

Expected behavior

I can see which tab is active clearly.

Actual behavior -- Could we use a very different color to identify the active tab ?

Please see bellow picture. it's hard to figure out which tab is active when my monitor is not so good. I have to chick on each tab to find the active one.
Issue 1:
I build and install Atom on my Gentoo.

But when I open any file I see chrome console that contains Uncaught Error: spawn ENOENT.

Issue 2:
I'm getting an error when ever lint tries to run on my *.ts files:

activate linter-csslint init.coffee:8
activate linter-jscs init.coffee:9
activate linter-jshint init.coffee:8
activate linter-scss-lint init.coffee:7
Window load time: 1394ms /Applications/Atom.app/Contents/Resources/app/src/window-bootstrap.js:18
command and arguments ["tslint", "-t", "json", "-f", "/var/folders/h5/qvc0ydkj0bz9gntxfv4xpt7m0000gn/T/11462-1252-1nivsndsource.ts"] linter.coffee:68
is node executable: false linter.coffee:91
Uncaught Error: spawn ENOENT util.js:682
exports._errnoException util.js:682
ChildProcess._handle.onexit child_process.js:857
(anonymous function) child_process.js:1005
_tickCallback node.js:605
stderr execvp(): No such file or directory linter.coffee:110

My thinking is that it isn't tslint at it was working about 4-5 days ago, but today when I went to open my *.ts files, I started getting the above, but it could have also been the 0.107.0 release as well. Not sure.
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

6.0.11 and v7.0.0-beta.6

Operating System:

MacOs Mojave Version 10.14.5

Expected Behavior

Hi, I need to create a multi-threaded application. I used two threads options, but both don't work.

First option is worker_threads https://nodejs.org/api/worker_threads.html

Second option is web workers https://electronjs.org/docs/tutorial/multithreading

Actual Behavior

When i used worker_threads i got this error: Uncaught Error: The V8 platform used by this instance of Node does not support creating Workers

When i used web workers I ran into a threads creation limit. I can create max 240-243 threads, but when i add 1 more thread - it crash. I have free 7 GB RAM, but it crush anyway. Btw, in activity monitor it'll show x2 threads count, than i created. If i created 240 threads - it'll show 480+ threads in activity monitor

To Reproduce

For reproduce worker_threads error:

const { Worker } = require("worker_threads") new Worker("./src/workers/profile.js") // need provide a path to file

For reproduce web workers error:

for( let i = 0 ; i < 250 ; i ++ ) { new Worker("./src/workers/profile.js") // need provide a path to file } // 240 = no crush, 250 will crush

Screenshots

worker_threads

Web workers

This screenshot shows that were created x2 threads, than I actually create (as I described above). Were created 240 threads, but in fact 486 is displayed

This screenshot shows what happens when I add one thread, after creating 240 web workers

Additional Information

If i can provide more info for you - tell me it please !

Issue 2:
Issue Details

Electron Version:

v5.0.2

Operating System:

Windows 10

Expected Behavior

On app ready start nodejs worker which consoles string.

Actual Behavior

App crash immediately after run

To Reproduce

git clone https://github.com/BorysTyminski/electron-issue.git

cd electron-issue

npm install

npm run start

Additional Information

I used electron-forge to quick build app.
Issue 1:
I'm using Atom 0.196.0 on Windows,

when deleting a folder and this folder is open at atom folder explorer (enpanded on left bar)

EPERM is thrown.

Expected Behavior:

Atom shouldn't lock the folder,allowing to delete it from another running program

After the folder is deleted, atom must reload the file explorer and do not list that folder nor it's files

Issue 2:
Instead of vaguely explaining, here are the steps for reproducing the bug:

If you have a Yeoman-created project folder i.e. generator-webapp created project, run grunt serve. It'll create a .tmp file, and I'll assume you haven't had one at first.

When everything goes well expand the folder .tmp in Atom so you can see the subfolders inside.

Stop the grunt process.

Run grunt serve again, and it will run grunt-contrib-clean to delete .tmp.

It won't. .tmp will still exist as a "corrupted file" and you can't delete it by the Windows Explorer. Command line will show Warning: Unable to create directory [path to .tmp folder]" (Error code: EPERM). Use --force to continue. when trying to create a new .tmp folder.

Go to Atom and try to delete it, and the Dev Tools will show the same error: Uncaught Error: EPERM, operation not permitted: [path to .tmp folder]. All you need to do is close the folder again on the sidebar to remove the folder. I also tried the same method to Sublime Text, and it doesn't do the same, so I assume there's a clash between grunt-contrib-clean and Atom's way of handling files.

Atom is 0.123.0, and Windows is 8.1. Command line running Grunt is running as Administrator.
Issue 1:
Version

2.6.11

Reproduction link

https://codepen.io/davegould41/pen/qBRqyRo?editors=101

Steps to reproduce

Create an input element with event modifier v-model.number="num"

try typing .01

notice it resets the value to 1

(inputting 0.01 works though)

What is expected?

If the user enters .01 the input element should have the value of .01

What is actually happening?

.number input modifier is removing decimal on user input

If a user inputs .01 they the input element will capture as 1

I realize that javascript evaluates .0 as 0 but this is a common scenario when adding numbers to an input element

Issue 2:
Version

2.5.8

Reproduction link

https://jsfiddle.net/50wL7mdz/79189/

Steps to reproduce

Included in fiddle

What is expected?

Input type='number' should not clear values, accept stings formatted in different locales. v-model.number should not return string.

What is actually happening?

Input value is cleared sometimes, v-model.number returns "" for "" and partially typed numbers.

This issue started with topic on forum https://forum.vuejs.org/t/extra-directive-for-number-inputs/22438, it was suggested to open an issue for that. Here is original post:

Hi!

I've found that v-model.number has limitations and requires some boilerplate in some cases. This is mostly because input[type="number"] returns '' for partially input numbers (like 1.). Here are some problems with it:

App has no difference when input is either empty or invalid/partial.

Bound attribute has to be of [String, Number] type.

'', undefined, and 0 are falsy values. This leads to val !== '' checks in all places this attribute is used.

2nd and 3d issues can be solved with computed property, but it's hard to implement for nested ones and array of values.

I came to using separate field for casted values:

<input
type='number'
v-model='obj.val'
@input='$set(obj, "valCasted", _nOrNull($event.target.value))'
/>

I wanted to it implement with custom directive (like v-model-number='obj.valCasted'), but I see that v-model is handled differently by compiler. This way it can automatically use $set when property is not defined on object. But I have not found how this can be implemented with custom directives.

So here are questions :) :

Is there a better way to work with input[type="number"]?

If not:

Can this be implemented with custom directives as convenient as v-model is?

Should this be added to vue?

After that post I've tried to implement custom component, it's included in fiddle, but it also has some issues.

I've also added different types of inputs to fiddle to check their behaviour and checked against different locales.

Thank you!
Issue 1:
I built a project using (Merge, merge) layer once, and use share layer in another. The problem I can't find any documentation that explains how merge or share layer works like convolution or max-pooling layers.

I will be grateful if anyone can direct me or suggest some paper to me ???

Issue 2:
Check that you are up-to-date with the master branch of Keras. You can update with:

pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

ImageDataGenerator.flow() expects numpy arrays and does not accept but TF tensors containing the same image data. Should this be updated to accept TF tensors of images and labels, and are there any plans to do so?

Proposed example code of loading such data from a TFRecord for semantic segmentation:

import tensorflow as tf
from keras.preprocessing.image import ImageDataGenerator

# tfrecord_filenames_queue : tfrecord filename queue
# String queue object from tf.train.string_input_producer()
reader = tf.TFRecordReader()

_, serialized_example = reader.read(tfrecord_filenames_queue)

features = tf.parse_single_example(
serialized_example,
features={
'height': tf.FixedLenFeature([], tf.int64),
'width': tf.FixedLenFeature([], tf.int64),
'image_raw': tf.FixedLenFeature([], tf.string),
'mask_raw': tf.FixedLenFeature([], tf.string)
})

image = tf.decode_raw(features['image_raw'], tf.uint8)
annotation = tf.decode_raw(features['mask_raw'], tf.uint8)

height = tf.cast(features['height'], tf.int32)
width = tf.cast(features['width'], tf.int32)

image_shape = tf.pack([height, width, 3])
annotation_shape = tf.pack([height, width, 1])

image = tf.reshape(image, image_shape)
annotation = tf.reshape(annotation, annotation_shape)

# This will do preprocessing and realtime data augmentation:
datagen = ImageDataGenerator(
featurewise_center=False, # set input mean to 0 over the dataset
samplewise_center=False, # set each sample mean to 0
featurewise_std_normalization=False, # divide inputs by std of the dataset
samplewise_std_normalization=False, # divide each input by its std
zca_whitening=False, # apply ZCA whitening
rotation_range=0, # randomly rotate images in the range (degrees, 0 to 180)
width_shift_range=0.1, # randomly shift images horizontally (fraction of total width)
height_shift_range=0.1, # randomly shift images vertically (fraction of total height)
horizontal_flip=True, # randomly flip images
vertical_flip=False) # randomly flip images

datagen.flow(image, annotation,
batch_size=32)
Issue 1:
Code:

interface Foo {
}

interface Bar implements Foo {
}

Expected (from old compiler):

(4,15): Interface declaration cannot have 'implements' clause.

Actual (current):

(4,15): '{' expected.

(4,26): ';' expected.

(4,30): ';' expected.

Issue 2:
Now with the dedicated Path type (#5462), we should be able to minimize the number of normalization in tsserver by changing all the file name strings to the Path type. We also have many duplicated file name normalization in program.ts and other places.
Issue 1:
UPDATED DESCRIPTION:

We now allow the original problem, but some corner cases are still unhandled. See comments below.

ORIGINAL DESCRIPTION:

Where clauses right now require predicates to contain type parameters, as in:

trait Foo {
fn foo(&self);
}

struct Bar<T> {
x: T,
}

impl<T> Foo for Bar<T> where T: Foo {
fn foo(&self) {
self.x.foo()
}
}

But we cannot add constraints on non-generic types:

struct Baz { x: i32 }

impl Foo for Baz where i32: Foo {
fn foo(&self) {
self.x.foo()
}
}

Will error out with:

test.rs:15:1: 19:2 error: cannot bound type `i32`, where clause bounds may only be attached to types involving type parameters
test.rs:15 impl Foo for Baz where i32: Foo {
test.rs:16 fn foo(&self) {
test.rs:17 self.x.foo()
test.rs:18 }
test.rs:19 }

In hand written code this usually won't come up, but this would be really helpful for a code generator like macro_rules! or #[derive], especially when dealing with associated types. Currently the only way to know if a type is generic or not is to manually walk it and see if any of the type paths start with the same name as a type parameter. If so, add that type to the predicate list. Instead, it would be much simpler if we could just add all the types listed in a field or enum to the predicate list and let the type checker report an error if one of those types doesn't implement the trait.

cc @nikomatsakis, @jroesch

Issue 2:
Today’s rust-nightly-x86_64-unknown-linux-gnu.tar.gz is 125MiB in size. I did a make dist-tar-bins which output the same tarball, but only 88MiB in size. This is 70% of whatever we publish to s3.

I took liberty to also test:

xz (the default level, -6) → 69MiB (55% original);

xz -9 → 59MiB (47% original, but has high memory requirements to decompress)

bz2 → 82MiB (65% original);

lzma → 69MiB, but took longer than xz.

I strongly propose to either migrate to a more modern compression algorithm (xz) or at least investigating why gzip does such a bad job on the build bots.

cc @brson
Issue 1:
Windows 7, atom already opened with the window in the background.

When I open a file via the explorer, the symbol in the task bar is blinking but atom doesn't come to the front.

Is this a wanted behavior?

(I couldn't find any existing issue. If this is the case, please let me know)

Issue 2:
When Atom is restored but hidden behind several windows. "Open with Atom" right click function should send it to the front.
Issue 1:
Description of the problem

InstancedMesh instancing breaks if the supplied material has been already been used.

If a .clone() of the material is passed into the InstancedMesh, it works.

Repro showing the issue... remove the .clone() operation to see instancing break.

https://jsfiddle.net/4u1aox7j/

Three.js version

Dev

r117

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

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

Issue 2:
Description of the problem

I'm having a problem where the InstancedMesh method setMatrixAt seems to fail (the matrix positions doesn't change visually) whenever I add another object with the same material object (not a clone) in the scene. No log/warning/errors are emitted.

The following briefly illustrates:

var geometry = new THREE.BoxBufferGeometry();
var material = new THREE.MeshStandardMaterial( { roughness: 0, envMap: texture });
var mesh1 = new THREE.Mesh( geometry, material );
mesh1.position.set(0, 1, 0);
scene.add( mesh1 ); // removing this line makes the instanced mesh work as intended
mesh = new THREE.InstancedMesh( geometry, material, 9 ); // same material usage
scene.add( mesh ); // This works and I can see both meshes in the scene.

var dummy = new THREE.Object3D();
dummy.position.set( 1, 5, 1 );
dummy.updateMatrix();
mesh.setMatrixAt( 0, dummy.matrix ); // Nope, doesn't work, it just stays where it's at.
mesh.setMatrixAt( 1, dummy.matrix ); // Rotation seems to be applied, but position doesn't.
// It looks like every instance is at the same place, but I don't know.

Note that if I use material.clone() at the instanced mesh declaration, the problem also goes away / is fixed, but now I have two materials, and I intend to have one for performance reasons.

A live example is available here:

jsfiddle (The problem is that you should see multiple boxes, but only 1 or 2 are visible, remove line 41 to fix)

Three.js version

Dev

r109

r108

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

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

(Not applicable, as far as I know)
Issue 1:
After the update, the new confirm, alert and prompt do not work properly.

Platform: Windows 10 x 86_64

I was able to reproduce the issue in another Windows machine.

let name = prompt("What's your name?");
let sure = confirm(`Is ${name} your real name?`);
if (sure) {
alert("OK, you are sure");
} else {
alert("Well, you are not sure!");
}

Note: The example code from the release blog post do not work as well.

Issue 2:
to reproduce:

Linux (WSL) | Windows

isn't limited to repl
Issue 1:
[Enter steps to reproduce below:]

Open legacy rails(1.2.3) project from ubuntu terminal with command "atom ."

...

Atom Version: 0.165.0

System: linux 3.13.0-43-generic

Thrown From: Atom Core

Stack Trace

Uncaught Error: spawn /usr/share/atom/atom (deleted) ENOENT

At events.js:85

Error: spawn /usr/share/atom/atom (deleted) ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)

Commands

Config

{
"core": {
"autoHideMenuBar": true,
"disabledPackages": [
"atom-rails",
"rails-snippets"
]
},
"editor": {
"fontSize": 21,
"showIndentGuide": true,
"softWrapAtPreferredLineLength": true,
"preferredLineLength": 140,
"softWrap": true,
"softTabs": false
}
}

Installed Packages

# User
No installed packages

# Dev
No dev packages

Issue 2:
TEMPORARY WORKAROUND: ln -s /usr/share/atom/atom "/usr/share/atom/atom (deleted)"

Uncaught Error: spawn /opt/atom/atom (deleted) ENOENT

Atom Version: 0.152.0

System: linux 3.13.0-40-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At events.js:85

Error: spawn /opt/atom/atom (deleted) ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)
Issue 1:
These volumes don't support stats metrics, and yet the errors got printed out periodically for each pod.

I0614 17:01:54.337456 30118 volume_stat_caculator.go:103] Failed to calculate volume metrics for pod kube-proxy-e2e-test-yjhong-minion-group-21rr_kube-system(b7c4ad73450e2cf13c9cb849231754c2) volume kubeconfig: metrics are not supported for MetricsNil Volumes
I0614 17:01:54.337464 30118 volume_stat_caculator.go:103] Failed to calculate volume metrics for pod kube-proxy-e2e-test-yjhong-minion-group-21rr_kube-system(b7c4ad73450e2cf13c9cb849231754c2) volume varlog: metrics are not supported for MetricsNil Volumes
I0614 17:01:54.337544 30118 volume_stat_caculator.go:103] Failed to calculate volume metrics for pod e2e-image-puller-e2e-test-yjhong-minion-group-21rr_kube-system(0d136a4468db307b8063df140402a70e) volume socket: metrics are not supported for MetricsNil Volumes
I0614 17:01:54.337563 30118 volume_stat_caculator.go:103] Failed to calculate volume metrics for pod e2e-image-puller-e2e-test-yjhong-minion-group-21rr_kube-system(0d136a4468db307b8063df140402a70e) volume docker: metrics are not supported for MetricsNil Volumes
I0614 17:01:54.337591 30118 volume_stat_caculator.go:103] Failed to calculate volume metrics for pod node-problem-detector-v0.1-oa8xn_kube-system(b9edf393-3187-11e6-8f11-42010af00002) volume log: metrics are not supported for MetricsNil Volumes

Issue 2:
Many volumes do not support GetMetrics and return an error when called. Because this returns an error, we cannot differentiate from an actual error condition when a volume that does support metrics fails to gather metrics. The latter should be logged and investigated, whereas the former should be silently ignored.
Issue 1:
Trying to create an FTP Extension but I need a way to be able to view the contents on the FTP server. A side bar panel would be great or at least the have access to the folder panel to create a virtual tree for the user to use for navigation.

Issue 2:
One great feature that could be added to VsCode is the possibility to add more "tabs" in the letf area like the Git and the Debug one.

This way one developer can add other things like Sql server browser, github issues and more

If somebody already has an idea to where to add these extension pointe I will be glad to help.