WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

Yes

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Mac OS X 10.13.6

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:

N/A

TensorFlow installed from (source or binary):

binary

TensorFlow version (use command below):

v1.10.0-rc1-19-g656e7a2b34 1.10.0

Python version:

Python 3.6.5

Bazel version (if compiling from source):

N/A

GCC/Compiler version (if compiling from source):

N/A

CUDA/cuDNN version:

N/A

GPU model and memory:

N/A

Exact command to reproduce:

N/A

Describe the problem

Placeholders with shape () gets shape <unknown> after tf.graph_util.convert_variables_to_constants has been run on a graph def.

The expected result is that the shape is kept, as it is for tensors with higher rank.

Source code / logs

import tensorflow as tf

with tf.Graph().as_default(), tf.Session() as sess:
placeholder = tf.placeholder(tf.float32, shape=(), name='placeholder')
output = tf.identity(placeholder)

graph_def = tf.graph_util.convert_variables_to_constants(sess, sess.graph_def, [output.op.name])
print('Before:', placeholder.shape)

with tf.Graph().as_default() as g, tf.Session() as sess:
tf.import_graph_def(graph_def, name='')
placeholder = g.get_tensor_by_name('placeholder:0')
print('After:', placeholder.shape)

Output

Before: ()
After: <unknown>

Issue 2:
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no

TensorFlow installed from (source or binary): pip install tensorflow

TensorFlow version (use command below): v1.10.0-0-g656e7a2b34 1.10.0

Python version: Python 3.6.6 :: Anaconda, Inc.

Bazel version (if compiling from source): N/A

GCC/Compiler version (if compiling from source): N/A

CUDA/cuDNN version: N/A

GPU model and memory: N/A

Exact command to reproduce: Run the program below

Describe the problem

Usually, tf.placeholder(tf.float32, shape=[]).get_shape() is an empty shape, (). However, if you import a specific frozen graph first, the result of get_shape() will be unknown.

Here is an example of a script that reproduces the issue and prints unknown:

import tensorflow as tf

IN_OUT = ['images_ph:0', 'inception_v3/logits/flatten/Reshape:0']

with open('inception-v3.pb', 'rb') as in_file:
graph_def = tf.GraphDef()
graph_def.ParseFromString(in_file.read())
tf.import_graph_def(graph_def, name='', return_elements=IN_OUT)

print('shape result', tf.placeholder(tf.float32, shape=[]).get_shape())

Where inception-v3.pb can be downloaded at: https://storage.googleapis.com/agi-data/models/inception-v3.pb
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 a feature request that matches the one I want to file, without success.

Electron Version

11.2.3

What operating system are you using?

macOS

Operating System Version

macOs Big Sur 11.2.1

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

N/A

Expected Behavior

The app is not crashing.

Actual Behavior

The app crashing sporadically.

Testcase Gist URL

https://gist.github.com/Glebka/b7c6b202d89ea25e3b64d6c504dfd194

I attached a crash report as gist.

Please have a look.

Our app is a corporate messenger with telephony and video meeting capabilities.

The version that is crashing was built for x64 arch and was running using Rosetta on Apple M1 hardware.

The crash occurs sporadically. Users report that may happen suddenly when they navigate thru the UI or start a telephony / video call. We use WebRTC features and WebAssembly, fyi.

The crash I published were caught by Mac OS, despite we have a Sentry crash reporter configured.

I see the stack trace from com.github.Electron.framework is not symbolicated, so, probably not useful.

Could you please suggest how to symbolicate it?

Will appreciate any help on this. Thanks.

Issue 2:
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 a feature request that matches the one I want to file, without success.

Electron Version

11.4.1

What operating system are you using?

macOS

Operating System Version

macOs Big Sur 11.2.1

What arch are you using?

arm64 (including Apple Silicon)

Last Known Working Electron version

N/A

Expected Behavior

App is not crashing.

Actual Behavior

App crashes sporadically.

Testcase Gist URL

https://gist.github.com/Glebka/b4b50c4b4eeec40bcb32fac94d2d154c

I attached a crash report as gist.

Please have a look.

