Running Speech service containers fail

Runing Command:
docker run -it -p 5000:5000 --memory 4g --cpus 4 -v custom-stt-vol:/usr/local/models containerpreview.azurecr.io/microsoft/cognitive-services-custom-speech-to-text ModelId=***** Eula=accept Billing=https://eastasia.api.cognitive.microsoft.com/sts/v1.0/issuetoken ApiKey=******
Runing process:
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
Starting custom model download
2020/05/13 08:18:21 Preparing file /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedPrepAM/model.fe
2020/05/13 08:18:21 Downloading file: /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedPrepAM/model.fe
2020/05/13 08:18:22 Preparing file /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/graphV2/base.lms
2020/05/13 08:18:22 Downloading file: /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/graphV2/base.lms
2020/05/13 08:21:51 Preparing file /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.lms
2020/05/13 08:21:51 Downloading file: /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.lms
2020/05/13 08:21:57 Preparing file /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.hclg
2020/05/13 08:21:57 Downloading file: /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.hclg
2020/05/13 08:22:29 Preparing file /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.lms
2020/05/13 08:22:29 Downloading file: /usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.lms
2020/05/13 08:22:46 Preparing file /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedAM/srthresholds.tsv
2020/05/13 08:22:46 Downloading file: /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedAM/srthresholds.tsv
2020/05/13 08:22:46 Preparing file /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedPrepAM/model.dbn.am
2020/05/13 08:22:46 Downloading file: /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedPrepAM/model.dbn.am
2020/05/13 08:22:46 Preparing configuratons
========================= ENVIRONMENT VARS ===========================================
EULA:            accept
BILLING:         https://eastasia.api.cognitive.microsoft.com/sts/v1.0/issuetoken
APIKEY:          ***
========================= ARGUMENT VARS ==============================================
CUSTOM ARGS:
/host /onprem_start
Starting dotnet Microsoft.CloudAI.Containers.SpeechToText.dll ModelId=6cf7e86b-f683-49f0-9192-8392a0d14a6a Eula=accep                                                                                t Billing=https://eastasia.api.cognitive.microsoft.com/sts/v1.0/issuetoken ApiKey=bee5e3d9aed54b73abca3288f143d98d
max number of threads 32767, 1000
min number of threads 4, 4
New min number of threads 20, 4
Notice: This Preview is made available to you on the condition that you agree to the Supplemental Terms of Use for Mi                                                                                crosoft Azure Previews [https://go.microsoft.com/fwlink/?linkid=2018815], which supplement your agreement [https://go                                                                                .microsoft.com/fwlink/?linkid=2018657] governing your use of Azure. If you do not have an existing agreement governin                                                                                g your use of Azure, you agree that your agreement governing use of Azure is the Microsoft Online Subscription Agreem                                                                                ent [https://go.microsoft.com/fwlink/?linkid=2018755] (which incorporates the Online Services Terms [https://go.micro soft.com/fwlink/?linkid=2018760]). By using the Preview you agree to these terms.
Logging to console.
Submitting metering to 'https://eastasia.api.cognitive.microsoft.com/sts/v1.0/issuetoken'.
Child pid=46 created
/onprem_start
Starting /opt/bin/run-decoder
Running an instance of gRPC based Richland
=======================
Checking ENV variables:
DECODER_COUNT_AUTO is unset
DECODER_COUNT is unset
DECODER_MAX_COUNT is unset
ENGINE_CONFIG_OVERRIDE is set to '/usr/local/models/properties.json'
MODELSPATH is set to '/usr/local/models'
MODELSPATH will be set to: '/usr/local/models'
SSL_ENABLE is unset
SSL_SERVER_CERT_PATH is unset
SSL_SERVER_PRIVATE_KEY_PATH is unset
SSL_ROOT_CERT_PATH is unset
SSL_FORCE_CLIENT_AUTH is unset
STATSD_HOST is unset
STATSD_PORT is unset (will use default port 8125)
STATSD_METRIC_PREFIX is unset
COGS_ENABLE is set
SERVICE_HOSTNAME is set to: '0660b2c2a203'
Starting gRPC server
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
No XML encryptor configured. Key {74189273-9aeb-4220-9fcd-39168d4e6726} may be persisted to storage in unencryp                                                                                ted form.
05-13-2020 08:22:48.047 SR 68 info
____  _
/ || | ___   _ _ __ ___   __ _ _ __
_ | |/ / | | | '  _ \ / _ | '_
) |   <| || | | | | | | (| | | | |
|/||_\__, || || ||_,|| ||
|__/
05-13-2020 08:22:48.047 SR 68 info log_level set to 2 ('info')
05-13-2020 08:22:48.047 SR 68 info started prometheus exposer on <IP_ADDRESS>:8080/metrics
05-13-2020 08:22:48.047 SR 68 info engine_config path overridden by environment variable (ENGINE_CONFIG_OVERRIDE)
05-13-2020 08:22:48.047 SR 68 info engine_config path: /usr/local/models/properties.json
05-13-2020 08:22:48.048 SR 68 info DefaultModelPath (evaluated MODELSPATH): /usr/local/models/
05-13-2020 08:22:48.048 SR 68 info IN_FESpec: audio(/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedPrepAM/m                                                                                odel.fe,8kHz16kHzLFB80x2EnergyMLPVADRuntime,/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/adaptedAM/srthresholds.                                                                                tsv)
05-13-2020 08:22:48.048 SR 68 info IN_DNNSpec: cntkHalide(/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/container                                                                                AM/0.1.0/model.onnx.bin.prod,28,160,features,ScaledLogLikelihood,1.0),lookAheadFrameCount(14),allValidInUtt(1),frameC                                                                                opyCount(1),resetOnSegmentation(1)
05-13-2020 08:22:48.048 SR 68 info IN_BeamSize: 5000
05-13-2020 08:22:48.048 SR 68 info IN_BeamThreshold: 170.0
05-13-2020 08:22:48.048 SR 68 info IN_NBestBeamSize: 100
05-13-2020 08:22:48.048 SR 68 info IN_DynBeamGrowthRate: 0.0
05-13-2020 08:22:48.048 SR 68 info IN_ModelMap[default]: type=Static, path='not_used_but_have_to_be_nonempty', hclg='                                                                                interpolated_lm_custom(0.9,/usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.hclg,/usr/local/m                                                                                odels/8026e414-09f5-4b2a-84f6-c20cae34dc1a/graphV2/custom.i1.lms,/usr/local/models/8026e414-09f5-4b2a-84f6-c20cae34dc                                                                                1a/graphV2/custom.lms)', base_hclg='interpolated_lm_base(/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/graphV2/ba                                                                                se.lms)', weight='0.0', default='false'
05-13-2020 08:22:48.048 SR 68 info IN_ModelMap[topLevelClm]: type=BaseClm, path='not_used_but_have_to_be_nonempty', h                                                                                clg='expanded_class_hclg()', base_hclg='expanded_class_hclg_base(/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/dg                                                                                i/mmf.cdbn.lambda,/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/dgi/list.lambda,/usr/local/models/0_en-us-2019120                                                                                2-8-2_HALIDE_DGI/dgi/clm.minhclg.hclg,/usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/dgi/clm.minhclg.lms,/usr/loca                                                                                l/models/0_en-us-20191202-8-2_HALIDE_DGI/dgi/classmap.txt)', weight='0.0', default='false'
05-13-2020 08:22:48.048 SR 68 info unable to open richland config file: /usr/local/models/richland.ini
05-13-2020 08:22:48.050 SR 68 warning Statsd server is undefined (use STATSD_HOST env to set it up)
05-13-2020 08:22:48.050 SR 68 info About to start gRPC server @ <IP_ADDRESS>:50051
05-13-2020 08:22:48.050 SR 68 info gRPC server decoder pool MIN count: 1
05-13-2020 08:22:48.050 SR 68 info gRPC server decoder pool MAX count: 10
05-13-2020 08:22:48.050 SR 68 info gRPC IPv4 exclusive mode
05-13-2020 08:22:48.069 SR 68 info Loaded CoreCLR from /opt/bin/libcoreclr.so
05-13-2020 08:22:48.121 SR 68 info CoreCLR started
Notice: This Preview is made available to you on the condition that you agree to the Supplemental Terms of Use for Mi                                                                                crosoft Azure Previews [https://go.microsoft.com/fwlink/?linkid=2018815], which supplement your agreement [https://go                                                                                .microsoft.com/fwlink/?linkid=2018657] governing your use of Azure. If you do not have an existing agreement governin                                                                                g your use of Azure, you agree that your agreement governing use of Azure is the Microsoft Online Subscription Agreem                                                                                ent [https://go.microsoft.com/fwlink/?linkid=2018755] (which incorporates the Online Services Terms [https://go.micro soft.com/fwlink/?linkid=2018760]). By using the Preview you agree to these terms.
Logging to console.
Submitting metering to 'https://eastasia.api.cognitive.microsoft.com/sts/v1.0/issuetoken'.
05-13-2020 08:22:48.377 SR 68 info ObjectPool: m_minCount = 1, m_maxCount = 10, reclaim = false
05-13-2020 08:22:48.377 SR 68 info Grammar model 'default' [Static] loading...
05-13-2020 08:22:48.379 SR 68 info IUnidecSearchGraphCombo::Create: spec interpolated_lm_base(/usr/local/models/0_en-                                                                                us-20191202-8-2_HALIDE_DGI/graphV2/base.lms)
05-13-2020 08:22:48.426 SR 68 info   CWFST_Persisted_LM_SearchGraph.h[416] 0.000087 seconds: CWFST_Persisted_LM_Searc                                                                                hGraph::CBuilder Loaded lms /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/graphV2/base.lms
05-13-2020 08:22:48.426 SR 68 info persisted_LM Fallback WFST: 16676977 states 149716283 transitions
warn: Microsoft.AspNetCore.Server.Kestrel[0]
Overriding address(es) 'http://+:80'.
Result: Failed.
My question:
1. I am very curios about  "Downloading file: /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/graphV2/base.lms"  such dowloading hint.  But I do not see any dowloaded file in directory "/usr/local/models"
2 In Running Command, for parameter -v , no matter what file path I define, it always tells me file is  download to  /usr/local/models.
3.  Seems that procedure is Aborted after Unable to open filename /usr/local/models/0_en-us-20191202-8-2_HALIDE_DGI/dgi/clm                                                                                .minhclg.hclg, does it cause the failure or otherthing?

@fifteenjoy can you post a link to the doc you are following?

@TravisCragg-MSFT , I am following below guide:
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/speech-container-howto?tabs=stt%2Ccsharp%2Csimple-format

@aahill can you please review the above feedback. Thanks.

@GiftA-MSFT this is something the product group should look at. Please reassign this to the product contact.

@GiftA-MSFT could you please assign this to the right product contact to move this forward?

I'm seeing the container you're using is a previous one hosted on containerpreview.azurecr.io.

I'd recommend using the container at mcr.microsoft.com/azure-cognitive-services/speechservices/speech-to-text:latest as it's newer - could you try this container and open a new issue if you're still encountering issues?
#please-close


Duplicate manager/provider objects after build

Describe the bug
After building a Unity project every object in MIxedRealityToolkit is duplicated.
I tested only in 2020.1.0a16 as this version is required for my project.
To reproduce
Steps to reproduce the behavior:

Create new project with MRTK packages imported
Mixed Reality Toolkit -> Add to Scene and configure
Build Unity Project in the Build Window of MRTK
Observe that every object in MixedRealityToolkit (e.g. HandJointService, WindowsMixedRealityDeviceManager) exists twice.

Expected behavior
No object duplication after building
Your setup (please complete the following information)

Unity Version 2020.1.0a16
MRTK Version 2.2.0

Target platform (please complete the following information)

HoloLens
HoloLens 2

Happening in Unity 2019.3.3f1 with MRTC v2.3.0 too.

This also happens on Unity 2020.1 with MRTK Quest.

Do we know the root cause? Also what is the workaround? Should the user manually delete one of each of the duplicates or is there a better fix?


Raise an error when PyTorch's activation checkpointing is used with Thunder-jitted model

🐛 Bug
Activation checkpointing is a technique to reduce memory usage by clearing activations of certain layers and recomputing them during the backward pass. Thunder doesn't know how to deal with PyTorch's annotations and wrappers implementing this feature that leads to silent or loud problems, like https://github.com/Lightning-AI/lightning-thunder/issues/582.
When nn.Module passed to thunder.jit includes an instance of torch.distributed.algorithms._checkpoint.checkpoint_wrapper.CheckpointWrapper in its submodules Thunder should raise an error.
Is there any other indicator that the user used torch.distributed.algorithms._checkpoint.checkpoint_wrapper.apply_activation_checkpointing?
cc @apaz-cli

I wonder how hard it would be to actually support basic CheckpointWrapper by having a "container symbol" and defining a grad transform that includes the forward in the backward...

plan to do automatic checkpointing based on memory available (eventually)
but this is also a hugely important thing for memory use, which is a big deal right now
interim solution: make use of user's annotation? (This might actually be harder than just doing the full solution.)
can we just push a scope on the stack and use that for handling what gets checkpointed? yes, but then we'll need to modify backward
we would accept compromises, but let's wait for a bigger design


restack appears to enter infinite loop when it encounters a merge conflict

When I amend to an older commit in the stack that results in a merge conflict, I get repeated errors indicating a rebase is in progress:
branchless: git rebase b5ed1de43634dc9e64ab9a0e0d1555f6a2c41297 06e73bfc36ab4f7b83a6abbda1e24c55aa3435c5 --onto 69feacd33c46f8c4bdf053d7f778e2077bdfee56
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
Rebasing (1/1)^Mbranchless: processing 1 update to a branch/ref
branchless: processing 1 update to a branch/ref
error: could not apply 06e73bf... Make line 2 extra verbose
Resolve all conflicts manually, mark them as resolved with
"git add/rm <conflicted_files>", then run "git rebase --continue".
You can instead skip this commit: run "git rebase --skip".
To abort and get back to the state before "git rebase", run "git rebase --abort".
branchless: processing 1 update to a branch/ref
Recorded preimage for 'README.md'
branchless: processing 1 update to a branch/ref
Could not apply 06e73bf... Make line 2 extra verbose
branchless: resolve rebase, then run 'git restack' again
branchless: git rebase b5ed1de43634dc9e64ab9a0e0d1555f6a2c41297 06e73bfc36ab4f7b83a6abbda1e24c55aa3435c5 --onto 69feacd33c46f8c4bdf053d7f778e2077bdfee56
fatal: It seems that there is already a rebase-merge directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
        git rebase (--continue | --abort | --skip)
If that is not the case, please
        rm -fr ".git/rebase-merge"
and run me again.  I am stopping in case you still have something
valuable there.

branchless: resolve rebase, then run 'git restack' again
branchless: git rebase b5ed1de43634dc9e64ab9a0e0d1555f6a2c41297 06e73bfc36ab4f7b83a6abbda1e24c55aa3435c5 --onto 69feacd33c46f8c4bdf053d7f778e2077bdfee56
fatal: It seems that there is already a rebase-merge directory, and
I wonder if you are in the middle of another rebase.  If that is the
case, please try
        git rebase (--continue | --abort | --skip)
If that is not the case, please
        rm -fr ".git/rebase-merge"
and run me again.  I am stopping in case you still have something
valuable there.

The last bit repeats endlessly.
Repro:
mkdir -p origin-repo
cd origin-repo
git init .
printf "one\ntwo\nthree\n" > README.md
git add .
git commit -am "Initial commit."

git checkout -b feature-2
cp README.md tmp && sed '2s/^/this is /' < tmp > README.md && rm tmp
git commit -am "Make line 2 extra verbose"
git prev
cp README.md tmp && sed '2s/^lin /line /' < tmp > README.md && rm tmp
git amend -a
git restack

If you run into this in the wild:

Break the loop w/ Ctrl-C
Resolve the conflict by editing the conflicted file (README.md in the repro).
git add README.md
git rebase --continue
git restack

Thanks for the detailed report and repro steps. I wasn't able to to reproduce this, with this slightly modified script (git amend doesn't exist in stock Git):
mkdir -p origin-repo
cd origin-repo
git init .
printf "one\ntwo\nthree\n" > README.md
git add .
git commit -am "Initial commit."

git checkout -b feature-2
cp README.md tmp && sed '2s/^/this is /' < tmp > README.md && rm tmp
git commit -am "Make line 2 extra verbose"
git prev
cp README.md tmp && sed '2s/^lin /line /' < tmp > README.md && rm tmp
git commit -a --amend
git restack

Most likely this was fixed in https://github.com/arxanas/git-branchless/commit/15fe10431aa2e24bafd48b1b7cc671e820d837a2, released in https://github.com/arxanas/git-branchless/releases/tag/v0.3.2. I would ask what version of git-branchless you're using, but it might be hard to say, given that git-branchless doesn't correctly report its version number (9d4f4f126be259d53aef231059ea9a726d72a714)... Reopen if the issue persists after upgrading to v0.3.2 or later.
git restack is implemented in kind of a hacky way for now. In the long run, I'd like to use the git move machinery to form a rebase plan and execute it all in one go, rather than iterating until we reach a fixed point. This should make it much harder to hit an infinite loop bug because we won't be doing any looping.

Oops, I forgot that amend is an alias. You guessed it correctly in any case.
Issue is gone after upgrading.


Mat/Pat - Change leave start date conditions

Context
It was initially decided to allow mat/pat form to be submitted upto 9 months before leave starts. This was an arbitrary decision. In terms of processing the application a 2 month lead is all thats needed. Any application submitted earlier will be too early for processing.
AC

[x] Change maternity leave start date condition from 9 months to 2 months in advance

[x] Change error message from "You must select a date up to 9 months in the future" to "You can submit your application up to 2 months before the start date of your maternity leave"

[x] Change parental leave start date condition from 9 months to 2 months in advance (this is for applicants taking only parental leave)

[x] Change error message from "You must select a date up to 9 months in the future" to "You can submit your application up to 2 months before the start date of your parental leave"

@Andrew-Vargas-bcgov could you give us and estimate on this?

Tested in TEST environment ✅

Maternity leave date error message updated:
Private Zenhub Image

Only parental leave error message updated:
Private Zenhub Image

Hey @Andrew-Vargas-bcgov Works well. Just noticed that for maternity leave when submitting on Sept 14, Nov 13 is 2 months in advance, and Nov 14 shows an error but for parental leave Nov 14 is accepted. Since the condition is same for both, just wanted to ask why the discrepancy is there
Parental leave -
Private Zenhub Image
Maternity Leave -
Private Zenhub Image

@fazil-ey fixed and moved the changes to test.

Works as expected


Forward bundle_name to iOS test rules

Only merge if https://github.com/bazelbuild/rules_apple/pull/1948 gets merged.

Thanks, @jerrymarino!


Arweden Custom Voiced High Elf Companion and Quest

Link to the mod
https://www.nexusmods.com/skyrimspecialedition/mods/14742
Is the follower adult only?
no

currently hidden


keras/examples/tensorboard_embeddings_mnist.py gives an

[ yes] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

[ yes] Check that your version of TensorFlow is up-to-date. The installation instructions can be found here.

[https://github.com/keras-team/keras/blob/master/examples/tensorboard_embeddings_mnist.py] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I am using Anaconda python(3.6) for running the example code for tensorboard embedding in mnist. After training for an epoch, when the call back is called, it gives the following error.
Epoch 1/12
60000/60000 [==============================] - 8s 139us/step - loss: 0.2665 - acc: 0.9170 - val_loss: 0.0716 - val_acc: 0.9774
2018-11-29 13:04:24.254467: W tensorflow/core/framework/op_kernel.cc:1273] OP_REQUIRES failed at save_restore_v2_ops.cc:137 : Unknown: Failed to rename: ./logs\keras_embedding.ckpt-0.data-00000-of-00001.tempstate7943206387758954579 to: ./logs\keras_embedding.ckpt-0.data-00000-of-00001 : Access is denied.
; Input/output error
Traceback (most recent call last):
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1334, in _do_call
return fn(*args)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1319, in _run_fn
options, feed_dict, fetch_list, target_list, run_metadata)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1407, in _call_tf_sessionrun
run_metadata)
tensorflow.python.framework.errors_impl.UnknownError: Failed to rename: ./logs\keras_embedding.ckpt-0.data-00000-of-00001.tempstate7943206387758954579 to: ./logs\keras_embedding.ckpt-0.data-00000-of-00001 : Access is denied.
; Input/output error
[[{{node save/SaveV2}} = SaveV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/SaveV2/tensor_names, save/SaveV2/shape_and_slices, features_embedding/_137)]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "embedding.py", line 88, in
validation_data=(x_test, y_test))
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\engine\training.py", line 1039, in fit
validation_steps=validation_steps)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\engine\training_arrays.py", line 217, in fit_loop
callbacks.on_epoch_end(epoch, epoch_logs)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py", line 79, in on_epoch_end
callback.on_epoch_end(epoch, logs)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py", line 981, in on_epoch_end
epoch)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 1441, in save
{self.saver_def.filename_tensor_name: checkpoint_file})
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 929, in run
run_metadata_ptr)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1152, in _run
feed_dict_tensor, options, run_metadata)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1328, in _do_run
run_metadata)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\client\session.py", line 1348, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.UnknownError: Failed to rename: ./logs\keras_embedding.ckpt-0.data-00000-of-00001.tempstate7943206387758954579 to: ./logs\keras_embedding.ckpt-0.data-00000-of-00001 : Access is denied.
; Input/output error
[[node save/SaveV2 (defined at C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py:887)  = SaveV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/SaveV2/tensor_names, save/SaveV2/shape_and_slices, features_embedding/_137)]]
Caused by op 'save/SaveV2', defined at:
File "embedding.py", line 88, in
validation_data=(x_test, y_test))
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\engine\training.py", line 1039, in fit
validation_steps=validation_steps)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\engine\training_arrays.py", line 117, in fit_loop
callbacks.set_model(callback_model)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py", line 54, in set_model
callback.set_model(model)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py", line 887, in set_model
self.saver = tf.train.Saver(list(embeddings_vars.values()))
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 1102, in init
self.build()
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 1114, in build
self._build(self._filename, build_save=True, build_restore=True)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 1151, in _build
build_save=build_save, build_restore=build_restore)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 792, in _build_internal
save_tensor = self._AddSaveOps(filename_tensor, saveables)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 284, in _AddSaveOps
save = self.save_op(filename_tensor, saveables)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\training\saver.py", line 202, in save_op
tensors)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\ops\gen_io_ops.py", line 1690, in save_v2
shape_and_slices=shape_and_slices, tensors=tensors, name=name)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\util\deprecation.py", line 488, in new_func
return func(*args, **kwargs)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\framework\ops.py", line 3274, in create_op
op_def=op_def)
File "C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\tensorflow\python\framework\ops.py", line 1770, in init
self._traceback = tf_stack.extract_stack()
UnknownError (see above for traceback): Failed to rename: ./logs\keras_embedding.ckpt-0.data-00000-of-00001.tempstate7943206387758954579 to: ./logs\keras_embedding.ckpt-0.data-00000-of-00001 : Access is denied.
; Input/output error
[[node save/SaveV2 (defined at C:\Users\abalu\AppData\Local\Continuum\anaconda3\envs\keras\lib\site-packages\keras\callbacks.py:887)  = SaveV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/SaveV2/tensor_names, save/SaveV2/shape_and_slices, features_embedding/_137)]]
I searched for the possible reasons for this to happen, I found the following few issues/discussion:
https://github.com/balancap/SSD-Tensorflow/issues/72
https://stackoverflow.com/questions/43644893/windows-tensorflow-could-not-restore-checkpoint-access-is-denied
my understanding is that, this could be something to do with the behavior in windows. I dont know what the exact issue is, I would like to contribute if someone could let me know what might be the issue. Thanks

