WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
When attempting to use exportAs with a template-based directive, the following behaviour occurs:

(1) When used with * syntax: You get the error "There is no directive with "exportAs" set to "foo"" despite this not being true

(2) When used with template: You don't get an error, but the export is null, so any method calls or property access will error

The only way for the export to work is:

(1) Using <template>

(2) and specifying exportAs, despite having to... [edit: not actually necessary for workaround]

(3) manually set the local with `ViewRef.setLocal("exportAsName", this);

Additionally, in no case is the exported variable accessible in the external context. When set with setLocal it can only be accessed inside the template. (It makes sense that setLocal only works inside the template, so this is more a consequence of the overall divergent behaviour)

(While that's a workaround to get at the variable inside the template, it doesn't constitute a "way for the export to work" since it's somewhat unrelated feature-wise)

Demonstration plunkr: http://plnkr.co/edit/jXYxQ6NYk7tec4QNf355?p=preview

Issue 2:
If you want to use a TemplateRef to instantiate an embedded View anywhere other than in that template's location (i.e., with its own ViewRef), the inability to grab the TemplateRef (or a directive instance) on the template element becomes cumbersome. The only real way to accomplish it now is to use @ViewChild / @ViewChildren to retrieve some decorating Directive that exposes the TemplateRef.

For example:

<component-with-popup [popup]="content"></component-with-popup>

<template popup-content #content>
This is the template content!
</template>

This doesn't work, since the assumption is that #content is for something in the template rather than the template itself.

Proposal:

Add a new syntax for referencing the template itself:

<component-with-popup [popup]="content"></component-with-popup>

<template popup-content template-var-content>
This is the template content!
</template>

This uses template-var- as the prefix for the variable over the standard var-. Since this is going to be a somewhat uncommon use-case, a shorthand syntax isn't strictly necessary.

If desired, possible shorthand syntaxes:

<template @content>

<template *#content>

<template **content>

<template ##content>

<template !#content>

<template 😱content>

cc @vsavkin @tbosch
Issue 1:
When I initialize popover via javascript(not adding data attributes) does some facinating things it shoudn't do. It appends content to .content. as it should, but doesn't clear previous content, so there will be this content I need to append there, and previous content

Whatever.prototype.init(){
var parent=this;
this.elem.popover({
content:parent.content,
title:'Heading',
container:'body',

});
}
Whatever.prototype.content = function() {
$form=$($.Mustache.render('content',this));
return $form;
};

So when I press first time:

And say fifth time:

today I need to do quite idiotic thing:

Whatever.prototype.content = function() {
$(this).data('bs.popover').$tip.find('.popover-content').empty();
$form=$($.Mustache.render('content',this));
return $form;
};

Issue 2:
Hey there,

A recent change 5bf1391 related to issue: #10658

Leads to behavior I'd consider at the very least undesired(and probably overlooked). The net effect is that by using "append", the content returned by the popover method gets re-appended on every single popover toggle.

http://jsfiddle.net/jQxdv/

This is different than the plugin's behavior historically. Was this a desired change? If yes, why is piling up content considered correct in this case?
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-learn-how-script-tags-and-document-ready-work has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-target-the-same-element-with-multiple-jquery-selectors has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Code below "You shouldn't need to modify code below this line" initially missing, then once it appears, instructions disappear. Reloading page sometimes causes scrollbar next to instructions to disappear as well. Requires reloading page 4-5 times for everything to return, so maybe it's just me?
Issue 1:
During package updates the "Updating" status of many (not all) packages doesn't seem to change to "Updated" even after the updates have been successfully installed. I can see the updates were successfully installed by clicking "Check for Updates" again after which the "Updating" message disappears and I get the message "All of your installed packages are up to date!".

The issue only appeared after the 1.0.0 release and mostly with some of the larger packages. I realise that larger packages take longer to install but I've tested by waiting more than 10 min and then checking for updates again.

This is not a major issue – in the past I usually waited for conformation that all packages were installed before I continued working where now I have to allow enough time to ensure the process has successfully run.

System specs:

MacBook Pro 17" 2011

Mac OS X Yosemite (10.10.4)

Atom Version 1.0.0

Thx!

(PS. I've tried pretty much all available editors and Atom is by far the best.)

Issue 2:
Just noticed this as of Atom 0.208.0-c06d62e:

Click the Update button in an available update package card in the Updates panel

Wait a sufficiently long time so you know it should've been installed (~5 mins with an SSD, for example)

Package card will still say "Updating..."

Click another panel in Settings View

Close Settings View

Reopen Settings View

Click the Updates panel

Assuming there was only 1 update, it will report that all packages are up-to-date.

Can anyone in @atom/feedback reproduce with the same version?
Issue 1:
VSCode Version:1.2.0

OS Version:Windows 7

Steps to Reproduce:

Problem 1

Ctrl + `

