WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
🐛 Bug

My basic Conda environment is python 3.7, but creating a new environment and installing in it Pytorch ('conda install pytorch-nightly cuda92 -c pytorch'), python --version gives me 'Python 3.5.6 :: Anaconda, Inc.'.

This bug seems very similar to #9967, although the issue there is supposed to be closed, so I also left a comment there.

To Reproduce

Steps to reproduce the behavior:

Install Anaconda with python 3.7 and Cuda 9.2 on Ubuntu 16.04

Create a new environment

Check that python version is still 3.7

Install Pytorch with 'conda install pytorch-nightly cuda92 -c pytorch'

Check the python version now. In my case, it is now 3.5.6

Expected behavior

Pytorch is said to be working with python 3.7 in the download page, so there's no reason it would downgrade it.

Environment

PyTorch version: 1.0.0.dev20181022
Is debug build: No
CUDA used to build PyTorch: 9.0.176

OS: Ubuntu 16.04.3 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
CMake version: Could not collect

Python version: 3.5
Is CUDA available: Yes
CUDA runtime version: 9.2.148
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 396.37
cuDNN version: Could not collect

Versions of relevant libraries:
[pip] numpy (1.15.2)
[pip] torch (1.0.0.dev20181022)
[conda] cuda92 1.0 0 pytorch
[conda] pytorch-nightly 1.0.0.dev20181022 py3.5_cuda9.0.176_cudnn7.1.2_0 pytorch

Additional context

It's the first time I write an issue on Github, so I apologize in advance if it is not very clear or something ;)...

Thanks in advance for your help !!

Sebastien

Issue 2:
🐛 Bug

My basic Conda environment is python 3.7, but creating a new environment and installing in it Pytorch ('conda install pytorch-nightly cuda92 -c pytorch'), python --version gives me 'Python 3.5.6 :: Anaconda, Inc.'.

This bug seems very similar to #9967, although the issue there is supposed to be closed, so I also left a comment there.

To Reproduce

Steps to reproduce the behavior:

Install Anaconda with python 3.7 and Cuda 9.2 on Ubuntu 16.04

Create a new environment

Check that python version is still 3.7

Install Pytorch with 'conda install pytorch-nightly cuda92 -c pytorch'

Check the python version now. In my case, it is now 3.5.6

Expected behavior

Pytorch is said to be working with python 3.7 in the download page, so there's no reason it would downgrade it.

Environment

PyTorch version: 1.0.0.dev20181022
Is debug build: No
CUDA used to build PyTorch: 9.0.176

OS: Ubuntu 16.04.3 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
CMake version: Could not collect

Python version: 3.5
Is CUDA available: Yes
CUDA runtime version: 9.2.148
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 396.37
cuDNN version: Could not collect

Versions of relevant libraries:
[pip] numpy (1.15.2)
[pip] torch (1.0.0.dev20181022)
[conda] cuda92 1.0 0 pytorch
[conda] pytorch-nightly 1.0.0.dev20181022 py3.5_cuda9.0.176_cudnn7.1.2_0 pytorch

Additional context

It's the first time I write an issue on Github, so I apologize in advance if it is not very clear or something ;)...

Thanks in advance for your help !!

Sebastien
Issue 1:
I'm running atom on archlinux.

I have three config folders for atom that I found in my ~

.atom

.config/Atom

.config/Atom-Shell

It would be nice to move .atom to .config

Also one folder inside .config would be nice

while we're at it, for linux it's usual to have lower-case letters

Issue 2:
When splitting a pane you end up with the same file open in two panes. While splitting a file is a useful feature it should be separate from splitting panes. It is frustrating having to close the extra file view every time I split a pane.

I should be able to split panes without ending up with duplicate views of the same file, but I should also be able to split a file into multiple views if I want.
Issue 1:
This compiled as of yesterday, but no longer does:

fn main() {
let mut foo = ~[];
'foo: for i in [1, 2, 3].iter() {
foo.push(i);
}
}

test.rs:4:9: 4:12 error: unresolved name `foo`.
test.rs:4 foo.push(i);
^~~
error: aborting due to previous error

Renaming either the label or the variable fixes the error.

rustc 0.10-pre (329fcd4 2014-02-23 15:37:05 -0800)
host: x86_64-unknown-linux-gnu]

cc @edwardw

Issue 2:
After #24034 lands we will be setting CLOEXEC on all file descriptors on unix in the standard library. Currently we do so in a nonatomic fashion, however, so it's possible to continue to leak file descriptors into children if a thread is concurrently forking.

Many platforms have methods of creating CLOEXEC file descriptors atomically, but many of the APIs are quite new and they need to be properly detected at runtime. For example, the current instances of fd.set_cloexec() that need to be migrated are listed below. A reminder of our minimum platform requirements are linux 2.6.18 and OSX 10.7.

File::open - this should specify the O_CLOEXEC flag. This flag was added in linux 2.6.23 and appears to exist on OSX 10.7. #27971

Socket::new - this should be specify the SOCK_CLOEXEC flag in the type argument (second). This flag was only added in linux 2.6.27 and does not exist on OSX. #31417

Socket::accept - this should be replaced with a call to accept4. This system call was only added in linux 2.6.28 and does not exist on OSX. #31417

Socket::duplicate - this should be replaced with dup3 (linux 2.6.27, not on OSX) or F_DUPFD_CLOEXEC (linux 2.6.24, appears to exist on OSX 10.7). #27980

anon_pipe - this could be replaced with pipe2 on linux 2.6.27 and perhaps socketpair on OSX (not confirmed). #31417

The hard part about this bug is figuring out if it's possible to avoid compile-time detection of these functions (and instead rely on runtime detection).
Issue 1:
I am writing a simple todo list component with:

Vue.component('todo-list', {
props: ['todos'],
template:
`<ol>
<li v-for="(td, ix) in todos">
{{td}}
<button title="delete" @click="todos.splice(ix,1)">X</button>
<button title="move up" @click="todos.swap(ix,ix-1)" v-show="ix>0">^</button>
</li>
</ol>`,
})

For this to work I need (in core/observer/array.js) something like:

Array.prototype.swap = function(x,y) {
var t = this[x]
this[x] = this[y]
this[y] = t
}
const arrayProto = Array.prototype
export const arrayMethods = Object.create(arrayProto)

/**
* Intercept mutating methods and emit events
*/
;[
'push',
'pop',
'shift',
'unshift',
'splice',
'swap', // added
'sort',
'reverse'
]

It works when I (lazily) fixed dist/vue.js, but did not run the tests.

I think it is worth to add swap this way because notify() is run just once, am I wrong?

Issue 2:
Version

2.6.11

Reproduction link

https://github.com/dxvladislavvolkov/vue-issue

Steps to reproduce

Clone repo

Run npm i

Run npm run serve

Open console. You see the wrong parent element

What is expected?

I want to see my-comp2 as the parent of my-comp

What is actually happening?

I get #app element as the parent of my-comp

To reproduce I create two js files and create my components using extend. Then I import my files to index js and create global components using Vue.component. After it, I get the wrong parent of a component when I wrap my-comp
Issue 1:
So as per the documentation, I tried using two different offsets for desktop and phone. But I could not find the col-lg-offset on the CDN hosted css file.

http://netdna.bootstrapcdn.com/bootstrap/3.0.0-rc1/css/bootstrap.min.css

Am not sure if this is an issue or am I going wrong somewhere?

