WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
ansible 0.8 (devel 761330b) last updated 2012/10/04 10:13:36 (GMT +200)

Hello,

I have a host in the inventory which uses a non-standard SSH port (in my case: 2222).

If I use delegate_to to delegate to another host, ansible connects to the host (vz112.local) with the port from the host (10.20.20.208) which is processed by the playbook (port 2222 in my case). Of course this fails.

It seems I'm not able to override the port via "delegate_to: otherhost:22".

Is this a bug, feature or do I something wrong?

(Well, workaround is to use redir on the delegate_to host for now.)

Thanks,

Dietmar

[xxx]

10.20.20.208:2222

name: Create base Nagios host configuration

action: template src=files/etc/nagios/hosts/host.cfg.j2 dest=/etc/nagios/hosts/${ansible_hostname}.cfg

delegate_to: vz112.local

TASK: [Create base Nagios host configuration] *********************

fatal: [10.20.20.208] => failed to transfer file to /source:

Connecting to vz112.local...

ssh: connect to host vz112.local port 2222: Connection refused

Couldn't read packet: Connection reset by peer

FATAL: all hosts have already failed -- aborting

Issue 2:
Thanks to a tip earlier, I'm using ansible_python_interpreter to jiggle with the Python version nodes can use: hosts in my inventory have that variable set accordingly.

Installing 0.7 now allows me to use some of the new cool features, but I find certain inconsistencies:

Jinja2 templates don't use the specified interpreter. The following code complains that simplejson cannot be imported, though the Python-2.7.3 I point to with ansible_python_interpreter can, indeed, import json:

{{ ansible_facts | to_json }}

A Playbook which has a local_action: template src=xx.j2 dest=/tmp/xx uses the default /usr/bin/python on the target system (i.e. 127.0.0.1) instead of that configured with ansible_python_interpreter.
Issue 1:
Vue.js version

1.0.20

Reproduction Link

https://jsfiddle.net/ardoramor/hyk86ca3/

Steps to reproduce

Run fiddle, examine console.

What is Expected?

Entries will be tracked by the specified path, just like in filters (e.g., orderBy)

What is actually happening?

VueJs prints out a warning and fails to get the unique value specified by path

Required change

There are three lines that would need to change from value[trackByKey] to getPath(value, trackByKey) in functions cacheFrag, getCachedFrag, and deleteCachedFrag. I can make a PR but maybe such a small change doesn't require it?

Also, is it possible to add expression evaluation for track-by? This way, a combination of fields can yield a unique identifier (e.g., track-by="employee.company + employee.id", in case id can be reused by companies). I have a different application but this should make sense as well.

Issue 2:
What problem does this feature solve?

Keep-alive filter by slot instance.

I need to use it to filter my route component in router-view by :key="$route.fullPath"

What does the proposed API look like?

<keep-alive :include-keys="function(keyOfSlot:string) or regex or string">
<component :key="myKey"/>
</keep-alive>
Issue 1:
Challenge

Using Objects for Lookups

https://www.freecodecamp.com/challenges/using-objects-for-lookups

Issue Description

Cannot progress to the next challenge although all conditions are met

Browser Information

Google Chrome, Version: Version 51.0.2704.106 (64-bit)

Operating System: Mac OSX v10.11.6

Mobile, Desktop, or Tablet: Laptop

Your Code

// Setup
function phoneticLookup(val) {
var result = "";

// Only change code below this line

lookup = {
alpha: 'Adams',
bravo: 'Boston',
charlie: 'Chicago',
delta: 'Denver',
echo: 'Easy',
foxtrot: 'Frank'
};

result = lookup[val]; //must use [ ] notation if looking up variables
// Only change code above this line

return result;
}

// Change this value to test
phoneticLookup("alpha");

Screenshot

Issue 2:
Challenge tests for jQuery fail to run if syntax errors are present in a campers code.

Examples:

#9289

#9082

#9470

#9672

#9698

What is stopping the tests running? Can we fix it?

Is there a way to lint jQuery in codemirror so campers get visual clues to syntax errors, like in the JS challenges?

-Or-

When there is a syntax error, can we present a modal to the camper saying there is a syntax error present in their code when they click 'Run tests'?
Issue 1:
Hi

I am using transformer 4.1.1 on multiple gpus with distributed launch script below, the n_gpu set in this case is 1 instead of actual n_gpus, could you tell me how I can access to the total number of ranks calling the launcher with? Is there any variable in huggingface library which could show the number of gpus the script is called with? Here is the command I run:

export BS=4; CUDA_VISIBLE_DEVICES=0,1 USE_TF=0 python -m torch.distributed.launch --nproc_per_node=2 --master_port=9915 finetune_trainer.py --model_name_or_path t5-small --output_dir output_dir --adam_eps 1e-06 --data_dir wmt_en_ro --do_train --freeze_embeds --label_smoothing 0.1 --learning_rate 3e-5 --logging_first_step --logging_steps 1000 --max_source_length 128 --max_target_length 128 --num_train_epochs 1 --overwrite_output_dir --per_device_train_batch_size $BS --sortish_sampler --task translation --val_max_target_length 128 --warmup_steps 500 --n_train 500

thanks

Issue 2:
Hi

I am using transformer 4.1.1 on multiple gpus with distributed launch script below, the n_gpu set in this case is 1 instead of actual n_gpus, could you tell me how I can access to the total number of ranks calling the launcher with? Is there any variable in huggingface library which could show the number of gpus the script is called with? Here is the command I run:

export BS=4; CUDA_VISIBLE_DEVICES=0,1 USE_TF=0 python -m torch.distributed.launch --nproc_per_node=2 --master_port=9915 finetune_trainer.py --model_name_or_path t5-small --output_dir output_dir --adam_eps 1e-06 --data_dir wmt_en_ro --do_train --freeze_embeds --label_smoothing 0.1 --learning_rate 3e-5 --logging_first_step --logging_steps 1000 --max_source_length 128 --max_target_length 128 --num_train_epochs 1 --overwrite_output_dir --per_device_train_batch_size $BS --sortish_sampler --task translation --val_max_target_length 128 --warmup_steps 500 --n_train 500

thanks
Issue 1:
Bug Report

I would like to work on a fix!

Current behavior

When using the programmatic API, babel always throws an error when I use path.buildCodeFrameError.

Input Code

A simple example:

const { parseAsync, traverse } = require('@babel/core');

async function demo() {
const parsed = await parseAsync('foo.bar()', { sourceFileName: 'foo.js' });
traverse(parsed, {
enter(path) {
path.buildCodeFrameError('some error');
}
})
}

demo().catch(console.error);

Expected behavior

I would expect an awesomely formatted code frame error.

Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)

none

Environment

System:
OS: Windows 10 10.0.19041
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
npmPackages:
@babel/core: ^7.9.6 => 7.10.4
@babel/generator: ^7.9.6 => 7.10.4
@babel/parser: ^7.9.6 => 7.10.4
@babel/plugin-proposal-decorators: ^7.8.3 => 7.10.4
@babel/preset-react: ^7.9.4 => 7.10.4
@babel/preset-typescript: ^7.9.0 => 7.10.4
babel-plugin-transform-decorators-legacy: ^1.3.5 => 1.3.5

Issue 2:
Bug Report

This related to #8617

I would like to work on a fix!

Current Behavior

@babel/parser has a different behavior when estree enabled, and when not.

Input Code

When estree disabled code with Duplicated variable declaration throws while parsing:

const {parse} = require('@babel/parser');
const traverse = require('@babel/traverse').default;

const code = `function square(n) {
const n = 1;
}`;

// crash with an error: Identifier 'n' has already been declared (1:16)
const ast = parse(code);

When estree mode enabled code is parsed, but can't be traversed because of this.hub is undefined:

const {parse} = require('@babel/parser');
const traverse = require('@babel/traverse').default;

const code = `function square(n) {
const n = 1;
}`;

const ast = parse(code, {
plugins: [
'estree',
]
});

traverse(ast, {
enter(path) {
console.log('n');
}
});

/*
throw this.hub.buildError(id, `Duplicate declaration "${name}"`, TypeError);
^

TypeError: Cannot read property 'buildError' of undefined
at Scope.checkBlockScopedCollisions (/home/coderaiser/node_modules/@babel/traverse/lib/scope/index.js:402:22)
*/

Same result when instead of estree plugin, errorRecovery enabled.

Expected behavior/code

Would be great if in estree mode babel throws while parsing and/or can throw while traversing

about Duplicate declaration.

Environment

Babel version(s): v7.9.4

Node/npm version: Node 12(13)/npm 6

OS: Ubuntu

Monorepo: no

How you are using Babel: parse, traverse

Possible Solution

I suggest to use TypeError, because this is what hub actually does, this way:

throw TypeError(`Duplicate declaration "${name}"`);

If of course buildError doesn't used in development purpose to set breakpoint on error building, anyways Chrome Developer Tools debugger already suggest similar feature pause on exceptions (caught and uncaught).
Issue 1:
VSCode Version: 0.10.11

