Implement TcpListener::accept()

Would something like this be accepted? I'm aware it's not an idiomatic way, but sometimes there's a need to just attempt to accept one connection. My need is to support fibers/coroutines as Futures, where a fiber is accepting connections one by one: https://github.com/dpc/tokio-fiber/blob/aef185bac414fb1745e2c1addf813fae981dc71e/examples/echo2.rs#L51

I'd be totally down for having this! Perhaps through a Handle could be passed in to avoid the dance with oneshot, spawn, and wait?

TBH, I'm not sure if I fully understand the whole Handle & Remote thing. From my (user) perspective it might be an inconvenience, as fibers / coroutines are considered thread-like, so things inside them must be passed as Send. And as Handle is not Send, so one have to use a Remote and then do similar "dance" manually. So if I understand it right, I would have to change: https://github.com/dpc/tokio-fiber/blob/aef185bac414fb1745e2c1addf813fae981dc71e/examples/echo2.rs#L51 line  to include such "dance"
Similar problem with TcpListener::bind. I guess some wrapper that do the dance and returns the value back could be created. Or two invocations provided - one taking Handler, one that doesn't need it and do the "dance" .

A Handle is basically just a standard handle to an event loop. With one you can create I/O objects or otherwise send messages to the event loop. The critical difference, however, is that Handle cannot be sent across threads whereas a Remote can be. Because a Remote can be sent across threads it has less functionality than a Handle unfortunately, and primarily only allows spawning futures rather than creating I/O objects directly.
The problem with the current construction is that in theory accept is nonblocking but it is in fact blocking. If that code path is executed on the event loop itself it risks blocking the I/O thread.
The solution would be to pass in a Handle directly to define which event loop the accepted connection should be accepted with. It's a bit wonky, yeah, unfortunately. I wonder, presumably you'd want easy interoperation between fibers and futures, right? That is, while executing a fiber, if handed a future it should know how to wait for the future in a "cooperative" fashion?

I wasn't aware that accept can block. I expected it to just resturn WouldBlock if there's nothing to accept.
Yes. The goal is to do exactly what the https://github.com/dpc/tokio-fiber/blob/aef185bac414fb1745e2c1addf813fae981dc71e/examples/echo2.rs#L51 is trying to do - have a code that is just like a blocking, threaded code, that just cooperatively jumps out of coroutine, when its blocked.

Oh well mio's accept method doesn't block. The one you've written here blocks because it calls Future::wait.
If the future interop is possible then I see a few possible solutions here:

With the future interop enable stream interop, enabling usage of incoming.
Take a &Handle argument to associate accepted connections.
Modify this method to track the internal state of the spawned future. That is, keep the impl roughly the same as it is today, it just calls poll on the spawned future in accept sometimes if one was previously scheduled.

Ah, I see what you mean now. I was considering that wait harmless, but now I see it isn't.

Is definitely on my list.

However what if accept returned a future resolving to TcpStream? Do you think it would work OK with other usage? Since tokio-fiber already has await, the coroutine code would change from:
 let (mut conn, _addr) = poll!(socket.accept())?;

to
 let (mut conn, _addr) = await(socket.accept()))?;

Yeah accept could return a future for sure. That may be the best option in the end. I was hoping to keep the I/O operations all pretty consistent amongst one another in the sense that currently they all just operate in the standard fashion (return an io::Result) where an error is returned on "would block". If we were to return a future from accept it'd be a deviation from that as that method would return a future rather than an io::Result.
I will say though this looks pretty slick:
let (mut conn, _addr) = await(socket.accept()))?;

There can be multiple versions (with handle, returning socket, and another not taking handle but returning future). Let me know what version would you be willing to merge ATM (it can be changed later too, I guess) and I'll modify the PR accordingly.

Hm so thinking some more, I don't think this should return a future because then we have to deal with the semantics of what happens if you call it twice in a row, and in general that's what the incoming stream is for anyway.
Additionally I don't think this should take a Handle as that would be inconsistent.
Let's see if we can have this signature (as is in this PR) but change the implementation to keep ahold of the spawned future and poll that on future calls to accept.
Does that sound ok?

Sure. I will give it a try.

I had to make it &mut self. I think it's consistent with other IO operations (read and write). Alternatively RefCell could be used.

Looks great to me! Could the incoming method also be defined in terms of this method calling accept?

Oh. Haven't thought about it (plus I was too shy to touch existing code). Will check.

Oh sorry I missed the update here! Looks good to me, so merging.

Er nvmd this was literally just updated as I looked at it, what a coincidence!

Yeah. You're fast. :)

Should I bother with removing that one boxed?

Ah it's ok it was easy enough to just push up locally, so I've already done so now.


Add support for DLS Term Lookup Queries

Signed-off-by: Jochen Kressin<EMAIL_ADDRESS>opensearch-security pull request intake form
This PR adds support for Term Lookup Queries (TLQ) in Document-level security. It introduces two different modes for executing DLS filters which can either be set in opensearch.yml or are chosen automatically by Opensearch Security.
Lucene-level DLS
This mode implements DLS by modifying Lucene queries and data structures directly. This is the most efficient mode but does not allow certain advanced constructs in DLS queries, including TLQ. This is how DLS works currently.
Filter-level DLS
With this mode, DLS is applied by modifying queries as received by OpenSearch. This allows the use of term lookup queries in DLS queries but limits the set of operations that can be used to retrieve data from the protected index to get, search, mget, msearch. Also, the use of Cross Cluster Searches is limited in this mode.
By default, OpenSearch Security will detect if a DLS query contains a TLQ or not, and chooses the appropriate mode automatically at runtime. The mode can also be set explicitly in opensearch.yml:
plugins.security.dls.mode: <lucene-level | filter-level | adaptive>

lucene-level: enforces that all DLS queries are applied on Lucene-level. This is the current implementation
filter-level: enforces that all DLS queries are applied on filter level
adaptive (default): OpenSearch chooses the mode automatically. DLS queries without TLQ are executed on Lucene level, while DLS queries that contain TLQ are executed on filter level.

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

Enhancement / New feature

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

#1508

Description of changes:

As described above, this PR introduces two different approaches to executing DLS queries.

Why these changes are required?

TLQ in DLS queries can only be supported if the query is executed on filter level.

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

If a DLS query contains a TLQ, an exception is thrown. Now a DLS query can also contain a TLQ. Per default, Opensearch Security detects a TLQ and sets the corresponding mode automatically.

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

Executed existing tests and added new tests for TLQ (DlsTermLookupQueryTest).

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

If this PR is accepted the documentation needs to be updated accordingly.

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

No.
Additional notes:

I excluded the transitive dependency to JUnit5 from spring-kafka-test in pom.xml. This was causing issues when running the Junit4 unit and integration tests in Eclipse
For the integration tests, I disabled the high disk watermark checks. I think it is not necessary to have this on during the tests, and it caused some hard-to-spot issues when running the tests locally.

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.

Thanks @jochenkressin! In addition to addressing the comments above, this test seems to be failing (and based on the name could be related to these changes)

Codecov Report

Merging #1541 (ec5d7a9) into main (ff40615) will decrease coverage by 1.29%.
The diff coverage is 49.38%.

@@             Coverage Diff              @@
##               main    #1541      +/-   ##
============================================
- Coverage     64.59%   63.29%   -1.30%
- Complexity     3214     3307      +93
============================================
  Files           247      253       +6
  Lines         17352    18126     +774
  Branches       3082     3249     +167
============================================
+ Hits          11208    11473     +265
- Misses         4594     4999     +405
- Partials       1550     1654     +104

Impacted Files
Coverage Δ

...rch/security/configuration/DlsFlsRequestValve.java
0.00% <ø> (ø)

...opensearch/security/filter/SecurityRestFilter.java
76.66% <ø> (+0.80%)
:arrow_up:

...pensearch/security/securityconf/ConfigModelV6.java
27.81% <0.00%> (+0.31%)
:arrow_up:

...g/opensearch/security/support/ConfigConstants.java
94.44% <ø> (ø)

...search/security/queries/QueryBuilderTraverser.java
19.08% <19.08%> (ø)

...security/support/ReflectiveAttributeAccessors.java
22.22% <22.22%> (ø)

...nsearch/security/privileges/DocumentAllowList.java
39.69% <39.69%> (ø)

...search/security/configuration/DlsFlsValveImpl.java
58.17% <54.28%> (-12.06%)
:arrow_down:

...ity/configuration/DlsFilterLevelActionHandler.java
55.50% <55.50%> (ø)

