WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Example failure at

https://app.shippable.com/builds/55b327486572ba0c00576d31

--- FAIL: TestDQ_always_pop_earliest_deadline (23.77 seconds)
delay_test.go:256: Expected delay-prority of 1s got instead got 2s
FAIL
coverage: 64.9% of statements
FAIL github.com/GoogleCloudPlatform/kubernetes/contrib/mesos/pkg/queue 92.958s

@karlkfi

Issue 2:
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:16:57Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.0", GitCommit:"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b", GitTreeState:"clean", BuildDate:"2016-09-26T18:10:32Z", GoVersion:"go1.6.3", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: AWS

OS (e.g. from /etc/os-release): Debian GNU/Linux 8 (jessie)

Kernel (e.g. uname -a): 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux

What happened:

Deployed a scheduled job from this manifest:

---
apiVersion: batch/v2alpha1
kind: ScheduledJob
metadata:
name: expire-documents
spec:
schedule: 15,45 * * * *
jobTemplate:
spec:
template:
spec:
containers:
- name: expire-documents-job
image: registry.example.com/base:alpine
imagePullPolicy: Always
args:
- curl
- -XPOST
- -v
- http://document.stage.svc.example.cluster:8080/admin/tasks/expire-documents
restartPolicy: OnFailure

imagePullSecrets:
- name: my-registry

After some time the jobs are no longer executed:

kubectl --namespace stage describe scheduledjobs
Name: expire-documents
Namespace: stage
Schedule: 15,45 * * * *
Concurrency Policy: Allow
Suspend: False
Starting Deadline Seconds: <unset>
Image(s): registry.example.com/base:alpine
Selector: <unset>
Parallelism: <unset>
Completions: <unset>
No volumes.
Labels: <none>
Last Schedule Time: Sat, 08 Oct 2016 18:15:00 +0200
Active Jobs: <none>
Events:
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
1h 31m 178 {scheduled-job-controller } Warning FailedCreate Error creating job: jobs.batch "expire-documents-1858111306" already exists
30m 1m 177 {scheduled-job-controller } Warning FailedCreate Error creating job: jobs.batch "expire-documents-1858242378" already exists
8h 1m 14 {scheduled-job-controller } Warning FailedCreate (events with common reason combined)
56s 6s 6 {scheduled-job-controller } Warning FailedCreate Error creating job: jobs.batch "expire-documents-1400211256" already exists

What you expected to happen:

Jobs are executed as defined in the manifest.

How to reproduce it (as minimally and precisely as possible):

Deploy a scheduled job and wait for some time.
Issue 1:
ie8 calculates the size of input, textarea and select fields wrong if box sizing is border-box.

maybe a workaround:

min-height: @input-height-base; // Make inputs at least the height of their button counterpart (base line-height + padding + border)
min-height: (@input-height-base - @padding-base-vertical * 2 - 2px) ~"\9"; // ie8

Issue 2:
Removing min-height from Shared size and type resets in forms.less stops inputs being bloated in IE8. Tested in IE9/10 latest FF and Chrome and dosen't seem to cause any problems.
Issue 1:
Atom version: v0.165.0

OS: elementaryOS 0.2 "Luna" (64-bit)

Minor, but annoying if you like your projects hoisted into the sidebar. This seems to work fine on Windows 7.

Issue 2:
I checked this issue list and it seems it is not a duplicate. I suppose this could be considered an enhancement request.

Atom is too heavy-weighted. Given all those features such as package management, even some support like a web-browser way, it should be alright. But taking the official release as example, they are approximately 100 Mb, which is almost the size of Firefox browser. I see for windows compilation, chromiumcontent.dll is the single biggest file, along with others.

Is there any way or work goign on to slim down Atom a little bit more?
Issue 1:
We have a dark application background. However, the browser-window initially shows as white(which causes flickering) and we want to make it custom color so it matches our application background(which will prevent the flickering).

Issue 2:
Is your feature request related to a problem? Please describe.

My application (REST client) allows to manipulate cookies when making a HTTP request. It also allows to export and import application data. It is possible to export created session cookies data but it is not possible to import them back because the URL used to set the cookie is not available.

Describe the solution you'd like

When querying for cookie data from the session class I would like to see another property with original URL used to set the cookie.

Describe alternatives you've considered

