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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.8

Operating System version: MacOS 15.17

Java version: 1.8

Steps to reproduce this issue

Define a Main class for start dubbo include:

ClassPathXmlApplicationContext parentContext = new ClassPathXmlApplicationContext("classpath:applicationContext-root.xml");
ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext(new String[] {"classpath:/configs/applicationContext-app.xml" }, parentContext);
ApplicationContext.setContainer(context);
context.start();
System.in.read();

In applicationContext-root.xml declare：

<dubbo:application name="dubbo-demo-api" />
<dubbo:registry protocol="zookeeper" address="172.20.71.128:2181" />

In applicationContext-app.xml declare:

<dubbo:service interface="org.demo.DemoService" ref="demoService" />
<bean id="demoService" class="org.demo.DemoServiceImpl" />

If declare dubbo service like above，demoService can not export to zookeeper registry.

In DubboBootstrap.java

private void exportServices() {
configManager.getServices().forEach(sc -> {
// TODO, compatible with ServiceConfig.export()
ServiceConfig serviceConfig = (ServiceConfig) sc;
serviceConfig.setBootstrap(this);

if (exportAsync) {
ExecutorService executor = executorRepository.getServiceExporterExecutor();
Future<?> future = executor.submit(() -> {
sc.export();
exportedServices.add(sc);
});
asyncExportingFutures.add(future);
} else {
sc.export();
exportedServices.add(sc);
}
});
}

configManager.getServices() return empty.

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: xxx

Operating System version: xxx

Java version: xxx

Steps to reproduce this issue

xxx

xxx

xxx

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:
From what I can see, LogisticRegressionCV.score always computes accuracy, not the metric given by scoring. That's inconsistent with the behavior of GridSearchCV. How do other CV estimators do that? I assume the same?

That's pretty unfortunate and I think we should change it. We did the same backward incompatible change in GridSearchCV before with a warning.

Issue 2:
input length (true, score) is 9177

output fp,tp,th size is 5816 but when I re-sample the data it is 5756 (I guess due to sampling with replacement creates duplicate data which is about 1/e)

in matlab, perfcurve returns fp,tp,th the same size as the input size or at specified fp/tp/th values.
Issue 1:
>>> import pandas as pd
>>> df = pd.DataFrame({'x': [1.], 'y': [2.], 'z': [3.]})
>>> df.columns = ['x', 'x', 'z']
>>> df[['x', 'y', 'z']]
KeyError: "['z'] not in index"

I expected to see KeyError: "['y'] not in index".

I've tested this on the latest code in master (and on 0.16):

>>> pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 2.7.3.final.0
python-bits: 64
OS: Linux
OS-release: 2.6.18-400.1.1.el5
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_GB
LOCALE: None.None

pandas: 0.18.1+279.g31f8e4d
nose: None
pip: 1.3.1
setuptools: 0.6
Cython: 0.22
numpy: 1.9.2
scipy: None
statsmodels: None
xarray: None
IPython: 3.2.0-1
sphinx: None
patsy: None
dateutil: 2.4.2
pytz: 2015.6
blosc: None
bottleneck: None
tables: None
numexpr: None
matplotlib: None
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: None
httplib2: None
apiclient: None
sqlalchemy: None
pymysql: None
psycopg2: None
jinja2: None
boto: None
pandas_datareader: None

Issue 2:
Code Sample, a copy-pastable example if possible

>>> s = pd.Series([10,9,8,7,7,7,6])
>>> s.nlargest(4)
0 10
1 9
2 8
3 7
dtype: int64

Problem description

The docstrings list False as one of the possible argument values for keep. pandas raises a ValueError when attempting to use this parameter.

Expected Output

It would be nice to have nlargest work like this.

>>> s.nlargest(4, keep=False)
0 10
1 9
2 8
3 7
4 7
5 7

Output of pd.show_versions()

