WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
There is a big difference between default git tags and annotated ones (-a): default tags are mere pointers without their own authorship etc. practical implication for me:

$> git describe origin/0.14.X
0.4-12969-gc9ba2c3
$> git describe --tags origin/0.14.X
0.14a1-20-gc9ba2c3

Cheers

Issue 2:
Describe the issue linked to the documentation

One difficulty that I had in the past while using, for example, GridSearch or RandomizedSearch for hyperparameter tuning is which range of values seems reasonable to be used in the search for each different classifier or regressor (principally for the numeric parameters). I always need to google examples of parameter ranges to use in the grid search and it is not always easy or obvious to find.

Suggest a potential alternative/fix

Adding a suggestion of the ranges of each parameter (principally the numeric ones) in the user guide that could give some initial guidance to the user in the grid search.
Issue 1:
Describe the workflow you want to enable

Allow passing trained models to VotingClassifier, and use these trained models directly for prediction, without refitting.

The current VotingClassifier requires fitting all inputted estimators on the given training data, even if these estimators have already been trained. This is inconvenient if we want to create an ensemble classifier from estimators trained with different datasets (or with different partitions of the dataset).

Describe your proposed solution

Maybe adding a new prefit parameter to VotingClassifier, allow the user to specify whether fitting is needed.

A similar solution has been implemented in #22215 for StackingClassifier and StackingRegressor

Additional context

This workflow is also mentioned in #12297, as there seems to be no update, here I am requesting it as a new feature.

This feature can be implemented at the user-level, code from stackoverflow, mors

from sklearn.ensemble import VotingClassifier
from sklearn.preprocessing import LabelEncoder

clf_list = [clf1, clf2, clf3]

eclf = VotingClassifier(estimators = [('1' ,clf1), ('2', clf2), ('3', clf3)], voting='soft')

eclf.estimators_ = clf_list
eclf.le_ = LabelEncoder().fit(y)
eclf.classes_ = seclf.le_.classes_

# Now it will work without calling fit
eclf.predict(X,y)

If this feature is approved, I can work on it.

Issue 2:
I work on python 3.6.5 and sklearn 0.19.1 on conda 4.5.11.

According to this post, I am surprised that voting classifiers do not accept prefix classifiers.

May I know is it because it is unnecessary from your respective or it was purely short of hand?

Thank you very much.
Issue 1:
When I change the select option, the two way binding do not work in Firefox 44.0.2

Sample: https://angular.io/resources/live-examples/forms/ts/plnkr.html

It's working fine on Chrome.

Issue 2:
I'm seeing an issue in beta.1 that appears to be a regression from beta.0. ngModel/ngModelChange don't appear to work at all in Firefox, at least on selects. Here's a plunkr demo. You'll notice if you change the script src's to beta.0, the selects work as expected. Is there a breaking change that I'm missing? I don't see anything about ngModel/ngModelChange in the changelog.

import {Component} from 'angular2/core';

@Component({
selector: 'my-app',
template: `
<h1>ngModel/ngModelChange not working on Firefox</h1>
<select [ngModel]="name" (ngModelChange)="changed($event)">
<option value=""></option>
<option *ngFor="#n of names" [value]="n">{{n}}</option>
</select>
<pre>Name: {{name}}</pre>

<select [(ngModel)]="name">
<option value=""></option>
<option *ngFor="#n of names" [value]="n">{{n}}</option>
</select>
<pre>Name: {{name}}</pre>
`
})
export class AppComponent {
names: String[] = ['Alpha', 'Bravo', 'Charlie'];
name: string;

changed(event) {
this.name = event;
}
}
Issue 1:
Copy issue by @zhonshu from microsoft/vscode-react-native#199

renderPhotosList = () => { if (this.state.showSelectPhotos) { } }

'property declarations' can only be used in a .ts file.

(property) MainPage. renderPhotosList: () => JSX.Element

in ES6 function bind this

Issue 2:
From @nwehrle on February 9, 2016 21:17

I use eslint to lint my jsx files. Before I switched to salsa, the linting inside the editor worked fine. After switching to salsa the linting fails inside the editor.

Salsa is enabled:

Linting from the shell still works without any errors or warnings.