Our app is a corporate messenger with telephony and video meeting capabilities.

The version that is crashing was built for x64 arch and was running using Rosetta on Apple M1 hardware.

The crash I published were caught by Mac OS, despite we have a Sentry crash reporter configured.

Will appreciate any help on this. Thanks.
Issue 1:
sklearn.metrics introduces isclose() in https://github.com/scikit-learn/scikit-learn/blob/master/sklearn/metrics/ranking.py which can leave the unaware data practitioner with hours of debugging.

In very unbalanced classification, probabilities/scores can be very small and yet meaningful. This however will cause unexpected missing precision_recall points due to isclose treating values within 10e-6 as equal.

I'd suggest to place a warning about isclose in the documentation and also replace the absolute epsilon by a relative closeness comparison in order to avoid the problems with small probabilities in unbalanced classification.

Issue 2:
pred=[1e-10, 0, 0]

sol=[1, 0, 0]

metrics.roc_auc_score(sol, pred) # 0.5, wrong, 1 is correct

pred=[1, 0, 0]

sol=[1, 0, 0]

metrics.roc_auc_score(sol, pred) # 1 correct
Issue 1:
When using the Image Bitmap Loader to load in images for sprites the images render upside down. It should be noted that if the image downloaded is not the correct power of 2 and the resizer is fired the images appear the right way up but if they images are the correct power of 2 and the resizer is not called they appear upside down;

let material = new THREE.SpriteMaterial();
let sprite = new THREE.Sprite( material );
sprite.scale.set(5, 5, 5);
sprite.position.copy(props.position);
sprite.userData = props.userData;
scene.add(sprite);
new THREE.ImageBitmapLoader().load( props.imageUrl, (imageBitmap) => {
let texture = new THREE.CanvasTexture( imageBitmap );
material = new THREE.SpriteMaterial( { map: texture } );
sprite.material = material;
sprite.scale.set(5, 5, 5);
}, undefined, function (err) {
console.error("Error loading image", err)
} );

Three.js version

[x ] r107

Browser

[] All of them

[x ] Chrome

Firefox

Internet Explorer

OS

[] All of them

Windows

[ x] macOS

[ x] Linux

Android

iOS

Havent tested on the others

Issue 2:
Description of the problem

Non POT ImageBitmap texture can be upside down.

Demo: https://jsfiddle.net/7do6um2f/ (Use Chrome)

Non POT image can be resized to POT canvas in WebGLRenderer(WebGLTexture). If original image is ImageBitmap and texture.flipY is true, texture will be upside down.

This is from the difference of ImageBitmap API from others. ImageBitmap requires flipY on bitmap creation while others requires on uploading data to GPU (= texture.flipY).

texture.flipY used on uploading data to GPU is ignored for ImageBItmap. But if non POT ImageBitmap is converted to canvas, texture.flipY will have an effect. So texture will be upside down.

texture.flipY has no effect for ImageBitmap so we should force it to false if texture's image is ImageBitmap?

