WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I am pretty sure this is going to affect any install from a git remote with a ref that's not found in the origin. But I encountered it trying to install a PR, and haven't investigated further.

Instead of "remote reference not found in git repository", or some other helpful thing, it does this.

Current Behavior:

Pacote fails with a git folder issue.

$ npm i npm/pacote#pull/55
npm ERR! code 128
npm ERR! command failed
npm ERR! command git clone --mirror -q ssh://git@github.com/npm/pacote.git /Users/isaacs/.npm/_cacache/tmp/git-clone-00c3d7a2/.git
npm ERR! fatal: destination path '/Users/isaacs/.npm/_cacache/tmp/git-clone-00c3d7a2/.git' already exists and is not an empty directory.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/isaacs/.npm/_logs/2021-05-03T00_17_29_111Z-debug.log

Expected Behavior:

Report that pull/55 isn't a thing that exists in the npm/pacote repository.

Environment:

macOS, npm 7.11.2

My bet is that this is a bug in either pacote or @npmcli/git, but I haven't dug any further into it as yet.

Issue 2:
### Current Behavior:

Expected Behavior:

npm install with erroneous git version on a github dependency whines about cache "already exists"

Steps To Reproduce:

with a fresh npm package.json, add a dep for a non-existent branch, e.g."dependencies": { "shex-test": "github:shexSpec/shexTest#master" }

npm install --cache /tmp/brand-new-cache

Environment:

OS: Ubuntu 20.04

Error Message:

eric@touchy:/tmp/npmz/npm-user$ npm install --cache /tmp/brand-new-cache
npm ERR! code 128
npm ERR! command failed
npm ERR! command git clone --mirror -q ssh://git@github.com/shexSpec/shexTest.git /tmp/brand-new-cache/_cacache/tmp/git-clone-e421e02b/.git
npm ERR! fatal: destination path '/tmp/brand-new-cache/_cacache/tmp/git-clone-e421e02b/.git' already exists and is not an empty directory.

npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/brand-new-cache/_logs/2021-04-25T16_32_24_722Z-debug.log

The real prob had nothing to do with the cache, but simply that the master branch was renamed to main (which makes this a timely UI experience to improve).

Related issue:

If you change to an existent branch (e.g. main), npm i, change back, and npm i again, you see no error. The package-lock.json entry was changed to "shex-test": "github:shexSpec/shexTest#master" but the node_modules entry appeared to stay on main. While playing with this, i had to reset to square 1 with rm -rf node_modules/ package-lock.json /tmp/brand-new-cache/ to get around this overly agreeable behavior.
Issue 1:
Unable to enter Chinese on any terminal opened by Windows terminal

Windows terminal : Windows Terminal (Preview) Version: 0.6.2951.0

windows : Win10 Enterprise Edition version: 18362.449

Issue 2:
Description of the new feature/enhancement

It would be really nice to be able to rename tabs by just double-clicling them and setting new title in some kind of text-box. This name replaces original title and stays until tab closed or renamed again.

This feature is very useful when working with multiple similar tabs like many ssh connections to different servers or tailing multiple logs, etc. Quite often it's one-time sessions and there is no reason to make custom profile for them. Example - hackathon event when you work with a lot of terminal tabs but when it's finished - you never use it again.

For example i use this very feature in IntelliJ IDEs (PyCharm, PhpStorm, etc) all the time.
Issue 1:
As I am already including:

"node/node.d.ts": {
"commit": "e850b6ac0d59fee86dd7cb6a1be2caf6400bde14"
}

In my tsd.json file and angular also includes those, I get lots of error TS2300: Duplicate identifier ... errors.

Is there really no solution for this? If there is a solution, can someone point me to it because I cannot find something that would make it work, besides me not including these typings in my own tsd.json file.

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

[ x ] bug report
[ ] 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

ngc is creating the following code for app.component.ngfactory.ts

...
import * as import9 from '@angular/core/src/change_detection/change_detection';
import * as import10 from '@angular/router/src/router_outlet_map';
import * as import11 from '@angular/core/src/linker/component_factory_resolver';
import * as import12 from '@angular/core/src/metadata/view';
import * as import13 from '@angular/core/src/linker/component_factory_resolver';
import * as import14 from './model/navigation.service';
import * as import15 from '@angular/router/src/router';
...

