WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Feature request

When outputting content targeting the web platform, it would be nice to have the option to output an es module for modern browsers. (I don't believe there is currently a way to do this - if there is it needs better documentation :P).

What is the expected behavior?

Ideally, I would like to be able to have webpack output two entry files, an esmodule as well as what it currently outputs.

Then in the index.html file, both files can be loaded like this:

<head>
<script nomodule src="bundle.js" async></script>
<script type="module" src="bundle.mjs" async></script>
</head>

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

Supporting the modern web.

How should this be implemented in your opinion?

Maybe something like this:

// webpack.config.js

const config = {
//...
};

const webConfig = Object.assign({}, config, {
target: 'web',
//...
});

const webModuleConfig = Object.assign({}, config, {
target: 'web-module',
//...
});

module.exports = [
webConfig, webModuleConfig,
];

Are you willing to work on this yourself?

Maybe but probably not. I'm still a novice when it comes to the webpack eco-system so I'd probably be at a loss on how to implement this.

Issue 2:
I'm submitting a feature request

It would be nice, if output.libraryTarget could support the ES2015 module format.

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

Say I develop a fancy component called fancy-component with webpack. I use a very custom config with specific loader settings e.g. for inlining images and stuff like that. My module exports FancyComponent and BigFancyComponent.

A friend develops a single page application and uses rollup to do that. He knows nothing about webpack, but wants to use my FancyComponent, but not BigFancyComponent. He installs fancy-component and imports FancyComponent. BigFancyComponent should not be included in the build (because of tree shaking).

As far as I know this is currently not possible. My friend would need fancy-component in a format using ES2015 modules. But currently these include webpack specific loader logic. I really need to publish fancy-component without webpack specific logic, but with ES2015 modules.
Issue 1:
https://docs.scipy.org/doc/numpy/reference/generated/numpy.cov.html

The ddof definition in the above link is incorrect. ddof should be 1 instead of 9.

Issue 2:
Documentation in https://docs.scipy.org/doc/numpy/reference/generated/numpy.var.html#numpy.var contains this statement

The variance is the average of the squared deviations from the mean, i.e., var = mean(abs(x - x.mean())**2).

The mean is normally calculated as x.sum() / N, where N = len(x). If, however, ddof is specified, the divisor N - ddof is used instead.

It is not clear which mean is calculated using N - ddof instead of N, and the first part of the second sentence suggests (to me, at least) that it's the inner mean - which is not the case (and rightly so).

Suggested (IMHO clearer) rewording:

The outer mean is normally calculated as t.sum() / N, where N = len(x). If, however, ddof is specified, the divisor N - ddof is used instead.

The same problem is present in the documentation for nanvar, std and nanstd. Similar rewording should make it clearer.
Issue 1:
Do you want to request a feature or report a bug?

This probably is a feature request since the root of this is considering the build tooling and questions on how to proceed with my efforts.

What is the current behavior?

No native ecmascript module output and the current build tools don't easily allow adding a native ecmascript module build target.

While investigating a workflow using a native ecmascript module version of React (and ReactDOM) in browsers I found no implementation which outputs native ecmascript modules.

One can use a wrapped version of the transpiled versions with added export statements but transpiling would not be necessary for browsers supporting ecmascript modules natively.

Even spread operators are supported by these browsers although they're not fully supported by AST generators or other tools due to the fact that the spec for that isn't finalised.

After some test projects and different build tools I built a simple proof of concept which outputs ecmascript modules that can be used in modern browsers.

The challenge (and question I have) is that the tools and settings used in the POC contradict the current build settings and tools.

So I am wondering if this is something that can be added as a build target or that this is something that is better suitable for an external repo for the time being...

I would love to make this happen but I would like to hear if this is something that is deemed worth while and if so in what would be the preferred way of implementing this.

During my investigation I did not find an easy way of doing so without changing a considerable amount of code and build tooling. Making this a relatively high risk endeavour.

Webpack vs Rollup, different settings needed for Babel, and named exports instead of CommonJS module.exports pattern to name a few, and all the effects those have on the build process make this somewhat complex.

To clarify some things, these are links to the POC's:

repo which outputs native ecmascript modules for React and ReactDOM: https://github.com/wearespindle/react-ecmascript

repo with a minimal setup to test if a working app can be made these modules in a browser: https://github.com/PM5544/module-test

What is the expected behavior?

Preferably a build target for native ecmascript modules.

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

not relevant

Issue 2:
Currently we only ship CommonJS versions of all packages. However we might want to ship them as ESM in the future (#10021).

We can't quite easily do this because we haven't really decided on what top-level ES exports would look like from each package. For example, does react have a bunch of named exports, but also a default export called React? Should we encourage people to import * for better tree shaking? What about react-test-renderer/shallow that currently exports a class (and thus would start failing in Node were it converted to be a default export)?
Issue 1:
I can get the following on Julia 1.6.1:

julia> foo() = ===(0)
foo (generic function with 1 method)

julia> foo()
Internal error: encountered unexpected error in runtime:
BoundsError(a=Array{Any, (2,)}[
Main.:(===),
0], i=(3,))
jl_bounds_error_ints at /buildworker/worker/package_linux64/build/src/rtutils.c:186

The syntax may indeed be invalid, but it doesn't produce a friendly error.

Issue 2:
This needs to be implemented in task.c. After copying all the fields of the jl_task_t, the following extra changes are needed:

deepcopy tls

set consumers to jl_nothing

set donenotify to jl_nothing

allocate with allocb a copy of stkbuf, which is bufsz bytes

I think there is a chance that will work.
Issue 1:
With Wn=2 I correctly got the message

ValueError: Digital filter critical frequencies must be 0 < Wn < 1

But actually Wm=1 is accepted without error. The message should be changed to 0 < Wn <= 1 if 1 is allowed.

Issue 2:
When using scipy.singal.iirfilter (or any other related filter design method), it is possible to trigger the error Digital filter critical frequencies must be 0 < Wn < 1:

from scipy.signal import iirfilter
iirfilter(2, Wn=5, btype='low')

This error message is correct and helpful in the default case, but when the newish fs parameter is used, the error message is misleading/wrong:

from scipy.signal import iirfilter
iirfilter(2, Wn=600, fs=1000, btype='low') # Error message
iirfilter(2, Wn=300, fs=1000, btype='low') # No Error message

This error message is generated in this line:

if not analog:
if numpy.any(Wn <= 0) or numpy.any(Wn >= 1):
raise ValueError("Digital filter critical frequencies "
"must be 0 < Wn < 1")

I would suggest to change it to:

if not analog:
if numpy.any(Wn <= 0) or numpy.any(Wn >= 1):
if fs is not None:
raise ValueError("Digital filter critical frequencies "
"must be 0 < Wn < fs/2 (fs={})".format(fs))
raise ValueError("Digital filter critical frequencies "
"must be 0 < Wn < 1")

If this is ok, I would start a pull request with this change
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

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

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

Issue Details

Electron Version:

v2.0.18

macOS 10.15.1

Last Known Working Electron version:

Expected Behavior

Login input fields should not show the LastPass Chrome extension icon.

Actual Behavior

I see the LastPass icon in the login fields.

To Reproduce

Create a login form using Bootstrap and install the LastPass Chrome extension in the Chrome app.

Screenshots

Additional Information

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

12^

Operating System Version

Windows 10 v19042

What arch are you using?

x64

Last Known Working Electron version

11 downwards

Expected Behavior (Electron 11 and older)

notifications would close after timeout, not appearing the windows 10 notification center. (and thus not duplicating)

In the gist with v11 you can see it logs "notification closed" when it timeout

Actual Behavior (Electron 12 and newer)

After the notification timeout - it moves to the notification center without closing and also can't be closed programmatically

(notification.close doesn't do anything IF it has already timeout and moved to notification center)

which can result in a spam of notifications in notification center

In the gist with v12/13 you can see the notification doesn't close on timeout + oldNotification.close() only works if the old notification hasn't timed out yet

Testcase Gist URL

https://gist.github.com/a1c1ac4c057370540be18e0b5aeefb89

Additional Information

I found no documentation or breaking change that indicate any modifications in notification API

reported at th-ch/youtube-music#312

tested by me on multiple versions of electron 11, 12 and 13 - including latest releases

if this doesn't get directly fixed - there should atleast be an option "close on timeout" that allows using that functionality and avoid spamming the notification center
Issue 1:
I propose including the SourceFile being emitted in the emit callback.

TypeScript Version:

1.7.5 / 1.8.0-beta / nightly (1.9.0-dev.20160217)

Code

import * as ts from 'typescript';
import * as fs from 'fs';
import * as fse from 'fse';

const fileName = 'index.ts';
const fileNames = [fileName];

class LocalHost implements ts.LanguageServiceHost {
getCompilationSettings(): ts.CompilerOptions {
return {
experimentalDecorators: true,
modules: ts.ModuleKind.CommonJS,
target: ts.ScriptTarget.ES5
};
}

getProjectVersion(): string { return "1";}
getScriptFileNames(): string[] { return fileNames; }
getScriptVersion(fileName: string): string { return "1"; }
getCurrentDirectory(): string { return dir; }

getScriptSnapshot(fileName: string): ts.IScriptSnapshot {
const filteredName = nameFilter(fileName);
if (fs.existsSync(filteredName))
return ts.ScriptSnapshot.fromString(fs.readFileSync(filteredName, 'utf8'));
}

getDefaultLibFileName(options: ts.CompilerOptions): string {
return './node_modules/typescript/lib/lib.es7.d.ts';
}
}

const host = new LocalHost();
const ls = ts.createLanguageService(host);
const program = ls.getProgram();

const emitResult = program.emit(undefined, (absoluteFilePath, fileContent, sourceFile) => {
console.log('emitting', absoluteFilePath, 'for', sourceFile.fileName);
fse.mkdirsSync(path.dirname(absoluteFilePath));
fs.writeFileSync(absoluteFilePath, this.fixSourceMapSources(fileContent), { encoding: 'utf-8' });
});

Expected behavior:

If this proposal is taken then the sourceFile parameter above will contain the SourceFile instance emit currently emitting the file absoluteFilePath on behalf of.

Justification:

.d.ts files do not contain information about the decorators used in the .ts files, nor can it. However, these decorators often contain valuable information that other processors might need, such as, in our case, the Angular 2 offline compiler and the Angular 2 language service. To preserve this information we emit a .metadata.json file for each .d.ts file emitted if the corresponding module contains classes with decorators.

We use program.emit() in our build process and use the callback to trigger the emit of the .metadata.json file but we must make an educated guess as to which SourceFile the .d.ts file is being emitted for. It would be more straight forward for the SourceFile to passed into the callback to emit.

Issue 2:
I'm just reading scanner code and find some unicode characters are duplicate in unicodeES5IdentifierStart array:

var unicodeES5IdentifierStart = [170, 170, 181, 181, ..., 748, 748...

Any reason?
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Context

I initially found the HOC pattern to be confusing, since (as a consumer) you can't explicitly see what prop(s) are being added.

(Also, it seems weird to create a component that can't stand on it's own, and then wrap it into something that can.)

Here is an explanation of the render-props pattern, which solves that (first) problem to offer a better Developer eXperience:

https://cdb.reacttraining.com/use-a-render-prop-50de598f11ce

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

This is related to #88, but not quite the same. In this case, we are routing between the same page (/user.js), not different pages. Something weird is happening with the normal react lifecycle hooks for ALL page child components (all the way down the tree) that makes it impossible to prevent something from re-rendering.

Essentially, this means that on every route change (even if you are routing between the same page) every single component on the page is forced to re-render, and there is no way to stop it.

Expected Behavior

shouldComponentUpdate should be triggered as normal on the page component, and its child components.

Current Behavior

shouldComponentUpdate is skipped on the page component, and its child components.

Steps to Reproduce

I have created an example that reproduces the issue in an isolated environment. It includes instructions for running, and seeing what's going on. It also includes a link to an animated gif for you lazy folks out there :).

https://github.com/stoplightio/nextjs-router-bug

Context

We have complicated inner components and not being able to prevent them from re-rendering is a problem.
Issue 1:
From @atcq1 on March 25, 2016 13:11

VSCode Version:0.10.11

OS Version:ubuntu 14.04 x64

Intellisense\autocomplete not work to call methods and property through this.methodName () / this.propertyName.

Steps to Reproduce:

Create route:

import Ember from 'ember';

export default Ember.Route.extend({
property1: 'text',
model(params) {
return {};
},
firstMethod()
{
//test1
},
secondMethod()
{
//test2
},
thirdMethod()
{
//Intellisense
secondMethod(); //work
this.secondMethod(); //do not work
//Autocomplete
property1; //work
this.property1; //do not work
}
});

2 Enter this.second or this.prop in thirdMethod(){}:

Copied from original issue: microsoft/vscode#4671

Issue 2:
let o = {
f: function () { this./**/ }
}

Expected: Intellisense shows 'f' in the list

Actual: Intellisense shows nothing because this: any.

Note that this similar code already works:

let o = {
f() { this./**/ }
}
Issue 1:
Something wrong with keyboard modifiers processing?

We have wrong processing of keyboard input with modifiers... For example:

using System;

namespace ConsoleApp1
{
class Program
{
static void Main(string[] args)
{
ConsoleKeyInfo cki;
do
{
cki = Console.ReadKey();
Console.Write(" --- You pressed ");
if ((cki.Modifiers & ConsoleModifiers.Alt) != 0)
{
Console.Write("ALT+");
}
if ((cki.Modifiers & ConsoleModifiers.Shift) != 0)
{
Console.Write("SHIFT+");
}
if ((cki.Modifiers & ConsoleModifiers.Control) != 0)
{
Console.Write("CTL+");
}
Console.WriteLine(cki.Key.ToString());
}
while (cki.Key != ConsoleKey.Escape);
}
}
}

Same keys sequence is pressed... 1 2 ... 0 RCtrl+1 RCtrl+2 RCtrl+3... RCtrl+0

LCtrl+1 LCtrl+2 LCtrl+3 LCtrl+4

We have some, but also wrong result only for Ctrl+2... Shift modifier added.

Same behaviour also with more complicated software - "Far Manager" for example (in this situation problem not with simple Console.ReadKey but with keyboard events processing. In this example we don't see any reactions of software on pressing Ctrl like we can see in old console. So problems also with keyboard modifiers).

Issue 2:
Your Windows build number:

10.0.18362.86

What you're doing and what's happening:

Trying to enter the @ sign on a Swedish keyboard in a PowerShell console using Alt Gr + 2.

See animated gif:

What's wrong / what should be happening instead:

Windows terminal shows digit-argument instead of outputting the @ sign as expected.

It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓
Issue 1:
https://gist.github.com/stevejmason/2fab8149460a5565ef388f92cd2e478e

When running the above gist with Deno, the process crashes with BorrowMutError, see Actual text below. I believe this is caused by the mutable borrow calls within the async blocks on cli/ops/net.rs:144 and cli/ops/net.rs:212.

Perhaps we can use tokio::net::udpsocket split() and update UdpSocketResource to have a send/recv half contained in Arc<Mutex<>>, borrow state immutably on the main thread, clone the Arc container and use this from the async block? I have a working version to push, but would like some feedback on this approach as I'm fairly new to Rust.

(sidenote, the gist is unlikely to run on master due to the new NetAddr/UnixAddr interfaces, I've been playing with types to add generics to DatagramImpl which i'll follow up with).

Actual output

thread 'main' panicked at 'already borrowed: BorrowMutError', /rustc/b8cedc00407a4c56a3bda1ed605c6fc166655447/src/libcore/cell.rs:878:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected output (duplicate lines removed)

Using fork - https://github.com/stevejmason/deno/tree/async-udp

TEST SOCKET RECV (1): hello world ! from [127.0.0.1:44444]
TEST SOCKET RECV (...10): hello world ! from [127.0.0.1:44444]
Received: [This is a response for message (1)] from (127.0.0.1:25262)
Received: [This is a response for message (...10)] from (127.0.0.1:25262)

Deno version (also master#2874664)

deno 0.36.0
v8 8.1.310
typescript 3.8.3

Issue 2:
http://server01/a.jsx

import React from "http://server01/react.js";

...

http://server02/b.jsx

import React from "http://server02/react.js";
...

main.jsx

import {A} from "http://server01/a.jsx";
import {B} from "http://server02/b.jsx";
...
return <div>
<A/>
<B/>
</div>
...
Issue 1:
Version

2.5.20

Reproduction link

codepen.io

Steps to reproduce

When I'm on the same page or component，“v-for” multiple times using the same array， "Duplicate keys detected. This may cause an update error." will be reported on the page，But the key of V-for is not repeated

What is expected?

In a page, using an array to render V-for multiple times will not report an error

What is actually happening?

In a page, use an array to render V-for multiple times and report errors

Issue 2:
Version

2.6.10

Reproduction link

https://codesandbox.io/s/elated-sun-8npx9?file=/src/App.vue

Steps to reproduce

Error message displays immediately when viewing repro.

What is expected?

Vue should recognize that the given v-slot is attached to a component, because the element has the is="hello-world" attribute set.

What is actually happening?

Vue sees the v-slot attribute on a section element, and assumes it is an error.

Ordinarily I'd just rewrite my code to directly reference the component (without the is= attribute) but I'm rehydrating server-rendered content and need the wrapper to be semantic.
Issue 1:
Attention models get more popular. In many of my experiments with attention, I end up using Softmax over multiple dimensions.

tf.nn.softmax() supports only one dimension. It would be nice to expand the API with another argument, softmax_dim, for softmax over multiple dimension, say over 2 (images) or 3 (CT-scans, videos)

I;d like to here what you think? DO more people end up writing softmax code themselves?

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): macOS

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

TensorFlow installed from (source or binary): source

TensorFlow version (use command below): master

Python version: 2.7

Bazel version (if compiling from source): 0.15.0

GCC/Compiler version (if compiling from source): None

CUDA/cuDNN version: None

GPU model and memory: None

Describe the current behavior

I convert the TF model to TFLite model by tflite_convert command with float inference_type, and input_shapes set to 1,W,H,3; when I run the model with input shape W*H, it works well; However, when I change the input shapes to different values, it would give error like "tensorflow/contrib/lite/kernels/kernel_util.cc:125 d1 == d2 || d1 == 1 || d2 == 1 was not true; Node number xx (ADD) failed to prepare" for tf.add op. Similar errors appear for other ops like CONCAT and RESHAPE. When I set breakpoints in tflite codes, it seems to always check/use the tensor shapes when converting the model, even the input shape has changed.

Part of the codes are like this:

int input = interpreter->inputs()[0];
interpreter->ResizeInputTensor(input, new_input_sizes);
if (interpreter->AllocateTensors() != kTfLiteOk) {
NSLog(@"Failed to allocate tensors for model.");
exit(-1);
}
Issue 1:
h1, h2, h3 tags within panel-headings are set with margin-top: 20px; margin-bottom: 10px;

h4, h5, h6 are at 10px; 10px;

Gives an undesirable look. So, create another rule for these headings?

Or is this not being used enough to warrant?

Issue 2:
In the example there is are panel headers with and without a title being shown. There is a height inconsistency among them, as shown on the image bellow:

Should both of them be 40px or is this inconsistency expected?
Issue 1:
i update atom to v0.189.0, then open a file with chinese code, and it's messy

Issue 2:
Text:

这上面的夜的天空，奇怪而高，我生平没有见过这样奇怪而高的天空。他仿佛要离开人间而去，使人们仰面不再看见。然而现在却非常之蓝，闪闪地睒着几十个星星的眼，冷眼。他的口角上现出微笑，似乎自以为大有深意，而将繁霜洒在我的园里的野花草上。

It happen after update to 0.189.0, and it's normal in 0.188.0 .

I try disabled all community packages or star with --safe mode, still happen.

Update: Ubuntu 14.04