WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Describe the feature and motivation

There is no way currently, within OpenCV, to list existing devices to let the user select them. This means that they must be obtained in a different manner (either by re-implementing manually, or using a third-party library), which may not match OpenCV's indexes and may not work on all platforms.

There is a workaround to try every indexes individually, but this has 4 main issues:

Some VideoCapture devices will freeze if opened and closed quickly or if it was already in use.

The popular SD capture card GV-USB2 (confirmed myself)

I've had reports that an AverMedia capture card is affected as well

Some devices take a long time to boot, making this technique quite slow (like my Logitech c920 webcam)

The total amount of devices is unknown, and usable devices may not be sequential. So we have to guess how many devices maximum the user may have, trying to balance between time spent or risking missing some

Even if you get all the IDs after this, you don't have access to the names to present to the user. (see #23537)

Additional context

No response

Issue 2:
Transferred from http://code.opencv.org/issues/935

|| Rune Espeseth on 2011-03-08 10:27
|| Priority: Normal
|| Affected: None
|| Category: highgui-camera
|| Tracker: Feature
|| Difficulty:
|| PR:
|| Platform: None / None

Add API to enumerate cameras

OpenCV should have an API to enumerate cameras. Without it, writing programs that support non-fixed hardware is not possible.

The point of this API is to retrieve information about the cameras attached to the system:
- NumberOf
- Name of each camera (can be used for user-selection in a GUI)
- Resolution of each camera
- other properties.

It will then be possible to write programs (f.i. surveillance software) that support 1 to any number of cameras instead of requiring a given number of cameras.

History

Alexander Shishkov on 2012-02-12 21:12

- Description changed from [[OpenCV]] should have an API to enumerate
cameras. Without it, writing progr... to OpenCV should have an API
to enumerate cameras. Without it, writing programs ... More

Alexander Reshetnikov on 2012-04-25 14:27

- Priority changed from High to Normal
- Assignee set to Vadim Pisarevsky

Andrey Kamaev on 2012-08-16 15:23

- Category changed from highgui-images to highgui-camera

Neil Jansen on 2015-02-03 04:59

