WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Challenge Waypoint: Local Scope and Functions 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.

The code shown below should just print console.log() once, and pass the test.

However, when I run the code, the sandbox seems to execute twice.

I tested this by putting new statements in, and it's clear to me that the code is being executed twice for some reason.

I tried running the code at least 10 times, it's been executed twice every time.

My code:

function myFunction() {
var myVar = 'hello';
console.log(myVar);
}
myFunction();

// run and check the console
// myVar is not defined outside of myFunction

// now remove the console.log line to pass the test

Issue 2:
Challenge Waypoint: Clone an Element Using jQuery has an issue.

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

Please describe how to reproduce this issue, and include links to screenshots if possible.

Issue

I believe I've found bug in the phone simulation in Waypoint: Clone an Element Using jQuery:

I entered the code to clone target5 and append it to left-well, and now I see three target5 buttons in the phone simulator. FCC says my code is correct and advances me to the next challenge. The following challenges also show three target5 buttons:

Waypoint: Target the Parent of an Element Using jQuery

Waypoint: Target the Children of an Element Using jQuery

@qualitymanifest confirms this issue on his Linux box.

My code:

<script>
$(document).ready(function() {
$("#target1").css("color", "red");
$("#target1").prop("disabled", true);
$("#target4").remove();
$("#target2").appendTo("#right-well");
$("#target5").clone().appendTo("#left-well");
});
</script>

<!-- Only change code above this line. -->

<div class="container-fluid">
<h3 class="text-primary text-center">jQuery Playground</h3>
<div class="row">
<div class="col-xs-6">
<h4>#left-well</h4>
<div class="well" id="left-well">
<button class="btn btn-default target" id="target1">#target1</button>
<button class="btn btn-default target" id="target2">#target2</button>
<button class="btn btn-default target" id="target3">#target3</button>
</div>
</div>
<div class="col-xs-6">
<h4>#right-well</h4>
<div class="well" id="right-well">
<button class="btn btn-default target" id="target4">#target4</button>
<button class="btn btn-default target" id="target5">#target5</button>
<button class="btn btn-default target" id="target6">#target6</button>
</div>
</div>
</div>
</div>
Issue 1:
Do you want to request a feature or report a bug?

bug

What is the current behavior?

The following error is raised

"Warning: Unknown prop xmlns on svg tag

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/reactjs/69z2wepo/).

create an a component with and svg tag and set the xmlns attribute

What is the expected behavior?

No warning

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

15.2.0

Issue 2:
In Load Initial Data via AJAX it uses isMounted which doesn't exist for es6 classes. Not sure how to best update the example, but it should probably be changed. Maybe abort the jqxhr?
Issue 1:
I am following this guide on OS X:

https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/getting-started-guides/vagrant.md

I am able to run other vagrant's using the same provider.

$ ./cluster/kube-up.sh
Starting cluster using provider: vagrant
... calling verify-prereqs
Can't find the necessary components for the vmware_fusion vagrant provider, please fix and retry.

Issue 2:
The /etc/sysconfig/network-scripts/ifcfg-en33 configuration file declares a MAC address that does not match the one the device receives.

$ ./cluster/kube-up.sh
Starting cluster using provider: vagrant
... calling verify-prereqs
... calling kube-up
Using credentials: vagrant:vagrant
Bringing machine 'master' up with 'vmware_fusion' provider...
Bringing machine 'minion-1' up with 'vmware_fusion' provider...
==> master: Machine is already running.
==> minion-1: Cloning VMware VM: 'kube-fedora20'. This can take some time...
==> minion-1: Verifying vmnet devices are healthy...
==> minion-1: Preparing network adapters...
==> minion-1: Fixed port collision for 22 => 2222. Now on port 2200.
==> minion-1: Starting the VMware VM...
==> minion-1: Waiting for machine to boot. This may take a few minutes...
minion-1: SSH address: 172.16.156.131:22
minion-1: SSH username: vagrant
minion-1: SSH auth method: private key
minion-1:
minion-1: Vagrant insecure key detected. Vagrant will automatically replace
minion-1: this with a newly generated keypair for better security.
minion-1:
minion-1: Inserting generated public key within guest...
minion-1: Removing insecure key from the guest if its present...
minion-1: Key inserted! Disconnecting and reconnecting using new SSH key...
==> minion-1: Machine booted and ready!
==> minion-1: Forwarding ports...
minion-1: -- 22 => 2200
==> minion-1: Configuring network adapters within the VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown ens33

