WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Describe what you were doing when the bug occurred:

1.

2.

3.

Please do not remove the text below this line

DevTools version: 4.8.2-fed4ae024

Call stack: at updateTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17786:17)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17717:25)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

at getCommitTree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:17710:30)

Component stack: at CommitFlamegraphAutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:31701:48)

at div

at div

at div

at SettingsModalContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26139:23)

at Profiler_Profiler (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:33363:48)

at ErrorBoundary (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27172:5)

at PortaledContent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27303:32)

at div

at div

at ProfilerContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:30463:23)

at TreeContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:22538:23)

at SettingsContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:23040:27)

at ModalDialogContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28328:23)

at DevTools_DevTools (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:33797:21)

Issue 2:
Describe what you were doing when the bug occurred:

I did profiling on a list, that gets updated on each pagination api call.

Once the profiling was done, I moved around in the Profiler to view the Flamegraph

Moving to second capture, the Profiler crashed.

DevTools version: 4.6.0-6cceaeb67

Component stack: in ec
in div
in div
in div
in So
in Unknown
in n
in Unknown
in div
in div
in rl
in Ze
in fn
in Ga
in _s
Issue 1:
What version of Go are you using (go version)?

Go Playground

What operating system and processor architecture are you using (go env)?

Go Playground

What did you do?

See https://play.golang.org/p/beWgN_LRyJ -- it fails to compile with internal compiler error: large ONEW with EscNone: new(). The code itself doesn't make a lot of sense, building a buffer and not using it, but it should still compile.

What did you expect to see?

The program should run on the Go Playground.

What did you see instead?

The program fails to compile with internal compiler error: large ONEW with EscNone: new()

Other

If I assign the buffer to a variable and invoke a method, the code compiles and runs. See https://play.golang.org/p/tKXN_mw_Sp

Issue 2:
Go version: +2e4b659 15/07/2015, OS: Debian Jessie AMD64

The following program fails to compile:

package main

type X struct {
Array [1 << 16]byte
}

func main() {
_ = &X{}
}

with the message

./test.go:8: internal compiler error: large ONEW with EscNone: new()
Issue 1:
System information

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

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

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

TensorFlow version (use command below): 1.7.0

Python version: 3.6

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: Intel graphics, 4GB RAM

Exact command to reproduce: import tensorflow

Describe the problem

I've installed tensorflow v1.7.0 via PIP and I am having issues working with it. Upon entering a REPL and attempting to import tensorflow the REPL silently exits with an exit code of 132. I've run PDB and tried importing it and it appears it is exiting around the from tensorflow.python import * section of the tensorflow code. Looking at the PDB output it appears that code is exiting with error code 132 after running importlib._bootstrap._find_and_load which is a python internal.

Source code / logs

PDB output from trying to import tensorflow (around the section that it exits):

> <frozen importlib._bootstrap>(191)_get_module_lock()->_ModuleLock('...40427194539368
(Pdb) n
> <frozen importlib._bootstrap>(149)__enter__()
(Pdb) n
--Return--
> <frozen importlib._bootstrap>(149)__enter__()->None
(Pdb) n
> <frozen importlib._bootstrap>(969)_find_and_load()
(Pdb) n
> <frozen importlib._bootstrap>(970)_find_and_load()
(Pdb) n
> <frozen importlib._bootstrap>(971)_find_and_load()
(Pdb) n

What I'm trying to run:

$ python3.6
Python 3.6.4 (default, Jan 5 2018, 02:35:40)
[GCC 7.2.1 20171224] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
$ echo $?
132

Issue 2:
As announced in release notes, TensorFlow release binaries version 1.6 and higher are prebuilt with AVX instruction sets. This means on any CPU that do not have these instruction sets either CPU or GPU version of TF will fail to load with any of the following errors:

ImportError: DLL load failed:

A crash with return code 132

Our recommendation is to build TF from sources on these systems.

System information

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

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): ubuntu/windows/macos

TensorFlow installed from (source or binary): binary

TensorFlow version (use command below): 1.6 and up

Python version: 2.7, 3.3, 3.4, 3.5, 3.6 and any newer

Bazel version (if compiling from source): n/a

GCC/Compiler version (if compiling from source): n/a

CUDA/cuDNN version: any

GPU model and memory: any

Exact command to reproduce: python -c "import tensorflow as tf"
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-generate-random-whole-numbers-with-javascript has an issue.

