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

Operating System version: windows

Java version: 1.8

Steps to reproduce this issue

incubator-dubbo-dubbo-2.6.3\dubbo-demo\dubbo-demo-provider

after run this main

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

Expected Result

dubbo=2.6.3

Actual Result

Issue 2:
Environment

Dubbo version: 2.6.3

Operating System version: win

Java version: 1.8.0_73

Steps to reproduce this issue

starting provider

Expected Result

regist 2.6.3 version

Actual Result

the actual regiser url is: dubbo://XXXX?dubbo=2.0.2 ...

备注

当provider注册service时，注册url中传的dubbo 版本号不正确，在注册中心里看到的版本号也不对，传了错误的2.0.2
Issue 1:
Got an error (403) while querying the GitHub API: {"message":"API rate limit exceeded for 180.253.11.147. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}

it gots me this url https://deno.land/x/accepts

Issue 2:
https://deno.land/std

Failed to get directory listing

Querying the GitHub API failed. This is usually caused by a network outage or because you have reached your hourly API rate limit of 60 requests.
Issue 1:
Description

In scikit-learn/scikit-learn/blob/master/sklearn/externals/joblib/externals/cloudpickle/cloudpickle.py,

import imp

should be changed to

import importlib

Issue 2:
Description

A deprecation warning is thrown when using sklearn. Recently cloudpickle was updated to do away with this warning, the sklearn version needs to be updated accordingly.

Steps/Code to Reproduce

I imagine this occurs anywhere cloudpickle is imported. I am getting it from:

from sklearn.ensemble import RandomForestRegressor

and using said Regressor

Expected Results

No deprecation warning should be thrown

Actual Results

/usr/local/lib/python3.6/dist-packages/sklearn/externals/joblib/externals/cloudpickle/cloudpickle.py:47: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses

import imp

Versions

System

python: 3.6.6 (default, Sep 12 2018, 18:26:19) [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]]
executable: /usr/bin/python3.6
machine: Linux-4.15.0-36-generic-x86_64-with-Ubuntu-18.04-bionic

BLAS

macros: NO_ATLAS_INFO=1, HAVE_CBLAS=None
lib_dirs: /usr/lib/x86_64-linux-gnu
cblas_libs: cblas

Python deps

pip: 18.1
setuptools: 40.0.0
sklearn: 0.20.0
numpy: 1.15.3
scipy: 1.1.0
Cython: None
pandas: 0.23.4
Issue 1:
Context:

Playwright Version: 1.24.*

Operating System: Windows

Node.js version: 16.10 +

Browser: Chrome

Code Snippet

electronApp = await electron.launch({ args: [path.join(__dirname, ' ****')], bypassCSP: true });

app1stWindow= await electronApp.firstWindow();

**Describe the bug**

**Electron 12 has been EOL, so i migrate the electron app to electron 18 , but seems the playwright get the firstWindow timeout,
my question is does latest playwright supported the electron 18 now???**

Issue 2:
Hi, we've noticed that context.route() can alter the rendering for some websites, e.g. https://www.wm.com/ca/en/support/faqs/how-do-i-handle-medical-waste-or-sharps-disposal

Would you know what can cause that, and how to debug it?

System info

Playwright Version: v1.32.3 (Node v18.15)

Operating System: Debian 11

Browser: Chromium, Firefox

Other info: A bit more reliable with Firefox

Source code

I provided exact source code that allows reproducing the issue locally.

Test file (self-contained)

const { chromium } = require('playwright');

(async () => {
const browser = await chromium.launch();

let success;
let attempt = 1;
do {
console.log(`attempt ${attempt}...`);
const context = await browser.newContext();

// This will make the rendering fail after a few attempts some point
// When commented out, all 100 attempts succeed.
await context.route('**/*', async route => {
await route.continue();
});

const page = await context.newPage();
await page.goto(
'https://www.wm.com/ca/en/support/faqs/how-do-i-handle-medical-waste-or-sharps-disposal',
{ waitUntil: 'networkidle' }
);
const element = page.locator('h1');
success = (await element.count()) > 0;
if (!success) {
console.log('FAILED!');
await page.screenshot({ path: 'rendering_fail.png' });
break;
}

await page.close();
await context.close();
++attempt;
} while (attempt <= 100);

await browser.close();
})();

Steps

node repro_script.js

Expected

Rendering never fails (100 successful attempts).

Actual

After a few rendering attempts, you will see a FAILED! log and a rendering_fail.png image is generated, showing that the content of the page wasn't correctly loaded.

