Replace hostname -f with uname -n

Should not depend on hostname command. The specification of hostname command is changeable.
On the other hand, uname -n is a front end for a system call and simply get hostname. Please also refer gethostname(2) man page.

I signed it!

We use hostname -f because it returns fully qualified domain name (FQDN). If we changed it to uname -n, shouldn't we lost that?

Didnt Yu-Ju just change it to only take the first word anyway?
On Apr 6, 2015 10:35 AM, "Dawn Chen"<EMAIL_ADDRESS>wrote:

We use hostname -f because it returns fully qualified domain name (FQDN).
If we changed it to uname -n, shouldn't we lost that?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/6466#issuecomment-90165710
.

@thockin If I remembered correctly Yu-Ju's change is involved only on static pods name. When generate fully name for those static pods, we only use the first word of current FQDN name. But I thought we first introduce fqdn because some cloud provider(s) expect hostname resolvable. Not sure if that is still the requirement now?
@brendandburns

I don't think that we are wedded to FQDN, but it is very important that both the kubelet and the master have the same notion of the identity of a node.  kubelet currently gets this identity via hostname -f master generally gets it from a cloud provider.
As long as those match up, I don't think we much care.

FWIW, there was a discussion a long time ago in #584.

Actually appending fqdn suffix already causes issue for hosted master on GKE based on @cjcullen today:
Today when NodeController "registers" nodes in SyncCloud by getting bare instance names (https://github.com/GoogleCloudPlatform/kubernetes/blob/9949936b5ce9d205328269ea304db4ab5dce5a67/pkg/cloudprovider/gce/gce.go#L101) from GCE, and recreating the fqdn and append it to instance names(https://github.com/GoogleCloudPlatform/kubernetes/blob/9949936b5ce9d205328269ea304db4ab5dce5a67/pkg/cloudprovider/gce/gce.go#L427). The issue is when the master is in a project we own, the fqdn suffix will be different, and we don't really have a good way of generating it on the master.
In this case, replacing hostname -f with uname -n is a right approach?
@nak3 could you please run hack/e2e-test.sh?

uname -n doesn't seem to be deterministic, though? I have at least one box where it's giving me the FQDN and another it's giving me a naked name. It looks consistent with hostname (minus the -f), but if we need things to line up, that may mean we still have to name hack.

Basically, I just repeated what @thockin said months ago: https://github.com/GoogleCloudPlatform/kubernetes/pull/584#issuecomment-49901915

hostname pretty much includes an internal call to uname, that explains why the outputs are the same.
The problem is that hostname could be fully qualified or not qualified. POSIX does not specify which of these forms should be returned by uname. Some implementations do, but they are split between use of the unqualified name and the fully-qualified name.
My concern raised earlier is if our eco-system does require fully qualified name, and from various sources it sounds like NO. In this case, we could settle down with first token by splitting the output by "." to get rid of domain name.
hostname -f failed us many times before because couldn't retrieve fqdn suffix.

@dchen1107
I will run hack/e2e-test.sh first. But hold on... I cannot pass hack/e2e-test.sh regardless of hostname -f or uname -n.

@nak3 What kind of failures are you observing? @quinton-hoole

@dchen1107
I am hiting similar error to #6045
I got same error with #6045, and after I updated, I still keep getting similar error.

Commit ID

(master)$ git show -s --format=%H
2719194154ffd38fd1613699a9dd10a00909957e

Log snippet

I0408 07:52:46.882759     728 integration.go:284] Error on creating endpoints: endpoints "service1" not found^M
I0408 07:52:47.482741     728 integration.go:284] Error on creating endpoints: endpoints "service1" not found^M
I0408 07:52:47.485097     728 integration.go:266] Check whether pod nginx-controller-h7l1o.test exists on node "localhost"^M

... snip ...

I0408 07:53:16.485701     728 integration.go:266] Check whether pod nginx-controller-moyc2.test exists on node ""^M
I0408 07:53:16.485712     728 integration.go:268] Pod nginx-controller-moyc2.test is not bound to a host yet^M
F0408 07:53:16.485718     728 integration.go:435] FAILED: pods never started running timed out waiting for the condition^M
!!! Error in hack/test-integration.sh:47^M
  '"${KUBE_OUTPUT_HOSTBIN}/integration" --v=2 --apiVersion="$1"' exited with status 255^M
Call stack:^M
  1: hack/test-integration.sh:47 runTests(...)^M
  2: hack/test-integration.sh:60 main(...)^M
Exiting with status 1^M

@nak3  Sorry for those failures tests, lately we have a churn of broken tests, and ppl are working on fix. I noticed that travis and shippable, which run integration test too, are green for this PR now. Can you sync your branch, and rerun hack/e2e-test.sh again? There are tons of output related pods, and events at the end of test output. Ignore those output and scroll up, you should see how many tests are passed, failed or skipped. There is one known failure. Please post the result here. Thanks!

@dchen1107
I synced and rerun hack/e2e-test.sh again. But I still got following error.

Commit ID

(master)$  git show -s --format=%H
d85fbd7b5a402eea4959db71ad4afb87f4b7ae89

Log

... snip ...
I0409 12:50:50.901542    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:50:52.341825    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 88
E0409 12:50:52.343126    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 87
W0409 12:51:00.785274    1252 master.go:194] Portal net unspecified. Defaulting to <IP_ADDRESS>/24.
I0409 12:51:00.785797    1252 master.go:224] Will report <IP_ADDRESS> as public IP address.
E0409 12:51:03.517143    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:03.525897    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
E0409 12:51:03.527285    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:03.532114    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:51:04.045273    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:04.047512    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:04.048992    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
I0409 12:51:04.050553    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:51:06.098020    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 102
E0409 12:51:06.099150    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 101
E0409 12:51:13.181222    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:13.186641    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:13.187601    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:51:13.190653    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:13.193296    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:13.194463    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:13.195583    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:13.196344    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
I0409 12:51:13.197442    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
I0409 12:51:13.198127    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
I0409 12:51:13.199839    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
I0409 12:51:13.203832    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
E0409 12:51:14.941478    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:14.943950    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:51:14.946975    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:14.950540    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
E0409 12:51:14.956067    1252 publish.go:42] Can't create rw service: Service "kubernetes" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
E0409 12:51:14.957719    1252 publish.go:67] Can't create ro service: Service "kubernetes-ro" is invalid: spec.portalIP: invalid value '<IP_ADDRESS>': IP <IP_ADDRESS> is already allocated
I0409 12:51:14.958566    1252 publish.go:152] setting endpoints for master service "kubernetes" to &{{ } {kubernetes  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 6443 TCP}]}]}
I0409 12:51:14.959482    1252 publish.go:152] setting endpoints for master service "kubernetes-ro" to &{{ } {kubernetes-ro  default    0001-01-01 00:00:00 +0000 UTC <nil> map[] map[]} [{[{<IP_ADDRESS> <nil>}] [{ 7080 TCP}]}]}
E0409 12:51:15.107128    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 112
E0409 12:51:15.114186    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 112
E0409 12:51:15.115267    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 113
E0409 12:51:15.116286    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 113
E0409 12:51:15.643778    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 113
E0409 12:51:15.645251    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 112
E0409 12:51:15.646459    1252 publish.go:70] Can't create ro endpoints: endpoints "kubernetes-ro" cannot be updated: the resource was updated to 112
E0409 12:51:15.648037    1252 publish.go:45] Can't create rw endpoints: endpoints "kubernetes" cannot be updated: the resource was updated to 113
FAIL
FAIL	github.com/GoogleCloudPlatform/kubernetes/test/integration	113.699s
!!! Error in /go/src/github.com/GoogleCloudPlatform/kubernetes/hack/test-go.sh:152
  'go test "${goflags[@]:+${goflags[@]}}" ${KUBE_RACE} ${KUBE_TIMEOUT} "${@+${@/#/${KUBE_GO_PACKAGE}/}}"' exited with status 1
Call stack:
  1: /go/src/github.com/GoogleCloudPlatform/kubernetes/hack/test-go.sh:152 runTests(...)
  2: /go/src/github.com/GoogleCloudPlatform/kubernetes/hack/test-go.sh:207 main(...)
Exiting with status 1
!!! Error in hack/test-integration.sh:40
  'KUBE_GOFLAGS="-tags 'integration no-docker' " KUBE_RACE="-race" KUBE_TEST_API_VERSIONS="$1" "${KUBE_ROOT}/hack/test-go.sh" test/integration' exited with status 1
Call stack:
  1: hack/test-integration.sh:40 runTests(...)
  2: hack/test-integration.sh:60 main(...)
Exiting with status 1
+++ [0409 12:51:22] Integration test cleanup complete
!!! Error in /ssd/kubernetes/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:432
  '"${docker_cmd[@]}" "$@"' exited with status 1
Call stack:
  1: /ssd/kubernetes/hack/e2e-internal/../../cluster/gce/../../cluster/../build/../build/common.sh:432 kube::build::run_build_command(...)
  2: /ssd/kubernetes/hack/e2e-internal/../../cluster/gce/../../cluster/../build/release.sh:36 main(...)
Exiting with status 1
2015/04/09 21:51:26 Error running build-release: exit status 1
2015/04/09 21:51:26 Error building. Aborting.
exit status 1

This integration test failure is new. I suspect it is caused by #6466 itself. Have you tried to run hack/test-integration.sh in a different branch without your change? Looks like the resource version is messed up, but from your code, I couldn't link anything to that failure yet.

I suspect there is a race in our current HEAD. Will try to reproduce this.

@dchen1107

Have you tried to run hack/test-integration.sh in a different branch without your change?

Yes, I have tried to run without my change.

I suspect there is a race in our current HEAD. Will try to reproduce this.

Okay,  I will try to reproduce it tomorrow. (Sorry, I live in different time zone…)

@dchen1107
I cleaned up and sync latest commit, but I am still hitting another error.

Commit ID

$ git show -s --format=%H
4f3f19511fd2efa29635fd8ff59bd9ec02456c22

Log

