Can't login - 'Error': 'BadAuthentication'

hi,
I cant login with my google account.
is the google username the same as your google account<EMAIL_ADDRESS>

Yes it is, Username/Email should be<EMAIL_ADDRESS>and password should be your google password. It is though highly recommend to use an app password instead.
If you have Two Factor Authentication enabled. I think you can only use an app password. Link to app password guide

Ik still cant login

Can you please check the logs in Home Assistant. You can find them under Configuration and then logs. Please choose Load Full Home Assistant Logs. And past them here using.

@hugostegeman if you are using a Gmail account, try logging it without adding @gmail.com, maybe that should do the trick.
Also, as @DurgNomis-drol pointed out, if you are using 2FA authentication, generate an app password.

I tried it with and without @gmail.com but i still cant login.
2FA authentication also does not work.
my log looks like this:
2021-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] You are using a custom integration 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-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] You are using a custom integration sonoff 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-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] You are using a custom integration google_home 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-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] You are using a custom integration googlehome 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-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'googlehome'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'googlehome'
2021-03-19 13:40:29 ERROR (Recorder) [homeassistant.components.recorder.util] The database at //config/home-assistant_v2.db is corrupt or malformed.
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 168, in validate_sqlite_database
run_checks_on_open_db(dbpath, conn.cursor(), db_integrity_check)
File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 179, in run_checks_on_open_db
sanity_check_passed = basic_sanity_check(cursor)
File "/usr/src/homeassistant/homeassistant/components/recorder/util.py", line 157, in basic_sanity_check
cursor.execute(f"SELECT * FROM {table} LIMIT 1;") # nosec # not injection
sqlite3.OperationalError: no such table: states
2021-03-19 13:40:29 ERROR (Recorder) [homeassistant.components.recorder.util] The system will rename the corrupt database file //config/home-assistant_v2.db to //config/home-assistant_v2.db.corrupt.2021-03-19T12:40:29.350868+00:00 in order to allow startup to proceed
2021-03-19 13:40:29 WARNING (MainThread) [homeassistant.components.http] The 'base_url' option is deprecated, please remove it from your configuration
2021-03-19 13:40:33 WARNING (MainThread) [homeassistant.loader] You are using a custom integration afvalbeheer 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-03-19 13:40:33 ERROR (SyncWorker_5) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:41 WARNING (MainThread) [homeassistant.loader] You are using a custom integration saver 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-03-19 13:40:41 WARNING (MainThread) [homeassistant.loader] You are using a custom integration nodered 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-03-19 13:40:45 ERROR (MainThread) [homeassistant.components.wled] Error fetching wled data: Invalid response from API: Error occurred while communicating with WLED device at <IP_ADDRESS>
2021-03-19 13:40:45 WARNING (MainThread) [homeassistant.config_entries] Config entry 'mengpaneel' for wled integration not ready yet. Retrying in background
2021-03-19 13:40:49 ERROR (SyncWorker_0) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_5) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_4) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_2) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_7) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_0) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_3) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_10) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_2) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_6) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'
2021-03-19 13:40:49 ERROR (SyncWorker_0) [pymodbus.client.sync] [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0'

Which version of Home Assistant are you using?
Please try to remove it and reinstalled it again. It seems there is an issue with its name here:
2021-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] You are using a custom integration googlehome 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-03-19 13:40:28 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'googlehome'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'googlehome' <- Problem here. Is name should be google_home.

Also please use code blocks when embedding logs. Markdown Guide

@hugostegeman The integration is not name googlehome, but google_home. The underscore is important. Are you installing it through HACS? If so please uninstall it and then remove the repository in HACS and re-add it and try installing it again.

I installed it by using hacs and even after removing en reinstalling i cant login.
Can it have something to do with the country rules from google or something im from NL?
maybe manuel install of the intergration can help?

I don't think it matters which country you are in as long as the Google sells it devices in that country it should be supported.
You can try, but i doubt it will change any thing as installing through HACS always gives you the latest version.
Can you please try adding this to your configuration.yaml file:
logger:
  default: info
  logs:
    # log level for mielelogic_laundry
     custom_components.google_home: debug

And the post back the logs.
This will enabled a lot more information in the logs and will give os a clearer understanding of why it does not work.

Hi,
Same problem.
Already try with
as login: user_name, full email
as password: app token, master token, password to account
Logger set to:
logger:
default: debug
logs:
# log level for mielelogic_laundry
custom_components.google_home: debug
In logs only:
2021-03-20 19:09:44 ERROR (SyncWorker_16) [glocaltokens.client] [!] Could not get master token.
2021-03-20 19:09:44 ERROR (MainThread) [custom_components.google_home]

@WRLPDZ
When have you installed this integration?
Can you also add:
logger:
  default: info
  logs:
     custom_components.google_home: debug
     glocaltokens: debug <- Add this line

This will enable logs for the underlaying package glocaltokens.

Still the same. Debug level changed.
2021-03-21 14:33:10 ERROR (SyncWorker_48) [glocaltokens.client] [!] Could not get master token.
2021-03-21 14:33:10 ERROR (MainThread) [custom_components.google_home]

@ArnyminerZ @leikoilja Any ideas on what could cause this? Besides not using the latest version, where it should have been fixed?
I think we would need more information to know exactly why this is happening, if this problem have indeed risen again 🤔

Core
Version
core-2021.3.4
Supervisor
Version
supervisor-2021.03.6
logger:   default: debug   logs:     custom_components.google_home: debug     glocaltokens: debug
Nothing more is showing in logs:
2021-03-21 15:22:35 ERROR (SyncWorker_40) [glocaltokens.client] [!] Could not get master token.
2021-03-21 15:22:35 ERROR (MainThread) [custom_components.google_home]
I'm trying to use this because Drakulix/googlehome not showing me correct values but it's connected.

@WRLPDZ Can you please remove Drakulix/googlehome's integration and restart just to make sure that it is not effecting this integration. It is important that you remove both the files and how it was installed, if in configuration.yaml then remove it from here, or if via config flow, remove it from there before deleting the files. 😄

All integrations corelated wit google home uninstalled.
Host restarted. Browser cache cleared.
ha-google-home installed again. Result the same.
For now I will pass.

I'm pretty sure there's an issue with @hugostegeman Home Assistant's database, and maybe that's the issue, but since @WRLPDZ has the same issue, maybe there's something more there...
Also, @WRLPDZ are you sure there aren't any more logs regarding the integration in your Home Assistant's register?
@DurgNomis-drol @leikoilja maybe we should add more debugging to glocaltokens just in case something like this happens. At debug level, so it doesn't bother normally, but more info should be provided. Will open an issue there and work on it ASAP. Then we may update ha-google-home's dependency version, and take further look.

Great call, @ArnyminerZ, thank you! 💥

I have the same issue. Just installed this via HACS, but can't log in. In log I only see:
2021-03-22 10:48:13 ERROR (SyncWorker_1) [glocaltokens.client] [!] Could not get master token. 2021-03-22 10:48:13 ERROR (MainThread) [custom_components.google_home]

Hi, @cs42, thank you for the information. We are currently working on this issue, you can follow the progress at glocaltokens#48.
Also, please, use code blocks for logs, not blockquotes. 😇

@cs42, @bacco007, there is now a new release of the integration.
Please upgrade to 1.0.1 using HACS.
Also make sure you have the logger enabled in your configuration.yaml:
logger:
  default: info
  logs:
    custom_components.google_home: debug

That will now print much more elaborate logs. Please post them here (IMPORTANT make sure not to paste your sensitive info here as master_token or login). These elaborate logs (paste as code block) will help us get a better understanding why you are not able to login

Here are the logs:
2021-03-25 11:14:35 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2021-03-25 11:14:35 DEBUG (MainThread) [glocaltokens.client] Set self username to "c******************", password to "f***************", master_token to "" and android_id to
2021-03-25 11:14:35 DEBUG (MainThread) [glocaltokens.client] Set self access_token, homegraph, access_token_date and homegraph_date to None
2021-03-25 11:14:35 DEBUG (SyncWorker_20) [glocaltokens.client] There is not any stored master_token, logging in...
2021-03-25 11:14:35 DEBUG (SyncWorker_20) [glocaltokens.client] There is not any stored android_id, generating a new one
2021-03-25 11:14:35 DEBUG (SyncWorker_20) [glocaltokens.client] Generating mac...
2021-03-25 11:14:35 DEBUG (SyncWorker_20) [glocaltokens.client] Generated mac: 525CFDC290AA48
2021-03-25 11:14:36 ERROR (SyncWorker_20) [glocaltokens.client] [!] Could not get master token.
2021-03-25 11:14:36 DEBUG (SyncWorker_20) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}

I have a 2FA setup and created a new app password for this test.

I was watching this because I was experiencing the very same issue. I have a 2FA and I can't login with my username and the generated app password.
I just updated to 1.0.1, add the logger to the config and now I can login and I can't understand why.
If I can provide any more info or if you need any tests at all feel free to ask and I'll be glad to help

Here's my 1.01 log to add to the fire. ;)  I am trying to login using an app password
2021-03-25 08:42:35 WARNING (MainThread) [homeassistant.loader] You are using a custom integration google_home 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-03-25 08:42:35 INFO (SyncWorker_19) [homeassistant.util.package] Attempting install of glocaltokens==0.2.6
2021-03-25 08:43:15 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2021-03-25 08:43:15 DEBUG (MainThread) [glocaltokens.client] Set self username to "b******************", password to "g***************", master_token to "" and android_id to
2021-03-25 08:43:15 DEBUG (MainThread) [glocaltokens.client] Set self access_token, homegraph, access_token_date and homegraph_date to None
2021-03-25 08:43:15 DEBUG (SyncWorker_25) [glocaltokens.client] There is not any stored master_token, logging in...
2021-03-25 08:43:15 DEBUG (SyncWorker_25) [glocaltokens.client] There is not any stored android_id, generating a new one
2021-03-25 08:43:15 DEBUG (SyncWorker_25) [glocaltokens.client] Generating mac...
2021-03-25 08:43:15 DEBUG (SyncWorker_25) [glocaltokens.client] Generated mac: E0400A08AB5949
2021-03-25 08:43:15 ERROR (SyncWorker_25) [glocaltokens.client] [!] Could not get master token.
2021-03-25 08:43:15 DEBUG (SyncWorker_25) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2021-03-25 08:43:15 ERROR (MainThread) [custom_components.google_home]