This is an access denied error. This just means that you don't have the windows permissions to do something, like create or rename a file. This is unrelated to keras or tensorflow.

But I do have write access to that folder... Something else seems to be the problem


Orphaned mitigation on service instance update failures

Thanks for submitting an issue to cloud_controller_ng. We are always trying to improve! To help us, please fill out the following template.
Issue
CC issues an orphaned mitigation on service instances with failed updates resulting in the removal of the service instance.
Context
Updating service instances may result in a failure and for such scenario the orphaned mitigation should not be triggered as described in the OSB specification.

https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#orphan-mitigation
https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#updating-a-service-instance

We assume that this commit has introduced this bug where it triggers the mitigation when a request to last_operation is issued by the CC and the service broker report its state is 'failed'.

https://github.com/cloudfoundry/cloud_controller_ng/commit/80176ff0068741088e19629516c0285b4cf57ef3#diff-6e29198ceec350cf6dfa0220146b0c61

From our point view it is incorrect to initiate a mitigation on a service instance based on the last_operation without checking the type of the operation that had been performed.
For additional information:

The service instance provisioning / deprovisioning / update is asynchronous.
The service broker returns a http 200, state = 'failed' when last_operation is requested by CC.

Steps to Reproduce

Create any service in Cloud Foundry
Update the service (change of a plan, configuration)