Stdout from the command:

ERROR : [/etc/sysconfig/network-scripts/ifdown-eth] Device ens33 has MAC address 00:0C:29:96:3F:2C, instead of configured address 00:0C:29:16:5F:2B. Ignoring.

Stderr from the command:
Issue 1:
This code:

try {
foo();
} catch(e) {
// do nothing
}

Compiles to this:

"use strict";

try {
foo();
} catch (e) {}

// do nothing

It's ok at all, except eslint. It's affecting no-empty rule.

Issue 2:
try {
// yo
} catch (err) {
// lol
}

becomes

"use strict";

try {} catch (err) {}
// yo
// lol
Issue 1:
We have a library of components for angular that we are currently migrating to Angular 2. We have a container that injects content using ng-content. We would like to have a child component that injects the parent if you nest it inside of the parent, like so:

<parent>
<child></child>
</parent>

This works beautifully in angular 2. However, since are in the process of migration, we would like to use the ngUpgrade adapter for this. The dependency injection seems to fail if the parent and child are specified in an angular 1 context. Any insights on this issue? Is this something that is going to be supported in the ngUpgrade adapter?

I have a working plunker that illustrates the problem:

http://plnkr.co/edit/9qb6ZK9SpJyrWoJDEFEj?p=preview

In both cases, the template includes a parent with the child transcluded/projected into it. The child tries to inject the parent and then calls a function on it when you press the button. The ng2 example works, but not the ng1/ngUpgrade version.

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

[x] bug report => search github for a similar issue or PR before submitting
[ ] 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

After implementing ControlValueAccessor to the component, ngOnInit can no longer set a default value for this.model. No matter what I do it does not update the component view or notify outside components of the change.

Expected behavior

ngOnInit would update the view and notify outside components of the change.

Minimal reproduction of the problem with instructions

Open console

