WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Context:

Playwright Version: 1.3.0

Operating System: Windows 7

Node.js version: 12.18

Browser:Chromium

Code Snippet

const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch();
const context = await browser.newContext();
const page = await context.newPage();

await browser.close();
})();

Describe the bug

Chromium doesn't work, but other browsers seems to work fine

Console Output:

G:\GitHub\quran-api>set "DEBUG=pw:api" && node dircheck.js
(node:16052) UnhandledPromiseRejectionWarning: Error: browserType.launch: Host s
ystem is missing dependencies!

Full list of missing libraries:
api-ms-win-core-winrt-error-l1-1-0.dll

Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs
.
at validateDependenciesWindows (G:\GitHub\quran-api\node_modules\playwright\
lib\server\validateDependencies.js:78:11)
at async validateDependencies (G:\GitHub\quran-api\node_modules\playwright\l
ib\server\validateDependencies.js:47:16)
at async Object.validateHostRequirements (G:\GitHub\quran-api\node_modules\p
laywright\lib\server\validateDependencies.js:34:5)
at async Chromium._launchServer (G:\GitHub\quran-api\node_modules\playwright
\lib\server\browserType.js:154:13)
at async Chromium._innerLaunch (G:\GitHub\quran-api\node_modules\playwright\
lib\server\browserType.js:76:61)
at async ProgressController.run (G:\GitHub\quran-api\node_modules\playwright
\lib\progress.js:75:28)
at async Chromium.launch (G:\GitHub\quran-api\node_modules\playwright\lib\se
rver\browserType.js:62:25)
at async G:\GitHub\quran-api\dircheck.js:4:19
(node:16052) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This
error originated either by throwing inside of an async function without a catch
block, or by rejecting a promise which was not handled with .catch(). To termin
ate the node process on unhandled promise rejection, use the CLI flag `--unhandl
ed-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejecti
ons_mode). (rejection id: 1)
(node:16052) [DEP0018] DeprecationWarning: Unhandled promise rejections are depr
ecated. In the future, promise rejections that are not handled will terminate th
e Node.js process with a non-zero exit code.

Issue 2:
Context:

Playwright Version: 1.3.0

Operating System: Windows

Node.js version: 12.18.1

Browser: All

Code Snippet

const playwright = require('playwright');
const browserType = 'chromium';

async function botfunc() {
let browser = playwright[browserType].launch();
const context = await browser.newContext();
const page = await context.newPage();

await page.goto("http://google.com");
}

botfunc();

Describe the bug

Error log -

UnhandledPromiseRejectionWarning: Error: browserType.launch: Host system is missing dependencies!
Full list of missing libraries:
api-ms-win-core-winrt-error-l1-1-0.dll

It was solved when I used 1.0.2 version.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The label stays floated, if the user enters non numeric values to a TextField with type="number"

Current Behavior

The label stays not floated.

With only numeric values the label stays floated

Also there are some wierd characters if the TextField is empty:

Steps to Reproduce (for bugs)

create a TextField component and use it with type="number"

Context

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.8

React
15.6.1

browser
Firefox 54.0

Issue 2:
console logs null, undefined, undefined

<TextField
ref={(a, b, c) => {
console.log(a, b, c);
}}
...

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

Tech
Version

Material-UI
^1.0.0-beta.17

React
^15.0.2

browser
chrome os x

etc
Issue 1:
Currently (at least on 0.3.11, have checked master docs but not implementation), abs does not behave in a mathematically correct manner: abs(typemin(Int)) == typemin(Int) on my Linux x86-64 machine.

This problem plagues the C standard library abs(), llabs(), etc as well due to subtle asymmetry in 2's complement arithmetic. The C standard leaves behavior on INT_MIN, etc undefined, and this is fortunately documented, though easily missed by many programs.

I thus see 2 possible approaches:

Follow the C standard behavior, give no guarantee for abs(typemin), and document it.

Do something special with typemin, and document it.

Issue 2:
I saw the discussion in https://groups.google.com/forum/#!topic/julia-users/46i-NNUxpa8, and did not find an issue on github discussing this.

Most users will probably expect abs(x)>=0 and failing this assumption will probably create bugs that will be really hard to find (especially for the typical Julia user).

@StefanKarpinski suggested to throw an error for these numbers, and that seems like a good option. The problem is that performance will suffer so much that some users might want access to the simple inlinable abs function so that we have to add a abs_raw.
Issue 1:
Electron version: any

Operating system: Linux

Expected behavior

Latest Ubuntu comes with Wayland a default display server.

On embedded devices, wayland provides usually the best rendering performance, at least compared to X11 where the performance is usually pretty poor.

Actual behavior

Current linux / arm / arm64 binary releases are great but run pretty bad from my experience on embedded devices. They all link to libx11 / gtk which makes them unusable for wayland.

libGtk can be build with --wayland-backend and then electron can be built against it

I would really like electron team to consider providing prebuilt binaries usable with wayland, that would open a new range of possibilities, especially on embedded devices.

Issue 2:
Electron version: 1.6.7

Operating system: Win 7

Hi!

Several users reported that they can't use screensharing, because there is no available sources. For this cases getSources method is called, but callback is not triggered.

I don't know how desktopCapturer works inside, so maybe you have ideas what's going wrong. May it be related to system preferences or drivers? May it be issue of 56 chromium?

Unfortunately I can't check this issue on 1.7.* for now.

Thanks!
Issue 1:
As far as I can tell, the static getInitialProps doesn't provide a uniform way to access url params on the client and server. On the server, you can access req and parse the url yourself. On the client, we don't seem to have access to the route information within the getInitialProps function. The uses for this are fairly obvious, i think, such as loading a particular user profile based on an :id param, and so on. I'm also wondering if auth could somehow be implemented here too -- thought I'm less clear if that's the best API.

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

This pages/_document.js does change color only after 2 triggered HMRs:

import Document, {Head, Main, NextScript} from 'next/document';

export default class MyDocument extends Document {
static getInitialProps(ctx) {
return super.getInitialProps(ctx);
}

render() {
return (
<html>
<Head>
<style jsx global>{`
body {
color: green;
}
`}</style>
</Head>
<body>
<Main />
<NextScript />
</body>
</html>
);
}
};

This is in a fresh project (yarn add next@^3.0.1-beta react react-dom, hello world pages/index.js and the above in pages/_document.js), running server with yarn next.

Expected Behavior

When I edit color: green to another color (e.g. red) and save, page updates to show the new color.

Current Behavior

When I edit color: green to another color (e.g. red) and save, page stays green. Then I edit the color again (e.g. black) and save, page becomes red.

Context

Trying to get a new project with some global styling going.

Your Environment

Tech
Version

next
2.4.7 and 3.0.1-beta.13 (using styled-jsx 1.0.8)

node
8.1.3

OS
OS X 10.9.5

browser
Chrome 59

editor
Sublime Text 3 (build 3141)
Issue 1:
Bug report

Bug summary

Calling show() after generating a simple line plot causes my machine to log my user out in what appears to be a forced shutdown. This problem only occurs when running python through terminal and not through a Jupyter Notebook (though in a notebook I have to run the cell twice to see any results).

Code for reproduction

import numpy as np
import matplotlib.pyplot as plt

cond1 = np.array([25]*10)

plt.plot(cond1)

plt.show()

Actual outcome

(base) Johns-MacBook-Pro:Work_Code johnwilson$ python condition_numbers_new.py
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.643 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.644 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.644 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.644 python[11487:59261] CGSTrackingRegionSetIsEnabled returned CG error 268435459
2019-08-27 16:28:51.649 python[11487:59261] HIToolbox: received notification of WindowServer event port death.
2019-08-27 16:28:51.649 python[11487:59261] port matched the WindowServer port created in BindCGSToRunLoop

Expected outcome

This code should produce the following plot (generated by running the above code in a jupyter notebook) instead of shutting down.

Matplotlib version

Operating system: macOS Mojave, Version 10.14.6

Matplotlib version: 3.1.0

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

Python version: Python 3.7.3

Jupyter version:

jupyter==1.0.0

jupyter-client==5.3.1

jupyter-console==6.0.0

jupyter-core==4.5.0

Other libraries:

numpy==1.16.4

I installed everything through the Anaconda distribution using default settings just last week.

Issue 2:
The weekly build with nightly wheels from numpy and pandas

has failed. Check the logs for any updates that need to be

made in matplotlib.

https://github.com/matplotlib/matplotlib/actions/runs/4390878412
Issue 1:
I'm receiving a weird behavior which is: when using tab key to switch between TextField for the first time, the position of the TextField changes a little. The following screen shot might better explain the situation. I think it's because of 'FloatingLabelText` but what I don't understand is why only tab key's event causes this problem not click event, and why does this behavior only happens the first time.

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

