WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Running the simple iOS example provided by this repository will crash if I target any iPhone 4s/iPhone 5 simulator. The app will crash immediately at launch, before entering didFinishLaunchingWithOptions. The last call I can identify in the debugger is usually tensorflow::internal::LogMessageFatal::~LogMessageFatal:.

The crashes happen on iPhone 5 simulators running iOS 10.2, 9.3, and 9.1. And on iPhone 4s simulators running iOS 9.3, 9.1, and 8.4.

I can reproduce this behavior with other TensorFlow iOS apps.

The same apps that crash in an iPhone 4s/iPhone 5 simulator, will build & run fine on other simulators & devices, e.g. on iPad Air simulator running 10.2, a physical iPad Air running 10.2, or physical iPhone 6s Plus running 10.2. Tests on a device farm including iPhone 4s & iPhone 5 devices were inconclusive… I’m seeing a very similar crash happen, mostly affecting devices running 9.3.5, but the devices/iOS combos that fail on physical devices are slightly inconsistent from run to run (in the simulator the same devices crash 100% of the time no matter what OS I use, and from run to run).

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?

This issue is the only hit I get, but seems unrelated.

Environment info

Operating System: macOS Sierra 10.12.13

Commit hash: b393fd7 (master as of this writing)

Bazel Version:

Build label: 0.4.3-jdk7
Build target: bazel-out/local- fastbuild/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Dec 22 12:31:38 2016 (1482409898)
Build timestamp: 1482409898
Build timestamp as int: 1482409898

Minimal reproducible example

Prepare the simple iOS example provided by Tensorflow

$ git clone https://github.com/tensorflow/tensorflow.git
$ cd tensorflow
$ tensorflow/contrib/makefile/download_dependencies.sh
$ tensorflow/contrib/makefile/build_all_ios.sh
$ open tensorflow/contrib/ios_examples/simple/tf_ios_makefile_example.xcodeproj

Download the Inception graph per the instructions

Target the iPhone 5 simulator on iOS 10.2, and Run.

The app will crash before entering didFinishLaunchingWithOptions.

(If you target the iPad Air simulator on iOS 10.2, it will work.)

Issue 2:
Have I written custom code: N/A

OS Platform and Distribution: cpe:/o:centos:centos:7

TensorFlow installed from: pip install

TensorFlow version: 1.10

Bazel version: N/A

CUDA/cuDNN version: Cuda 9.0

GPU model and memory: 1080 Ti, 11G

Exact command to reproduce: N/A

Mobile device: N/A

I checked the roadmap says the new feature:

Eager execution

Use DistributionStrategy to utilize multiple GPUs and multiple TPU cores.
Distributed training support (multi-machine).
Performance improvements.
Simpler export to a GraphDef/SavedModel.

I am wondering whether tf 2.0 will consider synchronizing batchnorm statistics across multiple GPUs which is extremely helpful for segmentation and other task.

Similar issue as Synchronized BatchNorm statistics across GPUs
Issue 1:
The issue is a duplicate of scipy/scipy#4720

The document suggests that the parameter degree of freedom should be df >= 1 to use numpy.random.noncentral_chisquare. However, taking df = 1 raises error.

import numpy as np
df = 1
nc = 2
np.random.noncentral_chisquare(df, nc)

---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
<ipython-input-2-7c9f3f6a3a16> in <module>()
----> 1 np.random.noncentral_chisquare(df, nc)

mtrand.pyx in mtrand.RandomState.noncentral_chisquare (numpy/random/mtrand/mtrand.c:15618)()

ValueError: df <= 0

It makes me suspect that the random variate generation of the noncentral chi-square distribution with degree of freedom df and noncentrality parameter nc is implemented in numpy using a method similar to the following.

np.random.chisquare(df-1) + (np.random.standard_normal()+np.sqrt(nc))**2

However, this method is valid only for the case where df > 1 because with df = 1, it needs to generate a chi-square random variate with degree of freedom 0, which is not mathematically well-defined.

On the other hand, noncentral chi-square distribution is indeed mathematically well-defined for all df > 0. It simply requires a different algorithm for random variate generation if 0 < df <= 1, such as the following one:

np.random.chisquare(df + 2*np.random.poisson(nc / 2.0))