For good measure I also deleted yesterday's app password, and generated a new one.
2021-03-25 08:50:14 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2021-03-25 08:50:14 DEBUG (MainThread) [glocaltokens.client] Set self username to "b******************", password to "n***************", master_token to "" and android_id to
2021-03-25 08:50:14 DEBUG (MainThread) [glocaltokens.client] Set self access_token, homegraph, access_token_date and homegraph_date to None
2021-03-25 08:50:14 DEBUG (SyncWorker_17) [glocaltokens.client] There is not any stored master_token, logging in...
2021-03-25 08:50:14 DEBUG (SyncWorker_17) [glocaltokens.client] There is not any stored android_id, generating a new one
2021-03-25 08:50:14 DEBUG (SyncWorker_17) [glocaltokens.client] Generating mac...
2021-03-25 08:50:14 DEBUG (SyncWorker_17) [glocaltokens.client] Generated mac: 33FF090A894B45
2021-03-25 08:50:14 ERROR (SyncWorker_17) [glocaltokens.client] [!] Could not get master token.
2021-03-25 08:50:14 DEBUG (SyncWorker_17) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2021-03-25 08:50:14 ERROR (MainThread) [custom_components.google_home]

Related logging tips:

To get colored coded output like mine, start your log output block with  ```python (instead of just ```).
Install LogExpert, open homeassistant.log in your config folder, then use glocaltokens|google_home as your Text filter to include logs from both glocaltokens and google_home.

I'm having the same issue

Hey guys, can we try something out?
I actually think it has nothing to do with google accounts themself but with the dependency libraries used. We have seen BadAuthentication before on some versions of requests library that are used under the hood. It might be that some other integrations or packages that you use in parallel with Google Home are enforcing different (lower) version of the requests library.
@DurgNomis-drol, I know you are more expert in that field. What was the good way to see the version of requests installed in the HA setup? 🤔  😅

You can check which version you have installed by running pIp show package_name in the command line in the docker container of HA.
The important packages is requests,urllib3,chardet and gpsoauth. The problem is caused by a bug on the Google servers in how urllib3 have implemented SNI support. It should have been solved, but as @leikoilja states, if some other things are forcing a wrong version, this bug will show up.

Can someone please who encounters BadAuthentication post here the output of (please see @DurgNomis-drol message on how to get to the docker container where to run this command):
bash-5.0# pip freeze | grep 'requests\|glocaltokens\|urllib3\|chardet\|gpsoauth'
cchardet==2.1.7
chardet==3.0.4
glocaltokens==0.2.6
gpsoauth==0.4.3
requests==2.25.1
requests-file==1.5.1
requests-futures==1.0.0
requests-oauth==0.4.1
requests-oauthlib==1.3.0
requests-toolbelt==0.9.1
urllib3==1.26.3

(that's example of mine)

here's my output
pip freeze | grep 'requests\|glocaltokens\|urllib3\|chardet\|gpsoauth'
chardet==3.0.4
glocaltokens==0.2.6
gpsoauth==0.4.3
requests==2.25.1
requests-oauthlib==1.3.0
requests-toolbelt==0.9.1
urllib3==1.25.10

@cs42
Can you please try upgrading urllib3 to the same versions as @leikoilja. By running pip install urllib3==1.26.3 and try to login again. Remember to restart. 😁

I just did :-D, but it didn't help :-(
Same problem as before
2021-03-26 08:34:15 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2021-03-26 08:34:15 DEBUG (MainThread) [glocaltokens.client] Set self username to "c******************", password to "u***************", master_token to "" and android_id to
2021-03-26 08:34:15 DEBUG (MainThread) [glocaltokens.client] Set self access_token, homegraph, access_token_date and homegraph_date to None
2021-03-26 08:34:15 DEBUG (SyncWorker_24) [glocaltokens.client] There is not any stored master_token, logging in...
2021-03-26 08:34:15 DEBUG (SyncWorker_24) [glocaltokens.client] There is not any stored android_id, generating a new one
2021-03-26 08:34:15 DEBUG (SyncWorker_24) [glocaltokens.client] Generating mac...
2021-03-26 08:34:15 DEBUG (SyncWorker_24) [glocaltokens.client] Generated mac: 9DE38201B51C4C
2021-03-26 08:34:15 ERROR (SyncWorker_24) [glocaltokens.client] [!] Could not get master token.
2021-03-26 08:34:15 DEBUG (SyncWorker_24) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2021-03-26 08:34:15 ERROR (MainThread) [custom_components.google_home]

Packages are now (oh, I just see it's urllib 1.26.4 - latest one):
pip freeze | grep 'requests\|glocaltokens\|urllib3\|chardet\|gpsoauth'
chardet==3.0.4
glocaltokens==0.2.6
gpsoauth==0.4.3
requests==2.25.1
requests-oauthlib==1.3.0
requests-toolbelt==0.9.1
urllib3==1.26.4

Nope, doesn't work with urllib3==1.26.3 as well.

Ik still cant login

I'm getting the same issue.
In the logs:
Logger: custom_components.google_home Source: custom_components/google_home/config_flow.py:97 Integration: Google Home (documentation, issues) First occurred: 16:57:03 (4 occurrences) Last logged: 16:59:42

When I run a script on Home-Assistant's python to get the master token, it works. Not sure what is happening to cause it to generate the issue with urllib3 all the versions are correct of gpsoauth and urllib3

Uhhh, there is some deep-buried issue here that we need to solve. The worst thing is that we can't replicate it yet, cause for some of us it works as expected, for others - we see a bad authentication error.
I don't have many good ideas on how to solve it yet, but here are some thoughts...
Can someone with the issue help replicate it in the isolation? We need to get the same error in isolation (let's say using Raspberry Pi 3/4) with minimum configurations (preferably clean setup with only Google Home integration installed) and get to the point where the same issue occurs? Then posting here as much configs as possible (HA version, pip packages and dependencies versions), so I could try replicating it locally following the exact same setup/versions you would have.

I know its not optimal but is there a way to support adding the master token or the account credentials, i'm not sure how long the master token is good for vs the the account credentials, might be a work around option.

Master token is very very long lived. A couple of years or so. If not more.

I'm pretty sure master token is meant to be "forever" lived. But that is a good idea, @stboch. Thank you 💥
Our underlying dependency glocaltokens supports receiving master_token alone, so we should be able to add that feature relatively effortlessly.
I was thinking we should spend some effort making a better config flow where one can edit the existing config and during initial setup allow users options like 'username', 'password' as well as 'master_token` and 'android_id' specifications.
What do you guys think, @KapJI, @DurgNomis-drol, @ArnyminerZ?

If 2FA is not used, you need to enable "Less secure apps" as well: https://github.com/rithvikvibhu/GHLocalApi/issues/54#issuecomment-674654337
Also can you guys try to use this gist directly? Are you still getting the same error? Can you try to downgrade requests and gpsoauth libs?
Regarding making the component more configurable, it's a good idea as well. Especially if it helps someone.

@KapJI that's is basically the script I ran on the underlying ha container, and it ran fine with all the python packages provided, not sure why when just asynchronously via home-assistant itself it fails.

Any news update? I have the same problem

@stboch what if you go the step further and try to use glocaltokens library?
Something like this: https://github.com/leikoilja/glocaltokens/blob/master/example/get_tokens.py

@KapJI sorry should have looked closer I used the glocaltokens implementation of get_tokens.py not the other googleapi one.
but yes it worked no issues was very odd. Not much debugging done in gpsoauth to see if HA is calling something different about urllib3 as part of the environment...

I have been trying to look around and the topic of Bad Authentication has been there for many people in a very random order (see 1, 2, 3).
@cs42, can you please try downgrading requests library by running pip install requests==2.23.0? Please don't forget to restart after and show us pip freeze | grep 'requests\|glocaltokens\|urllib3\|chardet\|gpsoauth' after the restart.

This still doesn't work.
$ pip freeze | grep 'requests\|glocaltokens\|urllib3\|chardet\|gpsoauth'
chardet==3.0.4
glocaltokens==0.2.6
gpsoauth==0.4.3
requests==2.23.0
requests-oauthlib==1.3.0
requests-toolbelt==0.9.1
urllib3==1.25.11

@leikoilja If we can implement it in a way that you need to push a button or so to enable advanced login, then i think it is a good work around for now until we can get to the bottom of this. 😄
As @leikoilja said somewhere. We need to find a way to replicate it locally and repeatably before we can find a solution.
My best guess is that it occurs in the gpsoauth package and that we should isolate it there and do some tests. It could have something to do with how we generate an android id/mac address. We need to spend sometime understand that we generate something that is valid. I read inside-android-play-services-magic. It describes how we actually authenticate with Google. I believe that there need to be something speciel in the android id/mac address for it to work. But i am not an expert on this at all. But this could possibly be explanation for why it occur at random. If some one with better knowledge of this have any idea, please correct me if there is something that I don't known.

I agree, we probs need to remedy the issue rn by introducing master_token field in config_flow as a workaround until we can replicate and solve the issue at hand.
@DurgNomis-drol, i had an idea that android id might be the issue and I have locally tried to use one of the android id mentioned above as BadAuthentication with no results. I was still able to authenticate and it all worked fine for me.

@leikoilja Dammit, i though i got closer to understanding it 😞 If we can get everyone having this issue to try and fetch it directly from gpsoauth or maybe even glocaltokens to see if it is, as @stboch mentions, a problem with HA.

@stboch, can you please try something out for me?

Login into ssh of your HA instance. Here are some instructions how to ssh to your device if you are using Home Assistant Operating System.
Get into the docker container docker exec -it homeassistant /bin/bash
Get into python shell by running python
Import glocaltokens
Create client using the test credentials i have just created (see the snippet below)
Get master token

>>> from glocaltokens.client import GLocalAuthenticationTokens
>>> client =<EMAIL_ADDRESS>password='htbdkrqaxicayofs', verbose=True, android_id='9DE38201B51C4C')
>>> client.get_master_token()

See if you will get a master_token.
7. Make sure your have google_home logs set to debug on your HA
8. Try using the same test credentials in HA when adding Google Home as an integration. Check logs, it should print you  the master_token when the config is created.
Please let me know how it goes and if it would still fail for you.
I have tested all those steps on my setup and it all has worked as expected.

Ok tested what you asked above, Got the master token when using the  local SSH method (same thing I was doing before) there it worked, and in the UI failed.
Got my dev system rebuilt, only Terminal/SSH and HACS, installed google_home and restarted, after the boot logged in and it worked... gonna try and work backwards install some of the same custom_intergrations I have on my production instance and see if I can tell what might be conflicting or breaking...

Also my production instance has been an upgraded instance for a long while... at least 1 1/2 yr since last rebuild so who knows what cobwebs are hiding...

Thanks, @stboch for trying it out. As you say the issue is most likely cause by some other conflicting custom integration or specific HA configuration/settings. Please keep us posted with your finding, those can be helpful for many :)

@cs42 Are you also using YouTube Music Player component with your environment?

I found it! @cs42 @nckslater do either of you use LG SmartThinq custom Component? it looks like it lowers the SSL ciphers level
requests.packages.urllib3.util.ssl_.DEFAULT_CIPHERS += "HIGH:!DH:!aNULL"
I added this to the file to test...
import ssl
import requests
from urllib3.poolmanager import PoolManager
from requests.adapters import HTTPAdapter
from urllib.parse import urljoin, urlencode, urlparse, parse_qs

requests.packages.urllib3.disable_warnings()
# requests.packages.urllib3.util.ssl_.DEFAULT_CIPHERS += "HIGH:!DH:!aNULL"

Toggle the line to test, anyone know what the supported ciphers are supposed to be? can add a fix by changing them before the client call I think. going to test.

Default is 'ECDHE+AESGCM:ECDHE+CHACHA20:DHE+AESGCM:DHE+CHACHA20:ECDH+AESGCM:DH+AESGCM:ECDH+AES:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!eNULL:!MD5:!DSS'

I tried installing it in a clean dev environment and it worked (no device was created, but the dev environment is in another subnet, so I guess this is expected).
I then tried to reinstall the glocaltokens library in the Docker container on the Raspberry (Pi 4) running Home Assistant OS, with: docker exec -it homeassistant pip3 install glocaltokens==0.2.7
Then I've got this error:

@notherealmarco it's not related to this issue. Your Docker container doesn't have build-essential package which is required to build grpc. Please open a separate issue for this.

Anyone who is having this issue and wasn't running the LG custom components.  can you grep for "DEFAULT_CIPHERS" in your custom_components directory to see if there are any third party components causing the issue. If it find nothing and your able to get to your docker HA Container try this...
grep -R "DEFAULT_CIPHERS" /usr/local/lib/python3.8/site-packages

I found it! @cs42 @nckslater do either of you use LG SmartThinq custom Component? it looks like it lowers the SSL ciphers level

Yes, I'm using the LG custom component.

@leikoilja do we have this patch in gpsoauth?
https://github.com/simon-weber/gpsoauth/pull/25/files

@cs42 custom_components/smartthinq_sensors/wideq/core_v2.py delete lines 115-125, not sure why they are changing the supported ciphers as it doesn't seem to cause any problems with LG... I will send a Issue and PR for them.

Me too 👍On 29 Mar 2021 21:07, Carsten @.***> wrote:
I found it! @cs42 @nckslater do either of you use LG SmartThinq custom Component? it looks like it lowers the SSL ciphers level
Yes, I'm using the LG custom component.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

@cs42 custom_components/smartthinq_sensors/wideq/core_v2.py delete lines 115-125, not sure why they are changing the supported ciphers as it doesn't seem to cause any problems with LG... I will send a Issue and PR for them.

With this change it finally works! I could even use my email as username, as I would expect for a google account.

Actually I think we shoul rather make gpsoauth more bulletproof. It probably should set ciphers explicitly without relying on DEFAULT_CIPHERS.

Thank you @stboch for finding what causes this! Appreciate that a lot 🎉

@stboch, awesome job for finding where the issue was buried 💥 🔥
@KapJI, we seem to have the gpsoauth patch enabled that you are referring to. It came out in gpsoauth==0.4.3, which is what we are using.
Let's keep the issue open for tracking purpose for the time being and once the [LG custom component]`(https://github.com/ollo69/ha-smartthinq-sensors/issues/139) stboch's issue is resolved we can close it

@Edo78 v2.4.1 AlexxIT / SonoffLAN

same here so it can't be and I don't have any other components of your list

@nckslater, i know it will be painful to do, but as we have just seen - chances are that some (or just one sucker) of those custom components are causing conflict(s).
I would recommend you to try removing them one by one and see if that issue would go away. smartthinq_sensors was one of them, but there might be more 😅  You could go different ways about it: one is to do a full backup of your current setup and experiment on that, another if you have a chance to setup a test environment to replicate your current setup and play there.
Either way, please keep us posted if you'll be able to find anything - will be useful for others having the same issue

Interesting thread!
I am also getting
2021-03-31 13:41:22 ERROR (SyncWorker_26) [glocaltokens.client] [!] Could not get master token.
2021-03-31 13:41:22 ERROR (MainThread) [custom_components.google_home]
I'm aso using the LG custom component
following...

@stboch, awesome job for finding the issue with LG-smartthinq integration, it seems that there is an update that fixes the issue with a chipset, can you please try updating LG-smartthinq to the latest version to see if it fixes the problem? :)

