WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Just something I stumpled upon and I am not sure if this is a potential bug.

In the MatchQuery class in the blendTermQuery method there is

if (fuzziness != null) {
if (mapper != null) {
Query query = mapper.fuzzyQuery(term.text(), fuzziness, fuzzyPrefixLength, maxExpansions, transpositions);
if (query instanceof FuzzyQuery) {
QueryParsers.setRewriteMethod((FuzzyQuery) query, fuzzyRewriteMethod);
}
}
int edits = fuzziness.asDistance(term.text());
FuzzyQuery query = new FuzzyQuery(term, edits, fuzzyPrefixLength, maxExpansions, transpositions);
QueryParsers.setRewriteMethod(query, rewriteMethod);
return query;
}

As far as I can see the if (mapper != null) branch doesn't really do anything. Shouldn't that Query be returned?

Issue 2:
There are various bugs to do with match query rewriting.

Wrong fuzzy_rewrite default

The docs for the boolean match query say that fuzziness should use a constant_score rewrite method by default. Instead it uses the top_terms_N method.

fuzzy_rewrite never applied

The fuzzy_rewrite parameter is never applied, so it is impossible to change it. This is fixed with the following patch:

diff --git a/src/main/java/org/elasticsearch/index/search/MatchQuery.java b/src/main/java/org/elasticsearch/index/search/MatchQuery.java
index b776416..7cc1f4f 100644
--- a/src/main/java/org/elasticsearch/index/search/MatchQuery.java
+++ b/src/main/java/org/elasticsearch/index/search/MatchQuery.java
@@ -303,10 +303,11 @@ public class MatchQuery {
if (query instanceof FuzzyQuery) {
QueryParsers.setRewriteMethod((FuzzyQuery) query, fuzzyRewriteMethod);
}
+ return query;
}
int edits = fuzziness.asDistance(term.text());
FuzzyQuery query = new FuzzyQuery(term, edits, fuzzyPrefixLength, maxExpansions, transpositions);
- QueryParsers.setRewriteMethod(query, rewriteMethod);
+ QueryParsers.setRewriteMethod((FuzzyQuery) query, fuzzyRewriteMethod);
return query;
}
if (mapper != null) {
@@ -318,4 +319,4 @@ public class MatchQuery {
return new TermQuery(term);
}

-}
\ No newline at end of file
+}

Unused rewrite parameter

The match query accepts a rewrite parameter which is never used.

Bad rewriting of match_phrase_prefix

The match_phrase_prefix should (IMO) use a constant_score_auto rewrite on the final term (and this should be settable with rewrite), but this functionality is implemented with the MultiPhraseQuery which doesn't support the rewrite methods.
Issue 1:
It has to do with FP but I think it is still precarious considering a 'small' error changes the entire mesh.

Following is an MWE

>>>np.mgrid[0.:0.5+0.5/2:0.5/2, 0.:0.2+0.2/2:0.2/2].reshape(2,-1).T
array([[ 0. , 0. ],
[ 0. , 0.1 ],
[ 0. , 0.2 ],
[ 0. , 0.3 ],
[ 0.25, 0. ],
[ 0.25, 0.1 ],
[ 0.25, 0.2 ],
[ 0.25, 0.3 ],
[ 0.5 , 0. ],
[ 0.5 , 0.1 ],
[ 0.5 , 0.2 ],
[ 0.5 , 0.3 ]])`

which is due to the FP representation of 0.1+0.2

However if I use the following, I get the expected result

>>> np.mgrid[0.:0.75:0.25, 0.:0.3:0.1].reshape(2,-1).T
array([[ 0. , 0. ],
[ 0. , 0.1 ],
[ 0. , 0.2 ],
[ 0.25, 0. ],
[ 0.25, 0.1 ],
[ 0.25, 0.2 ],
[ 0.5 , 0. ],
[ 0.5 , 0.1 ],
[ 0.5 , 0.2 ]])`

A silly workaround would be use only the first few (~16) decimal places for such cases but I do think that float(format(0.1+0.2,'.16f')) is not very natural to many people

Issue 2:
If I do np.arange(3.18,3.21,0.01), it gives array([ 3.18, 3.19, 3.2 ]). However, if I do np.arange(3.18,3.22,0.01), it gives array([ 3.18, 3.19, 3.2 , 3.21, 3.22]). This seems inconsistent. Why is this so? I am using numpy 1.11.2 on Python 2.7.13.
Issue 1:
**$ flutter doctor -v

