Toggle "Follow Me" from integration?

I'm not sure if this is possible, but I notice that my unit has a "follow_me" mode. This toggles between a sensor in an unknown location (maybe intake vent?) and the thermostat in the wall controller.
In most cases, the temp sensor in the wall controller is probably the one I want to get readings from - and is active when follow_me: true is in the device attributes:

I get two sensors for temperature in the device:

I believe the "Indoor" temperature probe is likely the one I don't know the location of - but nothing seems to return the wall control temperature.
Sometimes, it would be good to toggle the follow_me option from remote to change which sensor is in use. When turning it off on the wall controller, the attribute correctly changes to false.
That means its reading the value correctly, but it doesn't seem to be able to change this value?
On another related note, being able to get the temperature of the wall controller would be fantastic if this is possible. Currently, in HA I display a reading from my ZoneTouch 3 ducting controller which site just to the left of the wall control panel - and the readings between the "Indoor" sensor and the ZT3 makes me believe the sensors are in different locations.

The integration supports setting follow_me via a service/action call.

Some additional details in this PR: https://github.com/mill1000/midea-msmart/pull/91
It's an experimental feature and I've seen mixed success from users.

On another related note, being able to get the temperature of the wall controller would be fantastic if this is possible. Currently, in HA I display a reading from my ZoneTouch 3 ducting controller which site just to the left of the wall control panel - and the readings between the "Indoor" sensor and the ZT3 makes me believe the sensors are in different locations.

I can only report what the device sends me. I'm not currently aware of any other temperature sensors I can report. This is the first time I've heard of a wall controller for these devices.

Interesting, thanks. I tried setting the following action without success:

The attributes still show follow_me: true
For reference, this is my install:

The unit is made by these guys:
https://www.rinnai.com.au/online/air-conditioning/ducted-air-conditioners/ducted-reverse-cycle/
The Wifi module is a 'B064869 Smart Port WiFi OIM kit" Manual attached, because why not :D
B064869 Smart Port WiFi OIM Issue 1 April 2019 V2 (2).pdf
Annoyingly, it comes with an IR remote control that the ONLY button that works is the button to set the Wifi module into pairing mode so you can connect it to wifi. It doesn't have any other operations or functions. Total waste of a remote control and IR receiver :laughing:

Can you enable debug logging and try the service again? Perhaps it's not setting the bit as I expect.
Is there any form of OEM app that can control this follow me mode for your unit, or is it solely based on the control panel?

As requested:
2024-09-07 13:18:11.847 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac00000000000003418100ff03ff000200000000000000000000000003ca831b
2024-09-07 13:18:11.848 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000540b1203070918146db307000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b30b7d1adca2c4d4cd1ba595d032b97b5f79ab27472366a3b8159e8b6704d997c59c03ac2c7541d3feaaeac549abf43dbc
2024-09-07 13:18:11.849 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e206694f8b53c95ea3f76ea5aebd81a892e934742dd5b7e690132466b2a33c2521c727844edcd9aef12cf12a9b3b781e6dcf7472df32dc977a7a7609e93a412ea604c523f2e73d658761a9d918f6cce6b56fcb0cf9f5ffd258542a9786ed7f1a3702cce915c8624c2815d40bc23c5a95674b57f514d5cc441b95948624825c166b0ae146d2e00bebc06687ae9f68ccffb3ed3
2024-09-07 13:18:11.936 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e2063db2662fa8d132505abdce7898d0b44ab42e93e0336aed033c3e19671563a9c99038e720ff9ceb5aa7a64980aa601d611277d2efbca9c90000d0d29eec2e4be7c0d5c2c1d677caf3d2cc30fef2c25a7642073f92caf4d441ab56c5be293bda979969a3dc1240ce2b8a6be6cc8dcf65689f33ff768caf920622c786e5226a42608c6dd41eb0139994af49553bbcbf37074
2024-09-07 13:18:11.937 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a0111680020800000000000000000000000006db3070000890000000000000000000000000000c7e33322591b889ef841d027e6d53b63a35257479efa1367694eb2c5c30f4d71719c8d6623206accd86c0d3d431fb9ff79a4d0d737214fc5a94e87c17935ea68
2024-09-07 13:18:11.938 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c001a6507f7f0030000000635f00000000000000000083b250
2024-09-07 13:18:11.938 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.090000 seconds.
2024-09-07 13:18:11.938 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c001a6507f7f0030000000635f00000000000000000083
2024-09-07 13:18:11.938 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.091 seconds (success: True)
2024-09-07 13:18:14.145 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa24ac000000000000024003a6507f7f003000000000000000000000000000000000cb8775
2024-09-07 13:18:14.146 DEBUG (MainThread) [msmart.lan] Connection to <IP_ADDRESS>:6444 has expired.
2024-09-07 13:18:14.146 DEBUG (MainThread) [msmart.lan] Disconnecting from <IP_ADDRESS>:6444.
2024-09-07 13:18:14.146 INFO (MainThread) [msmart.lan] Creating new connection to <IP_ADDRESS>:6444.
2024-09-07 13:18:14.155 DEBUG (MainThread) [msmart.lan] Connected to <IP_ADDRESS>:6444.
2024-09-07 13:18:14.158 INFO (MainThread) [msmart.lan] Authenticating with <IP_ADDRESS>:6444.
2024-09-07 13:18:14.158 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444:<PHONE_NUMBER>00000018bf9c4cb6b1b5b44d7ca548cfb6efdb46d39e740b9d39ea71e1ff5589e1f9ba8f7dfd5bcd872a0961923ab282353a7bc6e1b99a02521a46ca605c05bb3eab0e
2024-09-07 13:18:14.188 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444:<PHONE_NUMBER>0100008f13ddc1332d5a1485bce9cb956f23435425f457021c389b7e3ae342e63f55e361c103010b9c1fedccb0a2e27417f362e192a1062b146c0ebf8e5b02be91650d
2024-09-07 13:18:14.189 INFO (MainThread) [msmart.lan] Authentication with <IP_ADDRESS>:6444 successful. Expiration: 2024-09-07T15:18:14+00:00, Local key: 00a69cc7583c7c74ecbc1798b7b9d5d57423f593feb0f97a815014810966e57f
2024-09-07 13:18:15.190 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000130f1203070918146db307000089000000000000000000000000000054cc3c3ea2c5c6f295152f6dbfbbf6f58b0164f204b60803fd1e0ea38206e81cc7b904c22dca512a96a2ec282e86aa58fdf00a394089aa993159243a0df490eb
2024-09-07 13:18:15.190 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e20664ffdf9775a54a12f08384dc9fd2de16eb37f552a8dfb270f5caedfd08670e0ccdbf149b30541fa1359e7cd45786af141256a8ade8b5f3247b4abb5a77d255af6d2435857024f2ca9ec6f9339f00eee182809ea6498940a6b9c3ebc69ea7e865362f01bfbb1837000c9778213f42d522c44b5c1a7c1581a87431ca0178f51ac98b694e11281bd427d351134e96dc9fb61
2024-09-07 13:18:15.843 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e20638caaa750fcf3db0d7908cec8b91b7d223800f70131fd8f226529f47c88af0bfbfac6184757eb04960009cd4ddd2c8763d675cebc6a697d6c2fc49333b91f0bd0d492c5db7b715ea6bcc8511426bfc1c2b3b915cb1b4c6e75aa539ec76df25c46b4c0ff9fb98e5adb99fe9005c906dda7df47fad285f11e252bdd34d7df5e244672df4c793d9aae2d0c2f3e6ace8c222a
2024-09-07 13:18:15.844 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a0111680020800000000000000000000000006db3070000890000000000000000000000000000b2551b9a1549e4db0a4adc890fcc8594a35257479efa1367694eb2c5c30f4d71592dbb88b3c7cf970a7e64cd2996ad783300c57bbc369ddedc21098aaa87e15a
2024-09-07 13:18:15.844 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000302c001a6507f7f0030000000635f00000000000000000000dcaa
2024-09-07 13:18:15.845 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 1.700000 seconds.
2024-09-07 13:18:15.845 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c001a6507f7f0030000000635f00000000000000000000
2024-09-07 13:18:15.845 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac00000000000003418100ff03ff000200000000000000000000000003cc5e3e
2024-09-07 13:18:15.850 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a01116800200000000000540f1203070918146db307000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b369f92e59c9a22c84d55711cfbdbcf74dcca640b70e6ea249061c9c01fa576d2e14c731ca9acc82b4e811a4e0fc52c41b
2024-09-07 13:18:15.850 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e2066661f6b9a8a5190de4fb57cebe111270f3b681063d262c91a5912e10dec08668f1f1542f54db556bdb7c5f5d3704a00f961b337bd023c8ab2f4b485acb7ed429bab626f09fd3bd4db238f803c7b708b6f562f431d520a35b67fb68bda49ad2f7a2ae3faeff4b56e4ec5b0c6dfac140e31edb2cbcc529af89935f921b525761f93b9c273c95d5f4197dfdf752c3ad272be
2024-09-07 13:18:15.931 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e2063ae750be84a52c62894d4cd53697adc34ce8cc01e703db8d929b492d293bfa33ecc5d022d54d2988f8c36d39a22bc99d90fc1c0e0397e28b52cb881a1fa8202af3b7defc7c0b24367f09e7e4ce47ab6c16d54a173e8ac96cc241d7e61a299960405d0314be7da771e0a34a16163826dadded6eee1b494f90979a9249dfd1d303fa7072827a0ca438b68332ad4767ecb6f
2024-09-07 13:18:15.931 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a0111680020800000000000000000000000006db3070000890000000000000000000000000000c7e33322591b889ef841d027e6d53b63a35257479efa1367694eb2c5c30f4d71ba1c567b9b91f9bed418a02634f2fd7f008787c8eafb4348e61dda4d04272ab4
2024-09-07 13:18:15.931 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c001a6507f7f0030000000635f0000000000000000005e180f
2024-09-07 13:18:15.931 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.090000 seconds.
2024-09-07 13:18:15.932 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c001a6507f7f0030000000635f0000000000000000005e
2024-09-07 13:18:15.932 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.086 seconds (success: True)
2024-09-07 13:18:16.934 DEBUG (MainThread) [msmart.base_device] Sending command to <IP_ADDRESS>:6444: aa21ac00000000000003418100ff03ff000200000000000000000000000003cd009b
2024-09-07 13:18:16.935 DEBUG (MainThread) [msmart.lan] Sending packet to <IP_ADDRESS>:6444: 5a5a011168002000000000005d101203070918146db307000089000000000000000000000000000065cd8728fc6a5d31e6464235e81fa3b3c4af172d627dc261b35011770d101306985367d7041250269ca4cb48f887e5028df87e20f35d998cbcbb179f70835888
2024-09-07 13:18:16.936 DEBUG (MainThread) [msmart.lan] Sending data to <IP_ADDRESS>:6444: 8370008e2066f1134ce972f0d568141dc2fa80ebe4f9c0678d70a7c0c7f6ce9e7b14c6a58933f8373d7d9a8d2158732eb9f7e7e7bc5bb37fac67ba487206b513e1dbabdd8842d341d81bfd66773beb2cba31b80461f86ac32845ee6dfaf282382cde52dfd430ce7a0398e4be1d38f7611f332b5b099f1158b049152e89e3ef351713f8b221410c0757ef90e0b91dd7c3fb149d373a2e
2024-09-07 13:18:17.017 DEBUG (MainThread) [msmart.lan] Received data from <IP_ADDRESS>:6444: 8370008e206343c82da7d553693775124b3adb46dc47944c825787a7a2f4d22051ee63e63ea9b02b92c5f3ac1a3eec67f3cf3bc21785021e6cd104d84f883ba3661760fd333c7f2194df4b2ad9805cd0f9c9bca46d17a68fbff47fb64a3a2ce19309cc22b17d18c9f24d790191beb669d853ee49ad9c67a58f1b96fbe783300478718d6dbe2a0b799bf3f8eb2d63310dedbb8a30807f
2024-09-07 13:18:17.018 DEBUG (MainThread) [msmart.lan] Received packet from <IP_ADDRESS>:6444: 5a5a0111680020800000000000000000000000006db3070000890000000000000000000000000000c7e33322591b889ef841d027e6d53b63a35257479efa1367694eb2c5c30f4d71586706a0f9c65ab1a68da1a9977f8e96c78a5ed7f81acbc8595cdf756a232095
2024-09-07 13:18:17.019 DEBUG (MainThread) [msmart.lan] Received response from <IP_ADDRESS>:6444: aa22ac00000000000303c001a6507f7f0030000000635f00000000000000000000dca9
2024-09-07 13:18:17.019 DEBUG (MainThread) [msmart.base_device] Response from <IP_ADDRESS>:6444 in 0.080000 seconds.
2024-09-07 13:18:17.019 DEBUG (MainThread) [msmart.device.AC.command] State response payload: c001a6507f7f0030000000635f00000000000000000000
2024-09-07 13:18:17.019 DEBUG (MainThread) [custom_components.midea_ac.coordinator] Finished fetching midea_ac data in 0.086 seconds (success: True)