Yay!
After submitting login and app password, the configuration window gets
crazy and starts to resize itself about 10 times per second and it goes on
for 30 seconds. After that, the integration is added successfully :-)

@joggs, it's a funny behaviour but i m pretty sure not caused from ha-google-home integration :D If you feel so, please make a separate ticket with more details.
Happy it works for you now 💥

No problem at all.:-)
I am not sure it works though. Am I supposed to see "x devices and y
entities" on the integration card on the integrations page, like for all
other integrations?
I just see the google home logo on the integration card on the integrations
page, even though I have created a test alarm. I have so many entities on
the developer page, so it is possible that I have something in there, but
haven't found it yet.
On Thu, Apr 1, 2021 at 3:00 PM Ilja Leiko @.***> wrote:

@joggs https://github.com/joggs, it's a funny behaviour but i m pretty
sure not caused from ha-google-home integration :D If you feel so, please
make a separate ticket with more details.
Happy it works for you now 💥
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/leikoilja/ha-google-home/issues/95#issuecomment-811890449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLJXKQM234KQK6OKBGX6TTGRVALANCNFSM4ZORKUCQ
.

--
/Jörgen Bergström

I have no sensors with alarm list or timer lists even though i have 5
google home/nest devices
On Thu, Apr 1, 2021 at 3:06 PM Jörgen Bergström @.***>
wrote:

No problem at all.:-)
I am not sure it works though. Am I supposed to see "x devices and y
entities" on the integration card on the integrations page, like for all
other integrations?
I just see the google home logo on the integration card on the
integrations page, even though I have created a test alarm. I have so many
entities on the developer page, so it is possible that I have something in
there, but haven't found it yet.
On Thu, Apr 1, 2021 at 3:00 PM Ilja Leiko @.***>
wrote:

@joggs https://github.com/joggs, it's a funny behaviour but i m pretty
sure not caused from ha-google-home integration :D If you feel so,
please make a separate ticket with more details.
Happy it works for you now 💥
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/leikoilja/ha-google-home/issues/95#issuecomment-811890449,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACLJXKQM234KQK6OKBGX6TTGRVALANCNFSM4ZORKUCQ
.

--
/Jörgen Bergström

--
/Jörgen Bergström

@joggs, sorry, i'll remove your messages since they are not related to BadAuthentication error. Please open a new issue and follow it's template by providing all necessary logs so we'd see what problem you are encountering :)

I also have an LG Smartthinq Custom Component installed. I was successfull with authenticating the Google Home integration today, after the recent LG Smartthinq update. (Was there a conflicting verison of a requirement?)
Anyway, I'm looking forward to exploring it today. :)

I also have an LG Smartthinq Custom Component installed. I was successfull with authenticating the Google Home integration today, after the recent LG Smartthinq update. (Was there a conflicting verison of a requirement?)
Anyway, I'm looking forward to exploring it today. :)

Same behaviour here. Tested seting up the Google Home integration unsuccessfully just before updating smartthinq. After updating and a reboot, the setup of Google Home completed without a hitch :)

@leikoilja I think maybe add to the readme under troubleshooting login problems ensure if your using the LG smartthinq custom component that the version is 0.6.7 or newer.

@stboch, we have just added a remark to the troubleshooting section to refer to this issue if someone still gets BadAuthentication problem. As we saw from @nckslater, LG smartthinq is not the only custom integration that can cause that behavior, I think we are better off generalizing in the troubleshooting section and just refer people here. So far it was been working for many of us :)

Ok, I'm closing this. Actions we've taken to remediate this:

Added troubleshooting section in README.
Pointed out to LG ThinQ author that they shouldn't alter urllib3's DEFAULT_CIPHERS. They have fixed this already in the new version.
Updated gpsoauth to use fixed list of ciphers to prevent similar issues in the future.

Please update to 1.3.0 where this should be solved.

