WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Open a workspace on a removable or network-attached medium

Close Atom

Disconnect the medium

Open Atom

Experience an error while trying to open the workspace. Of course, it shouldn't open. But it shouldn't throw an error either; just ask me to make/open a new workspace.

Atom Version: 1.0.0

System: Mac OS X 10.10.3

Thrown From: Atom Core

Stack Trace

Uncaught Error: EIO: i/o error, open '/Users/sean/remote/workspace-crystal/---hidden-package-name---/WebContent/WEB-INF'

At /Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:466

Error: EIO: i/o error, open '/Users/sean/remote/workspace-crystal/---hidden-package-name---/WebContent/WEB-INF'
at Error (native)
at Object.fs.openSync (fs.js:544:18)
at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:118:20)
at Project.module.exports.Project.open (/Applications/Atom.app/Contents/Resources/app.asar/src/project.js:371:27)
at Workspace.module.exports.Workspace.openURIInPane (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:449:31)
at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:375:19)
at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:46:25)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:169:7)

Commands

Config

{}

Installed Packages

# User
No installed packages

# Dev
No dev packages

Issue 2:
To Reproduce:

Open a file from a network share, e.g. \MyServer\Logfiles\error.log then close Atom.

Open Atom again when the network share is no longer present, e.g. on a different network at home.

Atom Version: 0.208.0

System: Microsoft Windows 10 Pro Insider Preview

Thrown From: Atom Core

Stack Trace

Uncaught Error: UNKNOWN: unknown error, open '\cpc-23949-001\LogFiles'

At C:\Users\dw\AppData\Local\atom\app-0.208.0\resources\app.asar\src\workspace.js:458

Error: UNKNOWN: unknown error, open '\\cpc-23949-001\LogFiles\'
at Error (native)
at Object.fs.openSync (fs.js:544:18)
at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:118:20)
at Project.module.exports.Project.open (C:\Users\dw\AppData\Local\atom\app-0.208.0\resources\app.asar\src\project.js:371:27)
at Workspace.module.exports.Workspace.openURIInPane (C:\Users\dw\AppData\Local\atom\app-0.208.0\resources\app.asar\src\workspace.js:440:31)
at Workspace.module.exports.Workspace.open (C:\Users\dw\AppData\Local\atom\app-0.208.0\resources\app.asar\src\workspace.js:366:19)
at EventEmitter.<anonymous> (C:\Users\dw\AppData\Local\atom\app-0.208.0\resources\app.asar\src\window-event-handler.js:46:25)
at emitTwo (events.js:87:13)
at EventEmitter.emit (events.js:169:7)

Commands

Config

{
"core": {
"disabledPackages": [
"language-objective-c",
"language-clojure",
"language-go",
"language-java",
"language-perl",
"language-php",
"language-python",
"language-toml"
],
"projectHome": "C:\\Projects\\"
},
"editor": {
"invisibles": {},
"showIndentGuide": true,
"showInvisibles": true
}
}

Installed Packages

# User
language-cshtml, v0.1.1
language-fsharp, v0.8.4
language-powershell, v2.0.1
minimap, v4.9.4
vim-mode, v0.51.0

# Dev
No dev packages
Issue 1:
Issue originally made by @decafdennis

Bug information

Babel version: 6.7.2

Node version: 5.0.0

npm version: 3.3.9

Options

{
"plugins": [
"external-helpers",
"transform-es2015-parameters",
"transform-async-to-generator"
]
}

Input code

function f() {
g(async function() {
c(() => this);
});
}

Description

Expected output:

function f() {
g(babelHelpers.asyncToGenerator(function* () {
var _this = this;

c(function () {
return _this;
});
}));
}

Actual output:

function f() {
var _this = this;

g(babelHelpers.asyncToGenerator(function* () {
c(function () {
return _this;
});
}));
}

