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

I'm still not able to generate man page as I've reported that in #20229 however recently I've changed methodology of generate man pages from using sphinx<>setuptools integration (python setup.py build_sphinx) to straight use sphinx-buid command. All because already sphinx<>setuptools is marked as deprecated.

As part of that change I've started using sphinx-build -n switch.

Sphinx still is not able to generate man page however before it crashes it shows many warnings which are mot related to generate man page.

Here is the output

You can peak on fixes that kind of issues in other projects

latchset/jwcrypto#289

click-contrib/sphinx-click@abc31069

Reproduce the code example:

`/usr/bin/sphinx-build -n -T -b man doc/source build/sphinx/man`

Error message:

No response

NumPy/Python version information:

1.22.4

Issue 2:
New parameter needed, to add the columns which need to be skipped.

e.g:

columns = (1,2,3) - to skip columns 2,3,4
Issue 1:
System information (version)

OpenCV => 3.4.1 Android SDK

Operating System / Platform => Windows 64 Bit (for coding), arm64-v8a for trying out the app

Compiler => Android studio 3.2.1

Detailed description

I am trying to make an app for face detection and eye detection on android using opencv.

but every time i try to build the project using ndk-build it is giving me error: undefined reference to 'cv::CascadeClassifier::detectMultiScale(cv::_InputArray const&, std::ndk1::vector<cv::Rect, std::ndk1::allocator<cv::Rect > >&, double, int, int, cv::Size, cv::Size)'

i have attached the files along with the issue

Steps to reproduce

just start a new project and add the code

OpencvClass.txt

MainActivity .txt

jni.zip

-->

My NDK is configured properly because i can run simple programs.

Issue 2:
System information (version)

OpenCV => 3.1-dev

Operating System / Platform => Windows 64 Bit

Compiler => Visual Studio 2015

Detailed description

When trying to run pyramids as the input for the cv2.calcOpticalFlowPyrLK function the program gives out an error. when I run the cv2.buildOpticalFlowPyramid method it returns a pyramid, without any errors but as soon as I use it as input it doesn't run.

Steps to reproduce

lk_params = dict(winSize=(21, 21), # Parameters used for cv2.calcOpticalFlowPyrLK (KLT tracker)
maxLevel=3,
criteria=(cv2.TERM_CRITERIA_EPS | cv2.TERM_CRITERIA_COUNT, 30, 0.01))

def KLT_featureTracking(image_ref, image_cur, px_ref):

image_ref = cv2.buildOpticalFlowPyramid(image_ref, (512, 512), 2)
image_cur = cv2.buildOpticalFlowPyramid(image_cur, (512, 512), 2)

kp2, st, err = cv2.calcOpticalFlowPyrLK(image_ref, image_cur, px_ref, None, **lk_params)
kp1, st, err = cv2.calcOpticalFlowPyrLK(image_cur, image_ref, kp2, None, **lk_params)

Error:

kp2, st, err = cv2.calcOpticalFlowPyrLK(image_ref, image_cur, px_ref, None, **lk_params)
TypeError: prevImg is not a numerical tuple
Issue 1:
What is the correct process to update typings for the "master" and the “types-2.0” branch:

This project has a “master” branch, and a “types-2.0” branch.

What is the correct process to make a change to a typings file ?

1]

First create the fix as a PR in the “master” branch and then duplicate the code changes in a new PR on the ”types-2.0″ branch ?

2]

Or create a PR in the “master” branch and also create a PR on the “types-2.0” branch which does a merge ?

3]

Or ?

I could not find this information on the Wiki yet ? Maybe an idea to add something here about the process?

See also my question here : https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/#comment-25535

Issue 2:
I propose a simple naming convention for issues that relate to an individual type definition.

If I want to file a bug about the jQuery definition, I would name my issue

[jquery] missing method "foo"

The text within square brackets must match the name of the typing's directory in this repository.

The motivation is that, when I discover a bug in a type definition, I want to make sure I don't file a duplicate bug. Therefore I need to search the issue queue for any other issues related to that type definition.

If this naming convention is explained on definitelytyped.org's contribution guide, we can easily link to it when someone makes an issue that doesn't follow the convention. Before long all issues will use the convention, and we'll no longer need to explain it. That's the theory, at least.
Issue 1:
Alternative to --cached-only

More generally we need to improve vendoring story and documentation around it.

Issue 2:
Hi all--