Notice that import11 and import13 refer to the same file. This creates a naming conflict which in turn breaks dependency injection (No provider found for ComponentFactoryResolver$1) when used with rollup.js. Even if that weren't the case, this would unnecessarily increase the project's code size.

The original app.component.ts file looks like this:

import { Component } from '@angular/core';
import { RouterOutlet } from '@angular/router';
import { SelectorPageComponent } from './pages/selector.component';
import { NavigationService } from './model/navigation.service';

@Component({
selector: 'my-app',
directives: [RouterOutlet],
providers: [NavigationService],
template: '<router-outlet></router-outlet>',
precompile: [ SelectorPageComponent ]
})
export class AppComponent {}

NavigationService imports @angular/router, as does AppComponent. Given the order of the imports in the ngfactory file, this seems to be the source of the issue.

This may be related somehow to #10132, although ngc succeeds without any warnings so it's a different issue.

Expected/desired behavior

Regardless of the cause, ngc should never import the exact same thing twice.

Reproduction of the problem

I have not yet figured out how to reproduce this exact problem in a smaller project. Does anybody have insight as to what might cause this to happen? I am using @angular/compiler-cli (ngc) 0.4.1 and Angular 2.0.0-rc.4 with a fairly standard tsconfig.json file.

One odd thing is that "angularCompilerOptions": {"debug": true} doesn't seem to do anything. I'd hoped it would shed insight on where imported files are coming from.

Please tell us about your environment:

Angular version: 2.0.0-rc.4

Browser: all

Language: TypeScript 1.8.2
Issue 1:
Electron version: 1.4.4

Operating system: Windows 10

Scenario:

I want to paste a copied image in my Electron app. But when I copy an image in Windows Explorer (png or jpg) and try to retrieve it from Clipboard, Clipboard.readImage() returns an empty NativeImage Object.

Based on the docs, I assumed it would work with all operating systems:

http://electron.atom.io/docs/api/clipboard/#clipboardreadimagetype

The same code is working fine in macOS. But the majority of our customers are using Windows.

Issue 2:
i want to get image file from clipboard.

when right-click an image on a web page and copy it, i can get the image file from both browser's onpaste event and clipboard module that electron provided.

when it came to files(images) in finder, cmd+c copy it, browser's onpaste event can only give you a preview icon of this file.

like this:

i hope electron can give me more power to access clipboard data. but after i look through the api doc of clipboard and native-image, tryed in devtool of electron, the result still the same, i can only get the preview icon of the image.

how can i access to image data copyed from finder, not from web page?

here is some code, paste those code to devtool of electron, copy an image file in finder, back to devtool, press enter.

var clipboard = require('clipboard');
var img = clipboard.readImage('png');
document.body.innerHTML += '<img src="' +img.toDataUrl()+ '">';
Issue 1:
[Enter steps to reproduce below:]

...

...

Atom Version: 0.169.0

System: Mac OS X 10.10.1

Thrown From: Atom Core

Stack Trace

Uncaught Error: Atom can only handle files < 2MB for now.

At /Applications/Atom.app/Contents/Resources/app/src/project.js:355

Error: Atom can only handle files < 2MB for now.
at Project.module.exports.Project.buildBuffer (/Applications/Atom.app/Contents/Resources/app/src/project.js:355:15)
at Project.module.exports.Project.bufferForPath (/Applications/Atom.app/Contents/Resources/app/src/project.js:332:63)
at Project.module.exports.Project.open (/Applications/Atom.app/Contents/Resources/app/src/project.js:286:19)
at Workspace.module.exports.Workspace.openUriInPane (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:485:29)
at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:412:19)
at Ipc.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:45:32)
at Ipc.emit (events.js:110:17)
at process.<anonymous> (/Applications/Atom.app/Contents/Resources/atom/renderer/api/lib/ipc.js:22:29)
at process.emit (events.js:118:17)

Commands

