WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
It is a great option to have HTML tag fieldset and legend during form builder .Is it available in the current Symfony2 version. I didn't see the option to build forms using HTML tags fieldset and legend.

Srinivasa Varrey

Issue 2:
I would like to add a convenience type "fieldset" which extends "form", renders as fieldset and has the "virtual" (or "inherit_data" after #6573) option set by default.

This should be implemented after #6573 is merged.
Issue 1:
If you leave the the modal control provided by the 'Vim Mode' package in command mode and disable the package, all editor panes will be left in an un-usable state where they do not accept any input until restarting the entire app.

On disabling the package, the modal state should be restored to the usual input mode.

Issue 2:
Steps to reproduce:

Enable vim-mode

Go to command mode

Disable vim-mode from the settings tab

Try to type or escape command mode!
Issue 1:
One is that the CanvasRenderer was moved to a new directory. Not very clear why?

<canvas id="myCanvas" width="600" height="900"></canvas>
var renderer = new THREE.CanvasRenderer({canvas: $("#myCanvas")[0]});

and CanvasRenderer is not longer working but WebGLRenderer is Ok.

Issue 2:
Is the CanvasRenderer class missing in the latest build?
Issue 1:
Glide Version: 4.6.0

implementation 'com.github.bumptech.glide:glide:4.6.0'

kapt 'com.github.bumptech.glide:compiler:4.6.0'

Integration libraries:

implementation 'com.github.bumptech.glide:okhttp3-integration:4.6.0'

Issue details / Repro steps / Use case background:

Can't compile on Android Studio 3.1-beta1 with version 4.6.0, Glide 4.5.0 compiles fine.

Stack trace / LogCat:

error: incompatible types: NonExistentClass cannot be converted to Annotation @error.NonExistentClass() ^

Issue 2:
It's simply not there, but it used to be in 4.5.0. In fact, all four transitive dependencies found in the pom for 4.5.0 are missing in 4.6.0.
Issue 1:
<div class="cell" @click="linkTo">
<div class="cell-wrapper">
<div class="cell-title">
<slot><slot>
</div>
<div class="cell-link" v-if="isLink">
<i class="iconfont"><i>
</div>
</div>
</div>

<vcell>
<div class="cell-input">
<span>电话：</span>
<input type="text" name="name" value="" placeholder="请填写收货手机号码">
</div>
</vcell>

Vue.js version

2.0.8

Issue 2:
Version

2.4.2

Reproduction link

https://jsfiddle.net/5k4ptmqg/89/

Steps to reproduce

In a component render function, return an element that contains a slot directly followed by raw text.

What is expected?

New content completely replaces the old content on re-render.

What is actually happening?

New content is appended to the old content on re-render.

Seems like this was fixed for render functions compiled from templates in 2.1.5.

Release notes for that version says:

Small across-the-board performance improvement for render functions compiled from templates. They now skip the normalization of nested children arrays based on information inferred from the templates at compile time.

I couldn't reproduce this in .vue files in a project generated from vue-cli Webpack template. JSX is affected, as can be seen in this issue and, render functions, as seen in the linked fiddle.
Issue 1:
13:41:01 Bringing down cluster
13:41:49 ERROR: (gcloud.compute.instance-groups.managed.delete) Some requests did not succeed:
13:41:49 - Internal Error
13:41:49
13:41:51 ERROR: (gcloud.compute.instance-templates.delete) Some requests did not succeed:
13:41:51 - The instance_template resource 'e2e-slow-minion-template' is already being used by 'e2e-slow-minion-group'
13:41:51
13:41:57 Updated [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/zones/us-central1-f/instances/e2e-slow-master].
13:42:44 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/zones/us-central1-f/instances/e2e-slow-master].
13:43:09 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/global/firewalls/e2e-slow-master-https].
13:43:26 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/global/firewalls/e2e-slow-minion-all].
13:43:27 Deleting routes e2e-slow-5f46aa47-79b1-11e5-bafa-42010af00002 e2e-slow-96a9332a-79b7-11e5-bafa-42010af00002 e2e-slow-a8196f66-79b0-11e5-bafa-42010af00002
13:43:49 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/global/routes/e2e-slow-5f46aa47-79b1-11e5-bafa-42010af00002].
13:43:49 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/global/routes/e2e-slow-96a9332a-79b7-11e5-bafa-42010af00002].
13:43:49 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/global/routes/e2e-slow-a8196f66-79b0-11e5-bafa-42010af00002].
13:43:57 Deleted [https://www.googleapis.com/compute/v1/projects/k8s-jkns-e2e-gce-slow/regions/us-central1/addresses/e2e-slow-master-ip].

Issue 2:
Our kubernetes-upgrade-gce Jenkins job has been broken for quite a while now, and it looks like it's due to target pools and/or forwarding rules leaking and exceeding quota:

Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer: creating loadbalancer
Sep 2 00:48:45.094: INFO: event for mutability-service-test: {service-controller } creating loadbalancer failed: error creating load balancer (will retry): failed to create external load balancer for service e2e-tests-services-mrlvq/mutability-service-test: googleapi: Error 403: Quota 'TARGET_POOLS' exceeded. Limit: 50.0

I've cleared out the old rules, and I'll try to diagnose what's leaking them and why.
Issue 1:
useContext hook have a problem. If you for example create a context like this:

import React, { createContext, useState } from 'react';

export const DummyContext = createContext();

export const DummyProvider = (props) => {
const [state1, setState1] = useState('');
const [state2, setState2] = useState('');
const [state3, setState3] = useState('');

return (
<DummyContext.Provider
value={[
[state1, setState1],
[state2, setState2],
[state3, setState3]
]}
>
{props.children}
</DummyContext.Provider
)
}

Let's say I have also wrote something like this:

function App() {
return (
<DummyProvider>
<SomeComponent/>
</DummyProvider>
);
}

If I want to use that context inside SomeComponent, I will have to call those states and handlers in the exact order I have wrote inside DummyContext, because it seems React is looking for states and handlers by their index, instead of the name. If I don't use those states and handlers in the exact order, values will get mixed.

Other issue with that is that I can't call only handler for that state, but I also have to include that state even tho I might not use that state inside that component, but only that state handler. If I only include handler, it will give me error like 'handler is not a function', if we say that handler is the name of the actual handler.

Wouldn't it be better if it looks for those states by their name (since there can't be duplicate states in the context), so I would be able to include only those states I want from the context? Less code and it would be easier to maintain that code.