Issue 2:
Numpy's bool_ type seems to fail an isinstance check with the Python numbers.Integral ABC:

import numpy
import numbers
x = numpy.array([True])
print( isinstance(x[0],numbers.Integral) ) # -> False

I find this odd since Python's built-in bool passes:

print( isinstance(bool(x[0]),numbers.Integral) ) # ->True

Is this a bug?

My system information is:

PYTHON:

Python 2.7.5 (default, May 19 2013, 02:56:42)

[GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)] on darwin

NUMPY INSTALLED WITH PIP:

Downloading/unpacking numpy from https://pypi.python.org/packages/source/n/numpy/numpy-1.7.1.tar.gz#md5=0ab72b3b83528a7ae79c6df9042d61c6

Downloading numpy-1.7.1.tar.gz (2.8MB): 2.8MB downloaded

Running setup.py egg_info for package numpy

Running from numpy source directory.

non-existing path in 'numpy/distutils': 'site.cfg'

F2PY Version 2

blas_opt_info:

FOUND:

extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']

define_macros = [('NO_ATLAS_INFO', 3)]

extra_compile_args = ['-msse3', '-I/System/Library/Frameworks/vecLib.framework/Headers']

lapack_opt_info:

FOUND:

extra_link_args = ['-Wl,-framework', '-Wl,Accelerate']

define_macros = [('NO_ATLAS_INFO', 3)]

extra_compile_args = ['-msse3']
Issue 1:
When I open Atom, after updating to v0.192.0, it launches 7 processes, one of which runs this:

/usr/share/atom/atom --eval require('/usr/share/atom/resources/app/node_modules/coffee-cash/lib/coffee-cash.js').setCacheDirectory('/home/yajo/.atom/compile-cache/coffee');
require('/usr/share/atom/resources/app/node_modules/coffee-cash/lib/coffee-cash.js').register();
require('/usr/share/atom/resources/app/node_modules/coffeestack/index.js').setCacheDirectory('/home/yajo/.atom/compile-cache/coffee/source-maps');
require('/usr/share/atom/resources/app/src/task-bootstrap.js');

This process hangs my system eating all CPU and RAM available.

If I kill that process before it eats my computer, I can continue using Atom, but obviously it's not very comfortable.

I use Fedora 21 with the official RPM package from atom.io.

Issue 2:
When editing a file, after the editor was open for a little while, it started to consume all the CPU and steadily consume more RAM (until all the available RAM is consumed).

The command line of the runaway process was:

/usr/share/atom/atom --eval require('/usr/share/atom/resources/app/node_modules/coffee-cash/lib/coffee-cash.js').setCacheDirectory('/home/james/.atom/compile-cache/coffee'); require('/usr/share/atom/resources/app/node_modules/coffee-cash/lib/coffee-cash.js').register(); require('/usr/share/atom/resources/app/node_modules/coffeestack/index.js').setCacheDirectory('/home/james/.atom/compile-cache/coffee/source-maps'); require('/usr/share/atom/resources/app/src/task-bootstrap.js');

This behavior seems to have just emerged after I updated it to 0.192.0 this morning.
Issue 1:
Using Atom 0.183.0 on Windows 7 x64.

After atom updates, I become unable to double click files and have them open. The command line still works fine.

To fix:

Open regedit.exe

Navigate to HKEY_CLASSES_ROOT\Applications\atom.exe

Right-click (Default), click Modify...

Modify the text from C:\Users\Michael\AppData\Local\atom\app-0.181.0\atom.exe to C:\Users\Michael\AppData\Local\atom\app-0.183.0\atom.exe

Close regedit.exe

Close and reopen explorer.exe

Double clicking files works again!

Could this registry item be updated when atom is updated?

Issue 2:
Currently it is not so easy to assign atom as default editor on windows eg for all .css files

the path to atom.exe is changed with every update.

no exe in C:\Users\hebbet\AppData\Local\atom

Chrome has eg an chrome.exe in:

C:\Users\username\AppData\Local\Google\Chrome SxS\Application which starts chrome with the currect folder.
Issue 1:
I'm submitting a ... (check one with "x")

[x ] bug report
[ ] 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

Making a GET request with no body results in an exception of "Cannot read property 'toString' of null".

