Add option to cleanup unused keys to phrase push

Hello! We are new to Phrase and are just starting to use the phrase cli. We have a command setup to push updated keys to Phrase and just noticed that phrase push does not automatically delete unused keys.
We are able to work around this for now by using
phrase uploads cleanup --id <YOUR_UPLOAD_ID>

as outlined in the usage docs every time after we upload in case we've deleted keys, but it's a bit tough to extract the upload id from the response to set it up to run automatically.
Have you considered adding a flag to phrase push or an option that could be added to phrase.yml to run the cleanup on the upload? Does one already exist?

Just to add another voice - I've given this a thumbs up because I've hit exactly the same issue. Cleanup of unmentioned keys is something we normally do after every upload, and so I've got some ugly regex magic for parsing the UUID out of the response. An extra flag on phrase push would be great

Just to add another voice - I've given this a thumbs up because I've hit exactly the same issue. Cleanup of unmentioned keys is something we normally do after every upload, and so I've got some ugly regex magic for parsing the UUID out of the response. An extra flag on phrase push would be great

Hey @ciaran-phillips can you please share your workaround solution?

We have decided to close all GitHub issues and, instead, handle them through our Customer Support. We think this shift will allow us to offer proper prioritization of issues as well as a more appropriate response time that would be expected from Phrase products.
We apologize for any inconveniences this may cause. If you believe your issue is still relevant or has a high priority, please contact<EMAIL_ADDRESS>and we can take more direct action toward finding a solution.

We have decided to close all GitHub issues and, instead, handle them through our Customer Support.

Well that's just silly. If you don't want to use GitHub, I would suggest you provide at least have a comparable offering on your website (eg a support forum), but all I can see is a "contact support" form. Removing this channel takes away transparency and inhibits discussion (see: this thread).

I agree with @jarrodrobins. Would appreciate open communication to everyone that is looking for this.
That said; Looking for the same thing. Do we have a flag yet? :)

Hi everyone - sorry for not getting back here.
The decision made in the past was wrong and we apologize for that.
We have recognized that it is way better for developers to fire their questions directly in github where they are related to the code.
That said we have adjusted our workflow and have a custom integration so that first a customer success manager will get in touch directly within github issues. If it can not be sorted out by customer success a developer will be involved.
To get this process triggered for this issue - if it is not resolved yet - I would kindly ask to re-create an issue so that it get's into our customer success database.
Again I am sorry for the decision that was made in the past and hope that our new workflow will make everyone happy.

Thanks for reversing @forelabs, appreciate it.
I emailed Support about this issue - apparently it's now been recorded as a feature request.
For anyone else still reading this, in the meantime here's the script I use. I wrote it specifically for multi-module Android projects that have more than one strings file. I don't recommend using phrase uploads cleanup unless you are uploading only one file, otherwise you'll blow away all your translations upon subsequent uploads.
I'm sure someone can write a better Bash script than this, but it seems to work well enough.
Make sure you're using the tags param in your .phrase.yml file to tag each uploaded file. You'll also need to set PHRASE_ACCESS_TOKEN and PHRASE_PROJECT_ID (get from your .phrase.yml file) as environment variables.
#!/bin/sh

echo "Pushing to Phrase"

phrase push --access_token $PHRASE_ACCESS_TOKEN | tee push_output

cat push_output | while read first_line; read second_line
do
	tag=`echo $first_line | sed -n '/ *Uploading* / { s///; s/\/.*//; p; }'`
	upload_id=`echo $second_line | sed -n '/ *Check upload Id*: / { s///; s/,.*//; p; }'`

	echo "Deleting unmentioned strings from upload with id $upload_id and tag $tag"

	phrase keys delete-collection --project_id $PHRASE_PROJECT_ID --q "tags:$tag unmentioned_in_upload:$upload_id" --access_token $PHRASE_ACCESS_TOKEN
done

rm push_output

It's pretty hacky, grabbing the tag and the upload ID from the output. If the Phrase CLI output changes this will likely break.

Please @forelabs can you re-open this issue.
We still wait for a solution.
Here the steps to reproduce it:

Create a new git branch my-branch
Add a new key in your locale YAML files.
Create a new phrase branch my-branch.
phrase push --branch my-branch.
Delete the key in your locale YAML files.
phrase push --branch my-branch.
Expectation: The key should not appear in phrase.com (branch  my-branch).
Issue: The key still appears in phrase.com (branch  my-branch).

Are there any news on this issue, @forelabs?
Regarding @jarrodrobins post, it has been recorded as a feature request, but this issue still remains closed.
Would love to see this option in the CLI as the mentioned scripting solution has other downsides (when using --use-local-branch-name, we also have so extract the branch name somehow, before we can call the cleanup). Maybe you can give us an update and re-open this one to avoid confusion 🙏🏼

Hi there, we're struggling with this too. It would be great to get a solution!
P.S.: One other workaround we have for this is to "Upload files" within Phrase (en-US.json, for example) when you start a translation project, instead of importing keys from GitHub via the client or the "GitHub sync". When you do that, you get a big red button called "Deleted unmentioned keys" that will delete keys from all languages if they're not present in the upload... That does the trick, but it's crazy that we cannot declare that at least in the phrase.yml config....

Still waiting any news on this issue, @forelabs.

I would like to let @theSoenke and the team take over this (since we have moved out the cli to a new team).

Opened internal JIRA ticket (TSI-2234) to address this.

Implemented by adding --cleanup option to phrase push.

Hey, is cleanup doing what it's supposed to be?
When we use --cleanup on our uploads it deletes unused keys in the target language also in the base language.
Which means all untranslated keys are deleted in the base language, when we upload with --cleanup.

@malua keys are not tied to any specific language. each key can have a translation in any of the project's locales (languages). cleanup works with keys, it deletes keys not mentioned in any of the uploads caused by CLI push.
deleting translations instead is currently not supported by the CLI, and would be a separate feature request.

Ok thanks for your answer. Is it possible to add the cleanup option insde the .phraseapp.yml config file. So that the cleanup will only be executed for the base language files?

I would decouple one feature request (support specifying --wait and --cleanup options in the config file) from the other (execute cleanup only using a single locale keys) and open new issues accordingly.

Great thanks I will do that!

Just for clarity, phrase push --wait --cleanup has removed all the unused keys in my source language but not in any other language. How can I delete all the keys missing a source?


Fixes for deployment

This PR includes all the last minute changes that were necessary to run the online and offline ingestor separately in the staging environment serving YMIR and CODA.
Changes summary:

online ingestor

logging
offline ingestor command
message deserialization

ofline ingestor

schema selection
variable value computation
dataset and origdatablock creation

I'll just... merge it...?


varlink API hangs: too aggressive daemon timeout hits systemd's start limit

/kind bug
Description
In trying to debug issue #3602 , I ran some podman operations on the command line using the varlink API. But this locks up very often with hangs or "Unable to connect: CannotConnect".
Steps to reproduce the issue:

podman pull docker.io/library/busybox:latest

mkdir -p /tmp/v1 /tmp/v2

while true; do podman rm -f busybox-with-tty || true; varlink call unix:/run/podman/io.podman/io.podman.CreateContainer '{"create":{"args":["docker.io/library/busybox:latest","sh","-c","while echo Hello World; do sleep 1; done"],"resources":{},"name":"busybox-with-tty","tty":true,"publish":["6000:5000/TCP","6001:5001/UDP","8001:8001/TCP"],"env":["APPLE=ORANGE","PEAR=BANANA","RHUBARB=STRAWBERRY"],"volume":["/tmp/v1:/tmp/ro:ro","/tmp/v2:/tmp/rw:rw"]}}'; varlink call unix:/run/podman/io.podman/io.podman.StartContainer '{"name":"busybox-with-tty"}'; podman ps; done
(This is a fairly faithful representation of what happens in our integration test).

Describe the results you received:
After a few iterations this starts to fail with "Unable to connect: CannotConnect". The journal says why:
systemd[1]: io.podman.service: Succeeded.
systemd[1]: io.podman.service: Consumed 204ms CPU time.
systemd[1]: io.podman.service: Start request repeated too quickly.
systemd[1]: io.podman.service: Failed with result 'start-limit-hit'.
ystemd[1]: Failed to start Podman Remote API Service.
systemd[1]: io.podman.socket: Failed with result 'service-start-limit-hit'.

It seems that pretty much every operation starts io.podman.service, and immediately stops it again. podman varlink --help says the default timeout is 1s, but apparently it's lower than that -- and even that, if you issue one request per second (which is fairly realistic for a UI), then you hit the "5 restarts in 10 seconds" barrier pretty quickly.
Describe the results you expected:
varlink calls should succeed regardless of their frequency. Please increase the timeout to something reasonable, a magnitude of a minute. Once something starts talking to varlink, it's reasonable to assume that it will do more than just one call, so serving each call by a full startup of the executable is very expensive and prone to start limits.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:            1.4.5-dev
RemoteAPI Version:  1
Go Version:         go1.12.6
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.6
  podman version: 1.4.5-dev