Expected Behavior

When focus on a textfield using tab key, the position should stay the same.

Current Behavior

As shown above, only the position of TextField named 'treatmentType' is not changed because it's focused by click event rather than tab key. And if the same TextField was focused by tab before, its position won't be changed.

Steps to Reproduce (for bugs)

Render component: Table > TableBody >TableRow >TableRowColumn > TextField

Click on the first TextField in the first TableRowColumn

Switch focus on the otherTextField by pressing Tab key.

class TreatmentContent extends React.Component {
constructor(props) {
super(props);
this.state = {
type: '',
notes: '',
status: '',
location: '',
food: '',
firstName: '',
lastName: '',
email: '',
day: ''
};
this.notesToAdd = {
type: 'text',
notes: 'text',
status: 'text',
location: 'text',
food: 'text',
firstName: 'text',
lastName: 'text',
email: 'text',
day: 'number',
};
this.reorgTableRow = this.reorgTableRow.bind(this);
}

reorgTableRow() {
const notesKeys = _.keys(this.notesToAdd);
const chunkedKeys = _.chunk(notesKeys, 3);
return _.map(chunkedKeys, (keyChunk, i) => (
<TableRow selectable={false} key={i} style={{border: 'None'}}>
{_.map(keyChunk, (keyName, j) => (
<TableRowColumn key={j}>
<TextField
hintText={keyName}
floatingLabelText={keyName}
type={this.notesToAdd[keyName]}
value={this.state[keyName]}
/>
</TableRowColumn>
))}
</TableRow>
));
}

render() {
return (
<div>
<Table>
<TableBody displayRowCheckbox={false}>
{this.reorgTableRow()}
</TableBody>
</Table>
</div>
);
}
}

