WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I'm using MaterialUI w/ React 16 w/ server-side rendering. Everything seems to be working, but React is complaining about the server-side and client-side markups not matching. Warning goes away if I remove the TextField from my view. What am I doing wrong?

React Warning: Warning: Prop 'htmlFor' did not match. Server: "email-undefined-Email-51592" Client: "email-undefined-Email-58019"

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

Expected Behavior

Should be able to utilize MUI's TextField component w/ SSR w/o having React warn on SSR and CSR render mismatches.

Current Behavior

The warning above is displayed in the browser console.

Steps to Reproduce (for bugs)

This is a server-side render issue, so using something like codesandbox.com isn't an option since you can only do CSR in that case.

Create a SSR react app

Create a view w/ a TextField component in it like follows:

<TextField
className=""
type="email"
fullWidth={true}
name="email"
floatingLabelText="Email"
/>

Load the view.

Check console to see React warning above.

Context

Just building an app using MUI and can't make the warning go away (which is also causing components to re-render in the client)

Your Environment

Node 8, KoaJS v2, React 16, react-router v4, Chrome latest

Tech
Version

Material-UI
0.19.4

React
16

browser
Chrome latest

etc
OSX High Sierra

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

Expected Behavior

Whenever a FlatButton is clicked, the event handler should receive the event object of the button.

Current Behavior

Instead it receives the event object of a child span.

Steps to Reproduce (for bugs)

Open: https://codesandbox.io/s/l9v5q2548z

Open debugging console.

Click on the buttons & see the event.target object, which is a child span of the FlatButton that is being created behind the scenes.

Context

I need to pass name property of the buttons to the event handlers and there perform different actions depending on the value of the name property.

Your Environment

Tech
Version

Material-UI
0.20

React
16.2.0

browser
Chrome

etc
Issue 1:
I see that the libraries are using viewless Fragments to do work. This creates a problem where under some circumstance, would conflict with other fragment transactions that fragment manager is doing

The full stacktrace:

java.lang.IllegalStateException: Recursive entry to executePendingTransactions
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1457)
at android.support.v4.app.FragmentManagerImpl.executePendingTransactions(FragmentManager.java:482)
at com.bumptech.glide.manager.RequestManagerRetriever.supportFragmentGet(RequestManagerRetriever.java:148)
at com.bumptech.glide.manager.RequestManagerRetriever.get(RequestManagerRetriever.java:66)
at com.bumptech.glide.manager.RequestManagerRetriever.get(RequestManagerRetriever.java:29)
at com.bumptech.glide.Glide.with(Glide.java:537)

A perfect example of this would be an ViewPager containing several Fragments that calls Glide at the very beginning of onCreateView.

Issue 2:
I have a customized ImageView which is using Glide to load up it's content during onAttachedToWindow(). It works correctly if it is embedded into an activity, however if I put it into a Fragment it fails.

I use Glide with this two lines as recommended:

Glide.get(getContext()).register(GlideUrl.class, InputStream.class, new VolleyUrlLoader.Factory(...));
Glide.with(getContext()).load(...).into(this);

It fails on the second line, and note that in the Fragment's case, the getContext() is returning the FragmentActivity, not the Fragment. I'm guessing that this is the problem, which I might be able to circumvent with some hacking (by providing the Fragment to the view, which I don't really want to do).

Anyway the resulting stack trace is the following:

FATAL EXCEPTION: main
java.lang.IllegalStateException: Recursive entry to executePendingTransactions
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1456)
at android.support.v4.app.FragmentManagerImpl.executePendingTransactions(FragmentManager.java:482)
at com.bumptech.glide.manager.RequestManagerRetriever.supportFragmentGet(RequestManagerRetriever.java:148)
at com.bumptech.glide.manager.RequestManagerRetriever.get(RequestManagerRetriever.java:66)
at com.bumptech.glide.manager.RequestManagerRetriever.get(RequestManagerRetriever.java:29)
at com.bumptech.glide.Glide.with(Glide.java:537)
Issue 1:
When a parent give a constraint to his childrens by annotations,

whe cannot remove the constraint by annotation in the class child

It's possible to had a way to manage inheritance strategy like this ? :

/**
* @assert:NotBlank()
* @assert:NotInheritance()
*/

or/and do this :

$childObject->getValidator()->removeConstraint('name');

Issue 2:
Use case

