Extend replicate_model_fn to work with datasets with arbitrary nested structure of tensors as input_fn

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v1.8.0-0-g93bc2e2072 1.8.0
Python version:  3.5.2
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: CUDA 9.0 / cuDNN 7.0
GPU model and memory: Nvidia K80 (x4)
Exact command to reproduce: python training/train.py

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Feature request: extend tf.contrib.estimator.replicate_model_fn to be usable with a dataset feeder (with arbitrary nested structure of tensors) as input_fn. Currently the _split_batch (in replicate_model_fn.py) can only split flat nested structures.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
Below is traceback from dataset using dict of dict of tensors.
Traceback (most recent call last):
  File "training/train.py", line 82, in <module>
    run_experiment(args.train_files, args.eval_files, hparams)
  File "training/train.py", line 50, in run_experiment
    tf.estimator.train_and_evaluate(_estimator, train_spec, eval_spec)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/training.py", line 439, in train_and_evaluate
    executor.run()
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/training.py", line 518, in run
    self.run_local()
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/training.py", line 650, in run_local
    hooks=train_hooks)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/estimator.py", line 363, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/estimator.py", line 843, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/estimator.py", line 856, in _train_model_default
    features, labels, model_fn_lib.ModeKeys.TRAIN, self.config)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/estimator/estimator.py", line 831, in _call_model_fn
    model_fn_results = self._model_fn(features=features, **kwargs)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/contrib/estimator/python/estimator/replicate_model_fn.py", line 226, in replicated_model_fn
    features, labels, len(devices), device=consolidation_device)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/contrib/estimator/python/estimator/replicate_model_fn.py", line 486, in _split_batch
    feature_shards = split_dictionary(features)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/contrib/estimator/python/estimator/replicate_model_fn.py", line 478, in split_dictionary
    ensure_divisible_by_shards(tensor)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/contrib/estimator/python/estimator/replicate_model_fn.py", line 462, in ensure_divisible_by_shards
    batch_size = ops_lib.convert_to_tensor(sequence).get_shape()[0]
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1014, in convert_to_tensor
    as_ref=False)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/framework/ops.py", line 1104, in internal_convert_to_tensor
    ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/framework/constant_op.py", line 235, in _constant_tensor_conversion_function
    return constant(v, dtype=dtype, name=name)
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/framework/constant_op.py", line 214, in constant
    value, dtype=dtype, shape=shape, verify_shape=verify_shape))
  File "/home/alex/T2/virtualenv/lib/python3.5/site-packages/tensorflow/python/framework/tensor_util.py", line 521, in make_tensor_proto
    "supported type." % (type(values), values))
TypeError: Failed to convert object of type <class 'dict'> to Tensor. Contents: {'input_seq': <tf.Tensor 'IteratorGetNext:4' shape=(128, ?) dtype=int64>, 'stop_token': <tf.Tensor 'IteratorGetNext:3' shape=(128, ?) dtype=float32>, 'target_seq': <tf.Tensor 'IteratorGetNext:2' shape=(128, ?, 80) dtype=float32>}. Consider casting elements to a supported type.

Nagging Assignee @jart: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @jart: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

tf.contrib.estimator.replicate_model_fn is deprecated in favor of tf.contrib.distribute.MirroredStrategy. Have you had a chance to try that? I'm sure feedback on the new API would be welcome.


Page Migrations Overview seems incomplete

This page seems missing a part in the end.
In "Create your first migration" section if you click "Visual studio" tab the text that appears is incomplete.

Dettagli del documento
⚠ Non modificare questa sezione. È necessaria per i collegamenti relativi ai problemi tra docs.microsoft.com ➟ GitHub.

ID: 6e28b0a8-b7e4-4c07-9e60-0df403bbee28
Version Independent ID: 12300b31-6f7b-b75c-970d-693365e77013
Content: Panoramica delle migrazioni - EF Core
Content Source: entity-framework/core/managing-schemas/migrations/index.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @bricelam
Microsoft Alias: avickers

@lucianodelucchi under "Creare il database e lo schema", when I click the Visual Studio tab, I can see "Update-Database", which is the right content. Are you seeing something else?

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


mo.todo

Description
Have a todo list in marimo
Suggested solution
Like, in a sidebar or nav menu, we can jump to each todo and finish our unfinished jobs
Alternative
No response
Additional context
No response

We've talked about adding a variable length version of mo.ui.array/dictionary -- that lets you add and remove entries. That could be used as a TODO list as well as other things.


SST not deploying stack to AWS.

Hi I've been running into a problem deploying a stack to aws with npx sst start so I can try it in my local env.
This is the code for the repo https://github.com/fddayan/react-trpc-api
and this is the error I have been getting

The debug stacks gets deployed correctly and I can see in my aws console.
Any idea what [100%] fail: Your socket connection to the server was not read from or written to within the timeout period. Idle connections will be closed. might be ?
Thanks!

Just to double check, are you running sst start or sst deploy?

Cos it sorta sounds like the upload to AWS failed. Could it be because of your internet connection?

I'm running sst start.... yes, it could be because of my connection. However, it was able to deploy the debug stack and I tried it multiple times and different days. I thought at some point it had to work. I'm not sure how much data is transferring to deploy the stack

This is the stack https://github.com/fddayan/react-trpc-api/blob/master/stacks/MyStack.ts

Thanks, let me ask @fwang to take a look.


systemd: 251.15 -> 251.16

