WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Can VScode inherit cold folding from Visual Studio:

Normal:
On Hover:

and having the fold on the same line like this:

Issue 2:
I would like to see more options with code folding and with bracket matching.

It seems the user base is quite split on how they want the collapsed region to display, so I think this should be a user configuration setting along with the other features listed.

Feature Requests

Collapse fold to a single line Related#2 Alternative Designs#1

Bracket anchors/leads/lines seen in pictures #2 and #3 + Related#2 Alternative Designs#2

Peek at top bracket when hovering the bottom bracket pictures #3 This should only happen when the top matching bracket isn't visible on the current viewport.

Highlight current region. In pictures #1 and #2 it highlights the current block you're on

Collapse block from bottom bracket. In pictures #1 and #3 you can collapse a block region from the lower bracket which can be really nice, it can be a quick way to see what the bracket belongs to w/o feature request #3

Picture examples

Single line collapse

Anchor / leads / lines

Peek at top bracket

Related

Collapse to same line #3352

Icons for folding #2948

Labels

editor

editor-folding

feature-request
Issue 1:
Summary

Installing TypeScript 1.7 tooling for Visual Studio causes different behaviour from 1.6 when publishing web applications, both from within Visual Studio (right click > publish) and via msbuild.exe (/p:DeployOnBuild=true).

This issue has only been observed using a file system publish.

Symptoms

Generated JavaScript is no longer included in the packaged / published output.

Observations

It appears there is a difference in the MSBuild Content ItemGroup's metadata. I believe that previously the generated JavaScript files were being included in the Content ItemGroup as paths relative to the .csproj file:

Scripts\App.js

As of 1.7 it appears the generated JavaScript files are now being included in Content as absolute paths:

C:\Projects\Solution\Web\Scripts\App.js

Perhaps this is causing a problem for the web publishing mechanism?

Issue 2:
TypeScript 1.4 allows variables to be used before they are initialized.

For example, both:

function dd(): number {
var x: number;
return x;
}

and

function ddd() {
var x: number;
x++;
}

are allowed.

It would be useful to have a compiler flag such as --noUseBeforeInit that would turn variable use before initialization into an error.

This suggestion fits in with #274 meta-bug.
Issue 1:
Why was the dedup plugin deprecated? Without it my build is several kb larger.

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

Feature! 🎉

What is the current behavior?

(This is gonna be a bit longer.)

Let’s imagine working on a project using WebWorkers. Let’s say I am using this great new shiny library Comlink. It’s needed by both main.js and worker.js as Comlink is an abstraction over postMessage. Of course both main.js and worker.js have other dependencies besides Comlink.

(You might already be able to tell where I’m going with this)

Attempt 1: Entry points

Listing both worker.js and main.js as entry points doesn’t yield the expected results as all static imports will be inlined. Comlink will be (down)loaded twice. The semantics of entry points are that only one entry point will be loaded at a time. In the context of my example, though, two entry points are loaded in parallel.

Attempt 2: Dynamic loading

I tried some hackery with import(), but the problem is that WebPack (rightly) assumes that there’s is a global registry of loaded modules. worker.js, however, runs in a different realm and has a separate global scope to main.js

Workaround: Force a common chunk

My current workaround is to use the entry point approach and manually maintain a list of shared modules that need to be put in a separate chunk using CommonChunksPlugin:

module.exports = {
entry: {
main: './src/main.js',
worker: './src/worker.js',
},
output: {
filename: '[name].js',
},
plugins: [
// Force comlink into its own bundle
new webpack.optimize.CommonsChunkPlugin({
name: 'comlink',
minChunks: 2,
}),
],
};

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

What is the expected behavior?

Under the assumption that there’s good caching headers, the optimal behavior is to put Comlink in it’s own chunk (or a chunk for shared modules) so it’s only downloaded once. The second request by the worker will hit the HTTP cache and re-use the already downloaded shared chunk.

API

I’m not sure what the API for this would look like. This API would not only be useful for workers, but also for pages that load another entry point in an iframe (although, tbh, I struggle to find a good example for this 🤷‍♂️ )

I think the most straight-forward way would to add a realmEndpoints (name pending lol) to the webpack config which lists entry points that can be loaded in parallel to one of the main entry points.

