WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I cannot access GlideApp thought i'm creating this class , is there anything missing?

Glide Version: 4.0.0 RC

Integration libraries: nothing

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

package mobi.foo.project.activity;

import android.content.Context;

import com.bumptech.glide.GlideBuilder;
import com.bumptech.glide.Registry;
import com.bumptech.glide.annotation.GlideModule;
import com.bumptech.glide.load.engine.cache.LruResourceCache;
import com.bumptech.glide.module.AppGlideModule;

/**
* Created by Jack Lebbos on 5/31/2017.
*/
@GlideModule
public final class MyGlideModule extends AppGlideModule {
@Override
public void applyOptions(Context context, GlideBuilder builder) {
super.applyOptions(context, builder);
setMemoryCache(context, builder);
}

public MyGlideModule() {
super();
}

@Override
public void registerComponents(Context context, Registry registry) {
super.registerComponents(context, registry);
}

public void setMemoryCache(Context context, GlideBuilder builder) {
int memoryCacheSizeBytes = 1024 * 1024 * 20; // 20mb
builder.setMemoryCache(new LruResourceCache(memoryCacheSizeBytes));
}

public void setDiskCache() {
int diskCacheSizeBytes = 1024 * 1024 * 100; // 100 MB

}

}

Issue 2:
I'm trying to use glide 4.0.0-RC0 by Gradle:

dependencies {
compile 'com.android.support:appcompat-v7:25.1.0'
compile 'com.caverock:androidsvg:1.2.2-beta-1'
compile 'com.github.bumptech.glide:glide:4.0.0-RC0'
compile 'com.android.support:support-v4:25.3.1'
}

I followed the example here: https://github.com/bumptech/glide/tree/master/samples/svg/src/main/java/com/bumptech/glide/samples/svg

but after add glide by Gradle, I got error: Cannot resolve symbol 'GlideApp'

My source:

package com.example.quangson.glidesvg;

import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import static com.bumptech.glide.load.resource.drawable.DrawableTransitionOptions.withCrossFade;

import android.content.ContentResolver;
import android.graphics.drawable.PictureDrawable;
import android.net.Uri;
import android.widget.ImageView;
import android.widget.LinearLayout;

import com.bumptech.glide.RequestBuilder;
import com.example.quangson.glidesvg.glide.SvgSoftwareLayerSetter;

public class MainActivity extends AppCompatActivity {

private static final String TAG = "SVGActivity";

private ImageView imageViewRes;
private ImageView imageViewNet;
private RequestBuilder<PictureDrawablerequestBuilder;
LinearLayout ll;

@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);

imageViewNet = (ImageView) findViewById(R.id.svg_image_view2);

requestBuilder = GlideApp.with(this)
.as(PictureDrawable.class)
.placeholder(R.drawable.image_loading)
.error(R.drawable.image_error)
.transition(withCrossFade())
.listener(new SvgSoftwareLayerSetter());

Uri uri = Uri.parse("http://www.clker.com/cliparts/u/Z/2/b/a/6/android-toy-h.svg");
requestBuilder.load(uri).into(imageViewNet);
}
}

Please help
Issue 1:
I pass my proxy object to the axios.request() method and test everything with charles proxy but nothing happens. After some debugging i realized that the http adapter file is not packaged because it is not used.

And the adapter is not used because of this code inside the defaults.js

function getDefaultAdapter() {
var adapter;
if (typeof XMLHttpRequest !== 'undefined') {
// For browsers use XHR adapter
adapter = require('./adapters/xhr');
} else if (typeof process !== 'undefined') {
// For node use HTTP adapter
adapter = require('./adapters/http');
}
return adapter;
}

Can someone help me so i can use the proxy feature with react-native?

Issue 2:
The new 0.40.0 release of RN has broken axios for me.

I've done two test cases in which I create a blank application, install axios, then import axios on the index page. The only difference between the two projects are the RN version number.

react-native init TestProject (this is @latest which is currently 0.40.0)

cd TestProject

npm install axios --save

I then go into the index.android.js file and add: import axios from 'axios'

react-native run-android

In this case, I get the following error:

Unable to resolve module http from C:\ReactNative\Projects\TestProject\node_modules\axios\lib\adapters\http.js: Module does not exist in the module map or in these directories: C:\ReactNative\Projects\TestProject\node_modules.

However, when I install an older version of RN like below, axios works fine.

rninit init TestProject --source react-native@0.39.2

