WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
Hello,

Originally seen when using FunctionWrappers. @yuyichao was nice enough to provide a MWE, that shows non-repeatably inefficient code. I am out of my depth here for such julia internals, just relaying the message :)

julia> using BenchmarkTools

julia> f3(x, y) = x - x + 0.5
f3 (generic function with 1 method)

julia> g3(f, x, y) = f3(x, y)
g3 (generic function with 1 method)

julia> p3 = @cfunction(g3, Float64, (Ref{typeof(f3)}, Float64, Float64))
Ptr{Nothing} @0x00007f8405b31650

julia> @benchmark ccall($p3, Float64, (Ref{typeof(f3)}, Float64, Float64), f3, 1.0, 2.0)
BenchmarkTools.Trial:
memory estimate: 48 bytes
allocs estimate: 3
--------------
minimum time: 66.488 ns (0.00% GC)
median time: 68.980 ns (0.00% GC)
mean time: 74.425 ns (0.45% GC)
maximum time: 510.097 ns (73.69% GC)
--------------
samples: 10000
evals/sample: 977

julia> p3 = @cfunction(g3, Float64, (Ref{typeof(f3)}, Float64, Float64))
Ptr{Nothing} @0x00007f8405b42ec0

julia> @benchmark ccall($p3, Float64, (Ref{typeof(f3)}, Float64, Float64), f3, 1.0, 2.0)
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 4.527 ns (0.00% GC)
median time: 4.554 ns (0.00% GC)
mean time: 4.965 ns (0.00% GC)
maximum time: 44.207 ns (0.00% GC)
--------------
samples: 10000
evals/sample: 1000

Cheers!

Issue 2:
Copied from: https://discourse.julialang.org/t/performance-and-memory-regression-with-function-wrappers-in-julia-1-4/44589

Setup:

julia> using BenchmarkTools

julia> using FunctionWrappers: FunctionWrapper

julia> w = let closed_over=([1], [2])
FunctionWrapper{typeof(closed_over), Tuple{}}(() -> closed_over)
end;

Results

Julia 1.3.1:

julia> @btime $w()
5.435 ns (0 allocations: 0 bytes)

Julia 1.4.2:

julia> @btime $w()
9.919 ns (1 allocation: 16 bytes)

Julia 1.5.0

julia> @btime $w()
10.112 ns (1 allocation: 32 bytes)

Julia 1.6.0-DEV.607

julia> @btime $w()
11.846 ns (1 allocation: 32 bytes)

This turns out to be the source of a significant performance regression in Parametron.jl (which was designed to allocate zero memory).

Here's my system info:

julia> versioninfo()
Julia Version 1.5.0
Commit 96786e22cc (2020-08-01 23:44 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-9.0.1 (ORCJIT, skylake)

@yuyichao pointed to yuyichao/FunctionWrappers.jl#14 as a related issue. I cannot reproduce the MWE from yuyichao/FunctionWrappers.jl#14 (comment) on Julia 1.5, but the slowness and extra allocation of my example here is still present in Julia 1.5.0.
Issue 1:
Vue.js version

1.0.21

Steps to reproduce

<div :style="{backgroundSize:'100%'}"></div>

What is Expected?

<div style="background-size:100%;"></div>
// or
<div style="background-size:100% auto;"></div>

What is actually happening?

<div style="background-size:100% 100%;"></div>

from css documentation of background-size:

Sets the width and height of the background image in percent of the parent element. The first value sets the width, the second value sets the height. If only one value is given, the second is set to "auto"

Issue 2:
What problem does this feature solve?

Sometimes prop validation error messages are to vague, and one would like to specify his own custom error message, instead of the default "Invalid prop: custom validator check failed for prop" message.

What does the proposed API look like?

I suggest supporting the validator to be an object. Instead of:

export default {
name: 'MyComponent',
props: {
type: {
type: String,
validator: v => ['positive', 'negative', 'warning', 'info'].includes(v)
}
}
}

Have the following:

export default {
name: 'MyComponent',
props: {
type: {
type: String,
validator: {
handler: v => ['positive', 'negative', 'warning', 'info'].includes(v),
message: "Type must be one of 'positive', 'negative', 'warning', 'info'"
}
}
}
}
Issue 1:
It's a common beginner's problem to create a vector with run-time size filled with identical values, but the idiomatic solution is pretty much undiscoverable without asking people on IRC/StackOverflow/Reddit.

cc @steveklabnik

Issue 2:
Rustc sometimes recognizes and logs the same error multiple times.

Test case: https://gist.github.com/reem/78db1ad233f1c87f9ca7

rustc --test consistently logs (note the double report on the L#33 error):

lib.rs:33:5: 33:16 error: failed to find an implementation of trait core::ops::FnOnce<(uint),uint> for fn(uint) -> uint
lib.rs:33 replace_map(b, double);
^~~~~~~~~~~
lib.rs:33:5: 33:16 error: failed to find an implementation of trait core::ops::FnOnce<(uint),uint> for fn(uint) -> uint
lib.rs:33 replace_map(b, double);
^~~~~~~~~~~
lib.rs:36:5: 36:16 error: failed to find an implementation of trait core::ops::FnOnce<(uint),uint> for closure
lib.rs:36 replace_map(b, |&mut: x: uint| x * 2);
^~~~~~~~~~~
lib.rs:39:5: 39:16 error: failed to find an implementation of trait core::ops::FnOnce<(uint),uint> for closure
lib.rs:39 replace_map(b, |&: x: uint| x * 2);
^~~~~~~~~~~
error: aborting due to 4 previous errors
Issue 1:
arrays defined in vars or vars_files work ok, while those from host/group vars and inventory (${groups.somegroup} are handled incorrectly

See attached gist (full test case with output)

https://gist.github.com/mkaluza/6121615

vars 'a' and 'c' behave correctly, while var 'b' and group 'grp' does not

Issue 2:
Issue Type:

Bug Report

Ansible Version:

ansible 1.9.1
configured module search path = None

Ansible Configuration:

N/A

Environment:

Mac OSX 10.9.5

Summary:

Roles that are included multiple times cannot have their dependencies included multiple times. The documentation states that allow_duplicates accomplish something like this so long as the dependency is included multiple times from the same role, but it does not seem to work for the aforementioned case.

Steps To Reproduce:

Here's a simple set of playbooks / roles that should illustrate the problem.

### ./hypervisor-1.yml

---
- hosts:
- host1
roles:
- role: vm
name: red
- role: vm
name: blue

### ./hypervisor-2.yml

---
- hosts:
- host2
roles:
- role: vm
name: green
- role: vm
name: yellow
- role: vm
name: purple

### ./inventory
[hosts]
host1
host2

### ./roles/disk/tasks/main.yml
- debug: msg="Setting up disk for {{ path }}"

### ./roles/vm/meta/main.yml

---
allow_duplicates: yes
dependencies:
- role: disk
path: "/path/to/{{ name }}"

### ./roles/vm/tasks/main.yml
- debug: msg="Installing VM {{ name }}"

Expected Results:

Running the first playbook, hypervisor-1.yml, should give output that shows a disk is set up for both red and blue, as well as the installation of the VM for both.

Actual Results:

PLAY [host1] ******************************************************************

GATHERING FACTS ***************************************************************
ok: [host1]

TASK: [disk | debug msg="Setting up disk for /path/to/red"] *******************
ok: [host1] => {
"msg": "Setting up disk for /path/to/red"
}

TASK: [vm | debug msg="Installing VM red"] ************************************
ok: [host1] => {
"msg": "Installing VM red"
}

TASK: [vm | debug msg="Installing VM blue"] ***********************************
ok: [host1] => {
"msg": "Installing VM blue"
}

PLAY RECAP ********************************************************************
host1 : ok=4 changed=0 unreachable=0 failed=0

Note the disk is only set up for red and is skipped for blue.
Issue 1:
If the viewport is smaller than the list of dropdown links of a fixed-top navbar, there is no way to scroll down to view links that are beyond my view. The reason being obviously that the entire navbar is "fixed". I've tried to make .navbar-collapse scrollable but it won't always scroll down to the very end, it's very confusing.

Can be reproduced using your example here: http://getbootstrap.com/examples/navbar-fixed-top/, both on mobile and desktop. I'm using the newest Chrome Browser.

Any thoughts on this are VERY MUCH appreciated - thanks!

Issue 2:
[Original title: Expanded navbar on mobile (landscape) is cut off]

/CC @mdo
Issue 1:
What use are options like precision, rounding_mode for an integer type?

Why is this form called "integer" when it clearly deals with floats?

I'd expect integer type to allow only values like -2, -1, 0, 1, 2, 3, ... etc, and to have options like allow_negative and allow_zero.

This field has different options on how to handle input values that aren't integers. By default, all non-integer values (e.g. 6.78) will round down (e.g. 6).

I'd expect number field to behave like this (based on configuration options), and integer type should only allow.. well.. integer values. The name of this form is misleading.

PS. Am I the only one who finds precision weird option for an "integer" type?

Issue 2:
The IntegerType supports floats, but as the name suggests it should only accept integers, i.e. whole numbers.

The NumberType supports floats, locale specific numeric strings (e.g. "40,000") etc.

I propose a change to these 2 types:

IntegerType: should be used for whole integers as the name suggests

NumberType: should be used for floats (rendering as an input[type="number"]), and have a new option (support_locale_strings or something similar) so that it renders as input[type="text"] and has the relevant attached NumberToLocalizedStringTransformer.

This is obviously a BC break so marked it for 3.0.
Issue 1:
VSCode Version: 1.2.0 + 1.3.0-insiders

OS Version: MacOS X 10.11.5

Steps to Reproduce:

Open/create scss file

Write a map, the first colon is marked as an error

Error message: ") expected"

Code from screenshot:

// Breakpoints
$breakpoints: (
'xsmall': 21.25rem, // 340px
'small': 40rem, // 640px
'medium': 48rem, // 768px
'large': 61.25rem, // 980px
'xlarge': 82rem // 1312px
);

Issue 2:
If I add a map to a scss file, e.g. "$map: (key1: value1, key2: value2, key3: value3);" it shows as an error. Red squiggly appears under the ":" after the first key and hover message reads ") expected". Despite the error in editor node-sass evaluates map-get correctly over it.
Issue 1:
https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging/6016/

Failed: Kubectl client Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:135
Jun 15 07:17:41.598: Timed out after 300 seconds waiting for name=update-demo pods to reach valid state

Issue 2:
Seeing a fair number of failures from the PR builder failing because they can't reach gcr.io

Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable\n v1 ping attempt failed with error: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable

May need to disable the affected tests until the issue can be resolved.

18:11:42 I0331 01:07:35.717951 2083 provider.go:91] Refreshing cache for provider: _credentialprovider.defaultDockerConfigProvider

18:11:42 I0331 01:07:35.718029 2083 docker.go:161] Pulling image gcr.io/google_containers/busybox:1.24 without credentials

18:11:42 I0331 01:07:36.102990 2083 docker.go:161] Pulling image gcr.io/google_containers/mounttest:0.2 without credentials