What do y’all think? API suggestions/corrections? Am I just holding it wrong?

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

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Issue 1:
NOTE: Only file GitHub issues for bugs and feature requests. All other topics will be closed.

For general support from the community, see StackOverflow.

To make bugs and feature requests more easy to find and organize, we close issues that are deemed

out of scope for GitHub Issues and point people to StackOverflow.

For bugs or installation issues, please provide the following information.

The more information you provide, the more easily we will be able to offer

help and advice.

Currently trying to run tensorflow android code downloaded from Github facing following error

Error:Execution failed for task ':buildNativeMake'.

A problem occurred starting process 'command 'tensorflow/contrib/makefile/build_all_android.sh''

Environment info

Operating System: 64 bit

Android Studio : 2.3

Bazel: 0.3.0

python: 3.5

JDK: 8

Please get back to us today ASAP

Thanking you in advance.

build_gradle.txt

Issue 2:
NOTE: Only file GitHub issues for bugs and feature requests. All other topics will be closed.

For general support from the community, see StackOverflow.

To make bugs and feature requests more easy to find and organize, we close issues that are deemed

out of scope for GitHub Issues and point people to StackOverflow.

For bugs or installation issues, please provide the following information.

The more information you provide, the more easily we will be able to offer

help and advice.

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?

Environment info

Operating System:

Installed version of CUDA and cuDNN:

(please attach the output of ls -l /path/to/cuda/lib/libcud*):

If installed from binary pip package, provide:

A link to the pip package you installed:

The output from python -c "import tensorflow; print(tensorflow.__version__)".

If installed from source, provide

The commit hash (git rev-parse HEAD)

The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)

What other attempted solutions have you tried?

Logs or other output that would be helpful

(If logs are large, please upload as attachment or provide link).
Issue 1:
System info

Playwright Version: [v1.XX]

Operating System: [All, Windows 11, Ubuntu 20, macOS 13.2, etc.]

Browser: [All, Chromium, Firefox, WebKit]

Other info:

Source code

I provided exact source code that allows reproducing the issue locally.

Link to the GitHub repository with the repro

