WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
In order to have nice looking paths without hash or bang, I am using history mode:

var router = new VueRouter({

routes: routes,

mode: 'history'

})

However, when I refresh a page, I get a 404 error. If I remove mode: 'history', I can go directly to urls at a path and refresh pages in my browser.

Can I remove hash and bang (#!) from my urls and be able to refresh pages and use direct urls to a path?

Issue 2:
Vue.js version

2.0.2

Reproduction Link

When I deployment my vue app to IIS, refresh page in SPA component, I go 404 error
Issue 1:
Issue originally made by @dfilatov

Bug information

Babel version: 6.3.13

Node version: 4.2.1

npm version: 2.14.7

Options

--presets es2015

Input code

export * from './client/mounter';

Description

Given input code will be transformed to:

var _mounter = require('./client/mounter');

for (var _key in _mounter) {
if (_key === "default") continue;
Object.defineProperty(exports, _key, {
enumerable: true,
get: function get() {
return _mounter[_key];
}
});
}

In result all reexported stuff will reference to the same _mounter[_key], where _key is a last key from _mounter.

Issue 2:
flow v0.32.0:

New syntax for exact object types: use {| and |} instead of { and }. Where {x: string} contains at least the property x, {| x: string |} contains ONLY the property x.
Issue 1:
I have a form some fields are not validated based on the validation groups. The validation works as expected but the error message is always added to the wrong field. It seems to just use which ever property is last in the validation.yml file.

I believe my use case is valid. It worked fine in 2.4 but when testing 2.5 BETA2 there were test failures. Also seems to be an issue with the master branch.

I found it easiest to reproduce the issue using a system test. This can be found in the following repository: https://github.com/tompedals/symfony-form-test

Model: https://github.com/tompedals/symfony-form-test/blob/master/src/Test/FormTestBundle/Model/Attachment.php

Form: https://github.com/tompedals/symfony-form-test/blob/master/src/Test/FormTestBundle/Form/AttachmentType.php

Validation mapping: https://github.com/tompedals/symfony-form-test/blob/master/src/Test/FormTestBundle/Resources/config/validation.yml

Test: https://github.com/tompedals/symfony-form-test/blob/master/src/Test/FormTestBundle/Tests/Form/AttachmentTypeTest.php

Use phpunit -c app to run the tests.

Issue 2:
Hello,

When using Validator 2.5 to validate an array of scalars, the propertyPath of the returned violations has really strange values.

Consider the following script:

<?php

require 'vendor/autoload.php';

use Symfony\Component\Validator\Constraints;
use Symfony\Component\Validator\Validation;

$constraints = array(
'foo' => array(
new Constraints\NotBlank(),
new Constraints\Date()
),
'bar' => new Constraints\NotBlank()
);

$collectionConstraint = new Constraints\Collection(array('fields' => $constraints));

$validator = Validation::createValidatorBuilder()
->setApiVersion(Validation::API_VERSION_2_5)
->getValidator();

$value = array(
'foo' => 'bar'
);

$violations = $validator->validate($value, $collectionConstraint);

foreach ($violations as $violation) {
var_dump($violation->getPropertyPath());
}

Output:

string(11) "[foo].[foo]"
string(17) "[foo].[foo].[bar]"

If I set Validation::API_VERSION_2_4 and call the old validateValue method, it outputs:

string(5) "[foo]"
string(5) "[bar]"

Is this something expected ?
Issue 1:
Christian Nelson opened SPR-6118 and commented

Spring JDBC 3.0.0.M4 maven pom includes derby and derby.client - these should be optional dependencies.

Here is the relevant output from mvn dependency:tree...

[INFO] +- org.springframework:spring-orm:jar:3.0.0.M4:compile

[INFO] | +- org.slf4j:slf4j-jdk14:jar:1.5.2:compile

[INFO] | +- org.springframework:spring-beans:jar:3.0.0.M4:compile

[INFO] | +- org.springframework:spring-core:jar:3.0.0.M4:compile

[INFO] | | - org.springframework:spring-asm:jar:3.0.0.M4:compile

[INFO] | +- org.springframework:spring-jdbc:jar:3.0.0.M4:compile

[INFO] | | +- org.apache.derby:com.springsource.org.apache.derby:jar:10.5.1000001.764942:compile

[INFO] | | - org.apache.derby:com.springsource.org.apache.derby.client:jar:10.5.1000001.764942:compile

[INFO] | - org.springframework:spring-tx:jar:3.0.0.M4:compile

[INFO] | +- aopalliance:aopalliance:jar:1.0:compile

[INFO] | +- org.springframework:spring-aop:jar:3.0.0.M4:compile

[INFO] | - org.springframework:spring-context:jar:3.0.0.M4:compile

[INFO] | - org.springframework:spring-expression:jar:3.0.0.M4:compile

These dependencies should be configured as <optional>true</optional> since they're not required for regular usage of spring-jdbc.

Affects: 3.0 M4

Issue Links:

#10777 Spring JDBC POM should declare derby dependency is optional ("duplicates")

Issue 2:
Keith Garry Boyce opened SPR-1412 and commented

I have a situation when I need access to the portlet name in the controller to then in turn look up data related to that data in db. I don't want a separate controller config for each portlet s it would seem if framework detected that I implement and interface requiring that then it would do the right thing and give me access to read it. What do you think?

Affects: 2.0 M1
Issue 1:
In Polish language exists letter 'ś', written by pressing rightAlt+s. In atom this combination brings up the 'Spec suite' window.

Worth noticing is fact, that in settings shortcut responsible for this is ctrl-alt-s, yet rightAlt+s alone brings up the window too.

I tried adding

'body':
'ralt-s': ''
'ctrl-alt-s' : ''

to the keymap, but it didn't fix my problem.

Expected change:

chaning default shortcut to a non-colliding one

or

making only ctrl-alt-s as hotkey and not rightAlt-s,

Issue 2:
Original issue: atom/atom#1625

Use https://atom.io/packages/keyboard-localization until this issue gets fixed (should be in the Blink upstream).
Issue 1:

Issue 2:
I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

When using Angular 2.3.0 with Safari 9, the application does not start up at all. Instead the console shows the following error message:

Error: (SystemJS) Strict mode does not allow function declarations in a lexically nested statement.
eval@[native code]
invoke@http://localhost:8000/lib/zone.js:229:31
run@http://localhost:8000/lib/zone.js:113:49
http://localhost:8000/lib/zone.js:509:60
invokeTask@http://localhost:8000/lib/zone.js:262:40
runTask@http://localhost:8000/lib/zone.js:151:57
drainMicroTaskQueue@http://localhost:8000/lib/zone.js:405:42
run@http://localhost:8000/lib/shim.js:4005:30
http://localhost:8000/lib/shim.js:4018:32
flush@http://localhost:8000/lib/shim.js:4373:12
Evaluating http://localhost:8000/lib/@angular/compiler/bundles/compiler.umd.js
Error loading http://localhost:8000/lib/@angular/compiler/bundles/compiler.umd.js as "@angular/compiler" from http://localhost:8000/lib/@angular/platform-browser-dynamic/bundles/platform-browser-dynamic.umd.js — zone.js:672

Expected behavior

Expected it, that the application works and starts up according to the supported browser matrix.

The same plunkr - as shown below - works as expected in Safari 10.

Minimal reproduction of the problem with instructions

To reproduce you can use the template offered when creating a new issue: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5

Fire it up in Safari 9 and take a look into the console.

Please tell us about your environment:

macOS El Capitan 10.11.6

Angular version: 2.3.0

Browser: Safari 9.1.2

Error may be related to #13301
Issue 1:
VSCode Version: 1.1.0

OS Version: OS X 10.11.4

Steps to Reproduce:

Create a new text file test.js

Set the content to the following:

let x = true ? '' : `${1}`
console.log('still part of the template!')

VS Code fails to parse the opening of the template string at the end of the ternary operator correctly. It therefore sees the final as an opening tick, and interprets the rest of the file as a template string:

As a workaround you can wrap the failure case in parenthesis:

let x = true ? '' : (`${1}`)
console.log('still part of the template!')

Issue 2:
From @garthk on April 8, 2016 4:30

VSCode Version: Version 0.10.10 (0.10.10) or Version 0.10.14-insider (0.10.14-insider) 17fa1cbb49e3c5edd5868f304a64115fcc7c9c2c

OS Version: OS X 10.11.4 (15E65)

javascript.validate.enable set either true or false

Steps to Reproduce:

Open a new Code – Insiders window

Paste in the following JavaScript

Observe

function test1(x) {
const defaultValue = `${x}`;
const value = x ? x : y;
console.log('so far, so good');
}

function test2(x) {
const value = !x ? `${x}` : x;
console.log('so far, so good');
}

function test3(x) {
const value = x ? x : `${x}`; // this comment is coloured as if it's part of the template literal
console.log('this entire line, too');
} // and this one

If I'm getting this right:

test1 shows code knows when a template literal ends, usually

test2 shows code still knows when a template literal ends if it's the first AssignmentExpression in a ternary

test3 shows code somehow misses the end of a template literal as the second AssignmentExpression in a ternary, highlighting from then on as a string

Copied from original issue: microsoft/vscode#5090
Issue 1:
ECMAScript 2018 was finalized, what do we need to enable these features by default for preset-env?

SyntaxError: /path/to/file.js:
Support for the experimental syntax 'objectRestSpread' isn't currently enabled (11:9):

10 | {
> 11 | ...example,
| ^
12 | key: 'value',
13 | },

The proposal keyword was removed from @babel/plugin-syntax-object-rest-spread package name but babel-preset-env/data/plugins.json still have:

babel/packages/babel-preset-env/data/plugins.json

Line 232
in
6f3be3a

"proposal-object-rest-spread": {

Issue 2:
Hi there,

a simple module just reexport a module fails.

export * from './some-module';

My .babelrc looks like this:

{
"presets": ["es2015", "stage-1"],
"plugins": ["transform-async-to-generator"]
}

This should contain the required export-extensions transform.

The error message looks like this:

$ ./node_modules/.bin/babel test.js
Error: test.js: Invariant Violation: To get a node path the parent needs to exist
at Object.invariant [as default] (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/node_modules/invariant/invariant.js:44:15)
at Function.get (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/path/index.js:82:27)
at TraversalContext.create (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/context.js:73:30)
at NodePath._containerInsert (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/path/modification.js:80:32)
at NodePath._containerInsertBefore (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/path/modification.js:138:15)
at NodePath.insertBefore (/home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/path/modification.js:57:19)
at BlockScoping.wrapClosure (/home/markusw/source/ankara/node_modules/babel-preset-es2015/node_modules/babel-plugin-transform-es2015-block-scoping/lib/index.js:485:21)
at BlockScoping.run (/home/markusw/source/ankara/node_modules/babel-preset-es2015/node_modules/babel-plugin-transform-es2015-block-scoping/lib/index.js:385:12)
at PluginPass.Loop (/home/markusw/source/ankara/node_modules/babel-preset-es2015/node_modules/babel-plugin-transform-es2015-block-scoping/lib/index.js:89:36)
at /home/markusw/source/ankara/node_modules/babel-cli/node_modules/babel-core/node_modules/babel-traverse/lib/visitors.js:271:19

Any hint on this?
Issue 1:
# coding: utf-8
import pandas as pd
import numpy as np

frame = pd.read_csv("table.csv", engine="python", parse_dates=['since'])
print frame
d = pd.pivot_table(frame, index=pd.TimeGrouper(key='since', freq='1d'), values=["value"], columns=['id'], aggfunc=np.sum, fill_value=0)
print d
print "^that is not what I expected"
frame = pd.read_csv("table2.csv", engine="python", parse_dates=['since']) # add some values to a day
print frame
d = pd.pivot_table(frame, index=pd.TimeGrouper(key='since', freq='1d'), values=["value"], columns=['id'], aggfunc=np.sum, fill_value=0)
print d

The following data is the contents of table.csv

"id","since","value"
"81","2015-01-31 07:00:00+00:00","2200.0000"
"81","2015-02-01 07:00:00+00:00","2200.0000"

This is table2.csv:

"id","since","value"
"81","2015-01-31 07:00:00+00:00","2200.0000"
"81","2015-01-31 08:00:00+00:00","2200.0000"
"81","2015-01-31 09:00:00+00:00","2200.0000"
"81","2015-02-01 07:00:00+00:00","2200.0000"

The output of print after pivoting table.csv

id value
<pandas.tseries.resample.TimeGrouper object at 0x7fc595f96c10> 81 2200
id 81 2200

I would expect something like this:

value
id 81
since
2015-01-31 2200
2015-02-01 2200

I can trace the problem to here:

https://github.com/pydata/pandas/blob/62529cca28e9c8652ddf7cca3aa6d41d4e30bc0e/pandas/tools/pivot.py#L114 the index created by groupby already has the object there.

I can't figure anything else. What is the problem, any fixes?

Thanks.

Issue 2:
The following code seems to raise an error, since the result object does not make sense (well, at least to me):

In [61]: import datetime

In [62]: import pandas as pd

In [63]: df = pd.DataFrame.from_records ( [[datetime.datetime(2014,9,10),1234,"start"],
[datetime.datetime(2013,10,10),1234,"start"]], columns = ["date", "change", "event"] )

In [64]: df
Out[64]:
date change event
0 2014-09-10 1234 start
1 2013-10-10 1234 start

In [65]: ts = df.set_index('date')

In [66]: ts
Out[66]:
change event
date
2014-09-10 1234 start
2013-10-10 1234 start

In [67]: byperiod = ts.groupby([pd.TimeGrouper(freq="M"), "event"], as_index=False)

In [68]: byperiod.groups
Out[68]:
{<pandas.tseries.resample.TimeGrouper at 0xab6bcaec>: [Timestamp('2014-09-10 00:00:00')],
'event': [Timestamp('2013-10-10 00:00:00')]}

I would expect, for Out[68], two groups, one for each (date, event) pair.

Am I wring, or this is a bug?
Issue 1:
Electron Version:

v5.0.0-beta.5

Operating System:

Windows 10 Pro.

Last Known Working Electron version::

4.x (latest)

Expected Behavior

When I perfrom a GET-request using http or https built-in library, I expect the app to keep running after the request completes.

Actual Behavior

When performing a GET request to an arbitrary host, the app crashes after a few seconds after completing the request. Usually ranges between 5 and 20 seconds.

To Reproduce

https://github.com/haroldiedema/electron-5x-http-crash

$ git clone https://github.com/haroldiedema/electron-5x-http-crash
$ npm install
$ node_modules/.bin/electron .

Sit back and wait for a few seconds for the app to crash with exit code 127. (or exit code 1 if started from npm or yarn).

Screenshots

N/A

Additional Information

I think this might have something to do with either:

A) Electron not handling the closing of sockets correctly anymore, or

B) The garbage collector kicking in and cleaning up the socket resource which makes electron crash.