...search/security/transport/SecurityInterceptor.java
75.38% <57.69%> (+1.43%)
:arrow_up:

... and 32 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 ff40615...ec5d7a9. Read the comment docs.

@jochenkressin Could you resolve the merge conflicts so we can merge this PR?

@peternied I rebased to main

LGTM!
Re-trigerring CI.
Please squash the commits and remove all unnecessary texts in the commit message upon merging.

@cliu123 @peternied I removed the references to log4j from the PR


Ability to Wait on Lock to Expire

I need to rate limit some outgoing requests. Therefore, I would like the ability for tasks to queue up to only go out at a metered rate. The way, I suppose, to do this would be to simply have a configuration option to wait for the lock to expire instead of just giving up.
Can this be achieved as the library is now, or would this require a new feature?
Basically, I want to do what the StorageBasedLockProvider does except that it waits and tries again to acquire the lock.

Hi, yes, you can do that. You can create a your LockProvider, wrapping the original one and do whatever you need there.


Trying to fix upstream aka GenevaERS/Community master branch being behind my local and my origin

Merge pull request #25 from AOrthVector/master
I think

gonna try something else


Skip verify imagemagick plugins for asan builds

I agree we need to be careful disabling things like this.  In this case, we are only skipping for ASAN builds and only skipping the plugin verify, which doesn't exercise any code, only confirms the .so was linked correctly.  We aren't skipping any unit tests or really any code testing here.  Its just due to some strangeness around libmagick.  These tests will certainly happen on production builds that enable testing.

Cherry-picked to v10.0.x


Add monthly meetings section

Added new section to blogs and backfilled through 2023 - https://deploy-preview-94--sparkling-souffle-4f78b0.netlify.app/blog/monthly-calls/

@TomScarboroughYMCA this is all fixed up now. Thanks for flagging it!


gulp: Compress keyword lists?

Motivation
Almost every language definition has some kind of keyword list. With keyword list I mean a list of words (usually keywords) with are concatenated via alternations and surrounded by a word boundary. Example: C keywords, Python built-ins, C-like class-name prefixes.
Especially long keyword lists tend to contain a fair amount of redundancy. This can be used to compress the keyword list to decrease the overall files.
Description
The idea is to use common prefixes and suffixes of the keywords to compress the regex.
I.e. return|returns can be compressed to returns? and get|let|set can be compressed to [gls]et.
We could then use gulp to detect such keywords lists and automatically compress them to further decrease the size of minified files.
By leaving the compression to gulp we can enjoy readable keyword list regexes while also keeping the size of the minified files small.
Current progress
I actually already implemented most of the necessaries of this to work. The average compression rate is about 85-90%, so not very good but most keyword lists only contain ~100 keywords. The compression works best for really long list >500 words. With a lot of words, compression rates of up to 50-60% are possible.
I'm currently implementing more advanced compression strategies, so the compression rate will probably go down by 2-5%.
The only problem is that this is quite slow. It will probably add another 30s to the current build process.

So do we even want this?
It takes quite some time and the average compression rate isn't too good but language definitions which mostly consist of keyword lists profit immensely.

Ouch 30s is a lot though! You said this improved code size, but have you had the chance to check the performance? If we were to implement such a compression, we need to make sure it does not hurt the performance of the regexps.

I forgot to close this.
As suggested, I made a few performance tests and my results showed the compressed patterns are about 2x slower than uncompressed ones. At a compression of only ~85% it's not worth it.


add locale-flow for dev only

Add ailoc from hackathon to dev view in sidekick
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/?martech=off
After: https://ailoc-sidekick--express--adobecom.hlx.page/express/?martech=off

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7982826) 31.92% compared to head (f035e17) 31.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #520      +/-   ##
==========================================
- Coverage   31.92%   31.75%   -0.17%
==========================================
  Files         126      124       -2
  Lines       24002    23811     -191
==========================================
- Hits         7662     7561     -101
+ Misses      16340    16250      -90

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


Claims should all be accessible from the result

Current implementation only includes a subset of claims in the result and we should output all the claims that were found in the token.

merged


Idea for pdb based debugger

@dbaeumer I just realized this morning that we may have a miscommunication on the repo for this. Thought I'd just put this up to show it, while I work on moving this to the other repository.

Closing in favor of https://github.com/microsoft/vscode-python-web-wasm/pull/16


Train list & Evaluation list

Anyone can help with the train list and evaluation list?
From where I can find these both lists?
@joonson @dvisockas

They are daraset dependent. If you'll look into the Data section of the readme - you'll find links to get the voxceleb datasets and both links should be there

Thank you @dvisockas. Sorry, previously I did not notice that.


please tag and version this project

Hello,
Can you please tag and version this project?
I am the Debian Maintainer for http-link-go and versioning would help Debian keep up with development.

This code has not been touched in three years and it's unlikely that any meaningful changes will be merged. Also, as a general rule we don't do version numbers for our libraries.

For Deban its hard to keep up. I have to personally come and see if there is a new commit. However, we have scripts that checks for tags (Fedora also has this).
Just tagging a 1.0 release and creating a new tag when and if something new is merged will ensure that Debian packages depending on http-link-go are updated. This is relatively low efforts and will benefit distros.


Replace static userx_demo/test passwords

Replace cactus1/2 with generated password everywhere

Done in PR #1429


Questions about the implementation

After reading the blog by Preshing I am still confused about something.

The C++11 atomic library standard does not guarantee an efficient implementation, only a correct one.

No offense. Why can you provide a better implementation against the compiler? Mintomic's interfaces and compilers' are totally same, it is impossible to have a better implementation without changing the interfaces.

Well he can, if the C11 atomic library is not efficiently implemented. Just as it says. Think of it of being mostly academic.

@mulle-nat I had a glance on its implementation, but not sure if it has a big different with the "popular" implementation. If system level locks are not involved with the atomics(i.e. x86, ARM, etc.), is it nothing different with atomics provided by compilers?

I think Preshing would agree with you on that: https://github.com/mintomic/mintomic/issues/11. I use mintomic as a fallback, when I don't have C11 available

@mulle-nat
C11 is not available in the latest Visual Studio 2015 yet, so far I have to use the C++11's atomics instead of C11's, but I am wondering if I can make a recap of C++11's atomics into pure C. For example, providing pure C header files as well as C++ source files(compiled to library), then we can have it!

@mulle-nat See you in 10 hours, it is really late in China(12:30 AM). I am interesting in Mintomics. Because stdatomics is not available in Visual Studio, an alternative is to use Mintomics or pure C header files with C++ implementation in source which I mentioned in context. #11 told ARM64 is not supported in Mintomics, so it is not a good choose to use Mintomics for all platforms. Maybe I am wrong about stdatomics, I googled it but found no explanation about it. But Visual Studio does provide a xatomic.h I don't know if it works.

Yeah, that ARM64 doesn't work is not so great. Someone recommended concurrencykit to me, but I haven't checked it out

Why can you provide a better implementation against the compiler?

Back when std::atomic was first added to Visual Studio 2012, it generated pretty bad code (at least in my own testing). It's part of the reason I started Mintomic.
These days, modern compilers do an excellent job with std::atomic in C++11. I would not claim Mintomic is better, only equal.
I haven't really spent time with C11, so I can't comment on that.

@preshing Thanks, I read your blogs a lot and appreciate it. By the way, even if the latest VS 2015 we don't have stdatomic.h available yet, but xatomic.h as well as customized APIs for Win.

@preshing I think I shouldn't ask you questions here, but still do it: why we don't have a StoreLoad barrier but memory_order_seq_cst(it promise more things)?

A StoreLoad fence is quite slow in hardware, so the CPU instructions that do it also tend to provide the other fence types too.

@preshing I don't totally understand. When CPU does only a full-barrier, it ensures all intrinsics are sent in program sequence. If we want a sequentially consistent, the CPU does the same and must wait until the memory or all the caches are updated. In my imagination, it must be more costly than a full-barrier. Besides, I think StoreLoad is expensive because Store is always slower than Load, if we force CPU to complete a Store, it must be a longer pipeline stall, am I right?

Are you asking about sequentially consistent fences, such as std::atomic_thread_fence(std::memory_order_seq_cst)?
Or are you asking about sequentially consistent loads and stores, such as std::atomic<>::store(, std::memory_order_seq_cst)?
They're different things. The comment I wrote about was talking about sequentially consistent fences. But now it sounds like you're trying to figure out how CPUs implement sequentially consistent loads/stores.

@preshing
Oops......took a mistake, sorry. I think the questions is becoming two subquestions:

Why don't we have full-barrier version Load/Store?
Why don't we have full-barrier fence?

If I understand right, you answered 2) and told the full-barrier fence will not much cheaper than sequentially consistent fence, so CPU rather provides the second one but not only the first one. I am not an expert of this field, please excuse for my simple mistakes. I think:
a) Modern multi-core CPUs can always ensure memory/caches synchronization in single CPU.
b) MESI protocol is powerful enough to make sure the expense of memory/caches synchronization between CPUs is not such expensive.
So, "CPU rather provides the second one but not only the first one.". And we always use memory fences to achieve well-ordered Load/Store, so it makes no difference in many CPUs between sequentially consistent fences and sequentially consistent Load/Store.

In addition: I mean the full-barrier by LoadLoad+StoreStore+LoadStore+StoreLoad.

Sequentially consistent loads and stores are a bit less expensive, though. They don't always need fences. For example, on x86, a sequentially consistent load is implemented as a simple MOV instruction. No explicit CPU fence of any kind. And it works. See http://preshing.com/20120930/weak-vs-strong-memory-models/
See also https://www.cl.cam.ac.uk/~pes20/cpp/cpp0xmappings.html

@preshing I have read that blog, and learning the link below now. But still curious, what's the costs between LoadLoad+StoreStore+LoadStore+StoreLoad and sequentially consistent? In other word, assuming there are two sets A={LoadLoad+StoreStore+LoadStore+StoreLoad}, B={sequentially consistent}, what scenarios are included in {A-B}? Such like MESI fails, or, even if using Acquire/Release, do we always have {A-B} (means all memory/caches are synchronized)?

Sorry, I'm not able to answer your question.
As for atomics in C, I've basically moved all the Mintomic code to Turf, so I encourage you to keep an eye on this subfolder to see if it fits your needs: https://github.com/preshing/turf/tree/master/turf/c


Crash when turn on notification wirdget

Hello!
After installation i can set Widget 5 to "Notifications".
But after, if I change some settings in "Other features" it crashes down.
Working only if notification widget not used.
For example widgets for crash:
1- weather Icon
2- steps
3- watch alarm
4- battery %%
5- Notifications
Bar - Steps
Features:
resolution +
flashing -
month txt +
3 letters month +
3 letters day +
No 0 +
wind as arrows -
show status bar -
animate -
always am/pm -
Official firmware <IP_ADDRESS> (Startos)

I've detected, when notifications non empty it works well, when it's empty -> crash

I can't replicate the problem (at least with the latest amazmod), however, I am monitoring it.


Access forbidden

Hey Amey100,
Are you getting this error after going through the Google Authentication window? or before that?

Also, are you getting this when you try using the template? or when you're using the connector by itself? I'd highly recommend that you make sure that your API is set up correctly as that error is often caused by either:

The API not set up correctly
Your query trying to access data that you don't have access to (like revenue data of another youtube channel)

This custom connector grabs the information of the primary channel of the authenticated user, so when you do the sign in operation, the connector automatically finds your primary channel and will only give you information related to that channel.

I am  getting this error after going through the Google Authentication window

will try the process again

Hello Miguel... is it possible to grab data from other channel different from Primary?.  Is there access to some ‘channel definition’ parameter that can be modified as user level?
Thanks!

Hey Alex,
Check out this one for a more comprehensive explanation about the subject.
You could also modify the project to your specific needs (specifically the line 145), so you can define the specific channelId that you want to get data from, but at this time I've paused all the development on this connector until the Custom Connectors reach GA where I'd need to validate a bunch of connectors (including this one) to make sure that they are ready to be published to the Power BI Service.

hmm... I'm not sure. This channel administered from the account, which I use to login in power bi. But I'm not the owner.

I'd probably recommend that you try changing that part of the code for DailyVideoStats to be:
= YoutubeAnalytics.VideoStats(StartDate,EndDate, false)
that last optional parameter asks you if you're a partner or not. The template that I created is intended for channels that are partnered since they'll have monetary information that others channels won't.
If you try querying monetary information from a channel that is not partnered then you'll get some errors.
Let me know if this helps out.

It helped! Thank you so much.


[T5A1][T13-B2] Gao Yu

Ready for review.

@GaoYu-Karen : Some comments added. Please close the PR after reading comments.


UAT | Security Bug | Join a case code visible

Code to join a case along with additional case details available in network tab when searching for a case during the join a case process flow.
cc: @subhashini-egov @atul

@manimaarans please add @Exclude annotation for the accesscode field so that is not sent as part of response.
@Ramu-kandimalla @suresh12 this is a 1 line change. should be taken up ASAP

@atulgupta2024 if we exclude in code, then it would not be possible to test this flow in UAT unless the summons deliveries are implemented, i.e. some sms at least

let's ignore the issue since the access code is publicly visible on notice/summons anyway. and no one can sniff it over the wire. once the summary API is in place, the access code will not be visible at the time of join a case as well for anyone to find that out from the response info.
@Ramu-kandimalla @anirudh-0 @suresh12 @subhashini-egov - my vote is to close this ticket.

Concur with Atul on the decision to close this ticket.

closing


Room

[X] Set up Room
[X] Refactored RecyclerView
[X] Modified AddTask to utilize local DB (not working yet though)
[X] Set up Details Page to show Task Description and Title (set up but not showing, will debug tomorrow in Remo)

Because this is not complete I did NOT take any new screenshots.
However, I did build 5 tests for custom methods in the code.

Completed implementation of Room DB, added more unittests, updated espresso tests, added color, cleaned up code a little, and updated the README.


fix: change BaseBermission class declaration

I adopted the change from upstream, in particular from this commit:
https://github.com/typeddjango/djangorestframework-stubs/commit/a1ec425434daf5e392e1d640bddca1486d4c98f9
AFAIK, this is due to the changes introduced mypy 0.991.