The service update must fail

Expected result

Update service instance fails but no orphaned mitigation is triggered.

Current result

Update service instance fails and orphaned mitigation is triggered.

Thank you for raising this @brunograz. This is clearly an incorrect behavior and we are working on a fix.


Fix typo: formats are exposed in singular form

Formats are exposed as winston.format.smthg, not winston.formats.something.

This is true!  Thanks for spotting this!


Add padding to target regions in somatic variant calling workflows

Closes #915
Removes requirement of a second interval list from somatic workflows, and instead bases the roi for variant calling on the target region plus some padding (configurable option)

Ready for re-review here. A test run using a new PP succeeded and showed splice site variants appearing as expected.


Conditional bindings support

First of all thank you for this awesome editor! This is the editor I was always looking for!
Specifications
Virtual Studio Code implements CtrlC and CtrlX without any selection for copying and cutting the line. I find this very useful and I would like to add it to micro (this is not at all essential by the way).
Is there a way to specify a condition for the shortcut? I'm thinking of something like
{
    "CtrlX & EmptySelection": "CutLine",
    "CtrlC & EmptySelection": "CopyLine",
}

You can achieve this with a little bit of lua scripting. You can place lua code in ~/.config/micro/init.lua to be executed when micro starts. You can call actions from lua as well as access additional info. You can read about the lua scripting in help plugins.
The cut is simpler than the copy because there already exists a CutLine action, but it isn't too hard to create your own CopyLine. When executing an action, the boolean that is passed tells micro whether it should call any plugin callbacks that are bound to that action. Generally it doesn't really matter too much, the option is just there to avoid a callback recursively calling itself (if it calls the action that it is a callback for).
Here is an example for your problem:
function SpecialCut()
    local v = CurView()

    if v.Cursor:HasSelection() then
        v:Cut(true)
    else
        v:CutLine(true)
    end
end

function SpecialCopy()
    local v = CurView()

    if v.Cursor:HasSelection() then
        v:Copy(true)
    else
        local x, y = v.Cursor.X, v.Cursor.Y

        v:StartOfLine(false)
        v:SelectToEndOfLine(false)
        v:Copy(true)
        v.Cursor:ResetSelection()

        v.Cursor.X, v.Cursor.Y = x, y
    end
end

Now these two functions can be bound as actions in bindings.json:
{
    "CtrlX": "init.SpecialCut",
    "CtrlC": "init.SpecialCopy"
}

@zyedidia Thank you! This works very well. I might publish a plugin with this when I get the chance!


Docker image with annotation-tool is missing

Are there any plans to create a docker image that includes the annotation tool (like allinone-plus-annotation)?
Otherwise I will try to modify the allinone Dockerfile to include the annotation-tool installation (as described in https://github.com/opencast/annotation-tool/blob/master/documentation/opencast-installation.md#installing-the-annotation-tool) and use it locally.

An easy way to do this is to write a Dockerfile based on the allinone image and include the annotation tool JARs into the /opencast/deploy folder. Opencast will init all JARs during startup so you don't need to deal with Karaf.

An easy way to do this is to write a Dockerfile based on the allinone image and include the annotation tool JARs into the /opencast/deploy folder. Opencast will init all JARs during startup so you don't need to deal with Karaf.

Thanks for your answer - this is exactly what I did (see https://github.com/opencast/annotation-tool/issues/433): I build the annotation tool and store the JARs in the /opencast/deploy folder. This is the content of the folder:
-rw-r--r-- 1 opencast opencast   10797 Jan 12 19:25 annotation-tool-api-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast    1987 Jan 12 19:25 annotation-tool-frontend-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast 1423001 Jan 12 19:25 annotation-tool-frontend-delivery-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast  252812 Jan 12 19:25 annotation-tool-impl-0-SNAPSHOT.jar

But as described in the other issue I get the following error on startup:
...
opencast_1  | Run opencast_main_start
opencast_1  | 2021-01-12T19:28:05,467 | WARN  | (PaxLoggingServiceImpl$1ManagedPaxLoggingService:398) - Error while starting bundle: file:/opencast/deploy/annotation-tool-api-0-SNAPSHOT.jar
opencast_1  | org.osgi.framework.BundleException: Unable to resolve annotation-tool-api [10](R 10.0): missing requirement [annotation-tool-api [10](R 10.0)] osgi.wiring.package; (&(osgi.wiring.package=org.opencastproject.mediapackage)(version>=8.10.0)) Unresolved requirements: [[annotation-tool-api [10](R 10.0)] osgi.wiring.package; (&(osgi.wiring.package=org.opencastproject.mediapackage)(version>=8.10.0))]
opencast_1  |   at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149) ~[?:?]
opencast_1  |   at org.apache.felix.framework.Felix.startBundle(Felix.java:2119) ~[?:?]
opencast_1  |   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
...

Next steps would be testing if the package in the error log has really the wrong version and if an earlier version of opencast (8.6) works.

Thanks for your answer - this is exactly what I did (see https://github.com/opencast/annotation-tool/issues/433): I build the annotation tool and store the JARs in the /opencast/deploy folder. This is the content of the folder:
-rw-r--r-- 1 opencast opencast   10797 Jan 12 19:25 annotation-tool-api-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast    1987 Jan 12 19:25 annotation-tool-frontend-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast 1423001 Jan 12 19:25 annotation-tool-frontend-delivery-0-SNAPSHOT.jar
-rw-r--r-- 1 opencast opencast  252812 Jan 12 19:25 annotation-tool-impl-0-SNAPSHOT.jar

But as described in the other issue I get the following error on startup:
...
opencast_1  | Run opencast_main_start
opencast_1  | 2021-01-12T19:28:05,467 | WARN  | (PaxLoggingServiceImpl$1ManagedPaxLoggingService:398) - Error while starting bundle: file:/opencast/deploy/annotation-tool-api-0-SNAPSHOT.jar
opencast_1  | org.osgi.framework.BundleException: Unable to resolve annotation-tool-api [10](R 10.0): missing requirement [annotation-tool-api [10](R 10.0)] osgi.wiring.package; (&(osgi.wiring.package=org.opencastproject.mediapackage)(version>=8.10.0)) Unresolved requirements: [[annotation-tool-api [10](R 10.0)] osgi.wiring.package; (&(osgi.wiring.package=org.opencastproject.mediapackage)(version>=8.10.0))]
opencast_1  |   at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4149) ~[?:?]
opencast_1  |   at org.apache.felix.framework.Felix.startBundle(Felix.java:2119) ~[?:?]
opencast_1  |   at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) ~[?:?]
...

Next steps would be testing if the package in the error log has really the wrong version and if an earlier version of opencast (8.6) works.

This is "normal". Since Opencast (more specific Apache Karaf) does not know the correct loading order for files in the deploy directory, there is basically a race if all the necessary dependencies for the annotation-tool are loaded. The most effective way to mitigate this error is to postpone the loading of the additional files by increasing felix.fileinstall.poll in org.apache.felix.fileinstall-deploy.cfg, e.g.:
felix.fileinstall.dir           = ${karaf.base}/deploy
felix.fileinstall.tmpdir        = ${karaf.data}/generated-bundles
felix.fileinstall.poll          = 30000
felix.fileinstall.start.level   = 80
felix.fileinstall.active.level  = 80
felix.fileinstall.log.level     = 3

This is "normal". Since Opencast (more specific Apache Karaf) does not know the correct loading order for files in the deploy directory, there is basically a race if all the necessary dependencies for the annotation-tool are loaded. The most effective way to mitigate this error is to postpone the loading of the additional files by increasing felix.fileinstall.poll in org.apache.felix.fileinstall-deploy.cfg, e.g.:
felix.fileinstall.dir           = ${karaf.base}/deploy
felix.fileinstall.tmpdir        = ${karaf.data}/generated-bundles
felix.fileinstall.poll          = 30000
felix.fileinstall.start.level   = 80
felix.fileinstall.active.level  = 80
felix.fileinstall.log.level     = 3

Thank you @mtneug, this did the trick! And when I checked where to find or create this file, I saw that this issue isn't new: https://github.com/opencast/annotation-tool/issues/226, https://groups.google.com/a/opencast.org/g/dev/c/-MYXY9BFcyQ?pli=1 but I don't know, why I didn't saw it beforehand.
Next steps would be adding the configuration for the annotation tool into my Dockerfile and than I will share the full version.

Thank you @mtneug, this did the trick! And when I checked where to find or create this file, I saw that this issue isn't new: https://github.com/opencast/annotation-tool/issues/226, https://groups.google.com/a/opencast.org/g/dev/c/-MYXY9BFcyQ?pli=1 but I don't know, why I didn't saw it beforehand.
Next steps would be adding the configuration for the annotation tool into my Dockerfile and than I will share the full version.