In the manual, they use Nethome Plus app.  It just gives me the presets Boost and Sleep Curve - which you already have support for (and I really have to figure out what they actually do one day)...
I don't see anything about changing the Follow Me mode...

This is the app page for the sleep curve...

If I'm reading the logs right, they all show follow_me as off. Did the attribute say otherwise?
Maybe a good test would be to collect logs for the following.
A. Turn follow_me On then Off at the control panel. Wait 20 seconds between changes.
C. Use the service to set follow_me On, then again to set Off.
Re: Sleep curve. The integration supports the sleep preset, not sure how/if that's related to sleep curve or not

To start with, Follow Me was ON from the control panel. I turned it off at the control panel, waited ~20 seconds, then turned it back on again.
Log attached:
home-assistant_midea_ac_2024-09-12T06-28-49.160Z.log

Second log, started with Follow Me turned ON at the control panel... Called the action to turn it OFF... Wait ~20 seconds... Call the action to turn it back ON...
Log attached:
home-assistant_midea_ac_2024-09-12T06-33-09.411Z.log

So, there's two modules I guess.... One is the module that adds wifi - which is what I'm using with this integration.
The other is the square one on the left side of the picture above. If I remember correctly, part of installing the 'wifi module' means disconnecting the wall wired panel, then hooking it to the wifi controller. The wifi controller then connects to the mainboard in the main unit in the roof. I'm guessing its some kind of RS422 or similar over the actual cable - and both just talk over the same bus.
I might be wrong on the RS422 bit - but information is pretty scarce about it...

I might be wrong on the RS422 bit - but information is pretty scarce about it...
Is there much in the way of documentation for the protocol?

Nothing official. Typically there's a UART interface between the WiFi module and AC device. The signalling has been TTL in the units I've tested but there's no reason it couldn't be RS232, RS422 or RS485.
The LAN protocol is a thin wrapper around the UART protocol that provides some encryption and authentication. The WiFi module receives packets, decodes and extracts a payload and forwards it over UART.
A worthwhile reference
https://github.com/dudanov/MideaUART

Hello, I think in this case it is the same cause as with my system, a VIVAX R Design ACP-12CH35AERI+.
With this system, follow_me cannot be activated via app (NetHome Plus), but only via IR remote control. The status of the attribute "follow_me = false" does not change.  The status cannot be changed to "true" using the actions in the developer options either. The AC acknowledges the change with "Peep", but cannot do anything with the command sent.
The reason behind this is actually quite simple with my system. "follow_me" is not switched in the AC indoor unit. The indoor unit constantly listens to whether an external temperature sensor is sending signals. If this is the case, it automatically uses it instead of using the built-in temperature sensor.
The button on the remote control only activates/deactivates the temperature sensor in the remote control and the integration has no influence on this.
In the case of the wall sensor here, it will probably be comparable. If it is "active" then it is used preferentially. If the system no longer receives signals from the wall sensor, it automatically uses the integrated sensor again.
Summary: If "follow_me" cannot be activated/deactivated via the app, the integration has no way of having an influence.

Summary: If "follow_me" cannot be activated/deactivated via the app, the integration has no way of having an influence.

I think this may well be the case - being that the integration will be able to REPORT the value, but not SET the value.
I'll close this off - as if the only capability is REPORT, that's fine - its a system limitation and can't be worked around.


Extend/rework security-related documentation

Fixes #3448
This renames the documentation file as suggested and extends it with answers from comments.

@brauner thanks for pedantry :) All comments should be addressed


Add Ruff Lint

