WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hey!

Is there a way to pass in a sourcemap to createBundleRenderer()? There's an options argument, but it isn't documented (happy to write these docs if you point me towards the correct bit of source: I couldn't find it).

Currently, I'm getting this error, which isn't too understandable:

ReferenceError: window is not defined
at e.__esModule.default (__vue_ssr_bundle__:1:478)
at __vue_ssr_bundle__:1:1052
at r.(anonymous function).exports (__vue_ssr_bundle__:1:146)
at Object.<anonymous> (__vue_ssr_bundle__:1:285)
at /Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6152:21
at runInVm (/Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6144:10)
at Object.renderToStream (/Users/callumacrae/Sites/samknows/website-vue/node_modules/vue-server-renderer/build.js:6175:9)
at server.get (/Users/callumacrae/Sites/samknows/website-vue/server/index.js:29:35)
at Layer.handle [as handle_request] (/Users/callumacrae/Sites/samknows/website-vue/node_modules/express/lib/router/layer.js:95:5)
at next (/Users/callumacrae/Sites/samknows/website-vue/node_modules/express/lib/router/route.js:131:13)

Issue 2:
Vue.js version

2.x.x

Reproduction Link

Because it is a ssr issue and hard to provide a running demo online, please see Steps to reproduce

Steps to reproduce

clone the https://github.com/vuejs/vue-hackernews-2.0.git repostory

edit file src/\components/ItemList.vue to cause an error. For example:

// ...
import Spinner from './Spinner.vue'
import Item from './Item.vue'
import { watchList } from '../store/api'
// abc is a undeclared variable that can cause a ReferenceError
console.log(abc)
// ...

then run npm run build, npm run start in command line

open browser and navigate to http://localhost:8080

the command line will report some error info as below:

error during render : /
ReferenceError: abc is not defined
at Object.module.exports.exports.default.props (__vue_ssr_bundle__:388:13)
at __webpack_require__ (__vue_ssr_bundle__:21:30)
at Object.module.exports.__vue_styles__ (__vue_ssr_bundle__:994:19)
at __webpack_require__ (__vue_ssr_bundle__:21:30)
at Object.module.exports.module.exports (__vue_ssr_bundle__:866:83)
at __webpack_require__ (__vue_ssr_bundle__:21:30)
at Object.<anonymous> (__vue_ssr_bundle__:650:80)
at __webpack_require__ (__vue_ssr_bundle__:21:30)
at Object.module.exports.exports.default.name (__vue_ssr_bundle__:224:66)
at __webpack_require__ (__vue_ssr_bundle__:21:30)

What is Expected?

The error info in the command line should include the specific file path and line number, for example:

ReferenceError: abc is not defined
at src/components/ItemList.vue (26:13)
...

What is actually happening?

Error info dose not include the file path and line number that cause the error to produce..

I know it is the bundle render that cause the error hard to locate. And is there any solution, like soucemap, that can solve this debug issuse with bundle render?
Issue 1:
Gentlemen! I want to filter multidimensional signal with 1D convolutional filter using scipy.signal.fftconvolve (along specified axis). Cannot you such an option to specify axes to filter to scipy.signal.fftconvolve?

Issue 2:
As mentioned in #337 (comment), fftconvolve/convolve/correlate/etc could use an axis= parameter. An example application is computing the CWT in one step. nitime's version of fftconvolve has this.
Issue 1:
Would love it if Launcher could fully replace WIN + S... thoughts?

Issue 2:
Currently, in Windows 10 (1903), when clicking Win+R, it opens the "Run" window command.

This functionality is very limited - the user must remember the exact command, or the exact file. No auto-correct, and if the user is wrong, it only brings an error message that says the file or command was not found.

Can you please add a tool which improves this window, at least with auto-correct?

crutkas edits:

https://github.com/microsoft/PowerToys/wiki/Launcher is the spec

remember to xref #51 as it was listed as a dup
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

package.json :

{
"name": "xxx",
"files": ["./dist/"]
}

running npm publish, the dist will not be packed.

Expected Behavior

the dist should be packed.

I just found a workaround: "files": ["dist/"]

Steps To Reproduce

In this environment...

With this config...

Run '...'

See error...

Environment

npm: 8.5.5

Node.js: v16.15.0

OS Name: macos

System Model Name:

npm config:

; copy and paste output from `npm config ls` here

Issue 2:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

When using leading periods in paths within the files section, the path is not included in publishing. This feels very inconsistent from paths in exports maps and other places.

Expected Behavior

All relative paths defined in package.json content should consistently allow leading periods.

Steps To Reproduce

Create a project to publish with files in a lib folder.

Create a package.json which includes the lib folder in the files section:

{
"files": [
"./lib"
]
}

Run npm publish --dry to see what gets published.

Remove the leading period in the ./lib path and re-run the publish dryrun. Notice more files.

Environment

npm: 8.8.0

Node.js: 14.17.6

OS Name: MacOS

System Model Name: Macbook Pro M1

npm config:

; node bin location = /usr/local/bin/node
; node version = v14.17.6
; npm local prefix = /Users/dzearing/git/ori
; npm version = 8.8.0
; cwd = /Users/dzearing/git/ori/js/packages/api
; HOME = /Users/dzearing
Issue 1:
Describe your issue.

** operator raises a sparse matrix to a power, but it is element-wise power when we use it on .A of the same sparse matrix.

I am not sure this is a bug in numpy or scipy, or if it is intentional.

It at least looks like an inconsistency between numpy arrays and scipy.sparse

Reproducing Code Example

import scipy.sparse as sp

someMatrix = sp.csc_matrix(([1, -1], ([0, 1], [1, 0])), shape=(2, 2))

# print the matrix
print(someMatrix.A)

# raises the matrix to a power
print((someMatrix**2).A)

# element-wise power
print((someMatrix.A)**2)

Error message

No error messages.

SciPy/NumPy/Python version information

1.8.0/1.22.1/3.10.1

Issue 2:
Describe your issue.

Currently, applying the ** operator to a sparse array implements the numpy.linalg.matrix_power function. This is not compatible with the np.array implementation of **, which does element-wise power. This should be fixed as part of the migration from sparse "matrices" to sparse "arrays". Additionally, the matrix_power function should then also be included in the sparse.linalg package.

Reproducing Code Example

from scipy.sparse import csr_array, random

A = csr_array(random(5,5,0.1))
print(A.A)
print((A**2).A) #This does matrix_power, eventhough it is initialised as a sparse array (not a matrix)
print((A.A)**2) #This does element-wise power, since it is a numpy array

Error message

N/A

SciPy/NumPy/Python version information

1.8.0 1.20.3 sys.version_info(major=3, minor=9, micro=7, releaselevel='final', serial=0)
Issue 1:
Should this program work?

package main

type T interface {
m() interface {T}
}

type foo struct {
}

func (f *foo) m() interface {T} {
return &foo{}
}

func main() {
var t T
t = &foo{}
t.m()
}

It seems to compile but panics when run:

http://play.golang.org/p/swxTnFlwQI

By contrast this program works fine:

package main

type T interface {
m() T
}

type foo struct {
}

func (f *foo) m() T {
return &foo{}
}

func main() {
var t T
t = &foo{}
t.m()
}

http://play.golang.org/p/Bxnf72xPsn

Issue 2:
Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go1.6.2

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

GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

What did you do?

I tried to define an interface that expects itself as the argument of one of its methods:

type Nestable interface {
AddChild(interface{Nestable})
}

https://play.golang.org/p/oB091DHIS2

What did you expect to see?

I would expect it to simply look for the desired signature of the argument passed in and accept it as valid

What did you see instead?

It seems it recursively walk the full interface definition so it enters som kind of loop

panic: interface conversion: *main.TreeNode is not interface { AddChild(interface { AddChild(interface { AddChild(interface { AddChild(interface { AddChild(interface { AddChild<...> }) }) }) }) }) }: missing method AddChild
Issue 1:
MRE:

julia@1.5.2

julia> methods(show);

julia> length(methods(show))
304

julia> @time methods(show);
0.000278 seconds (966 allocations: 46.531 KiB)

julia@master

julia> methods(show);

julia> length(methods(show))
314

julia> @time methods(show);
0.022454 seconds (14.80 k allocations: 812.578 KiB)

The profiling shows most of the time is spent in _methods_by_ftype, and I guess #35983 might be the source of this.

Well, I'm not sure the performance for methods is critical; I found this problem just because Juno's completions are much slower than before when using Julia built from master, and profiling shows that this line calling methods is the source of the performance regression:

https://github.com/JunoLab/Atom.jl/blob/c751731bd488db815110ed7771b7f313d8b92116/src/utils.jl#L268

ismacro(f::Function) = startswith(string(methods(f).mt.name), "@")

Now I found changing this line into

function ismacro(@nospecialize(f::FT)) where {FT<:Function}
isdefined(FT, :name) || return false
tn = FT.name::Core.TypeName
return occursin('@', string(tn.name))
end

gets rid of the performance regression anyway, so I'm okay with it if the slowness of methods can't be helped in order to circumvent the latency issues.

Issue 2:
In version 1.4.2, the following is evaluated pretty much instantly:

julia> using LinearAlgebra

julia> mul!
mul! (generic function with 154 methods)

However, in the latest nightly build from commit f130d9b, the mul! takes multiple seconds to evaluate.
Issue 1:
VSCode Version: 1.2.0

OS Version: Linux 4.4.0-22-generic #40-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

Escape is bound to close the new terminal window feature, this is frustrating since some terminal applications use escape as a key to do certain things ( such as escape the application ).

I am now stranded in vim, with no way of getting out within my embedded terminal.

Steps to Reproduce:

Open a terminal.

Press ESC.

Issue 2:
Integrated terminal master issue: #143

Open question: Currently pressing esc will hide the terminal, this can be a problem for some terminal programs, for example vim. Perhaps this should be configurable?
Issue 1:
Pretty much like the title says, private methods should stay private:

input:

class NoRespect {
private priv() {}
pub() { return this.priv(); }
}

actual output:

var NoRespect = (function () {
function NoRespect() {}
NoRespect.prototype.priv = function () { };
NoRespect.prototype.pub = function () { return this.priv(); };
return NoRespect;
})();

expected output:

var NoRespect = (function () {
function NoRespect() {}
var priv = function () { };
NoRespect.prototype.pub = function () { priv.call(this); };
return NoRespect;
})();

➜ tsc --version
message TS6029: Version 1.7.5

Issue 2:
Currently private functions are put on the prototype of a function so they are not really private. I suggest adding them as normal functions in the scope of the class so that they are in fact only accessible to the class.

Example

module Example
{
export class ExampleClass
{
method()
{
this.privateMethod();
}
private privateMethod()
{
console.log("private");
}
}
}

would create

var Example;
(function (Example) {
var ExampleClass = (function () {
function ExampleClass() {
}
function ExampleClass_privateMethod()
{
console.log("private");
}
ExampleClass.prototype.method = function () {
privateMethod();
};
return ExampleClass;
})();
Example.ExampleClass = ExampleClass;
})(Example || (Example = {}));
Issue 1:
VSCode Version: Version 0.10.11 (0.10.11)

OS Version: OS X 10.10.5

Steps to Reproduce:

Create a javascript file and enter following code:

expect(confNy.vars['config']).to.equal(
`proxy=nyproxy.company.org1, port=8081`);

The code is highlighted this way:

Issue 2:
From @f111fei on February 23, 2016 6:14

version： 0.10.10

letter

Copied from original issue: microsoft/vscode#3270
Issue 1:
Not sure if this is a duplicate, but, if I have a function like:

function f()
a = 1
b = 1
f(a b)
end

then I get an error like:

julia> include("test.jl")
ERROR: syntax: missing comma or ) in argument list
while loading /home/simon/Desktop/test.jl, in expression starting on line 1