I was considering creating a database storing cookie with the url but it would defeat the purpose of using this API in the first place as I would have to duplicate the whole API.

Additional context

There are few use cases when the user would export cookie data from the application:

application backup

moving application to another machine

sharing session data with team mates so it's easier for them to use the REST client

In the application the user can configure cookies by either creating a cookie manually or by opening a browser window and logging in to a web service.

When the application makes a request to the endpoint it queries for the cookies to apply them to the request.

This feature would also simplifies cookie removal from the session. Currently when the user request from the panel on the screenshot to remove a cookie the application constructs the url from cookie domain and cookie path. However sometimes I noticed it does not work as intended. Having the URL would also allows the app to handle this issue.
Issue 1:
Bug report

Bug summary

AttributeError: module 'matplotlib' has no attribute 'verbose'

Code for reproduction

# from matplotlib import cbook, pyplot as plt, style
#
#

Actual outcome

Traceback (most recent call last):
File "C:/Users/95235/Desktop/history-1.py", line 4, in <module>
from matplotlib import cbook, pyplot as plt, style
File "D:\JetBrains\pyEnv\python363\lib\site-packages\matplotlib\pyplot.py", line 115, in <module>
_backend_mod, new_figure_manager, draw_if_interactive, _show = pylab_setup()
File "D:\JetBrains\pyEnv\python363\lib\site-packages\matplotlib\backends\__init__.py", line 62, in pylab_setup
[backend_name], 0)
File "D:\JetBrains\PyCharm 2017.3\helpers\pycharm_matplotlib_backend\backend_interagg.py", line 17, in <module>
verbose = matplotlib.verbose
AttributeError: module 'matplotlib' has no attribute 'verbose'

Expected outcome

"verbose = matplotlib.verbose"(line in in backend_interagg.py) should be "verbose = matplotlib.Verbose"

Matplotlib version

Operating system: Windows 10

Matplotlib version: matplotlib-2.2.0

Matplotlib backend (print(matplotlib.get_backend())): module://backend_interagg

Python version: python 3.6.3

Jupyter version (if applicable):

Other libraries:

pip install matplotlib

Issue 2:
Minimum amount of code to reproduce the bug:

import matplotlib.pyplot as plt

x = [0.15, 0.11, 0.06, 0.06, 0.12, 0.56]
flierprops = dict(marker='o', markerfacecolor='green', markersize=12, linestyle='none')
plt.boxplot(x, flierprops=flierprops)
plt.show()

This produces

Note the flier is a large blue plus sign, not a green circle as specified by flierprops.

This happens with Python 2.7.8 and matplotlib 1.4.0 -- haven't tested other situations.

This bug does not seem to be dependent upon the particular choice of flierprops but I haven't exhaustively tested this.

Notably, this broken example can also be found in the boxplot demo code: http://matplotlib.org/examples/statistics/boxplot_demo.html

The relevant code at that page is shown in the third line at the top and the last two lines at the bottom of this image:

And the demo graph that results from this demo code is also broken in the same way as the first example -- a large blue plus is shown instead of the specified symbol:

Lastly, note that if the the sym argument is provided that specifies the symbol desired, boxplot does seem to respect flierprops. Code example:

import matplotlib.pyplot as plt

x = [0.15, 0.11, 0.06, 0.06, 0.12, 0.56]
flierprops = dict(marker='o', markerfacecolor='red', markersize=16, linestyle='none')
plt.boxplot(x, flierprops=flierprops, sym='o') # Added sym argument!
plt.show()

Result:

If this is the intended fix or correct way to use this function, this should be made clear in the documentation and in the demo code.

Justification for this issue: There were closed issues related to this, but one seemed to involve some debate about defaults and the other seemed to concern only lower values. The bug reported here is not a problem with defaults nor just with lower fliers. Couldn't find other potential duplicates but apologies if that is the case.
Issue 1:
Version

2.5.17

Reproduction link

https://codepen.io/fjc0k/pen/KxBvbY?editors=1111

Steps to reproduce

open codepen url

open console

What is expected?

$attrs: { value: '' }

$listeners: { input: () => {} }

What is actually happening?

$attrs: {}

$listeners: { input: () => {} }

Issue 2:
Version

2.6.10

Reproduction link

https://codesandbox.io/embed/vue-template-3pnsx