... snip ...
+++ [0410 16:42:51] Docker builds done
+++ [0410 16:43:01] Building tarball: full
+++ [0410 16:43:01] Building tarball: test
2015/04/10 16:43:20 Running: get status
Project: myProject
Zone: us-central1-b
current-context: ""
Running: /var/tmp/fab/kubernetes/cluster/../cluster/gce/../../cluster/../_output/dockerized/bin/linux/amd64/kubectl --match-server-version version
Error: couldn't read version from server: Get http://localhost:8080/version: dial tcp <IP_ADDRESS>:8080: connection refused

2015/04/10 16:43:21 Error running get status: exit status 1
2015/04/10 16:43:21 Running: up
Project: myProject
Zone: us-central1-b
Starting cluster using provider: gce
... calling verify-prereqs

All components are up to date.

All components are up to date.
... calling kube-up
Project: myProject
Zone: us-central1-b
current-context: ""
Running: /var/tmp/fab/kubernetes/hack/e2e-internal/../../cluster/../cluster/gce/../../cluster/../cluster/../cluster/gce/../../cluster/../_output/dockerized/bin/linux/amd64/kubectl config view -o template --template={{$dot := .}}{{with $ctx := index $dot "current-context"}}{{range $element := (index $dot "contexts")}}{{ if eq .name $ctx }}{{ with $user := .context.user }}{{range $element := (index $dot "users")}}{{ if eq .name $user }}{{ index . "user" "username" }}{{end}}{{end}}{{end}}{{end}}{{end}}{{end}}
current-context: ""
Running: /var/tmp/fab/kubernetes/hack/e2e-internal/../../cluster/../cluster/gce/../../cluster/../cluster/../cluster/gce/../../cluster/../_output/dockerized/bin/linux/amd64/kubectl config view -o template --template={{$dot := .}}{{with $ctx := index $dot "current-context"}}{{range $element := (index $dot "contexts")}}{{ if eq .name $ctx }}{{ with $user := .context.user }}{{range $element := (index $dot "users")}}{{ if eq .name $user }}{{ index . "user" "password" }}{{end}}{{end}}{{end}}{{end}}{{end}}{{end}}
Creating gs://kubernetes-staging-4484187ceb
Creating gs://kubernetes-staging-4484187ceb/...
BadRequestException: 400 Invalid argument.
2015/04/10 16:43:34 Error running up: exit status 1
2015/04/10 16:43:34 Error starting e2e cluster. Aborting.
exit status 1

@dchen1107
I cannot pass the test because of the above error. It is 100% reproduceable and even though I tried after new git clone. Do you pass the test without error? And should I submit as new issue?

@nak3 My tests are passed. It is flaky sometimes, but failed most of time. How about do a "make clean && make release && hack/e2e-test.sh"?

This currently breaks the /validate endpoint. It expects node names to be resolvable DNS addresses. That is a bug in the validate handler, but should be fixed before we merge this.
Also, is there a reason not to just use os.Hostname() in the Go code?

@dchen1107
I tried make clean && make release && hack/e2e-test.sh but it is still same result. Okay, I will try to debug it by myself.
@cjcullen

Also, is there a reason not to just use os.Hostname() in the Go code?

Please read comment here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/v0.15.0/pkg/util/node.go#L29-L30
os.Hostname() just returns from /proc/sys/kernel/hostname:
https://github.com/golang/go/blob/weekly.2012-03-27/src/pkg/os/sys_linux.go#L9-L26

Just a memo,
I resolved last issue, but I am still hitting another issue.
Found 2 nodes.
     1	e2e-test-knakayam-minion-g9cv.c.nak3-test2.internal
     2	e2e-test-knakayam-minion-lfas.c.nak3-test2.internal
Attempt 1 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 2 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 3 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 4 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 5 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 6 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ... [not working yet]
Attempt 7 at checking Kubelet installation on node e2e-test-knakayam-minion-g9cv ...
Kubelet failed to install on node e2e-test-knakayam-minion-g9cv. Your cluster is unlikely to work correctly.
Please run ./cluster/kube-down.sh and re-create the cluster. (sorry!)
2015/04/17 00:25:14 Error running up: exit status 1
2015/04/17 00:25:14 Error starting e2e cluster. Aborting.
exit status 1

$ ./cluster/kube-up.sh didn't in my environment, and single running of $ ./cluster/kube-up.sh is hitting same problem.

@nak3 I believe the last issue you hit here is the issue mentioned by @cjcullen above: /validate endpoint is broken. I will take a deep look at this.

@nak3 Do you mind me to cherry-pick your commit to my branch, and pick up the rest of work from here? I will preserve your work, and fix what is broken internally.

@dchen1107

Do you mind me to cherry-pick your commit to my branch, and pick up the rest of work from here? I will preserve your work, and fix what is broken internally.

No I don't mind. Please do as you like.

@nak3 I were out last Friday without sending my PR. It turns out several breakages in e2e setup and test itself were fixed recently. I sent out #7072 based on your commit, now everything works fine. Thanks!

So this broke AWS.... but ... does this mean that the actual string doesn't matter any more (it doesn't need to be resolvable?)  If so, I might try putting in the AWS instance-id - using a truly unique identifier would make things a lot more robust.

@justinsb name is not required to be resolvable, but need to be unique in a given cluster. Using AWS instance-id is a good choice. Sorry for breakage here. I should cc to you at the first place. Thanks!


congenital diseases: sparql + Robot to add subclass

Fixes #4069

I dont really want to review this, but looks good on cursory glance! Well done going full circle SPARQL + TEMPLATE + MERGE! Impressive!

thanks for doing this @sabrinatoro!


Client Allocation Request for: asd

Client Allocation Questions
Core Information

Name: asd
Website / Social Media: asd, (asd, asd)
Region: Africa
DataCap Requested: 896 GiB
Addresses to be Notarized: asd
Notary Requested: Deon Erda

This user’s identity has has been verified through filplus.storage

This user’s identity has been verified through filplus.storage


doc: Add 'Zephyr FSM plan' to glossary

Add 'Zephyr FSM plan' to glossary
as used in the zephyr functional safety management plan.

Agree on not re-using the FSM acronym

@simhein's suggestion goes in the right direction. This new entry needs to be reference from at least somewhere though, as we don't want to add entries to the glossary just for the sake of it, but rather have these entries being pointed to from other pages in the docs.

True I generally agree with that, I will check on it how we can integrate the safety plan and reference to it in the docs because we can't publish the whole plan because of legal issues with references and text to the safety standard

closing this PR as it looks like there is agreement on taking a different approach than adding safety terms in the general Zephyr glossary


How to Stake with that contract?

"The network launches with a Validator Deposit Contract deployed at address 0x4242424242424242424242424242424242424242. This can be used to onboard new validators into the network by depositing 32 ETH into the contract"
Where could I get deposit contract details.....
I just want to add validator by staking(maybe deposit to contract), but I can't find the detail process of that...
Could I get any contract method detail for deposit and withdraw???

I used ethereal to deposit.


Test out endpoints

solved issue #426

Conflicts, no one updates workflow files except for me or @/ibitolamayowa
so i can't merge this


Add subtitle support (via drag-n-drop)

Drag and drop a subtitles file (.srt or .vtt) onto the player (or the
app icon on OS X) to add subtitles to the currently playing video.
For #281
With controls hidden:

With controls shown:

Modeled the text style after VLC. White text, black outline, gray shadow to the bottom right.

Wow, that was fast!

@MoOx thanks!

is srt-to-vtt really needed?
AFAIK  tag has native srt support, i mean, vtt is kinda a superset of srt.
Let me check but i am pretty sure its fully compatible with  tag

@feross modified subtitle state structure to handle multiple tracks, will be working on it a little bit more
Do we have a tooltip like menu we can display on CC icon selection to display and select subtitles when more than one is available?


[Build][CMake] LIBOMP: Cannot find llvm-lit

Description
Hey, I am trying building MXNet from source using CMake. Although I am able to build it, cmake does produce some warnings that I would love to configure out why.
-- LIBOMP: Cannot find llvm-lit.
-- LIBOMP: Please put llvm-lit in your PATH, set LIBOMP_LLVM_LIT_EXECUTABLE to its full path or point OPENMP_LLVM_TOOLS_DIR to its directory
CMake Warning at 3rdparty/openmp/runtime/cmake/LibompUtils.cmake:21 (message):
  LIBOMP: The check-libomp target will not be available!
Call Stack (most recent call first):
  3rdparty/openmp/runtime/test/CMakeLists.txt:62 (libomp_warning_say)

I suppose that openmp is downloaded by the cmake script and built from scratch, so shouldn't it be self-contained? So is there any flags that i missed out? Any ideas would be super helpful!
Environment info (Required)
----------Python Info----------
Version      : 3.7.4
Compiler     : GCC 7.3.0
Build        : ('default', 'Aug 13 2019 20:35:49')
Arch         : ('64bit', '')
------------Pip Info-----------
Version      : 19.2.2
Directory    : /home/ubuntu/anaconda3/envs/mx-dev/lib/python3.7/site-packages/pip
----------MXNet Info-----------
No MXNet installed.
----------System Info----------
Platform     : Linux-4.15.0-1050-aws-x86_64-with-debian-buster-sid
system       : Linux
node         : ip-172-31-6-139
release      : 4.15.0-1050-aws
version      : #52-Ubuntu SMP Thu Sep 12 19:56:00 UTC 2019
----------Hardware Info----------
machine      : x86_64
processor    : x86_64
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              96
On-line CPU(s) list: 0-95
Thread(s) per core:  2
Core(s) per socket:  24
Socket(s):           2
NUMA node(s):        2
Vendor ID:           GenuineIntel
CPU family:          6
Model:               85
Model name:          Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
Stepping:            4
CPU MHz:             1328.387
BogoMIPS:            4999.99
Hypervisor vendor:   KVM
Virtualization type: full
L1d cache:           32K
L1i cache:           32K
L2 cache:            1024K
L3 cache:            33792K
NUMA node0 CPU(s):   0-23,48-71
NUMA node1 CPU(s):   24-47,72-95
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves ida arat pku ospke
----------Network Test----------
Setting timeout: 10
Timing for MXNet: https://github.com/apache/incubator-mxnet, DNS: 0.0065 sec, LOAD: 0.4751 sec.
Timing for Gluon Tutorial(en): http://gluon.mxnet.io, DNS: 0.0008 sec, LOAD: 0.0202 sec.
Timing for Gluon Tutorial(cn): https://zh.gluon.ai, DNS: 0.0009 sec, LOAD: 0.3636 sec.
Timing for FashionMNIST: https://apache-mxnet.s3-accelerate.dualstack.amazonaws.com/gluon/dataset/fashion-mnist/train-labels-idx1-ubyte.gz, DNS: 0.0005 sec, LOAD: 0.1157 sec.
Timing for PYPI: https://pypi.python.org/pypi/pip, DNS: 0.0019 sec, LOAD: 0.0496 sec.
Timing for Conda: https://repo.continuum.io/pkgs/free/, DNS: 0.0004 sec, LOAD: 0.0244 sec.
----------Environment----------
CC="/usr/bin/gcc"
CXX="/usr/bin/g++"
MXNET_HOME="/home/ubuntu/Projects/mxnet-dev"

