WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
This is not a bug request, but rather, it's a discussion on the reasons why you named 2 prop types of TextField almost the same with one being upper case.

According to TextField API,

TextField exposes two prop types with almost same names. InputProps and inputProps.

Currently, my Eslint gives me an error for having duplicate prop type.

Is there any reason to name 2 prop types almost the same?

Can't we rename 1 of them to something more clarifying?

This also gives headaches with linting tools.

Expected Behavior

Eslint or any other linting tool doesn't give me any duplicate error.(react/jsx-no-duplicate-props).

Current Behavior

Eslint throwing duplicate prop error.

Plugin is located here.

##Temporal solution

Yes, you can set ignoreCase to false in .eslintrc but isn't it better to name our props in a more definitive way?

Thank you.

Your Environment

Tech
Version

Material-UI
1.0.0-beta30

React
^16.0.0

eslint
^4.8.0

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

I was thinking I could contribute a "solo field" to Material UI, if you're interested, and given you don't already have a solution for it already. The idea is to have a input field that can be used as the main search form in webapps. I have created a custom one that I use together with material-ui, and figured it would be cool to make a contribution to the project.

First of all, does it make sense to have this as a component or is the idea that it is easy enough to change the existing TextField / AutoComplete components with the new classes API and withStyles HOC?

Second, I was thinking of making it a separate component, but perhaps it's better to include it in the existing TextField component? Thoughts? Actually, when I think about it, it definitely needs to support auto-complete, so on a second thought it should probably rely on AutoComplete (which I assume in turn is based on TextField).

It should support an icon (and potentially a drop down menu) and auto-complete.

Examples:

Search for "solo fields" in the Text fields spec

Search for "Floating toolbar" in the Layout/structure guideline

Google Maps - floating toolbar with solo field

Google Drive - the search field in the toolbar

Screenshot examples:

Floating toolbar with solo field:

Regular toolbar/app bar with solo field:
Issue 1:
Environment

Windows build number: 10.0.18990.0
Windows Terminal version (if applicable): After 1909 release, built from master, latest commit: https://github.com/microsoft/terminal/commit/df26c677efcb815a3b66a974345c9d3483cab678

Any other software?

Steps to reproduce

Resize the Terminal from the bottom or double click to make it full screen. Any vertical resizing will do it.

Expected behavior

Everything draws properly and the background color fills the window.

Actual behavior

The background doesn't fill and black rectangles fill it instead. Improper redrawing.

Issue 2:
You can't input Chinese using the Chinese input method that comes with WIndows 10.
Issue 1:
The problem is that you can shoot yourself in the foot with the numpy version of all, because it is not consistent with the Python build-in all in return value when generator is passed to it:

In [1]: import numpy

In [2]: numpy.all(a for a in [False])
Out[2]: <generator object <genexpr> at 0x7f22623eeaa0>

In [3]: bool(numpy.all(a for a in [False]))
Out[3]: True

In [4]: __builtin__.all(a for a in [False])
Out[4]: False

This is especially confusing when used with ipython -pylab in which case the buildin.all is shadowed with the numpy one:

$ ipython -pylab
... blah blah...
In [2]: all.func_code
Out[2]: <code object all at 0x7ff967d8c5b0, file "/usr/lib64/python2.7/site-packages
numpy/core/fromnumeric.py", line 1842>

Issue 2:
Numpy's any() (and all()) functions should work with generator expressions to be consistent with basic python. I spent several hours trying to debug a case of this, which would work if I used a list, but not if I used a generator expression -- only to discover that it was because numpy's all() function was being used instead of the usual python one that works identically with both generators and lists.

lst = [0,1,2]

print any(i < 0 for i in lst) # False
from numpy import any
print any([i < 0 for i in lst]) # False
print any(i < 0 for i in lst) # <generator object <genexpr> at 0x1006bd500>
Issue 1:
VSCode Version: 0.10.11

OS Version: Windows 8.1

Steps to Reproduce:

Install a big extension that is likely to take some time

Navigate away from VS Code and come back

No progress bar/indication if the extension is installing

