WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Just a documentation issue that - http.ServeMux (cleanPath) gets also rid of duplicate /-s. http.ServeMux already contains:

ServeMux also takes care of sanitizing the URL request path, redirecting any request containing . or .. elements to an equivalent .- and ..-free URL.

I'm not sure how to reword it nicely to include the case of empty path segments, hence I didn't make a CL. Here's shortest example:

package main
import ("fmt"; "net/http")
func main() {
http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
fmt.Fprintf(w, "%s", r.URL.Path)
})
http.ListenAndServe(":8001", nil)
}

/hello////world will redirect to /hello/world. From URI standpoint they are different and both valid (https://tools.ietf.org/html/rfc3986#section-3.3).

Issue 2:
Some examples:

//Example 1
package main

import "fmt"

func main() {
const num = 1e1
s := make([]int, 10)
fmt.Println(s[num])
}

./test.go:8: non-integer slice index num

// Example 2
package main

import "fmt"

func main() {
const num = 1e1
s := make([]int, num)
fmt.Println(s[num])
}

panic: runtime error: index out of range

goroutine 1 [running]:
main.main()
/Users/kamil/tmp/test.go:8 +0xb6
exit status 2

num is assignable to a variable of type int, so shouldn't it work as a slice index as
well? It seems like it's being allowed in example 2 and triggering an out of range
panic, but disallowed in example 1.
Issue 1:
Hello Julia-ers!

When adding remote workers with addprocs(), I would really love to be able to send my current working environment along for the new Julia workers. Currently this does not happen for workers added using an SSHManager, though local workers do seem to inherit the same environment.

After browsing the repo, I think that this behavior could (gulp) easily be added by extending the code in managers.jl to set all, or some specified subset, of the current environment variables in the same way that JULIA_WORKER_TIMEOUT is set. Of course that might not be the default behavior, but maybe an option? Maybe something like (but not identical to):

# the default worker timeout
tval = haskey(ENV, "JULIA_WORKER_TIMEOUT") ?
`export JULIA_WORKER_TIMEOUT=$(ENV["JULIA_WORKER_TIMEOUT"])\;` : ``

envvals = map(key->`export $(key)=$(ENV[key])\;`, keys(ENV))

# Julia process with passed in command line flag arguments
cmd = `cd $dir '&&' $tval $envvals $exename $exeflags`

Is this a reasonable thing to propose? Please let me know if this is a terrible idea! Otherwise I will be happy to attempt to implement this. I just wanted to float the idea here first.

Thanks!

Issue 2:
Making the documentation omits dates.rst since it is not included in the main index.rst file.

$ make html
...
/Users/jiahao/local/src/julia/doc/manual/dates.rst:5: WARNING: Duplicate explicit target name: "here".
looking for now-outdated files... none found
pickling environment... done
checking consistency... /Users/jiahao/local/src/julia/doc/manual/dates.rst:: WARNING: document isn't included in any toctree
/Users/jiahao/local/src/julia/doc/stdlib/dates.rst:: WARNING: document isn't included in any toctree
...

The fix is easy; just include the line manual/dates somewhere in index.rst, but I'm not sure what order the chapters should be in.

cc: @quinnj
Issue 1:
Challenge Waypoint: Local Scope and Functions has an issue.

User Agent is: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:43.0) Gecko/20100101 Firefox/43.0.

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

My code:

function myFunction() {
var myVar = 1;
console.log(myVar);
}
myFunction();

// run and check the console
// myVar is not defined outside of myFunction

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

After following the instructions.

inside the function creata a variable myVar, as this

function myFunction() {
var myVar = "abc";
console.log(myVar);
}
myFunction();
console.log(myVar);

after this remove the second console.log line:

function myFunction() {
var myVar = "abc";
console.log(myVar);
}
myFunction();

the exercise don't pass.

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

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

The test asks you to remove the second console.log() to pass. When you remove the second console.log() it still fails. You have to remove both console.log() calls to pass(including the one inside myFunction().)

Reproducible every time by removing the console.log() outside of myFunction(), as asked by test. I'm assuming this is a bug in the test and not the text as there's no reason to remove the console.log() call within myFunction().
Issue 1:
by naomi.bancroft:

1. What is a short input program that triggers the error?
package main

func main() {
var max uint64 = 0
num := 1 << max
num += 1
}

2. What is the full compiler output?
bugreport.go:5: internal compiler error: agen OREGISTER

Please file a bug report including a short program that triggers the error.
http://code.google.com/p/go/issues/entry?template=compilerbug

3. What version of the compiler are you using? (Run it with the -V flag.)
8g version release.r58.1 8739

Issue 2:
by marius@vastech.co.za:

What steps will reproduce the problem?

Forward slashes cannot be escaped in a pattern. The following snippet does not compile:

re, err := regexp.Compile("\/out\/sctp\/5.*")

gives compiler error:

tstRegex.go:9: unknown escape sequence: /
(9 is the line in the actual test file)

The following program incorrectly matches the pattern to the test string:

package main

import(
"fmt"
"regexp"
)

func main() {
if re, err := regexp.Compile("/out/sctp/5.*"); err == nil {
fmt.Println(re.MatchString("/out/sctp/1420/0.753085.dat"))
}
}

When the pattern was replaced with:

re, err := regexp.Compile(".out.sctp.5.*")

It correctly matched all test strings. But this does not allow us to require a
"/" in the pattern.

What is your $GOOS? $GOARCH?

GOARCH=amd64
GOOS=darwin

Which revision are you using? (hg identify)

00a1813e5bc5 tip

Please provide any additional information below.
Issue 1:
[y ] I have searched the issues of this repository and believe that this is not a duplicate.

https://codesandbox.io/s/mjy74qv98

Is there any way to fix this?

Tech
Version

Material-UI
0.19.2

browser
Chrome V60

react-autosuggest
9.3.2

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

Expected Behavior

Theme nesting is not working as expected.

In below example, "MuiInput root of theme1" and "MuiInput underline of theme2" both should work.

Current Behavior

But here "MuiInput underline of theme2" works well but it does apply properties of "MuiInput root of theme1".

Steps to Reproduce (for bugs)

import React from 'react';
import { createMuiTheme, MuiThemeProvider } from 'material-ui/styles';
import Input, { InputLabel } from 'material-ui/Input';

const theme1 = createMuiTheme({
typography: {
fontFamily:
'Hind Vadodara',
body1: {
fontSize: 16,
},
},
overrides: {
MuiInput: {
root: {
fontSize: 16,
color: 'red',
},
}
},
});

const theme2 = outerTheme => ({
...outerTheme,
overrides: {
MuiInput: {
underline: {
'&::before': {
height: 0,
},
},
},
},
});

function Demo() {

return (
<MuiThemeProvider theme={theme1}>
<div>
<InputLabel style={{ margin :8 }}>Title</InputLabel>
<Input id="title" />
</div>
<div>
<MuiThemeProvider theme={theme2}>
<InputLabel style={{ margin :8 }}>Title</InputLabel>
<Input id="title" />
</MuiThemeProvider>
</div>
</MuiThemeProvider>
);
}

export default Demo;

Your Environment

Tech
Version

Material-UI
v1.0.0 beta.23

React
16.0.0
Issue 1:
This appears to be a defect that is specific to Intel's Math Kernel Library and the resolution will likely require changes therein. I'm submitting here as I believe the NumPy team has some relationships/connections with the Intel team and there have been some efforts to make MKL work well with NumPy (and SciPy). I am using Python 3.6.4, built from source on OSX 10.13.4 and Linux 16.04 (WSL). NumPy is built from source using gcc 7.1.0 on Mac and gcc 7.2 on Linux.

When executed with python3 this script will hang the terminal on OSX and Linux. No tests have been performed on Win64. If the size of the vector, x, is reduced by a factor of 10 to 1000, no hang is observed and the script executes correctly. The hang is specific to the call to linalg.norm. It is likely caused by multi-threaded execution of the norm() method using MKL's infrastructure, leaving the system in a state that interferes with Python execution of subprocess.run(). I also get a hang when using Python's Multiprocessing module process creation in place of subprocess.run().