Chinese character gash in Terminal.

Problem 2

创建一个目录： D:\新建文件夹

打开VS Code， 文件 -> 打开文件夹，选择创建好的“新建文件夹”

Ctrl + ` 无法打开 Terminal。

Issue 2:
After updating I now receive an error.

[c:/Program Files (x86)/Microsoft VS Code/resources/app/extensions/csharp-o]: Cannot read file c:/Program Files (x86)/Microsoft VS Code/resources/app/extensions/csharp-o/package.json: ENOENT: no such file or directory, open 'c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\csharp-o\package.json'

Upon checking I found that the entire c# extension is empty and have found no solutions yet to remedy this.
Issue 1:
TypeScript Version:

1.8.10

Visual studio Version:

2015 community version update 2

typescript tools for visual studio 1.8.29.0

Code

any typescript code

Expected behavior:

Visual studio typescript debugger could correctly setup breakpoint red point at the line I double clicked.

Actual behavior:

When enable inlineSourceMap: true in tsconfig.json, when setting a breakpoint in VS editor, it can map that source line number from .ts file to the corresponding line number in the .js file, however, the breakpoint red point in the VS editor is shown on the line number in the .js file, rather than the line number on the .ts file. Therefore, if I double click on line 100 in one .ts file, the breakpoint red point would be shown on maybe line 90 of that .ts file, corresponding to what the mapped line number is in the corresponding .js file.

If I disable inlineSourceMap: true, and enable sourceMap: true in tsconfig.json, everything would be just fine.

I've noticed that there is a previous issue similar to this: #4360, and that issue is closed. Is my configuration wrong or missing something? Thanks.

My tsconfig.json:

{
"compileOnSave": true,
"compilerOptions": {
"module": "commonjs",
"target": "ES5",

"noImplicitAny": true,
"suppressImplicitAnyIndexErrors": true,
"removeComments": false,
"preserveConstEnums": true,
"forceConsistentCasingInFileNames": true,
"noEmitOnError": true,

// "sourceMap": true,
"inlineSourceMap": true,

"inlineSources": true
}
}

Issue 2:
TypeScript Version:

1.8.7

Code

private streamProcess(stream: NodeJS.ReadableStream): Promise<void> {
return new Promise<void>((ok, fail) => {
stream
.pipe(this.parser.createStream()) // returning type is `NodeJS.ReadWriteStream`
.on("error", fail)
.pipe(this.transformer.createStream()) // returning type is `NodeJS.ReadWriteStream` and error appears in the line
// error TS2339: Property 'pipe' does not exist on type 'EventEmitter'.
.on("error", fail)
.pipe(this.persister.createStream()) // returning type is `NodeJS.WritableStream`
.on("error", fail)
.once("finish", () => {
});
});
}

Expected behavior:

Actual behavior:

i got error if only set event emitters, what's the wrong of the code?
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

Ansible setup module.

ANSIBLE VERSION

ansible 2.2.2.0

config file = /etc/ansible/ansible.cfg

configured module search path = Default w/o overrides

CONFIGURATION

N/A

OS / ENVIRONMENT

Control: CentOS 7.3

Target: CentOS 7.3

SUMMARY

When gathering facts for a host with a high open file limit setting, fact gathering can take a long time. This is exacerbated on systems with many network interfaces. On a system with an open file limit of 1048576 and ~50 network interfaces (mostly virtual), fact gathering takes in excess of 20 seconds.

STEPS TO REPRODUCE

Set the open file limit to a high value:

- hosts: all
become: yes
tasks:
- name: increase file descriptor limit
copy:
dest: /etc/security/limits.d/99-nofile.conf
content: |
root soft nofile 1048576
root hard nofile 1048576

Gather facts:

- hosts: all
become: yes
gather_facts: yes

EXPECTED RESULTS

Facts are gathered in a reasonable time.

ACTUAL RESULTS

Facts took a long time to be gathered.

Issue 2:
ISSUE TYPE

Feature Idea

COMPONENT NAME

setup

ANSIBLE VERSION

ansible 2.1.0.0

CONFIGURATION

OS / ENVIRONMENT

Linux

SUMMARY

On some of my linux cluster servers, I have quite large max-open-files configuration (for some practical need), like:

$ulimit -n
655360

And ansible playbook's setup stage takes more than one minutes.

time ansible -vvvv <any host> -m setup

use strace -f python /home/admin/.ansible/tmp/ansible-tmp-1493734939.34-186220473132806/setup, I can see that when forking commands it's closing all fds until os.sysconf('SC_OPEN_MAX'), which cost lots of time。

Since that is python's subprocess implementation behavior, for testing I hacked build_module_command in ansible/plugins/shell/__init__.py like this: cmd_parts = ['ulimit -n 1024;', env_string.strip(), shebang.replace("#!", "").strip(), cmd], setup will only take less than 2 seconds.

Any good idea? Or just should never config such large max-open-files at OS scope?

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS
Issue 1:
I feel like the previous issue #12392 was locked without explaining why. What is wrong with this piece of code when edited into the project? If nothing I would be happy to create a pull request.

.btn-group-justified {
&> .btn {
border-right-width: 0px;
}
&> .btn:last-child {
border-right-width: 1px;
}
&> .btn:hover + .btn, .btn:focus + .btn {
/* Bootstrap sass mixins/_buttons L18 and _buttons L58*/
border-left-color: darken($btn-default-border, 12%);
}
&> .btn:active + .btn, .btn.active + .btn {
/* Bootstrap sass _theme L49 and L63*/
border-left-color: darken($btn-default-bg, 14%);
}
}

I understand @cvrebert might have had good reasons to lock the previous issue, I didn't understand them though. Would you be so kind to leave this one unlocked for me to give a reaction?

Issue 2:
Please consider removing the double border on justified link variation, like you have on multiple buttons in an input group, in the upcoming v3.1.0?

http://getbootstrap.com/components/#btn-groups-justified

Thanks!

Lee
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

11.03

Operating System:

macOS 11.0.1

Expected Behavior

remote.screen has EventEmitter methods such as on defined, to listen to screen events such as display-added

Actual Behavior

remote.screen does not have any defined EventEmitter methods

To Reproduce

In the devtools, inspect require('electron').remote.screen and notice that it does not have the on method defined

Additional Information

There was a PR to address other remote.screen methods not being defined that was merged in 11.0.3 (#26660), but it did not seem to address this bug

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

11.0.2

Operating System:

NixOS 21.03 x86_64

Last Known Working Electron version:

10.1.6

Expected Behavior

remote.screen.getPrimaryDisplay() works.

Actual Behavior

Uncaught TypeError: remote.screen.getPrimaryDisplay is not a function

To Reproduce

Electron Fiddle: https://gist.github.com/andersk/6158c0016c56e52c58cec4aa4cd8317e

Additional Information

This broke between 11.0.0-nightly.20200724 and 11.0.0-nightly.20200729, probably in #24677. Cc @nornagon.

See also electron-userland/spectron#771, webtorrent/webtorrent-desktop#1896.
Issue 1:
Challenge http://freecodecamp.com/challenges/waypoint-create-a-set-of-radio-buttons has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

When I visit challenge page, the HTML inside editor is rendered twice.

Notice there are two title CatPhotoApp.

This issue, however, is gone when click the Run Code button or press control + Enter.

Maybe there is something wrong with the onload/initial callback.

Additional info:

Browser: Mozilla Firefox 40.0

OS: Ubuntu 14.04

Thank you for the amazing learning resource :)

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-line-up-form-elements-responsively-with-bootstrap has an issue.

I think the problem is happening on all Waypoint pages; the device right side of the screen where the CatPhotoApp page displays the information is being displayed duplicated;

Another point is that the HTML / CSS code is not completely displayed when the page is loaded, it is necessary to click or edit the code so that the code from the previous lesson is displayed correctly;
Issue 1:
Description of the problem

I see RENDER WARNING in the two examples on my Windows + Chrome.

[.Offscreen-For-WebGL-000002652FEC91C0]RENDER WARNING: Render count or primcount is 0.

https://threejs.org/examples/webgl_octree.html

https://threejs.org/examples/webgl_materials_cubemap_dynamic.html

But I don't see on FireFox nightly. It could be (Windows) Chrome specific issue?

Three.js version

Dev

r95

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

Hardware Requirements (graphics card, VR Device, ...)

Issue 2:
Sorry, it was glitch on my side after ObjLoader update. After my code fixing everything works fine.

...

Three.js version

Dev

r74

r75

...

Browser

[] All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

Linux

Android

IOS
Issue 1:
An optional parameter on the facet, like sort's "ignore_unmapped" parameter would be great.

Context : We use "dynamic_templates" in our index mapping and allow clients to search, sort, and "facet" on any field that is valid by the rules of the mapping.

The problem arises when facets are run on fields that do not exist in the data, and thus are not "actually" in the mapping.

Example : With a "dynamic_template" for "rating-*" fields, we can search, filter, and sort

(with "ignore_unmapped" = true), against a "rating-Tuna" field, even though there are no

documents in the index with that field.

See Gist https://gist.github.com/4568689 for a script that will quickly demonstrate the problem.

Issue 2:
Changing the routing value or parent id of a document will lead to duplicate documents with the same index, type, and id. I think that internally a documents id is constructed from the index, type, id, and routing value so internally the id's are different, yet they look the same to the end user.

Is there something we can do to address this? Maybe add an "old_route" and "old_parent" flag that when found can be used to do issue a delete on the old shard? Is there a better approach?
Issue 1:
Hi,

Is there any plan to add support for CMake build tool? CMake is more easy and portable.

Issue 2:
I'm creating this issue to discuss the possibility of standardizing our build system on CMake, which seems to be getting significant traction as a saner, cross-platform build system than Make. If we decide to use this to build Julia, we may want to standardize on it as a standard build system for Julia packages that need to compile things too.
Issue 1:
Uncaught Error: spawn /opt/atom/atom (deleted) ENOENT

Atom Version: 0.152.0

System: linux 3.13.0-40-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At events.js:85

Error: spawn /opt/atom/atom (deleted) ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)

Issue 2:
TEMPORARY WORKAROUND: ln -s /usr/share/atom/atom "/usr/share/atom/atom (deleted)"

Uncaught Error: spawn /opt/atom/atom (deleted) ENOENT

Atom Version: 0.152.0

System: linux 3.13.0-40-generic

Thrown From: Atom Core

Steps To Reproduce

...

...

Stack Trace

At events.js:85

Error: spawn /opt/atom/atom (deleted) ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1051:32)
at child_process.js:1142:20
at process._tickCallback (node.js:378:11)
Issue 1:
Describe what you were doing when the bug occurred:

1.

2.

3.

Please do not remove the text below this line

DevTools version: 4.2.1-3816ae7c3

Call stack: at n.value (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:163226)

at m (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:332702)

at uc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:40:332919)

at gi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:59907)

at el (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:68139)

at jl (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:108547)

at Lc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92715)

at Pc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:92640)

at wc (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:89544)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32:46341

Component stack: in uc

in div

in div

in wo

in Unknown

in n

in Unknown

in div

in div

in Li

in $e

in dn

in Ca

in Pc

Issue 2:
Here is the link to Sandbox

I have simple code like this:

Sidebar.js:

import React, { Component } from "react";
import { BrowserRouter as Router, Route, NavLink } from "react-router-dom";

import Menu from "./Menu";

class SidebarExample extends Component {
render() {
console.log("Sidebar - render()", new Date());
return (
<Router>
<div>
<div>
If I uncomment the below component Menu the render() method of the component is called everytime I change the link. Why? In the Menu component the is the same html code below. What is going on?
{/*<Menu />*/}
<ul>
<li>
<NavLink exact to="/">
Home
</NavLink>
</li>
<li>
<NavLink to="/bubblegum">Bubblegum</NavLink>
</li>
<li>
<NavLink to="/shoelaces">Shoelaces</NavLink>
</li>
</ul>
</div>
</div>
</Router>
);
}
}

export default SidebarExample;

Menu.js:

import React, { Component } from "react";
import { NavLink } from "react-router-dom";

class Menu extends Component {
render() {
console.log("Menu - render()", new Date());
return (
<ul>
<li>
<NavLink exact to="/">
Home
</NavLink>
</li>
<li>
<NavLink to="/bubblegum">Bubblegum</NavLink>
</li>
<li>
<NavLink to="/shoelaces">Shoelaces</NavLink>
</li>
</ul>
);
}
}

export default Menu;

If I uncomment the component the render() method of the component is called everytime I change the link. Why? In the Menu component there is the same html code below.

What is going on?

I'm loosing my mind!
Issue 1:
Issue originally reported by @sheerun in babel/babel-preset-env#434

When using useBuiltIns: 'usage' and doing two passes with babel, it can require polyfills multiple times, what makes babel not idempotent on second run (in my opinion it should be).

require("babel-polyfill/lib/core-js/modules/es6.promise");

require("babel-polyfill/lib/core-js/modules/es6.symbol");

require("babel-polyfill/lib/core-js/modules/web.dom.iterable");

function _typeof2(obj) { if (typeof Symbol === "function" && typeof Symbol.iterator === "symbol") { _typeof2 = function _typeof2(obj) { return typeof obj; }; } else { _typeof2 = function _typeof2(obj) { return obj && typeof Symbol === "function" && obj.constructor === Symbol && obj !== Symbol.prototype ? "symbol" : typeof obj; }; } return _typeof2(obj); }

require("babel-polyfill/lib/core-js/modules/es6.symbol");

require("babel-polyfill/lib/core-js/modules/web.dom.iterable");

require("babel-polyfill/lib/regenerator-runtime/runtime");

require("babel-polyfill/lib/core-js/modules/es6.string.starts-with");

Issue 2:
Issue originally made by Ivan (istarkov)

Bug information

Babel version: 6.6.0

Node version: 5.6.0

npm version: 3.7.5

Description

Looks like bug in latest 6.6.0 babel version

Next simple plugin

export default function (/* { types: t } */) {
return {
visitor: {
CallExpression(path) {
const { callee: { type, name } } = path.node;
console.log('calleeName', type, name);
},
},
};
}

for a file

import css from './some';

outputs

calleeName Identifier require
calleeName Identifier _interopRequireDefault

but for a same file + console.log

import css from './some';
console.log(css);

outputs

calleeName MemberExpression undefined

but must output

calleeName MemberExpression undefined
calleeName Identifier require
calleeName Identifier _interopRequireDefault

This breaks this plugin istarkov/babel-plugin-webpack-loaders#39

And some others I know