Models:

abstract class AbstractUser
{
private $username;
private $password;
}

class ConcreteUser extends AbstractUser
{
/**
* @var UserProfile
*/
private $profile;
}

class UserProfile
{
private $name;
}

validation.xml (1)

<class name="AbstractUser">
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
<property name="password">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

validation.xml (2) :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
</class>

<class name="UserProfile">
<property name="name">
<constraint name="NotBlank">
<option name="groups">
<value>Profile</value>
<value>Registration</value>
</option>
</constraint>
</property>
</class>

When setting validation_groups to Registration, the error messages show twice for the UserProfile::name property.

A simple test can be adding the username validation again into ConcreteUser class constraints :

<class name="ConcreteUser">
<property name="profile">
<constraint name="Valid" />
</property>
<property name="username">
<constraint name="NotBlank">
<option name="groups">Registration</option>
</constraint>
</property>
</class>

Then validation error messages will show twice on the username as well.

In production environnement that's inconvenient :/

Hack, ugly but....

For now, there is a hack until this is fixed, in form theme blocks (twig) :

{% block field_errors %}
{% spaceless %}
{% if errors|length > 0 %}
<ul>
{% set lastError = null %}
{% for error in errors %}
{% if lastError != error %}
<li>{{ error.messageTemplate|trans(error.messageParameters, 'validators') }}</li>
{% endif %}
{% set lastError = error %}
{% endfor %}
</ul>
{% endif %}
{% endspaceless %}
{% endblock field_errors %}
Issue 1:
Button groups with checkboxes or radios don't get the checked status on pageload, even if the "checked" attribute is set on one or more of checkboxes.

Example see here: http://www.bootply.com/79923

Issue 2:
Hi guys! Love your work!

Have some issues with checkbox and radio Buttons on Button-groups. I've try to pre-load option with a form, but got all buttons disabled. Hope you'll fix it.

Thank you!
Issue 1:
Checklist

I have verified that the issue exists against the master branch of Celery.

This has already been asked to the discussion group first.

I have read the relevant section in the

contribution guide

on reporting bugs.

I have checked the issues list

for similar or identical bug reports.

I have checked the pull requests list

for existing proposed fixes.

I have checked the commit log

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

I have included all related issues and possible duplicate issues

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

Mandatory Debugging Information

I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have verified that the issue exists against the master branch of Celery.

I have included the contents of pip freeze in the issue.

I have included all the versions of all the external dependencies required

to reproduce this bug.

Optional Debugging Information

I have tried reproducing the issue on more than one Python version

and/or implementation.

I have tried reproducing the issue on more than one message broker and/or

result backend.

I have tried reproducing the issue on more than one version of the message

broker and/or result backend.

I have tried reproducing the issue on more than one operating system.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with autoscaling, retries,

ETA/Countdown & rate limits disabled.

I have tried reproducing the issue after downgrading

and/or upgrading Celery and its dependencies.

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Environment & Settings

Celery version: 4.4.7

celery report Output:

Steps to Reproduce

Required Dependencies

Minimal Python Version: 3.8.2

Minimal Celery Version: 4.4.6

Minimal Kombu Version: N/A or Unknown

Minimal Broker Version: N/A or Unknown

Minimal Result Backend Version: N/A or Unknown

Minimal OS and/or Kernel Version: ubuntu

Minimal Broker Client Version: N/A or Unknown

Minimal Result Backend Client Version: N/A or Unknown

Python Packages

pip freeze Output:

amqp==2.6.1
celery==4.4.7
kombu==4.6.11
redis==3.5.3

Other Dependencies

N/A

Minimally Reproducible Test Case

Expected Behavior

We upgraded from celery version 4.4.6 to 4.4.7, everything was working fine on 4.4.6.

Actual Behavior

After upgrading, we failed to start the worker service because "--app" parameter is not loaded from "ExecStart" command. Beat service works well with "--app" though. We downgraded back to 4.4.6 and it works fine again.

Issue 2:
The basic tutorial setup outlined here: https://docs.celeryproject.org/en/latest/django/first-steps-with-django.html now fails to locate set the broker or CELERY_BROKER_URL parameter. Celery just ignores the settings and defaults to searching for a host at amqp://guest:**@127.0.0.1:5672//:, which is not my host of choice.