Issue 2:
I suddenly couldn't build my react project. This error seems to appear for many people.

https://stackoverflow.com/questions/52339225/react-typescript-2312-14-duplicate-identifier-librarymanagedattributes

https://stackoverflow.com/questions/52323056/typescript-error-duplicate-identifier-librarymanagedattributes

ant-design/ant-design#11697

https://stackoverflow.com/questions/52399839/typescript-duplicate-identifier-librarymanagedattributes

yarn build:

Failed to compile.

C:/dev/project/frontend/node_modules/@types/prop-types/node_modules/@types/react/index.d.ts
(2312,14): Duplicate identifier 'LibraryManagedAttributes'.

error Command failed with exit code 1.

It looks like LibraryManagedAttributes is defined in the following files:

node_modules/@types/react/index.d.ts

node_modules/@types/prop-types/node_modules/@types/react/index.d.ts

node_modules/@types/react-overlays/node_modules/@types/react/index.d.ts

....

What is the expected behavior?

No error.

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

"@types/react": "^16.4.14",
"@types/react-dom": "^16.0.7",
"@types/prop-types": "^15.5.5",
"react": "^16.5.2",
"react-dom": "^16.5.2",
"prop-types": "^15.6.2",
Issue 1:

Issue 2:
From another thread proposed by @thockin:

"make a cluster of 1 minion, create

an RC of 50, then ramp that up in increments of 50 until it breaks.