It seems in the commit e7a8e27 the text function now doesn't do the isPresent(this._body) e7a8e27#diff-c9b22b9d241f7ed55d13b39d1ccb333bL109 check causing the failure

It now falls through to here e7a8e27#diff-1239ed5b0c3fa3d870cb4005226ed5d6R56 when null causing the error.

Expected/desired behavior

Should be able to send a HTTP GET request with no request body.

Reproduction of the problem

So far, making a HTTP get request with an empty body reproduces the issue.

What is the expected behavior?

Should be able to send a HTTP GET request with no request body.

Angular version: 2.0.0-rc.5

Browser: Tested on [Chrome 52 | Safari 9.1 ]

Language: [TypeScript 1.8.10]

Issue 2:
Has it been considered exposing the typings for the angular2/test_lib module? Maybe even have it as top level module? Because I use some of the exposed methods in unit tests for the components I write, and I think that might be the case for many others, unless there is a plan for some other lib for unit tests.
Issue 1:
Context:

Playwright Version: 1.30.0

OS: macOS 13.0.1

Memory: 216.70 MB / 16.00 GB

Node: 18.13.0 - ~/.nix-profile/bin/node

Yarn: 1.22.19 - ~/.nix-profile/bin/yarn

npm: 8.19.3 - ~/.nix-profile/bin/npm

Bash: 3.2.57 - /bin/bash

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and

that we can run and debug locally. For example:

const getPort = (await import("get-port")).default;

Describe the bug

I'm trying to import an ES module without converting everything to ESM. This is possible by using a dynamic import, as TS helpfully points outs when I'm trying to run the test. But it doesn't work, because I'm assuming the default TS config doesn't have module: nodenext.

The docs tell me that adding a tsconfig.json won't help as Playwright only cares about paths and basePath options. Is there a way to support importing ES modules non-invasively, or should I consider manually compiling the tests? (This affect a lot of packages since many npm package maintainers switched to supporting only ESM.)

Issue 2:
Context:

Playwright Version: 1.25.1

Operating System: MacOs

Node.js version: v16.17.0

Code Snippet

import { test } from "@playwright/test";

test("dynamic import of ESM", async ({}) => {
const { default: getPort } = await import("get-port");
console.log(await getPort());
});

Describe the bug

From the node.js docs

Dynamic import() is supported in both CommonJS and ES modules. In CommonJS modules it can be used to load ES modules.

Yet, trying to load an ESM only package like get-port with a dynamic import statement fails with the error:

Error [ERR_REQUIRE_ESM]: require() of ES Module .../node_modules/get-port/index.js from .../tests/example.spec.ts not supported.
Instead change the require of index.js in .../tests/example.spec.ts to a dynamic import() which is available in all CommonJS modules.

It's complaining I'm trying to use require to load an ESM only module, but as can be seen in the snippet, it's an import().
Issue 1:
Wojciech Durczyński opened SPR-5156 and commented

In OSGI @Configurable mechanism works well only when used in one bundle.

If there is <context:spring-configured /> in application contexts of more then one bundle, the AnnotationBeanConfigurerAspect (single instance) is injected with two different BeanConfigurerSupport objects in non deterministic order.

Bundle whose BeanFactory is injected to aspect most recently works well - others don't work at all.

Is there any work around for this problem?

Affects: 2.5.5

Issue Links:

#10074 AnnotationBeanConfigurerAspect is created as a singleton and cannot be shared across multiple contexts ("duplicates")

#10074 AnnotationBeanConfigurerAspect is created as a singleton and cannot be shared across multiple contexts ("is duplicated by")

15 votes, 20 watchers

Issue 2:
Robert Binna opened SPR-9296 and commented

In version 3.1.1 of the springframework, the creation of the application context and the lookup of beans by type, in particular the lookup of prototype beans is extremely slow (factor 10).

The same creation and lookup process in spring 3.0.6 was significantly faster.

The definition of the application context is done through java based bean configuration.

Therefore we created a sample programm which can be used to reproduce the problem (program together with a gradle build file is attached, gradle run executes the test).

This application uses javasssist to create 100 bean classes. Each bean class has 5 autowired bean properties. The bean properties are generated, such that no cyclic dependencies occur. Finally a configuration class containing the generated beans is constructed and loaded. All beans are created as singletons except one bean which has been created as prototype scope.