Then again, that is purely speculation on my end.

Issue 2:
Electron Version:

5.0.0-beta (all)

Operating System:

Ubuntu 18.10, Linux 4.18, x64

Last known working Electron version (if applicable):

4.0.5

Expected Behavior

Google API should work as it they are meant to.

Actual behavior

Any Google API calls may crash renderer process (even if they are run on Worker thread).

The request may be done and the answer given, but immediately or after several seconds the renderer process may crash.

To Reproduce

$ git clone https://github.com/ruslang02/youtube-electron-crash-example
$ npm install electron@beta
$ npm start || electron .

Version 5 will randomly crash, version 4: doesn't

Additional Information

May be a Node.JS bug, but not sure
Issue 1:
Bruno Hansen opened SPR-9334 and commented

New support for Jackson 2.X because of changing of packages:

Jackson reference:

http://wiki.fasterxml.com/JacksonRelease20#Changing_Java_packages

Spring forum reference:

http://forum.springsource.org/showthread.php?125213-Support-for-Jackson-2-0&p=408474#post408474

Affects: 3.2 M1, 3.2 M2

Reference URL: http://forum.springsource.org/showthread.php?125213-Support-for-Jackson-2-0&p=408474#post408474

Issue Links:

#13940 Use Jackson 2.0 for Jackson based json processing such as MappingJacksonJsonView ("duplicates")