Hi, I know this issue has been open for a while, but is there any chance that it could be fixed easily? It would be very helpful for those of us using machine vision with more than 1 camera. I am even willing to place a cash bounty on this bug if necessary (tried to do it at bountysource.com, but they don't support the ChiliProject bug tracking platform that OpenCV uses...). Thanks!

Steven Puttemans on 2015-02-03 09:29

Depending on which camera type you are using this already exists. The recently adapted PvAPI interface of Allied Vision Technology cameras does exactly this. No idea if other do it or not.
Issue 1:
Please state the information for your system

OpenCV version: 3.1

Host OS: Ubuntu 16.04 LTS

Nvidia-367 with CUDA 7.5

-Compiler & CMake: GCC 5.3 & CMake 3.5

In which part of the OpenCV library you got the issue?

Examples:

core, cuda

Error generated using gcc & cmake in 16.04 LTS

Error generated:

/usr/include/string.h: In function ‘void* mempcpy_inline(void, const void, size_t)’:

/usr/include/string.h:652:42: error: ‘memcpy’ was not declared in this scope

return (char *) memcpy (__dest, __src, __n) + __n;

Using the methods in [https://github.com/BVLC/caffe/issues/4046] by adding

set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -D_FORCE_INLINES")

to the top of the CMakeLists.txt, everything compiled and worked fine

Issue 2:
System information (version)

OpenCV => 3.4

Operating System / Platform => macOS High Sierra

Compiler => Clang (mac's default gcc)

Detailed description

I think I read somewhere clang wasn't supported, but I can't find it again so hopefully I was wrong. I compiled it from source from the 3.4 tag, there were no errors.

I'm running opencv as a nodejs addon in c++, it is running on a separate thread and every once in a while (one or two loops), when it gets to the detectMultiScale function it crashes.

When I run it without the node addon api library as a separate program (still in a separate thread) it doesn't crash, it just keeps the capture loop going as it is supposed to. But because it crashes on an opencv function I think it makes sense to put the issue here.

Piece of code where is crashes:

// Gray has 1 channel, 2 dims, cols = 1280, rows = 720
// found_bodies is an empty std::vector<Rect>
body_cascade.detectMultiScale(gray, found_bodies, 1.01, 4, 0, cv::Size());

Error I get after a while:

libc++abi.dylib: terminating with uncaught exception of type cv::Exception: OpenCV(3.4.4-dev)
/usr/local/include/opencv2/core/mat.inl.hpp:1179: error: (-215:Assertion failed) (unsigned)(i1 *
DataType<_Tp>::channels) < (unsigned)(size.p[1] * channels()) in function 'at'

Steps to reproduce

I'm not sure how you can help me with this as I'm not allowed to share this code. :/

It's basically this code here (below), with a normal opencv capture loop from a video, running in a separate thread and doing detectMultiScale every loop.

Thank you in advance, anything you need, just ask.
Issue 1:
Do you want to request a feature or report a bug?

possible bug

I have already asked on StackOverflow and it seems as if this behavior would be quite common but there have been no possible solutions.

What is the current behavior?

I have a large webpack build that almost hangs at 91% on an "additional asset processing" step.

To complete processing take about 8 minutes but the step "additional asset processing" consumes at lwat half of the time.

Webpack does not give me a lot more information and I would like to better understand if this is "normal", a bug or what can be done to eventually optimize my build?

56205ms building modules
31ms sealing
0ms optimizing
0ms basic module optimization
15ms module optimization
0ms advanced module optimization
0ms basic chunk optimization
0ms chunk optimization
16ms advanced chunk optimization
14487ms building modules
0ms module and chunk tree optimization
31ms module reviving
0ms module order optimization
16ms module id optimization
0ms chunk reviving
16ms chunk order optimization
31ms chunk id optimization
140ms hashing
0ms module assets processing
265ms chunk assets processing
0ms additional chunk assets processing
0ms recording
206740ms additional asset processing
79781ms chunk asset optimization
1ms asset optimization
906ms emitting

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

What is the expected behavior?

faster or more information on what is currently being done

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

node: 6.10.0

webpack: 2.3.1

OS: Windows 7 x64

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

Probably it's bug...

What is the current behavior?

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

I build a simple example with one 'import' = angular library.

After update to 2.3.1 version I noticed that build is too long.

What is the expected behavior?

The same project with 2.2.1 webpack.

If this is a feature request, what is motivation or use case for changing the behavior?

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Issue 1:
The babel-node help says like node's help :

Usage: babel-node [options] [ -e script | script.js ] [arguments]

With a myScript.js containing only "console.log(process.argv)", on the following call, -p is taken as a babel-node option instead of a script argument :

$ babel-node myScript.js -p abc
ReferenceError: abc is not defined

Where node outputs :

$ node myScript.js -p abc
[ 'node',
'/home/fabrice.marsaud/Documents/myScript.js',
'-p',
'abc' ]

Issue 2:
I have a script which responds to the --debug flag.

babel-node main.js --debug

Right now, it is getting handled by 'babel-node' and not being passed to main.js

I think babel-node should only handle arguments that come before the script.
Issue 1:
Summary of the new feature

Add PowerToy for customization of context menu. Tool should enable to group, hide or move position of app's shortcut.

CURRENT SITUATION

SUGGESTION

Issue 2:
Easily manage the right click actions to edit, open at. Right now this is all over the place, different applications add right-click extensions and it is a mess. You can somehow change the default open application. But it would be great to be able to manage other actions to for example edit e.g Tiff file, HTML file, compile, etc.
Issue 1:
The exact engine we use needs further discussion. Probably we don't want to use yarr because it requires the nitro jit, which is a big dependency and could be undesirable for various reasons. Ideally, we would have a nice syntax extension that precompiles the regexes (in addition to runtime compilation options).

Issue 2:
This program seems correct to me:

fn main(args: [str]) {
let one = fn@() -> uint {
enum r { a };
ret a as uint;
};
let two = fn@() -> uint {
enum r { a };
ret a as uint;
};
one(); two();
}

If I compile it with rust 0d5d2e5 I get:

herugrim::~/code/limerick $ RUST_LOG=rustc=0,::rt::backtrace rustc enumbug.rs
enumbug.rs:2:0: 12:1 warning: unused variable args
enumbug.rs:2 fn main(args: [str]) {
enumbug.rs:3 let one = fn@() -> uint {
enumbug.rs:4 enum r { a };
enumbug.rs:5 ret a as uint;
enumbug.rs:6 };
enumbug.rs:7 let two = fn@() -> uint {
...
error: internal compiler error duplicate LLVM symbol: _ZN4main1r1a7discrim17_7bb11dc7a9aa7ee4E
rust: upcall fail 'explicit failure', ../src/rustc/driver/diagnostic.rs:78
rust: upcall fail 'explicit failure', ../src/rustc/driver/rustc.rs:182
rust: domain main @0x7fd822818600 root task failed

This problem only seems to happen with boxed closures (fn@)
Issue 1:
This is about the "documentation inaccuracy" and the discussion on "scale_C".

I really want to fix this before the release but I don't have much time atm.

As far as I understood, at the moment we can agree that having "C" as parameter with "scale_C=True"

is not perfect, as this doesn't agree with how "C" is used in the literature / other software.

I am not sure if there was a solution that we could agree on.

I would like to have votes pro/con having a "duplicate" parameter C (which has scale_C=False semantics) and alpha, which behaves as in the other linear models. Another option would be to have just the "alpha" parameter.

Any other suggestions are welcome.

I created this script: https://gist.github.com/2354823 to understand the effect of "scale_C".

Not sure if that helps.

Results look like this:

These are grid searches for C=2**k with "shuffle & split" and different fractions of training data.

In principle the results should just be shifted by a factor of "n_samples". Guess that is not a power of two so that makes it a bit different. Not sure I like one more than the other.

Issue 2:
problem

I am trying to get the nmf_missing branch to compile without success, as per this suggestion.

The compiler error:

On branch nmf_missing after issuing make at the command line it build largely fine until the following error (The first one I know of, although several warnings):

error: Command "x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat -Werror=format-security -fPIC -I/usr/local/lib/python2.7/dist-packages/numpy/core/include -I/usr/local/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 -c sklearn/neighbors/quad_tree.c -o build/temp.linux-x86_64-2.7/sklearn/neighbors/quad_tree.o -MMD -MF build/temp.linux-x86_64-2.7/sklearn/neighbors/quad_tree.o.d" failed with exit status 1
Makefile:24: recipe for target 'inplace' failed

How I think this can be solved(?)

It seems to come from trying to compile the following line in quad_tree.c (3582) printf(__pyx_k_QuadTree_found_a_duplicate);. I have tried commenting out this line but whenever I type make it reverts the change. Hence I have tried tracking down what is producing either this file, or whatever is producing the compiler flags -Wformat -Werror=format-security which is causing the compiler to throw the error. However, trying to track the origin of these has proved too much and I am lost.
Issue 1:
版本：0.6.2951.0

Windows版本：18363.476

通过win+space切换至中文输入法后，无法输入中文，有问题的输入法包括：

微软拼音输入法，版本：系统自带；

小狼毫，版本：0.12.0；

手心输入法，版本：2.7.0.1702；

具体表现为，切换输入法后，系统托盘图标显示切换成功，但是输入的内容实际还是英文。

Issue 2:
Environment

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

Any other software? Ubunutu WSL

Steps to reproduce

To reproduce, on an install of Windows that has never had WSL enabled or installed, install the new Windows Terminal preview from the store. Open it to allow itself to get through any first initialization stuff it needs. Then enable WSL and install a Linux distribution. In my case it was Ubuntu but I have a feeling it would break for the others too.

Expected behavior

In the event that you install the new terminal first before you install WSL, that terminal would pick up on the next launch that there has been a new distribution installed and that it needs to add a basic profile into the settings JSON.

Actual behavior

Nothing happens and the Terminal is left with the same options as before. In my case the default options of CMD, Powershell, and Azure.
Issue 1:
I decided to start using transitions with material-ui 0.18.7, installed react-transition-group v2 (RTGV2), was happy with my transitions, then started noticing really weird behavior in unrelated components. In particular, ripples fail by leaving a big circle over the rippling component. In my case, I'd just added an unrelated FloatingActionButton when I discovered this, and thought it had run amok.

NPM didn't gripe about material-ui having a conflict. I don't see what you could do differently that would make it complain.

Moving to RTGV2 is a big move, so if you do get more push for compatibility in material-ui <1.0, you'll probably need to somehow allow clients to use either v1 or v2 - which is probably prohibitively difficult.

A runtime check and console spew for the wrong version might make sense, though.

Issue 2:
Problem description

After I Installed React Transition Group on my project, when I click on Material UI Buttons (Raised or Flat) a weird <div> appears in the Button comp, like this:

<div in="false" style="position: absolute; top: -51.6045px; left: -2.60453px; height: 141.209px; width: 141.209px; border-radius: 50%; background-color: rgb(255, 255, 255);"></div>

one for each new click.

If I remove React Transition Group, via yarn remove, everything works fluently, again.

I'm using Transition in this way, as explained in main documentation:

import React from 'react';
import PropTypes from 'prop-types';
import Transition from 'react-transition-group/Transition';

const defaultStyle = {
transition: `opacity 300ms ease-in-out`,
opacity: 0,
};

const transitionStyles = {
entering: { opacity: 1 },
entered: { opacity: 1 },
};

const Fade = ({
in: inProp,
children,
}) => (
<Transition in={inProp} timeout={300}>
{state => (
<div
style={{
...defaultStyle,
...transitionStyles[state],
}}
>
{children}
</div>
)}
</Transition>
);

Fade.propTypes = {
in: PropTypes.bool.isRequired,
children: PropTypes.node.isRequired,
};
export default Fade;

Maybe, is there a conflict with React Transition Group v. 1.2.0, used as dependency in Material UI?

Versions

Material-UI: 0.18.7

React: 15.6.1

React Transition Group: 2.2.0

Browser: all
Issue 1:
Hi all,

I am getting segfaults when running the test suite. Specifically, they occur in the manifold module.

Furthermore, all of the examples in that module end in segfaults.

I am using Mac OS X Lion 10.7,

the latest scipy superpack (superpack_10.7_2011.11.04.sh)

gcc version i686-apple-darwin11-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)

I use the following flags:

declare -x CC="gcc-4.2"

declare -x CXX="g++-4.2"

declare -x FFLAGS="-ff2c"

Maybe I should try with different permutations of these flags.

I have to mention that I have a failing numpy test (tests polyfit) and a lot of failing scipy tests (specifically all the ones related to symmetric arpack modes). Detailed version and output is in this pastebin:

http://pastebin.com/Dm1dwsUt

Issue 2:
The example examples/manifold/plot_compare_methods.py segfaults when using scipy from the development version.
Issue 1:
Mark Dolgov opened SPR-3431 and commented

Reference manual for ver. 2.0.4

http://static.springframework.org/spring/docs/2.0.x/reference/beans.html

Section 3.2.2.1

The problem is still there!

(Copied form related bug: #8093)

The xml shown in section 3.2.1.1 of documentation is missing the following text "http://www.springframework.org/schema/beans" in xsi:schemaLocation attribute of beans tag. If we try this xml, we get org.xml.sax.SAXParseException with message '

'SchemaLocation: schemaLocation value = ' http://www.springframework.org/schema/beans/spring-beans-2.0.xsd' must have even number of URI's.'

The old xml is :

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">

<bean id="..." class="...">

<!-- collaborators and configuration for this bean go here -->

</bean>

<bean id="..." class="...">

<!-- collaborators and configuration for this bean go here -->

</bean>

<!---- more bean definitions go here... -->

</beans>

The new xml should be :

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd">

<bean id="..." class="...">

<!-- collaborators and configuration for this bean go here -->

</bean>

<bean id="..." class="...">

<!-- collaborators and configuration for this bean go here -->

</bean>

<!---- more bean definitions go here... -->

</beans>

Affects: 2.0.4

Issue Links:

#8056 Wrong bean configuration xml file header in Spring 2.0.4 PDF Reference Manual : missing data in xsi:schemaLocation ("duplicates")

Issue 2:
Henryk Konsek opened SPR-7868 and commented

I created simple bean implementing BeanDefinitionRegistryPostProcessor. All I want to do is to register some bean definition in the BeanDefinitionRegistryPostProcessor#postProcessBeanDefinitionRegistry method. The problem is that code working with ClassPathXmlApplicationContext doesn't work with AnnotationConfigApplicationContext.

My intelligent guess would be that BeanDefinitionRegistryPostProcessor#postProcessBeanDefinitionRegistry is called after JavaConfig bean postprocessor.

I'm attaching minimal Maven project with two unit tests (XmlTest & AnnotationTest) to demonstrate the issue.

Affects: 3.0.5

Attachments:

registryBug.zip (23.00 kB)

Issue Links:

#14099 Method postProcessBeanDefinitionRegistry is not called if the bean implements BeanDefinitionRegistryPostProcessor ("is duplicated by")

#12917 BeanFactoryPostProcessor breaks default post-processing of @Configuration classes

#15258 Allow BeanDefinitionRegistryPostProcessor to register other BeanDefinitionRegistryPostProcessors
Issue 1:
it would have performance advantage over client side reindex command and it will increase availability of reindexing because not every client supports it.

Issue 2:
Probably not a high priority or must have feature, but this would be extremely convenient.

This would allow one to:

Switch gateways

Upgrade to new version with incompatible gateway

Clone an entire cluster

Based on this discussion here:

http://groups.google.com/a/elasticsearch.com/group/users/browse_thread/thread/43b534ca360d808f?pli=1
Issue 1:
Hi,

Using v0.191 installed on Linux with this command script/grunt install --install-dir ~/.local.

Steps to reproduce:

Type following in a shell

$ touch /tmp/hihi
$ atom /tmp &

Right click on hihi

Select Delete

Result: File is still on disk.

Expected: File removed.

Thanks for the fine work.

Kévin

Issue 2:
Moving a file in the tree view causes an autosave.

Refs atom/tree-view#123
Issue 1:
Let us know what functionality you'd like to see in Playwright and what your use case is.

Let's say I have a page object like the one below

class PageObject {
readonly parent: Locator;

readonly child: Locator;

constructor(page: Page) {
this.parent = page.locator('[data-id=parent]');
this.child = page.locator('[data-id=child]');
}
}

It makes sense in my use case to have these as separate locators.

But in some instances I would essentially want to chain the parent locator to the child locator.

I could add another locator this.parentChild = page.locator('[data-id=parent] [data-id=child]') but it seems like duplication of selectors that are already defined.

Or I could extract out the selectors but that again is more code.

Some ideas are:

Allow the first arg of page.locator() to be either a selector: string OR a locator: Locator --> this.parent.locator(this.child)

Be able to get the selector from a locator --> this.parent.locator(this.child.selector)

Issue 2:
Right now we need to repeat lines of code to get to the element with more than one attribute.

We would like to have an implementation that will help us with defining for example elements and then filter them by additional attribute:

[Example of what we want]:

[What we have?]

Right now we need to duplicate part of the standardProducts:

async chooseStandardProduct(dataProductName: string): Promise<void> {
await this.page.locator(`[e2e-target-name="standard"][e2e-target-name="${dataProductName}"`]).click()
}

Thanks to that solution we can decrease code duplication. Similar solution already have testcafe.
Issue 1:
Hi community,

This issue is for #20305.

Aim

Add more unit tests for YamlSQLParserRuleConfigurationSwapper to test its public functions to improve unit test coverage.

Unit test coverage can be viewed at: https://app.codecov.io/gh/apache/shardingsphere

Basic Qualifications

Java

Maven

Junit

Issue 2:
Hi community,

This issue is for #20305.

Aim

Add more unit tests for YamlSQLParserRuleConfigurationSwapper to test its public functions to improve unit test coverage.

Unit test coverage can be viewed at: https://app.codecov.io/gh/apache/shardingsphere/blobs/master/shardingsphere-kernel/shardingsphere-parser/shardingsphere-parser-core/src/main/java/org/apache/shardingsphere/parser/yaml/swapper/YamlSQLParserRuleConfigurationSwapper.java

Basic Qualifications

Java

Maven

Junit
Issue 1:
sharding is affected when encrypt。but query is not decrypt.

and I found The problem is (SQLServerResultSetMetaData)

this.rs.getColumn(var1).getTableName().getObjectName(); ,this code return "",so cann't decrypt

for example config:

encrypt: encryptors: encryptor_aes: type: aes props: aes.key.value: 123456 tables: users: columns: mobile: cipherColumn: mobile_cipher encryptor: encryptor_aes props: query.with.cipher.column: true sql.show: true

Issue 2:
the profile as below:

spring:

shardingsphere:

props:

sql.show: true

query.with.cipher.comlum: true

datasource:

name: ds0

ds0:

type: org.apache.commons.dbcp.BasicDataSource

driver-class-name: com.mysql.cj.jdbc.Driver

url: jdbc:mysql://127.0.0.1:3306/test?useUnicode=true&characterEncoding=utf-8&serverTimezone=UTC

username: root

password: root

max-total: 100

sharding:

tables:

user:

actual-data-nodes: ds0.user_$->{0..4}

table-strategy:

inline:

sharding-column: id

algorithm-expression: user_$->{id % 5}

encrypt:

encryptors:

encryptor_aes:

type: aes

props.aes.key.value: 123456

tables:

user:

columns:

name:

cipherColumn: name

encryptor: encryptor_aes