WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I notice that there is no separate cone geometry, but that a CylinderGeometry with radius 0 in one end will be reduced to a cone through merging of vertices.

I also notice that a simple (straight wall) cone in fact has the same graph of vertices as the CircleGeometry. I have had some success, but mostly failure, trying to manipulate the CircleBufferGeometry into a usable cone for optimizing a scene with an extreme number of simple cones (procedural generation of a tree).

I am not really (only) asking for help here. Wondering what you think and know about the differences, regarding how textures are applied et cetera, and maybe considering the idea of building a simple cone class on top of the CircleBufferGeometry, if that is wise.

You may all have a tree, by the way. A Three tree. :-)

Issue 2:
If I add a lightmap to my standardmaterial then the envmap still appears to light that mesh

Steps to reproduce the behavior:

1 Create a simpe screne in blender lit by a HDR

2 Bake out lightmaps for that scene to use in Three JS

3 Load the screne and HDR using Three JS. Add the baked lightmap to the scenes standard material.

4 Observe that the envmap is still lighting the scene as well as providing reflections

Expected result is that the lightmap should be the only thing lighting the scene and the envmap used for reflections only.
Issue 1:
Environment

Windows build number: [Version 10.0.18363.900]
PowerToys version: v0.18.2
PowerToy module for which you are reporting the bug (if applicable): N/A

Steps to reproduce

With PowerToys in the System Tray (no active window open) I restart windows from the start button and while Windows is closing programs, an error message-box pops up. (See screenshot attached to this post). The error reads:

"The exception unknown software exception (0xe0434352}

occurred in the application at location 0x00007FFDB1C6A799."

Windows won't shutdown/restart until I click OK or Cancel (which just closes the program, allowing the restart/shutdown to continue.)

Expected behavior

Normally the program should just exit silently and allow windows to restart/shutdown.

Actual behavior

Instead it just crashes and prevents windows from shutting down or restarting until I interact with the error message box.

Screenshots

Issue 2:
Note: This issue is mainly for community discussion rather than bug/feature issue for maintainers.

By default PT Run is launched by Alt + Space, but the issue is it sometimes opens window menu instead of PT Run.

I tried Windows Key + Space but it also opens keyboard layout switcher instead of PT Run sometimes. Which keyboard shortcut would you suggest for PT Run instead of default Alt + Space?
Issue 1:
The original motivation for this is having a nicer syntax for transpose and conj, where the most appropriate I could come up with was M'ᵀ and z'ᶜ. Currently this would only be possible by special casing transpose and conj at a parser level, but if #33683 was merged, one could extend the concept of Unicode modifiers for infix operators to ' very nicely. This would also be useful for packages like Zygote, which like to pun on ' as notation for taking the derivative, which could then export e.g. 'ᴰ instead.

A problem is that currently, a'ᵀb is valid syntax for adjoint(a) * (ᵀb), which is quite unfortunate, since this is different from other infix operators like +, where the modifier gets parsed as part of the operator, even if there is no whitespace in between. I therefore believe that parsing these as part of the operator will make for more consistency, but as this is technically breaking, it might be necessary to deprecate this syntax for one minor release first. Eventually it might make sense to disallow modifiers in front of variable names altogether, but that would be a separate issue.

Issue 2:
Since #22089 it is possible to add suffixes to existing binary operators in order to create entirely new ones.

If it were possible to add suffixes to the postfix ' operator as well, then that would make it possible for the user to create an arbitrary number of new postfix operators. For example, it would make it possible to make A'ᵀ the transpose of A.

See #21037 for the beginning of this discussion. Here's a brief summary as best as I've understood: The original proposal was to map x' to the function call '(x), and then allow suffixes on that function name, but this is not possible. The first character of an identifier cannot be ', because ' is already used to introduce character literals. On the other hand, using a function name like apostrophe can lead to problems similar to #25947. That problem can be avoided by mapping to Base.apostrophe instead of using the local scope.
Issue 1:
System information (version)

OpenCV => Latest 4.0.0 (Master Branch)

Operating System / Platform => Ubuntu 18.04.1 LTS

Compiler => GCC 7.3.0

Detailed description

All Python Bindings Seems Broken:(See below)

Python 2.7.15rc1:

abhishek@abhishek-HP-Pavilion-Notebook:~/Downloads/opencv-master/build_tbb$ python
Python 2.7.15rc1 (default, Nov 12 2018, 14:31:15)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import cv2
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: /usr/local/lib/python2.7/dist-packages/cv2.so: undefined symbol: _ZN2cv8Stitcher17estimateTransformERKNS_11_InputArrayE
>>>

Python 3.6.6:

abhishek@abhishek-HP-Pavilion-Notebook:~/Downloads/opencv-master/build_tbb$ python3
Python 3.6.6 (default, Sep 12 2018, 18:26:19)
[GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cv2
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: /usr/local/lib/python3.6/dist-packages/cv2.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN2cv8Stitcher17estimateTransformERKNS_11_InputArrayE
>>>

Debug Files:

Strace:

python2.txt

python3.txt

Issue 2:
System information (version)

OpenCV => 3.4+

Operating System / Platform => windows

Compiler => MSVC debug with _DEBUG macro defined

Steps to reproduce

The following c++ code fails in assert inside Mat::elemSize

int f()
{
cv::Mat1b m(2, 2);
auto crop = m(cv::Rect(0,0,0,0));
int res = cv::sum(crop)[0]; // assert fails in Mat::elemSize
return res;
}

Detailed description:

Matrix ctor calls Mat::release() in case of rows==0 && cols==0.

In debug mode (if _DEBUG is defined) Mat::release() sets dims to 0.

Thus Mat::dims variable has different values in debug and release after the construction of the matrix.

expected behavior:

assert fails only in case of an uninitialized matrix.

cv::sum(cv::Mat()); // should fail
cv::Mat1b m(2, 2);
cv::sum(m(cv::Rect(0,0,0,0))); // should not fail

Mat is expected to have the same dims value in release and debug

possible fix:

--- a/modules/core/src/matrix.cpp
+++ b/modules/core/src/matrix.cpp
@@ -475,6 +475,7 @@ Mat::Mat(const Mat& m, const Rect& roi)
if( rows <= 0 || cols <= 0 )
{
release();
+ dims = 2;
rows = cols = 0;
}
}
Issue 1:
Hello, i recently upgraded from R71 to R73 and am pretty happy with the evolution of Three.Audio

I am currently developing some sort of game, and i need different type of sound capabilities

A) ambient sound (no position, just some background)

B) "event" sound, like footstep, punch... (once again, no position needed)

C) positional sound (like a torch on a wall, a monster, a fountain...)

Three.audio is not really useful for A and B, which is ok (but you loose some of the ease of use that provide Three.audio)

C is clearly the intended use of Three.audio, with the use of the panner to position the sound seamlessly with position update from Three.

but i could see some enhancement (some easy, some more complex) added.

first and foremost, the ability to directly create a Three.Audio with a pre-loaded buffer, thus avoiding a request if the sound is already loaded. Particularly useful if a sound is used at a lot of different positions (like 'medieval' torch burning in my case for example).

if you want to go further, and more powerful/generic, we could provide directly a way to connect an audio source/node to three.Audio (instead of a buffer or file), which would open all (or almost) the possibilities of the webAudio api while still benefiting from Three.Audio functionality

maybe a way to add/remove filter in Three.Audio, instead of just setting one (which is already a big plus), but it would maybe become too complicated/cumbersome...

what do other peoples think of this ? any idea ?

if it is interesting and possible to have that in Three, i could try and do an implementation candidate for a pull request instead of just having my own code (case in point, if it is something needed and acceptable for Three).

Issue 2:
I use Skeletal animation in my scene and I want to add shadow to the animated mesh, but I fail.

When I examine the code, it seems that only "_depthMaterialMorph" is provided(in WebGLRenderer.js line:130), can you provide shadow for Skeletal animation?
Issue 1:
providing both inputProps and InputProps raises warning on compilation

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

Expected Behavior

No warning on compilation. Have different names for the two properties so it's not clashing, and case isn't required. (perhaps htmlInputProps and inputProps)

Current Behavior

If you provide both an inputProps and an InputProps property on a single component there is a warning on compilation that you are supplying duplicate properties as case is ignored.

Steps to Reproduce (for bugs)

provide both inputProps and InputProps

Context