Typo - "You should have multiplied the result of Math.random but 10 to make it a number that's greater then zero');"

Correction - "You should have multiplied the result of Math.random by 10 to make it a number that's greater then zero');"

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-generate-random-whole-numbers-with-javascript has an issue.

"You should have multiplied the result of Math.random but 10 to make it a number that's greater then zero"

But I believe is a typo for 'by'
Issue 1:
Steps to Reproduce

Run this:

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatefulWidget {
@override
_MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
body: Center(
child: Container(
width: 200,
height: 200,
decoration: BoxDecoration(
color: Colors.blue,
border: Border.all(
color: Colors.white,
),
),
),
),
),
);
}
}

I'd expect to see a blue box with a simple white border, but there is actually a very slight blue line outside of the white border. I haven't seen it in previous versions of flutter, but then again I haven't looked for it specifically. I'd guess this is something to do with anti-aliasing in the engine.

This is what it looks like in a screenshot (and FYI I've tested in release mode and it does the same thing, not that I'd really expect it to be different).

And blown up:

Logs

N/A

Flutter Doctor

[√] Flutter (Channel dev, v1.0.0, on Microsoft Windows [Version 10.0.17134.407], locale en-GB)
[√] Android toolchain - develop for Android devices (Android SDK 28.0.3)
[√] Android Studio (version 3.2)
[√] IntelliJ IDEA Community Edition (version 2018.2)
[√] IntelliJ IDEA Community Edition (version 2018.3)
[√] VS Code (version 1.27.2)
[√] VS Code, 32-bit edition
[√] Connected device (1 available)

• No issues found!

This is running on a Nexus 5x running 8.1.0 on the Nov 5 2018 security patch.

Issue 2:
I create a plugin by following the documentation :

flutter create --org com.example --template=plugin hello
cd hello/example; flutter build ios --no-codesign
open ios/Runner.xcworkspace

The documentation says that the development files can be found under this folder in the Xcode project navigator:

Pods/Development Pods/hello/Classes/

But in fact, the project navigator puts them under:

Pods/Development Pods/hello/../../example/ios/.symlinks/plugins/hello/ios/Classes

Note: the files are physically at the right location hello/ios/Classes/, so I guess it's only a symlink issue.

My environment:

Flutter 0.5.1 • channel beta • https://github.com/flutter/flutter.git
Framework • revision c7ea3ca377 (7 weeks ago) • 2018-05-29 21:07:33 +0200
Engine • revision 1ed25ca7b7
Tools • Dart 2.0.0-dev.58.0.flutter-f981f09760
Issue 1:
Currently PriorityQueue defaults to a max-heap and if you want to use it as a min-heap you need to overload Ord and change the comparison.

But you should be able to use the default ordering and simply specify that you want a min-heap, so we can use it for types like (uint, &str) for example.

The simple idea would be to simply make a new_min_heap and a min_heap_with_capacity constructors.

Thoughts?

Issue 2:
When documenting traits, rustdoc lists known implementations. From there it links to both the trait and the type it’s implemented on, which both (usually) have an [src] link.

However, the source code of an impl is not always next to either of them. Could each impl have an [src] link as well?

For example, it’s hard to go from http://doc.rust-lang.org/std/fmt/trait.Binary.html to https://github.com/rust-lang/rust/blob/master/src/libcore/fmt/num.rs , even grep doesn’t help.
Issue 1:
Attaching events in template throws error.

e.g the following template works fine

<input #testname value="Test" />
<p> {{ testname.value }}</p>

but the following one throws error, the moment I add the event

<input #testname value="Test" (keyup)/>
<p> {{ testname.value }}</p>

Looks like its related to the issue #1789

Issue 2:
Related: #3664 (should be fixed together)

I have a template with the following element:

<input type="file" id="picture" accept="image/*"
(change)="onFileSelected(f, $event)"
(fileread)>

On alpha 33 it worked great.

On alpha35 it produces the following runtime error:

EXCEPTION: TypeError: Cannot set property 'lastInBinding' of undefined
angular2.js:13030 STACKTRACE:
angular2.js:13030 TypeError: Cannot set property 'lastInBinding' of undefined
at Function.execute._ConvertAstIntoProtoRecords.create (http://localhost:5555/lib/angular2.js:18104:47)
at http://localhost:5555/lib/angular2.js:17730:49
at Array.map (native)
at createEventRecords (http://localhost:5555/lib/angular2.js:17729:36)
at JitProtoChangeDetector.execute.JitProtoChangeDetector._createFactory (http://localhost:5555/lib/angular2.js:17575:39)
at new JitProtoChangeDetector (http://localhost:5555/lib/angular2.js:17567:32)
at $__1.execute.JitChangeDetection.createProtoChangeDetector (http://localhost:5555/lib/angular2.js:10323:20)
at http://localhost:5555/lib/angular2.js:15553:42
at Array.map (native)
at Function.execute.ListWrapper.map (http://localhost:5555/lib/angular2.js:6374:26)

The following modification still produces the error:

<input type="file" id="picture" accept="image/*"
(change)="onFileSelected(f, $event)"
(fileread)="">

This one works

<input type="file" id="picture" accept="image/*"
(change)="onFileSelected(f, $event)"
(fileread)="x">
Issue 1:
I've just updated the definitions from the version 0.0.33 to the latest version 0.0.36 and my build is failing with the following error (but that error occurs also in 0.0.34 and 0.0.35):

.../node_modules/@types/google-apps-script/google-apps-script.base.d.ts
Type error: Subsequent variable declarations must have the same type. Variable 'console' must be of type 'Console', but here has type 'console'. TS2403

325 | // declare var MimeType: GoogleAppsScript.Base.MimeType;
326 | declare var Session: GoogleAppsScript.Base.Session;
> 327 | declare var console: GoogleAppsScript.Base.console;

TypeScript version: 3.0.1

Authors: @motemen, @grant

Issue 2:
In the node declarations, it seems like the EventEmitter interface and EventEmitter class have become out of sync so that typescript code which should compile clean generates error TS2352:

repro case::

/// <reference path="typings/index.d.ts" />
import {EventEmitter} from 'events';
const pe = process as EventEmitter;

observed error:

error TS2352: Type 'Process' cannot be converted to type 'EventEmitter'.
Property 'prependListener' is missing in type 'Process'.

It seems like this happened when new Node V6 methods on core EvenentEmitter (prependListener, prependOnceListener, and eventName), but in the declaration file these methods were only only got added to the class declaration in module 'events'. As a result, attempting to pass the process variable to a method expecting a events.EventEmitter generate a typescript error.

Should these methods be added to both declarations of EventEmitter, or does it make sense to try to eliminate the dual declaration of EventEmitter?
Issue 1:
Repro:

Start up a kube cluster.

Make some API calls that result in 404 (e.g. http://apiserver/aaa or http://apiserver/api/v1/pods/aaa) or 503 (kill etcd and make some API calls).

Visit http://apiserver/metrics.

Expected behavior: The metrics that have a "code" tag (e.g. apiserver_request_count and rest_client_request_status_codes) should have lines referring to code="404" or code="503".

Actual behavior: No such lines exist. Only code="200" lines exist.

Happening at HEAD (730a6a1). This is currently blocking us from monitoring and alerting on 5xx errors.

Issue 2:
When looking into those metrics, the code is always 200.

I explicitly send a bad request:

wojtekt@wojtekt-work:~/go/src/k8s.io/kubernetes/pkg/labels$ curl localhost:8080/api/v1/pods?timeoutSeconds=xxx

{

"kind": "Status",

"apiVersion": "v1",

"metadata": {},

"status": "Failure",

"message": "strconv.ParseInt: parsing "xxx": invalid syntax",

"reason": "BadRequest",

"code": 400

}

and in metrics it was reported as code "200".

cc @lavalamp @kubernetes/goog-csi
Issue 1:
I have to use the device_attributes.pb.h and I don't know where it is.

Thank you !

Issue 2:
I want to use the sparse tensor in C++ API(https://www.tensorflow.org/api_docs/cc/class/tensorflow/ops/add-sparse-to-tensors-map).

But when I search in "https://github.com/tensorflow/tensorflow", there is no "tensorflow/cc/ops/sparse_ops.h"

Does anyone know how to use the sparse tensor in C++?
Issue 1:
Right now if there is an error such as `Unexpected identifier`` it goes to STDOUT, it should go to STDERR and the process should exit with an error code so that CI , npm test, ... can detect something went wrong.

Issue 2:
Hi,

I'd like to know when a build failed using the webpack client (because of a module not found for example). Right now, it seems that the client is outputting the error to the console but the status code of the webpack client process is 0 (success).

Is it the normal behavior? I can imagine that when using the watch option we don't want the process to end on a build failure but without the option, could the client terminate with a status != 0?

I'd like to avoid to search for "ERROR" inside the client output to determine that the build failed.

Thanks.
Issue 1:
React introduces a new JSX transform that is supported in TypeScript 4.1: https://devblogs.microsoft.com/typescript/announcing-typescript-4-1-beta/#jsx-factories

We should consider the impact of this on Deno and specifically --no-check.

Issue 2:
React 17 introduced new JSX transforms and they are available in TypeScript 4.1. There are two new options for "jsx" in TypeScript:

"react-jsx"

"react-jsxdev"

Currently with check these should be supported without any further changes, but are unsupported in --no-check and deno bundle.

We need support from swc before integrating. Ref: swc-project/swc#1103

cc/ @kdy1
Issue 1:
While reading the CRNN model from meijieru

in OpenCV, I got the following error

import cv2
net = cv2.dnn.readNetFromTorch("crnn.pth")

error: OpenCV(4.2.0) C:\projects\opencv-python\opencv\modules\dnn\src\torch\torch_importer.cpp:1022: error: (-213:The function/feature is not implemented) Unsupported Lua type in function 'cv::dnn::dnn4_v20191202::TorchImporter::readObject'

model link

How to fix this error?

System information (version)

OpenCV = 4.2.0

Operating System / Platform => Windows 64 Bit

Issue 2:
Is there any plan to add DepthwiseConvolution layer of caffeImporter into opencv?
Issue 1:
If you index the same percolator query twice without a refresh in between, then it will show up twice in the percolator results. Also, the percolator count API will return the wrong number of results (will return 2).

Here is a test case showing the issue (uses the Elasticsearch Ruby gem):

https://gist.github.com/cjbottaro/10920007

Issue 2:
Some of the nodenames in names.txt are not very name-like.

General problems:

Weird capitalization conventions

Lastname, Firstname formatting

Duplicates

General weirdness: "Cody Mushumanski gun Man aka: the hunter"
Issue 1:
It would be cool to be able to define a profile containing other different profiles that open up in a single tab an there in multiple panes (right / left etc.)

Issue 2:
Would it be possible to release preview/Insider builds of Terminal in the Microsoft Store? Having to install 30 GB of C++/UWP tooling, followed by a compilation that takes up another 20 GB of storage, seems pretty excessive just to try out the terminal.

Or at a minimum, maybe release the binaries on GitHub with a PowerShell script to install Cascadia. Then, you'd be able to do nightly/weekly builds.
Issue 1:
Often you have files with the same names when searching, and you can easily see if you have the correct one based on the content, quicker than looking at the file path.

I suggest that the file is shown beneath the file quick picker.

Issue 2:
Support sublime-like preview mode when opening files from the tree view, fuzzy finder, find and replace, etc.

The main issue being tracked is here: atom/tree-view#3
Issue 1:
I'm reporting here since f2py is part of numpy, but this is ONLY f2py-related!

As reported in GeoscienceAustralia/hiperseis#121 f2py fails on

https://github.com/GeoscienceAustralia/ellip-corr/blob/master/ellip/ellipcorr.f

Reading fortran codes...
Reading file 'ellip-corr/ellip/ellipcorr.f' (format:fix,strict)
Post-processing...
Block: ellipcorr
Block: ellipticity_corr
{}
In: :ellipcorr:ellip-corr/ellip/ellipcorr.f:phase_alias
vars2fortran: No typespec for argument "delta".
{}
In: :ellipcorr:ellip-corr/ellip/ellipcorr.f:phase_alias
vars2fortran: No typespec for argument "ip".
Block: phase_alias
Block: lnblk
Post-processing (stage 2)...
Building modules...
Building module "ellipcorr"...
Constructing wrapper function "ellipticity_corr"...
tcor = ellipticity_corr(phase,edist,edepth,ecolat,azim)
Constructing wrapper function "phase_alias"...
phase_alias(phase,delta,ip)
Creating wrapper for Fortran function "lnblk"("lnblk")...
Constructing wrapper function "lnblk"...
lnblk = lnblk(s)
[..]
analyzevars: character array "character*8 phcod(57)" is considered as "character phcod(57,8)"; "intent(c)" is forced.

I would glad about any hint why this error occurs.

Issue 2:
in current devel version when a character variable is defined using the asterisk form

character*8 name

and I then use

common name(12)

I get an error message from f2py like

analyzevars: character array "character*8 name(12)" is considered as "character name(12,8)"; "intent(c)" is forced.

if the first definition is changed to

character(8)

then the error goes away.

The old behaviour that is consistent with FORTRAN should be restored.

Any suggestion on bug fix?
Issue 1:
A little background of what is happening:

Inventory:

[chroot]
/tmp/tmpZhhROE/build ansible_connection=chroot

Playbook:

hosts: chroot
tasks:
- name: Copy image files to destination
synchronize: src={{ app_image }}/ dest=/

Error:

TASK: [Copy image files to destination] ***************************************
failed: [/tmp/tmpZhhROE/build] => {"cmd": "rsync --delay-updates --compress -- timeout=10 --archive --rsh 'ssh -o StrictHostKeyChecking=no' --out- format='<<CHANGED>>%i %n%L' /root/stacks/test/stacker/image/ root@/tmp/tmpZhhROE/build:/", "failed": true, "item": "", "rc": 12}
msg: rsync: mkdir "/tmp/root@/tmp/tmpZhhROE/build:" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(595) [Receiver=3.0.7]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]

Ansible wrongly generates the rsync command. The problematic part is destination - root@/tmp/tmpZhhROE/build:/

When dealing with chroot, there's no point to prepend a hoststring, local filesystem path would be enough.

Issue 2:
ISSUE TYPE

Feature Idea

COMPONENT NAME

feature

ANSIBLE VERSION

ansible --version git:aws
ansible 2.3.1.0
config file =
configured module search path = Default w/o overrides
python version = 2.7.10 (default, Feb 7 2017, 00:08:15) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]

OS / ENVIRONMENT

AWS

SUMMARY

How do we configure AWS new NLB? Do you have any documentation for this?

STEPS TO REPRODUCE

Refer: http://docs.aws.amazon.com/elasticloadbalancing/latest/network/introduction.html

EXPECTED RESULTS

Ansible should provide a feature to create AWS NLB

ACTUAL RESULTS

Ansible should provide a feature to create AWS NLB
Issue 1:
If one tries to use the string index syntax of the r_ object, and it crashes due to an error, it seems like it retains it internal state, making it behave inconsistently.

It can be made consistent again by simply resetting the internal state.

my version of numpy is 1.11.1.

python is the version 3.4.3+

running on Linux Kubuntu 15.10

Kernel: 4.2.0-42-generic x86_64

the error can be replicated with this code

# this works fine
r_[1, 2]
print(r_.axis) # 0

# this works fine, and the state is maintained
r_['1', [[1, 2]]]
print(r_.axis) # 0

# this crashes, and the state is modified
try:
r_['1', [1, 2]]
except IndexError as e:
print(e) # axis 1 out of bounds [0, 1)
finally:
print(r_.axis) # 1

# now this previously correct code crashes as well
try:
r_[1, 2]
except IndexError as e:
print(e) # axis 1 out of bounds [0, 1)

# by resetting the wrong value it works again
r_.axis = 0
r_[1, 2]

Issue 2:
Consider the following code:

from __future__ import print_function

import numpy as np

a = np.ones((3, 3, 3))
b = np.zeros((3, 3))

# Uncommenting this will make the below call to `np.r_` work.
# try:
#	np.r_['2,3', a, b]
# except ValueError:
#	print('failure')

print(np.r_[a, b.reshape((3, 3, 1))])

This fails with:

Traceback (most recent call last):
File "test.py", line 13, in <module>
print(numpy.r_[a, b.reshape((3, 3, 1))])
File "/usr/local/lib/python2.7/dist-packages/numpy/lib/index_tricks.py", line 338, in __getitem__
res = _nx.concatenate(tuple(objs), axis=self.axis)
ValueError: all the input array dimensions except for the concatenation axis must match exactly

All right as the dimensions don't match indeed. However uncommenting the above try/except block will make the second call to numpy.r_ work, just as it was numpy.r_['2,3', a, b.reshape((3, 3, 1))] instead (stacking along the last axis). So it seems that numpy.r_ still has that string from the previous failing call cached and is using it for the second call.

failure
[[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]

[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]

[[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]
[ 1. 1. 1. 0.]]]

Tested on:

Python 2.7.12 + numpy==1.12.0

Python 3.5.2 + numpy==1.12.0