As a side note (to my self): To test this PR locally, I used the CI/CD image and scripts defined in this repository as follows (I am on NixOS, so I didn't want to bother setting up a new Nix shell etc.):
## Run CI/CD container this repository uses (Docker images as stated in `.circleci/config.yml` file):
docker run -it --user "$(id -u):$(id -g)" -v "$(pwd):/myapp" circleci/python:3.7-node /bin/bash

## Change the directory:
cd /myapp

## Install requirements (as stated in `.circleci/config.yml` file):
export PATH="$PATH":"$HOME"/.local/bin
python -m pip install --user poetry==1.1.9
poetry config virtualenvs.in-project true
poetry --version
poetry install
yarn install --frozen-lockfile --non-interactive

## Run lint:
./s/lint

thank you!

Wow, so fast! Thank you, indeed.


Add support for Automated payment of OC/AP members

Implement blockchain part related to tc-payments contract.
TODOs:

Store and instantiate this contract in the chain. That means, a contract "upgrade" proposal for tc-payments.
Modify tgrade so that it calls this contract's end blocker. That means, a tgrade chain upgrade proposal.
Modify valset distribution so that it sends the engagement funds to this contract instead to the engagement contract. That means, a valset contract upgrade proposal, as the distribution list is currently not part of the update config mechanism (https://github.com/confio/poe-contracts/issues/182).

Release 0.14 of tgrade-contracts is required beforehand.

Modify tgrade so that it calls this contract's end blocker. That means, a tgrade chain upgrade proposal.
No need to upgrade the chain. When when.a contract is promoted to "privileged" (via gov proposal), a callback to the contract is sent to let it register for chain permissions (end blocker in this case).

Modify tgrade so that it calls this contract's end blocker. That means, a tgrade chain upgrade proposal.

No need to upgrade the chain. When when.a contract is promoted to "privileged" (via gov proposal), a callback to the contract is sent to let it register for chain permissions (end blocker in this case).

Nice! Didn't knew that.

Release 0.14 of tgrade-contracts

The repo was tagged 3 days ago. ( https://github.com/confio/poe-contracts/releases/tag/v0.14.0) do you mean v0.15 ?

tc_payments is part of tgrade-contracts, not poe-contracts. This requires a new release of tgrade-contracts, yes. I can do it.

The only problem is that that gov proposal is currently unimplemented at the voting contract level (https://github.com/confio/poe-contracts/issues/158).
Will implement that, and we would finally have a route for storing, instantiating, promoting and wiring the payments contract.

Ok thanks. So it looks like there isn't anything that needs to be done on the blockchain side.
@maurolacy have you had a chance to implement PromoteToPrivilegedContract?

Yes, this is already done (see https://github.com/confio/poe-contracts/pull/188).
In fact the validator-voting contract with these changes is already deployed and migrated. See proposal #8 in tgrade mainnet.

See the following slab doc for detailed progress / data for this: https://confio.slab.com/posts/tgrade-tc-payments-deployment-on-mainnet-j8k6iz27.


Adding ability to reset and run indexer.

I would like to propose an idea and change in the same time to give the plugin ability to reset and run indexers.

Hi @piotrgradzinski - thanks for creating this PR! The code changes look good to me. I will test this out and try to get it in for our next release of the extension. Thanks again!


Support streamed chunking (fixing #531 and others)

query() will now return a generator of ResultSets instead of a list when setting chunked=True. This might be backwards incompatible, but seems to be the only reason one might even use chunked mode?
Another reason to use chunked mode could be that the server enforces it, but then again: If results are that big, wouldn't you want a generator as well?

i'll try to fix the test as well

I think it would be cleaner to add a "stream" parameter to get a streaming response. This way we wont breakn compatibility. Perhaps there are also some usecases where someone wants to autonagically combine a chunked result in memory, like it is currently working.

All set and done now. there a new stream parameter to support "streamed chunking". this is usefull for very large result sets. (trying to traverse and anaylse over 20 million+ results here) Also updated/added documentation in the sourcecode.
related project: https://github.com/psy0rz/meowton

@psy0rz thank you for the patch! would you mind adding a test to this PR?

Ok will do that soonish..

Hi, I believe that someone forgot to actually resolve the conflicts.
@xginn8 do you mind finishing this merge PR?

also i dont have time to add the requested regressions tests.

If the author does not have the time to finish the PR then someone has to pick it up. I'll close this one and merge the other, if it is complete and includes tests.

"Potentially break the api" ;) Dont worry you can be harsh, I would apply the same policy in your case.

I had picked that up from your initial comment saying it could be backwards incompatiblte but this is not t he case due to the steam parameter, is it?

yes, but still i could have made a mistake :)

Any solution for this? returning a query with millions of rows will affect memory badly.

returning a query with millions of rows is still impossible on 2019-08-01. @pedrofaria09 @aviau


[FINCN-345] Collections API Improvements

https://mifosforge.jira.com/browse/AL-54

This PR mentions or links to a closed source issue Tracker. Even the commit message is misleading. Please can we correct this?


wrap has to be stateless?

In the docs for wrap it is stated that "It is assumed that f is stateless (this will therefore not work with closures).". Is this strictly true? Could you explain why this is necessary? Is it related to purity?

TimeDag needs to be able to manage state internally — among other things, making the same call to evaluate twice (with the same node(s) and time range) should always give the same answer.
If you wrap some function that depends on (or, especially, mutates) some external state, then this property can be violated — since effectively you now have an object which could give different answers when called for a second time with the same arguments.
It gets worse if you were to wrap multiple things depending on the same global state, and if you were to depend on the order of evaluation, since TimeDag reserves the right to evaluate things in whatever order it likes :)

Currently any state is represented as an instance of a struct which inherits from NodeEvaluationState. It is possible to make wrap handle statefulness, but then it starts to look quite similar to just creating the node "by hand". See e.g. history: https://github.com/invenia/TimeDag.jl/blob/main/src/ops/history.jl#L1-L39
It might be possible to remove a small amount of boilerplate by expanding wrap, although I'm in two minds about whether it'd be a good thing.

I see. I guess I'm imagining a use-case in which there's no risk of the "state" associated with your closure changing over time (so the closure is best thought of as a member of a parametric family of (pure) functions).
Something like:
function make_closure(a)
    my_closure(x) = a + x
    return my_closure
end
wrap(make_closure(5.0))

My reasoning being that there's no risk of accidentally mutating the a field of any given instance of my_closure.
Or could this still potentially cause problems?

julia> TimeDag.wrap(make_closure(5.0))
(::TimeDag.Wrapped{var"#my_closure#9"{Float64}(5.0)}) (generic function with 1 method)

So this is actually fine, because 5.0 is immutable. And it works! But
julia> TimeDag.wrap(make_closure([5.0]))
ERROR: TypeError: in Type, in parameter, expected Type, got a value of type var"#my_closure#9"{Vector{Float64}}

blow up in some cryptic way (I don't know why so cryptic), basically because it's had to actually create some kind of closure object.

I guess in this particular case we, the user, know it's fine because [5.0] is an rvalue (to use C++ lingo) — i.e. the local frame doesn't have a reference to it, so can't mutate it. I have no idea if Julia can detect the difference between
f([5.0])

and
x = [5.0]
f(x)

I don't think that Julia can tell the difference unfortunately.

blow up in some cryptic way (I don't know why so cryptic), basically because it's had to actually create some kind of closure object.

Ah interesting -- I see why this is the case. You've got an interesting implementation for Wrapped! To be honest, I'm not totally sure why your implementation works for the closure at all. I guess Julia is smart enough to know it's a singleton or something....
Anyway, if you implemented Wrapped as
struct Wrapped{Tf} <: Function
    f::Tf
    time_agnostic::Bool
end
@inline function (wrapped::Wrapped)(x, rest...; kwargs...)
    return apply(wrapped.f, x, rest...; time_agnostic=wrapped.time_agnostic, kwargs...)
end

I imagine the more complicated closure with an array in could be made to work.

So the reason that Wrapped is implemented the way it is is to ensure that the compiler knows the function & value of time_agnostic at compile time — basically this permits some rather crucial inlining, since they are depended upon in the inner loop in the alignment code. Without this, you end up with moderate overhead from runtime switching&dispatch... (I vaguely remember noting something about this on the docstring to time_agnostic and related functions).
Possibly we could have something more permissive for non-function types (i.e. closures / callable objects), although I still worry about mutability guarantees. I consider it a feature that it doesn't allow things like x=[5.0]; wrap(make_closure(x)); x[1] = 6.0 :)
Down the line it might also end up being handy when thinking about parallelising schedulers too — I imagine life gets a lot more fiddly if we want to permit arbitrary closures, perhaps?
I am aware that (generally) I err on the side of strictness where possible, just to remove cases I need to think about.

But I'd also say that I definitely think we could make writing stateful node ops a little less boiler-plate-y, if/when that ends up being annoying.


Avoid homekit cast exception since null is not an expected temperature

Apple homekit cannot handle null as temperature and throws an exception (seen in debug log). Therefore use 0 as default instead.

Would it be better just not to set this, if we don't have a value?
if(this.latestSamples.data.temp)
  this.temperatureService.getCharacteristic(api.hap.Characteristic.CurrentTemperature).updateValue(
     this.latestSamples.data.temp
  );

sounds reasonable. Will check it as soon as possible.

works lika a charm so far. Thanks @davidjbradshaw for the review and the change suggestion


Mod won't launch

I don't know why
(00:27:24) Java version: Oracle Corporation, Java(TM) SE Runtime Environment, 1.8.0_371-b11
(00:27:24) System: windows 7, 6.1, x86
(00:27:24) Version RubyDungSquared has an invalid `file-ver` parameter.
(00:27:24) Loaded in: 175540194 ns
(00:27:24) java.io.FileNotFoundException: C:\Users\ASUS\Desktop\.betacraft\launcher\launch-methods\preclassic
(00:27:24) .jar (The filename, directory name, or volume label syntax is incorrect)
(00:27:24) 	at java.util.zip.ZipFile.open(Native Method)
(00:27:24) 	at java.util.zip.ZipFile.<init>(Unknown Source)
(00:27:24) 	at java.util.zip.ZipFile.<init>(Unknown Source)
(00:27:24) 	at java.util.jar.JarFile.<init>(Unknown Source)
(00:27:24) 	at java.util.jar.JarFile.<init>(Unknown Source)
(00:27:24) 	at org.betacraft.launcher.Launcher.loadClasses(Launcher.java:296)
(00:27:24) 	at org.betacraft.launcher.Launcher.main(Launcher.java:219)
(00:27:24) Launch method: preclassic
(00:27:24)
(00:27:24) java.lang.ClassNotFoundException: preclassic
(00:27:24)
(00:27:24) 	at java.net.URLClassLoader.findClass(Unknown Source)
(00:27:24) 	at java.lang.ClassLoader.loadClass(Unknown Source)
(00:27:24) 	at java.lang.ClassLoader.loadClass(Unknown Source)
(00:27:24) 	at org.betacraft.launcher.Launcher.main(Launcher.java:221)
(00:27:25)
Client closed.

probably because i fucked something up when exporting the latest version, i'll check whenever i have time. thanks for reporting

should be fixed in 1.2_01


ConnectionError: Couldn't reach https://raw.githubusercontent.com/huggingface/datasets/1.15.1/datasets/wmt16/wmt16.py

when I use python examples/pytorch/translation/run_translation.py     --model_name_or_path examples/pytorch/translation/opus-mt-en-ro     --do_train     --do_eval     --source_lang en     --target_lang ro     --dataset_name wmt16     --dataset_config_name ro-en     --output_dir /tmp/tst-translation     --per_device_train_batch_size=4     --per_device_eval_batch_size=4     --overwrite_output_dir     --predict_with_generate to finetune translation model on huggingface, I get the issue"ConnectionError: Couldn't reach https://raw.githubusercontent.com/huggingface/datasets/1.15.1/datasets/wmt16/wmt16.py".But I can open the https://raw.githubusercontent.com/huggingface/datasets/1.15.1/datasets/wmt16/wmt16.py by using website. What should I do to solve the issue?

Hi ! Do you have some kind of proxy in your browser that gives you access to internet ?
Maybe you're having this error because you don't have access to this URL from python ?

Hi，do you fixed this error?
I still have this issue when use "use_auth_token=True"

You don't need authentication to access those github hosted files
Please check that you can access this URL from your browser and also from your terminal


Cursor flickers for no reason

I haven't traced down the exact culprit but I have totally eliminated 100% of my own config and just symlinked .tmux.conf and .tmux.conf.local right to your repo and I am getting cursor flicker that doesn't happen with vanilla tmux or my own home grown config

http://g.recordit.co/vbFnfcltZl.gif gif recording -- I'm giving no input to cause this

Hello @chrisjohnson 👋
I have no idea at that point. I suspect it's caused by the commands launched from the status line.
If it's the case, it means doing:
:set -g status-left ''
:set -g status-right ''

will stop the "flickering".

Also noticing this. Is there any update?

I removed the battery indicator completely from the right status bar and the problem went away:
~/.tmux.conf.local
tmux_conf_theme_status_right='#{prefix}#{pairing}#{synchronized}, %R , %d %b | #{username}#{root}'


Amorphous definition

Periodic structure is not present for e.g., quasicrystalls, though they are not amorphous (see attachment).

The definition should probably include absense of the lattice structure locally.

Addressed in https://github.com/OCDO/cmso-ontology/commit/4573278e73009eb486e113bb915eec557dc49dfa


Remove compose in favor of encode

By now, the compose workflow operation is doing an exact subset of the
encode workflow operation which universally can be used as a drop-in
replacement.
In addition to the functionality of compose, encode supports parallel
encoding as well as the adaptive encoding profiles but these are
additional features and using the same configuration as compose, encode
works identical. It even uses mostly the same code internally.
So, there is no real reason to keep compose around any longer. That is
why this patch drops it.
Your pull request should…

[ ] have a concise title
[ ] close an accompanying issue if one exists
[ ] be against the correct branch (features can only go into develop)
[ ] include migration scripts and documentation, if appropriate
[ ] pass automated testing
[ ] have a clean commit history
[ ] have proper commit messages (title and body) for all commits
[ ] have appropriate tags applied

@pascalseeland, did you test this? In that case, I could merge this.

@lkiesow Yes, I did a checkout of the PR and it did encode my testvideos without issues.

Signing off on this given @lkiesow and @pascalseeland's results.


collection_type field

It would be handy to enforce collection_type s such as 'mixed', 'channels', 'playables', 'photos', etc. because

then they can be displayed and filtered by type,
a 'channel list' can be made to only include channels, etc. and
so that less logic is required to route a collection to its proper display,
we don't have to get and inspect every claim to be sure what the type intention was (initially, we load the first (5) claim items).
it's impossible to know whether the intent is for a mixed list.

Alternative to having a type field:
Collections are anything-goes. Collections created on one device force a guess as to the intentions when pulled to another device OR the entire list must be inspected claim by claim.

Team suggested that sdk should derive current type from all claims before sending collection with collection_type so that app knows what's in it without ~resolving~ all the claimids.
This would be acceptable.
Create UX: Originally I imagined that when creating a list for a specific content type, they would make a choice. Perhaps not? App can make the same assessment of collection type for local unpublished / edited lists.
Update UX: When user goes to add a file to an existing list, they should initially only see matching types unless "show all" or such.
Types:
All existing stream-types plus some combo types such as playable, and channel types.
audio, video, audio/video, mixed, images, models, docs, etc.
Display UX: App reads collection type to load the appropriate display mode.

My original idea was that users specify the type, sdk stores the type and enforces all additions, but I'm persuaded that that's bad ux.
Possibly all of the above questions dissolve except the hub burden if the collection claim simply returns
collection_claim_types = [...stream_types, ...claim_types].
I can't answer the hub burden question.

Inspecting the claims on publish/update and inserting a list of claim and stream types present would be fine as well.


Port L2a -> L2b JPL II&T code:  Subtract master dark

@mygouf, @kjl0025, do we need something special here, or is what we currently have in the l2a_to_l2b.dark_subtraction() good enough (pending the update to propagate errors)?

Hi @JuergenSchreiber, we should probably look through the II&T pipeline for dark creation to see if there is anything more optimal we should be doing than just a simple mean of the dark frames: https://github.com/roman-corgi/cgi_iit_drp/tree/main/Calibration_NTR/cal/calibrate_darks.  Perhaps you can consult with @kjl0025 on slack, since he wrote those functions for II&T.

Sorry for the delayed response.  The plan for the master dark for Roman is to take many stacks of frames, where each stack is taken at a particular exposure time and EM gain.  Essentially, that module you linked (calibrate_darks) takes all these stacks, subtracts the bias, converts from DN to e-, corrects for cosmic rays, averages each stack, and then does a fit for every pixel over the range of averaged frames for the fitting function s = FPN + gaintimedark current + gain*CIC.  From this, a synthesized master dark can be created for any given exposure time and gain.  And the plan is to use the synthesized master dark in the frame processing pipeline.  I can work on porting that over if you'd like.

Thanks for the explanation! Ok, just to clarify the output: the final "master dark" calibration will be the fitted coefficients for each pixel to determine the dark current for any arbitrary exposure time?
For the purpose of the dark creation function, we can ssume that the bias is subtracted, converted to e-, and corrected for cosmic rays (other functions that other folks will write), so all we need to do is to average each stack and then do the fitting.
I'll ping both of you on slack to discuss coordination.

I think, we should call this issue differently, like "generation of  master dark calibration file", which is not a pipeline step. The pipeline step dark subtraction we already have, (well, maybe minor updates needed). As far as I understand, Issue #65 should implement a function that generates the master dark (that should be subtracted) out of the coefficients of the calibration file.

I'm going to close this issue, because I think the subtraction step is done, it's just the generating the right dark that is not, which is covered by issue #65.


Bug:login for Honeywell Home

Describe The Bug
my username and password aren't recognized and clicking the forgot password button says the account isn't recognized
To Reproduce
trying to complete the configuration
Expected behavior
login success
Relevant log output
Loading logs using native method...
File: /Users/cwmn/.homebridge/homebridge.log

current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:26:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.96V] current current [0A].
[11/12/2021, 11:26:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.96V] current current [0.00A].
[11/12/2021, 11:27:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.04V] current current [0A].
[11/12/2021, 11:27:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:27:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:28:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.96V] current current [0A].
[11/12/2021, 11:28:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.96V] current current [0.00A].
[11/12/2021, 11:29:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.12V] current current [0.00A].
[11/12/2021, 11:29:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.97V] current current [0A].
[11/12/2021, 11:29:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.98V] current current [0.00A].
[11/12/2021, 11:30:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.8V] current current [0A].
[11/12/2021, 11:30:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.80V] current current [0.00A].
[11/12/2021, 11:31:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.80V] current current [0.00A].
[11/12/2021, 11:31:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.8V] current current [0A].
[11/12/2021, 11:31:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.80V] current current [0.00A].
[11/12/2021, 11:32:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:32:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:33:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.92V] current current [0.00A].
[11/12/2021, 11:33:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.88V] current current [0A].
[11/12/2021, 11:33:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.88V] current current [0.00A].
[11/12/2021, 11:34:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:34:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:35:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:35:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.10V] current current [0.00A].
[11/12/2021, 11:36:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.84V] current current [0A].
[11/12/2021, 11:36:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.84V] current current [0.00A].
[11/12/2021, 11:36:49 AM] [Simplisafe] Warning: Authentication with username / password is expected to cease to function on or after December 2021. Please re-authenticate using newest method. See README for more info.
[11/12/2021, 11:37:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.72V] current current [0.00A].
[11/12/2021, 11:37:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.72V] current current [0A].
[11/12/2021, 11:37:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.72V] current current [0.00A].
[11/12/2021, 11:38:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.96V] current current [0A].
[11/12/2021, 11:38:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.96V] current current [0.00A].
[11/12/2021, 11:39:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:39:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.04V] current current [0A].
[11/12/2021, 11:39:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:40:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.04V] current current [0A].
[11/12/2021, 11:40:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:41:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.28V] current current [0.00A].
[11/12/2021, 11:41:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.22V] current current [0A].
[11/12/2021, 11:41:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.23V] current current [0.00A].
[11/12/2021, 11:42:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:42:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:43:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:43:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:43:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:44:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:44:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.04V] current current [0A].
[11/12/2021, 11:45:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.12V] current current [0.00A].
[11/12/2021, 11:45:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:45:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:46:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:46:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:47:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.43V] current current [0.00A].
[11/12/2021, 11:47:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:47:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:48:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [119.88V] current current [0A].
[11/12/2021, 11:48:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [119.88V] current current [0.00A].
[11/12/2021, 11:49:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:49:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.04V] current current [0A].
[11/12/2021, 11:49:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.04V] current current [0.00A].
[11/12/2021, 11:50:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:50:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:51:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.33V] current current [0.00A].
[11/12/2021, 11:51:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:51:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:52:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:52:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:53:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 11:53:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 11:53:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 11:54:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:54:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:55:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:55:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 11:55:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 11:56:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 11:56:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 11:57:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.08V] current current [0.00A].
[11/12/2021, 11:57:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:57:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:58:21 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.3V] current current [0A].
[11/12/2021, 11:58:21 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.31V] current current [0.00A].
[11/12/2021, 11:59:00 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 11:59:01 AM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 11:59:01 AM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 12:00:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:00:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:01:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.92V] current current [0.00A].
[11/12/2021, 12:01:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.92V] current current [0A].
[11/12/2021, 12:01:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.92V] current current [0.00A].
[11/12/2021, 12:01:50 PM] [Simplisafe] 4 errors were received from the SimpliSafe API while refereshing sensors in the last 5 minutes. Enable debug logging for detailed output.
[11/12/2021, 12:02:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:02:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:03:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:03:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 12:03:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 12:04:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.67V] current current [0A].
[11/12/2021, 12:04:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.67V] current current [0.00A].
[11/12/2021, 12:05:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:05:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:05:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:06:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.72V] current current [0A].
[11/12/2021, 12:06:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.73V] current current [0.00A].
[11/12/2021, 12:07:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:07:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:07:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:08:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 12:08:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 12:09:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:09:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:09:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:10:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:10:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:11:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:11:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:11:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:12:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:12:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:13:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:13:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:13:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:14:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 12:14:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 12:15:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:15:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:15:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:16:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:16:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:17:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:17:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:17:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:18:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:18:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:19:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:19:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:19:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:20:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:20:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:21:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:21:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:21:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:22:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:22:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:23:02 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 12:23:03 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.2V] current current [0A].
[11/12/2021, 12:23:03 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.20V] current current [0.00A].
[11/12/2021, 12:24:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.75V] current current [0.00A].
[11/12/2021, 12:24:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.75V] current current [0A].
[11/12/2021, 12:25:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.36V] current current [0.00A].
[11/12/2021, 12:25:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:25:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:26:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:26:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:27:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:27:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.59V] current current [0A].
[11/12/2021, 12:27:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:28:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:28:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:29:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.59V] current current [0.00A].
[11/12/2021, 12:29:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:29:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:30:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:30:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:31:00 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:31:01 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.44V] current current [0A].
[11/12/2021, 12:31:01 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.44V] current current [0.00A].
[11/12/2021, 12:32:21 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.51V] current current [0A].
[11/12/2021, 12:32:21 PM] [eWeLink] [CW Office Light] current power [0.00W] current voltage [120.51V] current current [0.00A].
[11/12/2021, 12:32:37 PM] [eWeLink] [CW Office Light] current state [on].
[11/12/2021, 12:32:37 PM] [eWeLink] [CW Office Light] current power [0W] current voltage [120.35V] current current [0A].
[11/12/2021, 12:32:41 PM] [eWeLink] [CW Office Light] current power [27.94W] current voltage [120.2V] current current [0.32A].
[11/12/2021, 12:32:41 PM] [eWeLink] [CW Office Light] current power [27.94W] current voltage [120.20V] current current [0.33A].
[11/12/2021, 12:32:43 PM] [eWeLink] [CW Office Light] current power [27.96W] current voltage [120.2V] current current [0.32A].
[11/12/2021, 12:32:43 PM] [eWeLink] [CW Office Light] current power [27.96W] current voltage [120.20V] current current [0.33A].
[11/12/2021, 12:33:00 PM] [eWeLink] [CW Office Light] current power [27.75W] current voltage [119.64V] current current [0.33A].
[11/12/2021, 12:33:01 PM] [eWeLink] [CW Office Light] current power [27.72W] current voltage [119.64V] current current [0.32A].
[11/12/2021, 12:33:01 PM] [eWeLink] [CW Office Light] current power [27.72W] current voltage [119.64V] current current [0.33A].
[1636742000951] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/login",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 63242
    }
    reqId: "req-w"
[1636742000956] ERROR (69 on metalimac.local): Promise may not be fulfilled with 'undefined' when statusCode is not 204
    reqId: "req-w"
    err: {
      "type": "FastifyError",
      "message": "Promise may not be fulfilled with 'undefined' when statusCode is not 204",
      "stack":
          FastifyError: Promise may not be fulfilled with 'undefined' when statusCode is not 204
              at /usr/local/lib/node_modules/homebridge-config-ui-x/node_modules/fastify/lib/wrapThenable.js:30:30
      "name": "FastifyError",
      "code": "FST_ERR_PROMISE_NOT_FULFILLED",
      "statusCode": 500
    }
[1636742000959] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 6.419930003583431
    reqId: "req-w"
[1636742001590] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/auth/settings",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 63241
    }
    reqId: "req-x"
[1636742001592] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 1.9030840024352074
    reqId: "req-x"
[1636742009025] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "POST",
      "url": "/api/auth/login",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 63340
    }
    reqId: "req-y"
[1636742009053] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 201
    }
    responseTime: 27.850778006017208
    reqId: "req-y"
[11/12/2021, 12:34:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [119.49V] current current [0.32A].
[11/12/2021, 12:34:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [119.49V] current current [0.33A].
[11/12/2021, 12:35:00 PM] [eWeLink] [CW Office Light] current power [27.76W] current voltage [119.49V] current current [0.33A].
[11/12/2021, 12:35:01 PM] [eWeLink] [CW Office Light] current power [27.74W] current voltage [119.49V] current current [0.33A].
[11/12/2021, 12:35:01 PM] [eWeLink] [CW Office Light] current power [27.74W] current voltage [119.49V] current current [0.32A].
[11/12/2021, 12:36:21 PM] [eWeLink] [CW Office Light] current power [27.71W] current voltage [119.41V] current current [0.34A].
[11/12/2021, 12:36:21 PM] [eWeLink] [CW Office Light] current power [27.71W] current voltage [119.41V] current current [0.34A].
[11/12/2021, 12:37:00 PM] [eWeLink] [CW Office Light] current power [27.74W] current voltage [119.42V] current current [0.34A].
[11/12/2021, 12:37:01 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.49V] current current [0.34A].
[11/12/2021, 12:37:01 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.49V] current current [0.34A].
[11/12/2021, 12:37:05 PM] [Simplisafe] Warning: Authentication with username / password is expected to cease to function on or after December 2021. Please re-authenticate using newest method. See README for more info.
[11/12/2021, 12:38:21 PM] [eWeLink] [CW Office Light] current power [27.80W] current voltage [119.80V] current current [0.34A].
[11/12/2021, 12:38:21 PM] [eWeLink] [CW Office Light] current power [27.8W] current voltage [119.8V] current current [0.34A].
[11/12/2021, 12:39:00 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.56V] current current [0.34A].
[11/12/2021, 12:39:01 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.72V] current current [0.34A].
[11/12/2021, 12:39:01 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.72V] current current [0.34A].
[11/12/2021, 12:40:21 PM] [eWeLink] [CW Office Light] current power [27.75W] current voltage [119.49V] current current [0.34A].
[11/12/2021, 12:40:21 PM] [eWeLink] [CW Office Light] current power [27.75W] current voltage [119.49V] current current [0.34A].
[11/12/2021, 12:41:00 PM] [eWeLink] [CW Office Light] current power [27.66W] current voltage [119.49V] current current [0.34A].
[11/12/2021, 12:41:01 PM] [eWeLink] [CW Office Light] current power [27.72W] current voltage [119.52V] current current [0.34A].
[11/12/2021, 12:41:01 PM] [eWeLink] [CW Office Light] current power [27.72W] current voltage [119.52V] current current [0.34A].
[11/12/2021, 12:42:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:42:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [119.72V] current current [0.35A].
[1636742554989] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/712-es2015.a8cde2abdbf03c2e4028.js",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64123
    }
    reqId: "req-z"
[1636742555014] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 24.353560000658035
    reqId: "req-z"
[1636742555124] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64123
    }
    reqId: "req-10"
[1636742556391] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 1266.4709809944034
    reqId: "req-10"
[11/12/2021, 12:43:00 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:43:01 PM] [eWeLink] [CW Office Light] current power [27.83W] current voltage [119.8V] current current [0.35A].
[11/12/2021, 12:43:01 PM] [eWeLink] [CW Office Light] current power [27.83W] current voltage [119.81V] current current [0.35A].
[1636742629299] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/config-schema/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-11"
[1636742629302] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 3.2703549936413765
    reqId: "req-11"
[1636742629314] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/config-editor/plugin/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-12"
[1636742629316] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 1.7484400048851967
    reqId: "req-12"
[1636742629397] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/fa-brands-400.c1210e5ebe4344da5083.woff2",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-13"
[1636742629423] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 25.95872200280428
    reqId: "req-13"
[1636742629611] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/settings-ui/homebridge-honeywell-home/index.html?origin=http%3A%2F%2F<IP_ADDRESS>%3A8581&v=11.0.2",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-14"
[1636742629614] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 2.0781970024108887
    reqId: "req-14"
[1636742629744] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/assets/plugin-ui-utils/ui.js?v=4.41.2",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-15"
[1636742629747] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 2.2660509943962097
    reqId: "req-15"
[11/12/2021, 12:43:49 PM] [Homebridge UI] [homebridge-honeywell-home] Incoming Request: Start Honeywell Login Server
[1636742630244] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/styles.5bd6a810141a08897dfd.css",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64154
    }
    reqId: "req-16"
[1636742630371] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime:<PHONE_NUMBER>956379
    reqId: "req-16"
[11/12/2021, 12:44:21 PM] [eWeLink] [CW Office Light] current power [27.75W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:44:21 PM] [eWeLink] [CW Office Light] current power [27.75W] current voltage [119.73V] current current [0.35A].
[11/12/2021, 12:45:00 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.64V] current current [0.35A].
[11/12/2021, 12:45:01 PM] [eWeLink] [CW Office Light] current power [27.76W] current voltage [119.67V] current current [0.35A].
[11/12/2021, 12:45:01 PM] [eWeLink] [CW Office Light] current power [27.76W] current voltage [119.67V] current current [0.35A].
[11/12/2021, 12:46:21 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.89V] current current [0.34A].
[11/12/2021, 12:46:21 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.89V] current current [0.34A].
[11/12/2021, 12:47:00 PM] [eWeLink] [CW Office Light] current power [27.80W] current voltage [119.88V] current current [0.34A].
[11/12/2021, 12:47:01 PM] [eWeLink] [CW Office Light] current power [27.84W] current voltage [119.88V] current current [0.34A].
[11/12/2021, 12:47:01 PM] [eWeLink] [CW Office Light] current power [27.83W] current voltage [119.88V] current current [0.34A].
[11/12/2021, 12:48:21 PM] [eWeLink] [CW Office Light] current power [27.81W] current voltage [120.12V] current current [0.34A].
[11/12/2021, 12:48:21 PM] [eWeLink] [CW Office Light] current power [27.81W] current voltage [120.12V] current current [0.34A].
[11/12/2021, 12:49:00 PM] [eWeLink] [CW Office Light] current power [27.89W] current voltage [120.04V] current current [0.35A].
[11/12/2021, 12:49:01 PM] [eWeLink] [CW Office Light] current power [27.86W] current voltage [120.04V] current current [0.35A].
[11/12/2021, 12:49:01 PM] [eWeLink] [CW Office Light] current power [27.86W] current voltage [120.04V] current current [0.35A].
[11/12/2021, 12:50:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [120.12V] current current [0.35A].
[11/12/2021, 12:50:21 PM] [eWeLink] [CW Office Light] current power [27.78W] current voltage [120.12V] current current [0.35A].
[1636743050619] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/server/cached-accessories",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64626
    }
    reqId: "req-17"
[1636743050742] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime:<PHONE_NUMBER>9861813
    reqId: "req-17"
[11/12/2021, 12:51:00 PM] [eWeLink] [CW Office Light] current power [27.81W] current voltage [119.96V] current current [0.35A].
[11/12/2021, 12:51:01 PM] [eWeLink] [CW Office Light] current power [27.8W] current voltage [120.04V] current current [0.35A].
[11/12/2021, 12:51:01 PM] [eWeLink] [CW Office Light] current power [27.80W] current voltage [120.04V] current current [0.35A].
[11/12/2021, 12:52:21 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.88V] current current [0.35A].
[11/12/2021, 12:52:21 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.88V] current current [0.35A].
[11/12/2021, 12:52:44 PM] [Homebridge UI] [homebridge-honeywell-home] Terminating child process...
[11/12/2021, 12:52:44 PM] [Homebridge UI] [homebridge-honeywell-home] Child process ended
[1636743170940] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/config-schema/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64781
    }
    reqId: "req-18"
[1636743170943] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 3.204116001725197
    reqId: "req-18"
[1636743170958] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/config-editor/plugin/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64781
    }
    reqId: "req-19"