# Paste the output here pd.show_versions() here
INSTALLED VERSIONS
------------------
commit: None
python: 3.6.1.final.0
python-bits: 64
OS: Darwin
OS-release: 15.6.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8

pandas: 0.20.2

pytest: 3.0.7

pip: 9.0.1

setuptools: 35.0.2

Cython: 0.25.2

numpy: 1.13.0

scipy: 0.19.0

xarray: None

IPython: 6.0.0

sphinx: 1.5.5

patsy: 0.4.1

dateutil: 2.6.0

pytz: 2017.2

blosc: None

bottleneck: 1.2.0

tables: 3.4.2

numexpr: 2.6.2

feather: None

matplotlib: 2.0.2

openpyxl: 2.4.7

xlrd: 1.0.0

xlwt: 1.2.0

xlsxwriter: 0.9.6

lxml: 3.7.3

bs4: 4.6.0

html5lib: 0.999999999

sqlalchemy: 1.1.9

pymysql: None

psycopg2: None

jinja2: 2.9.6

s3fs: None

pandas_gbq: None

pandas_datareader: 0.3.0.post
Issue 1:
by jan.newmarch:

If a program has unused variables, then 6g produces a compile error. It would be nicer
as a compile warning instead. Often I'm commenting out a piece of code during debugging
which can change a variable from used to unused, meaning I have to temporarily get rid
of the variable which is a nuisance.

e.g.
package main

func main() {
var n int
}

produces
test.go:4: n declared and not used
and no object file

Preferred: same warning, but also an object file

Issue 2:
Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What does 'go version' print?
go1.4rc1 darwin/amd64

What steps reproduce the problem?
If possible, include a link to a program on play.golang.org.

1. install go from source code to build cross-compiler for android by
cd $GOROOT/src && \
./all.bash && \
CC_FOR_TARGET=$NDK_ROOT/bin/arm-linux-androideabi-gcc GOOS=android GOARCH=arm GOARM=7 ./make.bash

2. after install go from source code, there is no issue to build
golang.org/x/mobile/example/basic for target android by ./make.bash in that folder. The
android program can be successfully built.

3. But it have issue to build host darwin/amd64 cgo enabled code by
go build local_cgo_enabled_folder or
CGO_ENABLED=1 GOOS=darwin GOARCH=amd64 go build local_cgo_enabled_folder

What happened?
cc1: error: unrecognized command line option '-m64'

What should have happened instead?
build successfully.

Please provide any additional information below.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When developing an app, with or without a third-party server (express, for instance), the app should reload without "clearing" the terminal. When starting with next dev --preserve-log, the log should not be obscured. This option should also be available when starting programmatically with const app = next({ dev, preserveLog: true });.

Current Behavior

The log scrolls offscreen every time the app rebuilds.

Context

I will often start troubleshooting code with console.log. Having to take my hands off the keyboard to scroll back through the logs slows me down and breaks my flow.

Your Environment

Tech
Version

next
v4.1.1

node
v8.7.0

OS
macOS 10.13

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

Expected Behavior

When I upload details from a form to an end-point it works in dev server I can console.log and see the details.

But in production, both now and heroku, it returns error 501 not implemented.

It won't even log the first statement (content received) when I post to /api/contact-us/add

Using server.get instead of post doesn't help either

const express = require('express');
const next = require('next');
const mongoose = require('mongoose');
const bodyParser = require('body-parser');
const sgMail = require('@sendgrid/mail');

const dev = process.env.NODE_ENV !== 'production';
const app = next({ dev });
const handle = app.getRequestHandler();

const Contact = require('./database/ContactModel');

app.prepare()
.then(() => {
const server = express();
server.use(bodyParser.urlencoded({ extended: true }));
server.use(bodyParser.json());

server.post('/api/contact-us/add', (req, res) => {
console.log('Content received');
console.log(req.body);
});

server.get('*', (req, res) => {
return handle(req, res);
});

server.listen(3000, '0.0.0.0', (err) => {
if (err) throw err;
console.log('> Ready on http://localhost:3000');
});
})
.catch((ex) => {
console.error(ex.stack);
process.exit(1);
});