I expect vscode to not show any linting errors.

System:

OSX 10.11.2

vscode 0.10.8

db71ac615ddf9f33b133ff2536f5d33a77d4774e

jsconfig.json:

{
"compilerOptions": {
"target": "ES6",
"module": "system",
"experimentalDecorators": true
},

"exclude": [
"node_modules"
]
}

User settings:

{
"javascript.validate.enable": false,
"editor.tabSize": 2,
"files.trimTrailingWhitespace": true,
// Migrated from previous "File | Auto Save" setting:
"files.autoSave": "onFocusChange"
}

Partial eslintrc:

"rules": {
"func-names": 0,
"no-unused-expressions": 0,
"id-length": 0,
"no-multi-spaces": 0,
"no-mixed-spaces-and-tabs": 2,

"no-unused-vars": [1, {"vars": "all", "args": "none"}],
"react/jsx-uses-react": 1,
"react/prop-types": 0,
"no-console": 0
},
"plugins": [
"react"
]

Copied from original issue: microsoft/vscode#2866
Issue 1:
Q
A

Bug report?
no

Feature request?
yes

BC Break report?
no

RFC?
no

Symfony version
3.2.1

I use a form field using snake_case, while I use camelCase for the property name (and for the getter and setter method for this property) in the model.

When the form is submitted, the data is mapped to the model properties:

the PropertyPathMapper uses the PropertyAccessor to set the value. The PropertyAccessor uses a camelize() method to find getters and setters for the property.

But when a validation error occurs on such a property, it is not mapped back to the form field, because the ViolationMapper compares the camelCased propertyPath of the model property with the snake_cased propertyPath of the form field.

This may not be a bug, and people should not use a form field with another name than the property, (when not explicitly using the property_path option of the form field).

But I find it confusing that the mapping used for changing the model based on the form data works, but mapping the validation errors back to the form field does not.

Issue 2:
Hi.

Today I searched two hours for the reason why one validation error wasn't shown at the form field but at the root form.

My form builder class looked like that:

public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder->add('xfade', 'integer', array('required' => false));
}

My validation.yml looked like that:

Streamserver:
properties:
xFade:
- Range: { min: 0, groups: [ Default ] }

The validation error of the property xFade wasn't mapped to the form field xfade and that error was hard to find, because the value of the field was mapped correctly to the entity of course.

One possible solution would be:

When mapping violation to form child (in Symfony\Component\Form\Extension\Validator\ViolationMapper\ViolationMapper->matchChild()) do a case-insensitive comparison.

But maybe there are better ways.
Issue 1:
We use an asset file to configure some feature inside our app.

So during test, we tried to access to it but we keep getting this error.

The getter 'buffer' was called on null.
Receiver: null
Tried calling: buffer
dart:core Object.noSuchMethod
package:flutter/src/services/asset_bundle.dart 148:29 CachingAssetBundle._fetchString
===== asynchronous gap ===========================
package:flutter/src/services/asset_bundle.dart 142:50 CachingAssetBundle.loadString.<fn>
dart:collection _HashVMBase&MapMixin&&_LinkedHashMapMixin.putIfAbsent
package:flutter/src/services/asset_bundle.dart 142:27 CachingAssetBundle.loadString

I know that assets are not available during test, but can you at least return null if no assets ?

An other possibility would be to provide assets before test like tester.provideAsset(name, asset);

Issue 2:
Its kind of a no-brainer that you might want to validate your assets in some way. Especially when you have multiple people working on the same project (not all of them developers). Furthermore its common to want to test the code that processes those assets, without having to hardcode versions of the assets in the tests, that might not match up with the live assets as they change through time. Finally of course, there is testing widgets that use the asset bundle, and need valid assets from it to behave properly.

#8490 seems to confirm that reading assets during test is not possible.
Issue 1:
From the docs:

Returns
-------
out : ndarray
Contiguous array of same shape and content as `a`, with type `dtype`
if specified.

But

>>> a = np.array(1)
>>> a.shape
()
>>> np.ascontiguousarray(a).shape
(1,)

Since its implementation is

return array(a, dtype, copy=False, order='C', ndmin=1)