I'm ignoring the issues template because this is a very basic regression that the last committor can fix quickly.
Issue 1:
A project in Blender -

three editor (note the arrows to the active camera) -

the render shows a black screen on that picture is not attached.

Turn around 180 degrees (note the arrows to the active camera) -

The source of light from above, lighting is the side.

Is it possible to fix this and how?

Issue 2:
Geometry's fromBufferGeometry() exports duplicated vertices and colors.

Code to reproduce:

var box = new THREE.BoxGeometry(1,1,1);
var bufferBox = new THREE.BufferGeometry();
bufferBox.fromGeometry(box);

var newBox = new THREE.Geometry();
newBox.fromBufferGeometry(bufferBox);

Result:

box : {vertices: Array(8), colors: Array(0)}

newBox : {vertices: Array(36), colors: Array(36)}

If you see useful, we have written a basic method to remove the vertices and fix the vertex index in the faces:

function clearDuplicateVertices(geometry) {
//store the vertex index changes
var data = [];
var vertices = [];
var faces = [];

//vertices
for (var v = 0; v < geometry.vertices.length; v++) {
var vertex = geometry.vertices[v];

//see if we have that vertex already
var newIndex = -1;
for (var i = 0; i < vertices.length; i++) {
if (vertices[i].equals(vertex))
{
newIndex = i;
break;
}
}

if (newIndex > -1)
{
data.push({oldIndex: v, newIndex: newIndex});
} else
{
vertices.push(vertex);
data.push({oldIndex: v, newIndex: vertices.length - 1});
}
}

//faces
for (var f = 0; f < geometry.faces.length; f++) {
var currentFace = geometry.faces[f];

var a = currentFace.a;
var b = currentFace.b;
var c = currentFace.c;
for (var i = 0; i < data.length; i++) {
var currentData = data[i];

if (a === currentData.oldIndex) {
a = currentData.newIndex;
}

if (b === currentData.oldIndex) {
b = currentData.newIndex;
}

if (c === currentData.oldIndex) {
c = currentData.newIndex;
}
}
faces.push(new THREE.Face3(a, b, c));
}

//copy
var geo = new THREE.Geometry();
geo.vertices = vertices;
geo.faces = faces;
geo.computeFaceNormals();
return geo;
}

Three.js version

r96
Issue 1:
Hi everyone,

cache:clear won't run up correctly anymore. It can't delete dev_old/annotations/(some_folder). I think it's because the filename length in (some_folder) is too long now compared to the 2.7 Symfony version. I'm running on Windows 7.

Look at the filename for example: 5b5b435d53796d666f6e795c42756e646c655c57656250726f66696c657242756e646c655c436f6e74726f6c6c65725c50726f66696c6572436f6e74726f6c6c65722474656d706c6174654d616e61676572405b416e6e6f745d5d5b315d.doctrinecache.data

If I try to rename this file by removing some char, cache:clear works again (actually, it goes farther then it bugs on another file which has the same problem)

Does someone have a solution ?

Regards

Issue 2:
After update symfony (composer update), symfony update 3.4.4 to 3.4.5. And i get this error:

request.CRITICAL: Exception thrown when handling an exception
(Twig_Error_Runtime: An exception has been thrown during the rendering of a template ("Object not found").
at C:\dev\project\vendor\symfony\symfony\src\Symfony\Bundle\TwigBundle\Resources\views\images\favicon.png.base64 line 1) {"exception":"[object] (Twig_Error_Runtime(code: 0): An exception has been thrown during the rendering of a template (\"Object not found\").
at C:\\dev\\project\\vendor\\symfony\\symfony\\src\\Symfony\\Bundle\\TwigBundle\\Resources\\views\\images\\favicon.png.base64:1, UnexpectedValueException(code: 0): Object not found at C:\\dev\\project\\vendor\\symfony\\symfony\\src\\Symfony\\Bridge\\Twig\\Extension\\ProfilerExtension.php:48)"} []
Issue 1:

Issue 2:
By doing that, I can make button labels disappear in small screen and shown correctly in big screen.

Example:

<button class="btn btn-primary"> <i class="icon icon-refresh"></i> <span class="hidden-xs"> Refresh </span> </button>

Code to modify:

.responsive-visibility() {
display: block !important;
table& { display: table; }
tr& { display: table-row !important; }
th&,
td& { display: table-cell !important; }
span& { display: inline !important; }
}

