Add educational Pluto example

This pull request is intended to resolve issue #242

Change name of folder containing the example to 7.educational_pluto_notebook

educational_pluto_notebook

Addressed in https://github.com/cncastillo/KomaMRI.jl/pull/253/commits/ba7b836a443d33d4759e2a7f727cfeac37e281b3

The solution looks like this:

Addressed in https://github.com/cncastillo/KomaMRI.jl/pull/253/commits/ba7b836a443d33d4759e2a7f727cfeac37e281b3

Change name of folder containing the example to 7.educational_pluto_notebook

Addressed in https://github.com/cncastillo/KomaMRI.jl/pull/253/commits/ba7b836a443d33d4759e2a7f727cfeac37e281b3


[Reflection] Bring back an "array case" handling in CustomAttributeTypedArgument ctor.

Relates to https://github.com/mono/mono/pull/10450
Mono had it here.
CoreRT has it here
Mono unit test for an "array case" fails without this part.

Thanks for review!


custom model predictor is not working

/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I am going to run custom model predictor (docs)
When I run apply custom yaml, It occurs error.
kubectl apply -f custom.yaml

error: resource mapping not found for name: "custom-model" namespace: "" from "custom.yaml": no matches for kind "InferenceService" in version "serving.kserve.io/v1beta1"
ensure CRDs are installed first

So I searched this docs
In this docs, there is no predictor > container. so I changed like this
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  name: custom-model
spec:
  predictor:
    PodSpec:
      containers:
        - name: kserve-container
          image: name/custom-model:v1

but It occur same error.
what is wrong? and what documents is right?
What did you expect to happen:
What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version:
Knative Version:
KServe Version: 0.10
Kubeflow version:
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube/Kind version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

@ssilb4 It might be a kserve installation problem. Do you encounter any errors when installing kserve? You can try reinstalling kserve

I succeeded first inference
but is it installation problem?

Your inference service spec is wrong, podSpec should not be there.
https://kserve.github.io/website/0.10/modelserving/v1beta1/custom/custom_model/#deploy-the-rest-custom-serving-runtime-on-kserve


Can't access api with basic auth (user kube has no permission for anything)

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Environment:

Cloud provider or hardware configuration:
Scaleway (bare hardware)
OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
Linux 4.4.92-mainline-rev1 x86_64
NAME="Ubuntu"
VERSION="16.04.1 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.1 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Version of Ansible (ansible --version):
ansible <IP_ADDRESS>
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/etc/ansible/module']
ansible python module location = /usr/lib/python2.7/dist-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609]

Kubespray version (commit) (git rev-parse --short HEAD):
92d0380
Network plugin used:
Default
Copy of your inventory file:
Command used to invoke ansible:
ansible-playbook -b kubespray/cluster.yml -u root -i /etc/ansible/inventory/hosts
Output of ansible run:

Anything else do we need to know:

Cluster seems healthy, I can launch deployments etc. from the console of one of the three master servers. When trying to launch a dashboard using kubectl create -f https://raw.githubusercontent.com/kubernetes/kops/master/addons/kubernetes-dashboard/v1.6.3.yaml
everything is created normally. When trying to access it remotely using /ui I was able to login but retrieved an error. Thats when I noticed this user doesn't seem to be able to do anything?
Trying to reach /api/v1/nodes
returns

  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {

  },
  "status": "Failure",
  "message": "nodes is forbidden: User \"kube\" cannot list nodes at the cluster scope",
  "reason": "Forbidden",
  "details": {
    "kind": "nodes"
  },
  "code": 403
}

???
root@Master03:~# cat /etc/kubernetes/users/known_users.csv
changeme,kube,admin

Maybe I am missing something? It's been a while since I stood something up with kubespray but in the past using defaults was always a sure thing.

Possibly being affected by this https://github.com/kubernetes/kubeadm/issues/484

@mattymo

@shadycuz
I deployed an environment by hand with the following settings:
kubeadm_enabled: false
kube_basic_auth: true