host:
  BuildahVersion: 1.9.0
  Conmon:
    package: podman-1.4.4-1.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 0.2.0, commit: 41010e63c287618b1dc34ee11d10d268e2feeefe'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree: 286429184
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    package: runc-1.0.0-93.dev.gitb9b6cc6.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8+dev
      commit: e3b4c1108f7d1bf0d09ab612ea09927d9b59b4e3
      spec: 1.0.1-dev
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 1
  hostname: m1.cockpit.lan
  kernel: 5.1.16-300.fc30.x86_64
  os: linux
  rootless: false
  uptime: 22m 59.44s
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mountopt=nodev,metacopy=on
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  ImageStore:
    number: 3
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Additional environment details (AWS, VirtualBox, physical, etc.):

 I see it in ps. The starting did succeed:
# podman ps
CONTAINER ID  IMAGE                             COMMAND               CREATED        STATUS            PORTS  NAMES
996536350dba  docker.io/library/busybox:latest  sh -c while echo ...  3 minutes ago  Up 3 minutes ago         c1

systemd shows that the process exited cleanly, but apparently before the StartContainer call got fully processed:
 # systemctl status io.podman
● io.podman.service - Podman Remote API Service
   Loaded: loaded (/usr/lib/systemd/system/io.podman.service; disabled; vendor preset: disabled)
   Active: inactive (dead) since Thu 2019-07-18 17:19:28 EDT; 1min 0s ago
     Docs: man:podman-varlink(1)
  Process: 7435 ExecStart=/usr/bin/podman varlink unix:/run/podman/io.podman (code=exited, status=0/SUCCESS)
 Main PID: 7435 (code=exited, status=0/SUCCESS)
      CPU: 193ms

Jul 18 17:19:27 m1.cockpit.lan systemd[1]: Started Podman Remote API Service.
Jul 18 17:19:27 m1.cockpit.lan podman[7435]: time="2019-07-18T17:19:27-04:00" level=error msg="unable to find flag trace"
Jul 18 17:19:27 m1.cockpit.lan podman[7435]: time="2019-07-18T17:19:27-04:00" level=error msg="unable to find flag http-proxy"
Jul 18 17:19:27 m1.cockpit.lan podman[7435]: time="2019-07-18T17:19:27-04:00" level=error msg="unable to find flag syslog"
Jul 18 17:19:27 m1.cockpit.lan podman[7435]: 2019-07-18 17:19:27.876929013 -0400 EDT m=+0.377240165 container create 996536350dba80739e>
Jul 18 17:19:28 m1.cockpit.lan podman[7435]: 2019-07-18 17:19:28.666345623 -0400 EDT m=+1.166656657 container init 996536350dba80739e8c>
Jul 18 17:19:28 m1.cockpit.lan podman[7435]: 2019-07-18 17:19:28.706713511 -0400 EDT m=+1.207024646 container start 996536350dba80739e8>
Jul 18 17:19:28 m1.cockpit.lan systemd[1]: io.podman.service: Succeeded.
Jul 18 17:19:28 m1.cockpit.lan systemd[1]: io.podman.service: Consumed 193ms CPU time.

This is not triggering the start-limit, as it's just two calls. Just the second one seems to happen at a bad time.

safe to assume you are running this all as root?

also, instead of running varlink as a service, if you run it manually with a timeout of 0, does it work?

safe to assume you are running this all as root?

Yes.
I took a look again at the timeout behaviour in
issue #3602, with microsecond precision. The important part for this bug:
# journalctl -o short-precise -f -u io.podman -u io.podman.socket
-- Logs begin at Thu 2019-07-18 02:32:35 EDT. --
Jul 19 03:26:51.863787 m1.cockpit.lan systemd[1]: Listening on Podman Remote API Socket.
Jul 19 03:27:10.089846 m1.cockpit.lan systemd[1]: Started Podman Remote API Service.
Jul 19 03:27:10.172716 m1.cockpit.lan podman[8570]: time="2019-07-19T03:27:10-04:00" level=error msg="unable to find flag trace"
Jul 19 03:27:10.179353 m1.cockpit.lan podman[8570]: time="2019-07-19T03:27:10-04:00" level=error msg="unable to find flag http-proxy"
Jul 19 03:27:10.179511 m1.cockpit.lan podman[8570]: time="2019-07-19T03:27:10-04:00" level=error msg="unable to find flag syslog"
Jul 19 03:27:10.438117 m1.cockpit.lan podman[8570]: 2019-07-19 03:27:10.436936497 -0400 EDT m=+0.313240917 container create eeab55fbab3c3ba61b4ef482516960377fe455a2352727de540258388ad24f90 (image=docker.io/library/busybox:latest, name=c1)
Jul 19 03:27:11.220678 m1.cockpit.lan podman[8570]: 2019-07-19 03:27:11.220016136 -0400 EDT m=+1.096320510 container init eeab55fbab3c3ba61b4ef482516960377fe455a2352727de540258388ad24f90 (image=docker.io/library/busybox:latest, name=c1)
Jul 19 03:27:11.259892 m1.cockpit.lan podman[8570]: 2019-07-19 03:27:11.259843447 -0400 EDT m=+1.136147722 container start eeab55fbab3c3ba61b4ef482516960377fe455a2352727de540258388ad24f90 (image=docker.io/library/busybox:latest, name=c1)
Jul 19 03:27:11.448315 m1.cockpit.lan systemd[1]: io.podman.service: Succeeded.
Jul 19 03:27:11.449047 m1.cockpit.lan systemd[1]: io.podman.service: Consumed 171ms CPU time.

So this shows that between the last event and the shutdown there's less than 0.2s.
With
/usr/bin/podman varlink --timeout 0 unix:/run/podman/io.podman

the container create/start/rm loop works fine, and podman does not exit.
With --timeout 10000 it works as well. With --timeout 1000 it exits too fast (and it's not really a full second).

The service files and the backend has been improved. The issue is now resolved in master.
Thanks a lot for opening the issue, @martinpitt !


[BUG] Delay in Blob Availability vs CreatedOn Timestamp

Library name and version
Azure.Storage.Blobs 12.17.0
Describe the bug
In the Azure.Storage.Blobs SDK version 12.17.0, there's an observed discrepancy between the CreatedOn timestamp and the actual time the blob is available in the storage. Specifically, for larger blobs, the CreatedOn timestamp suggests that the blob has been created and is available several seconds before it actually appears and becomes accessible in the blob storage.
Expected behavior
The CreatedOn timestamp should accurately reflect the time when the blob is fully uploaded and available in the blob storage.
Actual behavior
The CreatedOn timestamp is set a few seconds (variable based on blob size) before the blob is actually accessible in the storage.
Reproduction Steps

Use the Azure.Storage.Blobs SDK version 12.17.0
Upload a large blob (e.g., several gigabytes in size) to Azure Blob Storage
Immediately after receiving the upload confirmation, query the blob's metadata to obtain the CreatedOn timestamp
Repeatedly query the blob storage for the presence of the blob
Note the discrepancy between the CreatedOn timestamp and the actual time the blob becomes available.

Environment

OS: Windows 10.0.19045
Azure Storage Explorer: 1.31.1
.NET Runtime Version: 7.0.401

This behavior is expected, as the backend storage service is a distributed service.


Error with single speaker adaptation

'\torch\nn\backends\backend.py' line 11, in getattr
"Could not find function class for [{}]".format(name))
AttributeError: Could not find function class for [Embedding]

This seems like an internal pytorch error and not something spawning from our work


Complete routing

In this Pr, I've done these tasks:

Create routing for Quote, calculator, and home pages;
Stylize the components using the CSS module;
fix linters error;

Thank you all


Use funding key in package.json instead of postinstall script

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ion-fab in ionic/core throws a type error

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ ] 3.x
[x ] 4.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

In ionic/core this syntax
<ion-fab bottom right>
    <ion-fab-button>Share</ion-fab-button>
    <ion-fab-list side="top">
      <ion-fab-button>Facebook</ion-fab-button>
      <ion-fab-button>Twitter</ion-fab-button>
      <ion-fab-button>Youtube</ion-fab-button>
    </ion-fab-list>
    <ion-fab-list side="left">
      <ion-fab-button>Vimeo</ion-fab-button>
    </ion-fab-list>
  </ion-fab>

Throws this type error Type '{ bottom: true; right: true; }' has no properties in common with type 'IonFabAttributes'.  After talking to Brandy about this its because bottom and right are css attributes, not JSX attributes.
Steps to reproduce:

Use the JSX posted above in a render function with the latest ionic/core and stencil/core

@jthoms1 This is similar to the issue with adding padding to elements we discussed previously. We can convert these to input(s), but they're currently just CSS attributes.


[$250] Desktop app startup is slow

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.75-0
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @neil-marcellini
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1716480870229429
Action Performed:

Install the desktop app on Mac
Open it
Quit/close it completely
Open it again