After the application context is loaded a single bean is looked up from the application context 100 times. In the first case this is done with a bean of scope singleton. In the second case this is done with a bean of scope prototype.

The same tests was issued on spring 3.1.1 and spring 3.0.6

The results are as follows:

==== Spring 3.1.1 ====

SingletonBean:

StopWatch 'SpringPerformanceTest': running time (millis) = 17004; [settingUpApplicationContext] took 15177 = 89%; [retrievingBeans] took 1827 = 11%

PrototypeBean:

StopWatch 'SpringPerformanceTest': running time (millis) = 24400; [settingUpApplicationContext] took 13126 = 54%; [retrievingBeans] took 11274 = 46%

==== Spring 3.0.6 ====

SingletonBean:

StopWatch 'SpringPerformanceTest': running time (millis) = 3110; [settingUpApplicationContext] took 2654 = 85%; [retrievingBeans] took 456 = 15%

PrototypeBean:

StopWatch 'SpringPerformanceTest': running time (millis) = 3163; [settingUpApplicationContext] took 1790 = 57%; [retrievingBeans] took 1373 = 43%

Affects: 3.1.1

Attachments:

benchmark.zip (3.84 kB)

Issue Links:

#11536 Cache by-type lookups in DefaultListableBeanFactory ("duplicates")

1 votes, 3 watchers
Issue 1:
master but also present on 1.5.3

imshow(rand(5, 5)); gca().set_xticklabels(["foo", "bar"])

results in

Almost certain this is due to the xticks internally including a tick at the position "just left of bounds". Seems related (not directly, though) to the issue discussed in #7042.

Issue 2:
Tested on matplotib 1.5.1 on OSX, pip installation. Not sure about regression but I never noticed this behavior before.

Expected behavior:

plt.figure(figsize=(6, 4))
ax = plt.subplot(1, 1, 1)
ax.set_xlim(0, 2)
plt.show()

Bad: Extends the x limit for unknown reason

majors = ["0", "1", "2"]
plt.figure(figsize=(6, 4))
ax = plt.subplot(1, 1, 1)
ax.xaxis.set_major_formatter(ticker.FixedFormatter(majors))
ax.set_xlim(0, 2)
plt.show()

Bad: First item is not displayed

majors = ["0", "1", "2"]
plt.figure(figsize=(6, 4))
ax = plt.subplot(1, 1, 1)
ax.xaxis.set_major_locator(ticker.MultipleLocator(1.0))
ax.xaxis.set_major_formatter(ticker.FixedFormatter(majors))
ax.set_xlim(0, 2)
plt.show()
Issue 1:
When updating from v3.0.3 to v3.0.4 the version gets updated to v3.0.4-DEV.

This issue also has been reported by Loïc Vernet on the release page for v3.0.4: symfony.com: Symfony 3.0.4 released.

Issue 2:
After upgrading Symfony to version 3.0.4 I see "3.0.4-DEV" instead of "3.0.4" as version in console and debug toolbar. Would you be so kind to fix this issue?

Thank you.
Issue 1:
Can not import css after upgrading to v5

//next.config.js
const withCSS = require('@zeit/next-css')
module.exports = withCSS()

//pages/test.js
import React from 'react';
import './test.css';

export default () => <div className="test">Hello World!</div>;

/*pages/test.css*/
.test{background-color: red;}

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

Expected Behavior

Have a box with red background

Current Behavior

Seeing this error:

ERROR in ./pages/test.css
Module build failed: ValidationError: Style Loader Invalid Options

options['importLoaders'] should NOT have additional properties

@ ./pages/test.js 10:0-20
@ multi ./pages/test.js

Context

I don't have .babelrc and postcss.config.js in my local and trying to import css

Your Environment

Tech
Version

next
5

node
9.5

OS
macOS 10.12.6

browser
chrome Version 64.0.3282.140

Issue 2:
Bug report

Discussed with @timneutkens on Slack.

Describe the bug

After a change I am not seeing server SSR reflect the change.

The server bundle is being rebuilt properly, but its serving stale pages.
Issue 1:
I tried to recreate this example to add off diagonal lines to a pairplot: https://stackoverflow.com/a/48122198/4464887

