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

Expected Behavior

When a popover is closed, a document that is longer than the viewport's height should remain at its current position

Current Behavior

Under certain scenarios, the page will jump to a previously clicked position.

Steps to Reproduce (for bugs)

This can be reproduced on the Popover demo page. I have reproduced this on Windows as well. I have not been able to reproduce it on Firefox / Safari.

On the demo page, in Chrome:

Click 'Open Popover' under the section 'Anchor Playground'.

Click outside of popover to close it.

Scroll down to section 'Mouse over interaction'

Hover over 'Hover with Popover.'

Mouse out of 'Hover with Popover.'

Page will snap up to top of page.

Context

In my app, this error seems to be triggered only if I click on certain elements, scroll the page to a different part of the document and then trigger/close a new popover. I can't determine whether this is related to #8040, but due to the browser-specific nature of this issue, I suspect it isn't.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.30

React
16.2.0

browser
Chrome 63.0.3239.132 (extensions disabled)

OS
macOS 10.13.2 + Windows 10 (Fall Creators, v1709)

Issue 2:
For a specific tab bar, I wanted to tweak the color of not-currently-selected tabs to make it more different from the disabled state. Using the classes system, I had to override rootPrimary (expected), but since that style is applied to all three states of the tab, I had to also override rootPrimaryDisabled and rootPrimarySelected.

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

Expected Behavior

It would be easier if there was an extra class rootPrimaryUnselected that I could use to set just the attributes specific to the unselected state, while rootPrimary would contain attributes common to all three states.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.23

React
15.6.2

browser

etc
Issue 1:
A few points of improvement of the Redis example on https://github.com/kubernetes/kubernetes/tree/master/examples/redis:

Configuration files should include only fields that deviate from the default in order to clarify. For example for redis-master.conf it could probably be (excluding comments) using CONFIG GET to check, or just use a single redis.conf like:

save 900 1
save 300 10
save 60 10000
dir /redis-master-data
slaveof ${master-ip} ${master-port} # only for slave, not when bootstrapping.

Describe how to use in clients (should be to use the redis-sentinel host name but should be documented)

Describe how to upgrade to newer versions of Redis, preferably using the Deployment Job.

Could simplify run.sh:

Use cat some.config.template | envsubst > some.config for both cases: launchsentinel() and launchslave()

Use Kubernetes args: ["redis-server", "/redis-master/redis.conf"] to start the master.

Use Kubernetes args to ask the redis-master Pod to start with master IP set to $(hostname -i).

Possibly even remove completely run.sh

Remove to describe redis-proxy.yaml

Extra question: Instead of while true, why not just let Kubernetes handle that? It seems useful to see pods restarting vs seeing them running. Of course one should include some probes (could be in the example as well), so that it'd get restarted anyway.

Issue 2:
Right now, when users create federation resources (for ex: services, namespaces), we create them in federation control plane and all underlying kubernetes clusters. We need to enable users to be able to specify a subset of kubernetes clusters in which that resource should be created.

For ex: while registering a cluster, user needs to create a secret with kubeconfig for that cluster. This secret is required only in the federation control plane and not in the underlying kubernetes cluster. We need a way for users to specify that this secret should not be created in any of the underlying kubernetes clusters.

Proposal: Support annotation with key federation.beta.kubernetes.io/cluster-selector. Value will be a struct ClusterSelector which be exactly same as NodeSelector.

All federation controllers will be looking for this annotation to decide in which kubernetes clusters should that resource be created.

Note: If the create request was sent to federation apiserver, then the resource will always be created in federation control plane. This cluster selector is to decide in which kubernetes clusters should the resource be created in.

Work items:

Define ClusterSelector in the API.

Update existing federation controllers to honor the annotation (Just services controller for now)
Issue 1:
Kernel parameters are not parsed when importing resources in routing.yml:

_nested:
resource: %kernel.config_dir%/file_name.yml

It would be nice to be fixed.

Issue 2:
When using Symfony without bundles, the only thing making it difficult is that in routing.yml, you can't reference the kernel.root_dir parameter. Without this, you have to always have your resource definitions be relative to the config file, which is pretty ugly.
Issue 1:
I would like to compute the matrix exponential of many small matrices at once. This works, but is slow:

import numpy as np
import scipy.linalg

A = np.random.rand(3, 3, 777)

exp_A = np.array([
scipy.linalg.expm(dt * W[..., k])
for k in range(m)
])

scipy.linalg.expm(A)

It'd be great of expm could be vectorized.

Issue 2:
Continuation of discussion from #10534. Several suggestions from @rlucas7 there:

Quantile fits

post-hoc "tests", including Bayesian methods (e.g. https://arxiv.org/pdf/1506.06101.pdf)

meta-analysis along the lines of scipy.stats.combine_pvalues

more options for censoring / truncation

bootstrapping (see gh-13371)

non-parametric versions of hypothesis tests (e.g. several in Hollander and Wolf)

intervals beyond confidence intervals (prediction intervals, tolerance intervals, HPD (Bayesian))

fit methods for rv_discrete classes - (see gh-15436)

(@chrisb83) exact calculation of p-values, where possible (see gh-13899), (@mdhaber) especially for ties

(@mdhaber) distribution-specific documentation of each distribution method (see gh-10328)

(@mdhaber) overhaul of distribution test suite (e.g. tests of every method with array input)

(@mdhaber) unify stats and mstats with consistent support for axis, nan_policy, and masked arrays (see gh-14651)

(@mdhaber) overhaul of rv_generic and subclasses
Issue 1:
Summary of the new feature/enhancement

Request for an option to allow Fancy Zone colors to match to the system light/dark mode.

Proposed technical implementation details (optional)

Under Appearance, provide a "follow system theme" option (on/off switch or checkbox)

When "follow system theme" is enabled, the custom color settings (inactive, highlight, border color) are disabled and the zones follow the system color mode (similar color to the background of the alt-tab dialog).

This would allow the zones to match the look/feel (color tone) of the user's desktop environment and visually look similar to other UI throughout the OS.

Issue 2:
Summary of the new feature/enhancement

Allow FancyZones to sync with system color settings.

Proposed technical implementation details (optional)

A slide toggle that enables FancyZones to sync to the system color themes. This would disable the color picker regions, and apply the following colors:

active color - The system color, whether user selected, or automatically picked from the background.

inactive color - Based on the current light / dark theme settings in Windows

border color - a darkened version of the active color.

Essentially, FancyZones would dynamically adjust based on whatever these current settings are. This includes updating if a wallpaper slideshow causes the system color to change via the Automatically pick an accent color from my background setting.
Issue 1:
I get the following warning under React16

React does not recognize the valueLink prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase valuelink instead. If you accidentally passed it from a parent component, remove it from the DOM element.

in textarea (created by EnhancedTextarea)

....

MUI version 0.19.3

Issue 2:
The style for <Tab> labels https://github.com/callemall/material-ui/blob/v1-beta/src/Tabs/Tab.js#L81 is a smaller font-size at screens > 960px. This seems counterintuitive to me and I was wondering if this was intended or a typo?

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

Expected Behavior

font-size should increase at larger screen sizes

Current Behavior

font-size decreases at larger screen sizes
Issue 1:
Summary of the new feature/enhancement

show the historical list of selected process\windows when opening the search bar(before you start typing).

This could be useful replacements for Alt-tab that's specific to the usage of windows walker.

Proposed technical implementation details (optional)

whenever you select a window from the list, maintain the processID and other relevent data inside an array, and shift further the list when you select other processes.

Issue 2:
Summary of the new feature/enhancement

Provide a history of the last x commands via arrow up and down keys. This would help to prevent typing similar commands.

For example I typed > ping x.x.x.x and after that I opened I don't know code and then I would like to execute the ping command again. It would be nice to just open the launcher (PowerToys Run) and click the down arrow to get the last command "> ping x.x.x.x" before I typed code (EDIT: I commented out this part since the > action key already works similarly to this feature request, what it's not implemented it's the general history outside of specific plugins)

Proposed technical implementation details (optional)

make the implementation configurable to have the history or not and let users define the amount of entries like 20 entries.
Issue 1:
Description

Add justification reason before pausing a DAG, and the UI should ask for unpause deadline datetime.

Use case / motivation

Sometimes we go to the Airflow UI to find out that a DAG is disabled but we can't link back to why it's paused, and who paused it.

If we implemented this change, it will be much easier to know who disabled the DAG, why, and when the DAG will be unpaused again.

Are you willing to submit a PR?

Related Issues

Issue 2:
Description

It would be great to have a way to add a justification when pausing a DAG.

This could be also shown on when a DAG is paused to understand why the DAG is not active.

Use case / motivation

We use a lot of DAGs on a Airflow project right now and every time a DAG needs to be paused we open a issue on our issue tracker and communicate with the rest of the team about this change. This is done totally outside of Airflow right now and it's hard to keep track of why a given DAG on a given environment is paused and if it's supposed to be kept that way.

There should be a optional field for adding a justification when pausing a DAG. If present this field could also be used for showing more info on the DAG list when a DAG is paused.

Are you willing to submit a PR?

Yes, but would probably need some help.

Related Issues

N/A
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

ansible-vault

ANSIBLE VERSION

ansible-vault 2.4.0.0
config file = /etc/ansible/ansible.cfg
configured module search path = ['<home_dir>/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /opt/envs/ansible/lib/python3.6/site-packages/ansible
executable location = /opt/envs/ansible/bin/ansible-vault
python version = 3.6.1 (default, Apr 22 2017, 00:00:00) [GCC 4.8.4]

CONFIGURATION

No changes to config

OS / ENVIRONMENT

Ubuntu 14.04

SUMMARY

ansible-vault decrypt does not print to stdout

STEPS TO REPRODUCE

> echo "hello" > /tmp/foo
> ansible-vault encrypt /tmp/foo
Encryption successful
> ansible-vault decrypt /tmp/foo --output -
Decryption successful

EXPECTED RESULTS

hello
Decryption successful

ACTUAL RESULTS

Decryption successful

ansible-vault==2.3.1.0 yields the expected output.

Additional question: Is it possible to suppress "Decryption successful" as I would like to use the output in a script.

Issue 2:
ANSIBLE VERSION

ansible 2.4.0.0

In ansible 2.3.x, it was possible to do ansible-vault decrypt example.txt --output - to get the decrypted output into stdout. In fact, that is advertised in ansible-vault decrypt --help:

--output=OUTPUT_FILE output file name for encrypt or decrypt; use - for stdout

In Ansible 2.4, this is bugged and results in a file named -.
Issue 1:
VSCode Version: 1.1.1

OS Version: Windows 10

I figured out that the built-in formatter does nothing when applied to an HTML template element. As far as I see it is really the template tag and all it's content that is completely ignored by the formatter.

Other HTML files are formatted properly. When using modern component-based frameworks like Aurelia, you're writing nothing else than templates and for me auto-formatting is indispensable.

Steps to reproduce:

create a .html file

paste in an example template with messed up indentation like:

<template>
<require from="components/nav-bar.html"></require>
<require from="bootstrap/css/bootstrap.css"></require>
<nav-bar router.bind="router"></nav-bar>
<div class="page-host">
<router-view></router-view>
</div>
</template>

Press Alt+Shift+F to format the file

Issue 2:
VSCode Version: 1.0.0

OS Version: OSX 10.11.4

Steps to Reproduce:

Try to auto format the following HTML

<template><div>Hello</div><div>World</div></template>

I expect to get something like this

<template>

____<div>Hello</div>

____<div>World</div>

</template>

But it does not work. If I replace the <template> tag with <div> then the auto format works correctly. This issue was not present in the previous version.

Thanks,
Issue 1:
function returnX(x, f = function () { return x }) {
var x;
return x;
}
returnX(42);

In Firefox, this produces 42. In babel, this produces undefined.

In the ECMAScript spec for FunctionDeclarationInstantiation, item 28 > f > i > 4/5, if a var name is also a parameter name, then it should get the parameter's value, even when the parameters have expressions (that is, default values).

Issue 2:
The following snippet:

(function(x, f = () => x) {
var x;
var y = x;
x = 2;
return [x, y, f()];
})(1)

gives [2, null, 1] in Babel. Aside from x shadowing behavior (and what f should resolve to — 1 or 2 (which Babel and FF disagree on)), y definitely shouldn't be null here (as far as I can tell), so this looks like a bug?
Issue 1:
I used Neo4j 2.1.2 to dump my whole DB:

bin/neo4j-shell -host localhost -readonly -config conf/neo4j.properties -c "dump" > ./backup/$(date +"%y%m%d_%H%M%S").cypher

And I got this:

begin
create index on :`Line`(`guid`)
create (_0:`Line` {`direction`:"钟南街首末站西=>车坊首末站", `guid`:"9f1f41ea-8939-492b-a969-028ef588857b", `name`:"128"})
create (_1:`Line` {`direction`:"车坊首末站=>钟南街首末站", `guid`:"7e5f894b-db9a-43da-b5eb-8c6a170db5b8", `name`:"128"})
create _0-[:`SIBLING_LINE`]->_1
create _1-[:`SIBLING_LINE`]->_0
;
commit

But when I tried to import this from a new DB:

bin/neo4j-shell -host localhost -port 1337 -config conf/neo4j.properties -file backup/140726_234717.cypher
bin/neo4j-shell -path /Users/Vej/Documents/Neo4j/neo4j-enterprise-2.1.2/data/graph.db/ -file backup/140726_225731.cypher

I always got this error:

ERROR (-v for expanded information):
SyntaxException: Invalid input 'c': expected whitespace, comment, ';' or end of input (line 2, column 1)
"create (_12868:`Line` {`direction`:"钟南街首末站西=>车坊首末站", `guid`:"9f1f41ea-8939-492b-a969-028ef588857b", `name`:"128"})"
^

If I only keep this first create and remove other creates, it succeeds. It looks like a bug in your dump or import?

Issue 2:
This issue ties together all bugs related to the shell's dump command.

Schema support

Constraints using indexes during import: there needs a way to wait for indexes to become available after creating them, otherwise the import takes forever.

The shell could be extended with a command to achieve the above, but this functionality might be better introduced in Cypher, some discussion occurred here: #2491 (comment). Edit: there actually already is the schema await command which can be used for that purpose.

Currently indexes and schema creation statements aren't properly generated, they need to be separate statements. Issue: #2491

@nawroth raised the question whether this change will break the integrated live console in the manual here: #2576 (comment) So this needs to be tested.

Robustness

Newline characters need to be properly escaped (also: tab, ...). Issue: #2577

Strings containing && confuse the shell. There might be more problems if the shell attempts to parse something inside a string. Issue: #2579

Byte arrays are exported as int arrays. Does Cypher support byte arrays? Should it? Issue: #2491

Maybe (no personal experience with large data sets): scaling to allow inserting more data than fitting a single transaction. This depends on what the goal of the dump command is, whether it shall be usable the same way SQL people dump DBs to SQL scripts to load them into another DB or whether dump is designed for smaller data sets (this should also be documented, so people will know what to expect from the command).

Cosmetics: there shouldn't be a BEGIN/COMMIT pair for schema creation if no schema is created

Order of dumped statements (esp. index/constrains), discussion: #4437
Issue 1:
The following code builds and runs fine:

struct S(i32);

static S0: S = S(0);

fn main() {
let d = S0;

println!("{}",
match d {
S(0) => true,
_ => false,
});
}

However attempting to match 'd' against 'S0' produces an error at the declaration of S0:

struct S(i32);

static S0: S = S(0);

fn main() {
let d = S0;

println!("{}",
match d {
S0 => true,
_ => false,
});
}

test.rs:3:16: 3:20 error: unsupported constant expr
test.rs:3 static S0: S = S(0);
^~~~

Issue 2:
edited because it no longer ICEs.

pub mod glfw {
pub struct InputState(uint);

pub static RELEASE : InputState = InputState(0);
pub static PRESS : InputState = InputState(1);
pub static REPEAT : InputState = InputState(2);
}

fn action_to_str(state: glfw::InputState) -> ~str {
use glfw::{RELEASE, PRESS, REPEAT};
match state {
RELEASE => { ~"Released" }
PRESS => { ~"Pressed" }
REPEAT => { ~"Repeated" }
_ => { ~"Unknown" }
}
}

fn main() {}

Error:

ice.rs:4:40: 4:53 error: unsupported constant expr
ice.rs:4 pub static RELEASE : InputState = InputState(0);
^~~~~~~~~~~~~
Issue 1:
can we have title parameter in MarkerOption (something like this screenshot)

and infoWidowText has to parameter

1st is title and 2nd is snippet, so can we have any clickable button in infoWindow or else can we use custom infoWindow in googlemap

controller.addMarker(new MarkerOptions(
`title: placename` //feature request
customInfoWindow: new widget() // feature request
infoWindowText: InfoWindowText(mCrag[j].title, mCrag[j].overview, **new Widget()**),
icon: BitmapDescriptor.fromAsset('assets/images/down-arrow.png'),
position: LatLng(mCrag[j].lat, mCrag[j].lon),
));

Issue 2:
It would be very handy to allow markers on the google maps to be flutter widgets. I know that currently there is already a method to load an image from assets but this is a static marker.

Overlaying a widget as a marker allows for dynamic generation of markers (example: rating of location on the map)
Issue 1:
When looking at the API of GestureDetector you find that

this.onTapDown,
this.onTapUp,
this.onTap,
this.onTapCancel,
this.onDoubleTap,
this.onLongPress,

Don't pass any tap details to there handlers making it hard to get the position of the tap. All other handler get some xxDetail as parameter.

The above handlers should get such details too.

Issue 2:
We've seen this feedback in a few places, including this article:

https://proandroiddev.com/what-the-f-tter-understanding-flutter-as-an-android-java-developer-2158086a2bd9

Note : You don’t actually need libimobiledevice , ideviceinstaller, ios-deploy and CocoaPods unless you want to build an iOS app, so ignore flutter doctor’s advice on installing them and you’ll save a hell lot of a time."

I thought there was a bug about adding a --android-only flag or similar to flutter doctor, but I didn't find it.

FYI @the-dagger (who wrote that article)
Issue 1:
404 error flashes when rendering custom routes on clientside

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

Related issues:

#2208

#2833

Expected Behavior

Routes to render correctly on both client and server.

Be able to define a link using next/link with only one prop, href, which contains the actual url.

Define routes in one place.

Example route: /posts/:id.

Current Behavior

The next/link component requires manually passing url parameters. This can be a bit inconvenient when attempting to navigate to a url string from a json response.

For example, if you have a simple blog backend that outputs a json response:

{ "posts": [{... "link": "/posts/my-first-post"}] }

Doing something like this does not work:

posts.map(post => <Link href={post.link} />)

The link will go to a 404 page and then it seems like the browser does a full reload and it gets rendered properly by the server.

Ideas

Allow custom routes to be defined in next.config.js and have the framework configure them

next.config.js

{
routes: [ ... { route: '/posts/:slug', component: '/posts/single' } ]
}

Somewhere in const { prepare } = require('next')

config.routes.forEach(({route, component}) => {
server.get(route), (req, res) => {
app.render(req, res, component, req.params);
});
})

Issue 2:
As described here: #159 (comment) and as far as I understand, if some React component has a getInitialProps, then all of its parents are condemned to need it too, and each parent in turn needs to call getInitialProps on their children, in the right order, making sure not to duplicate the work between the different levels of ancestry (the linked issue shows the case of a higher-component style, but the same applies when passing components as React children the normal way).

Forgetting one of these calls can lead to silent bugs such as not having server-side rendering, and this code repetition can hinder proper componentization (one of React's key patterns).

From an end-user perspective, just like with React component lifecycle methods such as componentWillMount etc, IMHO the developer should trust that getInitialProps will be called no matter what, as long as it's spelled properly.

Could Next.js handle getInitialProps as part of the React component lifecycle or implement the same kind of magic to make sure it gets called whenever defined in a component?

I'm new to SSR and Next.js, so apologies if this makes no sense 😄