Expected Result:
The app opens quickly, within a few seconds
Actual Result:
The app takes over 30 seconds to open, then a bunch of time to load a chat. Let's focus on the slow opening part specifically, since that's unique to the desktop app.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/7347b5a4-0e8d-480f-acf5-cfc14a0dead7

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0192a06bcd75528339
Upwork Job ID:<PHONE_NUMBER>691560448
Last Price Increase: 2024-05-23

Issue OwnerCurrent Issue Owner: @eh2077

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Contributor details
Your Expensify account email<EMAIL_ADDRESS>>
Upwork Profile Link: https://www.upwork.com/freelancers/~017e81b8541352d771?mp_source=share

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~017e81b8541352d771?mp_source=share

I have solved the issue and it is now ready for submition

@goldenbear101 Can you post a proposal for this issue? You can refer our https://github.com/Expensify/App/blob/main/contributingGuides/CONTRIBUTING.md

Waiting on proposals

Sorry to say but, I do not have the means (connects) to write a proposal on upwork. I request you allow me to operate through Telegram, you would be able to access the work, and only pay after confirmation.

@goldenbear101 You can just post proposals here and we'll review it, see propose-a-solution-for-the-job

Proposal
The desktop app for Mac takes over 30 seconds to open, significantly longer than expected. This issue is unique to the desktop app and affects user experience.
Root Cause
The slow startup likely results from:
Slow initialization of application components
Inefficient resource loading
Network requests made during startup
Proposed Changes
To solve the problem, the following changes are recommended:

Optimize Initialization
Streamline the initialization process to load only essential components at startup.

async function initializeApp() {
    await loadEssentialComponents();
    // Load non-essential components after startup
    setTimeout(loadNonEssentialComponents, 0);
}

Asynchronous Resource Loading
Load resources asynchronously to avoid blocking the main thread.

async function loadResources() {
    const [image, data] = await Promise.all([
        loadImageAsync('path/to/image.png'),
        fetchDataAsync('path/to/data.json'),
    ]);
}

Network Request Optimization
Delay non-critical network requests until after the app has loaded.

async function initializeApp() {
    await loadEssentialComponents();
    setTimeout(() => {
        fetchNonCriticalData();
    }, 0);
}

Expected Result
The app should open quickly, within a few seconds.
By implementing these changes, the startup time of the desktop app should be significantly reduced.

@dominictb your proposal sounds pretty promising. Would you please do some benchmarking / testing for us to gather evidence about how much faster it starts up when built for arm? If you don't have an arm mac, please provide steps for me to test.

I'm testing @dominictb 's proposal

Issue not reproducible during KI retests. (First week)

I'll update testing results tomorrow

@dominictb this sounds related with https://github.com/Expensify/App/issues/39631#issuecomment-2148278445, right?

I can see significant difference of starting time between universal and x64 app running on M1 MacBook. I think it's common to create distributables for different hardwares, eg x64, arm64 and universal type bundles for macOS. So, @dominictb 's proposal looks good to me.
The other issue seems share some root cause with this issue. #39631 was created earlier though this issue seems has clearer scope. I'm also fine if we decide to put this issue on hold for the older one. Let's defer it to internal engineering team.
🎀👀🎀 C+ reviewed

Unassigning myself as @neil-marcellini is the true Engineer on this issue.

Not overdue, waiting for @neil-marcellini 's review on https://github.com/Expensify/App/issues/42558#issuecomment-2155182911

I can see significant difference of starting time between universal and x64 app running on M1 MacBook. I think it's common to create distributables for different hardwares, eg x64, arm64 and universal type bundles for macOS. So, @dominictb 's proposal looks good to me.

Ok great, I agree! Let's build the desktop app as universal.

I merged that PR, but I want to ask @dominictb @eh2077 how does this work for updating the app? If I click the update menu item in app with it change to being a universal app? If not, how can we make it do that?

Checklist

[x] [@eh2077] The PR that introduced the bug has been identified. Link to the PR: I don't think there's a specific PR responsible for this
[x] [@eh2077] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
[x] [@eh2077] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] [@eh2077] Determine if we should create a regression test for this bug. No

We fixed two issues together here

https://github.com/Expensify/App/issues/39631
https://github.com/Expensify/App/issues/42558

@mallenexpensify I saw you have handled the payment for the other issue. Can you also take care of this one please? As for the payment arrangement, whatever you all think is best works for me!

Contributor: @dominictb paid $250 via Upwork
Contributor+: @eh2077 paid $250 via Upwork
@eh2077 , the PR to fix this that you reviewed also fixed another bug. If you invested additional time on the review, because their was an increase of scope, you might be due additional compensation.  Comment if so.


coordinateTapped

Hello, thank you for this example I learned a lot but I have a doubt, in the event CoordinateTapped, How can I get the position of this point in angular 2?

I found the answer


Backend container: module 'h11' has no attribute 'Event'

Hello, anybody had a problem when starting with docker-compose up -d that container for backend write out error:
user@user-machine:~/Desktop/generated_project/fastapi$ sudo docker run backend:latest
Checking for script in /app/prestart.sh
Running script /app/prestart.sh
Traceback (most recent call last):
File "/app/app/backend_pre_start.py", line 5, in
from app.db.session import SessionLocal
File "/app/app/db/session.py", line 4, in
from app.core.config import settings
File "/app/app/core/config.py", line 7, in
class Settings(BaseSettings):
File "pydantic/main.py", line 197, in pydantic.main.ModelMetaclass.new
File "pydantic/fields.py", line 506, in pydantic.fields.ModelField.infer
File "pydantic/fields.py", line 436, in pydantic.fields.ModelField.init
File "pydantic/fields.py", line 557, in pydantic.fields.ModelField.prepare
File "pydantic/fields.py", line 831, in pydantic.fields.ModelField.populate_validators
File "pydantic/networks.py", line 591, in get_validators
File "pydantic/networks.py", line 578, in pydantic.networks.import_email_validator
File "/usr/local/lib/python3.7/site-packages/email_validator/init.py", line 6, in
import dns.resolver
File "/usr/local/lib/python3.7/site-packages/dns/resolver.py", line 39, in
import dns.query
File "/usr/local/lib/python3.7/site-packages/dns/query.py", line 58, in
import httpx
File "/usr/local/lib/python3.7/site-packages/httpx/init.py", line 2, in
from ._api import delete, get, head, options, patch, post, put, request, stream
File "/usr/local/lib/python3.7/site-packages/httpx/_api.py", line 4, in
from ._client import Client
File "/usr/local/lib/python3.7/site-packages/httpx/_client.py", line 29, in
from ._transports.default import AsyncHTTPTransport, HTTPTransport
File "/usr/local/lib/python3.7/site-packages/httpx/_transports/default.py", line 30, in
import httpcore
File "/usr/local/lib/python3.7/site-packages/httpcore/init.py", line 1, in
from ._api import request, stream
File "/usr/local/lib/python3.7/site-packages/httpcore/_api.py", line 5, in
from ._sync.connection_pool import ConnectionPool
File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/init.py", line 1, in
from .connection import HTTPConnection
File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/connection.py", line 13, in
from .http11 import HTTP11Connection
File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/http11.py", line 44, in
class HTTP11Connection(ConnectionInterface):
File "/usr/local/lib/python3.7/site-packages/httpcore/_sync/http11.py", line 140, in HTTP11Connection
self, event: h11.Event, timeout: Optional[float] = None
AttributeError: module 'h11' has no attribute 'Event'
I find solution that I need to install pip install --force-reinstall httpcore==0.15 but I don't know how to install it inside stopped container or where to write this line during installation of backend container
Did anyone had this problem ? Every help will be appreciated and thank you in advance

I figured it out.
You have to add this line in file /backend/app/pyproject.toml in [tool.poetry.dependencies]
httpcore = "0.10"
Then it's working properly.

For those rookies like me who is seeing the above resolution, update the poetry lock file before building the container again.
i.e. go to the path of toml file above, activate the venv and run command "poetry lock"


feat: increment parse in lsp

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y #895

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
Add parse cache in lsp state and increment parse in lsp.

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[x] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.82%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2300

Relevant Lines:
2619

💛  - Coveralls


vimPlugins.fruzzy: init at 2019-10-28