Steps to reproduce

Click "toggle loading" button

What is expected?

Both child elements should have data attribute applied and should be green.

What is actually happening?

First child element is missing data attribute

Looks like div element is reused between loader and first child of the slot content
Issue 1:
Describe the issue:

Functions often accepts any ndarray as long as the elements are numbers. Using npt.NDArray[np.number] creates many mypy/pyright errors as none of the operators seems to be annotated for it.

Reproduce the code example:

import numpy as np
import numpy.typing as npt

def foo(x: npt.NDArray[np.number]):
x * 1
x * x

Error message:

error: Unsupported operand types for * ("ndarray[Any, dtype[number[Any]]]" and "int") [operator]
error: Unsupported operand types for * ("ndarray[Any, dtype[number[Any]]]" and "ndarray[Any, dtype[number[Any]]]") [operator]

NumPy/Python version information:

1.22.3 3.10.2 (v3.10.2:a58ebcc, Mar 10 2022, 19:36:59) [GCC 9.4.0]

Issue 2:
Describe the issue:

Why operating on arrays typed as npt.NDArray[np.number[Any]], the mypy plugin reports that ndarray.__mul__ cannot accept argument type int.

I would expect that an array of np.number can be multiplied by an integer.

Reproduce the code example:

# tmp.py
from typing import Any

import numpy as np
from numpy import typing as npt

arr: npt.NDArray[np.number[Any]] = np.array([1, 2])
arr * 3 # mypy error

Running mypy on the above code gives an error.

Error message:

$ mypy tmp.py
tmp.py:8: error: No overload variant of "__mul__" of "ndarray" matches argument type "int"
tmp.py:8: note: Possible overload variants:
tmp.py:8: note: def __mul__(self, Union[str, bytes, Sequence[Union[str, bytes]], Sequence[Sequence[Union[str, bytes]]], Sequence[Sequence[Sequence[Union[str, bytes]]]], Sequence[Sequence[Sequence[Sequence[Union[str, bytes]]]]]]) -> NoReturn
tmp.py:8: note: def __mul__(self, Union[_SupportsArray[dtype[object_]], Sequence[_SupportsArray[dtype[object_]]], Sequence[Sequence[_SupportsArray[dtype[object_]]]], Sequence[Sequence[Sequence[_SupportsArray[dtype[object_]]]]], Sequence[Sequence[Sequence[Sequence[_SupportsArray[dtype[object_]]]]]]]) -> Any
tmp.py:8: note: def __mul__(self, Sequence[Sequence[Sequence[Sequence[Sequence[Any]]]]]) -> Any
Found 1 error in 1 file (checked 1 source file)

NumPy/Python version information:

$ mypy --version
mypy 0.910
$ python
Python 3.9.7 | packaged by conda-forge | (default, Sep 29 2021, 19:23:11)
[GCC 9.4.0] on linux
...
>>> import numpy; print(numpy.__version__)
1.21.4
Issue 1:
when the variable is pointer of instance making with new(), finalizer isn't call for
last.

------------------
package main
import "runtime"
type foo struct { }
func bar() {
f := foo {}
runtime.SetFinalizer(&f, func(pf *foo) {
println("finalized")
})
}
func main() {
bar()
bar()
runtime.GC()
}

// finalized
// finalized
------------------
but
------------------
package main
import "runtime"
type foo struct { }
func bar() {
f := new(foo)
println("allocated", f)
runtime.SetFinalizer(f, func(pf *foo) {
println("finalized", pf)
})
}
func main() {
bar()
bar()
runtime.GC()
}
// allocated 0x7b0008
// allocated 0x7b00f8
// finalized 0x7b0008
------------------

It seems a bug.

Issue 2:
If you view an interface as a set of constraints on the implementing type, then
combining two interfaces (that are not mutually incompatible) such as:

type I interface { f(); String() string }
type J interface { g(); String() string }

has a natural interpretation that is equivalent to an interface containing the union of
such constraints. e.g. these should be equivalent:

type IJ interface { I; J }
type IJ interface { f(); g(); String() string }

but in fact the first is an error: "duplicate method: String". This is
somewhat surprising. Is there any reason not to permit this? The set-union behaviour
is easy to understand, describe and implement, and it seems useful in practise when you
have overlapping interfaces describing different aspects of a type.

