WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
MeshPhysicalMaterial.aoMap does not contribute to envMap occlusion

Steps to reproduce the behavior:

Go to https://threejs.org/examples/webgl_materials_displacementmap.html

Remove ambient intensity and increase roughness and environment intensity to max.

Notice that occlusion map is not visible like it is with ambient lighting.

Similar issues have emerged before like #8107 fixed by #8152 and possibly others.

Perhaps I'm unaware and this is expected behavior. But I imagine ambient occlusion should also occlude environment map. At least when the surface completely diffuse when the physics of light is pretty much the same as ambient lighting.

Issue 2:
Hello,

In the following scenes rendered using the MeshStandardMaterial and a white ambientLight, you can see

an object using an aoMap without any envMap (so no dynamic reflexion):

an object using an aoMap with an envMap (so with dynamic reflexion):

The problem is that in the second case (which is the one I'm trying to achieve), the light from the envMap (or reflexions) is not occluded by the aoMap. This leaves the rendering with bright regions that should be dark (for example, behind the cushion on the right side, there's light between the cushion and the back of the seat. According to the aoMap, it should be completely dark - as it is when I turn of the envMap like in the first case).

I saw a few discussions on the topic, specifically in #7377, but I was wondering if

I understood right, and what I'm seeing is currently expected for three.js?

this behavior is going to be improved/fixed in the future?

Thanks in advance for your help,

Silvain Toromanoff
Issue 1:
Here's a video of scrolling the Contacts demo up and down (without displaying the image): https://youtu.be/mAiho-wlRV4

Here's a video of scrolling the Colors demo up and down: https://youtu.be/z7hv37pxVWQ

Notice that in Contacts, we see "bursts" of rasterize chart followed by "quiet periods". In the Colors demo, we see consistent low charts.

Issue 2:
Probably most important is that if we fix this is that we find a way to test it since @chinmaygarde indicated this may be the same as an issue he fixed prior. :)

[✓] Flutter (on Mac OS, channel master)
• Flutter at /src/flutter
• Framework revision edbe0348474f6c88cc2935deb9fa52e323e7dc91 (16 minutes ago), 2016-10-19 16:17:55
• Engine revision 525c947ece
• Tools Dart version 1.21.0-dev.0.0

[✓] Android toolchain - develop for Android devices (Android SDK 23.0.2)
• Android SDK at /Users/eseidel/Library/Android/sdk
• Platform android-23, build-tools 23.0.2
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.0)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 8.0, Build version 8A218a