Your Environment

Tech
Version

next
3.0.6

node
8.3.0

OS
macOS

browser

etc
Issue 1:
I am building a web app with Flask when I encountered the strangest error.

pandas-0.19.2 calls in pandas.core.indexing

# 32-bit floating point machine epsilon
_eps = np.finfo('f4').eps

The call never finish in numpy-1.12.0 when called from the Apache server environment with mod_wsgi (compiled for Python/3.5.1+ and runtime using Python/3.5.2). The code loads properly when run from a normal Python/3.5.2 interpreter.

The very same code executes properly with pandas-0.18.1 and numpy-1.11.1 in the same Apache setup.

Issue 2:
If an application is using multiple embedded sub interpreters that use numpy, there is a possibility that floating point errors can cause the thread to deadlock. I traced this down to ufunc_object's _error_handler() method where it does NPY_ALLOW_C_API and that freezes on PyGILStateEnsure(). Interestingly, the PyGILState API is allegedly unsafe for applications using sub interpreters, but it works fine as long as long as each sub interpreter is on its own thread.

There is a workaround to call numpy.seterr(all='ignore') as that will not even enter the method. Ideally the print option would also not get the GIL as the GIL should not be needed for that. In the meantime I added a warning to Jep when it detects an interpreter on the same thread in the hopes of deterring the conditions that can cause this. I have a test case that illustrates the problem at https://github.com/mrj0/jep/blob/v3.3.0rc/src/jep/test/numpy/TestNumpyGILFreeze.java

This is somewhat related to gh-3837. If you have problems running the test case, you may need to configure the environment variables PATH, LD_LIBRARY_PATH, or LD_PRELOAD depending on your system.
Issue 1:
Summary of the new feature/enhancement

It would help people who use multiple keyboards to easily setup macros without needing third party softwares.

Proposed technical implementation details (optional)

I want to be able to remap all the keys of more than one keyboard. Or perhaps of all connected keyboards.

Issue 2:
Now if i type edge in Run(0.19.2), I get this:

However actually I want to open the sites I already opened, for which I have to scroll to the second page of Run.

Like this:

Thank you guys in advance.
Issue 1:
Config:

{
"presets": [
"node6",
"stage-1"
],
"plugins": [
"babel-plugin-transform-async-to-generator",
"babel-plugin-syntax-async-functions"
]
}

Code:

class A {
log() {
return new Promise(resolve => {
setTimeout(function () {
console.log('should print after 1 second');
resolve();
}, 1000);
});
}
}

class B extends A {
async log() {
await super.log();
}
}

const b = new B;
b.log();

Expected:

Should dump should print after 1 second to screen

Actual:

yield super.log();

^^^^^

SyntaxError: 'super' keyword unexpected here

Issue:

The issue is that an await statement is wrapped like this...

let B = class B extends A {
log() {
return _asyncToGenerator(function* () {
yield super.log(); // <--- `super` loses its context
})();
}
};

This fixes it:

let B = class B extends A {
log() {
const fn = super.log.bind(this);
return _asyncToGenerator(function*() {
yield fn.call();
})();
}
};

Issue 2:
Issue originally made by Dmitriy Krasnikov (dmitriy.krasnikov)

Bug information

Babel version: 6.3.26

Node version: 5.3

npm version: 3.3.12

Options

{
plugins:[
"transform-async-to-generator",
]
}

Input code

export class BaseClass {
async test(id){
console.log(id);
}
}
export class ChildClass extends BaseClass{
async test(id){
id=1;
super.test(id);
}
}

let cls = new ChildClass();
cls.test(5);

Description

Outputs:

export class BaseClass {
test(id) {
return _asyncToGenerator(function* () {
console.log(id);
})();
}
}
export class ChildClass extends BaseClass {
test(id) {
return _asyncToGenerator(function* () {
id = 1;
super.test(id);
})();
}
}

