Are there any examples using this in an async/await scenario?

I have a scenario where I'm trying to call a REST API service using HttpClient and use the circuit breaker for service timeouts.
I think I'm getting lost in the async/await/TaskScheduler thing and I'm finding the asynchronous operations timing out aren't triggering any CircuitBreakerTimeoutException nor is the circuit breaker ever opening.
My code in an async/await method looks like this:
var circuitBreaker = new CircuitBreaker.Net.CircuitBreaker(
  TaskScheduler.Default,
  maxFailures: 3,
  invocationTimeout: TimeSpan.FromSeconds(4),
  circuitResetTimeout: TimeSpan.FromSeconds(20));

// DownstreamServiceClient is a very small wrapper
// around HttpClient to add a couple of strongly-typed
// operations.
var client = new DownstreamServiceClient();
try
{
  // client.GetDataAsync() does async/await around
  // HttpClient.GetAsync() and JSON deserialization around
  // the model. No magic.
  return await circuitBreaker.Execute(() => client.GetDataAsync());
}
catch (CircuitBreakerOpenException)
{
  // The service is unavailable.
  return null;
}
catch (CircuitBreakerTimeoutException ex)
{
  // The circuit timed out.
  return null;
}

If I stick breakpoints on the return null lines in the code they aren't ever hit; I always get data returned (after however very long the wait is).
Am I missing something obvious? Do you have any async/await examples floating about?

Hi Travis,
The library doesn't support async/await yet. I made some quick hacking in #2 You can take a look at the example: https://github.com/alexandrnikitin/CircuitBreaker.Net/pull/2/files#diff-0845b8c16762d4759c1865fae508a237R51

I published 0.2.0-alpha just to play with it. It is not covered with tests. Timeouts for async don't work. :blush:
I will continue tomorrow or day after.

I look forward to it. Thanks!

@tillig published the 0.2.2 version with async/await support. Feel free to try it :smile:

Works awesome. Thanks! :sunglasses:


Implement better validation of how CLI arguments are used together

Description of the new feature / enhancement
The current validation of arguments seems to miss many combinations of arguments that don't make sense together. For example, the upgrade commands allows winget upgrade --all -v 1.0 (version is used only when upgrading single package, not all of them) or winget upgrade -m myManifest.yaml --accept-source-agreements (sources are not used with local manifest, so there are no agreements).
We should improve that validation, preferably in a way that makes it easier to extend as we add more arguments.
Proposed technical implementation details
I think we could create "categories" of arguments and define the rules on top of them. For example, for upgrade there are arguments for selecting the package (e.g. id, version), arguments for selecting multiple packages (--all, --include-unknown), and arguments for the sources (source name, REST source header, agreements). We could define rules on top of them like disallowing arguments for both single and multiple packages, or for sources when including a local manifest. Adding a new argument to one category would include it in all existing rules easily.

Indeed, Powershell's parameter sets was something I had considered when this was originally written.  At the time it wasn't really worth it, but I assumed we could just add it later.  I still think we could do so easily.
I would argue for keeping them separate as in sets, rather than tagging each argument with flags.  That way, each set can have custom documentation (if needed) for the argument.

@florelis - Is this resolved with the above PR?

@florelis Is this resolved with the above PR?

I think the PR does what I wanted so I'll close this. Maybe in the future we'll want to do what @johnmcpms suggested about sets, but that can be a different issue.


Process lookup error

I've installed bokeh_root_cmd==0.1.1 on my jupyterhub.
In my config.yml file (link) I've added
hub:
  extraConfig:
    ...
    cds-extra-frameworks: |
      c.CDSDashboardsConfig.extra_presentation_types = ["flask", "panel"]

      c.VariableMixin.extra_presentation_launchers = {
          "flask": {
              "args": [
                  "--destport=0",
                  "python3",
                  "{-}m",
                  "flask_gunicorn_cmd.main",
                  "{presentation_path}",
                  "{--}port={port}",
              ]
          },
          "panel": {
              "args": [
                  "--destport=0",
                  "python3",
                  "{-}m",
                  "bokeh_root_cmd.main",
                  "{presentation_path}",
                  "{--}port={port}",
                  "{--}allow-websocket-origin={origin_host}",
                  "{--}panel",
                  "--ready-check-path=/ready-check",
              ]
          },
      }

The two extra frameworks show up in the menu

But when I "save" I get the error message after the image has built and started.
Traceback (most recent call last):
  File "/opt/conda/lib/python3.9/site-packages/tornado/web.py", line 1704, in _execute
    result = await result
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/websocket.py", line 102, in get
    return await self.http_get(*args, **kwargs)
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/proxyhandlers.py", line 849, in http_get
    return await self.proxy(self.port, path)
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/proxyhandlers.py", line 843, in proxy
    return await self.oauth_proxy(port, path)
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/proxyhandlers.py", line 798, in oauth_proxy
    return await self.core_proxy(port, path)
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/proxyhandlers.py", line 829, in core_proxy
    if not await self.ensure_process():
  File "/opt/conda/lib/python3.9/site-packages/jhsingle_native_proxy/proxyhandlers.py", line 762, in ensure_process
    await proc.kill()
  File "/opt/conda/lib/python3.9/site-packages/simpervisor/process.py", line 167, in kill
    return await self._signal_and_wait(signal.SIGKILL)
  File "/opt/conda/lib/python3.9/site-packages/simpervisor/process.py", line 140, in _signal_and_wait
    self.proc.send_signal(signum)
  File "/opt/conda/lib/python3.9/asyncio/subprocess.py", line 138, in send_signal
    self._transport.send_signal(signal)
  File "/opt/conda/lib/python3.9/asyncio/base_subprocess.py", line 145, in send_signal
    self._check_proc()
  File "/opt/conda/lib/python3.9/asyncio/base_subprocess.py", line 142, in _check_proc
    raise ProcessLookupError()
ProcessLookupError

Any suggestions/ fixes would be appreciated. Thanks.

Flask works though

Panel works if I change the framework back to Bokeh. The problem is that bokeh does not serve all the css and js needed by Panel.

If I run the below in a terminal
python3 -m bokeh_root_cmd.main /home/jovyan/./shared/panel-app.ipynb --port=2000

and open https://<domain>/mt-workspace/user/masma/proxy/2000/ (important with final /) I see

If I run
python3 -m bokeh_root_cmd.main /home/jovyan/./shared/panel-app.ipynb --port=2000 --server=panel

and open https:///mt-workspace/user/masma/proxy/2000/ it works

ahh. I should probably change {--}panel to {--server}=panel in the config file.

I tried to but I still get the error

I changed the config.yaml to
"panel": {
              "args": [
                "--destport=0",
                "python3",
                "{-}m",
                "bokeh_root_cmd.main",
                "{presentation_path}",
                "{--}port={port}",
                "{--}allow-websocket-origin={origin_host}",
                "--ready-check-path=/ready-check"
                ]
          },

So now my app is deployed under the framework name panel. But using the bokeh server.

I can now see from the logs that I start containDS app from a dev image containing bokeh-root-cmd==0.1.1 but builds a (prod) image containing bokeh-root-cmd==0.1.0.

I got it fixed and now it works. To summarize the issues that made it difficult to get working.

My notebook was running on a dev image with bokeh_root_cmd==0.1.1 it build and deployed a prod image with bokeh_root_cmd==0.1.0. Thus the --server option was not recognized. As this error is not shown to the user trying to deploy the pod its difficult to understand what the error is. I can see logs in Azure with a 15 mins delay. But I need to know how to query the logs using ksql which is not easy if you don't do it regularly. I don't have access to k8s logs directly via kubectl.
I was in doubt whether it should be --server=panel or {--}server=panel and why. It's the latter I have to use.
General lack of knowledge of the pipeline building and deploying our jupyter hub.
The final step to get this working was a hard refresh of the browser. It was needed to load panel 0.12.1 js where the browser had cached panel 0.11.3 js.

This worked
"panel": {
              "args": [
                "--destport=0",
                "python3",
                "{-}m",
                "bokeh_root_cmd.main",
                "{presentation_path}",
                "{--}port={port}",
                "{--}allow-websocket-origin={origin_host}",
                "{--}server=panel",
                "--ready-check-path=/ready-check"
                ]
          },

