WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
As of threejs version 112 a directional light with castShadow set to true adds a yellow tint to objects on some devices including the Pixel 3a. Confirmed on the Pixel 3a using both Chrome 79 and Firefox 68.4.1.

Here's a demo of the issue (no cdn for 112 exists so you'll have to download it)

The cube should be a yellowish green.

The yellow tint goes away if you do one of the following:

use a previous version of threejs

comment out 'mainLight.castShadow = true'

skip enabling the shadowMap on the renderer.

<html>
<head>
<!-- <script src="https://cdnjs.cloudflare.com/ajax/libs/three.js/110/three.min.js"></script>-->
<script src="three.112.js"></script>
<style>
body {
margin:0;
padding:0;
}
#scene-container {
width:100%;
height:100%;
}
</style>
</head>
<body>
<div id="scene-container"></div>
<script>
const container = document.querySelector( '#scene-container' );

const scene = new THREE.Scene();

scene.background = new THREE.Color( 'skyblue' );

const mainLight = new THREE.DirectionalLight(0xFFFFFF, Math.PI - 0.5);
mainLight.castShadow = true;
mainLight.position.set(0.15, 0.866, 0.35);
scene.add( mainLight );

const fov = 35;
const aspect = container.clientWidth / container.clientHeight;
const near = 0.1;
const far = 100;

const camera = new THREE.PerspectiveCamera( fov, aspect, near, far );
camera.position.set( 0, 0, 10 );

const geometry = new THREE.BoxBufferGeometry( 2, 2, 2 );

const material = new THREE.MeshStandardMaterial();
material.roughness = 1;
material.metalness = 0;

const mesh = new THREE.Mesh( geometry, material );
scene.add( mesh );

const renderer = new THREE.WebGLRenderer();
renderer.shadowMap.enabled = true;
renderer.shadowMap.type = THREE.PCFSoftShadowMap;
renderer.setSize( container.clientWidth, container.clientHeight );
renderer.setPixelRatio( window.devicePixelRatio );

container.appendChild( renderer.domElement );

renderer.render( scene, camera );
</script>
</body>
</html>

Issue 2:
Description of the problem

I assume this is a driver bug on the Pixel 3, and it's probably long-standing; it repros on dev, as well as r112 and r110. I haven't tried any more versions. Try this fiddle; normally it's just a white sphere:

But on Pixel 3, specifically with this line enabled:

renderer.shadowMap.type = THREE.PCFSoftShadowMap;

We get yellow:

Three.js version

Dev

r112

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

Pixel 3
Issue 1:
JAVA_HOME="$(/usr/libexec/java_home -v 1.9)" mvn clean package

Results in the following:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project java-util: Compilation failure: Compilation failure:
[ERROR] /Users/charles.allen/src/druid/java-util/src/main/java/io/druid/java/util/common/ByteBufferUtils.java:[22,16] cannot find symbol
[ERROR] symbol: class Cleaner
[ERROR] location: package sun.misc
[ERROR] /Users/charles.allen/src/druid/java-util/src/main/java/io/druid/java/util/common/ByteBufferUtils.java:[57,11] cannot find symbol
[ERROR] symbol: class Cleaner
[ERROR] location: class io.druid.java.util.common.ByteBufferUtils

Issue 2:
Recently there have been quite a few PRs and issues opened relating to null/empty string handling.

I have gathered links to these PRs/issues here, if we would like to have a wider discussion on this topic.

#2715 - stringFormat extractionFn should be able to return null on null values (Fix for #2706) #2715

#2737 - Fix predicate-based ValueMatcher behavior for IncrementalIndex on missing columns.

#2758 - handle null values in In Filter

#2765 - Null string is encoded as "null" in incremental index

#2771 - Various ExtractionFn null handling fixes.

#2772 - DimensionPredicateFilter and JavaScriptFilter don't handle null columns properly

#2776 - Inconsistent null/empty str handling for multi-value/single-value dimensions in QueryableIndexStorageAdapter
Issue 1:
Compiling with the instructions in #10181 results in two test failures. One is JuliaMath/openspecfun#30. The other is:

exception on 5: ERROR: assertion failed: |func(D) - func(DM)| <= 3.4332275e-5
func(D) = 1.048798f0 - 1.5707964f0im
func(DM) = 1.0487979650497437 - 0.5797938426309308im
difference = 0.9910025278753558 > 3.4332275e-5
in read at ./iobuffer.jl:86
in read at stream.jl:699
in anonymous at task.jl:837
while loading linalg4.jl, in expression starting on line 263
ERROR: assertion failed: |func(D) - func(DM)| <= 3.4332275e-5
func(D) = 1.048798f0 - 1.5707964f0im
func(DM) = 1.0487979650497437 - 0.5797938426309308im
difference = 0.9910025278753558 > 3.4332275e-5
in anonymous at task.jl:1367
while loading linalg4.jl, in expression starting on line 263
while loading /home/jiahao/julia-intel/test/runtests.jl, in expression starting on line 39

Issue 2:
Environment: Ubuntu 14.04 icc 15.0 ifort 15.0 mkl 11.2

source /opt/intel/composerxe/bin/compilervars.sh intel64

source /opt/intel/mkl/bin/mklvars.sh intel64 ilp64

export LD=/opt/intel/composerxe/bin/xild

export AR=/opt/intel/composerxe/bin/xiar

export MKL_INTERFACE_LAYER=ILP64

export MKLROOT = /opt/intel/composerxe/mkl

Make.user:

USE_INTEL_MKL = 1

USE_INTEL_MKL_FFT = 1

USE_INTEL_LIBM = 1

USEICC = 1

USEIFC = 1

Built succesful. However, when running make test, it stopped at mod2pi unit test

ERROR: assertion failed: |totalErrNew - 0.0| <= 1.7763568394002505e-11

totalErrNew = 12.56641004881809

0.0 = 0.0

difference = 12.56641004881809 > 1.7763568394002505e-11

in error at error.jl:22

in test_approx_eq at test.jl:109

in testModPi at mod2pi.jl:182

in runtests at /home/mickey/Sources_ML/julia/test/testdefs.jl:5

in anonymous at multi.jl:855

in run_work_thunk at multi.jl:621

in anonymous at task.jl:855

while loading mod2pi.jl, in expression starting on line 184

ERROR: assertion failed: |totalErrNew - 0.0| <= 1.7763568394002505e-11

totalErrNew = 12.56641004881809

0.0 = 0.0

difference = 12.56641004881809 > 1.7763568394002505e-11

in anonymous at task.jl:1367

while loading mod2pi.jl, in expression starting on line 184

while loading /home/mickey/Sources_ML/julia/test/runtests.jl, in expression starting on line 35
Issue 1:
Dear julia community, when running eval on an expressions of an expression the typ information is unexpactedly lost:

> expr1 = :(sin(1))
> expr1.typ = Float32
> print(expr1)
sin(1)::Float32
> expr2 = Expr(:quote, expr1)
> eval(expr2).typ
Any

Julia: 0.5.1

Operating System: Windows 10

Issue 2:
I thought that a QuoteNode as meant as a bulletproof way to be able to shield an expression from the compiler poking into it while e.g. returning it from a macro. But consider the following code with a macro which wraps an expression in a QuoteNode and returns it:

macro l()
QuoteNode(Expr(:block, (Expr(:line,42,:none)), :(f(x))))
end
show(typeof(@l().args[1]))

This prints LineNumberNode, which means that the Expr(:line,42,:none) has turned into a LineNumberNode.

Should this be corrected, or do I misunderstand the intent of QuoteNode? If I do, does there exist a bulletproof way to shield an expression from the compiler?
Issue 1:
Electron version: v1.4.2

Operating system: masOS 10.11.6 (El Capitan)

When an window that has nodeIntegration: false tries to open a Facebook login or share window, the window can not be closed. Neither with operating-system provided closing methods (close button, cmd+w) nor from the window itself (window.close()) is the window closeable. The Facebook window can also not be reloaded (cmd+r or window.location.reload() do nothing). There are no errors logged (neither windows nor to the main process).

Steps to reproduce:

Given the example app below, start it with electron .

Click on "Facebook"

The first time Facebook will prompt for login

Log in to Facebook

Try closing the Facebook popup window (might need to restart the application before this to see the bug happening)

Example app:

index.html:

<a href="https://www.facebook.com/sharer/sharer.php?u=http://electron.atom.io/" target="_blank">Facebook</a>
<a href="about:blank" target="_blank">Blank</a>