[1636743170960] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 1.694312997162342
    reqId: "req-19"
[1636743171200] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/settings-ui/homebridge-honeywell-home/index.html?origin=http%3A%2F%2F<IP_ADDRESS>%3A8581&v=11.0.2",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 64781
    }
    reqId: "req-1a"
[1636743171203] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 2.3348319977521896
    reqId: "req-1a"
[11/12/2021, 12:52:51 PM] [Homebridge UI] [homebridge-honeywell-home] Incoming Request: Start Honeywell Login Server
[11/12/2021, 12:53:00 PM] [eWeLink] [CW Office Light] current power [27.77W] current voltage [119.74V] current current [0.35A].
[11/12/2021, 12:53:01 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.88V] current current [0.35A].
[11/12/2021, 12:53:01 PM] [eWeLink] [CW Office Light] current power [27.79W] current voltage [119.88V] current current [0.35A].
[11/12/2021, 12:54:21 PM] [eWeLink] [CW Office Light] current power [27.76W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:54:21 PM] [eWeLink] [CW Office Light] current power [27.76W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:55:00 PM] [eWeLink] [CW Office Light] current power [27.67W] current voltage [119.56V] current current [0.35A].
[11/12/2021, 12:55:01 PM] [eWeLink] [CW Office Light] current power [27.69W] current voltage [119.55V] current current [0.35A].
[11/12/2021, 12:55:01 PM] [eWeLink] [CW Office Light] current power [27.69W] current voltage [119.56V] current current [0.35A].
[11/12/2021, 12:56:21 PM] [eWeLink] [CW Office Light] current power [27.63W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:56:21 PM] [eWeLink] [CW Office Light] current power [27.63W] current voltage [119.72V] current current [0.35A].
[11/12/2021, 12:57:00 PM] [eWeLink] [CW Office Light] current power [27.70W] current voltage [119.79V] current current [0.35A].
[11/12/2021, 12:57:01 PM] [eWeLink] [CW Office Light] current power [27.65W] current voltage [119.80V] current current [0.35A].
[11/12/2021, 12:57:01 PM] [eWeLink] [CW Office Light] current power [27.65W] current voltage [119.8V] current current [0.35A].
[11/12/2021, 12:58:21 PM] [eWeLink] [CW Office Light] current power [27.38W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 12:58:21 PM] [eWeLink] [CW Office Light] current power [27.39W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 12:59:00 PM] [eWeLink] [CW Office Light] current power [27.35W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 12:59:01 PM] [eWeLink] [CW Office Light] current power [27.35W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 12:59:01 PM] [eWeLink] [CW Office Light] current power [27.35W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 12:59:06 PM] [Homebridge UI] [homebridge-honeywell-home] Terminating child process...
[11/12/2021, 12:59:06 PM] [Homebridge UI] [homebridge-honeywell-home] Child process ended
[1636743547580] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/config-schema/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 65198
    }
    reqId: "req-1b"