Changelog:
5f8a449eab test-network: add workaround for bug in iproute2 v6.2.0
d95989f4de coredumpctl: fix bash completion matching
11c53ec3b1 test: create temporary units under /run
17af002034 core/transaction: use hashmap_remove_value() to make not remove job with same ID
23bfa90166 fuzz-journal-remote: fix potential fd-leak
67bba19aed fuzz-journal-remote: remove temporary files on exit
86ec045f25 hwdb: update to 46b8c3f5b297ac034f2d024c1f3d84ad2c17f410
fb1078b2e8 sd-journal: make journal_file_copy_entry() return earlier
905553acb1 sd-journal: copy boot ID
6e42053a12 sd-journal: tighten variable scope
3d88973ff6 journal: Don't try to write garbage if journal entry is corrupted
42589738cf core: fix property getter method for NFileDescriptorStore bus property
2d216fdb2c mkosi: disable fedora builds
f8344c2006 test: bump the base VM memory to 768M
f7be8106e8 test: allow overriding $QEMU_MEM when running w/ ASan
f8bd6cd7d6 test: use setpriv instead of su for user switch from root
bbe058c449 test: wrap mkfs.*/mksquashfs/mkswap binaries when running w/ ASan
f7b20156b3 test: bump the D-Bus related timeouts to 120s
085d847ae7 coredump filter: add mask for 'all' using UINT32_MAX, not UINT64_MAX
30a4629e47 coredump filter: fix stack overflow with =all
7ee604ab53 build(deps): bump github/super-linter from 4.9.7 to 4.10.1
b4c431fc7e cryptenroll: fix a memory leak
eeb91ba62e portablectl: add --extension to bash completion
783885a98a man: /usr/lib/systemd/random-seed -> /usr/lib/systemd/systemd-random-seed
3776e1f2ee test: drop uses of "&& { echo 'unexpected success'; exit 1; }"
f12531d653 man: fix LogControl1 manpage example
3fc9c413a9 pam: cache sd-bus separately per module
1f36857e4b pam_systemd_home: clean up sd-bus when called about something else's user
b1f2d0da63 man: clarify sd_bus_default
ce99445126 man: add working example to LogControl1 manpage
479718f743 detect-virt: add message at debug level
42094f7b79 list: fix double evaluation
a09b9fca5b mountpoint-util: check /proc is mounted on failure
47bbd034c3 test: prefix the transient unit with test- to make coverage runs happy
1bbf03374e kmod-setup: bypass heavy virtio-rng check if we are not running in a VM anyway
3411ab6a9a kmod-setup: use STARTSWITH_SET() where appropriate
48b9984e64 creds: make available to all ExecStartPre= and ExecStart= processes
4730d729cb user-util:remove duplicate includes
226ba320d3 virt: Further improve detection of EC2 metal instances
2b003d91ad string-util: add strstrafter()
369b81c021 test: add a couple of tests with invalid UTF-8 characters
cb8e9f29db test: add a simple test for getenv_path_list()
f92b6fe962 shared: add a missing include
78e20624b2 test: stop the test unit when it's not needed anymore
491530f2e7 Synposis and description of networkctl man page reflecting only part of its functionality  (#27264)
42d1f6a067 core/main: fix a typo for --log-target
4e9ed04401 test: add some tests for RuntimeMaxSec
7aa7e9e93d scope: do not disable timer event source when state is SCOPE_RUNNING
468acc7264 Fix cross-reference of manual for LogsDirectory
857fdbc608 pid1: fix coredump_filter setting
db89c44f82 Uphold/StopWhenUnneeded/BindsTo: requeue when job finishes
fe3e998ac8 Uphold/StopWhenUnneeded/BindsTo: add retry timer on rate limit
6c1046121d man: add util-linux to the package list for Fedora container
ab287e91bf man: link to Fedora 37
7e67870804 systemctl: suppress error for try-* if unit is masked
b8af3f5d8c ci: drop checkout from release workflow
372b22c6a8 ci: don't run release wf on `systemd-security`
cfb4a5343b shell-completion: add --xml-interface option of busctl to the rules
ddc80a6c47 busctl: add --xml-interface to the help message
95d729a278 test: update description
62c29bc87b ci: add permissions to make a release
d277048bb4 test/test-functions: fix typo in install_suse_systemd()
4b1da60389 test: install symlinks with valid targets on SUSE and Debian
3e88053037 localed: fix invalid free after shifting pointers using strstrip
83a29385fa test: bump the timeout for non-qemu runs to 90s
4af462fcbc man/systemd-mount: Clearify documentation about --bind-device
7fb9c442b7 resolve: change DNS_PACKET_UNICAST_SIZE_LARGE_MAX to 1232 (#27171)
2866dee297 man: netdev: Clarify wireguard IPv6 endpoint format
a92fc49cf4 ci: do one build with no tpm/p11kit/fido2
2ae7492eac man: mention -o option for systemd-journal-remote
2d458aa454 manager: remove transient unit directory during startup
b4588585f5 core: a more informative error when SetProperties/StartTransientUnit fails
fc9215ad58 journald: fix log message
29b01b2e41 Added unit test for strv_env_name_is_valid() function listed in env-util.c (#27100)
cf07a7c6ac test: make make_addresses() actually return the addresses
a42abcdb0b coverage: add a wrapper for execveat()
7245c4bdba man: add example for sd_bus_call_method
7d728849c2 man: link up new online coredump docs from man page
fdb1ceed47 tree-wide: reset optind to 0 when GNU extensions in optstring are used
6ed548a51c units: let's establish the coredump socket before writting core_pattern sysctl
7e1fab3526 test: do not remove state directory on failure
8e18fbb3f8 man: fix shellcheck warning for html.in
785b116cc1 busctl: also assume --full if not writing to terminal
03e5cdfdae busctl: use size_t for set size
f5ef1d5853 busctl: do not truncate property values when --full
03f8b9d1fe oomd: add inline comments with param names
cca2d36a85 test: add more testcases for rm_rf()
03b90ce85d rm-rf: also chmod() directory if it cannot be opened
999eebacac rm-rf: mask file mode with 07777 when passed to chmod()
37db6597da rm-rf: fix errno handling

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I'm not confident about this, so reviews and testing are still welcome.  Binaries are already available (!) on the staging-next-22.11 branch, so I hope that makes it easier.

No feedback?  I'm running on it right now (whole staging-next-22.11).


AD Authentication in SQL Server on Windows

I am trying to deploy Sql Server to my windows docker host but one of the requirements I have is that users need to be able to sign in with ActiveDirectory. I've tried deploying my container using a gMSA but it still doesn't seem to connect to the domain.
Is there any way to configure this?

Figured it out! I happened to be sitting at the Docker Session and the presenter mentioned that the host name needs to match the gMSA name. Adding -h <account_name> --name <account_name> fixed my problems.

Were users able to login using domain credentials after that? Were the domain users already added to the database before attach?


Support informing why the uri cannot be converted to a UUri

In this code snippet we drop the error that came through in the map_err.
We should probably keep it so that a user knows that went wrong and how to fix it.

Should be fixed in https://github.com/eclipse-uprotocol/up-transport-zenoh-rust/pull/84


Hook naming lint rule

Fixes #213
Introduce a new linter rule to enforce the React hook naming pattern

Released in<EMAIL_ADDRESS>🎉


Drop python 3.3 support

Currently, python 3.3 is broken in tox in our test suite with:

DEPRECATION: Python 3.3 supported has been deprecated and support for it will be dropped in the future. Please upgrade your Python.

Any reason not to just drop this from CI?

+1

Yeah. Let's kill it.

Dead.


fix extra trimmin with trim_trailing_whitespace_on_save #77155

Closes https://github.com/godotengine/godot-proposals/issues/6300
for 3.5

You need to write:
"Closes godotengine/godot-proposals#6300"

Edit: You shouldn't link this as this is not closing the issue as it is for a feature, for 4.0, you are changing this for 3.x, it's best to first add this change to 4.0 and then to 3.x

Okey, thanks! In separate pull request?

Yes you need a separate RP targeting 4.x, also in the future I recommend to make branches for your changes it's not recommended to use your main branches like master or 3.x

Yes you need a separate RP targeting 4.x, i.e. master, also in the future I recommend to make branches for your changes it's not recommended to use your main branches like master or 3.x

Thanks, it makes sense

Some comments on the commit itself:
Your commit seems not to be linked to your GitHub account. See: Why are my commits linked to the wrong user? for more info.
The commit message should ideally also be amended to follow the format we use more conventionally, to have a short human-readable description of the change in English (starting with a capital letter), and more details such as "Fixes " in the body of the commit message. E.g.:
Fix trimming indentation on empty lines with option to trim trailing whitespace

Fixes https://github.com/godotengine/godot-proposals/issues/6300

Regarding the fix itself though, for me this actually implements something that breaks the functionality of trim_trailing_whitespace_on_save. I do want trailing whitespace on empty lines to be removed too. I described it in the proposal already: https://github.com/godotengine/godot-proposals/issues/6300#issuecomment-1432713247
So changing the behavior like this is IMO not a good change.

Note that this targets 3.x and no 4.x version has been added yet

Seems to target 3.5 even, which is wrong. PRs should be made in priority for the master branch (development version for Godot 4.1), and if relevant for 3.x, then for the 3.x branch (development version for Godot 3.6).
Once approved/merged, they can be cherry-picked if relevant for a stable release.

 See: Why are my commits linked to the wrong user? for more info.
The commit message should ideally also be amended to follow the format we use more conventionally, to have a short human-readable description of the change in English (starting with a capital letter), and more details such as "Fixes " in the body of the commit message. E.g.:
Fix trimming indentation on empty lines with option to trim trailing whitespace

Fixes https://github.com/godotengine/godot-proposals/issues/6300

Regarding the fix itself though, for me this actually implements something that breaks the functionality of trim_trailing_whitespace_on_save. I do want trailing whitespace on empty lines to be removed too. I described it in the proposal already: godotengine/godot-proposals#6300 (comment)
So changing the behavior like this is IMO not a good change.

Understand, thanks. I thought about how it should be more convenient, but then some flags or a drop-down list would be necessary.
The problem is that some people in the team use this flag, and some remove the tabs manually. Because of this, "useless" changes get into the commits, such as tabs in the file are removed.

I think will close this PR and reopen new one (with fixes that you find) after PR for 4.x

You would only need to open a PR for 3.x if the changes for 4.x can't be cherry picked, and I think discussing the actual implementation on the proposal first would be good


Unicode / Encoding issues

I'm facing some encoding issues with the client;
The problem are when using non ascii characters, more precisely æøåÆØÅ etc.
client.jsonset("test", Path.rootPath(), {'name': 'test111', 'items': []})

client.jsonget('test') --> {'name': 'test111', 'items': []}

client.jsonarrinsert('test', Path('.items'), 0, {'company': 'Åre', 'destination': 'ÅS', 'origin': 'LØR'})
client.jsonget('test')
This does not look correct?
{"name":"test111","items":[{"company":"\u00c3\u0085re","destination":"\u00c3\u0085S","origin":"L\u00c3\u0098R"},]}
What i had expected:
{"name":"test111","items":[{"company":"\u00c5re","destination":"\u00c5S","origin":"L\u00d8R"},]}
or
{"name":"test111","items":[{"company":"\xc5re","destination":"\xc5S","origin":"L\xd8R"},]}
If i save as strings they appear to get the correct encoding, but then my array elements are turned in to strings instead of objects
If I'm doing it wrong, I'd be greatful for any tips! :)

Hello!
I just tried it too and same result with rejson-py. But I checked with the ReJSON CLI tool, to no avail. The problem stays the same. See the screenshot attached.

I think the problem comes from the ReJSON internal encoding, and not the Python client. Maybe you could check if there is an open issue there or open one to see if they could help you ?

I belive there might be an issue here after all?
I did manage to get around it though:
In python I am able to restore the string by encoding as follows:
somevalue.encode('utf-8').decode('unicode-escape').encode('latin1').decode('utf-8')
and similarly in .NET after fetching with JSON.MGET
		public static string GetEncoded(params string[] strings)
		{
			var lat1 = System.Text.Encoding.GetEncoding("iso-8859-1");
			Regex rx = new Regex(@"\\[uU]([0-9A-Fa-f]{4})");
			var combined = string.Join(",", strings);
			var result = rx.Replace(combined, match => ((char)Int32.Parse(match.Value.Substring(2), System.Globalization.NumberStyles.HexNumber)).ToString());
			var lat1bytes = lat1.GetBytes(result);
			return System.Text.Encoding.UTF8.GetString(lat1bytes);
		}

Having problems as well.
JSON.SET foo . '"bãr"'
OK
JSON.GET foo .
"\"b\\u00c3\\u00a3r\""

When I remove the duplicate \ and decode the result bÃ£r

I believe there is now an option to encode special character with a no-escape option in the JSON.SET command as said in the replies of this issue. Maybe we could add it as an option for the python command? I can try to add it if wanted.
RedisJSON/RedisJSON#98

@bentsku if you can submit a PR that will be great


Scaling settings for xwayland on hidpi monitor overwritten after a while

So I have a single 4k monitor, following the instruction on the wiki, I installed hyprland with patched xwayland and wlroots and set up the monitor and scaling in my config like this:
~/.config/hypr/hyprland.conf:
monitor = , 3840x2160@60, 0x0, 2
exec-once =xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2

hyprland wrapper:
#!/usr/bin/env sh
# vim: ft=sh ts=4 sw=4 sts=4 et :

cd ~

export GDK_SCALE=2
export QT_AUTO_SCREEN_SCALE_FACTOR=1
export QT_QPA_PLATFORM="wayland;xcb"
export QT_QPA_PLATFORMTHEME=qt5ct
export XCURSOR_SIZE=48
export XCURSOR_THEME=breeze_cursors
export XDG_CURRENT_DESKTOP=Hyprland
export XDG_SESSION_DESKTOP=Hyprland
export XDG_SESSION_TYPE=wayland
export _JAVA_AWT_WM_NONREPARENTING=1

exec Hyprland

It works as expected, however after around 30 ~ 60s all xorg apps will spawn with giant UI. I suspect _XWAYLAND_GLOBAL_OUTPUT_SCALE is reset to 1 for some unknown reason, because after I run xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2 again the issue is gone temporarily -- after a while the scaling factor is reset again and I have to manually set it to 2 once more.
I'm trying to find some workarounds like executing this command every time a new app is spawned via a hook or something like that, but haven't find a way to achieve that in Hyprland yet.

@fufexan
hidpi patches are not officially supported, they're just a "this may work"
if you need any help, hit fuffie up on discord or anyone else who uses those.

@fufexan
hidpi patches are not officially supported, they're just a "this may work"
if you need any help, hit fuffie up on discord or anyone else who uses those.

Thanks for your reply! Hyprland is awesome, but the lack of hidpi support just keeps me away from it. Could I ask if there is a plane to add official hidpi support in the foreseeable future (1~2 years)?

unfortunately it's very much not up to us. As you can see, all the patches are to wlroots and xwayland. Hyprland has nothing to do with this.

Alright. Last question, can I add a hook or something like that on Hyprland to execute a command before I execute an application?
I manage to solve the issue for Chrome by executing xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2 every time before I launch it through the shortcut super+g:
bind = $super, g, exec, xprop -root -f _XWAYLAND_GLOBAL_OUTPUT_SCALE 32c -set _XWAYLAND_GLOBAL_OUTPUT_SCALE 2
bind = $super, g, exec, google-chrome-stable

But in this way I have to manually set it up for every app that use xwayland; yet it does not apply to apps that are not launched through a shortcut, for example, apps launched through wofi.
I searched through the Hyprland Wiki hoping to find some mechanism similar to a hook, but with no result.
So I would like to ask if it is possible to do this on Hyprland?

As for chrome, you can launch it in wayland mode with chrome --ozone-platform=wayland.

It will be very helpful if we can add an exec-before option for window rules to mimic a hook.

As for chrome, you can launch it in wayland mode with chrome --ozone-platform=wayland.

Thanks for your suggestion!


Migrate FoundationEssentialsTests to Swift Testing

This PR migrates all FoundationEssentialsTests to Swift Testing.

@swift-ci please test

@swift-ci please test

@swift-ci please test

Hopefully the new toolchain fixes the crashing issue.


Bad Gateway during logging

I faced this when I install it for the first time.
my system is unraid 6.8.1, I install it in app market and I didn't change anything.

suddenly all right.


Standardize crypto errors

Description
Enriched errors in cryptography API. This is still a draft as unit tests need to be updated and integration tests need to be added
Issue reference
Please reference the issue this PR will close: #7491
Checklist

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[x] End-to-end tests passing

@cicoyle I am getting some errors related to MockActors in http_test while running tests locally. Am i missing something

Please note that with crypto operations, errors are sensitive as they can disclose information to users that can be used for attacks (side channel).
Please make sure errors from the crypto components are never returned to callers. They are ok to log, but not returned in the API response - return a generic "failed to perform operation" error instead.

@cicoyle I am getting some errors related to MockActors in http_test while running tests locally. Am i missing something

I believe you might need the tags in your Go Tool Args. When you run the tests in Dapr you will likely need to add these tags: -tags=stablecomponents,unit

Once you get to the integration tests too, you will need a tag: go test -v -race -tags integration ./tests/integration -focus errors, where errors might change pending what you'd like to 'focus' on

@chaitanyab2311 are you planning to take this PR out of draft?

ping @chaitanyab2311


Backend/feature/communities tests attempted fix

It failed for me, here's my try at fixing it up further!

Fixed by @kalvdans in #532


Erik the Outgolfer: Watch puspack.com

Erik the Outgolfer requests the watch of the watch_keyword puspack\.com. See the MS search here and the Stack Exchange search here.

!!/approve

Coverage remained the same at 66.384% when pulling 4ff26b04221eea2420297705763861f008f5ea48 on auto-blacklist-1534422284 into e1f36b7a2e5c82f930f3162853b297ec327bf50b on master.


error: g_dbus_connection_real_closed

I added hamster-bridge to the "Startup applications" in Ubuntu and get the following error.
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Seems like that's no problem anymore..does not happen anymore.


Suport  train/test bevfusion with waymo dataset.

Motivation
When I train/test bevfusion with waymo dataset, some errors occurred, you can see it in ## Modification.
Modification

Compatible with varying image sizes from multiple viewpoints in Det3DLocalVisualizer.
Compatible with camera intrinsic parameters in the 3x4 format(e.g. waymo), in BEVLoadMultiViewImageFromFiles.

Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.tangkang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

这是来自QQ邮箱的自动回复邮件。您好，我已收到您的邮件，会在阅读之后尽快给您回复。

Motivation
When I train/test bevfusion with waymo dataset, some errors occurred, you can see it in ## Modification.
Modification

Compatible with varying image sizes from multiple viewpoints in Det3DLocalVisualizer.
Compatible with camera intrinsic parameters in the 3x4 format(e.g. waymo), in BEVLoadMultiViewImageFromFiles.

Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

Hi Could you provide the waymo config file for BEVFusion?!


Integrating GoogleSignIn with Firebase for Mac Catalyst

I am looking to implement GoogleSignIn with Firebase Authentication for my app on Mac Catalyst.
GoogleSignIn does not support Catalyst yet.
As a temporary workaround,  can I use GTMAppAuth (https://github.com/google/GTMAppAuth) and integrate with the open source FirebaseAuth SDK using the signIn(withCustomToken:completion:) method?
If not, are there any other workarounds?

@morganchen12 @renkelvin Are there any alternatives to waiting for https://github.com/googlesamples/google-services/issues/420?

@meroelyth  Thanks, got client-side authentication working using GAppAuth.
My next hurdle is cross-client authentication. Ran into the issue here: https://github.com/elsesiy/GAppAuth/issues/13

@girishw can you please share how did you manage to get the redirect working with GAppAuth?
I am also ending in Safari, although app does receive callback with auth info. Same with FacebookLogin BTW.

@ondrejhanak No, the redirect is switching the user to Safari. However, authentication is successful. This seems to be a bug with Catalyst/MacOS : https://github.com/openid/AppAuth-iOS/issues/507
I did get cross-client authentication working by modifying GAppAuth to include "audience" in additionalParameters. This sends back the correct serverAuthCode that I use on the server side.

Any updates on this?

I've filed a feature request internally as b/160626909.

See https://github.com/googlesamples/google-services/issues/420#issuecomment-661961707

@paulb777 @petea Any updates?

@meroelyth Did you ever solve the invalid_grant/Bad Request error?

GoogleSignIn 6.0.0 is now released and open source.  Catalyst has not been validated, but it might just work. Please try with 6.0.0 and follow up at https://github.com/google/GoogleSignIn-iOS/issues with any outstanding issues.


__post_init_post_parse__ is incorrectly passed keyword arguments when no __post_init__ is defined

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic  (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
when a __post_init_post_parse__ method is defined on a dataclass without a __post_init__, it incorrectly passes keyword args to it, when the args are not annotated with InitVar as specified in the docs
Example Code
from pydantic.dataclasses import dataclass

@dataclass
class Foo:
    a: int

    # uncomment this and the error goes away
    # def __post_init__(self):
    #     ...

    def __post_init_post_parse__(self): # TypeError: Foo.__post_init_post_parse__() got an unexpected keyword argument 'a'
        ...

a = Foo(a=1)

Python, Pydantic & OS Version
this issue seems to have been introduced after the 1.9.1. this occurred after installing the latest commit from master:
pip uninstall pydantic
pip install git+https://github.com/samuelcolvin/pydantic.git@a69136d2096e327ed48954a298c775dceb1551d1

pydantic version: 1.9.0
            pydantic compiled: False
                 install path: C:\Users\chungus\AppData\Local\pypoetry\Cache\virtualenvs\project-e01-Hfn1-py3.10\Lib\site-packages\pydantic
               python version: 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
                     platform: Windows-10-10.0.19042-SP0
     optional deps. installed: ['typing-extensions']

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[X] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Settings Management
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

I can confirm the error. It seems we have the problem because we update the initvars_and_values by kwargs that I am not sure is the right behavior or not.
@samuelcolvin what do you think?
https://github.com/samuelcolvin/pydantic/blob/a69136d2096e327ed48954a298c775dceb1551d1/pydantic/dataclasses.py#L263


Add monitoring

Can't assign myself but I'll take this

Weird, your access got removed entirely when switching from triage to write. Added you back, you should be good to go!

Great, thank you!


Android Basics: classes-and-inheritance

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-classes-and-inheritance?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-2-pathway-1%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-classes-and-inheritance#6
In which task and step of the codelab can this issue be found?
Describe the problem
At chapter 7. Summary says that you have learned how to use the "super" keyword to reference functions and properties in the parent class. The keyword super in not reference  to any part of the class and inheritance session.
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

@dimd11
Thank you for reaching out to us. Following the steps provided in the codelab you will find all the information about class hierarchy including about superclass.


AngujarJS 1.7.9 is not available in Bower

The last version is not avaliable in Bower but the previous one (1.7.8) is.
bower ENORESTARGET  No tag found that was able to satisfy ~1.7.9

Additional error details:
Available versions in https://github.com/angular/bower-angular-messages.git: 1.7.8, 1.7.7, 1.7.6, 1.7.5, 1.7.4, 1.7.3, 1.7.2, 1.7.2-build.5558+sha.c9a92fc, 1.7.1, 1.7.0, 1.7.0-rc.0, ...

This should now be resolved - see https://github.com/angular/bower-angular-messages/tree/v1.7.9


Redirects to old url on click of view btn of Document log.

Describe the bug
Redirects to https://user.easycloudbooks.com/user/Preview.html?acid=74.
Screenshots

that is actually microsoft error
sometimes we get  preview from microsoft/ sometimes not depending upon file type
image preview works perfectly as we are providing preview

Still redirects to https://user.easycloudbooks.com/Preview.html?acid=74


Crash on load

Hi, I added Ex Nihilo Adscensio to my modpack but when I load it up it crashes. I checked the crash log but I don't understand any of it. Any help would be appreciated, also if anyone can see anything else wrong with the pack then please let me know so I can fix it.
Here is the full crash report: https://pastebin.com/vL5WsSdz
Thanks

This has been reported a number of times, and I believe it's supposed to
be fixed in 0.1.20.

Ok thanks I'll try that version.

I'm gonna guess by the silence that this is fixed. Please reopen if the issue persists.

Sorry I completely forgot to post back, yes updating the mod fixed the issue. Thanks BrianEdmonds


Allow adding buttons to Action header

Describe the problem feature solves
Right now the only way to add a button to the header of a resource/record is to use a custom action. I want to create a button that is simply a link to a different page.
Describe the solution you'd like
The ability to pass a custom component to the header
Describe alternatives you've considered
Creating an action with a custom component that just acts as a redirect
Acceptance criteria

[ ] Pass component to header
[ ] Document this feature

Potential implementation:

add href option to Action config
handler should be optional
if href is specified but handler isn't, the UI button should simply open the link


Create achievements classes

Needed to create instances of Achievements to be displayed on rewards page

[ ] Create abstract achievements class
[ ] Create child achievement classes
[ ] Set up basic fields and methods for abstract and child classses

Great inclusion of subtasks in the issue. Approved by Ou-An


Person component not working anymore

Home Assistant release with the issue:
0.92.0
Last working Home Assistant release (if known):
0.91.3
Operating environment (Hass.io/Docker/Windows/etc.):
hass.io
Component/platform:
https://www.home-assistant.io/components/person/
Description of problem:
Person component not available anymore when upgraded to 0.92.0
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
person:

Traceback (if applicable):
None available
Additional information:
Similar issues #23368 but I don't use Daikin.

Cannot help without seeing your logs.

Which logs do want to have? I have hass.io running.

2019-04-26 11:18:55 ERROR (MainThread) [homeassistant.components.hassio.handler] Client error on /homeassistant/restart request None
Config directory: /config
2019-04-26 11:19:10 INFO (SyncWorker_6) [homeassistant.loader] Loaded alarm_control_panel from homeassistant.components.alarm_control_panel
2019-04-26 11:19:10 INFO (SyncWorker_5) [homeassistant.loader] Loaded alert from homeassistant.components.alert
2019-04-26 11:19:10 INFO (SyncWorker_8) [homeassistant.loader] Loaded apple_tv from homeassistant.components.apple_tv
2019-04-26 11:19:10 INFO (SyncWorker_10) [homeassistant.loader] Loaded automation from homeassistant.components.automation
2019-04-26 11:19:10 INFO (SyncWorker_4) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2019-04-26 11:19:10 INFO (SyncWorker_12) [homeassistant.loader] Loaded config from homeassistant.components.config
2019-04-26 11:19:10 INFO (SyncWorker_6) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2019-04-26 11:19:10 INFO (SyncWorker_7) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2019-04-26 11:19:10 INFO (SyncWorker_11) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery
2019-04-26 11:19:10 INFO (SyncWorker_1) [homeassistant.loader] Loaded frontend from homeassistant.components.frontend
2019-04-26 11:19:10 INFO (SyncWorker_12) [homeassistant.loader] Loaded group from homeassistant.components.group
2019-04-26 11:19:10 INFO (SyncWorker_6) [homeassistant.loader] Loaded history from homeassistant.components.history
2019-04-26 11:19:10 INFO (SyncWorker_10) [homeassistant.loader] Loaded homekit from homeassistant.components.homekit
2019-04-26 11:19:10 INFO (SyncWorker_11) [homeassistant.loader] Loaded http from homeassistant.components.http
2019-04-26 11:19:10 INFO (SyncWorker_1) [homeassistant.loader] Loaded hue from homeassistant.components.hue
2019-04-26 11:19:10 INFO (SyncWorker_19) [homeassistant.loader] Loaded input_boolean from homeassistant.components.input_boolean
2019-04-26 11:19:10 INFO (SyncWorker_14) [homeassistant.loader] Loaded input_datetime from homeassistant.components.input_datetime
2019-04-26 11:19:10 INFO (SyncWorker_7) [homeassistant.loader] Loaded light from homeassistant.components.light
2019-04-26 11:19:10 INFO (SyncWorker_11) [homeassistant.loader] Loaded logbook from homeassistant.components.logbook
2019-04-26 11:19:11 INFO (SyncWorker_18) [homeassistant.loader] Loaded lovelace from homeassistant.components.lovelace
2019-04-26 11:19:11 INFO (SyncWorker_12) [homeassistant.loader] Loaded map from homeassistant.components.map
2019-04-26 11:19:11 INFO (SyncWorker_6) [homeassistant.loader] Loaded ios from homeassistant.components.ios
2019-04-26 11:19:11 INFO (SyncWorker_10) [homeassistant.loader] Loaded mobile_app from homeassistant.components.mobile_app
2019-04-26 11:19:12 INFO (SyncWorker_11) [homeassistant.loader] Loaded mqtt from homeassistant.components.mqtt
2019-04-26 11:19:12 INFO (SyncWorker_1) [homeassistant.loader] Loaded nest from homeassistant.components.nest
2019-04-26 11:19:12 INFO (SyncWorker_19) [homeassistant.loader] Loaded notify from homeassistant.components.notify
2019-04-26 11:19:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded person from homeassistant.components.person
2019-04-26 11:19:12 INFO (SyncWorker_7) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
2019-04-26 11:19:12 INFO (SyncWorker_17) [homeassistant.loader] Loaded rfxtrx from homeassistant.components.rfxtrx
2019-04-26 11:19:12 INFO (SyncWorker_18) [homeassistant.loader] Loaded scene from homeassistant.components.scene
2019-04-26 11:19:12 INFO (SyncWorker_12) [homeassistant.loader] Loaded script from homeassistant.components.script
2019-04-26 11:19:12 INFO (SyncWorker_6) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2019-04-26 11:19:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded speedtestdotnet from homeassistant.components.speedtestdotnet
2019-04-26 11:19:12 INFO (SyncWorker_11) [homeassistant.loader] Loaded sun from homeassistant.components.sun
2019-04-26 11:19:12 INFO (SyncWorker_5) [homeassistant.loader] Loaded system_health from homeassistant.components.system_health
2019-04-26 11:19:12 INFO (SyncWorker_2) [homeassistant.loader] Loaded telegram_bot from homeassistant.components.telegram_bot
2019-04-26 11:19:12 INFO (SyncWorker_8) [homeassistant.loader] Loaded timer from homeassistant.components.timer
2019-04-26 11:19:12 INFO (SyncWorker_10) [homeassistant.loader] Loaded tts from homeassistant.components.tts
2019-04-26 11:19:12 INFO (SyncWorker_11) [homeassistant.loader] Loaded updater from homeassistant.components.updater
2019-04-26 11:19:12 INFO (SyncWorker_1) [homeassistant.loader] Loaded utility_meter from homeassistant.components.utility_meter
2019-04-26 11:19:12 INFO (SyncWorker_19) [homeassistant.loader] Loaded weather from homeassistant.components.weather
2019-04-26 11:19:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded yeelight from homeassistant.components.yeelight
2019-04-26 11:19:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded zone from homeassistant.components.zone
2019-04-26 11:19:12 INFO (SyncWorker_0) [homeassistant.loader] Loaded zwave from homeassistant.components.zwave
2019-04-26 11:19:12 INFO (SyncWorker_19) [homeassistant.loader] Loaded cast from homeassistant.components.cast
2019-04-26 11:19:12 INFO (SyncWorker_12) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2019-04-26 11:19:12 INFO (SyncWorker_19) [homeassistant.loader] Loaded sonos from homeassistant.components.sonos
2019-04-26 11:19:12 INFO (SyncWorker_12) [homeassistant.loader] Loaded zeroconf from homeassistant.components.zeroconf
2019-04-26 11:19:12 INFO (SyncWorker_6) [homeassistant.loader] Loaded persistent_notification from homeassistant.components.persistent_notification
2019-04-26 11:19:12 INFO (SyncWorker_15) [homeassistant.loader] Loaded api from homeassistant.components.api
2019-04-26 11:19:12 INFO (SyncWorker_9) [homeassistant.loader] Loaded webhook from homeassistant.components.webhook
2019-04-26 11:19:12 INFO (SyncWorker_8) [homeassistant.loader] Loaded configurator from homeassistant.components.configurator
2019-04-26 11:19:12 INFO (SyncWorker_14) [homeassistant.loader] Loaded homeassistant from homeassistant.components.homeassistant
2019-04-26 11:19:12 INFO (SyncWorker_16) [homeassistant.loader] Loaded panel_custom from homeassistant.components.panel_custom
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up persistent_notification
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain persistent_notification took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up homeassistant
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant took 0.0 seconds.
2019-04-26 11:19:12 INFO (SyncWorker_4) [homeassistant.loader] Loaded auth from homeassistant.components.auth
2019-04-26 11:19:12 INFO (SyncWorker_18) [homeassistant.loader] Loaded onboarding from homeassistant.components.onboarding
2019-04-26 11:19:12 INFO (SyncWorker_19) [homeassistant.loader] Loaded system_log from homeassistant.components.system_log
2019-04-26 11:19:12 INFO (SyncWorker_3) [homeassistant.loader] Loaded websocket_api from homeassistant.components.websocket_api
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up http
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up system_log
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up cast
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up rfxtrx
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up configurator
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain configurator took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up nest
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain nest took 0.0 seconds.
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up group
2019-04-26 11:19:12 INFO (SyncWorker_0) [nest.nest] Open data stream
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up updater
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up homekit
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setting up zwave
2019-04-26 11:19:12 INFO (MainThread) [homeassistant.setup] Setup of domain zwave took 0.0 seconds.
2019-04-26 11:19:15 INFO (SyncWorker_0) [nest.nest] Event loop started.
2019-04-26 11:19:16 INFO (MainThread) [homeassistant.components.zwave] Z-Wave USB path is /dev/serial/by-id/usb-0658_0200-if00
2019-04-26 11:19:16 INFO (MainThread) [homeassistant.setup] Setting up utility_meter
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain utility_meter took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up timer
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up sonos
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain sonos took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up sun
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.2 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up hue
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain hue took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up zone
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up discovery
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain discovery took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up yeelight
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up alert
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up scene
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up speedtestdotnet
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain speedtestdotnet took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 5.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain homekit took 5.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up recorder
2019-04-26 11:19:17 INFO (SyncWorker_16) [homeassistant.loader] Loaded buienradar from homeassistant.components.buienradar
2019-04-26 11:19:17 INFO (SyncWorker_9) [homeassistant.loader] Loaded tod from homeassistant.components.tod
2019-04-26 11:19:17 INFO (SyncWorker_14) [homeassistant.loader] Loaded manual from homeassistant.components.manual
2019-04-26 11:19:17 INFO (SyncWorker_15) [homeassistant.loader] Loaded telegram from homeassistant.components.telegram
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up api
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up apple_tv
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up config
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up webhook
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up auth
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up mqtt
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain mqtt took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain alert took 0.3 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds.
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.setup] Setting up telegram_bot
2019-04-26 11:19:17 INFO (MainThread) [homeassistant.components.telegram_bot] Setting up telegram_bot.webhooks
2019-04-26 11:19:18 INFO (MainThread) [homeassistant.setup] Setting up system_health
2019-04-26 11:19:18 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.0 seconds.
2019-04-26 11:19:18 INFO (SyncWorker_12) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2019-04-26 11:19:18 INFO (MainThread) [homeassistant.setup] Setup of domain rfxtrx took 6.5 seconds.
2019-04-26 11:19:18 INFO (MainThread) [homeassistant.setup] Setup of domain yeelight took 1.5 seconds.
2019-04-26 11:19:18 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for afvalwijzer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-04-26 11:19:18 INFO (MainThread) [homeassistant.loader] Loaded afvalwijzer from custom_components.afvalwijzer
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up weather
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up alarm_control_panel
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up notify
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain api took 2.1 seconds.
2019-04-26 11:19:19 INFO (SyncWorker_4) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.weather] Setting up weather.buienradar
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.alarm_control_panel] Setting up alarm_control_panel.manual
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain apple_tv took 2.1 seconds.
2019-04-26 11:19:19 INFO (SyncWorker_1) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain config took 2.1 seconds.
2019-04-26 11:19:19 INFO (SyncWorker_5) [homeassistant.loader] Loaded climate from homeassistant.components.climate
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2019-04-26 11:19:19 INFO (SyncWorker_19) [homeassistant.loader] Loaded workday from homeassistant.components.workday
2019-04-26 11:19:19 INFO (SyncWorker_15) [homeassistant.loader] Loaded template from homeassistant.components.template
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up tts
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 2.1 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up climate
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain climate took 0.0 seconds.
2019-04-26 11:19:19 INFO (SyncWorker_16) [homeassistant.loader] Loaded remote from homeassistant.components.remote
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up media_player
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 0.0 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor 0x001788010202d816 occupancy
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.climate] Setting up climate.nest
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.climate] Setting up climate.zwave
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: binary_sensor 0x0017880102026f47 occupancy
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x001788010202d816 temperature
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x001788010202d816 illuminance
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x001788010202d816 battery
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x001788010202d816 linkquality
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x0017880102026f47 temperature
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x0017880102026f47 illuminance
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x0017880102026f47 battery
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Found new component: sensor 0x0017880102026f47 linkquality
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.telegram_bot.webhooks] Set new telegram webhook https://h.grtrs.nl/api/telegram_webhooks
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain telegram_bot took 2.1 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 2.8 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.sonos
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.3 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.workday
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tod
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tod
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tod
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tod
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.tod
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up history
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds.
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.setup] Setting up camera
2019-04-26 11:19:19 INFO (SyncWorker_19) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: binary_sensor 0x001788010202d816 occupancy, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: binary_sensor 0x0017880102026f47 occupancy, sending update
2019-04-26 11:19:19 INFO (SyncWorker_15) [homeassistant.loader] Loaded fan from homeassistant.components.fan
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x001788010202d816 temperature, sending update
2019-04-26 11:19:19 INFO (SyncWorker_18) [homeassistant.loader] Loaded lock from homeassistant.components.lock
2019-04-26 11:19:19 INFO (SyncWorker_2) [homeassistant.loader] Loaded dsmr from homeassistant.components.dsmr
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x001788010202d816 illuminance, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x001788010202d816 battery, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x001788010202d816 linkquality, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x0017880102026f47 temperature, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x0017880102026f47 illuminance, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x0017880102026f47 battery, sending update
2019-04-26 11:19:19 INFO (MainThread) [homeassistant.components.mqtt.discovery] Component has already been discovered: sensor 0x0017880102026f47 linkquality, sending update
2019-04-26 11:19:20 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
2019-04-26 11:19:20 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
2019-04-26 11:19:20 INFO (MainThread) [homeassistant.components.notify] Setting up notify.telegram
2019-04-26 11:19:20 INFO (MainThread) [homeassistant.setup] Setup of domain group took 8.0 seconds.
2019-04-26 11:19:20 INFO (MainThread) [homeassistant.setup] Setting up frontend
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 5.1 seconds.
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.components.notify] Setting up notify.group
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 2.9 seconds.
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 3.1 seconds.
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setup of domain camera took 2.7 seconds.
2019-04-26 11:19:22 INFO (SyncWorker_12) [homeassistant.loader] Loaded pi_hole from homeassistant.components.pi_hole
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setting up light
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setting up cover
2019-04-26 11:19:22 INFO (MainThread) [homeassistant.setup] Setting up script
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setting up automation
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setting up remote
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setup of domain remote took 0.0 seconds.
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 4.3 seconds.
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.components.camera] Setting up camera.nest
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 4.4 seconds.
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setting up switch
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 0.0 seconds.
2019-04-26 11:19:23 INFO (MainThread) [homeassistant.setup] Setting up fan
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain fan took 0.0 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setting up lock
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain lock took 0.0 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.cover] Setting up cover.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.cover] Setting up cover.group
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.cover] Setting up cover.rfxtrx
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.switch] Setting up switch.zwave
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.fan] Setting up fan.zwave
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.lock] Setting up lock.zwave
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain script took 1.5 seconds.
2019-04-26 11:19:24 INFO (SyncWorker_15) [homeassistant.loader] Loaded unifi from homeassistant.components.unifi
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 3.7 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 4.5 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 6.9 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 6.8 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.nest
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.zwave
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mqtt
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.hue
2019-04-26 11:19:24 INFO (SyncWorker_0) [homeassistant.loader] Loaded season from homeassistant.components.season
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 1.5 seconds.
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setting up logbook
2019-04-26 11:19:24 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.1 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setting up panel_custom
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain panel_custom took 0.0 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setting up map
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.yeelight
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain alarm_control_panel took 5.7 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setting up hassio
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain cover took 2.8 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setting up unifi
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain unifi took 0.0 seconds.
2019-04-26 11:19:25 INFO (SyncWorker_10) [homeassistant.loader] Loaded time_date from homeassistant.components.time_date
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.cover] Setting up cover.zwave
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.unifi
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setup of domain light took 2.9 seconds.
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.light] Setting up light.zwave
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.light] Setting up light.hue
2019-04-26 11:19:25 INFO (SyncWorker_7) [homeassistant.loader] Loaded yr from homeassistant.components.yr
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.light] Setting up light.yeelight
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.setup] Setting up sensor
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.dsmr
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.afvalwijzer
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.pi_hole
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.season
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.time_date
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.yr
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2019-04-26 11:19:25 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py:847: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
2019-04-26 11:19:25 INFO (MainThread) [hole] Response from *hole: 200
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.7 seconds.
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 1.1 seconds.
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.nest
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.zwave
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hue
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mqtt
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.hue.sensor_base] Starting sensor polling loop with 5.0 second interval
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.utility_meter
2019-04-26 11:19:26 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.speedtestdotnet
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 2.3 seconds.
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.setup] Setting up ios
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.setup] Setup of domain ios took 0.0 seconds.
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.ios
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.0 seconds.
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.notify] Setting up notify.ios
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 18.31s
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2019-04-26 11:19:27 INFO (SyncWorker_10) [homeassistant.components.zwave] Starting Z-Wave network...
2019-04-26 11:19:27 INFO (SyncWorker_10) [openzwave] Start Openzwave network.
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Activeer light theme bij zonsopgang
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet thermostaat op aanwezig
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Activeer dark theme bij zonsondergang
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet thermostaat op afwezig
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Update Available new Hass version
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notificatie vervangen motion sensor
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Disable Zigbee joining
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notificatie vervangen batterij rookmelder
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Enable Zigbee joining
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Overdag - Lichten uit bij voldoende zonlicht
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Disable Zigbee joining by timer
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Overdag - Lichten aan als het te donder wordt
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet alarm aan bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar beneden
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet alarm uit wanneer iemand thuis is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar boven
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar boven
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar boven
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar boven
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Screen naar boven
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Brandalarm gaat af
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Sonos by day
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Rolluiken omhoog bij aankomst
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Sonos by night
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Verlichting aan bij aankomst
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Verlichting aan bij zonsondergang
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet muziek aan bij thuiskomst
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Plex pause/idle
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Rolluiken dicht bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Plex afspelen
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Verlichting uit bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Nachtlamp na uur uit
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Zet muziek uit bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notificatie vervangen motion sensor
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Sensors monitoring bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Sensors monitoring bij afwezigheid
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Overloop uit
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Lampen uit na 02:00
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Rolluiken omhoog bij opkomende zon
2019-04-26 11:19:27 INFO (Dummy-30) [openzwave] Driver ready using library Static Controller version Z-Wave 4.61
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Nacht - Lampen uit na laatste beweging
2019-04-26 11:19:27 INFO (Dummy-30) [openzwave] home_id 0xef6a7ab2, controller node id is 1
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Verlichting uit na zonsopgang
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Nacht - lampen aan bij beweging
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Rolluiken dicht na zonsondergang
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Keuken uit wanneer TV aan is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Ventilatie aan als er rook is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Awakening mode aan op werkdagen
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notificatie vervangen batterij badkamer
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Overdag boven de lichten uit
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Ventilatie uit badkamer
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Ochtendroutine als iemand beneden komt
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Ventilatie aan badkamer
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Afval - Een dag ervoor
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Rolluik garage open
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Ochtendroutine als het winter is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notificatie wanneer deurbel offline is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Alarm doordeweeks
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Deactiveer hal na 1 min na laatste beweging
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Notify when Hass is started
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Activeer hal wanneer beweging is
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Initialized trigger Dark theme activeren bij herstart
2019-04-26 11:19:27 WARNING (MainThread) [homeassistant.components.template.sensor] Could not render template Sensor badkamer batterij status, the state is unknown.
2019-04-26 11:19:27 WARNING (MainThread) [homeassistant.components.template.sensor] Could not render template Sensor rookmelder batterij status, the state is unknown.
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.core] Timer:starting
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.components.automation] Executing Notify when Hass is started
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.helpers.script] Script Notify when Hass is started: Running script
2019-04-26 11:19:27 INFO (MainThread) [homeassistant.helpers.script] Script Notify when Hass is started: Executing step call service
2019-04-26 11:19:27 INFO (Dummy-30) [homeassistant.components.zwave] Ignoring entity sensor.philio_technology_corporation_ph_pat02_b_eu_multisensor_2in1_sourcenodeid due to device settings
2019-04-26 11:19:27 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: <state sensor.bathroom_battery_level=initializing; unit_of_measurement=%, friendly_name=Sensor badkamer batterij status, device_class=battery @ 2019-04-26T11:19:27.800439+02:00> (Offending entity: initializing)
2019-04-26 11:19:27 INFO (Dummy-30) [homeassistant.components.zwave] Ignoring entity sensor.philio_technology_corporation_ph_pat02_b_eu_multisensor_2in1_burglar due to device settings
2019-04-26 11:19:27 INFO (Dummy-30) [homeassistant.components.zwave] Ignoring entity sensor.fibaro_system_fgsd002_smoke_sensor_sourcenodeid due to device settings
2019-04-26 11:19:28 INFO (Dummy-30) [homeassistant.components.zwave] Ignoring entity sensor.fibaro_system_fgsd002_smoke_sensor_burglar due to device settings
2019-04-26 11:19:28 WARNING (MainThread) [homeassistant.helpers.condition] Value cannot be processed as a number: <state sensor.living_room_battery_level=initializing; unit_of_measurement=%, friendly_name=Sensor rookmelder batterij status, device_class=battery @ 2019-04-26T11:19:28.037807+02:00> (Offending entity: initializing)
2019-04-26 11:19:36 INFO (SyncWorker_3) [homeassistant.loader] Loaded daikin from homeassistant.components.daikin
2019-04-26 11:19:36 INFO (SyncWorker_5) [homeassistant.loader] Loaded lifx from homeassistant.components.lifx
2019-04-26 11:19:37 INFO (SyncWorker_9) [homeassistant.loader] Loaded smartthings from homeassistant.components.smartthings
2019-04-26 11:19:37 INFO (SyncWorker_10) [homeassistant.loader] Loaded twilio from homeassistant.components.twilio
2019-04-26 11:19:37 INFO (SyncWorker_8) [homeassistant.loader] Loaded ifttt from homeassistant.components.ifttt
2019-04-26 11:19:38 INFO (SyncWorker_13) [homeassistant.loader] Loaded openuv from homeassistant.components.openuv
2019-04-26 11:19:38 INFO (SyncWorker_3) [homeassistant.loader] Loaded toon from homeassistant.components.toon
2019-04-26 11:19:38 INFO (SyncWorker_4) [homeassistant.loader] Loaded geofency from homeassistant.components.geofency
2019-04-26 11:19:38 INFO (SyncWorker_6) [homeassistant.loader] Loaded zha from homeassistant.components.zha
2019-04-26 11:19:39 INFO (SyncWorker_1) [homeassistant.loader] Loaded locative from homeassistant.components.locative
2019-04-26 11:19:39 INFO (SyncWorker_0) [homeassistant.loader] Loaded logi_circle from homeassistant.components.logi_circle
2019-04-26 11:19:39 INFO (SyncWorker_18) [homeassistant.loader] Loaded point from homeassistant.components.point
2019-04-26 11:19:39 INFO (SyncWorker_17) [homeassistant.loader] Loaded tradfri from homeassistant.components.tradfri
2019-04-26 11:19:39 INFO (SyncWorker_8) [homeassistant.loader] Loaded owntracks from homeassistant.components.owntracks
2019-04-26 11:19:39 INFO (SyncWorker_15) [homeassistant.loader] Loaded smhi from homeassistant.components.smhi
2019-04-26 11:19:39 INFO (SyncWorker_11) [homeassistant.loader] Loaded upnp from homeassistant.components.upnp
2019-04-26 11:19:39 INFO (SyncWorker_1) [homeassistant.loader] Loaded ps4 from homeassistant.components.ps4
2019-04-26 11:19:39 INFO (SyncWorker_0) [homeassistant.loader] Loaded ipma from homeassistant.components.ipma
2019-04-26 11:19:39 INFO (SyncWorker_18) [homeassistant.loader] Loaded heos from homeassistant.components.heos
2019-04-26 11:19:39 INFO (SyncWorker_17) [homeassistant.loader] Loaded deconz from homeassistant.components.deconz
2019-04-26 11:19:39 INFO (SyncWorker_11) [homeassistant.loader] Loaded mailgun from homeassistant.components.mailgun
2019-04-26 11:19:39 INFO (SyncWorker_1) [homeassistant.loader] Loaded emulated_roku from homeassistant.components.emulated_roku
2019-04-26 11:19:39 INFO (SyncWorker_0) [homeassistant.loader] Loaded simplisafe from homeassistant.components.simplisafe
2019-04-26 11:19:39 INFO (SyncWorker_18) [homeassistant.loader] Loaded tplink from homeassistant.components.tplink
2019-04-26 11:19:39 INFO (SyncWorker_5) [homeassistant.loader] Loaded axis from homeassistant.components.axis
2019-04-26 11:19:39 INFO (SyncWorker_11) [homeassistant.loader] Loaded luftdaten from homeassistant.components.luftdaten
2019-04-26 11:19:39 INFO (SyncWorker_3) [homeassistant.loader] Loaded dialogflow from homeassistant.components.dialogflow
2019-04-26 11:19:39 INFO (SyncWorker_0) [homeassistant.loader] Loaded homematicip_cloud from homeassistant.components.homematicip_cloud
2019-04-26 11:19:39 INFO (SyncWorker_18) [homeassistant.loader] Loaded rainmachine from homeassistant.components.rainmachine
2019-04-26 11:19:39 INFO (SyncWorker_5) [homeassistant.loader] Loaded tellduslive from homeassistant.components.tellduslive
2019-04-26 11:19:39 INFO (SyncWorker_11) [homeassistant.loader] Loaded esphome from homeassistant.components.esphome
2019-04-26 11:19:39 INFO (SyncWorker_3) [homeassistant.loader] Loaded hangouts from homeassistant.components.hangouts
2019-04-26 11:19:39 INFO (SyncWorker_0) [homeassistant.loader] Loaded gpslogger from homeassistant.components.gpslogger
2019-04-26 11:19:39 INFO (SyncWorker_18) [homeassistant.loader] Loaded ambient_station from homeassistant.components.ambient_station
2019-04-26 11:19:44 INFO (Dummy-30) [homeassistant.components.zwave] Z-Wave network is ready for use. All awake nodes have been queried. Sleeping nodes will be queried when they awake.
2019-04-26 11:19:44 INFO (MainThread) [homeassistant.components.zwave] Z-Wave ready after 16 seconds
2019-04-26 11:19:44 INFO (SyncWorker_5) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms
2019-04-26 11:19:47 INFO (SyncWorker_3) [homeassistant.loader] Loaded plex from homeassistant.components.plex
2019-04-26 11:19:47 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.plex
2019-04-26 11:19:47 INFO (SyncWorker_9) [homeassistant.components.plex.media_player] Discovery configuration done (no token needed)
2019-04-26 11:19:47 INFO (SyncWorker_9) [homeassistant.components.plex.media_player] Connected to: http://<IP_ADDRESS>:32400
/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py:847: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)