API difference has another issue. (May be it isn't so serious tho.) FlipY and premultiplyAlpha is required on bitmap creation. texture.flipY/premultiplyAlpha used on uploading data to GPU are ignored for ImageBitmap.

So the following code has no effect for ImageBitmap, but the code has effect if ImageBitmap is resized and converted to canvas.

texture.premultiplyAlpha = ! texture.premultiplyAlpha;
texture.flipY = ! texture.flipY;
texture.needsUpdate = true;

Three.js version

Dev

r103

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
E.g. install an extension and open readme and then return:

Issue 2:
We need to explore improving the way that we display warnings, errors and notifications to users. Currently we have a variety of mechanisms (info in status bar, details in quick open, error/warning dialog).

We need a consistent way that prompts the user when there are notifications/errors/warnings for them to pay attention to and a consistent affordance for the user to get a holistic view of all of the notitications/errors/warnings.
Issue 1:
I am now using Electron 0.33.6 for some hours in VS Code and run into an issue that I cannot really reproduce or explain but it happens always after some time of usage (30 minutes). It might be just memory related when memory consumption reaches a certain limit.

What I know is that a process (forked with child_process) is crashing with a SIGABRT signal, which seems to indicate an issue deep down in node or at least in a C++ layer above with memory allocation. We do have a crash dump when this happens: https://gist.github.com/bpasero/bbe9001163baca220057

I will try to reproduce this on Windows tomorrow.

I wonder if this is related or duplicate to: #2889

Issue 2:
When downloading large files inside child process, it crashes with the following:

Electron Helper(65819,0x7fff72367300) malloc: *** error for object 0x7f8063e86ab0: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

Here is the crash dump

Sample code to reproduce the issue can be found here.

It works fine when downloading from the main process (i.e. from index.js). Downloading from child process used to work fine too until electron v0.30.6
Issue 1:
53116ca07207+ tip

This is a bit of a silly example, but the behavior is different on Linux and Windows
nonetheless, and I'm wondering if it might be part of a bigger issue:

package main

import "fmt"

func main() {
n := uint8(0) // or uint16, uint32, uint64...
f := float64(-1) // or float32, but not int32/int64
on := uint8(f) // does not underflow on Windows
// on := uint8(int32(f)) // this works on both platforms
fmt.Printf("on is %d\n", on)
n += on
if n != 255 {
fmt.Printf("n is not 255: %d\n", n)
}
}

On Linux (x64):

# uintunderflow
on is 255

On Windows (x64):

# uintunderflow.exe
on is 0
n is not 255: 0

Issue 2:
This idea originated in #13785 when using OpenBSD's precedent with arc4random(3).

The Go crypto code includes a CSPRNG by default (see src/crypto/rand/rand_unix.go:85). However, it is only used on operating systems that Go doesn't determine to have a reliable, non-blocking randomness sources. Examples of reliable non-blocking randomness sources include a modern /dev/urandom, Linux's getrandom(2), and OpenBSD's getentropy(2).

Many cryptography guides suggest userland CSPRNGs. The possible benefits include:

improving performance by avoiding the vast majority of randomness-related syscalls

Go's CSPRNG fetches 16 bytes of seed entropy for every 1 MB of generated randomness

easing up on the kernel, which may expend considerable effort when serving a Go process's randomness-related syscalls

I remember seeing Poul-Henning Kamp quoted that FreeBSD kernel spends 15% of its time on random number generation

adding some additional mixing to potentially weak OS-supplied randomness

This would be a minimal stopgap. However, the Go currently uses ANSI X9.31 which mixes via AES and kneads in the current nanosecond time, which is better than nothing.

potentially being able to replace math/rand with crypto/rand, which would simplify the codebase and prevent misuse of math/rand

code for deterministic pseudo-randomness could be condensed, and the ability to seed it could be removed

Network applications that use forward secret encryption make the peformance concerns more relevant.

The primary risk is that we would then rely on the soundness and safety of Go's CSPRNG logic. I don't know whether timing attacks are a risk, but that's one issue that came to mind. The CSPRNG backs up to Go's AES implementation, though, so any risks unique to the CSPRNG would have to be outside of that. The fact that uses a standard algorithm (ANSI X9.31) and a strong crypto primitive (AES) gives me confidence. I'm definitely not qualified to rigorously review something like this, though.

This ticket could also entail a review of the existing CSPRNG and whether it could be stronger.

Thoughts? Also, if anyone knows of relevant profiling techniques and targets, please share. I plan on investigating what kind of performance impact this switch would have.
Issue 1:
This issue has been around for quite a while, and I just reproduced it in 0.14.4 and 0.15.1-alpha.1. I looked through all "button" and "ripple" related issues and found no mention of this, so apologies if this is a duplicate.

https://dl.dropboxusercontent.com/u/19969663/ripple_issue.mov

As you can see, this is the latest version of the demos on material-ui.com. Video was taken in chrome on a mac.

Basically, through some sequence of clicks the ripple effect doesn't go away. I've been playing around with it for quite a while and couldn't find consistent repro steps. It also seems to happen much more often on chrome in android as well as safari in iOS. I've noticed this issue in all browsers.

Issue 2:
As our team checked, WebAIM recommends to always specify the scope attribute, so suggesting to make it out-of-the-box for the TableCell for the "head" type.

Mainly, without this attribute screen readers fail to read the table as expected (even if it sounds weird to me personally for special semantic <th> inside <thead> usage).

The scope attribute tells the browser and screen reader that everything within a column that is associated to the header with scope="col" in that column, and that a cell with scope="row" is a header for all cells in that row.

All <th> elements should generally always have a scope attribute. While screen readers may correctly guess whether a header is a column header or a row header based on the table layout, assigning a scope makes this unambiguous.

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

Expected Behavior

The scope attribute is set to "col" for type "head" by default (if not specified manually).

Current Behavior

The scope attribute is not used.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.31
Issue 1:
Environment

Windows build number: 10.0.19041.264
PowerToys version: 18.2

Steps to reproduce

Cannot bind any combination of Windows Key + anything. To reproduce the bug, go to powertoys run, and click inside the box. Press the windows key, and nothing will be bound. I am attempting to bind Windows+Space to powertoys run, and cannot get it to do so.

Expected behavior

I expect the Windows key to be able to be used inside of shortcuts

Actual behavior

Windows key is not able to be used in keyboard shortcuts

Issue 2:
Example commands below. When typing these today into the windows search bar, or Run command, they will open specific control panel items.

ncpa.cpl

inetcpl.cpl

appwiz.cpl
Issue 1:
Hi,

Tried to build latest archive, this is what I get (Fedora 20/rawhide 64-bit)

exception on 2: ERROR: BoundsError()
in setindex! at ./array.jl:309
in colval at ./datafmt.jl:317
in store_cell at ./datafmt.jl:195
in dlm_fill at ./datafmt.jl:296
in dlm_fill at ./datafmt.jl:309
in readdlm_string at ./datafmt.jl:271
in __readdlm_auto#85__ at ./datafmt.jl:59
in __readdlm#83__ at ./datafmt.jl:49
in __readdlm#82__ at ./datafmt.jl:47
in anonymous at ./no file
in runtests at /builddir/build/BUILD/julia-master/test/testdefs.jl:6
in anonymous at ./multi.jl:847
in run_work_thunk at ./multi.jl:613
in anonymous at ./task.jl:847
while loading readdlm.jl, in expression starting on line 4
ERROR: BoundsError()
in anonymous at ./task.jl:1350
while loading readdlm.jl, in expression starting on line 4
while loading /builddir/build/BUILD/julia-master/test/runtests.jl, in expression starting on line 46
make: *** [all] Error 1

Issue 2:
@pao asked my to file an issue about the url pulled into METADATA while discussing my pull request for the Roots package here JuliaLang/METADATA.jl#202

When I ran Pkg.pkg_origin("Roots"), apparently the wrong github URL was being pulled in. It should have been: git://github.com/jtravs/Roots.jl.git rather than git@github.com:jtravs/Roots.jl.git.

The output of git remote -v run in my packages repository is:

origin git@github.com:jtravs/Roots.jl.git (fetch)
origin git@github.com:jtravs/Roots.jl.git (push)
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-override-class-declarations-with-inline-styles has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Twice click Run Code button to submit the code. Is it friendly to users?

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-iterate-over-arrays-with-map has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Even though the assertions are right, you need to hit the run code button twice to advance in the waypoints in the "Object Oriented and Functional Programming" section. It isn't really a major issue, just a mild annoyance.
Issue 1:
See #4303 (comment) for details.

Issue 2:
We'd like VS Code and the Node Debugger to support Live Reloading Scenarios. The current behavior is preventing React-Native users from having a good experience: microsoft/vscode-react-native#74

Currently it's not supported so modifying breakpoints while the program is running can have weird results (Breakpoints set in one line, appear in another line, or get deleted completely).

Things that we'd like to be supported are:

Be able to edit a file in memory, and set a brekpoint before saving the file, so if there is any source map associated at all with this file at all, it'll map to the wrong thing, so VS Code would need to Remember the line where the breakpoint was set, and wait until the proper source map was loaded before actually setting the breakpoint.

Be able to edit a file, save it, and set breakpoints before the recompilation process is finished, so initially it'll be associated with the wrong source map.

The red and greyed out stop signs for the breakpoints should correctly indicate if the breakpoints were successfully installed.

Editing a source file with breakpoints should result in intuitive results when adding lines before, or after the breakpoints, or even on the same line.
Issue 1:
We had a quite serious case today which caused all our pods to terminate because AWS had trouble with their EC2 service in Ireland (6:00 AM PDT)

Basically after 40s (corresponding to node-monitor-grace-period) of API downtime during which kubelet couldn't list EC2 instances, it hit the maximum node status retry count and killed everything:

12:44:22 kubelet.go:1933] Error updating node status, will retry: failed to get node address from cloud provider: error listing AWS instances: Unavailable: The service is unavailable. Please try again shortly.
status code: 503, request id: []