Motivation for this change
This adds the vim plugin fruzzy. Note that this plugin has a 'native' component (fuzzy searcher implemented in Nim), so I bootstrapped the Nim dependencies in a little bit of a hackey way (could be made neater if https://github.com/NixOS/nixpkgs/pull/67878 ever gets merged).
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg build vimPlugins.fruzzy

rebased and resolved 'forbidden in restricted mode'
@GrahamcOfBorg build vimPlugins.fruzzy

@jonringer Have been using this happily for months now, is anything blocking merge? Thanks!

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-may-2019/3032/167

Result of nixpkgs-review pr 81440 1

1 package built:
- vimPlugins.fruzzy

I took a break while my server was being repaired. sorry


Inconsistant spacing between date input fields

Bug Report
A manual tester noticed the spacing between day and month fields is slightly smaller than the spacing between month and year, due to the month label being larger than the field itself, effecting the look and feel of our product.

What is the issue?

What steps are required to reproduce the issue?

What was the environment where this issue occurred?

Device:
Operating System:
Browser:
Browser version:
NHS.UK frontend package version:
Node version:
npm version:

Is there anything else you think would be useful in recreating the issue?

Hi @J1883R15H thanks for opening this issue, the team will triage this on Monday and get back to you on it.

This visual inconsistency also seems to be the same in the GOV.UK Frontend (GOV.UK design system - Date input example)
It could potentially be fixed by creating a new modifier class to reduce the font size of the date input label such as:
.nhsuk-date-input__label---xs {
  @include nhsuk-font(16);
}
``

This fixes the spacing issue however it reduces the font size by quite a bit and would require further user testing to make sure that the font size is still usable and is accessible.

I've put a message out for design input on this.

Hi @J1883R15H, did you attempt the suggested fix above? How did it test with users for usability and readability?

Going to close this issue due to inactivity and the initial concerns in the original response. Feel free to reopen if you think it might still be an issue that needs addressing.


Clippy fixes and version pin

The CI broke again because clippy is configured to target stable and introduces breaking changes with each version. Apply the fixes for the latest stable, then pin clippy to this version.
For the GUI i wasn't sure so i just pinned clippy to the latest stable.

self-ACK f996e2565797b413870d75fa764ebd207bb264c4 -- trivial


Remove Stakeholders

This list is now available on
https://solidproject.org/use-solid/ for Pod and WebID providers
and
https://solidproject.org/use-solid/apps for Solid Apps.
I propose to delete this list to avoid wiki rot.

PR closure, even by the original submitter, without merge and without comment, especially after meaningful and/or approving comment/discussion on that PR, is baffling to later readers like myself.  Such closure should always be accompanied by some explanation thereof.  Adding it now would be better than not adding it at all.


Correct name of github actions "focus-stacking"

Give a proper name

Rename action focus-stacking to "make_pytest_check"


Unused type parameter

I just upgraded to Julia 1.8.2 and saw this warning:
WARNING: method definition for source_func_longwave at /.julia/packages/RRTMGP/4TrqV/src/optics/Sources.jl:155 declares type variable I but does not use it.

Closed by #320.


stable hlo sqrt

Add unit tests for stable hlo sqrt to tt-torch and tt-xla.

tt-xla was already, tt-torch done: https://github.com/tenstorrent/tt-torch/pull/2


fix: 🐛 added missing imports

👋 Thanks for creating a pull request! 🚀 Checkout the storybook we've created for it: react


Bug in filter.py

In 'synthesis()' there's a call to 'operator.cheby_op':
s = s + operator.cheby_op(self.G,
cheb_coeffs[i], c[i * N + tmpN])

but the function it's been moved to fast_filtering.py

That's right. Thanks for catching it! :)


Fix the Docker Compose to mount the config.toml volume as file and not as a directory

Fix an error on the docker-compose.yaml file since the config.toml volume mount does not specify the correct type.
It is mounting config.toml as a directory instead of a file:
docker compose up

[+] Running 2/0
 ✔ Container perplexica-searxng-1                             Running    0.0s
 ✔ Container perplexica-perplexica-frontend-1         Created   0.0s
Attaching to perplexica-backend-1, perplexica-frontend-1, searxng-1
Gracefully stopping... (press Ctrl+C again to force)
Error response from daemon: failed to create task for container: failed to create shim task:
OCI runtime create failed: runc create failed: unable to start container process: error during container init:
error mounting "/Users/***/***/Perplexica/config.toml" to rootfs at "/home/perplexica":
mount /Users/***/***/Perplexica/config.toml:/home/perplexica (via /proc/self/fd/6), flags: 0x5000:
not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)?
Check if the specified host path exists and is the expected type

I'm closing this PR since I made a new one with Dockerfile size optimization + security updates


when using setIcon to change a png icon to an svg one, the old png is still visible (except Firefox)

When I use setIcon on a marker to substitute an icon, it works if it is from png to png, or svg to svg, but not from png to svg. Firefox works, Chrome, Safari don't. The old png icon is still visible on top of the svg one.

The problem is still present. Here is the sample: https://embed.plnkr.co/lY4yqS/
Click on marker will cause switching its icon.
The Northern marker is toggling SVG icons only
The Southern marker is toggling PNG <-> SVG icons
SVG -> SVG switching is basically ok (some flickering is visible in Chrome)
PNG -> SVG switching is buggy:

Chrome: new icon size is set, but still old icon is displayed until some action is done, e.g. drag the map
Safari: after switching to SVG icon both icons are displayed (worst case)
Firefox: flickering is visible, but more-less ok


cluster-objects Decode functions have incorrect tag tests

