WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The native browser select element allows you to move to options by typing arbitrary characters when the select menu is open. The newly added Select component (which is greatly appreciated by the way!) does not support this functionality.

Current Behavior

When select menu is open, and I type the label of an option that is not selected, nothing happens.

Steps to Reproduce (for bugs)

Open a Select component

Start typing to select an option

Context

Material UI is an amazing asset, but in pursuit of the new and shiny, let's not abandon something as fundamental as basic select functionality :)

Your Environment

Tech
Version

Material-UI
1.0.0-beta-9

React
15.5.4

browser
Chrome 61.0.3163.79 (Official Build) (64-bit)

Issue 2:
Problem description

Duplicate react with webpack post npm install update of material-ui, using webpack example.

Steps to reproduce

Install webpack example so it installs older 15.0 version, and 15.0.1 of react.

After it working, npm install update to the latest MUI/REACT.

invariant.js:38 Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.

I noticed the dir "node_modules/material-ui/node_modules/react" did not exist in the older

setup, but once npm updates, theres a duplicate of react on "node_modules/material-ui/node_modules/react" and "node_modules/react"

rm -rf "node_modules/material-ui/node_modules/react" fixes the problem.

But how to avoid it re-occurring?

Versions

Material-UI: 0.15.0 / 0.15.1

React: 15.0.1 / 15.3.1

Browser: Chrome
Issue 1:
I'm submitting a feature request

Current behavior

Now We can only pass strings to directive. And sometimes it is quite hard to test becouse you need to escape it and IDEs dont test it on fly.

Minimal reproduction of the problem with instructions

Here plank that shows the problem

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

Better code mantaining

Angular version: 2.0.3

Thank you.

Issue 2:
I'm submitting a ... (check one with "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

Here's how I'm building a form input field

Regular expression pattern:

regexPattern:string is "/^\d{2}/\d{2}/\d{4}$/"

group[question.key] = ['', Validators.compose([Validators.required,Validators.pattern(regexPattern)])];

FormBuilder.group(group)

During Debugging I see:

regexPattern : "/^d{2}/d{2}/d{4}$/"

{ "pattern": { "requiredPattern": "^/^d{2}/d{2}/d{4}$/$", "actualValue": "01/01/2001" } }

Expected/desired behavior

As you can see the requiredPattern adds an extra ^ at the beginning and a $ at the end. Validators.pattern(String) should accept a Regexp not a String. The regexPattern set was "/^\d{2}/\d{2}/\d{4}$/" but as you can see it's value while debugging is obvsiously requiredPattern": "^/^d{2}/d{2}/d{4}$/$"

Validators.patterns(String) should instead accept a regular expression literal Validators.pattern(RegExp). It should have the same input signature as str.match(regexp) in javascript https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/match

Reproduction of the problem

If the current behavior is a bug or you can illustrate your feature request better with an example, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).

What is the expected behavior?

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

Please tell us about your environment:

Angular version: 2.0.0-rc.4

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [TypeScript X.X]
Issue 1:
Hi,

we updated from Symfony 2.6 to 2.8 with the choice options you can find below.

We expected the label of our choice type should be hidden and just the value and the input element exists. In 2.6 this worked for us.

When we upgraded to 2.8 (with the same options) the labels are shown again. The Problem is caused by an empty string in the view, not as expected false.

$resolver->setDefaults([
'choices' => [1 => false, 2 => false, 3 => false, 4 => false, 5 => false],
'expanded' => true,
'placeholder' => false,
'required' => false,
]);

So we added a workaround in our bootstrap_3_layout.html.twig to resolve this.

{%- block radio_label -%}
{% if label == '' or label is null %}
{% set label = false %}
{% endif %}

{{ parent() }}
{%- endblock radio_label -%}

Is there a cleaner way to hide the label or is this a bug/bc break?

Thanks

Issue 2:
After upgrading from 2.7.7 to 2.7.8 I noticed that some choice fields didn't display the empty value.

Example code:

->add('buyback', 'choice', [
'choices' => [
'Yes' => true,
'No' => false,
],
'choices_as_values' => true,
'required' => false,
]);

Before:

After:

So far I've found out that the false value is converted to empty string in this line v2.7.7...v2.7.8#diff-780e59a429c485d2d3b8a37fdf62ac59R79.

I think that the false value is displayed instead of empty value because of that.

This bug was introduced in #16705.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

All valid children of the Table component should be rendered.

Current Behavior

Only the last instance of each valid component is rendered

Steps to Reproduce (for bugs)

Create a table with two TableBody children

Render the table and verify that only the second TableBody is rendered

JSFiddle Example

Context

I am attempting to create draggable table sections.

Your Environment

Tech
Version

Material-UI
^0.19.2

React
^15.6.1

browser
chrome v61

Issue 2:
An asterisk (*) is hard-coded to required fields. I think we should allow users to customise the asterisk or remove it if they want to.

https://github.com/callemall/material-ui/blob/fb3a42f421d9a00cbc31e69e06e5e30c7b1998fc/src/Form/FormLabel.js#L125-L127

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

Expected Behavior

Be able to pass in a requiredText: Node to be displayed instead of the hard-coded asterisk, or false to completely remove it.

Current Behavior

There is no way to override the asterisk at the moment.

Steps to Reproduce (for bugs)

Not a bug

Context

For some forms that all fields are required, I'd like to display a label somewhere (All fields are required) and remove all the asterisks in each TextField.

The form looks cleaner without those.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.9

React
15.4.1

browser
Chrome

etc
Issue 1:
System information (version)

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