let cls = new ChildClass();
cls.test(5);
Issue 1:
Problem description

this is what causing the problem

<JssProvider>

This is a bug that i saw when making production build.

Below images the left side is development and right side is production.

This is my component.

Dev classes
Prod classes

MuiPaper-root-7
c7

MuiPaper-shadow2-b
cb

MuiPaper-rounded-8
c8

inject-Forgot-with-LangarStore-paper-3
c3

Below you see .c7 = .MuiPaper-root-7 which should only have background-color: #424242;.

But in production it has another set of style declarations.

Turns out in production .inject-DarkError-with-DarkErrorStore-LangarStore-root-7 and .MuiPaper-root-7 are given the same classname .c7

Steps to reproduce

Screenshots only

update: https://github.com/dsslimshaddy/jssprovider-bug

Versions

Material-UI: beta6

React: 15.6.1

Browser: latest chrome

Issue 2:
When using keyboard to navigate to, and use, a SelectField, when activating the field to open the dropdown, the currently selected item is not highlighted, nor in focus.

Example: https://www.youtube.com/watch?v=swz82ul6Hao

On clicking enter to open the dropdown, nothing is currently keyboard highlighted - on clicking "down" on the keyboard, the 2nd item is selected.

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

Expected Behavior

We would expect the first/current item to be focussed on opening the dropdown.

Current Behavior

Steps to Reproduce (for bugs)

Tab to a SelectField

Click enter to activate/open the field

Note that nothing is currently focussed/selected

Pressing down selects the next item in the list.

Context

Getting complaints from users during testing that to select the first item, we need to click down, then up again, and confusing that nothing is focussed on activating the dropdown.

Your Environment

Tech
Version

Material-UI
0.18.0

React
15.6.1

browser
Any

etc
Issue 1:
Challenge Target Even Numbered Elements Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36.

Please describe how to reproduce this issue, and include links to screenshots if possible.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
$("#target1").parent().css("background-color", "red");
$("#right-well").children().css("color", "orange");
$("#left-well").children().css("color", "green");
$(".target:nth-child(2)").addClass("animated bounce");
$(".target:even").addClass("animated Shake");

});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-sift-through-text-with-regular-expressions has an issue.

in this challenge explanation of regexp matching basics looks like on the screenshot below.

in the example it sounds rather misleading, that "+" quantifier relates to whole "the" / "and" word. in fact, it relates to "d" letter only.

regards,

moshe
Issue 1:
The exception messages thrown by the user checker don't support internationalization natively :

Symfony/vendor/symfony/src/Symfony/Component/Security/Core/User/UserChecker.php

Issue 2:
Translating form fields for which translation strings are available in "singular | plural" form fails.

Form translation always uses trans() and never transchoice(). There is apparently no way to tell it to do so. That means duplication of translations or other stupidity to work around this problem.
Issue 1:
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

Reopening #6971. I cannot reopen, so hence I'm making a new ticket.

Binding routerLink to null or empty array does not yield exception anymore, but yields a url to the current route rather than an empty href, which is surprising (and imo bad).

Expected behavior

I would expect empty routerLink (i.e. null/undefined/empty array/array with only nulls and undefined) to not add an href attribute. It doesn't make sense to just pick a url (the current) for linking when a url cannot be produced.

Angular version: 2.4.2

Issue 2:
[ ] bug report
[ x ] feature request
[ ] support request

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

Currently null or empty value passed to routerLink adds current page href value to link that is not useful. There is a lot of usecases for 'disabled' links that should not navigate anywhere and should not has href attribute at all.

It would be useful to have null/empty value support by routerLink that will results with no href attribute on link at all to prevent any navigation/link copying.
Issue 1:
If I have an inner object that has the same name as a type, then queries for that inner object will fail.

The workaround is to rename the type or the inner object, but the behaviour is confusing and misleading (and wrong).

To reproduce, create a new index, type and document:

curl -XPOST 'localhost:9200/test/flow/' -d '{

"device": {

"id": "dummy"

}

}'

Querying for that document by device.id will work:

curl 'localhost:9200/test/_search?pretty' -d '{

"query":{

"filtered": {

"filter": {

"term": {

"device.id": "dummy"

}

}

}

}

}'

Add a type with the same name as the inner object, AND containing an inner object with that name as well:

curl -XPOST 'localhost:9200/test/device/' -d '{

"device": {

"id": "foo"

}

}'

Now querying for the original document by device.id will fail:

{

"took" : 0,

"timed_out" : false,

"_shards" : {

"total" : 5,

"successful" : 5,

"failed" : 0

},

"hits" : {

"total" : 0,

"max_score" : null,

"hits" : [ ]

}

}

Removing the 'device' type will allow the original document to be queryable again:

curl -XDELETE 'localhost:9200/test/device'

Issue 2:
As far as I understand it, fields are resolved on a first found basis. So given the following documents:

PUT /index/foo/1
{
"count": 1,
"foo": {
"count": 1
}
}

PUT /index/bar/2
{
"count": 1,
"foo": {
"count": 1
}
}

.... the field foo.count could resolve to foo.count, foo.foo.count, or bar.foo.count, depending on which is found first.

Field resolution should be unambiguous. Field names should be grouped by type and sorted in descending order by number of .. So the above mappings should result in:

bar:
foo.count
count

foo:
foo.count
count

Then if no type is specified (or multiple types are specified), go through the groups in alphabetical order.

This would result in the following resolutions:

foo.foo.count => (foo) foo.count
foo.count => (foo) count
count => (bar) count
*.foo.count => (bar) foo.count
*.count => (bar) count
*.*.count => (bar) foo.count
Issue 1:
I am using Julia for an application in PDE-constrained optimization, and have run into an issue I haven't seen before, giving a segfault when trying to return (apparently) from a function call. I only mention the nested functions because in the optimization setup, I construct functionals using passed data, and then pass those functionals to my optimization routine. Not sure if that is creating some issue behind the scenes.

Based on the optimization trace, all of the iterations in the solver are working correctly, but then something breaks. The embedded PDE solver and optimization routine have passing unit tests, so I'm (pretty) sure the problem is not with their separate functionality, but somehow at the interface between them.

The gist with the backtrace is here https://gist.github.com/jgoldfar/b311086329af529fff42. The same issue appeared in version 0.3.0 I've been using for a while, but I figured I'd update to check if it resolved somehow. I'd be happy to look more into what is causing the issue on my own if someone could point me in the right direction!

Issue 2:
This is a cross-post of JuliaGraphics/Gtk.jl#466. Brief summary: there is a 10x increase in package load time for Gtk (from ~1s to ~10s), for which the main culprit is the sheer number of calls to jl_recache_method_instance. Looking at the signatures it's being called on, it's not clear that all of those deserve to be there.

This might be a consequence of the new artifact system, but the signatures lead me to be skeptical that it's related.
Issue 1:
Hi there, I'm stuck here.

Challenge escaping-literal-quotes-in-strings has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.

My code:

var myStr = "I am a \"double quoted\" string inside \"double quotes\"."; // Change this line

So, what's the problem? I can't complete this task because of this error:

You should use two double quotes (") and four escaped double quotes (").

But.. I'm use them all, no?

Issue 2:
On the current staging, two challenges ("Escaping Literal Quotes in Strings" and "Quoting Strings with Single Quotes") do not pass all tests with standard solution code.

Namely, tests asserting regex match lengths for non-escaped double quotes are failing:

code.match(/[^\\\\]\"/g).length === 2 in the former challenge and

code.match(/\"/g).length === 4 in the latter.

(Note: each of these is only one half of their respective test, and it might be beneficial in this case to split each test into two parts so users know where to look for their mistake instead of counting every quotation mark, as well as speeding up debugging if something breaks the regex again later on.)