WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Synopsis

The following snippet of code does not work for it's intended challenge under certain browsers.

<style>
body{
background-color: black;
}
</style>

Challenge: Waypoint: Style the HTML Body Element

Browsers Effected: Firefox (42.0), Edge (20.10240.16384.0)

Confirmed Working (non-issue) in Google Chrome (ver unknown) by @h4r1m4u on FreeCodeCamp/Help (Gitter).

Issue 2:
Challenge Waypoint: Use Hex Code for Specific Colors has an issue.

User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.10586.

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

My answer is correct but wrongly flagged as erroneous.

My code:

<style>
body {
background-color: #000000;
}
</style>
Issue 1:
Using Babel v6.0.2 with the following simple file:

export function myfunc(first, second){
return first * second;
}

and a .babelrc with:

{
"plugins": ["transform-es2015-modules-systemjs"]
}

fails with the error:

Error: example.js: We found a path that isn't a NodePath instance

For comparison, changing babelrc to use "transform-es2015-modules-commonjs" works correctly outputting the expected transformation, so it looks like this is specific to the new systemjs transformer.

--philip

Issue 2:
I have a problem when I use my globally-installed version of babel to compile a UMD module.

Here's my package.json:

{
"scripts": {
"build": "babel src --out-dir dist",
"build-fail": "~/.nvm/versions/node/v5.0.0/bin/babel src --out-dir dist"
},
"devDependencies": {
"babel-cli": "6.0.2",
"babel-plugin-transform-es2015-modules-umd": "6.0.2"
},
"babel": {
"plugins": ["transform-es2015-modules-umd"]
}
}

My src consists of a single file foo.js with the content:

const x = 1

(The problem does not happen for a completely empty file.)

When I run npm run build-fail, this happens:

> @ build-fail /home/andy/babel-bug
> ~/.nvm/versions/node/v5.0.0/bin/babel src --out-dir dist

Error: src/foo.js: We found a path that isn't a NodePath instance
at Function.get (/home/andy/babel-bug/node_modules/babel-traverse/lib/path/index.js:103:13)
at TraversalContext.create (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:73:30)
at TraversalContext.visitMultiple (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:102:25)
at TraversalContext.visit (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:193:19)
at Function.traverse.node (/home/andy/babel-bug/node_modules/babel-traverse/lib/index.js:139:17)
at NodePath.visit (/home/andy/babel-bug/node_modules/babel-traverse/lib/path/context.js:106:22)
at TraversalContext.visitQueue (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:151:16)
at TraversalContext.visitQueue (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:157:21)
at TraversalContext.visitMultiple (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:106:17)
at TraversalContext.visit (/home/andy/babel-bug/node_modules/babel-traverse/lib/context.js:193:19)

When I run npm run build, it works just fine.

My babel --version is 6.0.2 (babel-core 6.0.2) -- both globally and within my package. which babel is /home/andy/.nvm/versions/node/v5.0.0/bin/babel.
Issue 1:
We're currently sitting at 1,809 open issues, a number which hasn't really ever been useful to think about. The issue tracker seems to have three kinds of bugs:

Questions, e.g. #22625, #22474, #22093, #22005

"Meta" bugs, e.g. #22475, #22221, #22172

Specific problems (almost all of the rest)

As far as I can tell, no one is taking specific action on anything here. The oldest bugs are years old.

Feedback we've heard from contributors is that it's hard to "listen" for discussion or bugs related to .d.ts files they've worked on. And as we can see from the issue tracker, people who don't know how to contribute fixes aren't really getting results from filing issues on the issue tracker.

What would a useful DefinitelyTyped issue tracker look like?

Issue 2:
[ X ] I tried using the @types/xxxx package and had problems.

[ X ] I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript

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

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

Authors: @samuelneff, @CodeAnimal, @drinchev, @babolivier, @kukoo1, @oktapodia, @oktapodia

Beginning in Sequelize 4.12.0 use of $ne, $in, $not and so on is deprecated. They have been replaced by new symbols in Sequelize.Op. If you use the deprecated WHERE operators you see this message:

sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators node_modules/sequelize/lib/sequelize.js:236:13

Please add the new operators to the WhereLogic type.
Issue 1:
At some situations, plain object isn't the best choise. I tried to render a Map object by v-for, but seems Vue does not support it currently. (Here's a post I created in the Help thread on the forum.)

Hope Vue can provide the for ... of syntax in v-for to iterate over data types like Map and Set.