It would be nice if the line number matched up with the line where the error was actually encountered, rather than the start of the function.

Issue 2:
A code example where Julia does not abort gracefully:

(::Type{T})(x::Int) where {T<:Integer} = println("crash")

entered in the REPL leads to:

crashcrashcrashcrashcrash

crash

crash

crash

corrupted double-linked list

signal (6): Aborted

while loading no file, in expression starting on line 0

A variation that leads to a sigsegv

(::Type{T})(x::Int) where {T<:Integer} = println(:crash)

prints

crashcrashcrashcrashcrash

crash

crash

crash

signal (11): Segmentation fault

while loading no file, in expression starting on line 0

unknown function (ip: 0x7ff958329554)

_ZN4llvm10AllocaInstC2EPNS_4TypeEPNS_5ValueEjRKNS_5TwineEPNS_11InstructionE at /home/picaud/ExternalSoftware/julia-d386e40c17/bin/../lib/julia/libLLVM-3.9.so (unknown line)

emit_function at /buildworker/worker/package_linux64/build/src/codegen.cpp:5643

....

My Julia version is:

Julia Version 0.6.2

Commit d386e40 (2017-12-13 18:08 UTC)

Platform Info:

OS: Linux (x86_64-pc-linux-gnu)

CPU: Intel(R) Xeon(R) CPU E5-2603 v3 @ 1.60GHz

