WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I tried to find any kind of documentation on how numpy implements inequality comparison between complex numbers, but I found none.

It seems like __lt__ is implemented as (lhs.real, lhs.imag) < (rhs.real, rhs.imag), or in other words

if lhs.real < rhs.real:
return True
if lhs.real > rhs.real:
return False
return lhs.imag < rhs.imag

Tests that brought me to this conclusion:

>>> numpy.array(9+999j) < numpy.array(10+10j)
True
>>> numpy.array(11+1j) < numpy.array(10+10j)
False
>>> numpy.array(10+1j) < numpy.array(10+10j)
True
>>> numpy.array(10+11j) < numpy.array(10+10j)
False

Is this correct? If so it would at the bare minimum require some formal documentation, as another perfectly valid implementation could have been abs(lhs) < abs(rhs).

Also, arange behaves weirdly and I can't put any sense in it. I would have expected it to be coherent with __lt__, that is

i = start
while (i < stop if step > 0 else i > stop):
yield i
i += step

but it isn't:

>>> numpy.arange(0+1j, 4+1j, 1)
array([], dtype=complex128)
>>> numpy.arange(0+1j, 4+4j, 1)
array([0.+1.j, 1.+1.j, 2.+1.j])
>>> numpy.arange(0, 4j, 1j)
array([], dtype=complex128)
>>> numpy.arange(0, 8+4j, 1)
array([0.+0.j, 1.+0.j, 2.+0.j, 3.+0.j])

Issue 2:
>>> np.arange(0, 10, 2)
array([0, 2, 4, 6, 8])

# as above, cast to complex
>>> np.arange(0 + 0j, 10 + 0j, 2 + 0j)
array([], dtype=complex128) #what?

# bizarre input needed to give expected output
>>> np.arange(0 + 0j, 10 + 10j, 2 + 0j)
# array([ 0.+0.j, 2.+0.j, 4.+0.j, 6.+0.j, 8.+0.j])

For some reason, it deliberately computes len as (c14792d)

c_len = (start - stop) / step
len = min(ceil(c_len.real), ceil(c_len.imag))

which for real-only values, gives 0.

I think a better approach would be to use one of

ceil(abs(c_len)) - has semantics "use the circle centered at start and passing through end" as the end point

ceil(c_len.real) - has semantics "use the projection of end onto the line start + k*step as the endpoint"

above with assert c_len.imag == 0 - requires that end lies on that line, but prone to rounding error

Project step onto the line between start and end, and use that instead

I like the look of 2 and 4
Issue 1:
💻

Would you like to work on a fix?

How are you using Babel?

@babel/cli

Input code

function toLowerCase(){}
low = {toLowerCase}
const v1 = fullStr => {
const v2 = new Map();
const v3 = [1,2,3];
for (let v4 of v3) {
let {
v20: v0,
v4 : v4
} = {
[6]: 5,
get: -12
};
}
return v2;
};
v1(low)

Here is the REPL

Configuration file name

babel.config.json

Configuration

{
"sourceType": "unambiguous",
"presets": ["@babel/preset-env"],
"plugins": [
"@babel/plugin-transform-runtime"
]
}

Current and expected behavior

The input code can be run by node, but when it is converted by babel, there is an error report

Duplicate declaration "v4"

Environment

babel

├── @babel/cli@7.17.0=6

├── @babel/generator@7.17.3

├── @babel/plugin-transform-runtime@7.17.0

├── @babel/preset-env@7.16.11

Node: [v17.3.0]

npm version [8.5.2]

os [ubuntu 20.04]

Possible solution

No response

Additional context

No response

Issue 2:
This input:

export async function foo () {
await bar();
}

export async function bar () {
await foo();
}

produces:

"use strict";

var _interopRequire = function (obj) {
return obj && (obj["default"] || obj);
};

var Bluebird = _interopRequire(require("bluebird"));

var Bluebird = _interopRequire(require("bluebird"));

var foo = exports.foo = Bluebird.coroutine(function* foo() {
yield bar();
});
var bar = exports.bar = Bluebird.coroutine(function* bar() {
yield foo();
});
//# sourceMappingURL=bug.js.map

Note the duplicate require('bluebird')s
Issue 1:
Bug report