The stereo_match.cpp code (https://github.com/opencv/opencv/blob/master/samples/cpp/stereo_match.cpp) has a scaling issue that took me 2 days to track down. The computed disparity is a signed int16, and is scaled by a factor of 16 compared to the true disparity, as per the documentation. The disparity thus must be converted to float and divided by 16.0 before invoking reprojectImageTo3D(). As it is now, since this division is not done, the result of reprojectImageTo3D() is wrong, as is at 1/16-the the scale.

Suggested fix:

Mat float_disp;
disp.convertTo(float_disp, CV_32F, 1.0f/16.0f);
reprojectImageTo3D(float_disp, xyz, Q, true);

Steps to reproduce

Issue 2:
System information (version)

OpenCV => 4.6.0

Operating System / Platform => Windows 64 Bit

Compiler => Visual Studio 2019

Detailed description

When I load onnx model which was quantified by script from opencv_zoo with the Intel neural-compressor>1.10.1, it will cause an error. (This model can be run correctly by onnx_runtime)

[ERROR:0@80.629] global D:\a\opencv-python\opencv-python\opencv\modules\dnn\src\onnx\onnx_importer.cpp (1021) cv::dnn::dnn4_v20220524::ONNXImporter::handleNode DNN/ONNX: ERROR during processing node with 11 inputs and 1 outputs: [QLinearConcat]:(onnx_node!StatefulPartitionedCall/model/regressors/concat_quant) from domain='com.microsoft'
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
cv2.error: OpenCV(4.6.0) D:\a\opencv-python\opencv-python\opencv\modules\dnn\src\onnx\onnx_importer.cpp:1040: error: (-2:Unspecified error) in function 'cv::dnn::dnn4_v20220524::ONNXImporter::handleNode'
> Node [QLinearConcat@com.microsoft]:(onnx_node!StatefulPartitionedCall/model/regressors/concat_quant) parse error: OpenCV(4.6.0) D:\a\opencv-python\opencv-python\opencv\modules\dnn\src\onnx\onnx_importer.cpp:571: error: (-5:Bad argument) Blob StatefulPartitionedCall/model/regressors/concascale not found in const blobs in function 'cv::dnn::dnn4_v20220524::ONNXImporter::getBlob'

When I use Intel neural-compressor==1.10.1, the mdoel can be loaded. Several models have this problem as well.

Steps to reproduce

Demo model file: palm_detection_mediapipe_2022may-int8-quantized.onnx

Python code:

import cv2
net = cv2.dnn.readNetFromONNX("path/to/model")

Issue submission checklist

I report the issue, it's not a question

I checked the problem with documentation, FAQ, open issues,

forum.opencv.org, Stack Overflow, etc and have not found any solution

I updated to the latest OpenCV version and the issue is still there

There is reproducer code and related data files: videos, images, onnx, etc
Issue 1:
I'm submitting a ... (check one with "x")

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

Current behavior

Having several times an element in the DOM tree with the selector associated to a component will only bootstrap the first DOM node found in the tree.

Expected behavior

All nodes matching the correct selector should be bootstrapped not only the first appearance in the tree.

Reproduction of the problem

http://plnkr.co/edit/bLCsmIRG7pkMu6GohOxS?p=preview

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

I need to bootstrap several time the same component on my page.

(For my special case I am bootstrapping 2 time the same ui-element that are at 2 different places in the DOM tree)

Angular version: 2.0.0-rc.6

Browser: Chrome

Language: TypeScript

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

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

Current behavior

Platform server fully renders a lazy module, and the view on the browser is changed several times:

The html rendered on the server is shown.

As the application starts to bootstrap, the page is shown without the lazy loaded component.

As the chunk is downloaded, the lazy loaded component is rendered.

In case of a heavy chunk, or alternatively a slow connection, it looks like the application flickers on the transition between the views.

Expected behavior

The transition between the server rendered page and the client side bootstrapped page should be smooth and invisible to the user.

Minimal reproduction of the problem with instructions

Universal example app was provided as an example in the roadmap. Running the application in chrome and throttling the network should be enough for reproducing the behavior (The lazy loaded components will flicker as described above).

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

It makes the application look bad and unprofessional.

I've used Angular Universal previously, and managed to solve the issue using preboot (rendered the application to a hidden div, and called preboot.complete() manually as the lazy loaded module view was initialized). I've integrated preboot to the current version and tried to use the same approach, but encountered style issues.

Please tell us about your environment:

Angular version: 4.0.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Tried on Chrome 56, Firefox

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript 2.2.2

Node (for AoT issues): node --version =

node v6.9.10 (I'm running LTS)
Issue 1:
Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable): Microsoft Windows NT 10.0.18362.0

Any other software? msbuild

Steps to reproduce

Log into a machine over RDP

Open a terminal cmd session

Start a build using msbuild.exe

Close RDP session

Expected behavior

It's expected that the build will continue in the background even after the RDP session is disconnected.

Actual behavior

Terminal output is blocked, causing the build to be blocked as well. This means that the build will not proceed until reconnecting the RDP session or logging into the host machine.

Issue 2:
The petty thing I miss most when I pop into Windows is having a separate hot key terminal for each of my three monitors. The closest i've ever been to believing in god was when I realized that was obtainable and if you could make that happen in Windows I just might have to kiss you.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I would expect that when I programmatically set the value of the multiline TextField to '', the text inside it would disappear.

Current Behavior

Currently, the previous value inside the multiline TextField is NOT being cleared after setting the value to ''.

Steps to Reproduce

You can directly reproduce the bug here: https://codesandbox.io/s/wwpojv800k

Type something in the multiline TextField.

Press the Reset button

Results:

The content of the multiline TextField is not cleared.

Here is a very simple component you can directly add to your code to reproduce the bug:

import React from 'react';
import TextField from 'material-ui/TextField';
import Button from 'material-ui/Button';

class Test extends React.Component {
constructor() {
super();

this.state = {
content: '',
};
}

handleChange() {
return (event) => {
this.setState({content: event.target.value});
};
}

resetContent() {
this.setState({content: ''});
}

render() {
return (
<div>
<TextField onChange={this.handleChange()} value={this.state.content} rows='5' rowsMax='5' label='Content' multiline fullWidth/>
<Button raised onClick={this.resetContent.bind(this)}>Reset</Button>
</div>
);
}
}

export default Test;

Your Environment

Tech
Version

Material-UI
1.0.0-beta.13

React
15.6.1

browser
Firefox 56.0 (32-bit), Firefox Dev Edition 57.0b5 (64-bit), Chrome 61.0.3163.100 (64 bit)

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

Expected Behavior

I should be able to somehow use a <ListItem> with a Link in TypeScript.

Current Behavior

I've found a few examples that suggest using:

<ListItem button component={Link} to="/somelink"></ListItem>

But I use TypeScript, and using to attr throws a compilation error since to is not a property of ListItem.

Steps to Reproduce (for bugs)

Use create-react-app my-app --scripts-version=react-scripts-ts to create a simple react app with TS

Add react-router as dep and install it

Use a List in the app template and try to add an item with <ListItem button component={Link} to="/somelink"></ListItem>

Context

I'm trying to setup Material UI with react-router.

Your Environment

Tech
Version

Material-UI
next

React
16.1.0

browser
Chrome

etc
Issue 1:
There needs to be a waypoint or a series of waypoints that explain how to properly use GitHub in general, and how to search for and report issues in particular, since people are posting a lot of duplicate issues (see #1062, and it's 7 duplicates, about a bug that was already fixed in staging).

I think I have seen this mentioned already, but my inability to find a relevant issue, if there is one, sort of just strengthens my point.

Issue 2:
When I added my solution it was this error. Then after some research, I tried in Firefox and it worked.

So basically this is stack issue from chrome so I thought of reporting as other campers might get the same issue.
Issue 1:
You can have a large frame in memory and want to drop a small percentage of labels with NA data just to clean things up. If you use drop() or dropna(), you will get a new object and effectively double the memory footprint. Favoring immutability is great, but under memory constraints this can be a killer.

Issue 2:
see related discussion in #2325

Possible and/or desirable to add an inplace keyword to dropna? Maybe an out keyword, so you can avoid typing the assignment? [Edit: I guess out doesn't really make sense like it does for numpy ufuncs.] Don't really mind if there's a copy even I just get tired of always doing assignment to the same name when I'm doing pre-, post-processing, etc.

dataframe = dataframe.action()
Issue 1:
It would be great to be able to have a custom checksum validator that can ignore certain branches of the DOM-tree when attempting to reuse markup.

The use case is for rendering static components. For static components that only need to be rendered once, we can just do the rendering on the server, and not have to render again on the client. Currently we have to pass down both the react markup AND the props used to generate the static markup. However, it is a waste to send those props down, if this component doesn't need to be rendered client-side.

One of the major performance concerns for using React is that apps not only have to send down markup but props as well, usually duplicating the data sent down to the client.

Being able to specify certain components as not needing a client side re-render, thus skipping check-sum, would save k-weight of the initial page load.

Issue 2:
React version:16.13.1

Steps To Reproduce

1.在package.json中引用react-file-viewer

2.npm install下载依赖

3.npm run build 打包 ，出奇的慢

Link to code example:

The current behavior

The expected behavior
Issue 1:
I want to use Sourcegraph code search and code review with scikit-learn. A project maintainer needs to enable it to set up a webhook so the code is up-to-date there.

Could you please enable scikit-learn on @sourcegraph by going to https://sourcegraph.com/github.com/scikit-learn/scikit-learn and clicking on Settings? (It should only take 15 seconds.)

Thank you!

Issue 2:
I want to use Sourcegraph code search and code review with scikit-learn. A project maintainer needs to enable it to set up a webhook so the code is up-to-date there.

Could you please enable scikit-learn on @sourcegraph by going to https://sourcegraph.com/github.com/scikit-learn/scikit-learn and clicking on Settings? (It should only take 15 seconds.)

Thank you!
Issue 1:
Jürgen Hermann opened SPR-4370 and commented

The API docs do not mention in what order (priority) duplicated properties are resolved. When using setLocations(a, b), is a:foo preferred over b:foo or vice versa?

http://static.springframework.org/spring/docs/2.5.x/api/org/springframework/core/io/support/PropertiesLoaderSupport.html#setLocations(org.springframework.core.io.Resource[])

Affects: 2.0.8, 2.5 final

Backported to: 2.0.9

Issue 2:
André Rouél opened SPR-8652 and commented

In a table column we use 19-digit IDs. The column type is set to NUMBER. An example of an ID is "1000000009704976470". Now, if we access by using NamedParameterJdbcTemplate.queryForLong (String sql, SqlParameterSource paramSource) or overloaded methods, it returns the for example the long 1000000009704976512L instead of 1000000009704976470L. The cause lies in the implementation of the method queryForLong.

The current implementation looks like this:

public long queryForLong(String sql, SqlParameterSource paramSource) throws DataAccessException {

Number number = queryForObject(sql, paramSource, *Number.class*);

return (number != null ? number.longValue() : 0);

}

A solution could look like this:

public long queryForLong(String sql, SqlParameterSource paramSource) throws DataAccessException {

Number number = queryForObject(sql, paramSource, *Long.class*);

return (number != null ? number.longValue() : 0);

}

One note, the JdbcTemplate class implements the method queryForLong properly.

Affects: 2.5.6, 3.0.5

Issue Links:

DATAJDBC-15 Incorrect output of big numbers when using NamedParameterJdbcTemplate.queryForLong ("is duplicated by")

Referenced from: commits 77372d7, 9b0412f, 118ee3f
Issue 1:
in html file-type

vscode version 0.10.6

My User Settings config says:

"editor.autoClosingBrackets": true,

but it still doesn't work.

For example, when you type in "<script" the IntelliSense suggestions pops up and you press enter on "script" it doesn't close the tag like this:

<script>
</script>

but it stays like this:

<script>

Issue 2:
Right now you have to type </ and press enter to close the last tag it would be much simpler to just press enter and have it close
Issue 1:
I installed the terminal from the windows app store, created a powershell tab, ran a command.

I then wanted to copy that command text, so I highlighted it, then pressed ctrl + c but it doesn't appear to have copied the command text. I also tried ctrl + shift + c. Getting desperate I right clicked on the tab item itself, looking for a menu where I could select "copy" but no such menu seems to exist. I also tried right clicking with the text selected hoping for a menu where I could select "copy selection" but again no such menu exists. In desperation I gave up - copying text does not appear possible. What am I doing wrong?

Issue 2:
Split screen in Windows Terminal opens the default shell in a new pane. Wouldn't be better to open the same kind of shell? (e.g. if I'm in #PowerShell Core, don't open Windows PowerShell in a new pane, open PowerShell Core again).
Issue 1:
I notice that Next.js assumes that all source code is basically put in the root, e.g. pages directory.

I prefer to keep a separate src directory, so it's clear what's source and what is not (build, passwords, etc). Is this possible / easy? How do I do it?

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

Expected Behavior

The with-apollo-auth example (https://github.com/zeit/next.js/tree/canary/examples/with-apollo-auth) should be updated to use the new _app.js functionality #4286. Each pages getInitialProps to check if a user is logged in should be moved to _app.js to reduce duplication of code.

Current Behavior

The with-apollo-auth example (https://github.com/zeit/next.js/tree/canary/examples/with-apollo-auth) has not yet been updated.

Steps to Reproduce (for bugs)

N/A

Context

Doing something similar to the following would be ideal, rather than having to put getInitialProps on each page that you want to authorize/redirect a user on via the checkLoggedIn function.

Note: I had an issue doing the following code however; seemed to be getting an infinite loop.. so hoping someone else can take a look and figure out a solution :D

import App, { Container } from 'next/app'
import React from 'react'

import redirect from '../lib/redirect'
import withData from '../lib/Apollo/withData'
import checkLoggedIn from '../lib/Apollo/checkLoggedIn'

class MyApp extends App {
static async getInitialProps({ Component, router, ctx }, apolloClient) {
let pageProps = {}

const { loggedInUser } = await checkLoggedIn(ctx, apolloClient)

if (!loggedInUser.me) {
// If not signed in, send them to the login page
redirect(ctx, '/login')
}

if (Component.getInitialProps) {
pageProps = await Component.getInitialProps(ctx)
}

return { pageProps, loggedInUser }
}

componentDidCatch(error, errorInfo) {
console.log('Error: ', error)
super.componentDidCatch(error, errorInfo)
}

render() {
const { Component, pageProps } = this.props
return (
<Container>
<Component {...pageProps} />
</Container>
)
}
}

export default withData(MyApp)

Your Environment

Tech
Version

next
6.0.2

node
9.11.1

OS
Windows 10

browser
Google Chrome

etc