...

12:45:04 kubelet.go:839] Unable to update node status: update node status exceeds retry count
12:45:10 kubelet.go:1518] Killing unwanted pod "swagger-extcs"
12:45:10 manager.go:1123] Killing container with id "aa4a55984..."
12:45:10 manager.go:1123] Killing container with id "9bdb1788e..."
12:45:10 kubelet.go:1343] Orphaned volume "5796b5eb..." found, tearing down volume
...

I could certainly assume that downtimes at AWS may never last more than t minutes and increase the node-monitor-grace-period and pod-eviction-timeout in my kube-controller-manager accordingly, but there is something dangerous in making such assumptions and relying only on the cloud provider to define nodes' health, since a not responding cloud provider doesn't mean a completely unhealthy platform.

We paid that price today and saw our whole prod cluster going down while everything was fine on the instances themselves 🙈

Issue 2:
The way we access the kubernetes service is inconsistent; in all other namespaces it is https://kubernetes, but in kube-system I don't have a kubernetes service (should I?).

When I try to use kubernetes from go I get this error:

Get https://kubernetes/api: dial tcp: lookup kubernetes on 100.64.0.10:53: server misbehaving

bboreham pointed out that I can use KUBERNETES_SERVICE_HOST, but I feel this inconsistently is likely to continue to surprise people.