Building flutter tool...

Unhandled exception:

Bad state: Future already completed**
#0 _AsyncCompleter.complete (dart:async/future_impl.dart:39)
#1 _NativeSocket.connect.<anonymous closure>.connectNext.<anonymous closure> (dart:io-patch/socket_patch.dart:494)
#2 _NativeSocket.issueWriteEvent.issue (dart:io-patch/socket_patch.dart:802)
#3 _NativeSocket.issueWriteEvent (dart:io-patch/socket_patch.dart:809)
#4 _NativeSocket.multiplex (dart:io-patch/socket_patch.dart:830)
#5 _RawReceivePortImpl._handleMessage (dart:isolate-patch/dart:isolate/isolate_patch.dart:165)
Error: Unable to pub upgrade flutter tool. Retrying in five seconds...

Issue 2:
Steps to Reproduce

Trying to install Flutter in Windows 10 Machine. Clone the repo and added path and

run flutter doctor it downloaded sdk and getting error. deleted the cache folder in bin and retried but same error.

Logs

same as flutter doctor -V

Flutter Doctor

Updating flutter tool....
CreateProcessW failed 193
CreateProcessW failed 193
CreateProcessW failed 193
%1 is not a valid Win32 application.

Command: C:\Users\KD\Desktop\flutter\bin\cache\dart-sdk\lib\_internal\pub\asset\7zip\7za.exe e data.tar.gz
Error: Unable to 'pub upgrade' flutter tool. Retrying in five seconds...

Waiting for 0 seconds, press CTRL+C to quit ...

For more information about diagnosing and reporting Flutter bugs, please see https://flutter.io/bug-reports/.
Issue 1:
Hey, there seems to be some kind of a problem with my setup and the ES6 highlighting.

I've got my jsconfig.json as the following:

{ "compilerOptions": { "target": "ES6", "module": "commonjs" }, "exclude": [ "node_modules" ] }

But that config file changes nothing. Whethere it's there or not, the syntax highlighting stays the same.

It looks like this:

My file structure:

Issue 2:
Extracted from microsoft/vscode#1470 reported by @MacKentoch

Got same issues with javascript ES6.

As examples

import (was red before) is now just grey

constructor is now grey

Occurs in OSX El capitan and windows 10.

Jsx seems not that much impacted (but still improvements to be done).
Issue 1:
export default class {

}

compiled code is:

class {
}
exports. = default_1;

compile command is tsc --module commonjs --target ES6 default.ts, TypeScript version is 1.7.5

Issue 2:
Compiling the following code:

"use strict";
export default class {};

Using the command line tsc --t es6 --m commonjs produces illegal JavaScript:

"use strict";
class {
}
exports.default = default_1
;

I realize this is a weird combination of switches, however it seems necessary to target current versions of Node.js/V8 that don't yet natively support ES6 modules.
Issue 1:
Bug report

What is the current behavior?

After packaging the file, the global variable name is repeated, resulting in the variable is overwritten, call the wrong method, resulting in an error.

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

Execute the command “cross-env BUILD_ENV=dev umi build“

What is the expected behavior?

Global variable definitions do not affect each other

Other relevant information:

webpack version: 5.6.0

Node.js version: 16.14.2

Operating System: win 10

Additional tools:

Related images

Issue 2:
Feature request

Webpack currently uses (only?) JS files as main entry-points via the entry property in configuration options, and then resolves dependencies from there. I request to support HTML files as entry points and resolve dependencies from there.

What is the expected behavior?

Currently webpack throws an error saying there is no loader associated to handle the file type.

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

Whenever a user (browser/UA) loads a page, the first thing it gets is an HTML response. The UA then resolves other resource files (CSS, JS, images, ...) from the HTML content and loads them as required. So it is intuitive for webpack to start from an HTML file and resolve dependencies from there. Parcel already does this, but comparing webpack with other module bundlers, webpack is still the fastest.