I am trying to upgrade my project from 4.x to 5.22 beta and the application stops working with libraryTarget as 'system' , i am loading the module using System.JS dynamically and the exported methods are missing in the 5.X

try {
// eslint-disable-next-line no-undef
const fetchedModule = await window.System.import(modulePath);
setModule(fetchedModule);
} catch (moduleError) {
console.log(moduleError);
setError(true);
}

If the current behavior is a bug, please provide the steps to reproduce.

https://github.com/ajaybeniwal/WebpackFailError

What is the expected behavior?

The application should work without any issues after the upgrade

Other relevant information:

webpack version: "webpack": "5.0.0-beta.22",

Node.js version:

Operating System: Mac

Additional tools:

Issue 2:
Bug report

DISCLAIMER: this issue is a duplicate of #8782. The original issue was closed without (as I can see) any strong reason. I asked to reopen the original issue, but, unfortunately, did not hear back. This bug is stopping us from migrating to webpack 4 from 3 (it works correctly in webpack 3). It will be great if someone can take a look.

What is the current behavior?

I'm importing css files from a third party library (installed in node_modules) into my main entry point. When I run webpack in development mode, the css files are correctly processed and extracted into the separate css file.

However, in production mode the css files are not processed at all.

Webpack output in development mode:

As you can see it has styles.css and styles.index.js

Webpack output in production mode:

As you can see it does not have styles.css and styles.index.js

If the current behavior is a bug, please provide the steps to reproduce.

Please take a look at GitHub repository

The repo has two absolutely identical configs except for mode property. I'm aware that it is not recommended to use split chunks in development mode. The purpose to have dev and prod configs identical is to illustrate that only difference in mode affects which files has been processed by webpack and which not.

Run:

yarn install

yarn build
yarn build:dev

Check the output of those commands. The webpack that run in development has a css files in the output, while the one that was in production does not.

What is the expected behavior?

Webpack should process css files from node_modules that are imported into entry point in development and production modes.

Other relevant information:

webpack version: 4.28.4

Node.js version: 11.6.0

Operating System: macOS Mojave

Additional tools: yarn 1.13.0
Issue 1:
UV offset and repeat (and probably some of the other texture properties) are uniforms which are strangely passed from the texture into the material, which leads to issues where you have to clone textures per material (wasting a ton of memory) if you want per-material offsets/repeats, or roll your own custom shader. It's very inefficient to force people to do this, the best case being if someone wants to tile a texture across a surface based on the size of the object it's applied to, or use a texture as a spritesheet for animations. I can only see the current system as a hindrance with no real advantages, since the likelihood of needing shared UV offsets/Repeats on a "shared" texture is low, and would normally be better served by sharing a material. In anycase updating the uniforms off the texture is weird, since it really has no business being part of the texture, and ends up being confusing to the end user. For example, changing the offset/repeat when more than one map is applied to the material, example diffuse+normalmap, only uses the offset/repeat of the diffuse map, so the value of the normalmaps offset/repeat is completely useless in that context, when it really suggests it should affect the normal map offset/repeat. It's all around confusing.

I'm pretty sure the change is required in the "refreshUniformsCommon" function, but there's probably more to it. There's some changes required in the sprite plugin aswell. This would probably break a lot of peoples projects but it's a pretty big inconsistency in the texture/material API. It might be a better idea to make it an override that's normally null for materials, and when set ignores the values in the textures, just so it doesn't break everyones stuff.

Issue 2:
Description of the problem

Mesh with fewer morph targets be affected by another mesh with more morph targets.

I duplicated the error here by adding a cube with 4 morph targets into Three.js official example webgl_morphtargets. The original example only has one cube with 8 morph targets.

Top 8 input bars change the morphTargetInfluences of gray cube, and bottom 4 bars change the blue cube. Two cubes have different geometries and materials, but adjusting the top 8 input bars affects the blue cube.

Have been troubled by this for days and couldn't figure it out. Any guidance will be much appreciated, thanks!

Three.js version

r80

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

Linux

Android

IOS
Issue 1:
@types/enzyme pulls @types/cheerio that pulls @types/node using triple slash notation that is not compatible with web platform and can't be disabled using types property in tsconfig.json causing react tests using enzyme to fail due to TS issues caused by incompatibility of setTimeout(), setInterval() etc signatures between web and node platform.