Package used (Python/R/Scala/Julia): Python
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio): gcc 7.4
>>> $CC --version
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

MXNet commit hash: cab1dfad37f044d691e7c4ea81d73463cfcf0c8d
Build config: cmake .. -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DUSE_CUDA=OFF
(Paste the content of config.mk, or the build command.)
Error Message:
>>> cmake .. -DUSE_CUDA=OFF
-- The C compiler identification is GNU 7.4.0
-- The CXX compiler identification is GNU 7.4.0
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- CMAKE_CROSSCOMPILING FALSE
-- CMAKE_HOST_SYSTEM_PROCESSOR x86_64
-- CMAKE_SYSTEM_PROCESSOR x86_64
-- CMAKE_SYSTEM_NAME Linux
-- Performing Test SUPPORT_CXX11
-- Performing Test SUPPORT_CXX11 - Success
-- Performing Test SUPPORT_CXX0X
-- Performing Test SUPPORT_CXX0X - Success
-- Performing Test SUPPORT_MSSE3
-- Performing Test SUPPORT_MSSE3 - Success
-- Performing Test SUPPORT_MSSE2
-- Performing Test SUPPORT_MSSE2 - Success
-- Determining F16C support
-- Performing Test COMPILER_SUPPORT_MF16C
-- Performing Test COMPILER_SUPPORT_MF16C - Success
-- F16C enabled
-- Downloading MKLML...
-- [download 0% complete]
-- [download 1% complete]
-- [download 2% complete]
-- [download 3% complete]
-- ...
-- [download 100% complete]
-- Setting MKLROOT path to /home/ubuntu/Projects/mxnet-dev/build/mklml/mklml_lnx_2<IP_ADDRESS>90502
-- CMAKE_BUILD_TYPE is unset, defaulting to Release
-- This is a product build
-- Detecting Intel(R) MKL: trying mklml_intel
-- Intel(R) MKL: include /home/ubuntu/Projects/mxnet-dev/build/mklml/mklml_lnx_2<IP_ADDRESS>90502/include
-- Intel(R) MKL: lib /home/ubuntu/Projects/mxnet-dev/build/mklml/mklml_lnx_2<IP_ADDRESS>90502/lib/libmklml_intel.so
-- Found OpenMP_C: -fopenmp (found version "4.5")
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- OpenMP lib: /home/ubuntu/Projects/mxnet-dev/build/mklml/mklml_lnx_2<IP_ADDRESS>90502/lib/libiomp5.so
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- VTune profiling environment is unset
-- Found Git: /usr/bin/git (found version "2.17.1")
-- Could NOT find MKL (missing: MKL_INCLUDE_DIR MKL_RT_LIBRARY)
-- Found OpenBLAS libraries: /usr/lib/x86_64-linux-gnu/libopenblas.so
-- Found OpenBLAS include: /usr/include/x86_64-linux-gnu
-- Could NOT find MKL (missing: MKL_INCLUDE_DIR MKL_RT_LIBRARY)
-- Found OpenBLAS libraries: /usr/lib/x86_64-linux-gnu/libopenblas.so
-- Found OpenBLAS include: /usr/include/x86_64-linux-gnu
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.1")
-- Could NOT find Jemalloc (missing: JEMALLOC_LIBRARY JEMALLOC_INCLUDE_DIR)
-- Found OpenCV: /usr (found version "3.2.0") found components:  core highgui imgproc imgcodecs
-- OpenCV 3.2.0 found (/usr/share/OpenCV)
--  OpenCV_LIBS=opencv_core;opencv_highgui;opencv_imgproc;opencv_imgcodecs
-- Found OpenMP_C: -fopenmp
-- Found OpenMP_CXX: -fopenmp
-- Found OpenMP: TRUE
-- Performing Test LIBOMP_HAVE_STD_CPP11_FLAG
-- Performing Test LIBOMP_HAVE_STD_CPP11_FLAG - Success
-- Performing Test LIBOMP_HAVE_FNO_EXCEPTIONS_FLAG
-- Performing Test LIBOMP_HAVE_FNO_EXCEPTIONS_FLAG - Success
-- Performing Test LIBOMP_HAVE_FNO_RTTI_FLAG
-- Performing Test LIBOMP_HAVE_FNO_RTTI_FLAG - Success
-- Performing Test LIBOMP_HAVE_X_CPP_FLAG
-- Performing Test LIBOMP_HAVE_X_CPP_FLAG - Success
-- Performing Test LIBOMP_HAVE_WERROR_FLAG
-- Performing Test LIBOMP_HAVE_WERROR_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_FUNCTION_FLAG
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_FUNCTION_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_LOCAL_TYPEDEF_FLAG
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_LOCAL_TYPEDEF_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_VALUE_FLAG
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_VALUE_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_VARIABLE_FLAG
-- Performing Test LIBOMP_HAVE_WNO_UNUSED_VARIABLE_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_SWITCH_FLAG
-- Performing Test LIBOMP_HAVE_WNO_SWITCH_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test LIBOMP_HAVE_WNO_COVERED_SWITCH_DEFAULT_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_DEPRECATED_REGISTER_FLAG
-- Performing Test LIBOMP_HAVE_WNO_DEPRECATED_REGISTER_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_SIGN_COMPARE_FLAG
-- Performing Test LIBOMP_HAVE_WNO_SIGN_COMPARE_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_GNU_ANONYMOUS_STRUCT_FLAG
-- Performing Test LIBOMP_HAVE_WNO_GNU_ANONYMOUS_STRUCT_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_UNKNOWN_PRAGMAS_FLAG
-- Performing Test LIBOMP_HAVE_WNO_UNKNOWN_PRAGMAS_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_MISSING_FIELD_INITIALIZERS_FLAG
-- Performing Test LIBOMP_HAVE_WNO_MISSING_FIELD_INITIALIZERS_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_MISSING_BRACES_FLAG
-- Performing Test LIBOMP_HAVE_WNO_MISSING_BRACES_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_COMMENT_FLAG
-- Performing Test LIBOMP_HAVE_WNO_COMMENT_FLAG - Success
-- Performing Test LIBOMP_HAVE_WNO_SELF_ASSIGN_FLAG
-- Performing Test LIBOMP_HAVE_WNO_SELF_ASSIGN_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_VLA_EXTENSION_FLAG
-- Performing Test LIBOMP_HAVE_WNO_VLA_EXTENSION_FLAG - Failed
-- Performing Test LIBOMP_HAVE_WNO_FORMAT_PEDANTIC_FLAG
-- Performing Test LIBOMP_HAVE_WNO_FORMAT_PEDANTIC_FLAG - Failed
-- Performing Test LIBOMP_HAVE_MSSE2_FLAG
-- Performing Test LIBOMP_HAVE_MSSE2_FLAG - Success
-- Performing Test LIBOMP_HAVE_FTLS_MODEL_FLAG
-- Performing Test LIBOMP_HAVE_FTLS_MODEL_FLAG - Success
-- Performing Test LIBOMP_HAVE_MMIC_FLAG
-- Performing Test LIBOMP_HAVE_MMIC_FLAG - Failed
-- Performing Test LIBOMP_HAVE_M32_FLAG
-- Performing Test LIBOMP_HAVE_M32_FLAG - Failed
-- Performing Test LIBOMP_HAVE_X_FLAG
-- Performing Test LIBOMP_HAVE_X_FLAG - Success
-- Performing Test LIBOMP_HAVE_WARN_SHARED_TEXTREL_FLAG
-- Performing Test LIBOMP_HAVE_WARN_SHARED_TEXTREL_FLAG - Success
-- Performing Test LIBOMP_HAVE_AS_NEEDED_FLAG
-- Performing Test LIBOMP_HAVE_AS_NEEDED_FLAG - Success
-- Performing Test LIBOMP_HAVE_VERSION_SCRIPT_FLAG
-- Performing Test LIBOMP_HAVE_VERSION_SCRIPT_FLAG - Success
-- Performing Test LIBOMP_HAVE_STATIC_LIBGCC_FLAG
-- Performing Test LIBOMP_HAVE_STATIC_LIBGCC_FLAG - Success
-- Performing Test LIBOMP_HAVE_Z_NOEXECSTACK_FLAG
-- Performing Test LIBOMP_HAVE_Z_NOEXECSTACK_FLAG - Success
-- Performing Test LIBOMP_HAVE_FINI_FLAG
-- Performing Test LIBOMP_HAVE_FINI_FLAG - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Perl: /usr/bin/perl (found version "5.26.1")
-- Performing Test LIBOMP_HAVE_VERSION_SYMBOLS
-- Performing Test LIBOMP_HAVE_VERSION_SYMBOLS - Success
-- Performing Test LIBOMP_HAVE___BUILTIN_FRAME_ADDRESS
-- Performing Test LIBOMP_HAVE___BUILTIN_FRAME_ADDRESS - Success
-- Performing Test LIBOMP_HAVE_WEAK_ATTRIBUTE
-- Performing Test LIBOMP_HAVE_WEAK_ATTRIBUTE - Success
-- Looking for include files windows.h, psapi.h
-- Looking for include files windows.h, psapi.h - not found
-- Looking for EnumProcessModules in psapi
-- Looking for EnumProcessModules in psapi - not found
-- LIBOMP: Operating System     -- Linux
-- LIBOMP: Target Architecture  -- x86_64
-- LIBOMP: Build Type           -- Release
-- LIBOMP: OpenMP Version       -- 50
-- LIBOMP: Library Kind         -- SHARED
-- LIBOMP: Library Type         -- normal
-- LIBOMP: Fortran Modules      -- FALSE
-- LIBOMP: Build                -- 20140926
-- LIBOMP: Use Stats-gathering  -- FALSE
-- LIBOMP: Use Debugger-support -- FALSE
-- LIBOMP: Use ITT notify       -- TRUE
-- LIBOMP: Use OMPT-support     -- FALSE
-- LIBOMP: Use Adaptive locks   -- TRUE
-- LIBOMP: Use quad precision   -- TRUE
-- LIBOMP: Use TSAN-support     -- FALSE
-- LIBOMP: Use Hwloc library    -- FALSE
-- Found PythonInterp: /home/ubuntu/anaconda3/envs/mx-dev/bin/python (found version "3.7.4")
-- Looking for sqrt in m
-- Looking for sqrt in m - found
-- Looking for __atomic_load_1
-- Looking for __atomic_load_1 - not found
-- Looking for __atomic_load_1 in atomic
-- Looking for __atomic_load_1 in atomic - found
-- LIBOMP: Cannot find llvm-lit.
-- LIBOMP: Please put llvm-lit in your PATH, set LIBOMP_LLVM_LIT_EXECUTABLE to its full path or point OPENMP_LLVM_TOOLS_DIR to its directory
CMake Warning at 3rdparty/openmp/runtime/cmake/LibompUtils.cmake:21 (message):
  LIBOMP: The check-libomp target will not be available!
