WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
scipy.linalg.eigvalsh() give a message

Intel MKL ERROR: Parameter 12 was incorrect on entry to ZHBRDB.

and return wrong eigenvalues. When the input matrix is a real Hermitian matrix or a complex Hermitian with dimension less than 2000, this function always give the right answer as np.linalg.eigvalsh does, but if the matrix is a complex matrix with dimension larger than 2000, this function always give the above message and wrong eigenvalues. The returned eigenvalues are all zeros but the last one.

Reproducing code example:

import scipy.linalg as la
import numpy as np

#row = col = 1999
row = col = 2000
shape = (row, col)

# A real matrix
#M = np.random.random(size=shape)

# A complex matrix
M = np.random.random(size=shape) + np.random.random(size=shape) * 1j

# Construct an Hermitian matrix
M += M.T.conj()

vals_numpy = np.linalg.eigvalsh(M)
vals_scipy = la.eigvalsh(M)
print(vals_scipy)
assert np.allclose(vals_numpy, vals_scipy)

Error message:

Intel MKL ERROR: Parameter 12 was incorrect on entry to ZHBRDB.
[ 0. 0. 0. ... 0. 0. 48000.]
Traceback (most recent call last):
File ".\test.py", line 20, in <module>
assert np.allclose(vals_numpy, vals_scipy)
AssertionError

Scipy/Numpy/Python version information:

scipy.__version__: '1.0.0'
numpy.__version: '1.14.2'
sys.version_info: sys.version_info(major=3, minor=6, micro=4, releaselevel='final', serial=0)
Python 3.6.4 :: Anaconda custom (64-bit)

Issue 2:
scipy.linalg.eigvalsh() throws ValueError() for large matrices. The bug appears for arbitrary matrices.

However, it also shows up in trivial examples, such as a large identity matrix, and large diagonal matrices with random coefficients in [0,1].

Reproducing code example:

import numpy as np
import scipy.linalg as la

H=np.eye(6470)
#np.random.seed(0)
#H=np.diag(np.random.uniform(size=6470))
E=la.eigvalsh(H)

Error message:

Traceback (most recent call last):
File "example0.py", line 7, in <module>
E=la.eigvalsh(H)
File "/Users/mbukov/anaconda3/lib/python3.6/site-packages/scipy/linalg/decomp.py", line 734, in eigvalsh
check_finite=check_finite)
File "/Users/mbukov/anaconda3/lib/python3.6/site-packages/scipy/linalg/decomp.py", line 384, in eigh
iu=a1.shape[0], overwrite_a=overwrite_a)
ValueError: On entry to DSBRDB parameter number 12 had an illegal value

Scipy/Numpy/Python version information:

0.19.1 1.13.0 sys.version_info(major=3, minor=6, micro=2, releaselevel='final', serial=0)
Issue 1:
When I use npm to install bootstrap package, I want to be able to use require.resolve('bootstrap') to get exact location (since it's not necessarily in node_modules of my package) on filesystem. Bootstrap package.json misses main section and require.resolve('bootstrap') doesn't work.

I'm not creating pull request because I'm not sure about what file main section should point to. Either dist/js/bootstrap.js or specially created empty file like dist/index.js or even dist/css/bootstrap.css. Probably something else, but something enough for require.resolve('bootstrap') to work.

Thanks.

Issue 2:
Great work on getting bootstrap onto npmjs.org.

Maybe I am missing something but there is no main property defined in package.json.

Currently I have to do this

require('bootstrap/dist/js/bootstrap');

but I would prefer to do this,

require('bootstrap');

Also, I currently have to do the following to meet the jquery dependency before requiring bootstrap.

window.jQuery = $;
Issue 1:
Bug report

When using React version 16.6.0, my app suddenly crashed with the error "Cannot read property replace of null". The exception happens when React tries to remove the string "topsecret-" from fiber.name. I tried to revert back to 16.5.2 to confirm the version where it happens, and it does indeed not happen in 16.5.2.

I'm not sure about steps to reproduce it, I've been using React 16.6.0 for a few days in this project without issues until now. Here's a screenshot of the exception and the file it happens in, along with the stack. Seems like a straightforward fix, so I hope a reproduction example isn't needed in this case.

Issue 2:
Ran create-react-app react-test then npm start on the fresh project with no changes and I get the following error when using react@16.6.0 and react-dom@16.6.0:

Uncaught TypeError: Cannot read property 'displayName' of null
at getDisplayName (backend.js:9159)
at getDataFiber (backend.js:9888)
at enqueueMount (backend.js:10158)
at mountFiber (backend.js:10246)
at backend.js:10306
at Set.forEach (<anonymous>)
at Object.walkTree (backend.js:10304)
at backend.js:8534
at <anonymous>:52:32
at Array.map (<anonymous>)
at Object.emit (<anonymous>:51:66)
at setupBackend (backend.js:8621)
at module.exports (backend.js:8567)
at Agent.<anonymous> (backend.js:116)
at Agent.g (backend.js:981)
at Agent.EventEmitter.emit (backend.js:894)
at backend.js:302
at backend.js:7619
at Array.forEach (<anonymous>)
at backend.js:7618
at Array.forEach (<anonymous>)
at Bridge._handleMessage (backend.js:7611)
at listener (backend.js:92)

If I rollback the version to react@16.5.2 and react-dom@16.5.2 then I get no errors. I believe I've tracked down the issue to

react-devtools/backend/getDisplayName.js

Line 27
in
faa4b63

if (typeof type.displayName === 'string') {

but not sure where to go from here.

I've also tried this on an existing project with the same results. Any help would be appreciated. Thanks in advance!
Issue 1:
Which version of ShardingSphere did you use?

shardingsphere-jdbc-core-spring-boot-starter：5.0.0-beta

mybatis-plus-boot-starter：3.4.3.1

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

only use ShardingSphere-JDBC

Expected behavior

The SQL exception information can be obtained.

Actual behavior

Failed to obtain the SQL exception information.

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

The database field 'status' set to mandatory.

use mybatis-plus provide the save function to save the entity not set status value.

can print insert log without exception，but don't success to save the data.

Issue 2:
Bug Report

Which version of ShardingSphere did you use?

5.1.0

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

transaction rollback(proxy-db) when connection ( application-proxy) is closed

Actual behavior

transaction no rollback(proxy-db) when connection ( application-proxy) is closed

Reason analyze (If you can)

When the above figure is executed to step 4-6, the disconnection of the upstream connection triggers the channelInactive method of Netty. At this time, the resources in the JDBCBackendConnection are still empty. Because step 7 has not been started, the subsequent step 7 is executed after the resources are cleaned up, and the subsequent connection will remain there.

JDBCBackendConnection Whether to add a new status to control the addition of connections？
Issue 1:
I'd like to have a type for a function which takes in zero or more parameters, and then use the type for the parameters, e.g.

// Note: the syntax below of course doesn't do what I'm looking for, something like (params: ...args: T) would be closer
let f = (params: T) => (params2: T) => 0;

// these should be legal:
f(5)(3);
f("foo")("bar");
f(5, "foo")(3, "bar");

// these should be illegal
f(5)("bar");
f("foo")(3);
f(5, 3)("foo", "bar");

This is useful in e.g. typing the spread function here:

DefinitelyTyped/DefinitelyTyped@3eb67c9

I need to use the ...args: any[], which is not quite what I'm looking for.

In essence, the type I want to use is [A?, B?, C?, ...], or maybe something like Params<T> if such an interface would exist.

Issue 2:
We can kind of already do this for functions by defining several overloads, but there is no corresponding mechanism for overloaded classes or interfaces. A typical use case would be defining a registry for callbacks which accept a number of parameters. Something like the following with loosely proposed variadic type syntax:

interface IDispatcher<...ArgTypes> {

add(callback: (...args: ArgTypes) => void): void {
// store the callback
}

dispatch(...args: ArgTypes): void {
// invoke the callbacks
}
}

function createDispatcher<...ArgTypes>(): IDispatcher<...ArgTypes> {
// create a concrete instance
}

var d = createDispatcher<number, string>();
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1528 on 2010-06-29 by @sandrotosi, assigned to unknown.

Hello,

I'm here forwarding the bug filed in the Debian BTS at http://bugs.debian.org/564774 .

The bug refers to 1.3.0 but I'm able to replicate it with 1.4.1 too. The key part is (for the rest, please read the link above):

>>> import numpy as np
>>> np.savez('test.npz', N.ones((10000, 1000)))
>>> ll -h *.npz
-rw-r--r-- 1 michael michael 77M 2010-01-11 15:52 test.npz
>>> !gzip test.npz
>>> ll -h test*.gz
-rw-r--r-- 1 michael michael 114K 2010-01-11 15:52 test.npz.gz
^^^^

Thanks for your support,

Sandro

Issue 2:
Original ticket http://projects.scipy.org/numpy/ticket/1527 on 2010-06-29 by @sandrotosi, assigned to unknown.

Hello,

I'm here forwarding the bug filed in the Debian BTS at http://bugs.debian.org/564774 .

The bug refers to 1.3.0 but I'm able to replicate it with 1.4.1 too. The key part is (for the rest, please read the link above):

>>> import numpy as np
>>> np.savez('test.npz', N.ones((10000, 1000)))
>>> ll -h *.npz
-rw-r--r-- 1 michael michael 77M 2010-01-11 15:52 test.npz
>>> !gzip test.npz
>>> ll -h test*.gz
-rw-r--r-- 1 michael michael 114K 2010-01-11 15:52 test.npz.gz
^^^^

Thanks for your support,

Sandro
Issue 1:
feature

What is the current behavior?

On the new developer tool you are unable to see what property type the value. You used to be able to see if the value was a string or int because of the quotation marks (for example id: "1" (string) or id: 1 (int)). Both string and int are shown without quotes.

What is the expected behavior?

I want to see if the value inside the prop or state is an string or integer by using quotation marks on the value.

id: "1"

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

I'm using version:

4.0.5 (8/19/2019)

Did this work in previous versions of React?

Yes, 3.*

Issue 2:
Follow up to a discussion thread on #294 and a Messenger chat with @gaearon.

The current UI for editing props/state/hooks values has a couple of shortcomings:

strings/numeric values are sometimes of an unclear type. (DevTools uses the correct <input type> but this is subtle. Showing e.g. quotation marks around strings could be more helpful.

null initial values can only become strings at the moment. (DevTools does not attempt to parse numeric or boolean values and change the input type. If it did, we would probably also need to enable a way for you to opt back out of that input type somehow in case it was incorrect.)

fields that maybe support multiple types (e.g. string | number) are locked into a single type (whichever type they happen to be initially).

Additional quirks that might be worth ironing out:

Non-editable strings are currently wrapped in quotation marks but editable ones aren't.

Originally reported via bvaughn/react-devtools-experimental#321
Issue 1:
Environment

Windows 10 188995
Latest nightly terminal build as-of 10/6

Steps to reproduce

Install PowerShell Core as a .NET Core global tool. dotnet tool install -g powershell. Confirm it works when you use pwsh.exe.

Create a new PowerShell Core profile and set "source": to "Windows.Terminal.PowershellCore". And open a new shell. Doesn't work. Commenting out source and using "commandLine": "pwsh.exe" works, as it is in the path.

Expected behavior

PowerShell Core should load.

Actual behavior

Profile is skipped or doesn't load.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.239]
Windows Terminal version : 0.2.1831

Any other software? Nope.

Steps to reproduce

Make tabs more then current terminal width. (tab name should be over the terminal topbar.)

Scroll topbar Using Mouse Wheel.

Tab does not appear. but topbar size has increased.

Expected behavior

topbar size has increase, and Tab have to appear.

Actual behavior

topbar size has increased, but Tab does not appear.

if close one tab, or increase window size. now appear hide tab.

On Two tab added, Topbar size has increased, but Tab does not appear.

increase window size, then Tab apeear.
Issue 1:
Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.6.2951.0

Epic

Scrollback handling should be just like in VTE because that's the best (ahem ahem) 🤣

Steps to reproduce 1

ssh to a Linux box, and execute these:

seq -f 'normal %.f' 100
echo -ne '\e[?1049h' # switch to alt screen
seq -f 'alt %.f' 100
echo -ne '\e[?1049l' # switch back to normal screen

scroll back and examine the contents

Expected behavior 1

Outputs of these two seqs shouldn't interleave

Actual behavior 1

Output consists of normal 1 to normal 74 (exact number depends on the window height), followed by alt 1 to alt 74, and finally normal 75 to normal 100. (alt 75 onwards are gone.)

Steps to reproduce 2

ssh to a Linux box.

produce a few pages of output

start a fullscreen app such as mc

resize the window in various ways (maybe even back and forth to smaller and then bigger)

quit mc

examine the output, including the scrollback

Expected behavior 2

This should look okay (see below).

Actual behavior 2

The contents seem quite garbled. Most of the time you'll see remains of mc's user interface in the scrollback buffer; sometimes even on the normal screen (this latter is harder to reproduce, and perhaps only happens with solid background colors).

VTE rocks

The way this works amazingly in gnome-terminal is:

The alternate screen is pretty much only used by fullscreen apps that control the entire UI and repaint on window resize. Therefore it's unrelated to the normal screen and the scrollback. Data never travels between the (normal screen + scrollback) combo and the alternate screen. The scrollback buffer belongs to the normal screen only. Everything scrolled out from the alternate screen is lost for good.

On resize, the (normal screen + scrollback) is resized as a single unit, for the resizing operation it doesn't matter where the boundary is.

The (normal screen + scrollback) combo is resized the same way, regardless of whether it's the active one or the alternate screen is shown. Stress-test this: produce output on the normal screen, switch to the alternate one (e.g. mc), resize, quit mc. The normal screen's contents will be updated to the new width just as if you haven't switched to the alternate screen.

There's plenty of further tiny details to this story, e.g. how to vertically position the contents, some of which are documented in VTE's doc/rewrap.txt.

Of course there's no specification anywhere that all this has to behave like this. It's just what I believe makes the most sense. Obviously my opinion is quite biased since this was my first big contribution to VTE. :) Luckily I only had to do the rewrapping; the separation of the (normal screen + scrollback) vs. alternate screen was already as desired.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version : 0.4.2382.0
Input method: the system defaut microsoft pinyin input method.

Steps to reproduce

always.

Expected behavior

the input method can switch to chinese mode, and can type chinese characters.

Actual behavior

the input method is always in english mode, and cannot type chinese characters .
Issue 1:
This came up while trying to de-duplicate some DataFrame vs Series arithmetic logic in core.ops.

Issue 2:
I often work with pandas using big dataframes and series with multi-index or multi-column and I use the EMACS shell.

Often when I write df.index the output is so big that almost make my computer crash (and it is a powerful pc).

As when you output a dataframe df the output is truncated to the first and last n columns, also indices and columns should be truncated when printed to screen.
Issue 1:
Bug report

Describe the bug

Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:

You might have mismatching versions of React and the renderer (such as React DOM)

You might be breaking the Rules of Hooks

You might have more than one copy of React in the same app

See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem.

To Reproduce

Details

So the error points on this code

static async getInitialProps (ctx) {
const sheet = new ServerStyleSheet()
const originalRenderPage = ctx.renderPage
const {
req: { locale, localeDataScript }
} = ctx
try {
ctx.renderPage = () =>
originalRenderPage({
enhanceApp: App => props => sheet.collectStyles(<App {...props} />)
})

const initialProps = await Document.getInitialProps(ctx)
return {
...initialProps,
userAgent: ctx.req.headers['user-agent'],
helmet: Helmet.renderStatic(),
locale,
localeDataScript,
styles: (
<>
{initialProps.styles}
{sheet.getStyleElement()}
</>
)
}
} finally {
sheet.seal()
}
}

Screenshots

Additional context

I suspect that it treats the ctx.renderPage = () => as a react hooks.

Issue 2:
We are working on a Very large project with several dependencies, when building the project we get a FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory.

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

Expected Behavior

When running yarn build I should get a working production bundle

Current Behavior

When running yarn build I get FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory.

After several hours of debugging I found out that the origin of this problem comes from https://github.com/zeit/next.js/blob/canary/server/build/index.js#L72

more exactly the JSON.stringify function, given that our stats file is 260MB, node can't handle it.

I was able to patch it using streams and make it work ok, I'll make a PR for this tomorrow.

Your Environment

Tech
Version

next
4.1.4

node
8.9.1

OS
Ubuntu 16.04

browser
N/A
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: *

Operating System version: *

Java version: *

Steps to reproduce this issue

Run it in different system having multiple network adapters.

Expected Result

Stably successful.

Actual Result

Fail sometimes.

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

Operating System version: win64

Java version: 1.8

Steps to reproduce this issue

ConsistentHashSelector(List<Invoker<T>> invokers, String methodName, int identityHashCode) {
this.virtualInvokers = new TreeMap<Long, Invoker<T>>();
this.identityHashCode = identityHashCode;
URL url = invokers.get(0).getUrl();
this.replicaNumber = url.getMethodParameter(methodName, HASH_NODES, 160);
String[] index = COMMA_SPLIT_PATTERN.split(url.getMethodParameter(methodName, HASH_ARGUMENTS, "0"));
argumentIndex = new int[index.length];
for (int i = 0; i < index.length; i++) {
argumentIndex[i] = Integer.parseInt(index[i]);
}
for (Invoker<T> invoker : invokers) {
String address = invoker.getUrl().getAddress();
for (int i = 0; i < replicaNumber / 4; i++) {
//这里生成的16字节摘要为啥要分在四个节点
byte[] digest = md5(address + i);
for (int h = 0; h < 4; h++) {
long m = hash(digest, h);
virtualInvokers.put(m, invoker);
}
}
}
}
Issue 1:
I was doing some testing using unsigned and signed integers with NumPy 1.20.3, and found out that when you multiply them with each other, it results in a 64-bit float.

Same goes for addition/subtraction.

As far as I know, this was not the case for earlier NumPy versions (as currently many parts of my code no longer work that previously worked just fine with this).

To me, it sounds a bit strange that multiplying two integers with each other results in a float.

Reproducing code example:

import numpy as np
print(type(np.uint(1)*1))
>>> <class 'numpy.float64'>

NumPy/Python version information:

Python: 3.8.8

NumPy: 1.20.3

Issue 2:
Describe the issue:

Expected Behavior:

I expect to create a python Fraction from numpy integer types with no loss of precision

Actual Behavior:

Types are coerced to numpy.float64 and precision is lost

Reproducible code example:

import numpy as np
from fractions import Fraction

nums = np.array([1])
denoms = np.array([18446744073709550592], dtype='uint64')
f = Fraction(nums[0], denoms[0]) # denom has been rounded, is now a float
print(f) # 1.0/1.8446744073709552e+19
print(type(f.denominator)) # <class 'numpy.float64'>

Error message:

No response

NumPy/Python version information:

Numpy: 1.21.2

Python: 3.7.9 (default, Aug 31 2020, 12:42:55) [GCC 7.3.0]

OS: Debian GNU/Linux 10 (buster)

Other information that may be helpful:

I discovered this behavior while creating fractions from parallel arrays representing the numerators and denominators of fractions. This loss of precision is problematic because the float is rounded up so that it is out of range for uint64, despite the original value being valid. In my case I have a workaround, as converting the values to python int before inputting them to the Fraction constructor prevents this issue. However, I wanted to let you know because it is unexpected that an operation with two numpy integer types produced a value with floating point types.

I briefly looked into the Fractions constructor and I discovered that this behavior comes from lines 175-180 of fractions.py:

elif (isinstance(numerator, numbers.Rational) and
isinstance(denominator, numbers.Rational)):
numerator, denominator = (
numerator.numerator * denominator.denominator,
denominator.numerator * numerator.denominator
)

numpy.uint64 is an instance of numbers.Rational:

>>> import numpy as np
>>> import numbers
>>> denoms = np.array([18446744073709550592], dtype='uint64')
>>> isinstance(denoms[0], numbers.Rational)
True

Inspecting the reproducible snippet above with pdb reveals that the multiplication on lines 178-179 of fractions.py is the moment when the type is changed.

Thank you for your time (:
Issue 1:
Bug report

I want to replace all the module name like node:fs to fs, so I set resolve.alias:

resolve: {
alias: {
'node:': ''
},
},

What is the current behavior?

error message:

configuration.resolve.alias['node:'] should be a non-empty string

What is the expected behavior?

No validate configuration failed error.

Other relevant information:

webpack version: 5.65.0

Node.js version: 16.13.1

Operating System: MacOS 12.1

Issue 2:
Hey there! I have a question.

I have two npm-packages: sub and common. I'm writing my app using this packages.

sub includes common as dependency.

import common from 'common';

// some code here

my app

import sub from 'sub';
import common from 'common';

// some code here

The final bundle contains two copies of common package. The first copy is for my app, and the second one - for package sub.

final bundle

...
// my app
({ /* some deps */ }) => {
var sub = __webpack_require__(1);
var common = __webpack_require__(2);
}
// end of my app

...
// sub
({ /* some deps */ }) => {
var common = __webpack_require__(3);
// ^ not the same line in app (in app uses 2)
}
// end of sub
...

// module 2
({ /* some deps */ }) => {
// code of common
}
// end module 2
...

// module 3
({ /* some deps */ }) => {
// code of common
}
// end module 3

Could I combine common in one module to avoid duplication? Thanks!