It's confusing, and having warnings on compilation is less than desirable

Your Environment

Tech
Version

Material-UI
1.0.0-beta.10

React
15.6.1

Issue 2:
Here in section Auto-layout https://material-ui.com/layout/grid/ there is example when you do not set xs value for Grid items. If you add long long text to these Grid items their width become too big and Grid items will be moved the the new line. Of course I can set wrap="nowrap" to the Grid container and Grid items will not be moved to the new line but in this case Grid width of all Grid items will be more than width of Grid container. To fix it you can set width: 0; to items.

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

Expected Behavior

Grid items have fixed max-width and are not moved to the new line

Current Behavior

Grid items width become the same as its content have. Grid items are moved to the new line.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/github/mui-org/material-ui/tree/v1-beta/examples/create-react-app Is not working, I do not know why, so I will put example here if you do not mind

import React from 'react';
import { MuiThemeProvider } from 'material-ui/styles';
import Grid from 'material-ui/Grid';

class GridExample extends React.Component {
render() {
return (
<div style={{width: '1000px', margin: '0 auto'}}>
<Grid container>
<Grid item xs={12} sm={6}>
Sidebar
</Grid>
<Grid item xs={12} sm>
LongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContentLongLongContent
</Grid>
</Grid>
</div>
);
}
}

const App = () => (
<MuiThemeProvider>
<GridExample />
</MuiThemeProvider>
);

ReactDOM.render(
<App />,
document.getElementById('container')
);

Context

Your Environment

Tech
Version

Material-UI
^1.0.0-beta.22

React
^16.2.0

browser
any

etc
Issue 1:
lt is a point-wise math operator so porting it from the TH code to Aten (and TensorIterator) expected to be easy. Such migration will help to clean up the code, simplify dispatch as well as provide immediate 2-3x operator performance gain.

Porting guide: https://github.com/pytorch/pytorch/wiki/TH-to-ATen-porting-guide

Example PR with porting of the adaptive_avg_pool2d: #14714

How to use TensorIterator: https://github.com/pytorch/pytorch/wiki/How-to-use-TensorIterator

Issue 2:
Porting TH operators is essential for code simplicity and performance reasons.

Porting guides and Q&A are available in umbrella issue: #24507

Feel free to add @VitalyFedyunin as a reviewer to get a prioritized review.
Issue 1:
Description

Looking at our variables, every single one of them is JSON, the largest being 100 lines long. I will assume that most other users are mainly using JSON vars as well.

I can think of a few quality of life changes that could be made to make working with these variables easier:

Make the 'Val' field on /admin/variable/edit use a fixed width font. This would probably not hurt non-JSON users either.

Add JSON syntax highlighting to the textarea there.

Add optional JSON syntax validation; perhaps a boolean flag in the DB for whether the var is supposed to be JSON. If true, reject updates with non-valid JSON syntax to the variable, and perhaps don't require deserialize_json=True to be specified in the code every time it's accessed.

This last one might be a bit far-fetched, but: Make it possible to add a JSON schema file that will be validated against on updates.

Let me know if you want these split into separate JIRA issues.

Use case / motivation

Related Issues

Moved here from https://issues.apache.org/jira/browse/AIRFLOW-310

Issue 2:
Description

Looking at our variables, every single one of them is JSON, the largest being 100 lines long. I will assume that most other users are mainly using JSON vars as well.

I can think of a few quality of life changes that could be made to make working with these variables easier:

Make the 'Val' field on /admin/variable/edit use a fixed width font. This would probably not hurt non-JSON users either.
Add JSON syntax highlighting to the textarea there.
Add optional JSON syntax validation; perhaps a boolean flag in the DB for whether the var is supposed to be JSON. If true, reject updates with non-valid JSON syntax to the variable, and perhaps don't require deserialize_json=True to be specified in the code every time it's accessed.
This last one might be a bit far-fetched, but: Make it possible to add a JSON schema file that will be validated against on updates.

Let me know if you want these split into separate JIRA issues.

Use case / motivation

Related Issues

Moved here from https://issues.apache.org/jira/browse/AIRFLOW-310
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

If you navigate to the Select element using the tab key it gets focused and both the underline and the input label gets colored.