Adds ruff linting and replaces isort in pre-commit ci
Only change I'm not sure of is in manim/mobject/opengl/opengl_mobject.py because there are two invert methods defined. I deleted the one without the self.assemble_family, but I'm not sure if that is the correct behavior (it's the current behavior).

Only change I'm not sure of is in manim/mobject/opengl/opengl_mobject.py because there are two invert methods defined. I deleted the one without the self.assemble_family, but I'm not sure if that is the correct behavior (it's the current behavior).

Unfortunate, but let's keep it this way. Keeping the last method was the best path :)


Can't compile: error: '_Generic' specifies two compatible types

Hi,
First of all, I like the API of your library.
Sadly, I was not able to use it.
Here's the code:
// unit testing framework
#include "external/snow.h"

// c lib
#include <stdio.h>
#include <stddef.h>
#include <stdint.h>
#include <stdbool.h>
#include <string.h>
#include <stdarg.h>
#include <stdlib.h>

describe(basic) {
	it("should work") {
                asserteq(1, 1, "Should be equal");
	}
}
snow_main();

Here's the error:
../tests/test_rbp2.c:20:9: error: '_Generic' specifies two compatible types
         asserteq(1, 1, "Should be equal");
         ^~~~~~~~
../tests/test_rbp2.c:20:9: note: compatible type is here
         asserteq(1, 1, "Should be equal");
         ^~~~~~~~
../tests/test_rbp2.c:20:9: error: '_Generic' specifies two compatible types
         asserteq(1, 1, "Should be equal");
         ^~~~~~~~
../tests/test_rbp2.c:20:9: note: compatible type is here
         asserteq(1, 1, "Should be equal");
         ^~~~~~~~
ninja: build stopped: subcommand failed.

Additional info:

Plateform: Windows 10 Pro [64-bit]
Compiler: gcc.exe (x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0

After further tests:
There's no error when running the same program in WSL2.

I think this is the same issue as https://github.com/mortie/snow/issues/24


It is not issue but question

How did you find out that this uri will give you list of apps?
https://manage.devcenter.microsoft.com/v1.0/my/analytics/applicationlist
I couldn't find anything about listing all apps in official documentation.

Hi.
You're right, there isn't anything about this uri in any documentation.
I found out by checking how the official Dev Center app was retrieving all my published apps.
Turned out to be really easy. Would've been great to mention it in the official documentation...

Thank you for answer. It's a shame that Microsoft didn't provide more in this api... I'm glad that I found your implementation, and this little trick. Thank you! :)


test/integration-test: use +nightly for ebpf

The ebpf probes require a nightly compiler. Before this change, if you ran cargo xtask integration-test with a stable compiler toolchain as default, or you ran cargo +stable xtask integration-test, you would have seen an error like the one below. This is now fixed.
  --- stderr
  /home/ajwerner/src/github.com/aya-rs/aya/test/integration-test/bpf/ring_buf_sched_tracepoint.bpf.c:18:21: warning: declaration of 'struct switch_args' will not be visible outside of this function [-Wvisibility]
  int bpf_prog(struct switch_args* ctx)
                      ^
  1 warning generated.
  error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  thread 'main' panicked at '"cargo" "build" "-p" "integration-ebpf" "-Z" "build-std=core" "--release" "--message-format=json" "--target" "bpfel-unknown-none" "--target-dir" "/home/ajwerner/src/github.com/aya-rs/aya/target/debug/build/integration-test-9bbcb3db5e9f8f57/out/integration-ebpf" exited
with status code 101:
  ', test/integration-test/build.rs:219:25
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: error while building userspace application

Caused by:
    Child { stdin: None, stdout: None, stderr: None, .. } exited with status code 101:

Relates to #670.

Can we put a toolchain file in the integration-ebpf directory instead? Does the tooling respect it when not at the workspace root?

It does if you clear RUSTUP_TOOLCHAIN.


BG Video Plan Page

Header image should be a background video like Phonebloks and Story hopper. We think "play the video" button shouldn’t open the full video in another page. Is there another way to make something out of this?
If not,  link it to the campaign page.

What's your opinion here @leo ?
The original concept was to have the video playing in the bg by default with a thick white overlay.
Like is happening here:
http://fantasy.co/
As users click "play video" the text and overlay would disappear leaving space for the video to be watched.
Is this even technically possible?

@davehakkens is currently creating a video that will be added behind that white overlay.


JSONiq runtime

Two high level comments:

It seems that your pull request is has old array code and is removing the new code.
Fix the imports to not use *.

Thanks for adding the error messages to your change.

I downloaded your pull request and made a few changes. Basically I found some differences between arrays and object that were cleaned up. Also fixed the formatting on the grammar.jj file. The resulting code has been squashed and merged with master. Please take a look.
This issue can be closed.


buildozer download kivy without checking kivy installed on OS(ubuntu), and downloading kivy in buildozer get error{  http.client.IncompleteRead: IncompleteRead(0 bytes read)}

Versions

Python:python3.6
OS:ubuntu
Kivy:
Kivy installation method:

Description
// REPLACE ME: What are you trying to get done, what has happened, what went wrong, and what did you expect?
Code and Logs
Traceback (most recent call last):
File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib/python3.6/runpy.py", line 85, in run_code
exec(code, run_globals)
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 1186, in
main()
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 1180, in main
ToolchainCL()
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 663, in init
getattr(self, args.subparser_name.replace('-', ''))(args)
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 152, in wrapper_func
build_dist_from_args(ctx, dist, args)
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/toolchain.py", line 205, in build_dist_from_args
args, "ignore_setup_py", False
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/build.py", line 536, in build_recipes
recipe.download_if_necessary()
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 297, in download_if_necessary
self.download()
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 343, in download
self.download_file(self.versioned_url, filename)
File "/mnt/e/008p4a/py2android/.buildozer/android/platform/python-for-android/pythonforandroid/recipe.py", line 158, in download_file
urlretrieve(url, target, report_hook)
File "/usr/lib/python3.6/urllib/request.py", line 1819, in retrieve
block = fp.read(bs)
File "/usr/lib/python3.6/tempfile.py", line 624, in func_wrapper
return func(*args, **kwargs)
File "/usr/lib/python3.6/http/client.py", line 449, in read
n = self.readinto(b)
File "/usr/lib/python3.6/http/client.py", line 483, in readinto
return self._readinto_chunked(b)
File "/usr/lib/python3.6/http/client.py", line 594, in _readinto_chunked
raise IncompleteRead(bytes(b[0:total_bytes]))
http.client.IncompleteRead: IncompleteRead(0 bytes read)
Command failed: /usr/bin/python3 -m pythonforandroid.toolchain create --dist_name=myapp --bootstrap=sdl2 --requirements=python3crystax,kivy --arch armeabi-v7a --copy-libs --color=always --storage-dir="/mnt/e/008p4a/py2android/.buildozer/android/platform/build" --ndk-api=21

Buildozer failed to execute the last command
// REPLACE ME: Paste your code and logs here, a template can be found at https://git.io/vM1id.

is this issue fixed? i meet the same issue


typedef-whitespace: Rewrite and add fixer

PR checklist

[x] Addresses an existing issue: #0000
[x] New feature, bugfix, or enhancement

[x] Includes tests

[x] Documentation update

Overview of change:
[new-fixer] typedef-whitespace
[enhancement] typedef-whitespace added checks for arrow function, call and construct signature
[bugfix] typedef-whitespace don't warn for leading whitespace if token is preceded by line break
Is there anything you'd like reviewers to focus on?

CHANGELOG.md entry:

@nchen63 conflicts are resolved. this is good to go


How to download a trimmed video from YT at 720p with audio?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Hello friends, I am trying to download this a video from you,
start_time 4048
end_time 4255
height<=720
how should I formulate the query? Thank you )
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

found the solution:
yt-dlp -F
yt-dlp -f 136 --download-sections "*4048-4255" -o "video.mp4"
yt-dlp -f 140 --download-sections "*4048-4255" -o "audio.m4a"
ffmpeg -i video.mp4 -i audio.m4a -c:v copy -c:a aac -strict experimental output.mp4

Looks like this single command would do what you want as well:
yt-dlp -S vcodec:h264,res:720,acodec:aac --download-sections "*4048-4255" "URL"

Looks like this single command would do what you want as well:
yt-dlp -S vcodec:h264,res:720,acodec:aac --download-sections "*4048-4255" "URL"

Works even better, thank you!


Only scroll to input when hidden by the keyboard

Measure where the input is in the screen and check if it will be hidden by the keyboard before scrolling to it.
This makes scrolling a lot less aggressive and match behaviour of apple apps.
Related issue: #39

Thanks! Will review now.

Thanks for your contribution @janicduplessis! 😊

Published https://github.com/APSL/react-native-keyboard-aware-scroll-view/releases/tag/v0.2.1

@alvaromb Awesome thanks!

Hi @janicduplessis!
How do you feel about being a collaborator of this library? ☺
I'm a bit overwhelmed and it would be great to have more collaborators!


ckeditor height

how to set the height of the ckeditor5 ?

You can modify those styles
Here in config file


nixos/trezord: revised and updated udev rules

Motivation for this change
Trezord devices should be run under a separate user/group (dialout->trezord) without others able to access the device (666->660).
Things done
Applied more restrictive policies (improved security), replaced generic dialout group with trezord group. Tested with both Trezor One and Trezor Model T.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

@roconnor-blockstream would you like to review this (and backports) PR?

This technically can break people's configs (them having relied on the old group), but there's probably very few if any affected by this.


Fixing implode() issue

Fixing this issue https://github.com/syamsoul/laravel-datatable-ssp/issues/2

Thanks for your submission.


Update managedEnvironmentId resourceGroups in README

Hi!
I came across this when using the container-apps-deploy-action in my project.
BR,
Rasmus

Thanks for catching this @razum90! :shipit:

You are welcome!


update users page

[ ] Be able to edit/add image, name, interests, major
[ ] Add saved clubs

We should make saved clubs a separate issue.

Edit profile page now pulls data from the database and populates the page.
Made several improvements on the page itself (implemented more fields, dropdowns, etc..)
Profile page is almost working.  Need to figure out how to pull only the logged in user's info (currently pulls all users).  This might be best as a separate issue.
Made changes to user database schema.
Users can almost edit their profile.  Currently running into a database access issue when user submits changes.


Not Scanning

Opened the app normally, and able to go into the actual map, however scanning doesn't occur anymore (tried to click scanned locations, but the hexagons aren't even appearing)

PGO is currently Critical
http://ispokemongodownornot.com/
Check status of PGO before opening an issue for connection reasons.
Please close this issue.


[playground] rename mongodb local module

Otherwise it gets confusing since we're also using a global mongodb module

Codecov Report

Merging #251 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #251   +/-   ##
=======================================
  Coverage   97.95%   97.95%
=======================================
  Files          55       55
  Lines         832      832
  Branches      162      162
=======================================
  Hits          815      815
  Misses         17       17

Continue to review full report at Codecov.

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


Migrations tables do not use t-shirt sized class.

Description

Link to documentation
https://opensource.adobe.com/spectrum-css/button-warning.html#migrationguide
Additional context
Seems like it just needs .spectrum-Table--sizeM...

Fixed by #1311


Add ordering at the DataSource level

This change makes order matter in DataSourceCollection.  It only has an effect on ground primitives.  All ground primitives from one DataSource render above all ground primitives in a lower DataSource in the same DataSourceCollection

Added raise, lower, raiseToTop, lowerToButtom methods in DataSourceCollection
Instead of adding everything directly to scene.primitives/scene.groundPrimitives, DataSourceDisplay creates it's own PrimitiveCollections.  This is so the order of data sources in the data source collection has a one-to-one mapping with the order of primitives in the primitive collection.
When a new data source is added to the data source collection, DataSourceDisplay creates a PrimitiveCollection for all the entities in that data source to use.
When the ordering of data sources changes, DataSourceDisplay re-orders the corresponding PrimitiveCollection so the ground primitives layer accordingly
Added a Sandcastle example to demonstrate this with CZML

@hpinkos, thanks for the pull request! Maintainers, we have a signed CLA from @hpinkos, so you can review this at any time.
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Works as advertised, those two comments were all I had as far as feedback on the approach.  When this is ready for merge I'll do a more thorough review.  Thanks @hpinkos!

Ready for a full review

I'll have to figure out why all these tests are failing on travis, they pass locally

Just those two comments.

@mramato ready

Don't add primitives to scene.primitives until either an entity is added to the defaultDataSource or the dataSourceCollection has at least one dataSource
Split up specs

Thanks @hpinkos!


Several backend related error messages when running on etna

When running on etna I get a chain of error messages the first time I ask for the frequencies, samples, ecc....
Namely, given the execution result result, asking for instance for the frequencies results in:
result.frequencies()
[Qibo 0.2.12|ERROR|2024-10-14 12:28:39]: The 'qibojit' backends' provider is not available. Check that a Python package named 'qibojit' is installed, and it is exposing valid Qibo backends.
[2024-10-14 12:28:39,557] ERROR: The 'qibojit' backends' provider is not available. Check that a Python package named 'qibojit' is installed, and it is exposing valid Qibo backends.
[Qibo 0.2.12|ERROR|2024-10-14 12:28:39]: The 'qibojit' backends' provider is not available. Check that a Python package named 'qibojit' is installed, and it is exposing valid Qibo backends.
[2024-10-14 12:28:39,558] ERROR: The 'qibojit' backends' provider is not available. Check that a Python package named 'qibojit' is installed, and it is exposing valid Qibo backends.
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1728901720.986336   43209 cuda_executor.cc:1015] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
[Qibo 0.2.12|INFO|2024-10-14 12:28:41]: Using tensorflow backend on /device:CPU:0
[2024-10-14 12:28:41,022] INFO: Using tensorflow backend on /device:CPU:0
Out[2]: Counter({'00': 976, '01': 24})

