WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
NOTE: Only file GitHub issues for bugs and feature requests. All other topics will be closed.

I'm now using TF version 0.10.0 installed from source.

I'm not sure its a bug or intended implementation but the embedding_lookup() returns zeros when the index exceed embedding matrix size. For example,

import tensorflow as tf
import numpy as np

embd_mat = np.linspace(1,10,10).reshape([10,1])*np.array([1,2,3]).reshape([1,3])
idx = np.linspace(0,19,20)

embd_in = tf.placeholder(tf.float32,[10,3])
idx_in = tf.placeholder(tf.int32,[20])

output = tf.nn.embedding_lookup(embd_in,idx_in)

with tf.Session() as sess:
sess.run(tf.initialize_all_variables())

embd_out = sess.run(output,feed_dict={embd_in:embd_mat, idx_in:idx})

print embd_out

The output of above code is,

[[ 1. 2. 3.]
[ 2. 4. 6.]
[ 3. 6. 9.]
[ 4. 8. 12.]
[ 5. 10. 15.]
[ 6. 12. 18.]
[ 7. 14. 21.]
[ 8. 16. 24.]
[ 9. 18. 27.]
[ 10. 20. 30.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]]

Is there any reason it returns zeros not raises an error?

I think that case happens only when programmers make a mistake.

Unless there is any specific reason which I don't know of, I think it should raise a value error that the index is exceeding the matrix size.

Issue 2:
NOTE: Only file GitHub issues for bugs and feature requests. All other topics will be closed.

I wrote an issues a month ago about the same problem #5260

I recently update the TF to latest master branch(0.11.head) without any custom modification and the commit hash is 55dbc54

The tf.embedding_lookup() still do not raise error even though the index is exceeding the embedding matrix size. It automatically fills zeros as you can see in the below example.

I tested same code with two different machines and the result was same.

In the previous issue(#5260), @strategist333 said it raise an InvalidArgumentError in binary release.

But when I tested TF installed from source, it didn't...

import tensorflow as tf
import numpy as np

embd_mat = np.linspace(1,10,10).reshape([10,1])*np.array([1,2,3]).reshape([1,3])
idx = np.linspace(0,19,20)

embd_in = tf.placeholder(tf.float32,[10,3])
idx_in = tf.placeholder(tf.int32,[20])

output = tf.nn.embedding_lookup(embd_in,idx_in)

with tf.Session() as sess:
sess.run(tf.initialize_all_variables())

embd_out = sess.run(output,feed_dict={embd_in:embd_mat, idx_in:idx})

print embd_out

The output of above code is,

[[ 1. 2. 3.]
[ 2. 4. 6.]
[ 3. 6. 9.]
[ 4. 8. 12.]
[ 5. 10. 15.]
[ 6. 12. 18.]
[ 7. 14. 21.]
[ 8. 16. 24.]
[ 9. 18. 27.]
[ 10. 20. 30.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]
[ 0. 0. 0.]]
Issue 1:
Description

I find the connections view often leads to confusion because connections defined as environment variables and in a secrets backend are not displayed. This is not stated clearly.

I suggest to:

Display connections set via environment variables (and hide the edit controls for those connections). This could also help debugging a URI string if you could see the URI components broken down in the connection view.

Display an info message in the connections view in case a secrets backend is configured stating that those connections are not visible in the webserver.

Use case/motivation

Motivation: having to explain over and over that only connections defined in the Airflow metastore are visible in the webserver.

Related issues

No response

Are you willing to submit a PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Issue 2:
Apache Airflow version: 1.10.9

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release): ubuntu 18.04

Kernel (e.g. uname -a):

Install tools:

Others:

What happened: Eventlet with CeleryExecutor not working in Airflow 1.10.9 version

log.txt

I notice when I tried switching celery pool option to eventlet the worker doesn’t seem to be picking up tasks.

Attached the snippet of logs.

What you expected to happen:

How to reproduce it: Start the airflow celery workers with Eventlet

Anything else we need to know: Attached the logs
Issue 1:
Feature request

When optimization.sideEffects is set to true, the code will not be analyzed for side effects during production mode construction，

The sideEffects field in package.json will still be used

Whether sideEffects in package.json should be ignored when optimization.sideEffects is true and in production mode

What is the expected behavior?

Whether sideEffects in package.json should be ignored when optimization.sideEffects is true and in production mode,

but when production model and optimization.sideEffects:true，Still use package.json's sideEffects

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