Then I tried to list nodes with my generated credentials:
root@k8s-mattymo-test-1:~# curl -s https://kube:qppUCGxPJoBlCwE@localhost:6443/api/v1/nodes | head -5
{
  "kind": "NodeList",
  "apiVersion": "v1",
  "metadata": {
    "selfLink": "/api/v1/nodes",

The UI works as well.
If you want to access the UI but not enable kube_basic_auth (or can't because you are using kubeadm mode), you can access the UI with kubectl proxy https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#using-kubectl-proxy . Keep in mind you want to use the following options on your host to allow this:
kubectl_localhost: true
kubeconfig_localhost: true

@mattymo Thanks for this. Like I said I used all defaults and that used to give me what I wanted. I guess things have changed and I will need to look through those var's files for now on. I also need to look up kubeadm as I don't know what that is. I will recreate the cluster soon with those settings.
Thanks.

We disabled basic auth because it's a much weaker attack vector to an account with admin privileges than a proper x509 cert.

@mattymo I need to look into it more. I have an ELB pointed at my Masters on port 6883? Or whichever port API is listening and that is how I always reached the cluster and used basic auth to hit the dashboard. If I can still reach the UI and run commands like kubectl create while using that load balancer then I am fine with use kubeadm and certs. I just didn't think I could log into the gui via a cert? So I need to look into it more.

@mattymo  Ahh, Look at what user floreks wrote here https://github.com/kubernetes/kubernetes/issues/31665
I will try to install that 509 cert in my browser and see if I can reach api and dashboard throug my Nginx reverse proxy. Mainly because I don't want to use a VPN to hit the cluster.

@shadycuz Enabling kube_basic_auth is easier than authenticating with a cert in a browser, in my experience.

@mattymo I will just do that, its a personal cluster for fun and learning. I will set a really long random password and call it a day =). Thanks for adding that kubeconfig role to set it up for end user, Super Nice!

@mattymo maybe I should start a new issue but I spun up a new cluster this morning I used
kubeadm_enabled: false
kube_basic_auth: true
kubectl_localhost: true
kubeconfig_localhost: true

unfortuantly I lost the ansible output, but all steps were changed or okay untill it was time to wait for the api servers to come up. 20 tries I think and all 3 failed. Was checking <IP_ADDRESS>:8080/health or something like that.
I checked the host docker and something isnt right...
root@Master01:/# service docker status
● docker.service - Docker Application Container Engine
   Loaded: loaded (/etc/systemd/system/docker.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
           └─docker-dns.conf, docker-options.conf
   Active: active (running) since Thu 2017-10-19 11:58:31 UTC; 36min ago
     Docs: http://docs.docker.com
 Main PID: 9240 (dockerd)
    Tasks: 35
   Memory: 1.0G
      CPU: 3min 38.876s
   CGroup: /system.slice/docker.service
           ├─ 9240 dockerd --insecure-registry=<IP_ADDRESS>/18 --graph=/var/lib/docker --log-opt max-size=50m --log-opt max-file=5 --iptables=false --dns <IP_ADDRESS> --dns <IP_ADDRESS> --dns-search default.svc.cluster.local
           ├─ 9252 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --shim docker-containerd-           └─15654 docker-containerd-shim c0ae8f0a2e9b6e7484463b977586047a4539f7093bde041f90cd89e2b158e52f /var/run/docker/libcontainerd/c0ae8f0a2e9b6e7484463b977586047a4539f7093bde041f90cd89e2b158e52f docker-runc

Oct 19 12:05:13 Master01 docker[9240]: time="2017-10-19T12:05:13.935797440Z" level=error msg="Handler for GET /v1.26/containers/498ffffcfd05/json returned error: No such container: 498ffffcfd05"
Oct 19 12:05:13 Master01 docker[9240]: time="2017-10-19T12:05:13.941314558Z" level=error msg="Handler for GET /v1.26/containers/ff1e9c00bb46/json returned error: No such container: ff1e9c00bb46"
Oct 19 12:05:13 Master01 docker[9240]: time="2017-10-19T12:05:13.945310473Z" level=error msg="Handler for GET /v1.26/containers/00bc1e841a8f/json returned error: No such container: 00bc1e841a8f"
Oct 19 12:05:13 Master01 docker[9240]: time="2017-10-19T12:05:13.949787846Z" level=error msg="Handler for GET /v1.26/containers/99e59f495ffa/json returned error: No such container: 99e59f495ffa"
Oct 19 12:09:45 Master01 docker[9240]: time="2017-10-19T12:09:45.526205467Z" level=error msg="Handler for DELETE /v1.26/containers/etcdctl-binarycopy returned error: No such container: etcdctl-binarycopy"
Oct 19 12:10:37 Master01 docker[9240]: time="2017-10-19T12:10:37.676144794Z" level=error msg="Handler for DELETE /v1.26/containers/etcd1 returned error: No such container: etcd1"
Oct 19 12:13:36 Master01 docker[9240]: time="2017-10-19T12:13:36.054842758Z" level=error msg="Handler for DELETE /v1.26/containers/etcdctl-binarycopy returned error: No such container: etcdctl-binarycopy"
Oct 19 12:19:46 Master01 docker[9240]: time="2017-10-19T12:19:46.363721789Z" level=error msg="Handler for GET /v1.26/containers/kubelet/archive returned error: No such container: kubelet"
Oct 19 12:19:52 Master01 docker[9240]: time="2017-10-19T12:19:52.395258535Z" level=error msg="Handler for POST /v1.26/containers/kubelet/stop returned error: No such container: kubelet"
Oct 19 12:20:07 Master01 docker[9240]: time="2017-10-19T12:20:07.494390285Z" level=error msg="Handler for POST /v1.26/containers/create returned error: No such image: quay.io/coreos/hyperkube:v1.6.7_coreos.0"

Why are you deploying kubernetes version 1.6.7 instead of 1.8.0?

@mattymo Idk?
ansible@rundeck:~/kubespray$ git pull
Already up-to-date.
ansible@rundeck:~/kubespray$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        modified:   roles/kubernetes/master/defaults/main.yml
        modified:   roles/kubespray-defaults/defaults/main.yaml

no changes added to commit (use "git add" and/or "git commit -a")
ansible@rundeck:~/kubespray$ grep version roles/kubespray-defaults/defaults/main.yaml
## Change this to use another Kubernetes version, e.g. a current beta release
kube_version: v1.6.7
## When OpenStack is used, Cinder version can be explicitly specified if autodetection fails (https://github.com/kubernetes/kubernetes/issues/50461)
# openstack_blockstorage_version: "v1/v2/auto (default)"

I guess I thought the defaults with out changing much would give me a good cluster out of the box, I know yesterday when I launched a cluster with all defaults it came up okay except basic auth wasn't enabled.

You shouldn't remove the group vars that are included. We can't guarantee that the role defaults are set correctly because it's not covered by CI.
I have a fix on review for the kube version issue: https://github.com/kubernetes-incubator/kubespray/pull/1845

@mattymo what do you mean remove groups vars? I didn't? You mean I need to put my inventory in kubespray inventory and run kubespray from inside the kubespray directory?

and then I will submit my vars via CLI so they take precedence over anything else cause im not really sure where should I change what

@shadycuz You can make your own json or yaml file with vars and then specify it on the CLI like -e @my_vars.yml

@mattymo The ansible config file inside of kubespray does not specify a path to an inventory, so dropping an inventory into kubespray/inventory/hosts and then running ansible-playbook -b cluster.yml fails. I had to run mine with ansible-playbook -e my_vars.yml -i inventory/hosts -u root -b cluster.yml but I have no clue if the group variables got called into "action".

Okay groupsvars should have worked?

In addition to storing variables directly in the inventory file, host and group variables can be stored in individual files relative to the inventory file (not directory, it is always the file).

@mattymo well this aint good, I don't know what has happened to kubespray but at one point in time it actually worked with defaults out of the box with my exact setup.
root@Master01:~# kubectl get pods -n kube-system
NAME                                    READY     STATUS              RESTARTS   AGE
calico-node-456fb                       0/1       ContainerCreating   0          33m
calico-node-9x89z                       0/1       ContainerCreating   0          33m
calico-node-g5w8b                       0/1       ContainerCreating   0          33m
calico-node-h2q8m                       0/1       ContainerCreating   0          33m
calico-node-mcgvr                       0/1       ContainerCreating   0          33m
calico-node-xkss4                       0/1       ContainerCreating   0          33m
kube-apiserver-master01                 1/1       Running             0          36m
kube-apiserver-master02                 1/1       Running             0          36m
kube-apiserver-master03                 1/1       Running             0          36m
kube-controller-manager-master01        1/1       Running             0          36m
kube-controller-manager-master02        1/1       Running             0          36m
kube-controller-manager-master03        1/1       Running             0          36m
kube-dns-596d7c8f8-whdzz                0/3       ContainerCreating   0          30m
kube-proxy-compute01                    1/1       Running             0          37m
kube-proxy-compute02                    1/1       Running             0          37m
kube-proxy-compute03                    1/1       Running             0          36m
kube-proxy-master01                     1/1       Running             0          37m
kube-proxy-master02                     1/1       Running             0          37m
kube-proxy-master03                     1/1       Running             0          37m
kube-scheduler-master01                 1/1       Running             0          37m
kube-scheduler-master02                 1/1       Running             0          37m
kube-scheduler-master03                 1/1       Running             0          37m
kubedns-autoscaler-86c47697df-rsjr7     0/1       ContainerCreating   0          30m
kubernetes-dashboard-7fd45476f8-9c7pz   0/1       ContainerCreating   0          30m
nginx-proxy-compute01                   1/1       Running             0          36m
nginx-proxy-compute02                   1/1       Running             0          37m
nginx-proxy-compute03                   1/1       Running             0          37m

@mattymo from the dashboard pod
Tolerations:     node-role.kubernetes.io/master:NoSchedule
Events:
  Type     Reason       Age                From                Message
  ----     ------       ----               ----                -------
  Normal   Scheduled    32m                default-scheduler   Successfully assigned kubernetes-dashboard-7fd45476f8-9c7pz to compute02
  Warning  FailedSync   16m (x7 over 30m)  kubelet, compute02  Error syncing pod
  Warning  FailedMount  12m (x9 over 30m)  kubelet, compute02  Unable to mount volumes for pod "kubernetes-dashboard-7fd45476f8-9c7pz_kube-system(2496f520-b4e4-11e7-bf2a-de19444b4004)": timeout expired waiting for volumes to attach/mount for pod "kube-system"/"kubernetes-dashboard-7fd45476f8-9c7pz". list of unattached/unmounted volumes=[kubernetes-dashboard-token-slvz2]
  Warning  FailedMount  1m (x23 over 32m)  kubelet, compute02  MountVolume.SetUp failed for volume "kubernetes-dashboard-token-slvz2" : secrets "kubernetes-dashboard-token-slvz2" is forbidden: User "system:node:Compute02" cannot get secrets in the namespace "kube-system": no path found to object

Tried again with a new cluster
TASK [network_plugin/calico : Calico | wait for etcd] **********************************************************************************************
Thursday 19 October 2017  17:53:35 -0400 (0:00:02.749)       0:26:59.961 ******
FAILED - RETRYING: Calico | wait for etcd (10 retries left).
FAILED - RETRYING: Calico | wait for etcd (9 retries left).
FAILED - RETRYING: Calico | wait for etcd (8 retries left).
FAILED - RETRYING: Calico | wait for etcd (7 retries left).
FAILED - RETRYING: Calico | wait for etcd (6 retries left).
FAILED - RETRYING: Calico | wait for etcd (5 retries left).
FAILED - RETRYING: Calico | wait for etcd (4 retries left).
FAILED - RETRYING: Calico | wait for etcd (3 retries left).
FAILED - RETRYING: Calico | wait for etcd (2 retries left).
FAILED - RETRYING: Calico | wait for etcd (1 retries left).
fatal: [Compute02 -> None]: FAILED! => {"attempts": 10, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error ('_ssl.c:574: The handshake operation timed out',)>", "redirected": false, "status": -1, "url": "https://localhost:2379/health"}

@shadycuz did you ever figure out a solution to this error you were getting?
fatal: [Compute02 -> None]: FAILED! => {"attempts": 10, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error ('_ssl.c:574: The handshake operation timed out',)>", "redirected": false, "status": -1, "url": "https://localhost:2379/health"}
I get the same thing sometimes for the "wait for etcd" task and every single time on the "Master | wait for the apiserver to be running" handler

@rhino5oh I did get past this, but I don't remember how. If you are using the latest code from here it might be something different from my issue. I would ask on the kubernetes slack. Kubespay has a room and I always get good help from people. You might want to SSH into your etcd nodes and check the logs and see what it says. Also make a new issue =)


PRIMAVERA Tropical Cyclones

It is a wrapper around a fortran executable. Diagnostic is mostly preparing the inputs for the executable and reading the outputs (far from easy)
It may be done in two sripts: one python to run the tracker and one R for the evaluation of the outputs

@ESMValGroup/esmvaltool-coreteam, how do we feel about this? This is a python wrapper that calls an unpackaged Fortran program. While the basic program is available for download here, according to this issue/associated PR actually a modified version of the program was used. Furthermore, I could not find licensing information about the program or its dependencies (that are distributed alongside the program).
Here we would be adding a Python wrapper around a Fortran program that is not generally available. While I think it is completely fine to use ESMValTool in this way locally, I am not sure we want to integrate this wrapper into the main tool. What do you think?

From our contribution guidelines:

If you have existing code in a compiled language like C, C++, or Fortran that you want to re-use, the recommended way to proceed is to add Python bindings and publish the package on PyPI so it can be installed as a Python dependency. You can then call the functions it provides using a Python diagnostic.

@sloosvel, @jvegasbsc, pending clarification of licensing terms and availability, given the fact that this diagnostic is not usable without the tracker, I don't think it should be included in ESMValTool as of now.

Well it formats the input so it can be read by the tracker (which is a modified version), even if the tracker is not executed. I would not call cmorizers not usable, this is the same concept.
I don't mind if it does not make it to this release, but I would really appreciate it if at some point this can be included. Because otherwise it will have been a big effort for nothing. It's work from years ago, before all those contributing guidelines were in place and the paper makes a point in mentioning and citing that what was used to format and execute the tracker is the esmvaltool.

I understand that this is frustrating, but if it's not possible to run an actual diagnostic with this, this seems to tip the balance against inclusion in my book. Perhaps it would be possible to release the tracker as open source? If you can sort out the legal situation regarding licenses, I might be able to help put up a conda package that we can depend on. This way, we would really open up this very interesting feature for the community.

I would not call cmorizers not usable, this is the same concept.

This case is very different from CMORizers, because their results are intended to used by the ESMValTool, not by a third party tool.

It's work from years ago, before all those contributing guidelines were in place

Contribution guidelines have been available for a long time, though I admit they were a bit scarce in the beginning. This is a learning experience for all of us and writing this kind of guidelines is a lot of work. The guideline I quoted above was introduced in #786, arguably after this issue was opened (without any description), but before pull request #1369 was opened.
Regardless of what was written down when, the idea behind the way we manage ESMValTool dependencies is and has always been that we try to make things easy for our users by ensuring that if you manage to install the ESMValtool, all diagnostics work and do not require additional dependencies.
It would be really great if you could work together with @zklaus and the authors of the Cyclone Tracking software to make their software more easily accessible.

I'll bump this to 2.5.0, but we should have a conversation on the way forward.


Another De-claw description

islandora playbook's repo description includes a "CLAW" 🐯
Only an owner can change this.

https://github.com/Islandora-Devops/islandora-playbook

Known issue (that's my comment in parentheses), but I just love the pun so much. I will bow to the will of the Islandora 8 collective if y'all deem this needs to go 🦞

@manez I got a second one for you. The official documentation on metadata links to  CLAW MIG MODS-RDF Simplified Mapping spreadsheet. The title still refers to CLAW.


"sticky" filters

Endpoints allows a server to specify both default includes and default filters for any endpoint.
Our current implementation of filters follows the JSON-API specification's semantics around include. That is, a server can specify a list of default included relations at a given endpoint, but if the user explicitly specifies any in their request, it should completely override the server-defaults. As mentioned above, we are doing the same for filters. However, we are not bound by the specification to do so.
There are times when a server might wish to specify a filter that the user cannot opt out of (such as suppressing records which have been flagged as deleted). While one could argue this should be implemented at the database layer, the general question remains: servers should be able to specify filters that stay by default, and filters which cannot be altered. What should our API for this be?
The current API is this:
controller.read({
  filter: {
    deleted: true
  }
});

Here are three proposed APIs:
controller.read({
  filter: {
    deleted: {
      value: true,
      sticky: true,
      locked: true
    }
  }
});

controller.read({
  filter: {
    deleted: true
  },
  filterSettings: {
    deleted: {
      sticky: true,
      locked: true
    }
  }
});

controller.read({
  filter: {
    deleted: true
  },
  stickyFilters: ['deleted'],
  lockedFilters: ['deleted']
});

I like the first best but it could be a little weird if we ever had a situation where the value of a filter was itself an object, then you'd end up with:
controller.read({
  filter: {
    deleted: {
      value: {
        key: 'pair'
      }
    }
  }
});

I'm struggling to think of a scenario where that would happen, and even if it would, perhaps it is sufficiently rare that this ugly configuration is acceptable?
Thoughts @bobholt?

It's also just occurred to me that some of this might belong at the model layer (otherwise you'd have to repeatedly set your sticky/locked deleted filter at every controller which could include the relevant resources). Even so, an implementor probably needs the flexibility to control it on a per-endpoint basis.

Yeah, from a per-endpoint standpoint, maybe I want to make an admin endpoint that can see the deleted records, so it's useful to do it in the model and use the controller for overrides.
I like the first one, too, for its simplicity. The object value is ugly, but I think it will be anyway. Here's another option to throw in the mix, though I still like number 1.
controller.read({
  filter: {
    employee: 12
  },
  stickyFilter: {
    is_active: true
  },
  lockedFilters: {
    deleted: true
  }
});

Granted, I'm not grokking the difference between sticky and locked. Would a filter need to be specified as both?

locked means if the server default is, say true for some value, it's invalid to try to set it to anything else. The endpoint would either throw an error for that request or silently ignore the value.


Error When Starting Docker Compose Following Documentation

Describe the bug
Following the documentation https://github.com/movementlabsxyz/movement/tree/main/docs/movement-node/run/manual to create and start the Docker Compose results in an error.
To Reproduce
Steps to reproduce the behavior:

Follow the instructions in the documentation to set up the Docker environment.
Run the command:
docker compose –env-file .env -f docker/compose/suzuka-full-node/docker-compose.yml -f docker/compose/suzuka-full-node/docker-compose.setup.yml -f docker/compose/suzuka-full-node/docker-compose.local.yml up
Observe the error in the logs.

Expected behavior
All containers should start successfully without any errors.
Additional context
Startup command and log output:
Startup command:
docker compose –env-file .env -f docker/compose/suzuka-full-node/docker-compose.yml -f docker/compose/suzuka-full-node/docker-compose.setup.yml -f docker/compose/suzuka-full-node/docker-compose.local.yml up
Log output:
docker compose --env-file .env -f docker/compose/suzuka-full-node/docker-compose.yml -f docker/compose/suzuka-full-node/docker-compose.setup.yml -f docker/compose/suzuka-full-node/docker-compose.local.yml up
[+] Running 10/7
 ✔ Network suzuka-full-node_default            Created                                                                                0.0s
 ✔ Container setup                             Created                                                                                0.0s
 ✔ Container m1-da-light-node-celestia-appd    Created                                                                                0.0s
 ✔ Container m1-da-light-node-celestia-bridge  Created                                                                                0.0s
 ✔ Container celestia-light-node               Created                                                                                0.0s
 ✔ Container celestia-light-node-synced        Created                                                                                0.0s
 ✔ Container m1-da-light-node                  Created                                                                                0.0s
 ✔ Container suzuka-full-node                  Created                                                                                0.0s
 ✔ Container wait-for-suzuka-full-node         Created                                                                                0.0s
 ✔ Container suzuka-faucet-service             Created                                                                                0.0s
Attaching to celestia-light-node, celestia-light-node-synced, m1-da-light-node, m1-da-light-node-celestia-appd, m1-da-light-node-celestia-bridge, setup, suzuka-faucet-service, suzuka-full-node, wait-for-suzuka-full-node
setup                             | 2024-07-15T06:16:47.522650Z  INFO m1_da_light_node_setup::local: Setting up Celestia for M1 DA Light Node.
setup                             | 2024-07-15T06:16:47.522661Z  INFO m1_da_light_node_setup::local: Setting up Celestia.
setup                             | 2024-07-15T06:16:47.522667Z  INFO m1_da_light_node_setup::local: Initializing MemSeq Config.
setup                             | 2024-07-15T06:16:47.522670Z  INFO m1_da_light_node_setup::local: Creating Celestia App Path: /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | 2024-07-15T06:16:47.522795Z  INFO m1_da_light_node_setup::local: Creating Celestia Node Path: /.movement/celestia/7a241f6d45e434242012/.celestia-node
setup                             | 2024-07-15T06:16:47.522822Z  INFO m1_da_light_node_setup::local: Creating MemSeq Database Path: /.movement/memseq/7a241f6d45e434242012/.memseq
setup                             | 2024-07-15T06:16:47.522863Z  INFO m1_da_light_node_setup::local: Setup config for Memseq and Celestia: Config { appd: Config { celestia_rpc_listen_hostname: "<IP_ADDRESS>", celestia_rpc_listen_port: 26657, celestia_websocket_connection_hostname: "m1-da-light-node-celestia-bridge", celestia_websocket_connection_port: 26658, celestia_auth_token: None, celestia_chain_id: "7a241f6d45e434242012", celestia_namespace: Namespace(NamespaceId([0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 26, 171, 174, 95, 110, 227, 193, 117, 134, 18])), celestia_path: Some("/.movement/celestia/7a241f6d45e434242012/.celestia-app"), celestia_validator_address: None, celestia_appd_use_replace_args: false, celestia_appd_replace_args: [] }, bridge: Config { celestia_rpc_connection_hostname: "m1-da-light-node-celestia-appd", celestia_rpc_connection_port: 26657, celestia_websocket_listen_hostname: "<IP_ADDRESS>", celestia_websocket_listen_port: 26658, celestia_bridge_path: Some("/.movement/celestia/7a241f6d45e434242012/.celestia-node"), celestia_bridge_use_replace_args: false, celestia_bridge_replace_args: [] }, m1_da_light_node: Config { celestia_rpc_connection_hostname: "m1-da-light-node-celestia-appd", celestia_rpc_connection_port: 26657, celestia_websocket_connection_hostname: "m1-da-light-node-celestia-bridge", celestia_websocket_connection_port: 26658, m1_da_light_node_listen_hostname: "<IP_ADDRESS>", m1_da_light_node_listen_port: 30730, m1_da_light_node_connection_hostname: "m1-da-light-node", m1_da_light_node_connection_port: 30730 }, celestia_force_new_chain: true, memseq: Config { sequencer_chain_id: Some("7a241f6d45e434242012"), sequencer_database_path: Some("/.movement/memseq/7a241f6d45e434242012/.memseq") }, m1_da_light_node_is_initial: true }
setup                             | 2024-07-15T06:16:47.522882Z  INFO m1_da_light_node_setup::local: Setting up Celestia for chain id: 7a241f6d45e434242012
setup                             | 2024-07-15T06:16:47.522884Z  INFO m1_da_light_node_setup::local: Celestia App Path: /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | 2024-07-15T06:16:47.522886Z  INFO m1_da_light_node_setup::local: Celestia Node Path: /.movement/celestia/7a241f6d45e434242012/.celestia-node
setup                             | 2024-07-15T06:16:47.522887Z  INFO m1_da_light_node_setup::local: Initializing the Celestia App.
setup                             | Running command: celestia-appd init 7a241f6d45e434242012 --chain-id 7a241f6d45e434242012 --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | {"app_message":{"auth":{"accounts":[],"params":{"max_memo_characters":"256","sig_verify_cost_ed25519":"590","sig_verify_cost_secp256k1":"1000","tx_sig_limit":"7","tx_size_cost_per_byte":"10"}},"authz":{"authorization":[]},"bank":{"balances":[],"denom_metadata":[{"base":"utia","denom_units":[{"aliases":["microtia"],"denom":"utia","exponent":0},{"aliases":[],"denom":"TIA","exponent":6}],"description":"The native token of the Celestia network.","display":"TIA","name":"TIA","symbol":"TIA","uri":"","uri_hash":""}],"params":{"default_send_enabled":true,"send_enabled":[]},"supply":[]},"blob":{"params":{"gas_per_blob_byte":8,"gov_max_square_size":"64"}},"capability":{"index":"1","owners":[]},"crisis":{"constant_fee":{"amount":"1000","denom":"utia"}},"distribution":{"delegator_starting_infos":[],"delegator_withdraw_infos":[],"fee_pool":{"community_pool":[]},"outstanding_rewards":[],"params":{"base_proposer_reward":"0.000000000000000000","bonus_proposer_reward":"0.000000000000000000","community_tax":"0.020000000000000000","withdraw_addr_enabled":true},"previous_proposer":"","validator_accumulated_commissions":[],"validator_current_rewards":[],"validator_historical_rewards":[],"validator_slash_events":[]},"evidence":{"evidence":[]},"feegrant":{"allowances":[]},"genutil":{"gen_txs":[]},"gov":{"deposit_params":{"max_deposit_period":"604800s","min_deposit":[{"amount":"10000000000","denom":"utia"}]},"deposits":[],"proposals":[],"starting_proposal_id":"1","tally_params":{"quorum":"0.334000000000000000","threshold":"0.500000000000000000","veto_threshold":"0.334000000000000000"},"votes":[],"voting_params":{"voting_period":"604800s"}},"ibc":{"channel_genesis":{"ack_sequences":[],"acknowledgements":[],"channels":[],"commitments":[],"next_channel_sequence":"0","receipts":[],"recv_sequences":[],"send_sequences":[]},"client_genesis":{"clients":[],"clients_consensus":[],"clients_metadata":[],"create_localhost":false,"next_client_sequence":"0","params":{"allowed_clients":["06-solomachine","07-tendermint"]}},"connection_genesis":{"client_connection_paths":[],"connections":[],"next_connection_sequence":"0","params":{"max_expected_time_per_block":"75000000000"}}},"mint":{"bond_denom":"utia"},"params":null,"qgb":{"params":{"data_commitment_window":"400"}},"slashing":{"missed_blocks":[],"params":{"downtime_jail_duration":"60s","min_signed_per_window":"0.750000000000000000","signed_blocks_window":"5000","slash_fraction_double_sign":"0.020000000000000000","slash_fraction_downtime":"0.000000000000000000"},"signing_infos":[]},"staking":{"delegations":[],"exported":false,"last_total_power":"0","last_validator_powers":[],"params":{"bond_denom":"utia","historical_entries":10000,"max_entries":7,"max_validators":100,"min_commission_rate":"0.050000000000000000","unbonding_time":"1814400s"},"redelegations":[],"unbonding_delegations":[],"validators":[]},"transfer":{"denom_traces":[],"params":{"receive_enabled":true,"send_enabled":true},"port_id":"transfer"},"vesting":{}},"chain_id":"7a241f6d45e434242012","gentxs_dir":"","moniker":"7a241f6d45e434242012","node_id":"0e030d1a1416de413ccc381fcb8c189d988f1175"}
setup                             | 2024-07-15T06:16:47.557990Z  INFO m1_da_light_node_setup::local: Adding the validator key.
setup                             | Running command: celestia-appd keys add validator --keyring-backend=test --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             |
setup                             |
setup                             | - address: celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz
setup                             |   name: validator
setup                             |
setup                             |
setup                             |   pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"Aptc4LwdQDBO2KYu70vI7mS3T9kaM9aYGMly2MCB75yF"}'
setup                             |   type: local
setup                             |
setup                             |
setup                             | **Important** write this mnemonic phrase in a safe place.
setup                             |
setup                             | It is the only way to recover your account if you ever forget your password.
setup                             |
setup                             |
setup                             | rocket motion light mixture black detail illness mixture dizzy tuition color awesome only attitude royal unable flock river comfort load curve brave valve comic
setup                             |
setup                             |
setup                             |
setup                             | 2024-07-15T06:16:47.603827Z  INFO m1_da_light_node_setup::local: Getting the validator address.
setup                             | Running command: celestia-appd keys show validator -a --keyring-backend=test --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz
setup                             | 2024-07-15T06:16:47.639015Z  INFO m1_da_light_node_setup::local: Adding the genesis account.
setup                             | Running command: celestia-appd add-genesis-account celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz<PHONE_NUMBER>000000utia --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | 2024-07-15T06:16:47.672720Z  INFO m1_da_light_node_setup::local: Creating the genesis transaction.
setup                             | Running command: celestia-appd gentx validator<PHONE_NUMBER>utia --keyring-backend=test --chain-id 7a241f6d45e434242012 --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | Genesis transaction written to "/.movement/celestia/7a241f6d45e434242012/.celestia-app/config/gentx/gentx-0e030d1a1416de413ccc381fcb8c189d988f1175.json"
setup                             | 2024-07-15T06:16:47.723607Z  INFO m1_da_light_node_setup::local: Collecting the genesis transactions.
setup                             | Running command: celestia-appd collect-gentxs --home /.movement/celestia/7a241f6d45e434242012/.celestia-app
setup                             | {"app_message":{"auth":{"accounts":[{"@type":"/cosmos.auth.v1beta1.BaseAccount","account_number":"0","address":"celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz","pub_key":null,"sequence":"0"}],"params":{"max_memo_characters":"256","sig_verify_cost_ed25519":"590","sig_verify_cost_secp256k1":"1000","tx_sig_limit":"7","tx_size_cost_per_byte":"10"}},"authz":{"authorization":[]},"bank":{"balances":[{"address":"celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz","coins":[{"amount":"1000000000000000","denom":"utia"}]}],"denom_metadata":[{"base":"utia","denom_units":[{"aliases":["microtia"],"denom":"utia","exponent":0},{"aliases":[],"denom":"TIA","exponent":6}],"description":"The native token of the Celestia network.","display":"TIA","name":"TIA","symbol":"TIA","uri":"","uri_hash":""}],"params":{"default_send_enabled":true,"send_enabled":[]},"supply":[{"amount":"1000000000000000","denom":"utia"}]},"blob":{"params":{"gas_per_blob_byte":8,"gov_max_square_size":"64"}},"capability":{"index":"1","owners":[]},"crisis":{"constant_fee":{"amount":"1000","denom":"utia"}},"distribution":{"delegator_starting_infos":[],"delegator_withdraw_infos":[],"fee_pool":{"community_pool":[]},"outstanding_rewards":[],"params":{"base_proposer_reward":"0.000000000000000000","bonus_proposer_reward":"0.000000000000000000","community_tax":"0.020000000000000000","withdraw_addr_enabled":true},"previous_proposer":"","validator_accumulated_commissions":[],"validator_current_rewards":[],"validator_historical_rewards":[],"validator_slash_events":[]},"evidence":{"evidence":[]},"feegrant":{"allowances":[]},"genutil":{"gen_txs":[{"auth_info":{"fee":{"amount":[],"gas_limit":"210000","granter":"","payer":""},"signer_infos":[{"mode_info":{"single":{"mode":"SIGN_MODE_DIRECT"}},"public_key":{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"Aptc4LwdQDBO2KYu70vI7mS3T9kaM9aYGMly2MCB75yF"},"sequence":"0"}],"tip":null},"body":{"extension_options":[],"memo":"0e030d1a1416de413ccc381fcb8c189d988f1175@<IP_ADDRESS>:26656","messages":[{"@type":"/cosmos.staking.v1beta1.MsgCreateValidator","commission":{"max_change_rate":"0.010000000000000000","max_rate":"0.200000000000000000","rate":"0.100000000000000000"},"delegator_address":"celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz","description":{"details":"","identity":"","moniker":"7a241f6d45e434242012","security_contact":"","website":""},"min_self_delegation":"1","pubkey":{"@type":"/cosmos.crypto.ed25519.PubKey","key":"9WxTSAFAJORcmEsl/4BivzGttPMAc84rhx5jqvtmFh8="},"validator_address":"celestiavaloper19r03grs7ehefah0gkg6vnl5e8w6wkgez8c5jky","value":{"amount":"5000000000","denom":"utia"}}],"non_critical_extension_options":[],"timeout_height":"0"},"signatures":["xyA2sRDp+A4uAE0sk7AkCBwRmYyLUefErwjvXd02Qwp/4xicDh12eLnARTbHTzMZRQUje50ilJ7bZuQ0I49U+g=="]}]},"gov":{"deposit_params":{"max_deposit_period":"604800s","min_deposit":[{"amount":"10000000000","denom":"utia"}]},"deposits":[],"proposals":[],"starting_proposal_id":"1","tally_params":{"quorum":"0.334000000000000000","threshold":"0.500000000000000000","veto_threshold":"0.334000000000000000"},"votes":[],"voting_params":{"voting_period":"604800s"}},"ibc":{"channel_genesis":{"ack_sequences":[],"acknowledgements":[],"channels":[],"commitments":[],"next_channel_sequence":"0","receipts":[],"recv_sequences":[],"send_sequences":[]},"client_genesis":{"clients":[],"clients_consensus":[],"clients_metadata":[],"create_localhost":false,"next_client_sequence":"0","params":{"allowed_clients":["06-solomachine","07-tendermint"]}},"connection_genesis":{"client_connection_paths":[],"connections":[],"next_connection_sequence":"0","params":{"max_expected_time_per_block":"75000000000"}}},"mint":{"bond_denom":"utia"},"params":null,"qgb":{"params":{"data_commitment_window":"400"}},"slashing":{"missed_blocks":[],"params":{"downtime_jail_duration":"60s","min_signed_per_window":"0.750000000000000000","signed_blocks_window":"5000","slash_fraction_double_sign":"0.020000000000000000","slash_fraction_downtime":"0.000000000000000000"},"signing_infos":[]},"staking":{"delegations":[],"exported":false,"last_total_power":"0","last_validator_powers":[],"params":{"bond_denom":"utia","historical_entries":10000,"max_entries":7,"max_validators":100,"min_commission_rate":"0.050000000000000000","unbonding_time":"1814400s"},"redelegations":[],"unbonding_delegations":[],"validators":[]},"transfer":{"denom_traces":[],"params":{"receive_enabled":true,"send_enabled":true},"port_id":"transfer"},"vesting":{}},"chain_id":"7a241f6d45e434242012","gentxs_dir":"/.movement/celestia/7a241f6d45e434242012/.celestia-app/config/gentx","moniker":"7a241f6d45e434242012","node_id":"0e030d1a1416de413ccc381fcb8c189d988f1175"}
setup                             | 2024-07-15T06:16:47.758284Z  INFO m1_da_light_node_setup::local: Updating the Celestia Node config.
setup                             | Running command: sed -i.bak s#"tcp://<IP_ADDRESS>:26657"#"tcp://<IP_ADDRESS>:26657"#g /.movement/celestia/7a241f6d45e434242012/.celestia-app/config/config.toml
setup                             | Running command: sed -i.bak s/^timeout_commit\s*=.*/timeout_commit = "2s"/g /.movement/celestia/7a241f6d45e434242012/.celestia-app/config/config.toml
setup                             | Running command: sed -i.bak s/^timeout_propose\s*=.*/timeout_propose = "2s"/g /.movement/celestia/7a241f6d45e434242012/.celestia-app/config/config.toml
setup                             | 2024-07-15T06:16:47.760987Z  INFO m1_da_light_node_setup::local: Copying keys from Celestia App to Celestia Node.
setup                             | 2024-07-15T06:16:47.761203Z  INFO m1_da_light_node_setup::local: Getting the auth token.
setup                             | Running command: celestia bridge auth admin --node.store /.movement/celestia/7a241f6d45e434242012/.celestia-node
setup                             | eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJBbGxvdyI6WyJwdWJsaWMiLCJyZWFkIiwid3JpdGUiLCJhZG1pbiJdfQ.tTsyfvuYtRxYL0-uuzAQWq9-2FA0Uo_2ZzN9V0UQRJk
setup                             | 2024-07-15T06:16:47.791045Z  INFO m1_da_light_node_setup::local: Celestia setup complete.
setup                             | 2024-07-15T06:16:47.791056Z  INFO m1_da_light_node_setup::local: M1 DA Light Node setup complete.
setup                             | 2024-07-15T06:16:47.791063Z  INFO suzuka_full_node_setup: SuzukaFullNodeSetup: Finished setup with config: Config {
setup                             |     execution_config: MaptosConfig {
setup                             |         maptos_config: Config {
setup                             |             chain: Config {
setup                             |                 maptos_chain_id: 27,
setup                             |                 maptos_rest_listen_hostname: "<IP_ADDRESS>",
setup                             |                 maptos_rest_listen_port: 30731,
setup                             |                 maptos_private_key: <elided secret for Ed25519PrivateKey>,
setup                             |                 maptos_db_path: Some(
setup                             |                     "/.movement/maptos/27/.maptos",
setup                             |                 ),
setup                             |             },
setup                             |             client: Config {
setup                             |                 maptos_rest_connection_hostname: "suzuka-full-node",
setup                             |                 maptos_rest_connection_port: 30731,
setup                             |                 maptos_faucet_rest_connection_hostname: "suzuka-faucet-service",
setup                             |                 maptos_faucet_rest_connection_port: 30732,
setup                             |             },
setup                             |             faucet: Config {
setup                             |                 maptos_rest_connection_hostname: "suzuka-full-node",
setup                             |                 maptos_rest_connection_port: 30731,
setup                             |                 maptos_faucet_rest_listen_hostname: "<IP_ADDRESS>",
setup                             |                 maptos_faucet_rest_listen_port: 30732,
setup                             |             },
setup                             |             fin: Config {
setup                             |                 fin_rest_listen_hostname: "<IP_ADDRESS>",
setup                             |                 fin_rest_listen_port: 30733,
setup                             |             },
setup                             |         },
setup                             |     },
setup                             |     m1_da_light_node: M1DaLightNodeConfig {
setup                             |         m1_da_light_node_config: Local(
setup                             |             Config {
setup                             |                 appd: Config {
setup                             |                     celestia_rpc_listen_hostname: "<IP_ADDRESS>",
setup                             |                     celestia_rpc_listen_port: 26657,
setup                             |                     celestia_websocket_connection_hostname: "m1-da-light-node-celestia-bridge",
setup                             |                     celestia_websocket_connection_port: 26658,
setup                             |                     celestia_auth_token: Some(
setup                             |                         "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJBbGxvdyI6WyJwdWJsaWMiLCJyZWFkIiwid3JpdGUiLCJhZG1pbiJdfQ.tTsyfvuYtRxYL0-uuzAQWq9-2FA0Uo_2ZzN9V0UQRJk",
setup                             |                     ),
setup                             |                     celestia_chain_id: "7a241f6d45e434242012",
setup                             |                     celestia_namespace: Namespace(
setup                             |                         NamespaceId(
setup                             |                             [
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 0,
setup                             |                                 26,
setup                             |                                 171,
setup                             |                                 174,
setup                             |                                 95,
setup                             |                                 110,
setup                             |                                 227,
setup                             |                                 193,
setup                             |                                 117,
setup                             |                                 134,
setup                             |                                 18,
setup                             |                             ],
setup                             |                         ),
setup                             |                     ),
setup                             |                     celestia_path: Some(
setup                             |                         "/.movement/celestia/7a241f6d45e434242012/.celestia-app",
setup                             |                     ),
setup                             |                     celestia_validator_address: Some(
setup                             |                         "celestia19r03grs7ehefah0gkg6vnl5e8w6wkgezz8ktqz",
setup                             |                     ),
setup                             |                     celestia_appd_use_replace_args: false,
setup                             |                     celestia_appd_replace_args: [],
setup                             |                 },
setup                             |                 bridge: Config {
setup                             |                     celestia_rpc_connection_hostname: "m1-da-light-node-celestia-appd",
setup                             |                     celestia_rpc_connection_port: 26657,
setup                             |                     celestia_websocket_listen_hostname: "<IP_ADDRESS>",
setup                             |                     celestia_websocket_listen_port: 26658,
setup                             |                     celestia_bridge_path: Some(
setup                             |                         "/.movement/celestia/7a241f6d45e434242012/.celestia-node",
setup                             |                     ),
setup                             |                     celestia_bridge_use_replace_args: false,
setup                             |                     celestia_bridge_replace_args: [],
setup                             |                 },
setup                             |                 m1_da_light_node: Config {
setup                             |                     celestia_rpc_connection_hostname: "m1-da-light-node-celestia-appd",
setup                             |                     celestia_rpc_connection_port: 26657,
setup                             |                     celestia_websocket_connection_hostname: "m1-da-light-node-celestia-bridge",
setup                             |                     celestia_websocket_connection_port: 26658,
setup                             |                     m1_da_light_node_listen_hostname: "<IP_ADDRESS>",
setup                             |                     m1_da_light_node_listen_port: 30730,
setup                             |                     m1_da_light_node_connection_hostname: "m1-da-light-node",
setup                             |                     m1_da_light_node_connection_port: 30730,
setup                             |                 },
setup                             |                 celestia_force_new_chain: true,
setup                             |                 memseq: Config {
setup                             |                     sequencer_chain_id: Some(
setup                             |                         "7a241f6d45e434242012",
setup                             |                     ),
setup                             |                     sequencer_database_path: Some(
setup                             |                         "/.movement/memseq/7a241f6d45e434242012/.memseq",
setup                             |                     ),
setup                             |                 },
setup                             |                 m1_da_light_node_is_initial: false,
setup                             |             },
setup                             |         ),
setup                             |     },
setup                             |     mcr: Config {
setup                             |         rpc_url: Some(
setup                             |             "http://localhost:8545",
setup                             |         ),
setup                             |         ws_url: Some(
setup                             |             "ws://localhost:8546",
setup                             |         ),
setup                             |         signer_private_key: Some(
setup                             |             "0xe2fc54ae7fc933553291c283d0084f025d11f59b75a618f8879736999614e3ec",
setup                             |         ),
setup                             |         mcr_contract_address: "0xBf7c7AE15E23B2E19C7a1e3c36e245A71500e181",
setup                             |         gas_limit:<PHONE_NUMBER>0,
setup                             |         num_tx_send_retries: 10,
setup                             |     },
setup                             | }
setup exited with code 0
dependency failed to start: container setup exited (0)


Change custom router to Zewo/Router

Migrated to DEVELOPMENT-SNAPSHOT-2016-05-03-a.
Swifton router was dependent on URITemplate package, which is not maintained anymore, so I changed it to Zewo Router.
Resolves #34

@weby thanks! I merged PathKit and Stencil. Travis actually shows both iOS and Linux failing.

OSX tests pass on Travis now.

@weby fantastic!


Faster parents lookup

Hi,
Improving the performance of parents lookup by adding parents index which map children to it's parents.
I have also removed the "objects" global variable to save some memory and now we are using combination of object index and parents index.
Now the showing of parents is slow only because of big tables, I decreased the lookup from 100ms~ to 6ms~ (checked using console.time and clicked multiple rows).

After pull request #9 is merged I will fix this pull request.


First Prototype

This is a first prototype, intended for demonstration purposes, and will serve as temporary pages.

satisfies deployment requirements, ready to 🚀


Provide instructions for enabling inside of ChatGPT

The README should show how to enable this plugin for use in ChatGPT.

Making the images here

Done.


Bump github.com/go-openapi/strfmt

The PR #2913 opened by dependabot brought a new version of github.com/go-openapi/strfmt, which seems to have a few API incompatibilities with the previous version. This ticket is about making the necessary changes so that we can upgrade to a newer version.

can I look into it

It's yours, @KrishnaSindhur

@ampaire, it's yours now!

@jpkrohling it no update has been made can I take this issue?

Closed by #2800


Sparse R-CNN: negative values in ROIs

Prerequisite

[X] I have searched the existing and past issues but cannot get the expected help.
[X] I have read the FAQ documentation but cannot get the expected help.
[X] The bug has not been fixed in the latest version.

🐞 Describe the bug
Thanks for this nice toolbox. When I delve into Sparse R-CNN training, I print out the rois in this line https://github.com/open-mmlab/mmdetection/blob/master/mmdet/models/roi_heads/sparse_roi_head.py#L88, there are negative values. Is it normal? As far as I can see, the rois should be within the range of [0, image_shape]. Could you please explain this behavior? Thanks.
Environment
sys.platform: linux                                                                                Python: 3.9.13 (main, Aug 25 2022, 23:26:10) [GCC 11.2.0]                                                                     CUDA available: True                                                                                GPU 0,1,2,3,4,5,6,7: NVIDIA GeForce RTX 3090
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 11.3, V11.3.58
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
PyTorch: 1.12.1
PyTorch compiling details: PyTorch built with:

GCC 9.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.6.0 (Git Hash 52b5f107dd9cf10910aaa19cb47f3abf9b349815)
OpenMP 201511 (a.k.a. OpenMP 4.5)
LAPACK is enabled (usually provided by MKL)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 11.3
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_37,code=compute_37
CuDNN 8.3.2  (built against CUDA 11.5)
Magma 2.5.2
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.3, CUDNN_VERSION=8.3.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -fabi-version=11 -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.12.1, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=OFF, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF,

TorchVision: 0.13.1
OpenCV: 4.6.0
MMCV: 1.6.1
MMCV Compiler: GCC 9.4
MMCV CUDA Compiler: 11.3
MMDetection: 2.25.2+9d3e162
Additional information
No additional modification is made. Dataset is MSCOCO.

The logic we implemented is consistent with the original code, and a negative roi does not affect the performance of the Sparse R-CNN.

The RoI with negative coordinates will has its RoI features to be zeros.


Indentation functions needed for YAML or format() to be indent aware

Is your feature request related to a problem? Please describe.
When formatting multiline strings which are in YAML format, there is often a need to perform indentation, especially when dealing with cloud-init, e.g.
var containerdScript = loadTextContent('containerd.sh')

var cloudConfig = '''
#cloud-config

write_files:
  - content: |
      ${0}
    path: /root/containerd.sh
    owner: root:root
'''

// Use format function as Bicep doesn't yet support interpolation on multiline strings
output cloudInit string = format(cloudConfig, containerdScript)

That code will not work as only the first line of the script which is injected at ${0} will have the correct indentation, the rest of the lines will be placed at column zero, and that's invalid YAML
Describe the solution you'd like
Terraform has a function for this providing this
https://www.terraform.io/docs/language/functions/indent.html
And Helm has several indent functions to help with this
https://helm.sh/docs/chart_template_guide/function_list/#indent
Maybe an indent function could be added to Bicep? With a parameter to supply how many spaces to ident by e.g.
var containerdScript = indent(loadTextContent('containerd.sh'), 4)

This is a great catch. Thanks for reporting, and thanks for sharing how other languages have solved this. Not sure what the options/solutions are, but we will discuss this week.

Here's an option if you want to DIY it with user defined functions:
@description('Indents a string by a given prefix')
func indentWithPrefix(input string, indent string) string => '${indent}${join(split(input, '\n'), '\n${indent}')}'

@description('Indents a string by a given number of spaces')
func indent(input string, count int) string => indentWithPrefix(input, padLeft('', count, ' '))

output script string = indent('''
#!/bin/bash

echo "Hello, world!"
''', 4)


Add hint to create cluster automation step  when aap is not installed

Related Issue: https://github.com/stolostron/backlog/issues/23819
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>Dark Theme:

Light Theme:

/hold

/retest-required

/unhold

/lgtm

/lgtm


🐛 [flutterfire_cli] I can't move with the arrows to choose the options

Bug report
Describe the bug
I can't move with the arrows to choose the options. The selection with the space bar works but I can only choose the first option since I cannot move to others.
Steps to reproduce
Steps to reproduce the behavior:

Run flutterfire configure
I can't move

Expected behavior
When I run the command I want to be able to move around and choose the available options

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
**[✓] Flutter (Channel stable, 3.3.0, on macOS 12.4 21F79 darwin-x64, locale es-419)
• Flutter version 3.3.0 on channel stable at /Users/exedemaio/Development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ffccd96b62 (6 days ago), 2022-08-29 17:28:57 -0700
• Engine revision 5e9e0e0aa8
• Dart version 2.18.0
• DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/exedemaio/Library/Android/sdk
• Platform android-31, build-tools 30.0.2
• ANDROID_HOME = /Users/exedemaio/Library/Android/sdk
• Java binary at: /Users/exedemaio/Library/Application
Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/211.7628.21.2111.8193401/Android
Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 13F100
• CocoaPods version 1.11.2

[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] Android Studio (version 2021.1)
• Android Studio at /Users/exedemaio/Library/Application
Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/211.7628.21.2111.8193401/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] Android Studio (version 2020.3)
• Android Studio at /Users/exedemaio/Library/Application
Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/203.7784292/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.70.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.46.0

[✓] Connected device (2 available)
• macOS (desktop) • macos • darwin-x64 • macOS 12.4 21F79 darwin-x64
• Chrome (web) • chrome • web-javascript • Google Chrome 104.0.5112.101

[✓] HTTP Host Availability
• All required HTTP hosts are available

• No issues found!**

@exedemaio
Please file this issue in flutterfire CLI's dedicated repo: https://github.com/invertase/flutterfire_cli/issues
Closing from here.


Fix iOS Fastlane build when using Unity Cloud Diagnostics

Fixes error described here: https://forum.unity.com/threads/ios-build-is-failing-seems-like-a-fastlane-problem-not-sure-how-to-proceed.682201/
Changes

Add username and password to mac build.sh

Checklist

[x] Read the contribution guide and accept the code of conduct
[x] Readme (updated or not needed)
[x] Tests (added, updated or not needed)

The description is not clear enough as to what exactly it fixes under which circumstances.
We currently have successful builds in iOS.
What would be interesting to know is how Unity Cloud Diagnostics is different and which exact post you're referring to in that long thread that is seemingly about a bug in Unity and little related to the code changes. I could be mistaken and would love to be educated.

The post I'm referring to is the first post in the thread.
I get this error during the build_app step in Fastlane:
6842: ▸ Running script 'Process symbols'
6843: ▸ ** ARCHIVE FAILED **
6844: ▸ The following build commands failed:
6845: ▸ PhaseScriptExecution Process\ symbols /BUILD_PATH/Library/Developer/Xcode/DerivedData/Unity-iPhone-gjomesfkojewdbcqkxboenqtbzba/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/IntermediateBuildFilesPath/Unity-iPhone.build/Release-iphoneos/Unity-iPhone.build/Script-F6E34F12805380276D47C8E3.sh
6846: ▸ (1 failure)

The solution from the thread is to add the username and password arguments when calling Unity through batchmode.

Sure thing, I'll let you know when the build is done.

Looks like it worked. 🙂


Versions, defaultValue and deprecationReason

Updated base MP versions to align with MP 2.1
Removed defaultValue field as it is replaced with @DefaultValue.
Removed deprecationReason field as it is replaced with @Deprecated

@andymc12 I added a note in the README, indicating how people can contribute


Sample collected showing repository numbers

In New Resource  - Fossil Collection Event - Samples Collected LOV is pointing at repository number not Genus species

This is correct behaviour - the Name primary descriptor is the repository number, not the list of scientific names.


[WIP] put the vagrant bin dir to the front of the PATH

Why?

I just ran bundle install in vagrant-berkshelf, which cause vagrant to be bundle-installed from a git source.
This caused W:\home\.chefdk\gem\ruby\2.0.0\bin\vagrant.bat to be added / created and this was now in front of the PATH
And I got this error then:

C:\Repos\_github\dev-box>vagrant up
W:/tools/chefdk/embedded/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'vagrant' (>= 0) among 308 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=W:/home/.chefdk/gem/ruby/2.0.0;W:/tools/chefdk/embedded/lib/ruby/gems/2.0.0', execute `gem env` for more information
        from W:/tools/chefdk/embedded/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:324:in `to_spec'
        from W:/tools/chefdk/embedded/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_gem.rb:58:in `gem'
        from W:/home/.chefdk/gem/ruby/2.0.0/bin/vagrant:22:in `<main>'

Thoughts:

putting the vagrant bin dir in front of the PATH surely helps
not sure though how well this plays with vagrant-wrapper?
or should we have vagrant-wrapper pre-installed as gem to prevent this?

Note:

having vagrant-wrapper preinstalled as a gem does not help --> same problem after running bundle install near a Gemfile which references vagrant from a git location
tried setting BUNDLE_BIN_PATH and BUNDLE_SYSTEM_BINDIR to a directory not on the path but it did not have any effect (in fact no gems ended up there)


Scope view intermittently goes black

Don't think this is a UI issue - the app is sending a message to the UI deleting all the nodes.

  I suspect something on the main probe thread is deadlocking.


feat: custom values to sandbox iframe

SUMMARY
when inside a dashboard any component as a Table that has links to external sities are blocked when open.
For example in a Table that renders a list of top post of tweets or Facebook post with a link to open this post in Twitter or Facebook when click the new window are opened but show as blocked content.
To avoid this issue need aggregate  allow-popups-to-escape-sandbox  to handle this we add a generic method to allow add any custom value to sandbox attribute of iframe passing using the new iframeSandboxExtras .
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

Thanks for the PR @dacopan. Would you mind adding some docs to the README?

Sure, give me a some hours and Will update the PR

@michael-s-molina changes done, also update version in package.json

I'm currently using v0.1.0-alpha.12, but I don't see the iframeSandboxExtras option to set my sandbox attributes. Will this feature be available in the next release? @dacopan @rusackas

Feature already published in npm package. where you can't see the prop?

@dacopan it's weird I'm using latest version of superset-ui/embedded-sdk

but I don't see this feature in node_modules

(I also tried to remove and generate new node_modules)

Can you check what  version has in package-lock.json?
Then try remove this file and reinstall

I've checked the yarn.lock file, and it shows the same version (0.1.0-alpha.12). I also tried removing both yarn.lock and node_modules, then regenerating them, but I'm still not seeing the iframeSandboxExtras props @dacopan

Let me check today in a fresh example
El mar, 20 de ago de 2024, 03:08, Mick Jerin @.***>
escribió:

I've checked the yarn.lock file, and it shows the same version
(0.1.0-alpha.12). I also tried removing both yarn.lock and node_modules,
then regenerating them, but I'm still not seeing the iframeSandboxExtras
props @dacopan https://github.com/dacopan
Screenshot.2024-08-20.133113.png (view on web)
https://github.com/user-attachments/assets/db7f4bdb-5b52-458e-a688-e7e674276a20
—
Reply to this email directly, view it on GitHub
https://github.com/apache/superset/pull/29590#issuecomment-2298235386,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCLUMJSSMRC7TINLMFF7YDZSL2QTAVCNFSM6AAAAABK3OE5Y2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYGIZTKMZYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@MickJerin12 I create a fresh project and all are correct

@dacopan It’s working for me now, thanks for your help!
After cleaning the .yarn files and updating yarn to the latest version, I started seeing the updated code in node_modules.


can't create file

I can't create new file  when the file's name is part of the other in the same floder. e.g. When  a file named "testsomething" in home floder, every time i want creat a new file named "test" use C-x C-f , emacs open the "testsomething".
Is ohter command used for create file?

:+1:

@bigbug I noted this in the README, too. :-)

Instead of switching to normal find file. You could use c-j.

@hariharanr5 Yes, that's also helpful sometimes.

@purcell Thanks for your nice conf :)
btw, may I ask why expression not evaluated when pressed  ?

btw, may I ask why expression not evaluated when pressed ?

@ibigbug Not sure what you mean. What type of expression, in which type of buffer, and what are you pressing? :-)

I'm sorry once I thought <C-j> means evaluate-last-expression which I find it was an other binding :(
Thanks for your active reply :+1:

Aha, right. No, this new binding was introduced in Emacs 24.4 (I think).

I've found this stack overflow answer suggesting c-j which dates back to '09. http://stackoverflow.com/questions/812524/ido-mode-is-too-smart-can-i-get-it-to-not-complete-a-filename So I guess this key binding is available from emacs 23 release onwards.

You're right -- I was thinking of C-x C-j, which lets you open an ido buffer for any current file.


refactor: use color with opacity for inline code

We're probably better off using colors with opacity for inline code. A more generic approach that is suitable for all use cases.
Before:

Light
Dark

After:

Light
Dark

looks better, any opinion @yangshun ?


Player should accelerate and decelerate

Who: Player
What:
Add acceleration corresponding to the player position, making it glide and has friction.
Why:
Because we are trying to get as close as possible to the original Asteroids experience
Time est:
15 min - 2 hours
Priority:
HIGH

Added first iteration of the movement.. it needs tweaking but it is getting there.

I'll close this now.. it is practically done, tweaking can be done at any time.


Transform styles LESS to SASS

:+1:

:+1: :+1:

:+1: :+1: :+1:

+1

:+1:

I personally prefer LESS, perhaps maintaining both wouldn't be out of the question.

This would be a pretty big change, but we do see the value in supporting SASS/SCSS in some way. We aren't in a position to fully replat our styles any time soon, but like @CuddleBunny mentions, I could see spinning up parallel versions at some point.
Tidbit for the sake of curiosity: we originally started with LESS because it had pretty broad adoption across product teams at Microsoft.

Agreed. Less is no longer the standard, as Sass has gotten much larger traction and a bigger following.

👍 +1 👍

They're used by different groups for different reasons.
LESS is easier to learn as its a intentionally tight feature set to cover the vast majority of use cases, but not all.
Like CSS, LESS is declarative. SASS is imperative. So that also makes it a more familiar concept to web developers. For instance, LESS had concepts like block scoping and cascading values that SASS does not have. So it's more like CSS+ and SASS is more like PHP or Ruby with CSS-like syntax.
So LESS doesn't try to be the standard but a solution to a different set of problems as priority. We (core Less users) regularly suggest Sass when people need a more programming-language-like imperative construct. Basically, Less is the iPod and Sass is the Zune, so, yup, Sass has way more features. :-)
Use what suits your project!

@matthew-dean by comparing SASS to Zune you have just made enemies with web developers at large! :smiley:

@andrewconnell lol a low blow, I know. But sometimes I hear "Sass is better than Less because it has more features." Which is pretty much exactly the same as saying, "Zune is better than the iPod because it has more features." Fewer features sometimes makes for faster adoption, less confusion, and easier onboarding for new devs, so that's the reason I bring up the comparison.

Look this : https://css-tricks.com/sass-vs-less/

I think many web developer switched from LESS to SASS. Support both will be a good option for those you still use less.

+1

I mentioned this thread in this post, if you're curious: http://getcrunch.co/2015/10/08/less-the-worlds-most-misunderstood-css-pre-processor/

Hi all! Looping back here to mention to everyone that our latest version, 1.2.0, includes the beginnings of our conversion to SASS - check it out! We've still got work to do, but we're open to hearing opinions/feedback.

Awesome update! How soon can we expect to this to be in the CDN?

Reason I ask – next week we will have our first release of the Angular Directives for Office UI Fabric and our demos reference the CDN links… we’d love to point to the latest stuff…

Oh nice now we're really up to par with Bootstrap, since it has AngularJS directives as well.
Stoked, can't wait to integrate them into my boilerplate MEANS open source project http://github.com/SharePointOscar/MEANS
Sent from my 6S
On Jan 8, 2016, at 11:43 AM, Andrew Connell <notifications<EMAIL_ADDRESS>wrote:
Reason I ask - next week we will have our first release of the Angular Directives for Office UI Fabric and our demos reference the CDN links... we'd love to point to the latest stuff...

Reply to this email directly or view it on GitHubhttps://github.com/OfficeDev/Office-UI-Fabric/issues/56#issuecomment-170104046.

@andrewconnell - we're currently pushing to get our CDN updated asap. I don't have a timeframe yet, but we're hoping for the next week or 2.

@SharePointOscar just FYI... we shipped the first drop of http://ngofficeuifabric.com, Angular directives for Office UI Fabric

Yummy!  Time to start integrating them into my MEANS boilerplate project!  Thanks for the heads up AC!
From: Andrew Connell
Reply-To: OfficeDev/Office-UI-Fabric
Date: Friday, January 15, 2016 at 10:39 AM
To: OfficeDev/Office-UI-Fabric
Cc: Oscar Medina
Subject: Re: [Office-UI-Fabric] Transform styles LESS to SASS (#56)
@SharePointOscarhttps://github.com/SharePointOscar just FYI... we shipped the first drop of http://ngofficeuifabric.com, Angular directives for Office UI Fabric
—
Reply to this email directly or view it on GitHubhttps://github.com/OfficeDev/Office-UI-Fabric/issues/56#issuecomment-172046676.

Np… planning another drop sometime early next week with at least one more directive…

Replacing LESS with Sass is underway, see pull request #279. We plan to have LESS completely removed when we release Fabric 2.0.

:+1:

Finished in #303!

Sad to learn that LESS is removed and no longer supported...  :disappointed:
Supporting SASS, although may provide you a richer set of features - that you may or may not use - it does add complexity and intimidation around setting up an environment for anyone that may want to use this project to create mashups.  It also limits us LESS users in actually taking advantage of Office UI Fabric... In my personal use cases, I have not been able to find a gap in functionality that required me to go use SASS - perhaps you guys have and thus the change in tooling...
That being said, I will eventually move to use SASS, since it seems that tool is moving quickly into becoming the most popular one.. and thus the one with best support.So I'm not a hatter of the tool... but I'm not ready yet either... so with that:

How to use Last release with LESS Support
For anyone that may find this thread and still want to use the LESS source, there is what I did:
The instruction below are for v1.2.1 - which seems to be the last tagged version that had LESS support.
From the command prompt:
$ git fetch --tags
$ git checkout -b release_1-2-1 1.2.1

If using Bower, just run this command instead of the default approach:
 bower install --save-dev OfficeDev/Office-UI-Fabric#1.2.1

now... back to using Office UI Fabric on custom widgets.... :grin:
/Paul

since it seems that tool is moving quickly into becoming the most popular one

Sorry, but under what metric have people determined that Sass is more popular than Less?
https://twitter.com/matthewdeaners/status/693228336814817280

We understand that this isn't a welcome change for everyone. We've communicated that it's coming (in this issue, our prior release notes, and in our roadmap) but we know it will be a surprise to some.
For us it's not a question of the features of LESS vs Sass or the wider popularity or trendiness of either one – what we've heard from our users, both inside and outside of Microsoft, is that Sass is preferred. We considered supporting both but this would burden our development process and keep us from fixing bugs and developing features. As a small team we have to be careful about where we spend our time. Thanks for your understanding.

For us it's not a question of the features of LESS vs Sass or the wider popularity or trendiness of either one – what we've heard from our users, both inside and outside of Microsoft, is that Sass is preferred.

That's a good answer, and makes sense.

Hi @matthew-dean... You are right: I don't have a metric I can point you to... its simply my personal opinion based on my recent encounters. I'm a LESS user and I have been feeling as if perhaps its time for me to move on from it... Several of the libraries/widgets I have used recently all had their CSS written in SASS...
@mikewheaton Thank you for our response. I understand the motive and agree with @matthew-dean : its ultimately what makes more sense for this project and the majority of its users.


fix for #111, hasBlock only available from template

we add an observer if template exists (preGlimmer) that sets hasBlock
to the value of template.blockParams, otherwise we do what ember would
normally do, post-glimmer

Seems reasonable. I'll have to wait until I have time to pull this down and test it locally before I merge, since I never found a good integration testing story for Ember 1.11-1.12, I'm forced to do manual testing. :\

Sounds good, I think this will help with what @blangset and @koryteg were mentioning in #101, specifically useTemplate=true.

Thanks @zkwentz ... all merged.

Good deal, thanks @blesh


Fix order of operations for macOS template check

Potentially resolves https://github.com/godotengine/godot/issues/62873.
I'm not a mac user myself, but looks like the order of operations was just wrong. If one of the custom template configs was missing, it'd force a check for the official templates, and if not present, lead to valid = false. In the issue, the workaround of specifying both custom template configs ensured the check for the official templates wouldn't happen.
Looking at all the other platforms, they check for the official templates first, then the custom templates. Made it consistent here

Thanks!

Cherry-picked for 4.2.1.


Saving notebook doesn't save plots in JupyterLab 1.0.1

After the release of JupyterLab 1.0.0, there are some compatibility issues between holoviews and JupyterLab. When running a visualization code, the plot displays correctly in the notebook but saving the notebook doesn't save the plot. The plot is lost when reopening the notebook (after saving and closing it).
Details:
OS: Ubuntu 18.10 (via Docker)
JupyterLab: 1.01   (installed using pip)
HoloViews: 1.12.3   (installed using pip)

Is it a problem in JLab 1.0.1 specifically? I can't reproduce this with 1.0.0 at least.

@philippjfr I'm so sorry about not testing the issue thoroughly. Just tried again and it seems to be a trust issue with JupyterLab. I'll close this issue and open a new one in the JupyterLab repository.

When I created a brand new notebook and made a Holoviews visualization example there, everything works well.

When I used a pre-saved notebook with a visualization example inside, the plot didn't show up after reopening the notebook. Manually trusting the notebook made the plot show up but it didn't persist, which means that I had to manually trust the notebook again next time I open the notebook. I don't have to go over the hassle if it's a newly created notebook.


⚠ Bofrost.lu has degraded performance

In 31fed7b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1811 ms

Resolved: Bofrost.lu performance has improved in 20aab6d after 13 minutes.


🐛 [cloud_firestore] IN and array_contains_any should allow 30 values

Bug report
With the introduction of OR clauses, Firestore queries can now contain up to 30 disjunctions in the query normal form. This also means that the maximum number of values in an IN clause or array-contains-any clause is now 30. The Flutter SDK still seems to limit this to 10 here: https://github.com/firebase/flutterfire/blob/81f1b80c445cfaab3e7752b8c58f35c92d234d8d/packages/cloud_firestore/cloud_firestore/lib/src/query.dart#L734

Hey @puf, I had a play with this. I found that you could have 30 disjunctive queries when using Filter API, but it isn't possible using the array-contains-any or where-in or where-not-in which still only allow 10 (I removed the 10 limit locally but received an error from the Firebase server when testing on android and iOS).

Thanks for testing, Russel!
Hmm... I really thought this should work now based on the documentation.
I'm gonna ask around...
On Fri, Jun 16, 2023 at 2:39 PM Russell Wheatley @.***>
wrote:

Hey @puf https://github.com/puf, I had a play with this. I found that
you could have 30 disjunctive queries
https://github.com/firebase/flutterfire/pull/11140/files#diff-24d88bfbf516869914dafeb46b907a3384e1dd9e4622ab0e23b8aaeac105108cR2096-R2147
when using Filter API, but it isn't possible using the array-contains-any
or where-in or where-not-in which still only allow 10
https://github.com/firebase/flutterfire/pull/11140/files#diff-24d88bfbf516869914dafeb46b907a3384e1dd9e4622ab0e23b8aaeac105108cR2149-R2344
(I removed the 10 limit locally but received an error from the Firebase
server when testing on android and iOS).
—
Reply to this email directly, view it on GitHub
https://github.com/firebase/flutterfire/issues/11085#issuecomment-1594613306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG7BX2H6ADBP7NKBL2DCKTXLRHXRANCNFSM6AAAAAAY3QN4EI
.
You are receiving this because you were mentioned.Message ID:
@.***>

I've created a PR to reinsert the commented out e2e tests and to increase the filters allowed for "in" & "array-contains-any" as they now appear to successfully complete. Not sure if it was something in my testing or response from the Firebase server but at least it works now ⚡


terminated tab remains open

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.450]
Windows Terminal version (if applicable): 1.2.2381.0

Steps to reproduce

open ssh terminal
exit the terminal (press CTRL - D)
sometimes the tab remains open with exit code greater than zero

Expected behavior
There should be an option to close tabs regardless the exit code.

You know, there is already an option to control if tabs closeOnExit, maybe you should check out the docs

I'm aware of that option and it's set to "closeOnExit": "always"

Thanks. Since it looks like closeOnExit isn't working, could you share a copy (or the appropriate snippet) of your settings.json?

settings.json
//
// https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md#profiles
//

{
  "$schema": "https://aka.ms/terminal-profiles-schema",
  "wordDelimiters": " \"'<>,:;=()[]{}",
  "alwaysShowTabs": true,
  "closeOnExit": "always",
  "theme": "dark",
  "defaultProfile": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
  "copyOnSelect": true,
  "copyFormatting": false,
  "largePasteWarning": false,
  "multiLinePasteWarning": false,
  "profiles": {
    "defaults": {
      // https://atomcorp.github.io/themes/
      "colorScheme": "Dracula",
      "cursorShape": "vintage"
    },
    "list": [ {
        "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
        "hidden": false,
        "name": "Ubuntu-20.04",
        "source": "Windows.Terminal.Wsl",
        "padding": "20, 20, 10, 10",
        "selectionBackground": "#ffbbcc",

      },
      {
        "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
        "hidden": false,
        "name": "Azure Cloud Shell",
        "source": "Windows.Terminal.Azure"
      },
      {
          "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",
          "hidden": false,
          "name": "Ubuntu-20.04",
          "source": "Windows.Terminal.Wsl"
      }
    ]
  },
  "schemes": [  {
      "name": "Afterglow",
      "black": "#151515",
      "red": "#ac4142",
      "green": "#7e8e50",
      "yellow": "#e5b567",
      "blue": "#6c99bb",
      "purple": "#9f4e85",
      "cyan": "#7dd6cf",
      "white": "#d0d0d0",
      "brightBlack": "#505050",
      "brightRed": "#ac4142",
      "brightGreen": "#7e8e50",
      "brightYellow": "#e5b567",
      "brightBlue": "#6c99bb",
      "brightPurple": "#9f4e85",
      "brightCyan": "#7dd6cf",
      "brightWhite": "#f5f5f5",
      "background": "#212121",
      "foreground": "#d0d0d0"
    },
    {
      // https://draculatheme.com/
      "name" : "Dracula",
      "background" : "#272935",
      "black" : "#21222C",
      "blue" : "#BD93F9",
      "cyan" : "#8BE9FD",
      "foreground" : "#F8F8F2",
      "green" : "#50FA7B",
      "purple" : "#FF79C6",
      "red" : "#FF5555",
      "white" : "#F8F8F2",
      "yellow" : "#FFB86C",
      "brightBlack" : "#6272A4",
      "brightBlue" : "#D6ACFF",
      "brightCyan" : "#A4FFFF",
      "brightGreen" : "#69FF94",
      "brightPurple" : "#FF92DF",
      "brightRed" : "#FF6E6E",
      "brightWhite" : "#F8F8F2",
      "brightYellow" : "#FFFFA5"
    },
    {
      "name": "Breeze",
      "black": "#31363b",
      "red": "#ed1515",
      "green": "#11d116",
      "yellow": "#f67400",
      "blue": "#1d99f3",
      "purple": "#9b59b6",
      "cyan": "#1abc9c",
      "white": "#eff0f1",
      "brightBlack": "#7f8c8d",
      "brightRed": "#c0392b",
      "brightGreen": "#1cdc9a",
      "brightYellow": "#fdbc4b",
      "brightBlue": "#3daee9",
      "brightPurple": "#8e44ad",
      "brightCyan": "#16a085",
      "brightWhite": "#fcfcfc",
      "background": "#31363b",
      "foreground": "#eff0f1"
    },
    {
      "name": "Calamity",
      "black": "#2f2833",
      "red": "#fc644d",
      "green": "#a5f69c",
      "yellow": "#e9d7a5",
      "blue": "#3b79c7",
      "purple": "#f92672",
      "cyan": "#74d3de",
      "white": "#d5ced9",
      "brightBlack": "#7e6c88",
      "brightRed": "#fc644d",
      "brightGreen": "#a5f69c",
      "brightYellow": "#e9d7a5",
      "brightBlue": "#3b79c7",
      "brightPurple": "#f92672",
      "brightCyan": "#74d3de",
      "brightWhite": "#ffffff",
      "background": "#2f2833",
      "foreground": "#d5ced9"
    }
  ]
}
"keybindings": [
  { "command": {"action": "copy", "singleLine": false }, "keys": "ctrl+c" },
  { "command": "paste", "keys": "ctrl+v" },
  { "command": "find", "keys": "ctrl+shift+f" },
  { "command": "newTab", "keys": "ctrl+shift+t"},
  { "command": { "action": "splitPane", "split": "vertical" }, "keys": "alt+shift+-" }

]
}

Ah! You will need to move closeOnExit into the profiles.defaults section. Since we made it a per-profile property (so that you could set closeOnExit differently for WSL and for your "production server SSH" or whatever profiles), it has to go into the profiles section.
Does that work for you?

Give me a couple of hours to test it because it doesn't happen every time.

I can usually make this happen reliably by pressing ^C ^D. This makes zsh at least exit with code 130, which is regarded as a failure.

It seems OK, thanks for the info!
I close the issue.


How to force LiveScript in order not to separate utility functions?

Hi,
I need to create a _design document (for CouchDB) and I want to write it in LiveScript, like so:
views:
    get-admins: (doc) ->
        if '_admin' in doc._id
            emit doc._id, 1

If the compiler would output something like
({
  views: {
    getAdmins: function(doc){
function in$(x, xs){
  var i = -1, l = xs.length >>> 0;
  while (++i < l) if (x === xs[i]) return true;
  return false;
}
      if (in$('_admin', doc._id)) {
        return emit(doc._id, 1);
      }
    }
  }
});

Then it will be all good. But instead lsc generates utility functions (in$() in this case) separately (which is for performance reasons, obviously). How can I force LiveScript put the utility functions nearby?

What's your compiler version?
on http://livescript.net/ output is as expected: the shim appears at the tail.
({
  views: {
    getAdmins: function(doc){
      if (in$('_admin', doc._id)) {
        return emit(doc._id, 1);
      }
    }
  }
});
function in$(x, xs){
  var i = -1, l = xs.length >>> 0;
  while (++i < l) if (x === xs[i]) return true;
  return false;
}

Hi @summivox;
What I need is just the opposite of your example, because in _design documents, all functions MUST be in your view function, not outside.

Perhaps consider using xs.indexOf(x) > -1 rather than in for your use-case.

Sorry I misread your question.
Just out of curiousity, is this requirement because your function is serialized (i.e. Function#toString)?
This has been a problem since Coffee times, and yea, you'll have to either embed the runtime into the serialized code or avoid using the runtime at all.


Move TEMP up one level

I think this may be a workaround to the XamlTaskFactory and CodeTaskFactory issues.  It appears that the combination of git clean and msbuild has somehow started to cause the TEMP directory to be asynchronously deleted (or at least deleted slower than before).  While msbuild is running, the TEMP dir finishes deletion, and suddenly msbuild fails to create files.  This fix does not fix the underlying issue. It's still unknown what change caused it, but it may be an Azure change.  I can repro outside of Jenkins and on a clean machine without any coreclr build ever done on it.
After making this tweak, a failure that occurred very often was not seen at all.
I am running the new version overnight on the test VM.  If it passes all the way through we should merge this.
/cc @dilijev

Sounds great! Thanks Matt! :shipit:

Fixed comment.

Saw the error again...don't merge.

@dotnet-bot test Windows x64_debug

@dotnet-bot test Windows x64_debug


Enable Guava as cache backend

What changes were proposed in this pull request?
This is a follow up of #419
Enabled Guava
Created a series of get functions in FiberCache for generic accessing
How was this patch tested?
Unit Test passed

merge this into #419


Add the ability to make HTTP requests from Squirrel.

This is still a work in progress, but is basically almost complete.
This PR aims to allow Squirrel scripts to make HTTP requests. This would allow them to do things like query APIs, send data to a server to save and more.
All HTTP request methods are supported. However, the following limitations apply:

You cannot make a request to a private network address.
You may only make a request to a hostname that resolves to an IPv4 address.

The above limitations are for security reasons. If for some reason, you need access to private network addresses or IPv6 hosts, you may start the game with -allowlocalhttp to bypass those checks.
Checklist

[ ] Bob's refactor. This PR is based on it, it needs to be merged first.
[ ] Native -> Squirrel message bridge.

Needs to be merged by EmmaM. I think it's not entirely complete but soon:tm:.

[X] Native HttpRequestHandler
[X] Squirrel functions to make an HTTP request.
[x] Prevent localhost HTTP requests unless explicitly enabled using -allowlocalhttp.

This is to prevent any potential exploit. This can be disabled for certain... usecases.

Example
I will be simplifying the functions a little bit, but for now, this is how it looks:
void function OnSuccess(int code, string body, string headers)
{
    printt(code, body, headers)
}

void function OnFailure(int error, string message)
{
    printt(error, message)
}

void function NSTestRequest()
{
    HttpRequest request = { ... }
    request.method = HttpRequestMethod.GET
    request.baseUrl = "https://northstar.tf/accounts/get_username"
    request.headers["hello"] <- "world"
    request.queryParameters["uid"] <- GetPlayerArray()[0].GetUID()
    request.contentType = "application/json"

    NSMakeHTTPRequest(request, OnSuccess, OnFailure)
}

Screenshots.

Which files did you change? I'm not looking at 156 files

FYI, we squash merge PRs and that also affects refactor, so once refactor is merged you might wanna cherry-pick your commits on top of new main and then force push to this branch to update ^^

Yeah once the refactor is in I'll try to rebase/cherrypick my commits. If that leaves this PR in chaos I'll remake it.

Which files did you change? I'm not looking at 156 files

Last 5 commits.

Getting private network request checks in. By default, those will be forbidden, unless you start the game with -allowlocalhttp as an argument. Keep in mind this leaves you vulnerable to requests being made to local services or devices within your home network that aren't very secure.

IPv6 requests will also be outright blocked for now. You can enable them with -allowlocalhttp to bypass the check.

Consider this PR feature complete. Waiting for the refactor & squirrel bridge to be merged.
I'll PR the Squirrel side, and documentation, in a bit.

Changed the branch to the refactor one. Will still need the squirrel bridge anyway.

Auto-closed by GitHub as the target branch was deleted. Change target to main and then just re-open ^^


ability for two workloads in two different namespaces to consume the same secret

I need to experiment with this idea a bit.

If two workloads have the same SVID, they will likely receive the same secret regardless of which namespace they are located.
Maybe create a demo and show that it’s possible.

done.