WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Ctrl + Click on a symbol is a shortcut for "Go to definition". I would want to instead select / highlight the text (same as double clicking), just like in Visual Studio.

I tried editing the keyboard shortcuts, but it doesn't look like I can use mouse inputs (ctrl+click or ctrl+mouse1 or ctrl+mouseleft didn't work).

Please consider setting this behavior as a built-in setting in settings.json, or allowing mouse input in keybindings. I realize this might not be very high priority, but if it's not too complex to implement, it would be a great quality of life improvement for me!

Issue 2:
VSCode Version: 1.0.0

OS Version: Windows 10 1511 - 10586

Steps to Reproduce:

Generate a New Extension (yeoman -> TypeScript)

src/extension.ts
Issue 1:
I install kubernetes 1.1.1 in ubuntu and check out the official url http://kubernetes.io/v1.1/examples/mysql-cinder-pd/README.html to create a cinder volume.

I config the following content in the path "/etc/kubernetes/cloud_config".

[Global]

auth-url=https://*****.v2.0

username=user

password=pass

region=regionOne

tenant-id=0c331a1df18571594d49fe68asa4e

I add the following contend in "/etc/default/kubelet"

--cloud-provider=openstack --cloud-config=/etc/kubernetes/cloud_config

restart the kubernetes service.

create cinder

cluster/kubectl.sh create -f examples/mysql-cinder-pd/mysql.yaml

The error information is following:

It looks as if you don't have a compiled kubectl binary

If you are running from a clone of the git repo, please run

'./build/run.sh hack/build-cross.sh'. Note that this requires having

Docker installed.

If you are running from a binary release tarball, something is wrong.

Look at http://kubernetes.io/ for information on how to contact the

development team for help.

Issue 2:
I install kubernetes 1.1.1 in ubuntu and check out the official url http://kubernetes.io/v1.1/examples/mysql-cinder-pd/README.html to create a cinder volume.

1.I config the following content in the path "/etc/kubernetes/cloud_config". [Global] auth-url=https://*****.v2.0 username=user password=pass region=regionOne tenant-id=0c331a1df18571594d49fe68asa4e

2.I add the following contend in "/etc/default/kubelet"

--cloud-provider=openstack --cloud-config=/etc/kubernetes/cloud_config

3.restart the kubernetes service.

4.create cinder

5.cluster/kubectl.sh create -f examples/mysql-cinder-pd/mysql.yaml

Now I can connect with openstack cinder. But when I create a mysql pod. The pod status is running first, then it changes to be error status.

I check out the kubelet.log.

I find the error Unable to find pair interface, setting up all interfaces: exec: "nsenter": executable file not found in $PATH
Issue 1:
TypeScript Version:

1.8.0-1.8.7

Code

import {Key} from 'types'; // Key is an interface
const Key = { test() {} };
Key.test();
export default Key;

Expected behavior:

Key.test();
exports.default = Key;

Actual behavior:

types_1.Key.test();
exports.default = types_1.Key;

Issue 2:
It is incredibly easy to make a copy/paste error for case clauses in a switch statement.

switch (node.kind) {
// ...
case SyntaxKind.TupleType:
// Do something with tuple types.
case SyntaxKind.TupleType:
// Do something with union types.
// ...
}

While it is easily arguable that non-exhaustive cases can be allowed in TypeScript, there is no reason not to report duplicated cases.

"Obvious" semantics for case clauses in a single switch statement are as follows:

Report when named entities with identical symbols are handled.

Report when equal string literals are handled.

Report when equal numeric literals (even 0.0 and 0) are handled.

Report when null is handled more than once.

Report when undefined is handled more than once.

One interesting question is whether exhaustive cases for an enum should report an error when there is a default clause.
Issue 1:
Right now, VolumetricConvolution in THNN doesn't mark or handle bias=NULL cases

Issue 2:
🐛 Bug

To Reproduce

Steps to reproduce the behavior:

Ensure tqdm is not installed in your environment, verify that python -c 'import tqdm' raises an exception.

import torch
torch.hub.load('willprice/pytorch-hub-bug', 'entry_point')

(repo here)

This errors with