https://github.com/galaxy-s10/issue-demo/blob/master/demo1/webpack.config.js

How should this be implemented in your opinion?

Are you willing to work on this yourself?

emm

Issue 2:
What is the current behavior?

ERROR in TypeError: __webpack_require__(...) is not a function

- index.ejs:1205 Object.../node_modules/webpack/buildin/harmony-module.js
/home/adam/apps/memory-n-back/web/index.ejs:1205:1

- index.ejs:622 __webpack_require__
/home/adam/apps/memory-n-back/web/index.ejs:622:30

- index.ejs:46 fn
/home/adam/apps/memory-n-back/web/index.ejs:46:20

- index.ejs:1197 Object.../node_modules/webpack/buildin/global.js
/home/adam/apps/memory-n-back/web/index.ejs:1197:1

- index.ejs:622 __webpack_require__
/home/adam/apps/memory-n-back/web/index.ejs:622:30

- index.ejs:46 fn
/home/adam/apps/memory-n-back/web/index.ejs:46:20

- index.ejs:1189 Object.../node_modules/lodash/lodash.js
/home/adam/apps/memory-n-back/web/index.ejs:1189:1

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

checking out this commit from my repo and running npm start

The thing is I don't know what is causing the crash, because as u can c above, the logs are not very informational, hence I'm opening this issue and not asking on SO

What is the expected behavior?

Work with tree shaking and not crashing

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

OS: ubuntu 16.04

webpack: 2.1.0-beta.25

webpack-dev-server: 2.1.0-beta.0

it crashes on both webpack and dev server
Issue 1:
I'm new to typings, but it seems as if the Knex SchemaBuilder methods (https://github.com/borisyankov/DefinitelyTyped/blob/master/knex/knex.d.ts#L303) are returning the wrong type. They return Promise while the knex source has the methods just returning a reference to 'this' (https://github.com/tgriesser/knex/blob/master/lib/schema/builder.js#L27).

I don't see any references to promises of any kind in there. I'd be happy to create a PR, but I wanted to make sure I wasn't completely wrong here.

Thanks!

Issue 2:
The following should compile but doesn't:

class ActiveState {
restrict = 'A'
constructor() {
}
}

angular.module('foo').directive('foo', ActiveState);
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

I am loading some application configurations from a json file just before the application loads using APP_INITIALIZER shown below:

@Injectable()
export class ConfigService {
private _config: any;
constructor(private http: Http) {
}

load(): Promise<any> {
let promise: Promise<any> = new Promise((resolve: any) => {
this.http.get('app/config/appConfig.json').map(res => res.json())
.subscribe(config => {
this._config = config;
resolve(true);
});
});
return promise;
}

get(key: any) {
return this._config[key];
}
}

export function initConfiguration(configService: ConfigService): Function {
return () => configService.load();
}

@NgModule({
imports: [
//Some imports here.
],
declarations: [AppComponent],
bootstrap: [AppComponent],
providers: [
{
provide: APP_INITIALIZER,
useFactory: initConfiguration,
deps: [ConfigService],
multi: true
}
]
})
export class AppModule { }

There are few services which use the loaded configurations by calling the get method defined in ConfigService. It was all working fine but after upgrading to 2.4.8, I can see that the get function is invoked before the configurations are loaded which produces an error.

Expected behavior

ConfigService.load should run in blocking mode like it used to work until 2.4.7

Please tell us about your environment:

OS: Windows 10 Pro

IDE: Visual Studio Code

Angular version: 2.0.8

Browser: [all]

Language: [TypeScript 2.1 | ES6]

Issue 2:
It would be nice if we could tell angular not to destroy components when we navigate out of them, even if the next component is of a different type. This could be useful, for example, when building a window management system, where users can navigate through different windows (components) without

the need for recovering the whole state.

The existing canReuse hook is not useful for this use case, since it only allows us to reuse components if the previous and the next component have the same type.

Code example:

@Component({...})
class ExampleComponent {
canDestroy() { // or some other name
return this.closeButtonClicked;
}
}
Issue 1:
Challenge Create a Form Element has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}

.thick-green-border {
border-color: green;
border-width: 10px;
border-style: solid;
border-radius: 50%;
}

.smaller-image {
width: 100px;
}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<p>Click here for <a href="#">cat photos</a>.</p>

<a href="#"><img class="smaller-image thick-green-border" alt="A cute orange cat lying on its back. " src="https://bit.ly/fcc-relaxing-cat"></a>