Problem
The generated code looks like this:
CHIP_ERROR Type::Decode(TLV::TLVReader &reader) {
    CHIP_ERROR err;
    TLV::TLVType outer;
    err = reader.EnterContainer(outer);
    ReturnErrorOnFailure(err);
    while ((err = reader.Next()) == CHIP_NO_ERROR) {
        switch (chip::TLV::TagNumFromTag(reader.GetTag()))

but this is assuming the tag is in fact a context-specific tag.  Nothing has checked that it is!  If it's not (i.e. a profile tag, though someone could send bogus data with a struct containing anonymous tags), then behavior of TagNumFromTag is wrong, in that it will return part of the profile tag, which could match the value of one of our field ids even though the tag is not the right one.
Proposed Solution
Either check that the tag is a context tag or do compares on tags, not tag numbers.  Add tests.
@yunhanw-google @mrjerryjohns

I'd slightly lean towards the compares on tags, to make it a better pattern in case we have mixed context & profile-tags (for manufacturer extensions, if/when we get to it).


[karma-esm] cannot execute snapshot testing in IE11 and Edge

Snapshot tests stopped working in IE11 and Edge (EdgeHTML) with the latest release.
The issue can be reproduced by running npm init @open-wc.
The test shows initially the text "hey there Nr. 5!" and an "increment" button fails with the following error:
TypeError: Unable to get property 'type' of undefined or null reference
   at assertHtmlEqualsSnapshot (base/node_modules/@open-wc/semantic-dom-diff/chai-dom-diff.js?transform-systemjs:114:11)
   at equalSnapshot (base/node_modules/@open-wc/semantic-dom-diff/chai-dom-diff.js?transform-systemjs:156:11)
   at methodWrapper (base/node_modules/chai/chai.js?transform-systemjs:7439:17)
   at _callee4$ (base/test/test-snapshots.test.js?transform-systemjs:201:19)
   at tryCatch (polyfills/regenerator-runtime.45f8b90cc0fac37d446d8da4b68e27f5.js:45:7)
   at invoke (polyfills/regenerator-runtime.45f8b90cc0fac37d446d8da4b68e27f5.js:271:9)
   at prototype[method] (polyfills/regenerator-runtime.45f8b90cc0fac37d446d8da4b68e27f5.js:97:9)
   at asyncGeneratorStep (base/test/test-snapshots.test.js?transform-systemjs:70:7)
   at _next (base/test/test-snapshots.test.js?transform-systemjs:92:11)
   at Anonymous function (polyfills/core-js.577a5602a7262d6256830802d4aaab43.js:8:30320)

I see this too

Seems to work with es-dev-server 1.39.1


add keyboard examples

closes https://github.com/ayrat555/frankenstein/issues/55

Thanks a bunch!


Update CODEOWNERS to fix some bad paths

Opportunistically update CODEOWNERS to fix a couple of bad paths.

@ronniegeraghty just an FYI - the catch all /sdk/communication entry should have an owner. Right now, there are 13 libraries under /sdk/communication but only 10 of them are in the codeowners file with owners. The CODEOWNERS file in azure-sdk-for-js has the same issues.

I need to override check-enforcer as there's nothing that will run for this change.

/check-enforcer override


chore(master): release 1.1.74

:robot: I have created a release beep boop
1.1.74 (2023-09-05)
Miscellaneous

deps: update dependency orchestra/testbench to v8.10.1 (7e01c43)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v1.1.74 :sunflower:


Prepare for Chrome 79 release (web XR in navigator by default)

It's necessary to handle new Web XR Device API default support on chrome from version 79+.
https://www.chromestatus.com/features/schedule
XR APIs will be present by default on the browser, this can potentially break AR.js based applications.
Before 10 of December, it's required - until a WebXR support will not ship for AR.js - to NOT use default XR API but current one (polyfill).

What can we do to advance this? I will study about the update to collaborate.

Hi and thanks to be willing to help!
@spartalisdigital install chrome canary (version 79) and try to launch any AR.js based example.
If it's not working, see in console what's the error and please post here screenshots

this is a bug coming from imported aframe.
I opened an issue on their repo: https://github.com/aframevr/aframe/issues/4317

I am also taking a look at this.
Right now it works on my phone. Will check on PC later.

It seems that version 79 is out... What next? May i help in some way?

2019-12-14. Aframe 1.0.0 is out and it's working with AR.js 2.0.8 on Android 8.0 and Chrome 79(webXR enable by default).

No action is required on AR.js side.
A-frame (which gave problems with web xr spec in beta) now works.
If you find problems with AR.js based apps and are using a-frame, please use the v1.0.0 to avoid problems with WebXR device API


What is the easiest way of creating  a folder and giving access to a group of users by modifying present code

@ciur is this possible?

There is no easy way. What you are asking is a complex feature.
I updated the roadmap and this feature will be added in 2.6.0.
If you want it faster - I am looking forward for a pull request from you.


Distributed keras using TFOS

Hi,
I am looking at this example. Here, in the map_func we are loading data using mnist.load_data which loads the entire dataset (dataset is in tfr format) into memory. I ran the example and it looks like every worker node calculates gradients for the entire training data. But ideally, we should distributed batches of data on every worker node, right?
Can someone explain if my understanding is correct and how is data being distributed in this example?
Is it possible to write distributed code for keras in TFOS?

@somya12 Most of the examples are there to demonstrate the conversion to TFoS (while trying to minimize the amount of change to the code).  That said, this example originally read the entire dataset into memory, so that's why each worker currently does the same.  If you want to distribute the data (in InputMode.TENSORFLOW), you probably want to store your data on your distributed file system and then use the tf.data APIs to read them in a sharded fashion.  Specifically, for the TFRecord format, you should probably use the tf.data.TFRecordDataset.

Closing due to inactivity.  Feel free to reopen if still an issue.


[KARAF-5787] Improve scheduler whiteboard handler to allow users to define scheduler service properties in raw String

retest this please


Improve plugin panels

Do not prepend plugin name unless necessary
Allows for "cleaner" navigation URLs

e.g. for the "wireviz" plugin:

@SchrodingersGat does this ensure the order of panels between 2 plugins with the same panel name is stable?

@SchrodingersGat does this ensure the order of panels between 2 plugins with the same panel name is stable?

There should be no change to this behaviour, the order of insertion is fixed - assuming that the API always delivers panels in the same "order"


Upgrade library for 4.11.3 type enums

Please, do the following:
a. Resend to the dev branch.
b. Use the commit prefixes according to the 'CONTRIBUTING' guide https://github.com/alkurbatov/cpp-sc2/issues/9


Issue on migration or new version

Hi,
I recently had to move all my configuration to a new microSD cuz an error on my las raspberry config. When i restored the bakcup and set the environment i detect this issue and the system dont add the vacuum to the devices on the hass.
My configuration:
#Hacs xiaomi vacumm
vacuum:
  - platform: xiaomi_vacuum
    host: <IP_ADDRESS>XX
    token: "the token info"
    name: Robotina

System Health

version
2021.1.5

installation_type
Home Assistant Supervised

dev
false

hassio
true

docker
true

virtualenv
false

python_version
3.8.7

os_name
Linux

os_version
5.4.83-v7+

arch
armv7l

timezone
America/Bogota

Home Assistant Community Store

GitHub API
ok

Github API Calls Remaining
4901

Installed Version
1.10.1

Stage
running

Available Repositories
710

Installed Repositories
8

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Hass.io

host_os
Raspbian GNU/Linux 10 (buster)

update_channel
stable

supervisor_version
2021.01.7

docker_version
20.10.2

disk_total
14.0 GB

disk_used
5.3 GB

healthy
true

supported
failed to load: Unsupported

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.2.0), Bitwarden RS (0.7.0), Duck DNS (1.12.4), NGINX Home Assistant SSL proxy (3.0.1), Nginx Proxy Manager (0.8.2), MariaDB (2.2.1), SQLite Web (2.3.2), Home Assistant Google Drive Backup (0.103.1), MQTT Server & Web client (1.2.0)

Lovelace

dashboards
1

mode
storage

views
8

resources
3

Spotify

api_endpoint_reachable
ok

I attach the log errors.

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
    await task
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/xiaomi_vacuum/vacuum.py", line 322, in update
    state = self._vacuum.status()
  File "/config/custom_components/xiaomi_vacuum/miio/dreamevacuum.py", line 260, in status
    return self.get_properties_for_dataclass(DreameStatus)
  File "/config/custom_components/xiaomi_vacuum/miio/miot_device.py", line 63, in get_properties_for_dataclass
    response = {
  File "/config/custom_components/xiaomi_vacuum/miio/miot_device.py", line 64, in <dictcomp>
    prop["did"]: prop["value"] if prop["code"] == 0 else None
TypeError: list indices must be integers or slices, not str

Has your vacuum updated to version 3.5.8_1096? could this be a problem? If I update the vacuum, won't there be any problems?

Has your vacuum updated to version 3.5.8_1096? could this be a problem? If I update the vacuum, won't there be any problems?

hi @Radlagerkok, at this moment the vacumm have 3.5.8_1059 😮 but the app says that i already have the latest version.

At 3.5.8_1096, everything works in the home assistant.  In mi home, the map is divided into zones.

I was looking on some reddit and forums and the new version is available for some users not for every-one, i think they are rolling to a small group of people and maibe on future they make the realease available for every one. I think the only solution is wait to have the new firmware version.
Other solution its try to make a downgrade for the xiaomi_vacuum component maibe from an old bakcup and dont upgrade the version until the new firmware is avialable for me.

some people put the region of Singapore or Germany.  An update came to them.  You can also create another mihome account and link the robot there.  It will update.  My robot updated yesterday

I finally receive the firmware update and i have back on the hass the vacumm, tnks @Radlagerkok for your help.!

Hey! I'm having the same issue, even with the latest firmware.

same here. i had the isue before and after the rooms update. here is the log:
2021-02-10 11:07:01 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for garbage_collection which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-02-10 11:07:01 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up http
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up system_log
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain system_log took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.1 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'auth', 'http', 'websocket_api', 'system_log', 'lovelace', 'person', 'cloud', 'device_automation', 'api', 'onboarding', 'image', 'frontend', 'search', 'alexa', 'config', 'hassio', 'webhook'}
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up auth
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2021-02-10 11:07:02 WARNING (MainThread) [homeassistant.components.lovelace] Lovelace is running in storage mode. Define resources via user interface
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up api
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up alexa
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain alexa took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up config
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up hassio
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up webhook
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up image
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up search
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.1 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.2 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain image took 0.0 seconds
2021-02-10 11:07:02 INFO (SyncWorker_0) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up person
2021-02-10 11:07:02 INFO (SyncWorker_2) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up cloud
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.3 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.0 seconds
2021-02-10 11:07:02 INFO (SyncWorker_0) [homeassistant.loader] Loaded group from homeassistant.components.group
2021-02-10 11:07:02 INFO (SyncWorker_1) [homeassistant.loader] Loaded panel_custom from homeassistant.components.panel_custom
2021-02-10 11:07:02 INFO (SyncWorker_4) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up frontend
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.components.http] Now listening on port 8123
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 0.4 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'zeroconf', 'script', 'updater', 'met', 'garbage_collection', 'samsungtv', 'upnp', 'sun', 'zone', 'scene', 'ssdp', 'input_datetime', 'media_source', 'input_boolean', 'automation', 'hacs', 'light', 'shopping_list', 'history', 'dhcp', 'logbook', 'map', 'sensor', 'persistent_notification', 'input_select', 'tag', 'cast', 'mobile_app', 'ipp', 'google', 'default_config', 'blueprint', 'tradfri', 'google_assistant', 'system_health', 'tuya', 'timer', 'vacuum', 'adguard', 'input_number', 'input_text', 'tts', 'counter'}
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up updater
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain updater took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up met
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up garbage_collection
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain garbage_collection took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up sun
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up zone
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up scene
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up media_source
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up light
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up shopping_list
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain shopping_list took 0.0 seconds
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setting up history
2021-02-10 11:07:02 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up dhcp
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain dhcp took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up logbook
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up map
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up input_select
2021-02-10 11:07:03 INFO (SyncWorker_3) [homeassistant.loader] Loaded template from homeassistant.components.template
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up tag
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up google
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up blueprint
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain blueprint took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up google_assistant
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up system_health
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up tuya
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain tuya took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up timer
2021-02-10 11:07:03 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for xiaomi_vacuum which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up vacuum
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain vacuum took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up adguard
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain adguard took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up input_number
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up input_text
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up counter
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2021-02-10 11:07:03 INFO (SyncWorker_2) [homeassistant.loader] Loaded binary_sensor from homeassistant.components.binary_sensor
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up group
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain light took 1.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up xiaomi_vacuum
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain xiaomi_vacuum took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain media_source took 1.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up hacs
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain hacs took 0.0 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.6 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.4 seconds
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setting up binary_sensor
2021-02-10 11:07:03 INFO (MainThread) [homeassistant.setup] Setup of domain binary_sensor took 0.0 seconds
2021-02-10 11:07:03 INFO (SyncWorker_2) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 0.6 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain tag took 0.6 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain google_assistant took 0.4 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.vacuum] Setting up vacuum.xiaomi_vacuum
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 0.3 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain counter took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain input_text took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain group took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up sensor
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [custom_components.xiaomi_vacuum.vacuum] Initializing with host <IP_ADDRESS> (token 387571637a4d436a67564d6b30637670...)
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up ipp
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain ipp took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up tradfri
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain tradfri took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up tts
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.template
2021-02-10 11:07:04 INFO (SyncWorker_2) [homeassistant.loader] Loaded calendar from homeassistant.components.calendar
2021-02-10 11:07:04 INFO (SyncWorker_4) [googleapiclient.discovery] URL being requested: GET https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.light] Setting up light.group
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.garbage_collection
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.garbage_collection
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.garbage_collection
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.garbage_collection
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up samsungtv
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain samsungtv took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.updater
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 1.5 seconds
2021-02-10 11:07:04 INFO (SyncWorker_4) [googleapiclient.discovery] URL being requested: GET https://www.googleapis.com/calendar/v3/users/me/calendarList?alt=json
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain google took 0.9 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up calendar
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain calendar took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up upnp
2021-02-10 11:07:04 INFO (SyncWorker_2) [homeassistant.loader] Loaded notify from homeassistant.components.notify
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain upnp took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.calendar] Setting up calendar.google
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 1.6 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 1.6 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 1.6 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.2 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2021-02-10 11:07:04 INFO (SyncWorker_1) [homeassistant.loader] Loaded switch from homeassistant.components.switch
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.adguard
2021-02-10 11:07:04 INFO (SyncWorker_1) [googleapiclient.discovery] URL being requested: GET https://www.googleapis.com/discovery/v1/apis/calendar/v3/rest
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up switch
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain switch took 0.0 seconds
2021-02-10 11:07:04 DEBUG (MainThread) [custom_components.hacs] Configuration type: flow
2021-02-10 11:07:04 INFO (MainThread) [custom_components.hacs]
HACS (Home Assistant Community Store)
Version: 1.11.1
This is a custom integration
If you have any issues with this you need to open an issue here:
https://github.com/hacs/integration/issues
2021-02-10 11:07:04 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.WEBSOCKET
2021-02-10 11:07:04 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.FRONTEND
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.switch] Setting up switch.adguard
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up automation
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up notify
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 0.0 seconds
2021-02-10 11:07:04 INFO (SyncWorker_4) [homeassistant.loader] Loaded plex from homeassistant.components.plex
2021-02-10 11:07:04 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.CATEGORIES
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up device_tracker
2021-02-10 11:07:04 INFO (MainThread) [custom_components.hacs] HACS is enabled
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
2021-02-10 11:07:04 INFO (SyncWorker_1) [googleapiclient.discovery] URL being requested: GET https://www.googleapis.com/calendar/v3/calendars/ionuttimofte53%40gmail.com/events?orderBy=startTime&maxResults=5&singleEvents=true&timeMin=2021-02-10T11%3A07%3A04.662547%2B01%3A00&alt=json
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up cast
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain cast took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up script
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.calendar] Setting up calendar.garbage_collection
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain device_tracker took 0.1 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.device_tracker] Setting up device_tracker.mobile_app
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up media_player
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain media_player took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.cast
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Not adding entity AdGuard DNS Queries Blocked because it's disabled
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.3 seconds
2021-02-10 11:07:04 INFO (SyncWorker_2) [homeassistant.loader] Loaded weather from homeassistant.components.weather
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up weather
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up default_config
2021-02-10 11:07:04 INFO (SyncWorker_1) [homeassistant.loader] Loaded stream from homeassistant.components.stream
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.weather] Setting up weather.met
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.sensor] Not adding entity AdGuard Rules Count because it's disabled
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.updater] Submitted analytics to Home Assistant servers. Information submitted includes {}
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.weather] Not adding entity Home Hourly because it's disabled
2021-02-10 11:07:04 INFO (SyncWorker_0) [pychromecast] Querying device status
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setting up stream
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain stream took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.setup] Setup of domain default_config took 0.0 seconds
2021-02-10 11:07:04 INFO (MainThread) [homeassistant.components.switch] Not adding entity AdGuard Query Log because it's disabled
2021-02-10 11:07:05 DEBUG (MainThread) [custom_components.hacs] Can update 263 repositories
2021-02-10 11:07:05 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.HACS_REPO
2021-02-10 11:07:05 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> Checking repository.
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.light] Setting up light.tradfri
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.tradfri
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.switch] Setting up switch.tradfri
2021-02-10 11:07:05 INFO (SyncWorker_0) [homeassistant.loader] Loaded cover from homeassistant.components.cover
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.setup] Setting up cover
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.setup] Setup of domain cover took 0.0 seconds
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.tuya] Tuya discovery device poll interval set to 900 seconds
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.tuya] Tuya query device poll interval set to 120 seconds
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.cover] Setting up cover.tradfri
2021-02-10 11:07:05 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> Running checks against 1.11.1
2021-02-10 11:07:05 INFO (MainThread) [homeassistant.components.switch] Setting up switch.tuya
2021-02-10 11:07:06 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> All (0) checks passed
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] <Integration hacs/integration> Registration completed
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] Restore started
2021-02-10 11:07:06 DEBUG (MainThread) [queueman.manager] Checking out tasks to execute
2021-02-10 11:07:06 DEBUG (MainThread) [queueman.manager] Starting queue execution for 744 tasks
2021-02-10 11:07:06 DEBUG (MainThread) [queueman.manager] Queue execution finished for 744 tasks finished in 0.36 seconds
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] Restore done
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] Setup task HacsSetupTask.SENSOR
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] Stage changed: HacsStage.WAITING
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] Setup complete, waiting for Home Assistant before startup tasks starts
2021-02-10 11:07:06 INFO (MainThread) [custom_components.hacs] HACS is enabled
2021-02-10 11:07:06 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.hacs
2021-02-10 11:07:09 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.miioprotocol] Unable to discover a device at address <IP_ADDRESS>
2021-02-10 11:07:09 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.device] Unable to request properties [{'did': 'battery', 'siid': 2, 'piid': 1}, {'did': 'state', 'siid': 2, 'piid': 2}, {'did': 'error', 'siid': 3, 'piid': 1}, {'did': 'status', 'siid': 3, 'piid': 2}, {'did': 'brush_left_time', 'siid': 26, 'piid': 1}, {'did': 'brush_life_level', 'siid': 26, 'piid': 2}, {'did': 'filter_life_level', 'siid': 27, 'piid': 1}, {'did': 'filter_left_time', 'siid': 27, 'piid': 2}, {'did': 'brush_left_time2', 'siid': 28, 'piid': 1}, {'did': 'brush_life_level2', 'siid': 28, 'piid': 2}, {'did': 'operating_mode', 'siid': 18, 'piid': 1}, {'did': 'area', 'siid': 18, 'piid': 3}, {'did': 'timer', 'siid': 18, 'piid': 2}, {'did': 'fan_speed', 'siid': 18, 'piid': 6}]
2021-02-10 11:07:11 INFO (MainThread) [custom_components.hacs] Stage changed: HacsStage.STARTUP
2021-02-10 11:07:11 INFO (MainThread) [custom_components.hacs] setup task HacsSetupTask.CATEGORIES
2021-02-10 11:07:11 DEBUG (SyncWorker_7) [custom_components.hacs] Starting setup task: Extra stores
2021-02-10 11:07:11 DEBUG (SyncWorker_7) [custom_components.hacs] Enable category: HacsCategory.INTEGRATION
2021-02-10 11:07:11 DEBUG (SyncWorker_7) [custom_components.hacs] Enable category: HacsCategory.PLUGIN
2021-02-10 11:07:11 DEBUG (SyncWorker_7) [custom_components.hacs] Enable category: HacsCategory.THEME
2021-02-10 11:07:12 DEBUG (MainThread) [queueman.manager] The queue is empty
2021-02-10 11:07:12 DEBUG (MainThread) [custom_components.hacs] Did not store data for 'hacs.critical'. Content did not change
2021-02-10 11:07:12 INFO (MainThread) [custom_components.hacs] Loading known repositories
2021-02-10 11:07:12 DEBUG (MainThread) [custom_components.hacs] Got 93 elements for HacsCategory.REMOVED
2021-02-10 11:07:12 DEBUG (MainThread) [custom_components.hacs] Can update 263 repositories, items in queue 3
2021-02-10 11:07:12 DEBUG (MainThread) [queueman.manager] Checking out tasks to execute
2021-02-10 11:07:12 DEBUG (MainThread) [queueman.manager] Starting queue execution for 3 tasks
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Got 479 elements for HacsCategory.INTEGRATION
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Got 62 elements for HacsCategory.THEME
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Got 207 elements for HacsCategory.PLUGIN
2021-02-10 11:07:13 DEBUG (MainThread) [queueman.manager] Queue execution finished for 3 tasks finished in 0.48 seconds
2021-02-10 11:07:13 DEBUG (MainThread) [queueman.manager] 1 taks remaining in the queue
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Starting recurring background task for installed repositories
2021-02-10 11:07:13 DEBUG (MainThread) [queueman.manager] Checking out tasks to execute
2021-02-10 11:07:13 DEBUG (MainThread) [queueman.manager] Starting queue execution for 15 tasks
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Integration lukas-hetzenecker/home-assistant-remote> Checking repository.
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Integration hacs/integration> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin iantrich/config-template-card> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Integration bruxy70/Garbage-Collection> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin maykar/lovelace-swipe-navigation> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin thomasloven/lovelace-slider-entity-row> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin amaximus/garbage-collection-card> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin bramkragten/weather-card> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin kalkih/mini-graph-card> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin benct/lovelace-xiaomi-vacuum-card> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Theme basnijholt/lovelace-ios-dark-mode-theme> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin bratanon/lovelace-conditional-entity-row> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Plugin gadgetchnnel/lovelace-card-templater> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Integration Concentricc/xiaomi_vacuum> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] <Theme JuanMTech/google_dark_theme> Getting repository information
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update iantrich/config-template-card, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update hacs/integration, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update bruxy70/Garbage-Collection, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update bramkragten/weather-card, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update thomasloven/lovelace-slider-entity-row, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update amaximus/garbage-collection-card, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update JuanMTech/google_dark_theme, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update benct/lovelace-xiaomi-vacuum-card, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update Concentricc/xiaomi_vacuum, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update gadgetchnnel/lovelace-card-templater, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update maykar/lovelace-swipe-navigation, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update basnijholt/lovelace-ios-dark-mode-theme, content was not modified
2021-02-10 11:07:13 DEBUG (MainThread) [custom_components.hacs] Did not update kalkih/mini-graph-card, content was not modified
2021-02-10 11:07:14 WARNING (MainThread) [homeassistant.components.vacuum] Setup of vacuum platform xiaomi_vacuum is taking over 10 seconds.
2021-02-10 11:07:14 DEBUG (MainThread) [custom_components.hacs] Did not update bratanon/lovelace-conditional-entity-row, content was not modified
2021-02-10 11:07:14 DEBUG (MainThread) [custom_components.hacs] <Integration custom-components/remote_homeassistant> Running checks against 3.1
2021-02-10 11:07:14 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.miioprotocol] Unable to discover a device at address <IP_ADDRESS>
2021-02-10 11:07:14 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.device] Unable to request properties [{'did': 'last_clean', 'siid': 18, 'piid': 13}, {'did': 'total_clean_count', 'siid': 18, 'piid': 14}, {'did': 'total_area', 'siid': 18, 'piid': 15}, {'did': 'total_log_start', 'siid': 18, 'piid': 16}, {'did': 'button_led', 'siid': 18, 'piid': 17}, {'did': 'clean_success', 'siid': 18, 'piid': 18}, {'did': 'life_sieve', 'siid': 19, 'piid': 1}, {'did': 'life_brush_side', 'siid': 19, 'piid': 2}, {'did': 'life_brush_main', 'siid': 19, 'piid': 3}, {'did': 'dnd_enabled', 'siid': 20, 'piid': 1}, {'did': 'dnd_start_time', 'siid': 20, 'piid': 2}, {'did': 'dnd_stop_time', 'siid': 20, 'piid': 3}, {'did': 'map_view', 'siid': 23, 'piid': 1}, {'did': 'audio_volume', 'siid': 24, 'piid': 1}]
2021-02-10 11:07:14 DEBUG (MainThread) [custom_components.hacs] <Integration custom-components/remote_homeassistant> All (0) checks passed
2021-02-10 11:07:14 INFO (MainThread) [custom_components.hacs] <Integration custom-components/remote_homeassistant> Registration completed
2021-02-10 11:07:19 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.miioprotocol] Unable to discover a device at address <IP_ADDRESS>
2021-02-10 11:07:19 ERROR (SyncWorker_3) [custom_components.xiaomi_vacuum.miio.device] Unable to request properties [{'did': 'audio_language', 'siid': 24, 'piid': 3}, {'did': 'timezone', 'siid': 25, 'piid': 1}]
2021-02-10 11:07:19 ERROR (MainThread) [homeassistant.components.vacuum] xiaomi_vacuum: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 358, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 466, in async_device_update
await task
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/xiaomi_vacuum/vacuum.py", line 322, in update
state = self._vacuum.status()
File "/config/custom_components/xiaomi_vacuum/miio/dreamevacuum.py", line 260, in status
return self.get_properties_for_dataclass(DreameStatus)
File "/config/custom_components/xiaomi_vacuum/miio/miot_device.py", line 63, in get_properties_for_dataclass
response = {
File "/config/custom_components/xiaomi_vacuum/miio/miot_device.py", line 64, in
prop["did"]: prop["value"] if prop["code"] == 0 else None
TypeError: list indices must be integers or slices, not str
2021-02-10 11:07:19 DEBUG (MainThread) [queueman.manager] Queue execution finished for 15 tasks finished in 6.33 seconds
2021-02-10 11:07:19 DEBUG (MainThread) [custom_components.hacs] Did not store data for 'hacs.critical'. Content did not change
2021-02-10 11:07:19 DEBUG (MainThread) [custom_components.hacs] Saving data
2021-02-10 11:07:19 DEBUG (MainThread) [custom_components.hacs] Did not store data for 'hacs.hacs'. Content did not change
2021-02-10 11:07:19 DEBUG (MainThread) [queueman.manager] Checking out tasks to execute
2021-02-10 11:07:19 DEBUG (MainThread) [queueman.manager] Starting queue execution for 744 tasks
2021-02-10 11:07:20 DEBUG (MainThread) [queueman.manager] Queue execution finished for 744 tasks finished in 0.04 seconds
2021-02-10 11:07:20 DEBUG (MainThread) [custom_components.hacs] Recurring background task for installed repositories done
2021-02-10 11:07:20 DEBUG (MainThread) [custom_components.hacs] Nothing in the queue
2021-02-10 11:07:20 INFO (MainThread) [custom_components.hacs] Stage changed: HacsStage.RUNNING
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 18.30s
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.core] Starting Home Assistant
2021-02-10 11:07:20 INFO (SyncWorker_8) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.core] Timer:starting
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.new_automation] Initialized trigger Notify Ionut that Laura is home
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.notify_laura_that_ionut_is_home] Initialized trigger Notify Laura that Ionut is Home
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.new_automation_2] Initialized trigger Shopping Memento Laura
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.leaving_home_laura] Initialized trigger Leaving home Laura
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.leaving_home_ionut] Initialized trigger Leaving home Ionut
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.new_automation_4] Initialized trigger test trash
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.shopping_memento_ionut] Initialized trigger Shopping memento Ionut
2021-02-10 11:07:20 INFO (MainThread) [homeassistant.components.automation.blueprint_mimi_test] Initialized trigger Mimi Schedule
2021-02-10 11:07:20 INFO (SyncWorker_1) [homeassistant.loader] Loaded xiaomi_aqara from homeassistant.components.xiaomi_aqara
2021-02-10 11:07:20 INFO (SyncWorker_5) [homeassistant.loader] Loaded xiaomi_miio from homeassistant.components.xiaomi_miio
2021-02-10 11:07:20 INFO (SyncWorker_0) [homeassistant.loader] Loaded discovery from homeassistant.components.discovery