The code is:

import seaborn as sns
import numpy as np
import matplotlib.pyplot as plt

def plot_unity(xdata, ydata, **kwargs):
mn = min(xdata.min(), ydata.min())
mx = max(xdata.max(), ydata.max())
points = np.linspace(mn, mx, 100)
plt.gca().plot(points, points, color='k', marker=None,
linestyle='--', linewidth=1.0)

ds = sns.load_dataset('iris')
grid = sns.pairplot(ds)
grid.map_offdiag(plot_unity)
plt.savefig('test.png')

But the image produced doesn't show the off-diagonal lines present in the linked answer:

Package versions are the latest releases:

Matplotlib 3.3.2

seaborn 0.11.0

Python 3.6.5

I am running on Windows and get the same output from the REPL, iPython and Jupyter Lab.

Thanks for a great library!

Issue 2:
Hi,

I discovered that the map_* methods of PairGrid seem to be broken in version 0.11.0 for user defined functions. See reproducible example below with a corrfunc defined to plot the pearson correlation value on the lower plots. The function doesn't seem to get evaluated in version 0.11.0. When I pip install seaborn==0.10.1, I get the desired result. Plots from both cases also attached.

from scipy import stats
import pandas as pd
import seaborn as sns
import matplotlib.pyplot as plt
sns.set(style="white")

mean = np.zeros(3)
cov = np.random.uniform(.2, .4, (3, 3))
cov += cov.T
cov[np.diag_indices(3)] = 1
data = np.random.multivariate_normal(mean, cov, 100)
df = pd.DataFrame(data, columns=["X", "Y", "Z"])

def corrfunc(x, y,**kws):
r, _ = stats.pearsonr(x, y)
ax = plt.gca()
ax.annotate("r = {:.2f}".format(r),
xy=(.1, .9), xycoords=ax.transAxes)

g = sns.PairGrid(df, palette=["red"])
g.map_upper(plt.scatter, s=10)
g.map_diag(sns.distplot, kde=False)
g.map_lower(sns.kdeplot, cmap="Blues_d")
g.map_lower(corrfunc)
plt.show()
Issue 1:
Feature request

👋 I'm a developer who's been working on adding source map support to Node.js stack traces.

I've noticed that webpack's source maps use special pseudo paths, which look something like this:

webpack:///./index.js

When these source maps are loaded in Node.js, it's difficult to know what path ./index.js should be resolved relative to. The specification indictes:

the sources are resolved relative to the SourceMap (like resolving script src in a html document).

Which to me would suggest dist/index.js, vs., the sources's actual location dist/../index.js.

What is the expected behavior?

It would be nice to be able to read a variable like sourceRoot, to determine the root path of the JavaScript file prior to transpilation.

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

Folks use webpack to create bundles of Node.js applications that are run outside of the browser, it would be nice for these people to have accurate stack traces.

How should this be implemented in your opinion?

When specifying --target node, it would be useful if source paths either did not use the webpack:// pseudo path, or if the sourceRoot variable was populated (populating sourceRoot would potentially break other implementations reading the sourceMap).

Are you willing to work on this yourself?

yes

Refs: nodejs/node#35325

Issue 2:
Feature request

What is the expected behavior?

Expected compiled code Use Directly native es6 module

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

Because the browser environment supports

How should this be implemented in your opinion?

add a option

Are you willing to work on this yourself?

yes
Issue 1:
Challenge Name

Clone an Element Using jQuery

https://www.freecodecamp.com/challenges/clone-an-element-using-jquery

Issue Description

Browser Information

Browser Name, Version: 360 Safe Browser

Operating System: Windows 7

Mobile, Desktop, or Tablet:

Your Code

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Screenshot

Issue 2:
Challenge Waypoint: Clone an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.73 Safari/537.36.

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

Issue

I believe I've found bug in the phone simulation in Waypoint: Clone an Element Using jQuery:

I entered the code to clone target5 and append it to left-well, and now I see three target5 buttons in the phone simulator. FCC says my code is correct and advances me to the next challenge. The following challenges also show three target5 buttons:

Waypoint: Target the Parent of an Element Using jQuery

Waypoint: Target the Children of an Element Using jQuery

@qualitymanifest confirms this issue on his Linux box.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>