Call Stack (most recent call first):
  3rdparty/openmp/runtime/test/CMakeLists.txt:62 (libomp_warning_say)

USE_LAPACK is ON
-- Could NOT find Jemalloc (missing: JEMALLOC_LIBRARY JEMALLOC_INCLUDE_DIR)
-- Found GTest: gtest
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for fopen64
-- Looking for fopen64 - not found
-- Looking for C++ include cxxabi.h
-- Looking for C++ include cxxabi.h - found
-- Looking for nanosleep
-- Looking for nanosleep - found
-- Looking for backtrace
-- Looking for backtrace - found
-- backtrace facility detected in default set of libraries
-- Found Backtrace: /usr/include
-- Check if the system is big endian
-- Searching 16 bit integer
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of unsigned short
-- Check size of unsigned short - done
-- Using unsigned short
-- Check if the system is big endian - little endian
-- /home/ubuntu/Projects/mxnet-dev/3rdparty/dmlc-core/cmake/build_config.h.in -> /home/ubuntu/Projects/mxnet-dev/3rdparty/dmlc-core/include/dmlc/build_config.h
-- Found OpenMP_C: -fopenmp
-- Found OpenMP_CXX: -fopenmp
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ubuntu/Projects/mxnet-dev/build

Minimum reproducible example
Just run cmake .. -DUSE_CUDA=OFF.
Steps to reproduce
Just run cmake .. -DUSE_CUDA=OFF.
What have you tried to solve it?
No idea

Tried with the most recent HEAD (dccfc88f66d23366bd478ec42fd9b106ae74d2ad) the issue still exists.

problem still here in latest code today, master branch, on MacOS latest with llvm 11.

Should be fixed by https://github.com/apache/incubator-mxnet/issues/19610

Should be fixed by https://github.com/apache/incubator-mxnet/issues/19610


Adding documentation to types and functions.

This clears all golint warnings.

@carloseberhardt I'm going to break process and merge this myself.  It's just documentation.  ;)
The golint tool should no longer complain.


[FEATURE] : Design Privacy Page

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
@Counselllor
there are dummy footer link,
it doesn't redirect us to any page

Describe the solution you'd like
A clear and concise description of what you want to happen.
when user click privacy link from footer we can redirect them to /privacy

Would you like to work for all pages which is in footer !
This all containing level 3

@thestarsahil
yes, i would like to work on all of these footer pages
can you please asssign it to me i will do all those pages

@dhruv8433 Good to Go !

@thestarsahil
this is my discord user id
1103340371834056806
username
dhruv7143

@thestarsahil
thank you so much


time series forecasting using rnn

`
library(Quandl)
sh_stock_ex <- Quandl("YAHOO/SS_600292", type="xts")
library(xts)
data <- scale(sh_stock_ex[-1,5])
feat <- merge(na.trim(lag(data,1)), na.trim(lag(data,2)), na.trim(lag(data,3)), na.trim(lag(data,4)),
na.trim(lag(data,5)), all=FALSE)
dataset <- merge(feat, data, all = FALSE)
colnames(dataset) <- c("lag.1", "lag.2","lag.3","lag.4","lag.5", "obj")
index <- 1:4000
training <- as.data.frame(dataset[index,])
testing <- as.data.frame(dataset[-index,])
library(mxnet)
train.x <- data.matrix(training[,-6])
train.y <- training[,6]
test.x <- data.matrix(testing[,-6])
test.y <- testing[,6]
get.label <- function(X) {
label <- array(0, dim=dim(X))
d <- dim(X)[1]
w <- dim(X)[2]
for (i in 0:(w-1)) {
for (j in 1:d) {
label[i_d+j] <- X[(i_d+j)%%(w*d)+1]
}
}
return (label)
}
X.train.label <- get.label(t(train.x))
X.val.label <- get.label(t(test.x))
X.train <- list(data=t(train.x), label=X.train.label)
X.val <- list(data=t(test.x), label=X.val.label)
batch.size = 5
seq.len = 5
num.hidden = 5
num.embed = 5
num.rnn.layer = 1
num.round = 100
update.period = 1
learning.rate= 0.1
wd=0.00001
clip_gradient=1
mx.set.seed(0)
model <- mx.rnn(X.train, X.val, num.rnn.layer=num.rnn.layer, seq.len=seq.len, num.hidden=num.hidden,
num.embed=num.embed, num.label=5, batch.size=batch.size, input.size=5, ctx = mx.cpu(),
num.round = num.round, update.period = update.period, initializer = mx.init.uniform(0.01),
dropout = 0, optimizer = "sgd", batch.norm = FALSE,
learning.rate=learning.rate, wd=wd, clip_gradient=clip_gradient)`
It turn out an error:
[23:09:52] d:\chhong\mxnet\src\operator./reshape-inl.h:227: Using target_shape will be deprecated.
[23:09:52] D:\chhong\mxnet\dmlc-core\include\dmlc/logging.h:235: [23:09:52] D:\chhong\mxnet\src\ndarray\ndarray.cc:227: Check failed: from.shape() == to->shape() operands shape mismatch
Error: [23:09:52] D:\chhong\mxnet\src\ndarray\ndarray.cc:227: Check failed: from.shape() == to->shape() operands shape mismatch
How to understand this error message and locate the error code?
Is there any useful tutorial or papers about time series forecasting using rnn or lstm? many thanks!

Hi bifeng,
i am trying to understand your get.label function..for what do you need it?? this functio is not working..i_d is no found when i try it...

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!


Add go modules support

Codecov Report

Merging #10 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #10   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          224       224
=========================================
  Hits           224       224

Impacted Files
Coverage Δ

kdrange/range.go
100.00% <ø> (ø)

kdtree.go
100.00% <ø> (ø)

points/point.go
100.00% <ø> (ø)

points/point2d.go
100.00% <ø> (ø)

points/point3d.go
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b01f40c...d899500. Read the comment docs.


Theme switching doesn't appear to work for Regolith 3

Recently switched to regolith for my window manager, and went through the set up process for the themes for gnome-terminal and gtk.
However, running the regolith-look command clears my default font for gnome-terminal, and the surrounding colors don't appear to be updating either, instead just inheriting whatever theme was installed previously.

Same here

Same here as well

Same here as well

Hey guys check out this PR on regolith-looks-extra, someone seems to have made a regolith 3 compatible adaptation:
https://github.com/regolith-linux/regolith-look-extra/issues/18


Automated Package Upgrade

:tada: This PR is included in version 7.1.11 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Incorrect sum call in Boundaries.Internal.PartialVolumeN

outlet.m_flow is not an array in PartialVolumeN, so sum(outlet.m_flow) is incorrect on this line and should just be outlet.m_flow:
https://github.com/DLR-SR/ThermofluidStream/blob/4c7a642e49602af76d683a1d20405fdb63fb6537/ThermofluidStream/Boundaries/Internal/PartialVolumeN.mo#L117
This used to be allowed by OpenModelica by mistake, which caused some issues since it wasn't supposed to be allowed (the Modelica specification only define sum for array expression).

fixed in ef31d9a470c4115b708e3a4b9904b399a68e6d3f


Data[0] = "The provided uri did not return any Service Endpoints!

Hi @WaelHamze , I am trying to create CI pipeline but getting this error.
2020-05-11T08:18:07.9022261Z ##[section]Starting: Export Solution: RavinderTest
2020-05-11T08:18:07.9129816Z ==============================================================================
2020-05-11T08:18:07.9130135Z Task         : Export Solution
2020-05-11T08:18:07.9130450Z Description  : Exports a PowerApps/CDS/Dynamics 365 Solution from the source environment
2020-05-11T08:18:07.9130777Z Version      : 12.0.3
2020-05-11T08:18:07.9130984Z Author       : Wael Hamze
2020-05-11T08:18:07.9131470Z Help         : This task uses ExportSolutionRequest
2020-05-11T08:18:07.9131991Z ==============================================================================

@WaelHamze, Please suggest or redirect me on any link where I can find solution of this. I have tried number of times and with different organization instance but it is getting same error.
Data[0] = "The provided uri did not return any Service Endpoints!

The format for connection string is here: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/xrm-tooling/use-connection-strings-xrm-tooling-connect
The intro video might help: https://youtu.be/rl62P68UxE4

Thanks @WaelHamze  it is working now, that Video is really help full. :)

@ravinderkumar007 glad you got it working and the video wasn't a waste of time :)


Related workloads section - Need to add to Secrets and ConfigMap pages

We need to add a related workloads section to the Secret's details page.  It should be consistent with what we want to do in ConfigMap section

https://xd.adobe.com/view/fa2c37a2-9fc4-45ac-6f0d-7e0ee06eff5c-8c1d/