(I chose String() string since I've seen many users add this constraint to their
interfaces. It could be any method though.)
Issue 1:
I have seen evidence that both tuple indexing and slicing syntax are silently allowed by rustc, rather than requiring the feature gate turned on to enable them.

It could be that I missed some step along the way where these features were officially enabled. But I think its more likely that someone has accidentally turned them both on somehow, especially since the team discussion from last Thursday on #18006 included statements that tuple-indexing is meant to be feature gated.

% cat /tmp/f.rs
fn main() {
let t = ('a', 'b', 'c');
let v = vec!['x', 'y', 'z'];
println!("t: {} v: {}", t.1, v[]);
}
% rustc-0.12-x64 --version=verbose
rustc 0.12.0 (ba4081a5a 2014-10-07 13:44:41 -0700)
binary: rustc
commit-hash: ba4081a5a8573875fed17545846f6f6902c8ba8d
commit-date: 2014-10-07 13:44:41 -0700
host: x86_64-apple-darwin
release: 0.12.0
% rustc-0.12-x64 /tmp/f.rs
% rustc --version
rustc 0.13.0-dev (4480caf2a 2014-10-18 06:22:15 +0000)
% rustc /tmp/f.rs
% ./f
t: b v: [x, y, z]
%

Issue 2:
Feature gates are generally checked before expansion so feature gates are defeated by code inside macros.
Issue 1:
Followup from a tweet from Unpkg (unpkg?) about ES6 module support:

https://twitter.com/unpkg/status/905239560988221440

For fun, try using import * as d3 from '//unpkg.com/d3?module inside a <script type=module> and watch those modules load!

It would be neat if you could just import { Component } from 'https://unpkg.com/react?module' in browsers like Safari (and soon Chrome). As far as I understand the problem, we'd just need to export an ES6 build target from Rollup.

I use "just" lightly. Hopefully it's that simple; it's probably more complicated. In any case, now we have an issue for it!

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

Request a feature

What is the current behavior?

React ecosystem was promoting ES6 classes and modules since 2014 and many packages like react-router, redux and so on, have an "es" folder in the npm package with source code in ES2015 modules. Unless I am missing something, it is strange that React itself does not offer that option.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

Install react and try to import it in a browser with native modules enabled.

What is the expected behavior?

Have an "es" folder in the npm package with ES2015 modules source code, like most React ecosystem projects do. Allow to import react from ES2015 native modules to make developer workflow more simple.

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

All versions
Issue 1:
As I mentioned on Discourse, the issetequal docstring says that issetequal(a, b) is equivalent to a ⊆ b && b ⊆ a, but this isn't the case when there are duplicate elements:

julia> versioninfo()
Julia Version 1.0.0
Commit 5d4eaca0c9 (2018-08-08 20:58 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin14.5.0)
CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.0 (ORCJIT, broadwell)

julia> a = [1,2,3];

julia> b = [1,1,2,3];

julia> a ⊆ b && b ⊆ a
true

julia> issetequal(a, b)
false

This is because the implementation assumes no duplicate elements:

issetequal(l, r) = length(l) == length(r) && l ⊆ r

Issue 2:
Due to #9513, we've decided to push the 0.3.5 release up two weeks, shooting for this weekend for a new release. Let's discuss here what we want to try and include in this release. Although it is motivated by a single issue, I see no reason to avoid other fixes that have already been merged into release-0.3/are close to being merged. In short, this should be a fully-fledged release, not a targeted bugfix.
Issue 1:
Using Version 0.201.0 (0.201.0) on OS X Yosemite.

Given this:

When I click 'Replace All' I get this:

But I expected this:

Not sure if this is a bug or by design. Either way I thought I should raise it.

Cheers,

Matt.

Issue 2:
In Sublime Text and Text Wrangler it is possible to do regex find and replace such as this

Find : ^\d{2}$\n

Replace:

to find lines that are two digits only and delete them. In Atom, it can match the lines but cannot do the replace. When clicking on 'Replace All' the text remains unchanged.

Version 0.75.0, Platform:

Mac OS X Mavericks
Issue 1:
There should be a mode of Deno that is maximum sandbox -

-No file system access at all (including modules, etc) except for the initial deno command. Put the onus on the developer to package all js/ts in a single file.