If you select an option from the Select using the mouse or the keyboard after the element gets selected and it's value gets updated the Select remains in focus and both the underline and the input label remains colored.

Current Behavior

Switching to an Select is working as intended however if you select an option using the mouse or the keyboard only the underline remains colored, the input label loses the coloring.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/7yplykn0rq

Click on a Select element

From the menu select an option

When the select is updated with the newly selected option the coloring of the input label disappears

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.24

React
16.2.0

browser
Electron (Chrome 61.0.3163.100)

Issue 2:
When creating a BottomNavigation component with multiple BottomNavigationItem, the BottomNavigationItem are not centered in IE11.

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

Expected Behavior

I expect all the BottomNavigationItem to be centered within the BottomNavigation component. This is how it looks in Firefox ESR 52, Firefox 57, Chrome 62 and Chrome 63:

Current Behavior

In IE11, it appears that the first BottomNavigationItem is centered and the rest of the BottomNavigationItem moved to the right:

Steps to Reproduce (for bugs)

This bug is visible on the BottomNavigation component page on material-ui.com here.

I have also mocked up an example:

Context

I think the look should be consistent across browsers and the way the BottomNavigation component is being displayed on Firefox/Chrome is how it was intended to look.

Your Environment

Tech
Version

Material-UI
0.20.0

React
16.2.0

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

Expected Behavior

Navigate the Material-UI 1.0 docs using Internet Explorer 11 (useful to check component demos, etc).

Current Behavior

An error is thrown in the console and unable to click on the drawer navigation.

Steps to Reproduce (for bugs)

Go to https://www.material-ui.com using Internet Explorer 11 and attempt to click on a link on the drawer.

Context

Check component compatibility with Internet Explorer 11.

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.33

browser
Internet Explorer 11

Issue 2:
theme.transitions.create(CSS) should always take canonical CSS to work. For example, this input underline hover is not working currently, because it is given backgroundColor instead of background-color.

If this is a simple mistake, I can go through it and see if other places are using JS-style CSS, and shift them to regular CSS?

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

Expected Behavior

theme.transitions.create('backgroundColor')

Should properly add a transition of background-color.

Current Behavior

It does not because it isn't proper CSS.

Steps to Reproduce (for bugs)

None of the underline hover transitions are working in the docs

Tech
Version

Material-UI
next
Issue 1:
OpenCV => 3.2

Operating System / Platform => Fedora 25

Compiler => gcc 6.3.1

Detailed description

Undefined behavior in cv::rectangle() when two identical points passed.

Steps to reproduce

Try running the following:

cv::rectangle(im, cv::Point(1000, 1000), cv::Point(1000, 1000), 255, CV_FILLED);

in valgrind. The output is

==4102== Conditional jump or move depends on uninitialised value(s)
==4102== at 0xBFF483F: cv::FillConvexPoly(cv::Mat&, cv::Point_<long> const*, int, void const*, int, int) (in /usr/local/lib/libopencv_imgproc.so
.3.2.0)
==4102== by 0xBFFA096: cv::rectangle(cv::_InputOutputArray const&, cv::Point_<int>, cv::Point_<int>, cv::Scalar_<double> const&, int, int, int)
(in /usr/local/lib/libopencv_imgproc.so.3.2.0)

As a result of this I saw two different resultant images on two different computers. If two identical points are not supported then I think an exception should be thrown.

Issue 2:
System information (version)

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

Steps to reproduce
Issue 1:
Hi,

I'm having trouble calling a function of another module that receives an argument with a type from a third distinct module. I hope the explanation bellow helps you get a sense of the problem.

TypeScript Version:

1.8.9

We have the following folder structure. ProjectB depends on ProjectA. Both depend on Angular2.

| -- Solution
| -- projectA
| -- node_modules
| -- angular2
| -- projectB
| -- node_modules
| -- angular2
| -- projectA

Note: We use node as resolution strategy. angular2 folder is, in both cases, a symlink and both point to the same concrete folder, so the files inside them are exactly the same.

Code

On Project A, we have a class that has something like this:

public navigateByAction(router: ngRouter.Router): Promise<void>

On Project B, we have:

import * as ngRouter from "angular2/router";
import * as projectA from "projectA/main";

...
public router: ngRouter.Router;
....

