WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This is a CLI Docs Problem, not another kind of Docs Problem.

This is a CLI Docs Problem.

Description of Problem

Visiting this page, there are 2 "description" sections, using the reference #description with a link will point to the first description section link.

You cannot copy a link to the "description" package.json file field.

The right side indexing panel shows it as "#description-1" (link) but it wont redirect the user to that section since its labeled as "description" for some reason.

Potential Solution

GitHub supports the *-1 indexing method, it should be implemented similarly, or just tweak with the markdown file.

Affected URL

https://docs.npmjs.com/cli/v8/configuring-npm/package-json#description-1

Issue 2:
Hello! Can you please help me with the following problem: I cannot install SASS packages for my project. I created a folder for my sass project. There’s a package son file inside. Now I need to download node modules for it: gulp-sourcemap, autoprefixer, gulp-if, gulp-concat, gulp-clean-css and browser-sync.

I’m doing everything with MacOS Terminal.

I type in $ npm install --save-dev gulp-sass.

The reply I get is the following:

MacBook-Pro-Anastasia:SASS anastasia$ npm install --save-dev gulp-sass

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:

npm ERR! https://npm.community

npm ERR! A complete log of this run can be found in:

npm ERR! /Users/anastasia/.npm/_logs/2020-01-30T05_00_30_646Z-debug.log

It repeats with all the packages which I’m trying to install.

I’ve tried to update Gulp itself. Then But I failed and got the same reply "cb() never called!"

gulp -v

CLI version: 2.2.0

Local version: Unknown

Please can you help me? How can I fix this problem?

My node and npm version details are--

node -- 13.3.0

npm -- 6.13.1

System Information --

Operating System: MacOS High Sierra 10.13.6
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/8651/

Failed: [k8s.io] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:213
Jun 7 05:27:19.217: The test requires two Ready nodes on gke, but found just one.

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): It's a bit tough to search for this since this includes a lot of keywords.

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Question

Pretty much what the title says. I'm asking because sometimes I want to kill a pod for good but I don't remember what I used to create it.
Issue 1:
by happyalu:

When using cgo to compile for linux/386 on a linux/amd64 host, I get this error:
unexpected GOT reloc for non-dynamic symbol.

Small Code to reproduce the error is at http://play.golang.org/p/WfasIPKzKH

Running:
$ GOARCH=386 go build

produces:
unexpected GOT reloc for non-dynamic symbol x

The reloc in question here is a R_386_GOT32 reloc for the global 'x'.

--- Disassembly Snippet
00000020 <g>:

20: 53 push %ebx
21: e8 fc ff ff ff call 22 <g+0x2>
22: R_386_PC32 __x86.get_pc_thunk.bx
26: 81 c3 02 00 00 00 add $0x2,%ebx
28: R_386_GOTPC _GLOBAL_OFFSET_TABLE_
2c: 83 ec 08 sub $0x8,%esp
2f: e8 fc ff ff ff call 30 <g+0x10>
30: R_386_PLT32 f
34: 3b 83 00 00 00 00 cmp 0x0(%ebx),%eax
36: R_386_GOT32 x
3a: 0f 94 c0 sete %al
3d: 83 c4 08 add $0x8,%esp
40: 0f b6 c0 movzbl %al,%eax
43: 5b pop %ebx
44: c3 ret

---

cmd/8l/asm.c seems to handle only the MOVL instruction for R_386_GOT32 reloc of
non-dynamic symbols. The instruction this code generates is CMP.

I was able to work around this problem by basically adding a GOT entry for the symbol,
as if it were a dynamic symbol. That seemed to work both for this minimal example and
the real code I was trying to get working.

But I not quite sure what the actual fix here is :)

Which version are you using? (run 'go version')
go version devel +7cb3730e3f37 Fri Feb 08 19:24:50 2013 +0400 linux/amd64

Issue 2:
by ckolbeck:

Before filing a bug, please check whether it has been fixed since
the latest release: run "hg pull -u" and retry what you did to
reproduce the problem. Thanks.

What steps will reproduce the problem?
1. visit http://golang.org/pkg/os/#Variables

What is the expected output?
Single entry

What do you see instead?
Double entry