Context

Your Environment

"react": "^15.6.1",

"material-ui": "latest",

browser: Chrome v63

Tech
Version

Material-UI

React

browser

etc

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

Expected Behavior

The tab indicator must always show the selected tab

Current Behavior

When the number of tabs in a tab menu changes the indicator have a wrong position until next interaction such as clicking a new tab.

Steps to Reproduce (for bugs)

Go to https://codesandbox.io/s/2pm5jzmk10

Select a random tab

Click switch

Chehck indicator position

Context

I Noticed this issue when trying to remove some tabs based on the users permission role. I quickly realised that the indicator was not in sync with the amount of tabs inside the menu.

Reproduction Environment

Tech
Version

Material-UI
1.0.0-beta.11

React
15.5.3

browser
Google Chrome v61

Your Environment

Tech
Version

Material-UI
1.0.0-beta.6

React
15.6.1

browser
Google Chrome v61
Issue 1:
Describe what you were doing when the bug occurred:

I was watching the Flamegraph

I clicked on a node

I clicked on the Ranked tab and the bug occurred

Please do not remove the text below this line

DevTools version: 4.2.1-3816ae7c3

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157108

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157054)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:157577)

at vl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:314907)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)

at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:107381)

at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)

at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)

at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89544)

Component stack: in vl

in div

in div

in div

in wo

in Unknown

in n

in Unknown

in div

in div

in Li

in $e

in dn

in Ca

in Pc

Issue 2:
PLEASE INCLUDE REPRO INSTRUCTIONS AND EXAMPLE CODE

I got this error when I click 'Ranked'.

Please do not remove the text below this line

DevTools version: 4.0.4-3c6a219

Call stack: at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11441

at Map.forEach ()

at commitIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11387)

at e.getRankedChartData (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:11:11920)

at _i (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56:277123)

at Ha (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:55890)

at Xl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:98280)

at Hl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:84255)

at Fl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:81285)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:43:25363

Component stack: in _i

in div

in div

in div

in Or

in Unknown

in n

in Unknown

in div

in div

in Ha

in le

in ve

in ko

in Ul
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: xxx

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

xxx

xxx

xxx

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

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

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

Just put your stack trace here!

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.7

Operating System version: MacOS 10.14.6

Java version: 1.8.0_231

Steps to reproduce this issue

参数验证信息被吞掉了

https://github.com/apache/dubbo-samples/blob/master/java/dubbo-samples-validation/src/main/java/org/apache/dubbo/samples/validation/ValidationConsumer.java

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

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

Just put your stack trace here!

#5432
Issue 1:
Description

I find that it would be practical to be able to set up application group with a windows position that can be configured in the same way as the application groups set up on the Surface Duo :

All this can be configured with a positioning based on FancyZones as well as an application group icon in the taskbar :

Fancyzone amelioration of #5901

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18363.752]
PowerToys version: v0.16.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Press Win + '

Attempt to scale zones to fit full screen

Expected behavior

Zones to fit complete screen

Actual behavior

There is a gap along the right side of the screen and along the bottom of the screen

Screenshots
Issue 1:
Following is what I recently made using ThreeJS by importing OBJ files:

http://devplace.in/~harman/geometry_viewer/mug.html

http://devplace.in/~harman/geometry_viewer/cylinder.html

Users report following problem:

The model appears (briefly flashing) while user rotates. It appeared just fine before I applied material. User just get a blue background and the performance monitor in the bottom left corner. If he rotate the invisible model really quickly, it'll display the model briefly for a frame or two, but then goes back to blue.

Similar issue has been noticed at threeJS Editor: http://threejs.org/editor/ Model disappears on changing renderer. However, I'm not sure whether both of these problems are same.

Some other set of users encountered edges / lines on the model surface even when wireframe flag was not set. See:

and

It looks like a renderer problem, but still not sure.

From above image of mug, one can see the inner yellow bottom from the outside of the mug which is unexpected.

So is it a bug(s) in ThreeJS or it should be something fixable by me?

Issue 2:
Following is what I recently made using ThreeJS by importing OBJ files:

http://devplace.in/~harman/geometry_viewer/mug.html

http://devplace.in/~harman/geometry_viewer/cylinder.html

Users report following problems:

User just get a blue background and the performance monitor in the bottom left corner. If he rotate the invisible model really quickly, it'll display the model briefly for a frame or two, but then goes back to blue. It appeared just fine before I assigned material to models.

Similar problem has been noticed in ThreeJS Editor: http://threejs.org/editor/. When one changes the renderer from the drop down, model disappears. However, I'm not sure whether both these problems are same.

Other user encountered edges / lines on model surface even when the wireframe flag is not true. See:

and

This may be the renderer problem, but still not sure.

Also in above image of mug, one can see the inner yellow bottom from outside of the mug which is unexpected.

So, is it a bug(s) in ThreeJS or it should be something fixable by me?
Issue 1:
🐛 Bug 🐛

When loading a saved sparse tensor an error occurs: RuntimeError: size is inconsistent with indices: for dim 0, size is 3 but found index 140115406052656

Clearly, that is impossible (can't even fit such a large tensor on my memory)

To Reproduce

Steps to reproduce the behavior:

Install PyTorch and torch-sparse

Run the below code (which produces the above error for me)

import torch
x=torch.zeros(3,3)
x[1][1]=1
x=x.to_sparse()
torch.save(x, './scratch/test4e')
y = torch.load('./scratch/test4e')

Expected behavior

Loads y normally ...

Environment

PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.4 LTS
GCC version: (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
CMake version: version 3.10.2

Python version: 3.8
Is CUDA available: Yes
CUDA runtime version: 10.1.243
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 440.59
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] numpy==1.18.1
[pip3] torch==1.4.0
[pip3] torchvision==0.5.0
[conda] torch 1.4.0 <pip>
[conda] torch-cluster 1.4.5 <pip>
[conda] torch-geometric 1.4.1 <pip>
[conda] torch-scatter 2.0.3 <pip>
[conda] torch-sparse 0.5.1 <pip>

cc @ezyang @gchanan @zou3519 @vincentqb

Issue 2:
Current implementation of LSTMCell calls internal C function which makes it infeasible to write a layer normalization of LSTM cell by wrapping it with nn.LayerNorm.

It would be great to add this feature.

We could add trainable parameters inside RNNCellBase as follows

class RNNCellBase(nn.Module):
def __init__(self, input_size, hidden_size, bias, num_chunks):
super(RNNCellBase, self).__init__()
self.input_size = input_size
self.hidden_size = hidden_size
self.bias = bias
self.weight_ih = Parameter(torch.Tensor(num_chunks * hidden_size, input_size))
self.weight_hh = Parameter(torch.Tensor(num_chunks * hidden_size, hidden_size))
self.ln_ih = nn.LayerNorm(num_chunks * hidden_size)
self.ln_hh = nn.LayerNorm(num_chunks * hidden_size)
self.ln_c = nn.LayerNorm(hidden_size)

However, the it is impossible to use it for the computation

return _VF.lstm_cell(
input, hx,
self.weight_ih, self.weight_hh,
self.bias_ih, self.bias_hh,
)

as it calls C functions.

And writing it purely in Python, the speed would be too slow.