I know that I can write some code like require('./component.html') and use something like html-webpack-plugin to also get the HTML files and process them. But this feels very disconnected from requiring all the files in JS code, and only handling HTML code through a separate plugin (yes, there may be a way to do this, but I'm sure its just another hack/plugin/loader).

Module bundlers started with JS entry points when they only handled JS, but webpack evolved to be more than just a module bundler for JS, which is now used to load all kinds of files. A JS file is a dependency to an HTML file, not the other way around.

html <-- start from here
┌──────────┼─────────┐
css img js <-- not from here
┌────┴────┐ ┌────┼────┐
css css js js js

Because c'mon man, how standard (isomorphic?) is writing something like import styles from './styles.css';? Why couldn't webpack think (and also act) as a browser instead!?

Some people (who write HTML inside JS) may not like this feature, but I want to make it clear that I want webpack to support HTML entry-points along side JS entry-points, not replace the existing behavior.

How should this be implemented in your opinion?

Let HTML files be included in the entry option and webpack should handle it by default (without any need of plugins), then provide loaders for different file types.

Sidenote: I think one advantage of this approach may be for people to move their existing static/dynamic applications move to wepack without (re-)writing CSS and HTML imports in JS files. They can just include webpack and point it to some HTML files.

Are you willing to work on this yourself?

I'm a regular webpack user, but haven't looked into the source code yet. If someone can guide me on the internals, then yes!
Issue 1:
#19113 added basic support for adding a dependency from iOS to a module, by manually configuring dependency via the xCode UI. We should investigate if we can make this simpler, for example by delegating more work cocoapods (e.g., reduce the steps to adding a single pod reference)

Issue 2:
https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps provides steps to add Flutter to an existing app.

On iOS, it would be nice to automate these steps into the tooling to:

Add references to the Flutter Framework

Add/update appropriate config files

Add the Flutter build script phase

Add CocoaPods if it's not already added

/cc @matthew-carroll
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/9498/

Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/proxy.go:280
0 (0; 281.25345ms): path /api/v1/namespaces/e2e-tests-proxy-kbalk/pods/proxy-service-f34y9-v5ij9/proxy/ gave status error: {TypeMeta:{Kind: APIVersion:} ListMeta:{SelfLink: ResourceVersion:} Status:Failure Message:an error on the server has prevented the request from succeeding Reason:InternalError Details:name:"" group:"" kind:"" causes:<reason:"UnexpectedServerResponse" message:"Error: 'EOF'\nTrying to reach: 'http://10.180.1.5:80/'" field:"" > retryAfterSeconds:0 Code:503}

Previous issues for this test: #26164

Issue 2:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/7676/

Failed: [k8s.io] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/proxy.go:248
0: path /api/v1/namespaces/e2e-tests-proxy-5q81p/pods/proxy-service-xugyo-n1z2c:80/proxy/ gave error: an error on the server has prevented the request from succeeding
Issue 1:
A Show implementation could use the string representation.

Issue 2:
If I build rust with --disable-jemalloc, I am getting a strange memory issue somewhere in stage1 (see below for how to reproduce it on Linux). I also reproduced the same issue during porting rust to DragonflyBSD (which I initially built w/o jemalloc). There I noticed for some input files that it wants to mmap an anonymous region of size 0x800_000_000 or 0x1000_000_000, probably due to a mal-formed malloc call (just a wild guess). And then more or less stalls the system, probably trying to zero that region and swapping to disk. Changing a single letter in the file subject for compilation makes rustc behave well again. With jemalloc, these issues are not existent (both on Dragonfly and Linux)!

# uname -a
Linux linux-vbox 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
# ./configure --disable-jemalloc
# make

results in:

cp: x86_64-unknown-linux-gnu/stage1/lib/librustc_llvm
cp: x86_64-unknown-linux-gnu/stage1/lib/librustc_back
cp: x86_64-unknown-linux-gnu/stage1/lib/librustc
cp: x86_64-unknown-linux-gnu/stage1/lib/libnative
cp: x86_64-unknown-linux-gnu/stage1/bin/rustc
cp: x86_64-unknown-linux-gnu/stage1/lib/rustlib/x86_64-unknown-linux-gnu/lib/libmorestack.a
cp: x86_64-unknown-linux-gnu/stage1/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler-rt.a
rustc: x86_64-unknown-linux-gnu/stage1/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore
*** Error in `x86_64-unknown-linux-gnu/stage1/bin/rustc': free(): invalid next size (fast): 0x00002b032802af30 ***
*** Error in `x86_64-unknown-linux-gnu/stage1/bin/rustc': malloc(): memory corruption: 0x00002b032802af60 ***
Issue 1:

Issue 2:
Trying to get packages from nuget. I'm not getting intellisense in project.json. In the JSON server output window I see a lot of this:

Request to the nuget repository failed: <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="en-US">URI or query string invalid. Query option 'Format' is not allowed. To allow it, set the 'AllowedQueryOptions' property on EnableQueryAttribute or QueryValidationSettings.</m:message></m:error>

Running OS X 10.11.3 VS Code 0.10.9-insider and 0.10.9
Issue 1:
At the moment the scripts directory is hard coded to scriptsDirectory = new File(env.configFile(), "scripts"); but it would be handy to make this configurable.

Main reason is that with the Puppet module we allow multiple instances, and it would be handy that all instances on a single node can share the same directory where the scripts are located.

Issue 2:
Since dynamic scripting is off by default since elasticsearch >=1.2 (which is good!), we have to move all our scripts to files in the config/scripts folder. It would be awesome to have an option to change that folder in the config to make it easier for using different folders in different environments. Best would be to set it through ENV variables ELASTICSEARCH_SCRIPTS_FOLDER and through the config file

path:
logs: /var/log/elasticsearch
data: /var/data/elasticsearch
scripts: /my/custom/script/folder

thanks!
Issue 1:
Two nodes went away as I updated the instances, but they still appear and, more importantly/confusingly, their daemonset pods are still in Running state.

$ fleetctl list-machines
MACHINE IP METADATA
729947b9... 10.0.12.180 role=node
a0883347... 10.0.8.4 instance=m0,role=master
$ kubectl get nodes
NAME STATUS AGE
ip-10-0-10-222.ec2.internal NotReady 2d
ip-10-0-12-147.ec2.internal NotReady 1d
ip-10-0-12-180.ec2.internal Ready 17m
ip-10-0-8-4.ec2.internal Ready,SchedulingDisabled 2d
$ kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system fluentd-logging-2gxb1 1/1 Running 0 1d
kube-system fluentd-logging-33y2f 1/1 Running 0 1d
kube-system fluentd-logging-b1yuv 1/1 Running 0 17m
kube-system fluentd-logging-o9hvp 1/1 Running 0 1d

There are only two instances and thus two daemons up, not four.

I understand the rationale for not killing the pods outright, but is there a timeout after which they change state or perhaps the nodes do?

My concern is twofold:

Running is a lie. Things will be confusing for monitoring/accounting/troubleshooting purposes.

State about pods and nodes is kept around for a long time. Imagine someone using DaemonSets on a pool of EC2 spot instances...

Issue 2:
I don't see any existing issues filed for this.

Allow the user to instruct Kubernetes, based on data from liveness/readiness probes (or failures to start new pods at all), to automatically undo a rollout, not just pause it. This could even have a configurable maxFailures knob to specify how many pods in "failed after upgrade" state to allow before rolling back. Similar for pending pods.
Issue 1:
twitter thread https://twitter.com/domenic/status/697921719529398272

Issue 2:
I am using VSC on Windows while developing for Linux-based webserver. Also, several people on my team are using Macs. It is very annoying for us to switch end of line sequence for each new file. It would be great if there was a user setting to ensure all new files are created with a certain eol sequence.
Issue 1:
My current use case is to cluster a bunch of data to generate labels, then use a classifier to draw decision boundaries and make label predictions on new data.

I love using pipeline and gridsearch packages in tandem, but can't use it for this because clustering does not have a transform method for X. Is it worthwhile to make pipeline components chain-able by the labels_ attribute in addition to transform?

Issue 2:
Following up on #3113 and #3112, what about arbitrary transforms to the y values? Those issues dealt primarily with "label transforms" but I would like to use transformers to mean or range center the y values as well.

Ideally I would have some transform that can be applied to the y values before fitting and then applied in the inverse to the predicted y values coming out of predict.

Ideally this Transformer could be added to a pipeline.

Currently the signature for transform for StandardScaler allows for transforming y but as pointed out in the linked issues, not all transform methods have a signature allowing for a y to be passed in.

Further even for StandardScaler there is an inconsistency with the inverse_transform NOT taking y.
Issue 1:
Bug Report

Current Behavior

After I upgrade @babel/core to v7.5.5, circleci build throw error TypeError: helpers(...).ensure is not a function

This error only happen in circleci environment. No error in windows or Mac

Environment

Babel version(s): [v7.5.5]

Node/npm version: [e.g. Node 10/npm 5]

OS: [linux]

How you are using Babel: [loader]

Possible Solution

The error happen in below line in v7.5.5

babel/packages/babel-core/src/transformation/file/file.js

Line 207
in
fced5ce

helpers.ensure(name);

Additional context/Screenshots

@babel/core v7.5.5 build log

@babel/core v7.5.4 build log

Issue 2:
It looks like if I have:

class Test {
constructor() {
someService.get().then(async () => {
this.foo = 'tada';
})
}
}

this is undefined. If I remove async I have the right this.
Issue 1:
When installing on Windows 7 x64 with:

pip install opencv-python # py 2.7

or

pip3 install opencv-python # py 3.6

in both cases, it installs succesfully but at the end, when doing:

import cv2

we have this bug:

ImportError: DLL load failed: The specified module could not be found.

As noted on many posts, the reason is that this file is missing:

MS-WIN-DOWNLEVEL-SHLWAPI-L1-1-0.DLL

Fix: install KB2670838 / Platform Update for Windows 7, less than 15 MB

Windows6.1-KB2670838-x64.msu

Todo: Can we put this in the release notes of Open CV 3.4.3 or better:

Can we do a try: ... except: ... and display Please install Platform Update for Windows 7 / KB2670838 instead of just a non-explicit DLL load failed message ?

It would save countless hours for Windows users trying to install OpenCV.

Issue 2:
the installed opencv_world342.dll need "Api-ms-win-downlevel-shlwapi-l1-1-0.dll" which is not in Windows 7. (vc2015_redist.exe already installed).

when I copy it from windows10, it works.
Issue 1:
Hi,

I don't know if this is a bug or a feature, or even if you guys noticed it already and it's not an issue, but this caused me some problems so I thought I should report it.

When you use the read_csv command to read a csv, you can pass the columns you want to set as indexes. If those columns contain duplicated entries, the index will have duplicated entries.

To reproduce this, read a csv file with this contents:

indexcol, anothercol, yetanothercol
1, 1, 1
1, 2, 3
2, 1, 2

with the command:

In [1]: import pandas

In [2]: pandas.read_csv('bar.csv', index_col = 'indexcol')
Out[2]:
anothercol yetanothercol
indexcol
1 1 1
1 2 3
2 1 2

Is this what should happen? Is there a way to prevent it (like, for example, just read the first ocurrence of each duplicated index an drop the rest)? What I did to get rid of the duplicated entries was:

In [3]: df = pandas.read_csv('bar.csv', index_col = 'indexcol')

In [4]: df.groupby(lambda x:x).first()
Out[4]:
anothercol yetanothercol
1 1 1
2 1 2

Issue 2:
What do we want out of our API docs? What are the current issues?

I think we're (mostly) happy with api.rst: we manually list the classes and methods that we want to include the docs, grouped by topics of our choosing.

I think we're unhappy with some aspects of the auto-genrated class pages.

The hack in our vendored numpydoc.py "fixing" the autosummary to not include a table of methods for certain classes. This avoids a ton of redundant pages with the parent class, but we can't call out important differences like RangeIndex.start

We'd like a way to limit autosummary to specific methods in a class (I think this can be done with a Methods section in the docstring)

Tasks:

Limit API doc of classes to certain members (either extend autodoc or do it manually?) -> #18202

DOC: fix API docs generation with sphinx 1.6 #16705

DOC: documenting cython class (eg Timestamp): "cyfunction is not a python function" #5218 -> #18202

Remove vendored IPython sphinxext (#18193, #19657)

should be OK with ipython/ipython#10907 released)

removed in #19657

We should check on Windows!

Align our numpydoc version with upstream / use upstream version: for this we somehow need to fix (or push upstream) our hacks to numpydoc ( I think this are the only relevant changes to the numpydoc source since it was last aligned with upstream in #6003) (xref #11257)):

cf40991 initial commit for allowing classes without members table -> #18202

70c9d31 for None attributes

Remove vendored numpydoc (work around numpy/numpydoc#106 (comment))

Fix cache_readonly copying docstring (#18197)

Index.name and other class attributes. Either fix in numpydoc to use sphinx magic, or make into properties

DataFrame.index and DataFrame.columns (#18196)

Check performance (better than 1.6, but still slower? sphinx-doc/sphinx#4230)