WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Playwright has a utility toMatchScreenshot that will test a screenshot of something against a predefined image that is in it's snapshot directory. I would like for it to test against an image that is at an arbitrary absolute path. If I pass in an arbitrary path, it will coerce the path (replace the separators with hyphens) to a path inside the snapshot directory.

Is there a way I can use playwright's snapshot matching abilities to match against an arbitrary image?

Issue 2:
We currently have expect(screenshot).toMatchSnapshot(name[, options]) which is nice when comparing against at snapshot but it doesn't work when comparing a screenshot against a reference website which is useful for doing visual regression to see what has changed. I propose that we add a toMatchScreenshot(screenshot[, options]) that could be used for something like this:

page.goto("production.example.com")
const ref = await page.screenshot({
animations: "disabled",
fullPage: true,
scale: "css"
});

page.goto("localhost:8080")
const test = await page.screenshot({
animations: "disabled",
fullPage: true,
scale: "css"
});

expect(test, "should match reference").toMatchScreenshot(ref, {
maxDiffPixelRatio: 0,
maxDiffPixels: 0,
threshold: 0
});
Issue 1:
Environment

Windows build number: 10.0.18363.815
PowerToys version: 0.17.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

When a window is opened off, or partially off-screen, the FancyZones are no longer available to arrange Windows. Only able to use FancyZones again if I end the PowerToys process in Task Manager and reload the application. This happens if PowerToys is running either as administrator or not.

Expected behavior

Able to snap Windows to FancyZones

Actual behavior

FancyZones no longer appear when the target Window is dragged

Screenshots

Issue 2:
Environment

Windows build number: 10.0.18362.778
PowerToys version: 0.17.0
PowerToy module for which you are reporting the bug: FancyZones

Steps to reproduce

Uninstall previous version of PowerToys

Install 0.17.0

Open PowerToys, things work just fine

Wait for a while

Try to place a window inside a zone, it shows no zones, and acts as if the app no longer running

Can open settings window and interact with toggles and such, but cannot save

Can close settings window

Can sometimes right click > exit on the systray icon, other times i have to force close in task manager

Reopen PowerToys, repeat

Expected behavior

The ability to use FancyZones as long as the PowerToys app is running

Actual behavior

FanzyZones only being usable right after opening, and then no longer working after an undetermined amount of time when trying to snap a window
Issue 1:
When creating an EffectComposer with an OutlinePass in the pipeline, the alpha channel is discarded.

This is demonstrated in this jsfiddle snippet. Comment composer.addPass( outlinePass ) to see the background turning transparent (white).

Three.js version

r95

Issue 2:
Description of the problem

After commit b3cf1c7 the outlinePass renders transparent backgrounds in black.

Three.js version

Dev

r88

Browser

Chrome latest

Firefox

Internet Explorer

OS

All of them

Windows 10

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)
Issue 1:
Hello, I found Scrollspy doesn't support Chinese ID Targets.

In order to reproduce the bug, I post a gist. It looks almost the same to the example from official Doc. A slight difference is that I modify one element's id("mdo") into a Chinese ID ("艾姆滴欧").

When you view the html file in your browser, you can see that it can spy all the target elements except that element with Chinese ID.

Issue 2:
The alert types can be customized with alert-info, alert-sucess, alert-error and alert-danger corresponding to resp. blue, green, red, red alert boxes.

Please add an explicit warn style alert-warn.

Note that this would correspond to the default orange alert.

The reason I'm asking is, from my backend I'm providing the alert-type (like error, warn, info) and in case if it's not provided it will fall back to info.

If there would be an alert-warn I could easily do something like alert-<% the type %> in my html page.
Issue 1:
Please help, the site changes and loads behind the menu bar, the "x" button will not close the side bar. True for all safari, bing, chrome, and even using browsec Vpn. Not sure what could be causing this. Wanted to practice waypoints on the phone away from desktop to continue JavaScript lessons.

P.s. Displayed fine before January 13 approximately. Thanks.

Sent from my iPhone

Issue 2:
Hi,

I just can't use the website with Safari as of the release of the new design.

At any given time there is a blank panel on the right site of the webpage, the only links I can click on are map and chat, they both pop out a new panel that overlaps the blank one, but if I close the panel it does not dismiss the blank one. Screenshot for clarification

Website works fine on Chrome or Firefox on my computer, so I guess its just an safari Issue?
Issue 1:
Using multiple metric evaluation has the following example:

>>> def tn(y_true, y_pred): return confusion_matrix(y_true, y_pred)[0, 0]
>>> def fp(y_true, y_pred): return confusion_matrix(y_true, y_pred)[0, 1]
>>> def fn(y_true, y_pred): return confusion_matrix(y_true, y_pred)[1, 0]
>>> def tp(y_true, y_pred): return confusion_matrix(y_true, y_pred)[1, 1]
>>> scoring = {'tp': make_scorer(tp), 'tn': make_scorer(tn),
... 'fp': make_scorer(fp), 'fn': make_scorer(fn)}

This means that confusion_matrix will be called 4 times for each cross_validate fold.

This is probably not a performance issue because the cost of confusion_matrix is dwarfed by the cost of fitting and applying the model, but it is still clearly suboptimal.

It would seem natural to allow scorers to return dictionaries rather than numbers.

E.g., the previous example would be

def cm(y_true, y_pred):
mx = confusion_matrix(y_true, y_pred)
return {"tn:mx[0,0], "fp":mx[0,1], "fn":mx[1,0], "tp":mx[1,1]}
scoring = make_scorer(cm)

sklearn: 0.20.0

Issue 2:
Description

The implementation of _multimetric_score will call every scorer individually. HERE

Unfortunately, these scorers are typically generated via make_scorer and each individual metric will end up repeatedly calling predict, proba, etc. HERE

For a recent exploratory GridSearch where I was generating lots of metrics (multi-output regression and wanted individual statistics for each output), My scoring time was 75% as long as my fit time which is bonkers and I know that my scoring functions are nowhere near that slow.

Suggested Change

This code should really just be calling predict once and feeding the same predictions into each of the scorers.
Issue 1:
For some reason, the specified behavior in ES6 JavaScript (or "JavaScript 2015") of nodeLists having default iterators that allow you to iterate through them with behavior similar to values() or a for..of loop isn't defined in Babel yet.

In fact, unlike other transpilers that at least explicitly explains its lack of finding the default iterator for things, Babel currently merely states TypeError: undefined is not a function:

Issue 2:
I was reading this MDN page on for...of: https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Statements/for...of and they mentioned that you could use it with stuff from the DOM like NodeList. I tried it and it didn't work so I ended up polyfilling it with this code:

if (NodeList.prototype[Symbol.iterator] === undefined) {
NodeList.prototype[Symbol.iterator] = function () {
var i = 0;
return {
next: () => {
return { done: i >= this.length, value: this.item(i++) };
}
}
};
}

It actually works and lets do stuff like:

for (let { id } of document.querySelectorAll("div")) {
console.log(`elem.id = ${id}`);
}

I'd like to create a pull request for this and the other DOM lists. Where's a good place to put browser only polyfills?
Issue 1:
Search for contacts saved on Outlook (365 not outlook.com)

I have over 2,000 contacts in Outlook and it's very frustrating to find a contact’s phone number. On the Mac, you simply spotlight, type the name of the person and you have their phone number.

I want to invoke PowerToys Run, type a name and get their phone number. Not sure why this is so hard. Kind of funny that the fastest way I have for getting a contact from Microsoft Exchange is to use my iPhone…

Issue 2:
Summary of the new feature/enhancement

Adding links to control panel items and stuff like Device Manager would be cool - this would replace Keypirinha completely for me and many others I imagine!

EDIT: Woops, feel free to add Powertoys Run to the title.
Issue 1:
Body

days_ago is deprecated #21653

We have several references to the function in test suite / example dags.

Task:

there should be no imports of airflow.utils.dates import days_ago in the code.

In most cases we can simple replace with datetime(2022, 1, 1)

Committer

I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Issue 2:
Body

days_ago() is deprecated #21653

There are many test using this function thus raising warnings.

This task is to replace all usages of days_ago() in the tests with alternatives.

A stale PR that started to work on it #21830 but didn't finish

Committer

I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Issue 1:
Issue description

The gradient of torch.clamp when supplied with inf values is nan, even when the max parameter is specified with a finite value. Normally one would expect the gradient to be 0 for all values larger than max, including for inf.

Code example

I'm trying to implement the following piecewise function: exp(x) for x < 0; 1 otherwise. A straightforward way to do this would be to use torch.exp(x).clamp(max=1), but this does not work as expected:

>>> x = torch.FloatTensor([-10, -5, 0, 5, 10, 50, 60, 70, 80, 90, 100])
>>> x.requires_grad = True
>>> y = torch.exp(x)
>>> y
tensor([4.5400e-05, 6.7379e-03, 1.0000e+00, 1.4841e+02, 2.2026e+04, 5.1847e+21,
1.1420e+26, 2.5154e+30, 5.5406e+34, inf, inf],
grad_fn=<ExpBackward>)
>>> z = y.clamp(max=1)
>>> z
tensor([4.5400e-05, 6.7379e-03, 1.0000e+00, 1.0000e+00, 1.0000e+00, 1.0000e+00,
1.0000e+00, 1.0000e+00, 1.0000e+00, 1.0000e+00, 1.0000e+00],
grad_fn=<ClampMaxBackward>)
>>> z.sum().backward()
>>> x.grad
tensor([0.0000, 0.0067, 1.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000,
nan, nan])

System Info

PyTorch version: 0.4.1

Is debug build: No

CUDA used to build PyTorch: 8.0.61

OS: Arch Linux

GCC version: (GCC) 8.1.1 20180531

CMake version: Could not collect

Python version: 3.6

Is CUDA available: Yes

CUDA runtime version: 9.2.148

GPU models and configuration: GPU 0: GeForce GT 730

Nvidia driver version: 396.24

cuDNN version: Probably one of the following:

/usr/local/R2017a/bin/glnxa64/libcudnn.so.5.1.5

Versions of relevant libraries:

[pip] numpy (1.14.2)

[pip] numpydoc (0.8.0)

[pip] torch (0.4.1)

[pip] torchvision (0.2.1)

[conda] cuda80 1.0 0 soumith

[conda] pytorch 0.4.1 py36_cuda8.0.61_cudnn7.1.2_1 [cuda80] pytorch

[conda] torchvision 0.2.1 py36_1 pytorch

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer

Issue 2:
🚀 Feature

Recurrent Dropout for RNN, GRU and LSTM.

Motivation

The concept of dropout to sequence models has been proposed in this paper. Also popular libraries like Keras and Tensorflow have their native implemenation of this but Pytorch does not. I personally feel Pytorch is giving a very stiff competition to Keras and Tensorflow, hence must not leave out this feature.

Pitch

There has been some good results in the paper for using droupouts in sequence models for language modelling. Hence adding this to Pytorch would be of great use to Pytorch users rather than depending on alternative solution.

Alternatives

An alternate solution is to depend on a non-native implementation of the same is given here as part of the language modelling toolkit of Salesforce.
Issue 1:
Hi there after the new update my avast detected atom as a virus and as blocked it. I tried uninstalling and reinstalling it but continues to block it. What must I do?

See image

Issue 2:
Atom version: 0.136.0

From atom 0.136.0, the following two files are falsely detected as: Win32:Malware-gen:

atom-0.136.0\build\windows\Setup.exe

atom-0.136.0\build\windows\Update.exe

Avast version: 2015.10.0.2206

Virus signatures version: 141021-0

I will also submit this to avast.
Issue 1:
Google Chrome Extension does not work anymore.

Google Chrome is up to date

Version 83.0.4103.116 (Official Build) (64-bit)

Most of the time, the new developer tabs never show up.

If I kill the whole process and re-load it, sometimes it will load, sometimes it doesn't.

The plugin has access to all data on all sites.

Was this plugin ever updated to use the new plugin format?

Note: I didn't initially realize this is the entire react project and not the dev tools plugin. Not sure why the dev tools plugin page in Chrome sent me here for support.

Issue 2:
Note this issue is due to CR bug 1085215

It is impacting several other popular extensions as well- including React, Redux, Relay, and Vue devtools.

React version: 16.13.1

DevTools version: 4.7.0 (5/18/2020)

macOS version: 10.15.4 (19E287)

Steps To Reproduce

Create a new profile in Google Chrome

Install the React Developer Tools

Go to https://reactjs.org

Open the browser Dev Tools

Screenshots

Not sure this helps, but this is basically what I get after following the aforementioned steps:

When using Opera the tabs do show up:

The current behavior

Sometimes the Components and Profiler (i.e. React devtools tabs) don't show up.

The expected behavior

These tabs should show for any site using React.

More details

I've tried a few browsers, including:

Google Chrome (83.0.4103.61)

Microsoft Edge (83.0.478.37)

Opera (68.0.3618.125)

All of them should be working, since they're all Chromium based.

The most reliable was Opera, which always shows the dev tools tabs. Chrome and Edge behaved the same way, sometimes showing them and other times not.

I've also taken a look at the background pages of the React Dev Tools extension and they don't show any errors, only these performance metrics in the devtools_app.html page:

The main background page shows nothing in the console at all times.
Issue 1:
Your conversions between Rust Futures and JS Promises is probably mature, but thought I'd make you aware of this new crate owned by Rust team members Alex Crichton and Nick Fitzgerald, wasm-bindgen-futures. It might allow you to remove code so you don't duplicate work, or improve your existing.

API Docs here, GitHub Repo here.

Crate description:

This crate bridges the gap between a Rust Future and a JavaScript Promise. It provides two conversions:

From a JavaScript Promise into a Rust Future.

From a Rust Future into a JavaScript Promise.

Issue 2:
Running Cargo install deno results in the following error:

Compiling deno_runtime v0.117.0

error[E0432]: unresolved import tokio_metrics::RuntimeMonitor

--> /home/justdave/.cargo/registry/src/index.crates.io-6f17d22bba15001f/deno_runtime-0.117.0/tokio_util.rs:6:5

|

6 | use tokio_metrics::RuntimeMonitor;

| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no RuntimeMonitor in the root

For more information about this error, try rustc --explain E0432.

error: could not compile deno_runtime (lib) due to previous error

warning: build failed, waiting for other jobs to finish...

error: failed to compile deno v1.34.3, intermediate artifacts can be found at /tmp/cargo-installj3lO39
Issue 1:
I am in the process of following the exact steps as mentioned in the scipy contributer guide in order to obtain a development version of scipy . When I run the code ' python3 runtests.py -v ' on terminal , on after passing 22% of the test , it gives an error :

scipy/linalg/tests/test_decomp.py::TestEigh::test_eigh_integer realloc(): invalid next size

Fatal Python error: Aborted

Sorry its not really possible to reproduce the error.

Specs :

Ubuntu : 16.04

Issue 2:
Hello!

I'm a first-time contributor and attempting to set up a dev environment by following the instructions here: https://docs.scipy.org/doc/scipy/reference/dev/contributor/quickstart_ubuntu.html#quickstart-ubuntu

on step 19, I'm trying to run the runtests.py file but I am getting the following:

scipy/linalg/tests/test_decomp.py::TestEigh::test_eigh_integer realloc(): invalid next size Fatal Python error: Aborted at 21% completed.

I'm sure this is not an actual bug, so apologies if this isn't the right place to post this, but I really want to contribute to SciPy and I haven't managed to find any sort of fix to this from googling. I also recently installed Ubuntu to go through this set up so there may be some sort of issue there.
Issue 1:
The example of the std::num module speaks for itself. I can count at least three grammatical forms among the function descriptions:

indicative form (abs: Computes the absolute value.);

imperative form (acos: Compute the arccosine of the number.);

noun phrase (abs_sub: The positive difference of two numbers. or cos: Cosine function).

The various style guides (https://github.com/mozilla/rust/wiki/Note-style-guide, https://github.com/mozilla/rust/wiki/Doc-using-rustdoc and http://static.rust-lang.org/doc/master/rustdoc.html) recommend writing "sentences that begin with capital letters and end in a period" but do not mention how the sentences should be formed.

I am willing to work on making all this coherent but a convention should be fixed first.

Issue 2:
With a lot of library code expected to change before the 1.0 release, it doesn't make much sense to do this now, but the core and std libraries should use a consistent style for API documentation. The wiki makes some attempt at specifying conventions, but these need to be fleshed out and actually applied to the codebase.

Right now, some doc-comments are written in the third-person indicative:

pub fn map<T, U>(opt: &Option<T>, f: fn(x: &T) -> U) -> Option<U> {
//! Maps a `some` value by reference from one type to another

and some are written in the imperative:

pub fn chain<T, U>(opt: Option<T>,
f: fn(t: T) -> Option<U>) -> Option<U> {
/*!
* Update an optional value by optionally running its content through a
* function that returns an option.
*/

These two examples illustrate another inconsistency: Some summaries (the first line of the comment) have no terminal punctuation, while others end with a period.

One more thing that varies is the comment style itself. Some doc-comments look like

/*!
* foo...
* bar...
* baz...
*/

while others look like

/*!
foo...
bar...
baz...
*/

Once these rules (and others) are codified, I'd be happy to start going through the doc-comments and updating them.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

next@latest should add without incorrect peer dependency

Current Behavior

>yarn add react@latest react-dom@latest next@latest
yarn add v1.2.0
info No lockfile found.
[1/4] Resolving packages...
warning next > glob-promise > semantic-release > npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
warning next > glob-promise > semantic-release > @semantic-release/condition-travis > travis-deploy-once > travis-ci > request > node-uuid@1.4.8: Use uuid module instead
[2/4] Fetching packages...
info fsevents@1.1.2: The platform "win32" is incompatible with this module.
info "fsevents@1.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "styled-jsx@2.0.2" has incorrect peer dependency "react@15.x.x".
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 618 new dependencies.

>yarn check
yarn check v1.2.0
error "next#styled-jsx#react@15.x.x" doesn't satisfy found match of "react@16.0.0"
error Found 1 errors.
info Visit https://yarnpkg.com/en/docs/cli/check for documentation about this command.

Steps to Reproduce (for bugs)

yarn add react@latest react-dom@latest next@latest on Windows 7 laptop

Also try

>yarn check

After adding.

Context

I am currently developing an app with Next@3 and using React@15/Styled-JSX. I am now trying to install Next@4 and thought of using React@16/Styled-JSX@2. Not sure if this is an error with Yarn.

Apologize if this is a duplicate issue or a silly one.

Your Environment

Tech
Version

next
4.0.3

node
8.1.2

OS
Windows 7

browser
N/A

etc
N/A

Issue 2:
When doing a static export with assetPrefix defined in next.config.js, stylesheet does not link properly.

Script files are included as <assetPrefix>/_next/<...>/index.js, while the css file is included as /_next/static/style.css with no prefix.

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

Current Behavior

Stylesheet is linked as /_next/static/style.css with no prefix when assetPrefix is defined

Expected Behavior

Stylesheet should be linked as <assetPrefix>/_next/static/style.css when assetPrefix is defined

Your Environment

Tech
Version

next
canary (07-03-2018)

node
v8.4.0

OS
macOS Sierra

browser
Chrome Version 63.0.3239.132
Issue 1:
I'm submitting a ... (check one with "x")

[ ] bug report
[x] feature request
[ ] support request

Current behavior

There is no way how to get the value of 'formControlName' inside a custom validation function to identify which control is beeing actually validated (model-driven forms) because the only parameter is (c: FormControl) and the actual API of 'FormControl' is:

_errors, _onChange, _parent, _pristine, _status, _statusChanges, _touched,
_value, _valueChanges, asyncValidator, dirty, errors, pending, pristine,
root, status, statusChanges, touched, untouched, valid, validator, value, valueChanges

Expected/desired behavior

Be able to get 'formControlName' value inside a custom validation and generic function and use it as the identity of the actually validated control. It allows to have a dynamic set of validation rules for each control (for example in JSON syntax) that could be maintenated outside of the app code then.

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

To be more flexible and minimize the code = reducing the number of custom validators.

Please tell us about your environment:

Angular version: 2.0.0-rc.4

Browser: [all]

Language: [all]

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

[x ] feature request

Current behavior

Angular will always find and render component tag.

e.g. <my-component-tag>

Expected behavior

I would like to have an option to have component tag be ignored and just kept as a plain html.

e.g. <my-component-tag plainHtml>

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

A lot of external components are not compatible to other external directives, components.

And in order to get same html structure and get things working I would like to be able to create it manually.

Thanks.
Issue 1:
Many comments in the .less-Files start with //** which in a lot of programming languages is equal to a multi-column comment (/* ... */). Therefore any IDE not perfectly adjusted to LESS syntax highlighting (such as VisualStudio) tend to interpret these comments as multi-column, which is in the case of the bootstrap sources basically every following line, making the code more or less unreadable.

Sure, an answer to this request could be "go and set up a proper highlighting" 😉 But in the end this would be a very minor change without drawbacks (afaik) but nevertheless improving usability of the bootstrap sources.

An example of what I mean is in variables.less, line 27:

//** Background color for .

which without any effort could be changed to

// ** Background color for . (note the added space in col 3)

Issue 2:
I'm not sure why the comments in the variables.less got changed to this style //**, but it my opinion it was a brave move.

For me at least it prevents compilation when using the nodejs compiler lessc.

At also breaks the syntax highlighting in my IDE, Visual Studio 2013