Go figure out why it broke (I already mentioned 2 node-related issues

in the other thread) and repeat until we can get 250 pods on a machine

with none of them randomly crashing or getting killed.

Then focus on making apiserver not suck for listing those 250.

Then focus on making scheduler not suck for scheduling 250 new pods quickly.

"
Issue 1:
Challenge Center Text with Bootstrap has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0.

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

My code:

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

h2 {
font-family: Lobster, Monospace;
}

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

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

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

<div class="container-fluid">
<h2 class="red-text">CatPhotoApp</h2>

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

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

<img src="https://bit.ly/fcc-running-cats" class="img-responsive" alt="Three kittens running towards the camera. ">
<p>Things cats love:</p>
<ul>
<li>cat nip</li>
<li>laser pointers</li>
<li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
<li>flea treatment</li>
<li>thunder</li>
<li>other cats</li>
</ol>
<form action="/submit-cat-photo">
<label><input type="radio" name="indoor-outdoor"> Indoor</label>
<label><input type="radio" name="indoor-outdoor"> Outdoor</label>
<label><input type="checkbox" name="personality"> Loving</label>
<label><input type="checkbox" name="personality"> Lazy</label>
<label><input type="checkbox" name="personality"> Crazy</label>
<input type="text" placeholder="cat photo URL" required>
<button type="submit">Submit</button>
</form>
</div>

Hello,

I can't put my cursor on the h2 element lign to modify the part to make it "text-center". My cursor goes everywhere else, but not there...

Thank you very much for your help.

Issue 2:
In all the exercises, we the users are forced to press the enter key before writing any code.

Update:

We have locked the conversation temporarily on this thread to collaborators only, this has been resolved in staging, and will be live soon.

The fix can be confirmed on the beta website.

The workaround currently on production website is:

Press the Enter key on the challenge editor and then proceed with the challenge.

Apologies for the inconvenience meanwhile.

Reach us in the chat room if you need any assistance.
Issue 1:
Environment

Windows build number: Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

Open any console (I'm using PowerShell for this issue submission). After you open 3 tabs you get tab scroll bar buttons on either end.

Expected behavior

When opening many tabs I expect them to grow across the top like in any web browser and only show tab scroll bar buttons when needed (I have more tabs than the window can display).

Actual behavior

I only ever see my 3 tabs and I have to scroll. A screenshot of this issue can be seen on my twitter feed... https://twitter.com/flying_maverick/status/1192882256517324800

Issue 2:
Environment

Windows build number:
Platform ServicePack Version VersionString
-------- ----------- ------- -------------
Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable):
0.4.2382.0
Any other software?

Steps to reproduce