This is regression introduced in this commit: 602e045#diff-b6bce2a5160083400070377ac11edbb8

The workaround is to lock dependency on version @types/cheerio@0.22.10.

Authors: @blittle, @wmaurer, @umarniz, @LiJinyao, @chennakrishna8, @AzSiAz, @nwtgck

Issue 2:
Regarding the npm package "mongodb" in Version ~3.2.0 :

Because of incomplete typedescriptions for at least the type , i get typescript compiling errors in my module.

The lacking descriptions for my case are:

Property 'dropAllIndexes' does not exist on type 'Collection<any>'
Property 'ensureIndex' does not exist on type 'Collection<any>'.
Property 'findAndModify' does not exist on type 'Collection<any>'.
Property 'findAndRemove' does not exist on type 'Collection<any>'.

I didnt check all types or properties though. Please complete theses descriptions, so there are no more typescript compiling errors.

Thank you!
Issue 1:
Jörg Heinicke opened SPR-3308 and commented

The current reference at http://www.springframework.org/docs/reference/beans.html#beans-factory-scopes-other-injection-proxies has a duplicate attribute proxy-target-class:

<bean id="userPreferences" class="com.foo.DefaultUserPreferences" scope="session">

<aop:scoped-proxy proxy-target-class="false" proxy-target-class="false"/>

</bean>

This is of course not well-formed XML.

Jörg

Affects: 2.0.3

Issue 2:
Roman Pichlík opened SPR-5574 and commented

Let suppose that there are beans of a given type T and these beans are marked by interface Ordered or annotation Order. It does make really sense to preserve their order according to Ordered/Order marker if they are collected. See following code for illustration.

@Component

@Order(value=1)

public class BusinessServiceA implements BusinessService{}

@Component

@Order(value=2)

public class BusinessServiceB implements BusinessService{}

@Component

public class ServiceRegistry {

@Autowired

public List<BusinessService> services;

}

assertThat(services.get(0).getClass(), is(BusinessServiceA.class));

assertThat(services.get(1).getClass(), is(BusinessServiceB.class));

Issue Links:

#10921 Allow to define autowired collections and array elements order ("is duplicated by")

#20761 Document common use cases for @Order vs @Priority vs @DependsOn

Referenced from: commits 4a9af23

15 votes, 15 watchers
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.5

Steps to reproduce this issue

1.org.apache.dubbo.common.utils.PojoUtils getDefaultValue ,when parameterType is boolean, error happens

Expected Result

bool -> boolean

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: dubbo-spring-boot-starter 2.7.3 (provider&consumer)

Operating System version: win7

Java version: 1.8

Steps to reproduce this issue

when I use redis as register center ,it occurs，when multicast no

no exception，return result like this，Result{returnCode=0, msg='null', data={}}

the timestamp of provider&consumer server is approximate, I set them by myself

4.In most cases,it does not happen

provider service:

@service(interfaceClass = IAccessService.class, version = "1.0.0", group = "authorize")

@component

