WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Description of the problem

Hi everyone,

I just found that sprite don't get hit when size attenuation is false

plunker (latest release branch)

Three.js version

Dev

r97

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

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

Issue 2:
Hi Friends!

SpriteMaterial.sizeAttenuation = false

seems not working as expected with rayCaster.

I doubt the sprite size(dimension) estimation may be a little bit off, ray is very hard to hit them after apply scale(), especially scale down.

I can upload a simplified code that regenerate this problem a bit later.

r96

Browser

All of them

Thanks!
Issue 1:
Hello,

this is intentionally a duplicate of the over-hastily closed #9260. Please reopen the issue and fix the bug, it's annoying. Workarounds are time-consuming.

Regards,

Matthias

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

vmware_guest_facts

vmware_guest_snapshot

ANSIBLE VERSION

ansible 2.3.0.0
config file =
configured module search path = Default w/o overrides
python version = 2.7.5 (default, Nov 6 2016, 00:28:07) [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]

CONFIGURATION

OS / ENVIRONMENT

N/A

SUMMARY

datacenter is required by the plugin, but it is not in reality

STEPS TO REPRODUCE

vmware_guest_snapshot:
hostname: my-vmware
username: user
password: pass
#datacenter: my-dc
validate_certs: no
snapshot_name: test
name: my-vm
delegate_to: localhost

EXPECTED RESULTS

It should work without datacenter

ACTUAL RESULTS

"msg": "missing required arguments: datacenter"

On these plugins, required should be set to false for datacenter
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 have a child aux route:

const routes = [
{
path: 'first',
component: FirstComponent,
children: [
{
path: 'add-groups',
outlet: 'aside',
component: AsideComponent
}
]
];

Aux component has a close button that works only when parent's params are set to navigate method like that:

this.router.navigate([this.route.parent.snapshot.params, {outlets: {aside: null}}]);

and doesn't work like:

this.router.navigate([{outlets: {aside: null}}]);

Expected behavior

Expect this.router.navigate([{outlets: {aside: null}}]); will close the aux

Minimal reproduction of the problem with instructions

https://plnkr.co/edit/kA434H7u5mJbiB7vvkCQ

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

Use aux routing

Please tell us about your environment:

Mac OS

Angular version: 2.0.X

2.4.8

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

All

Language: [all | TypeScript X.X | ES6/7 | ES5]

TypeScript

Node (for AoT issues): node --version =

Issue 2:
I'm submitting a ...

[X] bug report

Current behavior

I have some routes like:

const routes = [
{ path: "", component: HomeComponent, pathMatch: "full" },
{ path: "profile", component: ProfileComponent },
{ path: "menu", component: MenuComponent, outlet: "sidebar" },
];

When the route http://localhost/(sidebar:menu) is open, then I'm able to remove the named outlet and go to http://localhost/ by clicking an anchor like the following:

<a [routerLink]="['', {outlets: {sidebar: null}}]">
Close
</a>

What doesn't work is navigating away from the sidebar and also going to another route like http://localhost/profile.

<a [routerLink]="['/profile', {outlets: {sidebar: null}}]">
Close
</a>

The link that is rendered is http://localhost:3971/profile(sidebar:menu)

Expected behavior

The link that should be rendered is http://localhost:3971/profile.

Repro

https://github.com/tinchou/router-repro

Please tell us about your environment:

Windows 10, Visual Studio 2017

Angular version: 2.3.1 (didn't work with 2.1.0 either)

Browser: all

Language: TypeScript 2.0.10
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When dispatching an additional action (the middleware is awaiting the second action before forwarding the first action to next()) from a redux middleware invoked by an action call in getInitialProps, the function should await both of the action promises resolving before rendering.

Current Behavior

Server render does not include state from store dispatched by either action creator. If I don't await the second action call, state from the first action creator is present. As soon as the page is hydrated on the client side the actions dispatch normally in componentDidMount().

It seems as if for some reason, the server render is timing out and not waiting for getInitialProps to resolve.

getInitalProps:

static async getInitialProps({
store: { dispatch },
query: { slug },
res,
}) {
await dispatch(getActiveOrg(slug)).catch(
({ response: { status } }) => {
if (status === 404) {
res.statusCode = 404;
}
},
);
return {
slug,
};
}

middleware:

export default ({ dispatch }) => next => async action => {
if (action.type === ORGANIZATION_INFO_RECEIVED) {
const { payload } = action;
if (payload.donor_landing_page === 'cause') {
await dispatch(
fetchCauses(
payload.subdomain,
payload.donor_landing_page_id,
),
);
}
}
next(action);
};

Context

The goal of this redux middleware is to allow for conditionally fetching additional data before the server response dependent on the response of an initial API call.

Your Environment

Tech
Version

next
5.0.0

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

gaearon/react-hot-loader/issues/356 is the closest I found.

Expected Behavior

Error free .next/bundles/pages/index.js

Current Behavior

Firefox throws:

process.env is undefined

Chromium says:

TypeError: Cannot read property 'NODE_ENV' of undefined

both originate from:

;(function register() { /* react-hot-loader/webpack */ if (process.env.NODE_ENV !== 'production') { if (typeof __REACT_HOT_LOADER__ === 'undefined') { return; }

In most places the generated index.js reads:

;(function register() { /* react-hot-loader/webpack */ if (true) { if (typeof __REACT_HOT_LOADER__ === 'undefined') { return; }

Something, and I can't figure out what, triggered webpack and/or react-hot-loader to use "process.env.NODE_ENV" in the front-end, which kills it.

Context

"next dev" is rendered useless, because the hot-reload feature breaks the front-end coding.

Your Environment

Tech
Version

next
4.1.4

node
6.12.0

OS
Ubuntu 17.10

browser
Firefox and Chromium

Any help would be greatly appreciated. Banging my head against the wall since days :(

Unfortunately I wasn't able to create a minimal-example, so if any code is required I will happily share it.
Issue 1:
matplotlib/lib/matplotlib/tests/test_axes.py

Lines 1132 to 1155
in
31d2c2f

@image_comparison(baseline_images=['pcolormesh'], remove_text=True)

def test_pcolormesh():

n = 12

x = np.linspace(-1.5, 1.5, n)

y = np.linspace(-1.5, 1.5, n*2)

X, Y = np.meshgrid(x, y)

Qx = np.cos(Y) - np.cos(X)

Qz = np.sin(Y) + np.sin(X)

Qx = (Qx + 1.1)

Z = np.hypot(X, Y) / 5

Z = (Z - Z.min()) / Z.ptp()

# The color array can include masked values:

Zm = ma.masked_where(np.abs(Qz) < 0.5 * np.max(Qz), Z)

fig = plt.figure()

ax = fig.add_subplot(131)

ax.pcolormesh(Qx, Qz, Z, lw=0.5, edgecolors='k')

ax = fig.add_subplot(132)

ax.pcolormesh(Qx, Qz, Z, lw=2, edgecolors=['b', 'w'])

ax = fig.add_subplot(133)

ax.pcolormesh(Qx, Qz, Z, shading="gouraud")

Note that Zm is unused; and thus there is no test for pcolormesh with a masked array as input.

Issue 2:
The pcolormesh test says that masked colour arrays are supported, but this masked Zm variable is never used in the test. It appears that this has been the case since the test was added.

I'm not sure exactly how the "correct" masked result should look, or I would update this myself. I hope one of the assignees should have some idea what to do here.
Issue 1:
@alexcrichton has indicated this may be related to using newer versions of gcc, which might explain why it doesn't fail on the buildbot machines.

The segfault occurs while running the tailcallelim llvm pass on ast::Pat_::drop(), possibly during the prerequisite tti analysis.

Turning on any kind of debug information for either rust or llvm causes the problem to disappear.

Issue 2:
Just a heads-up to others: mingw-w64 (not sure about other platforms) GCC 5.x appears to be subtly mis-compiling LLVM, which results in a segmentation fault during rustc's codegen.

I've seen this with x86_64-5.1.0- and i686-5.2.0- toolchains. In the former case LLVM had to be compiled with asserts (--enable-llvm-assertions) for this to occur.

GCC 4.9.3 seems to be OK.
Issue 1:
Challenge adjust-the-width-of-an-element-using-the-width-property has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.

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

I set the full card width property to 245px and it doesnt like it. Says to keep trying. Browser zoom is set to 100%.

<style>
h4 {
text-align: center;
}
p {
text-align: justify;
}
.links {
margin-right: 20px;
text-align: left;
}
.fullCard {
width: 245px;
border: 1px solid #ccc;
border-radius: 5px;
margin: 10px 5px;
padding: 4px;

}
.cardContent {
padding: 10px;
}
</style>
<div class="fullCard">
<div class="cardContent">
<div class="cardText">
<h4>Google</h4>
<p>Google was founded by Larry Page and Sergey Brin while they were Ph.D. students at Stanford University.</p>
</div>
<div class="cardLinks">
<a href="https://en.wikipedia.org/wiki/Larry_Page" target="_blank" class="links">Larry Page</a>
<a href="https://en.wikipedia.org/wiki/Sergey_Brin" target="_blank" class="links">Sergey Brin</a>
</div>
</div>
</div>

Issue 2:
Challenge Comment your JavaScript Code has an issue.

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

When i tried to Run tests(ctrl+enter), it shows a message "Error: SyntaxError: Unsafe or unfinished function declaration". With a simple comments, there is no problem, but if use that comment, the problem exist. I think it has to do with the symbols, although it is a valid comment.

My code:

//I don't agree that a comment is good to clarify the function of parts of your code

/*
A good code can be determined with just the name of the functions, variables,
how it's easy to understand even without leaving comments.
If you need to leave a comment to the code, it's not a "good enough code"
*/
Issue 1:
#
First Name
Last Name
Username

1
Mark
Otto
@mdo

Mark
Otto
@twbootstrap

2
Jacob
Thornton
@fat

3
Larry the Bird
@twitter

Issue 2:
Hi,

I'm building an application with Twitter Bootstrap one of the reasons because I need it to be responsive and readable with hand-held devices.

The responsive layout works like a charm, but tables not so much, they have a fixed min width where they can't go any thiner, I get that, but it would be so cool if the tables would be responsive, meaning when they can't go any thinner they change their layout to show the information somehow to fit the screen.

I don't know how would you achieve this, maybe changing the scale (or zoom) on the table so it go smaller, since on a hand-held you can zoom in with a pinch.

Is there an easy solution to solve this?

Thanks!
Issue 1:
An estimator with multioutput support can be used for multilabel problems such as RandomForestClassifier. Its predict_proba methods returns

scikit-learn/sklearn/ensemble/forest.py

Lines 581 to 582
in
ee328fa

p : array of shape = [n_samples, n_classes], or a list of n_outputs

such arrays if n_outputs > 1.

Such estimators blends multilabel problems and multioutput problems because a multilabel problem is a special multioutput one.

Most of the estimators don't support multilabel directly and OneVsRestClassifier is required. Its predict_proba method returns

scikit-learn/sklearn/multiclass.py

Lines 337 to 339
in
ee328fa

T : (sparse) array-like, shape = [n_samples, n_classes]

Returns the probability of the sample for each class in the model,

where classes are ordered as they are in `self.classes_`.

Therefore, for multilabel problems, these classes return different types of results when calling predict_proba. It can introduce some issue, for example, implementing multilabel support for VotingClassifier.

Issue 2:
Right now, the content of classes_ and the shape of the output of predict_proba and decision_function are inconsistent between estimators.

If an estimator supports multioutput multiclass, classes_ will be [[0, 1]] * n_outputs and predict_proba will return an object array of length n_outputs where each is (n_samples, 2).

If the estimator supports multi-label classification, but not multioutput multiclass, classes_ will be np.arange(n_outputs) and predict_proba will be (n_samples, n_outputs).

That leads to issues such as #8773, but also runs counter to the sklearn promise of a consistent API.

Given that even basic API like the score method is broken on multioutput multiclass (see #9414), I'm not sure it's worth keeping this maintenance burden.

Alternatively we could detect in the multioutput multiclass classifiers that a problem is actually multilabel and use the appropriate shapes for that.

Either way, it's an incompatible change that's tricky to do with a deprecation cycle :-/
Issue 1:
Please go to Stack Overflow for help and support:

https://stackoverflow.com/questions/tagged/tensorflow

If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).

The form below must be filled out.

It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:

TensorFlow installed from (source or binary):

TensorFlow version (use command below):

Python version:

Bazel version (if compiling from source):

GCC/Compiler version (if compiling from source):

CUDA/cuDNN version:

GPU model and memory:

Exact command to reproduce:

You can collect some of this information using our environment capture script:

https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh

You can obtain the TensorFlow version with:

python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"

Describe the problem

Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.

Source code / logs

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

Issue 2:
In my programe, I use f.nn.embedding_lookup as follow:

embedding = tf.get_variable("embedding", [200000, 128], tf.float32, initializer=tf. random_normal_initializer(stddev=0.1), trainable=True,partitioner=tf.fixed_size_partitioner(10))

word_embedding = tf.nn.embedding_lookup(embedding, query_tensor)

while(1):

sess.run(word_embedding )

when I start 30 worker，each worker qps is 3000.

but when I test tf.nn.embedding_lookup_sparse, each worker qps is 110000

how to solve this problem,any suggestion welcome
Issue 1:
Juergen Hoeller opened SPR-5587 and commented

Spring 3.0 provides compatibility with Servlet 3.0 containers such as GlassFish V3 already. Spring 3.1 (Q2 2011) is likely to provide optional support for Servlet 3.0's multipart form handling (#11210), and possibly for other Servlet 3.0 features that we can provide fallback solutions for as well.

Also to consider is support for Servlet 3.0 async processing in Spring MVC and for Servlet 3.0 auto-registration in Spring's general web deployment.

http://jcp.org/en/jsr/detail?id=315

Issue Links:

#13162 Support for Servlet 3.0/3.1 asynchronous request processing

#12529 Provide servlet 3.0 web fragment to startup application context without web.xml modifications

#11210 Provide StandardMultipartResolver based on Servlet 3.0 Part API

#12328 Support configuring Servlet container in Spring using Servlet 3.0 programmatic config

#9840 Support for Tomcat's CometEvent enabled beans

18 votes, 21 watchers

Issue 2:
Josh Brackett opened SPR-7781 and commented

In Spring 3.0.4 this works as expected but was regressed in 3.0.5

We have a parameter in a method that looks like this:

@RequestParam(value = "removeList", required = false) List<Long> removeList

Where the parameter removeList on the page is a collection of checkboxes like below:

<input type="checkbox" value="7792" name="removeList">

The method is getting Strings instead of Longs though so we get exceptions in the method when the type isn't what is expected.

Affects: 3.0.5

Issue Links:

#12440 @RequestParam List list, will be filled up with String objects instead of Long objects ("is duplicated by")

#12440 @RequestParam List list, will be filled up with String objects instead of Long objects

#12422 Wrong data-type resolution using custom Converter

1 votes, 6 watchers
Issue 1:
unsafe.Sizeof(image.RGBAColor{}) == 8

this means that a 32-bit-per-pixel image actually
uses 64 bits, which seems a harsh price to pay.

in general, i'd hope that a struct size be padded
to fulfill the alignment requirement of its largest member
and no more.

Issue 2:
multipart.ReadForm is supposed to store up to maxMemory bytes in RAM and then the remainder on disk. The idea, presumably, is to prevent RAM exhaustion.

Temporary files are created using ioutil.TempFile. os.TempDir is used to determine the temporary directory to use. However, os.TempDir() returns $TMPDIR, or, failing that, "/tmp".

The problem is that on modern Linux systems, /tmp is a tmpfs and is thus hosted in RAM. This defeats the entire objective of saving large multipart parts to files.

/var/tmp should always be backed by disk. The FHS states the purpose of "/var/tmp" as "temporary files preserved between system reboots." multipart should use /var/tmp, not /tmp.

(Since there is no actual need for temporary multipart files to be preserved across reboots, it would be nice if the FHS provided something in between, thus allowing for periodic deletion on boot or so on, but alas it does not.)

Possible solutions:

Introduce an os.LargeTempDir() which returns a temporary directory to be used for large files. Change multipart to pass this value to ioutil.TempFile.
Issue 1:
If I place Grid inside a Collapse component, it doesn't expand and collapse smoothly. It expands a little more than needed and then collapses a bit back. Is that a bug? Or is there some workaround to use Grid inside collapsible part of the UI? Thanks.

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

Expected Behavior

Expand and collapse smoothly like it does without Grid inside

Steps to Reproduce (for bugs)

https://codesandbox.io/s/mzoqprz61y?module=%2FMyApp.jsx

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16.0.0

browser
Safari, Chrome, Firefox

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

Expected Behavior

Follow the next.js example in this repo and get a working material-ui+next.js setup

Current Behavior

DONE Compiled successfully in 1897ms 11:35:49 AM

Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in. Check your code at _document.js?entry:65.
in Unknown (created by Container)
in AppContainer (created by Container)
in Container (created by App)
in div (created by App)
in App
{ Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in. Check the render method of `StatelessComponent`.
at invariant (/Users/albinekb/Devel/Temp/nextjs/node_modules/fbjs/lib/invariant.js:44:15)
at ReactCompositeComponentWrapper.instantiateReactComponent [as _instantiateReactComponent] (/Users/albinekb/Devel/Temp/nextjs/node_modules/react-dom/lib/instantiateReactComponent.js:74:56)
at ReactCompositeComponentWrapper.performInitialMount (/Users/albinekb/Devel/Temp/nextjs/node_modules/react-dom/lib/ReactCompositeComponent.js:366:22)
at ReactCompositeComponentWrapper.mountComponent (/Users/albinekb/Devel/Temp/nextjs/node_modules/react-dom/lib/ReactCompositeComponent.js:257:21)
at Object.mountComponent (/Users/albinekb/Devel/Temp/nextjs/node_modules/react-dom/lib/ReactReconciler.js:45:35)
at ReactCompositeComponentWrapper.performInitialMount (/Users/albinekb/Devel/Temp/nextjs/node_modules/react-dom/lib/ReactCompositeComponent.js:370:34)

Steps to Reproduce (for bugs)

Get this code https://github.com/callemall/material-ui/tree/v1-beta/examples/nextjs

Install it yarn

Run it yarn dev
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The import() promise returns the entire module, including default.

Current Behavior

The import() promise returns the default export if it exists; otherwise, it returns the entire module. This breaks the spec-compliant method of loading default exports:

import('/some-module').then(module => module.default);

Steps to Reproduce (for bugs)

https://repro-ilvgtolutc.now.sh

https://github.com/tptee/nextjs-import-spec-repro

Context

I'm trying to create examples for my library that uses import(), and next's behavior is surprising compared to CRA and custom setups. Ensuring spec compliance would allow examples to apply everywhere and be shareable across environments.

These lines in the handle-import Babel plugin seem to be the offenders:

https://github.com/zeit/next.js/blob/v3-beta/server/build/babel/plugins/handle-import.js#L16

https://github.com/zeit/next.js/blob/v3-beta/server/build/babel/plugins/handle-import.js#L26

https://github.com/zeit/next.js/blob/v3-beta/server/build/babel/plugins/handle-import.js#L32

Happy to PR a fix, although it'll likely be a breaking change and (maybe) a usability loss.

Your Environment

Tech
Version

next
v3.0.1-beta.17

node
v7.9.0

OS
macOS 10.12.5

browser
Chrome 60.0.3112.50 (Official Build) beta (64-bit)

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

I just started using Next.js and so far I've been blown away by the combination of features and simplicity.

I'd like to donate in some way. How should I go about doing that? An Open Collective, maybe?