For example:

const map = new Map();
map.set('key1', 'val1');
map.set('key2', 'val2');

and we can render map in this way:

<ul>
<li v-for="[key, val] of map">{{key}} - {{val}}</li>
</ul>

Issue 2:
Hi

I has modified "Quick example" with using the Iterator protocol.

Will be great if it will work in 1.0 version for es6 environments.

Useful links:

https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Iteration_protocols

http://www.2ality.com/2015/02/es6-iteration.html
Issue 1:
I have viewed the guide https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps, it works.

And so I want to use the output file (framework& asset )to integrate to existing iOS APP. It seems simulator not support AOT ant it run in debug model with a VM.

Issue 2:
Current documentation (https://github.com/flutter/flutter/wiki/Flutter%27s-modes) states that Flutter release mode builds cannot be run on the Simulator. For many applications, the iOS Simulators are sufficiently high fidelity to do 99% of development work without going through the additional friction of deploying to devices regularly. It's unfortunate that, unlike in native application development, you can't get an accurate understanding of your release mode behaviors with Flutter.
Issue 1:
In AngularJS, ng-repeat can iterate Object as key-value map.

https://docs.angularjs.org/api/ng/directive/ngRepeat

<div ng-repeat="(key, value) in myObj"> ... </div>

In Angular2, ngFor doesn't support it. ngFor can iterate only an array.

https://angular.io/docs/ts/latest/api/common/NgFor-directive.html

<li *ngFor="#item of items; #i = index">...</li>

This mismatch makes migrations a little difficult.

I think ngFor also support Object iteration as well as ng-repeat.

Issue 2:
[ ] 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

It is currently impossible to use [required] and [disabled] in reactive forms

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

In many forms, some fields depend on other fields. With reactive forms it makes it extremely difficult and verbose to require or disable a field conditionally to another field

Angular version:

2.1.0

I have read here that

A future version of reactive forms will add the required HTML validation attribute to the DOM element (and perhaps the aria-required attribute) when the control has the required validator function.

Does it mean that [required] and [disabled] will be supported in future versions? It is important for users to understand the limitations of reactive forms so they can take the best decision (reactive vs template) based on their (future) needs.
Issue 1:
To work around #20096 we introduced a --hairpin-mode flag that flips cbr0 to promiscuous mode. Users of kubenet run with --configure-cbr0=false, so before we push kubenet to production we need to decide how to handle this.

If we decided to stick with promiscuous mode, kubenet should set it on whatever bridge it creates. We will (hopefully) not have to continue relying on promiscuous mode on newer kernel versions. Maybe it still makes sense to do in the interim? or maybe we can push it down into the CNI bridge driver (unsure of a valid generic use case to make a bridge promiscuous)?

@yifan-gu @dcbw @kubernetes/sig-network

Issue 2:
This block of code:

klet.volumePluginMgr, err =
NewInitializedVolumePluginMgr(klet, volumePlugins)
if err != nil {
return nil, err
}

klet.volumeManager, err = volumemanager.NewVolumeManager(
enableControllerAttachDetach,
hostname,
klet.podManager,
klet.kubeClient,
klet.volumePluginMgr,
klet.containerRuntime,
mounter)

Appears twice in NewMainKubelet, in pkg/kubelet/kubelet.go. This seems wrong.

Most-likely, the duplicate before switch containerRuntime is the one that should be removed, because that switch statement is where klet.containerRuntime is set.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.8

Operating System version: mac os

Java version: 1.8

Steps to reproduce this issue

Start multiple provider nodes

(中文：启动多个提供方节点)

Start consumer node

(中文：启动消费方节点)

Frequently shutdown and restart provider nodes or Frequently enable and disable provider nodes

(中文：频繁关闭、重启提供方节点或者频繁启用、禁用提供方节点)

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Only the thread of DubboClientHandler-xxx will appear

(中文：应该只会出现DubboClientHandler-xxx的线程用于网络连接、断连，因为获取响应结果用的是主线程)

Actual Result

What actually happens?

There are many threads named with Dubbo-thread-xxx on the consumer side，these threads will not be recycled.

(中文：消费方出现了很多以Dubbo-thread-xxx命名的线程，这些线程不会被回收)

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

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.9-SNAPSHOT

Steps to reproduce this issue

The pom.xml of dubbo-configcenter module has '' to include sub modules

<modules>
<module>dubbo-configcenter-zookeeper</module>
<module>dubbo-configcenter-apollo</module>
<module>dubbo-configcenter-consul</module>
<module>dubbo-configcenter-etcd</module>
<module>dubbo-configcenter-nacos</module>
</modules>

But the dubbo-configcenter-api is not included here. It may be an error.

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
Issue 1:
Is it possible to incorporate Weight Normalization (https://arxiv.org/abs/1602.07868) into tensorflow itself?

https://github.com/openai/weightnorm/tree/master/tensorflow

Issue 2:
can you implement weight norm ?

I want to use it as follows.

x = tf.layers.conv2d(x, filter_size=32, kernel_size=[3,3], strides=2)
x = weight_norm(x)

Is it possible?
Issue 1:
my conf:

services:
session.memcached:
class: Memcached
calls:
- [ addServer, [ 127.0.0.1, 11211 ]]

session.handler.memcached:
class: Symfony\Component\HttpFoundation\Session\Storage\Handler\MemcachedSessionHandler
arguments: [ @session.memcached, { prefix: zuo_session, expiretime: 3600 } ]

framework:
session:
handler_id: session.handler.memcached

my controller:

/**
* @Route("/about",name="aboutMe")
* @Template()
*/
public function meAction()
{
$v=rand(1,9999);
ld($v);
$this->get('session')->set('aaaaaaaaa',$v);
return new \Symfony\Component\HttpFoundation\RedirectResponse('/advice');
}

/**
* @Route("/advice",name="aboutAdvice")
* @Template()
*/
public function adviceAction()
{
ld($this->get('session')->get('aaaaaaaaa'));
return array('title' => 'aaa');
}

so what I did is:

1.generate a random number on page A

2.dump the number

3.Save the number into session on page A

4.redirect to Page B

5.dump the number which has been saved into session on page A

Normally, I will get 2 same number on page A and page B

but,some times, I will get the different number on Page B which has been save on last turn on Page A.

I guess the problem is because the save function of session hasn't been called automatically?

Issue 2:
I have been hit with a very strange situation during these last 2 days. I have a custom security listener and provider that sends some emails to the user and the user's "godfather" when registering. Immediately after registering, the user is redirected to his personal area. The problem arises when from time to time, the user is logged out when redirected.

Digging into the code, I can clearly see that the session is totally empty after the redirect, so no information about the user token is present. However, when I reload the page the session is perfectly filled and the user becomes logged in again. So I assumed that the session was still not written to disk (using native php file handler) when the user was redirected!

So here is what I found out. When sending emails with the default SF mailer (Swift) some bg processing must be kept somewhere. I am using nginx + php-fpm so the fastcgi_finish_request function is called and the page is immediately flushed. But as there must be some kind of bg processing, the session is still not written to disk when the next request coming from the redirect hits the server and the session is empty.

Comenting fastcgi_finish_request function call or not sending the emails seems to fix the problem so it has to be some problematic combination of those 2 things...but who knows!

Any ideas?
Issue 1:
While working on a way to address #101, it was discovered that some of the functions, constants, and structures offered in go/doc/comment.go are useful for parsing Go source code comments.

In particular, blocks(), block, op, opPara, opHead, and opPre.

Currently, consumers wanting to generate their own documentation or process Go source code are left with duplicating the existing logic found in go/doc/comment.go or adding special-case logic to that file itself for specific formats (undesirable). I would like to suggest that the aforementioned items be made public, or moved to a more suitable package for re-use by others.

Doing so would make it easier to add support for the generation of new documentation formats, such as manual pages, etc. and would likely provide a cleaner result.

If the desire is to keep these items where they are today, I would rename them as follows:

blocks -> Blocks
block -> Block
block.op -> block.Op
block.lines -> block.Lines
op -> Op
opPara -> OpPara
opHead -> OpHead
opPre -> OpPre

I am open to counter-suggestions as to how this logic should be exposed and I am willing to perform the work requested.

This bug was filed at the request of @adg

Issue 2:
by peter.waller:

This issue was discussed in this post on golang-dev:
https://groups.google.com/forum/?fromgroups=#!topic/golang-dev/xI7RIjkSeqk

The heap scavenger is hard-coded to free up memory spans which are unused for longer
than five minutes. For some applications this is unacceptable: in my case I need go
memory to become available to the operating system in short order (~10s).

The current proposed solution on the ML is to introduce a runtime function to run the
heap scavenger manually. This may require modifying the existing scavenger quite a bit.

MHeap_Scavenger code:
http://code.google.com/p/go/source/browse/src/pkg/runtime/mheap.c?spec=svn0a3866d6cc6b16e44ba6e8fb631a471ce81ca412&;name=b96e722aad5a&r=0a3866d6cc6b16e44ba6e8fb631a471ce81ca412#349
Issue 1:
by jdnurmi:

Often while experimenting or debugging a module, I'll find it necessary (or desirable)
to import the 'fmt' module to generate some temporary debugging printfs.

Alternatively, I might temporarily comment out a section that is the only user of the
"os",'io' or 'http' modules in 'helper' files for debugging.

This also occurs with variables or types that get commented out in a loop, the most
common occurance is something of the form:

for k,v := range someMap{
doSomething(k)
doSomethingElse(v)
}

There, commenting out either inner loop line will make the compilation fail since k/v
was 'set' but unused.

When I do this, go correctly flags that I've imported a module without using it. I
appreciate its semantic desire for a clean compile, but there are times when I know in
advance "It's coming back in 10 minutes, so shut-up", and would like to be
able to (for example) set my debug-build target to include
--warn-unused{,-import,-variable}.

I realize this is a convenience feature that's counter to the clarity of the language,
but especially as I first started learning it, the constant jumping around in the file
to satisfy the compilers need for "everything in its place, and every place
used" often became a frustrating irritant.

I would encourage leaving the default as is, I would just like a flag (or a pointer to
it in the doco if it already exists) to allow those issues to not inhibit my build.

Issue 2:
(Sorry I haven't managed to trim down the test case. In doing so, I kept running into
the formatting problem I just reported with strange comment movements.)

What steps will reproduce the problem?
1. git clone github.com/dgryski/dkrcrypt
2. edit aria.go, add "var _ cipher.Block = &AriaCipher{}" at the bottom
3. goimports

What is the expected output?
The crypto/cipher import is added.

What do you see instead?
I get a warning added to the top of my fail (which then fails to compile -- this may be
vim integration problems).
2013/12/18 10:16:12 addImportViaSourceModification error: 194:3: expected 1 expression
and the crypto/cipher import is added oddly split across a comment:

import

// The ARIA Block cipher from KISA
// Copyright (c) 2012 Damian Gryski <damian@gryski.com>
// Licensed under the GPLv3 or, at your option, any later version.
"crypto/cipher"
Issue 1:
Docs: https://docs.gradle.org/nightly/userguide/java_plugin.html#sec:incremental_annotation_processing

Gradle feature discussion: gradle/gradle#1320

Issue 2:
Gradle 4.7 provides support for incremental annotation processing.

https://docs.gradle.org/nightly/userguide/java_plugin.html#sec:incremental_annotation_processing

Gradle feature discussion: gradle/gradle#1320

It would be nice to see glide's annotation processor supporting it.

I started to have a look at the code and I was surprised to find such a complex annotation processing. I don't think I can do the PR quickly by myself. But I would be happy to provide all the information I can to help a maintainer doing it.
Issue 1:
Think this feature would be very useful

julia> type Foo
bar
baz::Int
qux::Float64
end

julia> foo = Foo("Hello, world.", 23, 1.5)
Foo("Hello, world.",23,1.5)

julia> foo.<tab>
bar baz qux

press tab after name and dot, show its fields only.

Would this be hard to implement ? I have no idea how auto-complete is implemented.

Issue 2:
julia> z = match(r"a", "apa")
RegexMatch("a")

julia> z.<tab><tab>

I know I can find the names of a composite type with typeof(z).names but I'd rather the repl do it for me and sprinkle some of its automagic-super-duper-wonderful-tab-completion-dust all over that tuple. :)
Issue 1:
Reproducing code example:

On my ARM Chromebook, running Debian 9.9 under Crouton I have a problem where the answer should be 'NaT', but I am getting '1970-01-01T00:00:00.000000000'.

import numpy as np
x = np.array([1,2,np.nan,np.nan]).astype('M8[ns]')
print(x)

Will print:

array(['1970-01-01T00:00:00.000000001', '1970-01-01T00:00:00.000000002',
'1970-01-01T00:00:00.000000000', '1970-01-01T00:00:00.000000000'],
dtype='datetime64[ns]')

Error message:

No error message.

Numpy/Python version information:

1.16.3 3.7.3 (default, May 22 2019, 00:01:31)

[GCC 6.3.0 20170516]

Issue 2:
Doing some calculations I discover this unexpected behavior related with

dtypes. I hope some of you can point me if this is a bug or I'm doing

something wrong.

Reproducing code example:

Here is a minimal peace of my code which tries to reproduce the problem:

import numpy as np

# VERSIONS USED
np.__version__ # '1.18.1'
np.__version__ # '1.19.0'

x = 731965.048356481480000000000000000000
x_arr = np.array([x])
big_int = 86400000000000
cnst = 719529

# THIS WORKS
arr1 = (x_arr - cnst) * big_int
out1 = arr1.astype("datetime64[ns]")

# THIS FAILS
arr2 = x_arr * big_int - cnst * big_int
out2 = arr2.astype("datetime64[ns]")

# WORKAROUND
big_int = 86400000000000. # NOW IS A FLOAT
arr3 = x_arr * big_int - cnst * big_int
out3 = arr3.astype("datetime64[ns]")

MWE

Here some code that I use for debugging a minimal reproducible example that

shows this unexpected behavior.

def check_dtype(big_int):
a = np.array([731965.04835648148]) * big_int
b = 719529 * big_int
c = a - b
return c.dtype

works_int = 20000000000000
fails_int = 30000000000000
check_dtype(works_int) # dtype('float64')
check_dtype(fails_int) # dtype('O')

Numpy/Python version information:

import sys, numpy; print(numpy.__version__, sys.version)
1.19.0 3.7.7 (default, Mar 26 2020, 15:48:22)
[GCC 7.3.0]
Issue 1:
Test case:

#[no_mangle]
fn main() {}

Output:

nom.rs:2:1: 2:13 warning: function main is marked #[no_mangle], but not exported, #[warn(private_no_mangle_fns)] on by default
nom.rs:2 fn main() {}
^~~~~~~~~~~~
rustc: /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/llvm/include/llvm/Support/Casting.h:237: typename llvm::cast_retty<X, Y*>::ret_type llvm::cast(Y*) [with X = llvm::Function; Y = llvm::Value; typename llvm::cast_retty<X, Y*>::ret_type = llvm::Function*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed.
Aborted

Issue 2:
#[no_mangle]
fn main() {
println!("hello world");
}

when rustc hello.rs, rustc panicked:

rustc: /home/liigo/rust/rust/src/llvm/include/llvm/Support/Casting.h:237: typename llvm::cast_retty<X, Y*>::ret_type llvm::cast(Y*) [with X = llvm::Function; Y = llvm::Value; typename llvm::cast_retty<X, Y*>::ret_type = llvm::Function*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed.
[1] 4419 abort rustc hello.rs
Issue 1:
I have seen that there are only Linux and MacOS based installations for the C language.

Kindly let me know if there is any tensorflow for the Windows in C langauage.

Issue 2:
I am working with Tensorflow in Java using the Maven dependency.

I would like to use the GPU version in my Java application but I notice there is only a supported Maven repository for Linux.

Will there be support for Tensorflow with Java in windows?

If so then what is the timeline for this?

Otherwise is there another way round it?

Thanks.
Issue 1:
DataFrame.duplicated correctly uses hashtable.duplicated_int64 a specialized routine, while core.series.IndexOpsMixin.duplicated uses lib.duplicated an object based one.

as its almost always better to factorize then use the fast routine, than to do object comparisons.

but YMMV, so needs a couple of perf tests.

In [3]: s = Series(np.random.randint(0,10000,size=100000))

In [4]: %timeit s.duplicated()
100 loops, best of 3: 5.75 ms per loop

In [6]: df = s.to_frame()

In [8]: %timeit df.duplicated()
1000 loops, best of 3: 1.86 ms per loop

Issue 2:
scatter_matrix (deprecate, redirect to seaborn)

andrews_curve

parallel_coordinates

lag_plot (maybe rename to lag)

autocorrelation_plot (maybe rename to autocorrelation?)

bootstrap_plot (maybe rename to bootstrap?)

radviz

I think it would be nice to allow scatter_matrix to be called directly on a DataFrame. Currently, scatter_matrix is a separate function that takes a DataFrame as a parameter, but it seems like it would be easy enough to rework to allow it to be called directly on a DataFrame as well. Effectively, the convenience function would look something like:

def scatter_matrix(self, ...):
pandas.tools.plotting.scatter_matrix(self.data, ...)

Is this feature feasible?