WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
For the keyboard manager on remaping shortscuts, it would be really help full if I didn't have to have a modifer key along with another key. For example i'm attempting to remap Alt + Left to F2 however I can't do that as it require a modifer key so I would have to do Alt + F2.

I did a search the issues and didn't see this so hopefully i'm not opening up a duplicate.

Issue 2:
Summary of the new feature/enhancement

Ability to remap a single key (² for example, sleeping in the top left corner of my KB), and assign it for example to alt+space, in order to open powertoys run, or to "open a new terminal", or whatever
Issue 1:
Describe the bug

A specific test file (for color space testing) is causing threejs to become unresponsive and take the entire browser with it.

To Reproduce

Steps to reproduce the behavior:

download the attached file

unlit=color.zip

open the file in https://threejs.org/editor/

zoom out until you can see the content

note browser is hanging, changing tabs doesn't change that, have to kill browser

Expected behavior

File loads and displays fast, it's pretty small.

Screenshots

The file is a test case for textures/colors/vertex colors. It has many small meshes and materials but loads very fast in other systems (e.g. Babylon Sandbox or gltf.report)

Platform:

Device: Desktop

OS: Windows 10

Browser: Chrome 95.0.4638.69

Issue 2:
Describe the bug

This appears to be the core issue behind google/model-viewer#2915

It seems that something about a recent materials change has caused shader compilation on my PC to take ~10x(!) longer than it used to. If I were to guess at why I'd say that it's probably the DirectX shader compiler hitting a pathological case that wasn't there before and trying to do an insane loop unroll or something of that nature.

To Reproduce

Steps to reproduce the behavior:

git checkout r132

Open examples/webgl_animation_keyframes.html

Observe load time

git checkout r133

Refresh examples/webgl_animation_keyframes.html

Observe (much longer) load time

