WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
When I use component , given the following code it adds the below css rules

.MuiGrid-spacing-xs-16 {
width: calc(100% + 16px);
margin: -8px;
}

My code

<Grid container direction={'row'} justify={'space-between'} align={'flex-start'}>
<Grid>
<OfferPreview />
</Grid>
<Grid>
<OfferPreview />
</Grid>
</Grid>

The result is that the container overlaping. Because the margin -8px affect also top and bottom.

The fix could be...

.MuiGrid-spacing-xs-16 {
width: calc(100% + 16px);
margin: 0 -8px;
}

Version

Material-UI: 1.0.0-beta.5

Issue 2:
The <Grid container> extends beyond its parent, with half of spacing size.

I have marked the extra width in red, also setting spacing to zero fixes the problem.

Here is a working example: https://codesandbox.io/s/Y8nzGm5W.

Similar code with a zero spacing works as expected: https://codesandbox.io/s/NxvYxvQpL.
Issue 1:
requests does not work with charset-normalizer 3.0.0 or 3.0.1, blocking users of requests from updating to the latest charset-normalizer.

Expected Result

Actual Result

Reproduction Steps

import requests

System Information

$ python -m requests.help

{
"paste": "here"
}

Issue 2:
Simple test under Python 3.3.2, using the current 2.0 branch of requests (same behaviour with requests-1.2.3 btw); inspecting request headers with requestb.in.

The Content-Type header contains two entries. I expected my stipulated header to override (replace) application/x-www-form-urlencoded.

import requests

data = open('C:/my_audio_files\sample_50.wav', 'rb').read()

response = requests.post(url = "http://requestb.in/183gv9g1"

data=data,

headers={'Content-Type': 'application/octet-stream'}

)

FORM/POST PARAMETERS

None

HEADERS

Content-Length: 38206

User-Agent: python-requests/1.2.3 CPython/3.3.2 Windows/8

Connection: close

Host: requestb.in

Content-Type: application/octet-stream, application/x-www-form-urlencoded

Accept: /

Accept-Encoding: identity, gzip, deflate, compress

RAW BODY

RIFF6�WAVEfmt etc...
Issue 1:
If I wrap the playwright test object with our own custom test class, no tests run. Importing the playwright test object into the spec file directly works as expected.

I am attempting to move a large codebase from a Selenium based framework (theintern.io) to playwright. We already have a strong test API that the framework implementation sits behind, unfortunately when it comes to implementing the test runner part of that API using Playwright we are running into an issue where it doesn't seem to find any thing to run.

The repo below has a very simple repro case.

Importing test from @playwight/test works as expected, but as soon as I try and use it from my wrapper class, nothing runs.

Test

import { MyBdd } from "../bdd";
// import { test } from "@playwright/test";

MyBdd.test("run google", async (page) => {
// test("run google", async ({ page }) => {
await page.goto("https://www.google.com");
await page.goto("https://www.google.com/");
await page.getByRole("button", { name: "Reject all" }).click();
await page.getByRole("combobox", { name: "Search" }).click();
await page.getByRole("combobox", { name: "Search" }).fill("bob");
await page.getByRole("combobox", { name: "Search" }).press("Enter");
});

Test wrapper

import { test, Page } from "@playwright/test";
export class MyBdd {
public static describe(name: string, func: () => void) {
return test.describe(name, func);
}
public static before(func: () => void) {
return test.beforeAll(func);
}
public static test(name: string, func: (args: Page) => Promise<void>) {
return test(name, (args) => func(args.page));
}
}

System info

Playwright Version: [v1.33.0]

Operating System: [All]

Browser: [All]

Other info:

Source code

[ x] I provided exact source code that allows reproducing the issue locally.

Link to the GitHub repository with the repro

https://github.com/David-Hart-i2/playwright-bdd-test

Steps

[Run the test]

Expected

The test to be found and run

Actual

The test doesn't seem to be found. I get the output like a test has been run, but with zero tests.

Issue 2:
System info

Playwright Version: [v1.31.1]

Operating System: macOS 13.0

Browser: Chromium

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

const fileToUpload = path.join(
__dirname,
`../e2e/__shared__/fixtures/samples/${wsdlRestApi}.wsdl`
)

//fileToUpload yields: /Users/calvin/Github/ui/e2e/__shared__/fixtures/samples/weather.wsdl