[https://github.com/your_profile/playwright_issue_title]

or

Config file

// playwright.config.ts
import { defineConfig, devices } from '@playwright/test';

export default defineConfig({
projects: [
{
name: 'chromium',
use: { ...devices['Desktop Chrome'], },
},
});

Test file (self-contained)

it('should check the box using setChecked', async ({ page }) => {
await page.setContent(`<input id='checkbox' type='checkbox'></input>`);
await page.getByRole('checkbox').check();
await expect(page.getByRole('checkbox')).toBeChecked();
});

Steps

[Run the test]

[...]

Expected

[Describe expected behavior]

Actual

[Describe actual behavior]

Issue 2:
Context:

In Page Object Model, I would create a page object like this

import { Locator, Page } from '@playwright/test';

export class PlaywrightDevPage {
readonly page: Page;
readonly getStartedLink: Locator;

constructor(page: Page) {
this.page = page;
this.getStartedLink = page.locator('text=Get started');
}

async goto() {
await this.page.goto('https://playwright.dev');
// duplicate selector appearence
await this.page.waitForSelector(''text=Get started'');
}
}

Because Locator.isVisible() does not wait for the element to become visible and returns immediately, I have to use waitForSelector method. But there is no supported function like page.waitForSelector(locator: Locator) or page.waitForLocator(locator: Locator) or Locator.waitUtil(state: State).
Issue 1:
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

importing parts of material-ui should be available from the top level folder

Current Behavior

The following list produces a typescript error ".../material-ui/index has no exported member "

InputAdornment (I believe this has already been resolved) #8959

Theme

StyleRulesCallback

TableFooter

TablePagination## Your Environment

Tech
Version

Material-UI
@next

React
16.2.0

Issue 2:
For each color palette (primary, accent, error, etc.), we have to either use default material design hues or provide our own. This requires a set of 15 hues. It is not clear to me (and so far haven't been able to find it here or in the docs, or on material.io) which hue is used in which context.

For example, why is A400 used here ?

It would be helpful to understand why and where hues are used, to make customization easier.

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

Tech
Version

Material-UI
next
Issue 1:
Open some directories in tree view

Creating a new file or folder on the root path, or delete a root folder

All open directories collapse

Expected: everything stays open

Issue 2:
If we plan to deprecate the space pen View class, we need a story for what folks can move to. Some kind of system that interoperates with custom elements. Something that UI heavy packages like settings view and fnr can use.

Maybe it looks like space pen (space-pencil)?

Maybe it's react?

We need to do more thinking.
Issue 1:
When I use ColumnTransformer to preprocess different columns (include numeric, category, text) with pipeline, I cannot get the feature names of the final transformed data, which is hard for debugging.

Here is the code:

titanic_url = ('https://raw.githubusercontent.com/amueller/'
'scipy-2017-sklearn/091d371/notebooks/datasets/titanic3.csv')

data = pd.read_csv(titanic_url)

target = data.pop('survived')

numeric_columns = ['age','sibsp','parch']
category_columns = ['pclass','sex','embarked']
text_columns = ['name','home.dest']

numeric_transformer = Pipeline(steps=[
('impute',SimpleImputer(strategy='median')),
('scaler',StandardScaler()
)
])
category_transformer = Pipeline(steps=[
('impute',SimpleImputer(strategy='constant',fill_value='missing')),
('ohe',OneHotEncoder(handle_unknown='ignore'))
])
text_transformer = Pipeline(steps=[
('cntvec',CountVectorizer())
])

preprocesser = ColumnTransformer(transformers=[
('numeric',numeric_transformer,numeric_columns),
('category',category_transformer,category_columns),
('text',text_transformer,text_columns[0])
])

preprocesser.fit_transform(data)

preprocesser.get_feature_names() will get error:

AttributeError: Transformer numeric (type Pipeline) does not provide get_feature_names.

In ColumnTransformer，text_transformer can only process a string (eg 'Sex'), but not a list of string as text_columns

Issue 2:
#6372 adds get_feature_names to PolynomialFeatures. It accepts a list of names of input_features (or substitutes with defaults) and constructs feature name strings that are human-readable and informative. Similar support should be available for other transformers, including feature selectors, feature agglomeration, FunctionTransformer, and perhaps even PCA (giving the top contributors to each component). FeatureUnion should be modified to handle the case where an argument is supplied. A proposal for support in Pipeline is given in #6424.

Modelled on #6372, each enhancement can be contributed as a separate PR. Note that default names for features are [x0, x1, ...]

PolynomialFeatures @amueller #6372

feature selection and randomized L1 @yenchenlin1994

feature agglomeration @yenchenlin1994

FunctionTransformer @nelson-liu #6431

scalers, normalizers and imputers: should be trivial like FunctionTransformer #6431

Binarizer #6431

OneHotEncoder #6441

FeatureUnion @yenchenlin1994

PCA?

SparseRandomProjection?

GaussianRandomProjection??

other transformers?
Issue 1:
can expose 'cv::partition' function to Java?

I download OpenCV 4.1(Win pack) and install it on my Windows-10 64 Bit.

I want to use it in my Java program but 'partition' function is not in java wrapper.

Issue 2:
can expose 'cv::partition' function to python?

OpenCV => 3.4.1(python-opencv)

Operating System / Platform => Windows 64 Bit

Compiler => Visual Studio 2015
Issue 1:
Version

2.6.8

Reproduction link

https://codesandbox.io/s/54v49n1nzn

Steps to reproduce

The repro shows the issue directly.

<Child
v-bind="{
appleColor: 'objective red',
bird: 'objective sparrow'
}"
:apple-color="`proper red`"
:bird="`proper sparrow`"
/>

What is expected?

I wanted to know what takes precedence when something is bound using v-bind={} vs set explicitly as a prop. I would expect this to always be one or the other, or to be resolved in order of declaration as when merging objects in JS ({...boundProps, specificProp })

What is actually happening?

The precedence is determined based on whether a prop has multiple words. duplicate keys are set by the object when they are declared in dash-case, and set by the prop/attribute if they are camelCase or a single word.

This can be made 'consistent' by declaring multiword props using camelcase, but that's against the recommendations in the styleguide which suggest using dash case for multiword props inside templates: https://vuejs.org/v2/style-guide/#Prop-name-casing-strongly-recommended.

I ran into this when an undefined value bound to a parent was overriding the same value explicitly set in the child, but it wasn't happening consistently depending on what the names of the props were.

Issue 2:
Version

2.6.11

Reproduction link

https://jsfiddle.net/pvzkc51t/4/

Steps to reproduce

open the jsfiddle.

wait page loaded.

input some charactor in element.

see the console.

What is expected?

nothing in console.

What is actually happening?

"Why should I update" outputs in console.

$attrs and $listeners appeared to reduce workload.

But they occur with form element will cause component update catastrophically.

Event though nothing change in $attrs.
Issue 1:
As you can see in the image bellow, If we go on with the example of the Hoizontal Form and don't have the checkbox, then the button will render without margins and ugly.

But if we have the checkbox, it will render good.

Why don't have something like button class for divs? (Same as what we have in the example for checkbox):

<div class="checkbox">
<label>
<input type="checkbox"> Remember me
</label>
</div>
<button type="submit" class="btn btn-default">Sign in</button>

Issue 2:
In the horizontal form example (http://getbootstrap.com/css/#forms-horizontal) everything looks great because the checkbox div has 10 pixels of top and bottom margin.

However, if you delete the checkbox div then the button is right up against the text field. Unless you have a checkbox or radio button at the end of your form it will not look very nice without adding custom styling.
Issue 1:
Original ticket http://projects.scipy.org/scipy/ticket/768 on 2008-10-31 by @pbrod, assigned to unknown.

The generalized pareto cumulative distribution in standard form [1]_ is defined as:

F(x;c) = 1-(1-c*x)**(1/c) for c>0 and c<0

where c is the shape parameter.

The limiting case as c->0 is the exponential cdf defined as

F(x;c=0) = 1-exp(-x)

and is not implemented in the scipy.stats.distributions.genpareto distribution.

To add this limiting case to scipy.stats.distributions.genpareto would

greatly simplify statistical analysis. Through inference on the shape parameter, c, the data themselves determine the most approprate type of tailbehavior and there is no need for making subjective a priori judgement of which individual extremevalue family to adopt.

.. [1] Stuart Coles (2000),

"An Introduction to Statistical Modeling of Extreme Values"

Issue 2:
As discussed here https://github.com/scipy/scipy/pull/337/files#r2227022 , Numpy's rfftn is not included in SciPy.

However, SciPy's version of rfft (2 real results per frequency bin) behaves differently from numpy's (1 complex result per frequency bin), so it may be confusing to just import it side-by-side.

In an old discussion, most people seem to agree that numpy's rfft output is superior:

[Numpy-discussion] rfft different in numpy vs scipy, Sep 11 2006

especially because that format matches the format for complex fft and works for N-dimensions, while SciPy's does not:

the reason why FFTW's r2c routines produce unpacked output is largely because "packed" formats do not generalize well to multi-dimensional FFTs, while the "unpacked" format does.

Does it make sense to replace Scipy's rfft with numpy's? Or to rename it or make its output behavior an option, with numpy's behavior as default?

Illustration:

In [1]: a = [9, -9, 1, 3]

In [2]: numpy.fft.fft(a)
Out[2]: array([ 4. +0.j, 8.+12.j, 16. +0.j, 8.-12.j])

In [3]: numpy.fft.rfft(a)
Out[3]: array([ 4. +0.j, 8.+12.j, 16. +0.j])

In [4]: numpy.fft.rfftn(a)
Out[4]: array([ 4. +0.j, 8.+12.j, 16. +0.j])

In [5]: scipy.fftpack.fft(a)
Out[5]: array([ 4. +0.j, 8.+12.j, 16. +0.j, 8.-12.j])

In [6]: scipy.fftpack.rfft(a)
Out[6]: array([ 4., 8., 12., 16.])

Other confused people:

Why does scipy.fftpack.rfft return real values? (SO, 2016)

Python scipy.fftpack.rfft frequency bin mapping (SO, 2014)

Python scipy.fftpack.rfft frequency bin mapping (DSP.SE, 2014)

[SciPy-user] Numpy/Scipy rfft transformations do not match?, Feb 28 2009

How should I multiply scipy.fftpack output vectors together? (SO, 2013)
Issue 1:
I don't know if this is a known issue and supposed to be this way, but I find it a little bit annoying.

If you are on a small laptop screen and for example scroll through the components page there are a few sections where you can't reach the lower half of the navigation on the left side, simply because with all the subsections of the current section there are to many items to display to fit onto the screen and there is no way to scoll on the navigation itself.

If this is a stupid issue and meant this way, simply close this issue ;-)

Issue 2:
When you display some item that has a lot of subitems, the nav grows so much that it doesn't fit on some resolutions, and some of the items aren't shown.

http://oi43.tinypic.com/2ivjtyv.jpg

On that screenshot, nav items are shown up to badges, missing the remaining. I've tested it on latest Firefox and Chrome at 1366x768.
Issue 1:
I'm submitting a ... (check one with "x")

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

To share CSS common to all components in an angular2 app, we have to currently Add a to a stylesheet with all the common CSS in the application's index.html (or add the styles to the application's root component and turn off view encapsulation for each component that wants to share this CSS? - not sure if this option works)

Expected behavior

A well-documented and recommended way to share CSS across components - whether one of the current options above, or a newer option that makes it easier to add root-level CSS to share among components.

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

Ease of use, trying to share CSS among components now involves lots of trial and error and stack overflow-ing for me right now, without knowing the pros/cons of each method.

Please tell us about your environment:

All

Angular version: 2.0.0-rc.X

2.0.0 final

Issue 2:
I'm submitting a ...

[x] feature request

Expected/desired behavior

Introduce a way to bundle css with the help of NgModules (see #9726). These styles would only be usable/scoped to the components inside the NgModules.

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

Sharing styles between multiple components is currently not supported out of the box. The user either has to insert these styles globally into the head, or copy them into each component's individual stylesheet. Both of these solutions are problematic.
Issue 1:
Environment

Windows build number: Microsoft Windows [Version 10.0.18362.836]
PowerToys version: 0.18.1
PowerToy module for which you are reporting the bug (if applicable): PowerToys Run

Steps to reproduce

Set the default shortcut to Alt + Space. Press Alt + Space to open the PowerToys Run

Expected behavior

Expecting the PowerToys Run to open the quick launcher

Actual behavior

Pressing Alt + Space on any active window brings the window's context menu. Not having any active window open does not do anything

Note

PowerToys Run works on v0.18.0

Screenshots

Issue 2:
Environment

Windows build number: [Version 10.0.18362.836]
PowerToys version: v0.18.1
PowerToys: PowerToys Run

Steps to reproduce

With PowerToys installed and running, press Alt + Space from any screen.

Expected behavior

PowerToys Run popup shows up to start typing a command or a search term

Actual behavior

window menu (Restore / Move / Size / Minimize / Maximize / Close) shows up in the top left corner of the focused window if the focus is on a window or nothing at all if the focus is on the desktop.

Screenshots
Issue 1:
I'm seeing an issue in Chrome 58.0.3029.83 on Android 7.0.0 where the visible viewport is getting clipped.

Here's: https://threejs.org/examples/#webgl_animation_cloth

And https://threejs.org/examples/#webgl_camera:

My own application is also exhibiting this problem:

Some other examples are fine however:

https://threejs.org/examples/#webgl_clipping

https://threejs.org/examples/#webgl_loader_obj

Unable to discern the difference between these cases...

Three.js version

Dev

r85

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android

iOS

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

Nexus 6 phone

Issue 2:
Hey Three.js team,

I found this weird bug that I thought you might find interesting.

When I attempt the cloth animation three.js example (https://threejs.org/examples/#webgl_animation_cloth) on this tablet in Chrome, it only shows a small part of the rendered canvas.

(What it looks like on device)

(What it looks like normally)

I debugged this a little bit. When setSize is usually called, it edits a _canvas variable, which usually adjusts the screen immediately after being set. However, in Chrome on this device this does not happen. To make a weird case even weirder, this example actually works on mobile Firefox on the same device.

Is this something that can be fixed from inside three.js, or is this something to developers of WebGL have to address?

Thanks so much!

Three.js version

Dev

r85

...

Browser

All of them

Chrome

Firefox

Internet Explorer

OS

All of them

Windows

macOS

Linux

Android 7

iOS

Hardware requirements for the device are right here: https://www.cnet.com/products/sony-xperia-z4-tablet-sgp771-tablet-android-6-0-marshmallow-32-gb-10-1-3g-4g/specs/ (however, I tested this on Android 7, not 6)