WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
After upgrading to next 6.0.0, when running Next in dev mode, page transitions sometimes get stuck rendering the current page rather than rendering the next page.

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

Expected Behavior

When clicking a <Link /> in dev mode, after the page bundle builds, the client should navigate to the linked page.

The behavior is inconsistent and I have not been able to reproduce this issue when the page is already built.

Current Behavior

After the next page bundle builds, the client re-renders the current page.

Steps to Reproduce (for bugs)

Run next in dev mode (I am using a custom Express server, so the dev command is node server.js

Go to a page in the browser

Click a <Link /> to second page

Wait a bit for the second page to build

The browser location changes to the second page's url, but you're still on the first page

Refreshing the page renders the second page correctly.

Context

This is preventing us from upgrading to Next 6.0.0

Your Environment

Tech
Version

next
6.0.0

node
8.10.0

OS
Mac OSX

browser
Chrome 65.0.3325.181

Issue 2:
I am trying add http://ogp.me/#array of article:tag property:

import NextHead from 'next/head'
<NextHead>
<meta property="article:tag" content="tag1" key="tag1key" />
<meta property="article:tag" content="tag2" key="tag2key" />
</NextHead>

Expected Behavior

I have set key for each line, so I expect that next.js understand that it is not duplicates:

<head>
<meta property="article:tag" content="tag1" />
<meta property="article:tag" content="tag2" />
</head>

Current Behavior

But next.js think tah it is a duplicates and remove tags except last tag:

<head>
<meta property="article:tag" content="tag2" />
</head>

Your Environment

Tech
Version

next
5.1.0

node
9.2.0

OS
OSX
Issue 1:
I mistakenly exported ServiceConfig twice, the second call produces the following exception which makes no sense:

java.lang.reflect.InvocationTargetException: null
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_91]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_91]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_91]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_91]
at org.apache.dubbo.config.AbstractConfig.refresh(AbstractConfig.java:568) [dubbo-2.7.0.jar:2.7.0]
at org.apache.dubbo.config.ServiceConfig.checkAndUpdateSubConfigs(ServiceConfig.java:272) [dubbo-2.7.0.jar:2.7.0]
at org.apache.dubbo.config.ServiceConfig.export(ServiceConfig.java:328) [dubbo-2.7.0.jar:2.7.0]
at xx.xx.xx.xx.rpc.NodeRpcServerV3.start(NodeRpcServerV3.java:298) [classes/:?]
at xx.xx.xx.xx.rpc.NodeRpcV3Test.init(NodeRpcV3Test.java:21) [test-classes/:?]
....
Caused by: java.lang.IllegalArgumentException: Unsupported generic type false
at org.apache.dubbo.config.ServiceConfig.setGeneric(ServiceConfig.java:959) ~[dubbo-2.7.0.jar:2.7.0]
... 67 more

It took me at least one hour to locate the root cause.

Dubbo version: 2.7.0

I've crafted a demo for this issue at this repo.

Issue 2:
I wonder why consumer url not register and unregister to consul:

dubbo/dubbo-registry/dubbo-registry-consul/src/main/java/org/apache/dubbo/registry/consul/ConsulRegistry.java

Lines 102 to 104
in
afbf7d5

if (isConsumerSide(url)) {

return;

}

dubbo/dubbo-registry/dubbo-registry-consul/src/main/java/org/apache/dubbo/registry/consul/ConsulRegistry.java

Lines 120 to 122
in
afbf7d5

if (isConsumerSide(url)) {

return;

}

And this issue is duplicated to #6147.
Issue 1:
[Power Toy Settings>General>left pane]

User Impact:

This will impact the screen reader users if the irrelevant information is announced by the screen reader on menu items.

Test Environment:

OS Version: 20221.1000

App Name: Power Toy Preview

App Version: v0.23.0

Reproe-Steps:

Open Power Toys Settings App. Turn on narrator.

Navigate to 'Open Navigation' button present in left pane and activate it.

Navigate to General menu item and verify the issue.

Actual Result:

Screen reader is announcing irrelevant information as 'level 1' on menu items of left pane.

Note:

Same issue is repro with NVDA(2020.2)

Expected Result:

There is no as such level present on the window so screen reader should not convey the 'level 1' information.

MAS Reference:

https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc=%7ba12f3779-bdf1-40c2-bbcc-0e314ea94858%7d&cid=127cc21c-7a42-48a4-9e3b-07f090c6bd8a

51_General_MAS4.2.1_Irrelevant information as level 1 is announce by the narrator.zip

51_General_irrelevant information as level 1_NVDA.zip

Issue 2:
Summary of the new feature/enhancement

I'd love, if FancyZones save original size of windows, like it happens if I stick window left, right or top (fullscreen). If I drag window from these modes, It returns to it's original size.

For now, it seems that FancyZones changes original size of window.
Issue 1:
Setting both options "index.auto_expand_replicas":"0-all" and "cluster.routing.allocation.same_shard.host": true causes unallocated shards in a cluster.

E.g. in a cluster with 5 physical hosts and 10 Elasticsearch instances (2 instances/host) the settings cause 5 unallocated shards per an index.

Is this the correct behavior?

Thanks!

P.S. Tested on Elasticsearch-1.4.4

Issue 2:
We already use fielddata on the _uid field today in order to implement random sorting. However, given that doc values are disabled on _uid, this will use an insane amount of memory in order to load information in memory given that this field only has unique values.

Having better fielddata for _uid would also be useful in order to have more consistent sort order when paginating or hitting different replicas: we could always add a tie-break on the value of the _uid field.

I think we have several options:

Option 1: Add SORTED doc values to _uid

Option 2: Add BINARY doc values to _uid

Option 3: Add SORTED doc values to _type and _id

Option 4: Add SORTED doc values to _type and BINARY to _id

Option 2 would probably be wasteful in terms of disk space given that we don't have good compression available for binary doc values (and it's hard to implement given that the values can store pretty much anything).

Options 3 and 4 have the benefit of not having to duplicate information if we also want to have doc values on _type and _id: we could even build a BINARY fielddata view for _uid.

Then the other question is whether we should rather use sorted or binary doc values, the former being better for sorting (useful for the consistent sorting use-case) and the latter being better for value lookups (useful for random sorting).
Issue 1:
I have been trying to use a full ES6 webpack configuration file using Babel 6 but it seems that export default if in fact not exporting anything.

I named my config file webpack.config.babel.js and this is the code:

import path from 'path';
import HtmlwebpackPlugin from 'html-webpack-plugin';

const ROOT_PATH = path.resolve(__dirname);
const APP_PATH = path.resolve(ROOT_PATH, 'app');
const BUILD_PATH = path.resolve(ROOT_PATH, 'build');

export default {
entry: APP_PATH,

output: {
path: BUILD_PATH,
filename: 'bundle.js'
},

plugins: [
new HtmlwebpackPlugin({
title: 'React Kanban App'
})
]
};

Every time I run webpack I just get the webpack options list and a message saying Output filename not configured., but If I change the expression to module.exports = { ... } everything works fine.

My .babelrc file is like this:

{
"presets": [
"es2015",
"react"
]
}

And my dependencies are:

"devDependencies": {
"babel-core": "^6.1.21",
"babel-preset-es2015": "^6.1.18",
"babel-preset-react": "^6.1.18",
"webpack": "^1.12.6"
}

I can't figure out what is going on here, is this a bug?

Issue 2:
I try to use es2015+ code in my webpack.config.babel.js file. After the recent upgrade this convention no longer works.

export default {
entry: './app.js',
output: {
path: __dirname,
filename: 'bundle.js'
},
module: {
loaders: [
{
test: /\.js$/,
loader: 'babel',
exclude: /node_modules/,
query: {
cacheDirectory: true,
presets: ['es2015']
}
}
]
}
}

I will get the error: SyntaxError: Unexpected token export

For reference, here is the package.json file:

{
"devDependencies": {
"babel-core": "^6.0.17",
"babel-loader": "^6.0.1",
"babel-preset-es2015": "^6.0.15",
"webpack": "^1.12.2"
}
}
Issue 1:
Hi,

i think there is an error on TypeScript documentation > Developer Guides > 6. Dependency Injection.

import {Injectable} from 'angular2/angular2'; should be import {Injectable} from 'angular2/core';

Thanks for your work!

Issue 2:
I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request

This would appear to be an issue with Jasmine during the pretty printing stage, but I am also logging it here in case there is something about Angular's testing that is causing this issue and should be changed.

Related Issue: jasmine/jasmine#1263

Current behavior

Attempting to test the existence of a DebugElement in a unit test results in the test hanging.

Expected behavior

It should not hang. The test should immediately fail.

Minimal reproduction of the problem with instructions

Set up a typical testing harness for an Angular component and create the following test:

var result = fixture.debugElement.query(By.css("#something"));
// The following line hangs when result is a DebugElement
// Also occurs with .toBeNull() and some others
expect(result).toBeFalsy();

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

N/A

Please tell us about your environment:

Windows 10, Visual Studio Code, Karma

Angular version: 2.4.10

Language: TypeScript 2.2.1
Issue 1:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
no

Symfony version
2., 3.

Description: There is constraint "All" that allows us to provide several fundamental constraints that all has to be valid for validation to pass. There is no constraint "Any" for which we can provide several fundamental constraints expecting at least one of those to be valid.

Example: We can, per example, have several classes, Invoice, ProInvoice, DebitNote, CreditNote (accounting). For some property path, we can expect for, per example, Invoice or ProInvoice to be provided, example:

@Assert\Any([ @Assert\Type(type="Model\Invoice"), @Assert\Type(type="Model\ProInvoice") ])

This can be done differently, via Callback validator, or Expression validator, or whatever...

However, "Any" seams a "syntactic sugar", if there is no reason for "No" I would like to submit a PR.

Issue 2:
Symfony version(s) affected: 4.0.11 (might as well be earlier versions)

Description

In Finder 4.0.8 the commit symfony/finder@45429ad was released which should remove duplicate slashes from path names.

However, this results in an error when used to find files in an FTP root dir.