const fileChooserPromise = page.waitForEvent('filechooser')
await page
.getByRole('button', {
name: 'Drag and drop files here or click to upload (json/wsdl/xml/xsd/yml/yaml/zip)',
})
.click()
const fileChooser = await fileChooserPromise
await fileChooser.setFiles(fileToUpload)

This seems to only be happening for .wsdl files, as similar code was used for .yaml files and didn't seem to come up with this path error.

Expected

Filechooser should select the path that fileToUpload yields, but cuts out the folders in the directory /e2e/__shared__/fixtures/samples/

Actual

Filechooser is choosing /Users/calvin/Github/ui/weather.wsdl instead of /Users/calvin/Github/ui/e2e/__shared__/fixtures/samples/weather.wsdl

[Describe actual behavior]
Issue 1:
Possibility to hide the menu bar on windows. I takes up unnecessary space and it's barely being used because of the command palette and hotkeys for remaining functionality.

Issue 2:
A lot of software on Windows (e.g. Sublime Text, Firefox) allow you to collapse the menu bar so there's only the tab bar. The menu bar can then be collapsed/expanded by pressing the Alt key.

It would be great to have this feature in Atom as it maintains the look and feel across different platforms and gives slightly more vertical space.

(By menu bar I mean the "File / Edit / View / etc" bar.)
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.5.8

Operating System version: win10

Java version: 1.8

Step to reproduce this issue

Write a service to upload file, such as pdf document...

interface maybe like this:

Result parseFile(String filename,InputStream inputStream);

Use a specified document test the interface.

reproduce this issue maybe need a specified pdf document.

Pls. provide [GitHub address] to reproduce this issue.

the content of pdf documents.

What do you expected from the above steps？

null, and exceptions below.

What is actually happen?

In fact, the first request throw a SocketTimeoutException, see below, but latter requests reponse correctly. So I guess that is because of initializaton probleam. Then I find when I set timeout=2000 on <dubbo:reference>, everything works rightly. It's very confusing to me. According to exceptions thrown by provider, that is, the consumer doesn't send input stream correcly, and it throws a timeout exception immediately, so provider cannot get input stream, it throws a org.apache.tika.exception.ZeroByteFileException.

If there is an exception, please attach the exception trace:

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.4.1

Operating System version: ANY

Java version: ANY(8 or above)

Steps to reproduce this issue

Apollo config center not work via XML configuration

# vm parameter
-Dapp.id=ABC

<!-- configuration xml -->
<dubbo:config-center protocol="apollo" address="127.0.0.1:8080" namespace="dubbo">
<dubbo:parameter key="env" value="DEV"/>
</dubbo:config-center>

And, this configuration is not friendly

Objective

Apollo config center initialized via XML like

<dubbo:config-center protocol="apollo" address="127.0.0.1:8080" namespace="dubbo">
<dubbo:parameter key="env" value="DEV"/>
<dubbo:parameter key="app.id" value="ABC"/>
</dubbo:config-center>

Or var XML with System Properties: "-Dapp.id=ABC -Denv=DEV -Dapollo.meta=http://127.0.0.1:8080"

<dubbo:config-center protocol="apollo" namespace="dubbo"/>
Issue 1:
🐛 Bug

torch.nn.functional.adaptive_avg_pool2d causes a segmentation fault when the parameter output_size is an empty tuple, () or an empty array [].

To Reproduce

import pytorch

torch.nn.functional.adaptive_avg_pool2d(torch.tensor([1,2,3,4,5]), ())

Expected behavior

Proper error handling for an empty tuple or empty array like adaptive_avg_pool1d.

Environment

PyTorch version: 1.5.0

Is debug build: No

CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.4 LTS

GCC version: Could not collect

CMake version: version 3.14.0

Python version: 3.7

Is CUDA available: No

CUDA runtime version: No CUDA

GPU models and configuration: No CUDA

Nvidia driver version: No CUDA

cuDNN version: No CUDA

Versions of relevant libraries:

[pip] numpy==1.18.1

[pip] torch==1.5.0

[pip] torchvision==0.6.0a0+82fd1c8

[conda] blas 1.0 mkl

[conda] cudatoolkit 10.1.243 h6bb024c_0

[conda] mkl 2020.1 217

[conda] mkl-include 2020.1 217

[conda] mkl-service 2.3.0 py37he904b0f_0