my issue dissappeared after removing my wifi range extenders. i'm suspecting the robot was using extended wifi ( cloned wifi, but still same ip ). cant be sure its that, but for the moment it is stable.


Think about how to store metadata

For some devices there may be metadata that is required alongside the device for later storage. e.g. the material the device is made of. It probably makes sense for dodal to have this data for applications to access but the way it's stored etc. is TBD
Acceptance Criteria

A meeting is had to discuss the best way of storing this data
The decision, and reasoning is documented in dodal with an example

this might be related https://github.com/DiamondLightSource/blueapi/issues/537


Gate: Don't update Business Partners without change

Currently, when business partner data for a given stage and external id should be upserted we should validate whether the business partner data really is different from the existing data in the database. Only when there is a change we should create change log entry. Likewise, only when business partner input is changed the Gate starts a golden record process.
Tasks

[ ] Create validation logic comparing incoming business partner stage data with existing stage data
[ ] Only create changelog on changed data
[ ] Only create golden record tasks for changed data

When an input is made, it should be validated if it already exists in the persistence to avoid always triggering the clean flow among all components.
Key Point:
What happens when a taskId from the Orchestrator is returned to the Gate and for some reason, the Orchestrator loses context? We won't have our data cleaned, but the persistence of the Input will remain the same as initially and won't trigger new requests that come in identically.
Recommendation:
Implementing a validation mechanism to check the input's existence in the persistence layer before proceeding could mitigate such issues and ensure the system handles new and identical requests efficiently.

