nnU-Netv2 pretraining and finetuning

This thread summarizes experiments related to nnU-Netv2 Pretraining and finetuning.

Pretraining and finetuning
Since training only on subjects without metal artifacts has not improved model performance much (see the comment above), I am trying Pretraining and finetuning.
Terminology:
SOURCE_DATSET - the dataset you intend to run the pretraining on -- only subjects without metal artifacts
TARGET_DATASET - the dataset you are interested in; the one you wish to fine tune on -- all subjects (including subjects with metal artifacts)
Steps
1. Prepare and download data
mkdir sci-zurich_pretraining_and_finetuning
cd sci-zurich_pretraining_and_finetuning
git clone git@data.neuro.polymtl.ca:datasets/sci-zurich
mv sci-zurich sci-zurich_rpi
# allow ** globbing
setopt globstarshort
git annex get **/*sag_T2w*

2. Reorient to RPI
for image in **/*sag_T2w*.nii.gz;do echo sct_image -i $image -setorient RPI;done

3. Create SOURCE_DATSET -- only subjects without metal artifacts
python convert_bids_to_nnUNetv2.py --path-data ~/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci-zurich_rpi --path-out ~/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci_zurich_rpi_good_subjects_only_nnunet --dataset-name tSCILesionsZurichGoodSubjects --dataset-number 525 --split 0.8 0.2 --seed 99 --good-subjects-only --path-yaml ~/duke/projects/ml_sci_seg/QCs/qc_zurich_sagittal/qc_artifact.yml  ~/duke/projects/ml_sci_seg/QCs/qc_zurich_sagittal/qc_fail.yml

4. Create TARGET_DATASET -- all subjects (including subjects with metal artifacts)
python convert_bids_to_nnUNetv2.py --path-data ~/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci-zurich_rpi --path-out ~/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci_zurich_rpi_all_subjects_only_nnunet --dataset-name tSCILesionsZurichAllSubjects --dataset-number 526 --split 0.8 0.2 --seed 99

5. Create symbolic links to $nnUNet_raw folder
ln -s /home/GRAMES.POLYMTL.CA/p118175/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci_zurich_rpi_all_subjects_nnunet/Dataset526_tSCILesionsZurichAllSubjects Dataset526_tSCILesionsZurichAllSubjects

ln -s /home/GRAMES.POLYMTL.CA/p118175/extrassd1/janvalosek/data/sci-zurich_pretraining_and_finetuning/sci_zurich_rpi_good_subjects_only_nnunet/Dataset525_tSCILesionsZurichGoodSubjects Dataset525_tSCILesionsZurichGoodSubjects

6. Pretraining on the source dataset
# TARGET_DATASET -- all subjects
nnUNetv2_plan_and_preprocess -d 526

# SOURCE_DATASET -- good subjects only
nnUNetv2_plan_and_preprocess -d 525		# this command is also necessary, although is not listed in the tutorial (https://github.com/MIC-DKFZ/nnUNet/blob/master/documentation/pretraining_and_finetuning.md#pretraining-on-the-source-dataset), othwerwise, `nnUNetv2_move_plans_between_datasets` commands fails because `nnUNetPlans.json` does not exist for 525
nnUNetv2_extract_fingerprint -d 525

# Take the plans from the target dataset and transfer it to the source
# Tutorial seems to be wrong, I had to swap 525 and 526; see [this comment](https://github.com/MIC-DKFZ/nnUNet/issues/1477#issue-1734332402)
nnUNetv2_move_plans_between_datasets -s 526 -t 525 -sp nnUNetPlans -tp nnUNetMovedPlans

# Preprocess and train
nnUNetv2_preprocess -d 525 -plans_name nnUNetMovedPlans
# `all` means https://github.com/MIC-DKFZ/nnUNet/issues/29#issuecomment-508985355
CUDA_VISIBLE_DEVICES=3 nnUNetv2_train 525 3d_fullres all -p nnUNetMovedPlans

nnUNetv2_move_plans_between_datasets -s 526 -t 527 -sp nnUNetPlans -tp nnUNetMovedPlansSC