// Eventually we call a method from projectA.
projectA.navigateByAction(this.router);

Expected behavior:

No TS Compiler error.

Actual behavior:

Argument of type 'Router' is not assignable to parameter of type 'Router'.

Types have separate declarations of a private property '_rootComponent'.

Workarounds

Workaround 1

If I change the structure of the project to something like the following it works fine.

This is not the way we want to move forward because each module should have it's own dependencies and not rely on a parent for dependency resolution.

| -- Solution
| -- node_modules
| -- angular2
| -- projectA
| -- projectB
| -- node_modules
| -- projectA

Workaround 2

Casting to any before calling the function will of course stop the error on the compiler. Definitely not the solution we are looking for in the long term.

Issue 2:
The error relates to enums, and exports using the new typescript node resolution (with the typings property in the package.json). I have tested this on typescript@next.

The bug can be reproduced through the following scenario: (please go to https://github.com/christyharagan/typeScript-enum-export-bug to find this code):

Three projects: a, b, c.

b depends on a

c depends on b

a exports an enum through its index.ts:

export enum E{}

b then exports a function that returns E through its index.ts:

import {E} from 'a'
export function f():E {
return null
}

c then consumes f through its index.ts:

import {E} from 'a'
import {f} from 'b'

let e:E = f()

There is now an error for e:

Type 'E' is not assignable to type 'E'.

All three packages have a package.json that looks like this:

{
"name": "b",
"version": "1",
"main": "lib/index.js",
"typings": "lib/index.d.ts",
"dependencies": {
"a": "1"
}
}

And a tsconfig.json that looks like:

{
"compilerOptions": {
"declaration": true,
"module": "commonjs",
"rootDir": "./src",
"target": "es5",
"outDir": "./lib"
},
"files": [
"src/index.ts"
]
}

Furthermore, this defect occurs if f were to export another symbol (e.g. an interface) which references an exported enum somewhere within it's structure or hierarchy.

This only seems to affect enums, not other types.
Issue 1:
When you start cmd or powershell with ShellExecuteEx or CreateProcess then you can define a working directory, cmd or powershell will start with that working directory but not wt. Is this unsupported or is there a setting?

SHELLEXECUTEINFO shExecInf

shExecInfo.cbSize = sizeof(SHELLEXECUTEINFO);

shExecInfo.fMask = NULL;

shExecInfo.hwnd = hwnd;

shExecInfo.lpVerb = verb.c_str();

shExecInfo.lpFile = path.c_str();

shExecInfo.lpParameters = args.c_str();

shExecInfo.lpDirectory = DirectoryExist(szDir) ? szDir : NULL;

shExecInfo.nShow = Items[i]->HideWindow ? SW_HIDE : SW_NORMAL;

shExecInfo.hInstApp = NULL;

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18990.1]
Windows Terminal version: 0.5.2622.0

Steps to reproduce

Windows Terminal doesn't find PowerShell Core unless it was installed via a standard MSI.

However, folks can also install PowerShell via .NET Core global tool (which is makes its detection and location different) https://devblogs.microsoft.com/powershell/introducing-powershell-as-net-global-tool/

Or you can install PowerShell Core via an MSIX installer (not an MSI) https://github.com/PowerShell/PowerShell/releases

I would propose that we detect all three of these PowerShell Core possible installation vehicles and make profiles for them. Example: PowerShell Core (MSIX), PowerShell Core (Global Tool), etc.

Expected behavior

PowerShell Core is totally ignored when installed in these alternate, but supported, ways.

Actual behavior

Nada.
Issue 1:
It seems that the current process does not change the password after a user is created. So, if keystone_user is called a second time with a different password, nothing would happen.

Issue 2:
Following construct does not changes the password on the existing user:

name: Creation of users...

keystone_user: user={{ item.user }} tenant=admin password={{ item.pass }} email={{ item.mail }} login_user={{ adminuser }} login_password={{ adminpass }} endpoint={{ endpoint }} login_tenant_name={{ tenant }}

with_items:

........

{ user: 'admin', pass: 'newpass', mail: 'admin@domain.com' }

tags:

create_user

All variables were mentioned in role variable file, and I can create new users with it. But using it against existing users with password do nothing - password stays the same :(

ansible --version

ansible 1.3.2