WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Challenge Target the Parent of an Element Using jQuery has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.

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

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. -->

<body>
<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>
</body>

The target5 button is cloned to the left-well but 2 times. This surely is a bug.

Issue 2:
Challenge Use jQuery to Modify the Entire Page has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.

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

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");
$("#target1").parent().css("background-color", "red");
$("#right-well").children().css("color", "orange");
$("#left-well").children().css("color", "green");
$(".target:nth-child(2)").addClass("animated bounce");
$(".target:even").addClass("animated shake");

});
</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:
Describe the workflow you want to enable

The Markov Chain is an algorithm that can generate data from data.

The idea of the Markov Chain was first published in 1906.

It fits SK-Learn's model of fit, predict/transform by fitting the data to a model, and then predicting a new sequence of data.

What I am looking for is the green light to go ahead with the implementation, in order to ensure the source code is organized properly, and to ensure there is no duplication.

Describe your proposed solution

I would like to implement the Markov Chain algorithm:

https://en.wikipedia.org/wiki/Markov_chain

My proposal is to provide it with a numpy array such as:

[
[1, 2],
[2, 3],
[3, 4],
]

So the training data is not limited to one dimensional data. I would like to implement the option to use one dimensional data for user simplicity. An example of 2 dimensional data would be when using music notes as the training data, each data point could be a vector containing the type of note (ex. half, whole, quarter) and the note itself (ex. A#2, C4).

To generate a sequence the user will provide a maximum length, or a stop condition (ex, element contains a 4, or element equals [3, 4]

The result of the predict would be the same format as the input.

Describe alternatives you've considered, if relevant

No response

Additional context

I have used Markov chains to generate music from a song, and to generate sentences from Lord of the Rings. I have implemented this algorithm twice (for one and two dimensional data).

Issue 2:
First off, I didn't find any mentioning of RFECV in the userguide.

Update: rest of this issue was fixed.
Issue 1:
Issue originally made by @taion

Bug information

Babel version: 6.11.4

Node version: 6.3.1

npm version: 3.10.3

Options

N/A

Input code

N/A

Description

From discussion on facebook/create-react-app#238:

This is the code of babel-runtime/helper/typeof.js:

"use strict";

exports.__esModule = true;

var _iterator = require("../core-js/symbol/iterator");

var _iterator2 = _interopRequireDefault(_iterator);

var _symbol = require("../core-js/symbol");

var _symbol2 = _interopRequireDefault(_symbol);

var _typeof = typeof _symbol2.default === "function" && typeof _iterator2.default === "symbol" ? function (obj) { return typeof obj; } : function (obj) { return obj && typeof _symbol2.default === "function" && obj.constructor === _symbol2.default ? "symbol" : typeof obj; };

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

exports.default = typeof _symbol2.default === "function" && _typeof(_iterator2.default) === "symbol" ? function (obj) {
return typeof obj === "undefined" ? "undefined" : _typeof(obj);
} : function (obj) {
return obj && typeof _symbol2.default === "function" && obj.constructor === _symbol2.default ? "symbol" : typeof obj === "undefined" ? "undefined" : _typeof(obj);
};

By contrast, the helper definition is:

(typeof Symbol === "function" && typeof Symbol.iterator === "symbol")
? function (obj) { return typeof obj; }
: function (obj) { return obj && typeof Symbol === "function" && obj.constructor === Symbol ? "symbol" : typeof obj; };

Similar things happen for other helpers like jsx.

It's counterproductive to actively pull in the polyfills here – doing so provides no additional functionality but increases bundle size for users for little reason.

Issue 2:
💻

Would you like to work on this feature?

What problem are you trying to solve?

Cannot use satisfies typescript operator because I need @babel/plugin-transform-typescript version 7.20 which is dependency of @babel/preset-typescript which was left behind on version 7.18 and not released as part of https://babeljs.io/blog/2022/10/27/7.20.0

Describe the solution you'd like

Update @babel/preset-typescript to use latest @babel/plugin-transform-typescript and release it.

Describe alternatives you've considered

.

Documentation, Adoption, Migration Strategy

.
Issue 1:
Migrated issue, originally created by Dave Hirschfeld

As detailed in GH#382 the dialects.mssql.TIMESTAMP class is a direct import of the sa.sql.sqltypes.TIMESTAMP class into the mssql namespace.

The fact that the mssql.TIMESTAMP class is the same as the sqltypes.TIMESTAMP class causes problems in a 3rd party library, odo which operates by mapping sqlalchemy types to the corresponding python/numpy types.

The reason this causes problem is that unlike the ANSI SQL TIMESTAMP the mssql.TIMESTAMP type doesn't represent a datetime object but is instead just a binary type which cannot be interpreted or converted to a datetime object.

This problem doesn't affect sqlalchemy itself because sqlalchemy emits the correct TIMESTAMP DDL and then simply passes through the results from the underlying driver.

With type(sqltypes.TIMESTAMP) == type(mssql.TIMESTAMP) being true there is no way for odo to distinguish the two types. Because one represents a Python datetime object and the other a byte string they need to be able to be distinguished and handled differently in odo.

A sufficient condition for odo to correctly handle MSSQL TIMESTAMP types is that the mssql.TIMESTAMP class does not inherit from the sqltypes.TIMESTAMP class - e.g.

def test_mssql_timestamp_is_not_timestamp():
"""The MSSQL TIMESTAMP type does *not* represent a datetime value
so should not inherit from the `sqltypes.TIMESTAMP` class

:ref: https://msdn.microsoft.com/en-us/library/ms182776%28v=SQL.90%29.aspx
"""
from sqlalchemy.sql import sqltypes
from sqlalchemy.dialects import mssql
assert not issubclass(mssql.TIMESTAMP, sqltypes.TIMESTAMP)

Issue 2:
Migrated issue, originally created by Dan Stovall

In MSSQL a ROWVERSION or TIMESTAMP column do not contain a date time. Instead the contain an 8-byte integer. Currently, the column is set as sqlachemy.sql.sqltypes.TIMESTAMP, which is an instance of the DateTime type. Running a query against a table with such a column returns a byte string value for those columns. The mssql dialect should probably have a specific ROWVERSION type and it should be an integer, not a DateTime. Also, it would be nice if the values of those columns returned an integer by using int.from_bytes to convert the byte string.
Issue 1:
VSCode Version: Version 0.10.11 (0.10.11)

OS Version: OS X 10.10.5

Steps to Reproduce:

Write code as screenshot below

Observe strange highlighting on variable names

Issue 2:
From @f111fei on February 23, 2016 6:14

version： 0.10.10

letter

Copied from original issue: microsoft/vscode#3270
Issue 1:
Hi Team, There is problem in Axios v1.1. Axios not respond with axios.get and axios.post. Please use previous version of axios for solve this problem.

Issue 2:
Describe the bug

My project is working strangely，I compare the current version with the previous one，The following code creates an BUG.

// version === 0.19.0
config = mergeConfig(this.defaults, config);

// version < 0.19.0
config = utils.merge(defaults, {
method: 'get'
}, this.defaults, config);

To Reproduce

Custom interceptors below:

const instance = axios.create({
...
});
instance.interceptors.request.use((opts) => {
// `options.mask` is undefined
if (options.mask) {
// show mask
}
});

// requst remote
instance( { url: '', mask: true } )

Expected behavior

customized options can be passed into the interceptor

Environment:

Axios Version [e.g. 0.19.0]

OS: [e.g. iOS 12.1.0, OSX 10.13.4]

Browser [e.g. Chrome, Safari]

Browser Version [e.g. 22]

Additional Library Versions [e.g. React 16.7, React Native 0.58.0]

Additional context/Screenshots
Issue 1:
As it said in this issue #3382

the PLYLoader does not support texture coordinates.

Is it still the same ?

code:

var loader = new PLYLoader()
loader.load(path,(geometry) => {
geometry.computeVertexNormals();

new THREE.TextureLoader().load( `${url}` (texture) => {
let material = new THREE.MeshStandardMaterial({
map: texture,
})

let mesh = new THREE.Mesh(geometry, material)
mesh.position.x = 0
mesh.position.y = 0
mesh.position.z = 0
mesh.rotation.x = -Math.PI / 2
mesh.scale.multiplyScalar(1.2)
mesh.castShadow = false
mesh.receiveShadow = false
this.scene.add(mesh)
this.camera.position.set(15, 15, 121)

this.preloaderRoot.querySelector('progress').setAttribute('value', '100')
this.preloaderRoot.style.display = 'none'
})
}, onProgress, onError)

three.js - 0.93.0

Chrome latest

macOs Sierra 10.12.6

screenshot of the result in attachment

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:
Description of the problem

Hello all, I've run into an issue where I have a series of promises concurrently calling TextureLoader.load, and occasionally the call simply doesn't appear to be triggering its success/failure callback, which leaves promises unresolved indefinitely.

I put together the most basic JSFiddle I could here:

http://jsfiddle.net/b7bbbLxz/14/

You'll need to pop open web inspector's console to see the logs, but in general you'll see 10 promises resolve with success, and the Promise.all subsequently resolve with success. This would be the expected, good behaviour.

However, sometimes one promise will hang without ever returning, and the whole call then hangs. You'll need to Run the fiddle manually to ensure the resources go through a full load. With 1-2 seconds between runs, the issue occurs every ~10-15 attempts. Running more quickly (i.e. right after the previous success message is shown), the issue occurs every ~3-4 attempts.

This all seems related to the latest release of Chrome as the code was working in previous versions, and other browsers do not seem to present the issue. In Firefox, I can hammer on the Run button non-stop and always get a successful resolve back.

The issue appears to be producible more reliably when throttling the network connection to 2G, but that is not required.

This may be related to #8666, but it's hard to tell. Not related.

I've attached an image of the console output that displays the issue. The arrow points at a subsequent Run after the previous Promise.all was hanging without getting to PROMISES SUCCESS.

##### Three.js version
- [x] Dev
- [x] r75
- [ ] ...
##### Browser
- [ ] All of them
- [x] Chrome
- [ ] Firefox
- [ ] Internet Explorer
##### OS
- [x] All of them
- [ ] Windows
- [ ] Linux
- [ ] Android
- [ ] IOS
##### Hardware Requirements (graphics card, VR Device, ...)

None
Issue 1:
TypeScript Version:

1.8.7

Code

interface Test {
field: {[key: string]: string};
}

var test: Test;
var foo = {qwerty: 'qwerty'};

test = {
field: foo
};

Expected behavior:

I don't see any errors.

Actual behavior:

I get the following error:

app\app.ts(46,1): error TS2322: Type '{ field: { qwerty: string; }; }' is not assignable to type 'Test'.

Types of property 'field' are incompatible.

Type '{ qwerty: string; }' is not assignable to type '{ [key: string]: string; }'.

Index signature is missing in type '{ qwerty: string; }'.

If I modify my code to this then I don't get an error

interface Test {
field: {[key: string]: string};
}

var test: Test;

test = {
field: {qwerty: 'qwerty'}
};

Issue 2:
Various libraries I use want to see dictionary "loops" that take some number of key/value pairs and operate on them. E.g.:

async.auto<any>({
'foo': (cb) => getFoo(cb),
'bar': ['foo', (cb, results) => getBar(results.foo)]
}, (err, results) => { ... });

The typings file for async likes to define helper dictionary types like this:

interface Dictionary<T> { [key: string]: T; }

Periodically, I need to create these key/value pairs conditionally and on the fly but the compiler yells at me if I try to send it in without explicitly typing my temporary object:

var block = {
'foo': (cb) => getFoo(cb),
'bar': ['foo', (cb, results) => getBar(results.foo)
}

if (flag) {
block.foo = getOtherFoo(cb);
}

async.auto<any>(block, (err, results) => { ... });

block now technically satisfies the { [key: string]: T; } because it is an object with two keys, both strings. TypeScript will still yell at me for it, though, unless I explicit add a similar dictionary type to block. I, therefore, find myself putting this dictionary type all over the place just to satisfy what seems to be an arbitrary distinction between what is or is not a key:string.

This comes up enough that I find the type bloat irritating and it also makes it a requirement to only access block.foo as block['foo'].
Issue 1:
Hi

When I open a git-controlled folder, and possibly change some settings, then Code creates a .vscode directory directly inside that folder, and stores files such as settings.json or launch.json in it.

That folder either has to be checked in or .ignored, which is OK on repos I control, but not OK on forked repos I want to contribute to for instance, which needs to stay clean.

Can't this data be stored in some Code own data folder?

Cheers

Issue 2:
Environment:

VS Code Version 0.10.9

Mac OS 10.10.5

Node.js v4.3.1

Steps to Reproduce:

Create a new directory named cluster-test

Create a new file cluster-test\app.js with sample code from https://nodejs.org/dist/latest-v4.x/docs/api/cluster.html#cluster_cluster as follows:

const cluster = require('cluster');
const http = require('http');
const numCPUs = require('os').cpus().length;

if (cluster.isMaster) {
// Fork workers.
for (var i = 0; i < numCPUs; i++) {
cluster.fork();
}

cluster.on('exit', (worker, code, signal) => {
console.log(`worker ${worker.process.pid} died`);
});
} else {
// Workers can share any TCP connection
// In this case it is an HTTP server
http.createServer((req, res) => {
res.writeHead(200);
res.end('hello world\n');
}).listen(8000);
}

Open cluster-test in VS Code

Switch to the Debug view and click the Start icon, or press F5

Select "Node.js" as the debug environment

Click Start again

Point you browser to http://localhost:8000/

Observe that no one is listening

Exit VS code, open a command prompt and invoke:

node cluster-test\app.js

Point you browser to http://localhost:8000/

Observe that a "hello world" response is received

Conclusion:

Basic node cluster example fails in VS Code
Issue 1:
Bug Report

Current Behavior

The code below causes a Duplicate declaration "values" error.

Input Code

REPL or Repo link if applicable: https://babeljs.io/repl/build/master#?babili=false&browsers=&build=&builtIns=false&spec=false&loose=false&code_lz=MYGwhgzhAECC0G8BQ1oGIBGAKAlM1qIApgC7QBuYIArkRANwrQC-Tawu-BxZlNdjVK2ZA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=false&fileSize=false&timeTravel=false&sourceType=script&lineWrap=true&presets=stage-3&prettier=false&targets=&version=7.2.0&envVersion=

class A {
#b(){
let values;
}
#c(){
let values;
}
}

Expected behavior/code

The variables should not conflict as they are in different scopes.

Babel Configuration (.babelrc, package.json, cli command)

{
presets: ['@babel/preset-env','@babel/preset-react'],
plugins: [
'@babel/plugin-proposal-object-rest-spread',
'@babel/plugin-proposal-private-methods',
'@babel/plugin-proposal-class-properties',
]
}

Environment

Babel version(s): v7.2.1

Node/npm version: Node 10, npm 6.4.1

OS: Windows 10

Monorepo: [e.g. yes/no/Lerna]

How you are using Babel: gulp-babel

Issue 2:
In Babel 5, it was possible to do this:

() => {
console.log("test");
}();

However, this is no longer possible in Babel 6 - it gives an "unexpected token" error. Instead, I have to wrap the function as an expression:

(() => {
console.log("test");
})();

I'm transpiling with the following Gulp task:

var gulp = require("gulp");
var browserify = require("browserify");
var buffer = require("vinyl-buffer");
var source = require("vinyl-source-stream");
var sourcemaps = require("gulp-sourcemaps");

gulp.task("js", function() {
var bundler = browserify("src/app.js")
.transform("babelify", {
presets: ["es2015"]
});

return bundler.bundle()
.on("error", function(err) {
console.error(err);
this.emit("end");
})
.pipe(source("app.js"))
.pipe(buffer())
.pipe(sourcemaps.init({ loadMaps: true }))
.pipe(sourcemaps.write("./"))
.pipe(rename("dist/app.js"))
.pipe(gulp.dest("./"));
});

This script works fine with everything else, as long as I wrap my self-calling arrow functions in brackets. Is this intentional, or is this a regression?
Issue 1:
Any thoughts on what might be driving this error and causing the build to fail? I installed the latest version of Visual Studio Community and tried running it from the VS command prompt as well.

python script\build.py -c D

ninja: Entering directory `out\D'
[339/1062] CC obj\vendor\node\deps\openssl\openssl\crypto\dso\openssl.dso_win32.obj
electron\vendor\node\deps\openssl\openssl\crypto\dso\dso_win32.c(289) : warning C4055: 'type cast' : from data pointer 'void *' to function pointer 'DSO_FUNC_TYPE'
[723/1062] CC obj\vendor\node\deps\openssl\openssl\crypto\whrlpool\openssl.wp_block.obj
electron\vendor\node\deps\openssl\openssl\crypto\whrlpool\wp_block.c(87) : warning C4164: '_rotl64' : intrinsic function not declared
[918/1062] CXX obj\atom\common\crash_reporter\electron_lib.crash_reporter.obj
FAILED: ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\bin\amd64\cl.exe" /nologo /showIncludes /FC @obj\atom\common\crash_reporter\electron_lib.crash_reporter.obj.rsp /c ..\..\atom\common\crash_reporter\crash_reporter.cc /Foobj\atom\common\crash_reporter\electron_lib.crash_reporter.obj /Fdobj\electron_lib.cc.pdb
electron\atom\common\crash_reporter\crash_reporter.cc(49) : error C2440: '<function-style-cast>' : cannot convert from 'const std::string' to 'base::FilePath'
No constructor could take the source type, or constructor overload resolution was ambiguous
[918/1062] CXX obj\atom\common\electron_lib.platform_util_win.obj
ninja: build stopped: subcommand failed.

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 a feature request that matches the one I want to file, without success.

Electron Version

12.x, 13.x, 14.x

What operating system are you using?

Windows

Operating System Version

Windows 10

What arch are you using?

x64

Last Known Working Electron version

11.x

Expected Behavior

Printing with silent: true should allow us to select a printer though deviceName.

Actual Behavior

Prints using Windows default printer opposed to the one we assigned it to.

Testcase Gist URL

No response

Additional Information

This is technically a "duplicate" as it has been reported before. But since this now affects every supported version of Electron projects cannot move forward with an upgrade if they depend on this feature. In our case it's point of sale system software and our ability to easily maintain a wide range of receipt printers. We strive to make sure all dependencies are the latest with proper security fixes. This and since new versions of Electron will start to trigger the bot to mark the duplicates as outdated/closed I felt like this merited a new issue. Apologies if not the case.