Based on comment from configmap, let's wait for API to make this easier.
https://github.com/rancher/dashboard/issues/265#issuecomment-614795824

Seems like it might be ready based on this: https://github.com/rancher/rancher/issues/27487

This shouldn't have been moved to test.  This issue is for adding a Related Resources tab to ConfigMap & Secrets Detail pages that show any workload that pull them.

It doesn't look anything like the 6 month old screenshots but I added related workloads to all the types that use <ResourceTabs>, which should be most detail pages.

Can't verify because backend API not returning relationship info for secret & Configmaps.  https://github.com/rancher/rancher/issues/30413

Once this backend is done, this should just work right away.


context menu editor

Description of the new feature / enhancement
ability to edit/remove any and all entries in all context menus
there are to my knowledge no complete context menu editors except possibly the ones in the sysinternals suite, which are very cryptic
Scenario when this would be used?
used any time an app adds an entry in the context menu
Supporting information
No response

Hello and thanks for your message. It's not that simple, because entries are coming from different places. /duplicate #33.


Class refactoring

@georgecrawford please review
This patch includes the following changes:

rewritten adapter into a class to share data across methods
minor tweaks due to wdio-sync package changes
simplified adapter methods (less parameters)

Not all hooks are running through wrapHook anymore because I complicates stuff a lot. So command hooks get propagated when calling wrapCommands and hook hooks get propagated when overwriting it and test ui commands. The function now has a more dedicated job.
Missing in this PR and WIP: unit tests. Wanted to make sure that PRs get tested accordingly. So I am using the process to fix this too.

Added tests for hooks.

@georgecrawford can you review?

It's working great for me, except this one remaining use case:
		browser.addCommand('wait1', function async() {
			return this.pause(1000)
			.then(() => {
				console.log('wait1 complete', Date.now() - start);
			});
		});

		browser.addCommand('wait2', function async() {
			return new Promise((resolve) => {
				console.log('wait2 starts', Date.now() - start);
				setTimeout(() => {
					console.log('wait2 complete', Date.now() - start);
					resolve();
				}, 1000);
			});
		});

		browser.addCommand('wait3', function async() {
			return new Promise((resolve) => {
				console.log('wait3 starts', Date.now() - start);
				return this.wait1()
				.then(() => {
					console.log('wait3 middle', Date.now() - start);
				})
				.then(this.wait2)
				.then(() => {
					console.log('wait3 complete', Date.now() - start);
					resolve();
				});
			});
		});

		start = Date.now();
		browser.wait3();
		console.log('wait3 after', (Date.now() - start));

gives:
wait3 starts 1
wait1 complete 1007
wait3 middle 1007
wait2 starts 1007
wait3 complete 1008
wait3 after 1009

Can this be fixed?

This issue is related to the wdio-sync package. The Fiber wrapper can't handle native promises or promises from 3rd party packages. I will look into that next and will add some testing around that

OK cool. Then no other issues :)

Ok, merge this in order to move forward. Adding tests once I've got it fixed in wdio-sync


Improved and new linked General Readme

What is the change?

Added all the new links and rectified and corrected previous links.
Made all the links in serial alphabetical order.

Related issue?
closes: #269
How was it tested?
This has been tested in my local PC.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelineswhile contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Have you tested the code before submission?
[x] Have you formatted your code ? (You can use any html,css beautifier)
[x] My changes generates no new warnings.
[x] I'm HSOC22 contributor.
[x] I have commented my code, particularly in hard-to-understand areas.

Please don't rename files

I have not renamed any file. There were two SignIn Forms with same Folder name, so I changed the Folder name by just putting a hyphen. So it's not any file rename issue.


stubbed user and stubbed test_2

This request implements the stubbed user and test project for Cypress
#108

So it seemes like the issue with the checks is that cypress could not verify that this server > http://localhost:5173 is running..
Is there any way to solve this?

@HassanAlhawari1998 Can you please make the review?

Yes, I will review this pull request.


Don't specify bucket names on the stack template

Buckets are global names and have some eventual name gc that we cannot control.
This enables deploying stack with same name on different regions as well.

Closed in 16db86f


{App Service} Bugfix: az webapp create error when name is a substring of existing webapp

Description
When creating a webapp with a name that is a substring of an existing webapp in your subscription, CLI throws error:
Webapp 'name_that_is_substring' already exists. The command will use the existing app's settings. Cannot acquire exclusive lock to create, update or delete this site. Retry the request later.
This is due to CLI using 'in' instead of '==' when comparing app names, and CLI thinks the app with the name that is a substring already exists when it doesn't.
Testing Guide

Creating two webapps, with second webapp name as a substring of first webapp name (ex. TestApp1, TestApp) should work. Currently, if you create webapp TestApp1 then try to create TestApp, the command thinks TestApp exists already since it's a substring of TestApp1.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

App Service

@qwordy anyway we can get the build to restart?

@qwordy anyway we can get the build to restart?

Do you mean rerun all checks? Comment '/azp run'

@calvinsID What's the status of this PR? I noticed that you deleted the changes.

@qwordy  Yup its good to go. I removed a yaml prerecording, but it wasn't necessary

@calvinsID The only code change in this PR is
data = (list(filter(lambda x: name.lower() == x.name.lower(), client.web_apps.list())))

I don't think it improves error handling.

@qwordy You're right, I'm not sure why I had error handling in there... must have moved it to a diff PR. I'll update description

@calvinsID  I believe this helper method is used in az webapp up as well so can you test that as well plus add a test case for this scenario using az webapp create so we don't regress this again? Thank you.

Closing since unable to repro on latest dev branch


DateTimeOffset - loss of offset information

scenario
store a value of datetimeoffset type with a non 0 utc offset (all tests store utc, so they dont see this issue). Observe both time and offset field stored.
load the same value using this library
compare stored datetime value and offset with loaded value and offset - offset will be 0 but should be the same as it was stored.

This isn't the official Parquet.NET repo. See https://github.com/aloneguid/parquet-dotnet


[WIP] Add test for gemm overflow.

Description
Add a test for big matrix multiplications that overflow gemm int32 indexes.
This test checks that an exception is thrown instead of calling gemm with wrong indices which causes segfaults or wrong results.
For more info see related issues and PR:
https://github.com/apache/incubator-mxnet/issues/14522 https://github.com/dmlc/mshadow/pull/372
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot Add [Test]

Thanks, needs mshadow PR to be merged first. Then I remove [WIP], rerun CI and merge.

@mxnet-label-bot add [pr-awaiting-review]

@mxnet-label-bot add[pr-awaiting-merge]

@mxnet-label-bot remove[pr-awaiting-response, pr-awaiting-review]

@mxnet-label-bot remove[pr-work-in-progress]

@larroy Please rebase so it can be merged

I don't think this change passes CI. I can either have another look in my next oncall or close. I don't have time in the following days to continue working on this issue.

@mxnet-label-bot remove [pr-awaiting-merge]

@larroy What's the path forward here ?

I don't think I have time to look into this, so I might have to close.


Issue with k8s.io/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice-interactive/

It is not possible to scroll to the bottom of the file list in the code part of the window:

The above is as far as I'm able to scroll down, which makes it impossible to reach the file I'm supposed to edit in the project.
(in general, holy gods, is that an unusable window size! If there's any way to expand it while keeping the tutorial in view, that would be wonderful! I tried  but all that did was make the terminal / katcode full screen, hide the tutorial, and I still couldn't scroll to the bottom (see

)

I am using Chrome (Version 104.0.5112.101 (Official Build) (x86_64)) on macOS

@offbyone   I am using Version 104.0.5112.81 (Official Build) (64-bit)  on windows and it is working find to me

That is ... great, I guess? It doesn't help me, though.

@offbyone  try reloading page. it might help

I did that.


Use more of Tintytest assertions

We can now remove some code duplication that https://github.com/meteor/meteor/pull/3780 was merged in.

(We should wait for it to be released.)

Also https://github.com/meteor/meteor/pull/3810 was merged in with more assertions.


Fixing master break... nearly... on more test to go

So, I fixed most of the tests... there was a function context problem and that resolved the bulk of stuff.
Right now, the Network from .fbp test is failing due to a deadlock... not sure why that is. Investigating...
BTW: I made this a PR to make my changes clearer

Also... sorry about the whitespace churn. I let my IDE clean things up for me.
I'll see if I can come up with something that results in less whitespace ping-pong

This link removes the whitespace changes, but also hides the comments...
https://github.com/jpaulm/jsfbp/pull/60/files?w=1

OK, I fixed the last test. I had my logic inverted on identifying self-starting processes.

Great!  I am still getting connections logged - any idea where these are
coming from? I have merged #60 (I think), and done a git pull, so I can't
see where they are coming from - or maybe I have missed a step!
The good news is that Travis says everything is OK now!  Thanks a million!
Onwards and upwards!
Paul
On Wed, Jun 1, 2016 at 2:06 PM, Dan Rumney<EMAIL_ADDRESS>wrote:

OK, I fixed the last test. I had my logic inverted on identifying
self-starting processes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jpaulm/jsfbp/pull/60#issuecomment-223076731, or mute
the thread
https://github.com/notifications/unsubscribe/AATGJ0TdPaFK8njIxCNCWYKEJbleKXA9ks5qHcoegaJpZM4IrzQO
.

Could I be running the npm version, rather than the version on my C
drive?!   Is npm automagically updated as we go?
On Wed, Jun 1, 2016 at 2:30 PM, Paul Morrison<EMAIL_ADDRESS>wrote:

Great!  I am still getting connections logged - any idea where these are
coming from? I have merged #60 (I think), and done a git pull, so I can't
see where they are coming from - or maybe I have missed a step!
The good news is that Travis says everything is OK now!  Thanks a million!
Onwards and upwards!
Paul
On Wed, Jun 1, 2016 at 2:06 PM, Dan Rumney<EMAIL_ADDRESS>wrote:

OK, I fixed the last test. I had my logic inverted on identifying
self-starting processes.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jpaulm/jsfbp/pull/60#issuecomment-223076731, or mute
the thread
https://github.com/notifications/unsubscribe/AATGJ0TdPaFK8njIxCNCWYKEJbleKXA9ks5qHcoegaJpZM4IrzQO
.

I just removed some stray log statements, so things should look cleaner now.

So long as you're doing git pull on your master branch, that should work fine.

Thanks!  I have to go out for a while, but will try to test it when I get back!  Thanks for all your help!

I'm back!  And confused!  Where did you find the "stray" log statements?  I am still getting what look like connections being logged!  I don't see any more console.log statements...?  It's a mystery... :-(

setPortRuntime had a few logging statements that weren't guarded with any tracing test.
I think I'm confused by what

I am still getting what look like connections being logged!

means... can you clarify?

Sorry, I had a console.log in a strange place... :-)
My test seems to be working...  I think it is safer if I recreate my
branch, for your review...  See branch
https://github.com/jpaulm/jsfbp/tree/alternative_network_defs
Especially as my reader.js seems not to be working...  tests that don't use
reader.js seem to work!  Unless the location of the test data has moved...!
I had to change the way we step through _processes (including some of your
nice, compact code) - I'm afraid I usually have trouble with "shorthands".
I just find it is easier for me if I use a few extra keystrokes... if it is
more transparent.    Remember APL?!
I'll hold off creating a PR until you have had a look...  I hope I built
the branch OK... (?)
Not sure how this fits in with #62... - haven't looked at it yet.
BTW There really weren't any changes to reader.js or OutputPort.js (I was
mostly adding or removing console.log statements).
I'll take a look at the other PR's later, or tomorrow...  I would say that
if you are OK with fbptest01.js as it is now, we could retire #35 (#55?).
I have been using the new notation for several years in JavaFBP.