Tested without "afvalwijzer" custom component, but still the issue exists.

Please add a more verbose description of the problem. What are the symptoms that the person component is not available?

Are you using a package for the config that has the person: section?

@MartinHjelmare yes. I  use package to separate each component into yaml files.
https://github.com/rgruyters/home-assistant-config

Noticed the same issue with the person component after updating to 0.92.0. It stopped working when in a package, but after moving person: to my main configuration.yaml, it started working again.

Noticed the same issue with the person component after updating to 0.92.0. It stopped working when in a package, but after moving person: to my main configuration.yaml, it started working again.

Can confirm this, I had the same issue and moved person: into the main configuration.yaml, and it works again.

Same problem. person component is in a package and configuration GUI disappeared with 0.92

Just adding another +1 since I'm getting this too

Same issue her.. This config used to work: https://github.com/sjabby/home-assistant-config/blob/master/components/packages/person.yaml
Now it does not show up unless person: is in configuration.yaml

Same here.
Ia actually reported this as part of https://github.com/home-assistant/home-assistant/issues/23188 because it all seemed related but haven't been back since.

I've got the same issue. What does work for me is if I start configuring the actual person component in the packages like so:
person:
  - name: Name
    id: id

So only when I do not define any person in the YAML file does it not work.
Actually configuring this person also adds my previously configured users again (configured via the UI)