With r132 I get the following recording from the performance tab in Chrome dev tools (though it's worth noting the same regression is also observable when using Firefox):

You can see that the largest block of work on the main thread takes ~500ms. It bottoms out at a bunch of getProgramInfoLog calls and a couple of texImage2D calls that all take about 20-50ms.

With r133 the recording looks significantly different. There are multiple calls to getProgramInfoLog that take ~150ms each and one particularly long one that takes 3+ seconds! In total, the block of work that represents to model's upload to the GPU takes nearly 5 seconds to complete, a 10x increase between versions (and consistent with what was seeing.)

Platform:

Device: Desktop, Intel Core i7-10700K, Nvidia GTX 1660 Super

OS: Windows 11

Browser: Chrome Canary 97.0.4685.2, Firefox Nightly 95.0a1

Three.js version: r133
Issue 1:
fetch('https://httpbin.org/cookies/set?foo=bar', cookies={'foo1':'bar1'}, meta={'dont_merge_cookies': True}, headers={'Cookie':'foor2=bar2'})

request.cookies
request.headers['cookie']

is:

{'foo1': 'bar1'}

b'foor2=bar2'

but response.text:

{\n "cookies": {\n "foor2": "bar2"\n }\n}\n

shouldn't request.cookies been sent with the fetch request?

Issue 2:
This example is straight from the documentation, and does not work because if dont_merge_cookies is set on the request, then the cookie middleware skips all cookie processing and no cookies are ever set.

Request(url="http://www.example.com",
cookies={'currency': 'USD', 'country': 'UY'},
meta={'dont_merge_cookies': True})

Does not work, however, this does:

Request(url="http://www.example.com",
cookies={'currency': 'USD', 'country': 'UY'})
Issue 1:
Examples bug report

Describe the bug

When using a complete copy of with-ant-design-less sample, styles are loaded after an initial page render when nextjs is built to production

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Go to https://github.com/zeit/next.js/tree/canary/examples/with-ant-design-less

Clone the repository

Install dependencies and build in production mode

Start in production mode

Expected behavior

Styles should be loaded before initial render

Screenshots

System information

OS: macOS

Browser (if applies) chrome

Version of Next.js: latest

Additional context

I tried to deploy using my nextjs app using now and same issue is happening.

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

Expected Behavior

A mailto link should open the email client of the user, regardless if the recipient is present or not.

Current Behavior

When the recipient is missing, isLocal in returns true. Leading to 'Cannot read property replace of null' further down the road.

Steps to Reproduce (for bugs)

mailto:jonas@example.com?subject=Next.js%20rocks works as intended

mailto:?subject=Next.js%20rocks does not work

Context

One of the ways our users can recommend an article to a friend, is to email a link. This is handled by providing a mailto link without recipient, but with information in the subject and body field. Then the users only need to fill in a recipient, and the mail will be sent from his own email client.

This issue is of course avoidable by using a form, but the project owner is currently insisting on keeping this how it is today. So we were hoping this could be fixed.

Your Environment

Tech
Version

next
4.0.3

node
6.11.3

OS
macOS 10.13

browser
Safari, Chrome

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

Expected Behavior

I just want to add the CircularProgress component to my app.

Current Behavior

I have an error : "Element ref was specified as a string (wrapper) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must-have-owner)."

Replacing by another component like LinearProgress, is working fine.

Steps to Reproduce (for bugs)

I have an another error trying to reproduce the bug

https://codesandbox.io/s/pw5klx47v7

Context

Your Environment

Tech
Version

Material-UI
0.20.0

React
16.0.0

browser
Chrome 63.0.3239.84

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

Expected Behavior

At mobile breakpoints, a <Snackbar /> positioned bottom-center should span the whole width of the window.

Current Behavior

At mobile breakpoints, a <Snackbar /> positioned bottom-center takes up at maximum the center 50% of the window. If the message is shorter than ~50% of the window, the snackbar will be smaller.

Steps to Reproduce (for bugs)

This bug is visible in the demo site under the "Positioned" section: https://material-ui-1dab0.firebaseapp.com/demos/snackbars/#positioned

Click "Bottom-Center".

Observe that the Snackbar is centered and not full width.

Click "Bottom-Left".

Observe that the Snackbar is full width.

Context

This bug is especially a problem when there are more than 8 or 9 words in the message, along with an action, and the snackbar looks oddly tall.

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.15

React
v16.0.0

browser
Chrome
Issue 1:
Hi guys.

I'm working in project that's support Angular 2 and I want to upload images directly to API.

How could I use Angular to do similar job ?

I tried using [(ng-model)] with input type file. and I get path look like C:/fakepath/imagename.png.

Issue 2:
I'm submitting a ...

bug report

feature request

Current behavior

In the old router, the new router and the very new router querystring parameters always are accessible as {[k:string]:string}. To pass an array of values via the querystring we have to rely on encoding within the application to serialize and then deserialize the array. We should be able to simply rely on existing URL standard behavior.

Adding to my frustration, there is already a class, URLSearchParams that fully models the querystring but seems unused when retrieving url search params from the router.

https://angular.io/docs/ts/latest/api/http/URLSearchParams-class.html

Expected/desired behavior

When retrieving data parsed from a querystring it should be presented either in a datastructure that supports the standard or in a class that models it properly.

const q: Observable<URLSearchParams> = r.routerState.queryParams;

const q: Observable<{[k:string]:string[]}> = r.routerState.queryParams;

My vote is for the URLSearchParams version of course.
Issue 1:
Bug summary

Import of matplotlib leads to KeyError: 'webagg.port' on Slackware64-current.

Seems related to #21684, #21662

During building matplotlib from pypi.org source-tar.gz, patches corresponding to above commits had been applied, giving this

matplotlibrc:

..

## ***************************************************************************

## * BACKENDS *

## ***************************************************************************

## The default backend. If you omit this parameter, the first working

## backend from the following list is used:

## MacOSX QtAgg Gtk4Agg Gtk3Agg TkAgg WxAgg Agg

## Other choices include:

## QtCairo GTK4Cairo GTK3Cairo TkCairo WxCairo Cairo

## Qt5Agg Qt5Cairo Wx # deprecated.

## PS PDF SVG Template

## You can also deploy your own backend outside of Matplotlib by referring to

## the module name (which must be in the PYTHONPATH) as 'module://my_backend'.

#backend: QtAgg

..

Still, also after commenting out #backend: QtAgg in either

~/.config/matplotlib/matplotlibrc

or in

/usr/lib64/python3.9/site-packages/matplotlib/mpl-data/matplotlibrc

results in this KeyError: 'webagg.port'

Code for reproduction

bash-5.1$ python
>>> import matplotlib

Actual outcome

bash-5.1$ python

Python 3.9.9 (main, Nov 20 2021, 19:41:34)

[GCC 11.2.0] on linux

Type "help", "copyright", "credits" or "license" for more information.

>>> import matplotlib

Traceback (most recent call last):

File "", line 1, in

File "/usr/lib64/python3.9/site-packages/matplotlib/init.py", line 895, in

defaultParams = rcsetup.defaultParams = {

File "/usr/lib64/python3.9/site-packages/matplotlib/init.py", line 898, in

rcParamsDefault[key]),

File "/usr/lib64/python3.9/site-packages/matplotlib/init.py", line 674, in getitem

return dict.getitem(self, key)

KeyError: 'webagg.port'

Expected outcome

no import error, i.e:

bash-5.1$ python

Python 3.9.9 (main, Nov 20 2021, 19:41:34)

[GCC 11.2.0] on linux

Type "help", "copyright", "credits" or "license" for more information.

>>> import matplotlib

>>>

Additional information

With matplotlib-3.4.3 nothing like this.

Operating system

Slackware64-15.0-RC2

Matplotlib Version

3.5.0

Matplotlib Backend

not possible

Python version

3.9.9

Jupyter version

not used

Installation

from source (.tar.gz)

Issue 2:
When setting both the markeredgecolor and the markerfacecolor as a rgba tuple, the transparency of both seems to be set to the one of markerfacecolor. Could this be a bug in matplotlib or am I making a mistake?

Minimal-ish example:

import matplotlib.pyplot as plt

# plot markers with varying alpha values for edge and face colors
alpha_faces = [1.0, 0.3, 0.7, 0.3]
alpha_edges = [1.0, 0.3, 0.3, 1.0]
for n, (af, ae) in enumerate(zip(alpha_faces, alpha_edges)):
plt.plot(n, 0, ms=20, mew=5, marker='s', mfc=(1,0,0,af), mec=(0,0,1,ae))
plt.text(n, 0.01, "$\\alpha$ edge: {}\n$\\alpha$ face {}".format(ae, af),
va='bottom', ha='center')

# a black line to make the transparency clearer
plt.axhline(0, color='k', lw=3, zorder=0)

plt.xlim(-0.5, n+0.5)
plt.show()

Result:

Versions: Ubuntu 12.04, python 2.7.3, matplotlib 1.4.3

I also posted this as a question on SO.
Issue 1:
Steps to reproduce and a minimal demo of the problem

Examine the response object returned by any http.get

Current behavior

res.ok is undefined.

Expected/desired behavior

res.ok, per API doc, " True if the response's status is within 200-299"

Let's implement it:

get ok() { return this.status >= 200 && this.status <= 300; }

Other information

beta.14

Issue 2:
I'm doing this

return this.http.request(request)
.map(res => {
if (!res.ok) {
console.error(res.ok);
console.error(res.status);
}

return res.json();
});

And some calls report status 200 and ok is undefined:
Issue 1:
Even in the official website, checking this on an iphone4 doesn't display properly also.

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

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Context

Your Environment

Tech
Version

Material-UI

React

browser

etc

Issue 2:
The bottom of both controls gets cut off by the navigation bar. Repros on the examples on material-ui.com
Issue 1:
scipy.linalg.eigh

click

Not Found

The requested URL /doc/scipy-1.8.0/html-scipyorg/reference/reference/generated/scipy.linalg.eigh.html was not found on this server.

Issue 2:
Here, for example, is a link to scipy.linalg.inv which is erroneously

https://docs.scipy.org/doc/scipy/reference/reference/generated/scipy.linalg.inv.html#scipy.linalg.inv

instead of

https://docs.scipy.org/doc/scipy/reference/generated/scipy.linalg.inv.html#scipy.linalg.inv
Issue 1:
Very often we have code that uses transferPropsTo, but it's very heavy handed. Often times we just want to add a class or some style based on an option.

Currently if we want to do that it looks something like this:

var joinClasses = require('joinClasses');
// ...
var MyComponent = React.createClass({
render: function() {
return <div className={joinClasses(this.props.className, "something")} />
}
});

While it's not too bad once, we sometimes do this with style as well. And longer classnames. Multiply by a large number and we're in a situation that adds a lot of duplicate work for developers.

So we want to make this better. Some of us talked about a few different ideas here, but we want a combination of explicit and not too much magic. One idea was a magical prop that could be used to pass through.

return <div props={{className: this.props.className}} className="something" />

On the surface this looks great, but then we need to bake knowledge of certain props into composite components (is it a string?) and we're not guaranteed that the component is using a prop in the same way it's used in the DOM.

So what we settled on for the least surprising is in line with some of the special casing React does for some DOM properties. Right now we have booleans which get handled specially. What we're planning is the ability to special case arrays. This allows us to do this:

return <div className={[this.props.className, "something"]} />

We would need to do this for individual properties and not apply the same handling for every property. For example, className would basically need to flatten and then join with a space. style would need to flatten and merge all objects.

This will diverge slightly from our current behavior of just stringifying allmost properties.

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

This is a feature request.

What is the current behavior?

There doesn't appear to be a way to pass context when calling renderer.create

I'm attempting to use snapshot testing in Jest with a component that uses react-intl. If I could provide context, I could create a similar helper function to those for enzyme.

What is the expected behavior?

Be able to provide a context, similar to shallowRenderer.render: #3721

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

I'm using React 15.13.2 and haven't tried any previous versions of React.
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.7.7

Operating System version: macOS Mojave 10.14.6

Java version: 1.8.x

Steps to reproduce this issue

升级 dubbo 到 2.7.7

使用 @DubboReference(version = "*") 注解注入Dubbo服务

服务提供者侧一直保持为2.7.7版本

Expected Result

此时被注入的dubbo服务应该可以使用。

Actual Result

被注入的Dubbo服务不能被使用（经验证消费者侧降级至2.7.6时，服务可用）

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

Operating System version: macos

Java version: 1.8

Steps to reproduce this issue

@service(interfaceClass = xxx.class, timeout = 3000, version = "1.0.7", group="#{config.group}")

What do you expected from the above steps？

register a provider service with the group name given by the spel
Issue 1:
🐛 Bug

When building libtorch with cmake/make directly, the generated TorchConfigVersion.cmake will always show 1.0.0 as the version number

To Reproduce

Steps to reproduce the behavior:

Clone Pytorch

Checkout v1.0.0

Build libtorch with cmake/make

Look at TorchConfigVersion.cmake

git clone https://github.com/pytorch/pytorch.git
cd pytorch
git checkout v1.1.0
git submodule update --init --recursive
mkdir build
cd build
cmake \
-DBUILDING_WITH_TORCH_LIBS=ON \
-DBUILD_BINARY=False \
-DBUILD_CAFFE2_OPS=True \
-DBUILD_PYTHON=False \
-DBUILD_SHARED_LIBS=ON \
-DBUILD_TEST=True \
-DBUILD_TORCH=ON \
-DCAFFE2_STATIC_LINK_CUDA=False \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_CXX_FLAGS= \
-DCMAKE_C_FLAGS= \
-DCMAKE_EXE_LINKER_FLAGS= \
-DCMAKE_SHARED_LINKER_FLAGS= \
-DINSTALL_TEST=True \
-DNCCL_EXTERNAL=True \
-DONNX_ML=False \
-DONNX_NAMESPACE=onnx_torch \
-DTHD_SO_VERSION=1 \
-DUSE_CUDA=True \
-DUSE_DISTRIBUTED=True \
-DUSE_FBGEMM=True \
-DUSE_FFMPEG=False \
-DUSE_LEVELDB=False \
-DUSE_LMDB=False \
-DUSE_MKLDNN=False \
-DUSE_NCCL=False \
-DUSE_NNPACK=True \
-DUSE_NUMPY=True \
-DUSE_OPENCV=False \
-DUSE_QNNPACK=True \
-DUSE_ROCM=False \
-DUSE_SYSTEM_EIGEN_INSTALL=OFF \
-DUSE_SYSTEM_NCCL=False \
-DUSE_TENSORRT=False \
-DCMAKE_PREFIX_PATH=/usr/local \
..
make -j8
cat ./TorchConfigVersion.cmake

Expected behavior

The first line in TorchConfigVersion.cmake should be:

set(PACKAGE_VERSION "1.1.0")

Environment

PyTorch version: 1.1.0

Is debug build: No

CUDA used to build PyTorch: 10.0.130

OS: Ubuntu 16.04.6 LTS

GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609

CMake version: version 3.5.1

Python version: 2.7

Is CUDA available: Yes

CUDA runtime version: 10.0.130

GPU models and configuration:

GPU 0: GeForce GTX 1080 Ti

Nvidia driver version: 410.104

cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.0

Versions of relevant libraries:

[pip] numpy==1.16.4

[pip] torch==1.1.0

[conda] Could not collect

Additional context

This was also tested on an ARM/Linux system with the same spurious results.

Issue 2:
🐛 Bug

CMake version (in TorchConfigVersion.cmake) seems stuck to 1.0.0 in the latest libtorch C++ windows packages (CUDA or not).

This problem may also have affected the previous 1.0.1 packages.

Another big problem for me is that I can't find any more link to download libtorch C++ 1.0.1 packages,

upon which I based all my current developments.

To Reproduce

Download the latest package here:

https://download.pytorch.org/libtorch/cu90/libtorch-win-shared-with-deps-latest.zip

Expected behavior

TorchConfigVersion.cmake with correct version.

Environment

PyTorch Version: 1.1

OS: Windows

How you installed PyTorch: binary package

CUDA/cuDNN version: 9

Thanks for your help,

Albert
Issue 1:
I haven't tried it yet, but does webpack reduce dependencies according to the package version? So if a module with the same version number is included from two different directories, e.g. A/node_modules/underscore@1.x and B/node_modules/underscore@1.x, webpack should include it only once into the bundle.

It would be even better if webpack includes only one version as long as the major version of those two dependencies don't differ. So if myLib1 depends on underscore@1.1.3 and myLib2 depends on underscore@1.0.2, webpack should include only underscore@1.1.3 because - according to semver - it won't break myLib2. Maybe this should be opt-in as it is potential risky.

In any case webpack should log a warning if two versions of the same module are included.

Issue 2:
Hi @sokra

When I try to require('jquery'), which is a jam module installed under web_modules, I always get the following message:

- Serving static content.
- dev-server on port 8081.
> Open http://localhost:8081/ in your browser.

Error: watch ENOENT
at errnoException (fs.js:806:11)
at FSWatcher.start (fs.js:837:11)
at Object.fs.watch (fs.js:861:11)
at module.exports (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:223:23)
at Array.forEach (native)
at EventEmitter.<anonymous> (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:222:19)
at EventEmitter.emit (events.js:123:20)
at writingFinished (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:522:19)
at /Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/webpack.js:379:30
at buildTree (/Users/karlvanrompaey/Documents/apps/experiments/webpack/jam-app/node_modules/webpack/lib/buildDeps.js:103:3)
Hash: 4732db73d220259503822d5a079cf898
Compile Time: 677ms
Chunks: 1
Modules: 6
Modules including duplicates: 6
Modules first chunk: 6

<id> <size> <filename>
dev.bundle.js
0 11 ./_template/entry.js [caching]
1 45 ./app/app.js [caching]
2 259828 ./app/web_modules/jquery/jquery.js [caching]
3 533 (webpack)/buildin/__webpack_amd_define.js [caching]
4 428 (webpack)/buildin/__webpack_amd_require.js [caching]
5 24 (webpack)/buildin/__webpack_options_amd.loader.js!(webpack)/buildin/__webpack_options_amd.loader.js [caching]
webpack: bundle is now VALID.

Jquery seems to be correctly bundled in the app and the server also works, but, I always get an error message related to watch and I am not sure whether it is save to ignore this message !!! For sure the message should not be there :-)