I just installed the integration but I have the same issue.
"Username/Password is incorrect. If your google account has 2FA enabled please generate app password"
Integration version 1.9.10
Home Assistant Core 2022.5.5
Multifactor enabled with app password.
This is what I get on logs with debug enabled:
2022-05-19 21:41:03 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2022-05-19 21:41:03 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client access_token, homegraph, access_token_date and homegraph_date to None
2022-05-19 21:41:03 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client username to "a***********************", password to "r***************", master_token to "" and android_id to
2022-05-19 21:41:03 DEBUG (SyncWorker_22) [glocaltokens.client] There is no stored master_token, logging in using username and password
2022-05-19 21:41:03 DEBUG (SyncWorker_22) [glocaltokens.client] There is no stored android_id, generating a new one
2022-05-19 21:41:03 DEBUG (SyncWorker_22) [glocaltokens.client] Generating android id...
2022-05-19 21:41:03 DEBUG (SyncWorker_22) [glocaltokens.client] Generated android id: eb89dc38eabe277b
2022-05-19 21:41:03 ERROR (SyncWorker_22) [glocaltokens.client] [!] Could not get master token.
2022-05-19 21:41:03 DEBUG (SyncWorker_22) [glocaltokens.client] Request response: {'Error': 'NeedsBrowser', 'Url': 'https://accounts.google.com/signin/continue?sarp=1&scc=1&continue=https://accounts.google.com/o/android/auth?hl%3Den_us%26xoauth_display_name%3DAndroid%2BLogin%2BService%26source%3DAndroid%2BLogin&plt=AKgnsbsDJKWaUmGA7j9ZQgmP21WBsuifozeb2bYmmZzbwe7DG54J4FJL5qFRuxh-rLsByr-YBgeMTMSgj15nDZQITNbpAJbjQSZBp2yUgG7EC8eS2IBjvg3Cyv4RdTjWdsRl1XAyvsuv', 'ErrorDetail': 'To access your account, you must sign in on the web. Touch Next to start browser sign-in.'}
2022-05-19 21:41:03 ERROR (MainThread) [custom_components.google_home]

To access your account you must sign in on the web but I don't see any Next on the integration to login.
Tried to access the link by browser, I can pass the multifactor auth but then nothing happens and I still have the same error.    Tried to reinstall it but no lock.  I don't have LgThinQ integration installed.

@agarbato this issue has been detected, and it is being addressed at leikoilja/glocaltokens#245.

yep, i was in the middle of doing so, @adam91holt, but some things got on the way :) Will do it tomorrow morning and then update you here as well :)

Beautiful! Thanks for your hard work @leikoilja 🚀🚀🚀

Fixed in ha-google-home v1.9.11 🚀
https://github.com/leikoilja/ha-google-home/releases/tag/v1.9.11
Please update to the latest version and verify it works :)

@Neolanco have you rebooted HA?

Same here - have tested gpsoauth 1.0.1/1.0.2 using this and still can't generate a master token using app password.

Just updated, I'm recieving a ValueError that 'plaintext is too long'. My email address is 34 characters long lol 😅
Used my main account and it works, but I'd prefer (as you recommend) to use an alt. For now I'll just make another account but figured I should mention this,

@leikoilja yeah, the check should not be complicated, we have already done that for long passwords.

Hi, I had this working but I uninstalled it and I have reinstalled it after a while, I can't log in.
I have created an app password, but I get errors.
I'm on:
Home Assistant 2022.10.3
Supervisor 2022.10.0
Operating System 9.2
Frontend 20221010.0 - latest
I run this on a VM.
I got this on the Log:
Este error se originó a partir de una integración personalizada.
Logger: glocaltokens.client
Source: custom_components/google_home/api.py:73
Integration: Google Home (documentation, issues)
First occurred: 10:39:47 (3 occurrences)
Last logged: 10:40:58

[!] Could not get master token.

And this:
Este error se originó a partir de una integración personalizada.

Logger: custom_components.google_home
Source: custom_components/google_home/config_flow.py:65
Integration: Google Home (documentation, issues)
First occurred: 10:39:47 (3 occurrences)
Last logged: 10:40:58

And on the full log:
2022-10-12 10:38:12.024 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration google_home 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

2022-10-12 10:39:47.141 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2022-10-12 10:39:47.141 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client access_token, homegraph, access_token_date and homegraph_date to None
2022-10-12 10:39:47.141 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client username to "a**********************", password to "y***************", master_token to "" and android_id to
2022-10-12 10:39:47.149 DEBUG (SyncWorker_1) [glocaltokens.client] There is no stored master_token, logging in using username and password
2022-10-12 10:39:47.149 DEBUG (SyncWorker_1) [glocaltokens.client] There is no stored android_id, generating a new one
2022-10-12 10:39:47.149 DEBUG (SyncWorker_1) [glocaltokens.client] Generating android id...
2022-10-12 10:39:47.149 DEBUG (SyncWorker_1) [glocaltokens.client] Generated android id: 3e0d925c5981cc49
2022-10-12 10:39:47.306 ERROR (SyncWorker_1) [glocaltokens.client] [!] Could not get master token.
2022-10-12 10:39:47.308 DEBUG (SyncWorker_1) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2022-10-12 10:39:47.308 ERROR (MainThread) [custom_components.google_home]
2022-10-12 10:40:38.538 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2022-10-12 10:40:38.538 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client access_token, homegraph, access_token_date and homegraph_date to None
2022-10-12 10:40:38.538 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client username to "a**********************", password to "v***************", master_token to "" and android_id to
2022-10-12 10:40:38.539 DEBUG (SyncWorker_3) [glocaltokens.client] There is no stored master_token, logging in using username and password
2022-10-12 10:40:38.539 DEBUG (SyncWorker_3) [glocaltokens.client] There is no stored android_id, generating a new one
2022-10-12 10:40:38.539 DEBUG (SyncWorker_3) [glocaltokens.client] Generating android id...
2022-10-12 10:40:38.539 DEBUG (SyncWorker_3) [glocaltokens.client] Generated android id: 2f17c0f09f04cbab
2022-10-12 10:40:38.730 ERROR (SyncWorker_3) [glocaltokens.client] [!] Could not get master token.
2022-10-12 10:40:38.731 DEBUG (SyncWorker_3) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2022-10-12 10:40:38.731 ERROR (MainThread) [custom_components.google_home]
2022-10-12 10:40:57.917 DEBUG (MainThread) [glocaltokens.client] Initializing new GLocalAuthenticationTokens instance.
2022-10-12 10:40:57.917 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client access_token, homegraph, access_token_date and homegraph_date to None
2022-10-12 10:40:57.917 DEBUG (MainThread) [glocaltokens.client] Set GLocalAuthenticationTokens client username to "a***********************", password to "%****************", master_token to "" and android_id to
2022-10-12 10:40:57.917 DEBUG (SyncWorker_3) [glocaltokens.client] There is no stored master_token, logging in using username and password
2022-10-12 10:40:57.917 DEBUG (SyncWorker_3) [glocaltokens.client] There is no stored android_id, generating a new one
2022-10-12 10:40:57.917 DEBUG (SyncWorker_3) [glocaltokens.client] Generating android id...
2022-10-12 10:40:57.918 DEBUG (SyncWorker_3) [glocaltokens.client] Generated android id: d965db2f3fd61914
2022-10-12 10:40:58.038 ERROR (SyncWorker_3) [glocaltokens.client] [!] Could not get master token.
2022-10-12 10:40:58.039 DEBUG (SyncWorker_3) [glocaltokens.client] Request response: {'Error': 'BadAuthentication'}
2022-10-12 10:40:58.039 ERROR (MainThread) [custom_components.google_home]

@Fonsos please move it to https://github.com/leikoilja/ha-google-home/issues/599


[Bug]: make 'Blogs' option visible in the navigation bar in portrait display.

Contact Details
<EMAIL_ADDRESS>What happened?
When the website is viewed in portrait mode, the Blogs route option is not visible in the navigation bar. I would like to address and fix this issue.

What browsers are you seeing the problem on?
Microsoft Edge
Relevant log output
No response
Are you interested in contributing?

[X] I'd like to work on this issue

Code of Conduct

[X] I have used the search function to check if an issue already exists
[X] I agree to follow this project's Code of Conduct

Which program are you contributing in?
gssoc, ssoc

hey @loveleen4k  i think i know the problem , can you assign me this issue ?


Discussion: Feasibility of developing a needleman-wunsch global aligner

Hi Philip,
Just brainstorming here. I wanted to hear your thoughts on the possibility of taking the existing smith-waterman code and altering it to perform a global alignment instead. The only reason I'd want to do this is to see how GKL-rs would compare against currently existing global pairwise aligners, like WFA https://github.com/smarco/WFA2-lib
I'm hoping to take this on as a side project, but I just want to hear if you think GKL-rs is currently adaptable as it currently exists.
Cheers,
Rhys

I think it already is global alignment: https://github.com/broadinstitute/gatk/issues/6576#issuecomment-1003504446
But either way, yes I think it is feasible to adapt GKL-rs to handle both.

Oh easy as, I remember seeing this comment of yours ages ago but must have forgotten about it. Glad to know it's easy, just wanted to double check there wasn't some weirdness happening in the background that would global/local alignments difficult.
Knowing it is already global, i'll go ahead and play around with it. Thanks again!

That might have been from #11. So there might still be some overhang differences to account for in order to get the same results as WFA2-lib, but that won't be hard.

Alright, nice I'll keep you posted then


Android Native UI Components - How to get Activity from reactContext

I'm relatively new to Android development so forgive me if I'm missing something here, but I'm trying to bridge over a bunch of native UI components to React Native, and the biggest thing I'm lacking is access to an Activity...
Some use cases:

I need an Activity to call .getFragmentManager() to be able to add a Fragment to my view.
I need an Activity to call .getWindow() to be able to add the FLAG_KEEP_SCREEN_ON to disable the screen idle timer.

Everything I've read online mentions getting access to the Activity by casting your context like so:
FragmentManager fragmentManager = ((Activity) mContext).getFragmentManager();
However, com.facebook.react.uimanager.ThemedReactContext cannot be cast to android.app.Activity
How can I get an Activity in a native UI component bridge? Or am I thinking about this the wrong way?

See https://github.com/facebook/react-native/issues/2996

please use ThemedReactContext class instance to invoke getCurrentActivity function to get the Activity.
best regard


Random test runner fix

Types of PR

[ ] New Features
[ ] Upgrade of existing features
[X] Bugfix

