WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Glide Version: 4.0.0-RC0

Integration libraries: OkHttp3

Issue details / Repro steps / Use case background:

I'm trying to migrate from v3 to v4. Most of the things looked good until I added @GlideModule into appropriate places and Glide's annotationProcessor to each of my Gradle modules.

Problematic pieces of generated code are in GlideRequests - 2 as methods:

@Override
public <ResourceType> GlideRequest<ResourceType> as(Class<ResourceType> resourceClass) {
return new GlideRequest<>(glide, this, resourceClass);
}

@Override
public <ResourceType> GlideRequest<ResourceType> as(Class<ResourceType> resourceClass) {
return (GlideRequest<ResourceType>) super.as(resourceClass);
}

There are 3 glide modules in total:

1 AppGlideModule that disables manifest parsing in the application Gradle module

1 LibraryGlideModule that configures OkHttp integration in the application Gradle module

1 LibraryGlideModule that registers some ModelLoaders in one of the library Gradle modules

Do not use any GlideExtentions or GlideTypes.

Tried to only apply annotationProcessor in the main application Gradle module but didn't change anything. Also tried to exclude OkHttp3 integration - no luck as well.

Compilation error:

Totally lost on what may be causing the issue.

Issue 2:
Glide Version: 4.0.0-RC0

Integration libraries: okhttp-integration:4.0.0-RC0

Device/Android Version: Galaxy S6 SDK version 25

Issue details / Repro steps / Use case background:

When using an annotation processor, generated class GlideRequests contains duplicate field:

@Override
public <ResourceType> GlideRequest<ResourceType> as(Class<ResourceType> resourceClass) {
return new GlideRequest<>(glide, this, resourceClass);
}
@Override
public <ResourceType> GlideRequest<ResourceType> as(Class<ResourceType> resourceClass) {
return (GlideRequest<ResourceType>) super.as(resourceClass);
}

My module:

@GlideModule
public class GlideAppModule extends AppGlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
builder.setDiskCache(new InternalCacheDiskCacheFactory(context, 20 * 1024 * 1024));
}

@Override
public boolean isManifestParsingEnabled() {
return false;
}
}

Extension:

@GlideExtension
public final class GlideAppExtension {
private GlideAppExtension() {}

@GlideOption
private static void cropCircle(RequestOptions options) {
// TODO
}
}

Should i use in build.gradle:

annotationProcessor 'com.github.bumptech.glide:compiler:4.0.0-RC0'

or

compile 'com.github.bumptech.glide:compiler:4.0.0-RC0

I've tried both, and tried SNAPSHOT version

Also in the documentation example the first argument is RequestOptions<?>, but the class from the sources is not generic?

Also in the code bellow, error drawable is not used when the url is null, and docs state: "null models will cause the error drawable to be displayed", this is working in the latest 3.x version.

Glide load line / GlideModule (if any) / list Adapter code (if any):

GlideApp.with(this).load(contractImage) // contractImage is null
.transform(new CropCircleTransformation())
.error(errorDrawable)
.into(imageView);
Issue 1:
Environment

Windows build number: 10.0.18362.175
Windows terminal version: v0.2.1831.0

Steps to reproduce

Open windows terminal

Click on maximize icon

Expected behavior

Get simply a maximized window

Actual behavior

The maximized windows causes notifications to be in silent mode (without notification) and does not get out of silent mode even passing to another application.

This is possible related to the unable access tothe task bar issue

Issue 2:
Description of the new feature/enhancement

Would be great if we could align Terminal keybinding settings with the VS Code keybinding conventions (link below).

Currently, the shortcut keys abbreviations do not match and this makes it more difficult to get started with keybindings - requiring users to try to do tons of digging to find the right convention - for example, to know page down is 'pgdn' (Terminal) instead of 'pagedown' (VS Code).

Would be fantastic if we could memorize and use a single convention rather than inventing a new one and trying to remember which convention works in which tool.

Proposed technical implementation details (optional)

The Terminal shortcut key abbreviations are documented here:

(Couldn't find any reference docs. Eventually found examples by holding Ctr while selecting "Settings" in order to get to the defaults.json file.)

The VS Code shortcut key abbreviations are documented here:

https://code.visualstudio.com/docs/getstarted/keybindings#_accepted-keys

For example of the problem currently, "Page Up" is "pgup" in Terminal profiles.json and "pageup" in VS Code.
Issue 1:
For a distributed application, timeout configuration is important. But for many cases, timeout is not easy to determine.

For example, a client calls a remote service service A , and A's method calls Service B and C and D in sequence. When the client set a timeout of 3s, for a good practice, B and C as well as D should not cost more than 3 seconds. However, if I set timeout of B, C and D to 3000ms. what if B cost 2000ms to return, and C cost 2000ms to return, these two service has been already cost 4 seconds, no matter how fast D is, it is a waste for many cases.

In a word, it is very hard to set a small enough and reasonable value for many cases. What if Dubbo provide a smart timeout?

Again, we use the same case above. when B returns, it takes 2s, and dubbo modify the timeout to a value less than 1s(consider other cost that in the same context), then go calling C. In this case C takes 2 seconds, it must timeout. then D will not be called.

I was trying to do this in dubbo filler, but in current implementation, timeout is not about to modify since it is from the url instead of attachment.

int timeout = getUrl().getMethodPositiveParameter(methodName, TIMEOUT_KEY, DEFAULT_TIMEOUT);

So user cannot even implement this feature in dubbo filter in their own.

Issue 2:
If Bean Class annotated @Service and Dubbo's @com.alibaba.dubbo.config.annotation.Service,

and @DubboComponentScan and @ComponentScan were present on @Configuration Class, the Spring Context will scan this component twice.

Test cases:

Test Configuration Class

@EnableDubbo(scanBasePackages = "com.alibaba.dubbo.config.spring.context.annotation")
@ComponentScan(basePackages = "com.alibaba.dubbo.config.spring.context.annotation")
@PropertySource("META-INF/dubbb-provider.properties")
@EnableTransactionManagement
public static class TestProviderConfiguration {
}

Service Class

@com.alibaba.dubbo.config.annotation.Service(
version = "2.5.7",
application = "${demo.service.application}",
protocol = "${demo.service.protocol}",
registry = "${demo.service.registry}"
)
@Service
@Transactional
public class DemoServiceImpl implements DemoService {

@Override
public String sayName(String name) {
return "Hello," + name;
}

@Override
public Box getBox() {
return new Box() {
@Override
public String getName() {
return "MyBox";
}
};
}
}
Issue 1:
Challenge Local Scope and Functions has an issue.

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

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

I am stuck I did the following and still stuck on the page

My code:

function myFunction() {
'use strict';

console.log(myVar);
}
myFunction();
var myVar="Hieu";
// run and check the console
// myVar is not defined outside of myFunction
//console.log(myVar);

// now remove the console log line to pass the test

Issue 2:
Challenge Local Scope and Functions has an issue.

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36.

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

My code:

function myFunction() {
'use strict';

var myVar = "test";
console.log(myVar);
}
myFunction();

// run and check the console
// myVar is not defined outside of myFunction
console.log(myVar);

// now remove the console log line to pass the test

href="http://content.screencast.com/users/Pisstt/folders/Default/media/d1d59d3a-6ca0-493b-9910-3c421028f88b/2016-01-17_1925.png">
Issue 1:
I have both go 1.3.3 and go 1.4 installed.

I start by cleaning my $GOPATH/pkg directory.

Running go test ./... with Go 1.4 completes successfully

I clean my $GOPATH/pkg directory again.

I set my PATH to point to Go 1.3.3

Running go test ./... fails

I end up with many errors all with the same error

object is [darwin amd64 go1.4 X:precisestack] expected [darwin amd64 go1.3.3 X:precisestack]

It seems to be a problem the moment you have an import in some other repo. Almost like the updated PATH isn't being passed along.

Issue 2:
What steps will reproduce the problem?

I routinely use a handful of different go toolchains. As a result, I hit variants of
this error pretty frequently when building:

import <...>: object is [darwin amd64 devel +351b6fe0ae36 Tue Sep 24 15:54:48 2013
-0400 X:none] expected [darwin amd64 devel +dd18f98c9aa5 Thu Sep 26 21:35:49 2013 +1000
X:none]

To reproduce quickly:

1. Use one go version (say 1.1.2).
2. go test -i ./...
3. Switch to another go version (say tip).
4. go build ./...

Please provide any additional information below.

It's easy enough to fix the problem; remove the pkg directory, or build with -a.
However, the former is an annoyance and both make builds needlessly longer. (Is there
another option I have failed to find?)

Possible fixes include:

* Put the go toolchain version in the pkg directory (darwin_amd64_1.1.2 or
darwin_amd64_351b6fe0ae36). Optimizes for build speed at the cost of disk space and
directory ugliness.
* Instead of dying on mismatch, just discard the object, recompile, and keep on going.

I'd even suggest that this be considered for Go 1.2, since most users are likely to hit
this (albeit just once) when they upgrade.
Issue 1:
Kubernetes use kubernetes/pause image to create network container. The problem is that whatever signals the pause container received, it will exit with code 2. Instead, with a normal exit, it should exit with code 0; while it exit with port binding issue, it should exit with code -1.

Issue 2:
Jenkins e2es are taking nearly an hour and a half to complete now.

Will file with a full list of git hashes that could be causes in just a little bit.
Issue 1:
Feature request

Add a way to control the versions of babel packages.

Is your feature request related to a problem? Please describe.

Yes.

I installed @babel/preset-env and passed 7.4.4 options (core: 3) to it but it used the old one. It really confused me. (Later I saw in docs it doesn't work indeed)

A potential problem might also be with plugins like @babel/plugin-transform-flow-strip-types that are not coming out of the box in next.js.

They are added with the latest version where the babel core is a pinned down a lower version.

This is a partial code from my package.json, I didn't know @babel/core is ignored and nothing warned me it is.

"@babel/core": "^7.4.4",
"@babel/preset-env": "^7.4.4",
"@babel/plugin-transform-flow-strip-types": "^7.4.4",
"@babel/plugin-proposal-optional-chaining": "^7.2.0",

Describe the solution you'd like

I think if a user adds @babel/core to his root project package.json next should use all babel versions from the user's code, and warn if he doesn't use all the expected in next.js babel plugins.

We should also consider adding a script to eject all babel dependencies from next to the user's project. For example: next eject-babel (somehow like in create-react-app)

Describe alternatives you've considered

The readme documents the following:

The next/babel preset includes everything needed to transpile React applications. This includes:

preset-env

preset-react

plugin-proposal-class-properties

plugin-proposal-object-rest-spread

plugin-transform-runtime

styled-jsx

These presets / plugins should not be added to your custom .babelrc. Instead, you can configure them on the next/babel preset:

But I think we should also tell the user he should use older versions of babel plugins and expose the babel version nextjs is using.

Also, we can warn the user that we ignore @babel/core and @babel/preset-env if he adds @babel/core to the project and runs next.

Additional context

I'd be glad to add all these features if this feature is accepted.

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

Expected Behavior

Bug

typechecking should occur in the typescript examples

Current Behavior

typechecking does not occur

Steps to Reproduce (for bugs)

Clone the with-typescript or custom-server-typescript repos

in pages/index.jsx write the below function

function typeCheckingNotCalled(): boolean {
return 'abc';
}

// call function to prevent typescript error about function unused
typeCheckingNotCalled()

Run npm run build

In step 3 you should expect an error that says 'abc' is not assignable to boolean.

However it builds fine.

Context

I'm trying to use next js with typescript

Your Environment

Tech
Version

next
5

node
8.10

OS
mac osx 10.13

browser
chrome 64

etc
Issue 1:
Sorry for the crap title, I'm not entirely sure what is going on but I think it's a bug. I also think this is somewhat related to #5449 but am unsure.

Library Example:

export interface InstanceConstructor<T extends BaseModel> {
new(fac: Factory<T>): T;
}

export class Factory<T extends BaseModel> {
constructor(private cls: InstanceConstructor<T>) {}

get() {
return new this.cls(this);
}
}

export class BaseModel {
constructor(private fac: Factory<this>) {}

refresh() {
// get returns a new instance, but it should be of
// type Model, not BaseModel.
return this.fac.get();
}
}

User Code Example:

export class Model extends BaseModel {
do() {
return true;
}
}

// Kinda sucks that Factory cannot infer the "Model" type
let f = new Factory<Model>(Model);
let a = f.get();

let b = a.refresh();

The issue that the compiler complains about is as follows:

error TS2345: Argument of type 'typeof Model' is not assignable to parameter of type 'InstanceConstructor<Model>'.
Types of parameters 'api' and 'api' are incompatible.
Type 'Factory<this>' is not assignable to type 'Factory<Model>'.
Type 'this' is not assignable to type 'Model'.
Type 'BaseModel' is not assignable to type 'Model'.
Property 'do' is missing in type 'BaseModel'.

If I change the extended model to be specific it errors in different way, but same theme.

export class Model extends BaseModel {
constructor(fac: Factory<Model>) {
super(fac);
}

do() {
return true;
}
}

error TS2345: Argument of type 'Factory<Model>' is not assignable to parameter of type 'Factory<this>'.
Type 'Model' is not assignable to type 'this'.

I think the reason is because this isn't being polymorphic in either the template or the constructor. When this is analyzed in the constructor of BaseModel it seems to stick with that context.

I initially posted about the use of polymorphic this which was answered by @RyanCavanaugh http://stackoverflow.com/questions/33443793/create-a-generic-factory-in-typescript

Issue 2:
This error also appears on generics with this to the super call (which is the real use case).

class A {
constructor(bar: this) { }
foo(bar: this) { }
}

class B extends A {
constructor() {
super(this); // Error
this.foo(this); // Works
}
}
Issue 1:
Extra slashes in the URL change the routing. For example, /x and //x do not route the same way.

Here's a unit test which demonstrates this:

https://gist.github.com/robnagler/1a5d0361cc71a6806fc6

If you put a proxy in front of flask, it will normalize the URLs so this isn't an issue. It would seem, however, that Flask should normalize the URLs as well.

Issue 2:
Here's an example:

from flask import Flask
app = Flask(__name__)

@app.route('/<urlvar>')
def hello_world(urlvar):
return 'Hello World! ' + repr(urlvar)

if __name__ == '__main__':
app.run(debug=True)

When running:

curl http://localhost:5000/aaa%2Fbbb

I would expect to see:

Hello World! u'aaa/bbb'

Instead I get:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>

I tested this against Flask 0.9 and Flask 0.10.1. Both had the same error.

While searching for existing bug reports, I came across this: pallets/werkzeug#21

Is this related? If yes, what's the status?

In any case, being a WSGI spec problem or not, this is behaviour is incorrect!
Issue 1:
Today, you have two ways to define a list of synonyms:

within the index settings (mapping) which could cause a very big index metadata (so big cluster state - imagine daily indices)

on the file system itself but this is hard to maintain then

This feature request is about storing that document within an index and be able to retrieve it when the index is created/loaded.

See also discussion on https://discuss.elastic.co/t/recommendation-for-large-synonym-file/42740/5

Issue 2:
I have a dictionary-based analyzer implementation, with the dictionary being loaded from the plugin jar. I want to allow the user to add their words to the dictionary by using a supplementary dictionary. And I want a flexible way of handling this custom list.

Using the standard Settings implementation isn't a valid option since this is can be a list of many words, each word having some additional descriptors, so its not a string suitable for storing in settings.

One possibility is to provide the analyzer with a path of some sort via settings, but to be able to run on the cloud using SaaS providers this is not a good option. Another option is to provide a download link, but again - I don't want my Analyzer downloading the internet on initialization, plus that may be a security breach.

Instead, I'm interested in a way to leverage ES as a document store. Loading a document with this configuration seems optimal considering all options, but I'm not sure if it is supported at all. If it is - would love to hear how; otherwise, would love to see this added.
Issue 1:
Version

Superset 0.18.5

npm node v6.10.0

npm verb npm v5.3.0

Problem

executing script "./static/assets/js_build.sh" failed

Log file

npm verb type version

npm verb stack gulp-sourcemaps: No matching version found for gulp-sourcemaps@1.7.0

npm verb stack at pickManifest (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/pacote/node_modules/npm-pick-manifest/index.js:61:11)

npm verb stack at fetchPackument.then.packument (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:51:18)

npm verb stack at tryCatcher (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)

npm verb stack at Promise._settlePromiseFromHandler (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)

npm verb stack at Promise._settlePromise (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)

npm verb stack at Promise._settlePromise0 (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)

npm verb stack at Promise._settlePromises (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)

npm verb stack at Async._drainQueue (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)

npm verb stack at Async._drainQueues (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)

npm verb stack at Immediate.Async.drainQueues (/home/liuxiangwei/.jumbo/opt/nodejs-bin/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)

npm verb stack at runCallback (timers.js:651:20)

npm verb stack at tryOnImmediate (timers.js:624:5)

npm verb stack at processImmediate [as _immediateCallback] (timers.js:596:5)

npm verb cwd /home/liuxiangwei/.jumbo/lib/python2.7/site-packages/superset-0.18.5-py2.7.egg/superset/static/assets

npm verb Linux 2.6.32_1-14-0-0

Issue 2:
Make sure these boxes are checked before submitting your issue - thank you!

[ * ] I have checked the superset logs for python stacktraces and included it here as text if any

[ * ] I have reproduced the issue with at least the latest released version of superset

[ * ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

Latest HEAD

Expected results

npm install would install superset

Actual results

npm ERR! fetch failed https://registry.npmjs.org/gulp-sourcemaps/-/gulp-sourcemaps-1.7.0.tgz

Steps to reproduce

clone repository

cd incubator-superset/superset/assets

npm install
Issue 1:
You can reproduce it with in http://getbootstrap.com/javascript/#modals "Launch Demo Modal".

The body displaces 15px when the modal is open.

This happens only in Safari ( tested in 6.0.5 )

Issue 2:
When launching the modal component (http://getbootstrap.com/javascript/#modals) the entire content will slightly move to the left on mac OS (haven't tried it on windows yet). With the active modal the scrollbar seem to disappear, while the content width still changes.

You can observer the problem on the bootstrap page
Issue 1:
Do you want to request a feature or report a bug?

Bug

What is the current behavior?

When I use the new version 16.3.2 I am getting a lot of error concerning that I set ref="name" for a component that doesn't have an owner. This works fine in 16.3.1 so I am not sure if your code got more stringent or if this is a bug detecting things it shouldn't. I have changed my code to work either way, but many third party libraries are breaking with this change.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:

What is the expected behavior?

This should work identical to 16.3.1 (if this is a new thing they this should be 16.4.x or maybe even larger)

Rolling the code back to 16.3.1 works normally.

Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?

16.3.2

Issue 2:
I have to implement my project functionality into a responsive theme. So please suggest me a material UI responsive theme compatible with next js.

Thanks.
Issue 1:
Describe the issue:

Examples are as follows:

np.arange(0,1.12,0.04) will return array([0. , 0.04, 0.08, 0.12, 0.16, 0.2 , 0.24, 0.28, 0.32, 0.36, 0.4 ,

0.44, 0.48, 0.52, 0.56, 0.6 , 0.64, 0.68, 0.72, 0.76, 0.8 , 0.84,

0.88, 0.92, 0.96, 1. , 1.04, 1.08, 1.12])

but

np.arange(0,1.18,0.04) return array([0. , 0.04, 0.08, 0.12, 0.16, 0.2 , 0.24, 0.28, 0.32, 0.36, 0.4 ,

0.44, 0.48, 0.52, 0.56, 0.6 , 0.64, 0.68, 0.72, 0.76, 0.8 , 0.84,

0.88, 0.92, 0.96, 1. , 1.04])

Reproduce the code example:

import numpy as np

# One open interval, one closed interval
print(np.arange(0,1.12,0.04))

print(np.arange(0,1.08,0.04))

Error message:

No response

NumPy/Python version information:

1.22.2 3.8.8 (default, Apr 13 2021, 15:08:03) [MSC v.1916 64 bit (AMD64)]

Issue 2:
Let me show you the issue directly:

Reproducing code example:

np.arange(2114.8,2114.8+.05,.05) produces array([2114.8 , 2114.85])

np.arange(2114.8,2114.8+1.,1.) produces array([2114.8])

dont understand why they return arrays of different lengths.