Same here. Moving my config to packages. Person: does not work indeed.


DAPP1-37: updated header and responsive menu for navbar

(bug) open menu items
https://3um-ecosystem.atlassian.net/browse/DAPP1-37
Previous

Latest

This looks to be mainly code style changes? Also where's the codesandbox UAT environment?

@charunb You need to setup your code signing key and sign the commit before this is merged


PR: Fix Help plugin string validation for the console

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)
[ ] Included a screenshot (if affecting the UI)

Fix validation to correctly check if and object if denifed in the shell attached to the Help or current Console
Issue(s) Resolved

Fixes #9143
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: dalthviz

Hello @dalthviz! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/help.py:

Line 755:5: E265 block comment should start with '# '

Fix validation to correctly check if and object if denifed in the shell attached to the Help or current Console

I think I parsed this correctly and fixed up the various problems, but just letting you know in case I didn't; it was a tad garbled...

@dalthviz, this is ready, please don't add more commits here. I'll fix the Azure error and then merge.


暂时不支持bitcode？见正文

ld: bitcode bundle could not be generated because
'/Users/xx/Documents/ee/ios/iphone-1.0/Pods/PLCameraStreamingKit/Pod/Library/lib/libPLCameraStreamingKit.a(PLH264Packetizer.o)'
 was built without full bitcode.