.responsive-invisibility() {
&,
tr&,
th&,
td&,
span& { display: none !important; }
}

I've been using it for the last month - seems to work :).
Issue 1:

Issue 2:
Given #30908 and #30909, it feels like maybe we would do well to make "Headless" an actual value for cluster.spec.type. Specifically, we don't intend to support node-ports or load-balancers for headless services, but it is possible to specify that intersection.

It would be cleaner, I think, to say:

headless-params:

selector (optional)

ports[*].port, protocol, and name

clusterip-params:

all of headless-params

clusterip (optional else assigned)

ports[*].targetPort

sessionAffinity

nodeport-params:

all of clusterip-params

ports[*].nodePort

loadbalancer-params:

all of nodeport-params

loadBalancerIP

loadBalancerSourceRanges

With #30599 we add:

externalname-params:

externalName

I argued against this before, but I am not sure why. Looking at history, I don't find my own arguments that compelling, but maybe I am missing some.
Issue 1:
What problem does this feature solve?

With the new Vue.observable you can create a simple reactive store which is super nice. It seems you can use these reactive properties directly in views (you don't need to use them through local computed properties). In this scenario, it would be nice to be able to also have global state based computed properties. This way, you'd be able to create a very nice and imo quite capable yet simple store pattern (compared to more verbose and complex solutions like Vuex). You also don't have to sprinkle computed props on components where they imo don't really belong.

It's possible to do a workaround by initiating new Vue instances, but I assume that causes some significant and completely unnecessary overhead.

What does the proposed API look like?

I'm completely open for your wisedom ;-) A few suggestions:

A)

Vue.computed({

computedProp: function() { ... }

});

B)

Vue.observable({

regularReactiveProp: 'something',

get computedProp: function () { ... }

});

I'm btw. not a big fan of transforming all functions to computed props, as this makes it less simple (impossible?) to pass along one store object that also contains all methods (for a more full scale model layer).

Issue 2:
Vue.js version

2.0-rc8 / 2.0-rc7

Reproduction Link

https://codepen.io/toxic-johann/pen/JRJgGJ?editors=1111

Steps to reproduce

use a v-for to render component

in component, you have to write a v-for with template in it but not wrapped with a root element

open console, and run test() function

What is Expected?

open console, and run success() function

or you can click https://codepen.io/toxic-johann/pen/JRJgGJ?editors=1111.

when i keep on one root element in v-for, the problem dispear.

So I think, if vue consider multiple element int the template is forbidden.It should throw a warn.

Otherwise, it's a bug

What is actually happening?

throw the warning

[Vue warn]: It seems there are duplicate keys that is causing an update error. Make sure each v-for item has a unique key.

and error

Uncaught (in promise) TypeError: Cannot read property 'tag' of undefined

it's the same problem with #3807

u can reopen that.
Issue 1:
Badly needed for commonjs modules where you are more likely to ship JS code plus a generated .d.ts file.

From codeplex : https://typescript.codeplex.com/workitem/2080

Issue 2:
There was an discussion about generating ambient declarations for external CommonJS modules: http://typescript.codeplex.com/workitem/2080

But even if typescript generates the definitions as we what we want, we'll still need to add references manually, which is not doing better job than JS libs with NuGet DefinitelyTyped packages.

I propose that when we publish a typescript package via npm, publish the .d.ts file(s) generated with the current style along with it.

So that we can manage to write a tool (or add a feature to something like WebEssentials) to watch related node_modules directory, resolve the definition references and create wrapped definition file(s) under scripts/typings folder.

Thoughts?
Issue 1:
Use of exclamation in an ngIf does not work when using null propagation operator. It worked in beta-15, not in beta-16.

See plunker for demo:

http://plnkr.co/edit/2TGZ2XVESVQQJ1IN39AA?p=preview

(change to beta-15 to see difference)

Short version:

<div *ngIf="!myData?.myBoolean">
<h2>With exclamation</h2> <---- does not show
</div>
<div *ngIf="myData?.myBoolean === false">
<h2>With === false</h2> <---- shows as expected
</div>

I could not find anything about this in the changelog - is this as designed?

Issue 2:
I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

Current behavior

I am dynamically creating a component (using viewContainer.createComponent) which uses ChangeDetectionStrategy.OnPush and that component instantiates a template provided by the parent component with viewContainerRef.createEmbeddedView(templateRef). When the parent component updates the template, the dynamically created component does not update.