<p>Things cats love:</p>
<ul>
<li>cat nip</li>
<li>laser pointers</li>
<li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
<li>flea treatment</li>
<li>thunder</li>
<li>other cats</li>
</ol>
<form action="/submit-cat-photo"><input type="text" placeholder="cat photo URL"></form>

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-bring-your-javascript-slot-machine-to-life has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When typing the solution, typing "$" "(" automatically generates a closing parenthesis, then typing the next "$" leaves "$($)" in the window, which is executed automatically, and freezes the page. From the behavior, I would assume an infinite loop. Copy-pasting the code suggestion bypasses the issue.

Reloading the page, once the error has occurred, reloads the problematic code -- there is no user-accessible way to force a reset when the page isn't responding
Issue 1:
Ran into an issue with the accordion. When you click on toggle headings too quickly, it doesn't always collapses all the groups properly, in this example, I've clicked on the "Collapsible Group Item # 2" then "Collapsible Group Item # 1", but it opened both of them at the same time.

Using latest version of Google Chrome (Version 37.0.2062.120), probably something to do with transition not being picked up properly.

Issue 2:
Step 1. Navigate to this page: http://getbootstrap.com/javascript/#collapse

Step 2. Click on one of the links that trigger opening of the accordion sections (ie. Collapsible Group Item #1)

Step 3. Before the section's opening animation has a chance to complete (the one from 'Step 2' above) click on a different link to trigger opening a second panel (ie. Collapsible Group Item #2)

At this point you should see that you have two accordion panels open at the same time.
Issue 1:
I get the warning message

W external/org_tensorflow/tensorflow/compiler/xla/service/hlo_pass_fix.h:49] Unexpectedly high number of iterations in HLO passes, exiting fixed point loop.

each time I evaluate grad(odeint) in the following code. The forward system has 4 * 4 * 64 = 1024 dimensions, and the dynamics function has 1 * 1 * 64 * 64 = 4096 parameters (so the adjoint system would have about 5121 dimensions). I also modified odeint to count NFE on the forward pass (which in this case is only 7).

Not really sure what this warning message means, but I suspect it might be affecting the performance of my code. Any insights into this would be greatly appreciate, and I'm happy to create a more stripped down example (e.g. without the haiku dependency) if needed.

XLA dump

Issue 2:
I am getting an error/warning message when using clip_grads. The message is:

"external/org_tensorflow/tensorflow/compiler/xla/service/hlo_pass_fix.h:49] Unexpectedly high number of iterations in HLO passes, exiting fixed point loop."

Does anyone know what this means, or how to call clip_grads so it doesn't occur? Does it affect any results?

In the code, with option == 1 (no jit for clip_grads), the message occurs five times. The number is dependent on the number of dense layers in the neural network. If option==1 (with jit), the message occurs only once. I assume the others are suppressed.

Incidently, apart from clip_grads, I also get the message (once) if I change the neural net to one input and send X[:,0] to it in net_apply().

And I also get the same message when I call odeint().

I'm using jax version '0.1.62' and jaxlib version '0.1.43' on the GPU.

from jax import grad
from jax import random
from jax import jit

from jax.experimental import stax
from jax.experimental.stax import Dense, Tanh, BatchNorm
from jax.experimental import optimizers

# setup neural network -------------------------------
L = 2
net_init, net_apply = stax.serial(
Dense(L), Tanh,
Dense(L), Tanh,
Dense(2)
)

rng = random.PRNGKey(0)
rng, subkey = random.split(rng)

out_shape, net_params = net_init(subkey, (-1, 2))
opt_init, opt_update, get_params = optimizers.adam(step_size=.001)
opt_state = opt_init(net_params)

# option for jit clip_grads --------------------------
def clip(gr):
return optimizers.clip_grads(gr, 4)

clip_jit = jit(clip)

# loss function --------------------------------------
def loss(params, X):
ans = net_apply(params, X[:,0:2])
return 1. # return dummy loss

# step function --------------------------------------
def step(opt_state, X):
params = get_params(opt_state)

gr = grad(loss, argnums=(0,)) (params, X)
print(len(params))
# try different options
option = [0,1,2][2]
if option == 0:
gr = optimizers.clip_grads(gr, 4)

elif option == 1:
gr = clip_jit(gr)

elif option == 2:
pass

return 1. # return dummy value

# setup data -----------------------------------------
rng, subkey = random.split(rng)
N = 50
X = random.normal(subkey, (N, 10))

# call step ------------------------------------------
for ii in range(2):
result = step(opt_state, X)
Issue 1:
There seems to be some path problems when specifying a custom Access Denied template and extending a layout. It seems this has been reported here...

http://trac.symfony-project.org/ticket/9502

More details can be seen in the comments of this blog article...

http://www.michelsalib.com/2011/03/advance-customization-of-the-403-error-page-in-symfony2/

Has there been any resolution to this issue?

Issue 2:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
yes

Symfony version
4.1

It would be nice allow inject tagged services as ServiceLocator instead of iterable. For example we have set of report generators, all of them implements ReportGenerator interface. We have tagged them with tag app.report_generator using autoconfigure, but we require compiler pass for creating ServiceLocator with them.
Issue 1:
The weekly build with nightly wheels from numpy and pandas

has failed. Check the logs for any updates that need to be

made in matplotlib.

https://github.com/matplotlib/matplotlib/actions/runs/3254383814

Issue 2:
The weekly build with nightly wheels from numpy and pandas

has failed. Check the logs for any updates that need to be

made in matplotlib.

https://github.com/matplotlib/matplotlib/actions/runs/3163174215
Issue 1:
VSCode Version:1.1.0-alpha

OS Version: Mac

Regarding test item #5753

Just found this issue a day after I did my testing.

Steps to Reproduce:

In a bower.json file, type in a package in the dependency section (I used lodash as the package). It will auto-complete and give you "lodash":"latest"

Try changing latest to something else, like ^1.0.0

Note that it does not give you a suggestion like it would in a package.json file.

Issue 2:
VSCode Version: 0.10.12-alpha

OS Version: Windows10

Steps to Reproduce:

Create Asp .net core empty project in visual studio.

Add some directories under wwwroot folder for client code like JS.

Add new item to manage client lib and add bower.json file.

Add some client side lib in to bower.json under dependency section like below:

Actual: Not getting intellisense for version #.

Expected:
Issue 1:
System information

OpenCV => 4.0.1 (Exactly, I am using OpenCV lib included in OpenVINO R5 2018 release.)

Operating System / Platform => Windows 64 Bit

Compiler => Visual Studio 2015

Detailed description

Memory increases quickly as i run my code.

My code is really simple: Create 2000 threads, and in each thread try to create a UMAT.

#include "stdafx.h"
#include <iostream>
#include <opencv2/core.hpp>
#include <opencv2/imgproc.hpp>
#include <opencv2/highgui.hpp>
#include <mutex>
#include <condition_variable>
#include <atomic>

#define DECODECORE_ROI_IMAGE_WIDTH 480
#define DECODECORE_ROI_IMAGE_HEIGHT 640
unsigned char resized[DECODECORE_ROI_IMAGE_WIDTH * DECODECORE_ROI_IMAGE_HEIGHT];

void TestThread()
{
std::cout << "TestThread started\n";

cv::Mat srcMat(DECODECORE_ROI_IMAGE_WIDTH, DECODECORE_ROI_IMAGE_HEIGHT, CV_8UC1, resized);
cv::UMat uMsrcImg = srcMat.getUMat(cv::ACCESS_READ);
uMsrcImg.release();
srcMat.release();
}
int main()
{
for (int i = 0; i < 2000; i++)
{
std::thread finderThread = std::thread(TestThread);
finderThread.detach();
std::cout << "i is " << i << "\n";
}
return 0;
}

Issue 2:
OpenCV => 3.3.0

Operating System / Platform => Arch Linux (4.12.13-1-ARCH SMP PREEMPT x86_64 GNU/Linux)

Compiler => gcc 7.2.0 and clang 5.0.0

Detailed description

It seems that a significant portion of memory is leaked in every thread.

The following code snippet consumes cca 100MB/s.

Steps to reproduce

#include <opencv2/opencv.hpp>
#include <future>
int main()
{
while(true) {
std::async(std::launch::async, []() { cv::Mat::zeros(1, 1, CV_32FC3); }).wait();
}
}
Issue 1:
My issue is taking a warning, while it is not logical.

Reproducing code example:

import numpy as np
from scipy.stats import pearsonr, spearmanr
x = np.asarray([0.20411998265592482, 0.07918124604762482])
y = np.asarray([0.017448610113466535, 0.012129956392826626])
print(pearsonr(x,y))

Warning message:

/usr/local/lib/python3.5/dist-packages/scipy/stats/stats.py:3020: RuntimeWarning: invalid value encountered in double_scalars
prob = _betai(0.5*df, 0.5, df/(df+t_squared))

Output

Below + warning above.

(0.9999999999999999, nan)

Expected Output

I expect getting no warning. in addition p-value must be 0 not nan!

(1.0, 0.0)

Scipy/Numpy/Python version information:

1.1.0 1.14.5 sys.version_info(major=3, minor=5, micro=2, releaselevel='final', serial=0)

Issue 2:
Hi,

This is an issue to mention that the implementation of pearsonr is not tolerant to overflows.

scipy/scipy/stats/stats.py

Line 3032
in
b7865dd

r_den = np.sqrt(_sum_of_squares(xm) * _sum_of_squares(ym))

Pearsonr is stable by a multiplicative coefficient. When this coefficient is too high, the computation fails with an error message:

scipy/stats/stats.py:3013: RuntimeWarning: overflow encountered in double_scalars
r_den = np.sqrt(_sum_of_squares(xm) * _sum_of_squares(ym))

The sum of squares product here is too high. Need to adapt the computation so that this partial computation is avoided.

To reproduce (starting from the documentation example in master branch):

import numpy as np
from scipy import stats

a = np.array([0, 0, 0, 1, 1, 1, 1])
b = np.arange(7)
pearson1 = stats.pearsonr(a, b)
a1 = a * 1e90
b1 = b * 1e90
pearson2 = stats.pearsonr(a1, b1)
print(pearson1 , pearson2)
assert(np.allclose(pearson1[0] , pearson2[0]))
assert(np.allclose(pearson1[1] , pearson2[1]))

Versions :

output of 'import sys, scipy, numpy; print(scipy.version, numpy.version, sys.version_info)'

1.1.0 1.14.5 sys.version_info(major=3, minor=6, micro=5, releaselevel='final', serial=0)

Also performed a lookup to see if a similar issue already exists.
Issue 1:
Firefox specific bug

Due to #6570 react > 15.0.3 populates every element with property is="null"

That's caused by weird Firefox behaviour checking the args number of document.createElement.

e.g.:

document.createElement('a', '') => <a is="">

document.createElement('a', null) => <a is="null">

document.createElement('a', undefined) => <a is="undefined">

Verified with Firefox v46.0.1, react@15.0.3-dev and react@15.1.0

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

Looks like a bug.

What is the current behavior?

I have a simple context set up to manage a global store. When implementing this context as a functional component with the useState hook, calls to my setStore function from inside a timeout are seeing old versions of the store and updating it incorrectly.

Possibly a duplicate of #14010 but I don't see why the value of my store should be getting saved by the closure. The closure created by the setTimeout can't see the value of store, so it shouldn't be captured.

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:

https://codesandbox.io/s/mnxr754oy

Refresh the page in the sandbox and click the "Increment otherVal" button a few times. After 3 seconds, a timeout fires in ChildThree that sets myVal to 42 but doesn't touch otherVal; however, the changes made by incrementing otherVal get blown away. This doesn't happen with changes prompted by onClick events (as you can test by clicking "Set myVal to 42" on the bottom), only timeouts.

The context implementation is in store.js. If you swap out the functional StoreProvider with the commented out class version, everything works as expected.

It's possible that I'm doing something wrong with how my closures are being created in the functional StoreProvider but I can't see why.

What is the expected behavior?

The context provided function setStore should be seeing the correct copy of the state returned by the hook.

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

Tested in Chrome/Firefox/Edge on React 16.9.0-alpha.1
Issue 1:
With #222 merged any ideas how to add a loader for TypeScript in next.config.js?

I've tried adding a TypeScript specific loader like this

const path = require('path');
const nextPagesDir = path.join(__dirname, 'pages');

const typescriptLoader = {
test: /\.ts(x?)$/,
loader: ['ts-loader'],
exclude: /node_modules/,
include: [
nextPagesDir
]
};

module.exports = {
webpack: (config) => {
config.module.rules.push(typescriptLoader);
return config;
}
}

but assume additional changes need to be made as well as additional entries for hot loading etc.

Another question is should the TypeScript loader be used in with babel e.g.

loaders: ['babel-loader', 'ts-loader']

If so I'd need to apply the same babel options as in webpack.js.

Issue 2:
this looks awesome but I also really like TypeScript.

is there any way to integrate typescript into the workflow?