My setup as as follows:

wpt create jam-app
cd jam-app
npm install

Now add jam-dependencies to package.json

"jam": {
"packageDir": "app/web_modules",
"baseUrl": "app",
"dependencies": {
"jquery": "1.8.0",
"bootstrap": "2.1.1-jam.1"
}
},

Then run:

jam install
dev-server.sh

And now the error messages start to appear
Issue 1:
Now that flask 2.0.0 has a py.typed file, the flask types are preferred over the typeshed hints. When running mypy on my code, I now see errors like the following:

app.py:6: error: Module 'flask' does not explicitly export attribute 'Flask'; implicit reexport disabled
app.py:6: error: Module 'flask' does not explicitly export attribute 'render_template'; implicit reexport disabled
app.py:6: error: Module 'flask' does not explicitly export attribute 'request'; implicit reexport disabled
app.py:6: error: Module 'flask' does not explicitly export attribute 'flash'; implicit reexport disabled
app.py:6: error: Module 'flask' does not explicitly export attribute 'send_file'; implicit reexport disabled

In flask/__init__.py there are lines like this:

flask/src/flask/__init__.py

Line 7
in
d575de5

from .app import Flask

However, mypy expects that these reexports should either have an __all__ to explicitly say which variables are being reexported, or to change the import to from .app import Flask as Flask

In typeshed there is an example of how this was done before flask including typing: https://github.com/python/typeshed/blob/6bb1d885c696914e5900329c3d0b6bf2bfefee81/stubs/Flask/flask/__init__.pyi

Environment:

Python version: 3.9

Flask version: 2.0.0

Issue 2:
Python 3.9.5 + mypy 0.812

# magic.py
from jinja2 import Environment

mypy ./magic.py
Success: no issues found in 1 source file

mypy ./magic.py --strict
magic.py:1: error: Module 'jinja2' does not explicitly export attribute 'Environment'; implicit reexport disabled
Found 1 error in 1 file (checked 1 source file)

Thanks 👍