Best regards,
Paul
On Wed, Jun 1, 2016 at 4:27 PM, Dan Rumney<EMAIL_ADDRESS>wrote:

setPortRuntime had a few logging statements that weren't guarded with any
tracing test.
I think I'm confused by what
I am still getting what look like connections being logged!
means... can you clarify?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jpaulm/jsfbp/pull/60#issuecomment-223114379, or mute
the thread
https://github.com/notifications/unsubscribe/AATGJ-0CfcvDyY7esoC-zCJR0PydD50Wks5qHes1gaJpZM4IrzQO
.

Regarding:

I'll take a look at the other PR's later, or tomorrow...  I would say that
if you are OK with fbptest01.js as it is now, we could retire #35 (#55?).
I have been using the new notation for several years in JavaFBP.

I think there's still the need to ensure that all processes are named, even if they aren't explicitly named.
Maybe the simplest approach is to require that processes be explicitly named and throw and error if they are not. That would remove the need to automatically name them if they are unnamed.

Sounds good!  I'll (try to) do that tomorrow!
Regards,
Paul
On Wed, Jun 1, 2016 at 10:02 PM, Dan Rumney<EMAIL_ADDRESS>wrote:

Regarding:
I'll take a look at the other PR's later, or tomorrow... I would say that
if you are OK with fbptest01.js as it is now, we could retire #35
https://github.com/jpaulm/jsfbp/issues/35 (#55
https://github.com/jpaulm/jsfbp/pull/55?).
I have been using the new notation for several years in JavaFBP.
I think there's still the need to ensure that all processes are named,
even if they aren't explicitly named.
Maybe the simplest approach is to require that processes be explicitly
named and throw and error if they are not. That would remove the need to
automatically name them if they are unnamed.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/jpaulm/jsfbp/pull/60#issuecomment-223176579, or mute
the thread
https://github.com/notifications/unsubscribe/AATGJ5OJU_sBW1QTe3Y6aUdEA6x_2lnRks5qHjnIgaJpZM4IrzQO
.


sql: support full HLC precision timestamps in AS OF #9934

PR: https://github.com/cockroachdb/cockroach/pull/9934
As mentioned in beta-2016-10-27 release notes:

AS OF SYSTEM TIME queries now support the decimal format returned by cluster_logical_timestamp() for maximum precision.

Feature already documented.

Feature already documented.


[rust] Commit to test rust CI

This is a trivial PR not meant to be merged, but rather to trigger CI workflows for debugging https://issues.apache.org/jira/browse/ARROW-9628

All the tests pass, so nothing was learned. Closing this PR. Sorry for the noise


[?] Unit times file names

Currently the function save_units saves the h5 times files adding a ch before the channel name. However, because the channel names are already chan_\d\d\d, for example, the units spike times h5 files end up saved as times_chan_chan_\d\d\d_u\d.h5.
https://github.com/HSUPipeline/convnwb/blob/142c8f8fb17d13eb8c350571923714d794cd242a/convnwb/sorting/io.py#L139

Fixed in this commit:
https://github.com/HSUPipeline/convnwb/commit/11415d866af726d84cf78b80b61dc83f988efe45


unable to receive binary data in subscribe on pubsub

Checklist

Python version
3.8.5
Using hiredis or just Python parser
StrictRedis?
Using uvloop or just asyncio event loop
uvicorn?
Does issue exists against the master branch of aredis?
not sure

Steps to reproduce
unable to publish a binary data, ex:
redis.publish(channel_name, pickle.dumps(someobject))
upon await pubsub.get_message()
the data received is an integer 1
Expected behavior
receive binary data

I think during initial subscription msg['data'] = 1 is emitted every time? is this a known behavior?


REL: set 1.15.0rc2 unreleased

Set the version to SciPy 1.15.0rc2 "unreleased."

[ci skip] [skip ci] [skip cirrus] [skip circle]

Ok, I revised to append .dev0. This is a one-line change with CI skipped and the instructions just call for a direct push anyway so I'm going to self-merge.


LTC5507

"The LTC5507 is an RF power detector for applications operating from 100kHz to 1000MHz. The input frequency range is determined by an external capacitor. A temperature-compensated Schottky diode peak detector and buffer amplifier are combined in a small 6-pin ThinSOT package.
The RF input voltage is peak detected using an on-chip Schottky diode and external capacitor. The detected voltage is buffered and supplied to the VOUT pin. A power saving shutdown mode reduces supply current to less than 2µA."
-Linear Technologies
┆Attachments: LTC5507 Datasheet.pdf

➤ Gavin Allcorn commented:
100kHz - 1GHz

➤ Gavin Allcorn commented:
Range is small

➤ Gavin Allcorn commented:
According to frequency range document, this chip will not work as the upper frequency band of cell phone communicatino is 1.9GHz


Week, Hour, Minute and Second components

Feature Request
Hi, I have done some work on a fork to add the following:

Week component
Hour component
Minute component
Second component

as well as changing the interval_ available to the duration. That ofc is a breaking change.
I have also refactored the tests to be a tad more exhaustive.
I am unsure how to proceed with this, if you would consider it (BC), but the fork is available for now  at https://github.com/thoroc/date_component.
~thoroc

@thoroc
thank you for your work!
I had a minor surgery last month, sorry for the late reply.

That ofc is a breaking change.

I think it is good.
so please feel free to open the PR.
thank you for your work again!

Hi,
I have opened a draft pull request: https://github.com/gpgkd906/date_component/pull/4
Let me know if you need to see something else in there.
~thoroc

@thoroc
Thank you for update the documentation！
I thought about the BC again, maybe we could make just a little adjustment
・keep the original day
・rename the new day based on the calculation of the week to dayofweek, or daybyweek
This will eliminates the BC
What do you think?

That makes sense.

merge PR.


Missing/invalid X11 libraries dependencies for libcairo on GNU/Linux

The packaged 3rd party library libcairo has dependencies which are not included (or refer to an unmodified name).
In particular libXau and libXdmcp are not found unless they are installed by the OS. In most installations, this is not a problem, but a vanilla container image might not include any X11 libraries.

Can you install the missing libraries on your Linux distribution using the package manager (apt, ...)?
And can you point out the vanilla container image which is missing the libs?

Of course, installing would help, but I thought Python Wheels should include all dependencies other than libc.
Pick any basic docker image, e.g. debian:latest. Here is an example output:
/tmp/rdkit/lib/python3.9/site-packages/rdkit.libs# ldd libcairo-ddd0c49f.so.2.11514.0
	linux-vdso.so.1 (0x00007ffed23d5000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f515ab61000)
	libpixman-1-f094a0b6.so.0.34.0 => not found
	libfreetype-c0e61f0c.so.6.14.0 => not found
	libpng15-ce838cd1.so.15.13.0 => not found
	libxcb-shm-7a199f70.so.0.0.0 => not found
	libxcb-65da195c.so.1.1.0 => not found
	libxcb-render-637b984a.so.0.0.0 => not found
	libXrender.so.1 => not found
	libX11.so.6 => not found
	libXext.so.6 => not found
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f515ab42000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f515ab36000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f515a9f2000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f515a81d000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f515acac000)

Here libXrender, libX11 and libXext are not found but also not supplied.

You're right that all dependencies should be included. But the libs you mentioned are explicitly excluded (for some reason) from the platform wheels.
Auditwheel is taking care of creating the platform wheel. See these policy lines that explicitly exclude these libs.
 "lib_whitelist": [
         "libgcc_s.so.1",
         "libstdc++.so.6",
         "libm.so.6", "libdl.so.2", "librt.so.1",
         "libc.so.6", "libnsl.so.1", "libutil.so.1", "libpthread.so.0",
         "libX11.so.6", "libXext.so.6", "libXrender.so.1", "libICE.so.6",
         "libSM.so.6", "libGL.so.1", "libgobject-2.0.so.0",
         "libgthread-2.0.so.0", "libglib-2.0.so.0", "libresolv.so.2",
         "libexpat.so.1",
         "libz.so.1"
     ],

Looks like an explanation can be found in https://github.com/pypa/auditwheel/issues/78.
Does this answer your question?

Yes, I did not know that. And thank you for the explanation!


Es6

All the cool kids are using es6 apparently..

Sorry for closing the PR. I changed the default branch to be gh-pages and deleted master.

Good work, Nathan! ES6 can definitely clean up a lot.
Feel free to continue to review the comments and make changes if you like, otherwise it lgtm.
:+1:

💯


Realm: possible off-by-one error in compute_covering of sparse compact instances