All object files and libraries for bitcode must be generated from Xcode Archive or Install build for architecture armv7

暂且取消了对 Bitcode 的支持。


CI fails on Windows

Information

Qiskit Optimization version: latest
Python version: 3.8
Operating system: Windows 10

What is the current behavior?
CI fails. https://github.com/Qiskit/qiskit-optimization/actions/runs/1178358017
test.algorithms.test_recursive_optimization.TestRecursiveMinEigenOptimizer.test_recursive_warm_qaoa
---------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):

      File "D:\a\qiskit-optimization\qiskit-optimization\test\optimization_test_case.py", line 47, in wrapper
    test_item(self, *args)

      File "D:\a\qiskit-optimization\qiskit-optimization\test\algorithms\test_recursive_optimization.py", line 155, in test_recursive_warm_qaoa
    np.testing.assert_array_almost_equal(cplex_result.x, result.x, 4)

      File "c:\miniconda\lib\site-packages\numpy\testing\_private\utils.py", line 1046, in assert_array_almost_equal
    assert_array_compare(compare, x, y, err_msg=err_msg, verbose=verbose,

      File "c:\miniconda\lib\site-packages\numpy\testing\_private\utils.py", line 844, in assert_array_compare
    raise AssertionError(msg)

    AssertionError:
Arrays are not almost equal to 4 decimals

Mismatched elements: 2 / 2 (100%)
Max absolute difference: 2.
Max relative difference: 1.
 x: array([0., 2.])
 y: array([2., 0.])

Steps to reproduce the problem
What is the expected behavior?
Suggested solutions

In looking at the test case, from what I can see the problem is symmetric, in the two variables, such that the solution found is correct, just it has swapped the variables
Minimize
 obj1: 2 x0 + 2 x1 + [ 4 x0 * x0 + x1 * x1 + 0.5 x0 * x1 + 0.5 x0 * x1 ] / 2
Subject To
 constraint: x0 + x1  = 2
Bounds
 0 <= x0 <= 4
 0 <= x1 <= 4

Hence to me it seems that the test case could be improved to cover that - given that this seems most likely to be platform dependent behavior in arriving at the solution.

Good catch. It might be a reason. Unfortunately, this issue is hard for me to resolve because it does not reproduce on my local Windows 10 environment. All unit tests pass successfully...

Your Win 10 env is with Python 3.8 like the unit test? I can see if I can reproduce it locally (I have 3.8.8). Either way I think this is a valid result right and if so then the fix just seems to be to allow either solution as a valid result in which case CI should then pass, even if in some other env we cannot reproduce the exact solution it ends up with in CI.

Yes, I use Python 3.8.10 on my Windows 10. I'm wondering what's the difference of my env and (your env or CI env). If it reproduces on my env, I can work on it...

I have not been able to reproduce the error yet. I made a script from the test case and have it in a for loop. It was running and I could not reproduce the failure and I was looking at Cplex and saw it has a randomseed parameter so stopped the test and  altered the CplexOptimizer creation to pass that as a cplex_parameter - plus for each loop iteration I made it a random value. It ran earlier for 10k iterations without failing - so either I am not able to reproduce it either or its a very slim chance of it failing and I did not see it yet. I started the script again since I had the loop set to end at 10k iterations - I increased that number and figured I'd leave it run overnight and see. So far its still going.

The windows CI was installing Terra from main outside the conda environment and later Aer was installing Terra from pypi inside it. So the Windows CI was running against all dependencies from main but Terra that was from Pypi.