I [[ https://github.com/babel/babel/compare/master...getstreamline:fix-arrow-this-in-anonymous-function | started work on a fix ]] but I haven't been able to figure out what causes _this to scope differently. Interestingly, if in babel-helper-remap-async-to-generator/src/index.js I remove the replaceWith(built) call, then the lexical scope for this is fixed, but of course I'm missing the call to the helper.

Issue 2:
Version 6.23.0 of babel-transform causes babel-plugin-transform-es2015-destructuring to crash while compiling our app.

Pinning to babel-tranform@6.22.1 removes the crash.

If I console.log(this.hub) in babel-transform I see that this.hub is an empty object. This should be trivial to reproduce in any app that uses destructuring..

TypeError: /Users/nick/git/app/src/server/server.js: this.hub.addHelper is not a function

at Scope.toArray (/Users/nick/git/app/frontend/node_modules/babel-traverse/lib/scope/index.js:463:38)

at DestructuringTransformer.toArray (/Users/nick/git/app/frontend/node_modules/babel-plugin-transform-es2015-destructuring/lib/index.js:122:27)

at DestructuringTransformer.pushArrayPattern (/Users/nick/git/app/frontend/node_modules/babel-plugin-transform-es2015-destructuring/lib/index.js:277:26)

at DestructuringTransformer.push (/Users/nick/git/app/frontend/node_modules/babel-plugin-transform-es2015-destructuring/lib/index.js:110:14)

at DestructuringTransformer.init (/Users/nick/git/app/frontend/node_modules/babel-plugin-transform-es2015-destructuring/lib/index.js:317:12)

at PluginPass.VariableDeclaration (/Users/nick/git/app/frontend/node_modules/babel-plugin-transform-es2015-destructuring/lib/index.js:468:27)

at newFn (/Users/nick/git/app/frontend/node_modules/babel-traverse/lib/visitors.js:276:21)

at NodePath._call (/Users/nick/git/app/frontend/node_modules/babel-traverse/lib/path/context.js:76:18)

at NodePath.call (/Users/nick/git/app/frontend/node_modules/babel-traverse/lib/path/context.js:48:17)

at NodePath.visit (/Users/nick/git/app/frontend/node_modules/babel-traverse/lib/path/context.js:105:12)
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-wrap-an-anchor-element-within-a-paragraph has an issue. Please describe how to reproduce it, and include links to screen shots if possible.

here is my code:

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-wrap-an-anchor-element-within-a-paragraph has an issue. Please describe how to reproduce it, and include links to screen shots if possible.

Here is my code:

<link href='http://fonts.googleapis.com/css?family=Lobster' rel='stylesheet' type='text/css'>
<style>
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}

.thick-green-border {
border-color: green;
border-width: 10px;
border-style: solid;
border-radius: 50%;
}

.smaller-image {
width: 100px;
}
</style>

<h2 class='red-text'>CatPhotoApp</h2>

<a href='http://www.catphotoapp.com'>cat photos</a>

<img class='smaller-image thick-green-border' src='https://bit.ly/fcc-kittens'/>

<p class='red-text'> <a href='http://www.catphotoapp.com'>click here for</a>Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.</p> <------------- (and here is my closing </p> tag)
<p class='red-text'>Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.</p>

Edit(@BerkeleyTrue): Added back ticks
Issue 1:
Description

We are using requests package for our application development and the framework picks up latest version of requests whenever it builds.Today we noticed that our app broken due to new version of Requests 2.16.0.The "Packages" module is completely missing and it leads to our delivery blocking,Could you please check and let us know if we can expect any quick fix for this issue?

Working version:

2.14.2 and 2.15.1

Issue 2:
Hey so the 2.16.0 release broke all of the vendored things I am assuming. I have issued two PRs to two frameworks I use that rely on the vendored packages in requests.

The changelog was a bit obscure about this

2.16.0

Unvendor ALL the things!

Something like BREAKING CHANGE: Vendor packages have been removed, if you relied on these you will need to modify your code would be nice in a 2.16.1 changelog update maybe?

I realize that it can be said these vendored packages are internal and should not be relied on but at least these packages had a use case for using requests and some of the underlying libs and used the vendor packages to ensure everything worked as expected with requests.

Anyone who was relying on these will have their code break upon upgrade, so perhaps a bigger version bump would have been welcome, but at least this can be a warning to people coming here wondering why stuff broke. My solution was a compat.py that conditionally imported urllib3 (works the same for other vendored packages), see my PRs for that fix.
Issue 1:
Kenny MacLeod opened SPR-4677 and commented

In some cases, I would like to be able to more tightly bind a controller's exception handling to the controller itself. I am imagining an @ExceptionHandler annotation which can be added to a controller's methods, which would be invoked by the framework if the @RequestMapping-annotated handler methods throw an exception. These annotated methods would be used in preference to the context-wide ExceptionResolvers.

This would be particularly useful in controllers with multiple @RequestMapping methods, all of which have related exception handling requirements, but which are specific to the controller. Handling this sort of complex exception handling logic in a context-wide ExceptionResolver is decoupling things too much from the source of the exceptions.

Thoughts?

Affects: 2.5.3

Issue Links:

#10236 Annotation for exception handling inside annotation based Controllers ("is duplicated by")

#10304 Portlet-version of @ExceptionHandler

Referenced from: commits f09f4e8

Issue 2:
Tim Nolan opened SPR-403 and commented

Spring constructor-arg comments state:

"NOTE: it is highly recommended to use the index attribute, in Spring up

to and including 1.1. The constructor matcher is extremely greedy in

matching args without an index, to the point of duplicating supplied args

to fill in unspecified constructor args, if they are compatible (i.e. one

single String arg will match a constructor with two String args, etc.).

The matcher should be less agressive in a future version."

This doesn't appear to be the case. This only occurs with autowiring. Here's a test case demonstating that a supplied argument isn't duplicated:

<bean id="exampleBean" class="dateformat.Test">

<constructor-arg type="java.lang.Boolean"><value>true</value></constructor-arg>

</bean>

public class Test {

public Test(Boolean b, Boolean b2) {

System.out.println("b='" + b + "'");

System.out.println("b2='" + b2 + "'");

}

}

No further details from SPR-403
Issue 1:
What problem does this feature solve?

通过过滤掉xss攻击代码来解决v-html容易导致的xss攻击

What does the proposed API look like?

v-html.xss

Issue 2:
What problem does this feature solve?

I'm currently working on making a blog using the WordPress REST API as the back end. The API returns the article with HTML markup in it. I'm taking that JSON response and using v-html to render it into my Vue app. I understand there are cross-site scripting security risks here.

What does the proposed API look like?

It would be great if v-html automatically sanitized the string to remove any <script> tags. For those needing script tags, for whatever reason, maybe v-html-unsafe can accomplish that.

I was recently made aware Angular 4 is doing this and think Vue.js would greatly benefit from this feature.

https://angular.io/guide/security#!#xss
Issue 1:
Symfony version(s) affected: 4.2.5

Description

If some listeners are removed from ContainerAwareEventManager before being initialized they can not be added back if any event was dispatched in the meantime. This happens because dispatchEvent marks specific groups of events as initialized BUT addEventListener checks whether anything was intialized

Possible Solution

Maybe if a listeners is a string the container should be always checked whether it has a service defined under that name? That should allow adding lazy loaded listeners after construction. Other option might be to initialize listeners in getListeners but I don't know how it is used internally by Symfony.

Additional context

In our app we're disabling and re-enabling Doctrine events mostly to disable FosElastica events for batch operations. This is no longer possible.

Issue 2:
in src/Symfony/Bundle/FrameworkBundle/Console/Application.php

use Symfony\Component\HttpKernel\Bundle\Bundle; instead of Symfony\Component\HttpKernel\Bundle;
Issue 1:
There should be a larger tutorial that not only shows how to use Flask but also some extensions (maybe Flask-Script, Flask-SQLAlchemy and Flask-WTF) and modules (or what we will call them then)

Related feedback issues:

http://feedback.flask.pocoo.org/message/115

Issue 2:
It would be nice to see an example application for 0.5 that is based on Flask plus a few Flask extensions that represents a semi-realworld example of how to do applications.

Example proposals:

A Wiki

showcase how config management works

how to unittest more complex apps

maybe even use modules

Flask-Fungiform for the form handling

Flask-SQLAlchemy for database

flask-mail for sending mail notifications

Flask-OpenID for user authentication

Flask-Babel for i18n

jQuery for client side JavaScript

a creoleparser for the wiki Syntax

Thanks to all the extensions that application could still be reasonable small (~1000 lines of code I guess without the templates)
Issue 1:
Hi,

When pressing the flag + ~, it does not launch the fancy zone in edit mode. It doesn't do anything.

Thanks.

Issue 2:
Environment

Windows build number: 10.0.18362.295
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

My main language is Dutch with US (International) keyboard layout and as second language English (United States) with US keyboard. With none of the language setting Win + ~ is working.

Expected behavior

When using US (International) keyboard ~ is a dead key so I think that would not work. But with US keyboard it should work.

Actual behavior

FancyZone editor is not launched.
Issue 1:
VSCode Version: 1.1.0

OS Version: Windows 8.1 Pro

Steps to Reproduce:

Download React.js v15.0.2 (https://fb.me/react-15.0.2.js).

Open the file in Visual Studio Code.

Problem with JavaScript syntax highlighting. It is fine in Sublime Text 3 or VS Studio 2015.

Issue 2:
Ported from microsoft/TypeScript-Sublime-Plugin#285

Related to microsoft/TypeScript-Sublime-Plugin#265.

Issue:

Correct:
Issue 1:
newbie to ES.

This does not return any docs:

"query": {
"filtered": {
"query": {
"match_all": {}
},
"filter": {
"range": {
"screened": {
"from": "now-3d",
"to": "now+3d"
}
}
}
}
}

This does:

"query": {
"match_all": {}
},
"filter": {
"range": {
"screened": {
"from": "now-3d",
"to": "now+3d"
}
}
}

Issue 2:
When using "now" in date math in the query string, the value for now is cached:

curl -XPUT 'http://127.0.0.1:9200/test/?pretty=1' -d '
{
"mappings" : {
"test" : {
"properties" : {
"date" : {
"type" : "date"
}
}
}
}
}
'

curl -XPOST 'http://127.0.0.1:9200/test/test?pretty=1' -d '
{
"date" : "2020-01-01"
}
'

Run this query multiple times:

curl -XGET 'http://127.0.0.1:9200/test/test/_search?pretty=1' -d '
{
"query" : {
"query_string" : {
"query" : "date:[now TO *]"
}
},
"explain" : 1
}
'

You will see that the description line "ConstantScore(date:[1363953493782 TO *])" reuses the same start date

# {
# "hits" : {
# "hits" : [
# {
# "_source" : {
# "date" : "2020-01-01"
# },
# "_score" : 1,
# "_index" : "test",
# "_shard" : 4,
# "_id" : "iOPrtwzdQFGixdfwaAAlcQ",
# "_node" : "gx3hk4y7S0Khhx8IQ4uYQQ",
# "_type" : "test",
# "_explanation" : {
# "value" : 1,
# "details" : [
# {
# "value" : 1,
# "description" : "boost"
# },
# {
# "value" : 1,
# "description" : "queryNorm"
# }
# ],
# "description" : "ConstantScore(date:[1363953493782 TO *]), product of:"
# }
# }
# ],
# "max_score" : 1,
# "total" : 1
# },
# "timed_out" : false,
# "_shards" : {
# "failed" : 0,
# "successful" : 5,
# "total" : 5
# },
# "took" : 5
# }

A range query on the other hand, updates the start date on each run:

curl -XGET 'http://127.0.0.1:9200/test/test/_search?pretty=1' -d '
{
"query" : {
"range" : {
"date" : {
"gt" : "now"
}
}
},
"explain" : 1
}
'
Issue 1:
.desktop file created after compiling from source has wrong binary location ( .../share/atom/atom) instead of the .../bin/atom file.

Besides there is no icon file in the installation share folder, so the .desktop file points at the wrong icon destination (because none is valid).

Issue 2:
When installing from source by following this guide the following .desktop entry is created in /usr/local/share/applications/atom.desktop:

[Desktop Entry]
Name=Atom
Comment=A hackable text editor for the 21st Century.
GenericName=Text Editor
Exec=/usr/local/share/atom/atom %U
Icon=/usr/local/share/atom/resources/app/resources/atom.png
Type=Application
StartupNotify=true
Categories=GNOME;GTK;Utility;TextEditor;Development;
MimeType=text/plain;

However, /usr/local/share/atom/resources/app/resources/atom.png does not exist.

$ ls /usr/local/share/atom/resources/app/
apm atom.sh

I solved it by simply copying the atom icon in atom/resources/atom.png over to the expected path.

cd atom
sudo cp --parents resources/atom.png /usr/local/share/atom/resources/app/

I didn't find this bug last week when installing release 0.192.0. Maybe this was introduced on 0.193.0 because of the asar archive file.
Issue 1:
Documentation linking to existing examples?

I'm slowly working on some of the documentation and I'm trying to figure out how to add some examples here and there in the docs. I'd like to not duplicate work that's already been done. I believe I will link to examples using relative links where they are pertinent in the API. I don't believe I've seen that done yet. It might be nice to also link to handy external examples.

Embedded live examples

I'm not sure I'm going to go this next route, but I was wondering if inline examples would be completely out of the question. Specifically some tweakable examples with the various mesh materials I believe would be quite helpful.

/src code vs /examples code

My next question is regarding the examples code base vs. the src code base. What's the reasoning behind the split between some of the code? A lot of the code in examples is quite handy and I feel like it should be documented. There's no structure in place for that as of yet.

Issue 2:
There are a few things which geometry.clone() doesn't copy a reference to, which it should.

.bones

.skinWeights

.skinIndices

.animations

.animation

are all left without references to the original, which leads to skinning being broken unless the references to those are manually copied. I think references should be passed as it's less confusing, but I don't think they should be deep copies, or this would lead to mostly wasted memory.
Issue 1:
What problem does this feature solve?

A vue component of mine, when applied a certain model generates certain HTML/CSS. Is there any CLI for extracting the output HTML/CSS into seperate entities? Currently I duplicate the Vue file with my own node templating generation.

What does the proposed API look like?

Some CLI that lets you pass in a model and a Vue component, which outputs the html/css file appropriate to the input model.

Issue 2:
Vue.js version

2.0.0-rc.1

Reproduction Link

Steps to reproduce

What is Expected?

What is actually happening?
Issue 1:
I'm trying to use a constant at compile time to define the length of some vectors:

/* Gamma ramps */
const GLFW_GAMMA_RAMP_SIZE : int = 256;

/* Gamma ramp */
struct GLFWgammaramp {
red : [c_ushort * GLFW_GAMMA_RAMP_SIZE], // unsigned short red[GLFW_GAMMA_RAMP_SIZE];
green : [c_ushort * GLFW_GAMMA_RAMP_SIZE], // unsigned short green[GLFW_GAMMA_RAMP_SIZE];
blue : [c_ushort * GLFW_GAMMA_RAMP_SIZE] // unsigned short blue[GLFW_GAMMA_RAMP_SIZE];
}

(code from glfw3-rs)

I get this error:

% rustc test.rs
test.rs:6:26: 6:46 error: expected `]` but found `GLFW_GAMMA_RAMP_SIZE`
test.rs:6 red : [c_ushort * GLFW_GAMMA_RAMP_SIZE], // unsigned short red[GLFW_GAMMA_RAMP_SIZE];

Is this a bug or by design?

Issue 2:
The format_args! built-in macro currently generates structures located in std::fmt, which makes it difficult to use with libcore, even though libcore has the correct traits to read the generated structure.

IMO it would be more logical to use core::fmt instead if possible.

It gives the following errors:

rust/main.rs:53:52: 53:55 error: failed to resolve. Maybe a missing `extern crate std`?
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site
rust/main.rs:53:52: 53:57 error: unresolved name `std::fmt::String::fmt`
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site
rust/main.rs:53:52: 53:55 error: failed to resolve. Maybe a missing `extern crate std`?
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site
rust/main.rs:53:52: 53:57 error: unresolved name `std::fmt::argument`
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site
rust/main.rs:53:46: 53:49 error: failed to resolve. Maybe a missing `extern crate std`?
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site
rust/main.rs:53:46: 53:50 error: unresolved name `std::fmt::Arguments::new`
rust/main.rs:53 core::fmt::write(&mut uart, format_args!("{}", 42u64));
^~~~
note: in expansion of format_args!
rust/main.rs:53:33: 53:59 note: expansion site

I currently have a workaround for this by putting a extern crate "core" as std; but it is really ugly ...
Issue 1:
Issue Details

When using an accelerator like Shift+CmdOrCtrl+3, the shown accelerator should be ⇧⌘3, However, it's shown as ⌘#.

The HIG show menus with the shift arrow: https://developer.apple.com/design/human-interface-guidelines/macos/menus/menu-anatomy/

Electron Version: 7.x

Operating System: macOS 10.14.6

Expected Behavior

The accelerator is shown as ⇧⌘3.

Actual Behavior

The accelerator is shown as ⌘#.

Will create a small fiddle later.

Issue 2:
Hi All,

My Electron and OS versions are:

Electron version: 1.6.15

Operating system: macOS High Sierra 10.13.1

So, I am trying to create a Frameless BrowserWindow object using the below parameters:

var framelessParams = {
width: 500,
height: 500,
frame: false,
transparent: true,
show: false,
backgroundColor: '#fff',
resizable: false,
movable: false,
maximizable: false,
minimizable: false
};

var framelessWindow = new BrowserWindow(framelessParams);

Expected behavior

Showing the frameless window with no warning or errors.

Actual behavior

Showing the frameless window with the below warning in the terminal output.

Electron[1745:97088] *** WARNING: Textured window <AtomNSWindow: 0x7fbcbecc4650> is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.

How to reproduce

I have realized that using frame: flase is producing this warning.

By removing this option, I am not getting this warning.

I think, this might be related to the update I made to High Sierra and I don't recall having to see this warning using older versions of macOS.

I am not really sure, whether this has been reported before or not. However, please advise whether this should be (or already) addressed in the new releases.

Thank you,

Shikartoos.