Keep wfs delay

The current implementation of time-domain WFS minimizes the delay:
At least one loudspeaker starts playing at t = 0.
This is very convenient behaviour for a single virtual source.
For multiple virtual sources this seems very unconvenient:
You have to figure out how much delay was removed or added. So you basically calculate all delays again.
Proposed Optional Behaviour
I'd like to propose a flag conf.wsf.removedelay:

true (default) results in the previous behaviour, suitable for a single virtual source

false does the following:

A common delay offset t0 is introduced for all virtual sources.

t0 ensures causality for all plane waves and focused sources. Restrictions discussed below!

t0 := diam(x0) / c corresponds to the maximum travel time through the array, where

diam(x0) denotes the diameter of the SSD, i.e. the maximum distance between two secondary sources.
(agrees with conf.secondary_sources.size for 'line', 'circle' and 'sphere').

Example
Three virtual sources (ps,pw and fs), shortly after t0:
conf = SFS_config();
conf.secondary_sources.geometry = 'circle';
x0 = secondary_source_positions(conf);
conf.wfs.usehpre = 0;
conf.wfs.removedelay = 0;

xs_ps = [1.6,0,0];
xs_pw = [1,-2,0];
xs_fs = [0,-1,0,0,1,0];

[d_ps,delay_ps] = driving_function_imp_wfs(x0,xs_ps,'ps',conf);
[d_pw,delay_pw] = driving_function_imp_wfs(x0,xs_pw,'pw',conf);
[d_fs,delay_fs] = driving_function_imp_wfs(x0,xs_fs,'fs',conf);
[~,sss_ps] = secondary_source_selection(x0,xs_ps,'ps');
[~,sss_pw] = secondary_source_selection(x0,xs_pw,'pw');
[~,sss_fs] = secondary_source_selection(x0,xs_fs,'fs');

d_sum = zeros(conf.N,conf.secondary_sources.number);
d_sum(:,sss_ps) = d_sum(:,sss_ps) + d_ps(:,sss_ps);
d_sum(:,sss_pw) = d_sum(:,sss_pw) + d_pw(:,sss_pw);
d_sum(:,sss_fs) = d_sum(:,sss_fs) + d_fs(:,sss_fs);
sss_sum = sss_ps | sss_pw | sss_fs;

conf.wfs.usehpre = 1;
d_sum = wfs_preequalization(d_sum,conf);

%% Plot
t0 = secondary_source_maximum_distance(x0)/conf.c; % reference time
t0 = round(t0*conf.fs) + 64 + 1; % in samples + prefilter delay
t = t0 + 20;            % some samples more to see the point source

conf.plot.usedb = 1;
conf.plot.usenormalisation = 0;
sound_field_imp([-2,2],[-2,2],0,x0(sss_sum,:),'ps',d_sum(:,sss_sum),t,conf);
hold;
scatter(0,0,'kx');               % origin
scatter(xs_ps(1),xs_ps(2),'ko'); % point source
scatter(xs_fs(1),xs_fs(2),'ko'); % focused source
hold off;

Restrictions
Focused sources may only be placed within the ball B with radius diam(x0)/2, that encloses the SSD.

(Note that for any closed SSD, the entire listening area lies within B, so that's fine.)
Rationale:

In an unbounded listening area, a focused source could be arbitrarily far away from the SSD, resulting in arbitrarily large negative delay. The admissable region for focussed sources has to be restricted in some way or another.
Personally, I like this simple rule. (It also suggests a work-around for itself.)
The alternative would be a somewhat obscure conf.wfs.maximum_focused_source_distance that is only relevant for this particular case.

Changes

additional flag conf.wsf.removedelay
internal changes in driving_function_imp_wfs()
additional function secondary_sources_maximum_distance which computes the diameter and the center of B.

Thoughts?

I discussed a similar issue with Hagen related to the additional delay added by the fractional delay filters. Imho, it would be easier to return the pre-delay which has been added to the driving function by a particular processing step, e.g. fractional delay, wfs prefilter, focused source, plane wave, etc..
Furthermore, I would prefer that t=0 corresponds to the t=0 of the virtual source, i.e. where the sound "starts" to radiate from a point/focused source or when the plane wave passed its point of zero phase.

Returning the introduced pre-delay would work. Maybe it's a better strategy in the bigger picture, I don't know. But I would have to correct the delay after each call to driving_function_imp_wfs. I would prefer thatdriving_function_imp_wfs simply "does it right in the first place."
(Context: The use case I have in mind is simulation of databased SFS, i.e. many virtual sources.)
I'm not sure if understand your second point correctly. t0 is the shifted t = 0 for all virtual sources. Or put differently, each virtual source has the time signal delta(t - t0).
The plot merely depicts a time instant short after t0, because I wanted the point source to be visible.

Upon re-reading: My motivation was not very clear and parts of the code example were misleading.
Also my response to Fiete was partly wrong.
An attempt to clarify:
What it's about: a bit more superposition
If I have a sum of simple virtual sources (e.g. an image source model), I just want to sum up the driving functions.
(For a sum of plane waves, I'd still have to take care for the arrival times. But I think it's step in the right direction.)
What it's not about: reference time
I make no assumptions about the total delay at the end of processing.
The user is still responsible to keep track of that.
The corresponding  part in the code example should have read like this:
%% Plot
t0 = secondary_source_maximum_distance(x0)/conf.c; % max. travel time
total_delay = round(t0*conf.fs) + conf.wfs.hpreFIRorder/2  % total delay in samples
t = total_delay + 20;            % some samples more to see the point source

I'am totally aware, that its about the correct superposition of driving functions, but let me phrase the problem(s) the other way around:

"there have some issues with the time-correct superposition of driving functions"
"there have some issues with the reference time"

Solving 1. does not necessarily solve 2. and might complicate solving 2. afterwards. I think that, if we solve 2., 1. should be solved automatically or 1. should be solvable with moderate effort. I would therefore prefer to find a solution for the bigger picture .

I agree that if driving_function_imp_wfs returns the pre-delay as you proposed, the superposition would be simple enough: just use delayline again. Would definitely work for me.
Still I do not consider this as very elegant for the particular case: If (for whatever reason) fractional delays are used with a suboptimal method, you'd have twice the artifacts.
(Though I think this probably doesn't matter much in practice?)
I also agree that it would be cool to have the reference time calculated automatically.

I started testing the current code:
1.) The secondary_source_maximum_distance() function is a nice idea and ready for integration from my perspective. The only think I would like to mention here, is that you should have in mind that for a circle or sphere it will not return the diameter of the circle on which the secondary sources are located, but the maximum distance between the secondary sources, which will be a little bit smaller in most cases. Also the center will then be a little of the actual center of the circle. But in my opinion this is ok, as we are interested in the actual sampled secondary sources.
2.) driving_function_imp_wfs(): I get the point of not applying the automatic delay adjustment and think the implementation via conf.wfs.removedelay is a good idea. For the current implementation of the else case I'm not 100% convinced.
The calculation of the diameter is probably not doing what you intended to achieve. As the x0 you feed into the function are the already selected secondary sources, they are no longer a full circle, sphere, or box, but smaller parts of those. This also means that the checking for focused sources fails in most cases. For example
>> conf = SFS_config;
>> conf.wfs.removedelay = false;
>> sound_field_imp_wfs([-2 2],[-2 2],0,[0.5 0.5 0 -1 -1 0],'fs',200,conf)
error: DRIVING_FUNCTION_IMP_WFS: Using 'config.wfs.removedelay == 0', focused source positions are restricted to the ball spanned by the array diameter.
error: called from
    driving_function_imp_wfs at line 132 column 13
    sound_field_imp_wfs at line 98 column 3