Using cache found in /home/will/.cache/torch/hub/willprice_pytorch-hub-bug_master
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python3.7/site-packages/torch/hub.py", line 336, in load
hub_module = import_module(MODULE_HUBCONF, repo_dir + '/' + MODULE_HUBCONF)
File "/usr/lib/python3.7/site-packages/torch/hub.py", line 70, in import_module
spec.loader.exec_module(module)
File "<frozen importlib._bootstrap_external>", line 728, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/home/will/.cache/torch/hub/willprice_pytorch-hub-bug_master/hubconf.py", line 3, in <module>
from entry import entry_point
File "/home/will/.cache/torch/hub/willprice_pytorch-hub-bug_master/entry.py", line 1, in <module>
import tqdm
ModuleNotFoundError: No module named 'tqdm'

Expected behavior

I'd expect torch to raise an exception saying a dependency isn't installed, rather than an ImportError.

I would expect torch.hub.load to check dependencies in hubconf.py before executing hubconf.py and actually loading in the entrypoints. It's not clear from examples of hubconf.py that to avoid this behaviour you'd have to wrap all your entrypoints in functions that import the dependencies within the function body and not at the top level. This is a pain as it involves adding a wrapper for every entrypoint and duplicating all the docstrings.

Suggested fix

Rather than evaluating the module, it'd make more sense to pull out the AST node corresponding to the dependencies variable and evaluate that only, perform the dependency check and only then import the full module. It might be that people have complicated hubconf.py files that prevent this from happening. In that case things get a bit more tricky and it might make sense to fallback on the current implementation as at least the user still gets ImportError exceptions that are useful if not the most user friendly.

Environment

PyTorch version: 1.1.0
Is debug build: No
CUDA used to build PyTorch: Could not collect

OS: Arch Linux
GCC version: (GCC) 9.1.0
CMake version: version 3.15.1

Python version: 3.7
Is CUDA available: No
CUDA runtime version: 10.1.168
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: /usr/lib/libcudnn.so.7.6.1

Versions of relevant libraries:
[pip3] msgpack-numpy==0.4.3.2
[pip3] numpy==1.16.4
[pip3] pytorch-ignite==0.1.2
[pip3] torch==1.1.0
[pip3] torchaudio==0.2
[pip3] torchfile==0.1.0
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.2.1
[pip3] torchviz==0.0.1
[conda] blas 1.0 mkl
[conda] mkl 2019.4 243
[conda] mkl_fft 1.0.12 py36ha843d7b_0
[conda] mkl_random 1.0.2 py36hd81dba3_0
[conda] pytorch-cpu 1.1.0 py3.6_cpu_0 pytorch
[conda] torchvision-cpu 0.3.0 py36_cuNone_1 pytorch
Issue 1:
Routing doesn't working in safari 10, I have some code like:

onClick={() => route.push(tab.href, tab.href, { shallow: true })}

back home
Both of them are not working, I don't know why, please help me

Issue 2:
When using nextjs dynamic imports, each dynamic import is imported twice... one file seems to be the bundle for distribution. The other seems to for hot reloading?

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

Expected Behavior

I'm expecting to see just one file requested per dynamic import.

Current Behavior

Instead I'm seeing two files requested per dynamic import.

Steps to Reproduce (for bugs)

Pull down this example nextjs app to reproduce

yarn dev to see it working in dev

yarn build then yarn start to spin up the production build

Context

Your Environment

Tech
Version

next
5.1.0 (latest)

node
9.7.1

OS
mac

browser
chrome
Issue 1:
I tried using the @types/Node package and had problems.

I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @....

I wanted Node Typings in my Typescript project so I entered this command:

npm install @types/node --save

Which resulted in:

error TS2403: Subsequent variable declarations must have the same type.
Variable 'require' must be of type 'Require', but here has type 'NodeRequire'.

My machine had node version 7.0.3 The installed types was for version + @types/node@7.0.28

If I uninstall the typings my project compiles with no problems.

It appears as if the typings content is not correct per the error message!

The failing line of code in index.d.ts

This is the TSConfig content:

"compilerOptions": {
"module": "amd",
"moduleResolution": "node",
"target": "es5",
"noImplicitAny": false,
"jsx": "react",
"sourceMap": false,
"baseUrl": ".",
"paths": {
"OfficeFabric/*": [
"node_modules/office-ui-fabric-react/lib-amd/*"
]
}
}
}

Typescript version is 2.2.2

Root Cause: Require.js had a var named Require in it's index.d.ts, and so did Node.js in it's index.d.ts. Renaming one of them fixed the problem. But there is the --types option for TSConfig too.

Issue 2:
TypeScript Version: 2.2.2

Code

This is my TSCConfig file content

{
"compilerOptions": {
"module": "amd",
"moduleResolution": "node",
"target": "es5",
"noImplicitAny": false,
"jsx": "react",
"sourceMap": false,
"baseUrl": ".",
"paths": {
"OfficeFabric/*": [
"node_modules/office-ui-fabric-react/lib-amd/*"
]
}
}
}