WORD_SIZE: 64

BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)

LAPACK: libopenblas64_

LIBM: libopenlibm

LLVM: libLLVM-3.9.1 (ORCJIT, haswell)

Obvioulsy this code is a non sense, the point is that Julia is really not happy with it.
Issue 1:
Numpy.power(a,b) doesn't seem to be handling large numbers properly.

Maybe a bug in multiplying matrixes?

Numpy info: numpy in /Users/usernameHere/miniconda3/envs/nnseries/lib/python3.6/site-packages (1.12.1)

Update:

This seems similar to my c++ program that couldn't handle numbers larger than 2^31. If numpy uses a c or c++, an arbitrary-length integer library may be need to handle large numbers.

Issue 2:
Simple demo:

In [1]: np.uint8(0) - np.uint8(1)
RuntimeWarning: overflow encountered in ubyte_scalars
Out[1]: 255

In [2]: np.uint8(0)[...] - np.uint8(1)[...]
Out[2]: 255

Should we even warn at all for unsigned integers?
Issue 1:
VSCode Version: 0.10.11

OS Version: WIN10 x64 - Home

Steps to Reproduce:

Write a sass-map

Issue 2:
If I add a map to a scss file, e.g. "$map: (key1: value1, key2: value2, key3: value3);" it shows as an error. Red squiggly appears under the ":" after the first key and hover message reads ") expected". Despite the error in editor node-sass evaluates map-get correctly over it.
Issue 1:
Looks like a change in v3 that never made it into the docs. Form size classes are now .input-small and .input-large instead of .input-sm and .input-lg.