Expected behavior

It should update

Minimal reproduction of the problem with instructions

Here is a plnkr which has implemented a way to show a callout when clicking on an element. I have hooked up two different callout components (one uses OnPush and one uses Default).

https://plnkr.co/edit/vYCuDwHj64qIp6GEShC9?p=preview

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

Right now we're having to use some hacky workarounds which register child change detector refs with the parent components, and having the parent component mark the children for check. Using OnPush is necessary for the performance of our app.

Angular version: 4.0.2

Browser: all

Language: all
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-parent-of-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

i am doing correctly but the objective is being crossed

Issue 2:
Challenge Name

Roman Numeral Converter

Issue Description

I'm reporting this based on my tests of an issue another camper reported on the forums.

The thread may be found here on the FCC forum

The code pasted below fails all tests for this challenge, even though it is returning the correct answer.

Moving var converted = [] inside the function returns the exact same result, yet passes all tests.

Browser Information

Browser Name, Version: Chrome / Firefox - latest

Operating System: Mac OSX El Capitan / Ubuntu 16.04

Mobile, Desktop, or Tablet:

Your Code

var converted = [];

function convertToRoman(num) {
//use roman numerial char codes

var romans = [{
1: "I",
2: "II",
3: "III",
4: "IV",
5: "V",
6: "VI",
7: "VII",
8: "VIII",
9: "IX"
}, {
1: "X",
2: "XX",
3: "XXX",
4: "XL",
5: "L",
6: "LX",
7: "LXX",
8: "LXXX",
9: "XC"
}, {
1: "C",
2: "CC",
3: "CCC",
4: "CD",
5: "D",
6: "DC",
7: "DCC",
8: "DCCC",
9: "CM"
}, {
1:"M"
}];

var stringedNum = num.toString().split("").reverse().join("");//63

for (i = 0; i < stringedNum.length; i++) {

switch (i) {
case 0:
converted.push(romans[0][stringedNum[i]]);
break;
case 1:
converted.push(romans[1][stringedNum[i]]);
break;
case 2:
converted.push(romans[2][stringedNum[i]]);
break;
case 3:
converted.push(romans[3][1].repeat([stringedNum[i]]));
break;
case -1:
console.log("-1");
alert("No number!");
break;
}
}
//63.
return converted.reverse().join("");
}

convertToRoman(2);

Screenshot
Issue 1:
Environment

Windows build number: 10.0.19631
PowerToys version: v0.18.1
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run

Steps to reproduce

Everytime I turn on the Launcher in the PowerToys Settings, the process PowerLauncher starts using 20% to 50% of my CPU. I have a quad-core i5 CPU and my computer performance isn't an issue.

Screenshots

Here's my Task Manager the second after I turn on PT Run.

Issue 2:
PowerLauncher.exe keeps ramping up to ~60% CPU usage in task manager and then back down to 0%. It happens about every 2 seconds or so.

Environment

Windows [Version 10.0.18363.720]

PowerToys 0.18

PowerLauncher

Steps to reproduce

Start PowerToys.

Screenshots
Issue 1:
Environment

Windows build number: 10.0.18965.0 (Insider Fast)
Windows Terminal version (if applicable): 0.4.2382.0

Any other software? No.

Steps to reproduce

Open the terminal

1.1 Perhaps it's relevant that I have showTabsInTitlebar set to the default value of true

double-click anywhere inside the draggable titlebar

Image for illustration purpose of the area I mean by "titlebar":

Expected behavior

The window should maximize

Actual behavior

Nothing happens

Issue 2:
Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 0.5.2681.0 (from store)

Any other software?

Steps to reproduce

(Happy for this to be closed if it should be raised with WSL instead.)

Have WSL installed and a .bashrc file set up

Open an Ubuntu tab in Windows Terminal

Expected behavior

.bashrc is executed as this is an interactive shell

Actual behavior

.bashrc is not executed. Only .bash_profile is executed.

This can be worked around by changing the commandline from wsl.exe -d Ubuntu to wsl.exe -d Ubuntu bash - but I'm not sure if this is a problem with Terminal, or with WSL. If I use the default shortcut to Ubuntu provided by WSL, that doesn't run .bashrc either, unless I create a similar shortcut to wsl.exe by hand.