Inline with #4539 and #5665, I've discovered when you declare deno-types in an import directive, it causes the Deno.bundle() command to ignore the imports.

Gist example: https://gist.github.com/randallb/745dd7cdd638f0e1018e3875641b542c

If I omit the deno-types declaration, it seems to bundle correctly. Might be a dupe of those other issues or might be unrelated, but I figure all three of these usecases would probably be useful to fix at once.
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.5.4

Operating System version: 2.6.32-504.el6.x86_64

Java version: 1.8.0_45

Steps to reproduce this issue

1.偶然发现，无法重现

Expected Result

What do you expected from the above steps？

Actual Result

1: 偶然发现，我重启dubbo项目，有个dubbo服务没有刷新，其时间戳tamp没有刷新，其节点

值都正常。

2: 调用这个dubbo服务，发现其报拒绝服务错误。

3: 解决办法：在zookeeper删除这个节点，然后重启项目，项目恢复。

4: 我无法判断，这个bug是zookeeper还是dubbo？

Issue 2:
In my scenario, some methods in the provider return a large amount of data each time, because the response is internally duplicated, so the serialization and transmission performance can be improved by implementing a new Serialization (protostuff+snappy).I hope that the remaining services or methods in the provider continue to use the default Hessian2 Serialization, however， the Serialization configuration supports only the protocol level.

In dubbo-remoting-netty, NettyServer, when the tcp connection is established, the response serialization type is specified through the NettyCodecAdapter's final url, it seems that Serialization configuration can not support the service or method level now.

Does dubbo subsequently plan to support serialization configuration to service or method?

在我们的使用场景中，provider中有些接口返回数据量较大，在M级别，因为数据内部重复数据多，通过实现新的Serialization插件（protostuff+snappy）可以提高序列化和传输的性能。我们希望provider中其余service或者method继续使用默认hessian2 Serialization，但是现有Serialization配置只支持到protocol级别。

netty通讯方式中，NettyServer当中，当tcp连接被建立，response序列化方式通过NettyCodecAdapter的final url被指定下来，Serialization配置不能支持到service或者method级别。

dubbo后续有计划将Serialization配置支持到service或者method么？
Issue 1:
As Python 2.7 was finally abandoned on January 1st of this year and should no longer be a prerequisite for anything in the computing world (except maybe folks on macos, all of whom should have python3 installed anyway now that 2.7 is dead) it would be a good idea to bump the version of node-gyp to 5.1.0 or higher (see nodejs/node-gyp#2052)

Issue 2:
I created a new node project with npm new. Initialized with default values.

While installing 'express' package using command below :

npm install express --save

npm exits with error

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:

npm ERR! https://npm.community

npm ERR! A complete log of this run can be found in:

Earlier I was getting 503 Error. Serivce Unavailable for which I followed the steps from

npm/npm#6841
Issue 1:
If I understand things correctly, under ES6, the second line should raise a referenceError due to x not yet having been declared.

"use strict";
let b = x; // should throw a referenceError
console.log('b: ', b);
b = 2;
const x = 'a';

Running this through Babel, I get no referenceError. But the following code does raise a referenceError:

"use strict";
let b = x; // throws a referenceError
console.log('b: ', b);
b = 2;

Issue 2:
Another one from the defs test suite:

~/projects/defs.js/tests % cat used-in-same-declaration.js
"use strict";
let x = x; // error
let y = 1, z = y; // ok
let a = b, b = 1; // error

Babel doesn't complain about this currently but should error something similar to

line 2: x is referenced before its declaration
line 4: b is referenced before its declaration

To clarify, I'm asking for static errors.
Issue 1:
Part of the class Private Properties transform is the terribly complicated "property" to function call visitor. It's strikingly similar to the replace supers (1, 2) transform.

That's because they're the same thing, just with different functions to call. This needs to be extracted into a new helper visitor, so we can cut down the duplication.

Issue 2:
From ModuleDeclarationInstantiation( ), step 12.d.iii., parsing import.js below should throw a SyntaxError.

export.js

export {definedExport} from './another-module'

import.js

import {
undefinedExport,
definedExport
} from './export'

However, it currently doesn't.

If someone confirms this issue, I might take a stab at a fix.
Issue 1:
Reproducing code example:

import numpy as np
>>> time_type = data.index.dtype
>>> time_type
datetime64[ns, tzfile('PRC')]

>>> time_type == np.dtype('int32')
False
>>> time_type in [1,2,3]
False
>>> time_type in {np.dtype('int32')}
False
>>> time_type in [np.dtype('int32')]
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: Cannot interpret 'datetime64[ns, tzfile('PRC')]' as a data type

NumPy/Python version information:

python3.9 pandas1.2.4 numpy 1.19.3（When I upgrade the numpy version, the problem is solved）

I'd like to know why an exception is thrown when trying to use "in List[np.dtype]" judgment in this "special" version, while "in set[np.dtype]" or "==" does not cause this problem.

Issue 2:
dtype = pd.date_range("2016-01-01", periods=2, tz="UTC").dtype

>>> dtype == np.dtype("datetime64[ns]")
False

>>> np.dtype("datetime64[ns]") == dtype
TypeError: Cannot interpret 'datetime64[ns, UTC]' as a data type

It'd be nice if this returned False instead of raising.
Issue 1:
The slider comparison is awesome for visual regression tests but the height of the websites often changes which causes the slider comparison to be disabled. Would it be possible to have it available even if the height are different? Maybe we could add an option to pad images that are different heights?

Issue 2:
Context:

Playwright Version: 1.23.0

Operating System: Mac

Node.js version: 16.14.0

Browser: Chromium

Code Snippet

Playwright config:

const config: PlaywrightTestConfig = {
testDir: 'tests',
fullyParallel: true,
reporter: process.env.CI ? [['github'], ['html']] : [['list'], ['html', { open: 'on-failure' }]],
forbidOnly: !!process.env.CI,
retries: process.env.CI ? 1 : 0,
use: {
headless: true,
viewport: { width: 1280, height: 720 },
screenshot: 'only-on-failure',
video: 'retain-on-failure',
trace: 'retain-on-failure',
},
expect: {
toHaveScreenshot: {
threshold: 0.2,
maxDiffPixelRatio: 0.05
},
},
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'] },
},
],
};
export default config;

