WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
For example, alt tag for images ...

Issue 2:
I just came across the following line of code in the second bootstrap waypoint:

<a href="#"><img class="smaller-image thick-green-border" src="https://bit.ly/fcc-relaxing-cat"></a>

I cannot in good conscience ignore this. A screenreader will read the resulting output in the following, rather helpful manner:

"link graphic

I appreciate the waypoint about the alt-tag being included in the FCC curriculum, please let there be no doubt about that. But I do think if FCC wants to teach proper HTML/CSS, a grave mistake like this should not be allowed to exist and the advice in the waypoint about the alt-tag should be taken for FCC's waypoints, ziplines, bonfires and oher exercises as well.

I also tripped over the lack of the 'for'-attribute in the label tag for forms. I suppose I can forgive that one for now since that attribute goes into some rather advanced semantic discussions and is exclusively for semantic correctness and accesibility, but I do hope this topic will be discussed at a later part in the curriculum. If not I'll have to write up a few waypoints meself, I reckon ;)

For completeness, the URL where I came across the offending line of code is below:

http://www.freecodecamp.com/challenges/waypoint-make-images-mobile-responsive
Issue 1:
Website or app

https://wayray.com/#how-we-work

Repro steps

not able to see

How often does this bug happen?

Sometimes

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.19.2-20ca9b565

Error message (automated)

Cannot add node "1" because a node with that id is already in the Store.

Error call stack (automated)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25708:41
at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:23923:22)
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24083:12
at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:52511:39)

Error component stack (automated)

No response

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot add node because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react

Issue 2:
Website or app

https://zhivika.ru/product/26406103_plastyr_perc_bperf_10smh18sm_n

Repro steps

Load page.

Open react components.

Click button "Смотреть все аптеки" for unfold all list.

How often does this bug happen?

Every time

DevTools package (automated)

react-devtools-extensions

DevTools version (automated)

4.13.5-0ae5290b54

Error message (automated)

Cannot add node "476" because a node with that id is already in the Store.

Error call stack (automated)

No response

Error component stack (automated)

No response

GitHub query string (automated)

https://api.github.com/search/issues?q=Cannot add node because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
Issue 1:
I can't access suscribe to router updates from child routes. It only works in AppComponent and it dosent work in DashboardComponent. This is my set up

@RouteConfig([
{ path: '/', name: 'Index', component: IndexComponent, useAsDefault: true },
{path: '/dashboard/...', name: 'Dashboard', component: DashboardComponent}
])
export class AppComponent{
constructor(private router: Router){
this.router.subscribe(route => {console.log(route)});
//works here
}
}

@RouteConfig([
{ path: '/', name: 'Home', component: HomeComponent, useAsDefault: true },
{path: '/inbox', name: 'Inbox', component: InboxComponent}
])
export class DashboardComponent{
constructor(private router: Router){
this.router.subscribe(route => {console.log(route)})
//dosent work here
}
}

Issue 2:
I test angular2 for form with many elements(300-400) and get errors. Then i test angular1 and it's ok.

angular1

angular2

chrome message: RangeError: Maximum call stack size exceeded

forefox message: InternalError: too much recursion
Issue 1:
Issue Type:

Bug Report

Ansible Version:

devel (e0147f1)

Environment:

N/A

Summary:

When trying to restrict tasks by tags all tasks are being executed. Regardless of the specified tags.

Steps To Reproduce:

Hostfile test:

localhost ansible_ssh_user=root

Playbook test-tags.yml:

- hosts: localhost
roles:
- test-tags

/roles/test-tags/tasks/main.yml:

- include: foo.yml
tags: foo

- include: bar.yml
tags: bar

/roles/test-tags/tasks/foo.yml:

- debug: msg="foo"

/roles/test-tags/tasks/bar.yml:

- debug: msg="bar"

Execute playbook:

ansible-playbook -i test test-tags.yml --tags bar --list-tasks

Expected Results:

playbook: test-tags.yml

play #1 (localhost):
debug msg="bar" (tags: all, bar)

Actual Results:

playbook: test-tags.yml

play #1 (localhost):
debug msg="foo" (tags: all, foo, bar)
debug msg="bar" (tags: all, foo, bar)

Please note that I added a debug output to ansible-playbook (see PR #6434) to see which tags are compiled for each task.

The problem seems to be: All tags are assigned to every task. So restricting via tag is completely useless in the current develop-branch.

Issue 2:
Issue Type:

Bug report in tag handling

Ansible Version:

Latest devel, as per git bisect, bug was introduced in 6577ff5

Environment:

Ubuntu, but N/A

Summary:

When running a larger playbooks contanin multiple plays with different tags, and running it with specifying a particular tag, all tasks in those plays that contain (tasks with) that tag are ran, instead of only those tasks that have the specific tag.

Steps To Reproduce:

1 - name: Restart Tomcat Servers
2 hosts: tomcat
3 gather_facts: False
4 tasks:
5 - name: trigger stop
6 debug: var=tomcat_version
7 changed_when: True
8 notify:
9 - stop_tomcat
10 tags: stop
11 - name: trigger start
12 debug: var=tomcat_version
13 changed_when: True
14 notify:
15 - start_tomcat
16 tags: start
17 handlers:
18 - include: handlers/tomcat.yml

running ansible-playbook util-tomcat-restart.yml -t stop will run both trigger tasks, not just the stop task.

Expected Results:

Run only the tasks that have a particular tag.

Actual Results:

All tasks from the play that contain some tasks with a given tag are ran.
Issue 1:
I am updating state in setState() and the page is rendered correctly, but "React Developer Tools" is showing previous state.

Objects and Arrays are updating in realtime but not "boolean / string / number values".

But when I close the dev tools window ( not switching tabs ) and reopen it, then only it shows the updated state.

I don't remember if this was the issue from prev version, but please add realtime state update functionality to it.

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

Bug

What is the current behavior?

Visual bug: showing wrong state; so user cant use devtools for debugging

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/wizardly-lewin-dlw5k

https://dlw5k.csb.app/

Open https://dlw5k.csb.app/

Open browser dev tools

select "Components", click on "App", expand selectedPairs of State

select 3+ currencies from the list on the page. State is proper for now

uncheck any not last box.

Devtools will remove the last from the list.

Uncheck something once more, and again just last item will disappear.

Click on 'bug' icon ("Log this component data to the console")

Expand data, 'State' is ok. So just a visual bug?

What is the expected behavior?

Devtools should update State properly.

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

React Developer Tools: 4.1.0 (9/19/2019)

Browser: Google Chrome 76.0.3809.132 (64bit)

OS: Windows 7 Professional SP1 64bit
Issue 1:
Bug summary

The suptitle of the figure does not show if using plt.subfigures, without defining layout to be 'constrained'.

Code for reproduction

fig = plt.figure(figsize=(20, 14))
subfigs = fig.subfigures(1, 4, wspace=0.5, width_ratios=[0.5, 1, 1, 1])

axs0= subfigs[0].subplots(nrows = 12, ncols = 1, sharex = True)
axs1 = subfigs[1].subplots(nrows = 12, ncols = 1, sharex = True)
subfigs[1].suptitle('\n A subfigure')

axs2 = subfigs[2].subplots(nrows = 12, ncols = 1, sharex = True)
subfigs[2].suptitle('\n A subfigure')

axs3 = subfigs[3].subplots(nrows = 12, ncols = 1, sharex = True)
subfigs[3].suptitle('\n A subfigure')

Actual outcome

Expected outcome

A title should be given on top of the figure

Additional information

No response

Operating system

Ubuntu

Matplotlib Version

3.6.2

Matplotlib Backend

Qt5Agg

Python version

3.10.9

Jupyter version

No response

Installation

conda

Issue 2:
Bug summary

In a fairly basic example using subfigures, a suptitle added to the parent figure is not visible:

Code for reproduction

f = plt.figure(figsize=(4, 3))
sf1, sf2 = f.subfigures(1, 2)
sf1.subplots()
sf2.subplots()
f.suptitle("It's a bird, it's a plane, it's a suptitle")

Actual outcome

Expected outcome

Visible suptitle.

Additional information

It looks like this is happening because the subfigures have a solid facecolor that obscure the suptitle:

f = plt.figure(figsize=(4, 3))
sf1, sf2 = f.subfigures(1, 2)
sf1.subplots()
sf2.subplots()
sf1.set_facecolor((.8, 0, 0, .3))
f.suptitle("It's a bird, it's a plane, it's a suptitle")

Setting the zorder of the suptitle to a large number has no apparent effect.

Matplotlib Version

3.6.2

Matplotlib Backend

module://matplotlib_inline.backend_inline
Issue 1:
if you execute

app/console

you get

Usage:
[options] command [arguments]

i think this wold be correct:

Usage:
command [options] [arguments]

what do you think?

Best regards, Oskar

Issue 2:
I propose to add the following constraints for validating Traversable instances and arrays:

Each: Validates that each entry satisfies some constraint (replaces All, which should be deprecated).

Some: Validates that at least one entry satisfies some constraint. The lower limit (default 1) and upper limit (default null, i.e. unbounded) can be configured. Alternatively, a precise number of matches can be given.

None: Validates that 0 entries satisfy some constraint (alias for Some(exactly = 0, ...))

Unique: Validates that the collection does not contain duplicates.

Example:

/**
* @Each(@GreaterThan(6))
*/
private $numbers.

/**
* @Some(@GreaterThan(6))
*/
private $numbers.

/**
* @Some(@GreaterThan(6), min = 2, max = 5)
*/
private $numbers.

/**
* @Some(@GreaterThan(6), exactly = 3)
*/
private $numbers.

/**
* @None(@GreaterThan(6))
*/
private $numbers.

/**
* @Unique
*/
private $numbers.

Each constraint should expect either a single constraint or an array of constraints to be given. That means you can also do:

/**
* @Each({
* @NotNull,
* @GreaterThan(6)
* })
*/
private $numbers.

"min" or "max" and "exactly" must not be given at the same time:

// ConstraintDefinitionException
new Some(array(
'constraints' => array(...),
'min' => 2,
'exactly' => 2,
));

Groups on inner constraints should be supported (ref #4453).

If a collection constraint has explicit groups given, it should call addImplicitGroupName() on the nested constraints with each of these groups (except "Default").

new Each(array(
'groups' => array('Default', 'Strict'),
'constraints' => new GreaterThan(6), // implicitly group "Default" and "Strict"
));

If a collection constraint has no explicit group given, its groups should be the merged result of all nested groups.

new Each(array(
'constraints' => array(
new GreaterThan(array(
'value' => 6,
'groups' => array('Default', 'Strict'),
)),
new NotNull(array('groups' => 'Filled')),
),
// implicitly group "Default", "Strict" and "Filled"
));

If both the collection constraint and a nested constraint have explicit groups given, the groups of the nested constraint need to be a subset of the groups of the outer constraint.

// ok
new Each(array(
'groups' => array('Default', 'Strict'),
'constraints' => new GreaterThan(array(
'value' => 6,
'groups' => array('Default', 'Strict'),
)),
));

// ok
new Each(array(
'groups' => array('Default', 'Strict'),
'constraints' => new GreaterThan(array(
'value' => 6,
'groups' => 'Strict',
)),
));

// ConstraintDefinitionException
new Each(array(
'groups' => array('Default', 'Strict'),
'constraints' => new GreaterThan(array(
'value' => 6,
'groups' => array('Strict', 'Sales'),
)),
));

Calls to addImplicitGroupName() on the collection constraint should be propagated to nested constraints.
Issue 1:
Bug report

Describe the bug

An index page implemented within a subdirectory behaves differently between development and production modes.

When the next server is started in dev mode everything seems to work as expected. When running in "production" mode via next build and next start the event listeners on page do not fire.

To Reproduce

I created a minimal example here: https://github.com/hoffrocket/next8bug

Expected behavior

I'd expect the same behavior in production as in dev. The event listeners should fire.

System information

OS: macOS

chrome, safari

Version of Next.js: 8.0.1

Version of node: 8.14.0

Issue 2:
Bug report

When you build next.js when the index page is located in /index/index.js instead of /index.js The client side script will not be executed when you access http://localhost/.

The built index page will register with /index (as shown below)

(window.__NEXT_P = window.__NEXT_P || []).push(["/index", function () {
var e = n("gDgk");
return {
page: e.default || e
}
}])

Moving the index.js to the pages root will restore the wanted behaviour.

It took a while for me to figure out what the actual issue is as it's working just fine in dev mode.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Check out https://github.com/adlk/nextjs-index-issue

Run npm install && npm run build && npm start

Check in DevTools if you have a log with Home: component did mount

System information

Version of Next.js: 8.0.0
Issue 1:
I loaded the local gif in the 3.7.0 version is normal, upgrade to version 4.0.0-RC1 local gif background turns green.Please help me find the problem:

Glide Version: 4.0.0-RC1

Glide load on onCreate():

This is the java code in version 3.7.0:

Glide.with(this)
.load(R.drawable.pic_placeholder_3x)
.asGif()
.fitCenter()
.dontAnimate()
.skipMemoryCache(true)
.diskCacheStrategy(DiskCacheStrategy.SOURCE)
.into(imageView);

This is the java code in version 4.0.0-RC1:

GlideApp.with(this)
.load(R.drawable.pic_placeholder_3x)
.fitCenter()
.skipMemoryCache(true)
.diskCacheStrategy(DiskCacheStrategy.NONE)
.into(placeholderImageView);

Layout XML:

<FrameLayout
android:layout_width="match_parent"
android:layout_height="match_parent"
android:background="#f6f6f6">

<ImageView
android:id="@+id/image"
android:layout_width="144dp"
android:layout_height="80dp"
android:layout_gravity="center"
android:scaleType="fitCenter" />
</FrameLayout>

Issue 2:
Glide Version 4.1.1:

**not use integration library **:

Coolpad/7320 4.2.2:

** the default DecodeFormat is still DecodeFormat.PREFER_RGB_565, the gif turn to green, but in glide 3.7, when you config it to ARGB_8888 , the gif isn't trun to green**:

Glide load line / GlideModule (if any) / list Adapter code (if any):

@GlideModule
public class MyAppGlideModule extends AppGlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
// nothing here
}
}

Layout XML:

<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical"
android:background="@color/list_background"
>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:orientation="vertical"
android:background="@drawable/list_item_shape"
android:layout_margin="5dp"
>

<ImageView
android:id="@+id/imageView1"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:paddingLeft="16dp"
android:paddingRight="16dp"
android:layout_gravity="center"
android:scaleType="fitXY"
android:adjustViewBounds="true"/>
</LinearLayout>
</LinearLayout>

LogCat:

this LogCat was show in glide 3.7.0 too, but everything is ok.
Issue 1:
The Go core packages should never leak memory.

container/list.Iter() leaks memory when the channel is not drained.

6g; hg id ec584ae2ad58 tip; GOOS=linux; GOARCH=amd64.

package main

import (
"fmt"
"container/list"
"runtime"
)

func memleak() {
l := list.New()
for i := 0; i < 1e3; i++ {
l.PushBack(make([]byte, 1e6))
}
for _ = range l.Iter() {
break
}
l.Init()
}

func main() {
for i := 0; i < 10; i++ {
memleak()
runtime.GC()
fmt.Println(i, runtime.MemStats.Alloc, runtime.MemStats.TotalAlloc)
}
}

Output:
0 1073420608 1073434744
1 2146666592 2146680728
2 3219910416 3219924600
3 4293155776 4293170008
4 5366401136 5366415416
5 6439644960 6439659288
6 7512890320 7512904696
7 8586135680 8586150104
8 9659379504 9659393976
9 10732624864 10732639384

Problems with a memory-leaking tree structure - golang-nuts
http://groups.google.com/group/golang-nuts/browse_thread/thread/371c577eb7a5cad6/72e40e8588341c3c

Issue 2:
We need to document what the rules are.
Issue 1:
Q
A

Bug report?
yes

Symfony version
3.3.10

#19973 added a default IDE file link web view, however the URL it uses is hard-coded in Resources/config/profiler.xml rather than using the route at Resources/config/routing/profiler.xml.

This means that if you use a route prefix e.g.

_profiler:
resource: "@WebProfilerBundle/Resources/config/routing/profiler.xml"
prefix: /my-prefix/_profiler

the URL produced by debug.file_link_formatter is /_profiler/open instead of /my-prefix/_profiler/open

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
~3.2

When viewing the web-profiler event (?panel=events) panel the links against the class names appear to be fixed to a hard-coded route _profile/open?file=xyz instead of being resolved using the router. I believe this might be the case anywhere file links are rendered.

Because of this when I change my development route prefixes to be anything other than the default ones given in a standard Symfony installation these links will 404.

_profiler:
resource: '@WebProfilerBundle/Resources/config/routing/profiler.xml'
prefix: /~dev/profiler

I looked at seeing whether I could implement a fix and noticed that this looks like it might be the issue, although I don't have the confidence to make this change.

symfony/src/Symfony/Bundle/WebProfilerBundle/Resources/config/profiler.xml

Line 57
in
fedbc3f

<argument>/_profiler/open?file=%%f&amp;line=%%l#line%%l</argument>

<service id="debug.file_link_formatter" class="Symfony\Component\HttpKernel\Debug\FileLinkFormatter" public="false">
<argument>%debug.file_link_format%</argument>
<argument type="service" id="request_stack" on-invalid="ignore" />
<argument>null</argument>
<argument>/_profiler/open?file=%%f&amp;line=%%l#line%%l</argument>
</service>

I personally am not affected by this as I would rather view the file in my IDE, however I thought I should report this anyway. Thanks.
Issue 1:
Database: DB2

Symfony version 2.2:

It is failing in class aclProvider.php with undefined index ancestor_id. Dynamic SQL statement has "ANCESTOR_ID" , whereas in aclProvider.php, it is defined as "ancestor_id".

Srinivasa Varrey

Issue 2:
I'm trying to extend the DateType in order to create a widget with only Year/Month (it's for a credit card expiration date). I couldn't set the DateType options to show only those 2 fields, so I tried to extend it. But when I use my new type, it throws this error:

Expected argument of type "\DateTime", "array" given

500 Internal Server Error - UnexpectedTypeException

This gist has the code used:

https://gist.github.com/990f5ea03c5f3f137861
Issue 1:
I am building my backend server based on the next.js/custome-express example, however, when I load a page I always get this error:

Refused to execute script from 'https://localhost:8081/_next/1511072683838/manifest.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

I noticed in dev the 1511072683838 is like a random number, however, in the production environment, it is an uuid. I am curious how can I use this number in my express server route, and is it safe to discard the number? e.g, having a route like:

app.use('/_next/:id/', constants.corsOptions, express.static(path.join(root, 'server', 'src', 'next', '.next')));

If I use this method and throw the :id parameter away will there be any issue (e.g security)? Or should I use this number as nonce in my pages, if that's the case how can I set the nonce.

Thanks!

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

Expected Behavior

As above.

Current Behavior

As above.

Context

Not sure if this will have any security issue.

Your Environment

Tech
Version

next
4.1.4

node
9.1

OS
Docker Linux Alpine

browser
Chrome V63

Issue 2:
I started a project based on https://github.com/zeit/next.js/tree/v3-beta/examples/with-firebase

The error I have when importing firebase in more than one component.

In this firebase start file:

`import firebase from 'firebase'

const firebaseConfig = {

apiKey: "fdsfsdfdsf",

authDomain: "fdsfdsfsdfdsf",

databaseURL: "sdfdsfdsf",

projectId: "dsfdsfdsf",

storageBucket: "dsfdsfdsf",

messagingSenderId: "dsfdsfsdfdsf"

}

const FbApp = firebase.initializeApp(firebaseConfig)

export default FbApp.auth()`

Then in the components:

import firebase from '../lib/firebaseClient'

With a single component works well, but if I add a new component with import firebase from '../lib/firebaseClient' the application fail:

Firebase: Firebase App named '[DEFAULT]' already exists (app/duplicate-app).

FirebaseError: Firebase: Firebase App named '[DEFAULT]' already exists (app/duplicate-app).
Issue 1:
Consider using the method described here: http://css-tricks.com/inheriting-box-sizing-probably-slightly-better-best-practice/ to have fewer unintended side-effects.

Issue 2:
I found this helpful while working on migrating a large legacy site over to new markup and CSS best practises.

http://css-tricks.com/inheriting-box-sizing-probably-slightly-better-best-practice/

It allows us to toggle off box-sizing for large parts of the site we haven't migrated yet, and is a nice default approach to take.
Issue 1:
I think its really nice that you can put the terminal-tabs in your titlebar but I got an issue there.

You can't move the window around klicking on the blank space in the the-bar to move the window around (highlighted in the screenshot).

Since people are moving their terminal quite often it would be nice to offer this space, so you can drag your terminal around.

Issue 2:
Your Windows build number: (Type ver at a Windows Command Prompt)

18.0.18362.53

What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

start terminal

hit ctrl+t to bring up tabs

click in the space between second tab and "+" and attempt to drag window

window won't drag, but now input is blocked

right click in window area

input is now unblocked.

This is unlikely to occur when the tabs are NOT inlined with the title bar. It is very likely to happen when tabs ARE inlined, as the free space seems like empty title bar area.

What's wrong / what should be happening instead:

Either allow window dragging from tabs bar (when inlined), or don't allow window dragging but don't lock up input. Maybe a prompt or tooltip text might help guide the user if dragging is disabled from this area.