OS Version: Mac OS X 10.10.5

Steps to Reproduce:

Create a new javascript file and add this source

import React from 'react';

export default class Item extends React.Component {
update(e) {
console.log(e.target.value);
}

test = (e) => {
console.log(e.target.value);
}

render() {
return <span>{this.props.name}<br/>
<input type="text" onChange={(e) => this.update(e)} /><br/>
<input type="text" onChange={this.test} />
</span>;
}
}

IDE show me as syntax error.

Issue 2:
… and I can't turn it off by setting javascript.validate.enable false.

Perhaps this is a soft documentation bug: the release notes proudly mention experimentalObjectRestSpread but then say:

Support for ObjectRestSpread is not yet provided by Salsa but it is on the roadmap (see microsoft/TypeScript#2103).

… which is confusing and misleading.

It's confusing because the stand-out tone of core dev responses to that issue is "not until TC39 moves it to stage 3; bother them, not us", which is much less optimistic than the Feb 2016 release notes or the TypeScript Roadmap itself.

It's misleading because it fails to describe the impact of "support… not yet provided" as error messages you can't make go away. If there's some way to make them go away, please describe it in that part of the release notes. If not, I don't think it's too strong to outright advise users of object spread properties to delay upgrading.

Without a work-around, this kills code for me, as I now have to dig for the real errors amongst a few dozen erroneous:

Property assignment expected.

Argument expression expected.

Declaration or statement expected.

I trust a workaround is possible, as code is not erroring in JSX.
Issue 1:
As numpy.matrix will be removed, we should remove SciPy's dependency in 1.1.0:

Add sparray:

bsr_array

coo_array

csc_array

csr_array

dia_array

dok_array

lil_array

sparray

Deprecate spmatrix.

Issue 2:
While sitting with @stefanv last week we discussed (and then @stefanv started implementing) sparse array classes that use the same code as the existing matrix classes, but instead satisfy the ndarray interface (only up to two dimensions). For example slicing out rows would result in 1d arrays rather than 2d matrices, the * operator means elementwise multiply rather than matrix multiply, etc..

This would be valuable for a number of communities and, in particular, anyone trying to use sparse arrays and numpy arrays interchangably, as happens in Pandas, Scikit-Learn, and Dask.array.

I thought I'd raise this issue to track this work (and also to subtly prod @stefanv).

Also cc @NelleV and @njsmith
Issue 1:
Thank u for the excellent works on next@5.

I found that it uses 'blob:http://localhost:3000/0xxxxxxx' to load css/scss into the page after dom is rendered.

So the users will see the page without styles about 1 or 2 seconds. I believe it is the only behavior in development mode at first.

So I tried build with yarn build & run server in production model with yarn start.But this time, I see no css files loaded.

Did I miss something or this is designed?

Issue 2:
In this small repo I've illustrated next-css not working with SSR, this is a blocker from my team moving off of https://github.com/traveloka/styled-modules which we're super eager to do.

Great work on Next.js 5.0! Can't wait to fully migrate to it :)

I would mind if Next.js apps had to have a custom _document.js to support this, but I guess thats more of an implementation detail.
Issue 1:
The ParameterBag class is implemented in two components and has different interfaces.

Symfony\Component\HttpFoundation\ParameterBag

Symfony\Component\DependencyInjection\ParameterBag

I can understand the duplication to avoid inter-module dependencies, but i do not understand why the different interfaces. For example the Http version allows default values:

$bag->get('name', null)

Where the DI version does not and makes you do:

$bag->has('name') ? $bag->get('name') : null

Could these be united? at least the interfaces? or is it a issue with requirements?

Issue 2:
Hello,

After a discussion on Symfony Slack about environment variables and CLI around my question:

I’m interested into how the community solves the environnement variable and the CLI.

It seems that nothing solid came out out of this discussion.

The documentation states that environment variables should be added on the webserver level on production.

Nothing is said reguarding the CLI, so a lot of people (like me) will end up spending time looking for why a crontab entries is not executed.

To me, prefixing the executed commands by the environment variables is not a good solution. I mean, it would involve:

variable duplication (so bad maintenance, "oops forgot to add this variable in this place"),

and very bad lisibility (prefix with 20+ environment variables 🤔?)

Regarding of this, why push in favor of environement variable if the only way of achieving this is to use a not recommended way (.env file).

One alternate solution would be to create a file on the system in /etc/environment that contains those environment variable, BUT again, what happens if your server hosts multiple projects and you want one app X to be APP_ENV=prod and the other Y APP_ENV=dev, then you have a variable collusion with the name unless you change the APP_ENV variable name in all project to include a vendor prefix ? (I don't even know if it's feasible).

Not all of us use containers to run in production (or doesn't even want to).

PS: I open this here instead of the documentation repository because it reveals more questions than just "how to deal with that in doc is missing".
Issue 1:
Feature request

Is your feature request related to a problem? Please describe.

Currently it is not possible to display two separate Next.js-based applications on the same page, if one attemps to do so, he gets an error. It is caused by the fact that Next.js-based application mounts on DOM elements with fixed IDs: __next and __NEXT_DATA__.

Describe the solution you'd like

We'd like IDs of elements on which Next.js-based application mounts to be parameterized, possibly provided in application build script. We've forked Next.js and implemented this change in our fork: Raudos@a4da2b6. This PoC was created during workshop at meet.js in Katowice, Poland on 29.09.2019 (https://summit.meetjs.pl/2019/zeit-workshop).

Describe alternatives you've considered

We've considered not having multiple separate Next.js-based applications on one page, but we're building our application in microfrontend architecture, hence in many cases we want to avoid having whole page as a single application.

Additional context

More information on our approach to microfrontend architecture can be found here: https://medium.com/stepstone-tech/microfrontends-extending-service-oriented-architecture-to-frontend-development-part-1-120b71c87b68 (we've not considered Next.js at the time of writing this article).

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

I notice that next.js ignores the node_modules directory from being compiled by babel. It will cause some errors in old version browsers.

For example, after npm run dev in example of data-fetch, it would generate the following code in .next/main.js

/* 347 */
/***/ (function(module, exports, __webpack_require__) {

"use strict";

const ansiRegex = __webpack_require__(348);

module.exports = input => typeof input === 'string' ? input.replace(ansiRegex(), '') : input;

/***/ }),
/* 348 */
/***/ (function(module, exports, __webpack_require__) {

"use strict";

module.exports = () => {
const pattern = [
'[\\u001B\\u009B][[\\]()#;?]*(?:(?:(?:[a-zA-Z\\d]*(?:;[a-zA-Z\\d]*)*)?\\u0007)',
'(?:(?:\\d{1,4}(?:;\\d{0,4})*)?[\\dA-PRZcf-ntqry=><~]))'
].join('|');

return new RegExp(pattern, 'g');
};

These code is generated from strip-ansi, which is one of the dependencies of next.js.

However, Chrome browsers whose version < 41 would throw error of "SyntaxError: Use of const in strict mode" according to caniuse. In addition, a few old browsers don't recogize arrow functions.

How can I make babel compile node_modules so that my project can run on these old version browsers?
Issue 1:
Not sure if this is related to #9348.

I am working on two projects at the same time and project B imports a local file from project A (for development only).

When I change the file in project A, I get the following LSP error in project B.

I think that the LSP is not updated when an imported file has changed that is outside the project directory.

Starting Deno language server...
version: 1.8.0 (release, x86_64-apple-darwin)
Connected to "Visual Studio Code" 1.54.1
language server initialized
Server ready.
Error processing TypeScript request: Error: The current snapshot version is missing.
Args: "GetChangeRangeArgs { specifier: "file:///******/deno-cliffy/command/command.ts", old_length: 50291, old_version: "1615124690846", version: "1615124762886" }"
at processResponse (deno:core/core.js:212:11)
at Object.jsonOpSync (deno:core/core.js:236:12)
at ScriptSnapshot.getChangeRange (deno:cli/tsc/99_main_compiler.js:224:19)
at acquireOrUpdateDocument (deno:cli/tsc/00_typescript.js:123008:133)
at Object.updateDocumentWithKey (deno:cli/tsc/00_typescript.js:122974:20)
at Object.getOrCreateSourceFileByPath [as getSourceFileByPath] (deno:cli/tsc/00_typescript.js:149726:49)
at tryReuseStructureFromOldProgram (deno:cli/tsc/00_typescript.js:107087:28)
at Object.createProgram (deno:cli/tsc/00_typescript.js:106618:29)
at synchronizeHostData (deno:cli/tsc/00_typescript.js:149648:26)
at Object.getReferencesAtPosition (deno:cli/tsc/00_typescript.js:149911:13)
[Error - 14:46:04] Request codeLens/resolve failed.
Message: Internal error
Code: -32603

Issue 2:
I have no idea what exactly happened

thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', cli\lsp\tsc.rs:806:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error processing TypeScript diagnostics:
channel closed
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', cli\lsp\language_server.rs:532:8
Issue 1:
Hi,

I've been experiencing some dificulty using Pkg.init() and Pkg.add() behind a corporate proxy. See below...

[31510:31508 - 0:1029] 01:16:24 [root@gb-slo-svb-0139:o +1] /opt $ julia
Version 0.5.0-dev
x86_64-redhat-linux
julia> Pkg.init()
INFO: Initializing package repository /opt/julia/lib/v0.5
INFO: Cloning METADATA from https://github.com/JuliaLang/METADATA.jl
ERROR: GitError(Code:ERROR, Class:OS, Failed to connect to github.com: Connection refused)
[inlined code] from libgit2/error.jl:98
in clone at libgit2/repository.jl:189
in __clone#364__ at libgit2.jl:310
in anonymous at pkg/dir.jl:49
in cd at file.jl:47
in init at pkg/dir.jl:47
in init at pkg.jl:22
in eval at ./boot.jl:263

julia>
[31510:31508 - 0:1030] 01:16:32 [root@gb-slo-svb-0139:o +1] /opt $ cd /tmp/
[31510:31508 - 0:1031] 01:16:38 [root@gb-slo-svb-0139:o +1] /tmp $ git clone https://github.com/JuliaLang/METADATA.jl
Cloning into 'METADATA.jl'...
remote: Counting objects: 52190, done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 52190 (delta 3), reused 0 (delta 0), pack-reused 52178
Receiving objects: 100% (52190/52190), 6.68 MiB | 3.47 MiB/s, done.
Resolving deltas: 100% (13081/13081), done.
[31510:31508 - 0:1032] 01:16:52 [root@gb-slo-svb-0139:o +1] /tmp $

I've tried the git config --global https.proxy <comeproxy> and also git config --global url."git://".insteadOf https://" , i've tried configuring environment variables in the shell. I've even tried issuing Pkg.init() with the full url, replacing https with git or http. I'm a bit stuck at the moment. I can't see any reason why this shouldn't work behind our proxy.

Any ideas guys?

Cheers,

Morgan

Issue 2:
I'm seeing the following issue when trying to use Pkg.init() on a fresh build of master:

$ ./julia
_
_ _ _(_)_ | A fresh approach to technical computing
(_) | (_) (_) | Documentation: http://docs.julialang.org
_ _ _| |_ __ _ | Type "?help" for help.
| | | | | | |/ _` | |
| | |_| | | | (_| | | Version 0.5.0-dev+640 (2015-10-06 18:24 UTC)
_/ |\__'_|_|_|\__'_| | Commit 128f8c6 (0 days old master)
|__/ | x86_64-linux-gnu

julia> Pkg.init()
INFO: Initializing package repository /home/lkuper/.julia/v0.5
INFO: Cloning METADATA from https://github.com/JuliaLang/METADATA.jl
ERROR: GitError(Code:ERROR, Class:Net, SSL error: error:140E0114:SSL routines:SSL_shutdown:uninitialized)
[inlined code] from libgit2/error.jl:96
in clone at libgit2/repository.jl:185
in clone at libgit2.jl:303
in anonymous at pkg/dir.jl:49
in cd at file.jl:22
in init at pkg/dir.jl:47
in init at pkg.jl:23

I started seeing this after pulling and rebuilding to fix the libgit2 SSL certificate issue in #13399. I'm now seeing this error instead of the certificate error. There's more discussion on that bug.

This is on Ubuntu 14.04, and I have libssl-dev installed. I've already tried make -C deps distclean-libgit2. I even did a make distcleanall to make extra sure.

Before I deleted my ~/.julia/v0.5 directory (because I hoped that doing that and running Pkg.init() might solve the problem), I was seeing a similar error message from Pkg.update().

I'm also having the same problem on CentOS with openssl-devel installed.
Issue 1:
Environment

Windows build number: 18363.418
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

enter the "🛰" character into the terminal (you will need a patched version of conhost that has the emoji fix).

Expected behavior

Emoji should be rendered at full size.

Actual behavior

Emoji is rendered at half scale:

Issue 2:
Summary of the new feature/enhancement

Very often when I'm working on a project, I want to open multiple tabs in the same directory. For example, for a web React project, I might want one tab for npm start, another for npm test --watch, and probably keep another around for various console commands I want to run (like git). It'd be very convenient to cd into my project directory and then just hit Ctrl-T a few times to open up more tabs in that project directory.

Instead, each tab current seems to be opened in the normal "startingDirectory", which is %USERPROFILE% by default, so you have to cd into the desired working directory for every new tab.