I install WSL - Ubuntu in Windows 10, want setup WSL in Windows Terminal. If change profile fontFace from Consolas to Ubuntu Mono derivative Powerline (https://github.com/powerline/fonts/tree/master/UbuntuMono), Windows Terminal will crash and close.

{
"acrylicOpacity" : 0.5,
"background" : "#012456",
"closeOnExit" : true,
"colorScheme" : "Campbell",
"commandline" : "wsl.exe -d Ubuntu /bin/bash -c zsh",
"cursorColor" : "#FFFFFF",
"cursorShape" : "bar",
"fontFace" : "Ubuntu Mono derivative Powerline",
"fontSize" : 10,
"guid" : "{d5ed219b-a9ca-4618-8250-d6b965766ba6}",
"historySize" : 9001,
"icon" : "ms-appx:///ProfileIcons/{61c54bbd-c2c6-5271-96e7-009a87ff44bf}.png",
"name" : "Ubuntu",
"padding" : "0, 0, 0, 0",
"snapOnInput" : true,
"startingDirectory" : "%USERPROFILE%",
"useAcrylic" : true
},

Expected behavior

Run wsl.exe with Powerline font in Windows Terminal.

Actual behavior

Windows Terminal crash and close.
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

( dateVariable | date:'yMMMMdjm') is producing '2016May1311 AM0'

Expected/desired behavior

should produce May 13, 2016 11:00 AM like it was before updating

Please tell us about your environment:

Angular version: 2.0.0-rc.2

Browser: [Chrome 51.0.2704.103 m]

Language: [TypeScript 1.8.10]

Issue 2:
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

Date pipe keeps the order of date components when using a custom format. According to the docs (https://angular.io/docs/ts/latest/api/common/index/DatePipe-pipe.html) this shouldn't be the case: 'In javascript, only the components specified will be respected (not the ordering, punctuations, ...) and details of the formatting will be dependent on the locale.'

Expected behavior

The date pipe should ignore ordering and whitespaces etc, it should only care about the date components and format the output date according to the locale.

Reproduction of the problem

http://plnkr.co/edit/fCZ4oVcn5qsnNssvSnar?p=preview

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

To be able to use custom date formats.

Please tell us about your environment:

macOS Sierra, Visual Studio Code, NPM 3.10.3

Angular version: 2.0.0 (Final release)

Browser: all

Language: TypeScript 2.0.2

Node (for AoT issues): node --version = v6.3.0
Issue 1:
Request

I want to request an option to omit runtime dependencies when auditing dependencies using npm audit. I would expect it to work identically to --omit dev, --omit optional, and --omit peer but instead for dependencies required through the "dependencies" field of package.json.

Reasoning

This may sound like a surprising request, but my reasoning is as follows:

As a "library" - i.e. a package of code that is never run on it's own but only as part of a larger application, ex. lodash - maintainer I don't necessarily need to worry about vulnerabilities in runtime dependencies. In particular, say my library depends on some dependency and supports ^2.0.0 of that dependency. For most classes of vulnerabilities1, if there's a vulnerability in 2.1.0 of this dependency that is not relevant to me as a library maintainer. The library itself will never run the vulnerable code in an interesting setting and users of my library can safely upgrade to 2.1.1 of this dependency whenever they want.

Now, as a library maintainer I could have ^2.0.0 in my manifest and depend on 2.1.1 in my lockfile. However, as a library maintainer I'd (personally) want to depend on exactly the minimum version that is support (2.0.0 in this case) during development to ensure my library stays compatible with that version of the dependency. Additionally, I (personally) consider bumping the version of a runtime dependency, even within the ^2.0.0 range, a breaking change; EDIT: this statement is incorrect.

Considering all that, I think it should be possible to omit runtime dependencies from the npm audit results - because for library maintainers they may not be directly relevant.

If there's anything incorrect about my assessment, please do point it out 🙂

Footnotes

Using a broad definition of "vulnerabilities" here, in line with what npm audit might report on. Things like malware in a dependency would constitute a problem even in the scenario I'm describing. ↩

Issue 2:
16696 silly extract google-closure-compiler-java@20190415.0.0 extracted to /data/data/com.termux/files/home/craze/fir>16697 http fetch GET 200 https://registry.npmjs.org/firebase/-/firebase-7.5.2.tgz 336498ms 16698 silly extract firebase@7.5.2 extracted to /data/data/com.termux/files/home/craze/firebaseui-web/node_modules/.s>16699 http fetch GET 200 https://registry.npmjs.org/google-closure-compiler-linux/-/google-closure-compiler-linux-201>16700 silly extract google-closure-compiler-linux@20190415.0.0 extracted to /data/data/com.termux/files/home/craze/fi>16701 http fetch GET 200 https://registry.npmjs.org/google-closure-library/-/google-closure-library-20190415.0.0.tgz 316702 silly extract google-closure-library@20190415.0.0 extracted to /data/data/com.termux/files/home/craze/firebaseu>16703 timing npm Completed in 397469ms 16704 error cb() never called! 16705 error This is an error with npm itself. Please report this error at: 16706 error https://npm.community
Issue 1:
When i use com.github.bumptech.glide:okhttp3-integration:1.4.0 ,then build error.And i do not find the package glide-parent in mvnrepository.

glide version 3.7.0

Issue 2:
It seems like something has gone wrong while deploying the OkHttp3 integration to the Maven repos

http://repo1.maven.org/maven2/com/github/bumptech/glide/okhttp3-integration/1.4.0/okhttp3-integration-1.4.0.pom

<dependencies>
<dependency>
<groupId>glide-parent</groupId>
<artifactId>library</artifactId>
<version>unspecified</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>3.0.1</version>
<scope>compile</scope>
</dependency>
</dependencies>

The dependency to Glide itself is wrong and doesn't work.

Workaround for now:

compile 'com.github.bumptech.glide:glide:3.7.0'
compile ('com.github.bumptech.glide:okhttp3-integration:1.4.0'){
exclude group: 'glide-parent'
}

1.5.0 is released, there should be no workaround needed
Issue 1:
Original ticket http://projects.scipy.org/numpy/ticket/1501 on 2010-06-03 by trac user dgoldsmith, assigned to @pv.

Presently, the docstring standard does not specify how to note that an object is to be deprecated; it has been proposed that this needs to be rectified.

Obviously, this should be an optional section in general, but required for objects once it is decided that they are to be deprecated.

Discussion on scipy-dev agreed that this section should be at or near the top, but at the top or between the One-line and Extended Summaries have both been proposed - we will try to reach a consensus here.

Proposed format is to utilize Sphinx' .. deprecated:: directive; someone please provide a concrete example of what this looks like (for example, does this directive support multi-line content, and if so, what does that look like).

Proposed content: summaries of deprecation schedule (in version number time, not real time) and justification for deprecation (e.g., being replaced, duplicates extant functionality elsewhere); existing alternatives to obtain the same functionality. (Feel strongly that it should contain something else? Add it below as a comment.)

IMO, we should try to decide on this and update the standard by June 15 at the latest.

Have I forgotten anything?

Issue 2:
Describe the issue:

I have a 4D array of shape [12, 11, 18, 3]. When I use np.arange() to do advanced indexing on the first and third dimensions, and index the 4th dimension with an integer, the return shape is [12, 11, 18], as expected. However, when I use np.arange() to do advanced indexing on the second dimension, the output shape is [11, 12, 18], which has the first and second dimensions transposed.

Reproduce the code example:

import numpy as np
voxels = np.zeros((12, 11, 18, 3))

print(voxels[np.arange(12), :, :, 0].shape)

print(voxels[:, np.arange(11), :, 1].shape)

print(voxels[:, :, np.arange(18), 2].shape)

print(np.version.version)

Error message:

Expected output:
(12, 11, 18)
(12, 11, 18)
(12, 11, 18)
Actual output:
(12, 11, 18)
**(11, 12, 18)**
(12, 11, 18)

Runtime information:

numpy 1.22.3

Context for the issue:

No response
Issue 1:
Symfony version(s) affected: 3.4.9 onwards

Description

This bug, which seems to be introduced in Cache component's version 3.4.9 does not invalidate cache by tags. How to reproduce / possible solution can be found at Stack overflow thread: https://stackoverflow.com/questions/50290019/symfony-doesnt-remove-cache-by-tags

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
^4.0

I am using the TagAwareAdapter so I can invalidate my REDIS cache by tag. The problem is that, while the cache item gets invalidated, this change does not persist between requests.

See this reproduction repo , it has four commands:

One that populates the cache, one that invalidates the cache by tag, one that fetches the keys and one that does all three in a single command.

Expected behaviour:

$ bin/console app:add
$ bin/console app:invalidate
$ bin/console app:get

The final command should output:

item-0, isHit:false
item-1, isHit:false
item-2, isHit:false
item-3, isHit:false
item-4, isHit:false

Actual output:

item-0, isHit:true
item-1, isHit:true
item-2, isHit:true
item-3, isHit:true
item-4, isHit:true

Running the command $ bin/console app:add-invalidate-and-get works as expected