WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hi,

The moment i upgraded from an older version to v0.10.1it started crashing. I can not open it anymore.

I tried downloading greater version like

v0.10.2

v0.10.3

But that does not work either. Please see attached file crash info.txt for more information.

Thanks

Issue 2:
See microsoft/vscode#296 for details. The stacktrace seems to be all in Electron land. Any ideas?
Issue 1:
右键弹出菜单位置错误

在放大的情况下（ctrl + +)，右键点击弹出的菜单，位置偏左，放大倍数越大，偏左越明显。

Issue 2:
When I zoom in (using Ctrl+Shift++) the context menu that is shown when I right click somewhere is displayed in the wrong place. I attached two images one without any zoom where the menu is displayed correctly in the second one how is displayed after pressing Ctrl+Shift++ twice. In both cases the click is where the text cursor is.

Some information about my environment: This is under Windows 10. I'm using two monitors both with scaling of 125% (by that I mean the option named "change size of text apps and other items" in the diplay settings ) and the resolutions of the displays are 2560x1440 and 1080x2024.
Issue 1:
I'm submitting a ... (check one with "x")

[ X ] bug report
[ ] 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

While configuring router (createUrlTree()), exception thrown trying to call access undefined rxjs_observable_of.

Expected/desired behavior

Router library to properly utilize existing rxjs UMD

Reproduction of the problem

Create any application with routing using Router 3.0.0-beta.2 and rxjs UMD bundle.

What is the expected behavior?

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

To use UMD modules

Please tell us about your environment:

Angular version: 2.0.0-rc.4, router 3.0.0-beta.2, rxjs 5.0.0-beta.6

Browser: Chrome; Firefox

Language: typescript 1.8.10

Issue 2:
So, in the RootRouter.commit method, the RouteParams are appended twice to the URL, causing an URL like this

http://host.com/path?state=3&code=4

to be transformed to an url like this

http://host.com/path;state=3;code=4?state=3&code=4

by angular.

This is not very pretty, and can cause problems, especially if you allow forward slashes in url query parameters, as I propose in #7312.

So the question is, how to fix this issue? I would propose to only append RouteParams by query parameters and drop matrix variables. However, I don't know if that is as easily done than said.

If matrix parameters need to be supported, then I would suggest, that they are supported by some sort of strategy pattern, so we can prevent duplication of parameters in the URL.

Does anybody have an opinion on this?
Issue 1:
WARNING - Refused to delete permission view, assoc with role exists DAG Runs.clear Admin

Issue with airlow webserver command on airflow 2.1.0

Please help

Issue 2:
Apache Airflow version:

1.10.11