As the actual calculated diameter is not 3m, but only 1.54m for the selected secondary sources.
Before fixing these issue I would like to ask, if this correction is needed at all? I think if the users set conf.wfs.removedelay = false; they have to play around with t anyhow to find the correct time step.

I tested a little bit further and I have to admit, that the code under the else statement in driving_function_imp_wfs() helps if you want to create a plot as you have shown above.

The calculation of the diameter is probably not doing what you intended to achieve. As the x0 you feed into the function are the already selected secondary sources, they are no longer a full circle, sphere, or box, but smaller parts of those.

Sad but true: I completely missed that. Somehow I got into the habit of getting the driving function first and doing the selection afterwards.
A solution would be to pass conf to secondary_sources_maximum_distance instead of x0.

For the preset geometries, the diameter and center can be directly taken from the size and center entries.
That would also solve the problem for spheres and circles that you pointed out.
For custom geometries, if x0 is present in conf, use that. Otherwise revert to size and calculate some upper bound.

Before fixing these issue I would like to ask, if this correction is needed at all? I think if the users set conf.wfs.removedelay = false; they have to play around with t anyhow to find the correct time step.

Do you mean the restriction of possible focused source locations? I think it's nice to ensure that no driving function is cut off in the beginning, which would otherwise happen with open arrays.

I changed secondary_source_maximum_distance() to use now conf, which is an elegant solution as this avoids the problems we have with the secondary source selection in both cases, predefined geometries and custom geometries.
In your example plot, you just have to change one line:
t0 = secondary_source_maximum_distance(conf)/conf.c; % max. travel time

With "if this correction is needed at all" I meant the whole statement after else. But in the meantime I figured out, that it seems to be needed as otherwise it is not so easy to get the result of your figure from above.

Maybe it would be better to rename secondary_source_maximum_distance() to secondary_source_diameter()?

Agreed, that's a better name.
Also maybe minimizedelay would be more precise than removedelay?
One question about array geometries: Is there a consistent definition of size?
(If not, that's fine and probably more convenient for adding other predefined setups.)

The definition of size is a bit tricky. At the moment we have linear, circular, box, rounded-box, and spherical as predefined secondary source distributions, where size is used.
1.) Simple cases:
a) linear: size == length of array
b) circular: size == diameter of array
c) spherical: size == diameter of array
2.) More complicated cases:
a) box: size == length of one linear array element (which is non-identical to the distance between two parallel linear array elements, this one is size + 2*dx0 if I remember correctly)
b) rounded-box: size == remove the round edges and use the definition from box

I prefer conf.wfs.removedelay as the explanation also starts with "Remove the leading delay in WFS-time domain ...". Something like adjustt0 should also be fine, but I'm not sure if everyone knows what t0 should be.
Regarding the renaming of secondary_source_maximum_distance(), what do you prefer:

secondary_source_diameter()
secondary_source_size()

I think, I would go for 2) as the value is more or less identical to conf.secondary_sources.size.

rounded-box: size == remove the round edges and use the definition from box

I am not sure, what you mean by "remove" in that context, but size in this case means the size of the square bounding box around the rounded-box.

@trettberg you are right, there is a small difference between box and rounded-box regarding its diameter, which I was not aware of before. That is the reason why I renamed secondary_source_maximum_distance() to secondary_source_diamter() and not to *_size() as it returns different values in the case of box or rounded-box.
In my opinion the code is now ready for integration into master. I also see no problem to change it afterwards to be more in line with the feature @fietew requested. For this I created a follow up at #61.
If you have no objections I would merge this pull request and close it.

Should be ready to merge.

One last question.
I added a test function test_driving_functions_imp_with_delay in order to check the new delay behavior for conf.wfs.removedelay = false; and used your proposed calculation of t with the only difference that I added 30 extra samples instead of 20.
If you run the test function with test_driving_functions_imp_with_delay(1) a lot of figures will pop up and you will realize that there is a larger difference between focused sources and point source. Is this ok? I guess yes, as you would argue that the impulse has traveled roughly the same time from the position of the virtual source?
Here, an example:

I think this is okay.
To observe the timing, I think it helps to place the point source unreasonably close to the array.
Otherwise, the focussed source is already "all over the place", before the point source even starts.
(For the circular array, the point source distance in the test scenario is 1m, while my initial code example had 0.1m).


[cluster roles] Error 'inaccessibleByURL' when saving cluster roles

Setup

Rancher version: v2.6.4-rc8
Browser type & version: Chrome Version 98.0.4758.80 (Official Build) (x86_64)

Describe the bug
When creating cluster roles, there are 2 errors in the console:
CreateEditView mixin failed to save:   {baseType: 'error', code: 'InternalError', message: 'admission webhook "rancherauth.cattle.io" denied t…: roletemplates.management.cattle.io "" not found', status: 500, type: 'error', …} baseType: "error" code: "InternalError" message: "admission webhook \"rancherauth.cattle.io\" denied the request: Internal error occurred: roletemplates.management.cattle.io \"\" not found" status: 500 type: "error" _headers: {content-encoding: 'gzip', content-length: '180', content-type: 'application/json', date: 'Fri, 11 Mar 2022 14:47:23 GMT', expires: 'Wed 24 Feb 1982 18:42:00 GMT', …} _req: XMLHttpRequest {readyState: 4, timeout: 0, withCredentials: true, upload: XMLHttpRequestUpload, onreadystatechange: ƒ, …} _status: 500 _statusText: "" _url: "https://ronrc8.qa.rancher.space/v3/roletemplates" [[Prototype]]: Object
https://ronrc8.qa.rancher.space/v3/roletemplates 500
To Reproduce

create downstream cluster
hamburger > users & authentication > roles > clusters
complete form and save

Result
Errors thrown. Role appears to save
Expected Result
No errors

Can you validate if this is still an issue.

Thanks @ronhorton

Reported as fixed in 2.6.4 - QA to validate

Pass verified in 2.6-head Commit ID 228a585

create downstream cluster
hamburger > users & authentication > roles > clusters
complete form and save

new role is created with no errors


Opl/rethrow illegal argument exception

Re-throw IllegalArgumentException as CodecException

It sounds there is something wrong. 5 commits to just add 1 word :slightly_smiling_face:

Integrated in master (commit 6a1ff2dad57d3513a4151e83e4d3d3f7032fc632)


rna-transcription: rename "ofDna" with "transcribe"

Ref. #455

@jtigger I think that the issue you mentioned is well related to this PR.  I think it would be great to rename it to dnaStrand.  I'll go ahead and make those changes. :+1:


audio-echo has high input latency because it doesn't use the SL_ANDROID_RECORDING_PRESET_VOICE_RECOGNITION preset

On some devices, such as the Nexus 5X not using this recording preset adds significant input latency (approximately 25ms).
Here's an example of how the preset can be used:
https://github.com/superpoweredSDK/SuperpoweredLatency/blob/master/Android/app/src/main/jni/SuperpoweredLatency.cpp#L122

This is fixed now.