Suggestion
Better error messages if the app deployed does not start would be really valuable. Including the full log.
I believe in many setups this would be a self service solution where users don't have access to logs from the underlying system. Thus making it very difficult to get things working if it does not. Leading to a high time to market instead of the opposite.

Thanks for all your comments here - really helpful for others, I'm sure. In general, better error reporting will always be helpful!


How to transfer the YCB dataset to the xml file?

Thanks a lot for your work! I tried to write .xml files for others objects in YCB. However, there is always an error for the texture. I download the YCB datasets and replace the strings for the object mesh (nontextured.stl) and texture (texture_map.png). It doesn't work.

Exception: Failed to load XML file: ycb_banana.xml. mj_loadXML error: b"Error: PNG size must be integer multiple of gridsize in texture

If I use the block.png, it can show well.

Could you please show me how you write the .xml files? Thank you for your help!

Here is part of the .xml file:
     <asset>
         <texture name="texture:object" file="includes/011_banana/google_16k/texture_map.png"/>
<!--         <texture name="011_banana"  file="includes/011_banana/google_16k/block.png"/>-->
        <mesh name="011_banana"     file="includes/011_banana/google_16k/nontextured.stl"/>
        <material name="011_banana" texture="texture:object"/>
    </asset>

Only a part of the banana is covered by texture.

If I add type="2d" as you did, only a half of the banana is covered.

Hello, thank you for your help. I use Mujoco 210. Which version are you using for support .obj files? It seems that the repo you posted uses the latest verion?

After updating MuJoCo to 2.3.5, problem is solved.

@happygaoxiao  -- if you have other models working, please send PR and we can integrate to create a YCB set for MuJoCo. Let me know if this will be of interest.

btw, here is the likely fix that recently landed https://github.com/deepmind/mujoco/issues/859


NOTICE: About further development and support

As I'm no longer using this personally, I'm ceasing further development and will no longer provide support here in issues or elsewhere.
Devs are welcomed to fork and further develop this. If you maintain an active fork, feel free to post your repo address and other details here.
Thank you and good luck.

Thank you for creating this script, it's been very useful.
I'll probably have to teach myself some Python now and then fork this once it really needs an update, but can you give an estimate as to how future-proof the current version is? I think the very first release still does the job so I'm pretty confident in that the script will last for a while but I'm still curious as to how long you think it'll keep working properly.
Again, thanks for the work you've put into making livestream_dl.

It's hard to say because IG has been on an aggressive rollout schedule. You can see this with the constant app updates on your phone.
My guess is, bugs and new features notwithstanding, it should work as-is for another 6 months. With some luck, a year is possible.
I would be shocked if it continues to work unchanged for longer than that though.

@notcammy Is this still working for you? I'm getting this <urlopen error timed out> then it proceeds to run normally most times.

@verafide This script still works fine without any errors or corrupted files on my end.

I've updated my original post at the top about leaving issues open even though the repo is no longer maintained. Please take note. Thanks.


Adding my personal blog and my Docker Image

Magento doesn't offer an official image to Linux, and this image is faster than the official image on Windows and MacOS.

Hi @rafaelstz, the commit looks good! Thank you for your contribution and for being awesome!  👍


time out immediately if process DNE or doesn't have caps

See discussion before here that was resolved by this suggestion.
https://discord.com/channels/1186394868336038080/1186684706700410962/1200237153519665264

Addressed in #255


Mark all threadpool Workers as weakly referenced

This is the workaround I mentioned in https://github.com/emscripten-core/emscripten/pull/18227. Since we know all the threads in the app are part of the threadpool, they can be just weakly referenced, so that the existence of the Worker alone doesn't prevent Node.js from exiting, and instead it's the blocking that waits for results of specific ops that keeps the event loop alive.
This allows to get rid of non-JS-esque shutdown helper.

FYI I am currently using a custom compiled version of  wasm-vips, because if you call vips.shutdown() while running on a Netlify server, the entire Node process crashes without an error message. This does not happen on any other platform, and wasm-vips still runs perfectly fine on Netlify up until shutdown is called. I have solved this by compiling a version of wasm-vips that includes this commit: https://github.com/atjn/easy-web-app-builder/commit/173bc1cf6fd93482ca7a0305f2a03a46aa346135


Bump NeuralPDE v5 benchmarks

@ChrisRackauckas could you please check.

It looks like the two that built look good!

why only two were built?

I'm not sure, maybe it just hit a compute limit. Let's merge and see. All 5 of the error ones worked, but only 2 of the optimization ones.


MRG: deprecated ConcatenateChannels and renamed EpochVectorizer

@agramfort @dengemann This PR addresses issue #2313
Is it fine to import ConcatenateChannels as EpochVectorizer in the init ??
or I should copy the code of ConcatenateChannels and name it class EpochVectorizer?

doc test don't pass because of deprecated call in the init...
so I'm gonna copy paste and rename ConcatenateChannels

besides LGTM

Oops. Sorry guys, I merged to quick.
On Wed, Jul 29, 2015 at 1:50 PM, Alexandre Gramfort <
<EMAIL_ADDRESS>wrote:

besides LGTM
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/2361#issuecomment-125928954
.

ready to merge, if doc test and travis are happy

ping me when you addressed @Eric89GXL comments

done! thanks @Eric89GXL

Yep because I get this error from test_docstring_parameters
AssertionError:
mne.utils.ConcatenateChannels.init arg mismatch: ['info']

perfect !
let's merge when travis is happy !

@trachelr for future reference you could have just added ConcatenateChannels to the list of excludes and it would have worked, too (it matches substrings)

Got it @Eric89GXL !
Thanks

thanks @trachelr

@trachelr the deprecations must go to the API section of whats_new. I just noticed this while rebasing. I'll make a fix in my PR but just so that you know for the future :)

Ok! thanks @mainakjas


Add cmath friend functions

@ckormanyos I am thinking hard about dropping GCC-6 since the failures keep racking up, and they are no longer contained to just the 32-bit address mode. Since every other compiler gets it right, and they are computational issues there must be some problem with code generation. What do you think?


feat(data): Rename evolutive to progressive and re-order code

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


fix tmp remove required of license check

The check has failed due to an unknown issue, so remove the requirement until the issue is resolved.
Proposed changes
Issue Number: close #xxx

run buildall


BAU: Remove old metadata generation app

This is now generated using the scripts in pki

@samcrang Safe to delete this?


Backport #621 to Garden