[1636743547583] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 2.6441939994692802
    reqId: "req-1b"
[1636743547593] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/config-editor/plugin/homebridge-honeywell-home",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 65198
    }
    reqId: "req-1c"
[1636743547595] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 1.6738779991865158
    reqId: "req-1c"
[1636743547795] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins/settings-ui/homebridge-honeywell-home/index.html?origin=http%3A%2F%2F<IP_ADDRESS>%3A8581&v=11.0.2",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 65198
    }
    reqId: "req-1d"
[1636743547797] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 2.054448999464512
    reqId: "req-1d"
[11/12/2021, 12:59:07 PM] [Homebridge UI] [homebridge-honeywell-home] Incoming Request: Start Honeywell Login Server
[11/12/2021, 1:00:21 PM] [eWeLink] [CW Office Light] current power [27.27W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 1:00:21 PM] [eWeLink] [CW Office Light] current power [27.27W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 1:00:37 PM] [Homebridge UI] [homebridge-honeywell-home] Terminating child process...
[11/12/2021, 1:00:37 PM] [Homebridge UI] [homebridge-honeywell-home] Child process ended
[11/12/2021, 1:01:00 PM] [eWeLink] [CW Office Light] current power [27.27W] current voltage [118.55V] current current [0.34A].
[11/12/2021, 1:01:01 PM] [eWeLink] [CW Office Light] current power [27.29W] current voltage [118.47V] current current [0.34A].
[11/12/2021, 1:01:01 PM] [eWeLink] [CW Office Light] current power [27.29W] current voltage [118.47V] current current [0.34A].
[11/12/2021, 1:02:21 PM] [eWeLink] [CW Office Light] current power [27.21W] current voltage [118.63V] current current [0.34A].
[11/12/2021, 1:02:21 PM] [eWeLink] [CW Office Light] current power [27.21W] current voltage [118.63V] current current [0.34A].
[11/12/2021, 1:03:00 PM] [eWeLink] [CW Office Light] current power [27.14W] current voltage [118.71V] current current [0.35A].
[11/12/2021, 1:03:01 PM] [eWeLink] [CW Office Light] current power [27.16W] current voltage [118.47V] current current [0.35A].
[11/12/2021, 1:03:01 PM] [eWeLink] [CW Office Light] current power [27.16W] current voltage [118.47V] current current [0.35A].
[11/12/2021, 1:04:21 PM] [eWeLink] [CW Office Light] current power [27.06W] current voltage [118.47V] current current [0.34A].
[11/12/2021, 1:04:21 PM] [eWeLink] [CW Office Light] current power [27.06W] current voltage [118.47V] current current [0.34A].
[1636743899485] INFO (69 on metalimac.local): incoming request
    req: {
      "method": "GET",
      "url": "/api/plugins",
      "hostname": "<IP_ADDRESS>:8581",
      "remoteAddress": "::ffff:<IP_ADDRESS>",
      "remotePort": 65390
    }
    reqId: "req-1e"