Issue 2:
To increase/decrease the size of form controls, you can add the classes input-lg or input-sm (at least according to the website [http://getbootstrap.com/css/#forms] - which is the most consistent solution). In the css code, however, the classes are called input-large and input-small.
Issue 1:
TypeScript Version:

1.8.2.

Code

// A self-contained demonstration of the problem follows...
class Foo {
bar: "fizz" | "buzz";
}

class Bar extends Foo {
bar = "fizz";
}

Expected behavior:

Bar.bar is initialized to "fizz";

Actual behavior:

Type 'string' is not assignable to type '"buzz"'

Issue 2:
Let's use:

interface A = {
data: number;
}
interface B = {
data: string;
}
interface C extends A, B {}

This will throw an error as data has two separately defined types. I think that it would be really useful to allow C to become a union of the two interfaces either implicitly or to allow explicit unions of the conflicting types. The ultimate result being that:

interface C extends A, B {} = { data: number | string; }

Otherwise, a new interface would have to be created which would be a duplication of effort or the type would have to be overridden with any, which defeats the purpose of having strict types.

It's just a thought, but since TypeScript allows multiple inheritance with interfaces and has union types, I thought that this could be a beneficial merging of the two ideas.
Issue 1:
In Microsoft Visual Studio Professional you can click+hold on selected text and then drag that text to a new location. Like a cut/paste operation by dragging/dropping. Requesting that VS Code support this feature. Thanks!

Issue 2:
We've seen several users run into issues while trying to use a Debugger in VS Code with source mapping for JavaScript projects (From TypeScript, React-Native, etc...). It's not trivial to configure your build project to generate the correct source maps, and it's difficult to understand if, and when they are wrong.

I'd be amazing if you could add better diagnostic tools so it'd be easier for the users to debug these kind of issues. For example, you could add a new feature that when you put a breakpoint on TypeScript, if you hover over it you'll see a tooltip that shows you a snippet from the mapped JavaScript code, and where was the breakpoint put exactly on the JavaScript code. You could also have a "More info" button on that tooltip, that would decode the values that are included in the source map, and show you exactly how the source map says the characters around the breakpoint should be mapped to the source code.

We've also noticed that sometimes if you put breakpoints and the source map is not completely valid, the breakpoints might disappear completely, or appear at the end of the file. It'd be nice if you could also have more validations around this (for example check that the breakpoint line should be less than the total lines of the file where you are putting that breakpoint), and show a nice error message with diagnostic information when something doesn't appear to be right, instead of just "ignoring" that breakpoint or error silently.

For more information you can see an issue that was created against our extension: microsoft/vscode-react-native#206 (comment)
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.

Problem Description

Currently, the accelerator property in MenuItem accepts only one string, therefore it's not possible to register multiple shortucts.

Proposed Solution

The accelerator property in MenuItem class should accept an array of strings.

Alternatives Considered

Adding multiple basically the same MenuItems.

[
{
accelerator: 'CmdOrCtrl+L',
label: 'Toggle Overlay',
click() {
appWindow.webContents.send('toggle-overlay');
},
},
{
accelerator: 'Ctrl+Space',
label: 'Toggle Overlay',
click() {
appWindow.webContents.send('toggle-overlay');
},
},
]

Issue 2:
As mentioned in #1507, it would be nice to be able to specify accelerator aliases, or multiple accelerators.

The most obvious use case is for Zoom In. Command+Plus and Command+= generally both work for zooming in, but there is no way to specify this behavior in Electron.

One idea is to specify an array of accelerators, where the first is shown as the menu item's shortcut, and the rest are aliases.

For example:

{ label: 'Zoom In', accelerators: [ 'Command+Plus', 'Command+=' ] }
Issue 1:
Generally, when using babel / babel-loader it is common to ignore node_modules for faster compilation speed.

The definition of the $$typeof attribute we're looking for is:

var REACT_ELEMENT_TYPE = typeof Symbol === 'function' && Symbol['for'] &&
Symbol['for']('react.element') || 0xeac7;

And this is pushed into a shared module that exports it when using the react.inlineElements transform.

Here's the problem:

On older browsers that don't support Symbol, like Safari 7 / Chromium 30, Symbol is polyfilled by the core-js runtime. But the same definition of REACT_ELEMENT_TYPE is present inside node_modules/react/lib/ReactElement.js, and this is not polyfilled by oore-js and therefore equals 0xeac7.

This causes the element test to fail on render (comparing a shimmed Symbol to 0xeac7) and breaks the render on those browsers.

I propose, rather than redefining REACT_ELEMENT_TYPE directly so it can be used in the inline elements (and thus having it break if upstream ever changes it), let's just instantiate an element and export its $$typeof.

Issue 2:
I am using 6to5 with jsx, gulp and browserify. After several file changes 6to5 crashes with error: FATAL ERROR: JS Allocation failed - process out of memory. I've found out that the problem is with my jsx source by simply switching entry point to js file instead jsx. See the console trace and my configuration below. Pay attention on increasing build time after each bundle change.

Tested with the latest 6to5-core

[20:08:04] Running 'bundle'...
[20:08:05] Finished 'bundle' in 73 ms
[BS] File changed: build/app.js
[20:08:10] Running 'bundle'...
[20:08:11] Finished 'bundle' in 88 ms
[BS] File changed: build/app.js
[20:08:13] Running 'bundle'...
[20:08:14] Finished 'bundle' in 367 ms
[BS] File changed: build/app.js
[20:08:18] Running 'bundle'...
[20:08:36] Finished 'bundle' in 17 s
[BS] File changed: build/app.js
[20:08:42] Running 'bundle'...
FATAL ERROR: JS Allocation failed - process out of memory
[1] 23299 abort gulp

Browserify Gulp task:

var browserify = require('browserify');
var watchify = require('watchify');
var bundleLogger = require('../util/bundleLogger');
var gulp = require('gulp');
var handleErrors = require('../util/handleErrors');
var source = require('vinyl-source-stream');
var _6to5 = require('./6to5ify');
var externalLibs = require('../external-libs');

gulp.task('browserify', function() {

var bundler = browserify({
cache: {}, packageCache: {}, fullPaths: true,
entries: ['./src/scripts/test_app.jsx'],
extensions: ['.js', '.jsx'],
debug: false,
paths: ['./src/scripts'],
fast: true,
detectGlobals: false
});

var bundle = function() {
bundleLogger.start();

return bundler
.external(externalLibs)
.transform(_6to5)
.bundle()
.on('error', handleErrors)
.pipe(source('app.js'))
.pipe(gulp.dest('./build/'))
.on('end', bundleLogger.end);

if(global.isWatching) {
bundler = watchify(bundler);
bundler.on('update', bundle);
}

return bundle();
});

test_app.jsx:

var React = require('react');

var Test = React.createClass({

render: function() {
return (
<h1>Test</h1>
);
}

});

React.render(<Test />, document.getElementById('root'));