Issue 2:
Xun Wang opened SPR-9302 and commented

Due to recent release of Jackson 2.0, hope it is on the road map to give Spring user the option to use Jackson 2.0 for Jackson related json functions. Jackson 2.x has different package name for its classes to let code with 1.x be able to coexist. Maybe a new set of the Spring classes need to be created for the same reason for those who like to use the 2.x while others can remain on 1.x. For example MappingJacksonJsonView remains but with MappingJacksonJsonView2 for the 2.x Jackson. I believe someone has better idea how to get it done.

Affects: 3.0.5

Attachments:

MappingJacksonHttpMessageConverter.patch (1.65 kB)

Sub-tasks:

#14141 Backport "Use Jackson 2.0 for Jackson based json processing such as MappingJacksonJsonView"

Issue Links:

#13972 Support for Jackson 2.X ("is duplicated by")

#14589 Add support for jackson 2.0 message converters MappingJacksonHttpMessageConverter refers to the older ObjectMapper package and methods ("is duplicated by")

9 votes, 10 watchers
Issue 1:
Anytime I click inside the code editor, a "copy / paste" popup appears, obscuring the code.

How do I get rid of it?

Issue 2:
Hey guys,

I just noticed a new feature in the code editor today. Its great to have for copying and pasting code to ask questions, but it can get in the way if I am just doing regular copy and pasting.