Glad that it is working now. I would not add an additional Docker image for allinone/presentation + annotation-tool since the annotation tool is not part of the main code base of Opencast, but having documentation + an example Dockerfile would certainly be helpful for others.

Glad that it is working now. I would not add an additional Docker image for allinone/presentation + annotation-tool since the annotation tool is not part of the main code base of Opencast, but having documentation + an example Dockerfile would certainly be helpful for others.

I finally got an working version and prepared a shareable Dockerfile that works with the standard allinone docker-compose files (only v8.x). What would be the best way to add this Dockerfile? As a closing comment to this issue?

I finally got an working version and prepared a shareable Dockerfile that works with the standard allinone docker-compose files (only v8.x). What would be the best way to add this Dockerfile? As a closing comment to this issue?

Since people who want to use OAT probably look through the OAT documentation first, maybe we could add a new article there? @JulianKniephoff does this make sense? Basically, a new markdown file describing this setup.

Since people who want to use OAT probably look through the OAT documentation first, maybe we could add a new article there? @JulianKniephoff does this make sense? Basically, a new markdown file describing this setup.

I'm glad to accept any kind of improvement to the docs over at opencast/annotation-tool. :slightly_smiling_face:

I'm glad to accept any kind of improvement to the docs over at opencast/annotation-tool. :slightly_smiling_face:

Alright, see https://github.com/opencast/annotation-tool/pull/439. This pull request documents how to use the Annotation Tool with Docker, so I will close this comment.

Alright, see https://github.com/opencast/annotation-tool/pull/439. This pull request documents how to use the Annotation Tool with Docker, so I will close this comment.


AH view of schedule rows: date in and out do not need to display year (gets cut off anyway and the year is shown as part of the schedule already)

Duplicate of #412


Questions: Rationale for this library and comparisons with existing js ML libraries?

Hi there,
first of all, thank you and congratulations on building such a modular and comprehensive set of ML tools in javascript for node and the browser.
In my search for ML libraries in Javascript, I stumbled on a few that have the same name or close one:

MILJS - From the University of Tokyo, uses graphical acceleration optionally
ML.JS - From the University of Lorraine, France. with an interesting demo, Github page here

Do you have a demo page? a tutorial/example of a workflow using different modules?

Hello @Bondifrench, we haven't check those libraries before, so it's really cool to check them, thanks!
Each module has it's respective documentation and example, but if it's not clear enough or it's missing please let us know. The most similar think to a demo it's http://www.cheminfo.org/, where you can find a tab called ML, there are some examples, but not all the modules are there


unable to compile: missing ice40_dsp_pm.h

Steps to reproduce the issue

Download yosys
Run make config-gcc
Run make

Output: (from https://travis-ci.org/xobs/toolchain-icestorm/jobs/574305514)
...
[ 46%] Building passes/opt/wreduce.o
[ 46%] Building passes/opt/opt_demorgan.o
[ 47%] Building passes/opt/rmports.o
[ 47%] Building passes/opt/opt_lut.o
[ 48%] Building passes/opt/pmux2shiftx.o
[ 48%] Building passes/opt/muxpack.o
[ 48%] Building passes/pmgen/test_pmgen_pm.h
[ 48%] Building passes/pmgen/test_pmgen.o
passes/pmgen/test_pmgen.cc:30:39: fatal error: passes/pmgen/ice40_dsp_pm.h: No such file or directory
compilation terminated.
make: *** [passes/pmgen/test_pmgen.o] Error 1

Note that the output from that build uses a more complex make command, however I have reproduced it on a different machine by simply running make.

Yep, same issue on nMigen's CI: https://travis-ci.org/m-labs/nmigen/jobs/574325647

It should work fine with proper dependency set. Not near development
machine right now, but will make a patch bit later with this.
OBJS += passes/pmgen/test_pmgen.o
passes/pmgen/test_pmgen.o: passes/pmgen/test_pmgen_pm.h
passes/pmgen/ice40_dsp_pm.h
$(eval $(call add_extra_objs,passes/pmgen/test_pmgen_pm.h))
$(eval $(call add_extra_objs,passes/pmgen/ice40_dsp_pm.h))
On Tue, Aug 20, 2019 at 2:36 PM whitequark<EMAIL_ADDRESS>wrote:

Yep, same issue on nMigen's CI:
https://travis-ci.org/m-labs/nmigen/jobs/574325647
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/YosysHQ/yosys/issues/1311?email_source=notifications&email_token=AA3UUSHVCEWLAKO7IJPI3WTQFPQM5A5CNFSM4INVSDX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4WEDTI#issuecomment-522994125,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3UUSDJDZJV75WO4HQRWUDQFPQM5ANCNFSM4INVSDXQ
.

I can't find required *.h files in my latest git pull
$ find yosys -name ice40_dsp_pm.h
$

@emard This is generated file, fix above should make sure it is created before compiling of that line.

yes it's generated really, after applying above there's another
passes/pmgen/test_pmgen.cc:31:10: fatal error: passes/pmgen/peepopt_pm.h: Nema takve datoteke ili direktorija
#include "passes/pmgen/peepopt_pm.h"

This makes compile to continue, lets seee....
OBJS += passes/pmgen/test_pmgen.o
passes/pmgen/test_pmgen.o: passes/pmgen/test_pmgen_pm.h passes/pmgen/ice40_dsp_pm.h passes/pmgen/peepopt_pm.h
$(eval $(call add_extra_objs,passes/pmgen/test_pmgen_pm.h))
$(eval $(call add_extra_objs,passes/pmgen/ice40_dsp_pm.h))
$(eval $(call add_extra_objs,passes/pmgen/peepopt_pm.h))

ah, so there is one more dependency

I've tried to reproduce it locally but cannot for some reason, what gives?

I compiled with aboved patch but now I get this when using yosys:
ERROR: Assert `pass_register.count(pass_name) == 0' failed in
kernel/register.cc:111.
On 8/21/19, whitequark<EMAIL_ADDRESS>wrote:

I've tried to reproduce it locally but cannot for some reason, what gives?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/YosysHQ/yosys/issues/1311#issuecomment-523467081

@emard Sorry I can not reproduce error you are getting, if you still get it after clean compile please send me on email example how to reproduce it.

#1315 fixes this issue. Closing now.

ERROR: Assert `pass_register.count(pass_name) == 0' failed in kernel/register.cc:111.

That's a different problem. Please file a new issue if it persist after make clean.


refactor: Update Configs

Description

Moves the Substation config so that it is public (can be imported by other Go apps)

config.go and Jsonnet functions are now in config/
example configurations are now in examples/

Adds runtime concurrency setting via SUBSTATION_CONCURRENCY environment variable

Default behavior is the same as the current behavior

Updated documentation

Motivation and Context

Making the Substation config public was a requirement to make the condition inspectors and processors highly usable in other applications
Using SUBSTATION_CONCURRENCY is preferred over pinning concurrency to the number of CPUs -- there are some scenarios when less or more concurrency is required

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Looks great! My only feedback is that /config vs /configs can be confusing change for others to understand which is for example and which is the actual config file.

I think this is a bit better now, but let me know what you think. Changes:

All examples are now in examples/
Build steps for both the quickstart (in the main README) and the AWS test deployment are simpler (copy/paste and it just works assuming the environment variables are correct)
Added examples for using conditions and processors in external apps (examples/condition and examples/process)

Great changes, much easier to navigate :) LGTM 🚢


using github url for yaml.v2 submodule

This is an attempt to fix Github pages build…
This is the answer that @sanscontext got from Github support:
Hello Laura,

Sorry for the trouble here, we don't have parsers in place for all of the Jekyll errors.

From our internal logs I see this:

Cloning into 'tests/src/gopkg.in/yaml.v2'...
error: RPC failed; result=22, HTTP code = 301
fatal: The remote end hung up unexpectedly
Clone of 'https://gopkg.in/yaml.v2' into submodule path 'tests/src/gopkg.in/yaml.v2' failed

Which I believe is referring to this:

https://github.com/docker/docker.github.io/blob/ae629e574198ba47182878ff720e3b63df294599/.gitmodules#L9

Is that URL correct? I would have thought it would be something like this:

https://github.com/go-yaml/yaml.git

I am not sure what you are trying to do there though so it may be correct.

Regards,
Daniel
@danayel
GitHub Support

I'm now using https://github.com/go-yaml/yaml.git instead of https://gopkg.in/yaml.v2
Signed-off-by: Adrien Duermael<EMAIL_ADDRESS>

Let's give it a shot! Fingers crossed. :) Thanks, @aduermael!


The note about deleted server can't be restored is incorrect

There's a step by step how to about how to restore a deleted server
https://docs.microsoft.com/en-us/azure/postgresql/howto-restore-dropped-server

@Ktoliver
Please make the edit.
thank you.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Merging per @markingmyname. Thanks, all.

thank you, @ktoliver for being so thorough.


 It is a good practice.

It's used and configured, check out package.json config.
It's just disabled by default, but if you wanna enable it you must run npm run semantic-release-prepare. That will setup the commit-msg and prepush hooks, since semantic release need a strict commit style (although you don't need to use semantic release, so you can use it only for the hooks)


Create Channel Invite https://discord.com/developers/docs/resources/channel#create-channel-invite

Done


Motion Module Failure

librealsense
2.33.1 RELEASE

OS
Windows

Name
Intel RealSense D435I

Serial Number
919122070909

Firmware Version
<IP_ADDRESS>

Advanced Mode
YES

Camera Locked
YES

Usb Type Descriptor
3.2

Product Line
D400

Asic Serial Number
924123050848

Firmware Update Id
924123050848

Please provide a description of the problem
Motion Module Error notification from hardware while turning on the module in the viewer. And the gyroscope and accelerometer output looks to be interchanged. Please have a look at the problem. Looking forward for a solution. Thank you.

I ran some tests with my own D435i on Windows in SDK version 2.33.1.  Whe you say the data is "interchanged", do you mean that the data display appears on one side in one picture and on the other side on the other picture?  If so, this is how the Viewer works.  The left and right sides (gyro and accel) display and hide their read-out depending on whether the mouse cursor is hovered over their panel.
When I repeated your process (start the motion module, stop it and then start it again), I got the same error box as you when re-starting after the stop.  On my Viewer, the IMU streams still kept working normally immediately after that though, so I wonder if it is a momentary glitch that corrects itself immediately after start-up.

Actually, The gyroscopic measure is displayed in accele window and accelerometer measure is displayed in gyro window as shown in the first two images

The values shown in the two windows are consistent with the ones that I got for each window in my own tests with SDK 2.33.1.  I checked against some reference pictures of the motion module of D435i on Google Images though and found that the values do indeed seem to be flipped.
Example from Google Images:

I checked the values in your test and mine against reference images on Google Images of the motion module.  They do seem to be correct (Gyro has values near 0 and Accel has values between 0 and 9.8)

But gyro should give consistent value as if we change the position of the camera. It shouldn't go back to 0 and accelerometer should give acceleration to gravity and goes to zero when it is not accelerating. But in our images, both are interchanged.

The IMU documentation makes reference to how you may get non-zero angular velocities due to it not having internal calibration.
https://github.com/IntelRealSense/librealsense/blob/master/doc/d435i.md#imu-calibration