Kubernetes version (if you are using kubernetes) (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.6", GitCommit:"dff82dc0de47299ab66c83c626e08b245ab19037", GitTreeState:"clean", BuildDate:"2020-07-16T00:04:31Z", GoVersion:"go1.14.4", Compiler:"gc", Platform:"darwin/amd64"}

Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-13T06:39:58Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: Azure Kubernetes Service

OS (e.g. from /etc/os-release): Debian GNU/Linux 10 (buster)

Kernel (e.g. uname -a): Linux airflow-web-65cb7d9cb8-qzcbv 4.15.0-1089-azure #99~16.04.1-Ubuntu SMP Fri Jun 5 15:30:32 UTC 2020 x86_64 GNU/Linux

Install tools: Helm chart "stable/airflow"

Others:

What happened:

After upgrading from 1.10.10 to 1.10.11 (and also with new installs of 1.10.11) there are some permission warnings in the webserver logs:

[2020-08-14 22:19:30,022] {manager.py:545} WARNING - Refused to delete permission view, assoc with role exists XComModelView.can_add Admin
[2020-08-14 22:19:30,038] {manager.py:545} WARNING - Refused to delete permission view, assoc with role exists XComModelView.can_edit Admin

It seems to be directly related to #9614 that @kaxil introduced for 1.10.11 which removes the can_add and can_edit permissions from XComModelView, but Airflow can not delete the permissions from that view because relations to those permissions still exist on the "Admin" and "Op" roles.

In more technical terms, the two permissions can't be deleted from ab_permission_view table because each have relations to both the Admin's and Op's role_ids in the ab_permission_view_role table.

What you expected to happen:

No warnings with Airflow 1.10.11

How to reproduce it:

Install 1.10.11

Either:

View the logs of the webserver

Run any airflow CLI command, such as airflow list_users and view the outputted log messages

After a few lines of the log you will see the warnings

Anything else we need to know:

If those 4 role permissions are removed from the ab_permission_view_role table the warnings should stop. I think a migration needs to be added, or some logic that cleans up these role permissions is failing to do its job.
Issue 1:
There are at least three sets of URLs that give the same thing:

http://doc.rust-lang.org/std/

http://doc.rust-lang.org/nightly/std/

http://static.rust-lang.org/doc/master/std/

One of the should be picked and the others redirect to it.

Related, but I believe not quite duplicate: #9461, #12466, #14466, #18558.

CC @brson

Issue 2:
The Ref type connected to RefCell supports some methods for changing the type of the reference, such as map and filter_map. While map is clearly fully general, filter_map is somewhat of a special case hooked into Option. To make it fully general would likely require HKT. We need an overall plan before stabilization.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I am trying to build a create-react-app for production using `npm run build``

Current Behavior

Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

./node_modules/material-ui/es/styles/withStyles.js:37

Read more here: http://bit.ly/2tRViJ9

This build process includes a minification step (can't be configured, for all I know), which fails (see above), as the 1.0.0-beta.20 version of your wonderful package is in ES6.

This error pattern is known in create-react-app, see the link in their docu: http://bit.ly/2tRViJ9

Steps to Reproduce (for bugs)

Can't provide a sandbox, as you need to use create-react-app and build for prod.

Create a create-react-app

Add material-ui dependency (1.0.0-beta.20)

Run npm run build

Context

Trying to build for prod.

Your Environment

node 8.1.1

npm 5.5.1

Tech
Version

Material-UI
1.0.0-beta.20

React
16.0.0

browser
--

etc
--

Issue 2:
When using the autocomplete component using a list of people [name, city, state ...] as data-source, Austin will be displayed twice.

How can we ensure the list won't show duplicate data while still using the same data source?

const data = [

{"id":1,"name":"bob", "city":"Austin","state":"TX"},

{"id":2,"name":"bobb", "city":"Austin","state":"TX"},

{"id":3,"name":"bobby", "city":"Dallas","state":"TX"},

]

const cityConfig = {

text: 'city',

value: 'city',

};

<AutoComplete

floatingLabelText={'label'}

dataSource={data}

dataSourceConfig={cityConfig}

/>
Issue 1:
Proof of concept: https://github.com/Bladrak/symfony-standard (master branch)

Go to {host}/demo/test

Enter anything in the form

Submit

The error message appears twice.

Expected result: the message should appear only once.

Model: The validation is set on the interface (TestModelInterface) ; the interface is implemented by a class (TestModel) which is overridden by our target entity for the validation (OverriddenTestModel).

Possible bug sources:

Symfony\Component\Validator\Mapping\ClassMetadata::mergeConstraints method systematically performs addConstraint on class-levels constraints where it may have to check if that constraint is already present.

Symfony\Component\Validator\Constraint\ElementMetadata::addConstraint method could perform the check as well.

Issue 2:
Use case

Models:

abstract class AbstractUser
{
private $username;
private $password;
}

class ConcreteUser extends AbstractUser
{
/**
* @var UserProfile
*/
private $profile;
}

class UserProfile
{
private $name;
}

validation.xml (1)

<class name="AbstractUser">
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
<property name="password">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

validation.xml (2) :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
</class>

<class name="UserProfile">
<property name="name">
<constraint name="NotBlank">
<option name="groups">
<value>Profile</value>
<value>Registration</value>
</option>
</constraint>
</property>
</class>

When setting validation_groups to Registration, the error messages show twice for the UserProfile::name property.

A simple test can be adding the username validation again into ConcreteUser class constraints :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

Then validation error messages will show twice on the username as well.

In production environnement that's inconvenient :/

Hack, ugly but....

For now, there is a hack until this is fixed, in form theme blocks (twig) :

{% block field_errors %}
{% spaceless %}
{% if errors|length > 0 %}
<ul>
{% set lastError = null %}
{% for error in errors %}
{% if lastError != error %}
<li>{{ error.messageTemplate|trans(error.messageParameters, 'validators') }}</li>
{% endif %}
{% set lastError = error %}
{% endfor %}
</ul>
{% endif %}
{% endspaceless %}
{% endblock field_errors %}
Issue 1:
This causes overhead on client side when parsing the errors since need to recheck content type for every error in order not to parse plain text as json (some libraries fail on that).

The errors message format should be standardized.

Examples:

404: Page Not Found

Content-Type: text/plain; charset=utf-8

405 Method Not Allowed

Content-Type: text/plain

409 Conflict

Content-Type: application/json

500 Internal Server Error

Content-Type: application/json

Issue 2:
If go-restful detects a particular method is not allowed, it will return this error:

HTTP/1.1 405 Method Not Allowed
Content-Type: text/plain; charset=utf-8

405: Method Not Allowed

That is preventing useful methods that resthandler would generate from making it to the client. Expected response:

HTTP/1.1 405 Method Not Allowed
Content-Type: application/json

{
"kind": "Status",
"creationTimestamp": null,
"apiVersion": "v1beta3",
"status": "Failure",
"message": "update is not supported on resources of kind event",
"reason": "InternalError",
"details": {
"kind": "event"
},
"code": 405
}
Issue 1:
Bug report

Bug summary

When boxplot is called multiple times on the same axis with manage_ticks=True, ticks and labels can get duplicated and be overdrawn.

I believe this problem to be caused in https://github.com/matplotlib/matplotlib/blob/master/lib/matplotlib/axes/_axes.py#L4062-L4072 because there, on the second boxplot call, the new locs of the FixedLocator and seq of FixedFormatter are just appended to the previous ones without removing duplicates.

Code for reproduction

import matplotlib.pyplot as plt

fig, ax = plt.subplots(1, 1)
_ = ax.scatter(['a'], [1])
_ = ax.scatter(['a'], [1])
fig.canvas.draw()

print(ax.xaxis.get_ticklabels())
# Returns [Text(0, 0, 'a')] which is ok

fig, ax = plt.subplots(1, 1)
_ = ax.boxplot([1,2,3])
_ = ax.boxplot([5,6,7])
fig.canvas.draw()

print(ax.xaxis.get_ticklabels())
# Returns [Text(1, 0, '1'), Text(1, 0, '1')] which causes overdrawn labels

The boxplot above is quite unreasonable, however this problem rises also in saner plots, such as the case of two shared axes with one boxplot each.

import matplotlib.pyplot as plt

fig, ax = plt.subplots(2, 1, sharex=True)
_ = ax[0].boxplot([1,2,3])
_ = ax[1].boxplot([1,2,3])

fig.canvas.draw()

print(ax[1].xaxis.get_ticklabels())
# Returns [Text(1, 0, '1'), Text(1, 0, '1')]

Expected outcome

I think that, in the instance of the shared axes, a user should not be required to set manage_ticks=False and set the locators and formatters by themselves in order to get the correct result.

But that is debatable, so I actually wonder if this is a bug or intended behaviour.

Matplotlib version

Operating system: Windows 10

Matplotlib version: 3.3.2

Matplotlib backend (print(matplotlib.get_backend())): TkAgg

Python version: 3.7.5

Jupyter version (if applicable):

Other libraries:

Issue 2:
It would be nice to migrate to py.test which seems to have more features and better usability than nose at this point.

This is potentially a large chunk of work given how customized our nose environment is.
Issue 1:
In my experience, there are few places in data work where problems with data are more evident than when merging datasets -- something that is both a problem (if you think you're doing a one-to-one merge and one of the keys isn't unique in one dataset, you can introduce huge problems) and an opportunity (checking that a merge works as expected is a great way to catch problems).

With that in mind, I'd like to propose adding a check_merge argument that accepts strings one_to_one, one_to_many, may_to_one, and many_to_many. If one of those strings is passed, the merge function would then check uniqueness of merge variables before running the merge, and if for example the merge key for the first dataset has duplicates in a one_to_many merge, it would throw an (informative) exception.

(Stata made a similar move to bake this functionality into its merge command around Stata 12 using 1:1, 1:m, m:1 syntax, which I'm also open to).

Though this functionality can be replicated with user tests, it gets tiring to write them every time...

Issue 2:
Dropping the index column with index=False normally works OK, but if the column headings are from a MultiIndex, it fails to drop the empty <th></th> spacers at the start of the header, so data rows are not aligned properly:

df = pd.DataFrame([[1,1],[1,2],[2,3]],
columns=pd.MultiIndex.from_tuples([('a','b'),('a', 'c')]))
df.to_html(index=False)
Issue 1:
Hi,

I wish to use Gapi for authentication in a future nextjs app. Any idea if this is possible ? or have been done already ?

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

Thanks

Issue 2:
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 1:
Challenge Name

Issue Description

Browser Information

Browser Name, Version:

Operating System:

Mobile, Desktop, or Tablet:

Your Code

Screenshot

Issue 2:
Challenge Name

https://www.freecodecamp.com/challenges/target-the-children-of-an-element-using-jquery

Issue Description

The button 4 should've deleted from the jQuery, and button 5 should have only one clone. But it seems that there're 3 "target 5" buttons the right-hand display.

Browser Information

Browser Name, Version: Chrome 55.0.2883.87 m

Operating System: Windows 7

Mobile, Desktop, or Tablet: msi laptop

Your Code

//Default - No change at all.

Screenshot
Issue 1:
Environment info

transformers version: 4.1.1

Platform: ubuntu 18.04

Python version: 3.8.5

PyTorch version (GPU?): 1.7.1

Who can help

@patrickvonplaten

To reproduce

Steps to reproduce the behavior:

from transformers import AutoModelForSeq2SeqLM
from transformers import AutoTokenizer

mt5s = ['google/mt5-base', 'google/mt5-small', 'google/mt5-large', 'google/mt5-xl', 'google/mt5-xxl']

for mt5 in mt5s:
model = AutoModelForSeq2SeqLM.from_pretrained(mt5)
tokenizer = AutoTokenizer.from_pretrained(mt5)

print()
print(mt5)
print(f"tokenizer vocab: {tokenizer.vocab_size}, model vocab: {model.config.vocab_size}")

This is problematic in case when one addes some (special) tokens to tokenizer and resizes the token embedding of the model with model.resize_token_embedding(len(tokenizer))

Expected behavior

vocab_size for model and tokenizer should be the same?

Issue 2:
❓ Questions & Help

Pretrained T5Tokenizer has vocab size of 32100 (32000 tokens plus 100 extra_ids) but the shared embedding layer of T5ForConditionalGeneration has size of (32128, 768). I checked the google-research implementation of T5 and also found that they have vocab size of 32100 also.

Where did the extra 28 embeddings come from and how can we map it to the tokenizer?

To reproduce

from transformers import (
T5Tokenizer,
T5ForConditionalGeneration,
)

tokenizer_pretrained = T5Tokenizer.from_pretrained('t5-base')
model_pretrained = T5ForConditionalGeneration.from_pretrained('t5-base')
len(tokenizer_pretrained.get_vocab()), model_pretrained.state_dict()['shared.weight'].shape

Output:

(32100, torch.Size([32128, 768]))
Issue 1:
TypeScript Version:

1.8.7 (ES6 mode)

Code

type SymbolKeysGiveNumbers = { [x: symbol]: number };

Expected behavior:

Should work

Actual behavior:

Error: an index signature parameter must be 'string' or 'number'

However:

Code

let x: { [key: string]: any };
x[Symbol("abcd")] = 12;

Expected behavior:

Should not work based on the error above

Actual behavior:

Works

Conclusion

Symbol type should be allowed as an index signature parameter type as in practice it is accepted as a valid index key type. Even the error message when doing something like:

let x: { [key: string]: any };
x[true] = 1;

includes 'symbol' as a valid option:

An index expression argument must be of type 'string', 'number', 'symbol' or 'any'

Issue 2:
TypeScript now has a ES6 target mode which includes definitions Symbol. However when trying to index an object with a symbol, I get an error (An index expression argument must be of type 'string', 'number', or 'any').

var theAnswer = Symbol('secret');
var obj = {};
obj[theAnswer] = 42; // Currently error, but should be allowed
Issue 1:
The issue is that putting class="visible-md visible-lg" on an element will only make the element visible in the largest of the specified views (in this case visible-lg).

The reason is that the CSS specificity that made this work in v3.0.3 was removed in v3.1.0 without correcting the order of CSS to make up for the decrease in specificity. Now the display: none !important of visible-lg overrides the display: block !important of visible-md because it is later in the CSS file (since the media query doesn't give any greater specificity). This most likely can be corrected by putting all the display: block !important wrapped in media queries after the display: none !important.

So change:

.visible-md,
tr.visible-md,
th.visible-md,
td.visible-md {
display: none !important;
}
@media (min-width: 992px) and (max-width: 1199px) {
.visible-md {
display: block !important;
}
table.visible-md {
display: table;
}
tr.visible-md {
display: table-row !important;
}
th.visible-md,
td.visible-md {
display: table-cell !important;
}
}
.visible-lg,
tr.visible-lg,
th.visible-lg,
td.visible-lg {
display: none !important;
}

to

.visible-md,
tr.visible-md,
th.visible-md,
td.visible-md,
.visible-lg,
tr.visible-lg,
th.visible-lg,
td.visible-lg {
display: none !important;
}
@media (min-width: 992px) and (max-width: 1199px) {
.visible-md {
display: block !important;
}
table.visible-md {
display: table;
}
tr.visible-md {
display: table-row !important;
}
th.visible-md,
td.visible-md {
display: table-cell !important;
}
}

See wet-boew/wet-boew#4448 (comment) for additional details.

Issue 2:
https://dl.dropboxusercontent.com/u/37682778/error/index.html
Issue 1:
There is a lot of information in the stats API, but little of it is documented, and confusion arises...

e.g.

_all.primaries.docs.count shows all the documents lucene sees, which may be different to the documents elasticsearch sees with a simple search if there are nested documents being used. (I think this statement is true... but is it?)

Issue 2:
Hello,

We have actually 7 nodes. We use elasticsearch 1.3.2.

We are configured in unicast mode with a minimum consistency of 4

Two days ago, in the night, network team has done a switches firmware upgrade of all production switches.

The result of this upgrade has been catastrophic for the cluster.

The cluster has been split in two parts with some node in first and second part

Node 3 and Node 5 was master together

Node 3 with Node 1, Node3 and Node 6

Node 5 with Node 1, Node2, Node4, Node 5, Node 6 and Node 7

Fortunately we have a second cluster on other lab which the same data and we have been able to do a snapshot/restore from this cluster to the first one after a rolling restart.

And don't understand how a switch upgrade, and a connectivity lost, can result of a corrupted cluster allocation.

Regards,
Issue 1:
apm (atom package manager) conflicts with the widely used advanced power management system on Linux. This has been confirmed on both current versions of Ubuntu and Debian.

Atom installs "apm" by default into /usr/bin, Advanced Power Management installs its client, also named "apm" into /usr/bin as well.

Since this is a widely used system, I would suggest that either the Atom package manager be renamed, or installed into another location so that they do not conflict.

Issue 2:
Error when installing on a system with "apmd" package installed:

Selecting previously unselected package atom.
(Reading database ... 183328 files and directories currently installed.)
Preparing to unpack atom-amd64.deb ...
Unpacking atom (0.138.0) ...
dpkg: error processing archive atom-amd64.deb (--install):
trying to overwrite '/usr/bin/apm', which is also in package apmd 3.2.2-15
Processing triggers for mime-support (3.57) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Errors were encountered while processing:
atom-amd64.deb