Link to the issue
https://tier4.atlassian.net/browse/RJD-706
Description
Multiple problems were fixed in this PR in order to allow performing tests with the random test runner successfully:

The duration of Autoware initialization was not specified in the random test runner launch file. Because of that test runner was not waiting for Autoware to initialize and instead stopped immediately. The default value of the parameter is now set inside the launch file.
allow_goal_modification was not declared as a parameter which made concealer crash while it was trying to use the parameter. The parameter is now declared with the usage of traffic_simulator::API.
OccupancyGridSensor was not attached by TestExecutor which blocked Autoware in planning the route. Autoware was stuck waiting for the initialization of occupancy grid map. The sensor is now attached with the usage of using traffic_simulator::API.
Because all TestExecutors were using the same instance of traffic_simulator::API only the first test could be initialized properly. It was caused by the fact that EntityManager does not allow to set the entity status after starting the scenario. Separate traffic_simulator::API instances are now being attached to each TestExecutor.
Exception thrown during the test ended the random test runner execution. Exceptions handling in TestExecutor is now added so that an exception ends only currently executed test and makes random test runner proceed to the next test.

How to review this PR.
Others
There is an issue which blocks random test runner from initializing the test if either initial position or goal pose exceeds the drivable area.

In the first case Autoware will be launched but the ego vehicle will not move waiting for Autoware to change its state to WaitingForEngage. After a timeout the test will finish, the error will be logged and the runner will continue with the next test.
In the second case test will be immediately stopped after launching the Autoware and similarly as in the first case the error will be logged and the runner will continue with the next test.

This issue is not related with this PR.

Sorry, I found that it is unnecessary for checking regression test in Evaluator.

LGTM!


Check if WinForms application is fully loaded

Hi,
I am creating engine to automated tests for WinForms application using FlaUI library. I found interesting problem and have no idea how to solve it without using Thread.Sleep method. I wish I could avoid unnecessary delay in test execution because the engine works on many different computers, where the time of sleep can much differ.
The thing is that when I start application process I wait for input idle to make sure that application is ready to work. Before engine tries to click some element it checks if this element is enabled and visible. The problem occures when element xpath uses indexing. Application window contains two elements of type Edit. Xpath of first one is Window/Edit[1], and the second Window/Edit[2]. Sometimes when test execution is very quickly it happens that two next clicks are performed on first element as if the other one was not loaded quickly enough in the application. When I changed xpaths of elements to use name attribute it seems to work properly but I would like to use indexing anyway.
Is there any way to check if  all window elements of the external application are fully loaded ?
Thanks in advance!

Per se there is no default way to determine if the application is loaded. If possible, the application itself should provide a loading screen or loading spinner which is displayed until the application is fully loaded. You can then do a Wait with FlaUI until the loading screen or spinner is removed and then continue with the test.

I'll close this as there is nothing to add from FlaUIs side.


ctr: make --runtime=./relative/path/to/shim/binary error less cryptic (ctr: failed to start shim: start failed: : exec: "/": permission denied: unknown)

What is the problem you're trying to solve
ctr produces a cryptic error when a relative path to a shim binary is specified as --runtime=./relative/path/to/shim/binary.
$ sudo ctr run  --rm --runtime=./containerd-shim-runc-v2 docker.io/library/hello-world:latest hello-world
ctr: failed to start shim: start failed: : exec: "/": permission denied: unknown

Probably ctr is attempting to parse the path string as an <TLD>.<VENDOR>.<RUNTIME>.<VERSION> format string.
An absolute path works as expected.
Describe the solution you'd like
Make the error message less cryptic.
Additional context
v1.6.0-rc.1

@AkihiroSuda I would like to work on it, could you please provide some information on how to proceed in the task and where the changes needed in the repo. Some code pointers would be really helpful.

Hi @AkihiroSuda , can I take this up ?
Should it be expected that your example above should fail with a message like this one?
https://github.com/containerd/containerd/blob/4f5ce5615adf81fcdf0e7c50e12b15d82b77e129/runtime/v2/manager.go#L249-L252
assuming relative paths to shim binaries are not supported based on this.

Yes please

Resolving since we've merged #6519.


Add support for Gitter.

