WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

How can I remove the background colour on the hover of a menu item, and change the font-color?

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

Expected Behavior

Print "ref is ok" in console.

Current Behavior

Warning printed:

Warning: Stateless function components cannot be given refs. Attempts to access this ref will fail.

Check the render method of withStyles(Toolbar).

in Toolbar (created by withStyles(Toolbar))

in withStyles(Toolbar) (created by Page)

Steps to Reproduce (for bugs)

<Toolbar innerRef={() => console.log("ref is ok"} />

Context

Your Environment

Tech
Version

Material-UI

React

browser

etc

Tech
Version

Material-UI
^1.0.0-beta.20

React
16

browser
Chrome 62

ts
2.6.1
Issue 1:
I'm having some difficulties to do a custom rendering for expanded choices. I'm using an entity type wich is ordering entities by a relation table, and for each different relation I have to do a group of chexkboxes, with another one at the top allowing to select all or none of the group.

My issue is that I can't do the correlation between the form views and choice views. So I think it's really complicated to do custom rendering on expanded choices.

I'm suggesting to pass the ChoiceView as a var for each choice subForm so that when iterating on the choice formview we can get access to the choice view data, giving more information to be able to render custom stuffs (when the original data is an object).

Issue 2:
When using "expanded" => true on a choice field that contains groups, the default form theme simply renders all radio buttons/checkboxes sequentially, without headings or any other indication of the group structure (at least under Twig).

From what I can tell, this issue stems from the fact that the choices in an expanded choice field are written directly from the FormView's choices variable, which is structured into groups. By contrast, expanded choice fields are represented using a series of checkbox/radio button fields, which are treated as children of the choice field - the problem being that the children are not arranged in any hierarchical structure.

The FormView for an expanded choice field does still have a choices variable like that of a collapsed choice field, but currently there is no effective way to match up the ChoiceView object with the corresponding child FormView in the template, so rendering the fields from the choices variable as with a collapsed choice field is not a viable option.
Issue 1:
function decorator(container, key) {}

class A {
@decorator // OK
fn(){}
}

let a = {
b: class B {
@decorator // Error TS1206: Decorators are not valid here
fn(){}
}
}

My use case is a controller class in an Angular 1.5 component:

const MyComponent = {
bindings: {...},
template: `...`,
controller: class MyComponentController extends BaseComponent {
@override
foo() {...}
}
}

abstract class BaseComponent {
protected foo() {...}
}

Issue 2:
TypeScript Version: 1.8.10

Code

export default new class Foo {
@someDecorator
someMethod() {}
}

Will result in an error on @someDecorator:

error TS1206: Decorators are not valid here.

It can be worked around via

class Foo {
@someDecorator
someMethod() {}
}
export default new Foo();
Issue 1:
Under What do I need? click should also be listed.

Issue 2:
This is a major backwards-compat breaking change, but I suspect not the intended design and hopefully easy to fix.

The issue is related to PR #2629, and this example follows from that:

Given blueprint bp and app app:

@bp.route('b/')
def tmp():
return "URI should be '/a/b/"

app.register_blueprint(bp, url_prefix='/a/')

In Flask 0.12 the URL is correctly /a/b, but in Flask 1.0 it's /ab.

Since issue #2629 relates to resolve double-slashes, I imagine this is a bug (and not a design decision) - and the correct solution would be to remove a slash only when there are two.
Issue 1:
Trying to use Input groups in inline form (single form or in Nav bar).

There are expected behaviour in FireFox (v26.0), but Chrom (v34.0.1809.0 dev-m) dumbs.

Trying to solve it but can't guess problem point.

Here are live example: http://jsbin.com/EreJodAC/1/

Here are screenshots:

FireFox (as expected)

Chrome

Checked on latest from master and still gets the same.

Issue 2:
When you have an input-group (I've only tested it with a button) inside a navbar the form doesn't align and makes the navbar height way longer.
Issue 1:
Bug report

Webpack supports the browser alias but it doesn't apply it to exports map.

What is the current behavior?

This pattern is supported

{
"main": "./index.js",
"browser": "./browser.js"
}

but this pattern isn't:

{
"exports": {
".": "./index.js",
"./browser": "./browser.js"
}
}

If the current behavior is a bug, please provide the steps to reproduce.

You can check out this folder: https://github.com/fregante/webpack-sandbox/tree/main/exports-browser

It also includes the webpack output (log and dist)

This is part of the output file that demoes which of the 2 files are imported for the "exports map" and "old style" imports respectively:

(() => {
var e = {
507: () => {
console.log('field: exports["."]');
},
933: () => {
console.log('field: browser');
},
},
r = {};
[clipped]

What is the expected behavior?

exports.browser should be picked up just like browser is

Other relevant information:

webpack 5.31.0

webpack-cli 4.6.0

Node.js version: v16.4.2

Operating System: macOS 11.5

Issue 2:
Bug report

What is the current behavior?

When generating a bundle with devtool: eval-source-map, the source maps don't work with the Firefox Dev Tools' console. Instead of seeing the expected file when I have an error in my code, I see bundle.js line 11739 > eval:52:29 (or equivalent).

If the current behavior is a bug, please provide the steps to reproduce.

Bundle a react app with an obvious bug that should break your code in it, bundle your code with devtools: eval-source-map as one of the options, and open Firefox Dev Tools & load the bundle in your browser.

What is the expected behavior?

When an error occurs, the Firefox Dev Tools console log should show the actual file in my source code where things have gone wrong.

Other relevant information:

webpack version: 4.33

Node.js version: 10.8.0

Operating System: Ubuntu 18.04

Additional tools: Firefox 67.0.1

It is worth noting that this worked fine as recently as last week (when I last used Firefox Dev Tools). I have updated Firefox since then. Using devtool: source-map works without issue currently. I have not tested on any other browsers.
Issue 1:
ISSUE TYPE

Feature Idea

COMPONENT NAME

yum_repository

ANSIBLE VERSION

2.3.1.0

OS / ENVIRONMENT

Control host: Fedora 26

Servers: CentOS 7.3

SUMMARY

Some public Yum repositories use multiple GPG keys and yum_repository does not support that currently.

STEPS TO REPRODUCE

- name: Enable Kubernetes yum repository
yum_repository:
name: kubernetes
description: Kubernetes
baseurl: https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64
enabled: yes
gpgcheck: yes
repo_gpgcheck: yes
gpgkey:
- https://packages.cloud.google.com/yum/doc/yum-key.gpg
- https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg
state: present

EXPECTED RESULTS

Multiple entries would be added for the "gpgkey" key in the Yum repository configuration.

gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg
https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg

ACTUAL RESULTS

gpgkey = ['https://packages.cloud.google.com/yum/doc/yum-key.gpg', 'https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg']

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

ANSIBLE VERSION

ansible 2.3.0.0
config file = ansible.cfg
configured module search path = [u'modules']
python version = 2.7.13 (default, Jun 9 2017, 12:31:00) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

Serializer seems to convert 1_ to 1 as a dictionary key

STEPS TO REPRODUCE

- hosts: localhost
connection: local
tasks:
- debug:
var: my_dict
vars:
my_dict:
0_9_2: value
1_1_0: value1
0000001: value2
1_: value3
12: value4

EXPECTED RESULTS

TASK [debug] *********************************************************************************************************************************************************************************************************************************************************
ok: [localhost] => {
"changed": false,
"my_dict": {
"0_9_2": "value"
"1_1_0": "value1"
"0000001": "value2"
"1_": "value3"
"12": "value4"
}
}

ACTUAL RESULTS

keys casted to integers when it contains '1'?

TASK [debug] TASK [debug] *********************************************************************************************************************************************************************************************************************************************************
ok: [localhost] => {
"changed": false,
"my_dict": {
"1": "value3",
"12": "value4",
"110": "value1",
"0_9_2": "value"
}
}
Issue 1:
Following code passes borrow checking leading to serious memory unsafety.

fn main() {
let mut v = Vec::new();
for _ in v.iter() {
v.push('j');
}
}

Code compiles with &c instead of _ too. Loop fails to compile only in for c in v.iter() case where there's an explicit variable with reference or when the loop is desugared manually.

Issue 2:
This simple code compiles on current master (0d3bd77) :

fn main() {
let mut vector = vec!(1u, 2u);
for &x in vector.iter() {
let cap = vector.capacity();
println!("Capacity was: {}", cap);
vector.grow(cap, &0u); // be sure to cause reallocation
*vector.get_mut(1u) = 5u;
println!("Value: {}", x);
}
}

and outputs:

Capacity was: 4
Value: 1
Capacity was: 8
Value: 2

while on 0.11 the borrow checker would complain that vector is already immutably borrowed by vector.iter().

It allows me to write 5u in vector[1] and then read it as 2u, because reallocation of the vector caused the iterator's slice to refer to freed memory.

(was found in a StackOverflow question : http://stackoverflow.com/q/25528271/2536143 )
Issue 1:
Command Queue language or simple Commands Queue

To be able to in a single command time queue up multiple commands that can either run sequentially or based on conditions(especially if integrated well).

for example, in my program, I use Mercurial, with Perl for build environment and python to run tests. Sometimes I want to locally run it like

→ C:\Users\project› q-commands (perl build.pl workspace --androidSupport=true >
if("build sucessful"),
[py tests.py --test-project=Android --test-filter=GradelTests]
| hg up -r fixedBranch)

Proposed technical implementation details

personally not sure how can we implement it but this seems super useful and new build dev friendly and overall expandable over time.

Allowing python or other languages that we can build pipelines in to have the ability to provide explicit.terminal.outs

where you can basically have on a function in python that simple returns

def isBuildSucessful():
wte.explicitoutbool("isBuildSucessful",True)

and in the terminal we can have

→ C:\Users\project›py main.py .explicit-return("isBuildSuccessful")
→ C:\Users\project› True

Issue 2:
Environment

SSH

Any other software?

# Steps to reproduce

on an SSH connection, paste the text on the screen tab position incorrectly

# Actual behavior

on an SSH connection, paste the text on the screen tab position incorrectly
Issue 1:
TypeScript Version:

1.8.10

Code

export class BaseLayoutModel extends BaseModel {
constructor(attributes?: any, options?: any) {
super(attributes, options);
}
}

export class BaseModel extends Backbone.Model {
constructor(attributes?: any, options?: any) {
super(attributes, options);
}

destroy(options?: Backbone.ModelDestroyOptions): any {
const opts = _.extend({
contentType: "application/json",
dataType: "text"
}, options || {});
super.destroy(opts);
}
}

Expected behavior:

Actual behavior:

Runtime error. BaseModel is undefined

Issue 2:
class B extends A {
constructor(msg:string) {
super(msg);
}
}

class A {
constructor(public msg:string) {

}
}

If the super class of B is defined after A you'll get a runtime error.

Just tested the above code in the typescript playground and I get the same error
Issue 1:
When a callback is called by GLFW I get no line information about where the error was thrown. Here's an example:

import GLFW
GLFW.Init()
w = GLFW.CreateWindow(640, 480, "")

function foo()
GLFW.Terminate()
throw(InexactError())
end

GLFW.SetWindowSizeCallback(w, (a, b, c) -> foo())

while GLFW.WindowShouldClose(w) == 0
GLFW.PollEvents()
end

When resizing the window, the error message is:

ERROR: InexactError()
in error at error.jl:21
in anonymous at /home/jhasse/.julia/v0.3/GLFW/src/GLFW.jl:22
in ErrorCallback at /home/jhasse/.julia/v0.3/GLFW/src/util.jl:90
in WindowSizeCallback at /home/jhasse/.julia/v0.3/GLFW/src/util.jl:56
in anonymous at no file:13
in include at ./boot.jl:245
in include_from_node1 at loading.jl:128
in process_options at ./client.jl:285
in _start at ./client.jl:354
in _start_3B_1718 at /usr/bin/../lib/x86_64-linux-gnu/julia/sys.so
while loading /home/jhasse/test.jl, in expression starting on line 12

I should point me to line 7 (throw(InexactError())).

Unfortunately I wasn't able to create a minimal working example without using GLFW, sorry. I'm not sure what exactly causes this.

Issue 2:
It seems that julia error tracebacks sometimes leave out some lines, including the one with the actual error.

When I load the following code from a script,

module M
function f()
x # line 3: error occurs here
end
function g()
f() # line 6
end
g() # line 8
end

it produces the output

in g: x not defined
in load at util.jl:230
in load at util.jl:242
at /work/toivo/code/juliastuff/code/errorline.jl:8
in load at util.jl:253

Note that both line 3, where the error occurs, and line 6, which calls it, are missing from the traceback.
Issue 1:
Here: http://docs.scipy.org/doc/numpy/reference/generated/numpy.where.html

x, y : array_like, optional
Values from which to choose. x and y need to have the same shape as condition.

Do they actually need to have the same shape as condition? Also from the docs:

>>> x = np.arange(9.).reshape(3, 3)
>>> np.where( x > 5 )
(array([2, 2, 2]), array([0, 1, 2]))
>>> x[np.where( x > 3.0 )] # Note: result is 1D.
array([ 4., 5., 6., 7., 8.])
>>> np.where(x < 5, x, -1) # Note: broadcasting.
array([[ 0., 1., 2.],
[ 3., 4., -1.],
[-1., -1., -1.]])

Issue 2:
I often use something like this:

NumpySlice = Tuple[Union[int, None, slice, ndarray], ...]

but I guess this is more general?

NumpySlice = Union[ndarray, Tuple[Union[int, None, slice, ndarray], ...]]

Also, why aren't _Shape and _ShapeLike exposed as Shape and ShapeLike? It would be nice to use those and the leading underscore makes them seem private and internal.
Issue 1:
http://jsbin.com/habucayi/2/

If I use "top" or "bottom" placement, everything is ok, but with "left" and "right" the popover is shown on the wrong place.

Issue 2:
look here:

http://jsbin.com/yalohofo/1/

The layout of the tooltips gets screwed up, if the tooltips are created when outside of the viewport !
Issue 1:
Currently, numpy.random.multivariate_normal makes use of SVD decomposition, numpy.dual.svd, on the provided covariance matrix to perform the sampling. This approach allows the use of positive semi-definite covariance matrix. However, it is not unique as the singular vectors are not guaranteed to be. In fact,

[[-1, 0],
[0, -1]]

and

[[1, 0],
[0, 1]]

can be the singular-vectors of a 2-by-2 identity matrix.

A Cholesky decomposition instead would result in an unique decomposition with the down side of only working on positive definite matrices. We could use instead a Cholesky decomposition with complete pivoting: http://www.netlib.org/lapack/explore-html/da/dba/group__double_o_t_h_e_rcomputational_ga31cdc13a7f4ad687f4aefebff870e1cc.html

It provides both advantages: works on positive semi-definite matrices and are unique (as far as I know).

Any thoughts?

Related issue: #13358

Issue 2:
Reported on the distutils-sig by Paul Moore.

A quick test later:
No BLAS/ATLAS/LAPACK causes a string of warnings, And ignoring the
rest of the error stack (which I'm frankly not interested in investing
the time to diagnose and fix) I get "RuntimeError: Broken toolchain:
cannot link a simple C program". Which is utter rubbish - I routinely
build extensions with this installation.
Issue 1:
Hi, when I'm trying to run kube-up.sh with aws and coreos i get

Attempt 1 to check for SSH to master [ssh to master not working yet]
Attempt 2 to check for SSH to master [ssh to master working]
Attempt 1 to check for salt-master [salt-master not working yet]
Attempt 2 to check for salt-master [salt-master not working yet]
Attempt 3 to check for salt-master [salt-master not working yet]
Attempt 4 to check for salt-master [salt-master not working yet]
Attempt 5 to check for salt-master [salt-master not working yet]
Attempt 6 to check for salt-master [salt-master not working yet]
Attempt 7 to check for salt-master [salt-master not working yet]
Attempt 8 to check for salt-master [salt-master running]
Creating minion configuration
./../cluster/aws/../../cluster/../cluster/aws/coreos/util.sh: line 32: $1: unbound variable

And when I'm looking at https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cluster/aws/util.sh#L945 it looks like it don't sends any arguments.

I'm on mac os x, the config I use is

export KUBE_AWS_ZONE=eu-west-1a
export AWS_S3_REGION=eu-west-1
export AWS_REGION=eu-west-1
export MASTER_SIZE=c4.large
export MINION_SIZE=r3.large
export KUBE_OS_DISTRIBUTION=coreos
export KUBERNETES_PROVIDER=aws

Issue 2:
Hello,

Is there more documentation on how to run a Kubernetes cluster using CoreOS on AWS ??

I tried the script for AWS specifying KUBE_OS_DISTRIBUTION=coreos, it started a master on ubuntu, and then tried to launch my minions but they all crashed.

I first had to modify the cluster/aws/coreos/util.sh script and delete those lines to make the script go this far:

i=$1
# TODO(bakins): Is this actually used?
MINION_PRIVATE_IP=$INTERNAL_IP_BASE.1${i}

MINION_IP=$(yaml-quote ${MINION_PRIVATE_IP})

That crashed because you dont use a loop anymore to create the minions.

Do you have a solution to use the script to start a cluster automatically, like create credentials and give me access to the cluster directly. I dont want to use the other guide in the multi-node coreos page, because it is basically useless as is. What do i do once the masters and minions are running ? SSH to get the credentials ?

I would love to be able to use the autoscaling group approach from the other script :)

I am on kubernetes version 1.0.1.
Issue 1:
Since upgrading from beta 19 to beta 21, our jest tests are failinng due to the following error:

TypeError: window.__NEXT_REGISTER_PAGE is not a function

at Object.<anonymous> (.next/bundles/pages/__tests__/create.test.js:2:8)
at handle (node_modules/worker-farm/lib/child/index.js:44:8)
at process.<anonymous> (node_modules/worker-farm/lib/child/index.js:51:3)
at emitTwo (events.js:125:13)
at process.emit (events.js:213:7)

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

Expected Behavior

I should not get this error

Current Behavior

TypeError: window.__NEXT_REGISTER_PAGE is not a function

at Object.<anonymous> (.next/bundles/pages/__tests__/create.test.js:2:8)
at handle (node_modules/worker-farm/lib/child/index.js:44:8)
at process.<anonymous> (node_modules/worker-farm/lib/child/index.js:51:3)
at emitTwo (events.js:125:13)
at process.emit (events.js:213:7)

Steps to Reproduce (for bugs)

import { shallow, mount } from 'enzyme'
import React from 'react'
import renderer from 'react-test-renderer'

import sinon from 'sinon'

import ConnectedLogoutPage from '../logout.js'
describe('Page: /logout', () => {
describe('Snapshot Testing', () => {
it('/logout renders"', () => {
const component = renderer.create(
<ConnectedLogoutPage url={{ pathname: '/logout' }} />
)
const tree = component.toJSON()
expect(tree).toMatchSnapshot()
})
})

Context

Your Environment

Tech
Version

next
3.0.0-beta21

node
8.2.1

OS
Mac OS 10.12.4

browser
command line

etc

Issue 2:
Hi! I am having some trouble getting set up with Redux and Apollo.

The existing with-redux-and-apollo example is only compatible with Apollo 1. Apollo 2 severs out-of-the-box support for redux in favor of Apollo's client side state management, but luckily https://github.com/rportugal/apollo-cache-redux gives you a way to still use redux with Apollo 2. That being said, I'm brand new to Nextjs and setting up the dev environment with Apollo 2 and Redux has been challenging, if anyone has ideas about how to accomplish this please let me know! An updated example would be greatly appreciated :)

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

Your Environment

Tech
Version

next
beta

node
9.0.0

browser
chrome
Issue 1:
Environment

Windows build number: 10.0.18362.207
Windows Terminal version (if applicable): Daily build from 7/4/2019

Any other software?

Steps to reproduce

Just run WindowsTerminal and make sure it is the active window. I also have the dark theme configured on my system with a Blue accent color.

Expected behavior

The window title bar area not covered by tabs should reflect my configured accent color - Blue like this:

BTW the above is from the store version of WT so something has changed for the worse.

Actual behavior

The window title bar area not covered by tabs is black:

Also, not a fan on the rounded corners. Every other Window on my system uses my accent color (and not rounded corners) e.g.:

File Explorer:

Notepad:

You get the idea.

Issue 2:
Description of the new feature/enhancement

To help reduce defects and provide better testing, SAL annotations should be applied to all applicable code in this project that utilizes C/C++. Guidance for this can be found at https://docs.microsoft.com/en-us/visualstudio/code-quality/using-sal-annotations-to-reduce-c-cpp-code-defects?view=vs-2019

SAL is the Microsoft source code annotation language. By using source code annotations, you can make the intent behind your code explicit. These annotations also enable automated static analysis tools to analyze your code more accurately, with significantly fewer false positives and false negatives.

A clear and concise description of what you want to happen.

For now, I'd just ensure it's applied to new PRs. Going back to the other code can be done as time permits. A quick action that can be taken in reference to this issue is to update the Contributor's Guide

This issue can be a placeholder to remain open until SAL annotations are applied across the entire code base (similar to the issues for adopting C++ iso standards).
Issue 1:
Context:

Playwright Version: [1.20.1]

Operating System: [Linux]

Node.js version: [16.14.0]

Browser: [Electron]

Extra: [Electron app]

Code Snippet

const electronApp = await electron.launch({ executablePath: ’xxx.AppImage‘ });
const winCount=electronApp.windows().length;
const window = await electronApp.firstWindow();

Describe the bug

Can't get the electron app when using AppImage, but launch electron main js file is ok

Using main.js is ok

The below code can start electron app normally and the window can return back normal.

const electronApp = await electron.launch({ args: ['main.js'] });
const window = await electronApp.firstWindow();

Issue 2:
1. using main.js

const electronApp = await electron.launch({ args: ['main.js'] });

const window = await electronApp.firstWindow();

The above code can start electron app normally and the window can return back normal.

2. using AppImage

const electronApp = await electron.launch({ executablePath: ’xxx.AppImage‘ });

const winCount=electronApp.windows().length;

const window = await electronApp.firstWindow();

The above code can start electron app normally, but can't get the window, and i the winCount variable is 0.

So I'm a little confused why can't get the window with AppImage？