Thank you for the documentation. I will haver a look at it. I turned off the motion module and turned it on after some time, but still getting the module error. Is it hardware or software issue you think?

Given that the issue was replicated exactly on my own camera, it is likely an SDK software issue rather than a hardware fault.  I will label this discussion as "bug" so that the RealSense team can track and investigate it.

Please let me know as fast as you can so that I can work on it without
much trouble. Thank you
On Tue, 10 Mar, 2020, 5:36 PM MartyG-RealSense<EMAIL_ADDRESS>wrote:

Given that the issue was replicated exactly on my own camera, it is likely
an SDK software issue rather than a hardware fault. I will label this
discussion as "bug" so that the RealSense team can track and investigate it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6008?email_source=notifications&email_token=AHZ5PK7F74BVNPM2WWJ4S7LRGYULNA5CNFSM4LE4ECZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOLEOEQ#issuecomment-597051154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZ5PK2DG24EC4FTUMUPFKTRGYULNANCNFSM4LE4ECZA
.

I am not part of the RealSense developer team and are part of the GitHub support team.  So I can highlight issues with tags for other team members to follow up on but cannot influence their development timetable, so I cannot provide a time estimate for a bug-fix if it is decided to be a bug.  Thanks for your patience..

Thank you.
On Tue, 10 Mar, 2020, 6:09 PM MartyG-RealSense<EMAIL_ADDRESS>wrote:

I am not part of the RealSense developer team and are part of the GitHub
support team. So I can highlight issues with tags for other team members to
follow up on but cannot influence their development timetable, so I cannot
provide a time estimate for a bug-fix if it is decided to be a bug. Thanks
for your patience..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/issues/6008?email_source=notifications&email_token=AHZ5PK2UKDKCNMYADFHQ7DDRGYYGJA5CNFSM4LE4ECZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOLHQIQ#issuecomment-597063714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZ5PKYG76RAZFLFMUNXUBTRGYYGJANCNFSM4LE4ECZA
.

I am also experiencing issues with Motion Module Failure when running RealSense viewer on Ubuntu 18.04. The message appears, but the viewer still works fine. It does affect the ROS Rtabmap example in realsense-ros though. Occasionally, the description for the error reads: "Motion Module force pause". I am also running firmware <IP_ADDRESS> and librealsense 2.33.1.
Any help would be greatly appreciated!

@justin-chau  I did extensive further research on the D435i motion module 'failure' and 'force pause' errors.  There does not seem to be a clear solution available at the moment, unfortunately.  Raspberry Pi 4 in particular seems to be vulnerable to having IMU problems.
https://github.com/IntelRealSense/librealsense/issues/4979#issuecomment-540456439
I added a "Bug" label to this discussion 9 days ago, meaning that the issue will be kept open and will be able to be tracked by the RealSense team.

Thanks for letting me know. I may try the installation method you described if I keep having issues. If I do, I will update my findings here.
Thanks again!

Case closed due to reported bug not being reported by other users recently.

I am experiencing the Motion Module failure error on 2.34.0 and FW <IP_ADDRESS>. Everything looks fine on the realsense viewer, but I receive 'Warning: Some linear velocity entries in parameter imu0_config are listed true, but an sensor_msgs/Imu contains no information about linear velocities' when launching with opensource_tracking.launch.

@Andyshen555   I researched your problem extensively but could not find any information on the error message that you quoted.  Are you using the D435i SLAM guide please?
https://github.com/IntelRealSense/realsense-ros/wiki/SLAM-with-D435i

Yes I'm using that. It worked for us for over a year and my last successful usage was yesterday. I'm sure that I have not hit the camera or have done anything that can physically damage the camera. By the way, I'd like to report that my laptop (ubuntu 18.04) recognizes the IMU as it belongs to the computer and rotates my desktop when I rotate the camera. Could that be a problem?

@Andyshen555   A physical knock would likely have not stopped the IMU from functioning if it had occurred.  And I have not heard of an IMU-equipped RealSense camera being able to rotate a computer desktop display when a RealSense application is not running.  It makes sense for computers to be able to detect gyroscopes though in order to rotate the screen on tablet computers.  I recommend turning off screen rotation in Ubuntu.
https://askubuntu.com/questions/1035209/how-to-turn-off-screen-rotation-in-ubuntu-18-04-lts
Do you still get the error messages if you unplug the camera and then put it back in after the messages occur?

For the first time I turn on IMU, it reports nothing, but if I switch it off and turn on again, I get the error every time. However, unplugging does nothing to the ROS error. I'll send the ubuntu log in the next comment

andy1234@andyThinkpad:~$ roslaunch realsense2_camera opensource_tracking.launch ... logging to /home/andy1234/.ros/log/78fa3306-a49f-11ea-b7f1-d46d6d655e19/roslaunch-andyThinkpad-6239.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://andyThinkpad:41673/
SUMMARY
CLEAR PARAMETERS

/ukf_se/

PARAMETERS