-No network at all, except for the ability to respond to http requests from localhost on a single port. no call-out of any kind.

-No console access at all.

-Any error should just successfully exit the process, no error reporting into the OS?

-No command execution at all (except for the initial Deno)

-No nothing of anything else. Just CPU, Memory, the ability to read a single file on startup, and the ability to respond to a single http response to another process on localhost.

-Would be nice to limit the request/response size of the http request

The OS/public facing process will handle

-if the process runs too long

-if Deno attempts to use too much ram or cpu time or use multiple cores

Issue 2:
This consists of

Setting the random number generator seed. We have this already.

Disabling all I/O - so turn off allow-read, allow-write, allow-net, allow-run, allow-plugin - etc.

Controlling the Date object

need a custom v8::Platform which will allow us to control the date precisely. Then we can add some APIs to allow people to change it. (Probably from the command line would be ideal?)

https://github.com/v8/v8/blob/cc1b741ef34b56d1b29cb24cb391ef38a1172ce8/include/v8-platform.h#L532-L545 So the fix is really in rusty_v8 - we need to expose those primatives
Issue 1:
Hi,

I have created HiddenEntityType (https://gist.github.com/kl3ryk/5781916), to transform value of hidden field into Entity. I was using FormBuilderInterface::getParent() to get Entity class. But in Symfony 2.3 function FormBuilderInterface::getParent was removed. So is there any way to retreive parent form data_class name (https://gist.github.com/kl3ryk/5781916#file-hiddenentitytype-php-L36)?

Issue 2:
Hi,

I thought about a new type of field type which can solve several problems i met on the user group.

The idea is to create an "hidden_entity" type which is just an hidden id in the form, and an entity fetched in the database by the DataTransformer. Here are two example of use:

The transport entity case

Imagine you have a comment which should be attached to an article. In the page, you'll maybe have your form posting to a special URL like /addComment/{article_id}, and then fetch back the article from the URL.

With hidden_entity, this would be way simplied since you'd just have to put the following on your comment form:

$builder->add('article', 'hidden_entity');

And populate if from the controller when rendering the form:

$comment->setArticle($current_viewing_article);
$form = $this->createForm(new CommentType(), $comment);

The "JS-UI" case

Just imagine you want your user to select something among a very large set of data, like a city, and use some complex JavaScript UI like autocompletion, dynamic map etc. The current symfony's entity will generate a containing the whole entries from the database, which is not acceptable in this case.
Using hidden_entity, you can easily add an hidden id to your form and your free to do whatever you want to fill it.
Hoping for feedbacks about this idea, I already wrote a prototype of this : https://github.com/Gregwar/FormBundle
Issue 1:
Bug report

Describe the bug

Simple javascript function to Router.push("/") will not work correctly.

in _app.js has:

Router.events.on('routeChangeStart', url => {
console.log(`Loading: ${url}`);
});

which is working...

in my AppBar(Material-ui Toolbar) i have a simple onClick (i've also tried with <Link> to no avail)

<Avatar
src="/static/img/favicon-96x96.png"
onClick={() => Router.push(ROUTE.LANDING)}
/>

To Reproduce

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

Create a new <Link> with href to "/" ....see if it redirects to your homepage from another page.

or

Create a new element with an onChange parameter. onChange={Router.push("/")} and see if it redirects to home page from another page.

The current page will stay rendered, however the routeChangeStart callback will fire...

Expected behavior

I expect the home page (index.js) to be rendered within a few seconds of calling Router.push or clicking a <Link> with href="/"

Screenshots

image of the routeChangeStart consoling out in _app.js

System information

OS: both macOS and Windows

i've tested with Firefox, Chrome, and Safari.

"next": "^9.0.5"

Additional context

Reopening from #5264 .

Thank you!

Issue 2:
Bug report

When attempting to navigate to some pages with a simple <Link href='...'/>, the page hangs and things break.

Go to https://nozzleio-8f0sjfbt1.now.sh/

Navigate around using the top nav bar

Go to the footer and click on the three links that contain "API Docs"

Observe the console and network tab

Expected behavior

The navigation should succeed.

System information

OS: macOS

Browser: Chrome

Version of Next.js: 9@latest

More Information

The repo for this website can be found at https://github.com/nozzle/nozzle.io on the master branch.