main.js:

'use strict'

const electron = require('electron')
const app = electron.app
const BrowserWindow = electron.BrowserWindow

var mainWindow = null

app.on('ready', function() {
mainWindow = new BrowserWindow({
width: 1290,
height: 800,
webPreferences: {
nodeIntegration: false
}
})

mainWindow.loadURL(`file://${__dirname}/index.html`)
})

package.json

{
"name": "no-facebook",
"private": true,
"version": "1.0.0",
"main": "main.js"
}

Issue 2:
Current behavior of beforeunload event in Electron may break existing web pages. However, changing the behavior according to the spec may break existing Electron apps.

This is a tradeoff proposed by @deepak1556 in #2481 to make both sides happy:

// do what Electron does currently: unload the page immediately.
window.addEventListener('beforeunload', function(ev) { ev.returnValue = 'true' });
// do what Electron does currently: prevent the unload.
window.addEventListener('beforeunload', function(ev) { ev.returnValue = 'false' });

// do what the spec says: ask the user for confirmation if the string is not empty
window.addEventListener('beforeunload', function(ev) { ev.returnValue =
a_string_other_than_true_false });

Non-string values, specifically true/false, are converted to their string forms.

If window.onbeforeunload is used instead, the return value of the handler has same effect of ev.returnValue.

A remaining question is what to do with ev.preventDefault(). The spec says the UA should ask the user for confirmation. However my test showed that Electron 0.30.4 on Windows allows reload even if ev.preventDefault() is called. So I think it is OK to implement ev.preventDefault() according to the spec?
Issue 1:
I just missed being able to drag and drop my selection. When one attempts to drag a selection, Atom just makes a new selection, beginning at the point of the drag and ending at the point of the drop. It should be possible to drag and drop the selection around in the current buffer and between buffers. For the latter, hovering above a buffer's tab should change the active buffer to there. This would make reorganizing content more intuitive by giving the user visual aid of what is being moved and where to.

Issue 2:
I was sure an issue was already opened for this, but can't find it now.

Halp ticket:

support/5124ebc4cfa211e3871387e11a229b02

Would be cool if it was possible to select some text and then drag-and-drop it to some other place.
Issue 1:
Proposed new feature or change:

Tensorflow and jax extend the numpy dtype system to include bfloat16. (see: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/lib/core/bfloat16.cc)

I'm trying to scope out the possibility of upstreaming this into numpy.

There is currently an eigen dependency, but I think this could probably be avoided because it is only use to convert to and from float32 and check for nans.

Is this the sort of change that numpy would be interested in accepting?

There are more accelerator floating point datatypes coming in the future, and we would probably want to add them to numpy as well.

eg:

E4M3 with 4 exponent bits, 3 mantissa bits, and 1 sign bit.

E5M2, with 5 exponent bits, 2 mantissa bits, and 1 sign bit

Issue 2:
Feature

Hi,

I am working at PaddlePaddle(chinese DL framework). We and other DL frameworks would extremely benefit from integrated bfloat16 numpy datatype. I have seen that TF added its own implementation and lately a standalone pip package bfloat16 was released.

I have also seen NEP 41, 42, 43 which from what I understand will allow adding new, user-defined datatypes. Are you guys planning to integrate bfloat16 into core numpy? If you don't have the bandwidth to do that, is there anyone that can guide me how to implement that so I can make a PR? And how are these NEPs going?
Issue 1:
I was going through the "Create your first page in Symfony" tutorial, and I noticed I was always getting a "No route found for "Get /lucky/number"" type exception; however I was certain everything I coded was correct. After cutting and pasting the sample code (which was identical), I noticed it worked.

The problem is here:

/**
* @Route("/lucky/number/{count}")
*/

Whereas this works:

/**
* @Route("/lucky/number/{count}")
*/

The difference is the first annotation has a tab in front of it. This is the bug! Seems to have an issue with tabs.

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.2.9

Doctrine ORM
2.5.6

Hi,

I'm using doctrine "joined" table inheritance, using the annotations in this way

* @ORM\InheritanceType("JOINED")
* @ORM\DiscriminatorColumn(name="joined_type", type="string")

Everything wotks fine when I create the entries, but when I try to get results from database with a simple findAll(), I get a duplicated property id for the entries of the inherited type, in this case "MoreText":