Expected behavior:

After running npm install @ types/node --save

The project should compile ok.

Actual behavior:

The error message TS2403 is indicated.

Uninstalling the node types fixes the problem.

Could this be a clash between : module:"amd" and moduleresolution: "node"

Current Node version is 7.0.3

The installed types was for version + @types/node@7.0.28
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

I am creating an editable table with add and remove row feature in the FormGroup with validation.

The table works when the rows add or remove from last. When the row is removed from the middle of the table, angular throw an error "There is no FormControl instance attached to form control element with name name_2".

On adding the row I have used the "addControl" method to add control in the group and on the removal of the row I am using "removeControl" method.

Expected behavior

There should be no error, from whichever place I remove or add the row.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Windows 10, IIS server 7, angular 2.1.0

Angular version: 2.0.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome Version 54.0.2840.71 m (64-bit)

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript 2.0.3

Node (for AoT issues): node --version =

Node 6.0

Issue 2:
I'm submitting a ... (check one with "x")

[x] bug report
[ ] 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

The QueryEncoder encodes %3D to ; instead of =

https://github.com/angular/angular/blob/master/modules/%40angular/http/src/url_search_params.ts#L44

Expected/desired behavior

The QueryEncoder should encode %3D to =

My comment on the PR that causes the bug:

#9651 (comment)

Reproduction of the problem

What is the expected behavior?

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Angular version: 2.0.0-rc.4

Browser: [all]

Language: [TypeScript]
Issue 1:
How to configure IntelliSense in Visual Studio Code?

For example, lets consider the below code snippet.

'use strict';

import React from 'react';
import ReactDOMServer from 'react-dom/server';

I would like the IntelliSense to suggests the available methods on React, when I press cmd + space after typing React..

Is that possible? If yes any pointer would be of great help.

PS:

I have already installed the dependent modules and updated the package.json and they are available at ./node_modules/

Raised it at StackOverflow a month ago.

Issue 2:
var express = require('express');

var app = express();

var port = process.env.PORT || 3000;

app.listen(port);

In the following code I required express but when I enter app and press crtl + space it shows no suggestions.

It would be nice to have code assist for installed packages because nodejs developers always play with packages.
Issue 1:
The Deno LSP gets confused by dynamic imports in weird ways it's easiest to demonstrate with screenshots...