Check the message (this is the default model set by ngOnInit

Check the pre elements in the template (you will see null for the component template and '' for the outside one), both of these should display {id: 0, name: 'Item 1'} but does not.

Demo:

https://plnkr.co/edit/gGCiYjcq70xaewn3n22F?p=preview

What is the motivation / use case for changing the behavior?

This is needed when writing custom form elements and you want a default value without having to set a default value in the outside model, the component should take care of that.

Please tell us about your environment:

OS X Sierra, using the latest Angular CLI version.

Angular version: 2.0.X

Fails on both 2.0.2 and 2.1.0

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

all

Language: [all | TypeScript X.X | ES6/7 | ES5]

typescript

Node (for AoT issues): node --version =
Issue 1:
When REQUESTS_CA_BUNDLE is defined, the CA certificate passed to requests.Session constructor is overridden when requests.Session.request is called.

Guilty method/lines:

https://github.com/psf/requests/blob/master/requests/sessions.py#L694-L710

Expected Result

I would expect for the priority to be:

requests.Session.request verify kwarg

requests.Session verify property

REQUESTS_CA_BUNDLE / CURL_CA_BUNDLE

Actual Result

As requests.Session.request verify kwarg was not set, it took the value from REQUESTS_CA_BUNDLE and only then requests.Session.verify was checked, but ignored, resulting in an invalid CA used (for that Session).

Related issue (in docker-py project) docker/docker-py#2433

System Information

$ python -m requests.help

{
"chardet": {
"version": "3.0.4"
},
"cryptography": {
"version": "2.7"
},
"idna": {
"version": "2.8"
},
"implementation": {
"name": "CPython",
"version": "3.7.4"
},
"platform": {
"release": "18.6.0",
"system": "Darwin"
},
"pyOpenSSL": {
"openssl_version": "1010103f",
"version": "19.0.0"
},
"requests": {
"version": "2.22.0"
},
"system_ssl": {
"version": "1000213f"
},
"urllib3": {
"version": "1.25.3"
},
"using_pyopenssl": true
}

Issue 2:
One would expect that when the caller explicitly asks to make unverified requests, then the REQUESTS_CA_BUNDLE environment variable doesn't affect it. The reality is different, however.

import os
import requests

os.environ['REQUESTS_CA_BUNDLE'] = 'asd.pem' # Must be an existing file

r = requests.get('https://self-signed.badssl.com/', verify=False)
print(r)
# Prints: <Response [200]>

session = requests.Session()
session.verify = False

r = session.get('https://self-signed.badssl.com/')
print(r)
# Fails: requests.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:749)
Issue 1:
not sure if it's too early to file bugs regarding experimental features?

Bug report

What is the current behavior?

webpack library.type "module" generates commonjs syntax (module.exports/require) for node.js builtins (when target is node) and for any module specified as external(s).

If the current behavior is a bug, please provide the steps to reproduce.

export { version } from "process";

export default {
entry: {
index: "./index.js",
},
experiments: {
outputModule: true,
},
// externals: ...
output: {
filename: "[name].js",
library: {
type: "module",
},
},
target: "node",
};

/***/ "process":
/*!**************************!*\
!*** external "process" ***!
\**************************/
/***/ ((module) => {

module.exports = require("process");;

/***/ })

What is the expected behavior?

I'd imagine that node builtins have to be either required on top of the file (outer module scope) or possibly dynamically import() ed.

Other relevant information:

webpack version: v5.22.0

Node.js version: v15.12.0

Operating System: macOS Big Sur

Additional tools: n/a

Issue 2:
Bug report

What is the current behavior?

Getting errors after updating to 5.19.0

Uncaught ReferenceError: __webpack_require__ is not defined

Uncaught (in promise) TypeError: c(...).Z is not a function

The compiled code is missing __webpack_require__

If the current behavior is a bug, please provide the steps to reproduce.

Here's a very minimal setup that reproduces this bug.

// webpack.config.js
const path = require("path");

module.exports = {
entry: {
app: "./src/app.js",
home: {
import: './src/home.js',
dependOn: 'app' // removing this line fixes it
}
},
output: {
path: path.resolve("./dist"),
},
optimization: {
runtimeChunk: "single",
},
};

// src/app.js
import("./test.js");

// src/log.js
export default function (msg) {
console.log(msg);
}

// src/test.js
import log from "./log";
log("Hi");

// src/home.js
import log from "./log";
log("Hi");

<script src="runtime.js"></script>
<script src="app.js"></script>
<script src="home.js"></script>

What is the expected behavior?

This error should not happen, it was working without errors on 5.18.0

Other relevant information:

webpack version: 5.19.0

Node.js version: v15.7.0

Operating System: macOS 11.2

Additional tools:
Issue 1:
I have a question regarding the new is_file_like function and its usage in IO functions like read_csv

This new change in pandas 0.20 breaks many codes which previously assume that a file-like object is just an object possessing read or write method.

Is there any specific reason we have to enforce such conditions?

When making such changes why we have to break the previous behaviors?

Issue 2:
related #6512, #6524, #6346

Update from @hayd I think these should reference _selected_obj rather than obj.

Looking through some others, looks these also ignore the selection

count #6570

corr #6570

cummax #6570

cummin #6570

cumsum #6570

cumprod #6570

describe #6570

fillna #6570

quantile #6570

head #6533

hist? the output is ok but the plots have all

ohlc? possibly fixed with #6570 (resample with ohlc is tested), should this method exist? see #6594

plot

rank #6570

tail #6533

filter, #6570 (tested in #6593)

resample, #6570

nth #6569

diff/shift, #6570

all/any #6570

ffill, #6570

pct_change #6570

idxmin/idxmax, #6570

dtypes #6570

apply #6570 (could be tested more / different paths?)

Aggregation functions like (they already kind of do, but they allow bad selections ie column names not in columns, may be sep issue?):

sum/max/min/median/mean/var/std/.. (not tested)

agg (not tested)

(these "work" with the described bug)

Atm selecting a column not in df doesn't raise:

it should raise a Key Error, #6578

what about iloc/loc/ix (current all disabled)?

iloc (very similar to head/tail)

loc/ix (maybe push off for now, this is pretty tricky)

iterate over all (whitelisted) functions to check they adhere to this

The column selection on a groupby object is being ignored when .quantile() is called. So it computes the quantile on all the (numeric) columns and returns the full DataFrame.

In [92]: t = pd.DataFrame(np.random.randn(10, 4)); t[0] = np.hstack([np.ones(5), np.zeros(5)])

In [95]: t.groupby(0)[[1, 2]].quantile() # shows other cols
Out[95]:
0 1 2 3
0
0 0 0.127152 0.108908 0.369601
1 1 -0.321279 0.265550 -0.382398

In [96]: t[[1, 2]].groupby(t[0]).quantile() # Should be equivalent to:
Out[96]:
1 2
0
0 0.127152 0.108908
1 -0.321279 0.265550

Seeing all these, I'm wondering if this is a bug or just how some of the methods are implementer. The docs don't mention anything about only supporting some methods though.

version: '0.12.0-883-g988d4be'
Issue 1:
Environment

Windows build number: Microsoft Windows [Versione 10.0.18362.900]
PowerToys version: 0.18.2
PowerToy module for which you are reporting the bug (if applicable): Power Toys

Steps to reproduce

Start PC with power toys with run on startup activated.

Expected behavior

In the past versions (before 0.18) after I gave it "run as admin" rights it never asked for those again-

Actual behavior

On every PC startup, there is the window asking if I want to start Power Toys.

Issue 2:
Environment

Windows build number: Microsoft Windows [Version 10.0.18363.815]
PowerToys version: v0.17.0
PowerToy module for which you are reporting the bug (if applicable): PowerToys Settings

Steps to reproduce

Install a previous version (I had v0.16.1)

Enable "Always run as administrator"

Update PowerToys

Expected behavior

In version 0.16.1 my PC would boot and PowerToys would load in the background

Actual behavior

Every time I boot my PC I get a UAC promt asking me if I'll grant PowerToys admin privileges
Issue 1:
According the [development setup] (https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup) I do the following:

clone vue repository

npm install

npm test

On npm run build -- vue.min.js && node test/e2e/runner.js "--env" "phantomjs" step

I get error:

vue@2.1.5 test:e2e C:\vue_github
> npm run build -- vue.min.js && node test/e2e/runner.js "--env" "phantomjs"

> vue@2.1.5 build C:\vue_github
> node build/build.js "vue.min.js"

Error: Could not load C:\vue_github\src\core/index (imported by C:\vue_github\src\entries\web-runtime.js): ENOENT: no such file or directory, open 'C:\vue_github\src\core\index'
at C:\vue_github\node_modules\rollup\dist\rollup.js:8833:10
at process._tickCallback (internal/process/next_tick.js:103:7)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
Starting selenium server... started - PID: 10820

[Commits] Test Suite
========================

Running: commits

Issue 2:
Versions

Vue.js = 2.0.2

Node.js = 6.9.1

NPM = 4.0.2

Windows 10

Steps to reproduce

Clone repo from GitHub

npm install

npm run build

or

Clone repo from GitHub

yarn install

yarn run build

What is Expected?

The expected behavior is that all versions of vue are build in the dist folder.

What is actually happening?

Error: Could not load C:\Development\github\vue\src\core/index (imported by C:\Development\github\vue\src\entries\web-runtime.js): ENOENT: no such file or directory, open 'C:\Development\github\vue\src\core\index'

at C:\Development\github\vue\node_modules\rollup\dist\rollup.js:8833:10

at process._tickCallback (internal/process/next_tick.js:103:7)

at Module.runMain (module.js:606:11)

at run (bootstrap_node.js:394:7)

at startup (bootstrap_node.js:149:9)

at bootstrap_node.js:509:3

Workaround

It appears that all imports that use the aliases defined in build/alias.js file do not work when the extension .js is not used. When .js is added to all imports, the build succeeds.
Issue 1:
Error:

error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'tried to get overflow intrinsic for non-int type', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/librustc_trans/trans/expr.rs:2358

stack backtrace:
1: 0x7f52af1682d2 - sys::backtrace::write::he3277a63d69f5b66QBA
2: 0x7f52af18e322 - panicking::on_panic::h2a4421d00c8eaa07jHJ
3: 0x7f52af0d4a69 - rt::unwind::begin_unwind_inner::hb49f4d2d01640667mnJ
4: 0x7f52ae7cefcc - rt::unwind::begin_unwind::h2680611462970500090
5: 0x7f52ae886c3d - trans::expr::with_overflow_check::h22ec817d39a9a5942nk
6: 0x7f52ae88535a - trans::expr::trans_eager_binop::h3675af8766a17880Yrj
7: 0x7f52ae861531 - trans::expr::trans_binary::h497e9acc1a254839iBj
8: 0x7f52ae84f381 - trans::expr::trans_unadjusted::h499460e0693ca7c136h
9: 0x7f52ae80fc37 - trans::expr::trans_into::he1bd2630274c6257Tph
10: 0x7f52ae8fbb6e - trans::_match::mk_binding_alloca::h16531623213959557454
11: 0x7f52ae80f0ed - trans::base::init_local::h4220d9153c798dbdGBs
12: 0x7f52ae8106a2 - trans::controlflow::trans_block::h24688e532ef957ffv7d
13: 0x7f52ae8cbf10 - trans::base::trans_closure::h0ab6c84c342248f8ent
14: 0x7f52ae7fff8b - trans::base::trans_fn::h365bd4f7574aa6067xt
15: 0x7f52ae7fbf36 - trans::base::trans_item::hfa9c20eef4d47c8aZVt
16: 0x7f52ae8d26bc - trans::base::trans_crate::h6a97e87f7f6b01f8aSu
17: 0x7f52af78cf92 - driver::phase_4_translate_to_llvm::h9b048c1a8eb1ea23gOa
18: 0x7f52af7688ea - driver::compile_input::h4ead3acd85265c84Nba
19: 0x7f52af82cebd - run_compiler::h297fa686def10927G6b
20: 0x7f52af82ac2c - thunk::F.Invoke<A, R>::invoke::h13212375243324058858
21: 0x7f52af829880 - rt::unwind::try::try_fn::h15556897595580953244
22: 0x7f52af1fa0f8 - rust_try_inner
23: 0x7f52af1fa0e5 - rust_try
24: 0x7f52af82a00b - thunk::F.Invoke<A, R>::invoke::h6333748217615269386
25: 0x7f52af17bb25 - sys::thread::thread_start::h14dbe992a2cfcf49t8E
26: 0x7f52a91cb181 - start_thread
27: 0x7f52aed4d47c - __clone
28: 0x0 - <unknown>

Code to reproduce:

#![feature(simd)]
use std::simd::u32x4;

#[inline(never)]
fn new(v: u32) -> u32x4 {
u32x4(v, v, v, v)
}

fn main() {
let x = new(1) + new(1);
}

Issue 2:
thread 'rustc' panicked at 'tried to get overflow intrinsic for non-int type', C

:\bot\slave\nightly-dist-rustc-win-64\build\src\librustc_trans\trans\expr.rs:235

2

Here is the code

#![feature(core)]

use std::simd::i16x8;

fn main() {
// create simd vectors
let x = i16x8(1, 2, 3, 4,1, 2, 3, 4);
let y = i16x8(4, 3, 2, 1,1, 2, 3, 4);

// simd product
let z = x * y;

// like any struct, the simd vector can be destructured using `let`
let i16x8(a, b, c, d,e,f,g,h) = z;

println!("{:?}", (a, b, c, d,e,f,g,h));
}
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Next.js dynamic imports should work with jest test suites.

Current Behavior

It is failing when we run the test with the following error.

TypeError: require.resolveWeak is not a function

Steps to Reproduce (for bugs)

Clone the repo https://github.com/PrudviGali/nextjs-dynamic-import-test-fail

npm install

npm run test

Your Environment

Tech
Version

next
4.1.3

node
6.9.1

OS
mac OS high sierra

browser
NA

etc
NA

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

Expected Behavior

Console no error

Current Behavior

React-hot-loader: fatal error caused by ƒ BasicLayout()

no instrumentation found. Please require react-hot-loader before React. More in troubleshooting.

Steps to Reproduce (for bugs)

Open the page

Use next/link to jump to other pages

Your Environment

Tech
Version

next
v5.0.0

node
v8.9.0

OS
macOS High Sierra version 10.13.3

browser
Chrome/64.0.3282.140