Issue 2:
Proposed new feature or change:

Note - Developer Only change

I have been working with Gitpod maintenance for a while now and It often requires me to test the builds with different dependencies types and configurations.

For safe measure I create myself a new Unix host and do my testing there.

It always requires me to do the setup steps documented here over and over again.

Link for the Setup Steps

It would be great if the setup process could be automated with all the software dependencies that will be required.

I wanted suggestions from the community if this is a good idea (To have an automated shell script) to have this?

Secondly

To have a shell script for numpy redevelopment only , having the steps of

git clean -xdf

python setup.py build_ext --inplace

pip install -e .

[OPTIONAL BUILDING DOCS]

cd doc

make html

It would be great to have the community opinion on this, If this is worth pursuing and having.
Issue 1:
C:\Users\iamsh>deno upgrade

Looking up latest version

============================================================

Deno has panicked. This is a bug in Deno. Please report this

at https://github.com/denoland/deno/issues/new.

If you can reliably reproduce this panic, include the

reproduction steps and re-run with the RUST_BACKTRACE=1 env

var set and include the backtrace in your report.

Platform: windows x86_64

Version: 1.28.1

Args: ["deno", "upgrade"]

thread 'main' panicked at 'called Result::unwrap() on an Err value: Error("unexpected character '<' while parsing major version number")', cli\tools\upgrade.rs:306:62

note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Issue 2:
I was trying to upgrade my deno version.

RUST_BACKTRACE=1 deno upgrade

output:

Looking up latest version

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: macos x86_64
Version: 1.28.3
Args: ["deno", "upgrade"]

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("unexpected character '<' while parsing major version number")', cli/tools/upgrade.rs:304:62
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: core::result::Result<T,E>::unwrap
4: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
5: deno::main::{{closure}}
6: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
7: deno_runtime::tokio_util::run_local
8: deno::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Issue 1:
System information (version)

OpenCV => 4.x / 3.x

Operating System / Platform => ALL

Compiler => ALL

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

Remove lena images samples from the project.

Initially reported at https://bugzilla.redhat.com/show_bug.cgi?id=1295173

Reference:

https://lintian.debian.org/tags/license-problem-non-free-img-lenna.html

Steps to reproduce

checkout the source code samples pictures.

Issue submission checklist

I report the issue, it's not a question

I checked the problem with documentation, FAQ, open issues,

answers.opencv.org, Stack Overflow, etc and have not found solution

I updated to latest OpenCV version and the issue is still there

There is reproducer code and related data files: videos, images, onnx, etc

Issue 2:
System information (version)

OpenCV => 4.3.0

Operating System / Platform => Fedora/Debian

Detailed description

The lena images have been determined by Debian and Fedora to not be distributable and must be removed from source tarballs which is a pain to deal with. Could a suitable alternative image be found? Thanks.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Eventually this is related to #9433 , but i'm not sure.

Expected Behavior

Snapshots should succeed when nothing was changed.

Current Behavior

Whenever introducing a new withStyles() Component or simply updating material-ui to the latest beta our jest test fails due to things like:

- className="MuiTypography-root-104 MuiTypography-body1-113"
+ className="MuiTypography-root-111 MuiTypography-body1-120"
// or
- className="MuiExpansionPanelSummary-content-169"
+ className="MuiExpansionPanelSummary-content-176"

basically the appended number changes.

Steps to Reproduce (for bugs)

Sorry I think there is no easy sandbox reproduction possible.

Context

We switched to material-ui from our existing global-css/deterministic className solution where we were able to easily snapshot components and check if they were altered. Now it seems like we have to adjust our setup, but I don't now how.

Your Environment

Tech
Version

Material-UI
basically all the v1 beta branches since we started using it (~8+)

React
16

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

Expected Behavior

Tab indicator should dynamically resize its width when the parent container width changes

Current Behavior

Tab indicator doesn't resize when the parent container width changes ~ only when the viewport size does

When parent container size changes:

What it should look like / what it looks like after triggering a re-render:

Steps to Reproduce (for bugs)

Create a container with a child tab element in it (fullwidth)

Resize the parent container programmatically (not by changing the viewport)

Context