#3341 deals with something similar to this but only a message was added as part of 83f1fe7

Issue 2:
When downloading a larger extension you get no progress/status indication.
Issue 1:
I've noticed an easy area to make a mistake in the language because of this SO question. Take this example:

class MyClass {
@SetDefaultValue
filePath: string;
}

var c = new MyClass();
console.log(c.filePath);

function SetDefaultValue(defaultValue = "Example") {
return function (target: Object, propertyKey: string | symbol) {
target[propertyKey] = defaultValue;
};
}

This compiles fine; however, this will output undefined. To fix this, the developer needs to remember to add parentheses:

class MyClass {
@SetDefaultValue()
filePath: string;
}

Now it will output Example.

This seems too sneaky to me. I can see this leading to incredibly annoying bugs in applications. Is there any way the compiler could get both ways to work or throw a compile error for one of them?

Issue 2:
As mentioned in #2249 (comment), consider this:

// decorator factory
function F(options?: {optional: boolean}) {
// returns a property decorator
return (target , propertyKey): void => {
// decorator implementation
}
}

class C {
@F() // OK, used as a factory
prop1;

@F // No error
prop2;
}

The problem here is that the compiler compares the signature of the decorator factory F against declare type PropertyDecorator = (target: Object, propertyKey: string | symbol) => void; which ends up to be assignable. I think we need a stronger check here to make sure we catch these issue.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When I click on a Select component, I don't expect my webpage scrollbar to disapear.

Current Behavior

Scrollbar disapear when a select is active.

Context

This is very annoying as in some situations it changes the layout of the page.

Issue 2:
1.0 TextField ref return null

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

Expected Behavior

Current Behavior

1.0 TextField ref return null

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI

React

browser