By the way, the shots are completely off, as the expected result is Counter({'10': 1000}) since I am sending two GPI2(0) (i.e. an X), but this might be a problem in the calibration I guess.

Concerning error message, this should be fixed after releasing qibo 0.2.13, given that https://github.com/qiboteam/qibo/pull/1486 was merged.

https://github.com/qiboteam/qibo/pull/1505


Face Mask Detector

This project is perfect already, a face mask project will get the beginners introduced to OpenCV with Machine Learning.
As the name suggests, this project will detect if a user is wearing a face mask or not !
Packages Used

OpenCV
Sklearn
Requests
Numpy

@Sabyasachi-Seal can you deploy it on any cloud

@Niketkumardheeryan Will try to deploy it on cloud and then confirm. I will update you soon. 😊

@Niketkumardheeryan Will try to deploy it on cloud and then confirm. I will update you soon. 😊

ok

@Niketkumardheeryan Hello, I checked and the thing will work on the cloud.

@Niketkumardheeryan could you please assign this issue  me :)

Make sure to add a demo

Ok sure, thanks a lot, I'm a contributor from GSSoC '22. Thanks for the opportunity.

Hello, if this problem statement still open, please assign this to me. I am eager to contribute to this.

I would like to work on this issue , Please assign this task to me


Unit tests S3FileSystemTest.viaRegistry and S3FileSystemTest.fileHandle are failing at merge time.

Bug description
These two unit tests are failing in CI at merge time.
https://github.com/facebookincubator/velox/actions/runs/9264077299/job/25483530209
https://github.com/facebookincubator/velox/actions/runs/9264287643/job/25484131434
System information
CI
Relevant logs
No response

CC: @majetideepak

cc @xiaoxmeng

@kagamiori There seems to be a fix here https://github.com/facebookincubator/velox/pull/9950

Resolved with https://github.com/facebookincubator/velox/pull/9959


little issue with "start" montage  order

Once you use "start" and try an "alias"
Following "start" steps lead to incorrect order of parameters
Just switching the order of "-name xxxx" "-mac xx:xxx:xxxxxx" solve it
Sory for bady engilish~

Which deauther version are you using, so I can try to replicate the issue?

Thank you for reporting! This is a deauther bug so not on the huhnitor side of things - but doesn't matter I just pushed a fix :)


Confusion with security updates not showing resolved from Nessus