For clarity: This command nnUNetv2_move_plans_between_datasets expects the source (i.e. -s) to be the dataset which we are want to fine-tune on (unlike what is defined as "source" in the documentation). This also makes sense because we want to move the plans from the fine-tuning dataset (i.e. the one we care about) to our pre-training dataset. Likewise, the target (i.e. -t) for the above command is the dataset which we want to use for pre-training (again, unlike what's referred to as "target" in the documentation).
A good way to remember this (and not get confused) is to know that we ultimately want the MovedPlans for the dataset we want to pre-train on. And, this MovedPlans will be available only when we move the plans from the fine-tuning (-s) dataset to the pre-training dataset (-t).

Experiment IV - Pretraining and finetuning - SC and lesions - all datasets
This experiment is similar to Experiment III (https://github.com/ivadomed/model_seg_sci/issues/43#issuecomment-1628782925). But here, we use all the datasets (sci-zurich, sci-colorado, sci-parts).
It does pretraining on all subjects using SC masks (in order to learn context about SC anatomy), then finetuning using lesion masks.
SOURCE_DATSET - the dataset you intend to run the pretraining on --  all subjects -- spinal cord masks
TARGET_DATASET - the dataset you are interested in; the one you wish to fine tune on -- all subjects -- lesion masks
Steps
1.  Reorient to RPI
cd sci-zurich_rpi
for image in **/*sag_T2w*.nii.gz;do sct_image -i $image -setorient RPI;done
cd ../sci-colorado_rpi
for image in **/*T2w*.nii.gz;do sct_image -i $image -setorient RPI;done
cd ../sci-paris_rpi/
for image in **/*T2w*.nii.gz;do sct_image -i $image -setorient RPI;done

Experiments finished --> closing.

Just to give more info on why this was closed -- we observed that there were only incremental gains (i.e. ~0.05 in Dice) with the pre-trained SC seg and fine-tuned lesion seg models compared to a single model that segmented both the SC and the lesion. Hence, in favour of having light model packaging, we proceeded with the single model.


Secret management

Use 1Password connect with a dev and prod Vault. Setup the 1Password cli to generate the 1Password- redentials.json file and to issue tokens as described here https://github.com/1Password/connect.
Set the dev/prod credentials and tokens inside the BuildBuddy secrets as well (4 in total).
Current secrets

BuildBuddy teleport user + identity
teleport-admin teleport user
PagerDuty integration key
Logz.io metrics id

TODO

[x] Install Docker in provisioner
[x] Install one password connect in provisioner
[x] Setup Telegraf logz.ip output plugin with one password connect
[x] Setup Ubuntu 2004 https://buildbuddy.slack.com/archives/CUHBFVATU/p1685021979012729?thread_ts=1684999111.495379&channel=CUHBFVATU&message_ts=1685021979.012729 for Python deps
[x] Fix failed production deploy
[x] Remove double logz ip config file
[x] Update logz.io monitoring to include env
[ ] Update bootstrap docs

Updated bootstrap docs https://github.com/mvgijssel/setup/wiki/Bootstrap-provisioner.


replace menu icon

I wanted to ask how to tweak sidemenu in order to replace menu icon (three parallel horizontal lines) with a icon of my choice.
I'm not that practical in javascript to argue it my myself.
Thanks.
By the way, great job!

done by myself


Add script to proxy pycharm debugger port into odoo container

Pycharm expects its dynamic debugger port to be reachable on <IP_ADDRESS>
on the host system. This adds a script that watches for pydevd debugger
ports and updates a proxy service accordingly

Humm... :confused: Some points:

I don't use pycharm, and we're currently on a transition to try to get all our workmates that still use it to leave it, so I'm not sure I want to maintain this... :thinking:
Can't pycharm use a port such as this one, which is used for all the other debuggers? https://github.com/Tecnativa/doodba-copier-template/blob/4b85e88858b2e56aa1be25adacdd5d9953897198/devel.yaml.jinja#L14
If both points are solved, then the script should be an invoke task instead.

i don't see how 1 could be resolved by me so 3 can also not be solved by me.
Leaves number 2:
No Pycharm can't (or not yet for more than 1,5 years). It randomizes the port and chooses an unused one, which is the reason for this script. I developed it after a short discussion on https://discord.com/channels/737652535149592587/765874032192520202 today for the OCA days. I always workarrounded the problem by using networks: *public on the odoo service in devel.yaml which disables the network isolation and was pointed out as not ideal by others (and i agree).
So i wrote this short script. As the others also used doodba with pycharm i thought this would be the right place to share it with them as this is the base of our common Odoo development.
unfortunately the whole copier and commit hook stuff doesn't work on my ubuntu 18.04 LTS as npm reports an error somwhere deep in the dependencies. so i have no real way currently of creating an invoke task. but if you decide supporting pycharm would be ok then i could investigate what's up with the npm stuff.

I have no idea about pycharm, but https://www.jetbrains.com/help/pycharm/run-debug-configuration-python-remote-debug.html says you can specify a port...

unfortunately the whole copier and commit hook stuff doesn't work on my ubuntu 18.04 LTS as npm reports an error somwhere deep in the dependencies

Open a new issue about the subject and we can discuss that, of course! :wink:

if you decide supporting pycharm

TBH that's not going to happen... :man_shrugging:
However, remember that with Copier you can have several templates applied to the same project. Check out https://copier.readthedocs.io/en/stable/configuring/#the-copier-answersyml-file
So, you can use this template to reuse all of our work, and have a separate template (tracked, say, in .copier-answers.pycharm.yml) that applies your customizations. I'll be happy to provide a link to that subtemplate here in case you do that, for those that want pycharm support.
Thus closing, as I think this is not gonna be merged anyway. I hope you understand, and thanks for your contribution. :blush:


PP-9380: Run integration tests on github actions

This PR follows the pattern of the adminusers PRs https://github.com/alphagov/pay-adminusers/pull/1283 and https://github.com/alphagov/pay-adminusers/pull/1284.

You forgot to change the
on:
  push: ....

To workflow call in this pr

@jfharden whoops, fixed!


Replace tempdir by tempfile

The former has been deprecated in favor of the latter

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+
Thanks!

:pushpin: Commit 8daf81e has been approved by alexcrichton

:hourglass: Testing commit 8daf81e1932a5d87d7717fc12c3c2da024b279ca with merge cff944b58ab3e9d3a1c68bf5b5601e27440692a6...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing cff944b58ab3e9d3a1c68bf5b5601e27440692a6 to master...


TN-1210 Patient list "Visit" column i18n

Add classification_types_enum to manual string extraction

Hello @ivan-c! Thanks for submitting the PR.

In the file portal/models/i18n.py, following are the PEP8 issues :

Line 22:1: E402 module level import not at top of file
Line 75:80: E501 line too long (81 > 79 characters)


fixing https://github.com/twitter/heron/issues/742 - can't compile fo…

…r centos

fixed python package names in Dockerfile.centos7
removed reference to HERON_GIT_COMMIT_MSG in compile-docker.sh - I couldn't find any references, and it was also causing the script to fail

That's great, thanks for the patch. I'll review this shortly. In the meanwhile would you please accept the CLA yet from here:
http://twitter.github.io/heron/docs/contributors/community/

Sure, CLA accepted!

@billonahill - I tried the changes in my branch and it works. Able to build centos7 binaries.


Feedback for docker 1.7/1.8 experimental networking features

Using this issue to solicit feedback on the exciting new networking experimental features introduced during the Docker 1.7 / 1.8 release time-frame.
https://github.com/docker/docker/blob/master/experimental/networking.md

I created a network called test using:
docker network create test
Then I ran two containers like that:
docker --default-network=test:bridge run -it --publish-service my-service1.test ubuntu bash
docker --default-network=test:bridge run -it --publish-service my-service2.test ubuntu bash
in two separate terminal windows.
I tried to ping from one container to the other using:
ping my-service1 from the second container, but it is not reachable. What is missing on my side?

@abdelrahmanhosny Couple of things.

--default-network is a daemon flag, which must be used when docker daemon is brought up.
Service Discovery code is not merged in docker experimental channel yet.
Its on its way via https://github.com/docker/docker/pull/14071

Regardless, we would like to keep this Issue for design questions, rather than discussing specific technical issues. If you have specific issues like these, please reach us in #docker-network IRC or open another issue once you confirm that it is a bug.

Excellent feature, thanks!
Since it's possible to publish a service when running a container via the --publish-service flag, it would be nice to be able to optionally deregister the service when stopping/removing a container.

A few issues.

I want to be able specify the CIDR for the bridge when I create a new bridge network.  Is there a way to pass parameters?

What are the restrictions on the name format?  For example, "_foo" is not a valid container name, but it is a valid network name?

When my docker daemon restarts, all my networks are gone.  Are those not persisted?

Hi folks,
I would like to see:
Multiple containers on the same host published under the same 'endpoint domain'
sudo docker network create srv
sudo docker run -d --name Hello --publish-service hello.srv stellaverse/hello
sudo docker run -d --name Hello2 --publish-service hello.srv stellaverse/hello
sudo docker run -d --name Hello3 --publish-service hello.srv stellaverse/hello

And running curl http://hello.srv from within any of the containers would be round-robin balanced across all available running containers.

I would like to see this extended across an entire swarm, and x-dc too.
I would also like to see same-host affinity tried first.

Thanks!

I can't try the multi-host with overlay network, having the following error:
# docker -d --kv-store=etcd:<IP_ADDRESS>:2379

WARN[0000] Running experimental build
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
INFO[0000] [graphdriver] using prior storage driver "aufs"
WARN[0000] Running modprobe bridge nf_nat failed with message: , error: exit status 1
FATA[0000] Error starting daemon: Error initializing network controller: error obtaining controller instance: failed to initialize vxlan id manager: failed to initialize bit sequence handler: 100: Key not found (/docker) [4]

What I doing wrong?

@diegomarangoni
this may be related to #14145, I met this problem at first on kernel 3.13, but it's solved now when i switch to 3.19.

@mavenugo
Hi,
I just tried the overlay over two nodes, basic setup is like below:

node-1
usr/bin/docker -d -H unix:///var/run/docker.sock -H tcp://<IP_ADDRESS>:2375 --kv-store=consul:<IP_ADDRESS>:8500 --label="com.docker.network.driver.overlay.bind_interface=eth0" &
node-2
usr/bin/docker -d -H unix:///var/run/docker.sock -H tcp://<IP_ADDRESS>:2375 --kv-store=consul:<IP_ADDRESS>:8500 --label="com.docker.network.driver.overlay.bind_interface=eth0" &

And I created overlay network called test:

node-1
root@ubuntu-swarm-1:~# docker network ls
NETWORK ID          NAME                TYPE
ecb6a9f48630        bridge              bridge
53e7cde4a447        test                overlay
7dc095d5e00f        none                null
4a78f9bd9d49        host                host
node-2
root@ubuntu-swarm-2:~# docker network ls
NETWORK ID          NAME                TYPE
58391b4faa42        host                host
ad294b290e39        bridge              bridge
53e7cde4a447        test                overlay
5e6f4b98d10a        none                null

And I started the two containers in these two nodes:

node-1
docker run -d -P --publish-service service.test centos/ssh
INFO[0181] POST /v1.20/containers/create
a5a9ea57d9522fc65b78bc6b0c617c66e17efb6fa55c3aca977d6b875746897a
INFO[0182] POST /v1.20/containers/a5a9ea57d9522fc65b78bc6b0c617c66e17efb6fa55c3aca977d6b875746897a/start
Received user event name:jl <IP_ADDRESS> 53e7cde4a447d0e07e5529da738596cfb77829612ce394a7a28d416da2cac449 7a39cb3ee96f9c8b0df2f71be8b9e7771fb4083555a47023147dabd1cd31a2b8, payload:join <IP_ADDRESS> 02:42:e7:16:4f:69
Parsed data = 53e7cde4a447d0e07e5529da738596cfb77829612ce394a7a28d416da2cac449/7a39cb3ee96f9c8b0df2f71be8b9e7771fb4083555a47023147dabd1cd31a2b8/<IP_ADDRESS>/<IP_ADDRESS>/02:42:e7:16:4f:69

node-2
docker run -d -P --publish-service service2.test centos/ssh
INFO[0924] POST /v1.20/containers/create
67d46f5acb27bceb1bd27db2c839a7e4d4e124536f22e7bdad5ca87c4211b795
INFO[0924] POST /v1.20/containers/67d46f5acb27bceb1bd27db2c839a7e4d4e124536f22e7bdad5ca87c4211b795/start
WARN[0924] Failed adding service host entries to the running container: open : no such file or directory
Received user event name:jl <IP_ADDRESS> 53e7cde4a447d0e07e5529da738596cfb77829612ce394a7a28d416da2cac449 252722b1318395c50a32675f903ad590a78f455a9c40cecbcf3f8230511f02de, payload:join <IP_ADDRESS> 02:42:aa:c6:2a:e5
Parsed data = 53e7cde4a447d0e07e5529da738596cfb77829612ce394a7a28d416da2cac449/252722b1318395c50a32675f903ad590a78f455a9c40cecbcf3f8230511f02de/<IP_ADDRESS>/<IP_ADDRESS>/02:42:aa:c6:2a:e5

but there are two problems here:
1 "-P" doesn't work, there is no port mapping, is it on purpose?
2  first container has ip "<IP_ADDRESS>", second container has ip "<IP_ADDRESS>", but they can't ping each other, it means overlay network doesn't work, what's wrong with my operation?
I noticed that there is warning when i start second container on overlay network - "WARN[0924] Failed adding service host entries to the running container: open : no such file or directory", is it because of that? how it happened?

@diegomarangoni we are working on a blog post to clearly mention all the pre-req and the configuration details. In addition to the issue with 3.13 kernel, we also have a PR opened in libkv to solve a specific problem with etcd, which got resolved in https://github.com/docker/libkv/pull/14. We will pull that fix in to libnetwork to make etcd backend work.

@wf2004081522 you are missing the --label="com.docker.network.driver.overlay.neighbor_ip in the second host, in order for Serf to join the neighbor.
We are working on an end-to-end blog post to get this cleared up.

@mavenugo
thanks very much for explanation, now containers on overlay network can communicate each other, but how about my first question? the container still can't map port with flag '-P' or '-p', is it on purpose? if so, how outside can visit the service on overlay network?

Hi,
I've create a Vagrant setup to test the docker multi host networking setup,
Its at https://github.com/eckz/docker-multihost-example
I hope that can help someone to test it and give feedback, or at least as a setup example.
This is some feedback, I hope it helps:

Configuring the neighbor_ip it's not clear, (do I need to specify only the first node?, a random node?).
Couldn't be easier just to create a list of IP's in consul, pretty much like swarm does when configured to use consul?

When defining --default-network= it's not clear that this network will be created automatically.

it would be useful to let the docker daemon to start even when the --kv-store is not accessible, (e.g. running consul inside docker ). Of course it would be checked when needed (e.g docker network ls).

I guess for now the docker client network part is missing, something like docker run --net="overlay:multihost", that would be great to test.

@eckz
I think the neighbor_ip needs to be configured on all hosts other than the first one, pointing to the ip address of the first node
If --default-network is set, it will be created automatically if not already present
You could run your kv-store directly on the host, or run a second docker daemon (with normal settings) if you wanted in the meantime
I think the behavior you are looking for is --publish-service
My own feedback:
It would be really nice, as @wf2004081522 said, to have a way to access overlay networks externally. A possible hack to solve this is starting a container to use as a proxy...
I'll continue adding to this post as I think of things...

Hi
I am trying to run the secnario at https://github.com/docker/docker/blob/master/experimental/compose_swarm_networking.md.  Setting up on AWS.  I see two errors.

when I try to run the following on Swarm-1 (my first swarm node)
docker-machine --debug create
--driver amazonec2 --amazonec2-access-key X --amazonec2-secret-key X --amazonec2-region X --amazonec2-subnet-id "X" --amazonec2-zone X --amazonec2-ami X --engine-install-url="https://experimental.docker.com" --engine-opt="default-network=overlay:multihost"
--engine-opt="kv-store=consul:$(docker-machine ip consul):8500"
--engine-label="com.docker.network.driver.overlay.bind_interface=eth0"
--engine-label="com.docker.network.driver.overlay.neighbor_ip=$(docker-machine ip swarm-0)"
swarm-1
I get the following weird error.
"Maximum number of retries (60) exceeded
docker: 'Error' is not a docker command.
See 'docker --help'."

When i try to run the "docker run busybox echo hello world" , it pulls the image down but then throws the following error
"Error response from daemon: Cannot start container 7fc95d4c287db41023c644a01c2761dafcb24b8cd3804f8f2c2d875f8dd93013: network sandbox join failed: could not add vxlan interface inside the network sandbox: failed in prefunc: failed to set namespace on link "vxlan06810e5": invalid argument"

There are some suggestions of upgrading the kernel to 3.16 or 3.19.  Can I just upgrade my swarm-0 (master) to 3.19 now or do I need to upgrade the kernel after creating the machine on AWS but before setting up swarm on master and individual nodes.

@wf2004081522 @jgkamat external access via overlay network is something that we are exploring. One of the ideas that we are trying out now is to add the container to the bridge network when the user expresses interest using the port-expose / mapping options : --expose or -P or -p. So, if you run a container with both the --publish-service option (in overlay network) and -P / -p, then that container is placed on 2 networks managed by overlay & bridge. The bridge network takes care of exposing the service via NAT and Port-mapping (just as it is done today) and the overlay network takes care of the east-west traffic between the container using the VXLAN overlay tunnel. Please try it out and let us know if that works for you.

@eckz Thanks for the feedback. @jgkamat answered a few of them.
We are exploring the possibility of moving away from the need to have an external consistent store (represented by --kv-store) and have an embedded eventually-consistent layer such as Serf that we currently use in the overlay driver. But it needs a lot of work and we will keep you posted.
Also, the --net option is a heavily discussed topic and we will have some concrete answer soon.

@rajnemani Yes. we currently have a pre-req of 3.16+ kernel in order to try the overlay driver. Your question is specific to Machine and I would ping @nathanleclaire to give a more authoritative answer.

@mavenugo Upgrading to 3.19 resolved my 2nd issue from my earlier post.  Thank you for your help.  But I still have 1st issue.  I cannot add/setup swarm-1 (additional node) to swarm.
@nathanleclaire, any thoughts on the following issue?
when I try to run the following on (my first swarm node, swarm-0 is my master)
docker $(docker-machine config swarm-1) run -d
--restart="always"
--net="bridge"
swarm:latest join
--addr "$(docker-machine ip swarm-1):2376"
"token://$SWARM_TOKEN"
I get the following weird error.
"Maximum number of retries (60) exceeded
docker: 'Error' is not a docker command.
See 'docker --help'."
Note that in my post above I gave the wrong docker command.  That command I gave is for creating the swarm-1 node using docker-machine on AWS.  That works fine.  The problem happens when I run the above docker run command that I provided in this post.
Thanks in advance for help.

@mavenugo thats a great solution! It looks like its working great right now! My only issue with it is that the IP of the container shows the overlay IP when running docker inspect <container>. I personally would prefer the external IP to show up (if running in this dual setup), and maybe the overlay IP in the 'secondary IP section'? I'm not sure if that is it's intended purpose. I have been using docker inspect to get the IP's of containers so far, but I'm not sure if that's the correct way to do so.

@mavenugo
Great job by Docker Networking team...
I was able to try out the bridge and overlay network types and basic stuff worked fine and I was able to connect containers.
Few questions:
Question 1:
As I understand endpoint and service is used interchangeably, endpoint and network are mapped 1:1, container can have multiple endpoints.
There can be 2 workflows:
workflow1:
create network
create service and attach to network
create container and attach to service and network
workflow2:
create container with service and network in 1 shot
Rather can container creation getting exposed to network option, can container attach/detach from service/endpoint and let service creation/deletion manage the network? Can we avoid specifying network while creating containers since we are anyway mentioning the service?
Question 2:
Related to previous question, can we create containers with just the network option? I think in 1 of the answers, you mention --net is widely discussed.
Question 3:
Is there a plan to share environment variables like --link option that was available earlier? Not sure if this is covered somewhere? I tried --link option with overlay, was not able to get that to work.
Thanks
Sreenivas Makam

So yesterday I watched the Docker channel video from DockerCon 2015 about Networking.
And of course I had to try it out and here I my thoughts on what I've seen.
Really glad you all figured out the right abstractions and things are starting to look usable.
At the moment when you want to connect to an overlay-network and you want to connect to the outside world you need to configure 2 things.
For example bridge and overlay.
But you can't specify both on the commandline in 1 command. This is all you get:
docker run --publish-service=test1.multihost.overlay -i -t alpine /bin/sh
or:
docker run --publish-service=test1.bridge.bridge -i -t alpine /bin/sh
It seems you can't use 2 --publish-service-flags or some combined command divided with a comma or something:
docker run --publish-service=test1.bridge.bridge,test1.multihost.overlay -i -t alpine /bin/sh
Also if you create the container with a bridge first and attach the overlay later you don't get the same behaviour as when you create the container with overlay network first and attach bridge later.
With overlay network first you get a working /etc/hosts file, the other way around you don't get that.
That is obviously kind of annoying.
If you have an application that at start up time needs to connect to something on the overlay-network and the outside world then it would probably fail because one isn't configured yet at the start of the application because you can't specify both on the commandline (maybe there is a workaround, but I don't know yet).
Also if you publish a network, you'll always have to unpublish it. While the cool thing about the default network is that all the bahaviour stays the same when just a deploy a container without any extra options. It does mean it will automatically publish and if you are not aware of what you are doing you'll get lots and lots of published networks you don't need anymore. If I'm not mistaken every single published network does generate some traffic.

Sreenivas Makam mentioned --link.
Haven't played with --link yet in this context.
But I'm not sure how much sense that would make.
Because as I understand it with overlays:
Every container connect to an overlay can talk to anything else connected to that overlay.
Also every container you deploy with an overlay will have it's published named available to all other container automatically.
So you can also choose the name: --publish-service=db.mynetwork.overlay
Not sure why I would still need --link for that, right ?

"We are exploring the possibility of moving away from the need to have an external consistent store (represented by --kv-store) and have an embedded eventually-consistent layer such as Serf that we currently use in the overlay driver. But it needs a lot of work and we will keep you posted."
Maybe I'm wrong, but I believe Serf is not a reliable message transport. If you want to do that you might want to look at the Consul code as an example on how to do that because Consul also uses Serf but in some kind of reliable fashion.
An option is to always use a KV and register the Docker host IP-address in the KV so you don't have to specify it on the commandline to find other hosts. That way it wouldn't need to specify any IP-addresses on the commandline when starting Docker just some way to connect to the KV.
Because now you have to do 2 cluster join operations. One for the KV (like Consul) and one for Docker.
Obviously as mentioned above, if Docker needs consul at start up and you want to run Consul in a container this is also kind of a weird situation. The easiest workaround is to use a 'system-docker' just like RancherOS has, basically 2 docker daemons running on the same host.

Have not tried to look at performance either. I would think vxlan, how it ended up in the kernel would be fast. But sometimes how you use it can really make things slower.
Thanks again,
Hope this thoughts are helpful.

Great job Docker networking team! Very useful feature. Have been able to successfully trial the basic overlay networking model with the guidance provided.
Have a couple of questions regarding IPAM -

By default, every network created using the overlay driver seems to be using the <IP_ADDRESS>/16 CIDR block. And an IP address is allocated to a service/endpoint by the driver at the time of service creation. How does a user specify a desired CIDR block/IP pool to the driver, instead of using the default IP pool? Is this specified on a per-network basis, or is it specified one time during initial driver configuration?

What is the longer term thinking in terms of using a customer's existing IPAM solutions/tools for IP address management? Are there any thoughts on having a pluggable IPAM module? I understand this may be too early to discuss now, but just want to get a sense for how this might evolve.

Another related question regarding IP addresses -
Now that networks have global scope, would there be a way to assign static IP addresses to some select services/endpoints on a given network?

@sridhardevarapalli Thanks for trying out and providing feedback.
Got the IPAM questions we will be adding the capability in the coming days to add multiple CIDR blocks and also the capability to choose different CIDR blocks on a per-network basis. They are not there at the moment.
Also it is popular request from many docker users to decouple IPAM from network driver so that the users can use their own custom IPAM solution while leveraging off-the-shelf network drivers. So this is something that is clearly in the roadmap.
We are also going to give some serious thought into how to provide users the capability to assign static IP address to service endpoints.
Please keep an eye on future PRs that will add these capabilities and provide feedback

@Lennie Thanks for the feedback.
This is exactly why the UI workflow is in experimental to gather feedback like this regarding publish/unpublish so we can see what works for the user and what doesn't.
For the data store, with all said and done we will use a back end distributed state mechanism which is all the more reliable and seamless to the user. Please keep an eye on more changes in this area in the coming weeks.

@mrjana I just remembered I had an other question:
What about traffic between overlay networks ? ;-)
I think in the talk it was said: very unclear at this point what we are going to do.

@Lennie By default a single network is the connectivity domain for containers on that network. The only way containers between networks can talk to each other is through the external connectivity path. This is by design :-)

Hi
I take back few of the questions I raised earlier and I have a different set of questions...
Earlier, I had thought:
endpoint and network are mapped 1:1, container can have multiple endpoints.
I think the above is incorrect, is below statement correct?
1 endpoint can have multiple networks, container can have multiple endpoints.
I tried this:
docker run --publish-service=nginx6.n6.overlay -d -p 8086:80 nginx
After this, I see the following in docker service listing(docker service ls)
798a0f56d9c8        nginx6              bridge              a6a281c6f142
da2c30af47e8        nginx6              n6                  a6a281c6f142
"nginx6" service is present in both bridge and n6 network. port exposure puts the service in bridge network, overlay network puts it in n6 network. I was able to reach the webserver from my local host.
I was not able to reach the webserver using the following approach. Not clear why.
docker run --publish-service=nginx7.n7.bridge -d -p 8087:80 nginx
The next question is related to exposing ports and linking. I assume that with container networking, we  will get away with --link option. Its not clear how we will exactly do this.
I took a simple mysql, wordpress linking as example below. options 1 and 2 are the traditional ways.
Container linking(option 1):
docker run --name some-mysql4 -e MYSQL_ROOT_PASSWORD=mysql -d mysql
docker run --name some-wordpress4 --link some-mysql4:mysql -d -p 9084:80 wordpress
Container linking(option 2):
docker run --name some-mysql3 -e MYSQL_ROOT_PASSWORD=mysql -d mysql
docker run --name some-wordpress3  -e WORDPRESS_DB_HOST=<IP_ADDRESS>:3306 -e WORDPRESS_DB_USER=mysql -e WORDPRESS_DB_PASSWORD=mysql -d -p 9083:80 wordpress
I tried something like below, but I could not connect to sql container from wordpress. Looks like I need to expose service from mysql in a different way.
docker run --publish-service=some-mysql4.n4.overlay -e MYSQL_ROOT_PASSWORD=mysql -d mysql
docker run --publish-service=some-wordpress4.n4.overlay -e WORDPRESS_DB_HOST=some-mysql4:3306 -e WORDPRESS_DB_USER=mysql -e WORDPRESS_DB_PASSWORD=mysql -d -p 9084:80 wordpress
Thanks
Sreenivas

A couple of more questions on overlays -

Can you provide more details on how end point reachability state (VTEP to MAC bindings) is discovered and propagated within a network? Do you use a flood and learn mechanism on every bridge that implements the overlay? Or is there a more intelligent way of discovering end point reachability?

I am assuming that the KV store is used only to distribute config state and not network reachability state. Is my assumption correct? A related question is - If a third party plugin (say VMWare NSX) that has a centralized controller model is used with Docker Network, then the third party plugin would be responsible for propagating network state across all the hosts. But you would still need the KV store to propagate config state across hosts. Is my understanding correct?

@rajnemani Hmm... it is an issue with the docker-machine ip command or the docker-machine config commands from the subshell.  One of them (probably config) is blowing up, could you paste the output of those commands on their own (preferably run using global -D flag for debug output) if you still are experiencing this issue?

I am using docker-hosts which does something similar by adding custom entries for each container into the /etc/hosts. What I like there is that I am able to define both the short name, but also full domain name, so service hello would be available as hello, but also as hello.example.com. So could you add a feature where we could define a domain to be appended to the service? This then allows easier migration from external to internal services and back.

Will it be possible to provide "docker  containers" on multiple hosts / VMs forming a  specific application cluster and to scale the cluster automatically ability to define a set of "docker IPs" as reserved ip for  this reserved  "cluster pool of ip addresses"  and ability to assign static IPs from this "cluster pool of ip addresses" to some specific nodes ? and ability to update  dns server dynamically  used by docker containers with each docker container being added or removed from cluster.

Some remote driver protocol feedback:

The way we refer to interfaces in CreateEndpoint and Join looks a little bit inconsistence:

CreateEndpoint response:

numeric ID key in Interfaces;

Join response:

numeric InterfaceId key in StaticRoutes section
string DstPrefix in InterfaceNames section, which implicitly joined with ID provided earlier in CreateEndpoint

Why don't we use actual interface name from the beginning, like "eth0"? It will make configuration more readable and intuitive.
It also easy to confuse these internal IDs with unix interfaces indexes in the beginning.

More on remote driver protocol:
I understand why two separate calls are necessary (CreateEndpoint and Join), but i'm not sure about the data libnetwork expects from each call:
Why libnetwork expects IP address to be part of CreateEndpoint response while routing configuration should be returned from Join?
If i have not missed anything it seems that the Interfaces information libnetwork receives from CreateEndpoint is not actionable till Join called?
In this case it would be more robust if remote driver returns as much configuration as possible from a singe call (say from Join).

@mrjana here is a new idea I had, I think there might be a better way of how startup of Docker and the new built-in overlay networking should look like:
My idea is the new built-in overlay networking should work more like a plugin.
So you should be able to configure it not only at startup of Docker on the cli, but also dynamically using the API.
That means the configuration of KV and configuration of the default networking and the configuration of the Serf peers should be able to do after startup.
You can obviously save the configuration on disk so after startup it can be restored (preferably to have it also regularly store the list of peer IP-addresses and not just one like it is usually done at start up).
Wouldn't that be a better way ?

@Lennie we are working on a a few enhancements to libnetwork so that the user does not need to setup a KV store at all and a bunch of the options that  the user is forced to provide during a daemon start will become entirely optional. Will release this to experimental when ready.

@pyakpyak The reason why we have two separate calls to CreateEndpoint and to Join is because CreateEndpoint is called when an endpoint is created and an endpoint creation is a cluster wide event. We only call the driver during this to allow the driver to allocate certain global resources like IP Addresses/Mac addresses etc.
While a Join is purely a local call i.e it only happens on the host where a container is joining the endpoint.

@mrjana any plans to eventually add encryption or at least message singing to the Serf-based protocol ?

@Lennie Yes. We will make it a secure protocol before we exit experimental and make it available for production

@mrjana thanks for the response. What do you think about my other question regarding using actual interfaces names instead of IDs?

@pyakpyak forgot to answer your other question. The reason why we don't allow the driver to provide the complete destination interface name is because the driver cannot determine this without ambiguity.
The case where this will become problematic is when a container is connected to two different networks managed by two different drivers. Now imagine if both the driver try to assign eth0 as the name for their own interface and there will be no way to resolve the conflict in libnetwork.
With the current protocol (although it's a bit convoluted) we can unambiguously provide a way for the drivers to refer to the interface that they allocated resources for.

In my opinion, It should be possible to check the interfaces available before assigning a name and to ensure uniqueness, some 1 or 2 character suffix/prefix could be added by the driver to interface name. feasible ?
From: Jana Radhakrishnan<EMAIL_ADDRESS>Sent: Wednesday, July 15, 2015 8:28 PM
To: docker/docker
Cc: Ajay Bhatnagar
Subject: Re: [docker] Feedback for docker 1.7/1.8 experimental networking features (#14083)
@pyakpyakhttps://github.com/pyakpyak forgot to answer your other question. The reason why we don't allow the driver to provide the complete destination interface name is because the driver cannot determine this without ambiguity.
The case where this will become problematic is when a container is connected to two different networks managed by two different drivers. Now imagine if both the driver try to assign eth0 as the name for their own interface and there will be no way to resolve the conflict in libnetwork.
With the current protocol (although it's a bit convoluted) we can unambiguously provide a way for the drivers to refer to the interface that they allocated resources for.
—
Reply to this email directly or view it on GitHubhttps://github.com/docker/docker/issues/14083#issuecomment-121788790.

@mrjana thank you for the response. Btw, i'm curious what is the schedule for experimental docker builds? I'm waiting for the fix i submitted recently to be available as part of the build, but seems the last docker package available for ubuntu is still from Jul 14th.

Will there be a way to assign a virtual ip to a service. For instance, 2 Load Balancer containers would share a virtual IP to avoid a single point of failure. When the first LB container (primary) goes down then the virtual IP is transferred to the second LB container (backup).

I have an experimental swarm going but can't seem to create a network.  This happens:
[ec2-user@ip-172-31-47-154 ~]$ docker network create -d overlay intc
Error response from daemon: 404 page not found
I'm guessing the "not found" is from an attempt to access a key/value store that the documents say the overlay driver needs.  Since all my nodes are already set up I don't need Machine to make them for me but the only documents for wiring in the key/value store are through machine.  Do I have to scrap everything just so Machine can spin it back up and wire the consul store in?  Or is there I way I can point the swarm nodes I have to the stand-alone node with the store on it?
Thanks,

@McAlister Swarm does not support docker experimental features.
As such, 404 is happening because swarm does not implement the docker network API endpoints.

@cpuguy83 thats rather confusing then.  This is a red herring?
https://github.com/docker/docker/blob/master/experimental/compose_swarm_networking.md

@McAlister You'll notice the example is not using the top-level networking API's, it's only using docker run and docker engine handles the rest.
docker network create, however, is a full-blown top-level API command that swarm does not implement, because it's not part of docker engine's stable release.

@cpuguy83 I think I found the proper set of instructions:
https://github.com/docker/libnetwork/blob/master/docs/overlay.md
Of course now I get to curse at EC2 for being on kernel 3.14 ... /shakes fist in the general direction of of the Oregon datacenter.

@McAlister You should be able to upgrade the kernel on your machines by changing the repository lists in /etc/apt/sources.list (to utopic?) and apt-get installing the new kernel. If you use 14.04:
sed -i 's/trusty/utopic/g' /etc/apt/sources.list
apt-get update
apt-get install linux-image-extra-3.16.0-41-generic

as root

@jgkamat Amazon EC2 boxes are a bit less cooperative than that ... it is possible to change their kernel but its less straightforward a yum update.
https://aws.amazon.com/blogs/aws/use-your-own-kernel-with-amazon-ec2/
If 3.16 isn't “EC2 compatible” I'll have to bake cookies for our yum repo guardian to convince him to add the rpm for the 3.16 kernel to the corporate repository where my on premise boxes can see them ... since for security reasons we aren't allowed to talk to public repos.
Glory in the freedom of open source work you lucky people  =).

For reference the Debian folks have put a free ec2 ami in the Amazon Marketplace that grubs you up to kernel 3.16.0-4  Image name:
Debian GNU/Linux 8 (Jessie)
The only others I found were $$$ images from Oracle and Redhat.  When you release you might add a list of docker-friendly ami's to a faq somewhere for people deploying docker into AWS.

Hrrmmm ... I'm seeing things in etc/hosts but the traffic doesn't seem to be getting from point A to point B.
admin@ip-172-31-33-164:/docker$ docker network ls
NETWORK ID          NAME                TYPE
8d03f93006e6        intc                overlay
d856ce91c4e8        none                null
5ea54da5e8b6        host                host
dad21bbeb170        bridge              bridge
admin@ip-172-31-33-164:/docker$ docker service ls
SERVICE ID          NAME                NETWORK             CONTAINER
f9a0d1c4f87d        ec                  intc                61c6cd06c88c
0123effc0634        la                  intc                986d3059dbab
ec.intc is on host 1 and la.intc is on host 2
admin@ip-172-31-33-164:/docker$ consul members
Node              Address             Status  Type    Build  Protocol  DC
ip-172-31-33-164  <IP_ADDRESS>:8301  alive   server  0.5.2  2         dc1
ip-172-31-44-7    <IP_ADDRESS>:8301    alive   client  0.5.2  2         dc1
ip-172-31-34-176  <IP_ADDRESS>:8301  alive   client  0.5.2  2         dc1
Exec into either one and I see the proper etc/hosts file:
Host 1:
admin@ip-172-31-33-164:/docker$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
61c6cd06c88c        busybox             "top"               15 minutes ago      Up 15 minutes                           mock-ec
admin@ip-172-31-33-164:/docker$ docker exec -it 61c6cd06c88c /bin/sh
/ # cat /etc/hosts
<IP_ADDRESS>      61c6cd06c88c
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
<IP_ADDRESS>      la
<IP_ADDRESS>      la.intc
<IP_ADDRESS>      ec
<IP_ADDRESS>      ec.intc
Host 2:
admin@ip-172-31-44-7:/docker$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PO
RTS               NAMES
986d3059dbab        busybox             "top"               14 minutes ago      Up 14 minutes
mock-la
admin@ip-172-31-44-7:/docker$ docker exec -it 986d3059dbab /bin/sh
/ # cat /etc/hosts
<IP_ADDRESS>      986d3059dbab
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
<IP_ADDRESS>      la.intc
<IP_ADDRESS>      ec
<IP_ADDRESS>      ec.intc
<IP_ADDRESS>      la
However, they can't ping each other and if I open a socket on one the other can't write to it.
Host 1:
/ # nc -l -p 4444
Host 2:
/ # telnet ec.intc 4444
asdfsadf
asdfsdaf
and nothing happens on host 1.
If i open another shell on host 1 like so:
admin@ip-172-31-33-164:~$ docker exec -it 61c6cd06c88c /bin/sh
/ # telnet ec.int 4444
asdfasd
asdfsadf
asdfsdf
^]
then I see my listener on host 1 output my asdfasd as expected.
Host 1:
/ # ping ec.intc
PING ec.intc (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.034 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=0.031 ms
Host 2:
/ # ping ec.intc
PING ec.intc (<IP_ADDRESS>): 56 data bytes
^C
--- ec.intc ping statistics ---
381 packets transmitted, 0 packets received, 100% packet loss
If I create another container on Host 1 things work as expected.
Host 1:
admin@ip-172-31-33-164:/docker$ docker run -itd --name mock-aa --publish-service=aa.intc.overlay busybox top
047d242eea177c2e7f2e6d0e3c36912d17e8baba6f4f3948e694a99522d2fbe2
admin@ip-172-31-33-164:/docker$ docker service ls
SERVICE ID          NAME                NETWORK             CONTAINER
f9a0d1c4f87d        ec                  intc                61c6cd06c88c
0123effc0634        la                  intc                986d3059dbab
95a325181ae6        aa                  intc                047d242eea17
admin@ip-172-31-33-164:/docker$ docker exec -it 047d242eea17 /bin/sh
/ # nc -l -p 4444
So I'm listening on mock-aa on HOST 1
then in another window in the ec-intc container:
admin@ip-172-31-33-164:~$ docker exec -it 61c6cd06c88c /bin/sh
/ # telnet aa.intc 4444
asdfsdf
asdfasdf
asdfsdf
^]
and I see the asdfasdf appear in the aa-intc container also on host 1 in the shell where it is listening
So if they are on the same host all is good.  Across hosts ... not so much.  All the amazon hosts in the test are in the same security group and all the tcp ports are open between computers within that group.  /etc/hosts files on all the containers update appropriately when I add containers in or take them out.  'docker network ls' and 'docker service ls' commands likewise are staying nicely in sync between all hosts in the network.
I'm not entirely sure how to debug this so I'll sleep on it.  I find it very intriguing that the telnet command appears to connect but doesn't get there.  I would expect a "connection refused" or a "trying ec.intc ...." that eventually times out.  I've never seen telnet appear to connect but not actually connect before.

@McAlister Any update on the connectivity issue? I'm also trying to get Docker networking running on AWS EC2.
See https://gist.github.com/felixrabe/bcc8f67d6c262443d2ef for my work-in-progress on a provisioning script. It's mostly Bash.

@McAlister I seem to remember that I once got two Docker containers successfully pinging each other on two AWS hosts, but I'm stuck reproducing how I did that right now.

I figured the missing part thanks to @mrjana on IRC (opening UDP port 4789 for VXLAN) and rewrote my provisioning script to docker-machine: https://gist.github.com/felixrabe/cf076655f1d0235e28a3 (this works)

@felixrabe Sorry I didn't respond faster, The UDP port makes sense, I'll try it tomorrow and let you know.  Thank you for digging into it too.

I am trying to setup containers which need to talk to some  external servers in meshed topology for example I have servers s1,s2 and s3 with their Ip addresses being <IP_ADDRESS>, <IP_ADDRESS> and <IP_ADDRESS> and 3 docker containers say c1,c2 and c3 on 3 separate servers s4,s5, and s6 with server IPs being <IP_ADDRESS>, <IP_ADDRESS> and <IP_ADDRESS>.  Containers are using overlay driver and ip associated with containers c1,c2 and c3 are <IP_ADDRESS>, <IP_ADDRESS> and <IP_ADDRESS> respectively. What routing mechanism to be used so that all 3 servers s1,s2, and s3 can talk to any container c1, c2 or c3 ?
Do I need to have  a route to network 172.17 vlan with one of the server hosting container acting as default gateway to container network   or any other mechanism is suggested . So far I am able to establish connectivity only to single container ip from external server by adding route add net command with the container hosting node acting as gateway other containers are not reachable from external nodes.

What is the process of allocating IP addresses to containers when they are launched on different hosts. How to ensure unique IPs across hosts. When launching containers on two different hosts, I get the same ip address <IP_ADDRESS> allocated with default setup.

A command to retrieve the types of network types available during creation would be useful.
e.g.
docker network create --help
 # Available Network Types:
 #    - bridge
 #    - host
 #    - weave

or
docker network list-types
# Available Network Types:
#     - bridge
#     - ...

This should probably be closed since #16645 was merged.

Agreed, let's close this (but feel free to comment after it's closed)


fix(core) svg usage alongside  tag

fix(core) svg usage alongside  tag
Using fix specified here: https://github.com/angular/angular.js/issues/8934#issuecomment-56568466
Fixes #1224, Fixes #1230

My Travis is cranky - I deleted my old repo by the same name. It keeps trying to checkout the version under the old hash.
This is a simple change though so let me know if it breaks anything.

@Wuntenn the change passes the tests but can you actually also include all the work on the other PR? because I believe that it also had this exact change, including changing the actual tests for the / URL.
Or, can you possibly go ahead and remove the  tag along with this PR? I wonder how that would work.

I just saw the commit that you mentioned, including the part that uses the same fix. I'm still newb Lirantal just trying to help out and learn.
I'll remove this PR, and have a stab at it. I'm not sure when I'll get chance to work on fixing it. I'm a bit squeezed for time right now.


Pane grid widget

This PR introduces a new widget: PaneGrid.
A PaneGrid consists of a collection of panes, which are distributed using either vertical or horizontal splits to completely fill the space available. This distribution of space is common in tiling window managers (like awesome, i3, or even tmux).
The new PaneGrid features:

Vertical and horizontal splits
Tracking of the last active pane
Mouse-based resizing
Drag and drop to reorganize panes
Hotkey support
Configurable modifier keys
API to perform actions programmatically (split, swap, resize, etc.)

I believe this widget can be very useful if you want to allow your users to dynamically customize the layout of the application. For instance, it could be used to build a three-pane interface, a dashboard with different kinds of data visualization, etc.
Additionally, I have:

Added a couple of new variants to MouseCursor for the new resizing interactions.
Moved some reusable keyboard types to iced_core, as we will need them in iced_web soon enough.
Implemented Subscription::with, which can be used to move external data into a subscription.

As always, I have created an example (pane_grid) to showcase all the current features of the new widget.

Holy moly! This is awesome!


Fix array types in polar area charts.

Fixes https://github.com/chartjs/Chart.js/issues/6453.

Example for testing purposes: https://jsfiddle.net/ekc83w5f/.

It'd be better to combine this PR with https://github.com/chartjs/Chart.js/pull/6454. In order to keep the docs consistent with each other, if we make a change to the way we describe scriptable and indexable options we should change the docs for all the chart types at once.
I'm going to close this PR to make sure all the discussion on this topic stays in a single place (i.e. on https://github.com/chartjs/Chart.js/pull/6454)

@benmccann I guess, you mean https://github.com/chartjs/Chart.js/pull/6450, https://github.com/chartjs/Chart.js/pull/6454 is this pr...

Yes, thanks. Sorry for the confusion


feat: use parsers for .hbs files

Fixes #1052 by adding overrides to use JSON and babel parsers for *.json.hbs and *.js.hbs files. If this is too complex of a solution we can simply ignore the files from prettier

works great 👍🏼


Get storage permissions & remove old packages

[x] Remove mediastore & filesystem modules
[x] Add better support for Java usage
[x] Add Bill of Material (thanks to @ghostbear)
[x] Add StoragePermissions.getPermissions method

gh pr checkout 77
<EMAIL_ADDRESS>


The link to the Baidu's main research page is broken

This link mentioned in the main readme file is broken:
http://research.baidu.com/bringing-hpc-techniques-deep-learning/

The latest usable copy on archive.org appears to https://web.archive.org/web/20180421011035/http://research.baidu.com:80/bringing-hpc-techniques-deep-learning/


New Relic: Mindglass

Effect:
Gaining clarity deals 5 damage to all enemies.
Gaining 10 clarity in the same fight deals 500 damage to all enemies.

Notes for self since I'm at work:

Add a power for Mindglass (see Pennib)
Check how flash works and see if determining when to call beingLongPulse can occur after the flash timer is set to 0
make sure relic stops pulsing if it fails kill upon activation. (for example awakened one phase one)


About Jenkins build failure after adding  ffimageloading to the project

Thanks for great Plugin ffimageloading.  When compiling in Visual Studio its working fine but when we use MSBuild environment Its giving the namespace not found in assembly error in xamarin forms  from which  unable to build the application on jenkins.

We use msbuild on appveyour just fine. I'll need some more info to hep you.
https://github.com/luberda-molinet/FFImageLoading/blob/master/MakefileAll.bat
Do you call this before building:
nuget restore -MsbuildPath "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin"
dotnet restore

Thanks for the reply. Ya I have tried using nuget restore and dotnet restore is implicitly called in MSBuild Still the same error happens even I have tried to call the dotnet restore explicitly through build tools in visual studio.

Did you try newest 2.2.25? It may be this (which was fixed already): https://github.com/luberda-molinet/FFImageLoading/issues/798

Ya It worked


[xkb] do not install in existing xkb/symbols/[locale] files

xkalamine installs layouts in xkb/symbols/[locale] files for historical reasons, and because let’s face it : writing
setxkbmap fr -variant lafayette

… is the coolest thing ever. ^_^
But that relies on some clunky text delimiters around every layout definition in those files, which is a very debatable design decision to say the least ; and it does not survive to an XKB upgrade, which is a pity.
A much saner approach would be to put all kalamine layouts in an xkb/symbols/kalamine subdirectory and associate those layouts to the proper locale in the xkb/rules/{base,evdev}.xml files. And selecting a layout on XOrg would become :+1:
setxkbmap kalamine/lafayette

And an intermediate approach would be to put all kalamine layouts directy in xkb/symbols buf forbid to overwrite non-kalamine layouts, which implies keeping the clunky text delimiters. We’d still avoid the loss of our layouts on an XKB upgrade, and the layout selection would become :
setxkbmap lafayette
setxkbmap lafayette -variant 101

… which looks pretty darn cool, too. ^_^

@fabi1cazenave  There may be a hybrid option :

Put the layouts in their own files in kalamine/
The XML uses these files (invisible for the user)
You may additionally add a variant in the locale that just include the corresponding section from the kalamine/* files. So you can use e.g. setxkbmap fr -variant lafayette as well as the canonical setxkbmap kalamine/lafayette.

This way your configuration via DE GUI tools should survive XKB update (being based on the XML file, it points to kalamine/* files), while only the aliases in the system files are deleted.
With this solution your hard work on the locale file was not all in vain!


New version: taers232c.GAMADV-XTD3 version 6.72.12

Created by 🥟 Dumplings in workflow run #776.
Logs
Updated: 6.72.11 → 6.72.12
Cannot validate argument on parameter 'ChatID'. The argument is null, empty, or consists of only white-space characters. Provide an argument that contains non white-space characters, and then try the command again.
Submitting WinGet manifests
Cannot validate argument on parameter 'ChatID'. The argument is null, empty, or consists of only white-space characters. Provide an argument that contains non white-space characters, and then try the command again.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！


Api freezes if character doesn't exist.

I have the following code
Character x = await client.GetCharacterAsync(realm, charactername, CharacterFields.All);
if (x.Name == null)
{
Console.ForegroundColor = ConsoleColor.Red;
Program.Log($"Error retrieving {charactername}'s information.\nThey may not be level ten yet.\nProceeding to next character...");
Console.ForegroundColor = ConsoleColor.White;
Stats.Levels.lowlevel += 1;
Runtime.errorcharacters = Runtime.errorcharacters + $"Name: {charactername}; Realm: {realm}; Account: {account}\n";
return;
}
It works perfectly on characters that are at least level 10....
But nothing happens if the character is under level 10, or has been deleted. It just sits there. Mine sat there for over 10 minutes, when I want the api to trigger the if statement if the character doesn't exist on the armory.
Thanks.

It's also doing this if the character has other information that is empty and I try to access it.
For example
Program.UpdateSheet($"K{cell}", $"{x.Professions.Primary[1].Name}({x.Professions.Primary[1].Rank})", $"profession 2");
Doesn't give an error or return a null value (preferable)... it just sits there.
But if the character has professions, it works just fine.

Okay, so I got it working by changing it to a try catch
try
{
x = await client.GetCharacterAsync(realm, charactername, CharacterFields.All);
}
        catch
        {
            Console.ForegroundColor = ConsoleColor.Red;
            Program.Log($"Error retrieving {charactername}'s information.\nThey may not be level ten yet.\nProceeding to next character...");
            Console.ForegroundColor = ConsoleColor.White;
            Stats.Levels.lowlevel += 1;
            Runtime.errorcharacters = Runtime.errorcharacters + $"Name: {charactername}; Realm: {realm}; Account: {account}\n";
            return;
        }

Just an FYI, a new future version will no longer require a try/catch wrapper.

@AussieEevee commit ddc53bd has the changes I was referring to earlier, expect a new nuget package soon too.


Add friendly name to output

Handy as often one will create multiple monitors for the same URL, using the "Friendly Name" to differentiate them.

Been almost a year & a half, methinks this isn't getting merged.  Closing.


Omnisharp's mono tries to use system mono lib instead of bundled mono

I get this output when OmniSharp tries to start up in vim:
channel 0 open: 'dyld: Library not loaded: /Library/Frameworks/Mono.framework/Versions/6.6.0/lib/libintl.8.dylib'
channel 0 open: '  Referenced from: /Users/Knoble/.cache/omnisharp-vim/omnisharp-roslyn/bin/mono'
channel 0 open: '  Reason: image not found'
channel 0 open: '/Users/Knoble/.cache/omnisharp-vim/omnisharp-roslyn/run : ligne 28 : 54423 Abort trap: 6           "${mono_cmd}" "${omnisharp_cmd}" "$@"'

I can confirm that running the run script and the bin/mono fail, so this may be more for OmniSharp/omnisharp-roslyn.
I have an (old?) mono install floating around:
+λ ls /Library/Frameworks/Mono.framework/Versions/5.4.1/
Commands/   bin/        etc/        lib/        share/
VERSION     docs/       include/    man/        updateinfo

Regardless, I'm not sure why this mono is searching /Library/Frameworks if it was supposed to be fully bundled?
After installing an up-to-date mono with brew, the bundled mono still looks in /Library/Frameworks where the new version is not.
(From OmniSharp/omnisharp-vim#556.)

Yea, I am running in to the same issue. It happens when I am running version 1.21.10 of the C# extension in vscode (ms-vscode.csharp). If I downgrade everything seems to be fine.

@JoeRobich isn't there something missing in the bundle here? https://github.com/OmniSharp/omnisharp-roslyn/pull/1679/files
libintl.8.dylib?

I am having the same issue as @DwaynesWorld with vs code:
dyld: Library not loaded: /Library/Frameworks/Mono.framework/Versions/6.6.0/lib/libintl.8.dylib

I am running into the same issue. I downgraded to 1.21.9 by the moment. Is there any update on this?

aa discussed elsewhere, this is caused by a mono bug.
the simplest workaround for now is to install mono 6.6.0 so that the path can be found.

@filipw,
I've exactly the same issue on a macOS machine. But the problem appeared in somewhat mysterious way.
I don't know what changed in my system and why. But obviusoly something should be happened!
Hope I can fix installing latest mono with brew.

aa discussed elsewhere, this is caused by a mono bug.
the simplest workaround for now is to install mono 6.6.0 so that the path can be found.

Thanks @filipw :)

@enigmaturing , I used hope because I was not sure to have success with this.
In part I was right. I've in this moment installed mono with brew. Problem disappeared, but in all my test projects OmniSharp doesn't resolve any symbol (even System.Object).
No dotnet restore worked.

@enigmaturing , I used hope because I was not sure to have success with this.
In part I was right. I've in this moment installed mono with brew. Problem disappeared, but in all my test projects OmniSharp doesn't resolve any symbol (even System.Object).
No dotnet restore worked.
I'll file an issue if I can't solve.

@gsscoder I guess you can also downgrade to 1.21.9 by the moment, until you find a solution for that

I've exactly the same issue on a macOS machine. But the problem appeared in somewhat mysterious way.
I don't know what changed in my system and why. But obviusoly something should be happened!

VS Code updates extensions automatically and this behavior is specific to C# extension 1.21.10. So it must have updated for you.

@filipw, same think I've then thought...
I didn't solved what happens with symbols, sorry I've to bother you with an new isuee...

Can't say if this is a good solution or how it might affect your system but I resolved with brew install mono

I've exactly the same issue on a macOS machine. But the problem appeared in somewhat mysterious way.
I don't know what changed in my system and why. But obviusoly something should be happened!

VS Code updates extensions automatically and this behavior is specific to C# extension 1.21.10. So it must have updated for you.

That was actually what happened to me. I fixed it by downgrading to 1.21.9

I had the issue on 1.21.10 on macOS. I fixed it by running brew install mono.

What's the timeline on the fix for this? It has to do with the 1.21.10 update on my system.

this is resolved in 1.21.11 in prerelease https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.21.11

the minimum required Mono version is 6.6.0.
OmniSharp looks at global mono if you have it installed on your machine because it would prefer to use that msbuild instead of the bundled one.
TL;DR: How should I read the above statement?

Longer version:
I'm hunting down why omnisharp isn't formatting my cs code in VSC, noticed I was getting this error:
[ERROR] Error: command 'dotnet.test.run' already exists
and found this link
That set me on a journey of discovery regarding mono -- since updating it was noted as a "good thing" for resolving the error.
And here I am.
Noob question: is it "good" (from a VSC perspective) to install mono on Ubuntu separately? Or "bad"... What I ended up doing was installing dotnet 3.1.101 to see what that would accomplish. Now my error message is gone. But I'm wondering if I should still install mono on my own.
And... yeah, my cs files still don't format. I don't know what I'm doing wrong there (or what's wrong on my machine) but that story for another day.

TL;DR: How should I read the above statement?

if you have global Mono 6.6.0+, OmniSharp will use it and should give you better support when working with non-.NET Core projects.

[ERROR] Error: command 'dotnet.test.run' already exists

this error is not related to the issue you are writing in 😀 normally when this happens, please grab the OmniSharp log (view -> output -> select omnisharp) and also any errors from VS Code window log (Help -> Toggle Dev Tools). Normally this error is related to conflict with other extension or unsuccessful start/restart.

And... yeah, my cs files still don't format.

if that's the case please open a new issue here https://github.com/OmniSharp/omnisharp-vscode and fill in the details of the issue template too (repro steps, Omnisharp log, list of extensions you have installed and so on), and hopefully we can help

this error is not related to the issue you are writing in

Correct. Apologies, it was a (probably unneeded) explanation of how I got to this issue.

if that's the case please open a new issue

Actually, I did. And as I was logging it up, the issue went away. I swear there are Heisenbug issues where Omnisharp is concerned. But if I say more here, I'll just clutter this thread even more. :)

These directories exists: /home/iron-e/Programming/ACTIVE/reef/and ~/.omnisharp/Roslynator/src/Core/bin/Debug/netstandard2.0/Roslynator.Core.dll.
For some reason the paths are been merged in one. So the path isn't valid.

Yeah. I notice that the first part of the path (/home/iron-e/…) is always equal to the root_dir, and I've tried this on a couple of other projects just to verify. It seems that now that the root_dir is being correctly resolved, it is being used as the context for all paths rather than just some of them.

I have a roslyn extension in the folder ~/.omnisharp/… as well.

Is this OmniSharp/omnisharp-vscode#2369 related?

I don't think so… Roslynator has worked for me in VSCode and still works in coc.nvim. Seems to be something the nvim_lsp repo is mistakenly prepending.
If that's true, it would also explain why it can't find the netstandard or core .dll files— it'd be looking in root_dir instead of the root of the filesystem.

I'm still not sure if this is an issue with nvim-lsp or omnisharp-rolsyn, but I suppose a good way to tell would be if ALE has the same problem.
Edit: I took some time tonight to try and figure out what was happening. I figured out that the error I was seeing is a red herring, as omnisharp-vim throws a similar one when loading a .cs file.
I didn't manage to figure out what was going wrong, but I figured out a workaround:

dotnet clean && dotnet build from the root_dir of the project (fixed a slew of errors for me, but not all of them)
Make sure there is at least one real error in your code when loading up (and save after putting it there).

For example, I took out the first letter of the visibility modifier of some random method.

Then, the unwanted messages will be gone. Unfortunately, it seems that this introduces a new bug: the last set of virtual text that was present will remain there until a new error appears (note that this is completely unrelated to nvim-lua/diagnostic-nvim).


high response region question

In the RA-CNN paper, the author claimed that they pretrained apn model by selecting squares with the highest response value in the last conv layer. Did you do the same in your impl ?
def high_response_region(network, inputs): //     cnn = network.cnn //     features = cnn(inputs).view(inputs.size[0], 512, 7, 7) //     square_norm = (features * features).sum(dim = 1)     unit = torch.Tensor([0, 0, 1])     return torch.stack([unit] * inputs.size(0))

    hello,I am very interested in your work on RA-CNN Implemented  by pytorch, but as a newbie, how do I prepare to train the dataset, I have already got the entire dataset of Compcars, you have not explained clearly in Readme. Training, can you tell the details, thank you!


Migrate tests from enzyme to testing-library\react

I suggest that we just migrate from enzume to testing-library in this PR and not update React version now. This allow us to make a cherry-pick to 20.2 if we will decide to not support react 17 in 20.2.
Also we can just make a tasks to test latest and next react versions.


always lose intellisense after serveral minutes' coding

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:07:25.676Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

githistory
don
0.2.3

docthis
joe
0.4.8

vscode-csscomb
mrm
5.1.0

sass-indented
rob
1.4.1

gitblame
wad
2.1.0

(3 theme extensions excluded)

Steps to Reproduce:

open workspace
start webpack compile and node debugger
coding for serveral minutes
tada~ no intellisense

Reproduces without extensions: Yes
Still the same result with no extension working. Maybe it's caused by too many files? My workspace contains over 2000 files (exclude /public /node_modules and so on...).

Hey, sorry this fell off my radar.
Are you still running into this with VS Code 1.18?

Problem occured less than before, but still on

Please try collecting the TypeScript server logs to see if that has any leads:

Add "typescript.tsserver.log": "verbose" to your user settings and restart VSCode.
Reproduce the issue
Run the Typescript: Open TS Server log command in vs code and look in the tsserver.log file in the opened directory

Look near the end of the logs for errors or long running requests. If you are able to share the logs, I can also look through them to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

Closing as we cannot investigate this without more information. Please let me know if you are able to collect the TS server logs


How should I refer when the two training stages have converged？

Dear Author :
I really like your great contribution and try to utilize this framework to my task.  But when I respectively train the local and global adapters, I do not know how to refer when the two training stages have converged? Since my sub-task needs pixel level performance, it is timely and have poor performance at two stages. So I would like to know what is the respective final performance of this two adapters before the joint inference?

Hello, did you solve this problem? I would also like to know what the respective final performance of this two adapters looks like，my training loss is not decreasing.

Dear Author : 亲爱的作者： I really like your great contribution and try to utilize this framework to my task. But when I respectively train the local and global adapters, I do not know how to refer when the two training stages have converged? Since my sub-task needs pixel level performance, it is timely and have poor performance at two stages. So I would like to know what is the respective final performance of this two adapters before the joint inference?我真的很喜欢你的巨大贡献，并尝试利用这个框架来完成我的任务。 但是，当我分别训练本地和全局适配器时，我不知道如何引用两个训练阶段何时收敛？由于我的子任务需要像素级的性能，所以它是及时的，并且在两个阶段的性能都很差。所以我想知道这两个适配器在联合推理之前各自的最终性能如何？
Hello, did you solve this problem? I would also like to know what the respective final performance of this two adapters looks like，my training loss is not decreasing.

Dear Author : 亲爱的作者： I really like your great contribution and try to utilize this framework to my task. But when I respectively train the local and global adapters, I do not know how to refer when the two training stages have converged? Since my sub-task needs pixel level performance, it is timely and have poor performance at two stages. So I would like to know what is the respective final performance of this two adapters before the joint inference?我真的很喜欢你的巨大贡献，并尝试利用这个框架来完成我的任务。 但是，当我分别训练本地和全局适配器时，我不知道如何引用两个训练阶段何时收敛？由于我的子任务需要像素级的性能，所以它是及时的，并且在两个阶段的性能都很差。所以我想知道这两个适配器在联合推理之前各自的最终性能如何？

Hello, did you solve this problem? I would also like to know what the respective final performance of this two adapters looks like，my training loss is not decreasing.

Dear Author : 亲爱的作者： I really like your great contribution and try to utilize this framework to my task. But when I respectively train the local and global adapters, I do not know how to refer when the two training stages have converged? Since my sub-task needs pixel level performance, it is timely and have poor performance at two stages. So I would like to know what is the respective final performance of this two adapters before the joint inference?我真的很喜欢你的巨大贡献，并尝试利用这个框架来完成我的任务。 但是，当我分别训练本地和全局适配器时，我不知道如何引用两个训练阶段何时收敛？由于我的子任务需要像素级的性能，所以它是及时的，并且在两个阶段的性能都很差。所以我想知道这两个适配器在联合推理之前各自的最终性能如何？

Hello, did you solve this problem? I would also like to know what the respective final performance of this two adapters looks like，my training loss is not decreasing.

Not yet. I have moved back to original ControlNet. Maybe you could try some other new open-source works


Terminal memory leak

Terminal references are retained on the renderer side after being destroyed
Upstream: https://github.com/xtermjs/xterm.js/issues/1341

I don't know if it is related, when I clone https://github.com/JakeWharton/butterknife.git, and run .\gradlew assembleAndroidTest, vs code will not responding after some time, happens every time.

@gengjiawen definitely not related to this issue, this is a fairly small memory leak where the terminal JS objects aren't being released when a terminal is killed.

It's more likely a problem with the file watcher https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afile-watcher

This should be fixed now, you can verify using the heap profiler in devtools, see https://github.com/xtermjs/xterm.js/issues/1341#issue-306690923

Fixed in https://github.com/Microsoft/vscode/commit/f6e82b7ce8f802e93819467ef961188589789c71, the majority of the work for this was done upstream https://github.com/xtermjs/xterm.js/pull/1525

To clarify on repro steps:

Open several terminals
Open devtools
Go to memory tab
Record a snapshot
Search the snapshot for "Terminal", you should see an entry named "Terminal"
Close all the terminals
Record another snapshot
Search the snapshot for "Terminal", you should not see an entry named "Terminal"


Oh no, Org Check had an error!

Describe the bug
While we are trying to roles and role hierarchy we are getting the error  Oh no, Org Check had an error!
To Reproduce
Install org check and navigate to roles tab
Oh no, Org Check had an error!

Hi Team any update on this @VinceFINET

Do you have more information like an error stack message?
What do you see in the browser console?
You need to give me more information about your error.

Hi Team,
Please find the below error which I have seen in the UI after I clicked on
Roles in the Org check . Any further information is needed . Please find
the stack message below
Stack:
INVALID_SESSION_ID: This session is not valid for use with the REST API
at r.getError
(/resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:72641)
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:71009
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229493
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229521
at MutationObserver.o
(/resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:104504)
[image: image.png]
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 7, 2024 at 10:48 PM Vincent FINET @.***>
wrote:

Do you have more information like an error stack message?
What do you see in the browser console?
You need to give me more information about your error.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#issuecomment-2098939249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYNFDKQGYERYVE5WJALZBEEGDAVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYHEZTSMRUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Team,
Could you please confirm if we have any update on the same .
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Wed, May 8, 2024 at 1:05 AM Varun Kumar Yerraguntla <
@.***> wrote:

Team please find the help article if this is some thing related to
https://help.salesforce.com/s/articleView?id=000387018&type=1
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 7, 2024 at 10:59 PM Varun Kumar Yerraguntla <
@.***> wrote:

Hi Team,
Please find the below error which I have seen in the UI after I clicked
on Roles in the Org check . Any further information is needed . Please find
the stack message below
Stack:
INVALID_SESSION_ID: This session is not valid for use with the REST API
at r.getError
(/resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:72641)
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:71009
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229493
at /resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:229521
at MutationObserver.o
(/resource/1715036552000/orgcheck__OrgCheck_SR/js/jsforce.js:1:104504)
[image: image.png]
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 7, 2024 at 10:48 PM Vincent FINET @.***>
wrote:

Do you have more information like an error stack message?
What do you see in the browser console?
You need to give me more information about your error.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#issuecomment-2098939249,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYNFDKQGYERYVE5WJALZBEEGDAVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJYHEZTSMRUHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @VinceFINET Any update on the same. We are awaiting your reply as it is preventing us to run org check on customer org

The link you provided refers to connected apps.
Org Check is not using such settings.
It gets the user access token from Visualforce directly.

Thank you. But please let me know how to resolve the error that we received.
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Mon, 13 May 2024 at 2:04 PM, Vincent FINET @.***>
wrote:

The link you provided refers to connected apps.
Org Check is not using such settings.
It gets the user access token from Visualforce directly.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#issuecomment-2106970923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYLVS6NR4RFBPKUKN53ZCB3K7AVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWHE3TAOJSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Team,
Any update on this ? We have dependency on the org check to perform Annual
Technical Health Review . Could you please prioritize it and let us know if
any further assistance is required.
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Mon, May 13, 2024 at 4:27 PM Varun Kumar Yerraguntla <
@.***> wrote:

Thank you. But please let me know how to resolve the error that we
received.
Regards,
Varun Kumar
Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Mon, 13 May 2024 at 2:04 PM, Vincent FINET @.***>
wrote:

The link you provided refers to connected apps.
Org Check is not using such settings.
It gets the user access token from Visualforce directly.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#issuecomment-2106970923,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYLVS6NR4RFBPKUKN53ZCB3K7AVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWHE3TAOJSGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Please refer to this issue it might resolve yours:  #118

Refering to the documentation https://salesforcelabs.github.io/OrgCheck/installation/

Thank you for your response Vincent. We will check it out and get back to
you if the issue persists.
Regards,
Varun Kumar
Sr. Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 14, 2024 at 6:35 PM Vincent FINET @.***>
wrote:

Closed #390 https://github.com/SalesforceLabs/OrgCheck/issues/390 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#event-12802005733,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYN4Q3UCCOGWCKFVY3LZCIDZBAVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSHAYDEMBQGU3TGMY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi Vincent,
Thanks for the update . The issue has been resolved.
Regards,
Varun Kumar
Sr. Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 14, 2024 at 7:20 PM Varun Kumar Yerraguntla <
@.***> wrote:

Thank you for your response Vincent. We will check it out and get back to
you if the issue persists.
Regards,
Varun Kumar
Sr. Proactive Monitoring Engineer | Salesforce
https://smart.salesforce.com/sig/vyerraguntla//us_mb/default/link.html
On Tue, May 14, 2024 at 6:35 PM Vincent FINET @.***>
wrote:

Closed #390 https://github.com/SalesforceLabs/OrgCheck/issues/390 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/SalesforceLabs/OrgCheck/issues/390#event-12802005733,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKFXYN4Q3UCCOGWCKFVY3LZCIDZBAVCNFSM6AAAAABHJ5FMWGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSHAYDEMBQGU3TGMY
.
You are receiving this because you authored the thread.Message ID:
@.***>


homework

I had a couple of troubles, not all of the code works

submitted
commited file to wrong location

therefore package doesn't work...
neither plots work when manually includeing code.

11/10


change depercated url

remove unnecessary blank
use hadoop 2.7.0 and install it using curl
change depercated serf url

I think that the hadoop downloaded from apache is compiled on 32-bit machine, it will have errors:

But the Dockerfile doesn't have these lines to download Hadoop. When I tried to build master on my laptop, it raise error that cannot find the path.

To download compiled Hadoop:
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.3.0/hadoop-2.3.0.tar.gz
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.4.0/hadoop-2.4.0.tar.gz
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.5.0/hadoop-2.5.0.tar.gz
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.6.0/hadoop-2.6.0.tar.gz
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.7.0/hadoop-2.7.0.tar.gz
wget https://github.com/kiwenlau/compile-hadoop/releases/download/2.7.2/hadoop-2.7.2.tar.gz


[7.x] Fixed deprecated "Doctrine/Common/Inflector/Inflector" class

The Inflector class is deprecated, use Doctrine\Common\Inflector\Inflector from doctrine/inflector package instead,

New class is non-static Doctrine\Inflector\Inflector::class

Please send this to 6.x, and support both 1.x and 2.x of the package.

@GrahamCampbell, sending to the 6.x version without any problems.
BUT it is difficult to specify both versions - I'll have to add a check for the existence of the class, because the namespace has changed.
To me it seems like a bad idea.

@GrahamCampbell. no problem. In the near future I will create a PR :)

Created: #32734

having the same error
Error: Class 'Doctrine\Inflector\Inflector' not found in var/www/html/vendor/laravel/framework/src/Illuminate/Support/Pluralizer.php:135

You need to update all your dependencies. Doctrine\Inflector\Inflector is only found in the newer versions of inflector.

@e-hop, use the composer update command.

I'm running Laravel 6.18.15 and getting this issue. I don't have doctrine listed as a separate requirement in my composer.json (it's in the composer.lock). I've tried to delete composer.lock and run composer update again with no success as it returns the same doctrine. I'm running PHP 7.4.3. How do I force this package to update to an acceptable version
    {
        "name": "doctrine/cache",
        "version": "1.10.0",
        "source": {
            "type": "git",
            "url": "https://github.com/doctrine/cache.git",
            "reference": "382e7f4db9a12dc6c19431743a2b096041bcdd62"
        },
        "dist": {
            "type": "zip",
            "url": "https://api.github.com/repos/doctrine/cache/zipball/382e7f4db9a12dc6c19431743a2b096041bcdd62",
            "reference": "382e7f4db9a12dc6c19431743a2b096041bcdd62",
            "shasum": ""
        },
        "require": {
            "php": "~7.1"

@Petro1979, installation requirements for this package are set by laravel/framework. It does not need to be installed manually.
This hotfix has been published in the following versions of Laravel: v7.11.0 and v6.18.14.
I installed a clean version of Laravel 6.18.15. I did not meet a mistake. Everything works perfectly.
        {
            "name": "doctrine/inflector",
            "version": "2.0.2",
            "source": {
                "type": "git",
                "url": "https://github.com/doctrine/inflector.git",
                "reference": "3fc171224a316569faad2df6b18a1fd8cce5a56d"
            },
            "dist": {
                "type": "zip",
                "url": "https://api.github.com/repos/doctrine/inflector/zipball/3fc171224a316569faad2df6b18a1fd8cce5a56d",
                "reference": "3fc171224a316569faad2df6b18a1fd8cce5a56d",
                "shasum": ""
            },
            "require": {
                "php": "^7.2 || ^8.0"
            },

Also in the project folder through the file search no error path was found:

I recommend that you execute the composer why doctrine/inflector command and find out if there are restrictions on using the latest version of the doctrine/inflector package from your other packages used in the application.


fix: 283 - correct guestbook manifest url

Issue: #283

Added the guestbook.yaml manifest and a reference to the file in the README.md

@swgriffith: Let me know if this looks good to be merged.