Current Gitter badge looks like this:
[![Join the chat at https://gitter.im/sahat/hackathon-starter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/sahat/hackathon-starter?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

Discussions are underway here about switching to shields.io.
This is how a you can make a shields.io badge for Gitter currently:
[![Join the chat at https://gitter.im/sahat/hackathon-starter](https://img.shields.io/badge/GITTER-join%20chat-green.svg)](https://gitter.im/sahat/hackathon-starter?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

I thought it would be much better to have a badge which looks like this:
[![Join the chat at https://gitter.im/sahat/hackathon-starter](https://img.shields.io/badge/GITTER-4%20users%20online-green.svg)](https://gitter.im/sahat/hackathon-starter?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

I will try to put together some API examples when I get a chance.

Thanks for the suggestion!
The original issue is here: https://github.com/badges/shields/issues/354.


Can you add a react-router configuration?

I always make mistakes according to the official document. Can I add a react-router in this configuration? thank you

If you think it's useful for other then I won't mind accepting a PR at all.

@lengziyu the master branch now provides an example of basic react-router

Thanks to you @pgerochi ! :D
@lengziyu I'm going to close this since we've implemented what you've asked for :)


Digging out an opened Storage Actuator causes server crash and item duplication.

Digging out an opened Storage Actuator causes server crash and item duplication.
Steps to reproduce the behavior:

One player opens a Storage Actuator while another player digs out the Storage Actuator block.
The player who opened the container continues to take out items, causing the items to be removed and resulting in a server crash.
The server crash leads to the map data not being saved.
If a player opens a Stable Wormhole and another player digs out a Storage Actuator, it will also cause a server crash and duplicate the items.

I have tried this experiment, and it does cause the Storage Actuator to not drop any items without crashing the server. However, the fourth situation still causes a server crash.

Occultism Version: 1.29.1
Minecraft Version: 1.16.5

`
Description: Ticking entity
com.github.klikli_dev.occultism.exceptions.ItemHandlerMissingException: ItemHandler
at net.minecraftforge.common.util.LazyOptional.orElseThrow(LazyOptional.java:296) ~[forge:?] {re:classloading}
at com.github.klikli_dev.occultism.common.tile.StorageControllerTileEntity.getStacks(StorageControllerTileEntity.java:184) ~[occultism:1.16.5-1.29.1] {re:classloading}
at com.github.klikli_dev.occultism.common.tile.StorageControllerTileEntity.getMessageUpdateStacks(StorageControllerTileEntity.java:202) ~[occultism:1.16.5-1.29.1] {re:classloading}
at com.github.klikli_dev.occultism.common.container.storage.StableWormholeContainer.func_75145_c(StableWormholeContainer.java:129) ~[occultism:1.16.5-1.29.1] {re:classloading}
at net.minecraft.entity.player.ServerPlayerEntity.func_70071_h_(ServerPlayerEntity.java:461) ~[?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:betterendforge.mixins.json:ServerPlayerEntityMixin,pl:mixin:A}
at net.minecraft.world.server.ServerWorld.func_217479_a(ServerWorld.java:756) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.world.World.func_217390_a(World.java:811) ~[?:?] {re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.world.server.ServerWorld.func_72835_b(ServerWorld.java:529) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:runtimedistcleaner:A}
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:1049) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:byg.mixins.json:server.MixinMinecraftServer,pl:mixin:APP:betterendforge.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:336) ~[?:?] {re:classloading,pl:accesstransformer:B}
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:943) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:byg.mixins.json:server.MixinMinecraftServer,pl:mixin:APP:betterendforge.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:775) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:byg.mixins.json:server.MixinMinecraftServer,pl:mixin:APP:betterendforge.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
at net.minecraft.server.MinecraftServer.func_240783_a_(MinecraftServer.java:265) ~[?:?] {re:mixin,pl:accesstransformer:B,pl:runtimedistcleaner:A,re:classloading,pl:accesstransformer:B,pl:mixin:APP:byg.mixins.json:server.MixinMinecraftServer,pl:mixin:APP:betterendforge.mixins.json:MinecraftServerMixin,pl:mixin:A,pl:runtimedistcleaner:A}
at java.lang.Thread.run(Thread.java:831) [?:?] {}
`

Thank you for reporting - I believe we had this error on later MC versions too but fixed it there.
1.16.5 is no longer receiving support so there won't be an update unless a community member provides a patch

Repairing higher versions can achieve 1.16.5, and I can transfer it myself

I hope to inform you after the repair. Thank you

Let's reopen this for a moment then - does it currently happen in modern versions?
If it does not happen you can check out https://github.com/klikli-dev/occultism/issues/843 and https://github.com/klikli-dev/occultism/issues/844 these are commits that fix a similar issue.
If it DOES happen on modern versions let me know and I will fix it :)


(Ivy) Assertion error: failed to find directive with exportAs: matAutocomplete

Reproduction
We used Angular Material in our project and it compiles fine with Angular 9.0.0-next.13 (non-Ivy mode). But if we try to set Ivy mode in tsconfig.json:
"angularCompilerOptions": {
"enableIvy": true
},
"ng build --prod" command failed.
We tried two Angular Material versions: 8.2.3 and 9.0.0-next.0 but error still reproduces.
Expected Behavior
Project compiled successfully.
Actual Behavior
ERROR in Error: Assertion error: failed to find directive with exportAs: matAutocomplete
at project\node_modules@angular\compiler\bundles\compiler.umd.js:28818:31
Environment
Angular CLI: 9.0.0-next.15
Node: 12.3.1
OS: win32 x64
Angular: 9.0.0-next.13
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package                           Version
@angular-devkit/architect         0.900.0-next.15
@angular-devkit/build-angular     0.900.0-next.15
@angular-devkit/build-optimizer   0.900.0-next.15
@angular-devkit/build-webpack     0.900.0-next.15
@angular-devkit/core              9.0.0-next.15
@angular-devkit/schematics        9.0.0-next.15
@angular/cdk                      8.2.3
@angular/cli                      9.0.0-next.15
@angular/material                 8.2.3
@ngtools/webpack                  9.0.0-next.15
@schematics/angular               9.0.0-next.15
@schematics/update                0.900.0-next.15
rxjs                              6.5.3
typescript                        3.6.4
webpack                           4.41.2

It's hard to tell what's going on based on the provided information. We have some examples of matAutocomplete that are working against Ivy. Can you post the code that's failing?

I've seen those kinds of errors. In my case, they had nothing to do with the directive/pipe/etc. mentioned in the error message. They were caused by some other library that wasn't ivy-compatible. Importing it didn't raise any errors of its own, but it would mess up the module it was imported to. I solved it by creating blank project and adding 3rd party libraries/modules one by one, to see which one was causing the issue.

I get this intermittently with various Angular Material modules. It compiles fine the first time, but within four or five updates (if I'm using --watch) then it cops out with failed to find directive with exportAs: [some-material-component]. If it is an external package causing the issue I have no idea how to isolate it as the project is huge, with many dependencies and builds fine the first time anyway.

Not reproduced with @angular/cdk 9.0.0-rc.4


Change simple cookie header parse to keep most recently set

Thanks, and sorry for the late review. I have implemented the fix for #1831 in b6bd4b455c54fa44c68df961b9d5c21a2bb0ae73. This works correctly if there are multiple cookies with the same name but different paths - just going with the most recently set may not be the correct choice in that case.

I recommend that this commit broken "set-cookie" list and makes cookies lacks of lost of messages!
https://github.com/jhy/jsoup/commit/b6bd4b455c54fa44c68df961b9d5c21a2bb0ae73


ADDED CODE FOR U.S. weather history visualization (issue-115)

Related Issue

Info about the related issue

[x] LGM-SOC'21 Participant

[x] Contributor

Closes: #115
Describe the add-ons or changes you've made
For this I have prepared 3 python files for the main code/analysis and 11 datasets.
U.S. weather history visualization
The raw data and code behind the story What 12 Months Of Record-Setting Temperatures Looks Like Across The U.S.
Source: Weather Underground
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Describe how it has been tested
Describe how have you verified the changes made
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

@HitainKakkar there is no output in ur files,so pls .ipynb files


Redux : module structure guidelines

After discussion, we have reached the agreement that the Redux modules should follow this structure :
Initial State
Selectors
Actions
Actions creators
Reducer

I try to keep selectors and action creators as short and simple as possible. If for some reason, one selector or action creator is more complicated, I create a utility function to which I delegate the "complicated" work and gather these utility functions in a utils.js file that I put next to the index.js file in the Redux module folder.
For example, the viewport Redux module would look like:

redux

modules

viewport

index.js
utils.js


Analyzer Error with empty feedback

In the IntelliJ event log:
10:45 AM Dart Analyzer Error
	 Encountered a Dart Analysis Server error.
	 Open issue submission form?

Clicking the Open issue submission form? link brought me here, but the populated feedback is empty except for the following line:

Analyzer Feedback from IntelliJ

Can you reproduce the problem?
I run into an issue several times where the content of the error report was not added to the issue body, but to the URL in the browser URL bar. #32496

I haven't been using IntelliJ consistently recently, but if I see it happen again I'll check to see if this is a duplicate of https://github.com/dart-lang/sdk/issues/32496. I suspect it is.

Closing in favor of #32496


About training of pointnet and pointnet++ on modelnet40 dataset

As you mentioned in the paper that pointnet and pointnet++ have been trained on modenet40 and then tested on your dataset. Did you train both pointnet and pointnet++ using all the 40 categories of modelnet40  or just those 11 categories which are overlapping with your dataset?
Thanks

For Table 3 in the main paper, we used all 40 classes on ModelNet40 for training the models. You may refer to the supplementary material for results on training on the common categories between the two datasets. Thanks!

Thanks a lot


ReferenceError: spatialAudio is not defined

https://github.com/voxeet/voxeet-uxkit-react/blob/dea3b2b6a6d5645cc5f1c2cc35d798fcf79c3b68/src/app/actions/ConferenceActions.js#L375

The app stack during loading screen with error: 1.bundle.js:1 Uncaught (in promise) ReferenceError: spatialAudio is not defined

Fixed in a2540a32f7545265f0161dca526c43a20c355dac commit


With proxy certs the list of DPCs can easily exceed pubsub msg size limit

DevicePortConfig (DPC) may store one or more proxy certificates for each port.
With multiple DevicePortConfigs, kept in the DevicePortConfigList (DPCL) for
fallback purposes, this may quickly exceed the message size limit
of 64KB, as imposed by pubsub.
Normally, if the latest DPC is working (providing connectivity to the
controller), DPCL is being compressed before it is published.
The compression removes all obsolete (not latest) entries except
for lastresort. However, if the latest DPC is not working, DPCL
may just keep growing as new DPCs are being submitted from the controller.
A typicall scenario when this can be a problem, is when a user submits
invalid device port config (i.e. device will not use this failing latest config)
and then makes multiple unsucessful attempts to fix the config, each time
generating a new DPC. If the port configuration contains proxy certificates,
each with the size of 1-4 KBs, this can quickly adds up and exceed the pubsub
limit.
This PR tries to mitigate this issue. First, before publishing, the DPCL
size is estimated and if it is close to 64KB, the compression is enforced
and applied even if the currently used DPC is not the latest.
Second, because the certificates themselves are often the source of DPC
invalidity (e.g. wrong format), it makes sense to skip persisted DPCs
with wrong certificates and not carry them across device reboots.
Signed-off-by: Milan Lenco<EMAIL_ADDRESS>

Do we have the DPCL which caused the size to get too large? I suspect this was due to the proxy certificate, and I wonder whether it would work to set the proxy certificate as a large item (such as e.g., CipherData []byte json:"pubsub-large-CipherData"

Oh, I wasn't aware of this pubsub capability. Yes, the culprit causing the size of DPCL to exceed the size limit is the list of proxy certificates. Will try to add pubsub-large json tag and retest to see if it is working and if it is sufficient to avoid the issue.

@eriknordmark I have update the PR (both content and the description) to use the pubsub-large json tag.


fix(jsdoc): add jsDoc to query parameters

Status

READY
Description
Use parameter descriptions to document the types
https://github.com/anymaniax/orval/blob/ba7ee988557a63c392c6d9bee50bbd7eddfe3b86/samples/react-app/petstore.yaml#L16-L22
- export type ListPetsParams = { limit?: string };
+ export type ListPetsParams = {
+ /**
+  * How many items to return at one time (max 100)
+  */
+ limit?: string;
+ };

Todos

[x] Tests
[ ] Documentation
[ ] Changelog Entry (unreleased)

Seems really good thanks @lukaw3d


WIP refactor(ci): deploy new release workflow

related to INFRA-2213
:exclamation: please don't merge yet :exclamation:

/lm add do-not-merge/work-in-progress


Coveralls does not include results of all CI's

It looks that coveralls includes only results of one CI provider.
In https://github.com/Toblerity/Fiona/pull/875/commits/b890f5c2007e783f45984107e34c88f65a0fd15b only the results of travis are included.
I'm not sure if coveralls supports multiple CI's at all.
Codecov claims that it merges reports from multiple CI providers: https://docs.codecov.io/docs/frequently-asked-questions#section-does-codecov-merge-reports-for-multiple-containers-and-or-ci-providers

After testing out how codecov works, I noticed that coveralls is not setup on appveyor. I'm not sure why.
Adding coveralls to appveyor requires setting a token:
Not on TravisCI. You have to provide either repo_token in .coveralls.yml or set the COVERALLS_REPO_TOKEN env var.
Traceback (most recent call last):
  File "C:\Python36-x64\Lib\site-packages\coveralls\cli.py", line 61, in main
    service_name=options['--service'])
  File "C:\Python36-x64\Lib\site-packages\coveralls\api.py", line 64, in __init__
    self.ensure_token()
  File "C:\Python36-x64\Lib\site-packages\coveralls\api.py", line 73, in ensure_token
    self.config_filename))
coveralls.exception.CoverallsException: Not on TravisCI. You have to provide either repo_token in .coveralls.yml or set the COVERALLS_REPO_TOKEN env var.

Codecov does not require a token for travis and appveyor. https://codecov.io/gh/rbuffat/Fiona/branch/try_codecov

Closed with https://github.com/Toblerity/Fiona/pull/885


Default for scheduler.rate does not follow the cron syntax

@Scheduled(cron = "${scheduler.rate:30000}")

@Scheduled can take one of cron(), fixedDelay(), or fixedRate() , but the default does not follow the cron syntax
Note that the cron syntax in spring (with precision up to seconds) is different from normal ones.
Spring: http://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/scheduling/annotation/Scheduled.html#fixedDelay--
Normal: http://www.nncron.ru/help/EN/working/cron-format.htm

Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scheduledJobLauncher': Initialization of bean failed; nested exception is java.lang.IllegalStateException: Encountered invalid @Scheduled method 'doTask': Cron expression must consist of 6 fields (found 1 in "30000")

This issue was moved to CogStack/cogstack#25


Not enough buffers provided by V4L2VideoDevice on RPi3B

Hey
I've used libcamera-apps on RaspberryPi4B with no problems, but now that I am trying to run the same thing on RaspberryPi3B I'm getting the following output which says there's not enough memory provided by V4L2VideoDevice:
Preview window unavailable
[0:00:38.313611546] [574]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0
[0:00:39.112628265] [574]  INFO Camera camera.cpp:937 configuring streams: (0) 1920x1080-YUV420
[0:00:39.113816546] [579]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt BG10 Score: 3217.33 (best 3217.33)
[0:00:39.114026234] [579]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt BG10 Score: 1500 (best 1500)
[0:00:39.114364359] [579]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt BG10 Score: 4297.33 (best 1500)
[0:00:39.114585348] [579]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BG10 Score: 6593.33 (best 1500)
[0:00:39.114927275] [579]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BA81 Score: 7593.33 (best 1500)
[0:00:39.115175921] [579]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt pBAA Score: 2717.33 (best 1500)
[0:00:39.115281754] [579]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pBAA Score: 1000 (best 1000)
[0:00:39.115495348] [579]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt pBAA Score: 3797.33 (best 1000)
[0:00:39.115815869] [579]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pBAA Score: 6093.33 (best 1000)
[0:00:39.116914671] [579]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected mode: 1920x1080-pBAA
[0:00:39.174797848] [579] ERROR V4L2 v4l2_videodevice.cpp:1165 /dev/video14[20:cap]: Not enough buffers provided by V4L2VideoDevice
[0:00:39.179206129] [579] ERROR RPI raspberrypi.cpp:817 Failed to allocate buffers

If I lower the width and height to 1280x720 It'll work with the following output:
Preview window unavailable
[0:05:32.120688361] [597]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0
[0:05:32.592355757] [597]  INFO Camera camera.cpp:937 configuring streams: (0) 1280x720-YUV420
[0:05:32.593463465] [602]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt BG10 Score: 3467.33 (best 3467.33)
[0:05:32.593667892] [602]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt BG10 Score: 1750 (best 1750)
[0:05:32.593766486] [602]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt BG10 Score: 2900.33 (best 1750)
[0:05:32.593862632] [602]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BG10 Score: 4593.33 (best 1750)
[0:05:32.593968465] [602]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BA81 Score: 5593.33 (best 1750)
[0:05:32.594068049] [602]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt pBAA Score: 2967.33 (best 1750)
[0:05:32.594163049] [602]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pBAA Score: 1250 (best 1250)
[0:05:32.594256017] [602]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt pBAA Score: 2400.33 (best 1250)
[0:05:32.594349611] [602]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pBAA Score: 4093.33 (best 1250)
[0:05:32.595439819] [602]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected mode: 1920x1080-pBAA
[0:05:32.652724819] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: Sharpness = 1.000000
[0:05:32.653003153] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: Saturation = 1.000000
[0:05:32.653121278] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: Contrast = 1.000000
[0:05:32.653257163] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: Brightness = 0.000000
[0:05:32.653363153] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:05:32.653985340] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: NoiseReductionMode = 1
[0:05:32.655017840] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: AeMeteringMode = 0
[0:05:32.656151694] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: AeExposureMode = 0
[0:05:32.656324194] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: ExposureValue = 0.000000
[0:05:32.656595757] [607]  INFO IPARPI raspberrypi.cpp:621 Request ctrl: AwbMode = 0
[0:05:32.664247997] [602]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:05:32.664372372] [602]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:05:32.772272007] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (7 left)
[0:05:32.819013934] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (6 left)
[0:05:32.860382580] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (5 left)
[0:05:32.887909871] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (4 left)
[0:05:32.919877424] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (3 left)
[0:05:32.953200444] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (2 left)
[0:05:32.987983778] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (1 left)
[0:05:33.021247267] [602]  INFO RPI raspberrypi.cpp:1635 Dropping frame at the request of the IPA (0 left)

This problem did not occur in RaspberryPi4. I have dedicated 128M to gpu_mem. Also there's no problem when using raspivid, it only occurs when using libcamera-vid and camera resolution of 1920x1080.

Hi, I've just tried this on a Pi 3 and it seemed to work OK. Can you perhaps say:

What OS you've installed (uname -a and vcgencmd version might be helpful). I used the latest version of Bullseye from the Raspberry Pi Imager tool.
What version does libcamera-hello --version report?
Have you changed anything in your /boot/config.txt? I believe the default gpu_mem is only 76MB when running Bullseye on a Pi 3 (the system needs less because the camera stack no longer uses it), Though I tried bumping it all the way up to 256 and it still works.
I notice it reports "Preview window unavailable". Is it running headless, or over ssh or is there anything else that would help me to do the same thing as you?
Giving the full commands you're using would also be helpful. Ah, I see you've reported the same thing on the forum with the commands given. No problem, then!

Thanks!

Same issue attaching versions
uname -a
Linux raspberrypi 5.10.63-v7+ #1459 SMP Wed Oct 6 16:41:10 BST 2021 armv7l GNU/Linux

libcamera-vid  --inline --listen -o tcp://<IP_ADDRESS>:8554
[0:46:31.874985905] [7107]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3156-f4070274
[0:46:32.026030499] [7107]  INFO Camera camera.cpp:937 configuring streams: (0) 640x480-YUV420
[0:46:32.026309457] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt BG10 Score: 2354 (best 2354)
[0:46:32.026453154] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt BG10 Score: 2136.67 (best 2136.67)
[0:46:32.026541019] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt BG10 Score: 1787 (best 1787)
[0:46:32.026622894] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BG10 Score: 1500 (best 1500)
[0:46:32.026704717] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BA81 Score: 2500 (best 1500)
[0:46:32.026784144] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 2592x1944 fmt pBAA Score: 1854 (best 1500)
[0:46:32.026862373] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pBAA Score: 1636.67 (best 1500)
[0:46:32.026941435] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 1296x972 fmt pBAA Score: 1287 (best 1287)
[0:46:32.027021435] [7112]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pBAA Score: 1000 (best 1000)
[0:46:32.029519922] [7112]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected mode: 640x480-pBAA
[0:46:32.056812500] [7112]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:46:32.056879427] [7112]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:46:32.122507488] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (7 left)
[0:46:32.184187637] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:46:32.214363545] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:46:32.246249868] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:46:32.277151193] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:46:32.308807725] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:46:32.340154569] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:46:32.371539487] [7112]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)

