WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
[Enter steps to reproduce below:]

...

...

Atom Version: 0.169.0

System: Mac OS X 10.9.5

Thrown From: Atom Core

Stack Trace

Uncaught Error: connect ECONNREFUSED

At stream.js:94

Error: connect ECONNREFUSED
at exports._errnoException (util.js:746:11)
at Object.afterConnect [as oncomplete] (net.js:990:19)

Commands

4x -0:06.9 window:decrease-font-size (atom-text-editor.editor)
-0:00.0 settings-view:open (atom-text-editor.editor)

Config

{
"core": {
"themes": [
"atom-dark-ui",
"atom-dark-syntax"
]
},
"editor": {
"fontSize": 12,
"invisibles": {}
}
}

Installed Packages

# User
No installed packages

# Dev
No dev packages

Issue 2:
[Enter steps to reproduce below:]

...

...

Atom Version: 0.169.0

System: Mac OS X 10.9.5

Thrown From: Atom Core

Stack Trace

Uncaught Error: connect ECONNREFUSED

At stream.js:94

Error: connect ECONNREFUSED
at exports._errnoException (util.js:746:11)
at Object.afterConnect [as oncomplete] (net.js:990:19)

Commands

4x -0:06.9 window:decrease-font-size (atom-text-editor.editor)
-0:00.0 settings-view:open (atom-text-editor.editor)

Config

{
"core": {
"themes": [
"atom-dark-ui",
"atom-dark-syntax"
]
},
"editor": {
"fontSize": 12,
"invisibles": {}
}
}

Installed Packages

# User
No installed packages

# Dev
No dev packages
Issue 1:
There are many instances where one concretely needs a statically linked executable (e.g. to avoid having to distribute a pile of Rust dynamic libraries, making deployment much simpler).