Would a better solution to this be to hold down shift + highlight the section as a way to access the menu?

What do you guys think?
Issue 1:
From @alexanderby on November 19, 2015 9:35

When formatting JavaScript or TypeScript, comments placed between parts of multi-line expressions are placed wrong.

Expected to look like

doStuff()
.then()
// Comment
.then();

but actually is

doStuff()
.then()
// Comment
.then();

Copied from original issue: microsoft/vscode#184

Issue 2:
To reproduce:

declare var _: any;

function chainer() {
_.chain()
// something here
.then()
// something here
.then()
// something here
.then();
}

Format the code. You get

declare var _: any;

function chainer() {
_.chain()
// something here
.then()
// something here
.then()
// something here
.then();
}

Observe the unindented comments.
Issue 1:
<input type='number' defaultValue={someValue}/> does not work correctly in Chrome. When user type in a decimal point ., the point will disappear and the caret will be be reset to the beginning of the input. If you keep typing in . twice, the value of input will disappear. However, if a input has no defaultValue, it seems to work fine.

I've put together a fiddle page to demo the bug: https://jsfiddle.net/sc3wpujs/2/

I think it has something to do with the internal state management of an uncontrolled component. When the first . is typed, it does not get to target.value (chrome may have trimmed the "unnecessary" . from the value because it's type is number). React pushing target.value back to input causing the . to disappear and caret position reset. Now if two . are typed in, the value is no longer a valid number and Chrome may return '' for target.value, causing the input to be reset.

Issue 2:
This appears to have been introduced in a new Chrome version, but I can't find any reference to where.

Affected/Tested Browsers (OS X):

Chrome 51.0.2704.106 (64-bit)

Opera 39.0.2256.15

Unaffected Browsers:

Safari 9.1

Firefox 49

Backspacing in an input element with value or defaultValue set causes some very odd behavior. Once a decimal point is gone, it can't easily be re-added.

Example:

In this example, I simply backspaced twice. On the second backspace, when I expect 3. to be showing, the input instead reads 3 and the cursor has moved to the beginning. The next two jumps are my attempts to add another decimal point.

Fiddle: https://jsfiddle.net/kmqz6kw8/

Tested with React 15.2.

Notes: This only occurs when value or defaultValue is set. If neither is set, the input behaves properly. We are currently working around this issue by (unfortunately) setting the input value on componentDidMount via a ref.
Issue 1:
System information (version)

OpenCV => 4.1.0

Operating System / Platform => Mac OS Mojave 10.14

Compiler => n/a python 3.7

Detailed description

https://docs.opencv.org/4.1.0/dd/dd7/tutorial_morph_lines_detection.html

python version of tutorial throws the following error:

File "ExtractHorzVert.py", line 104, in

main()

File "ExtractHorzVert.py", line 53, in main

horizontalStructure = cv.getStructuringElement(cv.MORPH_RECT, (horizontal_size, 1))

TypeError: integer argument expected, got float

Steps to reproduce

horizontal_size = cols / 30
horizontalStructure = cv.getStructuringElement(cv.MORPH_RECT, (horizontal_size, 1))

Issue 2:
System information (version)

OpenCV => :3.4

Operating System / Platform => :Windows 64 Bit / python

Compiler => :(python 3.6)

Detailed description

OpenCV writes a hdr file with header starting with "#?RGBE". But many programs suppose "#?RADIANCE" and don't work on files with "#?RGBE". Would you change this header line to "#?RADIANCE"?
Issue 1:
When using Deno.listen() without passing in the parameter hostname, it should listen to both ipv6 and ipv4 by default.

I found that currently it only listens on ipv4.

Deno 1.21.1

Issue 2:
After upgrading to version 1.14 this error happened when using deno bundle

Example test.ts code:

import { Application } from "https://deno.land/x/oak@v9.0.0/mod.ts";

const app = new Application();

app.use((ctx) => {
ctx.response.body = "Hello World!";
});

await app.listen({ port: 8000 });

Commads:

deno bundle test.ts out.js
deno run -A out.js

Error:

error: Uncaught ReferenceError: Cannot access 'Response' before initialization
const DomResponse = Response;
^

Deno version

deno 1.14.0 (release, x86_64-apple-darwin)
v8 9.4.146.15
typescript 4.4.2