libcamera-hello --version
libcamera-apps build: 2a38ae93f143 21-10-2021 (14:49:17)
libcamera build: v0.0.0+3156-f4070274

vcgencmd version
Oct 29 2021 10:50:02
Copyright (c) 2012 Broadcom
version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean) (release) (start_x)

@Rakhmanov Thanks for attaching this extra information. I can't see where you are getting a "not enough V4L2 buffers" error like the OP, so it's not immediately clear to me whether this is the same problem or something else. Can you perhaps clarify? Thanks!

@davidplowman This is what I get using an RPi 3B with the camera module attached when attempting to run libcamera-hello:

Seems to be along the lines of what the OP is describing.  This is with a fresh install of RPi OS Bullseye.

@miztroh Thanks for this information. I'm struggling to reproduce the same thing, here's what I've tried on a Pi 3B:

Installed a fresh Bullseye (full, not Lite) using the Raspberry Pi imager tool. I let it run through its updates when it started.
Re-enabled Glamor using sudo raspi-config and then let it reboot.
Once it had restarted I ran libcamera-hello which worked fine.

Again, I'm not convinced this is the same problem as the OP, after all, the error message is different, and I'm guessing you don't have the same symptom that it works with smaller frame sizes but not larger ones? If you're still seeing this problem, could I perhaps ask you to post a new bug report? Could I also please ask for the following information in the new bug report:

Report the output of uname -a.
Report the output of vcgencmd version.
Report the output of libcamera-hello --version.
Say which camera you are using. Is it an official Raspberry Pi module or if not where did it come from? Do you have a link?
Give the full command you are running which fails.
Include the full console output of that command.
Say whether you are logged directly into the Pi with an attached keyboard or screen, or using ssh. If you are using ssh, are you using X forwarding?
Have you changed anything in the /boot/config.txt file, and if so, what?
Does the end of dmesg show any obvious errors?

Thanks very much!

I am experiencing the same error.
official RPi HQ camera on Pi 4b running Buster 64-bit version.
in /boot/config.txt I replaced dtoverlay. Before that it did not detect camera.
dtoverlay=imx477
#dtoverlay=vc4-kms-v3d
After changing that USB keyboard does not work any more. I saw it on dmesg though.
GPU memory is set to 256
libcamera-hello --version
libcamera-apps build: 2a38ae93f143 21-10-2021 (14:45:05)
libcamera build: v0.0.0+3156-f4070274

uname -a
Linux raspberry 5.10.52-v8+ #1440 SMP PREEMPT Tue Jul 27 09:56:40 BST 2021 aarch64 GNU/Linux
f
vcgencmd version
Jul 21 2021 16:22:36
Copyright (c) 2012 Broadcom
version 6a796bb0062a6c75191c57cba1c13f9300076d02 (clean) (release) (start_x)

v4l2-ctl --list-devices
bcm2835-codec-decode (platform:bcm2835-codec):
        /dev/video10
        /dev/video11
        /dev/video12

bcm2835-isp (platform:bcm2835-isp):
        /dev/video13
        /dev/video14
        /dev/video15
        /dev/video16

unicam (platform:fe801000.csi):
        /dev/video0
        /dev/video1

Running locally, display attached:
libcamera-still
libEGL warning: DRI2: failed to authenticate
[0:16:22.662715342] [2155]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3156-f4070274
[0:16:22.680540714] [2165]  WARN CameraSensor camera_sensor.cpp:197 'imx477 10-001a': Recommended V4L2 control 0x009a0922 not supported
[0:16:22.680628509] [2165]  WARN CameraSensor camera_sensor.cpp:249 'imx477 10-001a': The sensor kernel driver needs to be fixed
[0:16:22.680661953] [2165]  WARN CameraSensor camera_sensor.cpp:251 'imx477 10-001a': See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information
[0:16:22.681476124] [2165]  WARN CameraSensorProperties camera_sensor_properties.cpp:141 No static properties available for 'imx477'
[0:16:22.681548123] [2165]  WARN CameraSensorProperties camera_sensor_properties.cpp:143 Please consider updating the camera sensor properties database
[0:16:22.681577974] [2165]  WARN CameraSensor camera_sensor.cpp:414 'imx477 10-001a': Failed to retrieve the camera location
[0:16:22.716744355] [2155]  INFO Camera camera.cpp:937 configuring streams: (0) 2028x1520-YUV420
[0:16:22.716908000] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 1332x990 fmt RG10 Score: 3956.22 (best 3956.22)
[0:16:22.716988665] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 4056x3040 fmt RG12 Score: 1387 (best 1387)
[0:16:22.717022183] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1520 fmt RG12 Score: 500 (best 500)
[0:16:22.717053516] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1080 fmt RG12 Score: 1583.84 (best 500)
[0:16:22.717084886] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 1332x990 fmt pRAA Score: 3456.22 (best 500)
[0:16:22.717116108] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 4056x3040 fmt pRCC Score: 887 (best 500)
[0:16:22.717146181] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1520 fmt pRCC Score: 0 (best 0)
[0:16:22.717176218] [2165]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1080 fmt pRCC Score: 1083.84 (best 0)
[0:16:22.717298105] [2165]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected mode: 2028x1520-pRCC
[0:16:22.754567080] [2165] ERROR V4L2 v4l2_videodevice.cpp:1165 /dev/video14[18:cap]: Not enough buffers provided by V4L2VideoDevice
[0:16:22.758382795] [2165] ERROR RPI raspberrypi.cpp:817 Failed to allocate buffers