public class AccessServiceImp implements IAccessService {

@OverRide

public Result checkAccess(Byte clusterId, String userName, String ip) {

Result result = new Result();

return result;

}

config:

dubbo.application.name=dubbo-provider-authorize

dubbo.registry.address=redis://root:bwda@123@192.168.2.34:6379/0

#本地调试地址，有效的多播地址范围是：224.0.0.0-239.255.255.255

#dubbo.registry.address=multicast://224.5.6.8:9090

dubbo.protocol.name=dubbo

dubbo.protocol.port=20880

consumer method:

private IAccessService accessService;

@reference(version="1.0.0",group ="authorize",timeout = 10000,check=false)

Result result = new Result();

result = accessService.checkAccess(cluster.getClusterid(), userName, ip);

if(Constants.PolicyAccess.ACCESS_CODE == result.getReturnCode()){

｝

config:

dubbo.application.name=dubbo-consumer-httpProxy

dubbo.registry.address=redis://root:bwda@123@192.168.2.34:6379/0

#本地调试地址，有效的多播地址范围是：224.0.0.0-239.255.255.255

#dubbo.registry.address=multicast://224.5.6.8:9090?unicast=false
Issue 1:
I use the following blog to use the playwright lib.

my app use login page, using the headless false

when the chromium is opened it ask to provide certificate popup (my user) and when I click on cancel it open the user password screen and the test proceed and pass, any idea how to avoid the certificate popup?

as it sometimes ask for it and sometimes not which a bit tricky

and this is my certificate which should be used on test.

(async () => {
const browser = await chromium.launch({ headless: false });
const page = await browser.newPage();
await page.goto('https://app.com');
await page.fill('input[type="text"]', 'user@test.com');
await page.fill('input[type="password"]', 'Abcd1234!');
page.click('button[id="logOnFormSubmit"]');
}
)();

additional question, in case I want to run this test for 10 users, is there an helpers which can help

or just to wrap it in async function and pass everytime diffrent user

[![enter image description here][2]][2]

Issue 2:
Similarly to puppeteer/puppeteer#540

Currently when navigating to a page that requires client certificates and client certificates are available a popup is shown in Firefox and Chrome which asks to select which certificate to use. It would be beneficial to provide an API to select the correct certificate to use (or use none).
Issue 1:
Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): Windows Terminal (Preview), Version: 0.4.2382.0

Any other software? No

Steps to reproduce

Open Windows Terminal.

Let the computer go into screen-locked status.

Unlocked the computer.

Notice Windows Terminal has been closed.

Proceed to Event Viewer -> Application Log and look for event 1000's showing Desktop Windows Manager and Windows Terminal applications both crashing/faulting.

Source: Application Error / ID: 1000

Faulting application name: WindowsTerminal.exe, version: 1.0.1908.26002, time stamp: 0x5d641823

Faulting module name: ucrtbase.dll, version: 10.0.18362.267, time stamp: 0x080a13f7

Exception code: 0xc0000409

Fault offset: 0x000000000006d33e

Faulting process id: 0x30050

Faulting application start time: 0x01d5695cb9dc2e1e

Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

Report Id: e93be2a0-375b-409c-a1e8-8df49489c81e

Faulting package full name: Microsoft.WindowsTerminal_0.4.2382.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Source: Application Error / ID: 1000

Faulting application name: dwm.exe, version: 10.0.18362.267, time stamp: 0x6468b8f9

Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30

Exception code: 0xc000000d

Fault offset: 0x000000000010f220

Faulting process id: 0x2cec0

Faulting application start time: 0x01d5696eb2d23787

Faulting application path: C:\WINDOWS\System32\dwm.exe

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: cd25779a-d818-438f-b423-2ddebb809148

Faulting package full name:

Faulting package-relative application ID:

Source: Dwminit / ID: 0

The Desktop Window Manager process has exited. (Process exit code: 0x000000ff, Restart count: 2, Primary display device ID: AMD Radeon(TM) Vega 8 Graphics)

Expected behavior

Windows Terminal should stay open until it is closed like any other program.

Actual behavior

Windows Terminal closes/crashes/faults unexpectedly.

Issue 2:
Environment

Not 100%-scale display (high DPI monitor)

Windows build number: Microsoft Windows [Version 10.0.18853.1000]
Windows Terminal version (if applicable): v0.4

Any other software?

Steps to reproduce

Expected behavior

Rectangles should properly surround text inside the text buffer.

Actual behavior

No alignment or sizing - displaying in the top left corner.
Issue 1:
Electron version: 0.37.6

Operating system: Ubuntu 16 64-bit

Hi guys,

Trying to bring Electron app on top & focus it when the user pushes a registered globalShortcut. Nor App.focus() nor BrowserWindow.focus() seems working on Ubuntu. Could only bring it on top by calling:

mainWin.setAlwaysOnTop(true);
mainWin.setAlwaysOnTop(false);

But still no success in focusing it.

Issue 2:
Electron version: the one bundled with Atom 1.7.1, also 0.36.0

Operating system: Linux

The "focus()" call does not actually focus the window, it only raises it. Focus remains in the caller app (terminal, for instance).

No "focus stealing prevention" is used. This can be reproduced on multiple window managers (xfwm, unity).

Steps to reproduce, using Atom (as an example -- works with any other Electron-based app that focuses itself):

open terminal

atom myfile.txt

switch back to terminal

atom myfile.txt

note that Atom raised itself, but the focus is still in terminal.
Issue 1:
In 2.x, when you hide a popover, it is removed from the DOM:

http://jsfiddle.net/moalla/vFDSZ/2/

In 3.x, when you hide a popover, it is not removed from the DOM:

http://jsfiddle.net/wbutler/dCQ3v/

It appears that the 'complete' callback fails to detach the popover due to the hoverState not being changed to 'out' on hide.

Issue 2:
i searched for an already opened issue but did not found any that was reporting this exact problem.

I'm trying to use the destroy method on tooltip (bootstrap v3) but it does not remove the element from the DOM.

Any idea ?

Fiddle : http://jsfiddle.net/52VtD/59/

click on the button to trigger the tooltip destroy method
Issue 1:
I'm not getting stack traces any time a module is loaded with errors. The module compiles fine on its own, but when a call to a method of the module gives an error, the only thing that gets printed is the exception string, but there is no line/stack information.

This is with the latest Julia on Win7 32bits, both using JuliaStudio and from the CLI (not the REPL).

For example, defining a module MyModule with a function double and calling it from another file:

MyModule.jl:

module MyModule

export double

function double(x::Int8)

x*2+a # this gives an error because 'a' is undefined

end

end

Main.jl:

using MyModule

MyModule.double(3)

Executing MyModule.jl gives no error.

Executing Main.jl gives the following error message:

LoadError("path_to_Main.jl/Main.jl",2,ErrorException("a not defined"))

This is just a small sample, but with other types of errors and more complicated code the issue remains.

Issue 2:
With #34287 running ]test BitIntegers:

julia: /home/jeff/src/julia/src/cgutils.cpp:514: unsigned int convert_struct_offset(llvm::Type*, unsigned int): Assertion `SL->getElementOffset(idx) == byte_offset' failed.

signal (6): Aborted
in expression starting at /home/jeff/.julia/packages/BitIntegers/4QmBA/test/runtests.jl:333
gsignal at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
abort at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
unknown function (ip: 0x7f5b6a6b2bf5)
__assert_fail at /lib/x86_64-linux-gnu/libc.so.6 (unknown line)
convert_struct_offset at /home/jeff/src/julia/src/cgutils.cpp:514
convert_struct_offset at /home/jeff/src/julia/src/cgutils.cpp:527 [inlined]
convert_struct_offset at /home/jeff/src/julia/src/cgutils.cpp:520 [inlined]
emit_struct_gep at /home/jeff/src/julia/src/cgutils.cpp:525
emit_getfield_knownidx at /home/jeff/src/julia/src/cgutils.cpp:1672
emit_builtin_call at /home/jeff/src/julia/src/codegen.cpp:2872
Issue 1:
Hi,

I am using DBSCAN to cluster some points of mine and I run into some possibly memory related issues. If I try to cluster something in the ballpark of 50k two-dimensional points with the haversine metric, I am running out of memory on a machine with 16GB, and I am not sure that this is supposed to happen. I mean, 50k isn't that many points, or am I wrong?

For the last two times I tried I also got this line repeated over and over again:

File "sklearn/cluster/_dbscan_inner.pyx", line 14, in sklearn.cluster._dbscan_inner.push (sklearn/cluster/_dbscan_inner.cpp:1243)

Followed by

MemoryError: std::bad_alloc

I call DBSCAN like this:

eps = 50 / (1000*6378.137)
db = DBSCAN(eps=eps, min_samples=3, algorithm='ball_tree', metric='haversine').fit(x)

I am on Python 2.7 and scikit-learn 0.16.

Issue 2:
Currently check_estimator requires that if binary classification is supported, multiclass classification must also be supported. Perhaps this is not a sensible constraint for contrib projects (see scikit-learn-contrib/scikit-learn-contrib#7).

This may be an appropriate subject for tags (#6599). See also #6715.
Issue 1:
Create a browser window with the resizable: false attribute in options - on OSX this acts as expected and is not able to be resized, on Linux you can still resize.

Issue 2:
Code like this does not work on ubuntu 14.04, the window size can be customized by dragging the edge.

// Create the browser window.
mainWindow = new BrowserWindow({
width: 800,
height: 480,
resizable: false
});

Note:We are using node.js v0.11.14 and atom-shell 0.19.5.