I'm not really expert but I just followed the doctrine documentation for table inheritance, and this is not the first time I use it, so I think that it can be a bug.

Thank you
Issue 1:
Migrated issue, originally created by jvanasco (@jvanasco)

There doesn't seem to be a (public) way to find out if a path has been registered to a query for eager loading. (A non-public way seems to be query.__dict__['with_options'])

I propose an enhancement to the Query API, which allows a query to be queried for the status of eager loads.

In the simplest concept, it would just return a dict where the keys are a stringified path, and the values are the type of load (joinedload vs subqueryload vs contains_eager). If there is no eager loading for a given relationship, then the key is absent.

print q.registered_eagers()
> {'foo': 'joinedload', 'foo.bar':' subqueryload', 'foo.biz': 'contains_eager'}

The use-case is when dealing with generative queries that are loading relationships several layers deep; it becomes increasingly hard to ensure you have a load-strategy for each intermediary relationship..

Issue 2:
Migrated issue, originally created by Michael Bayer (@zzzeek)

given issues like #3223 and the openstack issues with model_query(), here's a sketch of an idea:

@event.listens_for(EventedQuery, "before_compile", retval=True)
def append_order_by(new_query):

if inspect(new_query).selects_against(MyClass).has_any():
for insp in inspect(new_query).selects_against(MyClass).all_aliases():
new_query = new_query.order_by(insp.entity.whatever)
return new_query

with this extension we'd need to identify specific use cases (since we see them all the time anyway) and add them to the docs of this extension as covered use cases. So the docs here need lots of recipes and they need to be tested.
Issue 1:
When you maximize a window and then try to drag it down from the border (or in my case a header div with -webkit-app-region: drag; style), the window will unmaximize, but instead of getting the unmaximize event you'll just get the resize event.

If you do the same using the restore button (either through the border or using the taskbar menu item), you will get the unmaximize event and then the resize event, like you get with the rest of the size-change events.

This was tested on Windows 8.1 (64 bit) using Electron v0.30.2.

Issue 2:
On Windows, BrowserWindow maximize & unmaximize events are not triggered when maximizing/unmaximizing a atom-shell window by drag & drop.

atom-shell is really great, much better than NW.js (I used NW for quiet a long time), so congratulations to all contributors !
Issue 1:
using the following html form

<h1>Debug Form</h1>
<form action="/debug" method="POST">
<input name="item[1][name]" value="" />
<input name="item[2][name]" value="" />
<button type="submit">test</button>
</form>

to the following flask application method / view

@app.route('/debug', methods=["GET","POST","PUT","PATCH","DELETE"])
def debug_info():
return jsonify({"data":request.data,"formdata":request.form})

I get

{
"data": "",
"formdata": {
"item[1][name]": "fdhnnhdsfsdslkkl",
"item[2][name]": "djdfhdjfh"
}
}

I expected to see

{
"data": "",
"formdata": {
"item":[
{
"name": "fdhnnhdsfsdslkkl"
},
{
"name": "djdfhdjfh"
}
]
}
}

The first and actual output requires further, more explicit parsing, from a sub-optimal data structure to achieve a nice dictionary; but I cannot see how the flat structure of the request.form object could be helping anyone...

Issue 2:
Rewrite the tutorial and corresponding example, taking into account new and common patterns for Flask.

example

tutorial
Issue 1:
Since Modernizr only inserts the relevant browser prefix on the client render, there's a mismatch with the unprefixed server side render. As alluded to in #591 , this causes the following warning in react:

Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server...

I don't see any easy fixes for this, and it's quite a biggie, which is saddening. Obviously getting this whole module to move away from inline styles is a no-go.

Pure speculation: maybe it's possible to patch the way react handles styles, so that when a component is supplied with style={{'transition': 'all 1s'}}, it's prefixed at the same time it's rendered to HTML, so it becomes:

style="-webkit-transition: all 1s; transition: all 1s;"

instead of simply

style="transition: all 1s;"

Issue 2:
I have a React app, that runs on the server and in the clients browser.

When I upgrade to v0.8.0, React gives me the "Expected html differs from the given markup" warning, because there are differences in the inline style definitions. For example:

Server renders:

style="...; user-select: none;.."

But the client (Chrome in this case) renders

style="...; -webkit-user-select: none;.."