[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.6
• dartlang plugin version 0.6.40

[✓] IntelliJ IDEA Community Edition (version 2016.2.5)
• Dart plugin installed
• Flutter plugin installed

[✓] Connected devices
• Eric's iPhone • 245efaebda74df40169418839fff2a8368bcaae5 • ios

See video.

https://youtu.be/G0Da0Pxmf9g
Issue 1:
It's quite nice to be able to generate a PDF from the documentation for offline reading.

Issue 2:
I want a behavior in which during the forward pass, it will do quantization and for the backward pass, it will behave as an identity and pass the gradients as it is without considering the gradient of that layer.

I am using tensorflow as backend and write the custom ops in tensorflow and try to write a wrapper using it.

# Define custom py_func which takes also a grad op as argument:
def py_func(func, inp, Tout, stateful=True, name=None, grad=None):

# Need to generate a unique name to avoid duplicates:
rnd_name = 'PyFuncGrad' + str(np.random.randint(0, 1E+8))

tf.RegisterGradient(rnd_name)(grad) # see _MySquareGrad for grad example
g = tf.get_default_graph()
with g.gradient_override_map({"PyFunc": rnd_name, "PyFuncStateless": rnd_name}):
return tf.py_func(func, inp, Tout, stateful=stateful, name=name)

# Core logic of quantization function
def quantization(x):
power = tf.pow(2.0,5.0)
return tf.divide(tf.ceil(tf.scalar_mul(power, x)), power)

# function that binds forward and backward pass of tensorflow ops
def tf_quantization(x, name=None):

with ops.op_scope([x], name, "quantize") as name:
y = py_func(quantization,
[x],
[tf.float32],
name=name,
grad=_quantizationGrad) # <-- here's the call to the gradient
return y[0]

# Define Actual gradient
def _quantizationGrad(op, grad):
return grad`

And then I define my custom Quantization Layer

class QuantizeLayer(Layer):

def __init__(self, **kwargs):
super(QuantizeLayer, self).__init__(**kwargs)

def call(self, x):
return tf_quantization(x)

def get_output_shape_for(self, input_shape):
shape = list(input_shape)
return tuple(input_shape)`

But when I include this layer in my model and train the model using train_on_batch, it throws an error:

raise type(e)(node_def, op, message) tensorflow.python.framework.errors_impl.UnknownError: exceptions.AttributeError: 'numpy.dtype' object has no attribute 'base_dtype' [[Node: Wave_One/quantization/quantize = PyFunc[Tin=[DT_FLOAT], Tout=[DT_FLOAT], _gradient_op_type="PyFuncGrad34352844", token="pyfunc_1"

Am I missing something here?
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior

When using check-boxes within react-virtualized(https://github.com/bvaughn/react-virtualized) tree, the boxes translate to right a little bit while beeing checked and back to the normal position after they are checked. Same happens during unchecking. The issue is not present when checkbox is used outside of the tree.

Your Environment

Tech
Version

Material-UI
0.18.1

React
15.5.4

browser
any webkit based

Issue 2:
[y ] I have searched the issues of this repository and believe that this is not a duplicate.

<MuiThemeProvider>
<AutoComplete
open
animated={false}
filter={(searchText, key) => !key || key.includes(searchText)}
autoFocus
dataSource={["1", "2", "3"]}
/>
</MuiThemeProvider>

If I want the list of results to be shown on load, the search results will be wrongly positioned at the top left corner. Any way to fix this? https://i.stack.imgur.com/ysQco.png

Your Environment

Tech
Version

Material-UI
0.19.2

React
15.6.1

browser
Chrome V60
Issue 1:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Using a custom element that adds a class to itself is incompatible when setting the class in a component template.

Expected behavior

Classes set in a component template should be added to the classList, instead of overriding it.

Minimal reproduction of the problem with instructions

Create a custom element that modifies its classList in connectedCallback()

Use the custom element with a class attribute in a component template

View the demo in Chrome (native webcomponent support)

http://plnkr.co/edit/4pzXr214xEZyUZ9ftLG7?p=preview

What is the motivation / use case for changing the behavior?

Feeling the love between Angular and Polymer 2.

Specifically, the <paper-button> element adds the .paper-material class to its classList when attached to the DOM.

Angular first creates and attaches the element (and <paper-button> adds its class hooray!).

Next, the function asks the renderer to set the attributes from the component markup.

In the browser, the renderer uses setAttribute() on the element. When calling element.setAttribute('class', 'name');, existing classes are removed.

Suggested Fix

I think it makes the most sense for DefaultDomRenderer2 to understand that setting the class attribute can have negative consequences.

export class DefaultDomRenderer2 implements Renderer2 {
...
setAttribute(el: any, name: string, value: string, namespace?: string): void {
if (namespace) {
el.setAttributeNS(NAMESPACE_URIS[namespace], namespace + ':' + name, value);
} else if (name === 'class') {
value.split(' ').forEach(className => {
el.classList.add(name, className);
});
} else {
el.setAttribute(name, value);
}
}
}

Angular version: 2.4.10+

Browser: [all]

Language: [TypeScript 2.0.2]

Node (for AoT issues): node --version = v6.9.5

Issue 2:
Getting this in my code as well but easier to show on the official hero form. Here is the plunk of the official hero form with the dev dependency changed into min.

http://plnkr.co/edit/hKCBa1RDob5H9i9x7ZhT?p=preview

There error you get is

No provider for t! (t -> t)

And when you switch back to dev it goes away.
Issue 1:
Hi.

I have updated my typescript (npm install typescript -g) recently and now I have an issue with some multiple references to the same file.

It worked fine under TS 1.0.

shared/app/Sails.ts:

///<reference path='./lib/def/defLoader.d.ts'/>

import cli = require('./../../shared/app/Cli');
var Cli = cli.Cli;

export class Sails{

}

Because Cli also imports the same defLoader.d.ts, I get the following errors:

../../shared/app/lib/def/JQuery.d.ts(23,5): error TS2300: Duplicate identifier 'accepts'.
../../shared/app/lib/def/JQuery.d.ts(24,5): error TS2300: Duplicate identifier 'async'.
../../shared/app/lib/def/JQuery.d.ts(26,5): error TS2300: Duplicate identifier 'cache'.
../../shared/app/lib/def/JQuery.d.ts(28,5): error TS2300: Duplicate identifier 'contents'.
../../shared/app/lib/def/JQuery.d.ts(31,5): error TS2300: Duplicate identifier 'contentType'.
../../shared/app/lib/def/JQuery.d.ts(32,5): error TS2300: Duplicate identifier 'context'.

(much more errors but I guess you get what's the issue)

I can solve it two ways, either by removing the Cli reference (so, I don't require the file), or by removing the //<reference path at the top of the file.

I didn't have this problem in TS 1.0.

Weird thing, I have this issue only here, even if in some other files I do the same, I don't get the error there and I'm not able to understand why it works there while here it fails.

But I just figured it out while writing this issue. It is because of the path used to load my Cli module, I used require('./../../shared/app/Cli'); while I should have used require('./Cli'); and because of this somehow the compiler tried to perform the reference twice because it thought it was another file. Well, I didn't have this issue in TS 1.0, I don't know if it's on purpose, anyway my issue is solved now, just wanted to give you a feedback.

Keep up the good work, looking forward for TS 2.0!

Issue 2:
TypeScript Version:

1.7.5 / 1.8.0-beta / nightly (1.9.0-dev.20160217)

Code

// A self-contained demonstration of the problem follows...

Expected behavior:

Actual behavior:
Issue 1:
I am calling the celery tasks by task.delay, task.appy_asyn or send_task but each of these methods hang for ever when the broker is not started. I am using celery version 4.1.0.

I thought the action would expire and throw exception after default timeout. Is there any way to stop the application waiting for ever.

I also specified the retry_policy parameters while calling tasks but they do not make any difference.

Issue 2:
Checklist

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

to find out if the bug was already fixed in the master branch.

I have included all related issues and possible duplicate issues in this issue

(If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

PR: #5275 (status is open, but feature is already present since Celery v4.4.0)

Possible Duplicates

None

Description

First off, documentation is not especially wrong on the use of DynamoDB as a results backend. However, it is incomplete in a significant way. Because I manage the DynamoDB table through IaC I did not realize that defining a sort key would break compatibilty with Celery.

When you use a DynamoDB table with a sort key you can not use Celery v4.4 versions >= v4.4.3. The reason is commit c711047 which introduces a query of existing Celery result status. When you have a sort key defined for your DynamoDB table, the primary key is no longer just the partition key ('id'), but a combination of the partition and sort keys ('id' and 'timestamp' in my case).

Suggestions

It would be fun to add sort key support to the DynamoDB results backend, but I fear it will not be possible. For example, in my case I will need to know the value of the 'timestamp' in addition to the 'id' of the result item we need to retrieve. I don't believe Celery has knowledge of the 'timestamp' we are looking for at the time the query from commit c711047 is performed.

So my suggestion is simple: Let's add a line in the documentation about DynamoDB use as results backend that warns us that you cannot use a sort key on the table. Luckily, you could still add a global secondary index (GSI) if you want to perform queries based on something other than the partition key. A GSI will not break the primary key schema for the queries from Celery.
Issue 1:
julia> x = [1,2]
2-element Array{Int64,1}:
1
2

julia> A = [1 2; 3 4]
2x2 Array{Int64,2}:
1 2
3 4

julia> x * A
ERROR: DimensionMismatch("*")
in generic_matmatmul! at linalg/matmul.jl:369
in * at linalg/matmul.jl:76

julia> A * x
2-element Array{Int64,1}:
5
11

The fix is trivial: at linalg/matmul.jl:76, put the 1 first:

julia> (*)(A::AbstractVector, B::AbstractMatrix) = reshape(A,1,length(A))*B
Warning: Method definition *(AbstractArray{T,1},AbstractArray{T,2}) in module LinAlg at linalg/matmul.jl:76 overwritten in module Main at none:1.
* (generic function with 143 methods)

julia> x * A
1x2 Array{Int64,2}:
7 10

Issue 2:
from @alanedelman:

We really should think carefully about how the transpose of a vector should dispatch the various A_*op*_B* methods. It must be possible to avoid new types and ugly mathematics. For example, vector'vector yielding a vector (#2472, #2936), vector' yielding a matrix, and vector'' yielding a matrix (#2686) are all bad mathematics.

What works for me mathematically (which avoids introducing a new type) is that for a 1-dimensional Vector v:

v' is a no-op (i.e. just returns v),

v'v or v'*v is a scalar,

v*v' is a matrix, and

v'A or v'*A (where A is an AbstractMatrix) is a vector

A general N-dimensional transpose reverses the order of indices. A vector, having one index, should be invariant under transposition.

In practice v' is rarely used in isolation, and is usually encountered in matrix-vector products and matrix-matrix products. A common example would be to construct bilinear forms v'A*w and quadratic forms v'A*v which are used in conjugate gradients, Rayleigh quotients, etc.

The only reason to introduce a new Transpose{Vector} type would be to represent the difference between contravariant and covariant vectors, and I don't find this compelling enough.
Issue 1:
Environment

Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal (Preview)
Version: 0.5.2762.0

Steps to reproduce

enable openssh client in windows. Start Windows Terminal, it will start the default shell (powershell) , use ssh client connect to a remote ssh server, e.g ssh root@myhost .

wait for the ssh connection until it is timeout (let's say no keep alive package is sent by server or client)

Expected behavior

if the ssh connection is timeout , I can see what happen within the shell, e.g

[root@myhost ~]# Connection to myhost closed by remote host.

Connection to myhost closed.

Actual behavior

After the ssh connection is timeout. The whole windows terminal is stuck, you can not move windows terminal , you can not see what's happen within the shell , but you just can see the background of you desktop. I event can not close windows terminal. I have to click the + button to start a new shell, then I can get back the control fo windows terminal.

Issue 2:
I have noticed that if you try to compile the project and the system language is not set to English, there will be errors when compiling the CascadiaPackage. The reason for that is (in my opinion) that the buildscript gives an invalid response when it reaches

23>Does C:\Users\Marcel\Documents\Terminal\x64\Debug\TerminalApp.dll specify a file name
23>or directory name on the target
23>(F = file, D = directory)? f
23>C:\Users\Marcel\Documents\Terminal\x64\Debug\TerminalApp\TerminalApp.dll
23>1 File(s) copied
23>Does C:\Users\Marcel\Documents\Terminal\x64\Debug\TerminalApp.pdb specify a file name
23>or directory name on the target
23>(F = file, D = directory)? f
23>C:\Users\Marcel\Documents\Terminal\x64\Debug\TerminalApp\TerminalApp.pdb
23>1 File(s) copied

. I tested it in German where the letters for File and Directory are different and therefore the script throws an error and cannot build. However if I change the system language to English, everything build successfully.
Issue 1:
If in my playbook I do:

name: Install Ruby {{ ruby_version }}

It would be cool if when that message displays on stdout, it replaced {{ ruby_version }} with the value for that variable.

Issue 2:
Hi,

It would be great if vars_prompt could be taggable ;

permitting :

ansible-playbook my_playbook.yml --tags "config"

To ask for password.

But :

ansible-playbook my_playbook.yml --tags "import"

To not ask it.

Sample :

vars_prompt:
- name: "root_password"
prompt: "the future root password"
encryption: "md5_crypt"
confirm: True
private: True
salt_size: 7
salt: "blv"
tags: config

vars_prompt:
- name: "root_password"
prompt: "the future root password"
confirm: True
private: True
tags:
- config
- check

Thanks.
Issue 1:
Hi!

@spicyj said I should open an issue here. Disclaimer: I'm trying to do sort of sketchy things, and I know this isn't supported, but I think it would be nice.

I'm writing a library that I want to support react output optionally. To do this, right now I'm trying to inline all my ReactElements, such as

return {
type: 'hr',
key: state.key,
_isReactElement: true
};

instead of

React.createElement('hr', {
key: state.key
})

This is almost completely functional, except for the _store validation in react dev mode. This is because right now these literals don't have a _store key with .validated or .originalProps, which are assumed by the validators in React DEV. I can work around this, but to do so without duplicating props will have to write a wrapper function to create the element, which is a little unideal and slower (and adds unnecessary keys in non-dev mode).

Would it be reasonable to short circuit some of these checks so that they only happen if _store is actually present on the ReactElement? If so, I'd be happy to submit a pull request (no rush for react 0.13 though).

Curious as to your thoughts. Thanks!

Aria

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

Bug

What is the current behavior?

Elements with the same key are not deduplicated, which in itself is not unreasonable, I guess, since having duplicate keys is undefined behavior. However, on subsequent rerenders the duplicate elements remain in the render tree with no way to remove them.

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

https://codepen.io/asana/pen/ZaaKzQ (follow the instructions)

What is the expected behavior?

Elements with the same key are deduplicated (this was the behavior in React 15: https://codepen.io/asana/pen/RjjVbJ). Or, at the very least, duplicate elements are appropriately cleaned up in subsequent rerenders.

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

Mac Chrome, React 16+. Working in 15.
Issue 1:
As per @mrm007 in #143, arrays should be supported as targets in a bower.json.

Issue 2:
Hi!

I would like to see support out of the box in webpack for not only npm, but also the other very popular package managers, bower and component.

I'm guessing it should be a matter of adding this:

new DirectoryDescriptionFilePlugin("package.json", ["main"]),
new DirectoryDescriptionFilePlugin("bower.json", ["main"]),
new DirectoryDescriptionFilePlugin("component.json", ["main"]),

Thank you!
Issue 1:
📝 Provide a description of the new feature

Please add an export and import keyboard settings file in the in the "Keyboard Manager". It can help us to export our settings to other computers 👍👍👍👍

Issue 2:
Have both predefined profiles (e.g. mac/linux/etc) available to user, and also allow the user to create custom profiles.

Provide a quick way to switch between profiles.
Issue 1:
I mistakenly added massive entries(~500,000 lines) in /etc/ansible/hosts, ansible-playbook then hangs on execution. I guess it was trying to read entire file in to memory and parse. After truncating the file to a normal size, ansible-playbook started working as normal.

This looks like an ansible bug to me. A large size cloud could easily have hundreds of thousands VMs, ansible should be able to handle this extent of scalability.

Issue 2:
Issue Type:

Bug Report

Ansible Version:

1.5.3

Environment:

CentOS 6.4

Summary:

ansible-playbook will hang if /etc/ansible/hosts file contains massive entries

Steps To Reproduce:

add large number of entries to /etc/ansible/hosts file, for example, 500,000 entries

run any playbook by ansible-playbook

Expected Results:

playbook should run as normally as when /etc/ansible/hosts is in small size

Actual Results:

ansible-playbook hangs > 6 minutes