I'm using the tabs in a appbar using the persistent drawer layout, opening / closing the menu breaks the tab indicators until a manual re-render

Your Environment

Tech
Version

Material-UI
1.0.0-beta.20

React
15.5.4

browser
Chrome 63.0.3239.59
Issue 1:
Problem description

MaxLength works fine for input="text" but it doesn't for input="number". I imagined that max="" would work in this case, but that didn't work either.

Steps to reproduce

Versions

Material-UI:

React:

Browser:

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

Expected Behavior

Click on disabled TextField in IE11 (Internet Explorer 11.873) not activate underline animation

Current Behavior

Click on disabled TextField in IE11 (Internet Explorer 11.873) activate underline animation

Steps to Reproduce (for bugs)

Go to the link in IE 11

Click on disabled TextField

Look at the bug

Your Environment

Tech
Version

Material-UI
v1.0.0-beta.23

React
16.1

browser
Internet Explorer 11.873

etc
Windows 10
Issue 1:
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

I'm testing a service that we're connecting with HTTP. I wanted to make sure that not-ok responses (non 200 status), are dealt with correctly.

So I've setup a test with a MockBackend. In this tests, I've setup the response to respond with an error Response:

const response = new Response(new ResponseOptions({
url: 'url',
status: 500,
body: {
error: 'Shit hit the fan'
}
}));

backend.connections.subscribe((connection: MockConnection) => {
connection.mockRespond(response);
});

Unfortunately, the MockBackend seems to behave different from the actual Http implementation. The actual Http implementation will throw an error when receiving an non-200 response while the MockBackend simply passes the Response along.

This is demonstrated by:

http.get('url').subscribe((response) => {
console.log('incorrectly passed the response in a subscribe');
}, (error) => {
console.log('correctly subscribed to', error);
});

This always logs "incorrectly passed the response in a then".

I could change the configuration of the backend to respond with an error connection.mockError(response); but this function expects an Error rather than a Response

Expected behaviour

I would expect the response to be passed to the error callback.

Note that I'm using angular 4.1.0 with typescript 2.2.0.

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

Test Repo - https://github.com/mildfuzz/angular-mockError

I am unable to test predicted HTTP error responses. Mockbackend can either send a response with an error code (which my app treats as a successful response in the test environment, but as an error in real world)

I am unable to send status codes with an error response in my tests, so I can not test any error handling my application might implements.

Expected behavior

at least one of the defined test cases passes

Minimal reproduction of the problem with instructions

Test Repo - https://github.com/mildfuzz/angular-mockError

this is a re-opening of issue #7471, which was closed due to lack of repro steps.

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

To be able to test all responses

Please tell us about your environment:

OsX

Angular version: 2.0.X

Angular 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 ]

Chrome 54

Language: TypeScript 2.0.3

Node (for AoT issues): node --version = 6.9.1
Issue 1:
Environment

Windows build number: [run "ver" at a command prompt] Microsoft Windows [Version 10.0.19041.329]
PowerToys version: 0.19.0
PowerToy module for which you are reporting the bug (if applicable):

Steps to reproduce

Set "Open PowerToys Run" shortcuts to "Alt + Space"

Set the input method to Chinese mode.

Just press space

Expected behavior

Input a space.

Actual behavior

The PowerToys Run window display state switching.

Screenshots

Issue 2:
Hi,

to run Fancy Zones settings the shortkey is Win + ~.

But in a lot of keyboard (the mine is a Italian one) ~ does not exist.

I know I can use the GUI to run it, but it would be better to have "Fancy Zones settings shortcut" setting, to enable changing of it from ~ to another keyboard button.

I love this new powertoys utility.

Thank you
Issue 1:
Challenge http://www.freecodecamp.com/challenges/waypoint-bring-your-javascript-slot-machine-to-life has an issue. When I try to code on the selected area of problem "Bring your JavaScript Slot Machine to Life" browser get stuck while writing the second $. But if I copy paste the code rather than typing, it works well.

Issue 2:
checked my waypoint without confirmation, definitely a bug

Challenge http://www.freecodecamp.com/challenges/waypoint-mobile-responsive-images has an issue.

I did both but no confirmation, tried a couple of times
Issue 1:
The following should type check:

import { default as postcssNesting } from "npm:postcss-nesting@11.3.0";
postcssNesting();

but fails with the error message:

error: TS2349 [ERROR]: This expression is not callable.
Type 'typeof import("file:///home/martin/.cache/deno/npm/registry.npmjs.org/postcss-nesting/11.3.0/dist/index.d.ts")' has no call signatures.
postcssNesting();
~~~~~~~~~~~~~~

Likewise the following should type check:

import { default as Processor } from "npm:windicss@3.5.6";
const processor = new Processor();

but fails with the error message:

error: TS2351 [ERROR]: This expression is not constructable.
Type 'typeof import("file:///home/martin/.cache/deno/npm/registry.npmjs.org/windicss/3.5.6/index.d.ts")' has no construct signatures.
const processor = new Processor();
~~~~~~~~~

(using the latest deno 1.34.3)

Issue 2:
Describe the bug

npm:* default exports are incorrectly typed. Packages that are exported as default are assumed to have a default property. The plugin will claim a type error when there are no actual runtime errors. Furthermore, trying to appease the plugin error by using the default property will actually result in runtime errors.

To Reproduce

Create a file script.ts

import clsx from 'npm:clsx';

console.log(clsx("hello", "goodbye"));

Cache dependencies, notice the following error:

This expression is not callable.
Type 'typeof import("file:///Users/pting/Library/Caches/deno/npm/registry.npmjs.org/clsx/1.2.1/clsx")' has no call signatures.deno-ts(2349)

Try running deno run script.ts, notice there are no errors at runtime

Try appeasing the compiler:

console.log(clsx.default("hello", "goodbye"));

Notice runtime error.

Expected behavior

Expected plugin parsing behavior to match runtime behavior.

Screenshots

Versions

vscode: 1.77.3 deno: 1.33.0 extension: 3.17.0
Issue 1:
info

same works perfectly under ansible 1.8

code

- name: Unpack CloudWatch package
unarchive: src=/tmp/cloudwatch.zip dest=/usr/local copy=no
when: cloudwatch.stat.isdir is not defined or not cloudwatch.stat.isdir

output

TASK [aws : Unpack CloudWatch package] ******************************************
fatal: [enigma14]: FAILED! => {"msg": "ERROR! file or module does not exist: /tmp/cloudwatch.zip", "failed": true}

version

ansible --version
ansible 2.0.0 (devel ff251a0dcc) last updated 2015/06/22 10:38:58 (GMT +200)
lib/ansible/modules/core: (detached HEAD d6ed6113a7) last updated 2015/06/22 09:38:14 (GMT +200)
lib/ansible/modules/extras: (detached HEAD 57813a2e74) last updated 2015/06/22 09:38:14 (GMT +200)
v1/ansible/modules/core: (detached HEAD f8d8af17cd) last updated 2015/06/22 09:38:14 (GMT +200)
v1/ansible/modules/extras: (detached HEAD 495ad450e5) last updated 2015/06/22 09:38:14 (GMT +200)
configured module search path = None

server status

ubuntu@ubuntu:/tmp$ ls
cloudwatch.zip

Issue 2:
I have a playbook to install python. Works great under 1.8.4. Worked for a long time under 1.9.x. Fails today on 2.0.0-devel

I threw in the stat code for testing, but it doesn't make it work.

- name: configure /usr/src/python permissions
file: "dest=/usr/src/python state=directory owner={{ ansible_ssh_user }} group={{ ansible_ssh_user }} recurse=yes"
sudo: yes
- name: get python
get_url: "url=http://www.python.org/ftp/python/{{ python_version }}/Python-{{ python_version }}.tar.xz dest=/usr/src/python"
- stat: "path=/usr/src/python/Python-{{ python_version }}.tar.xz"
register: st
- name: unarchive python
unarchive: "src=/usr/src/python/Python-{{ python_version }}.tar.xz dest=/usr/src/python copy=no"
when: st.stat.exists == True

The error I get:

fatal: [aws-ansible]: FAILED! => {"msg": "ERROR! file or module does not exist: /usr/src/python/Python-2.7.10.tar.xz", "failed": true}