The documentation (https://symfony.com/doc/current/components/finder.html:) by the way explicitly states that the slash is required in this case:

// always add a trailing slash when looking for in the FTP root dir
$finder->in('ftp://example.com/');

How to reproduce

$finder = new Finder();
$files = $finder->files()->in('ftp://speedtest.tele2.net/');
foreach ($files as $file) {
var_dump($file);
}

Possible Solution

One might parse the given $dirstring and trwat it differently if ti starts with "ftp://"
Issue 1:
When tooltip is active/focused and destroy event is called the tooltip gets opacity 0, but still clickable and its element still in the DOM.

It's reproduced in this example: http://jsfiddle.net/jeRub/

When test button is clicked the tooltip gets "destroyed", but it still in the DOM and blocks click events on the text input.

Issue 2:
i searched for an already opened issue but did not found any that was reporting this exact problem.

I'm trying to use the destroy method on tooltip (bootstrap v3) but it does not remove the element from the DOM.

Any idea ?

Fiddle : http://jsfiddle.net/52VtD/59/

click on the button to trigger the tooltip destroy method
Issue 1:
Here is the plunk showing the problem

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

basically when using something like

<div class="form-group">
<label for="{{forLabel}}">{{label}}</label>
<input type="text" class="form-control">
</div>

you get

Can't bind to 'for' since it isn't a known native property ("
</nav>
<div class="form-group">
<label [ERROR ->]for="{{forLabel}}">{{label}}</label>
<input type="text" class="form-control">
</div>
"): RoutedComponent@28:12

Issue 2:
[X] bug report

[X] feature request

Do you want to request a feature or report a bug?

Bug in existing behavior, feature for proposed solution

I am creating an Angular2 component, in the template, I am wanting to create an <input>, with a calculated [id] property, which works.

I am also wanting to create a <label> with a matching [for] property, so that the label is appropriately bound to the input (clicking will focus said input).

What is the current behavior?

EXCEPTION: Template parse errors:
Can't bind to 'for' since it isn't a known native property

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal

<label [for]="getInputId()">Label</label>
<input [id]="getInputId()" />

What is the expected behavior?

The property should be calculated, and the result outputted into the <label> like the [id] property works for <input>;

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

The current behavior doesn't support a necessary feature for HTML output in dealing with label association to form controls.

Please tell us about your environment:

Angular version: 2.0.0-beta.7

Browser: all

Language: ES2016+ (Babel)

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

It would be nice if "unknown" native properties simply run and output the result,as [id] works on the <input> element.
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18363.900]

PowerToys version: 0.18.2

PowerToy module for which you are reporting the bug (if applicable): PowerToys Run

Description

PowerToys run does not search for files/folders in drives other than C:. It does it even when I tell it specifically to search, for example, in drive S: as seen in the picture below. Only way to get to the file/folder is to specify the entire path to it.

Steps to reproduce

open PowerToys run

search for a file or folder that is in a drive other than C: either by searching directly for its name, or by using the syntax "drive letter":\ >"name of the file/folder"

Expected behavior

PowerToys run finds the file/folder and displays it in the result list.

Actual behavior

PowerToys run only finds some unrelated results in drive C: and says that "Access to the path '"drive letter":\System Volume Information' is denied" if you specify the drive in which to search for the result.

Screenshots

ps : I've seen people using this kind of template for issue reporting... Is there a specific place from where I can get this template or is it user generated ?

Issue 2:
Comment by @EdgarVaguencia from #3223

Doesn't find Code

Wox result:

the G drive is a partition, the different thing is that i don't create shortcut on start menu, but i add the path in environment variables
Issue 1:
Hi !

Could it be possible to add a transformer for JSX that outputs a Javascript "normal" string ?

For example, this:

let foo = "Hello world !";
let bar = (
<div>
{foo}
</div>
);

would be transformed to:

let foo = "Hello world";
let test = "<div>" + foo + "</div>";

I'm not sure if it goes into the scope of the project, since one could use the preserve option and use an additional transpiler, but I think it could help users write components & templates for any library (Vuejs, Ractive, ...), instead of just React.

Issue 2:
interface A
{
func(arg: string): boolean;
func(arg: number): string;
} // OK!

interface B
{
func: (arg: string) => boolean;
func: (arg: number) => string;
} // Error! Duplicate identifier 'func'.

?
Issue 1:
Ref. #19364 (comment)

The idea would be that given a file bar.jl with contents y=5, one could do

function foo()
local y
@include "bar.jl"
return y
end

and foo() would return 5, but not define a global variable y in the containing module. (Using the existing include function, foo() would define y globally and then fail because y is undefined in local scope.)

Issue 2:
("before_first_compact", ir) = ("before_first_compact", 1 ── nothing
809 │ nothing
│ nothing
│ %4 = Base.Broadcast.axes(%%2)::Tuple{Base.OneTo{Int64}}
│ %5 = Base.Broadcast.axes(%%3)::Tuple{Base.OneTo{Int64}}
│ %6 = Base.Broadcast.:==(%4, %5)::Bool
└─── goto 14 if not %6
2 ── nothing
811 3 ── %9 = Base.getproperty(%%3, :f)::NotInferenceDontLookHere.Const(-, false)
│ %10 = Base.Broadcast.:===(%9, Base.Broadcast.identity)::NotInferenceDontLookHere.Const(false, false)
└─── goto 4 if not %10
4 ┄─ %12 = false::NotInferenceDontLookHere.Const(false, false)
4 ┄─ %62 = π (%12, NotInferenceDontLookHere.Const(false, false))
└─── goto 5 if not %62

Note the duplicate showing of BB4. Also pending nodes should be in yellow, which they don't appear to be anymore.
Issue 1:
Make sure these boxes are checked before submitting your issue - thank you!

I have checked the superset logs for python stacktraces and included it here as text if any

I have reproduced the issue with at least the latest released version of superset

I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

Master

Expected results

One <script> tag for each chunk.

Actual results

There are duplicate <script> tags for the shared chunks. If you view page source, there will be multiple vendors-addSlice-common-dashboard-explore-profile-sqllab-theme-welcome.0fe210d7.chunk.js

For example on the top of the page.

<script src="/static/assets/dist/vendors-addSlice-common-dashboard-explore-profile-sqllab-theme-welcome.0fe210d7.chunk.js"></script>
<script src="/static/assets/dist/vendors-dashboard-explore-profile-sqllab-theme-welcome.0fe210d7.chunk.js"></script>
<script src="/static/assets/dist/theme.0fe210d7.entry.js"></script>

<script src="/static/assets/dist/vendors-addSlice-common-dashboard-explore-profile-sqllab-theme-welcome.0fe210d7.chunk.js"></script>
<script src="/static/assets/dist/vendors-addSlice-common-dashboard-explore-profile-sqllab-welcome.0fe210d7.chunk.js"></script>
<script src="/static/assets/dist/addSlice-common-dashboard-explore-profile-sqllab-welcome.0fe210d7.chunk.js"></script>
<script src="/static/assets/dist/common.0fe210d7.entry.js"></script>

Because each entry in the js manifest lists an array of chunks each entry point needs, independent of other entry points. When we render this directly to FAB template, it does not de-dup.

XHR Performance-wise not too bad as browser only fetches and parses once, but for correctness, if the chunk executes something, it executes multiple times.

Steps to reproduce

Open Superset, view source.

Issue 2:
Hello,

I'm very new to Superset, so please forgive me if it's a newbie question or has been asked a lot.

I'm testing Superset with a couple of databases that all have the same type of application writing data to them. So all the databases obviously have the same tables in them.

Now after I added two databases and tables as datasets, I get Datasets with identical names, and I can't see a way to differentiate between them. When I want to create a new chart and want to choose a dataset, they're indistinguishable:

Is there any way to give the Datasets a specific name or similar, to differentiate them?

Thank you for your insights!
Issue 1:
Issue Type:

Bug Report

Ansible Version:

1.5.5

Environment:

CentOS 5.9

Summary:

We are using Ansible to run puppet agent, which by default (and very helpfully) uses colors to indicate severity of logs. When puppet is run with default (color=on) settings, there is no output from Ansible; when it is run with ("--color=false") then ansible displays the output. We would like to have puppet colors preserved since they are of value to spotting issues.

Steps To Reproduce:

Run the "puppet agent -t" (or other puppet apply command) on a system using Ansible.

[root@localhost ~]# ansible server.example.com -m shell -a 'puppet agent -t --noop' -v

Expected Results:

Expected to see something like below (but with ANSI colors):

[root@localhost ~]# ansible server.example.com -m shell -a 'puppet agent -t --noop' -v
server.example.com | success | rc=0 >>
info: Retrieving plugin
info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
info: Caching catalog for server.example.com
info: Applying configuration version '1400866037'
notice: Finished catalog run in 8.13 seconds

[root@localhost ~]#

Actual Results:

E.g.

[root@localhost ~]# ansible server.example.com -m shell -a 'puppet agent -t --noop' -v
server.example.com | success | rc=0 >>

[root@localhost ~]#

Issue 2:
错误信息：fatal: [globalmonitor1]: FAILED! => {"failed": true, "msg": "Timeout (12s) waiting for privilege escalation prompt: "}

ansible 2.1.0.0

Red Hat Enterprise Linux Server release 7.2 (Maipo)
Issue 1:
While creating or changing a zone, it would be nice if the size in pixels x*y will be visible

When creating a zone i would like to see how many pixels in x and y i have. On a big monitor with 38402160 i want to create some zone with 19201080 pixels.

Issue 2:
Would it be possible to display the sizes in each windows when creating/modifying the custom layouts in FancyZones? This will help, for example, when you want a window that is exactly half/third/quarter etc of the screen size of another window.

Thanks for a great tool.