-0:00.0 application:open (atom-text-editor.editor.is-focused)

Config

{
"core": {
"disabledPackages": [
"autocomplete"
]
},
"editor": {
"fontSize": 12,
"softWrap": true,
"invisibles": {}
}
}

Installed Packages

# User
atom-beautify, v0.21.2
autoclose-html, v0.13.0
autocomplete-paths, v0.9.1
autocomplete-plus, v1.1.0
dart-tools, v0.8.5
editorconfig, v0.3.0
html-id-class-snippets, v1.4.1
jsformat, v0.7.18
language-clojure, v0.10.0
language-dart, v0.1.1
linter-clojure, v0.0.4
minimap, v3.5.6
react, v0.8.8
recent-files, v0.3.0
remote-edit, v1.6.3
terminal-status, v1.3.5

# Dev
No dev packages

Issue 2:
Uncaught Error: Atom can only handle files < 2MB for now.

Atom Version: 0.153.0

System: linux 3.13.0-40-generic

Thrown From: tree-view package
Issue 1:
This sample illustrates what I'm talking about:

// Run this with:
// deno run --allow-run ./elevation.ts

if (Deno.args.includes('network')) {
console.log('Thanks for the elevated permissions sucker!')
const result = await fetch('https://example.com');

console.log(result)
} else {
const p = Deno.run({
cmd: ['deno', 'run', '--allow-net', './elevation.ts', 'network']
})

// await its completion
const code = await p.status()
console.log(code)
}

Unless Deno does some advanced cascading of ACL around further deno's spawned within its process (which it seems like it should do here) this is relaying a false sense of security to the user of the deno program.

If I am a user, and I run unknown code via deno, with the assumption of deno's security protecting me (which is what the marketing blurbs seem to imply), I wouldn't expect that an --allow-run flag is giving full unfettered access to everything.

As such, the allow-run flag is very misleading and should not be a distinct flag - if people need to run subprocesses, it should only be done with the allow-all flag.

Issue 2:
When you execute a subprocess there's no guarantees of what it can do - all security bets are off. --allow-run masks this and is an extra command line flag. Therefore I suggest removing it entirely and requiring users to supply --allow-all.
Issue 1:
Fresh clone of repo.

commit 1d53bab

% configure --disable-debug --disable-optimize --enable-clang
% time make -j8
...
compile_and_link: x86_64-apple-darwin/stage1/lib/rustc/x86_64-apple-darwin/lib/libcore.dylib
rust: task 7fa031d00000 ran out of stack
compile_and_link: x86_64-apple-darwin/stage1/lib/rustc/x86_64-apple-darwin/lib/libstd.dylib
cp: x86_64-apple-darwin/stage2/lib/libcore.dylib
cp: x86_64-apple-darwin/stage1/lib/rustc/x86_64-apple-darwin/lib/libcore-*.dylib: No such file or directory
make: *** [x86_64-apple-darwin/stage2/lib/libcore.dylib] Error 1
make: *** Waiting for unfinished jobs....
rust: task 7fa058c0ad10 ran out of stack

real 4m54.362s
user 22m36.394s
sys 1m4.580s

This may be a duplicate of another issue, for example perhaps #6049. I'm honestly not sure.

At this point I have bisected the problem down to:

4a24f10 is the first bad commit

commit 4a24f10

Author: Huon Wilson dbau.pp+github@gmail.com

Date: Wed Apr 24 22:29:19 2013 +1000

