WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
I think there may be a bug with some of the LR schedulers eg StepLR. essentially if the epoch is a multiple of the step size, the LR will keep multiplying by gamma, even if the epoch never increases:

sched = torch.optim.lr_scheduler.StepLR(opt, 2, 2.) # step size = 2, gamma = 2
for i in range(5):
opt.step()
opt.step()
sched.step(epoch=2) # fix the epoch
print(opt.state_dict()['param_groups'][0]['lr'])

2.0
4.0
8.0
16.0
32.0

versus if epoch % step_size != 0:

sched = torch.optim.lr_scheduler.StepLR(opt, 2, 2.) # step size = 2, gamma = 2
for i in range(5):
opt.step()
opt.step()
sched.step(epoch=3) # fix the epoch
print(opt.state_dict()['param_groups'][0]['lr'])
1.0
1.0
1.0
1.0
1.0

IIUC, calling sched.step(epoch=i) multiple times should be idempotent. Note that this seems to have been introduced in 1.1; 1.0 works as intended.

Pytorch 1.1.0

Python 3.6.5

Issue 2:
When the StepLR, MultiStepLR, ExponentialLR or CosineAnnealingLR scheduler is called with the same epoch parameter the optimizer value is further reduced even though it's the same epoch

a sample code

import torch.optim as optim
from torch import nn

conv = nn.Conv2d(3,3,3)
optimizer = optim.Adam(conv.parameters())
lr_scheduler = optim.lr_scheduler.StepLR(optimizer, 2)

now if we call lr_scheduler.step(epoch=2) multiple times

for _ in range(10):
lr_scheduler.step(2)
print(optimizer.param_groups[0]['lr'])

output:

>>> 0.0001
>>> 1e-05
>>> 1.0000000000000002e-06
>>> 1.0000000000000002e-07
>>> 1.0000000000000004e-08
>>> 1.0000000000000005e-09
>>> 1.0000000000000006e-10
>>> 1.0000000000000006e-11
>>> 1.0000000000000006e-12
>>> 1.0000000000000007e-13

Even if such use-case is bizarre, this is extremely unexpected.

This is happens using PyTorch version 1.1.0 but not 1.0.1. Because pull(#14010) redefined StepLR, MultiStepLR, ExponentialLR and CosineAnnealingLR to directly use the learning rate variable of the optimizer rather than using base_lr defined by _LRScheduler. This was in order to support multiple simultaneous schedulers (#13022)!
Issue 1:
Challenge http://beta.freecodecamp.com/challenges/waypoint-target-the-same-element-with-multiple-jquery-selectors has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

In the description "button-primary" should be replaced with "btn-primary".

Use the addClass() jQuery function to give the element one new class for each selector: "animated", "shake", and "button-primary".

The first three validation also have some text issues (see screenshot):

Issue 2:
Challenge http://beta.freecodecamp.com/challenges/waypoint-target-the-same-element-with-multiple-jquery-selectors has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

instructions say to add class 'button-primary' but tests against 'btn-primary'
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gce-serial/1446/

Failed: [k8s.io] [HPA] Horizontal pod autoscaling (scale resource: CPU) [k8s.io] [Serial] [Slow] Deployment Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:50
Expected error:
<*errors.errorString | 0xc820c91020>: {
s: "Only 0 pods started out of 1",
}
Only 0 pods started out of 1
not to have occurred

Issue 2:
Jenkins build kubernetes-e2e-gke-subnet/2545/ failed:

Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] Deployment Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:50 Mar 28 02:53:23.996: Number of replicas has changed: expected 3, got 4