Please provide any additional information below.
as of 10/1/10 1100 PDT
Issue 1:
I worked hard all day to figure out this one.

I use Scrollspy and navbar to navigate on a single page.

I have defined blue as the background color for the rollover in navbar:

If I click on a link and afterwards scroll to the next anchor the link that I first clicked on still got a blue background _ and the new anchor point has a blue background also:

Hope my explanation makes sense :-)

Kind Regards

Issue 2:
The menu icon doesn't change back to the "default" state once you close the menu. Here's a youtube video of it in action.
Issue 1:
I'm submitting a ...

[x ] bug report => search github for a similar issue or PR before submitting

[ ] feature request

Current behavior

Angular does not update the browser once it runs.

For instance, if you have a label and an input, if you bind the "for" attribute of the label to the "id" attribute of the input via a passed input, the browser will not recognize that the two are linked because Angular does not let the browser know it updated the DOM.

EXAMPLE MARKUP

<myInput id="input1"></myInput>

EXAMPLE COMPONENT

@Input id: string;

EXAMPLE COMPONENT MARKUP

<label [for]="id">My Label</label> <input [id]="id" type="text" />

RESULT:

Clicking the label does not apply focus to the input. This can also be seen with labels of radio buttons and checkboxes, where clicking the label does not produce the desired default browser behavior of interacting with the associated element.

RESULT:

Clicking labels for related inputs does not interact with the assigned element.

Expected behavior

Default browser behavior should be maintained when associated form elements via for and id.

Minimal reproduction of the problem with instructions

http://plnkr.co/edit/jJeqHAbO7vNVLV9GTvQW?p=preview

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

Should be able to use Angular to create dynamic components without having to reproduce default browser behavior. All form elements usingfor and id linking do not work as expected when given a dynamic value

Please tell us about your environment:

Windows 7, VSCode, NodeJS, Angular Generator

Angular version: 2.0.X

2.3.0

Browser:

all

Language:

all

Node (for AoT issues):

6.8.0

Issue 2:
Hey guys, I have a problem using http requests...

My code:

services/home.ts

import {Http} from 'angular2/http';
export class HomeService {
list: Object;
constructor(){
}
getAll(http: Http){
http.get('/api/todo/')
// Call map on the response observable to get the parsed people object
.map(res => res.json())
// Subscribe to the observable to get the parsed people object and attach it to the
// component
.subscribe(todo => this.list = todo);
}
}

components/home.ts

import {View, Component, NgFor} from 'angular2/angular2';
import {coreDirectives} from 'angular2/directives';
import {httpInjectables, Http} from 'angular2/http';
import {HomeService} from 'home/services/home';

@Component({
selector: 'home',
appInjector: [HomeService,httpInjectables]
})
@View({
templateUrl:`modules/core/home/views/home.html`,
directives: [coreDirectives, NgFor]
})
export class HomeComponent {
homeService: HomeService;
constructor(homeService: HomeService, http: Http) {
this.homeService = homeService;
homeService.getAll(http);
}
}

home.html

<h1>Todo List</h1>
<ul>
<li *ng-for="#todo of homeService.list; #i = index">
{{i}} - {{ todo.name }} {{todo.checked}}
</li>
</ul>

So, when I use homeService.getAll(http); in the Component, I get the list of items, but duplicated...

If I don't use this call, the list do not appear

What's the better way to do this correctly?

Thanks! 😄
Issue 1:
[x ] I have searched the issues of this repository and I believe this is not a duplicate

Expected Behavior

Adding Script tags got the Google Custom Search in HTML section with JSX should be supported or provide alternative ways

Current Behavior

Throws the following error

app/pages/index.js?entry: name.charAt is not a function

Steps to Reproduce (for bugs)

Add the following code in HTML section of JSX page inside a DIV.

<script> (function() { var cx = '0089289843748653:ikyblft4'; var gcse = document.createElement('script'); gcse.type = 'text/javascript'; gcse.async = true; gcse.src = 'https://cse.google.com/cse.js?cx=' + cx; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(gcse, s); })(); </script> <gcse:search></gcse:search>:search></gcse:search>

I also tried with following but didn't work