When an input is made, it should be validated if it already exists in the persistence to avoid always triggering the clean flow among all components.
Key Point: What happens when a taskId from the Orchestrator is returned to the Gate and for some reason, the Orchestrator loses context? We won't have our data cleaned, but the persistence of the Input will remain the same as initially and won't trigger new requests that come in identically.
Recommendation: Implementing a validation mechanism to check the input's existence in the persistence layer before proceeding could mitigate such issues and ensure the system handles new and identical requests efficiently.

The solution would be to the check the sharing state of the business partner whose data is being upserted. If the sharing state is in error a golden record task should be created regardless the input data is the same or not. If it is in Pending or in Success it should not be updated if the data is equal.


fix: Assignment of the Capacity Reservation id to an instance

Description
When trying to call the module with the specification of a Capacity Reservation ID, the module ends up with the following error:
╷
│ Error: Invalid function argument
│
│ on .terraform/modules/terraform-aws-ec2-instance/main.tf line 45, in resource "aws_instance" "this":
│ 45: capacity_reservation_id = lookup(capacity_reservation_target.value, "capacity_reservation_id", null)
│ ├────────────────
│ │ capacity_reservation_target.value is "cr-xxxxxxxx"
│
│ Invalid value for "inputMap" parameter: lookup() requires a map as the
│ first argument.
╵
As per line 45 analysis, it looks like the bug is in the following statement:
capacity_reservation_id = lookup(capacity_reservation_target, "capacity_reservation_id", null)
it should rather be as follows:
capacity_reservation_id = lookup(capacity_reservation_specification.value.capacity_reservation_target, "capacity_reservation_id", null)
In this case, terraform should lookup in the capacity reservation target map (since it is the iterator in the for_each) rather than in its value for the mapping of the attribute capacity reservation id
Motivation and Context