Notice that the type error is invalid (perhaps related to #11362 (comment)), and Deno seems to incorrectly think the type is scoped to the file of the first dynamic import later on in the function. Another weird thing is the file:// path Deno is displaying in the error omits the .js file extension.

Later in the same module, you can see that Deno incorrectly thinks each dynamic import is actually the next dynamic import:

The last dynamic import incorrectly has no intellisense when the path is hovered:

I've tried restarting the Deno LSP via the VS Code Deno extension command, and it doesn't help.

Issue 2:
Describe the bug

When the deno extension is enabled, typed imports via /** @type {import("... stop working.

To Reproduce

Create Bar.js:

export class Bar {}

Create Foo.js:

/** @type {import("./Bar.js").Bar} */
const foo = null;

Hover over foo and note it's type is set to Bar.

Enable deno with Deno: Initialize Workspace Configuration

Hover over foo again.

Expected behavior

The type remains set to Bar, rather than any.

Screenshots

If applicable, add screenshots to help explain your problem.

Versions

vscode: 1.62.3 deno: 1.16.3 extension: 3.9.2
Issue 1:
Challenge Waypoint: Local Scope and Functions has an issue.

User Agent is: Mozilla/5.0 (X11; CrOS x86_64 5841.83.0) AppleWebKit/537.36 (KHTML like Gecko) Chrome/36.0.1985.138 Safari/537.36.

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

My code:

function myFunction() {
var myVar = "loo";
console.log(myVar);
}
myFunction();

// run and check the console
// myVar is not defined outside of myFunction

// now remove the console.log line to pass the test

checker responds:

Remove the second console log

That's what's causing the issue, when the line is removed checker returns success:

// now remove the console.log line to pass the test

So it may be optimal to do it like this:

function myFunction() {
var myVar = "loo";
console.log(myVar);
}
myFunction();

// run and check the console
// myVar is not defined outside of myFunction
console.log(myVar); // now remove this whole line to pass the test

By the way, commenting second console log line produces checker error also, but this is probably known, because of instructions to remove the line to pass the test.

Issue 2:
Challenge Waypoint: Local Scope and Functions has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.48 Safari/537.36.

The test asks you to remove the second console.log() to pass. When you remove the second console.log() it still fails. You have to remove both console.log() calls to pass(including the one inside myFunction().)

Reproducible every time by removing the console.log() outside of myFunction(), as asked by test. I'm assuming this is a bug in the test and not the text as there's no reason to remove the console.log() call within myFunction().
Issue 1:
Why the MDS that is supplied does not supports weights in addition to the dissimilarity matrix?

Issue 2:
Hi!

My name is Charles, and I would like to share my very first contribution to open-source project.

Smacof from sklearn rules ! It only lacks the weighting

I regularly need the use of SMACOF algorithm, for sensor localization. In this field (and others), the weighting is mandatory to give more or less importance to pairwise distances. I send you to a well-known paper about it : Costa2006

So far I have been using a wrapping of smacof in R with rpy2, because it features the weighting. But everytime I update R or rpy2 I get errors, about types, etc.

You added a very good implementation of smacof in the pull request #797. The idea of adding the weighting was proposed, but was not done, was there maybe a reason about it ?

How to feature it

Today I tried to modify the source code of sklearn, and my tests on sensor localization, by adding weighting have shown consistent results so far.

The idea could be to add a weight parameter at the fit method:

from sklearn.manifold import MDS

smacof = MDS(n_components=2, dissimilarity='precomputed')

# Let D be a n_sample x n_sample euclidean distance matrix
# and weighting be a n_sample x n_sample weight matrix
smacof.fit(D, weight=weight)
pl.scatter(*smacof.embedding_.T) # maps the sensors

What to change?

Not that much actually! The way it was coded only need few modifications in the _smacof_single() function.

As you can see in the algorithm description, it needs to compute the matrix V and its pseudo inverse, for the final update (eq. (14)). And also, it needs to modify B, by weighting the ratio variable (=s_ij eq. (11) ).

Are you interested in adding this feature to your main branch?

Best,

Charles
Issue 1:
There's a problem with the ES6 generated code when using inner classes. The code:

// Bug.ts
module Stuff {
export class Foo {
constructor (message: string) {
this.Message = "Hello, " + message
}
Message = ""
}
export module Foo {
export class Bar {
}
}
}
var foo = new Stuff.Foo("World")
console.log(foo.Message)

compiled with tsc -t ES6 Bug.ts and then by babel --no-highlight-code Bug.js produces error:

TypeError: Bug.js: Line 10: Duplicate declaration "Foo"
8 | }
9 | Stuff.Foo = Foo;
> 10 | var Foo;
| ^
11 | (function (Foo) {
12 | class Bar {
13 | }

Issue 2:
Closely related to #2457 and also in reference to bd4d7fc#commitcomment-10328068

A class merging with a module will not work in ES6, because you will end up redeclaring a class and a var (the var is what we emit for the module) in the same scope, which will cause a runtime error. So a class merging with a module needs to be renamed in a similar way as #2457, except as a var instead of a let.
Issue 1:
In the table at http://twitter.github.com/bootstrap/#javascript, bootstrap-button.js's description is a mere duplicate of bootstrap-scrollspy.js's description

Issue 2:
When I open the bootstrap website in IE8 and go to the navbar section, when I click on the Dropdown link in the sample navbar, the dropdown menu has the position arrow at the top right of the dropdown.

I cannot duplicate this in my own site with IE8. I have stripped down my code to a minimum so it's just the navbar and bootstrap.css/.js being loaded, but still nothing in IE8.

Any ideas on what the bootstrap website is doing so that the position arrow appears in IE8 so that I can mimick that behavior on my own site? Can a note be added to indicate how to duplicate that behavior or possibly something added to the bootstrap.css code to enable that in IE8? Thanks.
Issue 1:
Running /opt/julia-1.0.2/bin/julia --output-o sys-all.o --sysimage /opt/julia-1.0.2/lib/julia/sys.so --startup-file=no --compile=all --eval nothing found 39977 uncompiled methods for compile-all causes segemtation fault:

found 39977 uncompiled methods for compile-all
11659 / 39977
signal (11): Segmentation fault
in expression starting at no file:0
jl_is_type_type at /buildworker/worker/package_linux64/build/src/julia.h:1058 [inlined]
emit_llvmcall at /buildworker/worker/package_linux64/build/src/ccall.cpp:977
emit_intrinsic at /buildworker/worker/package_linux64/build/src/intrinsics.cpp:921
emit_call at /buildworker/worker/package_linux64/build/src/codegen.cpp:3134
emit_expr at /buildworker/worker/package_linux64/build/src/codegen.cpp:3902
emit_ssaval_assign at /buildworker/worker/package_linux64/build/src/codegen.cpp:3615
emit_stmtpos at /buildworker/worker/package_linux64/build/src/codegen.cpp:3801 [inlined]
emit_function at /buildworker/worker/package_linux64/build/src/codegen.cpp:6254
jl_compile_linfo at /buildworker/worker/package_linux64/build/src/codegen.cpp:1159
_compile_all_deq at /buildworker/worker/package_linux64/build/src/precompile.c:262 [inlined]
jl_compile_all_defs at /buildworker/worker/package_linux64/build/src/precompile.c:303
jl_precompile at /buildworker/worker/package_linux64/build/src/precompile.c:365 [inlined]
jl_write_compiler_output at /buildworker/worker/package_linux64/build/src/precompile.c:34
jl_atexit_hook at /buildworker/worker/package_linux64/build/src/init.c:233
main at /buildworker/worker/package_linux64/build/ui/repl.c:234
__libc_start_main at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
_start at /opt/julia-1.0.2/bin/julia (unknown line)
Allocations: 1254722 (Pool: 1254268; Big: 454); GC: 2
Segmentation fault

I expect to get sys-all.so which then can be used for cc -shared -o sys-all.so sys-all.o -ljulia.

Issue 2:
It would be nice to have a switch-like statement, exploiting LLVM's built-in switch instruction, since this can greatly enhance performance of look-up tables (which are not uncommon in inner loops), compared to chains of if-else statements (or a Dict of functions).

I feel like I've mentioned this to @JeffBezanson, before, but can't find an issue for it.
Issue 1:
I rebuild the opencv and

NVIDIA CUDA: YES (ver 10.0, CUFFT CUBLAS)
NVIDIA GPU arch: 30 35 37 50 52 60 61 70 75
NVIDIA PTX archs:
cuDNN: YES (ver 7.6.4)

my config:NVIDIA GeForce MX150 CUDA:10.1 CUDNN：8.0.2

the darknet can use gpu

my code is :

auto net = cv::dnn::readNetFromDarknet("D://yolov4.cfg", "D://yolov4_last.weights");
net.setPreferableBackend(cv::dnn::DNN_BACKEND_CUDA);
net.setPreferableTarget(cv::dnn::DNN_TARGET_CUDA);
auto output_names = net.getUnconnectedOutLayersNames();

cv::Mat frame, blob;
std::vector<cv::Mat> detections;
frame = imread("D:/1.jpg");
auto total_start = std::chrono::steady_clock::now();
cv::dnn::blobFromImage(frame, blob, 1 / 255.0, cv::Size(416, 416));
net.setInput(blob);
auto dnn_start = std::chrono::steady_clock::now();
net.forward(detections, output_names);
auto dnn_end = std::chrono::steady_clock::now();

If i only use cpu,the time is 1.5 s . if i use the gpu ,the time is 5 s. i do not know why

hope giving me some tips . thank you

Issue 2:
1,i rebuild the opencv and

NVIDIA CUDA: YES (ver 10.0, CUFFT CUBLAS)
NVIDIA GPU arch: 30 35 37 50 52 60 61 70 75
NVIDIA PTX archs:

cuDNN: YES (ver 7.6.4)

2，my config:NVIDIA GeForce MX150 CUDA:10.1 CUDNN：8.0.2

3，the darknet can use gpu

4.my code is :

auto net = cv::dnn::readNetFromDarknet("D://yolov4.cfg", "D://yolov4_last.weights");

net.setPreferableBackend(cv::dnn::DNN_BACKEND_CUDA);

net.setPreferableTarget(cv::dnn::DNN_TARGET_CUDA);

auto output_names = net.getUnconnectedOutLayersNames();

cv::Mat frame, blob;
std::vector<cv::Mat> detections;
frame = imread("D:/1.jpg");
auto total_start = std::chrono::steady_clock::now();
cv::dnn::blobFromImage(frame, blob, 1 / 255.0, cv::Size(416, 416));
net.setInput(blob);
auto dnn_start = std::chrono::steady_clock::now();
net.forward(detections, output_names);
auto dnn_end = std::chrono::steady_clock::now();

5,if i only use cpu,the time is 1.5 s . if i use the gpu ,the time is 5 s. i do not know why

hope giving me some tips . thank you