It may be something wrong in my configuration (i.e. perhaps the kubernetes service should already be registered in kube-system), but is there some reason not to register it?
Issue 1:
document usage of 'namespace' attribute - which entities is it relevant to, when different namespaces should be used, can all namespaces be extracted to check what exists on the environment, etc.

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know:
Issue 1:
Hi there,

I installed 1.3 yesterday and my application no longer compiles correctly. Here's an example:

TS Input

import a = require("../dir1/file1");

import MongoClient = require('mongodb');

import b = require('../dir1/file2');

import c = require("../dir2/file1");

JS Output

var c = require("../dir2/file1");

For some reason three of the four lines did not make it into the JS file. All worked fine before I installed the new TypeScript.

Any thoughts?

Issue 2:
I've just come across a problem with tsc (version 1.1.0.0) which I've reduced to the following repro code. Suppose we have the following in main.ts:

import a = require('./main'); // doesn't matter what is required as long as tsc can find it
var b = a; // or any expression referring to 'a'
var c: typeof a;

Compiling this with tsc main --module commonjs gives me the following output:

var b = a;
var c;

Note that no var a = ... has been emitted, and running the code results in ReferenceError: a is not defined.

If the third line (var c: typeof a) is commented out or doesn't refer to a, then the var a = ... line is emitted as expected.
Issue 1:
Summary of the new feature/enhancement

PowerToys Run does not function well as a focus switcher. Run lists running processes in the dropdown, but not the first result and prefers to create a new process instead of focusing on open processes. There should be an option to prioritize running processes in the dropdown.

Description of use

A new option appears under the PowerTools Run settings to enable running process prioritization.

Opening PowerTools Run should bring up the usual menu, and when a query is searched, any results matching the query that are running processes should be prioritized in the results.

Issue 2:
Summary of the new feature/enhancement

It would be more useful if already running programs are shown first in the results list in the quick launcher (like the old WindowWalker). Or maybe an option to change the priority.

Proposed technical implementation details (optional)

In the results list, the running programs should be first in the list.