The compiler currently offers no way to request that a compiled artefact is always statically linked against Rust crates (the only option is -C prefer-dynamic which isn't really a guarantee either). Since there's no way to force these things, working out why the static linking defaulting failed is very hard, especially with a non-trivial number of dependencies (since the error is almost certainly one of those dependencies coming only in .so format).

If the compiler provided say, -C statically-linked, then a user can request that something is only statically linked and receive errors about exactly what is stopping this from happening, e.g. crate syntax can only be found as a dynamic library. Without this, the user has to search through all dependencies to find out what is breaking things.

(Case study: I was working through a problem like this with @emk on IRC. After much discussion and ldd wrangling, we eventually tracked it down to a library which defines a procedural macro internally along with the rest of the functionality, i.e. introducing a dependency on libsyntax. It would be much easier if we can get the compiler to tell us this straight away.)

Issue 2:
Now that #9658 has landed, libstd is buildable with both -Z debug-info and -Z extra-debug-info. It might be time to graduate these flags out of the experimental -Z zone.
Issue 1:
x = [
1 2 3 4 5 6;
2 3 4 5 6 7;
]
const y = x

let
local a = x
@time for i in 1:10^4 reshape(a, 12) end
end
0.002322 seconds (20.00 k allocations: 781.250 KB)

let
local a = y
@time for i in 1:10^4 reshape(a, 12) end
end
0.000344 seconds (10.00 k allocations: 625.000 KB)

It seems the type of a isn't inferred.

Issue 2:
_ _ _(_)_ |
(_) | (_) (_) | A fresh approach to technical computing
_ _ _| |_ __ _ |
| | | | | | |/ _` | | Version 0.0.0-prerelease
| | |_| | | | (_| | | Commit 335d1ef401 (2012-03-04 23:47:29)
_/ |\__'_|_|_|\__'_| |
|__/ |

julia> x = 5
5

julia> typeof(x)
Int64

julia> typeof([i | i = 1:5])
Array{Int64,1}

So far, so good.

julia> typeof([i | i = 1:x])
Array{Any,1}

Wat.

(with apologies to https://www.destroyallsoftware.com/talks/wat)
Issue 1:
Hi everyone,

I need to have some help with an annoying thing.

I have an modal popup which has vertical scrollsbar inside. When scrolling inside the modal sometimes the background scrolls instead.

I have tried to add

body .modal-open {

position:relative;

overflow: hidden;

}

which works fine on most of the browsers, but Safari for my iPhone still scrolls!

Please help me find how to solve this!

Regards Kristian

Issue 2:
When viewing a modal on iPad, attempts to scroll within the content of the modal instead triggers scrolling of the entire page in the background.

Tested on iPad 2 iOS 5.1 Mobile Safari while viewing Bootstrap Documentation and Examples http://twitter.github.com/bootstrap/javascript.html#modals
Issue 1:
I am using following code in my component, but handleChange event is not getting fired as i try to select one of the radio buttons.

I have tried to update my react and react-dom version from 16.0.0 to 16.0.2.

/* eslint-disable flowtype/require-valid-file-annotation */

import React from 'react';
import PropTypes from 'prop-types';
import { withStyles } from 'material-ui/styles';
import Radio, { RadioGroup } from 'material-ui/Radio';
import { FormLabel, FormControl, FormControlLabel, FormHelperText } from 'material-ui/Form';

const styles = theme => ({
root: {
display: 'flex',
},
formControl: {
margin: theme.spacing.unit * 3,
},
group: {
margin: `${theme.spacing.unit}px 0`,
},
});

class RadioButtonsGroup extends React.Component {
state = {
value: '',
};

handleChange = (event, value) => {
debugger;
this.setState({ value });
};

render() {
const { classes } = this.props;

return (
<div className={classes.root}>
<FormControl component="fieldset" required className={classes.formControl}>
<FormLabel component="legend">Gender</FormLabel>
<RadioGroup
aria-label="gender"
name="gender1"
className={classes.group}
value={this.state.value}
onChange={this.handleChange}
>
<FormControlLabel value="male" control={<Radio />} label="male" />
<FormControlLabel value="female" control={<Radio />} label="female" />
<FormControlLabel value="other" control={<Radio />} label="other" />
<FormControlLabel value="disabled" disabled control={<Radio />} label="Disabled" />
</RadioGroup>
</FormControl>

</div>
);
}
}

RadioButtonsGroup.propTypes = {
classes: PropTypes.object.isRequired,
};

export default withStyles(styles)(RadioButtonsGroup);

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

Expected Behavior

handleChange function should execute when a user tries to click on one of the radio buttons.

Current Behavior

Nothing happens if a user tries to select a radio button and no input is shown to user

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.21

React
16.2.0

browser
Chrome-62.0.3202.94

etc

Issue 2:
Issue : in mobile where there is possible to scroll (in search result) the keyboard not disappear when the user scroll (there isn't blur on the input) and therefore it give bed user experience.

Expected Behavior

On mobile devices if it's possible to scroll on search result, when the user scroll the keyboard should disappear.

Current Behavior

The keyboard not disappear

Steps to Reproduce (for bugs)

enter with mobile devices

scroll on menu result

Context

The bug cause bed experience when using autocomplete component on mobile devices

Your Environment

Tech
Version

Material-UI
v1-beta (all)

React
15.5.4

browser
all
Issue 1:
Current Behavior:

If the working directory's name differs from the name of the npm package it contains, then the generated package-lock.json has a ["packages"][""]["name"] property in violation of the npm v7 spec for the package-lock.json file per the docs at https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json

for example:

{
"name": "impact-api",
"version": "2.27.0",
"lockfileVersion": 2,
"requires": true,
"packages": {
"": {
"name": "impact-api",
"version": "2.27.0",
"license": "UNLICENSED",
"dependencies": {
...

Expected Behavior:

The generated package-lock.json file should not have a "name" property under ["packages"][""]

for example:

{
"name": "impact-api",
"version": "2.27.0",
"lockfileVersion": 2,
"requires": true,
"packages": {
"": {
"version": "2.27.0",
"license": "UNLICENSED",
"dependencies": {
...

Steps To Reproduce:

clone an npm project/package e.g. from GitHub into a filesystem directory whose name differs from the name of the npm package

remove package-lock.json and the ./node_modules directory if they exist

Run npm i

The generated package-lock.json contains an errant ["packages"][""]["name"] property in violation of the npm v7 spec for the package-lock.json file per the docs at https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json

Environment:

OS: macOS Big Sur Version 11.1

Node: 14.16.0

npm: 7.6.0

Issue 2:
Current Behavior:

package-lock.json changes depending on name of local copy of git repo, e.g. if i have two copies of the same repo locally one which matches the name in package.json and one which doesn't i get two different package-lock files, one specifies the name of the package in the inner packages list and one doesn't.

Expected Behavior:

package-lock.json should be independent of top level directory name, when working in a team there shouldn't be unnecessary changes to package-lock file due to a team member having a different local name of their git repository.

Steps To Reproduce:

clone a repository twice one in the default named directory and one into a name that differs from the repo name.

run npm install

two different package-lock files will be generated.

Environment:

OS: Ubuntu 20.04

Node: 15.3.0

npm: 7.0.14
Issue 1:
I notice that it exists a country form type that display a list of countries using the Intl bundle.

This form type is very usefull, but there is no easy way to restrict the countries available. For example if I want the user to select a country into a predefined list, it is currently not possible (except creating a custom choice form type).

What would be wonderfull is that we can configure a list of predefined countries by sending an array containing the countries ISO code (array('uk', 'fr', 'it', 'es') for example) And the component will generate the list translating those ISO code into user language country name.

NOTE: This could also be applied to language form type.

Issue 2:
It would be nice to have an option named for instance allowed_locales, that when set, would cause the widget to display only locales that appear in it, and would throw an exception if one of them can't be found in Intl::getLocaleBundle()->getLocaleNames() keys. If this is something that you think would be useful, I can write the code and make a PR.
Issue 1:
Vue.js version

1.0.26

Reproduction Link

https://jsfiddle.net/gregmi/yLqnv2ex/

Steps to reproduce

run and check the output, it says: "params.myAttr: undefined"

comment out the line 13 (props)

run again and check the output, it says: "params.myAttr: content"

What is Expected?

It should say: "myAttr: content"

What is actually happening?

When there is a tag attribute that is also a vue property and vue directive parameter at the same time, it is not reachable from within a vue directive (this.params.myAttr), but one can get it from vm (this.vm.myAttr).

It seem like a race condition of sorts (in time when vm properties are created) between vue component and vue directive.

Issue 2:
Version

2.6.6

Reproduction link

https://jsfiddle.net/xayduwf0/

Steps to reproduce

open the link and run

What is expected?

there should no html in the result window

What is actually happening?

the result shows all the rendered html

I'm not sure it is by design or a bug……

The scene I can think of the use of is, if someone use Vue.js in an progressive web page, they maybe need to control the app by themself, like call $destroy by them self, now if they want to clean the document, they need to execute

app.$destroy();
app.$el.parentNode.removeChild(app.$el);
Issue 1:
TypeScript Version:

1.9.0-dev.20160521-1.0

Code

Install node d.ts file:

npm install --save-dev @types/node@4.0.21-alpha

index.ts:

console.log('hello');

tsconfig.json:

{
"compilerOptions": {
"noImplicitAny": true,
"strictNullChecks": true,
"moduleResolution": "node",
"pretty": true,
"allowSyntheticDefaultImports": true,
"skipDefaultLibCheck": true,
// output options
"outDir": "dist/",
"rootDir": "./src",
"module": "commonjs",
"target": "es6",
"declaration": true,
"sourceMap": true,
"inlineSources": true
},
"files": [
"src/index.ts",
"node_modules/@types/node/index.d.ts"
]
}

Expected behavior:

the build should work

Actual behavior:

tsc errors with:

11:24:25 PM - File change detected. Starting incremental compilation...

13 stack?: string;
~~~~~

node_modules/@types/node/index.d.ts(13,5): error TS2300: Duplicate identifier 'stack'.

883 stack?: string;
~~~~~

node_modules/typescript/lib/lib.es6.d.ts(883,5): error TS2300: Duplicate identifier 'stack'.

// @RyanCavanaugh

Issue 2:
TypeScript Version:

nightly with "node.d.ts" from typings

We recently add thisin to es5.d.ts

Expected behavior:

No error

Actual behavior:

Duplicate Identifier with the same property defined in "node.d.ts"
Issue 1:
Spotted by @teropa and confirmed on my side in the ng2 directives for Bootstrap project (see: ng-bootstrap/ng-bootstrap#115):

I'm getting errors about platform directives like ng-for when using TestComponentBuilder. Seems like they're not "ambient" in the unit tests like they are during normal execution. I can fix it by including CORE_DIRECTIVES in the component, but that seems backward. Any ideas how to make them available?

Issue 2:
GET http://localhost:8080/undefined 404 (Not Found)

<img [src]="data.avatar_url" width="100" height="100"/>

this.data = {};
http.get('https://api.github.com/users/danicomas').toRx().map(res => res.json()).subscribe(response => this.data = response);
Issue 1:
In some cases, you'd like to set up your testing module the same as a larger module you're exporting, but want to mock out some declarations. Currently there is no way to remove a declaration though, so you'd have to make a whole new module and duplicate your list.

e.g., now

// in lib
@NgModule({
declarations: [A, B, C, D, E]
})
class MyLibModule {};

// in test for E, we want to mock out D
TestBed.configureTestingModule({
declarations: [A, B, C, MockD, E]
});

Instead it would be nice to be able to do something like:

// in test for E
TestBed.configureTestingModule({
imports: [MyLibModule],
remove: [D],
declarations: [MockD]
});

Issue 2:
WARNING in ./~/@angular/core/src/linker/system_js_ng_module_factory_loader.js
87:15-102 Critical dependency: the request of a dependency is an expression
at ImportContextDependency.getWarnings (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-web-api/node_modules/webpack/lib/dependencies/ImportContextDependency.js:28:4)
at Compilation.reportDependencyErrorsAndWarnings (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-web-api/node_modules/webpack/lib/Compilation.js:663:24)
at Compilation.finish (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-web-api/node_modules/webpack/lib/Compilation.js:526:9)
at /home/patrikx3/Projects/patrikx3/corifeus/corifeus-web-api/node_modules/webpack/lib/Compiler.js:472:16
at /home/patrikx3/Projects/patrikx3/corifeus/corifeus-web-api/node_modules/tapable/lib/Tapable.js:225:11
at /home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/html-webpack-plugin/index.js:60:9
at tryCatcher (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/promise.js:510:31)
at Promise._settlePromise (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/promise.js:567:18)
at Promise._settlePromise0 (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/promise.js:612:10)
at Promise._settlePromises (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/promise.js:691:18)
at Async._drainQueue (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/home/patrikx3/Projects/patrikx3/corifeus/corifeus-builder/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:666:20)
at tryOnImmediate (timers.js:639:5)
at processImmediate [as _immediateCallback] (timers.js:611:5)
Issue 1:
Bug report

Bug summary

Interactive code (Jupyter Notebook using %matplotlib notebook) worked up to v3.2.x, stops working for v3.3.x. Tested on Firefox and Chrome.

Code for reproduction

import ipywidgets as widgets
import matplotlib.pyplot as plt
from IPython.display import display

%matplotlib notebook

class MWE:

def __init__(self):
self.fig, self.ax = plt.subplots(1, 1)
self.ax.set_xlim([-5, 105])
self.ax.set_ylim([-500, 10500])
self.create_widget()
self.draw()

def create_widget(self):
value = widgets.interactive(
self.update_value,
value=widgets.IntSlider(value=50, min=0, max=100))
display(value)

def draw(self):
self.ax.plot(self.value, self.value**2, 'o')

def update_value(self, value):
self.value = value
self.draw()

MWE()

Actual outcome

Just an empty figure, moving the slider has no effect, no warning thrown either.

Expected outcome

More and more dots should be printed when moving the slider.

Matplotlib version

Operating system: Ubuntu 20.04

Matplotlib version: <3.2.x works, >=3.3.2 does not.

Matplotlib backend: nbAgg

Python version: 3.8.6

Jupyter version (if applicable): 1.0.0

Other libraries: widgets v7.5.1

Installed with mamba from conda-forge.

It might be related to #18481, but it happens for Firefox and Chrome on my machine. Also, the mentioned workaround (#18481 (comment)) does not help.

Issue 2:
Bug report

Bug summary

Using ipywidgets.interact to update a figure works as expected in matplotlib<=3.3.1, but fails in matplotlib==3.3.2.

I don't think this is an ipywidgets issue since downgrading matplotlib fixes this issue.

Code for reproduction

In[1]:

%matplotlib notebook
import matplotlib as mpl
import matplotlib.pyplot as plt
import ipywidgets as ipyw
"works if %s <= 3.3.1" % mpl.__version__

In[2]:

fig = plt.figure()
@ipyw.interact(m=ipyw.FloatSlider(value=1, min=-10, max=10, step=0.01))
def update(m):
plt.figure(fig.number, clear=True)
plt.plot([m * x for x in range(-9, 10)])

Followed by moving the slider.

Actual outcome

when moving the slider, the figure does not update

a second figure is sometimes created instead

the second figure is usually blank, but sometimes updates instead

Expected outcome

the original figure updates as it does in matplotlib==3.3.1

Matplotlib version

Operating system: Ubuntu

Matplotlib version: 3.3.2 vs 3.3.1

Matplotlib backend (print(matplotlib.get_backend())): nbAgg

Python version: 3.7.8

Jupyter version (if applicable): jupyter-core==4.6.3

Other libraries: ipywidgets==7.5.1

Installation source: conda channel conda-forge
Issue 1:
Description of the new feature/enhancement

Terminal seems not to play well with Power Toys, that is, the Shift + Move Window doesn't activate Power Toys Fancy Zones

Proposed technical implementation details (optional)

Implement move Terminal Window to Fancy Zone [Shift + Left Cursor on Window Bar]

Issue 2:
Description of the new feature/enhancement

Over time I written many Powershell scripts and modules to manage many stuff (either for personal and for work) I use some modules for manage my dev environment or my home router, or move, rename, delete personal fotos, ect.

So I'm used to have a Powershell session start when I log-in.

Now I want to move to Windows Terminal and so I would like to have it to start when I log-in

Proposed technical implementation details (optional)

The UWP SDK expose a way to configure a packaged app to start when a user log-in by adding the windows.startupTask extention to the manifest
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version (if applicable): windows terminal (Preview) 0.2.1715.0

Any other software?

Steps to reproduce

Create a Ubuntu 18 tab

type $ or any sign that can be created with AltGr

Expected behavior

we must see $ sign with AltGr+4

Actual behavior

nothing happens

Issue 2:
Your Windows build number:

10.0.18362.86

What you're doing and what's happening:

Trying to enter the @ sign on a Swedish keyboard in a PowerShell console using Alt Gr + 2.

See animated gif:

What's wrong / what should be happening instead:

Windows terminal shows digit-argument instead of outputting the @ sign as expected.

It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓
Issue 1:
Apache Airflow version

2.3.2 (latest released)

What happened

I accidentally created two dags with the same name.

No errors were given.

Code-tab in web-ui showed one of the versions.

Running the task actually executed the second version.

What you think should happen instead

One, or both DAGs should be rejected and pop up a dag import error in the UI

Starting the dag should not be possible.

How to reproduce

Create two dags with same name.

Start dag

Operating System

Debian GNU/Linux 11 (bullseye)

Versions of Apache Airflow Providers

apache-airflow-providers-celery==3.0.0

apache-airflow-providers-cncf-kubernetes==4.0.2

apache-airflow-providers-docker==3.0.0

apache-airflow-providers-ftp==2.1.2

apache-airflow-providers-http==2.1.2

apache-airflow-providers-imap==2.2.3

apache-airflow-providers-postgres==5.0.0

apache-airflow-providers-sqlite==2.1.3

Deployment

Other Docker-based deployment

Deployment details

No response

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct

Issue 2:
airflow/airflow/plugins_manager.py

Lines 291 to 292
in
ffb1fca

load_plugins_from_plugin_directory()

load_entrypoint_plugins()

Currently, entrypoint plugins are loaded after plugins directory plugins. If there's not a specific reason for this ordering, I think these should be reversed.

For example, if I have a custom operator MyOperator that I want to derive from another developer's custom operator TheirOperator, and that operator is part of a package that uses the Airflow plugins entrypoint, I would probably have a my_operator.py file that looks like this:

from airflow.operators.their_plugin import TheirOperator

class MyOperator(TheirOperator):
...
...

As it stands, since MyOperator is loaded first, this will fail with ModuleNotFoundError on their_package.plugins, making it difficult to derive operators from other packages.
Issue 1:
java.util.NoSuchElementException
at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:350)
at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:376)
at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:374)
at com.bumptech.glide.util.LruCache.trimToSize(LruCache.java:157)
at com.bumptech.glide.util.LruCache.clearMemory(LruCache.java:146)
at com.bumptech.glide.Glide.clearMemory(Glide.java:370)
at com.bumptech.glide.RequestManager.onLowMemory(RequestManager.java:95)
at com.bumptech.glide.manager.SupportRequestManagerFragment.onLowMemory(SupportRequestManagerFragment.java:156)

Issue occurs in Glide version 3.6.1

Issue 2:
Our crash monitoring facility had identified the above exception. It has been reported using Glide 3.5.2 and 3.5.0. It usually occurs in Android 4 devices, though we have reports up to 5.1. We're not able to reproduce it in our testing. While it's not a frequent report, we have seen 300+ reports in the last 30 days.

It looks like it may be the same or related to #266. Here's the stack trace in our case:

java.util.LinkedHashMap$LinkedHashIterator.nextEntry (LinkedHashMap.java:350)
java.util.LinkedHashMap$EntryIterator.next (LinkedHashMap.java:374)
com.bumptech.glide.util.LruCache.trimToSize (LruCache.java:157)
com.bumptech.glide.util.LruCache.clearMemory (LruCache.java:146)
com.bumptech.glide.Glide.clearMemory (Glide.java:372)
com.bumptech.glide.RequestManager.onLowMemory (RequestManager.java:92)
com.bumptech.glide.manager.SupportRequestManagerFragment.onLowMemory (SupportRequestManagerFragment.java:75)
android.support.v4.app.Fragment.performLowMemory (Fragment.java:1851)
dalvik.system.NativeStart.main (NativeStart.java)