[1636743899494] INFO (69 on metalimac.local): request completed
    res: {
      "statusCode": 200
    }
    responseTime: 8.033781997859478
    reqId: "req-1e"
[11/12/2021, 1:05:00 PM] [eWeLink] [CW Office Light] current power [27.04W] current voltage [118.63V] current current [0.35A].
[11/12/2021, 1:05:01 PM] [eWeLink] [CW Office Light] current power [27.06W] current voltage [118.47V] current current [0.35A].
[11/12/2021, 1:05:01 PM] [eWeLink] [CW Office Light] current power [27.06W] current voltage [118.47V] current current [0.35A].
[11/12/2021, 1:06:20 PM] [Simplisafe] 2 errors were received from the SimpliSafe API while refereshing sensors in the last 5 minutes. Enable debug logging for detailed output.
[11/12/2021, 1:06:21 PM] [eWeLink] [CW Office Light] current power [26.94W] current voltage [118.47V] current current [0.34A].
[11/12/2021, 1:06:21 PM] [eWeLink] [CW Office Light] current power [26.94W] current voltage [118.47V] current current [0.34A].
[11/12/2021, 1:07:00 PM] [eWeLink] [CW Office Light] current power [26.90W] current voltage [118.32V] current current [0.34A].
[11/12/2021, 1:07:01 PM] [eWeLink] [CW Office Light] current power [26.86W] current voltage [118.19V] current current [0.34A].
[11/12/2021, 1:07:01 PM] [eWeLink] [CW Office Light] current power [26.86W] current voltage [118.19V] current current [0.34A].
[11/12/2021, 1:08:21 PM] [eWeLink] [CW Office Light] current power [26.78W] current voltage [118.63V] current current [0.34A].
[11/12/2021, 1:08:21 PM] [eWeLink] [CW Office Light] current power [26.78W] current voltage [118.63V] current current [0.34A].
[11/12/2021, 1:09:00 PM] [eWeLink] [CW Office Light] current power [26.87W] current voltage [119.02V] current current [0.34A].
[11/12/2021, 1:09:01 PM] [eWeLink] [CW Office Light] current power [26.83W] current voltage [119.02V] current current [0.34A].
[11/12/2021, 1:09:01 PM] [eWeLink] [CW Office Light] current power [26.83W] current voltage [119.02V] current current [0.34A].