While it is nice to not have to worry about vendor prefixes, the correct handling of them creates those differences. Does anyone have an idea on how to fix (or workaround) this? I dont want to send the client, perfectly good markup, and then let React rebuild half of it, because of that.

Maybe include all prefixes necessary? Might be tricky as well..

Or do I have to exclude all css that needs to be prefixed back into style sheets?
Issue 1:
Hello,

I am looking at the gradient computation in Gaussian Process Kernel module. My understanding is that there we are trying to compute $$\partial{K(x,x')}{\partial \theta}$$, where $$\theta$$ is a hyperparameter. However, I am not sure that is what is computed in the code:

For example, the ConstantKernel has:

scikit-learn/sklearn/gaussian_process/kernels.py

Line 1013
in
f339609

self.constant_value,

While I think instead of filling in the constant value, we should fill in just 1.

Another example is the RBF kernel,

scikit-learn/sklearn/gaussian_process/kernels.py

Line 1232
in
f339609

elif not self.anisotropic or length_scale.shape[0] == 1:

I think the gradient should be further divided by the length_scale.

It seems to me that rather than computing the gradient, we are computing gradient * hyperparameter here. Am I missing something?

Thanks!

Junteng

Issue 2:
Description

As discovered in #8373, the docstring states that if eval_gradient is true, the gradient with respect to the kernel hyperparameters is returned, whereas actually it returns the gradient with respect to the log-transformed hyperparameters. As an example:

Writing the DotProduct kernel as a function of theta instead of sigma_0 with sigma_0 = exp(theta) gives us:

k(x_i, x_j) = sigma_0 ^ 2 + x_i \cdot x_j = exp(theta) ^ 2 + x_i \cdot x_j = exp(2*theta) + x_i \cdot x_j

Now the gradient with respect to theta is :

2*exp(2*theta) = 2*exp(theta)^2 = 2*\sigma_0^2
Issue 1:
Adapting from #6029 as an example:.

Assuming tsd is installed (npm install -g tsd)

Run

`tsd install react-global react-bootstrap --save`

tsconfig.json:

{
"compilerOptions": {
"target": "es5",
"module": "amd",
"jsx": "react"
},
"compileOnSave": false,
"files": [
"./main.tsx",
"./typings/tsd.d.ts"
]
}

main.tsx:

import * as React from 'react';
import { render } from 'react-dom';
import { Button } from 'react-bootstrap';

class App extends React.Component<{}, {}> {
render() {
return < /*1*/
}
}

render(</*2*/ />, document.getElementsByTagName("entrypoint")[0] );

Notice that at /*1*/ and /*2*/, you'll get App, but not Button.

Issue 2:
It looks like it's also missing in any other JSX-expression context.
Issue 1:
I've been using zeit's ncc to slim down and build our transpiled APIs into tiny, minified, individual scripts that run without any node_modules present on our servers/containers. It's absolutely fantastic.

I tried to us ncc w/ NextJS, but probably lack the requisite knowledge of understanding how nextJS builds work, and what is built into the output.

My goal: A single, transpiled/built file (or set of files w/ an exposed entrypoint script) that I can run without needing node_modules installed/present on my application servers/containers, which I can simply invoke with a command like:

"NODE_ENV=production node --require 'dotenv/config' ./dist/index.js"

We use a custom server with our nextJS app, but it's written in vanilla JS, and doesn't require transpilation, webpack, or babel.

It does, however, have a handful of dependencies including a redis client and express.

I was thinking that maybe the correct thing to do is use ncc for the server, and next build for the client, and then just runn the ncc'ed server file?

If someone could point me in the direction of the best resolution, that would sincerely save me days of failed attempts and wasted hours.

Thank you!! :)

Issue 2:
Hi, according to the v3-beta docs, next.js support exporting to static html, and apparently also support "dynamic routes". Was wondering if there was some documentation on how to create dynamic routes when exporting static html.

This is a way to run your Next.js app as a standalone static app without any Node.js server. The export app supports almost every feature of Next.js including dynamic urls, prefetching, preloading and dynamic imports.

I've added this to my next.config.js but it doesn't seem to work.

exportPathMap: () => {
return {
"/": { page: "/" },
"/account/:id": { page: "/account" }
}
}

I also tried "/account/*", but no luck. Any help would be greatly appreciated.

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