compute_covering fails to compute a covering for the index space composed of the following 10 rectangles
<7,0,0>..<7,6,6>
<8,0,0>..<8,7,8>
<31,0,0>..<31,7,8>
<0,7,0>..<7,8,6>
<0,31,0>..<7,31,8>
<0,0,7>..<7,8,8>
<0,0,31>..<7,8,31>
<8,0,31>..<8,7,31>
<31,0,31>..<31,7,31>
<0,31,31>..<7,31,31>

with max_pieces=10 and max_overhead=10.
If max_pieces is increased to 11, the computed covering is composed of the original 10 rectangles.
inst_layout: Layout(bytes=29424, align=32, fields={123=0+0}, lists=[[<7,0,0>..<7,6,6>->affine(<24,24,168>-168), <8,0,0>..<8,7,8>->affine(<24,24,192>+984), <31,0,0>..<31,7,8>->affine(<24,24,192>+2160), <0,7,0>..<7,8,6>->affine(<24,192,384>+3288), <0,31,0>..<7,31,8>->affine(<24,192,192>+1368), <0,0,7>..<7,8,8>->affine(<24,192,1728>-3048), <0,0,31>..<7,8,31>->affine(<24,192,1728>-41064), <8,0,31>..<8,7,31>->affine(<24,24,192>+8088), <31,0,31>..<31,7,31>->affine(<24,24,192>+7728), <0,31,31>..<7,31,31>->affine(<24,192,192>+2712)]])

@mariodirenzo - which test case is this?

compute_covering fails to compute a covering for the index space composed of the following 10 rectangles
<7,0,0>..<7,6,6>
<8,0,0>..<8,7,8>
<31,0,0>..<31,7,8>
<0,7,0>..<7,8,6>
<0,31,0>..<7,31,8>
<0,0,7>..<7,8,8>
<0,0,31>..<7,8,31>
<8,0,31>..<8,7,31>
<31,0,31>..<31,7,31>
<0,31,31>..<7,31,31>

with max_pieces=10 and max_overhead=10. If max_pieces is increased to 11, the computed covering is composed of the original 10 rectangles.
inst_layout: Layout(bytes=29424, align=32, fields={123=0+0}, lists=[[<7,0,0>..<7,6,6>->affine(<24,24,168>-168), <8,0,0>..<8,7,8>->affine(<24,24,192>+984), <31,0,0>..<31,7,8>->affine(<24,24,192>+2160), <0,7,0>..<7,8,6>->affine(<24,192,384>+3288), <0,31,0>..<7,31,8>->affine(<24,192,192>+1368), <0,0,7>..<7,8,8>->affine(<24,192,1728>-3048), <0,0,31>..<7,8,31>->affine(<24,192,1728>-41064), <8,0,31>..<8,7,31>->affine(<24,24,192>+8088), <31,0,31>..<31,7,31>->affine(<24,24,192>+7728), <0,31,31>..<7,31,31>->affine(<24,192,192>+2712)]])

This is the expected behavior - the covering produced meets the 2 constraints i.e. # of pieces (10)  <= max_pieces (11) and there is no additional overhead.
The code path taken is https://gitlab.com/StanfordLegion/legion/-/blob/master/runtime/realm/deppart/sparsity_impl.cc?ref_type=heads#L654

That's not the expected behavior as the max_pieces=10 should still provide a layout without additional overhead for an instance composed of 10 rectangles, if the inequality that you mentioned # of pieces (10) <= max_pieces (11)  holds.

If max_pieces=10 and max_overhead=10 - it produces the same result as max_pieces=11 and max_overhead=10. Is this what you are not seeing or expecting?

Setting max_pieces=10 in https://gitlab.com/insieme1/htr/htr-solver/-/blob/Develop/src/prometeo_constraints.cc?ref_type=heads#L46, all solverTests passed on lassen. Additional logging added in realm verifies that max_pieces=10, num_pieces=10 does occur in some tests + layout without additional overhead is returned.


Update stable version in repo from 1.1.0 to 1.2.0

Think about update stable version to 1.2.0
Version: stable=1.1.0 (60 days old) => latest=1.2.0 (30 days old)
Installs: stable=92 (55.76%), latest=36 (21.82%), total=165
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.2.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.2.0 but the current stable version is already 1.2.0.
So this issue should be closed.
@mcm1957 for evidence


Is this possible to be implemented with hybrid model (R50+ViT) ?

https://github.com/rwightman/pytorch-image-models/blob/f8463b8fa9c0490db093b36acfce71fa2363b8c3/timm/models/vision_transformer.py#L169
I can't found HybridEmbed in your implementation.
Could you suggest how to implement RelProp for HybridEmbed?
I want to use this your visualization method with this ResNetV2 implementation.
https://github.com/jeonsworld/ViT-pytorch/blob/460a162767de1722a014ed2261463dbbc01196b6/models/modeling_resnet.py#L129

class GroupNorm(nn.GroupNorm, RelProp):
    pass

Can GroupNorm be implemented with this in layers_ours.py?
or
Require some modification for RelProb?
Thx advance!!

class GroupNorm(nn.GroupNorm, RelProp):
    pass

Can GroupNorm be implemented with this in layers_ours.py?
or
Require some modification for RelProb?
Thx advance!!