Config for homebridge-honeywell-home
N/A at this point, unable to create link and finish configuration

Screenshots

Device & Model
iMac running latest Home Assistant
Node.js Version
14.18.1
NPM Version
6.14.15
Homebridge Version
1.3.6
Homebridge Honeywell Home Plugin Version
11.0.2
Homebridge Config UI X Plugin Version
4.41.2
Operating System
Mac OS

@cwmn So your issues are your credentials? Because it would be your Honeywell home login that you would put into that last screenshot

Thanks for the quick replay as well as your plugin work. I tried my username from my developer.honeywellhome.com http://developer.honeywellhome.com/ account and my account info from mytotalconnectcomfort.com http://mytotalconnectcomfort.com/, Both give me a message that a user with these credentials cannot be found.
Chuck
On Nov 12, 2021, at 1:37 PM, Donavan Becker @.***> wrote:
@cwmn https://github.com/cwmn So your issues are your credentials? Because it would be your Honeywell home login that you would put into that last screenshot
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/donavanbecker/homebridge-honeywell-home/issues/590#issuecomment-967401342, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3N5Z6JQHHAFDDQWQM3LRTULVUG7ANCNFSM5H5QBI2A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This is for Honeywell home accounts. So you will have to link your total comfort account to a Honeywell home account

Sorry, still unable to get this to work. I’ll just continue to use the TCC app I guess…
On Nov 12, 2021, at 2:48 PM, Donavan Becker @.***> wrote:
This is for Honeywell home accounts. So you will have to link your total comfort account to a Honeywell home account
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/donavanbecker/homebridge-honeywell-home/issues/590#issuecomment-967527560, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3N5ZYOUOICANRKMKJVVLTULV4TXANCNFSM5H5QBI2A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Download this app
https://apps.apple.com/us/app/honeywell-home/id880332077
Create Honeywell home account
Login and link to total comfort account.

Thanks, that was the ticket. However when all is said and done my brand new
RTH9585WF1004/U Wifi touchscreen Thermostat apparently isn’t supported!
Thanks again for all of the handholding. Kind of ironic after recently retiring from a 43 year career in Honeywell Aerospace….
Regards,
Chuck
On Nov 12, 2021, at 3:22 PM, Donavan Becker @.***> wrote:
Download this app
https://apps.apple.com/us/app/honeywell-home/id880332077 https://apps.apple.com/us/app/honeywell-home/id880332077
Create Honeywell home account
Login and link to total comfort account.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/donavanbecker/homebridge-honeywell-home/issues/590#issuecomment-967582629, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD3N5Z3KGHG6SAGGNCXPN6LULWAS3ANCNFSM5H5QBI2A.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

there is also the homebridge-tcc plugin you could try.


graphite should be listened on ip not vip

It appears to be a typo, it breaks graphite master from querying other graphite backends.
https://github.com/bloomberg/chef-bach/pull/947/files#diff-510da3baf69a4f5cdbde0019fc57c85eR9

Breakage caused by #947 and doesn't occur in release-3.0

thanks


add the new keyword documentation file

Critical Changes
Changes
checked in the new keyword documentation file
Issues Closed

Fixes #1011