18:11:42 • Failure [0.544 seconds]

18:11:42 Container Conformance Test

18:11:42 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/conformance_test.go:164

18:11:42 container conformance blackbox test

18:11:42 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/conformance_test.go:163

18:11:42 when testing images that exist

18:11:42 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/conformance_test.go:79

18:11:42 it should pull successfully [Conformance] [It]

18:11:42 /var/lib/jenkins/workspace/node-pull-build-e2e-test/go/src/k8s.io/kubernetes/test/e2e_node/conformance_test.go:63

18:11:42

18:11:42 Expected error:

18:11:42 <_errors.errorString | 0xc2083c1f00>: {

18:11:42 s: "image pull failed for gcr.io/google_containers/mounttest:0.2, this may be because there are no credentials on this request. details: (unable to ping registry endpoint https://gcr.io/v0/\nv2 ping attempt failed with error: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable\n v1 ping attempt failed with error: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable)",

18:11:42 }

18:11:42 image pull failed for gcr.io/google_containers/mounttest:0.2, this may be because there are no credentials on this request. details: (unable to ping registry endpoint https://gcr.io/v0/

18:11:42 v2 ping attempt failed with error: Get https://gcr.io/v2/: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable

18:11:42 v1 ping attempt failed with error: Get https://gcr.io/v1/_ping: dial tcp: lookup gcr.io on 169.254.169.254:53: dial udp 169.254.169.254:53: network is unreachable)

18:11:42 not to have occurred
Issue 1:
The first line is working, the second one, on GPU, returns an error

torch.FloatTensor(3, 4).random_(2)
torch.FloatTensor(3, 4).cuda().random_(2)

AttributeError: 'FloatTensor' object has no attribute 'random_'

Issue 2:
torch.Tensor(10).random_(0,10) #works

torch.Tensor(10).random_(0,10).cuda() #works

torch.Tensor(10).cuda().random_(0,10) #does not work
Issue 1:
I have no jap charakters also in UTF-8. (Linux Mint 17.1)

I didn't choose any font family in settings.

for example this

"TITLE_LOST_NEW": "新遺失",

"TITLE_LOST_EDIT": "遺失修正",

"TITLE_LOST_DETAIL": "遺失詳細",

"TITLE_LOSTS_PAIRS": "対で遺失",

"TITLE_LOSTS_MY": "個人の遺失",

"TITLE_LOSTS": "遺失",

*** Here is my additional information ***

$ atom --version

0.209.0

$ apm links

/home/frdm/.atom/dev/packages (0)

└── (no links)

/home/frdm/.atom/packages (0)

└── (no links)

YES the problem remains if Atom runs in safe mode

YES it doesn't matter if I chose a font that supports these characters, DejavuSans Mono, Monospace, Noto Sans etc...

here is my FULL /.atom

.atom.zip 13.3 MB

https://mega.co.nz/#!CZw1ETab!MG8JHXZ_3kIYuYoSMhwp-oaV2jATdMqk3Pk7MXavSbk

Processor : 4x AMD A8-4500M APU integrated GPU

Operating System : Linux Mint 17.1 Rebecca (MATE)

OpenGL : AMD Radeon HD 7640G

X11 Vendor : The X.Org Foundation v1.15.1

Kernel : Linux 3.13.0-55-generic (x86_64)

Issue 2:
Text:

这上面的夜的天空，奇怪而高，我生平没有见过这样奇怪而高的天空。他仿佛要离开人间而去，使人们仰面不再看见。然而现在却非常之蓝，闪闪地睒着几十个星星的眼，冷眼。他的口角上现出微笑，似乎自以为大有深意，而将繁霜洒在我的园里的野花草上。

It happen after update to 0.189.0, and it's normal in 0.188.0 .

I try disabled all community packages or star with --safe mode, still happen.

Update: Ubuntu 14.04
Issue 1:
Challenges 4, 5, etc., not logged in.

User Agent: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36"

Steps to reproduce:

Pass challenge 4, Work with Data in D3.

My passing code was:

<body>
<script>
const dataset = [12, 31, 22, 17, 25, 18, 29, 14, 9];

// Add your code below this line

d3.select('body').selectAll('h2')
.data(dataset)
.enter()
.append('h2')
.text('New Title');

// Add your code above this line
</script>
</body>

Do not go on to next challenge.

Resubmit and get this error:

// running test
"Identifier 'dataset' has already been declared"
"Identifier 'dataset' has already been declared"
"Identifier 'dataset' has already been declared"
"Identifier 'dataset' has already been declared"
// finished test

You can also get this error by:

Completing and passing challenge 4.

Moving on to challenge 5.

Submitting challenge 5, even with correct code.

Get the error, and your code will not show on phone.

Refresh page, it will pass.

Issue 2:
Challenge work-with-dynamic-data-in-d3 has an issue.

User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36.

<body>
<script>
const dataset = [12, 31, 22, 17, 25, 18, 29, 14, 9];

d3.select("body").selectAll("h2")
.data(dataset)
.enter()
.append("h2")
.text((d) => d + " USD");

// Add your code above this line
</script>
</body>

This would be the right solution, but it says dataset is already declared. The issue is resolved by renaming the variable.
Issue 1:
I had originally installed atom via brew cask install and the atom command was working fine. Then, for reasons, I uninstalled the cask version and installed atom from atom.io. Ever since, despite performing "Install Shell Commands" and making sure the symlinks are correct, the atom command fails to load the current folder. It's highly likely this is isolated to my installation only, but I'm having a hard time figuring out where things go wrong.

I have tried:

Removing ~/.atom entirely

Exporting a nearly uncustomized $PATH before launching atom

Atom -> Install Shell Commands (and manually checking the symlinks after)

Launching from various folders, just in case there was something weird in the pathname

So far nothing has worked.

Atom seems to be getting the --executed-from argument just fine and with a correct value. For example, if I launch atom in /tmp, I can see the following command with ps aux | grep -i atom:

/Applications/Atom.app/Contents/MacOS/Atom --executed-from=/tmp --pid=77617 --path-environment=/Users/redacted/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

The launched editor just shows a blank untitled document, does not open the tree view, and Cmd+P says that the project is empty. The --pid doesn't point to any existing process but then again I don't really know what it's for anyway.

File -> Open does work.

Any ideas? I'm on 0.209.0 currently but the issue has persisted for a month or so.

Here's the path to the atom script in case it helps:

➜ /tmp readlink /usr/local/bin/atom
/Applications/Atom.app/Contents/Resources/app/atom.sh

Issue 2:
When executing v 0.200.0 from command line, Atom open an empty untittled file instead the ones from that directory, and in fact the tree view don't get open both with the shortcut or the menu option. Other tabs like preference are working. After executing atom . the tree view gets shown and it works normally, and also now it gets shown when launching it without arguments too as it should do.
Issue 1:
No curves appear in Tensorboard 25 when I click on a heading to open one.

Maybe related to #3782

Environment info

Operating System: Ubuntu 14.04

If installed from source, provide

The commit hash (git rev-parse HEAD): 008bcae

The output of bazel version 0.3.0

Issue 2:
After a clean install of TensorFlow v0.10 (from master) my TensorBoard is suddenly broken. The scalar event plots do not show upon clicking (see screenshow below). While the logs in the terminal do not show any errors, the Chrome Developer console shows the following error upon opening a figure:

tf-tensorboard.html:1517 Uncaught Error: tf-chart-scaffold's content doesn't implement the required interfaceinsertBefore @ VM2478 polymer-mini.html:560

I am running Chrome Version 52.0.2743.116 (64-bit) on Linux Mint 17.
Issue 1:
Greater than or equal to version 0.189.0 of atom does not support Chinese input.Hopes to fix as soon as possible.

Issue 2:
Text:

这上面的夜的天空，奇怪而高，我生平没有见过这样奇怪而高的天空。他仿佛要离开人间而去，使人们仰面不再看见。然而现在却非常之蓝，闪闪地睒着几十个星星的眼，冷眼。他的口角上现出微笑，似乎自以为大有深意，而将繁霜洒在我的园里的野花草上。

It happen after update to 0.189.0, and it's normal in 0.188.0 .

I try disabled all community packages or star with --safe mode, still happen.

Update: Ubuntu 14.04
Issue 1:
Hi there,

I am in the process of upgrading a Silex app and part of that is an upgrade of the sf components. With sf 2.6 I've run into a problem with the TraceableEventDispatcher.

Dispatcher version is v2.6.6

silex_upgrade/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Storage/MockArraySessionStorage.php:134

silex_upgrade/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Session/Session.php:199

silex_upgrade/vendor/silex/silex/src/Silex/Provider/SessionServiceProvider.php:93

silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/WrappedListener.php:61

silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/WrappedListener.php:61

silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:164

silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/EventDispatcher.php:53

silex_upgrade/vendor/symfony/event-dispatcher/Symfony/Component/EventDispatcher/Debug/TraceableEventDispatcher.php:112

silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/HttpKernel.php:126

silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/HttpKernel.php:66

silex_upgrade/vendor/silex/silex/src/Silex/Application.php:543

silex_upgrade/vendor/symfony/http-kernel/Symfony/Component/HttpKernel/Client.php:81

silex_upgrade/vendor/symfony/browser-kit/Symfony/Component/BrowserKit/Client.php:327

silex_upgrade/php/tests/controllers/TestLookupController.php:20

Issue 2:
Q
A

Bug report?
yes

Feature request?
no

BC Break report?
no

RFC?
no

Symfony version
3.2.1

After upgrading to PHP 7.1 and symfony 3.2.1 I sometimes (once a week, random) get the following error:

FatalErrorException in classes.php line 347:

Error: Class Symfony\Component\HttpFoundation\Session\Storage\Proxy\SessionHandlerProxy contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (SessionHandlerInterface::write)

I changed the following lines in config.yml to the new Symfony 3 style:

session:
# handler_id set to null will use default session handler from php.ini
handler_id: session.handler.native_file
save_path: "%kernel.root_dir%/../var/sessions/%kernel.environment%"

But it still happened.

After reading http://stackoverflow.com/questions/36088683/php-7-symfony-3-fatal-error-1-abstract-method-and-must-therefore-be-declared-a

The solution is indeed to restart Apache.

I have no clue what can be the cause, maybe PHP 7.1, but Symfony 3 is compatible with 7.1 right?

Maybe someone here can point me in the right direction to solve this :)