cd TestProject

npm install axios --save

I then go into the index.android.js file and add: import axios from 'axios'

react-native run-android

As a workaround to fix this I have downgraded my RN back down to 0.39.2 rather than using 0.40.0.
Issue 1:
I propose deprecating the following exports (the definitions will remain in base):

ldltd and ldltd! (implementation of factorize for SymTridiagonal)

solve (implementation of \ for some types)

symmetrize! (specialized function, only one of several possible ways to symmetrize a matrix, symmetrize_conj! is not exported, non-mutating variants don't exist)

Issue 2:
Going into src/flisp and running make once built flisp but doesn't anymore. Not super crucial for Julia itself, but it seems like a good idea for this to work. We may want to pull flisp and support out into their own submodules?

[Background motivation: I'm at Hacker School and someone here wants to study a small and clean but non-toy programming language implementation. This was the best body of code I could think of looking at since it implements a fast, complete Scheme in under 8000 lines of C code.]
Issue 1:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details

Electron Version:

8.2.5 / 8.3.0

Operating System:

Windows 10 1909 64bit

Last Known Working Electron version:

6.x.y

Actual Behavior

If I double click electron.exe in node_modules or in downloaded package, no window show up, the exe will crash immediately.

If I run "electron ." in cmd, it will show following error, and also crashed:

[12192:0520/214855.899:FATAL:tsf_text_store.cc(33)] Failed to initialize CategoryMgr.
npm ERR! code ELIFECYCLE
npm ERR! errno 2147483651

Screenshots

Additional Information

The 64bit version is working fine

Issue 2:
Preflight Checklist

I have read the Contributing Guidelines for this project.

I agree to follow the Code of Conduct that this project adheres to.

I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

14

What operating system are you using?

Windows

Operating System Version

Випуск	Windows 10 Pro 21H1

What arch are you using?

x64

Last Known Working Electron version

13

Expected Behavior

Metadata is loaded correctly and displayed in the system widget.

Clicking on media buttons trigger action handlers.

Actual Behavior

Metadata not displayed in system widget.

Clicking on media buttons doesn't trigger action handlers.

Testcase Gist URL

https://gist.github.com/7a51c4236a83c4536b6759bf938c69e8

Additional Information

No response
Issue 1:
Hi,

Let's say I have a project with a dependency tree like (all dependencies being declared as "dependencies" in package.json)

Main application

angular

Sub-module 1

angular

Sub-module 2

angular

When bundling my app, I will end-up with angular being included 2 times in my webpage. I know I can use webpack.optimize.DedupePlugin() to prevent the file being included multiple times but it will still be called two times at runtime, resulting in a warning "tried to load angular more than once".

I feel this is the same for every sub-dependencies shared by my app dependencies, every sub-module will have its own version of angular and even though they use the exact same version, it will be loaded multiple times.

Is this tied to the philosophy of not having a flat dependency tree or am I doing something wrong ? One solution I have found is to move all the dependencies of my sub-modules as peerDependencies and add them as dependencies to my "Main application" but I feel like this is a very bad solution.

Any insights on this ?

Thanks.

Issue 2:
Bug report

Encountered this while trying to upgrade my loader to webpack@5.

In webpack@4, with @types/webpack, I could create a fully typed loader.

In webpack@5, there's aren't any exported types for the Loader or the LoaderContext

What is the expected behavior?

Auto generate (?) or just include these interfaces:

https://github.com/DefinitelyTyped/DefinitelyTyped/blob/6a1c6a5567fa177396fa802b2367ec34e1028eea/types/webpack/index.d.ts#L2116

Other relevant information:

webpack version: 5.0.0

Node.js version: 14.13.1

Operating System: Fedora 32

Additional tools:
Issue 1:
For .NET debugging, we have a number of spots where it can be confusing what the line-based text markers used by VS Code are actually pointing at. There are various language features in C# that commonly result either in multiple statements on a single line or in multi-line statements. Some of these such as setting a breakpoint inside of a lambda can be pretty confusing today because the editor markers (current statement, breakpoint bound) just show the line where things are happening instead of the text range. Thus there is no way to tell quite where you are stopped, or where the breakpoint is actually set.

I would suggest supporting both text markers that highlight an entire line, and text markers that highlight a text span ([begin-line,begin-col]->[end-line,end-col]).

Issue 2:
If a StackFrame or a Breakpoint has an optional end location, show the character range instead of the full line.
Issue 1:
2.1.0-beta.27

Do you want to request a feature or report a bug?

Bug.

I have a dependency structure whose salient point can be described as something like this:

root
├─ async@^2.0.0
└─ @scope
├─ foo
│ └─ async@^1.5.0
└─ bar
└─ async@^2.0.0

What is the current behavior?

It appears that after bundling, both dependencies foo and bar get the same version of async: ^2.0.0. Since the argument order for the async API has changed between 1.x and 2.x, this of course breaks the application.

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

Time permitting, I’ll try to come up with a minimal repro case.

What is the expected behavior?

foo and bar should receive different versions of async.

Issue 2:
I'm submitting a bug report

Webpack version:

^1.13.1

Environment:

Using archlinux, but this should be irrelevant.

Current behavior:

Using webpack with css-loader and UglifyJsPlugin mangles some CSS. In this particular case, it transforms a quoted string in an unquoted string, which becomes invalid from use of a plus sign (+) in the name of a font.

The rule is:

font-family: "M+ 1mn", "Fixedsys","Courier New", monospace;

Which becomes:

font-family: M+\ 1mn,Fixedsys,Courier New,monospace;

It has not been tested whether other characters causes similar issues.

Disabling both or either UglifyJsPlugin and the css-loader minification prevents this issue from occuring.

Expected/desired behavior:

The minification should properly handle special characters in CSS.

Special characters in CSS

Any character that is not a hexadecimal digit, line feed, carriage return, or form feed can be escaped with a backslash to remove its special meaning.

The following characters have a special meaning in CSS: !, ", #, $, %, &, ', (, ), *, +, ,, -, ., /, :, ;, <, =, >, ?, @, [, , ], ^, `, {, |, }, and ~.

(CSS character escape sequences)

Test case:

https://github.com/samueldr/webpack1-css-minification-test-case

Browser:

This is at least true for Chrome, but this should not matter as this is an invalid CSS minification.

This bug is possibly a duplicate or related to: #666 and #283
Issue 1:
Forked from #27194

@ichekrygin reported a weird cpu/usage_rate issue from heapster

I am running on v1.3.5 and this still seems to be an issue

curl http://localhost:8001/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/namespaces/production/pods/rain-377063289-tz0tq/metrics/cpu/usage_rate
{
"metrics": [
{
"timestamp": "2016-08-18T03:04:00Z",
"value": 18446744073709551449
},
{
"timestamp": "2016-08-18T03:05:00Z",
"value": 705
},
{
"timestamp": "2016-08-18T03:06:00Z",
"value": 18446744073709551028
},
{
"timestamp": "2016-08-18T03:07:00Z",
"value": 696
},
{
"timestamp": "2016-08-18T03:08:00Z",
"value": 18446744073709550587
},
{
"timestamp": "2016-08-18T03:09:00Z",
"value": 0
},

Node version:

kubelet --version
Kubernetes v1.3.5

@timstclair and I checked his node stats by collecting curl -s http://localhost:10255/stats/summary | jq '.node.cpu.usageCoreNanoSeconds'. usageCoreNanoSeconds is the accumulative cpu usage, and it is only stats used by heapster and HPA. This stat is mapping to heapster's cpu usage, and it is used to calculate cpu/usage_rate together with some timestamps. We noticed that the usageCoreNanoSeconds are sane, but corresponding heapster's cpu/usage_rate is insane as the above. I believe heapster ran into some overflow issue cAdvisor encountered before. Filed this one as a record to make sure the problem is addressed at the proper layer.

cc/ @mwielgus @fgrzadkowski

Issue 2:
Kubernetes version:

Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.6+coreos.0", GitCommit:"f6f0055b8e503cbe5fb7b6f1a2ee37d0f160c1cd", GitTreeState:"clean", BuildDate:"2016-08-29T17:01:01Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}

Environment:

Cloud provider or hardware configuration: AWS

OS: CoreOS

Kernel: 4.6.3-coreos

Install tools: kube-aws

What happened:

Some EBS volumes remain in the attachment state "attaching". These EBS volumes are attached on a device name that was used for a previous attachment.

Looking on the worker node, the volume is not visible in the device list (eg by running lsblk). After a reboot of the node the volume is attached successfully. The attachment state then is "attached".

Expected behavior:

The EBS volumes are attached correctly.

How to reproduce it:

Spin up a worker node

Create 20 EBS volumes

Create 19 pods with volumes attached on this node

Remove the first pod

Create a 20th pod with the 20th volume attached

Now the 20th volume remains in the attachment state 'attaching'.

20 is not necessary the lower bound but the issue did not appear with 3 volumes.

Additional information:

It seems related to the reuse of device names. Only when the device name /dev/xvdXX was already used for a previous attachment, the volume remains in the attachment state "attaching".

When using a lower number of volumes, it is still possible to detach-attach. Only when attaching a considerable amount of volumes (about 20), the issue appears.

According to this AWS support article it is possible that the device name was not released by the block device driver after detaching.
Issue 1:
Challenge Create a Text Field has an issue.

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

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

I cannot click anywhere beyond the on line 46 ( if I click anywhere beyond it, my cursor will fall in front of the .

I also have this issue on line 45. If I click anywhere beyond the <li, my cursor will just land after the "i" in <li

This has occurred on many of the challenges. Refreshing or restarting the browser has helped in most cases.

My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">
<style>
.red-text {
color: red;
}

h2 {
font-family: Lobster, Monospace;
}

p {
font-size: 16px;
font-family: Monospace;
}

.thick-green-border {
border-color: green;
border-width: 10px;
border-style: solid;
border-radius: 50%;
}

.smaller-image {
width: 100px;
}
</style>

<h2 class="red-text">CatPhotoApp</h2>

<p>Click here for <a href="#">cat photos</a>.</p>

<a href="#"><img class="smaller-image thick-green-border" alt="A cute orange cat lying on its back" src="https://bit.ly/fcc-relaxing-cat"></a>

<p>Things cats love:</p>
<ul>
<li>cat nip</li>
<li>laser pointers</li>
<li>lasagna</li>
</ul>
<p>Top 3 things cats hate:</p>
<ol>
<li>flea treatment</li>
<li>thunder</li>
<li>other cats</li>
</ol>

Issue 2:
In all the exercises, we the users are forced to press the enter key before writing any code.

Update:

We have locked the conversation temporarily on this thread to collaborators only, this has been resolved in staging, and will be live soon.

The fix can be confirmed on the beta website.

The workaround currently on production website is:

Press the Enter key on the challenge editor and then proceed with the challenge.

Apologies for the inconvenience meanwhile.

Reach us in the chat room if you need any assistance.
Issue 1:
Problem description

Sometimes the Divider Component display a 2px thickness, when no custom styles have been applied.

Steps to reproduce

<List>
<ListItem disabled={true}>
<div className={classes.detailTitle}>Trade Miles</div>
<div>{tradeInfo.miles}</div>
</ListItem>
<Divider/>
<ListItem disabled={true}>
<div className={classes.detailTitle}>Trade Payments</div>
<div>{tradeInfo.payment}</div>
</ListItem>
<Divider/>
<ListItem disabled={true}>
<div className={classes.detailTitle}>Trade Payoff</div>
<div>{tradeInfo.payoff}</div>
</ListItem>
<Divider/>
<ListItem disabled={true}>
<div className={classes.detailTitle}>Down Payment</div>
<div>0</div>
</ListItem>
<Divider/>
<ListItem disabled={true}>
<div className={classes.detailTitle}>Must Haves</div>
<div>0</div>
</ListItem>
</List>

Versions

Material-UI: v0.15.4

React: V15.3.1

Browser: Chrome

Issue 2:
The divider behavior in my code sandbox is weird. Sometimes is shows up thicker and sometimes they don't even show up. This can be reproduced by cmd+/- on mac to adjust the zoom on your browser. Please see screenshots attached for examples.

Expected Behavior 🤔

Current Behavior 😯

Steps to Reproduce 🕹

https://codesandbox.io/s/mmnoyvq9oy

Context 🔦

Just trying to make my dialogs work in a few different contexts

Your Environment 🌎

Tech
Version

Material-UI
v3.9.1

React
16.8.4

Browser
Chrome
Issue 1:
I love getting updates to Atom! However, I am often reluctant to click the button to restart and update because when it opens back up it just shows me a blank to tab, instead of opening from the project I ha d been on. When I do manually go an open the project folder where I do work it remembers all my open tabs just fine, so why it can't remember to open that project when it starts back up I'm not sure.

I don't know if this is a bug or not - may just be a feature that wasn't implemented what I think is the "right" way.

This is on Atom 0.122 using OSX 10.9.4 (and no, I can't test this on .124 since there is nothing to update to...)

Issue 2:
A feature I love about ST2 and iA Writer, which I'm missing in Atom, is when you quit the app with open windows (including unsaved documents), they all appear again when you reopen.

This has saved me countless times in my workflow to handle having to do a system restart for software update, etc and not have to take time to save all my unsaved docs, etc.

It's also nice because I generally have five or six open projects that I just keep minimized in the editor for ease of access. It would be great to have such a feature in Atom.
Issue 1:
Hi,

Looks like a basic next.js project gets react duplicated in the next-dev.bundle.js.

when launching my fresh project, and going to http://127.0.0.1:3000/_next/next-dev.bundle.js i can see two SECRET_DO_NOT_PASS_THIS_OR_YOU_WILL_BE_FIRED in the source, and i guess this is not good ?

it doesnt hurt for simple cases, but as soon as you use ReactCSSTransitionGroup or something using React refs then you get that error :

next-dev.bundle.js:945 Uncaught Error: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).(…)

PS: using next.js@1.2.3

Issue 2:
While trying to enable the Node inspector via the --inspect flag, it was noticed that it only works if is used in its default form. None of its other forms work, i.e: --inspect=0.0.0.0:9928

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

Expected Behavior

Node-related flags should be passed through as-is.

Current Behavior

The code in the bin/next file (lines 35-37) is only looking for the --inspect flag, but none of its other forms. A recommended solution is to define an array of Node flags, look them up in the next arguments, and pass them as-is to the Node runtime.

Steps to Reproduce (for bugs)

Run next --inspect=0.0.0.0:9229

The server starts without a debugger endpoint.

Context

This issue affects when deploying the app to a local docker container or a Kubernetes pod since the debugger IP must be set to 0.0.0.0, or else it won't be exposed in the container/pod. Currently, there's no way to setup debugging in a container/pod.

Environment

Tech
Version

next
latest

node
8.9.3

OS
MacOS
Issue 1:
Test.ts:

declare module "test" {
module A {
class C {
}
}
class B extends E {
}
import E = A.C;
}

Command line:

node tsc Test.ts --declaration --module commonjs --target ES5

Error:

TypeError: Cannot read property 'indent' of undefined
at /Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:7839:63
at Object.forEach (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:1794:30)
at writeAsychronousImportDeclarations (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:7836:20)
at Object.writeSymbol (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:7852:25)
at writeType (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:9323:28)
at writeTypeToTextWriter (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:9314:20)
at Object.writeTypeAtLocation (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:14383:13)
at emitTypeOfTypeReference (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:8081:30)
at emitCommaList (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:7880:21)
at emitHeritageClause (/Users/meir/Source/TypeScript-1.1/TypeScript/bin/tsc.js:8077:21)

Issue 2:
The following used to work in TS 1.0.3, but crashes the compiler in 1.1 (and current master).

test.ts:

export function bar(a: foo.Foo) { }
import foo = require("foo");

foo.ts:

export class Foo { }

Using the latest master (30a49db):

$ node ../TypeScript/built/local/tsc.js -m commonjs -d test.ts

c:\Source\TypeScript\built\local\tsc.js:8255
for (var declarationIndent = aliasEmitInfo.indent; declara
^
TypeError: Cannot read property 'indent' of undefined
at c:\Source\TypeScript\built\local\tsc.js:8255:63
at Object.forEach (c:\Source\TypeScript\built\local\tsc.js:1873:30)
at writeAsychronousImportDeclarations (c:\Source\TypeScript\built\local\tsc.js:8252:20)
at Object.trackSymbol (c:\Source\TypeScript\built\local\tsc.js:8267:25)
at buildSymbolDisplay (c:\Source\TypeScript\built\local\tsc.js:9786:24)
at writeType (c:\Source\TypeScript\built\local\tsc.js:9826:25)
at Object.buildTypeDisplay (c:\Source\TypeScript\built\local\tsc.js:9817:24)
at Object.writeTypeAtLocation (c:\Source\TypeScript\built\local\tsc.js:15679:39)
at emitParameterDeclaration (c:\Source\TypeScript\built\local\tsc.js:8779:30)
at emitCommaList (c:\Source\TypeScript\built\local\tsc.js:8295:21)

The same crash occurs when using 1.1.0-1 from npm.

When removing the -d or using the 1.0.3 compiler from VS, it works fine.

Admittedly, it's more logical to have the import before the function, but a construct like this happened to be present in our sources.