Horizontal pod autoscaling (scale resource: CPU) [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/horizontal_pod_autoscaling.go:61 Mar 28 03:28:13.740: Number of replicas has changed: expected 3, got 4

Related logs can be accessed at: https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-e2e-gke-subnet/2545/
Issue 1:
The typescript definition file for the Popover component is missing both the anchorPosition and anchorReference props added in #9004 . I believe (though I'm not familiar with Flow) the Flow types are there in the .js component file.

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

Expected Behavior

Popover in Typescript projects should be able to have anchorPosition and anchorReference set.

Current Behavior

Typescript throws the following errors:

TS2339: Property 'anchorPosition' does not exist on type 'IntrinsicAttributes & PopoverProps & { children?: ReactNode; }'.

TS2339: Property 'anchorReference' does not exist on type 'IntrinsicAttributes & PopoverProps & { children?: ReactNode; }'.

Steps to Reproduce (for bugs)

Add anchorPosition and anchorReference to Popover

Compile code with Typescript

Context

Your Environment

Tech
Version

Material-UI
1.0.0-beta.22

React
16.1.1

browser
N/A

typescript
2.6.1

Issue 2:
https://material-ui-1dab0.firebaseapp.com/demos/selects/

as this demo show, when I click a selected menu item and move out, the background not changed
Issue 1:
STR

#[deriving(Clone)]
//~^ error: trait `Clone` already appears in the list of bounds [E0127]
struct Foo<'a, T: 'a + Clone> {
foo: &'a [T],
}

fn main() {}

Output

If you look at the --pretty=expanded version, you'll see T is bounded twice by the Clone trait

#![feature(phase)]
#![no_std]
#![feature(globs)]
#[phase(plugin, link)]
extern crate "std" as std;
#[prelude_import]
use std::prelude::*;
//~^ error: trait `Clone` already appears in the list of bounds [E0127]
struct Foo<'a, T: 'a + Clone> {
foo: &'a [T],
}
#[automatically_derived]
impl <'a, T: ::std::clone::Clone + 'a + Clone> ::std::clone::Clone for
Foo<'a, T> {
#[inline]
fn clone(&self) -> Foo<'a, T> {
match *self {
Foo { foo: ref __self_0_0 } =>
Foo{foo: ::std::clone::Clone::clone(&(*__self_0_0)),},
}
}
}

Version

rustc 0.13.0-dev (82fc1aa87 2014-11-27 10:11:19 +0000)

The obvious fix seems to make the deriving syntax extension filter out the duplicated Clone just by looking at the trait name. The problem is that ::std::clone::Clone may not be the same trait as Clone, but AFAIK the syntax extension can't know that, since that (path) information is collected after macro expansion.

Work-around

One workaround to this issue is using the fact that the deriving syntax extension doesn't look at where bounds (see #19358), the following code compiles:

#[deriving(Clone)]
struct Foo<'a, T: 'a> where T: Clone {
foo: &'a [T],
}

fn main() {}

Issue 2:
(Should this be an RFC?)

Motivation

When refactoring, one may have dozens or hundreds of build errors which need to be fixed one by one. Sometimes, a build error is only a consequence of an earlier error rather than something that need to be fixed itself:

let foo = bar.method_that_was_renamed(); // First error
// ...
bar.other_method() // Second error because the type of `bar` is unknown

In such cases, it is a better strategy to start by looking at and fixing earlier errors (in the compiler output) first. The second error might just go away when the first is fixed.

In a large enough crate, it’s easy to get well over one screenful of compiler output. So the workflow is something like:

Build. See lots of output be generated too fast to read.

Scroll back to the beginning of the output for this build. Don’t miss it! It looks a lot like the output of the previous build.

Find the first error.

Try to fix the first error.

Repeat.

Proposal

Add a command-line argument to rustc, called something like --fatal. When it is given and the compile finds a build error (the kind that would cause the compilation to fail eventually, so not warnings), exit immediately after printing diagnostics for this error. This is the opposite of the usual strategy of finding as many errors as possible at once.

The new workflow is:

Build.

The first error is right there at the bottom of the terminal. A single error likely fits entirely on the screen.

Try to fix it.

Repeat.

(With some inotify-based tricks, it’s not even necessary to switch focus from the terminal.)
Issue 1:
I'm having problems when using child forms that have radio or expanded date (select) fields. This problem is related to #743.