/ImuFilter/_publish_tf: False
/ImuFilter/_world_frame: enu
/ImuFilter/use_mag: False
/camera/realsense2_camera/accel_fps: 250
/camera/realsense2_camera/accel_frame_id: camera_accel_frame
/camera/realsense2_camera/accel_optical_frame_id: camera_accel_opti...
/camera/realsense2_camera/align_depth: True
/camera/realsense2_camera/aligned_depth_to_color_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye2_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_fisheye_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra1_frame_id: camera_aligned_de...
/camera/realsense2_camera/aligned_depth_to_infra2_frame_id: camera_aligned_de...
/camera/realsense2_camera/allow_no_texture_points: False
/camera/realsense2_camera/base_frame_id: camera_link
/camera/realsense2_camera/calib_odom_file:
/camera/realsense2_camera/clip_distance: -2.0
/camera/realsense2_camera/color_fps: 30
/camera/realsense2_camera/color_frame_id: camera_color_frame
/camera/realsense2_camera/color_height: 480
/camera/realsense2_camera/color_optical_frame_id: camera_color_opti...
/camera/realsense2_camera/color_width: 640
/camera/realsense2_camera/depth_fps: 30
/camera/realsense2_camera/depth_frame_id: camera_depth_frame
/camera/realsense2_camera/depth_height: 480
/camera/realsense2_camera/depth_optical_frame_id: camera_depth_opti...
/camera/realsense2_camera/depth_width: 640
/camera/realsense2_camera/device_type:
/camera/realsense2_camera/enable_accel: True
/camera/realsense2_camera/enable_color: True
/camera/realsense2_camera/enable_depth: True
/camera/realsense2_camera/enable_fisheye1: True
/camera/realsense2_camera/enable_fisheye2: True
/camera/realsense2_camera/enable_fisheye: True
/camera/realsense2_camera/enable_gyro: True
/camera/realsense2_camera/enable_infra1: True
/camera/realsense2_camera/enable_infra2: True
/camera/realsense2_camera/enable_pointcloud: False
/camera/realsense2_camera/enable_sync: False
/camera/realsense2_camera/filters:
/camera/realsense2_camera/fisheye1_frame_id: camera_fisheye1_f...
/camera/realsense2_camera/fisheye1_optical_frame_id: camera_fisheye1_o...
/camera/realsense2_camera/fisheye2_frame_id: camera_fisheye2_f...
/camera/realsense2_camera/fisheye2_optical_frame_id: camera_fisheye2_o...
/camera/realsense2_camera/fisheye_fps: 30
/camera/realsense2_camera/fisheye_frame_id: camera_fisheye_frame
/camera/realsense2_camera/fisheye_height: 480
/camera/realsense2_camera/fisheye_optical_frame_id: camera_fisheye_op...
/camera/realsense2_camera/fisheye_width: 640
/camera/realsense2_camera/gyro_fps: 400
/camera/realsense2_camera/gyro_frame_id: camera_gyro_frame
/camera/realsense2_camera/gyro_optical_frame_id: camera_gyro_optic...
/camera/realsense2_camera/imu_optical_frame_id: camera_imu_optica...
/camera/realsense2_camera/infra1_frame_id: camera_infra1_frame
/camera/realsense2_camera/infra1_optical_frame_id: camera_infra1_opt...
/camera/realsense2_camera/infra2_frame_id: camera_infra2_frame
/camera/realsense2_camera/infra2_optical_frame_id: camera_infra2_opt...
/camera/realsense2_camera/infra_fps: 30
/camera/realsense2_camera/infra_height: 480
/camera/realsense2_camera/infra_width: 640
/camera/realsense2_camera/initial_reset: False
/camera/realsense2_camera/json_file_path:
/camera/realsense2_camera/linear_accel_cov: 1.0
/camera/realsense2_camera/odom_frame_id: camera_odom_frame
/camera/realsense2_camera/pointcloud_texture_index: 0
/camera/realsense2_camera/pointcloud_texture_stream: RS2_STREAM_COLOR
/camera/realsense2_camera/pose_frame_id: camera_pose_frame
/camera/realsense2_camera/pose_optical_frame_id: camera_pose_optic...
/camera/realsense2_camera/publish_odom_tf: True
/camera/realsense2_camera/publish_tf: True
/camera/realsense2_camera/rosbag_filename:
/camera/realsense2_camera/serial_no:
/camera/realsense2_camera/tf_publish_rate: 0.0
/camera/realsense2_camera/topic_odom_in: odom_in
/camera/realsense2_camera/unite_imu_method: linear_interpolation
/camera/realsense2_camera/usb_port_id:
/points_xyzrgb/approx_sync: True
/points_xyzrgb/decimation: 4.0
/points_xyzrgb/voxel_size: 0.0
/rosdistro: melodic
/rosversion: 1.14.5
/rtabmap/rgbd_odometry/approx_sync: True
/rtabmap/rgbd_odometry/config_path:
/rtabmap/rgbd_odometry/frame_id: camera_link
/rtabmap/rgbd_odometry/ground_truth_base_frame_id:
/rtabmap/rgbd_odometry/ground_truth_frame_id:
/rtabmap/rgbd_odometry/guess_frame_id:
/rtabmap/rgbd_odometry/guess_min_rotation: 0.0
/rtabmap/rgbd_odometry/guess_min_translation: 0.0
/rtabmap/rgbd_odometry/odom_frame_id: odom
/rtabmap/rgbd_odometry/publish_tf: True
/rtabmap/rgbd_odometry/queue_size: 10
/rtabmap/rgbd_odometry/subscribe_rgbd: False
/rtabmap/rgbd_odometry/wait_for_transform_duration: 0.2
/rtabmap/rgbd_odometry/wait_imu_to_init: False
/rtabmap/rtabmap/Mem/IncrementalMemory: true
/rtabmap/rtabmap/Mem/InitWMWithAllNodes: false
/rtabmap/rtabmap/approx_sync: True
/rtabmap/rtabmap/config_path:
/rtabmap/rtabmap/database_path: ~/.ros/rtabmap.db
/rtabmap/rtabmap/frame_id: camera_link
/rtabmap/rtabmap/ground_truth_base_frame_id:
/rtabmap/rtabmap/ground_truth_frame_id:
/rtabmap/rtabmap/landmark_angular_variance: 9999.0
/rtabmap/rtabmap/landmark_linear_variance: 0.0001
/rtabmap/rtabmap/map_frame_id: map
/rtabmap/rtabmap/odom_frame_id:
/rtabmap/rtabmap/odom_sensor_sync: False
/rtabmap/rtabmap/odom_tf_angular_variance: 1.0
/rtabmap/rtabmap/odom_tf_linear_variance: 1.0
/rtabmap/rtabmap/publish_tf: True
/rtabmap/rtabmap/queue_size: 10
/rtabmap/rtabmap/scan_normal_k: 0
/rtabmap/rtabmap/subscribe_depth: True
/rtabmap/rtabmap/subscribe_odom_info: True
/rtabmap/rtabmap/subscribe_rgbd: False
/rtabmap/rtabmap/subscribe_scan: False
/rtabmap/rtabmap/subscribe_scan_cloud: False
/rtabmap/rtabmap/subscribe_stereo: False
/rtabmap/rtabmap/subscribe_user_data: False
/rtabmap/rtabmap/wait_for_transform_duration: 0.2
/ukf_se/acceleration_gains: [0.8, 0.0, 0.0, 0...
/ukf_se/acceleration_limits: [1.3, 0.0, 0.0, 0...
/ukf_se/alpha: 0.001
/ukf_se/base_link_frame: camera_link
/ukf_se/beta: 2
/ukf_se/control_config: [True, False, Fal...
/ukf_se/control_timeout: 0.2
/ukf_se/debug: False
/ukf_se/debug_out_file: /path/to/debug/fi...
/ukf_se/deceleration_gains: [1.0, 0.0, 0.0, 0...
/ukf_se/deceleration_limits: [1.3, 0.0, 0.0, 0...
/ukf_se/frequency: 300
/ukf_se/imu0: /imu/data
/ukf_se/imu0_config: [False, False, Fa...
/ukf_se/imu0_differential: True
/ukf_se/imu0_linear_acceleration_rejection_threshold: 0.8
/ukf_se/imu0_nodelay: False
/ukf_se/imu0_pose_rejection_threshold: 0.8
/ukf_se/imu0_queue_size: 5
/ukf_se/imu0_relative: False
/ukf_se/imu0_remove_gravitational_acceleration: True
/ukf_se/imu0_twist_rejection_threshold: 0.8
/ukf_se/initial_estimate_covariance: ['1e-9', 0, 0, 0,...
/ukf_se/kappa: 0
/ukf_se/map_frame: map
/ukf_se/odom0: rtabmap/odom
/ukf_se/odom0_config: [True, True, True...
/ukf_se/odom0_differential: False
/ukf_se/odom0_nodelay: False
/ukf_se/odom0_pose_rejection_threshold: 10000000
/ukf_se/odom0_queue_size: 2
/ukf_se/odom0_relative: True
/ukf_se/odom0_twist_rejection_threshold: 10000000
/ukf_se/odom1: example/another_odom
/ukf_se/odom1_config: [False, False, Tr...
/ukf_se/odom1_differential: False
/ukf_se/odom1_nodelay: False
/ukf_se/odom1_pose_rejection_threshold: 2
/ukf_se/odom1_queue_size: 2
/ukf_se/odom1_relative: True
/ukf_se/odom1_twist_rejection_threshold: 0.2
/ukf_se/odom_frame: odom
/ukf_se/pose0: example/pose
/ukf_se/pose0_config: [True, True, Fals...
/ukf_se/pose0_differential: True
/ukf_se/pose0_nodelay: False
/ukf_se/pose0_queue_size: 5
/ukf_se/pose0_rejection_threshold: 2
/ukf_se/pose0_relative: False
/ukf_se/print_diagnostics: True
/ukf_se/process_noise_covariance: [0.05, 0, 0, 0, 0...
/ukf_se/sensor_timeout: 0.1
/ukf_se/stamped_control: False
/ukf_se/transform_time_offset: 0.0
/ukf_se/transform_timeout: 0.0
/ukf_se/twist0: example/twist
/ukf_se/twist0_config: [False, False, Fa...
/ukf_se/twist0_nodelay: False
/ukf_se/twist0_queue_size: 3
/ukf_se/twist0_rejection_threshold: 2
/ukf_se/two_d_mode: False
/ukf_se/use_control: False
/ukf_se/world_frame: odom

NODES
/camera/
realsense2_camera (nodelet/nodelet)
realsense2_camera_manager (nodelet/nodelet)
/rtabmap/
rgbd_odometry (rtabmap_ros/rgbd_odometry)
rtabmap (rtabmap_ros/rtabmap)
/
ImuFilter (imu_filter_madgwick/imu_filter_node)
points_xyzrgb (nodelet/nodelet)
rviz (rviz/rviz)
ukf_se (robot_localization/ukf_localization_node)
auto-starting new master
process[master]: started with pid [6249]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 78fa3306-a49f-11ea-b7f1-d46d6d655e19
process[rosout-1]: started with pid [6260]
started core service [/rosout]
process[camera/realsense2_camera_manager-2]: started with pid [6268]
process[camera/realsense2_camera-3]: started with pid [6269]
process[ImuFilter-4]: started with pid [6270]
process[rtabmap/rgbd_odometry-5]: started with pid [6271]
process[rtabmap/rtabmap-6]: started with pid [6281]
process[rviz-7]: started with pid [6284]
process[points_xyzrgb-8]: started with pid [6288]
[ INFO] [1591081543.714972508]: Initializing nodelet with 4 worker threads.
process[ukf_se-9]: started with pid [6290]
type is rtabmap_ros/point_cloud_xyzrgb
[ WARN] [1591081544.034165686]: Warning: Some linear velocity entries in parameter imu0_config are listed true, but an sensor_msgs/Imu contains no information about linear velocities
[ INFO] [1591081544.086758796]: RealSense ROS v2.2.13
[ INFO] [1591081544.086937441]: Running with LibRealSense v2.33.1
[ INFO] [1591081544.227041973]:
[ INFO] [1591081544.379808070]: Starting node...
[ WARN] [1591081544.552616030]: Failed to meet update rate! Took 0.016304024000000000294
[ WARN] [1591081544.552768004]: Failed to meet update rate! Took 0.013179006000000000054
[ WARN] [1591081544.592639664]: Failed to meet update rate! Took 0.016540097000000000133
[ WARN] [1591081544.592800818]: Failed to meet update rate! Took 0.013408794000000001656
[ WARN] [1591081544.636609206]: Failed to meet update rate! Took 0.017155591000000001284
[ WARN] [1591081544.636769362]: Failed to meet update rate! Took 0.014015503000000000336
[ WARN] [1591081544.660676586]: Failed to meet update rate! Took 0.013906261000000001357
[ WARN] [1591081544.660849984]: Failed to meet update rate! Took 0.010787520000000000095
[ WARN] [1591081544.728593568]: Failed to meet update rate! Took 0.014421251000000001249
[ WARN] [1591081544.728746467]: Failed to meet update rate! Took 0.01127601400000000087
[ WARN] [1591081544.748745100]: Failed to meet update rate! Took 0.016661846000000000989
[ WARN] [1591081544.750115274]: Failed to meet update rate! Took 0.014715227000000000862
[ WARN] [1591081544.760449333]: Failed to meet update rate! Took 0.0082576469999999999039
[ INFO] [1591081544.761104399]: Initializing nodelet with 4 worker threads.
[ INFO] [1591081544.777118325]: Initializing nodelet with 4 worker threads.
02/06 03:05:44,908 WARNING [140607242327808] (types.cpp:49) Accel Sensitivity:hwmon command 0x4f failed. Error type: No data to return (-21).
02/06 03:05:44,909 WARNING [140607242327808] (ds5-motion.cpp:463) IMU Calibration is not available, see the previous message
[ INFO] [1591081544.994754942]: Device with serial number<PHONE_NUMBER>23 was found.
[ INFO] [1591081544.995242356]: Device with physical ID 2-4-4 was found.
[ INFO] [1591081544.995583924]: Device with name Intel RealSense D435I was found.
[ INFO] [1591081544.998438076]: Device with port number 2-4 was found.
[ INFO] [1591081545.013558662]: getParameters...
[ WARN] [1591081545.256530273]: Failed to meet update rate! Took 0.010968333000000000249
[ WARN] [1591081545.256933568]: Failed to meet update rate! Took 0.0080889440000000006892
[ WARN] [1591081545.314445973]: Failed to meet update rate! Took 0.0075444110000000008665
[ INFO] [1591081545.394360588]: setupDevice...
[ INFO] [1591081545.394653465]: JSON file is not provided
[ INFO] [1591081545.394868675]: ROS Node Namespace: camera
[ INFO] [1591081545.395061312]: Device Name: Intel RealSense D435I
[ INFO] [1591081545.395244944]: Device Serial No:<PHONE_NUMBER>23
[ INFO] [1591081545.395428809]: Device physical port: 2-4-4
[ INFO] [1591081545.395622425]: Device FW version: <IP_ADDRESS>
[ INFO] [1591081545.395815855]: Device Product ID: 0x0B3A
[ INFO] [1591081545.396438094]: Enable PointCloud: Off
[ INFO] [1591081545.396806406]: Align Depth: On
[ INFO] [1591081545.397179930]: Sync Mode: On
[ INFO] [1591081545.397558423]: Device Sensors:
[ INFO] [1591081545.397936424]: Stereo Module was found.
[ INFO] [1591081545.398280407]: RGB Camera was found.
[ INFO] [1591081545.398595502]: Motion Module was found.
[ INFO] [1591081545.398961497]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591081545.399300297]: (Fisheye, 1) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591081545.399615212]: (Fisheye, 2) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591081545.399928405]: (Pose, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591081545.400274943]: num_filters: 0
[ INFO] [1591081545.400624549]: Setting Dynamic reconfig parameters.
[ INFO] [1591081545.605407920]: Approximate time sync = true
[ INFO] [1591081545.605909525]: /rtabmap/rtabmap(maps): map_filter_radius          = 0.000000
[ INFO] [1591081545.605978638]: /rtabmap/rtabmap(maps): map_filter_angle           = 30.000000
[ INFO] [1591081545.606012645]: /rtabmap/rtabmap(maps): map_cleanup                = true
[ INFO] [1591081545.606042467]: /rtabmap/rtabmap(maps): map_always_update          = false
[ INFO] [1591081545.606069845]: /rtabmap/rtabmap(maps): map_empty_ray_tracing      = true
[ INFO] [1591081545.606097974]: /rtabmap/rtabmap(maps): cloud_output_voxelized     = true
[ INFO] [1591081545.606126189]: /rtabmap/rtabmap(maps): cloud_subtract_filtering   = false
[ INFO] [1591081545.606154857]: /rtabmap/rtabmap(maps): cloud_subtract_filtering_min_neighbors = 2
[ INFO] [1591081545.652107119]: /rtabmap/rtabmap(maps): octomap_tree_depth         = 16
[ INFO] [1591081545.724241079]: rtabmap: frame_id      = camera_link
[ INFO] [1591081545.724430639]: rtabmap: map_frame_id  = map
[ INFO] [1591081545.724811079]: rtabmap: use_action_for_goal  = false
[ INFO] [1591081545.725105119]: rtabmap: tf_delay      = 0.050000
[ INFO] [1591081545.725375647]: rtabmap: tf_tolerance  = 0.100000
[ INFO] [1591081545.725654456]: rtabmap: odom_sensor_sync   = false
[ WARN] [1591081545.764945606]: Failed to meet update rate! Took 0.0080447110000000012636
[ INFO] [1591081545.842872128]: Odometry: frame_id               = camera_link
[ INFO] [1591081545.842941340]: Odometry: odom_frame_id          = odom
[ INFO] [1591081545.842968684]: Odometry: publish_tf             = true
[ INFO] [1591081545.843000662]: Odometry: wait_for_transform     = true
[ INFO] [1591081545.843050616]: Odometry: wait_for_transform_duration  = 0.200000
[ INFO] [1591081545.843121876]: Odometry: initial_pose           = xyz=0.000000,0.000000,0.000000 rpy=0.000000,-0.000000,0.000000
[ INFO] [1591081545.843157406]: Odometry: ground_truth_frame_id  =
[ INFO] [1591081545.843189549]: Odometry: ground_truth_base_frame_id =
[ INFO] [1591081545.843221975]: Odometry: config_path            =
[ INFO] [1591081545.843253868]: Odometry: publish_null_when_lost = true
[ INFO] [1591081545.843286101]: Odometry: guess_frame_id         =
[ INFO] [1591081545.843319156]: Odometry: guess_min_translation  = 0.000000
[ INFO] [1591081545.843352585]: Odometry: guess_min_rotation     = 0.000000
[ INFO] [1591081545.843385389]: Odometry: guess_min_time         = 0.000000
[ INFO] [1591081545.843410985]: Odometry: expected_update_rate   = 0.000000 Hz
[ INFO] [1591081545.843438311]: Odometry: wait_imu_to_init       = false
[ WARN] [1591081545.900443060]: Failed to meet update rate! Took 0.0068817600000000006544
[ WARN] [1591081545.914849565]: Failed to meet update rate! Took 0.011268687000000001189
[ WARN] [1591081545.915090721]: Failed to meet update rate! Took 0.0082184149999999997482
[ WARN] [1591081546.236452058]: Failed to meet update rate! Took 0.011379524000000000236
[ WARN] [1591081546.236537007]: Failed to meet update rate! Took 0.0081575099999999997613
[ INFO] [1591081546.244655218]: Setting RTAB-Map parameter "Mem/IncrementalMemory"="true"
[ INFO] [1591081546.245468621]: Setting RTAB-Map parameter "Mem/InitWMWithAllNodes"="false"
[ WARN] [1591081546.492416936]: Failed to meet update rate! Took 0.0092192210000000014009
[ INFO] [1591081546.776832029]: RGBDOdometry: approx_sync    = true
[ INFO] [1591081546.776976642]: RGBDOdometry: queue_size     = 10
[ INFO] [1591081546.777036377]: RGBDOdometry: subscribe_rgbd = false
[ INFO] [1591081546.777066693]: RGBDOdometry: rgbd_cameras   = 1
[ INFO] [1591081546.818489011]:
/rtabmap/rgbd_odometry subscribed to (approx sync):
/camera/color/image_raw,
/camera/aligned_depth_to_color/image_raw,
/camera/color/camera_info
[ INFO] [1591081547.722862269]: RTAB-Map detection rate = 1.000000 Hz
[ INFO] [1591081547.723139947]: rtabmap: Deleted database "/home/andy1234/.ros/rtabmap.db" (--delete_db_on_start or -d are set).
[ INFO] [1591081547.723212629]: rtabmap: Using database from "/home/andy1234/.ros/rtabmap.db" (0 MB).
[ INFO] [1591081547.842008213]: rtabmap: Database version = "0.19.3".
[ INFO] [1591081547.875108243]: /rtabmap/rtabmap: subscribe_depth = true
[ INFO] [1591081547.875225590]: /rtabmap/rtabmap: subscribe_rgb = true
[ INFO] [1591081547.875364418]: /rtabmap/rtabmap: subscribe_stereo = false
[ INFO] [1591081547.875481120]: /rtabmap/rtabmap: subscribe_rgbd = false (rgbd_cameras=1)
[ INFO] [1591081547.875591914]: /rtabmap/rtabmap: subscribe_odom_info = true
[ INFO] [1591081547.875707114]: /rtabmap/rtabmap: subscribe_user_data = false
[ INFO] [1591081547.875813009]: /rtabmap/rtabmap: subscribe_scan = false
[ INFO] [1591081547.875916360]: /rtabmap/rtabmap: subscribe_scan_cloud = false
[ INFO] [1591081547.876016789]: /rtabmap/rtabmap: queue_size    = 10
[ INFO] [1591081547.876131944]: /rtabmap/rtabmap: approx_sync   = true
[ INFO] [1591081547.876341795]: Setup depth callback
[ INFO] [1591081547.901267529]:
/rtabmap/rtabmap subscribed to (approx sync):
/rtabmap/odom,
/camera/color/image_raw,
/camera/aligned_depth_to_color/image_raw,
/camera/color/camera_info,
/rtabmap/odom_info
[ INFO] [1591081547.912618970]: rtabmap 0.19.3 started...
[ INFO] [1591081550.675764549]: Done Setting Dynamic reconfig parameters.
[ INFO] [1591081550.714708247]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16
[ INFO] [1591081550.715344696]: infra1 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
[ INFO] [1591081550.715875625]: infra2 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
[ INFO] [1591081550.751110297]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8
[ INFO] [1591081550.757073576]: setupPublishers...
[ INFO] [1591081550.761524231]: Expected frequency for depth = 30.00000
[ INFO] [1591081550.824257941]: Expected frequency for infra1 = 30.00000
[ INFO] [1591081550.863859318]: Expected frequency for aligned_depth_to_infra1 = 30.00000
[ INFO] [1591081550.907113144]: Expected frequency for infra2 = 30.00000
[ INFO] [1591081550.940093909]: Expected frequency for color = 30.00000
[ INFO] [1591081550.970127961]: Expected frequency for aligned_depth_to_color = 30.00000
[ INFO] [1591081550.996930926]: Start publisher IMU
[ INFO] [1591081551.002086267]: setupStreams...
[ INFO] [1591081551.054708680]: insert Depth to Stereo Module
[ INFO] [1591081551.055181895]: insert Color to RGB Camera
[ INFO] [1591081551.055507765]: insert Infrared to Stereo Module
[ INFO] [1591081551.055803401]: insert Infrared to Stereo Module
[ INFO] [1591081551.056295049]: insert Gyro to Motion Module
[ INFO] [1591081551.056461712]: insert Accel to Motion Module
02/06 03:05:51,107 WARNING [140606995150592] (uvc-device.cpp:664) interrupt event received: 1, 3, 0, 7, 0, 10,
[ WARN] [1591081551.278648694]: Could not obtain transform from camera_imu_optical_frame to camera_link. Error was "camera_link" passed to lookupTransform argument target_frame does not exist.
[ WARN] [1591081551.333065252]: Transform from camera_imu_optical_frame to camera_link was unavailable for the time requested. Using latest instead.
[ WARN] [1591081551.356735720]: Failed to meet update rate! Took 0.0067521890000000004545
02/06 03:05:51,374 WARNING [140607137761024] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
[ INFO] [1591081551.383752293]: SELECTED BASE:Depth, 0
^C[ INFO] [1591081551.468877748]: RealSense Node Is Up!
[ WARN] [1591081551.479691835]: Could not get transform from camera_link to camera_imu_optical_frame after 0.200000 seconds (for stamp=1591081551.324973)! Error="Lookup would require extrapolation into the past.  Requested time<PHONE_NUMBER>.324972630 but the earliest data is at time<PHONE_NUMBER>.329734325, when looking up transform from frame [camera_imu_optical_frame] to frame [camera_link]. canTransform returned after 0.201776 timeout was 0.2.".
   I note the error Accel Sensitivity:hwmon command 0x4f failed. Error type: No data to return (-21) though.  This is typically generated when the D435i's IMU has not been calibrated by the user.  Have you performed a self-calibration of the IMU since you purchased the D435i, please?
https://dev.intelrealsense.com/docs/depth-camera-d435i-imu-calibration

After calibration, realsense-viewer still gives ERROR and IMU still doesn't work on ROS. Also, some new problems arise. The accelerometer reads around 9.6 for all 6 axis before calibration and now it reads 9.4 camera facing down and 10.2 camera facing up, 9.5 cable facing down and 10.1 cable facing up. This is exactly what happened to my old camera which I used during SDK 2.17~2.20. I though the camera was broken and brought a new one (current one). What should I do now when I can't get a good calibration? I have recalibrated dozens of times lol

Another user had similar values to yours after IMU calibration.  They were advised that after IMU calibration, an option called Enable Motion Correction should become available in the Viewer.  This corrects the IMU values so that they approach closer to the ideal of 9.8.
https://github.com/IntelRealSense/librealsense/issues/4751#issuecomment-527138458
Correction of acceleration values is necessary because the IMU component used in the D435i does not have built-in calibration.

Mine are almost identical no matter the Enable Motion Correction is on or off. They still read something close to 9.5, 10.1 though.

If you still have the old "broken" D435i camera, I wonder if you could try swapping over their USB cables to eliminate the possibility that the ROS log errors are related to a bad USB cable.

Nothing changed doing a cable swap.

I got this when running the rs_camera.launch
02/06 15:04:17,549 WARNING [140687055988480] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
[ WARN] [1591124657.685268432]: Hardware Notification:RT IC2 Config error,1.59112e+12,Error,Hardware Error
[ERROR] [1591124657.685460059]: Performing Hardware Reset.

Were all the tests with the current and previous camera carried out on the same computer please?  If yes, do you have the option of trying the camera on a different computer?

[ INFO] [1591125014.176830764]: insert Accel to Motion Module
02/06 15:10:14,218 WARNING [139725679617792] (uvc-device.cpp:664) interrupt event received: 1, 3, 0, 7, 0, 10,
[ INFO] [1591125014.471291072]: SELECTED BASE:Depth, 0
[ INFO] [1591125014.526446177]: RealSense Node Is Up!
02/06 15:10:14,588 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
02/06 15:10:14,649 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
02/06 15:10:14,752 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
02/06 15:10:14,813 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: No data available, number: 61
02/06 15:10:14,894 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
[ WARN] [1591125014.945867324]: Hardware Notification:Motion Module failure,1.59113e+12,Error,Hardware Error
02/06 15:10:15,075 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
02/06 15:10:15,257 WARNING [139725889337088] (messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11

Currently I don't have any other Ubuntu machines available, but the IMU failure message showed up in the realsense viewer appeared on 2 win10 and a Ubuntu 18.04.

Doronhi the RealSense ROS wrapper developer has said in the recent past that the Resource temporarily unavailable error message can be related to lack of system resources - the app can't keep up with the incoming flow of images.  Enabling CUDA support can help with this if the computer has an Nvidia graphics GPU.

Bandwidth / system resource could be a problem as you said, so I disabled RGB, Resource temporarily unavailable error message is gone.

The IMU calibration seems to have fixed itself somehow. The norms read in every axis goes back to 9.8, which is great.

The problem comes back to IMU not giving out info as it should ::
[ WARN] [1591132803.683814185]: Warning: Some linear velocity entries in parameter imu0_config are listed true, but an sensor_msgs/Imu contains no information about linear velocities
[ WARN] [1591132809.978068997]: Could not obtain transform from camera_imu_optical_frame to camera_link. Error was "camera_link" passed to lookupTransform argument target_frame does not exist.
[ WARN] [1591132810.196124894]: /rtabmap/rgbd_odometry: Did not receive data since 5 seconds!

@Andyshen555  Great news that you made progress with the errors!
Regarding the remaining errors in ROS: there is no information about 2 of the 3 listed errors at all on the internet, so it is difficult to diagnose the problem from them.  The imu0_config that it refers to though seems to be related to robot localization.  Whilst sensor_msgs/Imu holds data from an IMU.
There is a lot more information available about the third error /rtabmap/rgbd_odometry: Did not receive data since 5 seconds!.  This may tie in to the availability of processing resources.  Others who have experienced this error suggest checking rqt_graph to see what is happening during processing.  If 30 FPS is being used then a publishing frequency of 30 hz would be expected to be displayed on the rqt_graph.  Significantly less than 30 may suggest that there is a problem that is causing the errors.
http://wiki.ros.org/rqt_graph


Class docstring template for curve fit analysis.

This is the curve analysis class template I wrote with @eggerdj
    r"""Single line description of this analysis.

    Overview
        This analysis takes two series. This series is fit by the ...
        You can write technical aspect or add some reference here.

    Fit Model
        The fit is based on the following functions.

        .. math::

            F_1(x_1) &= a x_1^2 + b x_1 + c  ... {\rm Experiment 1}\\
            F_2(x_2) &= d x_2^2 + e x_2 + c  ... {\rm Experiment 2}

    Fit Parameters
        - :math:`a`: Description of parameter a
        - :math:`b`: Description of parameter b
        ...

    Initial Guesses
        - :math:`a`: This parameter is estimated by math:`\sqrt{y_1 - c - b x_1} / x_1` where ...
        - :math:`b`: This parameter is estimated by ...  some very very
          long description.  # This requires exactly two spaces before the sentence to ignore line feed.
        ...

    Bounds
        - :math:`a`: [-1, 1]
        - :math:`b`: [min(:math:`x_1`), max(:math:`x_1`)]
        ...

    """

Parameters can be in latex format for readability, e.g. \sigma, but the representation should be carefully chosen so that user can easily find the corresponding parameter in analysis result.
This template will nicely show all information that user may need. Below is the example of SpectroscopyAnalysis.

This is nice and helpful, thanks. Will follow this pattern.

This is nice, I htink we should also have all analysis classes have a separate Analysis Options section to list and describe all the supported kwargs for set_analysis_options, and  Experiment classes should also have an Experiment Options section.

This is what I ended up doing in the tomography PR based off this example:
For Experiment subclasses:
"""Short description

Overview
    Experiment overview. If you included a lot of details on analysis in Analysis class doc
    should include something like See :class:`AnalysisClass` documentation for
    additional information on experiment analysis.

Analysis Class:
    Link to analysis class

Experiment Options:
    - **option** (``Type``): description

Analysis Options:
    - **option** (``Type``): description
"""

For analysis
"""Short description

Overview
     Overview of analysis

Analysis Options
     - **option** (``Type``): description

Extra headings and details
    Include extra sections and details ie Naoki's example for curve fit example.
    These could go before or after analysis options heading.
"""

The above formatting for options kwargs makes them render the same as function arg documentation. I couldn't find a way to do this automatically without the manual formatting.
Perhaps in both classes we should also include a heading for Analysis Result to document the returned data frields.


enable deep clone of multipolygon endss

Using deep clone of multipolygon endss in ol.geom.MultiPolygon.prototype.clone. Previously used flat clone caused the cloned geometry to not be completely decoupled from the original. Adresses issue https://github.com/openlayers/ol3/issues/3326

Thanks for the contribution @Kenny806.
Fixes #3326.


Fix Query.Builder.From.escape/1 typespec

Pretty sure the typespec return was back to front.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Move IstioCNI.spec.values.cni to IstioCNI.spec.values?

Is this the right place to submit this?

[X] This is not a question about how to use the sail-operator

Bug Description
The CNI values are currently specified in IstioCNI.spec.values.cni, which looks odd, since we already know we're configuring CNI values. The same applies to ZTunnel (ZTunnel.spec.values.ztunnel).
Should we move the values one level up (to IstioCNI.spec.values and ZTunnel.spec.values), since it's clear that those values are for CNI/ZTunnel?
For Istio, things are a bit different, since we don't have Istio.spec.values.istio, but Istio.spec.values.pilot (and others), but it might make sense to move these values up also. In all three cases, the charts already do use this structure.
Operator Version
0.1.0
Link to Gist with Logs
No response
Additional Information
No response

Yes, I think this is a good idea


[RESTEASY-1596] deleteOnExit on temp file only when the Cleaneable me…

...chanism eventually fails in deleting it

We have a test in Resteasy for this, EntityBufferingInFileTest.  Currently it is not deploying because it relies on
org.jboss.resteasy.resteasy-legacy which is not present on the server.
Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.resteasy.resteasy-legacy
working on getting this to run.

@rsearls can you expain better what you mean? I see two EntityBufferingInFileTest files in the sources (one in testsuite/integration-tests, one in testsuite/legacy-integration-tests) and both are part of the build, hence passing. Is there anything to be enabled in those tests, or do they have to be enriched to cover this ?

@ asoldano  There are 2 tests with identical names,
./testsuite/legacy-integration-tests/src/test/java/org/jboss/resteasy/test/client/EntityBufferingInFileTest.java
./testsuite/integration-tests/src/test/java/org/jboss/resteasy/test/client/EntityBufferingInFileTest.java
The one in legacy-integration-tests is encountered first.  It fails because of the legacy package.
Moving this test a side.  The other one runs.
I'm still try to confirm the desired code is being executed.

@rsearls ok, given the tests passed here though, I'm wondering if you have local changes on them or what.

@ asoldano
531 ApacheHttpClient4Engine line 531 always succeeds in deleting the
file so the warning message is never written.
I ran the test with this
mvn clean verify
-Dserver.home=/home/rsearls/j1/wfly10/wildfly/build/target/wildfly-11.0.0.Beta1-SNAPSHOT
-fn -Dtest=EntityBufferingInFileTest
-Dmaven.test.redirectTestOutputToFile=false
-Djava.io.tmpdir=/tmp/foofoo
-Dmaven.surefire.debug

@rsearls I've manually tested the fix works with the following procedure:

set a debugger breakpoint on line 531 of ApacheHttpClient4Engine
delete the file using a console
step forward with the debugger and let the code fail in deleting the file (as it's not there)
re-create the file that was previously there, using a console
disconnect the debugger and let the test finish
verify the file is not there anymore (as the deleteOnExit causes it to be removed then the JVM shuts down).

As for the legacy test failing, my bet is that's because the server instance you're explicitly telling the testsuite to use is not properly patched to enable the legacy stuff. In this case, to make it easy, simply avoid setting the server.home here and let the testsuite download, patch and run the server he wants.

@asoldano The issue here is that file.deleteOnExit() keeps the reference even when File.delete() succeeds is it correct?
Maybe another option could be to use try-with-resources with with custom file handler implementing Autoclosable (desribed here - http://stackoverflow.com/a/34050507). With this we could avoif the  usage of deleteOnExit() at all. Just a thought.

@kanovotn, yes the issue being fixed here is that deleteOnExit() is always called, as soon as the file is created. So, despite the file being later deleted (unless something wrong happens on the disk), we still have consumed memory that won't be freed till the JVM goes down (there's basically a static LinkedHashSet instance storing the path of the files marked as to be deleted on exit). This is basically a leak.
This said, we already have a mechanism to figure out when to delete those files (see the CleanableSequenceInputStream), so i believe there's no need for additional AutoCloseable abstraction.
I could have simply just removed the deleteOnExit(), actually that's what I did initially; then I thought it would have been better to keep the deleteOnExit() as a safety net, to be used just in case when we go and delete the file, we fail in deleting it, so we give the system a chance to try performing the cleanup just before shutting down. But that's an exceptional scenario.

@asoldano  ok, thank you for explanation.


Disable the LMDB writemap and map_async features when creating a db environment

Does this potentially address STL-957?


This pull request contains the changes for the email templates fom the backend and the frontend. It has 3 types of templates: 1) Single anomaly - with an anomaly card and the screenshot 2) Multiple anomalies - a tabular format, with links to investigate each anomaly, or all at once 3) Daily anomaly report - a tabular format, with a summary on top, and links to investigate each one

Please limit the length of the pull request titles to 50 characters.


Update finagle-core, finagle-mysql, ... to 20.5.0

Updates

com.twitter:finagle-core
com.twitter:finagle-mysql
com.twitter:scrooge-serializer
com.twitter:util-core

from 20.4.1 to 20.5.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.twitter" } ]

labels: library-update, semver-minor

Codecov Report

Merging #399 into develop will increase coverage by 0.09%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #399      +/-   ##
===========================================
+ Coverage    77.13%   77.23%   +0.09%
===========================================
  Files           46       46
  Lines         1041     1041
  Branches        29       29
===========================================
+ Hits           803      804       +1
+ Misses         238      237       -1

Impacted Files
Coverage Δ

.../main/scala/com/twitter/bijection/Bufferable.scala
91.95% <0.00%> (+1.14%)
:arrow_up:

Continue to review full report at Codecov.

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


Implemented Player Controls Animation

Player Controls Animation
Development
We’ve implemented animations for player controls instead of simply hiding. We’ve decided to use CABasicAnimation instead of UIView.animate.
First of all, because we want to use implicit animation. It means that we simply add animation to each view layer and then when position or opacity is changed, these changes are performed animated.
The reason for choosing that way is that our position animation is performed by changing constraints. So to animate these changes using UIView.animate, we had to call a layoutIfNeeded method in its animation block. And it is not what we want to call in viewWillLayoutSubviews. And it also makes a mess, because there are a lot of changes that have to be done only after the animation is completed and it looks very confusing, even in a single completion block.
So we’ve created AnimationDelegate, that now handles everything that has to be done only when the animation is completed.
UIProps Changes
We’ve added some changes to uiProps. Now that we’re not hiding our controls by hiding entire controlsView, each object of uiProps is now also watching the controlsHidden state. So now, in a case when all controls should be hidden, all elements that should be hidden will have isHidden state true.
Animation Types
We have the next list of views and animation types applied to them:

Fade in/Fade out
All buttons that located in the middle (play, pause, playlist buttons etc.), Compass view and Live indicator view and Shadow view.
Slide up/Slide down
Slide down animation is implemented for seekerView and for new bottomItemsView, that now contains settings button, pip button, airplay button and title label. There is a single case when seekerViewwill appear/disappear with fade. It happens when bottomItemsView is visible and we don’t want these views to cross each other.
Slide aside

This animation is applied only to sidebar view that will slide right or left.

Preview

Transition table and Gif from UI

From
To
Animation Type
Gif from UI

Slide

Slide

Slide

Slide

Fade

Fade

Current issues and future improvements

Fix for Sidebar when seeker moves down
Buttons changing each other with slide or fade
Device rotation bugs

Expecting .gif with animations :)

@AndriiMoskvin @AlexeyDemedetskiy and @BogdanBilonog We're looking forward to your review.

@RomanTysiachnik We are expecting gif's with animations as I mentioned in previous comment.

@AndriiMoskvin there already some under the spoiler ;)

900 lines of changes split into several logical PRs.

PR is divided on Animations implementation and on a new demo