Running over ssh, display attached, no X forwarding:
libcamera-jpeg -v -o test.jpeg
Preview window unavailable
Running without preview window
Opening camera...
[0:04:45.495745043] [1676]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3156-f4070274
[0:04:45.507889921] [1678]  WARN CameraSensor camera_sensor.cpp:197 'imx477 10-001a': Recommended V4L2 control 0x009a0922 not supported
[0:04:45.507964659] [1678]  WARN CameraSensor camera_sensor.cpp:249 'imx477 10-001a': The sensor kernel driver needs to be fixed
[0:04:45.508053026] [1678]  WARN CameraSensor camera_sensor.cpp:251 'imx477 10-001a': See Documentation/sensor_driver_requirements.rst in the libcamera sources for more information
[0:04:45.508859590] [1678]  WARN CameraSensorProperties camera_sensor_properties.cpp:141 No static properties available for 'imx477'
[0:04:45.508957679] [1678]  WARN CameraSensorProperties camera_sensor_properties.cpp:143 Please consider updating the camera sensor properties database
[0:04:45.509009011] [1678]  WARN CameraSensor camera_sensor.cpp:414 'imx477 10-001a': Failed to retrieve the camera location
Acquired camera /base/soc/i2c0mux/i2c@1/imx477@1a
Configuring viewfinder...
Viewfinder size chosen is 2028x1520
[0:04:45.550580812] [1676]  INFO Camera camera.cpp:937 configuring streams: (0) 2028x1520-YUV420
[0:04:45.550748695] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 1332x990 fmt RG10 Score: 3956.22 (best 3956.22)
[0:04:45.550814729] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 4056x3040 fmt RG12 Score: 1387 (best 1387)
[0:04:45.550847987] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1520 fmt RG12 Score: 500 (best 500)
[0:04:45.550889449] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1080 fmt RG12 Score: 1583.84 (best 500)
[0:04:45.550921207] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 1332x990 fmt pRAA Score: 3456.22 (best 500)
[0:04:45.550954002] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 4056x3040 fmt pRCC Score: 887 (best 500)
[0:04:45.550984612] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1520 fmt pRCC Score: 0 (best 0)
[0:04:45.551015352] [1678]  INFO RPI raspberrypi.cpp:122 Mode: 2028x1080 fmt pRCC Score: 1083.84 (best 0)
[0:04:45.551153550] [1678]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected mode: 2028x1520-pRCC
Camera streams configured
Buffers allocated and mapped
Viewfinder setup complete
Requests created
[0:04:45.590440952] [1678] ERROR V4L2 v4l2_videodevice.cpp:1165 /dev/video14[17:cap]: Not enough buffers provided by V4L2VideoDevice
[0:04:45.594731076] [1678] ERROR RPI raspberrypi.cpp:817 Failed to allocate buffers
Closing Libcamera application(frames displayed 0, dropped 0)
Camera stopped!
Tearing down requests, buffers and configuration
Camera closed

dmesg:
[  475.687471] cma: cma_alloc: alloc failed, req-size: 1140 pages, ret: -12
[  475.687506] bcm2835-isp bcm2835-isp: dma_alloc_coherent of size 4669440 failed
[  590.817398] cma: cma_alloc: alloc failed, req-size: 1140 pages, ret: -12
[  590.817434] bcm2835-isp bcm2835-isp: dma_alloc_coherent of size 4669440 failed

Thanks very much for this information. This does look like the same kind of problem as the OP, and it certainly seems like you're running out of CMA memory. A few things to check:

Are you doing anything in your /boot/config.txt or /boot/cmdline.txt to alter the amount of CMA allocation?
Could you post the contents of /proc/meminfo? In particular the amount of CMA (at the bottom) might be illuminating.
The GPU memory of 256MB seems larger than you should need when using libcamera. On Bullseye we set this as low as 76MB by default.

Thanks!

I got it to work! Almost entire day wasted because of no option to fall back to picamera...
@davidplowman you suggested to re-enable Glamor.
When I did, this added following line to /boot/config.txt:
dtoverlay=vc4-fkms-v3d
I had removed it earlier when adding dtoverlay=imx477 because i thought there cant be two parameters with identical name.
I tested with original dtoverlay
dtoverlay=vc4-kms-v3d
and it worked also.
Conclusion:
to solve libcamera ERROR: *** no cameras available *** add camera dtoverlay, e.g. dtoverlay=imx477 to /boot/config.txt
If there is no dtoverlay=vc4-kms-v3d or  dtoverlay=vc4-fkms-v3d defined in the same file, there will be Not enough buffers provided by V4L2VideoDevice error.
For some reason usb keyboard takes ages to start working (it started occuring when i added dtoverlay=imx477).

Hi everyone, I'm going to close this bug because there doesn't appear to be any further information on the original problem, and various other bugs have crept in, at least some of which appear to be quite different and I'm afraid that I'm struggling a bit to understand what are still live issues and what are not.
But I'd like to encourage everyone who is still experiencing a problem to please file a new bug report of your own describing your issue. Please include all the information mentioned here: https://github.com/raspberrypi/libcamera-apps/issues/144#issuecomment-979076466 . Also the result of grep -i cma /proc/meminfo would be helpful if there appear to be buffer or memory problems.
Thanks very much!

Followup
I removed dtoverlay=vc4-kms-v3d again to reproduce the error
[0:16:22.754567080] [2165] ERROR V4L2 v4l2_videodevice.cpp:1165 /dev/video14[18:cap]: Not enough buffers provided by V4L2VideoDevice
[0:16:22.758382795] [2165] ERROR RPI raspberrypi.cpp:817 Failed to allocate buffers

Note. GPU memory is still set to 256 MB.
/proc/meminfo :
MemTotal:        3832956 kB
MemFree:         3210736 kB
MemAvailable:    3473668 kB
Buffers:           37328 kB
Cached:           278020 kB
SwapCached:            0 kB
Active:           100976 kB
Inactive:         431372 kB
Active(anon):        932 kB
Inactive(anon):   225672 kB
Active(file):     100044 kB
Inactive(file):   205700 kB
Unevictable:          60 kB
Mlocked:              60 kB
SwapTotal:        102396 kB
SwapFree:         102396 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:        217208 kB
Mapped:           136128 kB
Shmem:              9604 kB
KReclaimable:      27876 kB
Slab:              53452 kB
SReclaimable:      27876 kB
SUnreclaim:        25576 kB
KernelStack:        4192 kB
PageTables:         5816 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     2018872 kB
Committed_AS:    1254292 kB
VmallocTotal:   262930368 kB
VmallocUsed:        9284 kB
VmallocChunk:          0 kB
Percpu:              768 kB
CmaTotal:          65536 kB
CmaFree:           54920 kB

Hi, thanks for this information. It's clear that this configuration has insufficient CMA memory so libcamera is going to struggle. You will need to put back either dtoverlay=vc4-kms-v3d or dtoverlay=vc4-fkms-v3d. Setting gpu_mem does not help since libcamera does not use it, in fact it is almost certainly harmful so I would strongly recommend removing it. Hope that helps!

I received the same buffer error as @katyaxm on a Zero W running bullseye, which led me to this bug report.
I had initially set gpu_mem to 256M while troubleshooting a camera I was having some difficulty with (yep, half the Zero W's memory, ouch!).  Now that I have the camera recognized, and verified it was able to produce an image on buster, switching to an sd card with bullseye installed and libcamera gave me the buffer error.
At @davidplowman's suggestion to check /proc/meminfo for Cma memory:
CmaTotal:           8192 kB
CmaFree:            3676 kB

... which seemed a bit low.  Since libcamera doesn't use the gpu for the cam, I dropped gpu_memory back to the default of 76M and rebooted.  Checking /proc/meminfo a second time:
CmaTotal:         262144 kB
CmaFree:          153460 kB

... and sure enough, libcamera-hello now functions - even the preview window works w/ a monitor attached.
It seems like this error could be triggered by merely having too much memory allocated to the gpu, leaving too little free for Cma.

Hi I've got a related problem when using IMX477 and touch screen at same time
Seem if I dtoverlay=vc4-kms-v3d then the camera works, but then the touch screen wont
If I remove that then the touchscreen works but its the no cameras available issue

Hi, if useful to others - I had a related problem when using IMX477 and touch screen at same time Seem if I dtoverlay=vc4-kms-v3d then the camera works, but then the touch screen wont If I remove that then the touchscreen works but its the no cameras available issue
I can however use dtoverlay=vc4-fkms-v3d and get both - but then you see
[0:00:35.383195367] [2235] INFO Camera camera.cpp:1029 configuring streams: (0) 1280x720-YUV420 [0:00:35.385228182] [2269] INFO RPI raspberrypi.cpp:760 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected sensor format: 2028x1080-SBGGR12_1X12 - Selected unicam format: 2028x1080-pBCC [0:00:36.862222014] [2269] ERROR V4L2 v4l2_videodevice.cpp:1852 /dev/video1[20:cap]: Failed to start streaming: Input/output error ERROR: *** failed to start camera ***

I’m stuck at the same point.  Any solutions yet?

I am having the same problem with touchscreen and camera.
With dtoverlay=vc4-kms-v3d, the camera works (imx219) but no touchscreen.
With dtoverlay=vc4-fkms-v3d the touchscreen works but no camera.

C