This is important for a few reasons 1) Jupyter QtConsole & Notebook and IPython use subprocess.run() to execute certain os commands (such as ls). Hence we get a hang when working in all these applications. 2) If you want to spawn or fork to subprocesses to execute cpu intensive tasks you'll get a hang if you've previously called np.linalg.norm() with a sufficiently large vector (and perhaps many other NumPy and SciPy calls).

Reproducing code example:

import numpy as np
import subprocess

x = np.arange(10000) # 1000 shows no hang.
xnorm = np.linalg.norm(x)

subprocess.run('ls')

Error message:

No error message, just a hang.

Numpy/Python version information:

NumPy 1.14.3

Python 3.6.4

MKL: l_mkl_2018.3.222, m_mkl_2018.3.185

Issue 2:
Hello!

Linux Mint: 18.3 (Sylvia)

Python: 3.6.3

NumPy: 1.13.3

Cython 0.27.3

I am trying to build numpy and scipy wheels from source using the intel mkl compilers. Numpy compiles just fine, however when I run the test suite, the suite hangs on test_path_type_input within test_einsum.TestEinSumPath (or maybe the test after it? not sure because the last test name visible is this one; see screen cap)

Running the test suite for scipy results in the suite hanging on test_lapack within test_build.TestF77Mismatch

In both cases (numpy and scipy) the tests run and pass fine when run individually, so I'm not sure what else might be the cause.

Any help is greatly appreciated. See screen shot for images of the test suites when they're stuck is included.
Issue 1:
I have notices that since there are no longer spans everything element wrapper by comments content fails to display for IE and Edge.

Issue 2:
The following

var Hello = React.createClass({
render: function() {
return <div><p>Hello</p>test</div>;
}
});

results in only "Hello" being written in IE11 - jsfiddle

I realize there has been some changes to the way text nodes work in v15, but before we update our code to use <span>, I wanted to check if this is the intended behavior (since "test" is written in chrome).
Issue 1:
Seems to only be IE is not displaying correctly on RC1 as it still includes the mobile nav. I am currently looking into why and such but want to know if others can duplicate or if it was a change on my end.

Issue 2:
I'm trying to download a customized bootstrap, changing the @gridColumnWidth variable to 65px (so that my .span12 is 1000px).

The generated css includes 3 different declarations of .span12. The first one is the right one (1000px), then it gets overwritten by the following two.

Manually changing everything is not feasible.

Is there a bug with the builder or I'm missing something?
Issue 1:
Currently we don't have a consistent way of handling error in our build, which results in confusing or duplicate errors being logged to console.

some broccoli plugin logs stuff to console (e.g. broccoli-typescript plugin prints type errors) and throws at the end to indicate that a build failed

AngularBuilder captures any broccoli plugin errors, prints them and rethrows them

gulp tasks also print any errors caught and often add more task-level errors to the output

Issue 2:
I'm submitting a ... (check one with "x")

[ ] bug report => search github for a similar issue or PR before submitting
[x] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

There's no validator for <input type="email"> so users have to use pattern validator

Expected behavior

We should provide validators for basic input types

This is a duplicate of #2962 but it's too much for a single pr so I want to break it into multiple issues
Issue 1:
System information (version)

OpenCV => 3.1

Operating System / Platform => Windows 64 Bit

Compiler => Visual Studio 2015

Detailed description

waitKey() returns 255 instead of -1.

Steps to reproduce

#include <iostream>
#include <opencv/cv.hpp>

int main(int argc, char** argv)
{
cv::Mat test(480, 640, CV_8UC1);
test.setTo(0);
cv::imshow("test", test);
std::cout << cv::waitKey(1) << std::endl;
return 0;
}

Expected output

-1

Actual output

255

Issue 2:
System information (version)

OpenCV => ❔

Operating System / Platform => ❔

Compiler => ❔

Detailed description

Steps to reproduce

my cuda is NVIDIA 10.1, cudnn is 9.0, when i compile it:
Issue 1:
Is there an existing issue for this?

I have searched the existing issues

This issue exists in the latest npm version

I am using the latest npm

Current Behavior

Running npm -g update serverless@pre-3 wipes the content of the global node_modules directory (/usr/local/lib/node_modules).

