WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Context:

Playwright Version: 1.19.2

Operating System: macOS

Node.js version: 14.x

Browser: Chromium

Extra: CI environment (Azure Pipelines)

Describe the bug

I just recently wanted to update to the 1.19.x release line for our tests in VSCode and now noticed how our smoke tests in web are almost 100% slower:

OLD

NEW

At first glance I could not find a single operation that would be slower, it seems like the entire run is slower, getting us closer to a 10 minute timeout we configured.

Starting an issue here to ask: has this been reported by others, how can we drill into this further?

Issue 2:
Context:

Playwright Version: [1.21.1]

Operating System: [Windows]

Node.js version: [14.15.1]

Browser: [Chrome]

Chrome version: [Version 101.0.4951.54]

Code Snippet

test('Demo Test Scenario:', async ({ page }) => {
await page.goto('https://usk.enterprisetube.com/');
await page.waitForSelector('[data-e2e-span="vidizmo-app"]', { state : "attached" });
await page.click('[data-e2e-link="LoginSignInButton"]');
await page.fill('[data-e2e-input="emailAddress"]', 'fahad@sharklasers.com');
await page.fill('[data-e2e-input="Password"]', 'Admin@123');
await page.click('[data-e2e-btn="signIn"]');
await page.waitForSelector('[data-e2e-heading="MashupsMostMostRecent"]')
await page.click('[data-e2e-link="selectMenuBar"]');
await page.click('[data-e2e-link="MediaManager"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
await page.click('[data-e2e-btn="toggleFilters"]');
});

Describe the bug

If we run the above code when the trace is on in the config then it completes within the 30-40 seconds, if the trace is off then it completes in the 7-8 seconds in the latest chrome version but in the chrome version 95 in both cases time is same

following are the results of the test

Chrome Version : Version 101.0.4951.54

Trace On in config

takes 30-40 Seconds

Trace off in config

takes 7 Seconds

Chrome Version : Version 95

Trace On in config

takes 7 Seconds

Trace off in config

takes 7-8 Seconds

Configuration file

const config: PlaywrightTestConfig = {
testDir: './tests',
timeout: 30 * 1000,
expect: {
timeout: 5000
},
forbidOnly: !!process.env.CI,
workers: process.env.CI ? 1 : undefined,
reporter: 'html',
use: {
actionTimeout: 0,
channel : "chrome",
trace: 'off',
},
};
export default config;

I can also provide the sample github repository if needed

This issue is related to following Bug #13498
Issue 1:
ex. one space click will become 2, a "arrow left" key will actually go up 2 levels

Issue 2:
No drop-down for Cut,Copy &Paste Only Reveal in Tree View shown

Pasting any text using Ctrl+v causes pasting text twice

Backspace deletes 2 characters

Right key moves 2 cursor further

Down key moves 2 lines down

Information

Atom Version: 0.132.0

OS: Windows 8.1
Issue 1:
Problem

(A follow-up on #20548.)

The purpose of contour and tricontour is to draw contour lines along given levels. The algorithm tries to close the contour loops, but sometimes that's not possible or useful. Example:

import numpy as np
import matplotlib.pyplot as plt

xmin, xmax = -3.0, 3.0
ymin, ymax = -3.0, 3.0
nx, ny = 500, 500

def f(z):
return np.angle(z)

x = np.linspace(xmin, xmax, nx)
y = np.linspace(ymin, ymax, ny)
X, Y = np.meshgrid(x, y)
fZ = f(X + 1j * Y)

c = plt.contour(X, Y, fZ, levels=[0.7853981633974483], colors="k")
plt.show()

The left "arm" of the contour is wrong. Let's verify this by computing the values:

for allseg in c.allsegs:
for seg in allseg:
x, y = seg.T
z = x + 1j * y
print(f(z))

[3.14109133 3.14108931 3.14108728 3.14108523 3.14108316 3.14108107
# ...
3.13344468 3.13287655 3.13222326 3.1314641 3.13057109 3.1295054
3.12821158 3.12660761 3.12456683 3.12188272 3.1181943 3.11280868
3.10420637 3.08829091 3.04901618 2.8198421 0.78539816 0.78539816
0.78539816 0.78539816 0.78539816 0.78539816 0.78539816 0.78539816
0.78539816 0.78539816 0.78539816 0.78539816 0.78539816 0.78539816
# ...
.78539816 0.78539816 0.78539816 0.78539816 0.78539816 0.78539816
0.78539816 0.78539816]

Note that the specified level is 0.7853981633974483, so the first half is completely off. A previous comment suggests that the contouring algorithm is right, though.

To fix this, I manually set the corresponding segments to np.nan which prevents plotting. However, this does not work for tricontour as I don't have a function f() that I can evaluate at the segments. The contouring algorithm itself must compute the values somewhere, so my suggestion would be to expose those values to the user.

Issue 2:
I tried to get a contour plot of the complex angles of a particular function, but always got one level too many around zeros and infinities. Consider the following MWE which is supposed to plot the contour line for pi / 4 only. It plots pi / 4 alright, but also pi.

import numpy as np
import matplotlib.pyplot as plt

xmin, xmax = -3.0, 3.0
ymin, ymax = -3.0, 3.0
nx, ny = 500, 500

x = np.linspace(xmin, xmax, nx)
y = np.linspace(ymin, ymax, ny)
X, Y = np.meshgrid(x, y)
fZ = np.angle(X + 1j * Y)

plt.contour(X, Y, fZ, levels=[0.25 * np.pi], colors="k")
plt.gca().set_aspect("equal")
plt.show()

This is with mpl 3.4.2.

Edit: A very similar report is on stackoverflow.
Issue 1:
Edit July 2021: The layouts example has been updated to persist state across page transitions: https://github.com/vercel/next.js/tree/canary/examples/layout-component

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

Expected Behavior

Expected to render css on the server first, using specific code in _document.js. So, expected behavior would be to see no FOUC.

Current Behavior

CSS is not rendered on the server, only on the client. It's interesting that class names are applied correctly on the server, only actual CSS is not rendered. As the result, we see FOUC before client side catch up.

This happened right after updated to 5.0. Latest canary releases also broken.

Steps to Reproduce (for bugs)

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-fela

cd with-fela

yarn

yarn dev

Context

Your Environment

Tech
Version

next
5.0.0 / 5.0.1-canary.4 / 5.0.1-canary.5 / 5.0.1-canary.9

node
9.5.0

OS
OSX 10.13.3
Issue 1:
Doesn't seem to haven been caused by my change: https://storage.cloud.google.com/kubernetes-jenkins/pr-logs/pull/27083/node-pull-build-e2e-test/10720/build-log.txt

Summarizing 3 Failures:

[Fail] [k8s.io] Downward API [It] should provide pod name and namespace as env vars [Conformance]
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2022

[Fail] [k8s.io] Downward API [It] should provide pod IP as an env var
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2022

[Fail] [k8s.io] Downward API [It] should provide container's limits.cpu/memory and requests.cpu/memory as env vars
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2022

Ran 19 of 22 Specs in 1130.000 seconds
FAIL! -- 16 Passed | 3 Failed | 0 Pending | 3 Skipped --- FAIL: TestE2eNode (1130.00s)
FAIL

Ginkgo ran 1 suite in 18m50.080565864s
Test Suite Failed

[k8s.io] Downward API
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:660
should provide container's limits.cpu/memory and requests.cpu/memory as env vars [It]
/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/downward_api_test.go:130

Expected error:
<*errors.errorString | 0xc8207f9770>: {
s: "gave up waiting for pod 'downward-api-63e732e1-334a-11e6-b754-42010af00048' to be 'success or failure' after 5m0s",
}
gave up waiting for pod 'downward-api-63e732e1-334a-11e6-b754-42010af00048' to be 'success or failure' after 5m0s
not to have occurred

/var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2022

Issue 2:
#8917 deletes tests for deprecated apis. Now we will add tests for v1. I will make several small PRs and refer to this issue.

@bgrant0607 @krousey @nikhiljindal
Issue 1:
VSCode Version: 1.0.0

OS Version: Windows

I love this editor. it's awesome, very fast response, open, edit.

but it's not support emmet expand abbreviations in custom syntax eg .blade, .vue

i try to add "files.associations": {"*.blade.php": "html"}, emmet work but my extension blade syntax hilighting not working. if it's can work together i think my heart is got by vscode 👍

if next release has settings about enable emmet expand abbreviations in settings.json or other place.

i think it's wonderful text editor in this world.

Best regard

ps. sorry for my bad english

Issue 2:
VSCode Version: 1.3.1

OS Version: Ubuntu 16.06

Steps to Reproduce:

Install Nunjucks plugin.

Type p and press tab.

\t was inserted.

Expected Result:

p expanded to <p></p>.

I was looking for the setting to enable emmet, but it seems hard-coded in the source (src/vs/workbench/parts/emmet/node/editorAccessor.ts#L20).

Can we modify this value through preference?

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

Expected Behavior

We should have documented as an example how to use the new next-sass plugin

Current Behavior

We have a few examples to import .sass files which are mostly hacks to make it work.

Context

With the release of Next.js v5 the current examples of importing SASS/SCSS are outdated and can be simplified with the new next-css plugin.

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

Expected Behavior

Both URLs /foo and /foo/ should render the contents of /pages/foo/index.js.

Current Behavior

/foo works fine, but /foo/ causes a 404 error on SSR and only reconciles later at client side rendering.

Steps to Reproduce (for bugs)

create minimal next.js project

create /pages/foo/index.js including e.g. export default () => <div>hello world</div>

test url /foo/, should throw 404 on SSR

Context

Your Environment

Tech
Version

next
5.0.0

node
8.9.0
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1700 on 2010-12-24 by trac user johnmark54, assigned to @rgommers.

After installing python binary

python-2.7.1.amd64.msi from python.org

the install of

numpy-1.5.0-win32-superpack-python2.7.exe

fails with error:''

Python 2.7 required, which was not found in the registry.''

Reinstalling python, using different versions of python etc. does not help.

Python runs fine.

(Is this the right place to report this?)

-john.m.agosta@intel.com

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1621 on 2010-09-26 by trac user alxx, assigned to @rgommers.

When installing numpy-1.5.0-win32-superpack-python2.7 on windows7 64 bit, the installer can not find python2.7 in the registry.

Its a know problem with the distutils installer.

see http://bugs.python.org/issue6792

and

http://stackoverflow.com/questions/3652625/installing-setuptools-on-64-bit-windows

Need to have a separate 64 bit windows installer or look for the additional registry entries to find the install location or have a fall through that allows a user to still install even if it doesn't find python 2.7.

PyQt v4.7.7 uses the fall through option.

wxpython has a separate installer

Someone provides unofficial numpy (and scipy) binaries here http://www.lfd.uci.edu/~gohlke/pythonlibs/

but I'd much prefer using an official package (if possible)
Issue 1:
It's a little sad that this isn't defined. For instance, in VectorizedRoutines.jl, the implementation of rep taking a number as the first argument has to either create a temporary array, or duplicate code, or create an immutable AbstractArray subtype that wraps a number. Neither are very attractive.

Is there any reason why the definition

eachindex(::Number) = 1

does not exist? I realize Numbers are not AbstractArrays, but neither are Tuples or Associatives. If this definition seems acceptable to most, I'll make a PR.

Issue 2:
On master, I get

julia> FloatRange(10.0,1.0,11.0,10.0)
WARNING: FloatRange{T}(start::T, step, len, den) is deprecated, use Base.floatrange(T, start, step, len, den) instead.
Stacktrace:
[1] depwarn(::String, ::Symbol) at ./deprecated.jl:62
[2] FloatRange(::Float64, ::Float64, ::Float64, ::Float64) at ./deprecated.jl:50
[3] eval(::Module, ::Any) at ./boot.jl:236
[4] eval_user_input(::Any, ::Base.REPL.REPLBackend) at ./REPL.jl:66
[5] macro expansion at ./REPL.jl:97 [inlined]
[6] (::Base.REPL.##1#2{Base.REPL.REPLBackend})() at ./event.jl:73
while loading no file, in expression starting on line 0
ERROR: MethodError: no method matching floatrange(::Type{Float64}, ::Float64, ::Float64, ::Float64, ::Float64)
Closest candidates are:
floatrange(::AbstractFloat, ::AbstractFloat, ::Real, ::AbstractFloat) at twiceprecision.jl:108
floatrange{T}(::Type{T}, ::Integer, ::Integer, ::Integer, ::Integer) at twiceprecision.jl:94
Stacktrace:
[1] FloatRange(::Float64, ::Float64, ::Float64, ::Float64) at ./deprecated.jl:52

This broke StatsBase.

cc: @timholy
Issue 1:
Both are providing support for static linking and link-time optimization. A 300% increase in size with no increase in scope of the libraries is quite bad. The standard library itself went from 39M to 42M but this can be explained by the added features and some cases of temporarily duplicated code like Vec<T> and ~[T]. I have not yet investigated the exact cause of the enormous increase in size.

Issue 2:
play.rust-lang.org: http://is.gd/AnPaWL

When the same trait is used more than one time but for different concrete types, it triggers the error for duplicate constraints without being sound.

pub trait Get<T> {
fn get(&self) -> T;
}

pub struct Foo {
one: uint,
two: uint
}

pub struct One(pub uint);
pub struct Two(pub uint);

impl Get<One> for Foo {
fn get(&self) -> One { One(self.one) }
}

impl Get<Two> for Foo {
fn get(&self) -> Two { Two(self.two) }
}

// error: trait `Get<Two>` already appears in the list of bounds [E0127]
fn bar<T: Get<One> + Get<Two>>(bar: &T) {
let One(one) = bar.get();
println!("{}", one);
let Two(two) = bar.get();
println!("{}", two);
}

fn main() {
let foo = Foo { one: 1, two: 2 };
// Works:
let One(one) = foo.get();
println!("{}", one);
let Two(two) = foo.get();
println!("{}", two);
// Does not work:
bar(&foo);
}
Issue 1:
The List of extensions is displayed, but when I click on one iE Elm it shows

Error getaddrinfo ENOTFOUND marketplace.visualstudio.com marketplace.visualstudio.com:443

Vscode was started from the commandline with

>set | grep proxy
https_proxy=http://user:pw@ip:port
http_proxy=http://user:pw@ip:port

System proxy is defined though an Automatic configuration script via th url of a *.pac file.

When I start vscode from start, without those environment variables, the above error shows already when loading the list of extensions.

PS. Thanks for the great work.

Issue 2:
Whenever I try to install any extension, using ext install, I get a connect ETIMEDOUT 191.238.172.191:443 error.

Trying to navigate to https://191.238.172.191 in the browser produces a warning regarding the certificate being valid only for *.market.visualstudio.com, but I'm allowed to proceed.

Shouldn't VSCode try to connect to the name instead of the IP?

I'm behind a proxy, VSCode updates just fine behind it, and also lists the available extensions. The firewall here logs the invalid certificate but allows the connection to proceed. Doesn't look like a problem in my end...

OS: Windows 7

VSCode: 0.10.1
Issue 1:
Challenge Waypoint: Target Elements by ID Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; rv:42.0) Gecko/20100101 Firefox/42.0.

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

My code:

<script>
$(document).ready(function() {
$("button").addClass("animated bounce");
$(".well").addClass("animated shake");
$("#target3").addClass("animated fadeOut");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Issue 2:
Challenge Waypoint: Use Hex Code for Specific Colors has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586.

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

My answer is correct but wrongly flagged as erroneous.

My code:

<style>
body {
background-color: #000000;
}
</style>
Issue 1:
I just noticed today that it is nearly impossible to give a RaisedButton a gradient. So I'm asking that BoxDecoration, or a Gradient property, be added to all material components.

Issue 2:
Internal: b/141787699

Flutter doesn't have a good way of decorating a button with something that isn't a flat color. This is because the underlying Material widget doesn't allow for it.

Right now we just stack a DecoratedBox behind a MaterialButton with a transparent background. This works for our larger buttons, but fails for our smaller buttons, since the MaterialButton pads the height up to 48dp. This makes the button look like a regular sized button and there's no reasonable way to workaround it.

A proper fix would be to allow a BoxDecoration to be specified in ButtonThemeData. Then we can remove the Stack + DecoratedBox workaround.

Related to or same as #21125
Issue 1:
When useAcrylic is turned off, ctrl+shift+scroll doesn't enable it. This stops people from adjusting their transparencies.

original text

Your Windows build number: (Type ver at a Windows Command Prompt)

Microsoft Windows [Version 10.0.18362.86]

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

CTRL+Shift+Scroll in cmd.exe works fine with transparency/blurring

CTRL+Shift+Scrol in Powershell.exe doesnt do a thing

What's wrong / what should be happening instead:

I was under the impression that it would work the same als the cmd.exe.

Issue 2:
Perhaps I overlooked it browsing through the json file but i didn't see another means to achieve transparency and i'm not a fan of the acrylic effects blurring factor or the fact that it turns off when the window is not selected. The traditional console provides for a static opacity just like in most nix envs, i'd hope it's just a matter of time before it's implemented here?
Issue 1:
Running log2 on an array of zeros with float dtype results in small non-zero numbers and sometimes nan.

Reproducing code example:

import numpy as np
x = np.zeros((1, 10), dtype=np.float)
print(x > 0)
print(np.log2(x, where=x > 0))

Error message:

[[False False False False False False False False False False]]
[[0.00000000e+000 0.00000000e+000 1.77229088e-310 3.50977866e+064
0.00000000e+000 0.00000000e+000 nan nan
3.50977942e+064 2.23604912e-314]]

Numpy/Python version information:

>>> import sys, numpy; print(numpy.__version__, sys.version)
1.15.4 3.6.6 |Anaconda custom (64-bit)| (default, Jun 28 2018, 11:07:29)
[GCC 4.2.1 Compatible Clang 4.0.1 (tags/RELEASE_401/final)]

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/83 on 2006-04-27 by @edschofield, assigned to unknown.

As of SVN revision 2431, matrix objects preserve orientation in methods that take axis arguments for axis=0 and axis=1. For axis=None, they return a matrix of shape (1, 1). For example:

>>> x = asmatrix(random.uniform(0,1,(3,3)))
>>> x.std()
matrix([[ 0.26890557]])

>>> x.argmax()
matrix([[4]])

I believe this behaviour is unfortunate, and that an operation aggregating a matrix over all dimensions should return a scalar.

Arguments for reducing dimensionality upon aggregation have been presented in several numpy-discussion threads, most recently in [Broadcasting rules (Ticket 76)].

This patch modifies this behaviour to return scalars (as rank-0 arrays) instead. It also removes some code duplication.

The behaviour with the patch is:

>>> x.std()
0.29610630190701492

>>> x.std().shape
()

>>> x.argmax()
3

A potential drawback to this patch is that matrix operations aggregating along all dimensions, which would now share the behaviour of numpy arrays, would be no longer be consistent with matrix operations that aggregate along only one dimension, which currently return matrices with height or width 1. This could be an argument for introducing a new vector class to represent one-dimensional data with orientation. Matrix objects, by contrast, are inherently 2-d.
Issue 1:
import torch

torch.autograd.Variable(torch.LongTensor([18])) / 0.0625
# Floating point exception (core dumped)

torch.LongTensor([18]) / 0.0625
#Traceback (most recent call last):
# File "<stdin>", line 1, in <module>
# File ".../lib/python2.7/site-packages/torch/tensor.py", line 294, in __div__
# return self.div(other)
#TypeError: div received an invalid combination of arguments - got (float), but expected one of:
# * (int value)
# didn't match because some of the arguments have invalid types: (float)
# * (torch.LongTensor other)
# didn't match because some of the arguments have invalid types: (float)

at 0.4.0a0+b608ea9; related to #327 and maybe #5411

Probably the cause is that in the variable case, it casts the divisor as Long and it triggers integer division by zero. But why only in the variable case?

Didn't test it after the tensor+variable merge, since don't want to migrate to vNext before ECCV deadline :)

Issue 2:
Example below. We should probably return a floating tensor like numpy does.

>>> import torch
>>> a = torch.tensor([1,2,3], dtype=torch.long)
>>> a + 0.5

1
2
3
[torch.LongTensor of size (3,)]