Issue 2:
To increase/decrease the size of form controls, you can add the classes input-lg or input-sm (at least according to the website [http://getbootstrap.com/css/#forms] - which is the most consistent solution). In the css code, however, the classes are called input-large and input-small.
Issue 1:
Describe the workflow you want to enable

Ability to plot the PR curve given probas_pred instead of estimator, X.

Describe your proposed solution

plot_precision_recall_curve() should accept either estimator, X or probas_pred.

Describe alternatives you've considered, if relevant

Alternatively, precision_recall_curve() could plot the PR curve if keyword argument plot=True.

Additional context

Issue 2:
The signature of plot_confusion_matrix is currently:

sklearn.metrics.plot_confusion_matrix(estimator, X, y_true, labels=None, sample_weight=None, normalize=None, display_labels=None, include_values=True, xticks_rotation='horizontal', values_format=None, cmap='viridis', ax=None)

The function takes an estimator and raw data and can not be used with already predicted labels. This has some downsides:

If a confusion matrix should be plotted but the predictions should also be used elsewhere (e.g. calculating accuracy_score) the estimation has to be performed several times. That takes longer and can result in different values if the estimator is randomized.

If no estimator is available (e.g. predictions loaded from a file) the plot can not be used at all.

Suggestion: allow passing predicted labels y_pred to plot_confusion_matrix that will be used instead of estimator and X. In my opinion the cleanest solution would be to remove the prediction step from the function and use a signature similar to that of accuracy_score, e.g. (y_true, y_pred, labels=None, sample_weight=None, ...). However in order to maintain backwards compatibility, y_pred can be added as an optional keyword argument.

TODO:

Introduce the class methods for the currently existing plots:

ConfusionMatrixDisplay #18543

PrecisionRecallDisplay #20552

RocCurveDisplay #20569

DetCurveDisplay #19278

PartialDependenceDisplay. For this one, we don't want to introduce the from_predictions classmethod because it would not make sense, we only want from_estimator.

For all Display listed above, deprecate their corresponding plot_... function. We don't need to deprecate plot_det_curve because it hasn't been released yet, we can just remove it.

for new PRs like #17443 and #18020 we can implement the class methods right away instead of introducing a plot function.
Issue 1:
System info

Playwright Version: 1.33.0

Operating System: Windows

Browser: Firefox

Other info: Node: 18.16.0

Source code

async runVisualChecksAfterProjectSave(headless) {
if (headless) {
// Start comparing snapshots on Custom tab
await this.customTabBtn.click();
await this.page.waitForLoadState("load", { timeout: 10 * 1000 });
await expect(async () => {
await expect(this.projectCard).toHaveScreenshot({
mask: [this.projectNameInput, this.footerRegisterLabel],
});
}).toPass({ timeout: 10000, intervals: [1000, 2000, 3000] });

Expected

As described on this feature wish: #20987

expect.toPass() should be walk around for image testing for pages that take bit more time to load content, goal is to reduce flaky tests. I would expect that toPass will retry toHaveScreenshot() for the timeout provided in toPass(). The default timeout for expect() is set for 5 sec. But in our case, assertion fails after 403s

Actual

Wrapping toHaveScreenshot() with expect.toPass should extend assertion timeout either for default timeout set for expect() or for timeout set inside toPass() and give us flexibility for visual testing.

Issue 2:
Playwright Version: 1.0.2

Operating System: Windows

Browser: Chromium

I use playwright for integration tests in my project and I have a page with many iframes that are loaded dynamically. When i receive a request, one of the iframes should be open, but chromium immediately disconnects after opening the iframe with the error:

messageWithStack.split is not a function

in this line

This is because the messageWithStack variable is false (boolean) and not a string type.

In browser firefox and webkit it works fine, without any disconnects.
Issue 1:
Bug report

Bug summary

Title sums it up all I guess.

Related:

Issue #3517 on Github

This and this on stack exchange

Here I used sinhala as Indic Script instance.

I think the font family has to do something with this issue since output to different font families are different. I'm not an expert in these stuff. Help appreciated to to get this work even with a different font family.

An example is given below for which I've tried with 3 different font families.

Code for reproduction

from matplotlib import rc
families = ['WARNA','LKLUG','Arial']
for familyname in families:
rc('font', family=familyname)
from matplotlib import pyplot as plt
import numpy as np
r = np.linspace(0.1,5,100)
A = 3*2/(r*2)+np.pi*r**2
fig = plt.figure()
axes = fig.add_axes([.1,.1,.8,.8])
axes.plot(r,A)
axes.set_ylabel(u'වර්ගඵලය')
axes.set_xlabel(u'අරය')
axes.set_title(familyname)

Actual outcome

Expected outcome

Result 1 looks fine but it has 2 problems:

Accents not been placed in the correct location. ("්" in "වර්ගඵලය" is placed after "ර" not before)

Letter "A" is not renderd in the title "WARNA"

Issues in result 2:

Same previous accent issue

Axis values or title not shown at all

Issues in result 3:

No Sinhala script shown.

Versions

Software
Version

Python
2.7.13 64bit [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)]

IPython
5.1.0

OS
Linux 4.4.0 78 generic x86_64 with debian jessie sid

matplotlib
1.5.1

(Matplotlib from anaconda bundle)

Wed Jun 14 22:54:11 2017 +0530

Issue 2:
a normalized distribution should have sum(bins) = 1 or at least be able to have this as an option
Issue 1:
Given the following code:

trait Stream<T, N: Stream<T>> {
}

pub fn main() {
println!("zomg");
}

Running rustc gives the following output:

task 'rustc' has overflowed its stack
[1] 47380 illegal hardware instruction rustc types.rs

Issue 2:
Compiling the following:

trait Chromosome<C: Chromosome> {
fn random() -> C;
}

Causes the following output:

task 'rustc' has overflowed its stack
Illegal instruction

The code was an unintentional typo, and probably isn't valid, but I think the compiler should handle this a lot better, as there's no indication of what the problem is, or where it lies. In large compilation units with complex templating etc., that could be a big roadblock.
Issue 1:
Atom 0.196.0

Mac OS X 10.10.3

"Reveal in tree view" does not always put tree view selection on revealed file. It seems to depend on the previous selection/collapse state of the tree view. Here's an example of a repro:

Note that if you just collapse the tree and then reveal the file, it works fine, but if you change the selection to the other directory, then collapse the tree, then choosing "reveal in treeview" expands the tree to reveal the correct file, but the selection stays on the root directory.

Issue 2:
Repro steps:

Open the image-view repository in safe mode atom --safe

Open the spec/fixtures folder

Open binary-file.png

Collapse the spec folder

Collapse the root folder (image-view)

Right click on the image and select Reveal in Tree View from the context menu

Expected:

binary-file.png to be highlighted because it was revealed

Actual:

The spec folder is expanded but the file is not selected

Repro Steps:

Open file inside a folder that visible in the tree view

Collapse folder with file

In file, right click and select Reveal in Tree View

The desired behavior is that the file is highlighted and not the parent folder. The desired behavior happens if the folder is expanded.

Windows 7, Atom Version 0.115.0
Issue 1:
I was getting a problem where the only lighting affecting the json model, with its default phong shading, was ambient.

I believe the issue was the bump scale array as changing this to a value to not an array ie 1.0 fixed the issue for me...

"mapBumpScale":[10.0,10.0]

Is this a new feature for bump map materials that we are be able to adjust x and y offset?...and for what version is this compatible with?

Json Exporter vers 1.5.0

r77 (npm version)

Blender 2.77

OSX Mac El Capitan 10.11.6

Issue 2:
When exporting a model from Blender to the threejs json format the materials bumpScale properties are arrays, while threejs expects regular values.

Actual export:

"bumpScale":[0.1,0.1]]

Expected by threejs:

"bumpScale": 0.1

Three.js version

r77
Issue 1:
First of all, let me say sorry for the fact that this issue will most probably not comply with the issue reporting guidelines. This is due to the fact that I am not a developer using electron but just a user using electron apps, in particular Franz (http://meetfranz.com) and Skype (the new electron version of it). Since the issue I want to report appeared in both apps, I assume that it is an issue of electron itself, but if I am wrong here, let me know.

The issue is of rather cosmetic nature: The text color in the menu bar seems to be hard coded to white when not hovered and black when hovered. This leads to the problem that in dark themes the text becomes hard to read when hovered and on light themes when not hovered. Here are some screenshots demonstrating the issue in Skype:

Light theme, not hovered:

Light theme, hovered:

Dark theme, not hovered:

Dark theme, hovered:

Electron version: Unknown, I'm using binary packages of Franz and Skype.

Operating system: Manjaro Linux

Expected behavior

The text color in the menu bar should follow the theme settings like in native (GTK) applications

Actual behavior

The text color is hard to read if hovered on dark themes or not hovered on light themes

How to reproduce

Use Skype or Franz on Linux with light or dark GTK themes.

Issue 2:
Google recently added a "use_gtk3" build flag to Chormium - export GYP_DEFINES="$GYP_DEFINES use_gtk3=1"﻿.

I think most end-users on GTK3 desktops would prefer to use modern widgets. It might be too early to add it as a default, but eventually it be nice.

Video of Chromium 47 w gtk3:

https://www.youtube.com/watch?v=TJidbdaHCYc

This somewhat relates to an old issue I opened up:

#765
Issue 1:
I didn't find the Deno in the docker hub.

Is there an official container ?

Issue 2:
@hayd started a while https://github.com/hayd/deno-docker

This can be ported to be integrated as the Official Deno docker image. So 3 steps are needed:

Integrate generation of docker image in the CI

Test the generated docker image

Publish image on the docker hub / github hub on release

Also do we plan to release on docker hub only or we push it to github registry also? It's just a matter of URL in the command in the CI but @ry and @piscisaureus have to create / set credentials in the project.
Issue 1:
Bug report

Describe the bug

my nextjs version is 9.1.7-canary.14,but it's still not work when I downgrade to 9.0.0

here the code is:

import Router from 'next/router';
...
handleClick = (index) => {
Router.push('/user');
};
...
<div onClick={this.handleClick}>click</div>

I've tried :

import {withRouter} from'next/router'

import Link from'next/link'

and all above don't work on ios10.x.x

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

create-next-app next-demo

cd next-demo and create a new test page file in pages folder 'test.js',and then type some code in this file

import React from 'react'
const Test = (props) => (
<div>
test
</div>
)
export default Test

and add router to home page:

import {useRouter}from 'next/router'

const router=useRouter()

the whole test content in home.js is:

import React from 'react'
import {useRouter}from 'next/router'
const Home = () => {
const router=useRouter()
const handleClick=()=>{
console.log('click')
router.push('/test')}
return (
<div>
<h1 className="title" onClick={handleClick}>welcome to Next!</h1>
</div>
)}
export default Home

start developing,run yarn dev,you will find that all above works well ,you click the h1 tag and page changed, but this will not work on ios 10.x.x

Expected behavior

next/router support ios10.x.x

Screenshots

If applicable, add screenshots to help explain your problem.

System information

OS:ios10.0.1 and ios10.2 and ios10.3 are tested,not work

Browser (if applies) [e.g. chrome, safari]

Version of Next.js:9.1.7 &9.0.0 &9.1.7-canary.14

Additional context

Add any other context about the problem here.

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

Expected Behavior

yarn build should build app.

Current Behavior

Failing with

yarn build v0.27.5
$ next build
> Using external babel configuration
> location: "/Users/steida/dev/este/.babelrc"
> Using "webpack" config function defined in next.config.js.
(node:45475) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'indexOf' of null
(node:45475) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

3.0.1-beta.14 works.
Issue 1:
I found what looks like a bug/oversight.

jjulia> d = Dict(i=>rand() for i in 1:3)
Dict{Int64, Float64} with 3 entries:
2 => 0.192129
3 => 0.340718
1 => 0.154868

julia> v = [d,d]
2-element Vector{Dict{Int64, Float64}}:
Dict(2 => 0.19212863767897548, 3 => 0.34071840174647483, 1 => 0.15486801172387077)
Dict(2 => 0.19212863767897548, 3 => 0.34071840174647483, 1 => 0.15486801172387077)

julia> union(keys.(v)...)
Set{Int64} with 3 elements:
2
3
1

julia> union(keys.(v[1:1])...)
ERROR: MethodError: no method matching copy(::Base.KeySet{Int64, Dict{Int64, Float64}})
Closest candidates are:
copy(::Union{SubArray{T, N, var"#s5", I, L} where {var"#s5"<:(PooledArrays.PooledArray{T, R, N, RA} where {N, RA}), I, L}, PooledArrays.PooledArray{T, R, N, RA} where RA} where {T, N, R}) at /home/joe/.julia/packages/PooledArrays/CV8kA/src/PooledArrays.jl:212
copy(::SubArray{var"#s832", var"#s831", var"#s830", I, L} where {var"#s832", var"#s831", var"#s830"<:Union{SparseArrays.AbstractSparseMatrixCSC, SparseArrays.SparseVector}, I, L}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.6/SparseArrays/src/sparsevector.jl:720
copy(::SubArray) at subarray.jl:70
...
Stacktrace:
[1] union(s::Base.KeySet{Int64, Dict{Int64, Float64}})
@ Base ./abstractset.jl:49
[2] top-level scope
@ REPL[30]:1

When I use union(Set.(keys.(v[1:1))...) it works as expected.

Issue 2:
julia> d = Dict(1=>2)
Dict{Int64,Int64} with 1 entry:
1 => 2

julia> union(keys(d))
ERROR: MethodError: no method matching copy(::Base.KeySet{Int64,Dict{Int64,Int64}})

julia> union(keys(d), keys(d))
Set([1])
Issue 1:
report error:

Error:Failed to resolve: annotationProcessor

Error:Failed to resolve: com.android.support:support-annotations:26.0.2

on

compileSdkVersion 25

buildToolsVersion '25.0.3'

compile 'com.github.bumptech.glide:glide:4.1.1'

compile 'com.github.bumptech.glide:okhttp3-integration:4.1.1@aar'

annotationProcessor 'com.github.bumptech.glide:compiler:4.1.1'

Issue 2:
After adding the latest gradle 4.1.1:

compile 'com.github.bumptech.glide:glide:4.1.1'

compile 'com.android.support:support-v4:25.3.1'

annotationProcessor 'com.github.bumptech.glide:compiler:4.1.1'

It says failed to resolve annotationProcessor. I need to revert to 4.0.0 release to make this work