Here is a log file of the command: https://gist.github.com/mnapoli/0170614e3f4ab1915a82783bf871d033

Here is what I tried to pinpoint the problem:

no problem with a local install (npm update serverless@pre-3)

npm -g i pure-prompt works

npm -g update pure-prompt works

npm -g i serverless works

npm -g update serverless works

npm -g i serverless@pre-3 works

npm -g update serverless@pre-3 ❌ wipes everything

yarn global add serverless works

yarn global update serverless@pre-3 works

Expected Behavior

Nothing should be removed, the package should be installed.

Steps To Reproduce

Run:

npm -g update serverless@pre-3

Now all global dependencies are gone (e.g. serverless, npm, etc.). The global folder /usr/local/lib/node_modules still exists, but it's empty.

I have to reinstall NPM and reinstall all global NPM dependencies.

Environment

npm: 8.3.0

Node.js: v17.3.1

OS Name: macOS

System Model Name: Bug Sur 11.6.2

npm config:

; "builtin" config from /usr/local/lib/node_modules/npm/npmrc

prefix = "/usr/local"

; "user" config from /Users/matthieu/.npmrc

//npm.pkg.github.com/:_authToken = (protected)
//registry.npmjs.org/:_authToken = (protected)

; node bin location = /usr/local/Cellar/node/17.3.1/bin/node
; cwd = /Users/matthieu/dev/PHP/bref
; HOME = /Users/matthieu
; Run `npm config ls -l` to show all defaults.

Issue 2:
Current Behavior:

Attempting to update a package with a tag using the update command globally causes ALL global packages to be removed.

Expected Behavior:

Packages should not be removed when updating global packages.

Steps To Reproduce:

npm i -g typescript nodemon @angular/cli # Install some global packages
npm ls -g --depth=0 # This shows the 3 installed packages
npm update -g @angular/cli@latest # Attempt to update one of the packages with a @latest tag
# Oh no! removed 620 packages
npm ls -g --depth=0 # Shows `-- (empty)

Environment:

OS: Windows 10 20H2

Node: 15.9.0

npm: 7.11.2

Additional Info

This only happens on the global scope
Issue 1:
Challenge Name

Issue Description

Browser Information

Browser Name, Version:

Operating System:

Mobile, Desktop, or Tablet:

Your Code

Screenshot

Issue 2:
Challenge http://www.freecodecamp.com/challenges/waypoint-clone-an-element-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

In this assignment the line of code still has to be placed outside of the function to work, but this time the function of clone and append has caused a duplication process that I cannot truly place into words. It simply has duplicated the element 10 times in the right well and an extra time in the left well.
Issue 1:
Describe the issue:

Using astype(np.float32) on integer array corrupts the data on ppc64el platform using numpy from conda-forge.

Reproduce the code example:

np.array([1, 0, 1, 0, 1, 0], dtype=int).astype(np.float32)

Error message:

array([0.0000000e+00, 0.0000000e+00, nan, 2.3509886e-38,
1.0000000e+00, 0.0000000e+00], dtype=float32)

### NumPy/Python version information:

1.22.3 3.10.4 | packaged by conda-forge | (main, Mar 24 2022, 17:42:07) [GCC 10.3.0]

Issue 2:
Describe the issue:

[I want to begin by first acknowledging that this is a fringe case of a bug appearing only in a VM (I haven't yet been able to reproduce it on real hardware), so please feel free to close this issue right away. However, I felt that I still should at least point it out, in case there is some latent real issue that this might uncover. In any case, hints as to how I can dig deeper into this so that I may report it to the proper channel (be it QEMU, GNU libc, or whatever) would be welcome.]

On a QEMU ppc64le VM, When casting an array of floats to np.intc, a weird truncation seems to happen. This only occurs in the VM; it does not happen onthe real ppc64le hardware I had access to (although that system hat an older 4.19 kernel; I cannot change that).

In the code below, I create arrays of value 1. of length 1 through 10, and then cast them to np.int64 and np.intc for comparison.

This works fine for arrays with length <= 3. If fails for longer ones, and apparently there is a pattern in this failure.

Reproduce the code example:

import numpy as np
for i in range(1, 11):
a = np.full(i, 1.)
print(i, a, a.astype(np.int64), a.astype(np.intc))

Error message:

1 [1.] [1] [1]
2 [1. 1.] [1 1] [1 1]
3 [1. 1. 1.] [1 1 1] [1 1 1]
4 [1. 1. 1. 1.] [1 1 1 1] [0 0 0 0]
5 [1. 1. 1. 1. 1.] [1 1 1 1 1] [0 0 0 0 1]
6 [1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1] [0 0 0 0 1 1]
7 [1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1] [0 0 0 0 1 1 1]
8 [1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0]
9 [1. 1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0 1]
10 [1. 1. 1. 1. 1. 1. 1. 1. 1. 1.] [1 1 1 1 1 1 1 1 1 1] [0 0 0 0 0 0 0 0 1 1]

NumPy/Python version information:

1.22.1 3.9.10 (main, Jan 16 2022, 17:12:18)

[GCC 11.2.0]
Issue 1:
$ python --version

Python 3.7.0

$ pip install numpy

...

Command "/usr/bin/python3 -u -c "import setuptools, tokenize;file='/tmp/pip-install-0jx06uto/numpy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" install --record /tmp/pip-record-b23lp18j/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /tmp/pip-install-0jx06uto/numpy/

Issue 2:
Am using Python 3.6.2 in MSYS2. The installation is unable to build the wheel:

Running setup.py bdist_wheel for numpy ... error

Then many pages are printed with the output of command setup.py bdist_wheel with warnings such as:

x86_64-pc-msys-gcc: _configtest.c

_configtest.c:1:5: warning: conflicting types for built-in function ‘sinf’

int sinf (void);

^~~~

After that it tries to run other commands with setup.py and it also fails:

Failed building wheel for numpy

Running setup.py clean for numpy

Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;file='/tmp/pip-build-pcj9wcf2/numpy/setup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" clean --all:

Running from numpy source directory.

setup.py clean is not supported, use one of the following instead:

- `git clean -xdf` (cleans all files)
- `git clean -Xdf` (cleans all versioned files, doesn't touch
files that aren't checked into the git repo)

Add --force to your command to use it anyway if you must (unsupported).

Failed cleaning build dir for numpy

Failed to build numpy

Installing collected packages: numpy

Running setup.py install for numpy ... error
Issue 1:
As of beta.1, .put and .post require a string body property (see also #6533).

It is a PITA to JSON.stringify the body object everywhere in our calling code. Other http clients (such as jQuery ajax) accept either string or object; they JSON.stringify the object for us.

Issue 2:
Such as:

developers using JSON 99.93% of the time and avoiding having to JSON.stringify things manually.

adding appropriate content-type headers when sending JSON.

possibly adding an operator like .json() as sugar for .map(res => res.json())
Issue 1:
Ok-Hyuns-MacBook-Pro:client olee$ npm install --save-dev @babel/parser

npm ERR! code ETARGET

npm ERR! notarget No matching version found for @babel/parser@^7.1.3

npm ERR! notarget In most cases you or one of your dependencies are requesting

npm ERR! notarget a package version that doesn't exist.

npm ERR! notarget

npm ERR! notarget It was specified as a dependency of '@babel/traverse'

npm ERR! notarget

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

npm ERR! /Users/olee/.npm/_logs/2018-10-11T16_32_17_220Z-debug.log

Issue 2:
EDIT 2: seems to have been resolved now

## EDIT (by @hzoo): Suggested workaround by @nikolas is to pin the version to the last available version (7.1.2) until the issue is resolved on the npm side. Also if you are on a proxy/cache check that it's up-to-date.

{
"devDependencies": {
"@babel/parser": "7.1.2"
}
}

Hi,

I'm getting this error when trying to install @babel/traverse. I'm on 10.12.0, npm 6.4.1 on Debian Linux.

$ npm i --save-dev @babel/traverse
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @babel/parser@^7.1.3
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@babel/traverse'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR! /home/nik/.npm/_logs/2018-10-11T16_20_54_846Z-debug.log