Method that compares screenshots:

async matchesScreenshot(
locator: Locator,
options?: LocatorScreenshotOptions,
) {
expect(locator).toHaveScreenshot({timeout: 5000, ...options});
}

Describe the bug

I'm doing visual regression testing. I want to see the difference between screenshots in the report. However, the difference is not present there. Also, in the test-results folder the difference is missing too.
Issue 1:
TypeScript Version:

1.8.2

When building a Visual Studio solution using a tsconfig.json file, the CompileTypeScriptWithTSConfig task reports "Skipping target "CompileTypeScriptWithTSConfig" because all output files are up-to-date with respect to the input files.", even though I have indeed modified my .ts files since the last build. I see this behavior both building from the command line and from within the IDE. If I select "Rebuild Solution" from within the IDE, the files get compiled correctly. Also, if I remove the tsconfig.json file (thus using the properties in the .csproj file), the files also get compiled correctly.

FWIW, I would actually prefer to use the .csproj file rather than a tsconfig.json file, but as it stands now I cannot specify certain options (such as --noImplicitReturns and --noFallthroughCasesInSwitch) in the .csproj file.

Issue 2:
In the typescript targets:

<VsTsc
ToolPath="$(TscToolPath)"
ToolExe="$(TscToolExe)"
TSConfigFile="%(ConfigFiles.Identity)"
YieldDuringToolExecution="$(TscYieldDuringToolExecution)"
ProjectDir="$(ProjectDir)"
ToolsVersion="$(TypeScriptToolsVersion)"
TypeScriptCompileBlocked="$(TypeScriptCompileBlocked)"
ComputeOutputOnly="false">

<Output TaskParameter="GeneratedJavascript" ItemName="emittedFiles" />
</VsTsc>

The output parameter GeneratedJavascript includes a js file for every ts file in the project even if:

The file is not set to TypeScriptCompile.

The file is excluded or not matched in tsconfig.json.

Side affect is publish fails trying to copy files that do not exist.
Issue 1:
Issue #7405 was a bug filed that tf.complex_abs() was removed in 1.0. At the bottom it says that tf.abs() now does that work, but the docs for tf.abs() only mention float. I confirmed that tf.abs() does in fact do as the comment on the issue describes (https://github.com/tensorflow/tensorflow/blob/r1.1/tensorflow/python/ops/math_ops.py#L225)

Please incorporate the info from https://www.tensorflow.org/versions/r0.11/api_docs/python/math_ops/complex_number_functions#complex_abs