App.componentDidMount = () => { var embedcode = <script>

(function() {

var cx = '013626029654558379071:ze3tw4csia4';

var gcse = document.createElement('script');

gcse.type = 'text/javascript';

gcse.async = true;

gcse.src = 'https://cse.google.com/cse.js?cx=' + cx;

var s = document.getElementsByTagName('script')[0];

s.parentNode.insertBefore(gcse, s);

})();

</script>

gcse:search</gcse:search>`

$('#gsearch').html(embedcode)

}`

Context

Trying to add Google Custom Search to my site created in NextJS

Your Environment

Tech
Version

next
4.2.1

react
16.2.0

OS
Mac

browser
Chrome

node
latest

Issue 2:
I think a client-side pushState should be performed BEFORE getInitialProps.

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

Expected Behavior

I think the correct way is to perform pushState first, leaving the unfetched data as default value, so that we can render the static part of the page, and dynamic part of the page will be blank or filled with loading spinners, just like what we do in writing a totally client-side-rendered project. After this, data fetching will be performed and dynamic data will be fed to the page asynchronously.

Current Behavior

Currently, in a client-side routing, pushState will be performed after the execution of getInitialProps of the destination page. So if the async data fetching in getInitialProps takes 5 seconds, the client-side will do nothing during the 5 seconds, leading to a bad user experience.

Context

This issue leads to a delay when I click any <Link> in client-side.

Your Environment

Tech
Version

next
4.2.1

node
8.9.1
Issue 1:
As I said in the last post I am implementing a web browser in the Atom editor using an iFrame. It works well except for one problem that seems to be an atom-shell problem.

When I browse most pages, like apple.com, atom.io, etc., the iFrame webpages work great. But when I go to gmail.com or github.com (irony much?) the page loads and then one second later the entire desktop window disappears with no errors shown. The reason I am assuming an atom-shell problem is that I've never seen the editor crash like this and because this is all happening inside an iFrame which is a feature of atom-shell.

How can I debug this?

I'm on windows 8.0 with atom-shell included in atom editor 0.136.0.

Issue 2:
For example, if you try to create an atom-shell app that has an iframe that references github.com, Github uses an iframe breaking technique to redirect the top window to the src of the iframe.

<iframe src="http://www.github.com/" name="disable-x-frame-options" sandbox="none"></iframe>

Is there anyway to trick the iframe to make it think it is the top window?

If not, what is the best way to manage a bunch of individual BrowserWindows inside of a main window?
Issue 1:
From statistics point of view standard deviation when all values are equal should be 0. For arr1 result is as expected: 0, but for arr2 is 1.3877787807814457e-17 - very small but not 0, which leads to issues with e.g. zscore.

As discussed here: https://stackoverflow.com/questions/63772729/numpy-std-standard-deviation-function-weird-behavior issue is caused by floating errors.

I think the problem could be solved by checking for "equality" before calculating std = sqrt(mean(abs(x - x.mean())**2)); when all values are equal std should return 0.0

Why this is important? For example zscore from scipy.stats is calculated as "(x-np.mean)/np.std ". Division by 0 return np.nan but division even by small number gives "proper number", but it also should be nan.

Reproducing code example:

import numpy as np
arr1 = [20.0] * 3
#[20.0, 20.0, 20.0]

arr2 = [-0.087] * 3
#[-0.087, -0.087, -0.087]

np.std(arr1) #0.0
np.std(arr2) #1.3877787807814457e-17

Numpy/Python version information:

1.19.1 3.6.9 (default, Jul 17 2020, 12:50:27) [GCC 8.4.0]

Issue 2:
NumPy may give a nonzero variance (and thus standard deviation) for a constant array. This may be due to loss of numerical precision, but Pythons builtin variance routine gives the correct 0 answer, so clearly it's a preventable loss:

In [45]: x = [6715266981.538051]*10

In [46]: statistics.variance(x)
Out[46]: 0.0

In [47]: numpy.array(x).var()
Out[47]: 9.0949470177292824e-13

I think it would be highly desirable if x.std() and x.var() for a constant array could be assumed to be exactly identical to zero. I'm aware one should not compare floating point numbers but zero is a bit of a special case.
Issue 1:
If InputRow.getDimensions() has duplicates, IncrementalIndex.add() fails with

java.lang.ArrayIndexOutOfBoundsException: 4

at com.metamx.druid.index.v1.IncrementalIndex.add(IncrementalIndex.java:148)

at com.metamx.druid.realtime.Sink.add(Sink.java:98)

at com.metamx.druid.realtime.RealtimeManager$FireChief.run(RealtimeManager.java:176)

[12:29pm]

Issue 2:
Hi,

We are facing an exception in overlord in a production environment while announcing the Historical Segment.

It looks to me some sort of multi-threading issue (if thats possible ) as the segment is already present in the MetaData and still the "segmentExists" method (IndexerSQLMetadataStorageCoordinator.java+581) is returning "FALSE" on some of the times .

We are using druid-0.9.1 in our production.

Following is the Logs :

2017-08-08 06:15:02.534+0000 INFO io.druid.metadata.IndexerSQLMetadataStorageCoordinator Found [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] in DB, not updating DB

2017-08-08 06:15:01.692+0000 ERROR io.druid.metadata.IndexerSQLMetadataStorageCoordinator Exception inserting segment[prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] into DB

org.skife.jdbi.v2.exceptions.UnableToExecuteStatementException: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "druid_segments_pkey"

...

Detail: Key (id)=(prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5) already exists.

Show all 89 lines

2017-08-08 06:15:01.690+0000 INFO [qtp1997290658-83] io.druid.metadata.IndexerSQLMetadataStorageCoordinator Published segment [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] to DB

In above logs it is clear the the segment [prod_report_ds_2017-08-08T05:00:00.000Z_2017-08-08T06:00:00.000Z_2017-08-08T05:00:04.589Z_5] has already been inserted in the postgres (metadata) but still overlord throws an exception. Also the very first line (after around 1 minute difference), "segmentExists" would have returned true.

Note the time between last two logger lines , hardly in milliseconds. Is it possible that two thread would have come at this method (announceHistoricalSegment) and executed segmentExists without knowing about each other (Race Condition)

More Details : https://groups.google.com/forum/#!topic/druid-user/8hFWfsD6THk
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

May be it is related to this: #7695 . I believe is a different issue.

Expected Behavior

I would expect the components to appear or disappear based on a breakpoint change.

Current Behavior

Check the gif

The elements appear, however they don't disappear, also the style is lost. See the MenuIcon.

Steps to Reproduce (for bugs)

It is a Gatsby project: https://github.com/Zetoff/portfolio/tree/feature/responsive-navbar

or http://wiry-hour.surge.sh/test/

Clone repo

Install Gatsby if you don't have it.

Run Gatsby

Access localhost:8000/test

Change viewport size.

Context

I am trying to build a responsive AppBar

Your Environment

Tech
Version

Material-UI
1.0.0.-beta8

React
15.6.1

browser
Chrome, Safari

etc
macOS-latest

Issue 2:
Problem description

On the demo, change width and responsive change fails with

Uncaught TypeError: context[CHANNEL].unsubscribe is not a function
at Object.unsubscribe (themeListener.js:27)
at Style.componentWillUnmount (withStyles.js:116)
at ReactCompositeComponent.js:408
at measureLifeCyclePerf (ReactCompositeComponent.js:75)
at ReactCompositeComponentWrapper.unmountComponent (ReactCompositeComponent.js:407)
at Object.unmountComponent (ReactReconciler.js:78)
at ReactCompositeComponentWrapper.unmountComponent (ReactCompositeComponent.js:417)
at Object.unmountComponent (ReactReconciler.js:78)
at Object.unmountChildren (ReactChildReconciler.js:146)
at ReactDOMComponent.unmountChildren (ReactMultiChild.js:371)

Link to minimal working code that reproduces the issue

demo

Versions

Material-UI: 72970c5

React: 15.6.1

Browser: chrome and canary
Issue 1:
Hey team,

Since the last version of deno, compile cmd produce a strange error:

TypeError: Number.isInteger is not a function
at queue (file://$deno$/bundle.js:4976:17)
at ProjectResolver.resolveProjects (file://$deno$/bundle.js:7655:31)
at async Sync.process (file://$deno$/bundle.js:8498:34)
TypeError: Number.isInteger is not a function
TypeError: Number.isInteger is not a function
at queue (file://$deno$/bundle.js:4976:17)
at ProjectResolver.resolveProjects (file://$deno$/bundle.js:7655:31)
at async Sync.process (file://$deno$/bundle.js:8498:34)

It works greatly with deno run. And compile works on Deno 1.11.2.

I don't have more log than that.

Issue 2:
After upgrading to version 1.14 this error happened when using deno bundle

Example test.ts code:

import { Application } from "https://deno.land/x/oak@v9.0.0/mod.ts";

const app = new Application();

app.use((ctx) => {
ctx.response.body = "Hello World!";
});

await app.listen({ port: 8000 });

Commads:

deno bundle test.ts out.js
deno run -A out.js

Error:

error: Uncaught ReferenceError: Cannot access 'Response' before initialization
const DomResponse = Response;
^

Deno version

deno 1.14.0 (release, x86_64-apple-darwin)
v8 9.4.146.15
typescript 4.4.2
Issue 1:
Describe the bug

When using axios.delete and sending config.data, the server receives no body

To Reproduce

Make a call using axios delete and send data via the config object. This used to work in v0.19.2 but doesn't work in v0.20.0 anymore.

axios.delete(BASE_URL + '/user', {
headers: {
Authorization: this.authToken
},
data: {'userId':'abcd1234'}
})

Expected behavior

Server should receive data-> body

Environment

Axios Version [0.20.0]

Node.js Version [12.18.3]

Additional context/Screenshots

using v0.19.2 server gets:

'body': '{"userId":"abcd1234"}'

using v0.20.0 server gets:

'body': None

Issue 2:
Describe the bug

Axios last version (0.20.0) does not use data from config when making DELETE request. In 0.19.2 it's working fine

To Reproduce

axios.delete("...", {
data: { ids: [...] },
}).then(response => {
...
}).catch(error => {
...
});

Expected behavior

Axios send request data from config when making DELETE request

Environment

Axios Version 0.20.0

Browser Chrome

Browser Version 84.0.4147.125

Node.js Version 12.18.3

OS: Linux Mint

Additional Library Versions React 16.13.1

Additional context/Screenshots

None
Issue 1:
I'm building a fairly large library for ios which is working great. Its about 20MB for each architecture.

However, the build times are really starting to take their toll. They are now taking around 5 minutes to build which is tough for productivity. It would be great to be able to speed up these time by perhaps caching some of the build data.

I'm not sure of the process but it seems for every build, bind generates a new random temporary folder for all the files, where perhaps, it could use a cached folder and reuse previously built object files?

Issue 2:
This can't really be called a bug, but it is potentially sub-par behaviour. It is a follow on from a suggestion I made in #12245.

gomobile bind currently generates binding code every time it is run. This has the following side effects:

Access to source for debugging: When debugging application errors in the wild, it is useful to have the source available. In the case of native libraries, we can use vendoring or the native package manager for versioning. With gobind however, the source is not easily available. It can be generated by manually running gobind, but there are a few concerns with this approach.

The options passed to gobind are opaque to the user: Currently there are no options, but if this changes in the future it becomes a guessing game.

Upgrades of the gobind tool can result in source changes: For production releases we will need to track the exact version of gomobile used to generate the library. This is fine once gobind is stable (for example with cgo now). However, it is problematic for early adopters since changes are being made to gobind on a regular basis.

Incremental builds: In an SDK app, gomobile bind must be run on source changes to regenerate the new framework/aar. There are two ways of approaching this. Manually run gomobile bind or have the IDE (XCode/Android Studio) invoke it before compiling the ObjC/Java source. The former, while not a chore, can be error prone. The latter is more robust, but results in the framework/aar being rebuilt even if no go source is changed. This adds delays to the code -> compile -> test cycle and negatively impacts our workflow. It also takes away one of the advantages of go which are its near instantaneous build times.

One solution would be for gomobile bind to accept a command line flag which specifies the directory in which to generate code and then skip regenerating code on every run.

This is more a nice to have rather than a need to have since there are workarounds present.