I do some basic development with VS so I'm familiar with it but I mainly do the IT side of things.  Keeping user's systems updated and doing security scans to make sure everything is updated.  For a couple months though I've been having issues reconciling what the Nessus security scanner is saying is on our developers systems and vulnerable versus what the systems show as being installed.  All of our systems are Windows 10 running Visual Studio 2017 15.7.6.  I've seen the other threads about how .NET Core old versions get left behind so on a test system I went in and uninstalled everything but the latest version which was "Microsoft .NET Core SDK 2.1.202 (x64)" and did a fresh Nessus scan and I still get findings.
Microsoft ASP.NET Core Privilege Escalation (March 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.2
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version     : 2.0.2
Package           : Microsoft.AspNetCore.HttpOverrides
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.2
Package           : Microsoft.AspNetCore.HttpOverrides
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>03
Fixed version     : 2.0.2

Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package           : Microsoft.AspNetCore.Identity
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Identity
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>03
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Identity
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>51
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Identity
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>14
Fixed version     : 2.0.4

Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>51
Fixed version     : 2.0.4
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>14
Fixed version     : 2.0.4

I then found that the latest .NET Core wasn't even shipping with the VS updates for 15.7.x and won't be till 15.8.x so I got the latest "Microsoft .NET Core SDK 2.1.302 (x64)" and installed it and removed 2.1.202 from the system.  I then did another fresh Nessus scan and it still continues to find vulnerable versions on the system.  I honestly don't know the inner workings of .NET Core enough but it looks like old DLLs are being moved into an archive folder but still being left on the system.  The NuGetFallbackFolder was new as of the 2.1.302 where in the 2.1.202 they were still in the main folders.
Microsoft ASP.NET Core Privilege Escalation (March 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.2
...

Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package           : Microsoft.AspNetCore.Identity
Path              : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.4
...

Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)

Path              : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package           : Microsoft.AspNetCore.Server.Kestrel.Core
Path              : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version     : 2.0.4
...

All that to say as a small shop with limited resources this is confusing and complicated.  Keeping VS 2017 up to date on our users systems is time consuming manual process now.  Not being able to provide clean compliance scans after an update has been applied to makes this even more time consuming as I have to track down what's going on and then write justification for every item.

Adding Damian,
Those issues are flagging Asp.net binaries in two different locations.

The runtime "store". This location is cumulative and things in here are used by applications based on exact version match. If anything in here is getting used, the application using it needs to be updated.

NugetFallbackFolder, this is a cache of nuget packages. Similar to above, the only way the version there will be used is if an application references it and in that case, the application needs to be updated.

Damian, anything to add?
-------- Original message --------
From: Leith Tussing<EMAIL_ADDRESS>Date: 8/8/18 1:03 PM (GMT-05:00)
To: dotnet/core<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [dotnet/core] Confusion with security updates not showing resolved from Nessus (#1842)
I do some basic development with VS so I'm familiar with it but I mainly do the IT side of things. Keeping user's systems updated and doing security scans to make sure everything is updated. For a couple months though I've been having issues reconciling what the Nessus security scanner is saying is on our developers systems and vulnerable versus what the systems show as being installed. All of our systems are Windows 10 running Visual Studio 2017 15.7.6. I've seen the other threads about how .NET Core old versions get left behind so on a test system I went in and uninstalled everything but the latest version which was "Microsoft .NET Core SDK 2.1.202 (x64)" and did a fresh Nessus scan and I still get findings.
Microsoft ASP.NET Core Privilege Escalation (March 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.HttpOverrides
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.HttpOverrides
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.2
Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>51
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>14
Fixed version : 2.0.4
Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>51
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>14
Fixed version : 2.0.4
I then found that the latest .NET Core wasn't even shipping with the VS updates for 15.7.x and won't be till 15.8.x so I got the latest "Microsoft .NET Core SDK 2.1.302 (x64)" and installed it and removed 2.1.202 from the system. I then did another fresh Nessus scan and it still continues to find vulnerable versions on the system. I honestly don't know the inner workings of .NET Core enough but it looks like old DLLs are being moved into an archive folder but still being left on the system. The NuGetFallbackFolder was new as of the 2.1.302 where in the 2.1.202 they were still in the main folders.
Microsoft ASP.NET Core Privilege Escalation (March 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
...
Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
...
Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
...
All that to say as a small shop with limited resources this is confusing and complicated. Keeping VS 2017 up to date on our users systems is time consuming manual process now. Not being able to provide clean compliance scans after an update has been applied to makes this even more time consuming as I have to track down what's going on and then write justification for every item.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcore%2Fissues%2F1842&data=02|01|peter.marcu%40microsoft.com|7d47e072d0714554cbc408d5fd50ce0e|72f988bf86f141af91ab2d7cd011db47|1|0|636693445858682545&sdata=skQWaP2pFQRNSzTz6dLt%2FesTlfDAXsRe4Iy1UT0hXU8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH2OB6TVCSmSDSeboBUTCeWvLnx-w9PIks5uOxnHgaJpZM4V0UHm&data=02|01|peter.marcu%40microsoft.com|7d47e072d0714554cbc408d5fd50ce0e|72f988bf86f141af91ab2d7cd011db47|1|0|636693445858692549&sdata=G8VK3vJUdhOkYMY51HMKyzqjTjnoJttPcQAE1dtEuxk%3D&reserved=0.

The problem I guess is nessus has no way to tell if applications are targetting the older pieces, nor does anyone else, you'd have to delete that version from the store / fallback folder and see. Nor does nessus realise there are updated versions available for things that don't version match.
There's nothing we can do here unfortunately.

There's a few things at play here which I agree makes this more difficult than it ideally could (should) be. For what it's worth, these are things we're actively looking to improve in .NET Core 3.0 and beyond, but let me try to explain the moving pieces as they are now.
As Peter said, there are two locations being flagged here by the scan for contain vulnerable pieces: the "runtime store", and the NuGet Fallback Folder. They're both used for different things at different times, but by themselves don't necessarily indicate that apps are using those versions and are thus vulnerable. Furthermore, how these things are used is different between .NET Core 1.x, 2.0, and 2.1 projects. It's different again if your ASP.NET Core application is targeting and thus running on .NET Framework, rather than on .NET Core.
Of these two locations, only the "runtime store" is tracked by installers, such that when you uninstall the files go away. The NuGet Fallback Folder is not removed when you uninstall .NET Core SDK versions and so older files will remain there until they're removed manually. The other important difference is that the "runtime store" is used by deployed applications at runtime (as they name implies), whereas the NuGet Fallback Folder is only used by projects during development. Once the project is published (and thus becomes an application) it either takes the assemblies it needs with it, or gets them from the "runtime store" (in 2.0) or a "shared framework" (in 2.1 and beyond).
In .NET Core 1.x and all .NET Framework projects, ASP.NET Core assemblies come from NuGet packages and are published with your application. The version you get is determined by the version of the package you reference in the project. So to ensure your project is up to date, you need to update the package versions referenced in the csproj file, then build/publish and redeploy it.
In .NET Core 2.0 projects, the ASP.NET Core assemblies come from NuGet packages at design/compile time, but typically aren't published with your application. Instead, at runtime they come from the "runtime store". However, the version the application needs is still dictated by the package version specified in the project file, so it's the same process for ensuring the project is up to date: update the package versions referenced in the csproj file, then build/publish and redeploy it. It also requires the additional step of ensuring the "runtime store" update is installed on the machines where the deployed application will actually run (i.e. the server).
In .NET Core 2.1 projects, the ASP.NET Core assemblies still come from NuGet packages at design/compile time, and they still aren't published with your application, but at runtime they come from a "shared framework" (located under C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App). The key difference with this is that you don't need to change the version of ASP.NET Core in the project file, but rather you can leave it completely blank (e.g. ) . The build process will then transparently set that to the "baseline" version (currently 2.1.1) which is the same version you'll find in the NuGet Fallback Folder (so that the restore can complete without going online). However, at runtime, the application will roll-forward onto the latest patch version of the shared framework it finds on the machine (currently 2.1.2). This means that as patches are released, the NuGet Fallback Folder doesn't need new packages (as the baseline stays at 2.1.1), you just need to get a new shared framework (which of course is included in the updated SDKs). It also means on the servers, you simply need to install patched shared frameworks as they're released (2.1.2, 2.1.3, 2.1.4, etc.) and all apps on that server that were compiled against 2.1.0 will automatically roll forward onto the patched runtime when they next restart (rather than having to have their project files updated, build/published, and redeployed).
The end result of all this is that vulnerable assemblies will continue to be found in the NuGet Fallback Folder for the life of 2.x, but that doesn't mean they're necessarily used at runtime by your applications. Scanning of machines that install the SDK will continue to show these results, but scanning of servers (where you typically only install runtime assets) should be more inline with what one would expect.
I hope that helps.
Damian
From: Peter Marcu
Sent: Wednesday, August 8, 2018 10:08 AM
To: dotnet/core<EMAIL_ADDRESS>dotnet/core<EMAIL_ADDRESS>Damian Edwards<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [dotnet/core] Confusion with security updates not showing resolved from Nessus (#1842)
Adding Damian,
Those issues are flagging Asp.net binaries in two different locations.

The runtime "store". This location is cumulative and things in here are used by applications based on exact version match. If anything in here is getting used, the application using it needs to be updated.

NugetFallbackFolder, this is a cache of nuget packages. Similar to above, the only way the version there will be used is if an application references it and in that case, the application needs to be updated.

Damian, anything to add?
-------- Original message --------
From: Leith Tussing <notifications<EMAIL_ADDRESS>Date: 8/8/18 1:03 PM (GMT-05:00)
To: dotnet/core <core<EMAIL_ADDRESS>Cc: Subscribed <subscribed<EMAIL_ADDRESS>Subject: [dotnet/core] Confusion with security updates not showing resolved from Nessus (#1842)
I do some basic development with VS so I'm familiar with it but I mainly do the IT side of things. Keeping user's systems updated and doing security scans to make sure everything is updated. For a couple months though I've been having issues reconciling what the Nessus security scanner is saying is on our developers systems and vulnerable versus what the systems show as being installed. All of our systems are Windows 10 running Visual Studio 2017 15.7.6. I've seen the other threads about how .NET Core old versions get left behind so on a test system I went in and uninstalled everything but the latest version which was "Microsoft .NET Core SDK 2.1.202 (x64)" and did a fresh Nessus scan and I still get findings.
Microsoft ASP.NET Core Privilege Escalation (March 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.HttpOverrides
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
Package : Microsoft.AspNetCore.HttpOverrides
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.httpoverrides\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.HttpOverrides.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.2
Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>51
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.identity\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>14
Fixed version : 2.0.4
Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.0.13103.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.1\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>03
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.2\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>51
Fixed version : 2.0.4
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\store\x64\netcoreapp2.0\microsoft.aspnetcore.server.kestrel.core\2.0.3\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>14
Fixed version : 2.0.4
I then found that the latest .NET Core wasn't even shipping with the VS updates for 15.7.x and won't be till 15.8.x so I got the latest "Microsoft .NET Core SDK 2.1.302 (x64)" and installed it and removed 2.1.202 from the system. I then did another fresh Nessus scan and it still continues to find vulnerable versions on the system. I honestly don't know the inner workings of .NET Core enough but it looks like old DLLs are being moved into an archive folder but still being left on the system. The NuGetFallbackFolder was new as of the 2.1.302 where in the 2.1.202 they were still in the main folders.
Microsoft ASP.NET Core Privilege Escalation (March 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.2
...
Security Updates for Microsoft .NET core and ASP.NET (Bypass) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Identity
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.identity\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Identity.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
...
Security Updates for Microsoft .NET core and ASP.NET (DoS) (July 2018)
Path : C:\Program Files\dotnet
Installed version : 2.1.13029.0
Package : Microsoft.AspNetCore.Server.Kestrel.Core
Path : C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.aspnetcore.server.kestrel.core\2.0.0\lib\netstandard2.0\Microsoft.AspNetCore.Server.Kestrel.Core.dll
Installed version : <IP_ADDRESS>05
Fixed version : 2.0.4
...
All that to say as a small shop with limited resources this is confusing and complicated. Keeping VS 2017 up to date on our users systems is time consuming manual process now. Not being able to provide clean compliance scans after an update has been applied to makes this even more time consuming as I have to track down what's going on and then write justification for every item.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcore%2Fissues%2F1842&data=02|01||1b42110d44184db232ce08d5fd518ac0|72f988bf86f141af91ab2d7cd011db47|1|0|636693449010405702&sdata=ka9ogx%2B8mrj2rGnAHeR7uWhF3dBsYHrlNaDjI3gCmHQ%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH2OB6TVCSmSDSeboBUTCeWvLnx-w9PIks5uOxnHgaJpZM4V0UHm&data=02|01||1b42110d44184db232ce08d5fd518ac0|72f988bf86f141af91ab2d7cd011db47|1|0|636693449010415710&sdata=wm6u7YOvSwGIpCUQgQEWixmmCECMmGUBiYzHhdaVHKc%3D&reserved=0.

There's a few things at play here which I agree makes this more difficult than it ideally could (should) be. For what it's worth, these are things we're actively looking to improve in .NET Core 3.0 and beyond, but let me try to explain the moving pieces as they are now.
As Peter said, there are two locations being flagged here by the scan for contain vulnerable pieces: the "runtime store", and the NuGet Fallback Folder. They're both used for different things at different times, but by themselves don't necessarily indicate that apps are using those versions and are thus vulnerable. Furthermore, how these things are used is different between .NET Core 1.x, 2.0, and 2.1 projects. It's different again if your ASP.NET Core application is targeting and thus running on .NET Framework, rather than on .NET Core.
Of these two locations, only the "runtime store" is tracked by installers, such that when you uninstall the files go away. The NuGet Fallback Folder is not removed when you uninstall .NET Core SDK versions and so older files will remain there until they're removed manually. The other important difference is that the "runtime store" is used by deployed applications at runtime (as they name implies), whereas the NuGet Fallback Folder is only used by projects during development. Once the project is published (and thus becomes an application) it either takes the assemblies it needs with it, or gets them from the "runtime store" (in 2.0) or a "shared framework" (in 2.1 and beyond).
In .NET Core 1.x and all .NET Framework projects, ASP.NET Core assemblies come from NuGet packages and are published with your application. The version you get is determined by the version of the package you reference in the project. So to ensure your project is up to date, you need to update the package versions referenced in the csproj file, then build/publish and redeploy it.
In .NET Core 2.0 projects, the ASP.NET Core assemblies come from NuGet packages at design/compile time, but typically aren't published with your application. Instead, at runtime they come from the "runtime store". However, the version the application needs is still dictated by the package version specified in the project file, so it's the same process for ensuring the project is up to date: update the package versions referenced in the csproj file, then build/publish and redeploy it. It also requires the additional step of ensuring the "runtime store" update is installed on the machines where the deployed application will actually run (i.e. the server).
In .NET Core 2.1 projects, the ASP.NET Core assemblies still come from NuGet packages at design/compile time, and they still aren't published with your application, but at runtime they come from a "shared framework" (located under C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App). The key difference with this is that you don't need to change the version of ASP.NET Core in the project file, but rather you can leave it completely blank (e.g. ) . The build process will then transparently set that to the "baseline" version (currently 2.1.1) which is the same version you'll find in the NuGet Fallback Folder (so that the restore can complete without going online). However, at runtime, the application will roll-forward onto the latest patch version of the shared framework it finds on the machine (currently 2.1.2). This means that as patches are released, the NuGet Fallback Folder doesn't need new packages (as the baseline stays at 2.1.1), you just need to get a new shared framework (which of course is included in the updated SDKs). It also means on the servers, you simply need to install patched shared frameworks as they're released (2.1.2, 2.1.3, 2.1.4, etc.) and all apps on that server that were compiled against 2.1.0 will automatically roll forward onto the patched runtime when they next restart (rather than having to have their project files updated, build/published, and redeployed).
The end result of all this is that vulnerable assemblies will continue to be found in the NuGet Fallback Folder for the life of 2.x, but that doesn't mean they're necessarily used at runtime by your applications. Scanning of machines that install the SDK will continue to show these results, but scanning of servers (where you typically only install runtime assets) should be more inline with what one would expect.
I hope that helps.

The end result of all this is that vulnerable assemblies will continue to be found in the NuGet Fallback Folder for the life of 2.x, but that doesn't mean they're necessarily used at runtime by your applications.

It seems like we should determine if there are reasonable ways to not leave vulnerable assemblies in the FallbackFolder.
/cc @natemcmaster

This will be fixed with the changes coming in 3.0, but fixing in 2.1.x is challenging without giving up other things, e.g. offline restore.

I'm going to close this issue now. I think we all understand how this works and that its going to be addressed in a future release.

Since I didn't need this version any longer, I installed SDK 2.1.202, then uninstalled it.  The /store directory is gone now, so Nessus doesn't report it any longer.

I was facing a similar issue with the Nessus security scan reporting the previous versions having vulnerabilities.
To resolve this, I installed the updated version of .Net Core SDK i.e.  .Net Core SDK 2.1.522
and uninstalled .Net Core SDK 2.1.202.
Good luck.
The vulnerabilities were remediated and not reported in the next scan report.


feat(llama): callback improvements

Improvements which did not fit into #1546:

fixes in _set_llm_chat_response

enable test_query_pipeline.py by bumping llama-index

add more events, e.g. AgentToolCallEvent

[x] I have added tests that cover my changes.

[ ] If adding a new instrumentation or changing an existing one, I've added screenshots from some observability platform showing the change.

[x] PR name follows conventional commits format: feat(instrumentation): ... or fix(instrumentation): ....

[ ] (If applicable) I have updated the documentation accordingly.

Hi @nirga, here are some small fixes and additions to the llama callbacks. Let me know please if this is useful.


Handle gender data within user profile

Add support for the gender attribute when fetching the user profile.
<?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
  <person id="22021035@N07" nsid="22021035@N07" ispro="0" can_buy_pro="0" iconserver="3486" iconfarm="4" path_alias="one_show" has_stats="1" gender="M" ignored="0" contact="0" friend="0" family="0" revcontact="0" revfriend="0" revfamily="0">
    <username>One Show</username>
    <realname>Kevin Swanepoel</realname>
    <location>New York, United States</location>
    <timezone label="Eastern Time (US & Canada)" offset="-05:00" timezone_id="EST5EDT" />
    <description />
    <photosurl>https://www.flickr.com/photos/one_show/</photosurl>
    <profileurl>https://www.flickr.com/people/one_show/</profileurl>
    <mobileurl>https://m.flickr.com/photostream.gne?id=21999705</mobileurl>
    <photos>
      <firstdatetaken>2008-06-23 17:51:45</firstdatetaken>
      <firstdate>1236280014</firstdate>
      <count>1358</count>
    </photos>
  </person>
</rsp>

Also attributes ignored contact friend family revcontact revfriend revfamily
are missing in the user profile.

I've done a fix for this and will do a release soon.
revcontact, revfriend and revfamily are already supported as far as I can tell.
Let me know if you have any problems with them.


chore: Add DeepCopyJSON method to functional

Issue #, if available:
Description of changes:

Add functional.DeepCopyJSON() to Karpenter core

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 12 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.3%) to 33.479%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/utils/functional/functional.go
0
12
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
460

Relevant Lines:
1374

💛  - Coveralls


Port okhttp-client to cats-effect-3

Has this been picked up? If not, I can pick it up

Nope, not yet.  This one will be interesting because it has some synchronous calls.  I would expect to see some F.blocking in it.

Incorrectly autoclosed when cats-effect-3 branch was merged.

Incorrectly autoclosed when cats-effect-3 branch was merged.


Open Website Stuff

It needs to know:

The default browser / If IE or Edge is installed
If you are online

I know how to open a website (start [browserexe].exe http://text-os.github.io), but it would be great if it could know the default browser and if you are online.
But these issues will probably be gone when I have fixed the Text-OS browser (Based off of Lynx).


Non-blocking I/O for STDIN

Could maybe be extended to non-blocking I/O in general.

Everything about this is a mess. For STDIN specifically, maybe soup::console could be used, but I'm thinking it might just be best to spin up a new thread.


where to change modal fade color ?

I have implemented ngx-simple-modal in which i am opening modal on link click. When modal opens then whole page gets faded with very light black color. I want to make this black color more dark so that my page will get more darker in black and my modal will be more prominent. From where i can change this styling?

I found the solution. I just change .modal class and change background-color: rgba(0, 0, 0, .4) !important; to background-color: rgba(0, 0, 0, .9) !important;


Cloudflare no Virignia regionCode

Hey guys,
as more and more states introduce their type of CCPA/GDPR compliance, we have some projects that are AMP based and rely on amp-geo to provide the correct location for amp-consent and our CMP to do its thing.
In order to test that everything is mapped correctly, I've been using some VPN software (NordVPN) - pointing it to California, everything works as expected, amp-geo picks up the correct country and regionCode -
text.replace(       '{{AMP_ISO_COUNTRY_HOTPATCH}}',       injectIsoCode.toLowerCase().padEnd(28)     ),     response
This seems to replace it just fine.
Whenever I try change my location to Virginia(with the VPN), I cannot get the regionIso appear for the love of me. This got me to wonder if it is some restriction in the CDN or am I going insane ?

Can you please tell me which CDN you're testing? Are you using https://cdn.ampproject.org/ (hosted on Google and is not open source) or https://ampjs.org/ (hosted on Cloudflare and is this CDN)
The Cloudflare-hosted CDN is not entirely launched yet (although it should be working correctly, the AMP validator code isn't set up yet to recognize it). If the problem is with the Google-hosted CDN I can try to forward this issue report to the relevant team at Google
Do note that due to the Christmas and New Year holidays, it's highly unlikely that we'll get a response before January

Hey, my bad, it is https://cdn.ampproject.org/.
My gut feeling is that it is a VPN issue, although its working fine for Cali...
Thanks for the reply!


Got a python error

--- stderr
/usr/lib/python3.5/re.py:203: FutureWarning: split() requires a non-empty pattern match.
  return _compile(pattern, flags).split(string, maxsplit)
Traceback (most recent call last):
  File "gen_rust.py", line 1657, in <module>
    generator.gen(srcfiles, module, dstdir)
  File "gen_rust.py", line 1206, in gen
    self.add_decl(decl)
  File "gen_rust.py", line 1176, in add_decl
    FuncInfo(self, decl, namespaces=self.namespaces)
  File "gen_rust.py", line 467, in __init__
    raise NameError("class not found: " + self.classname)
NameError: class not found: cv
thread '<main>' panicked at 'explicit panic', /home/knovour/.cargo/registry/src/github.com-0a35038f75765ae4/opencv-0.2.0/build.rs:86

Should I need to downgrade the python version?

You will need to have a python 2.7 somewhere, yes. python 2.x and python 3.x are not compatible, but most modern OS support having both installed at the same time.
I have changed the scripts so that they refer to "python2.7" instead of just "python". As far as I can tell, this will work on both macos and ubuntu. I can see you're using linux, but not which flavour. Tell me if 0.2.1 works for you.

I am using Manjaro Linux, and the default python version is 3.5.
Version 0.2.1 seems working now, thank you!


Rename / Move a file

From issue #321 - 'For renames/moves, you should go through project query API, removing/adding the file as the project system has to be aware of changes in most cases as well.'
Since (a) WorkspacesExtensibility.UpdateProjectsAsync() and (b) ITextDocumentEditor.Rename() can both rename a file, show I use (a), (b), or both when renaming?

We are discussing this internally and I will update here with the findings and we will apply updates to docs as well.

OK - thanks for the update.

We apologize for the delay and appreciate your patience. We've updated our sample documentation to include examples of renaming and moving files.
Renaming a File:
https://github.com/microsoft/VSExtensibility/blob/main/New_Extensibility_Model/Samples/VSProjectQueryAPISample/RenameFileCommand.cs
Moving a File:
https://github.com/microsoft/VSExtensibility/blob/main/New_Extensibility_Model/Samples/VSProjectQueryAPISample/MoveFileCommand.cs
Currently, we don’t have an API specifically for moving files. However, thanks to your feedback, we’ve added a MoveFile API to our backlog and plan to implement it in the future. In the meantime, I've included a workaround: you can copy the file’s contents to the new location and then delete the original file.
Please let me know if this solution meets your needs - thanks!


webjar is 7.4.0 although I set camunda version to 7.4.5-ee

Although #35 is supposed to be fixed via https://app.camunda.com/jira/browse/CAM-5299 I cannot not verify it, because I still only get the 7.40 webapp-classes and webapp-webjar.
Seems like the camunda.version property is not overwritten correctly.

This is NOT a starter issue, teh camunda bom does not contain webjar information. I created https://app.camunda.com/jira/browse/CAM-5704


Enhancement Dashboard

#50 Issue fixed
Final Look:
(https://github.com/Banbury-inc/Athena/assets/98104718/81f2c378-ba9f-4d9a-9721-41c726c3159d)

the dashboard is located in https://github.com/Banbury-inc/Athena/blob/main/Banbury_Cloud/frontend/src/renderer/components/Dashboard.tsx.
I don't need dashboard visuals fixed in the api. This would be noticeable with any level of care. Dont waste my time.


https://substack.com/@systemdesignone/note/c-54451197

https://substack.com/@systemdesignone/note/c-54451197

Retry Pattern:

Automatically retry failed operations to improve the chances of success.

Cache-Aside pattern:

Loading data into a cache on-demand to improve data access times and reduce server load.

Blue-Green Deployment pattern:

Deploying a new version of an application alongside the old one for easy rollback in case of issues.

Ambassador pattern:

Proxy managing communication between microservices.

Backends for Frontends pattern:

Specialized backend services for different user interfaces (frontends).

Bulkhead pattern:

Isolating components to prevent cascading failures in a system.

Circuit Breaker pattern:

Limiting requests to prevent system overload during a failure or downtime.

CQRS pattern:

Separating read and write operations for improved system scalability.

Event Sourcing pattern:

Capturing and storing every state-changing event for data reconstruction.

Materialized View pattern:

Precomputing and storing query results for faster data retrieval.

Publisher-Subscriber pattern:

Communication pattern where senders notify many receivers.

Rate Limiting pattern:

Restricting the rate of incoming requests to a system.

Saga pattern:

Coordinating a series of transactions to maintain data consistency.

Sidecar pattern:

Independent service extends the functionality of a main application.

Throttling pattern:

Controlling the rate of processing to prevent resource exhaustion.
Build reliable and scalable applications by studying proven cloud design patterns.


Unable to find Altme White paper

Hello everyone,
Where do I find the white paper for Altme?
Thanks

We don't have a white paper. The github project and the website (https://altme.io/) should provide the information you need.

Okay, thank you for your reply. 😄


Multiple outputs with TFDF

Hi,
I have a basic question about  multi-output regression and multi-label classification using TFDF package.
Does TFDF support such cases? If yes, are there some examples on how to implement such models with TFDF and some caveat to be mindful of?
Thanks.

Hey! It  appears this capability is not supported. See issue here: https://github.com/tensorflow/decision-forests/issues/19

@mrsergazinov Thanks for the pointer. Appreciate!


[Feature] Cut option

It would be really nice to have a cut option so that users can move around there sketches. I use excalidraw and onenote, and the fact that onenote has the cut ability does make the workflow a bit nicer.

Can I have clarity on what you mean @AdamLinCodes? Cutting / pasting / dragging a selection all work for me.

Can I have clarity on what you mean @AdamLinCodes? Cutting / pasting / dragging a selection all work for me.

Of courae @andrewblum. Essentially it would work like a marker, and you could draw around a section of your sketch that you want to either cut or copy.

i am interested in looking at this, but I believe this is a replication of https://github.com/excalidraw/excalidraw/issues/6350 which already has some good discussion so I suggest we move over there as close this.

@andrewblum Yes, ticket #6350  is far more fleshed out. Closing this now


add timeout for b2d release check; warn instead of error if cannot check

This adds a timeout to the check for the latest b2d release.  It also changes to a "warn" in the event of an error (internet issues, etc).
Fixes #435

LGTM

Hey @ehazlett, did you ever take care of this?

let's make sure to add some code to bail in the case that no local .iso exists and the network times out. Otherwise we try to careen into an ISO download that won't work.

Yes an error would be thrown but I will add an informational message as well.


Arn 356 add child

Adds data for displaying a new child table

Do we need to add the link here? Can't we infer it in the front-end from the table name?
Oh, hang on - that is what's happening, but this is adding some extra UI elements?

Do we need to add the link here? Can't we infer it in the front-end from the table name?
Oh, hang on - that is what's happening, but this is adding some extra UI elements?

I've put the 'child' table as a new sheet in the the existing spreadsheet to keep it all together - and yeah, lots of new UI bits were needed to match up with the prototype.


Variable hover value syntax highlighting is wrong for strings with " in them

Repro case
.Message = 'h"i'

Expected
The string in the hover is colored the same.
Actual
The string in the hover is colored differently after the ".

For reference, here's the FASTBuild code to print variables.

Image of the fix:


Identifiers validation failed for dataset The Fungarium of Elena Zvyagina

Identifier validation failed for the dataset The Fungarium of Elena Zvyagina:

Crawler attempt: 140
Publishing organization: Yugra State University Biological Collection (YSU BC)
Publishing country: RUSSIAN_FEDERATION
Installation: Northern West Siberia IPT installation
Number of occurrences indexed for this dataset at the time of the issue: 467
Cause: GBIF ID problems exceed 50% threshold: 51% duplicates; 929 total records; 477 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3753596/step

New IDs sample:

00338
00217
00219
00460
00340
00461
00346
00225
00104
00345

Old IDs sample:

00131
00154
00155
00156
00157
00158
00159
00160
00161
00162

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the The Fungarium of Elena Zvyagina : https://doi.org/10.15468/xxymuf.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset The Fungarium of Elena Zvyagina:

Crawler attempt: 141
Publishing organization: Yugra State University Biological Collection (YSU BC)
Publishing country: RUSSIAN_FEDERATION
Installation: Northern West Siberia IPT installation
Number of occurrences indexed for this dataset at the time of the issue: 467
Cause: GBIF ID problems exceed 50% threshold: 51% duplicates; 929 total records; 477 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3757430/step

New IDs sample:

00338
00217
00219
00460
00340
00461
00346
00225
00104
00345

Old IDs sample:

00131
00154
00155
00156
00157
00158
00159
00160
00161
00162

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the The Fungarium of Elena Zvyagina : https://doi.org/10.15468/xxymuf.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


fix some comments

There are some conflicts that need to be fixed before this one can be merged into the branch of #1. Please do that, merge it and we'll take a look at a single PR before merging it to master.


Problem with parsing x12 832 EDIs

Hi,
i have a problem with deserializing x12 PriceSalesCatalogs.
i'm using this sample:
ISA*00* *00* *01*999999999 *12*6309246701*060926*1242*U*00401*000000030*0*T*>~
GS*SC*999999999*6309246701T*20060926*1242*1*X*004010~
ST*832*2001~
BCT*RC*BISG*980112*******00~
N1*98*ABCManufacturerInc.*1*123-123456~
LIN*1*IB*0940016699*B7*Book Industry Study Group~
PID*S**BI*TI*X12 Implementation Guidelines for Electronic Data Interchange~
PID*S**BI*TI*X12 Implementation Guidelines for Electronic Data Interchange~
PID*S**BI*TI*X12 Implementation Guidelines for Electronic Data Interchange~
LIN*2*IB*0812976568*B7*The Gospel of the Flying Spaghetti Monster~
PID*S**BI*TI*Hello World~
CUR*SE*USD~
CTT*5~
SE*17*2001~
GE*1*1~
IEA*1*000000030~

My problem is that the deserializer doesnt parse the ItemDetails descriptions attributes(PID).
The ItemDetails itself are beeing parsed right, only the description instances inside of it are
empty :/ (But in right amount)
Also i have a similiar problem with the Party Identifications(N1).
They are there in right amount but all empty.
Here is how i tried to implement it:
    public class PriceSalesCatalog_832
    {
        [EdiValue("X(2)", Path = "BCT/0", Description = "BCT01 - Catalog Purpose Code")]
        public string CatalogPurposeCode { get; set; }

        [EdiValue("X(15)", Path = "BCT/1", Description = "BCT02 - Catalog Number")]
        public string CatalogNumber { get; set; }

        [EdiValue("X(2)", Path = "BCT/9", Description = "BCT10 - Transaction Set Purpose Code")]
        public string TransactionSetPurposeCode { get; set; }

        public List<PartyIdentification> Parties { get; set; }

        public List<ItemDetail> ItemDetails { get; set; }

        [EdiValue("X(3)", Path = "CUR/1", Description = "CUR02 - Currency Code")]
        public string CurrencyCode { get; set; }

        [EdiSegment, EdiPath("N1")]
        public class PartyIdentification
        {
            [EdiValue("9(3)", Path = "N1/0", Description = "N101 - Party Identification")]
            public string PublicIdentification;
            [EdiValue("X(60)", Path = "N1/1/0", Description = "N102 - Name")]
            public string Name;
            [EdiValue("9(2)", Path = "N1/2", Description = "N103 - Identification Code Qualifier")]
            public string IdentificationCodeQualifier;
            [EdiValue("X(80)", Path = "N1/3", Description = "N104 - Idenfication Code")]
            public string IdentificationCode;
        }

        [EdiSegment, EdiSegmentGroup("LIN", "PID", Description = "LIN - Item Identification")]
        public class ItemDetail
        {
            [EdiValue("X(20)", Path = "LIN/0")]
            public int Index { get; set; }
            [EdiValue("9(2)", Path = "LIN/1")]
            public string ProductServiceIDQualifier1 { get; set; }
            [EdiValue("X(80)", Path = "LIN/2")]
            public string ProductServiceID1 { get; set; }
            [EdiValue("9(2)", Path = "LIN/3")]
            public string ProductServiceIDQualifier2 { get; set; }
            [EdiValue("X(80)", Path = "LIN/4")]
            public string ProductServiceID2 { get; set; }
            public List<ItemDescription> Descriptions { get; set; }
        }

        [EdiSegment, EdiPath("PID")]
        public class ItemDescription
        {
            [EdiValue("9(1)", Path = "PID/0", Description = "PID01 - Item Description Type")]
            public int ItemDescriptionType;
            [EdiValue("X(3)", Path = "PID/1", Description = "PID02 - Product/Process Characteristic Code")]
            public string ProductProcessCharacteristicCode;
            [EdiValue("9(2)", Path = "PID/2", Description = "PID03 - Agency Qualifier Code")]
            public int AgencyQualifierCode;
            [EdiValue("X(12)", Path = "PID/3", Description = "PID04 - Product Description Code")]
            public string ProductDescriptionCode;
            [EdiValue("X(80)", Path = "PID/4", Description = "PID05 - Description")]
            public string Description;
            [EdiValue("9(1)", Path = "PID/7", Description = "PID08 - YesNo Condition or Response Code")]
            public int YesNoCondition;
            [EdiValue("X(80)", Path = "PID/8", Description = "PID09 - Language Code")]
            public string LanguageCode;
        }
    }

I will check it out and send you an update with a sample.

Hi and sorry for the late reply. The issue you got here is that both your classes ItemDescription & PartyIdentification use fields instead of properties and the Serializer searches solely for public properties. Add getters and setters and you will be fine.

Thanks! :)


KubeletPodResources is GA, but is still mentioned as a switchable feature gate

https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#grpc-endpoint-getallocatableresources
Support for the PodResourcesLister service requires KubeletPodResources feature gate to be enabled. It is enabled by default starting with Kubernetes 1.15 and is v1 since Kubernetes 1.20.

The "KubeletPodResources" feature gate is GAed, but it's still mentioned as a switchable one in the GetAllocatableResources gRPC endpoint section. Perhaps it's time to remove it from the page.
This fact is mentioned in https://github.com/kubernetes/website/pull/27575.

Page related to issue: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/
/language en

/triage accepted
PRs welcomed.

/assign @pegasas
I am working on it.

closing this issue as it was resolved by following PR #42860
Thanks @pegasas

/close


fix(configuration): hook up missing render whitespace option

Possibly I'm missing something here, but this just looks like it wasn't hooked up?

Ah, ya, nice catch @CrossR - looks like this was broken in https://github.com/onivim/oni2/commit/a89fc696473b7a25dce43d2954cdbf396224a1ce when migrating the configuration
Thanks for fixing it!

The CentOS hang isn't related to your change - investigating here #2715 & here https://github.com/esy/esy/issues/1227


plugin-seo: PayloadCMS SEO Plugin Causes UI Crash When Editing Documents

Hi everyone : )
Thanks for the amazing work done on PayloadCMS!
I'm trying to use the payloadcms SEO plugin (official one), but when I add it it breaks the UI.
Here is my config:
import seo from "@payloadcms/plugin-seo";
import path from "path";
import { buildConfig } from "payload/config";
import { Articles } from "./collections/Articles";
import { Categories } from "./collections/Categories";
import { Media } from "./collections/Media";
import { ProgrammingLanguages } from "./collections/ProgrammingLanguages";
import { Tags } from "./collections/Tags";
import { Users } from "./collections/Users";

export default buildConfig({
  admin: {
    user: Users.slug,
  },

  collections: [Users, Articles, Media, Tags, Categories, ProgrammingLanguages],
  localization: {
    locales: ["en", "fr"],
    defaultLocale: "en",
    fallback: true,
  },
  typescript: {
    outputFile: path.resolve(__dirname, "payload-types.ts"),
  },
  graphQL: {
    schemaOutputFile: path.resolve(__dirname, "generated-schema.graphql"),
  },
  plugins: [
    seo({
      collections: ["articles"],
      uploadsCollection: "media",
      tabbedUI: true,
      generateTitle: ({ doc }) => "",
      generateDescription: ({ doc }) => "",
    }),
  ],
});

When I try to edit an article, the UI crashed directly with this error:
iUncaught TypeError: Cannot read properties of null (reading 'useState')
    at useState (react.development.js:1622:1)
    at Overview (Overview.js:35:1)
    at renderWithHooks (react-dom.development.js:16305:1)
    at mountIndeterminateComponent (react-dom.development.js:20074:1)
    at beginWork (react-dom.development.js:21587:1)
    at beginWork$1 (react-dom.development.js:27426:1)
    at performUnitOfWork (react-dom.development.js:26557:1)
    at workLoopSync (react-dom.development.js:26466:1)
    at renderRootSync (react-dom.development.js:26434:1)
    at recoverFromConcurrentError (react-dom.development.js:25850:1)

Hey @jimzer - are you still facing this issue?
If so, can you pull down the latest version of the seo plugin for me and see if it resolves?
e.g. npm install @payloadcms/plugin-seo or yarn add @payloadcms/plugin-seo

@jimzer going to close this for now since it's not reproducible. If you're still experiencing issues after updating the plugin to its latest version and can create a reproducible repo for me, I'll reopen and look back into it!


can typescript -> wasm ?

can typescript -> wasm ?

Yes : typescript -> JS -> NectarJS -> wasm, asm.JS, PE, ELF ...

@adrien-thierry Is there a specific operating guide?


Cannot make multimesh out of extruded polygon curve.

This outputs nothing. My transforms exist and my polygon exists, yet combined they output nothing,

Basically, I want to make a plank generator (with custom width, height and length), and this is the only way so far I've seen how you'd do that, by extruding a rectangle curve.

Another way it would be possible is by adding some sort of "Scale" node. Right now there's only "scale from noise", but "scale from constant" would also be nice.

The multimesh issue should be fixed in fd1e1a73c5b160c849b8d394775be98e13d528ae (Will merge with master soon)
I'll take a look at the scale constant, it should be fast to add

Should be fixed now, feel free to reopen if you still have issues with this


Boostrap: include test in service template

Include the service descriptor test in the service template and use it when adding new service modules
Reviewer checklist

[ ] Read the contributing guide
[ ] PR should be motivated, i.e. what does it fix, why, and if relevant, how
[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage: 96.269%. Remained the same when pulling bfb5622acf245703d8c5a2e0d2a5eed5996a75b6 on bootstrap into cd73664148e28589356486c462710ecf837e8aca on main.