into

https://www.tensorflow.org/api_docs/python/tf/abs

... specifically the parts about it computing sqrt(a^2 + b^2) for complex numbers.

Issue 2:
I found one useful tensor operation "tensordot" is missing in tensorflow. Theano has an implementation of it. It would be great to have tensordot also in tensorflow.
Issue 1:
Electron version: 2.0.0-beta.1

Operating system: MacOS 10.12

Expected behavior

Context menu MenuItem click event fires on click

Actual behavior

Event doesnt fire

How to reproduce

https://github.com/pfrazee/electron-bug-context-menu-click

git clone https://github.com/pfrazee/electron-bug-context-menu-click
cd electron-bug-context-menu-click
npm install
npm start

Right click, select 'MenuItem1'. A log event should occur but wont.

Issue 2:
Electron version: Electron built at aea06ed

Operating system: macOS 10.13.2

Expected behavior

MenuItem click handlers should get called in the popped up context menu.

Actual behavior

Click handlers never getting called back.

How to reproduce

Open a popup in the main window:

window.webContents.on('context-menu', (event) => {
const menu = new Menu()
menu.append(new MenuItem({label: 'MenuItem1', click() { console.log('item 1 clicked') }}))
menu.append(new MenuItem({type: 'separator'}))
menu.append(new MenuItem({label: 'MenuItem2', type: 'checkbox', checked: true}))
menu.popup(mainWindow)
})

Right click on the running window and select MenuItem1, the log item 1 clicked should print but doesn't.
Issue 1:
Since a few updates ago, I've noticed that loading the Packages or Install options in the Settings window completely locks up Atom. I have to click "Keep Waiting" up to several times before Atom becomes operable again. This happens every single time I go into these menu options.

Atom 211

Windows 7 x86_64

Issue 2:
I am getting random freezes and crashes on Windows 7. I am using Atom version 0.209.0.

Freezing occurs randomly (i.e. not all the time) when:

changing values in the settings window.

opening files (infrequent, big files seem to cause crashes more often).

installing packages

uninstalling packages

closing tabs

I can't find any log files to get more information. The program is completely unresponsive and devtools console is not updated.
Issue 1:
I would like to humbly request a componentDidReceiveProps hook, often times I would like to do something on both componentWillMount and componentWillReceiveProps, but because this.props hasn't been set yet I am forced to pass props around instead of reading directly from this.props.

Before New Hook

componentWillMount() {
this.setup(this.props.id);
}

componentWillReceiveProps(next) {
this.setup(next.id);
}

setup(id) {
UserActions.load(id);
}

After New Hook

componentWillMount() {
this.setup();
}

componentDidReceiveProps() {
this.setup();
}

setup() {
UserActions.load(this.props.id);
}

In this simple example it may seem like a small thing, but often times the passing of props runs deep and instead of conveniently referencing this.props one is forced to plumb the props throughout the component.

Please consider adding componentDidReceiveProps as a hook to leverage the same code that is leveraged in componentWillMount without forcing both to plumb props throughout the component.

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

Feature

What is the current behavior?

useContext triggers update if the whole passed store changed

What is the expected behavior?

add keys argument to trigger update only if specified keys in passed store changed

It would be useful to improve application speed.

F.e.

function MyComponent() {
// example context value
// I want to ignore age changes (who does't hehe)
// {
// name: 'Max',
// age: 35
// }
// dep's-like style
const {name} = useContext(MyContext, 'name')
// or
// comparator style
const {name} = useContext(MyContext, (current, old) => current.name !== old.name)
}
Issue 1:
Is your feature request related to a problem? Please describe.

It's no secret that deno_lint is fast. Like, much, much faster than eslint. As such (and as the deno_lint roadmap heads toward eslint plugin compatibility and autofix), deno will see an increasing number of users and companies adopt deno lint for their linting solution, whether they use node, deno, or any other runtime.

Obviously, running lint in CI is nice, but most users want LSP integration, so that they can see lint issues as they write code.

Describe the solution you'd like

If this extension/lsp were to enable users to run the deno lsp purely for linting, without disabling normal typescript language features, and without enabling any other deno lsp features, we could have a hybrid world where users who use node, bun, etc, could use deno lint to great success.

This would increase adoption and awareness of deno tooling, and make other engineers happy.

Essentially, I wish the deno vscode extension would let us do "deno.enable": false, "deno.lint": true. In this sense, we get the linting features of the deno lsp without turning off visual studio code typescript language features.