Hi @gwang-kim, thanks for your interest in our work!
In our paper, we only included pure Transformer networks, so I removed the hybrid model implementation, but I can recommend several resources for getting LRP implementation: link to innvestigate which is a great resource, this link is specifically to the LRP alpha beta formulation we use in our paper with alpha=0 (i.e. only considering positive contributions), it should really help in implementation.
In addition, there's the RAP repo which is for a paper co-authored by @shirgur, I believe you'll find implementations there for probably anything you need (notice to use relprop and not RAP_relprop, it's a different method).
I hope this helps, it should cover all you require to implement LRP, and of course, I highly encourage you to share your results once you're done, and create a PR if you wish to :)

Hi @gwang-kim, thanks for your interest in our work!
In our paper, we only included pure Transformer networks, so I removed the hybrid model implementation, but I can recommend several resources for getting LRP implementation: link to innvestigate which is a great resource, this link is specifically to the LRP alpha beta formulation we use in our paper with alpha=0 (i.e. only considering positive contributions), it should really help in implementation.
In addition, there's the RAP repo which is for a paper co-authored by @shirgur, I believe you'll find implementations there for probably anything you need (notice to use relprop and not RAP_relprop, it's a different method).
I hope this helps, it should cover all you require to implement LRP, and of course, I highly encourage you to share your results once you're done, and create a PR if you wish to :)

Great @hila-chefer , thanks for your kind answer and It will be so great if you implement it!
There are official hybrid checkpoints here
https://console.cloud.google.com/storage/browser/vit_models;tab=objects?prefix=&forceOnObjectsSortingFiltering=false
And below two repos implemented pytorch version of the hybrid ViT!
https://github.com/rwightman/pytorch-image-models/blob/f8463b8fa9c0490db093b36acfce71fa2363b8c3/timm/models/vision_transformer.py#L75
https://github.com/jeonsworld/ViT-pytorch/blob/460a162767de1722a014ed2261463dbbc01196b6/models/modeling.py#L142

Great @hila-chefer , thanks for your kind answer and It will be so great if you implement it!
There are official hybrid checkpoints here
https://console.cloud.google.com/storage/browser/vit_models;tab=objects?prefix=&forceOnObjectsSortingFiltering=false
And below two repos implemented pytorch version of the hybrid ViT!
https://github.com/rwightman/pytorch-image-models/blob/f8463b8fa9c0490db093b36acfce71fa2363b8c3/timm/models/vision_transformer.py#L75
https://github.com/jeonsworld/ViT-pytorch/blob/460a162767de1722a014ed2261463dbbc01196b6/models/modeling.py#L142

@gwang-kim sure, I'll leave this issue open for now, as I'm not sure that Google's published weights are compatible with this ViT implementation, but in the future, once they'll be added to Ross Wightman's repo I'll add an implementation here as well.

@gwang-kim sure, I'll leave this issue open for now, as I'm not sure that Google's published weights are compatible with this ViT implementation, but in the future, once they'll be added to Ross Wightman's repo I'll add an implementation here as well.

Great, thanks a lot!

Great, thanks a lot!

Hi, @hila-chefer . I wonder whether GradCam that is applied to last transformer layer is equal to  method=="last".

Hi, @hila-chefer . I wonder whether GradCam that is applied to last transformer layer is equal to  method=="last".

@gwang-kim I refer you to this issue regarding Grad-CAM, since it does not require LRP, I'm using the ViT model without the LRP propagation for it...

@gwang-kim I refer you to this issue regarding Grad-CAM, since it does not require LRP, I'm using the ViT model without the LRP propagation for it...

Thx @hila-chefer 😄

Thx @hila-chefer 😄


Download election dataset raw files

I added a new pipeline step to download the dataset and hard-coded the list of raw files. We could easily move the file list to a separate config file and roll this into the existing import step.

Any feedback on this?

Need additional research on the approach. The use of a static list of files is not helpful. If a dynamic list can not be generated without. elevated privileges then we will better document how to acquire the files.

Chris, I think we should merge this PR now to make it easier for developers to get started with the project. We can always improve it later.
We need to think about making it easier for developers to get started with the project, and reliably run the pipeline. The Jupyter notebooks are a good way to prototype the pipeline, but they're long, complex, poorly documented, and prone to mistakes. If people are going to trust the results, we've got to make it more repeatable and reliable.


review use of kind kwarg

FIX #61

@mrakitin What else needs to be done?
Would you agree that the real positioners should be kind="normal" while the pseudo positioners should be kind="hinted"? (per comment in PR #52)

@mrakitin Thanks!


complete next-auth configuration and remove email/password accounts

This PR:

Removes the email/password configuration
Adds third-party auth providers (GitHub, Google and Reddit)
Updates .env.example and cleans up comment strings
Adds connect.ts to get the MongoDB collection
Pretties the files with npx prettier --write ./

Nice work!


Add achievements section in portfolio

As the name suggests, awards and achievements in portfolio is a separate section where user list relevant honors, achievements, awards, and acknowledgements user earned for going beyond average. It can include scholarships, competitions, work-related awards, or even promotions to leadership positions in user's job.
I am ready to make the UI for it. Can you assign it to me?

@Prachirsh sure, please share the screenshot of the section before opening the PR

it will look like this

Was not able to create new fork so I updated my old fork which was earlier used for contact form can you check once

okayy


Support Complex type in BeamSQL

We want have a smooth experience of complex type in BeamSQL.

For example, BeamSQL could support nested row in arbitrary levels (Row<Row<Row<...>>>) in both read and write from/to arbitrary sources.
Imported from Jira BEAM-5120. Original Jira may contain additional context.
Reported by: amaliujia.

The following subtask(s) are associated with this issue: #19010, #19011


vimPlugins.vim-go: use the correct motion derivation for the dependency

Motivation for this change
vimPlugins.vim-go was using the wrong motion package, see https://github.com/NixOS/nixpkgs/pull/49669#commitcomment-31301419
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

cc @Mic92

@GrahamcOfBorg build go-motion vimPlugins.vim-go

Success on aarch64-linux (full log)
Attempted: go-motion
The following builds were skipped because they don't evaluate on aarch64-linux: vimPlugins.vim-go
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin
shrinking /nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin/bin/motion
cannot find section .dynamic
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin/bin
patching script interpreter paths in /nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin
checking for references to /build in /nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin...
cannot find section .dynamic
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
/nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin

Success on x86_64-linux (full log)
Attempted: go-motion, vimPlugins.vim-go
Partial log (click to expand)
patching script interpreter paths in /nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/bench-syntax: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/lint: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/install-vim: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/run-vim: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/test: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/docker-test: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23...
/nix/store/2f0jpcsdk5w53c0riipf2k63lbb542fg-motion-unstable-2018-04-09-bin
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23

Success on aarch64-linux (full log)
Attempted: go-motion
The following builds were skipped because they don't evaluate on aarch64-linux: vimPlugins.vim-go
Partial log (click to expand)
a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

/nix/store/ry1pi9qjnxilfdnrlqag4prdyzh5q1q2-motion-unstable-2018-04-09-bin

Success on x86_64-linux (full log)
Attempted: go-motion, vimPlugins.vim-go
Partial log (click to expand)
patching script interpreter paths in /nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/install-vim: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/run-vim: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/test: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/bench-syntax: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/lint: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23/share/vim-plugins/vim-go/scripts/docker-test: interpreter directive changed from "/bin/sh" to "/nix/store/r47p5pzx52m3n34vdgqpk5rvqgm0m24m-bash-4.4-p23/bin/sh"
checking for references to /build in /nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23...
/nix/store/2f0jpcsdk5w53c0riipf2k63lbb542fg-motion-unstable-2018-04-09-bin
/nix/store/mnr063f2dgp3sm1n0bj86gr4210wi12q-vimplugin-vim-go-2018-10-23


dep panic on ctrl+c (new one)

dep ensure
^CSignal received: waiting for 1 ops to complete...
panic: canary - shouldn't be possible this SourceMgr has been released, its methods can no longer be called

goroutine 1 [running]:
github.com/golang/dep/vendor/github.com/sdboyer/gps.(*solver).unselectLast(0xc42023e7e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
	/root/go/src/github.com/golang/dep/vendor/github.com/sdboyer/gps/solver.go:1189 +0x863
github.com/golang/dep/vendor/github.com/sdboyer/gps.(*solver).backtrack(0xc42023e7e0, 0xc420183200)
	/root/go/src/github.com/golang/dep/vendor/github.com/sdboyer/gps/solver.go:942 +0x166
github.com/golang/dep/vendor/github.com/sdboyer/gps.(*solver).solve(0xc42023e7e0, 0x0, 0x0, 0x20)
	/root/go/src/github.com/golang/dep/vendor/github.com/sdboyer/gps/solver.go:409 +0x787
github.com/golang/dep/vendor/github.com/sdboyer/gps.(*solver).Solve(0xc42023e7e0, 0x2d, 0xa67140, 0xab51f8, 0xc420016011)
	/root/go/src/github.com/golang/dep/vendor/github.com/sdboyer/gps/solver.go:355 +0xab
main.(*ensureCommand).Run(0xc42013d560, 0xc420142e10, 0xc42000c160, 0x0, 0x0, 0x0, 0x0)
	/root/go/src/github.com/golang/dep/cmd/dep/ensure.go:145 +0x358
main.main()
	/root/go/src/github.com/golang/dep/cmd/dep/main.go:125 +0x6df
Makefile:21: recipe for target 'dep' failed
make: *** [dep] Error 2

This happens if I hit 'ctrl + c' almost immediately after starting 'dep ensure'.
I've tried to update to current master, but no luck.

Hmm - I changed a lot in that update with respect to lifecycle management within subcomponents of the SourceManager, but punted a bit on the overall lifecycle management (e.g., signals) with the expectation that we'd be coming to it in sdboyer/gps#159. Guess it needs some love sooner than that 😄
I'll have a look soon - thanks for posting the issue!

this is no longer an issue - or at least, not the panic. we still have error handling to deal with, but the primary focal point of this ticket is addressed.


FIX Fixes codecov upload

This PR fixes codecov upload.
Type

[x] Housekeeping

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
When looking at the codecov job on the ci, it fails to detect the xml file. This PR explicitly sets the xml file for the codocov GitHub Action to pick up.

Looking over the logs for codecov, it looks like the coverage is properly uploaded now!


Print Top 10 list using each

Using this as an example
http://borismoore.github.com/jsviews/demos/jQueryConfDemosOct2011/08_each-tag.html
What is the best method to print just the first x Languages.
Brad.

Well you can do {{#each Languages.slice(start,end)}}, or specifically: {{#each Languages.slice(0,x)}}`
You could also create a custom tag which does {{#myeach Languages from=0 to=x}}. Something like that may end up being added to the built-in each tag.


How to test directives? - angular2

Hi all,
How should I test directives? in angular2

In a similar way we test components.


Change inheritance on the UML Editor is not reflecting in the code

Done, but might need some more testing


Docker Micro Benchmark: Add dockerd and containerd support.

@timstclair Can you help me review this? I remember you made similar change locally before.
I used this to get the result https://github.com/kubernetes/kubernetes/issues/28698#issuecomment-244514829, but forgot to submit the PR at that time.

/lgtm


Avoid some unnecessary copying in scipy.linalg.blas and scipy.linalg.lapack

I am a Python novice, but I have some experience with BLAS / LAPACK via Julia.
I believe I have uncovered a possible efficiency improvement that could be applied to scipy.linalg.blas, but possibly it could also affect numpy and any other code that makes similar use of Python to BLAS/LAPACK interfaces.
I believe that some (or all?) of the interface routines in scipy.linalg.blas (and maybe also scipy.linalg.lapack) are too strict when inspecting matrices for compatibility with BLAS.  Although BLAS requires matrices to have fortran alignment (contiguous columns), it does not require the stride along the elements of a row to be equal to the number of rows.  In typical BLAS/LAPACK calls, the stride along rows is called the leading dimension and it must be >= number of rows. It seems to me that scipy.linalg.blas effectively checks for equality here (leading dimension  = number of rows) and if this is not satisfisfied, the matrix is unnecessarily copied to a newly allocated matrix where that condition holds.
For numpy arrays, does the scipy.linalg.blas code check the F_CONTIGUOUS flag for BLAS compatibility? As I show below, this flag seems to be too strict.
Below is an experimental example where I send numpy arrays into blas.dtrmm. I did not inspect the fortran source code, but I believe my experiment demonstrates this issue, at least for the case of dtrmm.
The experiment:

As control, creates a canonical, fortran-style matrix and shows that it can be updated inplace via dtrmm (multiplication by a triangular matrix).
Creates a sliced array view, that in my opinion should still be a valid BLAS argument, but which is then apparently copied, instead of being processed inplace.

(Note: The array strides produced by the code below are in terms of bytes. For the float64 elements, 8 bytes  = 1 float64.)
My code is:
import numpy, scipy
from numpy.random import randn
import scipy.linalg.blas as blas

print("numpy version:",numpy.__version__)
print("scipy version:",scipy.__version__)
print()

m,n = 3,4

A = randn(m,m).T
if A.strides[0]==8:
    print("A is blas-fiendly, with fortran alignment:")
    print("A.strides = ", A.strides)
    print("Indeed A.flags also show F_CONTIGUOUS: ")
    print(A.flags)
    print()

D = randn(n,m).T
print("The same applies to D:")
print("D.flags.f_contiguous = ", D.flags.f_contiguous,"\n")

S = randn(m,2*n).T[0:n,:]
if S.strides[0]==8:
    print("Although the sliced S is still blas-fiendly, with fortran alignment:")
    print("S.strides = ", S.strides)
if not S.flags.f_contiguous:
    print("... its flags do **not** show F_CONTIGUOUS: ")
    print(S.flags)
    print()

Y = blas.dtrmm(1.0, A, D,
               side = 0,
               lower = True,
               trans_a = False,
               diag = False,
               overwrite_b = True)
print("in trmm D was copied = ",not Y is D)

Y = blas.dtrmm(1.0, A, S,
               side = 0,
               lower = True,
               trans_a = False,
               diag = False,
               overwrite_b = True)
print("in trmm S was copied = ",not S is D)

and the output is:
numpy version: 1.18.1
scipy version: 1.4.1

A is blas-fiendly, with fortran alignment:
A.strides =  (8, 24)
Indeed A.flags also show F_CONTIGUOUS:
  C_CONTIGUOUS : False
  F_CONTIGUOUS : True
 [some lines omitted]

The same applies to D:
D.flags.f_contiguous =  True

Although the sliced S is still blas-fiendly, with fortran alignment:
S.strides =  (8, 64)
its flags do **not** show F_CONTIGUOUS:
  C_CONTIGUOUS : False
  F_CONTIGUOUS : False
 [some lines omitted]

in trmm D was copied =  False
in trmm S was copied =  True

Closing as duplicate (or closely related to) gh-9682.


Add reporting to profiles.

On Meower, you can report on profiles directly:

The modal itself is straightforward:

This'd be nice so inappropriate usernames can be reported through there.
Though ig fair this doesnt exist in roarer (atleast yet?) since you can just report through posts anyways but
if its unrelated to any of their posts it just won't make much sense

Done in https://github.com/mybearworld/roarer/commit/b4872baceae4c87ceb195470da3a0673c05ddf52

Done in b4872ba

tysm