(But it is possible that Huon's code is just exposing a latent bug in rustc, rather than actually having something fundamentally wrong with it itself.) I plan to investigate backing out Huon's change to see if that makes the problem go away, just so I can actually bootstrap a compiler and do more investigation.

Issue 2:
I encountered an assertion failure in rustc 0.6

fn main() {
let x = Some(3);
let y = 0;

match(x) {
None => println("None"),
_ if y == 0 => println("y is zero"),
Some(n) => println(fmt!("Some(%d)", n)),
}
}

Above is a simple test code to reproduce the bug

(Yes it is a silly code which can be rephrased into match nested in if)

kimhyunkang$ RUST_LOG=rustc=1,::rt::backtrace rustc test.rs
rust: task failed at 'assertion failed: (m.len() > 0u || chk.is_some())', /Users/kimhyunkang/usr/pkgs/rust-0.6/src/librustc/middle/trans/_match.rs:1262
error: internal compiler error: unexpected failure
note: the compiler hit an unexpected failure path. this is a bug
note: try running with RUST_LOG=rustc=1,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues
rust: task failed at 'explicit failure', /Users/kimhyunkang/usr/pkgs/rust-0.6/src/librustc/rustc.rc:357
rust: domain main @0x7f8789819410 root task failed
Issue 1:
Challenge Waypoint: Passing Values to Functions with Arguments has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.

This is the error throwing "​RangeError: Maximum call stack size exceeded"

My code:

// Example
function ourFunction(a, b) {
console.log(a - b);
}
ourFunction(10, 5); // Outputs 5

// Only change code below this line.
var myFunction = function(param1, param2){
console.log(param1 + param2);
};
myFunction(20, 20);

Issue 2:
Challenge Waypoint: Passing Values to Functions with Arguments has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.

Running tests outputs RangeError: Maximum call stack size exceeded and no tests pass.

My code:

// Example
function ourFunction(a, b) {
console.log(a - b);
}
ourFunction(10, 5); // Outputs 5

// Only change code below this line.

function myFunction(c, d){
console.log(c + d);
}
myFunction(2, 3);
Issue 1:
Hello,

after changing with django + celery to python 3.6.7 I get a DeprecationWarning for

../celery/utils/imports.py:

kind regards Jens

[x ] I have included the output of celery -A proj report in the issue.

(if you are not able to do this, then at least specify the Celery

version affected).

I have included all related issues and possible duplicate issues in this issue.

I have included the contents of pip freeze in the issue.

I have verified that the issue exists against the master branch of Celery.

I have tried reproducing the issue on more than one message broker and/or result backend.

I have tried reproducing the issue on more than one workers pool.

I have tried reproducing the issue with retries, ETA/Countdown & rate limits disabled.

problem is not visible with pyhton3.5.x

same output for celery 4.3.rc2 or 4.2.1

Expected Behavior

no Deprecation Warning for python 3.6.7 like before in python 3.5

Actual Behavior

Output of /venvdir/dev367/bin/python -Wd manage.py runserver 0.0.0.0:8000 :

/venvdir/dev367/lib/python3.6/site-packages/celery/utils/imports.py:5: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp as _imp

/venvdir/dev367/bin/celery -A client report software -> celery:4.3.0rc2 (rhubarb) kombu:4.4.0 py:3.6.7 billiard:3.6.0.0 py-amqp:2.4.2 platform -> system:Linux arch:64bit, ELF kernel version:4.14.92-boot2docker imp:CPython loader -> celery.loaders.app.AppLoader settings -> transport:amqp results:django-db

Issue 2:
Checklist

I have checked the issues list

for similar or identical feature requests.

I have checked the pull requests list

for existing proposed implementations of this feature.

I have checked the commit log

to find out if the if the same feature was already implemented in the

master branch.

I have included all related issues and possible duplicate issues

in this issue (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Brief Summary

With prefork, there are a couple parameters --max-tasks-per-child and --max-memory-per-child that can help control memory usage in case of memory leaks. Those parameters aren't compatible with gevent. It would be awesome if there was a way to handle memory leaks with eventlets, where a restart or cleanup can be triggered

Design

Architectural Considerations

None

Proposed Behavior

Proposed UI/UX

Diagrams

N/A

Alternatives

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

Expected Behavior

When exit a dialog, the dialog paper should disappear with the passed transition (zooms out if the transition is Grow)

Current Behavior

The dialog paper disappears immediately, but the backdrop disappears normally.

Steps to Reproduce (for bugs)

Open the dialog with Grow transition

Close the opened dialog

https://codesandbox.io/s/k01k060n73

Your Environment

Tech
Version

Material-UI
1.0.0-beta.20

React
16.0.0

browser
64.0.3265.0 (Official Build) canary (64-bit)

Issue 2:
When the button has focus and you press ENTER to execute the action, the handler is actually called twice. If I press the button with the mouse the handler is only called one, which is the expected behaviour. This is not specific to FlatButton, as I've seen the same behaviour for IconButton as well.

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

Expected Behavior

onClick handler should only be called once.

Current Behavior

onClick handler is called twice.

Steps to Reproduce (for bugs)

Check this url: https://codesandbox.io/s/20kq3pow9p

Bring up Chrome dev tools to be able to see the console.log

Click the text "hello" to move focus to that window.

On the keyboard hit tab to set focus to the "Click me" button

Hit ENTER on the keyboard

Watch the console and see that "clicked" was printed twice.

Also note that if I in the handler uncomment e.preventDefault() it's actually only printed once.

Context

Trying to enable navigation by using keyboard only (or most of the time).

Your Environment

OSX

Tech
Version

Material-UI
0.19.2

React
15.5.4

browser
Chrome
Issue 1:
test/repl.jl was added in #6955, most of the file is @unix_only at the moment except a few lines at the very end. These lines are freezing for me on Windows, but they're using process commands that you'd think should work.

| | |_| | | | (_| | | Version 0.3.0-prerelease+3381 (2014-06-02 13:19 UTC)
_/ |\__'_|_|_|\__'_| | Commit ddf4197* (0 days old master)
|__/ | x86_64-w64-mingw32

julia> exename = joinpath(JULIA_HOME, "julia")
"D:\\code\\msys64\\home\\Tony\\julia\\usr\\bin\\julia"

julia> outs, ins, p = readandwrite(`$exename -f --quiet`)
(Pipe(active, 0 bytes waiting),Pipe(open, 0 bytes waiting),Process(`'D:\code\msy
s64\home\Tony\julia\usr\bin\julia' -f --quiet`, ProcessRunning))

julia> write(ins,"1\nquit()\n")
9

julia> ins
Pipe(open, 0 bytes waiting)

julia> outs
Pipe(active, 2 bytes waiting)

julia> readall(outs)

This last command never exits, I have to manually kill the julia process(es).

exename = joinpath(JULIA_HOME, "julia")
outs, ins, p = readandwrite(`$exename -f --quiet`)
write(ins,"1\nquit()\n")
readall(outs)

Issue 2:
For some reason jl_is_pty (or more precisely the pNtQueryInformationFile in uv_get socketname) blocks until another character is received on stdin.
Issue 1:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): etcd watcher

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug report

Kubernetes version (use kubectl version): HEAD / commit 8b5264e

Environment:

Cloud provider or hardware configuration: local VM

OS (e.g. from /etc/os-release): Fedora 24

Kernel (e.g. uname -a): Linux localhost.localdomain 4.7.7-200.fc24.x86_64 #1 SMP Sat Oct 8 00:21:59 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Install tools: N/A

Others: N/A

What happened:

If you do a watch from resource version "0" using etcd_watcher.go (the etcd v2 client code), it initially performs a get of the key in question and returns Added or Modified events, based on a comparison of each node's createdIndex and modifiedIndex. This works all the time.

If you do a watch from resource version "0" using watcher.go (the etcd v3 client code), it attempts to get kv.modifiedIndex - 1 for each kv returned, in an attempt to provide both the previous and current versions of each kv/object. This works as long as kv.modifiedIndex - 1 has not been compacted. If compaction has occurred, the initial sync() will fail, and it's not possible to watch from "0"' for this particular key.

What you expected to happen:

Either:

The v3 watcher should not change the behavior from the v2 watcher; namely, it should not attempt to get the previous revision of each object and instead just return the current version as a watch.Added event

We agree that it's ok to change the behavior, and in the event that the database has been compacted and the previous revision of an object cannot be retrieved, that object is sent as a watch.Added event instead of watch.Modified.

How to reproduce it (as minimally and precisely as possible): I'm working on a unit test and fix.

Anything else do we need to know:

cc @wojtek-t @hongchaodeng @xiang90 @smarterclayton @liggitt @deads2k @derekwaynecarr @sttts

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Kubernetes version (use kubectl version):

Environment:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else do we need to know: