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.0

Operating System version: MacOS

Java version: 11.0.1

Steps to reproduce this issue

Run org.apache.dubbo.demo.provider.Provider

Expected Result

Provider should start.

Actual Result

Caused by: java.lang.IllegalStateException: Failed to connect to config center (zookeeper): 127.0.0.1:2181 in 30000ms.
at org.apache.dubbo.configcenter.support.zookeeper.ZookeeperDynamicConfiguration.initWith(ZookeeperDynamicConfiguration.java:79)
at org.apache.dubbo.configcenter.AbstractDynamicConfiguration.<init>(AbstractDynamicConfiguration.java:46)
at org.apache.dubbo.configcenter.support.zookeeper.ZookeeperDynamicConfiguration.<init>(ZookeeperDynamicConfiguration.java:62)
at org.apache.dubbo.configcenter.support.zookeeper.ZookeeperDynamicConfigurationFactory.createDynamicConfiguration(ZookeeperDynamicConfigurationFactory.java:29)
at org.apache.dubbo.configcenter.AbstractDynamicConfigurationFactory.getDynamicConfiguration(AbstractDynamicConfigurationFactory.java:33)
at org.apache.dubbo.config.ConfigCenterConfig.startDynamicConfiguration(ConfigCenterConfig.java:105)
at org.apache.dubbo.config.ConfigCenterConfig.init(ConfigCenterConfig.java:82)
at org.apache.dubbo.config.spring.ConfigCenterBean.afterPropertiesSet(ConfigCenterBean.java:98)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1688)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1626)
... 12 more

People may not install zookeeper locally, we need to restore the behavior to use multicast as default registry.

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: 2.7.3

Operating System version: macOs

Java version: 1.8

Steps to reproduce this issue

export service with protocolConfig defined as below in API mode.

ProtocolConfig protocolConfig = new ProtocolConfig();
protocolConfig.setPort(20880);
protocolConfig.setIothreads(2);

ServiceConfig messageService = new ServiceConfig();
messageService.setProtocol(protocolConfig);

export another service with default protocol as below in XML mode.

<bean id="demoService" class="com.ctrip.framework.cdubbo.api.DemoServiceImpl"/>
<dubbo:service interface="com.ctrip.framework.cdubbo.api.DemoService" ref="demoService">
</dubbo:service>

XML service get API service's protocol, which makes port and iothreads parameter incorrect.

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

Expected Result

XML service's port should in default 20880.

Actual Result

XML service's port is 20770, and iothreds is 2.
Issue 1:
In the meantime, using the above ideas here is what I came up with:

import { withRouter } from 'next/router';

export const withPageRouter = Component => {
return withRouter(({ router, ...props }) => {
router.query = [
...new URLSearchParams((router.asPath || '').split(/\?/)[1]).entries()
].reduce((q, [k, v]) => Object.assign(q, { [k]: v }), {});

return <Component {...props} router={router} />;
});
};

Originally posted by @cansin in #4804 (comment)

We should make sure (add a test) that client-side query strings are correctly merged into statically exported pages post-hydration (for a normal and dynamically routed page).

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

Expected Behavior

$ npm run test

Should run testcases without mistakes

Current Behavior

Steps to Reproduce (for bugs)

download next.js canary

npm install

npm run test

Your Environment

Tech
Version

next
canary

node
6.7.0

OS
Mac OS 10.12.6

tty
zsh
Issue 1:
VSCode Version: 1.2.0

OS Version: Windows 10

Steps to Reproduce:

Open the new embedded command line (CTRL + ")

Close CLI and change vscode theme

Then open embedded CLI again

It is not working!

Issue 2:
VSCode Version: Version 1.2.0-insider Commit 7ccb21d

OS Version: Fedora 23

Steps to Reproduce:

Open Terminal

Change Color Theme

Terminal is then broken until VSCode is restarted
Issue 1:
Compare this https://babeljs.io/repl/#?experimental=true&evaluate=true&loose=false&spec=false&code=function%20f%20()%7B%0A%20%20%2F%2F%20comment%20here%0A%20%20var%20f%0A%7D

to this https://babeljs.io/repl/#?experimental=true&evaluate=true&loose=false&spec=false&code=function%20f%20()%7B%0A%20%20%2F%2F%20comment%20here%0A%7D

Is there any reason for this behaviour? I used this trick https://github.com/ractivejs/ractive/blob/db7a5d61730ad72857ae355597838b3d77f5bc28/src/utils/log.js#L21 and suddenly realised it doesn't work because of the issue. I managed to solve it by switching to a similar technique (unused variable), but this still looks like an inconsistency.

Issue 2:
This code:

try {
foo();
} catch(e) {
// do nothing
}

Compiles to this:

"use strict";

try {
foo();
} catch (e) {}

// do nothing

It's ok at all, except eslint. It's affecting no-empty rule.
Issue 1:
This is slightly inconvenient when one uses atom -w for things like git commit messages, it'd be great if just closing the tab that was opened was enough to cause the process to exit.

Issue 2:
Hi, guys.

I've started to learn how to code and found out about Atom. I downloaded the installer and when I run it shows a error message "Instalation has failed/Failed to extract installer", even if I run as admin. Downloaded the installer twice. Am I doing something wrong? My os is win8 x64.

Thanks.
Issue 1:
Filing this as a close duplicate of #9299 because that issue is locked, and with the release of Node v12, the createRequireFromPath boilerplate has become more widespread, and it involves import.meta.url:

import {createRequireFromPath as createRequire} from 'module';
import {fileURLToPath as fromURL} from 'url';
const require = createRequire(fromURL(import.meta.url));

As a Babel end-user, I don't know how to work around the SyntaxError: Cannot use 'import.meta' outside a module, and leaving that issue open might allow someone more knowledgeable to offer a solution.

I personally find it mildly infuriating when conversations are locked without any spam or abuse problems, because nether I nor others can add anything that might help each other. Sometimes the "final word" from the core team is less than intelligible to those new to the topic.

Issue 2:
I am getting the following two type errors after switching to preset-env;

Issue 1

Duplicate declaration "activities" (This is an error on an internal node. Probably an internal error)

Related relevant code with the various (valid) declarations of activities:

.run((Page, Filters, moment, $store, $state, $transitions) => {
$transitions.onEnter({to: 'bookings'}, transition => {
const params = {};
if (!params.activity) {
const activities = transition.injector().get('activities');
//...
}
//...
});

//Page setup
$transitions.onSuccess({to: 'bookings'}, transition => {
//...
const activities = transition.injector().get('activities');
//...
});

Page.defineOption('switchActivity', {
async click() {
//...
const activities = await $store.activities.query();
//...
},
});
});

They are all defined in their own function scope, so perfectly valid.

Issue 2

Cannot read property '0' of null

Related code:

//Set relevant option
if (last && this.reminderOptions.some(o => o.value === last)) {
this.booking.reminderTime = last;
}
else {
this.booking.reminderTime = this.reminderOptions[0].value;
}

No idea why the latter error would be thrown as babel can't know what the value of this.reminderOptions will be at runtime, or whether it is null.

Babel/Babylon Configuration (.babelrc, package.json, cli command)

{
"presets": [
["env", {
"targets": {
"browsers": ["chrome >= 60"]
}
}]
],
"plugins": [
"syntax-async-functions",
"transform-regenerator",
"angularjs-annotate"
]
}

Expected Behavior

The code should compile and no errors should be thrown

Current Behavior

Error is thrown as described above.

Context

Can't build, had to revert back to es2015

Your Environment

"babel-core": "^6.26.0",
"babel-plugin-angularjs-annotate": "^0.8.2",
"babel-plugin-syntax-async-functions": "^6.13.0",
"babel-plugin-transform-regenerator": "^6.26.0",
"babel-polyfill": "^6.26.0",
"babel-preset-env": "^1.6.1",

software
version(s)

node
8.9.4

npm
Yarn 1.3.2

Operating System
OS X
Issue 1:
Costin Leau opened SPR-7703 and commented

The process of finding the methods to be invoked for each http dispatch could be improved. While it has been already addressed in a previous released, there are still some minor improvements to be made.

Issue Links:

#11510 improve annotation based invocations ("duplicates")

Referenced from: commits ec2603d, 01e79cf, 3552173, 18540de

Issue 2:
Arjen Poutsma opened SPR-7023 and commented

Currently, the RestTemplate has no way to handle generic types. In other words, the following does not work:

List<MyDomain> myDomainList = restTemplate.getForObject(uri, List.class);

This should be fixed.

Affects: 3.1.1

Issue Links:

#13482 RestTemplate Converting Generic Types ("is duplicated by")

#13028 HttpMessageConverter doesn't support typed collections

#19423 Add PATCH HTTP operation to RestTemplate

#11667 RestTemplate fails to convert properly for Generic Type Container with MappingJacksonHttpMessageConverter

Referenced from: commits ed3823b

14 votes, 16 watchers
Issue 1:
If we add 'numpy==1.20.2' requirements.txt, it resolves the following issue

2021-05-10 20:35:16,558 | Final missing wheels: {numpy==1.20.3(wheel)}

2021-05-10 20:35:19,015 | PythonPipBuilder:ResolveDependencies failed

Traceback (most recent call last):

File "/usr/local/Cellar/aws-sam-cli/1.21.1/libexec/lib/python3.8/site-packages/aws_lambda_builders/workflows/python_pip/actions.py", line 39, in execute

package_builder.build_dependencies(

File "/usr/local/Cellar/aws-sam-cli/1.21.1/libexec/lib/python3.8/site-packages/aws_lambda_builders/workflows/python_pip/packager.py", line 137, in build_dependencies

self._dependency_builder.build_site_packages(requirements_path, artifacts_dir_path, scratch_dir_path)

File "/usr/local/Cellar/aws-sam-cli/1.21.1/libexec/lib/python3.8/site-packages/aws_lambda_builders/workflows/python_pip/packager.py", line 207, in build_site_packages

raise MissingDependencyError(packages_without_wheels)

aws_lambda_builders.workflows.python_pip.packager.MissingDependencyError: {numpy==1.20.3(wheel)}

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/usr/local/Cellar/aws-sam-cli/1.21.1/libexec/lib/python3.8/site-packages/aws_lambda_builders/workflow.py", line 269, in run

action.execute()

File "/usr/local/Cellar/aws-sam-cli/1.21.1/libexec/lib/python3.8/site-packages/aws_lambda_builders/workflows/python_pip/actions.py", line 45, in execute

raise ActionFailedError(str(ex))

aws_lambda_builders.actions.ActionFailedError: {numpy==1.20.3(wheel)}

Build Failed

Issue 2:
I was wondering if it's possible for the relevant Numpy DLLs (e.g. lapack_lite or _umath_linalg) to export the CBLAS functions, so that other software can call into them using e.g. ctypes. Under Linux they are exported by default, but not under Windows (AFAIK you have to explicitly export symbols on Windows, by default "global" symbols in a shared library are private to the library).

Or perhaps I'm missing another way of accessing those functions at runtime?
Issue 1:
Version

2.5.13

Steps to reproduce

Use a component for property display in a loop over ordered by descendant array

What is expected?

An actual value

What is actually happening?

Cached value of previous object is displaying

I'm new with Vuejs and probably my issue is a dummy one, but I've not still realized how to fix it.

Situation: I have a collection of objects which I've sorted with lodash:

{
computed: {
sortedAlerts: function() {
return _.orderBy(this.filteredAlerts, 'createdAtUtc', 'desc');
}
}
}

And iterating with v-for="alert in sortedAlerts".

I also display one of the object property with the usage of Vuejs component:

components: {
'alert-title': {
props: ['model'],
computed: {
indicatorTitle: function() {
return this.alert.indicator.title.toLowerCase();
},
conditionTitle: function() {
return this.alert.condition.title.toLowerCase();
}
},
template:'<span><i>{{indicatorTitle}}</i> is {{conditionTitle}} {{alert.amount}}</span>',
data: function() {
return {
alert: this.model
}
}
}
}

like this <span is="alert-title" v-bind:model="alert"></span>.

Finally, when I add new objects into this array (which going to be the first elements in ordered array), the alert-title component do not display newly added object in a proper way (but continue to display the previous one, which now is actualty the second and duplicate).

Page refresh is fixing this situation, but I'm pretty sure that the code have an issue.

I know it's not too clear but I hope someone could figure out what's wrong with it.

Let me know if an example should also be provided.

Thank you.

Issue 2:
Important Note

I don't want this to happen in Vue, I just want to know how can I implement this in my projects.

If this can't be done right now ... Then this is a feature request of CustomKey

If this can already happen ... Then Please tell me how I can and happy to close!

What problem does this feature solve?

Keeping things short

I want to duplicate this below stuff

export default {
components: {
ComponentAdam,
ComponentMadam,
},
};

and make something like this ...

export default {
components: {
ComponentAdam,
ComponentMadam,
},
objects: {
ObjectSierra,
ObjectHotel,
ObjectIndia,
ObjectEcho,
ObjectLima,
ObjectDelta,
},
};

What does the proposed API look like?

Not exactly sure!
Issue 1:
Electron version: v.1.8.2.beta4

Operating system: Windows 10

I have a simple window and showed DevTools on it and when I start typing into its console, program crashes.

edit:grammar

Issue 2:
Electron version: 1.8.2-beta.3

Operating system: Windows_NT 10.0.15063

Expected behavior

When devtools are open I should be able to type directly into the console.

Actual behavior

When you type into the console in devtools it crashes the electron app without showing any errors.

How to reproduce

git clone https://github.com/electron/electron-api-demos.git
cd electron-api-demos
npm install --save-dev electron@1.8.2-beta.3
npm install
npm start

When the electron window opens, go to View menu, then Toggle Developer Tools option.

Go to Console tab.

Click into the console by the > and start typing anything.
Issue 1:
I have faced the issue with production build. I don't know why, but Next's babel config didn't properly compile my source code, so I ended up with "unexpected token punc()" which is most likely not compiled source to ES5 (which is needed for UglifyJS).

I have been searching for issues and also tried to extend babel config with babel-preset-env (targets.uglifyjs = true), but actually it didn't work, nor es-2015 presets.

I have fixed this issue by extending webpack config with BabiliPlugin and removing UglifyJS. This is first issue I wanted to report... Moreover I think uglify should be removed if it doesn't support new JS syntax. I want to be able to specify what browsers I support.

I have also a problem to detect where and what caused the problem in my source.

Sorry if this issue has been already discussed.

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

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

Expected Behavior

next dev should accept the -H/--hostname argument, like next start (see #1017).

Current Behavior

next dev ignores the hostname argument, defaulting to localhost.

Context

Cloud9 wants servers to start on 0.0.0.0

I am happy to provide a PR for this if you agree.
Issue 1:
I was just installing Three through npm and noticed that the code snippet and the JS fiddle at the end of the page is using THREE.CanvasRenderer. https://www.npmjs.com/package/three

You'll see this warning in the console:

"THREE.CanvasRenderer has been moved to /examples/js/renderers/CanvasRenderer.js"

It should probably be updated to use: renderer = new THREE.WebGLRenderer();

Fixed fiddle: https://jsfiddle.net/9sp1hqvb/

The script on the page should also have that fix:

<script>

var camera, scene, renderer;
var geometry, material, mesh;

init();
animate();

function init() {

camera = new THREE.PerspectiveCamera( 75, window.innerWidth / window.innerHeight, 1, 10000 );
camera.position.z = 1000;

scene = new THREE.Scene();

geometry = new THREE.BoxGeometry( 200, 200, 200 );
material = new THREE.MeshBasicMaterial( { color: 0xff0000, wireframe: true } );

mesh = new THREE.Mesh( geometry, material );
scene.add( mesh );

renderer = new THREE.WebGLRenderer();
renderer.setSize( window.innerWidth, window.innerHeight );

document.body.appendChild( renderer.domElement );

}

function animate() {

// note: three.js includes requestAnimationFrame shim
requestAnimationFrame( animate );

mesh.rotation.x += 0.01;
mesh.rotation.y += 0.02;

renderer.render( scene, camera );

}

</script>

If you're installing for the first time, this would be super confusing.

Sorry if this issue is a duplicate. I searched but didn't find anything about this.

Issue 2:
Hi,

First thank you for your amazing work. I am stunned by what that library can do!

I am using three.js with a dae on an ipad.

Now what i want to do is

select an object with touch

make all other objects' opacity to 0.2 and the selected to 1.0

This would make it clear what object you selected.

Now my problem is that the same material is shared by almost all objects in the dae. So applying opacity to one object's material will actually apply it to almost all objects in the dae.

So my idea was to use traverseHierarchy on dae loading and do something like

object.material = object.material.clone()

But that doesnt work. So my question is how can i clone a material?

Or may be there is another way of doing what i want ...

Thank you
Issue 1:
Environment

Windows build number: 18363.959
PowerToys version: 0.19.2
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run and/or Keyboard Manager

Steps to reproduce

Setup a Keyboard shortcut for Win+R -> Alt+Space

(optional) Open PowerToys Run with Alt+Space, type some stuff (anything), hit Esc

Open PowerToys Run with Win+R, note that you can hit backspace and escape, but typing anything else doesn't work.

Now 'Alt' is soft-locked pressed on the machine and trying to interact with other windows/OS causes issues, like trying to hit Win+R again is actually trying to hit Win+Alt+R and start a GameBar recording.

Expected behavior

Win+R should be able to bring up PowerToys Run normally, this worked fine before, so seems like a regression?

Alt key shouldn't get stuck 'down'.

Actual behavior

Unable to type into Power Toys Run textbox, Alt key is getting stuck in pressed state after closing PowerToys Run after using mapped shortcut.

Issue 2:
Ability to open a website in a choice of browsers after typing a URL, or at the very least, the default browser
Issue 1:
Environment

Windows 1903

Fira Code with Font Ligatures enabled

Steps to reproduce

Use a font with font ligatures and type - or = as your first character.

Expected behavior

I would expect the prompt not to interact with the characters. In c:\projects\> the > symbol should not connect with any font ligatures.

Actual behavior

The > symbol combines to create font ligatures.

The behavior is shown in the below images:

Issue 2:
When fonts with programming ligatures is used, a weird behavior is show if write some characters at first, for example with FiraCode.
Issue 1:
When trying to compile a react 15 project with Typescript and MaterialUI 1.0.0-beta, typescript found inconsistencies on typings defined.

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

Expected Behavior

Material-ui, react15 and typescript should be able to compile properly.

Current Behavior

Typescript is not able to compile due to several typing / descriptor inconsistencies.

First according to material-ui package descriptor, material-ui should be compatible with both react 15 and react 16.

Some of typings for example of Table component seems to rely on react 16 definitions, and in order to be compatible with react 15 this should not occur.

Example errors:

.../material-ui/Tooltip/Tooltip.d.ts (4,18): error TS2430: Interface 'TooltipProps' incorrectly extends interface 'HTMLAttributes<HTMLDivElement>'. Types of property 'label' are incompatible. Type 'ReactNode' is not assignable to type 'string | undefined'. Type 'null' is not assignable to type 'string | undefined'.

.../material-ui/Table/TableCell.d.ts (17,11): error TS2694: Namespace 'React' has no exported member 'ThHTMLAttributes'.

.../material-ui/Table/Table.d.ts (5,17): error TS2694: Namespace 'React' has no exported member 'TableHTMLAttributes'.

.../material-ui/Snackbar/SnackbarContent.d.ts (5,18): error TS2430: Interface 'SnackbarContentProps' incorrectly extends interface 'PaperProps'. Types of property 'action' are incompatible. Type 'ReactElement<any> | undefined' is not assignable to type 'string | undefined'. Type 'ReactElement<any>' is not assignable to type 'string | undefined'. Type 'ReactElement<any>' is not assignable to type 'string'.

Steps to Reproduce (for bugs)

create-react-app my-app --scripts-version=react-scripts-ts

add material-ui

add a component and try to compile

Context

Project do not build.

Your Environment

Tech
Version

Material-UI
1.0.0-beta10

React
15.3.0

typescript
2.3.4

Issue 2:
I tried the table demo on your site and found nothing about editing.

Thus I request a cell editing feature like they do it with angularjs:

http://codepen.io/anon/pen/YwGJVr?editors=101

You can edit the last comment column :-)
Issue 1:
There are several issues with non-core (angular2.js) bundles we publish to npm:

we are not using any bundle arithmetic which means that we bundle parts of the core with those optional bundles. This is mostly visible in http where the bundle is pulling most of ng2 (if not all!) and is in fact bigger than ng2 itself (!)

non-core bundle import non-public APIs (ex.: angular2/src/core/facade/lang in router). This makes it pretty hard impossible (?) to move to CJS bundles that wouldn't have to bundle core again.

cc @jeffbcross @rkirov

Issue 2:
To start with the current SFX bundle (angular2.sfx.dev):

contains the following barrels: zone, reflect-metadata, common, core, instrumentation, platform/browser, upgrade, http, router:

common, core, instrumentation, platform/browser are exported on the ng namespace

http is exported on the ngHttp namespace

router is exported on the ngRouter namespace

is using dev output

isn't minified

doesn't have source maps

provides support for noConflict mode -> although it is broken now since it doesn't restore ngHttp and ngRouter namespaces

As part of our bundling discussion(s) we've been several times touching upon role, content and setup of the SFX bundle. More specifically the open questions were / are:

who is the main consumer of the SFX bundle (ES5, ngUpgrade?). AFAIK @rkirov is aware of another use-case

shell we use the same bundle for ES5 and ngUpgrade scenarios?

what should be the content? Some barrels are non-controversial (common, core, instrumentation, platform/browser) other are disputable

what exact namespaces shell be used to export different barrels?

should we keep the non-conflict mode?

From the list above we can see that there are number of small decisions that we need to take.