When using the last DelegatingValidator file (I'm using 2.0.1, just updated), the errors keep bubbling to the parent due to unmatching property (I commented about it in #1917)

If I switch that file for the one having this commit @90fa363 (submitted in #743), radio errors are rendered ok, being placed next to the field. However, the problem with the expanded date remains and the errors are bubbled up.

Issue 2:
When using expanded choice list (input[type=radio] tags), error is bubbling in top of the form and not next to the errornous field, when expanded is set to false (select tag), everything workds as expected...
Issue 1:
go version 1.5.3

Suppose a directory Documents/ has sub-directories A/, B/, C/, and files a, b, c

URL in address bar: http://localhost/Documents/

Everything is okay

URL in address bar: http://localhost/Documents

Sub-directory's href is "http://localhost/A/", NOT "http://localhost/Documents/A/".

So do other sub-directories and files.

https://github.com/golang/go/blob/master/src/net/http/fs.go#L458-L461

Why is the redirect flag in serveFile(w, r, Dir(dir), file, false) set to be false?

What's the difference between ServeFile and FileServer except that FileServer will add "/" for directories and remove "/" for files?

As suggestion, I hope that ServeFile won't show directory structure. It only serves files.

Edited

Code: http://130.211.241.67:3000/test.go

The following 2 URLs has the same html output. But as two URLs have different endings, broswer generates different links.

http://130.211.241.67:3000/test

http://130.211.241.67:3000/test/

Just click "testFile"

The ServeFile function doesn't redirect directory URLs ends without "/" to right place.

If ServeFile redirects, there are no difference between ServeFile and FileServer.

@bradfitz tested

#13996 (comment)

So I wonder how to modify it.

Edited Jan 20, 2016, 13:40:00 UTC+8

@bradfitz 's test

If I change ServeFile's false to true and re-run the net/http tests, there are failures

#13996 (comment)

Issue 2:
Weak imports are currently not treated correctly. Most likely, ld does not have the
knowledge to handle weak imports, and simply ignores them.

Weak imports are important for cross-version API compatibility on OS X, allowing you to
check for the availability of APIs at runtime, without embedding a hard dependency on
that symbol into the binary.

See https://golang.org/issue/3131 for a example of where this is an
issue.
Issue 1:
When using _document.js, a style tag will render > as &gt;. This prevents selectors like .foo > .bar { ... } from working.

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

Expected Behavior

when defining a style tag in _document such as

<style>{' body > div { background-color: red }'}</style>

it should preserve the >

Current Behavior

The > gets encoded as &gt;

Steps to Reproduce (for bugs)

Using the hello-world example in examples/ as a basis

add a _document.js in pages that looks like

import Document, { Head, Main, NextScript } from 'next/document'
import flush from 'styled-jsx/server'

export default class MyDocument extends Document {
static getInitialProps({ renderPage }) {
const { html, head, errorHtml, chunks } = renderPage()
const styles = flush()
return { html, head, errorHtml, chunks, styles }
}

render() {
return (
<html>
<Head>
<style>{`body > div { background-color: red }`}</style>
</Head>
<body className="custom_class">
{this.props.customValue}
<Main />
<NextScript />
</body>
</html>
)
}
}

next build && npm start

view the page source in the browser, <style>body &gt; div { background-color: red }</style> is rendered.

workaround

Using dangerouslySetInnerHTML fixes the issue

<script dangerouslySetInnerHTML={{__html: 'body > div { background-color: red }' }} />

Context

I am attempting to change the css of divs that are outside of what a normal nextjs page can access.

Your Environment

Tech
Version

next
4.2.1

node
6.9.4

OS
Ubuntu 16.04

browser
Chrome 63.0.3239.108 and Firefox 57.0.3

Note

When using styled-jsx inside a nextjs page, > works as expected

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

Expected Behavior

We should have documented as an example how to use the new next-less plugin

Current Behavior

We have a few examples to import .less files which are mostly hacks to make it work.

Context

With the release of Next.js v5 the current examples of importing LESS are outdated and can be simplified with the new next-css plugin.
Issue 1:
Same issue like in #625

Same settings. Attached a screenshot to even better show you guy!

Issue 2:
Windows 7 PRO SP1 64 bit

Firefox 38.0.1

When the page is loaded, only the following text shows up but not the whole text. When clicking on the text, all text shows.

Showed text:

<style>
.red-text {
color: red;
}

h2 {

font-family: Lobster, Monospace;

}

p {

--> Screenshot is from issue #626 but it's the same issue so that shouldn't matter
Issue 1:
Challenge Name

Issue Description

When ever i click on the ide within all challenges for the first time it will show the blinking " | " however when i start to type for click tab ora nything it will move the the next line.

Browser Information

Browser Name, Version: Chrome

Operating System: Mac El Capitan v10.11.3

Mobile, Desktop, or Tablet: Mac Book Pro

Your Code

// If relevant, paste all of your challenge code in here

Screenshot

Issue 2:
Challenge http://freecodecamp.com/challenges/waypoint-remove-classes-from-an-element-with-jquery has an issue.

The instructions were:

"Let's remove the btn-default class from all of our button elements.

Here's how you would do this for a specific button, add $("#target2").removeClass("btn-default");"

But even before I typed in "btn-default", it said my answer was already correct:

http://postimg.org/image/4sts8kj5f/
Issue 1:
This is with Julia 0.6

I tagged one or two packages, and then tried to published them. This failed, likely because PkgDev couldn't properly authorize with Github. I then tagged and published the same package from Julia 0.4, where everything went fine. Now I see this in Julia 0.6:

julia> Pkg.update()
INFO: Updating METADATA...
WARNING: Cannot perform fast-forward merge.

This warning has been there for a few days. How do I avoid it? Is there a way to do this automatically, or do I need to low-level git repo management? Would a hard git reset to the upstream master branch be appropriate, or can this lose data? (I would reset only the metadata repo, leaving my packages alone.)

I am making this an issue instead of a question on the mailing list because I think that tagging and publishing should be mainstream (not expert) actions, and Pkg and PkgDev should handle common error conditions automatically, or if not, should at least detect them and point to respective documentation.

Issue 2:
This is admittedly likely to affect only a small number of people, but I wonder about whether it's reasonable to support publishing branches that are not metadata-v2. Now that I'm back working on packages, I often have 3 or more simultaneous PRs in to METADATA, and to avoid duplication I create separate branches. Even if we get to the point where Travis isn't the bottleneck in METADATA PRs, it's been demonstrated repeatedly that these PRs are still worth reviewing, so it seems likely that many PRs will be out there for at least several hours.
Issue 1:
If you know how to fix the issue, make a pull request instead.

I tried using the @types/styled-components package and had problems because since of v.4.1.9 another conflicted dependency was added (@types/react-native) and conflicts with @types/node . See commit

I tried using the latest stable version(3.3.3333) of tsc. https://www.npmjs.com/package/typescript

I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).

Mention the authors (see Definitions by: in index.d.ts) so they can respond.

Authors: @jkillian @Igorbek @Igmat @lavoaster @Jessidhia @eps1lon @flavordaaave

how to reproduce:

Fresh install react app by command

yarn create react-app my-app-ts --scripts-version=react-scripts-ts

add styled components

yarn add styled-components

yarn add -D @types/styled-components

import ThemeProvider to src/index.tsx and wrap to

import * as React from 'react';
import * as ReactDOM from 'react-dom';
import {ThemeProvider} from "styled-components";
import App from './App';
import './index.css';
import registerServiceWorker from './registerServiceWorker';

ReactDOM.render(
<ThemeProvider theme={{}}>
<App />
</ThemeProvider>,
document.getElementById('root') as HTMLElement
);
registerServiceWorker();

run build command:

yarn start

Expected result:

See the react app

Current result:

There is a lot of fails according to many definitions conflicts with lib.dom

Issue 2:
the current underscore definitions in /underscore folder are targeting browsers (i.e. they have declare var _ ambient declarations) which make it hard to use them with node which would require a declare module definition. There is a project hat provides this (https://github.com/alvivi/typescript-underscore), so it would be great to include it as node_underscore

(Note: I did not want to submit a PR for this since it's not my work)
Issue 1:
In bootstrap.css:

.container {
margin-right: auto;
margin-left: auto;
}

.container:before,
.container:after {
display: table;
content: " ";
}

.container:after {
clear: both;
}

.container:before,
.container:after {
display: table;
content: " ";
}

.container:after {
clear: both;
}

.row:before,
.row:after {
display: table;
content: " ";
}

.row:after {
clear: both;
}

.row:before,
.row:after {
display: table;
content: " ";
}

.row:after {
clear: both;
}

Is this a bug or a feature? :)

Issue 2:
show on bootstrap.css

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L581

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L723

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L743

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2023

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2433

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2617

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L2637

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3032

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3296

https://github.com/twbs/bootstrap/blob/3.0.0-wip/dist/css/bootstrap.css#L3453
Issue 1:
System information (version)

OpenCV => 3.3.0

Operating System / Platform => Arch Linux 64-bit

Compiler => g++ 7.1.1

Detailed description

I am trying to load a tensorflow model in OpenCV, but it fails on populateNet with:

dropout/Shape:Shape(Relu_2)
T:0
out_type:[ ]
OpenCV Error: Unspecified error (Unknown layer type Shape in op dropout/Shape) in populateNet, file /build/opencv/src/opencv-3.3.0/modules/dnn/src/tensorflow/tf_importer.cpp, line 883
terminate called after throwing an instance of 'cv::Exception'
what(): /build/opencv/src/opencv-3.3.0/modules/dnn/src/tensorflow/tf_importer.cpp:883: error: (-2) Unknown layer type Shape in op dropout/Shape in function populateNet

I think this is related to opencv/opencv_contrib#1241

Are there any plans for supporting shape layers?

Issue 2:
System information (version)

OpenCV => 3.3.0

Operating System / Platform => Ubuntu 16

Compiler => ❔

Detailed description

I had trained a model for MNIST with tensorflow1.3.0, the model contains a dropout layout.

keep_prob = tf.placeholder(tf.float32, name='keep_prob');

h_fc1 = tf.nn.dropout(h_fc1, keep_prob);

Then I use the model like below

mNet = cv2.dnn.readNetFromTensorflow(model)

The error is:

OpenCV Error: Unspecified error (Unknown layer type Shape in op dropout/Shape) in populateNet

=========

If the model not contain dropout layer, everything is ok.

Steps to reproduce
Issue 1:
We should make it possible to update some parts of sysimg (e.g. different stdlibs) to let all Julia versions use bug fixes without the need to update Julia.

One solution may be to use separate files for each stdlib, which Pkg can update them.

I have seen this issue a lot in the pull requests and issues. People avoid adding a feature to Julia because they are afraid they cannot update it later in case some change is needed. Some examples: #36326, #36223, Pkg's artifacts system, etc.

Issue 2:
This is mostly just a meta issue attempting to summarize several existing discussions (issues). I'll try to include links to existing issues I've found whenever possible, but if I miss something please feel free to post a suggestion.

Problem

I think the general problem is best summarized by the following statement:

stdlibs are the place code goes to die

I don't think this statement is entirely fair, but folks do seem to avoid contributing new stdlibs, fixes or updates (myself included). From my experience this is mostly because the stdlib dev workflow is closer to working on the core language rather than working on an external package (Pkg.jl and Statistics.jl sit in the middle).

Solutions

Here are some things that might make this better from a user standpoint.

Developing a stdlib: ] dev Statistics (current solution is pretty manual)

Using the latest version of a stdlib: ] free Statistics (so stdlibs are basically just pinned default packages that can be unpinned and updated).

Clearer documentation around what should be in Base, stdlibs or an external package. I think folks jump to wanting things in Base that could often be an independent stdlib or even an external package?

Technical Challenges

A couple technical problems that I've seen from other issues include:

stdlib load times: We can include stdlibs in the system image by default, but what happens if you dev a stdlib? Do we rebuild the sysimg or just take the load time hit? What happens for downstream stdlib dependencies?

stdlib artifacts: Should changing a stdlib version trigger re-downloading any required build artifacts?

Pkg dependencies: More of a question, but would it be possible for Pkg.jl to handle replacing itself or its dependencies (similar to pip install -U pip) and just requiring a restart? Currently, Pkg.jl doesn't need to define a compat because all dependencies are baked stdlibs, but if all stdlibs could be updated then I assume we'd need to handle potential incompatibilities appropriately?

Links

stdlibs as packages

stdlib artifacts

Steps for deving a stdlib