[conda] mkl_fft 1.0.15 py37ha843d7b_0

[conda] mkl_random 1.1.0 py37hd6b4f25_0

[conda] numpy 1.18.1 py37h4f9e942_0

[conda] numpy-base 1.18.1 py37hde5b4d6_1

[conda] pytorch 1.5.0 py3.7_cuda10.1.243_cudnn7.6.3_0 pytorch

[conda] torchvision 0.6.0 py37_cu101 pytorch

cc @ezyang @gchanan @zou3519

Issue 2:
🐛 Bug

In torch.nn.functional.adaptive_avg_pool2d and torch.nn.functional.adaptive_avg_pool3d, a segmentation fault occurs when passing an empty tuple (or an empty array) for output_size parameter. It occurs even though passing a valid 4D tensor for input parameter.

To Reproduce

import torch
# for 3d
torch.nn.functional.adaptive_avg_pool3d(torch.randn([2,2,2,2]), [])
# for 2d
torch.nn.functional.adaptive_avg_pool2d(torch.randn([2,2,2,2]), [])

Environment

PyTorch version: 1.5.0

Is debug build: No

CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.4 LTS

GCC version: Could not collect

CMake version: version 3.14.0

Python version: 3.7

Is CUDA available: No

CUDA runtime version: No CUDA

GPU models and configuration: No CUDA

Nvidia driver version: No CUDA

cuDNN version: No CUDA

Versions of relevant libraries:

[pip] numpy==1.18.1

[pip] torch==1.5.0

[pip] torchvision==0.6.0a0+82fd1c8

[conda] blas 1.0 mkl

[conda] cudatoolkit 10.1.243 h6bb024c_0

[conda] mkl 2020.1 217

[conda] mkl-include 2020.1 217

[conda] mkl-service 2.3.0 py37he904b0f_0

[conda] mkl_fft 1.0.15 py37ha843d7b_0

[conda] mkl_random 1.1.0 py37hd6b4f25_0

[conda] numpy 1.18.1 py37h4f9e942_0

[conda] numpy-base 1.18.1 py37hde5b4d6_1

[conda] pytorch 1.5.0 py3.7_cuda10.1.243_cudnn7.6.3_0 pytorch

[conda] torchvision 0.6.0 py37_cu101 pytorch

cc @ezyang @gchanan @zou3519 @albanD @mruberry
Issue 1:
Is there any way to combine two different kernels in scikit-learn for different dimensions?

For example, if there is two input dimensions in GP, is there any way to define:

K((x,y),(x',y') = k(x,x') * k(y,y')

More precisely, how can we define active dimension for each of them?

Thanks for consideration.

Issue 2:
When doing kernel engineering, you often want different parts of the kernel to operate on different features (like some on time and some on space and some on whatever).

From what I can see, this is not currently possible with sklearn.

GPy implements that with a active_dims option for each kernel.

That seems relatively easy, and I think it would be pretty cool. ping @jmetzen (also @jnothman and @GaelVaroquaux for the voice of reason?)
Issue 1:
The dgemm function does not write the result into c even when using overwrite_c.

I think this is a long-standing bug. I found an earlier mention of it here:

https://mail.scipy.org/pipermail/scipy-user/2008-August/017954.html

Issue 2:
Turns out the overwrite option, when provided, does not work in all cases. So, it would be nice to clarify that this requires a Fortran array of the right type.
Issue 1:
Describe the bug

The official fat line example doesn't work if we change the line scale to include negative.

To Reproduce

Steps to reproduce the behavior:

Go to Three.js official examples in the repo

Find the source file of webgl_lines_fat.html

At line 109, change to any negative scale.

Code

line.scale.set(-1, 1, 1);

Expected behavior

With a negative scale, lines are disappeared.

Platform:

Device: Desktop

OS: MacOS

Browser: Chrome

Three.js version: dev

Issue 2:
As the title say: a Line2 disappears completely when the scale is set to negative on a single axis line2.scale.set(-1, 1, 1). The line is obviously still there but it's not rendered.

Weirdly, if the scale is set to negative on more than one axis line2.scale.set(-1, -1, 1), the line appears again.

Here's a jsfiddle that demonstrates the issue: https://jsfiddle.net/jacopocolo/5fsotdpw/16/

Toggling wireframeToggle on line 7 to true shows two Line2 in wireframe but if wireframeToggle is set to false, only one is visible.

Three.js version

Dev

r117

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS (only tested here)

Linux

Android

iOS
Issue 1:
I'm getting an issue where throwing an unhandled error turns into an infinite loop because the guarded callback wrapper fails to extract the error from the event:

This causes the reconciler to ignore the error, thus triggering it again.

To reproduce, I flipped useSyncScheduling to false in ReactDOMFiber (not sure if that was important), started examples/real-world from Redux and added a throw to its User component.

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

Bug

What is the current behavior?

When a component returns something other than a valid React element, or null, it throws and does so infinitely. This is render-blocking and freezes the window.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

This happened to me when creating a Provider-type component that rendered its children directly. More specifically, when they were undefined. Eg

class Provider extends React.Component {
render() {
return this.props.children // should throw once.
}
}

// Elsewhere
<div>
<Provider>this works correctly</Provider>

// This freaks out
<Provider />
</div>

Is there a [CodePen, Fiddle, etc] of @next somewhere, that I can use to demonstrate this?

What is the expected behavior?

It should throw, but only once and not freeze the browser.

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

React 16.0.0-alpha.4

Yes, see http://codepen.io/rthor/pen/bqYBap?editors=0010#0

PS I know it's an alpha version 😄
Issue 1:
This is an issue being there since 2.1.

The FormValidator runs the validation of the underlying object graph in 2 cases:

on the root form

in case all parents have cascade_validation set to true

This means that when you have a subform with mapped set to false, the only way to have its object graph validation is to enable cascade_validation on all parents of the unmapped field, which will lead to duplicate validation of the object graph of the parent if it uses @Assert\Valid() properly.

As unmapped forms define a new object graph, I think it would make sense to run the validation on them as well.

/cc @webmozart

Issue 2:
SF 2.5.2 - after upgrade from 2.4

Validation in fallback mode

After submit form with errors (fields: text, datetime, collection + some assertions via annotations)

I'm going to webprofiler -> form

Error:

Key "id" for array with keys "submitted_data, errors, synchronized, children" does not exist in @WebProfiler/Collector/form.html.twig at line 417
500 Internal Server Error - Twig_Error_Runtime
Issue 1:
For code that builds a UI has to be readable. I understand that Dart is kind of like a simple version of Java, but it is not really a programming language for building a UI. For example, it doesn't have a closing tag. As a result, It is very hard to build a picture in mind with this unreadable code.

Moreover, Flutter was inspired by React. How can Flutter doesn't have JSX but has this kind of unreadable code? I am very scared that Flutter is going to die very soon as the early days of AnglurJs.

I understand people who work in Google are smart, but we also have some people who are not really smart choose React instead of Dart, and this is one of the reasons why Dart was dead in the past.

Issue 2:
Please see this movie, from my Nexus 5X: https://youtu.be/VC6spk7P6Xg

Notice how the FAB, while transitioning up, has a square shadow around it. It doesn't have the square the entire transition, but starting at second 3 of the transition.
Issue 1:
cc @pandas-dev/pandas-core

Targeting Friday June 8th.

Issue 2:
I am trying to merge multiple dataframe with consecutive merge operations, I want to add a suffix to the name of the newly merged column names. A simplified version of my code looks like this:

from pandas import *
f0 = DataFrame(columns=['data'], data=[1,2,3], index=['a','b','c'])
f1 = DataFrame(columns=['data'], data=[4,5,6], index=['c','b','a'])
f2 = DataFrame(columns=['data'], data=[7,8,9], index=['a','c','b'])
merged = f0
merged = merged.merge(f1, left_index=True, right_index=True, suffixes=("_0", "_1"))
merged = merged.merge(f2, left_index=True, right_index=True, suffixes=("", "_2"))
print merged.columns

With pandas 0.15.2 on python 2.7 this returns:

Index([u'data_0', u'data_1', u'data'], dtype='object')

while I would have expected

Index([u'data_0', u'data_1', u'data_2'], dtype='object')
Issue 1:
In matplotlib 3.5.1 on Linux (arch and opensuse) pcolormesh is causing some extreme slowdowns. When I try to zoom or pan inside the window, reactions from the mouse are very slow, such that the drawn zoom indicator is >1s delayed and the window/notebook freezes.

The extend varies somewhat by backend. Using the %matplotlib notebook backend in jupyter notebook, freezes as soon as one tries to zoom, and the kernel has to be restarted. Using Qt5Agg with ipython from the terminal, also freezes immediately. With the Gtk3Agg backend the window does not fully freeze but the zoom indicator etc. are extremely laggy.

I checked with pcolor and pcolorfast as well as imshow and all work fine.

Test case:

import matplotlib.pyplot as plt
import numpy as np

x = np.linspace(-5,5,512)
X,Y = np.meshgrid(x,x)
g = np.exp(-(X**2+Y**2)/2)

plt.figure()
ax = plt.subplot(111)
plt.pcolormesh(X,Y,g)
plt.show()

Run and select the zoom button in the opened window. If using Qt5Agg the window (and terminal) freezes, CTRL-C only works with very long delay.

Issue 2:
Bug summary

After updating to mpl 3.5.0 my program hangs after plotting with pcolormesh(), no error messages. It works fine witl mpl 3.3.3. When I reduce the nx,ny values in my program it works fine.

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt
import cartopy.io.img_tiles as cimgt
import cartopy.crs as ccrs

fig, ax1 = plt.subplots(num="TestXX", figsize=(30/2.54, 25/2.54))

#add a map of the Netherlands
request = cimgt.OSM()
ax1=plt.axes(projection=request.crs)
ax1.set_extent([3.25, 7.35, 50.45, 53.55],ccrs.PlateCarree())
ax1.add_image(request, 10)

#create a rectangular grid a little smaller than the map
#with cell sizes of 0.01 degree filled with random values
nx=400
ny=300
xedges=np.linspace(3.3, 7.3, nx)
yedges=np.linspace(50.5, 53.5, ny)
zvalues=np.random.random((nx, ny))

ax1.pcolormesh(xedges, yedges, zvalues.T ,\
alpha=0.3, shading='auto', transform=ccrs.PlateCarree())

plt.show()

Actual outcome

Program hangs. Toolbar doesn't response. Hourglass is visible. No errors.

Expected outcome

Plot has been made. Toolbar works, normal running program.

Additional information

It worked fine with matplotlib 3.3.3. I can then increase nx,ny to 8000,6000.(I didn't try higher values)

It seems that there is a 'problem' with pcolormesh().

It works fine in mpl 3.5.0 with reduced nx,ny values(i.e. 100,75)

Operating system

Windows 10

Matplotlib Version

3.3.3 and 3.5.0

Matplotlib Backend

Qt5Agg

Python version

Python 3.8.12

Jupyter version

No response

Installation

conda
Issue 1:
Having animated route transitions would be nice, as this is one of the many benefits through client-side routing. Doing so should be left up to the user in my opinion (some people prefer CSS transitions over more fine-grained control with react-motion etc). As I understand it, one would need to modify the top-level App component.

The client entry file seems to look for a globally assigned __NEXT_DATA__.app variable but I can't find any documentation on that.

Issue 2:
I noticed that one React root is used, while this is certainly the simplest solution, I'm curious if there's a plan to support or use multiple React roots?

In the current architecture with a single root, a client-side navigation blows away everything visible on the page and re-renders everything for the new route, including parts of the component tree that exist on both routes.

With multiple React roots, common site elements like a <header> could be in their own React root, and when the same page "region" exists between two routes the component tree won't need to be torn down and re-rendered during that client-side navigation. An architecture with multiple roots/regions would also allow the server to flush out to the response before waiting for the entire page to be rendered.

I imagine that when using Next, it'll be natural to break out common page-level UI component trees, like the site's header, and reuse it on all pages, similar to an "include", and at these page "region" boundaries there's an opportunity to use multiple React roots to speed up both server and client rendering.

So I'm mainly curious if this sort of thing might be part of Next in the future, or if the simplicity of one React root and re-rendering the entire page on client-side navigation is an explicit design decision for the framework?
Issue 1:
Some of the plot titles / legends seem to overrun the margins of the plots and get cut off.

See the narrative documentation here http://scikit-learn.org/dev/modules/gaussian_process.html for a start

Issue 2:
The plot in http://scikit-learn.org/dev/auto_examples/gaussian_process/plot_compare_gpr_krr.html

doesn't look good on the website (and is referred to in the user guide).

The legend is not really readable. Needs some tweaking with the legend position.