Please consider this request! Let me know if I can provide any further information.

Issue 2:
Is your feature request related to a problem? Please describe.

I wanted to use deno linter instead of eslint in VSCode for the project that is not deno-specific. I run deno lint on my project's code and the issues it finds are very useful for me, but I hate fixing them from the console, and I would greatly appreciate to see them as... well... lint output in the VSCode. But it seems it does not work :(

Is it possible to have this functionality in this extension?

My workspace config I tried to use:

{
"deno.enable": false, // As I don't want to use deno. Deno will not handle imports (standard imports; dependencies defined in package.json)
"deno.lint": true,
"eslint.enable": false
}

After restarting VSCode I don't see any linting messages in VSCode. It looks like deno.enable: false turns extension off.

And screenshot showing that indeed it's not working:

Describe the solution you'd like

I would love to use deno lint in the VSCode without enabling deno support. It should be possible, because deno lint works fine from the terminal.

And I would love to see these warning/errors marks directly in the code
Issue 1:
I've a $.fn.tooltip plugin (jQuery Tools) and the $.fn.tooltip (Bootstrap). For the moment i can't keep both because of the naming collision.

Can all plugins be renamed to something like $.fn.bootstrapTooltip instead of $.fn.tooltip ?

I know this is BC break. Also, i haven't find any discussion on this topic, hope i haven't created a duplicate issue.

Issue 2:
class .text-right not work in table, becase another class overwrite it

.table th, .table td {
border-top: 1px solid #DDDDDD;
line-height: 20px;
padding: 8px;
text-align: left;
vertical-align: top;
}

This maybe can be fixed with adding .table .text-right
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have found a very similar issue: #7012 but that talks about the handler being detached AFTER closing popover. Our popovers do not even open, yet they hook into the onScroll event.

Expected Behavior

I expect Popover to not touch scroll events until it is actually on screen.

Current Behavior

Every Popover element (including the ones in IconMenu) hooks into the onScroll event. If there are many of these present, the handling of the scroll events is impacted.

Steps to Reproduce (for bugs)

Go to http://www.material-ui.com/#/components/card

Check Chrome's Dev Tools > Elements > Event Listeners > scroll

You will see there is one scroll listener

This is your baseline

Now click on the Popover menu item to see the example Popover page

Check Chrome's Dev Tools > Elements > Event Listeners > scroll

You will see FOUR listeners.

One listener was registered for each Popover on the screen, even though they are not visible at the moment

This means Popovers are registering even if they are not active at all.

Context

We are (ab)using Popovers in our app, using hundreds/thousands of IconMenu elements within a table. Each of these contains a Popover and each Popover hooks into onScroll. This leads to bad performance when the table size grows.

Your Environment

Tech
Version

Material-UI
0.19.4

React
15.6.2

browser
Chrome 63.0.3239.84

Issue 2:
When using a Select inside a Dialog i get the error "Uncaught RangeError: Maximum call stack size exceeded." after clicking into the select box.

The error came from here.

Note: I'm using redux-form with redux-form-material-ui, but I don't think that they are related, expected for the fact that redux-form-material-ui is using beta 16 of material-ui for the Select component

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

Expected Behavior

To not throw errors

Current Behavior

Errors in console

Steps to Reproduce (for bugs)

Your Environment

Tech
Version

Material-UI
1.0.0-beta.17

React
15.6.1

redux-form-material-ui
5.0.0-beta1

browser
Chrome 61
Issue 1:
React version: 16.13.1

Steps To Reproduce

1- The first render is correct

2- The second re-render is correct because X changes from 1 to 2

3- The third re-render in the wrong

Link to code example:

https://codesandbox.io/s/bug-in-render-ldycb

The current behavior

The third re-render is unnecessary but happen

The expected behavior

The third re-render should not happen

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

Bug

What is the current behavior?

As demonstrated in this codesandbox, trying to implement a pattern similar to the one discussed in https://reactjs.org/docs/hooks-faq.html#how-do-i-implement-getderivedstatefromprops results in an infinite loop, even if the value of the state does not change. This seems like a bug, because, as documented here, If you update a State Hook to the same value as the current state, React will bail out without rendering the children or firing effects.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

What is the expected behavior?

Since the state does not change, bail out on the re-render.

This can be worked around by adding a check before setState to check if the state has changed before calling the function.

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