Backport #621 to Garden
Disable test failing due to ODE/libccd (#621)
 https://build.osrfoundation.org/job/gz_physics-ci-gz-physics6-homebrew-amd64/40/testReport/
Part of #620.
Original PR description
Disable test failing due to ODE/libccd (#621)
🦟 Bug fix
Part of #620.
Summary
As noted in #620, the JointFeaturesDetachTest/0.JointDetach test has been failing on macOS since ODE 0.16.5 was merged to homebrew-core in https://github.com/Homebrew/homebrew-core/pull/167158. This disables the failing test expectations while we investigate the cause in #620.
Checklist

[X] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[X] codecheck passed (See contributing)
[X] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Rebase-and-Merge.

fixing windows compiler warning in https://github.com/gazebosim/gz-physics/pull/629/commits/ea84ff77e5e021d53e1ecaacb5a0d6a09bd70912


Day111

Resolves #232.

Pull Request Test Coverage Report for Build 450

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

Totals

Change from base Build 441:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Command to change DNS Server Port at Runtime Not Available

We are writing test scripts for duckhorn based on the 1.3 Duckhorn Test Plan.
While going through the DuckHorn 3.2 test case (3.2. [COMPONENT]  Re-register service with active SRP server - Multiple BRs - With AIL) and 3.2b test case (3.2b. [PRODUCT] Re-register service with active SRP server - Multiple BRs - With AIL - Thread Product DUT) , we came across a requirement.
In Step 4 (for both the test cases Step 4) it is advised to configure the BR "to advertise its DNS/SRP Unicast Dataset at an available port value, P, different from 53."
In step 8 (3.2b) it is advised to again change the port "BR to advertise its DNS/SRP Unicast Dataset at a new port value, P2."
We could not found a suitable command for that.
Is it possible to change this port at the runtime?

Disabling the SRP server and enable it again will do this. SRP server will pick a new port number upon restart.
CLI command srp server disable and then srp server enable (which map to otSrpServerSetEnabled() API).

One supplement is only when there are SRP services registered, the DNS/SRP port that is registered into the Thread Network Data will be stored into non-volatile storage and increase in next stack restart or srp server disable/enable
The default SRP port for OTBR reference is 53535 (different from 53 as step4 requires) and there is DUT's SRP service registered before step8,  with srp server disable/enable on BR, the port will increase as the test requires.

Thanks @abtink and @librasungirl for your support.
I tried the same i.e: disabling the SRP server (srp server disable) and then again enabling it (srp server enable)
But its looking like not working for me

Am I doing something wrong?

@shouvik-grl as mentioned above, you need to bring up one thread device and let it register some SRP service to the BR. then disable and enable srp server, you will find the port increases.

Thanks for your support @librasungirl
Yes with the thread device register some SRP service to the BR
SRP port change is working.

Again thanks @abtink  and @librasungirl  for your sopport.


Add license

@fvitalini, if everything is fine please squash-merge (2 of the three commits are irrelevant)

MOAR commits for mighty Riccardo 😄


[NG] Collapse Animation doesn't work when using clrIfExpanded Directive

Select one ...  (check one with "x")
[x] bug
[ ] feature request
[ ] enhancement

Expected behavior

When an Element using clrIfExpanded is collapsed, it should first animate the collapse and then the children should be removed from the View
Actual behavior

When an Element using `clrIfExpanded is collapsed, animation doesnt work because the child nodes are removed from the DOM immediately.
Reproduction of behavior

Tree View:
https://plnkr.co/edit/NWGdymT6uBaSNnW3iJmw?p=preview

Environment details

Angular version: 4.2.X

Clarity version: 0.10.0

OS and version: All

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

After discussion with the team it was decided not to fix this, as we would have to introduce asynchronous update of the model, bound to an animation lifecycle event. The lost synchronicity and increased testing complexity are not justified with the minor visual animation gain.


How to upload react-native-bluetooth-escpos-printer without node module

Using this npm we need to change some code in node module/react-native-bluetooth-escpos-printer file so wehn i need to psuh my code on github that time i dont need to psuh node module so what can i do

you can use the patch-package to keep your changes
https://www.npmjs.com/package/patch-package


nucleotide substitution spectrum analysis

Hello,
Can you provide the script for the nucleotide substitution spectrum analysis section at your convenience?
Thanks
Kind regards,
Xuping

Howdy, Xuping.
I'm not sure who performed that analysis, but they might not be someone who receives messages for this repo.
Since you haven't gotten a response yet, I suggest you send an email to the lead author — she'll know who did that analysis and can  forward your request to them.


WiFiServer seems to hang while ESP32 is running in SoftAP mode and dealing with large file transfers

I am currently running my ESP32 in SoftAP mode with an HTTP Server listening on port 80.  My project has some basic input and outputs, with the occasional large POST from the client to the server (1-3 files of up to 256Kb each).
After a while, or one or two file uploads using POST, the WiFi server seems to hang and not receive any more clients.  Sometimes this is not permanent and after a few seconds (10-15secs) I can enter the first if statement below, sometimes it never recovers until I disconnect from the AP and reconnect.
I had seen that there were some issues with LWIP.  I also can't seem to tell if the client.setTimeout does anything.  I've definitely got caught in while loops indefinitely even though there is no response from my browser.
For reference I'm running esp-idf from the most up to date platformio.
Below is my main FreeRTOS task for handling http requests
void HTTPServer::handleHTTP(bool con, bool dis)
{
	if(httpServer != NULL && (*httpServer) && httpServer->hasClient()){
		ESP_LOGD(TAG, "Found HTTP Client");
		client.stop();
		client = httpServer->available();
		ESP_LOGD(TAG, "Client connected: %d, CLient available: %d", client.connected(),  client.available());
	}

	if(httpServer != NULL && !(*httpServer))
		ESP_LOGE(TAG, "Server stopped listening");

	if(client.connected()){
		ESP_LOGD(TAG, "Client connected");
		vTaskDelay(pdMS_TO_TICKS(10));
		client.setTimeout(5);
		client.setNoDelay(true);
		while(client.available()){
			ESP_LOGD(TAG, "Got data from browser");
			readHTTP();
			if(pageReady){
				servePage();
				vTaskDelay(pdMS_TO_TICKS(10));
				client.stop();
				pageReady = false;
				Serial.println("Page served, client disconnected");
			}
		}
	}
}

As an update, it seems that its not necessarily tied to large file transfers, but simply a function of the amount of time that the client is connected to the ESP32 AP.  I've tried bringing down the tcpip_interface using tcpip_adapter_up and tcpip_adapter_down, but that didn't seem to help.
The best solution I've come up with so far is to use esp_wifi_deauth_sta(0) periodically.  I'm not sure what  an AP_STADISCONNECTED and AP_STACONNECTED reinitializes, but it seems to refresh the connection so that its available immediately when the client requests a page.

Hi @seaduck13 is it possible to provide the whole demo code, then I can reproduce it.

@seaduck13
can you provide the IDF version? Or you can see the problem #1372 . Is it the same as your problem?

@liuzfesp Unfortunately no, this project is sensitive so I cannot share the code more than I have.
@zhangyanjiaoesp I believe it's ESP-IDF 2.1.1
I believe the issue is tied to the lwip_bind and lwip_listen and the time_wait state.  I could be way off though, its just what I've been looking at as a solution.  Some people suggested using socket option SO_REUSEADDR to reuse the address during bad disconnects, but I don't think it's fixed my issues completely.  I'm still getting periodic pauses where the server won't return true for hasClient().

@seaduck13  you can try to use idf 3.0, in another question idf 3.0 work well for the similar issue(#1372). If you insist on using 2.1 version, you need to wait for some time for updating


Cryptography backend can only use "auto" for cipher option.

When using CA role. Play fails with the following error :
TASK [cloudera.cluster.ca_server : Generate root private key] **************************************************************************************************************************
fatal: [xxxx]: FAILED! => changed=false
msg: Cryptography backend can only use "auto" for cipher option.
When looking at openssl_privatekey_module's documentation we can see that only "auto" value is accepted for cipher parameter

Was fixed in release 3.4.0


Add mTLS between GPTScript server and daemon tools

We need to support mTLS rather than inherently trusting all traffic to daemon tools.

Since we paused this, moving back


Make npm install work, fix npx tsc --noEmit errors

I tried creating a new project with the solid-styled template and ran into two issues 'fixed' in this PR:
1: Peer dependency error.
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vite
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer vite@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/solid-start-aws
npm ERR!     peerOptional solid-start-aws@"*" from<EMAIL_ADDRESS>npm ERR!     node_modules/solid-start
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!       8 more (solid-start-aws, solid-start-cloudflare-pages, ...)
npm ERR!   6 more (solid-start-cloudflare-pages, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/solid-start
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer solid-start@"*" from<EMAIL_ADDRESS>npm ERR!   7 more (solid-start-cloudflare-pages, ...)

2: Running npx tsc --noEmit resulted in a number of errors.
A few errors were caused by missing @types packages and one was caused by initializing an empty array without type definition (resulting in an inferred never[] type).
This PR fixes these issues (though, the Vite version should probably actually be fixed in a different way)

I see you merged a fix into the MR 👍 , locally things now seem to work with Vite 4- and all the types are looking good.

Thank you


Add the possibility to control a subset of coordinates in TSID:SE3Task

It would be convenient to port the changes in https://github.com/ami-iit/bipedal-locomotion-framework/pull/356 to TSID, as done in https://github.com/ami-iit/bipedal-locomotion-framework/pull/724 for the COM Task.

fyi @xela-95 @Gio-DS @diegoferigo @LoreMoretti


Pyomo mins

Pull Request Description
What issue does this change request address?
Closes #18
Contributes to #34 (however, EnsembleModel still crashes without at least one ARMA ROM)
What are the significant changes in functionality due to this change request?

Modifies pyomo dispatcher to correctly grab minimum production levels from components
Modifies pyomo dispatcher so that capacity and minimum production are assumed to be time-dependent values, allowing an ARMA to be used for either.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass.
[ ] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large tes.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
[ ] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

It looks like Jason is working in CIVET right now, so the automated tests aren't running, but they passed on my local machine, so hopefully they'll pass automation once they're up.


Add support for AtlanticPassAPCHeatingAndCoolingZone (io:AtlanticPassAPCZoneControlZoneComponent)

[x] I have read the Readme, including the Advanced section regarding debugging.

Device information
A clear and concise description of the device, together with specific usecases that you would like to see supported.
This is a french ac multisplit device compatible with IO homecontrol.
Use case : Would like ton controle remotly the AC temperature and mode (off / prog / manual / away).  Temperatures sensor are correctly displayed though.
Device details
Device is an atlantic multiplit AC controler equiped with an io compatible Zone control that manage (exatc model is https://www.atlantic-climatisation-ventilation.fr/climatisation/gainables/principe-de-la-solution-shogun/solution-shogun-monosplit-multi-zones).

Debug Logging
2020-12-09 23:05:33 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone)

{
	"commands": [{
		"commandName": "refreshComfortCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshComfortHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshEcoCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshEcoHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMaximumCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMaximumHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMinimumCoolingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshMinimumHeatingTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "refreshTargetTemperature",
		"nparams": 0
	}, {
		"commandName": "setActiveCoolingTimeProgram",
		"nparams": 1
	}, {
		"commandName": "setActiveHeatingTimeProgram",
		"nparams": 1
	}, {
		"commandName": "setComfortCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setComfortHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setCoolingOnOffState",
		"nparams": 1
	}, {
		"commandName": "setCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setDerogationOnOffState",
		"nparams": 1
	}, {
		"commandName": "setEcoCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setEcoHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setHeatingOnOffState",
		"nparams": 1
	}, {
		"commandName": "setHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMaximumCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMaximumHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMinimumCoolingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setMinimumHeatingTargetTemperature",
		"nparams": 1
	}, {
		"commandName": "setName",
		"nparams": 1
	}, {
		"commandName": "refreshPassAPCCoolingMode",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCCoolingProfile",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCHeatingMode",
		"nparams": 0
	}, {
		"commandName": "refreshPassAPCHeatingProfile",
		"nparams": 0
	}, {
		"commandName": "setPassAPCCoolingMode",
		"nparams": 1
	}, {
		"commandName": "setPassAPCHeatingMode",
		"nparams": 1
	}],
	"states": [{
		"type": "DataState",
		"qualifiedName": "core:ActiveCoolingTimeProgramState"
	}, {
		"type": "DataState",
		"qualifiedName": "core:ActiveHeatingTimeProgramState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:ComfortCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:ComfortHeatingTargetTemperatureState"
	}, {
		"values": ["off", "on"],
		"type": "DiscreteState",
		"qualifiedName": "core:CoolingOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:CoolingTargetTemperatureState"
	}, {
		"values": ["off", "on"],
		"type": "DiscreteState",
		"qualifiedName": "core:DerogationOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:EcoCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:EcoHeatingTargetTemperatureState"
	}, {
		"values": ["off", "on"],
		"type": "DiscreteState",
		"qualifiedName": "core:HeatingOnOffState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:HeatingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MaximumCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MaximumHeatingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MinimumCoolingTargetTemperatureState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:MinimumHeatingTargetTemperatureState"
	}, {
		"type": "DataState",
		"qualifiedName": "core:NameState"
	}, {
		"values": ["available", "unavailable"],
		"type": "DiscreteState",
		"qualifiedName": "core:StatusState"
	}, {
		"type": "ContinuousState",
		"qualifiedName": "core:TargetTemperatureState"
	}, {
		"values": ["cooling", "heating", "heatingAndCooling"],
		"type": "DiscreteState",
		"qualifiedName": "core:ThermalConfigurationState"
	}, {
		"values": ["available", "unavailable"],
		"type": "DiscreteState",
		"qualifiedName": "io:CoolingManualModeAvailabilityState"
	}, {
		"values": ["available", "unavailable"],
		"type": "DiscreteState",
		"qualifiedName": "io:HeatingManualModeAvailabilityState"
	}, {
		"values": ["absence", "auto", "comfort", "eco", "externalScheduling", "internalScheduling", "manu", "stop"],
		"type": "DiscreteState",
		"qualifiedName": "io:PassAPCCoolingModeState"
	}, {
		"values": ["absence", "comfort", "derogation", "eco", "externalSetpoint", "frostprotection", "manu", "stop"],
		"type": "DiscreteState",
		"qualifiedName": "io:PassAPCCoolingProfileState"
	}, {
		"values": ["absence", "auto", "comfort", "eco", "externalScheduling", "internalScheduling", "manu", "stop"],
		"type": "DiscreteState",
		"qualifiedName": "io:PassAPCHeatingModeState"
	}, {
		"values": ["absence", "comfort", "derogation", "eco", "externalSetpoint", "frostprotection", "manu", "stop"],
		"type": "DiscreteState",
		"qualifiedName": "io:PassAPCHeatingProfileState"
	}],
	"dataProperties": [],
	"widgetName": "AtlanticPassAPCHeatingAndCoolingZone",
	"uiClass": "HeatingSystem",
	"uiClassifiers": ["emitter", "heatingSystem", "coolingSystem"],
	"qualifiedName": "io:AtlanticPassAPCZoneControlZoneComponent",
	"type": "ACTUATOR"
}

Thanks for reporting, @fredleger! Currently we have a small backlog for climate devices, but hopefully support will be added soon.
We need to have a look if any other implementation is close to your device, which could speed up the process. I have added the available states and commands to your post.
Does your temperature sensor show up in Home Assistant separately as well?

@iMicknl yes temperature are showing without any flaw.
thanks and looking forward to see this integration working with my equipement (actually bought tahoma for this).
let me know if you need further details here i can provide it.

Hi, version 2.3.8 was just released with new info in debug log. Could you install it, activate debug log and report the device urls of the thermostat you want added, and the temperature sensor that goes with it?
Thanks.

hello @vlebourl and @iMicknl !
Here are the requested logs. Let me know if you need something else here:
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlMainComponent - HeatingSystem - AtlanticPassAPCZoneControl - io://1233-4449-5614/11530893#1)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#10)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#11)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#2)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#3)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#4)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#5)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#6)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#7)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#8)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#9)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:RollerShutterGenericIOComponent - RollerShutter - PositionableRollerShutter - io://1233-4449-5614/6596573)
2020-12-27 15:55:51 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.209 seconds
2020-12-27 15:56:21 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.297 seconds
2020-12-27 15:56:51 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.184 seconds
2020-12-27 15:57:21 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.253 seconds
2020-12-27 15:57:51 DEBUG (MainThread) [custom_components.tahoma] Finished fetching TaHoma Event Fetcher data in 0.239 seconds

Thanks for the information.
In order to gather more information, you can use the tahoma.get_execution_history service in Home Assistant which will print your execution history to the Home Assistant log. Run the all available commands via the official vendor app (e.g. TaHoma) and capture the commands. (this service has been added to the latest version, so you would need to update this integration).
It would be great if you could also add some screenshots / more information of the official vendor app.

Hi @iMicknl
I guess this is the logs you are looking for:
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (internal:TSKAlarmComponent - Alarm - TSKAlarmController - internal://1233-4449-5614/alarm/0)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlMainComponent - HeatingSystem - AtlanticPassAPCZoneControl - io://<redacted>#1)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://<redacted>#10)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://<redacted>#11)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://<redacted>#2)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://<redacted>#3)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://<redacted>#4)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://<redacted>#5)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://<redacted>#6)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://<redacted>#7)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Unsupported device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://<redacted>#8)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://<redacted>#9)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added device (io:RollerShutterGenericIOComponent - RollerShutter - PositionableRollerShutter - io://1233-4449-5614/6596573)
2021-02-06 18:39:59 DEBUG (MainThread) [custom_components.tahoma] Added gateway (1233-4449-5614 - GatewayType.TAHOMA_V2 - GatewaySubType.TAHOMA_SHORT_CHANNEL)
2021-02-06 18:40:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.188 seconds
2021-02-06 18:41:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.186 seconds
2021-02-06 18:41:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.187 seconds
2021-02-06 18:42:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.187 seconds
2021-02-06 18:42:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.197 seconds
2021-02-06 18:43:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.201 seconds
2021-02-06 18:43:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.225 seconds
2021-02-06 18:44:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.222 seconds
2021-02-06 18:44:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.198 seconds
2021-02-06 18:45:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#3, state: None -> None)
2021-02-06 18:45:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#11, state: None -> None)
2021-02-06 18:45:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.206 seconds
2021-02-06 18:45:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.181 seconds
2021-02-06 18:46:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.236 seconds
2021-02-06 18:46:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.202 seconds
2021-02-06 18:47:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.228 seconds
2021-02-06 18:47:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.185 seconds
2021-02-06 18:48:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.243 seconds
2021-02-06 18:48:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.190 seconds
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-04 00:47:29: setHeatingOnOffState executed via Parents - Off - iPhone on io://<redacted>#6, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-04 00:47:29: refreshPassAPCHeatingProfile executed via Parents - Off - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:14: refreshOperatingMode executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:14: setPassAPCHeatingMode executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:14: refreshTargetTemperature executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:14: refreshPassAPCHeatingProfile executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:05: refreshOperatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:05: setPassAPCHeatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#6, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:05: refreshTargetTemperature executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 23:48:05: refreshPassAPCHeatingProfile executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:25: refreshOperatingMode executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:25: setPassAPCHeatingMode executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:25: refreshTargetTemperature executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:25: refreshPassAPCHeatingProfile executed via Salon / SaM - Mode auto - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:15: refreshOperatingMode executed via Parents - Mode manu - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:15: setPassAPCHeatingMode executed via Parents - Mode manu - iPhone on io://<redacted>#6, with ['manu'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:15: setHeatingTargetTemperature executed via Parents - Mode manu - iPhone on io://<redacted>#6, with [19].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:15: refreshTargetTemperature executed via Parents - Mode manu - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:49:15: refreshPassAPCHeatingProfile executed via Parents - Mode manu - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 12:45:51: update executed via mise à jour box on internal://1233-4449-5614/pod/0, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 06:47:39: refreshOperatingMode executed via Salon / SaM - Mode manu - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 06:47:39: setPassAPCHeatingMode executed via Salon / SaM - Mode manu - iPhone on io://<redacted>#2, with ['manu'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 06:47:39: setHeatingTargetTemperature executed via Salon / SaM - Mode manu - iPhone on io://<redacted>#2, with [21.5].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 06:47:39: refreshTargetTemperature executed via Salon / SaM - Mode manu - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 06:47:39: refreshPassAPCHeatingProfile executed via Salon / SaM - Mode manu - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 00:52:50: setHeatingOnOffState executed via Bureau - Off - iPhone on io://<redacted>#10, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-03 00:52:50: refreshPassAPCHeatingProfile executed via Bureau - Off - iPhone on io://<redacted>#10, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-02 00:36:12: setHeatingOnOffState executed via Bureau - Off - iPhone on io://<redacted>#10, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-02-02 00:36:12: refreshPassAPCHeatingProfile executed via Bureau - Off - iPhone on io://<redacted>#10, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:53:17: setHeatingOnOffState executed via Salon / SaM - Off - iPhone on io://<redacted>#2, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:53:17: refreshPassAPCHeatingProfile executed via Salon / SaM - Off - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:51:17: setHeatingOnOffState executed via Parents - Off - iPhone on io://<redacted>#6, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:51:17: refreshPassAPCHeatingProfile executed via Parents - Off - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:51:02: setHeatingOnOffState executed via Bureau - Off - iPhone on io://<redacted>#10, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:51:02: refreshPassAPCHeatingProfile executed via Bureau - Off - iPhone on io://<redacted>#10, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:49:09: refreshOperatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:49:09: setPassAPCHeatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#6, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:49:09: refreshTargetTemperature executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:49:09: refreshPassAPCHeatingProfile executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 23:16:06: setClosure executed via SOLUS io - Régler à 83% - iPhone on io://1233-4449-5614/6596573, with [83].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 11:48:02: refreshOperatingMode executed via Bureau - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 11:48:02: setPassAPCHeatingMode executed via Bureau - Mode auto - iPhone on io://<redacted>#10, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 11:48:02: refreshTargetTemperature executed via Bureau - Mode auto - iPhone on io://<redacted>#10, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 11:48:02: refreshPassAPCHeatingProfile executed via Bureau - Mode auto - iPhone on io://<redacted>#10, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 02:05:14: setHeatingOnOffState executed via Salon / SaM - Off - iPhone on io://<redacted>#2, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 02:05:14: refreshPassAPCHeatingProfile executed via Salon / SaM - Off - iPhone on io://<redacted>#2, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 02:05:10: setHeatingOnOffState executed via Parents - Off - iPhone on io://<redacted>#6, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-31 02:05:10: refreshPassAPCHeatingProfile executed via Parents - Off - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:28:08: refreshOperatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#1, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:28:08: setPassAPCHeatingMode executed via Parents - Mode auto - iPhone on io://<redacted>#6, with ['internalScheduling'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:28:08: refreshTargetTemperature executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:28:08: refreshPassAPCHeatingProfile executed via Parents - Mode auto - iPhone on io://<redacted>#6, with [].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:27:53: setHeatingOnOffState executed via Bureau - Off - iPhone on io://<redacted>#10, with ['off'].
2021-02-06 18:48:50 INFO (MainThread) [custom_components.tahoma] 2021-01-30 22:27:53: refreshPassAPCHeatingProfile executed via Bureau - Off - iPhone on io://<redacted>#10, with [].
2021-02-06 18:49:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.205 seconds
2021-02-06 18:49:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.189 seconds
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] PushSubscriptionCreatedEvent/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.REFRESH_ALL_DEVICES_STATES_COMPLETED/None (device: None, state: None -> None)
2021-02-06 18:50:00 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.195 seconds
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#8, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#2, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_REGISTERED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.INITIALIZED -> ExecutionState.NOT_TRANSMITTED)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_STARTED/None (device: None, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.NOT_TRANSMITTED -> ExecutionState.TRANSMITTED)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.GATEWAY_SYNCHRONIZATION_ENDED/None (device: None, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.TRANSMITTED -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#6, state: None -> None)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:30 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.231 seconds
2021-02-06 18:50:31 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.054 seconds
2021-02-06 18:50:32 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#6, state: None -> None)
2021-02-06 18:50:32 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:32 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:32 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.064 seconds
2021-02-06 18:50:33 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.054 seconds
2021-02-06 18:50:34 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.055 seconds
2021-02-06 18:50:35 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#6, state: None -> None)
2021-02-06 18:50:35 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:35 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:35 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.063 seconds
2021-02-06 18:50:36 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.055 seconds
2021-02-06 18:50:37 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.QUEUED_GATEWAY_SIDE)
2021-02-06 18:50:37 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.QUEUED_GATEWAY_SIDE -> ExecutionState.IN_PROGRESS)
2021-02-06 18:50:37 DEBUG (MainThread) [custom_components.tahoma] Finished fetching events data in 0.081 seconds
2021-02-06 18:50:38 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.DEVICE_STATE_CHANGED/None (device: io://<redacted>#8, state: None -> None)
2021-02-06 18:50:38 DEBUG (MainThread) [custom_components.tahoma.coordinator] EventName.EXECUTION_STATE_CHANGED/78776527-ac10-3401-7145-93c1d8ca2587 (device: None, state: ExecutionState.IN_PROGRESS -> ExecutionState.COMPLETED)

Screenshot of tahoma app:

@fredleger thanks! There are quite some different commands in your history, this is because the service will send back all history of the last 24h. Could you perhaps have a look at them and remove the duplicates + write down what the action probably was? I don't know enough about your device to map this.
You can have a look at the description, for example executed via Parents - Mode auto - iPhone. Or you could run some commands again in a sequence, write them down and then capture the history again.

Just tired a couple of command and get new logs.
I will do a more in depth try but this could help as a starting point.
My Logs truncated to only the hour where i tested :
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:41: setPassAPCHeatingMode executed via Salon / SaM - Mode auto - iPhone on io://1233-4449-5614/11530893#2, with ['internalScheduling'].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:41: refreshTargetTemperature executed via Salon / SaM - Mode auto - iPhone on io://1233-4449-5614/11530893#2, with [].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:41: refreshPassAPCHeatingProfile executed via Salon / SaM - Mode auto - iPhone on io://1233-4449-5614/11530893#2, with [].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:19: setHeatingOnOffState executed via Parents - Off - iPhone on io://1233-4449-5614/11530893#6, with ['off'].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:19: refreshPassAPCHeatingProfile executed via Parents - Off - iPhone on io://1233-4449-5614/11530893#6, with [].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-11 20:47:24: refreshOperatingMode executed via Parents - Mode manu - iPhone on io://1233-4449-5614/11530893#1, with [].
2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-11 20:47:24: setHeatingOnOffState executed via Parents - Mode manu - iPhone on io://1233-4449-5614/11530893#6, with ['on'].

1st i clicked on 'Parents' and set it to off
after a while i clicked on 'Salon/SaM' and set it to 'Prog' mode

So i guess:

Set 'Parents' to Off is:

2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:19: setHeatingOnOffState executed via Parents - Off - iPhone on io://1233-4449-5614/11530893#6, with ['off'].

Set 'Salon/SaM' to 'Prog' is:

2021-02-12 01:04:04 INFO (MainThread) [custom_components.tahoma] 2021-02-12 01:02:41: setPassAPCHeatingMode executed via Salon / SaM - Mode auto - iPhone on io://1233-4449-5614/11530893#2, with ['internalScheduling'].

@iMicknl
Here a more detailed list:
SET "Parents" to "Prog" (Schedule mode)

2021-02-12 22:22:54: refreshPassAPCHeatingProfile executed via Parents - Mode auto - iPhone on io://0000-1111-2222/33334444#6, with [].
2021-02-12 22:22:54: refreshTargetTemperature executed via Parents - Mode auto - iPhone on io://0000-1111-2222/33334444#6, with [].
2021-02-12 22:22:54: setPassAPCHeatingMode executed via Parents - Mode auto - iPhone on io://0000-1111-2222/33334444#6, with ['internalScheduling'].
2021-02-12 22:22:54: refreshOperatingMode executed via Parents - Mode auto - iPhone on io://0000-1111-2222/33334444#1, with [].

SET "Bureau" to "Prog" (Schedule mode)

2021-02-12 22:24:30: refreshPassAPCHeatingProfile executed via Bureau - Mode auto - iPhone on io://0000-1111-2222/33334444#10, with [].
2021-02-12 22:24:30: refreshTargetTemperature executed via Bureau - Mode auto - iPhone on io://0000-1111-2222/33334444#10, with [].
2021-02-12 22:24:30: setPassAPCHeatingMode executed via Bureau - Mode auto - iPhone on io://0000-1111-2222/33334444#10, with ['internalScheduling'].
2021-02-12 22:24:30: setHeatingOnOffState executed via Bureau - Mode auto - iPhone on io://0000-1111-2222/33334444#10, with ['on'].
2021-02-12 22:24:30: refreshOperatingMode executed via Bureau - Mode auto - iPhone on io://0000-1111-2222/33334444#1, with [].

SET "Bureau" to "Manuel | 19°c" (Manual mode)

2021-02-12 22:27:19: refreshPassAPCHeatingProfile executed via Bureau - Mode manu - iPhone on io://0000-1111-2222/33334444#10, with [].
2021-02-12 22:27:19: refreshTargetTemperature executed via Bureau - Mode manu - iPhone on io://0000-1111-2222/33334444#10, with [].
2021-02-12 22:27:19: setHeatingTargetTemperature executed via Bureau - Mode manu - iPhone on io://0000-1111-2222/33334444#10, with [19].
2021-02-12 22:27:19: setPassAPCHeatingMode executed via Bureau - Mode manu - iPhone on io://0000-1111-2222/33334444#10, with ['manu'].
2021-02-12 22:27:19: refreshOperatingMode executed via Bureau - Mode manu - iPhone on io://0000-1111-2222/33334444#1, with [].

SET "Bureau" to "Off"

2021-02-12 22:28:00: refreshPassAPCHeatingProfile executed via Bureau - Off - iPhone on io://0000-1111-2222/33334444#10, with [].
2021-02-12 22:28:00: setHeatingOnOffState executed via Bureau - Off - iPhone on io://0000-1111-2222/33334444#10, with ['off'].

SET "Bureau" to "Absence" (away|holliday mode)
N.B.: even if this command is targeting 'Bureau' it indeed applied to the whole instalation (which make sense for away mode anyway)

2021-02-12 22:28:55: setAbsenceEndDateTime executed via Bureau - Mode vacances - jusqu'au 13/02/2021 - iPhone on io://0000-1111-2222/33334444#1, with [{'year': 2021, 'minute': 28, 'month': 2, 'hour': 22, 'day': 13}].
2021-02-12 22:28:55: setAbsenceStartDateTime executed via Bureau - Mode vacances - jusqu'au 13/02/2021 - iPhone on io://0000-1111-2222/33334444#1, with [{'year': 2021, 'minute': 28, 'month': 2, 'hour': 22, 'day': 12}].
2021-02-12 22:28:55: refreshOperatingMode executed via Bureau - Mode vacances - jusqu'au 13/02/2021 - iPhone on io://0000-1111-2222/33334444#1, with [].
2021-02-12 22:28:55: setPassAPCOperatingMode executed via Bureau - Mode vacances - jusqu'au 13/02/2021 - iPhone on io://0000-1111-2222/33334444#1, with ['stop'].

Hope this can help you. Looking at the other mentionned issues it seems to have a lot in common with Atlantic HeatPump and other Atlantic devices.
Just tell me if you need something else or a way we can help you

Thanks @fredleger. I see that many of your commmands are executed on io://0000-1111-2222/33334444#10, but I don't see any mention of a #10 device in your posts? Do you know which device is #10.

Hummm @iMicknl not sure what is a device here. I would have expected that all command goes through the device representing the room where i set the temperature.
So i can only guess here ...
I own only 2 "physical" devices:

Somfy Conexoon
Atlantic Shogun AC
Somfy Shutter

and i do thhink they have differents IOs ids
So my best idea is that #10 is the main controller of Atlantic shogun AC which i was sending commands to but can't be sure. Is there any way to debug this with browser devtools or so ?

ok i found it through the web interface
On my Setup:
#2 is Salon/SaM
#6 is Parents
#10 is Bureau

Tell me if this helps

@fredleger sorry, I already found it thus removed my comment. But I guess you got an email reply as well :-).
You did mention the device ids in your previous post already. We need to map every subdevice in Home Assistant, thus it is good to understand how they work together..
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlMainComponent - HeatingSystem - AtlanticPassAPCZoneControl - io://1233-4449-5614/11530893#1)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#10)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#11)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#2)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#3)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#4)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#5)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#6)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#7)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Unsupported TaHoma device detected (io:AtlanticPassAPCZoneControlZoneComponent - HeatingSystem - AtlanticPassAPCHeatingAndCoolingZone - io://1233-4449-5614/11530893#8)
2020-12-27 15:55:20 DEBUG (MainThread) [custom_components.tahoma] Added Device (io:AtlanticPassAPCZoneTemperatureSensor - TemperatureSensor - TemperatureSensor - io://1233-4449-5614/11530893#9)

@fredleger by the way. If you are willing to work with me via Discord and to share your credentials temporarily, feel free to let me know. It would speed up the development a lot, since those climate devices are hard to understand and implement. With other users I have seen that this helps to create a basic version in less than an hour, instead of going back and forth. (Discord: https://discord.gg/ENPcXd9j, or iMick#1903)

/reopen
Sorry was quite a busy period and i hadn't much free time to contact you
I will try to do it very soon
Le jeu. 18 mars 2021 à 03:13, github-actions[bot] @.***>
a écrit :

'There hasn't been any activity on this issue recently. Is this issue
still present?
Please make sure to update to the latest Home Assistant version and
version of this integration to see if that solves the issue. Let us know if
that works for you by adding a comment 👍.
This issue now has been marked as stale and will be closed if no further
activity occurs. Thank you for your contributions.'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/iMicknl/ha-tahoma/issues/322#issuecomment-801563187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVGM5PKITS6D5H5ZHXMRBLTEFOTVANCNFSM4UUE3UFA
.

/reopen still an issue
will contact @iMicknl

Invite sent my discord id is FredLight#2093

https://github.com/dubocr/homebridge-tahoma/blob/73f9a6200c64ac8179a3ff60e864762f58bfdff0/src/mappers/HeatingSystem/AtlanticPassAPCHeatingAndCoolingZone.ts
It seems that we need to inherit the cooling or heating state from the parent device...

I have been using it for quite a time now and don't see any defect.
There was some error but i dig it to tahoma server side transient errors (they might be something here but at the end it's very usable).
Even the cooling system is working too but the UI can be refactored. For cooling mode you must put the main control in cooling mode and then put the desired device in "heating" mode. Conceptually strange but works... So maybe "heating" should be "on" if possible in HA.
For me it's seems it could merged in main
Thanks for the help here ! Great work.

Does this get merged at some point ?
The bot comments let me think that this was not merged. If this is the case it's might better to reopen it ?

Hi @fredleger, sorry for the late reply. I have been very busy lately, but will see if I can pick up some of the open issues like yours this week.

Even the cooling system is working too but the UI can be refactored. For cooling mode you must put the main control in cooling mode and then put the desired device in "heating" mode. Conceptually strange but works... So maybe "heating" should be "on" if possible in HA.

Could you perhaps help me by creating a new issue about this? (with as much info as possible). This will be something I would like to fix in the coming months, but not on short term.


Create request, add members - why is this limited to two?

When making a request, is there a specific reason for limiting the number of members that can be added to two? The restriction is not on the combobox itself, but lblMembersErrorMessage is shown If(CountRows('cmbMembers.'.SelectedItems)>2,"Error").
Looking at the ProcessTeamRequest Logic App, when looping through members, there is no restriction set on the number of @triggerBody()?['Members'] so to my mind it should be possible for the requester to specify as many members as required?

@aqyx I will be removing this limitation from the frontend Power App - stay tuned for an update shortly.

I am interested in this limitation as well. Once you have removed it from the Power App, what will I need to do to update our end? Will it be as simple as re-importing the Power App?


DNSBin is broken

Trying to use the DNSBin just shows an empty page, and the devtools show errors in the websocket connection. Tried from 2 different browsers and IPs.
dns:34 WebSocket connection to 'wss://dns.requestbin.net:8443/dnsbin' failed: Error during WebSocket handshake: Unexpected response code: 521
createSocket @ dns:34
04:02:50.983 dns:112 Uncaught TypeError: Cannot read property 'appendChild' of null
    at WebSocket.socketConnection.onclose (dns:112)

Hi! Any update on this?

Hello, @mxcxvn Still this source code and website are broken in dns functionality!


Added a command to install squashfs-tools in README.md

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Left one comment as to where I'd expect squashfs-tools to be mentioned in README.md.
Also, you need to sign-off your commit (see CONTRIBUTING.md) before we can merge it.

Oh and when updating README.md, you may also want to list rsync in that same package list as it appears to be missing (tar, xz and acl are already there).

I have signed off my commits.

@DilipRenkila you've committed you're IDE sources. Also, you need to squash changes.

I removed my IDE sources and also i have an idea to develop a clustering application for LXD based on groups. Any Suggestions are welcome.

@DilipRenkila now it looks like this PR is totally messed up. )

Oh wow, this is in fact very messy :)
You really want to rebase your branch on master which should result in just your one commit showing up here.
Given that your change is properly signed-off, I can also just cherry-pick your commit into my bugfix branch and close this pull request if it's easier for you.


react-snapshot not crawling nested detail pages

I have routes of the form
/
/todos
/todos/1
/todos/2

and I have noticed that react snapshot does not create an html page for /todos/:id. Is there anyway to fix this aside from adding into package.json the explicit paths /todos/1 and /todos/2?

from readme

React-snapshot will crawl all links that it finds. You can create "site map" page, which will contain links to all pages.

Not sure how that helps if I have dynamic ids with 50,000 todos.

React-snapshot is also not able to see the links.

This sounds like a bug. Provide reproducible example.

@stereobooster Thank you for responding.
I apologize for the confusion. React-snapshot is not able to see the links because they are dynamic. They are only added to the page when the backend returns a list of todos. The reason it is not seen is because my backend server blocks any request from unknown domains so the fake browser that react-snapshot uses will not get a list of todos.

I suppose you want to whitelist react-snapshot. Also as of now react-snapshot uses default jsdom user agent, but this is possible to change.
There is an issue with async data https://github.com/geelen/react-snapshot/pull/30

@AaronCCWong I know I'm late for the party but had similar issue for the last three days and boy haven't I tried out everything. Turns out the code looks for either  with href or  with src attribute. My case, I didn't have either, just had a button. It took only 15 minutes or less going through the react-snapshot code-base to find out why it couldn't crawl through my dynamically generated pages. This was after 3 gruesome days of trying to find out why my build left all dynamically generated pages.


Make all the Atoms immutable

Initially I've tried to do that as part as #123, but now I have a "bright" idea to land it to the master branch before merging #123. The reason is: in #123 we have more changes to apply, so I'd like to separate the mutability changes and test them in isolation from SourceSpan and friends.
So, in #123, we've got ourselves into various troubles because our Atoms are mutable objects: we can't cache them, it's difficult to (safely) clone them etc.
I think we need to make all of our Atoms immutable (i.e. no writable or otherwise mutable properties; List will be banned and replaced with ReadOnlyCollection; every public setter will be replaced with a method that creates a changed copy of a current object). It will require some nontrivial changes to our code base, but I think it'll be worth.
Some of the methods' signatures will change, but as Atom is an internal class, almost none of our public APIs will change (and that's always a good thing).
That's a critical task for #123.

We have to make them mutable to support the \atop, \choose and \over commands.

I don't think so. Generally, in the cases you want to change something you just construct new changed copy of immutable data. In practical applications it tends to work very well.
Consider you want \atop {ATOM} to change the ATOM is some way. It should work like that:

Immutable ATOM is constructed by the parser.
\atop command wants to change ATOM in one way or another
\atop just takes the ATOM and creates a copy with changed data (e.g. new height value or such).

We, indeed, have some issues with creating immutable copies of our stuff, but all of them are solvable. Feel free to ask questions!


make testable on test.wikidata.org and beta

Please make this testable on test.wikidata.org and wikidata.beta.wmflabs.org .
To support this use absolute URLs in the frontend JS for loading scripts and css. And replace importStylesheet with the mw.loader.load variant, because it doesn't support absolute URLs.
Then it can be loaded from e.g. test.wikidata.org without needing to duplicate the code on local wiki pages.
If the tool has specific known property IDs then those need to be different for test and beta.

The first two lines that were relative I have seen:
var asyncSrc = '/w/index.php?title=User:Tomayac/async.js&action=raw' +'&ctype=text%2Fjavascript';
importStylesheet('User:Tomayac/freebase2wikidata.css');

This ticket was reported while https://phabricator.wikimedia.org/T95289#1265861 .

Thanks for the issue report, closed it with https://github.com/google/primarysources/commit/cc2da3c08b7663a24343d7dd94b34410e7d84d68, all URLs of external sources are absolute now.


Screen flicker occurred on Rust project

Type: Performance Issue
Screen flicker occured on Rust project, but not on any other languages project.
Reproduce a issue:

clone some rust project: github.com/startship/starship
open this repository on VSCode
open Rust code
coding, window width changing

Screen flicker like this:
https://github.com/microsoft/vscode/assets/42367320/020b8dce-d156-4728-94d5-cb36a036b00a
VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:57:32.750Z)
OS version: Darwin arm64 23.1.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Max (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
4, 4, 5

Memory (System)
64.00GB (7.22GB free)

Process Argv
--crash-reporter-id 67a27090-cfea-48f8-ad1e-a9f4fc0b89f6

Screen Reader
yes

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
   18	   262	  7271	code main
    6	    66	  7276	   gpu-process
    0	    66	  7277	   utility-network-service
   65	   918	  7279	window [1] (Startup Performance — data-processor)
    0	    66	  7592	ptyHost
    0	     0	  7874	     zsh (figterm)
    0	     0	  7894	       /bin/zsh --login
   46	   197	  7644	shared-process
    0	     0	 14265	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    66	 13495	fileWatcher [1]
    0	   197	 13496	extensionHost [1]
    0	    66	 13734	     electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=13496)
    0	    66	 14098	     electron-nodejs (/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) --ms-enable-electron-run-as-node /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/markdown-language-features/server/dist/node/workerMain --node-ipc --clientProcessId=13496)
   32	    66	 14263	window [3] (Issue Reporter)

Workspace Info
|  Window (Startup Performance — data-processor)
|    Folder (data-processor): more than 23420 files
|      File types: html(9210) o(4461) js(723) json(646) timestamp(499) d(449)
|                  rmeta(386) rlib(188) bin(119) rs(49)
|      Conf files: github-actions(1);

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263cf:30856253
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
89544117:30613380
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
copilotsettingc:30859502
synctok:30869157
dsvsc013:30795093
dsvsc014:30804076
pythonmhint1:30842940
dsvsc015:30845448
pythontestfixt:30871694
pythonregdiag2cf:30871583
pyreplss1:30865275
pythoncet0:30866520
2e7ec940:30870395
pythontbext0:30864172

Does this reproduce in other workspaces (languages) as well, or is this rust-specific?

Yes, rust-specific on my local development environment at least.
It happens even when all the VSCode extensions are disable.
However, this screen flickering doesn't always occur. Thus, it's hard to reproduce consistently. (Unfortunately, it doesn't occur right now while I'm writing this comment...)
But, this screen flickering always occurs in the window where I'm writing code on Rust project. Even if I have multiple windows open, including Rust projects and, for instance, TypeScript and Go projects, the flickering always occurs only in the window with the Rust project.
Lately, this has been happening frequently while I'm working, and it's been distressing. I'd be happy to help, so could you tell me how to investigate this phenomenon on VSCode? What should I pay attention to the next time this phenomenon occurs?
Let me know if you need any more information.

Can you provide the output of system_profiler SPDisplaysDataType. Do you have a multi monitor setup or using something like https://github.com/waydabber/BetterDisplay to get HiDPI ?

I am using two external monitors with FHD and 4K resolutions. I'm not sure if it's related, but I am using an application MonitorControl to control display settings with DDC protocol.

Result of system_profiler SPDisplayDataType is the following:
$ system_profiler SPDisplaysDataType

Graphics/Displays:

    Apple M1 Max:

      Chipset Model: Apple M1 Max
      Type: GPU
      Bus: Built-In
      Total Number of Cores: 32
      Vendor: Apple (0x106b)
      Metal Support: Metal 3
      Displays:
        Color LCD:
          Display Type: Built-in Liquid Retina XDR Display
          Resolution: 3024 x 1964 Retina
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
          Connection Type: Internal
        PL2790:
          Resolution: 1920 x 1080 (1080p FHD - Full High Definition)
          UI Looks like: 1920 x 1080 @ 60.00Hz
          Mirror: Off
          Online: Yes
          Rotation: Supported
        DELL U3223QE:
          Resolution: 5120 x 2880 (5K/UHD+ - Ultra High Definition Plus)
          UI Looks like: 2560 x 1440 @ 60.00Hz
          Mirror: Off
          Online: Yes
          Rotation: Supported

Can you clarify if the rust project window is placed on the primary built-in display or any of the external displays when the flickering happens. Can you try to narrow down if a particular display is trigger for the issue.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Can you clarify if the rust project window is placed on the primary built-in display or any of the external displays when the flickering happens. Can you try to narrow down if a particular display is trigger for the issue.

@deepak1556 Screen flickering occurs on an external 4K display, doesn't occur on built-in Retina display. Output of system_profiler SPDisplaysDataType is the following:
$ system_profiler SPDisplaysDataType

Graphics/Displays:

    Apple M1 Max:

      Chipset Model: Apple M1 Max
      Type: GPU
      Bus: Built-In
      Total Number of Cores: 32
      Vendor: Apple (0x106b)
      Metal Support: Metal 3
      Displays:
        Color LCD:
          Display Type: Built-in Liquid Retina XDR Display
          Resolution: 3024 x 1964 Retina
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
          Connection Type: Internal
        Pro Display XDR:
          Display Type: 2D backlit LCD
          Resolution: 6016 x 3384 Retina 6K
          Display Serial Number: C02GL03YML9W
          Display Firmware Version: 4.2.37
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: Yes

Thanks for testing, the relevant issue is tracked in
Can you check if the issue is resolved with our exploration build based on a newer version of the runtime.


Hardcoded db in postinstall script

The Vercel Serverless Functions example app has a postinstall script that is referencing a certain db
https://github.com/xataio/examples/blob/main/apps/starter-vercel-serverless-functions/package.json
This causes pnpm install to error for users who don’t have access to that workspace, which can be misleading for users who want to test out other apps.
 pnpm install
Scope: all 7 workspace projects
../..                                    |    +1209 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
../..                                    | Progress: resolved 1209, reused 1131, downloaded 0, added 1209, done
<EMAIL_ADDRESS>Running install script, done in 1.7s
../sample-imdb postinstall$ pnpm tailwind
│ ><EMAIL_ADDRESS>tailwind /Users/kostas/workers-demo/examples/apps/sample-imdb
│ > tailwindcss -i styles/globals.css -o styles/dist.css
│ Done in 86ms.
└─ Done in 931ms
. postinstall$ npx @xata.io/cli codegen --db="https://xata_examples-hf8grf.eu-west-1.xata.sh/db/marvel" -b="main" -o="_lib/xata.codegen.ts"
│ npm ERR! Cannot set properties of null (setting 'peer')
│ npm ERR!      /Users/kostas/.npm/_logs/2022-11-28T16_48_11_368Z-debug-0.log
└─ Failed in 1.8s
 ELIFECYCLE  Command failed with exit code 1.

This has been worked around by suggesting npm in other apps instead of pnpm.


Add FileFlows

---
base_pricing: 20
currency: USD
free_sso_providers:
  - OpenID Connect
name: FileFlows
notes: n/a
pricing_scheme: per month
pricing_sources:
  - https://fileflows.com/pricing
scim_pricing: n/a
sso_pricing: 100
updated_at: 2024-07-14
vendor_url: https://fileflows.com/

Hey @sahmeepee , thanks a lot for your contribution! Added it!


WASM as a KRM function runtime

WASM can be potentially used as a KRM function runtime and KRM function packaging method.
Exploration in the area is in progress. More details will be updated in this thread.

wasm function runtime is implemented in https://github.com/GoogleContainerTools/kpt/pull/3450.

We can close this issue since WASM support was added in https://github.com/GoogleContainerTools/kpt/pull/3450.
I opened another good first issue for publishing end user docs for this feature. https://github.com/GoogleContainerTools/kpt/issues/3755


[Proposal] Support conditional matrix on GitHub Actions

The length of CI script is inefficient since GitHub Actions does not support condition matrix strategy or conditional matrix computation yet. Currently, I approached via variable separation but it should not be done in this way.

Related: https://github.com/community/community/discussions/9044#discussioncomment-1898579


Keep Participants visible while scrolling

https://github.com/mermaid-js/zenuml-core/assets/32098252/cdee3a36-e4c1-44d2-85e0-cf6cfe5755b7

Looks very good.
不知道是不是给它们一个背景跟其他图层清晰的隔离开更好看？

没想好，感觉给没边框的加上边框就够了？大片背景感觉不会好看

https://github.com/mermaid-js/zenuml-core/assets/32098252/ad026f4a-e46c-46d8-a0e8-9f1e60fe0d2b

Can you please the design decision on reusing life-line-layer instead of splitting it into two components?

The main reason is that this is more convenient and requires the least changes. If a new layer is written, both line and lineGroup would have to be divided into two, even though their logic is the same. If it is reused, the subsequent maintenance will be almost the same as before. The disadvantage might be that people who are not familiar with it may be confused when they see these two identical layers (I personally think it's okay), and there may be duplicated logic in the two instances. For example, if there are some logs inside, it should be logged twice.