Updating Github actions and files to use main branch. (#1023)

(Cherry picked from commit dc291c2345cdb9885d7b99dff835df08bc3b15fd)
opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1378 (82f2a4f) into opendistro-1.5 (2f1b648) will increase coverage by 0.10%.
The diff coverage is 76.92%.

@@                 Coverage Diff                  @@
##             opendistro-1.5    #1378      +/-   ##
====================================================
+ Coverage             62.72%   62.83%   +0.10%
- Complexity             2950     2963      +13
====================================================
  Files                   229      231       +2
  Lines                 16321    16372      +51
  Branches               3056     3061       +5
====================================================
+ Hits                  10238    10287      +49
+ Misses                 4506     4499       -7
- Partials               1577     1586       +9

Impacted Files
Coverage Δ

...arch/security/ssl/OpenDistroSecuritySSLPlugin.java
82.05% <0.00%> (ø)

...ort/OpenDistroSecuritySSLTransportInterceptor.java
0.00% <0.00%> (ø)

...lasticsearch/security/support/ConfigConstants.java
90.00% <ø> (ø)

...rch/security/setting/OpenDistroDynamicSetting.java
60.00% <60.00%> (ø)

...ticsearch/security/configuration/CompatConfig.java
38.23% <66.66%> (+10.64%)
:arrow_up:

.../security/setting/TransportPassiveAuthSetting.java
80.00% <80.00%> (ø)

...ecurity/configuration/ConfigurationRepository.java
74.54% <80.39%> (+4.84%)
:arrow_up:

...transport/OpenDistroSecuritySSLRequestHandler.java
59.45% <83.33%> (-3.78%)
:arrow_down:

...ty/transport/OpenDistroSecurityRequestHandler.java
69.06% <83.33%> (+1.09%)
:arrow_up:

...arch/security/filter/OpenDistroSecurityFilter.java
64.33% <88.88%> (+3.14%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

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


Adding Swedish keymap to Arch server install script

Adding SE keymap.
Pull Request
Title
Adding Swedish (se) keymap to Arch server install script
Type of Change

[x] New feature
[ ] Bug fix
[ ] Documentation Update
[ ] Refactoring
[ ] Hotfix
[ ] Security patch
[ ] UI/UX improvement

Description
Added Swedish language to the keymap list, lot of languages are in the list but missing Swedish.
Testing
Tested the script independendly, works fine on my end.
Impact
No difference, it's giving more options to the user.
Issue related to PR

Additional Information

Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no errors/warnings/merge conflicts.

@sevu11 Sorry I missed you all! haha, I actually stayed about an hour outside Gothenburg for a month back in the early 2000s. Loved your country!


Filter debug variables

I can only sometimes get debug variables to filter
I am using the vscode-lldb extension and no mater where I click in the variable panel I can't get it to except my input and start filtering.  Is there some trick to where I should click in the panel?
#13201

Version: 1.43.0
Commit: 78a4c91400152c0f27ba4d363eb56d2835f9903a
Date: 2020-03-12T18:47:40.536Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

@blacktop anywhere you click on the variables view and the filtering should just start.
Please note that this feature is disabled when you have a screen reader attached for accessibility reasons, so make sure you do not have "editor.accessibilitySupport": "on"
Can you reproduce with vscode insiders https://code.visualstudio.com/insiders/


🐛 Bug Report: Warns when guest provider is explicitly disabled

📜 Description
With the new backend system, auth-backend-module-guest-provider warns about initialising the guest provider here
https://github.com/backstage/backstage/blob/eec9a51d5e04fffae336d4c231a6acc79b051b8b/plugins/auth-backend-module-guest-provider/src/module.ts#L41
even though auth.providers.guest is set explicitly to null
👍 Expected behavior
There should be no logging when explicitly disabled.
👎 Actual Behavior with Screenshots
The log message You should NOT be using the guest provider outside of a development environment. was outputted
👟 Reproduction steps
Include the following in packages/backend/index.ts:
backend.add(import('@backstage/plugin-auth-backend-module-guest-provider'));

And the following in your app-config.yaml
auth:
  providers:
    guest: null

Run the server with NODE_ENV=production
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

PR here https://github.com/backstage/backstage/pull/24188


⚠ Bofrost.de has degraded performance

In 58228b7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1205 ms

Resolved: Bofrost.de performance has improved in 68c8fc3 after 13 minutes.


[authoring] auto-closing brackets should not place cursor at the end

Automerge issue; pending AM team for information.
Re: https://github.com/dxos/dxos/issues/5358

@richburdon in my testing this has been resolved by #5520


Release 2023-09-14

Description
Generate SDK releases.
Type of change

[x] Release
[ ] Internal refactoring
[ ] Bug fix (bugfix - non-breaking)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Code snippets

See https://github.com/signalwire/signalwire-js/pull/883


Fix broken semgrep lint

The semgrep lint have been broken for a while, let's fix it

Since this tool no longer supports public display of contents, we decied to remove it instead.


Duplication of styles as components grow

I actually faced the problem of @import working on a NuxtJS project and ended up asking Stackoveflow. I then found your library which's a great idea, I thought this would be the solution but the problem remains the same...
When you use your loader, for each component present on the page it'll duplicate the styling on the page, and it'll be visible on the chrome developer tools as referred here https://stackoverflow.com/questions/54793275/global-styling-vs-local-styling-in-vuejs
Is there a way to load the SCSS on top of something and avoid this duplication ? It makes the page way heavier in development...
Thanks
PS: the problem is bigger than what we could think, it confuses the order of the rules in CSS because it loads it from everywhere at random time, so you can hardly make any shared logic at some point ...

Don't styles. Inject only variables.
You can't avoid that styles will leak into all components otherwise :|

Can you explain what you mean by this @manniL ?
Is this causing the duplication?
@include border-radius(1em);


rpm versioning

VSCode Version: 1.1
OS Version: Linux rpm

Steps to Reproduce:
rpm is called vscode-x86_64.rpm
when installing the package is called
code-1.1.1-1463146452
normal convention would be to have the rpm name be the -same- as the package name that's installed and to also add a distribution version in it (el6, el7,...)
so for rhel,centos,ol,scientific Linux,...
it should be 👍
download code-1.1.1-146314652.el7.x86_64.rpm and install code-1.1.1-146314652 or
download vscode-1.1.1-146314652.el7.x86_64.rpm and instal vscode-1.1.1-146314652

one reason to have the version in the main .rpm file is so that I actually -know- what version I downloaded. All I see is vscode-x86-64.rpm that's it. I have no idea whether that's the current version or older version until I would try and install it or run a command like rpm -q --info but that' should not be required.,

Duplicate of https://github.com/Microsoft/vscode/issues/6587, coming in the June release :smiley:


Title for pull request: Update IViewClient.java [before reopen]

Description of forced pull request. Update of description

adding my comment

im rejecting this pr

comment for closed

another comment

another comment 222

komenarz do pull requesta


Other: use precise distribution at travis

Travis CI's linux infrastructure has changed to Trusty distribution, however, it is a bit unstable. Let's stay at Precise meanwhile.

The maintainers of this repo require that all pull request submitters agree and adhere to the following:

[x] I have read and agree to the contribution guidelines.
(required)
[x] All related documentation has been updated to reflect the changes made. (required)
[x] My commit messages are cleaned up and ready to merge. (required)

The maintainers of this repository require you to select the semantic version type that
the changes in this pull request represent.  Please select one of the following:

[ ]  major
[ ]  minor
[ ]  patch
[x]  documentation only

ai....this also failed, so it is not an issue of the trusty distribution


Remove duplicate LNBITS_ALLOWED_USERS

related to https://github.com/lnbits/lnbits/issues/1209

Thank you for this fix!


error using watsontcp with net framework (6.0,6.1,6.2)

good evening and sorry for the inconvenience right now I am using net framework 6.2 which is a net framework compatible with all versions of Windows now there is a problem watson tcp connects to the server without problems but when sending a message it does not send it now yes I install net framework 7 it works without problem could you correct this error

Use.NET (core) https://dotnet.microsoft.com/en-us/download/dotnet/8.0
It's the latest framework. NET Framework 6... 're all outdated.


Devices unavailable

Version of the integration
Newest Version: V2.12.2
Configuration
All are light bulbs
l630: 1.1.0 Build 230823 Rel. 165100 - UK GU10   x 3
l530: 1.1.0 Build 230823 Rel. 163903 - UK E27      x 4
l530: 1.1.0 Build 230823 Rel. 163903 - UK B22      x 1
Image of Log

Describe the bug
Devices keep going unavailable with no explanation. They sometimes come back if I manually reload them but some of them are no longer returning. I have tried power cycling and resetting them to no avail.
Debug log

Home Assistant Core
2024-01-05 15:25:21.815 WARNING (SyncWorker_4) [homeassistant.loader] We found a custom integration tapo 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
2024-01-05 16:11:49.313 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:11:49.425 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:11:49.664 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:11:49.827 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:11:49.930 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-BE-AC-E1 with last ip <IP_ADDRESS>
2024-01-05 16:11:50.131 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-05-67-E9 with last ip <IP_ADDRESS>
2024-01-05 16:11:50.240 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-17-7C-E8 with last ip <IP_ADDRESS>
2024-01-05 16:11:50.385 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-1C-D9-4F with last ip <IP_ADDRESS>
2024-01-05 16:11:54.494 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:11:54.500 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:12:13.582 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.600 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_MEASUREMENT was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.MEASUREMENT instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.618 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.635 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.657 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_ENERGY was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.674 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_POWER was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.POWER instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.691 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_SIGNAL_STRENGTH was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.SIGNAL_STRENGTH instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.708 WARNING (MainThread) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.724 WARNING (MainThread) [homeassistant.const] POWER_WATT was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:13.740 WARNING (MainThread) [homeassistant.const] TIME_MINUTES was used from tapo, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTime.MINUTES instead, please create a bug report at https://github.com/petretiandrea/home-assistant-tapo-p100/issues
2024-01-05 16:12:33.820 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:12:33.944 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-05-67-E9 with last ip <IP_ADDRESS>
2024-01-05 16:12:34.068 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-BE-AC-E1 with last ip <IP_ADDRESS>
2024-01-05 16:12:34.204 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:12:34.293 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:12:34.394 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:12:40.441 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:12:40.465 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:12:50.021 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:12:53.058 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:12:53.171 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:12:53.299 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:13:03.342 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-05-67-E9 with last ip <IP_ADDRESS>
2024-01-05 16:13:03.533 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-62-8B-BE-AC-E1 with last ip <IP_ADDRESS>
2024-01-05 16:13:03.761 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:13:03.841 WARNING (MainThread) [plugp100.api.tapo_client] Default protocol not working, fallback to KLAP ;)
2024-01-05 16:13:16.674 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:13:16.843 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
File "/config/custom_components/tapo/light.py", line 155, in async_turn_on
File "/config/custom_components/tapo/light.py", line 182, in _set_state
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 123, in set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 210, in _set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 78, in execute_raw_request
2024-01-05 16:13:19.751 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:13:19.780 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:13:19.812 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
File "/config/custom_components/tapo/light.py", line 155, in async_turn_on
File "/config/custom_components/tapo/light.py", line 182, in _set_state
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 123, in set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 210, in _set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 78, in execute_raw_request
2024-01-05 16:13:57.562 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:14:00.671 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:14:17.770 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:15:18.202 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:15:24.025 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:15:24.265 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:15:29.947 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:15:46.002 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:15:50.525 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:15:54.074 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:15:55.995 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:15:59.470 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:16:06.576 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:16:10.080 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:16:12.623 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:16:18.128 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:16:27.108 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:16:28.592 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:16:36.567 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:16:48.008 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:16:48.981 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:17:07.525 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:17:29.681 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:18:11.515 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:18:28.098 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:18:50.202 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:19:01.211 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:19:35.190 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:19:48.720 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:20:10.428 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:20:24.693 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:20:58.893 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:21:09.184 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:21:30.951 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:21:45.085 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:22:22.418 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:22:29.911 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:22:51.228 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:23:46.056 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:24:06.081 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:24:09.915 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:24:11.784 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:25:09.719 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:25:32.037 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:25:37.614 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:25:41.680 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:26:30.639 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:26:32.580 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:26:32.654 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:26:33.023 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
File "/config/custom_components/tapo/light.py", line 155, in async_turn_on
File "/config/custom_components/tapo/light.py", line 193, in _set_state
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 123, in set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 210, in _set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 78, in execute_raw_request
2024-01-05 16:26:41.188 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
File "/config/custom_components/tapo/light.py", line 155, in async_turn_on
File "/config/custom_components/tapo/light.py", line 182, in _set_state
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 123, in set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 210, in _set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 78, in execute_raw_request
File "/config/custom_components/tapo/light.py", line 155, in async_turn_on
File "/config/custom_components/tapo/light.py", line 193, in _set_state
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 123, in set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 210, in _set_device_info
File "/usr/local/lib/python3.11/site-packages/plugp100/api/tapo_client.py", line 78, in execute_raw_request
2024-01-05 16:26:43.515 ERROR (MainThread) [custom_components.tapo.coordinators] Error fetching tapo data: Unexpected exception: 'device_id'
2024-01-05 16:26:52.573 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:27:56.542 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:28:02.324 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:28:12.855 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:29:14.110 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:29:19.863 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:29:33.094 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:30:26.833 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:30:43.423 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:30:53.462 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:31:47.090 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:32:06.892 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:32:13.901 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:32:43.347 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:33:30.421 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:33:34.325 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:33:39.746 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:34:03.777 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:34:53.709 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:34:54.508 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:35:18.930 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:35:42.451 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:36:14.860 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:36:17.156 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:36:42.440 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:37:05.967 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:37:35.338 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:37:40.449 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:37:40.623 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:37:42.432 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:37:47.585 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:37:48.858 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:37:49.977 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:37:56.113 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:37:57.608 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:37:58.459 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:38:09.638 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:38:11.018 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:38:11.984 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:38:33.337 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:38:34.683 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:38:35.585 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:38:56.049 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-D7-54 with last ip <IP_ADDRESS>
2024-01-05 16:39:16.689 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-21-5D with last ip <IP_ADDRESS>
2024-01-05 16:39:18.077 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 5C-E9-31-15-CD-AE with last ip <IP_ADDRESS>
2024-01-05 16:39:18.989 WARNING (MainThread) [custom_components.tapo.setup_helpers] No adapter found for 3C-52-A1-9A-1E-A8 with last ip <IP_ADDRESS>
2024-01-05 16:39:47.027 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.071 seconds (success: True)
2024-01-05 16:39:47.991 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.085 seconds (success: True)
2024-01-05 16:39:48.419 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.152 seconds (success: True)
2024-01-05 16:40:04.290 DEBUG (MainThread) [custom_components.tapo.coordinators] Finished fetching tapo data in 0.093 seconds (success: True)

It would be worth checking the Wi-Fi Signal of the device.

Do you happen to have your IP address change? It looks like you have added these devices before and for some reason your IP address has change and is no longer the same and TP-Link Tapo integration can no longer handle. Try remove and add back.

I have the same issue with P100.
Yesterday I installed two new P100 plugs on my network. I downloaded the TAPO app to my android phone to do the installlation to my network.
I gave the two P100 fixed IP-addresses.
I plugged the two P100 in the wall outlets and testet the system, worked fine.
Installed HACS and the TAPO integration yesterday. Installed two P100 and the worked fine on installation. Made an automation with the two P100 to turn on and off at specific times, but both P100 went unavailable before the first run was expected.
Today I notice both P100 are unavailable in HA. But they work fine from the TAPO app, so no issues with WiFi. I also have other WiFi units where the plugs are, a camera that is working fine with streaming video.
If I go into the TAPO integration and reload the plugs, it says it Fails.
I have double checked the IP-address for both P100 and they are correct.
How do I go about finding out the problem and fixing it?
Thanks!

It would be worth checking the Wi-Fi Signal of the device.

theyre all medium to max signal.

I just noticed a discrepancy in my case
My TAPO android APP reports the following for the plug
FW ver. 1.2.1 Build 230804 Rel. 190922
But HA reports
Firmware: 1.1.0 Build 220720 Rel.163239
The strange thing is that the plugs where updated to the last FW version even before I began the HACS and TAPO integration installations in HA.

ill try setting the ips to static then but even with the track ip with mac address turned on they do it. i reset them all and added them again and so far no issues. this time i didnt tick the track ip with mac option

Ok, so in my case, I deactivated the plugs, then I activated them again and HA told me to restart HA, so I did. And now they are back up again and HA is now reporting the same FW version as the TAPO app.
So I assume this had something to do with the plugs fw update, perhaps not taking place immediately but later on in the background.

Please upgrade to 2.13.0


Add organizer to workgroup is missing - in Safari 8.0.3 (works in firefox et al)

Somehow the option to add an organizer for a work group has gone missing. We need to add it back asap and put to PROD as users are stuck at this point.

@dottorer this should be restored in master branch now. let me know if you want me to push out to staging.

@dottorer: I cant seem to replicate this in any environment. I even "became" a prod user that seemed to have the issue and could not replicate. @kristysnet was thinking you meant the multiselect we had before private groups on the main settings page of a working group.
I can edit organizers by going to the organizers tab in the working group settings.

Are you sure that the user is on the right tab of the working group settings?
Just a note: the drop down is not shown if there are no other members available to be added to the working group members/organizers list. aka: all users in the circle are a member/organizer of the working group.

So we don't want the old multiselect back. But i did a skype with Tasha yesterday where i confirmed the issue and could not set her as a group organizer. I will try to replicate today again and provide more precise rep instructions, if still persisting.

@phil-monroe I debugged this with Tasha today. This is indeed a problem with Safari 8.0.3 that does not render the drop down list and add button to pick a workgroup organizer. We switched to firefox and it was all shown as expected.
Strange only that you tested this in Safari as well and it showed up....

@dottorer can you send a screenshot of the missing elements? I'm not seeing anything obvious in the code and I have no way of pulling up the site in an older version of safari.

Dont think i have a screen shot fron Tasha but it is showing the 'No volunteers' message for the list but nothing under it. So the dropdown list of helpernames and the button are not appearing.

Setting Prio to low; don't want to be chasing browser ghosts unless the users report this in a clearly replicable way...putting on hold for now...

Closing as 'Could not reproduce'...


Module Blacklisting: excluding experimental module from both exposed-modules and other-modules

Is there any way to blacklisting modules, i.e. to exclude specific module from both exposed-modules and other-modules?
This is useful when we develop some experimental functionalities in specific module, e.g. Lib.Great.New, but we don't want it to compiled.

The only ways to achieve this is by either specifying both exposed-modules and other-modules explicitly or by placing that "experimental" module into a separate source directory.

This is a question that has been answered.  I'm closing this issue.  If you want any specific changes to hpack then please open a separate issue for that.


Can i intergrate FirebaseUI - FirebaseListViewAdapter with Material Search Bar ?

Android device: Redmi Note 4
Android OS version: 7.0
Google Play Services version: 11.4.2
Firebase/Play Services SDK version: 11.4.2
FirebaseUI version: 3.1.0

Describe the problem:
How can i use MaterialSearchBar (https://github.com/mancj/MaterialSearchBar) to search for user or other things on Firebase Realtime Database ?
I have thought about using Firebase UI for Android to get Firebase ListView Adapter then BindViewHolder with ListView of Search Bar . Is it possible to do this way ?
Thank you

This question should probably be posted on SO, but I'll give you a short answer here.
I've briefly looked at MSB's source code and it looks like they require you to extend their custom adapter. So basically, you can't use any of the Firebase adapters. Either way, I don't think search suggestion content needs to be realtime! 😆 Instead, just add a text watcher with some sort of time filter so you don't get too many events and queue up a query for each event. Then, just use MSB's setSuggestions with whatever the result of your query is.

Thanks @SUPERCILEX for giving it a stab and yes @edenleeee this sort of thing should be posted on StackOverflow, so I'm going to close this issue.
We try to reserve github issues for potential library bugs or feature requests!


To Staging: Change to multiple Guides (Manually triggered)

Updated by github actions, triggered Manually.

Changes will be applied when guides need to be updated


Connecting to real robot

Hello. This might sound like a naive question but I'm not able to figure this out from the documentation.
I have a myCobot-pi model and it has ROS-Kinetic pre-installed on it.
When I run:
rosrun mycobot_ros slider_control.py
I get the error: unable to connect to "/dev/ttyUSB0"
My question is if I'm running ROS on the robot's RPi, do I need to specify the port?
Secondly, if I'm running ROS core on my laptop instead, don't I just need to specify the IP address of the ROS core machine for the robot's nodes on the RPi? Why do I need to connect with a USB cable?
Please let me know if I'm missing something or point me to some good documentation.

Have you tried ' /dev/ttyAMA0 ' ?

My question is if I'm running ROS on the robot's RPi, do I need to specify the port?
Re : Have to specify the port if you want to connect the machine
Secondly, if I'm running ROS core on my laptop instead, don't I just need to specify the IP address of the ROS core machine for the robot's nodes on the RPi? Why do I need to connect with a USB cable?
Please let me know if I'm missing something or point me to some good documentation.

Also, you can tried ' sudo chmod 777 /dev/ttyUSB* ' , hope this commang would help you.

Hello. This might sound like a naive question but I'm not able to figure this out from the documentation.
I have a myCobot-pi model and it has ROS-Kinetic pre-installed on it.
When I run: rosrun mycobot_ros slider_control.py
I get the error: unable to connect to "/dev/ttyUSB0"
My question is if I'm running ROS on the robot's RPi, do I need to specify the port?
Secondly, if I'm running ROS core on my laptop instead, don't I just need to specify the IP address of the ROS core machine for the robot's nodes on the RPi? Why do I need to connect with a USB cable?
Please let me know if I'm missing something or point me to some good documentation.

Please make sure that you follow the tutorial correcttly : https://www.elephantrobotics.com/docs/myCobot-en/3-development/4-ros&moveit/
These two commands should be executed in independent terminal windows before you run the rosrun command:
roscore and roslaunch mycobot_ros mycobot_slider.launch
Then run the rosrun mycobot_ros slider_control.py command in another terminal window.
Also you should check the connection between your laptop and the mycobot RPi, make sure the ports and the cable are in good condition.
As for the IP address, because of the serial interface is used in the connection between the laptop and robot, specifying the IP address is not necessary to the recognition and doesn't make sense.
Hope your problem has been addressed.


feat(sdk): verify credential and did wellknown JS api.

Codecov Report
Patch and project coverage have no change.

Comparison is base (aa5bcbb) 89.53% compared to head (ebc6234) 89.53%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #523   +/-   ##
=======================================
  Coverage   89.53%   89.53%
=======================================
  Files          93       93
  Lines        3690     3690
=======================================
  Hits         3304     3304
  Misses        257      257
  Partials      129      129

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

feat(sdk): verify credential and did wellknown JS api

Is in the PR title and commit title. It should be

feat(sdk): verify credential and did wellknown JS API

Instead.


Hope Yolo model can be added in pretrained models

❓ Questions and Help
Please note that this issue tracker is not a help form and this issue will be closed.
We have a set of listed resources available on the website. Our primary means of support is our discussion forum:

Discussion Forum

Hi,
We are planning on adding RetinaNet to the models soon, but there is currently no plans for YOLO.
Note that both RetinaNet and YOLO are single-stage methods, but RetinaNet is more accurate so should cover more cases (given a fixed backbone).
The PR adding RetinaNet can be found in https://github.com/pytorch/vision/pull/1697
As such, I'm closing this issue but let me know if you disagree.

Thank you very much.


Firebase integration.

Integrate with firebase.

Login with google.
Retrieve data.

Integrated firebase authentication
Integrated firestore
Integrated storage


KVM flag defaults to false with current Proxmox API Go

Proxmox API Go added the Qemu KVM flag recently. Since the Terraform Provider is not currently setting it to anything, it gets defaulted to false when creating or cloning a VM. This should be getting defaulted to true.

Did a fresh install of the provider and (at least for my quick VM clone test) seems to be working fine now!


Broken generated image from decoded data

I have decoded this file: Link and the output is Preview or Download
the source code for getting image/png file is:
/** buffer is of type ArrayBuffer which is read from sample file */
const tiffIfds = decode(buffer);

const first = tiffIfds[0];

const canvas = document.createElement("canvas");
canvas.width = first.width;
canvas.height = first.height;

const ctx = canvas.getContext("2d", { alpha: first.alpha });

const imageData = ctx?.createImageData(canvas.width, canvas.height);
imageData?.data.set(first.data);

ctx?.putImageData(imageData!, 0, 0);

const pngImage = canvas.toDataURL("image/png");

const imgEl = document.getElementById("my-image") as HTMLImageElement;

if (imgEl) imgEl.src = pngImage;

and the HTML markup is simple as:

The problem is that you cannot just set the image data like that, because this tiff file has only three channels (RGB, no alpha). ImageData objects always contain RGBA data.

The problem is that you cannot just set the image data like that, because this tiff file has only three channels (RGB, no alpha). ImageData objects always contain RGBA data.

So how can i convert such image to image/png base64?
Any clue would be helpful. Thank uou

You can use image-js:
import { Image } from 'image-js';
const img = await Image.load(data);
const url = img.toDataURL()

Feel free to ask more questions, but I'm closing this issue because the data returned by the decoder is correct.


Extra_data Validate Error in Admin

My django version is 1.3,social auth version is 0.6.0.
#1
when I change the extra_data for a UserSocialAuth instance in the django admin site, I got a validation error!
the extra_data value is set to:
{"access_token": "xxxxxxxx&yyyyyyyy", "friends": "", "account_name": "jeff"}
after press the save button , I got a validation error:
expected string or buffer.
#2
the extra_data before update as below:
{u'access_token': u'xxxxxxxx&yyyyyyyy', u'friends': '', u'account_name': u'jeff'}
it is not a valid json format, but I can read and write extra_data in the shell or script if I use admin site,other exception will be riase:
File "/lib/python2.6/site-packages/social_auth/fields.py", line 25, in to_python
raise ValidationError(str(e))

Fixed on https://github.com/omab/django-social-auth/commit/7ae03e087298e52a9db9655d450af4c3fd82efc3

omab, accessing Exception.message is deprecated since Python 2.6. You should use e.args[0] or str(e).

Thanks @sorcio. Fixed on https://github.com/omab/django-social-auth/commit/6cc074f8764f69ceaf490af2c0d2bdeae9310c30


Ignore dart_linter_active if dart_enable_analysis_server is turned on?

The new plugin version ships with "dart_enable_analysis_server": true, but I still had "dart_linter_active": true, in my User settings.
When I saved my file, it looks like the batch analyzer still ran.
If  "dart_enable_analysis_server": true, then should we ignore "dart_linter_active": true, ?

Good catch. I'll make the fix and deprecate the linter's event-based operation.


Validator Apis: avoid unknown block root error in fallback urls setup

Motivation

Due to the fallback urls setup in validator, "unknown beacon block root" error may happen if data is produced from one beacon node and published to another beacon node since HttpClient will call all beacon urls in parallel
Even through the final HttpClient call is a success, we may see "unknown beacon block" error from both beacon node and validator client, this is not good for UX
See https://github.com/ChainSafe/lodestar/issues/5098#issuecomment-1427504993

Description

We already have an API to wait for head block when validating gossip attestations
Refactor that API to make it generic and use it for concerning validator APIs
Affected APIs:

submitPoolAttestations
publishAggregateAndProofs
produceSyncCommitteeContribution

This change does not affect single beacon node url setup, it only affects fallback urls setup
It does not affect the flow or anything, the main thing is for UX improvement: users will not see these "unknown block" errors most of the time

part of #5098
related to #5063
Closes #5152

would like @dapplion input on this

:tada: This PR is included in v1.6.0 :tada:


Empty the value of searchbar from controller

Hello, I'm new to Angular and I need help with this module.
I need to erase the string inside autocomplete component after item is selected, or space/enter key pressed. I use events itemSelected when item is selected and ionAutoInput when space is pressed - but it is not fired on enter key. I have 2 questions:

How can I bind event to enter key press when focused to autocomplete component?

How can I erase (make it empty) string inside autocomplete component from my controller?

Thanks!

Will you help me, please? I assigned the model with ngModel but two way data binding is not working when I erase the model in controller.
And by event key press I meant tapping search (confirm) button on mobile keyboard.
Thank you.

same question.

ok got the solution:
Component Mapping to Controller
@ViewChild('nameFilter')nameFilter: AutoCompleteComponent;
Controller method code
this.nameFilter.clearValue();

Wonderful, thanks, now it works :) :+1:
And what about capturing submit event?

Input fields don't have submit events, forms and buttons have it. You can use nameFilter.getValue() inside your submit() function to get the selected value in AutoCompleteComponent .

But I think it's still bug. The two-way binding by NgModel should work well.


Updated all references to old Repo Address for NavCoin github current url

Updated the gitlian-linux.yml Repo Address for NavCoin
I think this only works because github does auto redirect of old repo URL?

yes, navcoindev is the old account but i guess craig linked them. approved for merge

I think that it should match the repo url exactly as RFC for urls is case
sensitive.
I guess if we want we could rename the repo to lowercase as it is better
looking as a URL.
On Sun, May 5, 2019, 17:52 alex v<EMAIL_ADDRESS>wrote:

@aguycalled commented on this pull request.
I prefer the lowercase writing of navcoin in the context of an URL, are
there some guidelines for this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NAVCoin/navcoin-core/pull/463#pullrequestreview-233771545,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIDAKMAWQSVBQENFPOMNRLPT2U4LANCNFSM4HJ7EQ2Q
.

yes, i would rather rename the url @craigmacgregor

repo URL has been renamed to navcoin all lower case. please update PR

organisation URL has been renamed to navcoin all lower case. please update PR

I've updated the PR

approved, re-running travis then will merge when it passes.

The job exceeded the maximum time limit for jobs, and has been terminated.
:/


[Uploaded model] Depth-Anything-Small metric depth model

Hi, just letting you know I've trained Depth-Anything-Small for KITTI metric prediction (10 epochs).
Feel free to re-use/finetune it or put it in the repo:
Wandb run
HuggingFace checkpoint
Metrics:

Method
$\delta_1 \uparrow$
$\delta_2 \uparrow$
$\delta_3 \uparrow$
AbsRel $\downarrow$
RMSE $\downarrow$
log10 $\downarrow$

ZoeDepth
0.971
0.996
0.999
0.054
2.281
0.082

Depth Anything Large
0.982
0.998
1.000
0.046
1.896
0.069

Depth Anything Small
0.971
0.996
0.999
0.053
2.267
0.023

Model size:

Method
model size (MB) $\downarrow$

Depth Anything Large
1 344.4

Depth Anything Small
101.6

怎么推理

Are the existing depth values and key values incorrect?
When I use DepthAnythingV2 class and call load_state_dict function for use the model, I get Error
"Error(s) in loading state_dict for DepthAnythingV2: 	Missing key(s) in state_dict"

I want to use a model you've created,
but in the new model you made, there are additional parameters like
"conv2.weight", "conv2.bias", "seed_bin_regressor._net.0.weight", "seed_bin_regressor._net.0.bias", "seed_bin_regressor._net.2.weight", .....

and so on. Because of this, I'm unsure how to properly load the model. When using DepthAnythingV2 and attempting to use load_state_dict, I encounter the following error:
RuntimeError: Error(s) in loading state_dict for DepthAnythingV2:
	Unexpected key(s) in state_dict: "conv2.weight", "conv2.bias" ......

How can I resolve this issue?

For metric depth, we need to load the weights using the metric_depth code. You can follow this file to use the weights.
Here is how I use it in my project, where the process_image function returns numpy array of metric depths: LINK.

@lukasz-staniszewski  Hi, thanks for sharing the trained model! Can you share the config_zoedetph.json file you used to train it? Thanks a lot!

@lukasz-staniszewski Hi, thanks for sharing the trained model! Can you share the config_zoedetph.json file you used to train it? Thanks a lot!

I'm pretty sure I didn't change the file, and it's the same as this one. However, there is also config_zoedepth_kitti.json, and I'm not sure which one is the exact one used under the hood.


'': is not true.

I/flutter ( 3071): 'dart:ui/painting.dart': Failed assertion: line 187: '<optimized out>': is not true.

Such errors are popping up recently in Flutter issues

https://github.com/flutter/flutter/issues/25396
https://github.com/flutter/flutter/issues/25325
https://github.com/flutter/flutter/issues/23512

I assume the failing expression should still be shown.

@zanderso @aam I think we had an existing bug about the assert snippets lacking source?

https://github.com/dart-lang/sdk/issues/34586

Duplicate of #34586

I had the same problem.

If you use .then() clauses don't use await.
.then() and await are two different ways to handle Future's but shouldn't be used for the same Future instance. you can split them and link them with a variable if you wish

E/flutter ( 5337): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: 'dart:ui/window.dart': Failed assertion: line 284: '': is not true.
E/flutter ( 5337): #0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:42:39)
E/flutter ( 5337): #1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:38:5)
E/flutter ( 5337): #2      new Locale (dart:ui/window.dart:284:15)
E/flutter ( 5337): #3      _EasyLocalizationState.saveLocale. (package:easy_localization/easy_localization_provider.dart:58:24)
E/flutter ( 5337): #4      State.setState (package:flutter/src/widgets/framework.dart:1148:30)
E/flutter ( 5337): #5      _EasyLocalizationState.saveLocale (package:easy_localization/easy_localization_provider.dart:57:7)
E/flutter ( 5337):
E/flutter ( 5337): #6      _EasyLocalizationState.initState (package:easy_localization/easy_localization_provider.dart:36:5)
E/flutter ( 5337): #7      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:4355:58)
E/flutter ( 5337): #8      ComponentElement.mount (package:flutter/src/widgets/framework.dart:4201:5)
E/flutter ( 5337): #9      Element.inflateWidget (package:flutter/src/widgets/framework.dart:3194:14)
E/flutter ( 5337): #10     Element.updateChild (package:flutter/src/widgets/framework.dart:2988:12)
E/flutter ( 5337): #11     RenderObjectToWidgetElement._rebuild (package:flutter/src/widgets/binding.dart:1028:16)
E/flutter ( 5337): #12     RenderObjectToWidgetElement.mount (package:flutter/src/widgets/binding.dart:999:5)
E/flutter ( 5337): #13     RenderObjectToWidgetAdapter.attachToRenderTree. (package:flutter/src/widgets/binding.dart:942:17)
E/flutter ( 5337): #14     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2412:19)
E/flutter ( 5337): #15     RenderObjectToWidgetAdapter.attachToRenderTree (package:flutter/src/widgets/binding.dart:941:13)
E/flutter ( 5337): #16     WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:819:7)
E/flutter ( 5337): #17     WidgetsBinding.scheduleAttachRootWidget. (package:flutter/src/widgets/binding.dart:804:7)
E/flutter ( 5337): #18     _rootRun (dart:async/zone.dart:1122:38)
E/flutter ( 5337): #19     _CustomZone.run (dart:async/zone.dart:1023:19)
E/flutter ( 5337): #20     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
E/flutter ( 5337): #21     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:965:23)
E/flutter ( 5337): #22     _rootRun (dart:async/zone.dart:1126:13)
E/flutter ( 5337): #23     _CustomZone.run (dart:async/zone.dart:1023:19)
E/flutter ( 5337): #24     _CustomZone.bindCallback. (dart:async/zone.dart:949:23)
E/flutter ( 5337): #25     Timer._createTimer. (dart:async-patch/timer_patch.dart:23:15)
E/flutter ( 5337): #26     _Timer._runTimers (dart:isolate-patch/timer_impl.dart:384:19)
E/flutter ( 5337): #27     _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418:5)
E/flutter ( 5337): #28     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)
E/flutter ( 5337):


Chapter recurrent neural networks/language models and dataset

Job d2l-zh/PR-783/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-783/

Job d2l-zh/PR-783/2 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-783/


issue #28 fixed; Small fix for PercentPlayed tracing for ajax websites/playlists

Fixed warning
"VIDEOJS: WARN: this.options() has been deprecated and will be moved to the constructor in 6.0"

This fixed it for me, thanks!

Few more commits!

Hi
Can this PR merged please ?


Redundantly Wrapped startFormTags()

When scaffolding out a new object, I noticed the following...
view/{controller}/new and view/{controller}/edit files are created with a similar structure...
#startFormTag()#
	#includePartial("form")#
	#submitTag()#
#endFormTag()#

Inside the _form.cfm partial is something like this...
#startFormTag()#
	<!--- form helper functions & markup --->
	#submitTag()#
#endFormTag()#

Because of this, the result is two forms, one nested inside the other, and two submit buttons.
I'd like to submit a PR on this, but it's not immediately obvious where I'd make this change. My first thought was to edit the /templates/crud/_form.txt file, but it appears that the CLI does all the magic within there. So, where's that magic happening?

Weird, that shouldn't happen.
commands/scaffold.cfc just calls a bunch of wheels generate x commands;
So it's the /generate/ folder you'd want to look at, probably /generate/view.cfc which just reads a file from the template directory and then replaces all the placeholder tokens

@geirman can you let me know what specific sequence of commands you ran. I’m trying to reproduce the error.

@bpamiri Sorry Peter, this was soo long ago and I've slept many times since then and cannot recall. Sorry for not documenting the steps to duplicate this issue better when those details were fresh. Also sorry for dropping the ball on the PR I promised. (shame)

@bpamiri Sorry Peter, this was soo long ago and I've slept many times since then and cannot recall. Sorry for not documenting the steps to duplicate this issue better when those details were fresh. Also sorry for dropping the ball on the PR I promised. (shame)

@geirman No worries Chris. I’m actively working on the CLI so if you run across anything let me know.


TypeError with example code

I am just running the following code but even this seems to throw an error for me...
import agent from 'secret-agent';

(async () => {
	await agent.goto('https://example.org');
	const title = await agent.document.title;
	const intro = await agent.document.querySelector('p').textContent;
	await agent.close();

	console.log('Retrieved from https://example.org', {
		title,
		intro,
	});
})();

I then run yarn start which pointts at this file node index.js but then I just get the following error
user@computer:~/Documents/projects/myproject$ yarn start
yarn run v1.22.10
$ node ./src/test.js
2021-05-02T14:59:10.343Z ERROR [/home/username/Documents/projects/myproject/node_modules/@secret-agent/core/index] UnhandledErrorOrRejection {
  clientError: "Error: TypeError: Cannot read property '0' of null\n" +
    '    at new ObjectAtPath (<anonymous>:212:38)\n' +
    '    at Function.exec (<anonymous>:128:30)\n' +
    '    at <anonymous>:1:53',
  context: {},
  sessionId: null,
  sessionName: undefined
} TypeError: Cannot read property '0' of null
    at new ObjectAtPath (<anonymous>:212:38)
    at Function.exec (<anonymous>:128:30)
    at <anonymous>:1:53
------CONNECTION----------------------------------
    at Object.createPromise (/home/username/Documents/projects/myproject/node_modules/commons/utils.ts:39:10)
    at RemoteConnectionToCore.createPendingResult (/home/username/Documents/projects/myproject/node_modules/client/connections/ConnectionToCore.ts:310:31)
    at RemoteConnectionToCore.internalSendRequestAndWait (/home/username/Documents/projects/myproject/node_modules/client/connections/ConnectionToCore.ts:237:43)
    at RemoteConnectionToCore.sendRequest (/home/username/Documents/projects/myproject/node_modules/client/connections/ConnectionToCore.ts:149:17)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at CoreCommandQueue.runRequest (/home/username/Documents/projects/myproject/node_modules/client/lib/CoreCommandQueue.ts:41:22)
    at Queue.next (/home/username/Documents/projects/myproject/node_modules/commons/Queue.ts:70:19)
------CORE COMMANDS-------------------------------
    at Queue.run (/home/username/Documents/projects/myproject/node_modules/commons/Queue.ts:27:19)
    at CoreCommandQueue.run (/home/username/Documents/projects/myproject/node_modules/client/lib/CoreCommandQueue.ts:30:31)
    at CoreTab.execJsPath (/home/username/Documents/projects/myproject/node_modules/client/lib/CoreTab.ts:62:36)
    at execJsPath (/home/username/Documents/projects/myproject/node_modules/client/lib/SetupAwaitedHandler.ts:115:18)
    at Object.getProperty (/home/username/Documents/projects/myproject/node_modules/client/lib/SetupAwaitedHandler.ts:31:24)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at AwaitedHandler.getProperty (/home/username/Documents/projects/myproject/files/2-finalized/awaited-dom/base/AwaitedHandler.ts:23:12)
    at file:///home/username/Documents/projects/myproject/src/test.js:5:16

--------------------------------------------------
------default-session-----------------------------
------f2745720-ab56-11eb-8440-cb8dd35f1f7a--------
-------------------------------------------------- {
  isDisconnecting: false
}

many thanks for this as I have been able to see some parts working like the browser display and getting past some anti-bot control ! The hardwork hasn't gone unnoticed and I'm hopeful with this! (If I could get past this part)
I've tried with the latest alpha and also gone back as far as 1.4.0-alpha.0
{
  "name": "project",
  "version": "1.0.0",
  "main": "index.js",
  "author": "me",
  "license": "MIT",
  "type": "module",
  "scripts": {
    "start": "node index.js"
  },
  "dependencies": {
    "secret-agent": "^1.4.1-alpha.4"
  }
}

OS: ubuntu 20.04

Thanks for reporting this. I accidentally broke this with a new version of awaited-dom: older versions of SecretAgent were allowing for minor versions to be resolved to the new breaking version. I'm going to push out a new release that fixes the awaited-dom version to the correct dependency.
You can fix in the interim by "pegging" awaited dom (add the following to your package.json:
"resolutions": {
        "awaited-dom": "1.1.12"
    }

Thanks for reporting this. I accidentally broke this with a new version of awaited-dom: older versions of SecretAgent were allowing for minor versions to be resolved to the new breaking version. I'm going to push out a new release that fixes the awaited-dom version to the correct dependency.
You can fix in the interim by "pegging" awaited dom (add the following to your package.json:
"resolutions": {
        "awaited-dom": "1.1.12"
    }

:joy: I just spent the last 3 hours digging down into awaited-dom trying to debug it...That worked! thanks Blake!

Oh geez. 🤦 Sorry..
Glad it worked.

No stress :) - I'm actually just really happy that you've been able to respond today!

I saw it come through and knew we fixed this in main shortly after that last release. Then I realized we never did the follow-on release, as we're still working through reorganizing the browser-emulators so they're easy to fork.
I just pushed out the new version too that pegs awaited-dom (1.4.1-alpha.5). Gonna go ahead and close this one. Thanks again!

I'm experiencing the same error, but it's basically anytime I try to 'click'. For example, await agent.interact({ move: email }, 'click'); where email is a result from document.querySelector. I added "resolutions" to the package.json but that didn't change anything. That field should be at the top level of the package.json right?

@H0r53 I think you might be running into a different error. If you change that to await agent.interact({ click: email }), do you see something different?

That did seem to work, although the example I referenced came from the docs at https://secretagent.dev/docs/basic-interfaces/interactions/#using-shortcuts which I'm guessing are out of date?

🤦 Yes.. I was going to say, what you're trying to do makes sense... I just don't think we know how to handle an empty click right now.

I sorta get it, basically every interaction is in simple JSON format and you can specify multiple via comma delimiting. Cool! Seems like a good product, although it looks like it's being detected by anti bot services.

Thanks!
Yeah, there are still a few holes at the moment. Your mileage may vary based on the site in question though (most sites are still fine).
CreepJS is kind of a theoretical kitchen sink of tests. The ones that are currently being detected are javascript level problems that every single tool using proxies are running into right now, and will be fixed in Chrome 91. We have a workaround right now, but it's still too slow to push out.
The CloudFlare issue has a workaround too, but needs some work to be ready for primetime.

Sorry to bump this thread, but do you have any details you can share about the Chrome 91 fix and how it helps in general? Thanks!

You can currently detect javascript Proxy objects by creating classes that extend them. The stack trace and error message convert overridden functions to a different value than a normal function: https://github.com/ulixee/secret-agent/issues/203
Chrome 91 has a patch that fixes the underlying issue in v8.