Fixes #277 and #281
Breaking Changes

No breaking changes, just fixing a typo in line 45 in the main.tf
How Has This Been Tested?

[X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X] I have tested and validated these changes using one or more of the provided examples/* projects

[X] I have executed pre-commit run -a on my pull request

@bryantbiggs : Hello Bryant, I noticed that my logic on the previous PR on the same topic was wrong.
In this PR I have revisited this statement in the main.tf:
capacity_reservation_id = lookup(capacity_reservation_specification.value.capacity_reservation_target, "capacity_reservation_id", null)
I also tested thoroughly using the complete example and this is now satisfactory.
Sorry again for the double review work.
Enjoy your weekend !

Hello @bryantbiggs,
kind reminder for this PR which is ready for review.
Thanks again for your feedback.
Bests.

Hello @bryantbiggs
Thanks for your valuable feedback that I have taken into account.
I have added the example for the targeted capacity reservation together with the simplification of the capacity reservation assignment. it's more readable with try function.
I have also deployed to test and well went through.
Looking forward for the merge if all is okay for you.
Thanks a ton !
Bests.

Hello @bryantbiggs
Would it be possible to review the changes I made upon your feedback ?
Thanks again.
Bests.

This PR is included in version 4.1.2 :tada:

Should the default value of capacity_reservation_specification be updated from null to {} ?

@yewton good spot - yes, looks like we need to update the variable as well. PRs are welcomed!

I will create a new PR to fix it.
Thanks for spotting it !

Thank you!


User Experience: usability test

Added documentation for user experience: usability testing
The documentation includes a brief intro, the importance of usability testing, how it's done (including method and data collection), and some misconception about usability testing.

Looks good to me. I think you are good to merge now.


Mas12517/3 d attribute sample

Sample
3D Attribute and Hit Test Samples
Summary
Add 3D Attribute and Hit Test Samples to Public Samples Repo (Still in Plugin)
Tests
Windows
ArcGIS Maps SDK Version
UE 5.0.3 W/ Maps SDK 1.3

Should update the TOC in the main readme

3D Attribute:
-Select attribute toolbar does not show currently selected attribute
-API key needs to be set in APIMapCreator, this could be more straightforward
-Doesn't work from SampleViewer by default.
Hit test:

No requested changes


Remove N/A Values for MA at state level

Description
MA seems to always give N/A values on Tuesdays, we remove these rows from the dataframe. See #1360 for more details.
In particular, we apply the following filter to HHS:

Only for confirmed_admissions_influenza_1d (including prop / 7dav variants)
Dates after 1 August, 2021
Value is N/A
Geo_type is state, geo_id is "ma"

Changelog
Itemize code/test/documentation changes and files added/removed.

run.py for delphi_hhs

@nmdefries @krivard Just thought of something: Maybe we should try to convert this error to a warning - but IIRC there's no way to do that right now for a particular combination of geo-sig-errortype (we only have the suppressed_error framework).
Should we try to add that in? Or are we OK with just removing NAs for this particular filter for now?
I'm also not too sure why having NA values is 'bad': I presume we want this for some sort of consistency, but I don't know if it messes with something by feeding in null values. The way I see it is:

Validator reports error, and leaves it in (current method with dry-run)
Validator reports error, prevents API ingestion (kinda bad given that there's NA data every week, would happen if dry-run was turned off)
Delphi_hhs removes rows, no error (This PR)
3a. Adding in a warning when rows are removed? Currently I removed rows under delphi_hhs.run, so the warning wouldn't show up in validator logs
3b. We can also impute 0s for this particular filter, and give a warning.

Just checking! I know we originally decided not to impute 0s in general, but I don't know if we would want to do it if the scope was narrowed down as such.

The NAs here are malformed data from the source dataset, and filtering them out (& not imputing them to zero) is part of the normal expected processing done by this indicator. An ongoing warning is not needed.


Auto Gen workflow

I've added an auto gen workflow outlining how to use the auto gen certificates

https://github.com/confluentinc/confluent-kubernetes-examples/pull/43 new pull


Don't bind key services to key path units

Removes binding from key service to key paths as per #116

I'm going to close this because upon testing it on my own configurations, I don't think this is the issue.
I'm not convinced the systemd path units are even working as anticipated for some reason and I don't know why.


Change a test setup requirement assertion to a skip.

High-level description
Encountered this when I was playing with integration tests.
>       assert len(dcos_api_session.slaves) >= 2, "Test requires a minimum of two agents"
E       AssertionError: Test requires a minimum of two agents
E       assert 1 >= 2
E        +  where 1 = len(['<IP_ADDRESS>'])
E        +    where ['<IP_ADDRESS>'] = <dcos_test_utils.enterprise.EnterpriseApiSession object at 0x7fa73c858128>.slaves

open_source_tests/test_service_discovery.py:72: AssertionError

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review


api: gpio: Clean up GPIO dt-bindings flags

This PR attempts to resolve the concerns and discussions of issue #10339 and is based on work in #11880 by @pabigot.
The main differences to #11880 are as follows:

multi-bit flags are defined using following standard pattern

#define GPIO_MULTI_BIT_FIELD             (N << GPIO_MULTI_BIT_FIELD_SHIFT)

where 'N' is the value/state we want to encode.

no _SHIFT and _MASK macros for single bit flags.
GPIO_POL_ flags are deprecated as their function overlaps with the new GPIO_ACTIVE_LOW, GPIO_ACTIVE_HIGH flags.
the documentation of gpio_pin_read(), gpio_pin_write() functions was updated to clarify usage of the new GPIO_ACTIVE_ flags.

The following design goals were applied:

only issues discussed in #10339 are addressed. Otherwise the changes are kept to minimum. Especially this PR does not attempt to align the API with the future pinctrl API (e.g. #6760).
to be able to keep DTS of GPIO nodes close to the Linux's dt-bindings gpio.h
Linux implementation is followed.

One extra point which we likely should revisit are issues raised by @DWagenk. Current implementation of pin read/write and interrupt API is not consistent.
I have not yet verified that generated documentation is formatted correctly.
Fixes #10339

Superseded by #16648.


[Breaking change]: Validate CompressionLevel for BrotliStream

Description
The change validates that the CompressionLevel argument of the System.IO.Compression.BrotliStream constructors is a defined value of the enum: Optimal, Fastest, NoCompression or SmallestSize.
Previously any underlying value from 0 to 11 would be valid and passed on as the level to Brotli, unless it's mapped to any of the CompressionLevel enum values.
Version
.NET 7 Preview 1
Previous behavior
Passing any value between 0 and 11 to the CompressionLevel parameter BrotliStream would be valid.
The value would either map to the one of the enum's defined values or passed as is to the underlying Brotli implementation.
New behavior
Only Optimal, Fastest, NoCompression or SmallestSize are valid values for the CompressionLevel parameter.
Type of breaking change

[X] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
[X] Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change
Being able to pass arbitrary values which are not defined by the CompressionLevel enum is unexpected and undocumented with a probability for mistakes.
Recommended action
Pass in only one of the valid values for CompressionLevel
Feature area
Core .NET libraries
Affected APIs
All System.IO.Compression.BrotliStream constructors that accept CompressionLevel

Thank you @i3arnon for adding the breaking change doc!
The linked PR https://github.com/dotnet/runtime/pull/57561 will hopefully be merged this week. I edited the "Version" section of the description to indicate it would go to Preview 1.