etc
Issue 1:
When in strict mode (what's advised to use).

E.g. ceil() and floor() calls in variables fail because the expressions inside them should be wrapped in extra parenthesis.

Also ceil() calls in type.

Issue 2:
LESS 1.4 is currently beta but it wouldn't harm to prepare for its breaking changes.

I only found problematic mathematical expressions that won't compile (correctly) with 1.4.0b (using the latest BS source):

panels ln 20 should be enclosed in parentheses

.make-column() will produce a width with NaN% for @media (min-width: 768px)
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Context

We export a Next.js site using next export and deploy it to Netlify. We noticed that after deploying a new version of the site, all users who have the previous version open in the browser cannot follow links anymore.

Expected Behavior

The router's onAppUpdated event is triggered and causes a reload of the page by default, as documented in the README.

Current Behavior

onRouteChangeStart is triggered, but onAppUpdated (or even onRouteChangeError) is never called. Instead, nothing user-visible happens. The browser developer tools reveal a failed <script> request (because the build ID - and thus the JS chunk's path - changed) which is apparently not being acted upon.

Steps to Reproduce (for bugs)

Create a Next.js page with at least one (non-prefetch) link and create a listener for onAppUpdated.

Build it with next export, serve it (e.g. npx server _build) and visit it.

With the page open, rebuild the page (another next export).

Try clicking on the link you created. Nothing happens, and the onAppUpdated listener is not called.

Your Environment

Tech
Version

next
4.2.1

node
9.3.0

OS
macOS 10.13.1

browser
Any

Issue 2:
I’m trying to render a nextjs page blob (from a HTTP POST) into an iframe src.

I do a HTTP POST to an url in my next server. Then convert that html document into a blob using const urlBlob = URL.createObjectURL(blob) and passing that into an iframe <iframe src={urlBlob}/>

I had to use assetPrefix in next.config.js to point to the host, in this case http://localhost:3000

In npm run dev the hmr is unavailable.

After running npm build and npm start it renders the page on an iframe and the JS loads.

The problem is that the router is breaking my JS.

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

Expected Behavior

Javascript should be functional. I expect the router to be disabled.

Current Behavior

Javascript crashes with the following error:

app.js:15 Failed to execute 'replaceState' on 'History': A history state object with URL 'tp://localhost:3000/2ada9931-0621-4f74-81ed-dc8255a340e6' cannot be created in a document with origin 'http://localhost:3000' and URL 'blob:http://localhost:3000/2ada9931-0621-4f74-81ed-dc8255a340e6'.

Steps to Reproduce (for bugs)

HTTP Post to a NextJS page

Render the html blob into an iframe using Url.createObjectURL

Open browser's console and see the router errors.

Context

I am unable to use JS on iframes which are populated by blobs.

Your Environment

Tech
Version

next
4.1.0

node
8.8.1

OS
OSX High Sierra

browser
Chrome 62

etc
...
Issue 1:
e.g. http://jenkins.kubernetes.io/job/kubernetes-e2e-gce/4289/

Issue 2:
Node e2e test should be run as part of the e2e conformance test suite.

figure out if the node e2e test should be run against every node in the cluster or just 1 node

support running tests using hooks provided by the cluster e2e framework for talking to the nodes

hook into existing test scripts

build node e2e with cluster e2e
Issue 1:
Version

2.6.11

Reproduction link

data:,see-steps-below

Steps to reproduce

Step 1:

<template>
<div>
<textarea v-on:keypress.ctrl.enter="handleSubmit"></textarea>
</div>
</template>

<script type="module">
import Vue from 'https://cdnjs.cloudflare.com/ajax/libs/vue/2.6.11/vue.esm.browser.min.js';
let App={
methods: {
handleSubmit(event){
console.log('Ctrl Enter pressed');
},
}
};
new Vue(App).$mount(document.querySelector('template'));
</script>

Step 1:

focus on the textarea and press Ctrl Enter

What is expected?

the event handler handleSubmit would be invoked

What is actually happening?

It doesn't work across browsers.

event \ working \ browser
Chrome 90
Firefox 78

v-on:keypress.ctrl.enter
N
Y

v-on:keypress.ctrl.10
Y
N

v-on:keypress.ctrl.13
N
Y

v-on:keypress.ctrl.10.13
Y
Y

// v-on:keypress.ctrl.enter="handleInputEnter"
on: {
"keypress": function($event) {
if (!$event.type.indexOf('key') && _k($event.keyCode, "enter", 13, $event.key, "Enter"))
return null;
if (!$event.ctrlKey)
return null;
return handleInputEnter($event)
}
}

Use .enter as an alias of .13 is sometimes misleading. If event keyCode is 13, then you may say Enter key is pressed, but if Enter pressed, the keyCode may also be 10 if Ctrl pressed in the mean time.

Currently I use v-on:keypress.ctrl.10.13="handleInputEnter" as a workaround.

So my idea is: either to add a caveat note in docuemtation section .enter, or let the component template compiler handle .enter modifier correctly.

Issue 2:
Version

2.6.11

Reproduction link

https://codesandbox.io/s/kind-water-hqs5f?file=/src/App.vue

Steps to reproduce

在任意输入框输入任意内容

What is expected?

输入流畅

What is actually happening?

输入卡顿

在v-for里面，绑定了$attrs的都会触发更新，引起不必要的渲染
Issue 1:
When creating a form type class with a default validation_group (using validation_groups key in default options array), I found that the specified group is not taken into account when generating the form for the NotBlank assert annotation (and most liekly the NotNull one as well).

When adding a NotBlank assert annotations to a model (or entity) class with a group application filter (groups attribute for the annotation) and generating a form view for this class (via a form type specifying the default validation group or another validation group), the Not Blank annotation is always processed before rendering the form and the field always ends up with a require="required" attribute.

The validation_groups options of the form type class should always be taken into account when generating a form. Right now it is not correctly processed and the generated form does not match the expected result ; the only way I found to fix this behaviour without going into the symfony core classes was to render each field using an attribute "required" => false when rendering the field using the form_(row|widget) twig tag.

Issue 2:
The ValidatorTypeGuesser does not consider the current form's validation_groups option when guessing type. This could be fixed by passing the options array to the guesser methods. The signature of the FormTypeGuesserInterface methods would look like this:

function guessType($class, $property, array $options = array());

The default argument is provided for BC.
Issue 1:
There was an original attempt to support exporting chart to image manually, which is a nice idea, but the implementation does not cover every chart and was inactive for long time, so I close the PR and created an issue to track the idea.

#3496

Issue 2:
It's known that the Redis cache is already applied in query for query_context and viz, but there is a situation that makes it doesn’t work well, that’s when multi concurrent query requests to one dashboard or chart, come in at the same time, from different users. It will cause duplicated query request to our query engine, because the cache is not ready yet. As a result, it brings burden to cluster and waste resources.

Since the superset is natively distributed, and the async task is supposed to run in multiple celery works, we come up with an assumption that, maybe the distributed lock can help, which should be acquired before cache retrieve and released after query complete, to make the queries with the same cache key execute in a serial way, instead of a concurrent way.

Checklist

Make sure to follow these steps before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are any.

I have reproduced the issue with at least the latest released version of superset.

I have checked the issue tracker for the same issue and I haven't found one similar.
Issue 1:
Is your feature request related to a problem? Please describe.

In version 2.x Quick Fix imports have suffixed the imports with the correct file extension now in 3.x I always have to add .ts etc manually which is painful.

Describe the solution you'd like

Add the feature back which automatically handled the file extensions.

Issue 2:
This plugin is mostly doing pretty incredible, I've been having a small issue with imports the past few weeks.

Given two files:

dep.ts

export const age = 28;

and main.ts

console.log(age);

The LSP gives a helpful action to import when triggered on the age word:

However, this is missing the .ts extension as should be added with Deno, which results in an error when importing.

Versions

vscode: 1.57 deno: 1.10.2 extension: v3.4.0

The screenshots are from nvim / coc.nvim but I confirmed the issue with vscode.
Issue 1:
macro_rules! foo {
() => { foo!() }
}

foo!()

just eats memory continuously (until it either segfaults from stack-overflow or otherwise crashes from OOM, presumably).

Issue 2:
Defining macros recursively like so

macro_rules! recursive(
() => (
recursive!()
)
)

fn main() {
recursive!()
}

will lead rustc to cause a stack overflow.

It would be useful to improve the error message for that problem.

There is currently no error message specified for that issue.
Issue 1:
For different dB, adding the same table name will result in an error. The source is two different dB, the index of tables table unique (table_ Name) should be changed to unique (database_id,table_name)I hope this problem can be corrected in the next version. Thank you

Issue 2:
A clear and concise description of what the bug is.

Expected results

save two tables with the same names but which have different schemes.

Actual results

when trying to call as different schema tables, we have an error.

"Integrity error, probably unique constraint"

what actually happens.

Screenshots

If applicable, add screenshots to help explain your problem.

How to reproduce the bug

Go to 'Sources > Tables'

Click on '+New, Database-> Schema->Table Name '

Scroll down to '....'

See error

Environment

(please complete the following information):

superset version: 0.36.0

python version: Python 3.6.9

node.js version: v8.10.0

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if there are any.

I have reproduced the issue with at least the latest released version of superset.

I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.
Issue 1:
As a developer, I want to be able to write a service worker and use it both in clients (user agents / web browsers) and in servers.

If deno adds support for installing service workers with support for install, activate, fetch and other ServiceWorkerGlobalScope events then isomorphic service workers become a possibility.

Issue 2:
To build a production ready cloudflare worker/ faas alternative with deno it would be very hard to use the current deno web worker implementation. (basically starting one webworker per handler and then dispatching messages from the main script)

i see some pain points implementing the registration / update workflows that browsers have in the main script, but i think finding a good solution there would REALLY pay of well:

custom caching strategies for fetch events

resourceful lifetime management of external 'processes' like browsers do with service workers, without having to manually start and stop the web workers

handling, rewriting, transforming, monitoring the requests that imported files make (huge number of possibilities here)

would love to help, but i dont know rust (yet) and not even at what point in the architecture this would need to be implemented
Issue 1:
>>> special.chndtr(np.inf, 16, 30)

(five minutes later) ^C^C^C no reaction

ok, kill -9

this does not seem to depend on other parameters, same story with >>> special.chndtr(np.inf, 16, 30)

This is used for non-central chi-square:

>>> stats.ncx2.cdf(np.inf, 8, 0.1)
1.0
>>> stats.ncx2._cdf(np.inf, 8, 0.1)

(hangs)

and skellam, which only defines _cdf, so sf goes via the generic code path:

>>> stats.skellam.cdf(np.inf, 10, 11)
1.0
>>> stats.skellam.sf(np.inf, 10, 11)

(hangs)

Issue 2:
>python -c "import numpy as np; from scipy import stats; stats.nct._sf(np.nan, 125.531223551, 2.82324307702)"

never comes back

I was tracking an rootfinding that never came back that had bad starting values.

scipy 0.9.0 and scipy 0.11.0
Issue 1:
Electron Version:

4.0.2

Operating System:

mac 10.14

Expected Behavior

sample code doesn't work. the dev tool shows, but it's empty.

<html>
<head>
<style type="text/css">
* { margin: 0; }
#browser { height: 70%; }
#devtools { height: 30%; }
</style>
</head>
<body>
<webview id="browser" src="https://github.com"></webview>
<webview id="devtools"></webview>
<script>
const browserView = document.getElementById('browser')
const devtoolsView = document.getElementById('devtools')
browserView.addEventListener('dom-ready', () => {
const browser = browserView.getWebContents()
browser.setDevToolsWebContents(devtoolsView.getWebContents())
browser.openDevTools()
})
</script>
</body>
</html>

Screenshots

the dev tools show nothing.

after remove this line browser.setDevToolsWebContents(devtoolsView.getWebContents()), the devtool can show correctly.

Issue 2:
It seems that Chromium disallows using guest view as devtools, I need to find out the code in Chromium to fix it.

not ok 55 <webview> tag setDevToolsWebContents() API sets webContents of webview as devtools
AssertionError: expected '' to equal 'InspectorFrontendHostImpl'
at Context.it (/Users/zcbenz/codes/electron/spec/webview-spec.js:721:26)
Issue 1:
I'm trying to test that a user with the wrong permissions sees the correct response when visting a page that has a csrf token in the path.

I've added a Behat context step to create a csrf token using the 'security.csrf.token_manager', however then visit the page with this token in the path, I get a "Cannot set session ID after the session has started" 500 error.

Can anyone advise what I'm doing wrong, or how I work around this, please?

/**
* @When /^I go to the application admin archive page for "(?P<status>[^"]*)" application (?P<number>\d+) with a valid token$/
*
* @param string $status
* @param int $number
*/
public function iGoToTheApplicationAdminArchivePageForApplicationWithAValidToken($status, $number)
{
$tokenManager = $this->kernel->getContainer()->get('security.csrf.token_manager');
$token = $tokenManager->getToken(ApplicationAdminController::CSRF_ARCHIVE);
var_dump($token);

$this->visitAdminPage('archive', $status, $number, ['token' => $token]);
}

Issue 2:
Hi guys!

Currently, in service definition, we can set parent of service. Setting parent means that arguments, method calls, property sets and some other things copied from parent definition and (possibly) replaced by concrete definition. How about new feature, that allows to set multiple parents? It is more like mixin, or trait for service. It would be something like this:

service:
class: stdClass
arguments: [@kernel]
mixins:
- mixin_service_1
- mixin_service_2

What do you think about this?
Issue 1:
I find it difficult to read hovers: the font is the same as the underlying text and the hover text does not stand out from the underlying text. And the fixed width font makes hovers wider than necessary.

Look here: where is the hover?

Issue 2:
Testing #2230

The rendering of the documentation in the hover and in Intellisense is inconsistent, different font, font size, font family, and color.

Suggest to align on the way the documentation is rendered in Intellisense. It looks nicer.

FYI @bgashler1

Delayed hover

Diagnostics hover

Glyph hover

Debug breakpoint expressions colorisation

URL click hover

Suggest widget

Parameter hints widget