Note: it never fails if the await context.route('**/*' hook is commented out.
Issue 1:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[ x ] 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 validation offered by the type attribute on an input element, such as , Angular 2 does not add the proper ng-invalid class when the browser sees the input as invalid.

Expected behavior

ng-invalid and ng-valid classes should be added appropriately when a user's input does not match the pattern defined by HTML5 type attribute.

Minimal reproduction of the problem with instructions

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

I believe it is best practice now to use type attributes offered by HTML5 to validate user input before submission.

Please tell us about your environment:

OSX, Brackets IDE, Angular CLI

Angular version: 2.0.X

2.0.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

All browsers

Language: [all | TypeScript X.X | ES6/7 | ES5]

Typescript

Node (for AoT issues): node --version =

Issue 2:
Data types: email, url, number, date, time, week, month.
Issue 1:
Hi.

Perhaps this has already been discussed, but I did not find.

IBM is already successfully experimenting with this.

https://github.com/IBM/browser-functions/blob/master/docs/index.md

There are a lot of advantages in this approach, native Web API from the browser manufacturer, SSR out of the box, only the I/O (fs, net) in the userland is missing, Deno can provide it.

How's the idea for you?

Issue 2:
Specified in https://html.spec.whatwg.org/multipage/structured-data.html#structureddeserializewithtransfer
Issue 1:
A lot of modern languages such as Julia heavily use math symbols. Without fallback fonts it's very hard to find font that has all the code points needed to properly render all the math fonts and emojis. Consolas doesn't have broad Unicode coverage, but with font fallbacks this can be improved.

Issue 2:
Please support emoji within Windows Console.

Very useful when you code in vim newsletters for startups or when you categorize stuff by emoji.

Maintainer notes:

The content you are editing has changed. Please copy your edits and refresh the page.

Title of tasklist

Cancel

Save

Input

Edit tasklist title

Beta
Give feedback

Tasklist Input, more options

Rename

Copy markdown

Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel

Delete

COOKED_READ (cmd.exe) doesn't properly support emoji input

#1503

Area-CookedRead

Area-Input

Issue-Feature

Priority-1

Product-Conhost

+5

Area-CookedRead

Area-Input

Issue-Feature

Priority-1

Product-Conhost

Edit...

Remove

Successfully updated the issue's project

There was an error updating the issue's project

[Epic] COOKED READ and character conversion fun with all our different Convert* functions

#7777

Impact-Correctness

Issue-Bug

Issue-Scenario

Product-Conpty

+4

Impact-Correctness

Issue-Bug

Issue-Scenario

Product-Conpty

Edit...

Remove

Successfully updated the issue's project

There was an error updating the issue's project

Options

Convert to issue

Toggle completion

Rename

Remove

Add item to Input

Type to add an item or paste in an issue URL

The content you are editing has changed. Please copy your edits and refresh the page.

Title of tasklist

Cancel

Save

Output

Edit tasklist title

Beta
Give feedback

Tasklist Output, more options

Rename

Copy markdown

Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel

Delete

[Epic] Text Buffer rewrite

#8000

Area-Output

Area-Server

Product-Terminal

+3

Area-Output

Area-Server

Product-Terminal

Edit...

Remove

Successfully updated the issue's project

There was an error updating the issue's project

Feature Request: Finish full unicode support (M:N cell rendering, ZWJ?)

#1472

Area-Rendering

+1

Area-Rendering

Edit...

Remove

Successfully updated the issue's project

There was an error updating the issue's project

Options

Convert to issue

Toggle completion

Rename

Remove

Add item to Output

Type to add an item or paste in an issue URL
Issue 1:
When I try to enter a command into the devtool console, the program crashes

Issue 2:
npm install electron --save-dev

Results in

> electron@1.6.6 postinstall ******\node_modules\electron
> node install.js

*******\node_modules\electron\install.js:47
throw err
^

Error: ENOENT: no such file or directory, lstat '******\node_modules\electron\dist\resources
'

....

"C:\\Users\\ir_fu\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "electron" "--save-dev"
npm ERR! node v7.9.0
npm ERR! npm v4.0.2
npm ERR! code ELIFECYCLE

npm ERR! electron@1.6.6 postinstall: `node install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the electron@1.6.6 postinstall script 'node install.js'.

Does anyone know why this happens?
Issue 1:
Environment

Microsoft Windows [版本 10.0.18362.267]
Windows Terminal version (if applicable):0.3.2142.0

Steps to reproduce

Open the terminal.

Switching CJK input methods.(doesn't work)

Typing.

Expected behavior

Show phrase candidate boxes.

Actual behavior

Directly entered English.

Issue 2:
Environment

Windows build number: Win32NT 10.0.18362.0
Windows Terminal version (if applicable): v0.4.2382.0

Steps to reproduce

Go to About screen, select text, right click, copy -> Crash

Select text if auto copy is enabled -> Crash

Select text and right click, copy -> Crash

Expected behavior

Expected behaviour is to have the selected text copied to the clipboard.

Actual behavior

Terminal becomes unresponsive for a second, then disappears.
Issue 1:
This works in Beta.0 but doesn't work in Beta.1

<select [(ngModel)]="name"> <option *ngFor="#n of names" [value]="n">{{n}}</option> </select> {{name}}

the current workaround in beta-1:

template.html:

<select class="form-control" #t (change)="update(t.value)"> <option *ngFor="#type of types" [value]="type">{{type}}</option> </select>

in component.ts

update(value){
console.log(value);
this.name=value;
}```

Issue 2:
I'm seeing an issue in beta.1 that appears to be a regression from beta.0. ngModel/ngModelChange don't appear to work at all in Firefox, at least on selects. Here's a plunkr demo. You'll notice if you change the script src's to beta.0, the selects work as expected. Is there a breaking change that I'm missing? I don't see anything about ngModel/ngModelChange in the changelog.

import {Component} from 'angular2/core';

@Component({
selector: 'my-app',
template: `
<h1>ngModel/ngModelChange not working on Firefox</h1>
<select [ngModel]="name" (ngModelChange)="changed($event)">
<option value=""></option>
<option *ngFor="#n of names" [value]="n">{{n}}</option>
</select>
<pre>Name: {{name}}</pre>

<select [(ngModel)]="name">
<option value=""></option>
<option *ngFor="#n of names" [value]="n">{{n}}</option>
</select>
<pre>Name: {{name}}</pre>
`
})
export class AppComponent {
names: String[] = ['Alpha', 'Bravo', 'Charlie'];
name: string;

changed(event) {
this.name = event;
}
}
Issue 1:
Bug summary

imshow rendering changed from 3.1.0 to 3.1.1 when yticks ar set.

Square matrix display is no longer square.

Note that setting xticks do not affect the display.

Code for reproduction

import matplotlib.pyplot as plt
fig, ax = plt.subplots()
ax.imshow([[1,2],[3,4]])
ax.set(yticks=[0,1]) # change the display in 1.3.1

outcome in 3.1.1

Previous outcome in 3.1.0

Matplotlib version

Operating system: Linux

Matplotlib version: 3.1.0 / 3.1.1

Matplotlib backend: module://ipykernel.pylab.backend_inline

Python version: 3.7.3

Issue 2:
Bug report

Bug summary

The very top and bottom of the heatmaps are getting truncated to 1/2 height in version 3.1.1. This does not happen for version 3.0.3.

This is the code from a Jupyter Notebook

import matplotlib
import pandas as pd
import numpy as np
import seaborn as sb
%pylab inline

print(matplotlib.__version__)
print(sb.__version__)

grid = pd.DataFrame(np.arange(9).reshape((3,3))/10)
fig, ax = subplots(1, 1, figsize=(5, 5))

sb.heatmap(grid, annot=True, fmt=".0f", ax=ax, cmap='RdBu', vmin=0, vmax=1, cbar=True);

Actual outcome

Populating the interactive namespace from numpy and matplotlib
3.1.1
0.9.0

Matplotlib version

Operating system: Ubuntu Linux

Matplotlib version: 3.1.1

Matplotlib backend: module://ipykernel.pylab.backend_inline

Python version: 3.6

Jupyter version (if applicable): 4.4.0

Other libraries:
Issue 1:
Challenge Name

Any Computer Basics tutorial -- the quizzes for passing cut away from the last question and goes to the next lesson

Issue Description

Browser Information

Browser Name, Version: Chrome

Operating System: Win 10

Mobile, Desktop, or Tablet: Desktop

Your Code

// If relevant, paste all of your challenge code in here

Screenshot

Issue 2:
Challenge create-a-javascript-slot-machine has an issue.

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

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

<script>
function runSlots() {
var slotOne;
var slotTwo;
var slotThree;

var images = ["//i.imgur.com/9H17QFk.png", "//i.imgur.com/9RmpXTy.png", "//i.imgur.com/VJnmtt5.png"];

// Only change code below this line.
slotOne = Math.floor(Math.random() * (3 - 1 + 1)) + 1;
slotTwo = Math.floor(Math.random() * (3 - 1 + 1)) + 1;
slotThree = Math.floor(Math.random() * (3 - 1 + 1)) + 1;

// Only change code above this line.

if (slotOne !== undefined && slotTwo !== undefined && slotThree !== undefined) {
$(".logger").html(slotOne + " " + slotTwo + " " + slotThree);
}

$(".logger").append(" Not A Win")
return [slotOne, slotTwo, slotThree];
}

$(document).ready(function() {
$(".go").click(function() {
runSlots();
});
});
</script>

<div>
<div class = "container inset">
<div class = "header inset">
<img src="https://s3.amazonaws.com/freecodecamp/freecodecamp_logo.svg.gz" alt="learn to code JavaScript at Free Code Camp logo" class="img-responsive nav-logo">
<h2>FCC Slot Machine</h2>
</div>
<div class = "slots inset">
<div class = "slot inset">

</div>
<div class = "slot inset">

</div>
<div class = "slot inset">

</div>
</div>
<br/>
<div class = "outset">
<button class = "go inset">
Go
</button>
</div>
<br/>
<div class = "foot inset">
<span class = "logger"></span>
</div>
</div>
</div>

<style>
.container {
background-color: #4a2b0f;
height: 400px;
width: 260px;
margin: 50px auto;
border-radius: 4px;
}
.header {
border: 2px solid #fff;
border-radius: 4px;
height: 55px;
margin: 14px auto;
background-color: #457f86
}
.header h2 {
height: 30px;
margin: auto;
}
.header h2 {
font-size: 14px;
margin: 0 0;
padding: 0;
color: #fff;
text-align: center;
}
.slots{
display: flex;
background-color: #457f86;
border-radius: 6px;
border: 2px solid #fff;
}
.slot{
flex: 1 0 auto;
background: white;
height: 75px;
margin: 8px;
border: 2px solid #215f1e;
border-radius: 4px;
}
.go {
width: 100%;
color: #fff;
background-color: #457f86;
border: 2px solid #fff;
border-radius: 2px;
box-sizing: none;
outline: none!important;
}
.foot {
height: 150px;
background-color: 457f86;
border: 2px solid #fff;
}

.logger {
color: white;
margin: 10px;
}

.outset {
-webkit-box-shadow: 0px 0px 15px -2px rgba(0,0,0,0.75);
-moz-box-shadow: 0px 0px 15px -2px rgba(0,0,0,0.75);
box-shadow: 0px 0px 15px -2px rgba(0,0,0,0.75);
}

.inset {
-webkit-box-shadow: inset 0px 0px 15px -2px rgba(0,0,0,0.75);
-moz-box-shadow: inset 0px 0px 15px -2px rgba(0,0,0,0.75);
box-shadow: inset 0px 0px 15px -2px rgba(0,0,0,0.75);
}
</style>

```
Issue 1:
In [62]: index = pd.MultiIndex.from_arrays([['a', 'b', 'c'], [1, 2]])

In [63]: index
Out[63]:
MultiIndex(levels=[['a', 'b', 'c'], [1, 2]],
labels=[[0, 1, 2], [0, 1]])

Probably not what the user wants, and we rely on them being the same length in, e.g. index.shape which will raise a ValueError if you access it.

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

In [2]: pd.MultiIndex.from_arrays([[1,2,3], ['a', 'b']])
Out[2]:
MultiIndex(levels=[[1, 2, 3], ['a', 'b']],
labels=[[0, 1, 2], [0, 1]])

In [3]: pd.MultiIndex.from_arrays([[1,2,3], ['a', 'b']]).values
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
<ipython-input-3-65e6fa14e07f> in <module>()
----> 1 pd.MultiIndex.from_arrays([[1,2,3], ['a', 'b']]).values

/home/nobackup/repo/pandas/pandas/indexes/multi.py in values(self)
552 values.append(taken)
553
--> 554 self._tuples = lib.fast_zip(values)
555 return self._tuples
556

/home/nobackup/repo/pandas/pandas/lib.pyx in pandas.lib.fast_zip (pandas/lib.c:11131)()
587 it = <flatiter> PyArray_IterNew(arr)
588 if len(arr) != n:
--> 589 raise ValueError('all arrays must be same length')
590
591 for i in range(n):

ValueError: all arrays must be same length

Expected Output

The first previous command should already raise an error.

output of pd.show_versions()

In [4]: pd.show_versions()

INSTALLED VERSIONS
------------------
commit: a63bd12529ff309d957d714825b1753d0e02b7fa
python: 3.5.1.final.0
python-bits: 64
OS: Linux
OS-release: 4.5.0-2-amd64
machine: x86_64
processor:
byteorder: little
LC_ALL: None
LANG: it_IT.utf8
LOCALE: it_IT.UTF-8

pandas: 0.18.1+174.ga63bd12
nose: 1.3.7
pip: 1.5.6
setuptools: 18.4
Cython: 0.23.4
numpy: 1.10.4
scipy: 0.16.0
statsmodels: 0.8.0.dev0+111ddc0
xarray: None
IPython: 5.0.0.dev
sphinx: 1.3.1
patsy: 0.3.0-dev
dateutil: 2.2
pytz: 2012c
blosc: None
bottleneck: 1.1.0dev
tables: 3.2.2
numexpr: 2.5
matplotlib: 1.5.1
openpyxl: None
xlrd: 0.9.4
xlwt: 1.1.2
xlsxwriter: 0.7.3
lxml: None
bs4: 4.4.0
html5lib: 0.999
httplib2: 0.9.1
apiclient: 1.5.0
sqlalchemy: 1.0.11
pymysql: None
psycopg2: None
jinja2: 2.8
boto: 2.38.0
pandas_datareader: 0.2.1
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

npm install should work on branch getting-started

Current Behavior

npm install fails with this output:

npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated @semantic-release/last-release-npm@2.0.2: Use @semantic-release/npm instead
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for duplexer3

npm ERR! A complete log of this run can be found in:
npm ERR! /home/jeff/.npm/_logs/2018-01-06T19_19_13_553Z-debug.log

Steps to Reproduce (for bugs)

git clone

git checkout getting-started

npm install

Environment

Tech
Version

next
^4.2.0

node
8.9.3

OS
Manjaro GNOME 3 x64 (relatively) fresh install

browser
Firefox 57.0.3

etc
npm version 5.6.0

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

Repro steps

When using an npm module that requires regeneratorRuntime (part of babel-runtime), I get an error:

regeneratorRuntime is not defined

Makes sense. So I try to define it by placing this at the top of my page .js file:

import 'babel-runtime';
import 'babel-runtime/regenerator';

But the error persists. It seems like I'm not importing the runtime early enough, but I don't know where else to put it. If I move it to _document.js, the same problem occurs.

Ultimately, I just want regeneratorRuntime to be defined on both client and server so I can use a library that expects it. (Many libraries exclude regeneratorRuntime from their bundles because it's oftentimes needed by several dependencies, and it's quite large.)

Is there some straightforward way to do this that I'm missing?

Your Environment

Tech
Version

next
5.1.0

node
8.9.1
Issue 1:
I’m working on a Rails project that uses the react-rails gem. We have React 15.1.0 and a pre-made modal component that requires react-addons-transition-group 15.0.1 (among other things). When the modal loads, I get the following error:

Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner)

When I try to close the modal I get this error:

Uncaught TypeError: Cannot read property 'componentWillEnter' of undefined

I’m not having any trouble using React in other components. I’ve already deleted and reinstalled my node_modules folder. Is this a known issue? Any tips?

I've already reviewed the following resources and attempted to debug per their suggestions, to no avail:

https://gist.github.com/jimfb/4faa6cbfb1ef476bd105

#1457

https://groups.google.com/forum/#!topic/reactjs/sJaIoLSQCSQ

#4876

Issue 2:
I noticed that legacy attributes like align, cellpadding, cellspacing wasn't rendered by React (at least on the server side).

It is annoying for me since i was trying to convert our email templating system to use React in order to be able to display them in our frontend app.

The fact is that i'm unable to complete this task with React. It led to another question. How am i supposed to make React and WebComponents work together if custom element/attributes names are filtered by React rendering engine ?
Issue 1:
We have structured our files so that page specific code is in the pages folder. Here is an example:

pages

manage-users

__tests__

manage-users.test.js

index.js

components

ManageUsersPage.js

<other page specific components here>

The index.js file has the ManageUsersPage.js components as its default export. That is a regular next.js page component

This structure has worked fine for us except when we build. This hardcoded glob assumes that all js files under pages is a page: https://github.com/zeit/next.js/blob/canary/server/build/webpack.js#L50

Does it make sense to make this glob overridable or do we have to not use file based routing?

Issue 2:
Bug report

Fixed Sidebar Not working after route change.

I have implemented a fixed sidebar in my next app using react-sticky-box. The sticky sidebar is working perfectly fine when the page is reloaded from the browser's reload button but stops working once the page is changed clicking the next.js's Link tag.

System information

OS: macOS

Browser chrome

Version of Next.js : 9.0.6