WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Bug report

What is the current behavior?

Error in dynamic import

Module parse failed: 'import' and 'export' may only appear at the top level (45:8)
You may need an appropriate loader to handle this file type.

ngAfterViewInit() {
import('./df.tinymce.files')
.then(() => {

What is the expected behavior?

Until version 4.29.0 this was working as expected, it's only with this version that this error happens

Other relevant information:

webpack version: v4.29.0

Node.js version: v11.7.0

Operating System: mac

Additional tools: ts 3.2.2

Issue 2:
Do you want to request a feature or report a bug?

Feature Request

What is the current behavior?

When webpack --watch is first run, the first thing it does it compile all of the entries.

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

What is the expected behavior?

For webpack to simply start watching the files and not immediately compile. But given that this doesn't apply as much to single-entry instances, at least have an option for it.

If this is a feature request, what is motivation or use case for changing the behavior?

Given the number of entries (and if sourcemaps are enabled) this can can take a significant amount of time. With this feature one would be able to enable watching and immediately get to work without having to worry about whether it's finishing compiling and is actually watching, yet.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

Node: 4.5.0

Webpack: 2.6.1

OS: Windows 10
Issue 1:
Is there an api that can be require ed from node to compile file. eg

var ts = require('typescript');
ts.compile(filePath, {options}, function(err, js) {
//etc
})

Issue 2:
I'm trying to use generic class in the TSX file and generic class is implemented in the another module. I have tried to use code like in the #3960 (comment) but it doesn't work because old style casting is not allowed in the TSX file. Ok, I have changed it to the as operator but it emits incorrect code. It refers to the generic class directly without using require.

After that I have created simple example without JSX which demonstrates that old style casting and as operator are different.

File generic.ts: export default class Generic<T> {}

File sample.ts:

import Generic from "./generic";
type Ctor = new() => Generic<number>;
const x = Generic as Ctor;

Compile tsc sample.ts --module commonjs. Result:

var generic_1 = require("./generic");
var x = Generic;

As you see generic_1 variable isn't used at all and undeclared Generic variable is assigned to x.

Workaround:

import Generic from "./generic";
type Ctor = new () => Generic<number>;
const x = Generic;
const y = x as Ctor;

Also please note that using old-style casting also helps:

import Generic from "./generic";
type Ctor = new() => Generic<number>;
const x = <Ctor>Generic;

So it looks like it is the problem in the as operator only.
Issue 1:
Code Sample

import os
import sys
import tempfile

import pandas as pd
from urllib.request import urlretrieve

# Settings
p_ext = 'https://ftp.ncbi.nlm.nih.gov/gene/DATA/gene_info.gz'
p_down = os.path.join(tempfile.gettempdir(), 'tmp_gene_info.gz')
p_out = os.path.join(tempfile.gettempdir(), 'tmp_gene_info.h5')

# Notify about usage of version of python and pandas, where error occurred
if sys.version.startswith('3.6.0 '):
print('You are using the same python version, where the problem occurred.')

if pd.__version__ == '0.19.2':
print('You are using the same pandas version, where the problem occurred.')

# Download dataset where error occurred
urlretrieve(p_ext, p_down)

# Get dataframe
df = pd.read_table(p_down, sep='\t', header=0)
df = df.drop_duplicates(['#tax_id', 'GeneID'])

# Attempt to save as Hdf5
# A process where kernel would die, approx. 2 seconds after memory usage
# approaches the limit of my machine (62GB out of 64GB)
df.to_hdf(
p_out,
'table',
mode='w',
append=True,
data_columns=['#tax_id', 'GeneID'])

Problem description

Kernel dies while exporting DataFrame to HDF5. This death occurs on two different machines of mine. The error occurs both, in iPython notebooks, and when running the script through command line.

I have not been facing problems with df.to_hdf on any other (and smaller) DataFrames (or subsets of the given DataFrame), which suggests that there might be some problem with the specific data set.

Prior to the death of the kernel, RAM usage shoots up to around 62GB of 64GB. Thus I am not sure, if my issue relates to some bug, or whether it would be a request for the implementation of a low-memory fall-back.

Expected Output

The DataFrame would become saved as an HDF5 file.

Output of pd.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.0.final.0
python-bits: 64
OS: Darwin
OS-release: 16.4.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8

pandas: 0.19.2

nose: 1.3.7

pip: 9.0.1

setuptools: 27.2.0

Cython: 0.25.2

numpy: 1.11.3

scipy: 0.18.1

statsmodels: 0.6.1

xarray: None

IPython: 5.1.0

sphinx: 1.5.1

patsy: 0.4.1

dateutil: 2.6.0

pytz: 2016.10

blosc: None

bottleneck: 1.2.0

tables: 3.3.0

numexpr: 2.6.1

matplotlib: 2.0.0

openpyxl: 2.4.1

xlrd: 1.0.0

xlwt: 1.2.0

xlsxwriter: 0.9.6

lxml: 3.7.2

bs4: 4.5.3

html5lib: None

httplib2: None

apiclient: None

sqlalchemy: 1.1.5

pymysql: None

psycopg2: None

jinja2: 2.9.4

boto: 2.45.0

pandas_datareader: None

Issue 2:
we have a Categorical section, but this mainly describes .cat. Maybe split this out into a separate section to document the actual Categorical methods / accessors (even though it is slightly duplicative.

http://pandas-docs.github.io/pandas-docs-travis/api.html#categorical

also need to add other public methods (that are not available on .cat). This is actually a big list, things like:

isnull, unique, map, value_counts, etc.

These are all Series like methods / accessors.
Issue 1:
Ability to add snippets from .vscode directory, instead of %APPDATA%/Roaming/Code/User/snippets.

This would be nice for working with snippets in a specific project, then there is no need to create a snippet extension for private snippets, and install it separately because it's included in the project

Issue 2:
VSCode Version: all

OS Version: all

We have a custom set of snippets written per-project and would like to include them in the project repo, like our launch.json, tasks.json. Right now we just include the json file and the dev has to copy+paste it into his user snippets, but the snippets are particular to a project, not to all projects.

Also it would be great to have a way to define what extensions a developer should have installed to work on the project. We use several code quality and styling plugins to enforce our custom rules and it would be nice if there was a project definition file to suggest installation of the extensions we define.
Issue 1:
While debugging a memory problem I found something that looks like temporaries from
previous scopes are sometimes not garbage collected.

In this case disabling compiler optimizations got rid of the leak.

I tried to strip down the problem as much as possible:
http://play.golang.org/p/HR-7R_0f-C

go version: tip (321d42ff40d3)

Issue 2:
If we can get some indication of the compiler or toolchain version into the build ID hash, it would let people flip between different toolchains with the same GOPATH more easily. In particular, when you flipped it would notice that all the things in $GOROOT/pkg are out of date and rebuild them, whereas today you have to use go install -a or else you get object version conflicts from the compiler and/or linker.

[Please do not close this as a duplicate of some other issue. This one describes what I plan to do.]
Issue 1:
Version

2.5.17

Reproduction link

https://jsfiddle.net/onbzk0m6/

Steps to reproduce

Just load the vue instance. See link to reproduction.

What is expected?

whitespace character

Text: " Drehmaschinen"

What is actually happening?

a string with &nbsp;

Text: "&nbsp;&nbsp;&nbsp;Drehmaschinen"

If you remove the vuejs code or change the 'el' attribute, it will work.

Issue 2:
Version

2.6.14

Reproduction link

codepen.io

Steps to reproduce

1.qtwebengine (navigator.userAgent :Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.6.3 Chrome/49.0.2623.111 Safari/537.36)

2.vue version (2.6.14)

3. someTimes click event not working (Open QT for a long time.)

What is expected?

work fine

What is actually happening?

When click event not working, we found something:

at "vue/src/platforms/web/runtime/modules/events.js" lines 70: e.timeStamp >= attachedTimestamp is false
Issue 1:
Is this captured in the metadata database already and just a matter of surfacing it in the API call, or is it not captured outside of the segments themselves?

Issue 2:
Storing aggregatorFactories in segment metadata will make it possible to reindex existing segments without having to provide the original aggregators out-of-band. As a bonus, it would also be nice to store the QueryGranularity used for indexing. This isn't required for reindexing, since it would work fine to use QueryGranularity.NONE, but it would still be cool.
Issue 1:
From @alefragnani on November 4, 2015 1:12

Is there a correct way to replace core commands?

(of course, if this is something that is available or in the roadmap)

My intention is to create an extension to replace Edit / Copy (editor.action.clipboardCopyAction) and Edit / Cut (editor.action.clipboardCutAction) commands. So, when there is no selection, the Copy/Cut would use the current word instead of the entire line.

About coding, I can:

Determine the word based on the cursor position

Select the word

Execute vscode.commands.executeCommand("editor.action.clipboardCopyAction")

Remove the selection, returning the cursor to its initial position.

But I was wondering if there is something else that I could (or couldn't) do, like defining the keybindings in package.json to Ctrl + C / Ctrl + X; or define vscode.commands.registerCommand for the core command, with my own code.

Thanks in advance

Copied from original issue: Microsoft/vscode-extensionbuilders#79

Issue 2:
Currently, reopen files behaviour is slightly weird. If no folders are open, no files are reopened upon restart of VSC. If a folder is open, any files that are opened, inside the opened folder or not, are reopened upon restart of VSC.

I would like to see VSC reopen files, regardless the opened folder count. Should probably be settable in the preferences, I can imagine not everyone is interested in this behaviour.
Issue 1:
Tried memory allocation debugging with --track-allocation=user and --track-allocation=all with version 0.3.4 and 0.4: Problem – *.mem files not written out for user source code on Windows 7. *.mem files written out only for Julia core files.

Issue 2:
I'm working at packaging entire Julia packages repository for the Nix package manager. One of things that might help me very much is packages' dependencies information. Right now I'm parsing REQUIRES files by myself to make Nix packages -- that's an unfortunate code duplication given that somewhere inside pkg we already have code which does exactly the thing. I imagine this as some function dependencies(pkg :: String) -> Requirement[].
Issue 1:
Currently, downloaded dependencies seem to be stored with the scheme $DENO_DIR/deps/$PROTOCOL/$ORIGIN/$CHECKSUM. I use neovim and coc-deno, and when I jump to definition, I’m sent to these cached files. My current problem is that I don’t get syntax highlighting because for my editor, this works based off file extension. I could probably fix this problem myself with editor configuration but it would be nice if DENO added file extensions so that the cached path was something like $DENO_DIR/deps/$PROTOCOL/$ORIGIN/$CHECKSUM.$EXTENSION.

The big thing I’m thinking about is what the file extension should be. If Deno only intends to store javascript/typescript files in the cache, then maybe .jsx? or .tsx? would suffice? Or maybe Deno could use an algorithm like: check if the URL path has an extension and use that, otherwise, check if the response has a Content-Type header and use the related canonical file extension, otherwise don’t use a file extension.

Issue 2:
The current cache filenames and layout is unfortunate.

It breaks code navigation. Code for the Deno runtime can only be written in editors that implement the workarounds to locate the files.

The workarounds required are non-trivial for editors like vim.

Files are extension-less which breaks a lot of editors (no syntax highlighting, etc) such as VSCode.

Editor tab bars are rendered useless. Open these files for viewing in an editor and you have tabs with names like "b7953a2fe90b56defc2c4cbba3f7f8b963cf2a38e587d20c3ffcd11e95f4fb64"

#4183

As I suggested in #4069 (comment), the file names need to be more descriptive.

All cached files should have an extension. I would suggest TSX for compatibility.

The hash should be prefixed with a descriptive name.

The proposed filename format is:

"[stripped-file-basename]_[hash].[appended-extension-from-content-type]"

Example

yaml_b7953a2fe90b56defc2c4cbba3f7f8b963cf2a38e587d20c3ffcd11e95f4fb64.tsx
Issue 1:
Bug report

What is the current behavior?

Requiring or importing a json file starting with a byte order mark \ufeff, commonly added by Microsoft editors, in webpack 4 causes the following error:

Unexpected token ﻿ in JSON at position 0

webpack 3 handles this though.

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

https://github.com/gatimus/webpack-json-bom/tree/webpack-4

npm start

What is the expected behavior?

https://github.com/gatimus/webpack-json-bom/tree/webpack-3

npm start

Other relevant information:

webpack version: 4.8.3

Node.js version: 8.11.1

Operating System: Win 10

Issue 2:
Bug report

What is the current behavior?

Requiring or importing a json file starting with the zero length, white space character, byte order mark (\ufeff), commonly added by Microsoft editors, in webpack 4 causes the following error:

Unexpected token ﻿ in JSON at position 0

webpack 3 handles this with out error though.

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

https://github.com/gatimus/webpack-json-bom/tree/webpack-4

clone https://github.com/gatimus/webpack-json-bom

checkout branch webpack-4

npm i

npm start

Unexpected token ﻿ in JSON at position 0

What is the expected behavior?

https://github.com/gatimus/webpack-json-bom/tree/webpack-3

clone https://github.com/gatimus/webpack-json-bom

checkout branch webpack-3

npm i

npm start

no errors

Other relevant information:

webpack version: 4.8.3

Node.js version: 8.11.1

Operating System: Win 10

I don't know how webpack 3 handles it but calling .trim() or .replace('\ufeff', '') on the file contents before passing to JSON.parse() would solve.
Issue 1:
Atom is updating fine but 'Help' > 'Release Notes' gives me an old stale version with an active restart and update button.

First time I installed Atom was 2-3 months ago before auto-updating was added (direct, not through chocolatey) so that could potentially be a clue. Haven't tried a complete nuke and re-install yet.

Atom 0.174.0 at Win 8.1 64bit

Issue 2:
I use Atom on two different machines and I'm seeing anomalies when looking at the release notes. On one of my machines the release notes are always blank with only a button showing to view previous release notes. On the other machine the release notes are old. Here is a current screenshot but keep in mind this isn't the only time the release notes have been outdated compared to the release I was using.

Currently using Atom 0.136 on Windows 8.1 (on two different systems).
Issue 1:
The [src] link at http://static.rust-lang.org/doc/master/std/prelude/index.html

points to http://static.rust-lang.org/doc/master/src/std/home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libstd/lib.rs.html#99

instead of http://static.rust-lang.org/doc/master/src/std/home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/libstd/prelude.rs.html

Just a small issue I noticed. I hope reporting it helps!

Issue 2:
The source link for Any links to the module declaration in lib.rs instead of the more useful file, any.rs.
Issue 1:
Challenge filter-arrays-with-filter has an issue.

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

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

var oldArray = [1,2,3,4,5,6,7,8,9,10];

// Only change code below this line.

var newArray = oldArray.filter(function(val){
return val < 6;
});

```

Issue 2:
Challenge filter-arrays-with-filter has an issue.

User Agent is: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.

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

Using the code below and it should be working but getting error message: "You should only be using filter to make the new array." I have searched and this is the correct code so I don't know what the problem is..

var oldArray = [1,2,3,4,5,6,7,8,9,10];

// Only change code below this line.

var newArray = oldArray.filter(function(val) {
return val <= 5;
});

```
Issue 1:
There are a lot of parts of CSS that are reused in multiple properties, that get duplicated in the XML file, leading to code bloat and risk of inconsistencies.

The most obvious one are the colour keywords which are repeated 42 times in css-scheme.xml alone (and there are a lot of colours!, and they're included in other files on top), but there are others such as border-style values (that are in column-rule, etc.), timing functions (transitions, animations, etc)

Some things already are reused, such as the length units, and hsla,rgba, etc. Would be nice to expand this.

Issue 2:
see #3817 (comment)
Issue 1:
System information (version)

OpenCV => 4.1.0

Operating System / Platform => Ubuntu

Compiler => g++

Detailed description

OpenCV should have a feature to select the number of CPU cores used for inference when using OpenVINO inference engine as backend.

Right now, this can be only achieved using OpenVINO IE API.

In op_inf_engine.cpp file at

https://github.com/opencv/opencv/blob/master/modules/dnn/src/op_inf_engine.cpp

function

void InfEngineBackendNet::initPlugin(InferenceEngine::ICNNNetwork& net)

can accept the number of CPU cores (num_cores) parameter when DNN_TARGET_CPU is selected.

This can be further passed as

std::map cpu_config<std::string, std::string>
cpu_config[InferenceEngine::PluginConfigParams::KEY_CPU_THREADS_NUM]=std::string(num_cores)
netExec = plugin.LoadNetwork(net, cpu_config);

Issue 2:
System information (version)

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

Steps to reproduce
Issue 1:
The bug

Let's say I have these two files

foo.ts

export default class Foo { }

bar.ts

import Foo from './foo';
let foo = new Foo();

If I compile these files with

tsc -t es6 -m commonjs foo.ts bar.ts

I get this output

foo.js

class Foo {}
exports.Foo = Foo;

bar.js

var foo_1 = require('./foo');
let foo = new foo_1.default();

Obviously this code will not work.

Solutions

converting module type to ES6, this seems to be the definite solution

converting imports to import * as Foo from './foo' this fixes the produced code but show this error during compile

bar.ts(3,11): error TS2351: Cannot use 'new' with an expression whose type lacks a call or construct signature.

Confusion

Above code works without any workaround when targetting ES5. Is this the intended behavior? If so, shouldn't this be documented somewhere? Also instead of producing a code that does not work, maybe it should just say

commonjs modules cannot be used when targeting ES6

Sorry if this was already reported or was already documented.

Issue 2:
Using typescript@next and the following compiler options:

"compilerOptions": {
"target": "ES6",
"module": "commonjs",
}

A class expression being default exported will be incorrectly compiled into a named export instead.

Example:

export default class Foo {}

compiles into:

class Foo {
}
exports.Foo = Foo;
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-use-clockwise-notation-to-specify-the-margin-of-an-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

Last paragraph of instructions reads: "Use Clockwise Notation to give an element a margin of 40px on its top and left side, but only 20px on its bottom and right side."

But only changing the margin of the green box validates. So the sentence should be changed to: "Use Clockwise Notation to give the green box a margin of 40px on its top and left side, but only 20px on its bottom and right side."

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-use-clockwise-notation-to-specify-the-margin-of-an-element has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

The challenge has words:

Use Clockwise Notation to give _an element_ a margin of 40px on its top and left side, but only 20px on its bottom and right side.

But green-box is required. It should be:

Use Clockwise Notation to give _the ".green-box" class_ a margin of 40px on its top and left side, but only 20px on its bottom and right side.

Disclamer: English is not my native language. I could be wrong.
Issue 1:
Environment

Windows build number: [run "ver" at a command prompt] [Version 10.0.18362.657]
PowerToys version: PowerToysSetup-0.16.0-x64
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce Editing

After editing Zones, applied layout selected (doesn't mater if predefined or custom) nothing happens. Tried to uninstall PowerToys via Programms and features, runs through the steps and explorer restarts before it completes - PowerToys never gets removed

Expected behavior

Actual behavior

Screenshots

Issue 2:
Environment

Windows build number: 10.0.18363.752
PowerToys version: 0.16.0
PowerToy module for which you are reporting the bug (if applicable): FanzyZones

Steps to reproduce

Use Remote Desktop session, FanzyZones is no longer working.

Expected behavior

FanzyZones to work for remote desktop sessions.

Actual behavior

FanzyZones not working for remote desktop sessions.

Screenshots

[not applicable]