WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Describe what you were doing when the bug occurred:

1.

2.

3.

Please do not remove the text below this line

DevTools version: 4.7.0-23309eb38

Call stack: at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163895)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

at I (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163773)

Component stack: at Gl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:345333)

at div

at div

at div

at Co (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:263571)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:366677

at n (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:276314)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:278724

at div

at div

at Xi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:325177)

at Ge (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:207026)

at sn (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:216342)

at Va (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:293773)

at us (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:371869)

Issue 2:
Note: @anushreesubramani is working on this, please don’t send PRs if you aren’t her :-)

Similar to #11081.

@anushreesubramani Wanna take this one as well? It would need to deduplicate based on owner/stack info, similar to how #11120 works.
Issue 1:
I'm submitting a ... (check one with "x")

[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Currently if you return a new Date() from a getter into an ngModel it freezes up the browser.

Expected behavior

That it would not cause an infinite loop

Minimal reproduction of the problem with instructions

have a getter method that returns a new Date() and put into an ngModel;

http://plnkr.co/edit/I0i4h6pu9ZqGfJk3XTNy?p=info

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

to be able to use a generated Date in ngModel.

Please tell us about your environment:

Ubuntu / Apache

Angular version: 2.1.0

Also was doing this in 2.0.0

Browser: [Chrome 53.0.2785.143]

Language: [all | TypeScript 2.0.3]

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

[x ] bug report => search github for a similar issue or PR before submitting

Current behavior

While implementing a custom ControlValueAccessor which should accept non-primitive model we can easily go into infinitive loop + browser crash. The work-around exists but is non-intuitive and requires boilerplate.

This happens for the following condition: <custom-control [ngModel]="foo()"> where foo() returns returns objects (non-primitive value) and can return different objects for subsequent calls (equal in terms of content but not equal in terms of references).

Expected/desired behavior

People should be able to use functions when binding to [ngModel] as it was the case till recently (I believe that it used to work till RC4 or RC5 where async component was introduced into ngModel impl).

Reproduction of the problem

Here is a minimal plunker based on the real life scenario: https://plnkr.co/edit/HlIgVEuZ3wfS5hFMjPFm?p=preview

In the above plunker there is a simple time-picker implementation that requires the following data structure as its input: {hour: number, minute: number};. It works fine when used as <time-picker [ngModel]="{hour: 13, minute: 30}"></time-picker>. But if a user wants to create {hour: 13, minute: 30} in a function call (ex. to convert internal string structure to a structure required by a date-picker) we go into infinitive loop.

To see infinitive loop + browser crash uncomment the following line <time-picker [ngModel]="strToTime(timeAsStr)"></time-picker>.

!!!WARNING!!! IT WILL CRASH YOUR BROWSER.

What is the expected behavior?

People can use functions to convert model values from internal data structures in a component (ex. string in my plunker) to data structures required by a control. Conceptually we need a mechanism similar to parsers / formatters pipeline from Angular 1.x.

Please tell us about your environment:

Angular version: 2.0.0-rc.5

Browser: all

Language: all

Additional info:

Discuses this use case with @mhevery and was advised to ping @kara

The issue was originally raised in the https://ng-bootstrap.github.io/ project under ng-bootstrap/ng-bootstrap#545
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

no error

Current Behavior

"'common' of undefined" error

Steps to Reproduce (for bugs)

yarn

yarn run dev

hit it on browser localhost:3000

Context

Your Environment

Tech
Version

next
v3

node
8.1.2

OS
sierra

browser
chrome latest

etc

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

Expected Behavior

Create new next app with create-next-app --example with-apollo with-apollo-app

Run the app with npm run dev.

In the app click on the About link and then click on the Home Link.

Home page should be displayed.

Current Behavior

Instead of displaying the Home page after clicking on the Home link from the About page I get to following error:

TypeError: Cannot read property 'data' of undefined
at new WithData (http://localhost:3000/_next/1512311880114/page/:18990:79)
at http://localhost:3000/_next/1512311880114/main.js:13520:24
at instantiate (http://localhost:3000/_next/1512311880114/main.js:13528:9)
at new WithData(Unknown) (http://localhost:3000/_next/1512311880114/main.js:13541:14)
at constructClassInstance (http://localhost:3000/_next/1512311880114/commons.js:6361:20)
at updateClassComponent (http://localhost:3000/_next/1512311880114/commons.js:7845:9)
at beginWork (http://localhost:3000/_next/1512311880114/commons.js:8231:16)
at performUnitOfWork (http://localhost:3000/_next/1512311880114/commons.js:10230:16)
at workLoop (http://localhost:3000/_next/1512311880114/commons.js:10294:26)
at HTMLUnknownElement.callCallback (http://localhost:3000/_next/1512311880114/commons.js:548:14)```
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

next

node

OS

browser

etc

Issue 2:
Hot module reloading does not work for .tsx pages in Next5.

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

Expected Behavior

Editing, for example, pages/index.tsx, should cause HMR to reload part of index.tsx.

Current Behavior

A browser warning is issued and the full page is reloaded:

Ignored an update to unaccepted module ./pages/index.tsx -> 2

Steps to Reproduce (for bugs)

Copy the with-typescript example into a clean directory

Edit package.json to next@5.0.1-canary.4

yarn install && yarn dev

Visit localhost:3000, open console.

Edit pages/index.tsx and save

Observe warning in the console and full reload.

I've observed this in next 5.0.0, 5.0.1-canary.2, and 5.0.1-canary.4 (canary3 not tested)

Chrome Version 64.0.3282.140

OSX High Sierra 10.13.3
Issue 1:
Its possible that tabs (or multiple spaces) are being miscounted somehow. It usually occurs after pasting something into the document. Here is what it looks like, after I attempt to Shift Tab, Undo then Redo. I am using a MAC.

describe('DELETED', function () {
it('get /deleted/tasks?since=<yesterday> returns list of tasks deleted', function (done) {
var yesterday = Date.now() - (24 * 3600 * 1000);
request.get({
uri: apiUrl + '/deleted/tasks?since=' + yesterday,
auth: {
user: 'regular',
pass: users.regular
},
json: true
},
function (err, response, body) {
response.statusCode.should.equal(200, JSON.stringify(body));
body.data.length.should.be.greaterThan(0);
done();
});

// CHARACTERS HAVE GONE MISSING HERE

EARCHES', function() {
it('verify template_python returns from a search', function(done) {
this.timeout(10000);
request({
method: 'GET',
uri: apiUrl + '/search/template_python',
auth: {
user: 'regular',
pass: users.regular
},

Issue 2:
I wanted to indent multiple lines at once but it failed. This is how it looks like when I select some lines and press Tab. Sometimes it works though, like when creating an untitled file in split screen.

Quite important bug @egamma @jrieken @bpasero
Issue 1:
Problem description

Make Horizontal Stepper Responsive

Link to minimally-working code that reproduces the issue

Versions

Material-UI: latest

React: latest

Browser: Chrome

Issue 2:
In order to use the stepper in a responsive way, it's necessary to seamlessly switch between vertical and horizontal stepper (e.g. someone switches from landscape to portrait-mode), without having to rebuild the component (and losing the step's states therefor).

So what I have is a vertical stepper:

If I switch the orientation from 'vertical' to 'horizontal' it looks like this:

What I would expect is something like this:

Material-UI: 0.16.5

React: 15.3.2

Browser: Any
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

On trying to analyse a component State using React Developer Tools, the analyse pane stays in the Loading ... state and throws this error

Uncaught TypeError: Cannot read property 'name' of undefined
at O (backend.js:1)
at s (backend.js:1)
at s (backend.js:1)
at s (backend.js:1)
at l (backend.js:1)
at Object.inspectElement (backend.js:6)
at t.<anonymous> (backend.js:6)
at t.r.emit (backend.js:6)
at backend.js:32
at t (backend.js:8)

What is the expected behavior?

Able to analyse component State as in the previous React Dev Tools versions.

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

React Developer Tools version: 4.3.0 (12/20/2019)

React Version: ^16.4.0

Browsers:

Chrome: Version 79.0.3945.88 (Official Build) (64-bit)

Brave: Version 1.1.23 Chromium: 79.0.3945.88 (Official Build) (64-bit)

Issue 2:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Select a component

The right panel (property panel?) always shows Loading...

The following error is printed to the console.

backend.js:1 Uncaught TypeError: Cannot read property 'name' of undefined
at O (backend.js:1)
at s (backend.js:1)
at s (backend.js:1)
at l (backend.js:1)
at Object.inspectElement (backend.js:6)
at t.<anonymous> (backend.js:6)
at t.r.emit (backend.js:6)
at backend.js:32
at t (backend.js:8)

I don't know why you minify the output, but the call stack points to here:

react/packages/react-devtools-shared/src/utils.js

Line 391
in
f887d1a

} else if (data.constructor.name === 'ArrayBuffer') {

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

https://codesandbox.io/s/falling-wave-1j0qe

What is the expected behavior?

React DevTools displays the props of the selected component.

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

React 16.12.0

Chrome 79.0.3945.88

IDK
Issue 1:
I have a strong habit of opening files from Windows Explorer. My prefered method is to double-click the file. Herein lies the issue: Atom is not only hidden in %appdata% where it can be difficult to find, but there is no static file to associate to since atom.exe is in a versioned directory.

My suggestion is to create a very basic launcher that opens the latest version of Atom installed so that users can associate files to Atom without needing to update associations every update.

Issue 2:
Currently it is not so easy to assign atom as default editor on windows eg for all .css files

the path to atom.exe is changed with every update.

no exe in C:\Users\hebbet\AppData\Local\atom

Chrome has eg an chrome.exe in:

C:\Users\username\AppData\Local\Google\Chrome SxS\Application which starts chrome with the currect folder.
Issue 1:
Symfony version(s) affected: Probably all of them, but I am currently in 4.1

Description

When you try to put the Translator Path in an envrionment variable, Symfony try to check if the Path exist BEFORE the compilation of the envrionment variable.

So with '%env(resolve:PATH_TRANSLATION)%', Symfony throw an UnexpectedValueException : %env(resolve:PATH_TRANSLATION)% defined in translator.paths does not exist or is not a directory.

How to reproduce

You can reproduce the bug easily by adding an environment variable (in .env) and resolve it in the config file.

framework:
translator:
paths:
- '%env(resolve:PATH_TRANSLATION)%'

Possible Solution

Symfony should resolve the environment variable before checking if the file exist or not.

Additional context

Symfony bump into here ==> https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/FrameworkExtension.php#L1020

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.3.9

when using an env var inside the value of a framework.translator.paths, the env var value is not resolved, and instead its placeholder is given to the translator

parameters:
active_site: '%env(ACTIVE_SITE)%'

framework:
translator:
paths:
- "%kernel.root_dir%/../src/ST/AppBundle/Resources/translations_sites/%active_site%"

UnexpectedValueException

/var/www/app/../src/ST/AppBundle/Resources/translations_sites/env_ACTIVE_SITE_1210a6ec49918eebfffc01fc4f72ca65 defined in translator.paths does not exist or is not a directory

note: same thing happen if I use the env directly like that:

framework:
translator:
paths:
- "%kernel.root_dir%/../src/ST/AppBundle/Resources/translations_sites/%env(ACTIVE_SITE)%"
Issue 1:
In type definition @types/react is bug in interface LinkHTMLAttributes.

Issue 2:
I tried using the @types/autoprefixer package and had problems.

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

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

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

Authors: @odnamrataizem

When compiling a project which contains gulp-postcss and autoprefixer I find myself facing the following errors:

[20:12:38] gulp-tsb [commonjs] 2 errors across 2 files
[20:12:38]
./node_modules/@types/autoprefixer/node_modules/postcss/lib/postcss.d.ts
1305:4 Duplicate identifier 'export='.

./node_modules/postcss/lib/postcss.d.ts
1283:4 Duplicate identifier 'export='.

I have a theory although I'm not certain: Is it due to the fact that @types/autoprefixer lists postcss as a dependency, ought it be a dev dependency and a peer dependency? Would that provide the typings for development but stop it from duplicating postcss.d.ts (as per above) when included as a dependency in a project. Is this idea testable?
Issue 1:
Dropdown not working on the navigation bar on Android.

I'm testing in some browsers for Android.

Links within the dropbox dont work.

Issue 2:
I had a project using more or less the same menu and it worked. Found out it was using Bootstrap version 2.3.1. Compared version 2.3.2 and 2.3.1 and found that in version 2.3.2 there's this snippet of CSS that reads:

.dropdown-backdrop {
position: fixed;
left: 0;
right: 0;
bottom: 0;
top: 0;
z-index: 990;
}

and the rule: position: fixed; seems to cause all the problems.

I still don't undertand the point of the markup that is added by the bootstrap dropdown plugin:

<div class="dropdown-backdrop"></div>

So I've temporarily fixed the bug on my end by adding a style to override the style causing the problem:

.dropdown-backdrop {
position: static;
}

To me this looks like a bug introduced from version 2.3.1 to 2.3.2. Maybe I'm wrong. If someone could explain the purpose of the empty div, it would be helpful.
Issue 1:
Bug report

Bug summary

When using a colormap to generate a color array with data that contains np.nan (NaN), an warning is given, and the previous color entry is duplicated. The method that has this issue is to_rgba.

Code for reproduction

import numpy as np
from matplotlib.colors import Normalize
from matplotlib import cm

y = np.linspace(0.0, 1.0, 4)
y[1] = np.nan

norm = Normalize(0.0, 1.0)
colormap = cm.ScalarMappable(norm, 'rainbow')
colors = colormap.to_rgba(y)

print(colors)

Actual outcome

/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/matplotlib/colors.py:496: RuntimeWarning: invalid value encountered in less
cbook._putmask(xa, xa < 0.0, -1)

[[ 5.00000000e-01 0.00000000e+00 1.00000000e+00 1.00000000e+00]
[ 5.00000000e-01 0.00000000e+00 1.00000000e+00 1.00000000e+00]
[ 8.33333333e-01 8.66025404e-01 5.00000000e-01 1.00000000e+00]
[ 1.00000000e+00 1.22464680e-16 6.12323400e-17 1.00000000e+00]]

Expected outcome

NaN values should be quietly handled. I think the most reasonable output would be to fill the color array with np.nan rather than copy the previous entry.

[[ 5.00000000e-01 0.00000000e+00 1.00000000e+00 1.00000000e+00]
[ NaN NaN NaN NaN]
[ 8.33333333e-01 8.66025404e-01 5.00000000e-01 1.00000000e+00]
[ 1.00000000e+00 1.22464680e-16 6.12323400e-17 1.00000000e+00]]

Matplotlib version

Operating system: OSX

Matplotlib version: 2.0.2

Matplotlib backend: module://ipykernel.pylab.backend_inline & MacOSX

Python version: 3.6.3

Jupyter Notebook version: 5.2.0

Other libraries: None

Issue 2:
Bug summary

The default minor colorbar ticks in matplotlib 3.5.1 look strange in the presence of major ticks determined by BoundaryNorm. Thought I had seen this issue in a previous thread but can't seem to find it... apologies if this is a duplicate.

Code for reproduction

import matplotlib
import numpy as np
import matplotlib.pyplot as plt

crf_bounds = np.array([0, 0.7, 0.75, 0.8, 0.85, 0.9, 0.95, 0.97, 0.98, 0.99, 1.0])
norm = matplotlib.colors.BoundaryNorm(boundaries=crf_bounds, ncolors=256)

x = y = np.array([-10, -5, 0, 5, 10])
np.random.seed(20)
data = np.random.uniform(0,1,(4,4))

fig = plt.figure()
ax = fig.add_subplot()
m = ax.pcolormesh(x, y, data, cmap='RdYlGn', norm=norm)
cb = fig.colorbar(m)
cb.minorticks_on()

Actual outcome

Matplotlib 3.5.1 result:

Expected outcome

Matplotlib 3.2.1 result:

Additional information

No response

Operating system

MacOS

Matplotlib Version

3.5.1

Matplotlib Backend

module://matplotlib_inline.backend_inline

Python version

3.9.9

Jupyter version

3.1.18

Installation

conda
Issue 1:
Hi, two question about glide.

1、How to clear cache of a specific url?

clearDiskCache() and clearMemory() will chear all cache, but this is not what I want?

2、How to get bitmap?

Issue 2:
Glide Version: 3.7.0

Device/Android Version: Android 4.4.2 - wolfgang AT-AS55HD1

Glide load line / GlideModule (if any) / list Adapter code (if any): RecyclerAdapter

Glide.with(context)
.load(APIRoutes.getProjectBlobURL(project.getProjectID(), accountConfiguration.peekLocalAccountToken()))
.placeholder(R.drawable.ic_image_black_24dp)
.into(holder.projectImage);

Layout XML:

<ImageView
android:id="@+id/project_image"
app:srcCompat="@drawable/ic_image_black_24dp"
android:adjustViewBounds="true"
android:layout_width="@dimen/material_list_avatar_size"
android:layout_height="@dimen/material_list_avatar_size"
android:layout_marginLeft="@dimen/material_baseline_grid_1x"
android:layout_marginBottom="@dimen/material_baseline_grid_1x"
android:layout_marginTop="@dimen/material_baseline_grid_1x"
app:layout_constraintLeft_toLeftOf="parent"
app:layout_constraintTop_toTopOf="parent"
app:layout_constraintBottom_toBottomOf="parent"/>

Stack trace / LogCat:

paste stack trace and/or log here
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): First attempted via #kubernetes-users on slack

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): internal aws load balancer

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Feature

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.5+b0deb2e", GitCommit:"b0deb2eb8f4037421077f77cb163dbb4c0a2a9f5", GitTreeState:"not a git tree", BuildDate:"2016-08-21T12:21:36Z", GoVersion:"go1.7", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.5+coreos.0", GitCommit:"d7a04b1c6044647f5919fadf3cecb9ee70c10fc5", GitTreeState:"clean", BuildDate:"2016-08-15T21:01:42Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: AWS

OS (e.g. from /etc/os-release): CoreOS

Install Method: kube-aws

Our use case:

We are extending our on premise infrastructure into the AWS Cloud. It's meant to be internal-only and we're taking measures to guarantee that security.

Feature Request:

A method to guarantee that the environment stays internal and does not accidentally get exposed externally.

Possible Methods I've explored:

AWS IAM Policy to restrict kubernetes from creating a public ELB

AWS Security Group limiting client source IPs

I was speaking with @justinsb on #kubernetes-users on slack and he suggested I submit a request for this here.

Issue 2:
I haven't found a way of pausing/decommissioning a node, have all its containers stopped and recreated elsewhere in the cluster.

This would be great for node upgrades (hardware, OS, etc.).

Obviously, the node would have to be blacklisted so that no new containers are scheduled to it.

/cc @jmreicha
Issue 1:
http/3 support?

https://www.rfc-editor.org/rfc/rfc9114.html

Issue 2:
Hi 👋🏻

I have tried Deno several times, before version 1.0, and with the latest version. One obvious problem I see, and which I think is huge, is the permission system. Currently, when we run a script with Deno, we have to specify the different permissions we want using arguments like --allow-run, --allow-read.... or --all or -A in order to accept all permissions.

The point is that by allowing all permissions on a program, we expose ourselves to serious risk to the machine or the user, but out of "developer laziness", we don't want to have an execution line like:

deno run --allow-read --allow-net --allow-write --allow-env mod.ts

That's why I propose a new way of working. Arguments are still important, especially for everything CI. At the same time, for a better user experience, I can see something like:

deno run mod.ts
mod.ts needs the net permission. Do you allow it?
- Yes
- No
> Yes
mod.ts needs the write permission. Do you allow it?
- Yes
- No
> Yes

Once the developer has entered his preferences, they are cached, so that he doesn't have to specify them again.

An alternative would be to have a configuration file for this, specifically, add this possibility to the current configuration system.

I think a better developer experience at this level would bring more developers into the project, or at least interest a part of the community.

This is an open suggestion, and I would love to hear from the developers and the Deno team about this one.