Add ability to link a IAsyncEnumerable  to a SignalR Group

Is your feature request related to a problem? Please describe.
We need to stream prices to a group of users base on their belonging to a group
Describe the solution you'd like
My understanding is that right now the only way to stream thru IAsyncEnumerable  is to return  it to the  user thru the hub , . It would be great if I could bind a channel to a group so i get the power and performance and simplicity of it
Describe alternatives you've considered
right now we plan to use the group.sendasync
Additional context
Add any other context or screenshots about the feature request here.
we are using Azure SignalR

I'm not really sure but does it would mean that on the Hub side pseudo code would look like
somewhere in the ioc a channel factory
if(NotExist(channelName)) // concurrent dictionary ?
{
var channel = Channel.CreateBounded<Poco>(....)
}
return channel

Somewhere else in a Service (can be done after a controller route being hit for example)
var channelFactory = serviceProvider.GetService<IFooChannelFactory>();
var hubContext = serviceProvider.GetService<IHubContext<StreamingHub>>();

var group = hubContext.Group("groupName")
var channel = channelFactory.Reader
group.Bind(channel.Reader) // that would fan put just like SendAsync already does

A background service could be in charge of only writing to a channel, thus decorelate it completely from any notion of Hub/client/group
var channelFactory = serviceProvider.GetService<IFooChannelFactory>();
var writer = channelFactory.GetOrCreate("myStreamFromWhatEver");
while(var data DataPolling()) // IAsyncEnumerable here ?
{
 writer.TryWrite(data);
}

Seems like it could be done today though right?

well i think the question is about getting the same Api for both Client and Group
today the Client needs to subscribe to a stream
it look like the question is more about driving that logic from the hubContext itself
the result could be done kinda like streamr sample does but avoiding the round trip
on the client side it would look like a mix between .on("eventName") and .stream("name").subscribe()
this issue with that is ...
if the client have no idea of the group strategy (he really should not know), is there a way to stream from the hubContext to a group directly

You could definitely build this today by writing to a channel and having a background service read out of that channel and send messages using IHubContext. We don't have plans to make something built-in like that.

ok I get it I thought that there was an advantage by using the IAsyncE but at the end everything end up on the connection.writeAsync. so using a channel in a background service like @anurse  said should do it
thks you guys


In Python, multiple closing braces on a new line does not dedent multiple times.

Python indentation of closing braces does not trigger dedentation correctly.
Best explained with following example:
Steps to reproduce:

Go to any Codemirror python text area (http://codemirror.net/mode/python/index.html).
Write the following code.

# | shows the position of cursor
a = [{( | )}]

Press enter.

What is observed:
Code changes to:
# | shows the position of cursor
a = [{(
        |)}]

What is expected:
Code may change to:
# | shows the position of cursor
a = [{(
|)}]

Please take a look at attached patch, and see whether it solves your problems.

Thanks for a quick fix.
I tested the code. It improved the situation did not fix the problem completely.
Example:

Go to https://rawgit.com/codemirror/CodeMirror/master/mode/python/index.html
Write code:

a = [[
    [|]
]]

3a. Pressing enter turns the code to
a = [[
    [
]
]]

3b. Expected
a = [[
    [
    ]
]]

PS: https://rawgit.com/ienzam/CodeMirror/issues/py_indentation/mode/python/index.html shows correct behaviour (at least for this case).

Good catch. Attached patch fixes this case.

Great, thanks for fixing these two issues quickly.


Packaging issue

Hi, when trying to package for Fedora for 0.1.1 with the default build I get some test errors (build status)

running 2 tests
test tests::durations ... ok
test tests::basics ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

   Doc-tests interim
     Running `/usr/bin/rustdoc --edition=2021 --crate-type lib --crate-name interim --test src/lib.rs --test-run-directory /builddir/build/BUILD/interim-0.1.1 -L dependency=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps -L dependency=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps --extern chrono=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps/libchrono-0e835bdf9f094266.rlib --extern interim=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps/libinterim-17baa27995409518.rlib --extern logos=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps/liblogos-42ee95e53464a2bd.rlib --extern time=/builddir/build/BUILD/interim-0.1.1/target/rpm/deps/libtime-c7ca52536bc6fd88.rlib -C embed-bitcode=no --cfg 'feature="default"' --cfg 'feature="std"' --error-format human`

running 4 tests
test src/lib.rs - (line 61) ... ignored
test src/lib.rs - parse_date_string (line 116) ... FAILED
test src/lib.rs - (line 76) ... ok
test src/lib.rs - parse_duration (line 146) ... ok

failures:

---- src/lib.rs - parse_date_string (line 116) stdout ----
warning: use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
 --> src/lib.rs:121:15
  |
8 | let now = Utc.ymd(2022, 9, 17).and_hms(13, 27, 0);
  |               ^^^
  |
  = note: `#[warn(deprecated)]` on by default

warning: use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
 --> src/lib.rs:121:32
  |
8 | let now = Utc.ymd(2022, 9, 17).and_hms(13, 27, 0);
  |                                ^^^^^^^

error[E0277]: the trait bound `chrono::DateTime<Utc>: interim::datetime::DateTime` is not satisfied
   --> src/lib.rs:122:51
    |
9   | let this_friday = parse_date_string("friday 8pm", now, Dialect::Uk).unwrap();
    |                   -----------------               ^^^ the trait `interim::datetime::DateTime` is not implemented for `chrono::DateTime<Utc>`
    |                   |
    |                   required by a bound introduced by this call
    |
note: required by a bound in `parse_date_string`
   --> /builddir/build/BUILD/interim-0.1.1/src/lib.rs:125:30
    |
125 | pub fn parse_date_string<Dt: DateTime>(s: &str, now: Dt, dialect: Dialect) -> DateResult<Dt> {
    |                              ^^^^^^^^ required by this bound in `parse_date_string`

warning: use of deprecated method `chrono::TimeZone::ymd`: use `with_ymd_and_hms()` instead
  --> src/lib.rs:124:29
   |
11 | assert_eq!(this_friday, Utc.ymd(2022, 9, 23).and_hms(20, 0, 0));
   |                             ^^^

warning: use of deprecated method `chrono::Date::<Tz>::and_hms`: Use and_hms_opt() instead
  --> src/lib.rs:124:46
   |
11 | assert_eq!(this_friday, Utc.ymd(2022, 9, 23).and_hms(20, 0, 0));
   |                                              ^^^^^^^

error: aborting due to 1 previous error; 4 warnings emitted

For more information about this error, try `rustc --explain E0277`.
Couldn't compile the test.

failures:
    src/lib.rs - parse_date_string (line 116)

test result: FAILED. 2 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.15s

error: doctest failed, to rerun pass `--doc`
error: 1 target failed:
    `--doc`

RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.MFsLtg (%check)
    Bad exit status from /var/tmp/rpm-tmp.MFsLtg (%check)

Also can you tag your commits that are submitted to crates.io? I am not sure where 0.1.1 points to

Just warning failures with the continuous deprecations added to chrono. Will look.

Also can you tag your commits that are submitted to crates.io

The commit tags should be in the crates metadata (https://docs.rs/crate/interim/0.1.1/source/.cargo_vcs_info.json) but I will also tag appropriately

This one in particular though:
error[E0277]: the trait bound `chrono::DateTime<Utc>: interim::datetime::DateTime` is not satisfied
   --> src/lib.rs:122:51

This is from a doctest. Doctests need the chrono feature enabled.

Those are included with the dependency installed as:
Package                                     Arch   Version        Repository      Size
Installing:
 rust-chrono+clock-devel                    noarch 0.4.38-1.fc41  fedora       2.2 KiB
 rust-chrono-devel                          noarch 0.4.38-1.fc41  fedora       1.2 MiB

The command used was:
$ cargo test -j4 -Z avoid-dev-deps --profile rpm --no-fail-fast

This is the default command for all rust packages and most of them still succeed with dev-dependencies, so I am thinking it could rather be a dependency version issue

Published and tagged 0.1.2 with the warnings fixed

Yeah, and thankfully there was a feature in rust2rpm to enable --all-features to fix this as well. Thanks for the quick fix on the warnings.

And thank for all of your work packaging up atuin!


add param checkbox

basic graphic selection menu for user to choose params to plot, have something like this:

implemented in #36


Botany

[x] Seeds
[x] Trays
[x] Planting
[x] Harvesting
[x] Plants die
[x] Plants need nutriment and water
[x] Pests and weeds
[x] Plants consume/exude gasses
[x] Plants need ideal temperatures
[x] Produce has different amounts of different reagents depending on the seed
[x] Tray lights
[x] Botany tools and sampling
[x] ????

Making tomatoes go splat
Closed system hydroponics
Mysterious seeds that appear in maint!
Light levels. shiver

Ready for review.

tomato plants disappear after the first harvest
sugarcanes dont disappear after the first harvest but honestly I have no idea if they should
water/nutrientment values go down extremely slowly, see image

tomato plants disappear after the first harvest

fixed now, thanks for pointing it out

sugarcanes dont disappear after the first harvest but honestly I have no idea if they should

porting botany from VG, they don't seem to repeat harvest there, I think?

water/nutrientment values go down extremely slowly, see image

I'll mess with the values and come back to you

porting botany from VG, they don't seem to repeat harvest there, I think?

They do:
/datum/seed/sugarcane
	name = "sugarcane"
	seed_name = "sugarcane"
	display_name = "sugarcanes"
	plant_dmi = 'icons/obj/hydroponics/sugarcane.dmi'
	products = list(/obj/item/weapon/reagent_containers/food/snacks/grown/sugarcane)
	harvest_repeat = 1
	chems = list(SUGAR = list(4,5))

	lifespan = 60
	maturation = 3
	production = 6
	yield = 4
	potency = 10
	growth_stages = 3
	ideal_heat = 298

Welp I totally missed that harvest_repeat = 1

Looking at it, I already set sugarcanes to repeat harvest. Might be a look so I'll look into it

@Aranclanos hey, I balanced consumption so it consumes 2 times more likely, and 4 times as much. Feel free to test and tell me how it feels now! Also I'm pretty sure sugarcanes repeat harvest juts fine hmm


Fatal error: security/pam_appl.h: No such file or directory

src/login.c:13:10: fatal error: security/pam_appl.h: No such file or directory
   13 | #include <security/pam_appl.h>
      |          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make: *** [makefile:52: obj/src/login.o] Error 1

I have installed all the dependencies, currently on Fedora 35, and I get this error. I have tried cloning multiple times the correct way shown in the README, yet this error always pops up. Even trying to make as sudo doesn't work.

Fixed by installing pam-devel using yum install pam-devel, closing this issue.


Imageflow benchmark

Hi,
Thank you for this awesome library.
I recently come across another library that claims upto 17x faster performance than ImageMagick.
Here's the link: https://github.com/imazen/imageflow
Can you please add imageflow to benchmark contenders for better comparison with sharp?

There was some discussion on Twitter about this - see https://twitter.com/jcupitt65/status/1252905648368619520
All the code for the benchmarks is at https://github.com/lovell/sharp/tree/master/test/bench - happy to accept a PR if you're able.

I created a work-in-progress bench-add-imageflow branch for this and added the latest v0.0.1-rc8 of @imazen/imageflow via commit 5cddb81.
Some preliminary results when run on a ~3 year old laptop with low battery:
jpeg jimp-buffer-buffer x 0.65 ops/sec ±6.09% (8 runs sampled)
jpeg mapnik-buffer-buffer x 2.96 ops/sec ±2.58% (19 runs sampled)
jpeg imageflow-buffer-buffer x 3.65 ops/sec ±11.73% (21 runs sampled)
jpeg gm-buffer-buffer x 6.97 ops/sec ±3.97% (38 runs sampled)
jpeg sharp-buffer-buffer x 15.95 ops/sec ±10.44% (52 runs sampled)

It looks like imageflow ships with and uses mozjpeg for JPEG output, which might explain why its ops/sec figure above is rather low. I'm sure the way in which I'm calling it could be wrong, and it's only on v0.0.1-rc8 so I'd imagine there's still work to be done.

imazen have a docker image for benchmarking, which is where they get their timings. You can test like this:
$ docker pull imazen/imageflow_bench_ubuntu20
...
$ docker run -it --rm --entrypoint /bin/bash imazen/imageflow_bench_ubuntu20
imageflow@f4d55028ee4e:~$ vipsheader u1.jpg
u1.jpg: 5104x3380 uchar, 3 bands, srgb, jpegload
imageflow@f4d55028ee4e:~$ time ./bin/imageflow_tool v0.1/ir4 --in u1.jpg --out if.jpg --command "width=128&height=85&quality=89" >& /dev/null

real	0m0.217s
user	0m0.196s
sys	0m0.021s
imageflow@f4d55028ee4e:~$ time vipsthumbnail u1.jpg --size 128 --strip --output v.jpg[Q=89]

real	0m0.212s
user	0m0.200s
sys	0m0.013s
imageflow@f4d55028ee4e:~$ ls -l v.jpg if.jpg
-rw-r--r-- 1 imageflow 1001 5490 Jun 27 07:33 if.jpg
-rw-r--r-- 1 imageflow 1001 5519 Jun 27 07:42 v.jpg

So they are pretty much the same speed for small JPEG thumbnails. For a larger output size:
$ time vipsthumbnail u1.jpg --size 2000 --output v.jpg[optimize-coding,strip,Q=89]

real	0m0.394s
user	0m0.575s
sys	0m0.041s
imageflow@f4d55028ee4e:~$ time ./bin/imageflow_tool v0.1/ir4 --in u1.jpg --out if.jpg --command "width=2000&height=1324&quality=89" >& /dev/null

real	0m1.252s
user	0m1.207s
sys	0m0.044s
imageflow@f4d55028ee4e:~$ ls -l v.jpg if.jpg
-rw-r--r-- 1 imageflow 1001 565222 Jun 27 07:43 if.jpg
-rw-r--r-- 1 imageflow 1001 741079 Jun 27 07:43 v.jpg

iflow is /much/ slower, but perhaps that's mozjpeg, as Lovell says. The file size difference does look like mozjpeg.
libvips is quite a bit quicker at PNG images:
imageflow@f4d55028ee4e:~$ time vipsthumbnail u1.png --size 128 --output v.jpg[optimize-coding,strip,Q=89]

real	0m0.693s
user	0m0.653s
sys	0m0.040s
imageflow@f4d55028ee4e:~$ time ./bin/imageflow_tool v0.1/ir4 --in u1.png --out if.jpg --command "width=128&height=85&quality=89" >& /dev/null

real	0m0.915s
user	0m0.850s
sys	0m0.065s

Perhaps because libvips can run PNG decode and image resize in parallel.

Here's a patch to add imageflow to the perf tests in case anyone wants to revisit this, however the project seems rather stagnant so I'll close for now.
--- a/test/bench/perf.js
+++ b/test/bench/perf.js
@@ -15,6 +15,7 @@ const imagemagick = require('imagemagick');
 const mapnik = require('mapnik');
 const jimp = require('jimp');
 const squoosh = require('@squoosh/lib');
+const imageflow = require('@imazen/imageflow');

 const fixtures = require('../fixtures');

@@ -253,6 +254,43 @@ async.series({
           });
       }
     });
+    // imageflow
+    jpegSuite.add('imageflow-file-file', {
+      defer: true,
+      fn: function (deferred) {
+        new imageflow.Steps(new imageflow.FromFile(fixtures.inputJpg))
+          .constrainWithin(width, height, { down_filter: 'lanczos' })
+          .encode(
+            new imageflow.FromFile(outputJpg),
+            new imageflow.MozJPEG(80, false)
+          )
+          .execute()
+          .then(function () {
+            deferred.resolve();
+          })
+          .catch(function (err) {
+            throw err;
+          });
+      }
+    }).add('imageflow-buffer-buffer', {
+      defer: true,
+      fn: function (deferred) {
+        new imageflow.Steps(new imageflow.FromBuffer(inputJpgBuffer))
+          .constrainWithin(width, height, { down_filter: 'lanczos' })
+          .encode(
+            new imageflow.FromBuffer(null, 'key'),
+            new imageflow.MozJPEG(80, false)
+          )
+          .execute()
+          .then(function (buffer) {
+            assert.notStrictEqual(null, buffer);
+            deferred.resolve();
+          })
+          .catch(function (err) {
+            throw err;
+          });
+      }
+    });
     // sharp
     jpegSuite.add('sharp-buffer-file', {
       defer: true,


asyncio.sleep(0) in agent message Dispenser introduces unnecessarily high CPU usage

Prerequisites

[X] I checked the documentation and found no answer to my problem
[X] I checked the existing issues and made sure there are no similar bug reports

Category
Bug (unexpected behavior)
Expected Behavior
No response
Observed Behavior
Even when running the simplest agent, like the following:
from uagents import Agent, Context

alice = Agent(name="alice", seed="alice secret phrase")

@alice.on_event("startup")
async def send_message(ctx: Context):
    ctx.logger.info("Hello World!")

if __name__ == "__main__":
    alice.run()

The CPU usage is kept constantly high. This was introduced in #363, where a Dispenser class was added and run for all agents. The run method is a sort of constant polling loop with no interval (i.e. asyncio.sleep(0)). Versions of uAgents previous to this PR don't have high CPU usage.
To Reproduce
On the current main branch of uAgents, in the python dir:
poetry install
poetry run python repro.py
top

where repro.py is the code I pasted above.
Version
main
Environment Details (Optional)
No response
Failure Logs (Optional)
No response
Additional Information (Optional)
I have a simple suggested fix for this, which I'll put in a PR shortly.

This has been fixed in #445


Added description and use cases for zero-shot classification

fixed #361 by adding description and use cases

I am making new PR

@merveenoyan  I messed up with this PR(committed every change on this). Can you review #385 for the reinforcement task and #386 for the zero-shot-classification? Sorry for the inconvenience.


Contain property is not working.

How can i view multiple slides one time.
contain property is not working.

Hello @MukulSinghKumawat,
I'm not sure I understand what the issue is.  Viewing multiple slides is not related to the contain property.
The contain property simply aligns the first cell to the left to avoid any extra space before the first cell. See the docs: http://flickity.metafizzy.co/options.html#contain
Here is a working demo that shows two sliders; one with contain: true and one without contain set: http://plnkr.co/edit/A8Ao3P
You can see in the demo that multiple slides are visible at the same time. This is based on your slideshow styles.

Closing for now, but if you are still having issues, please create a demo that shows the issue and I will reopen and try to help. (Fork this demo for a quick starting point)


Customize date format

I need to customise date
26-Aug-16 format, How to customise it plz suggest

Datepicker used Moment.js format the date.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


A matching Triton is not available, some optimizations will not be enabled. Error caught was: No module named 'triton'[bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
24
What version did you experience this issue on?
3.0
What happened?
A matching Triton is not available, some optimizations will not be enabled. Error caught was: No module named 'triton'
manual install doesn't work also
PS C:\InvokeAI> ..venv\Scripts\activate
(.venv) PS C:\InvokeAI> pip install triton-2.0.0-cp310-cp310-win_amd64.whl
WARNING: Requirement 'triton-2.0.0-cp310-cp310-win_amd64.whl' looks like a filename, but the file does not exist
Processing c:\invokeai\triton-2.0.0-cp310-cp310-win_amd64.whl
ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: 'C:\InvokeAI\triton-2.0.0-cp310-cp310-win_amd64.whl'
[notice] A new release of pip available: 22.2.1 -> 23.2
[notice] To update, run: python.exe -m pip install --upgrade pip
(.venv) PS C:\InvokeAI> pip install triton
ERROR: Could not find a version that satisfies the requirement triton (from versions: none)
ERROR: No matching distribution found for triton
[notice] A new release of pip available: 22.2.1 -> 23.2
[notice] To update, run: python.exe -m pip install --upgrade pip
(.venv) PS C:\InvokeAI>  python.exe -m pip install --upgrade pip
Requirement already satisfied: pip in c:\invokeai.venv\lib\site-packages (22.2.1)
Collecting pip
Downloading pip-23.2-py3-none-any.whl (2.1 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 2.4 MB/s eta 0:00:00
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 22.2.1
Uninstalling pip-22.2.1:
Successfully uninstalled pip-22.2.1
Successfully installed pip-23.2
(.venv) PS C:\InvokeAI> pip install triton
ERROR: Could not find a version that satisfies the requirement triton (from versions: none)
ERROR: No matching distribution found for triton
(.venv) PS C:\InvokeAI>  pip install triton-2.0.0-cp310-cp310-win_amd64.whl
WARNING: Requirement 'triton-2.0.0-cp310-cp310-win_amd64.whl' looks like a filename, but the file does not exist
Processing c:\invokeai\triton-2.0.0-cp310-cp310-win_amd64.whl
ERROR: Could not install packages due to an OSError: [Errno 2] No such file or directory: 'C:\InvokeAI\triton-2.0.0-cp310-cp310-win_amd64.whl'
Screenshots
Desired action:

Generate images with the browser-based interface
Explore InvokeAI nodes using a command-line interface
Run textual inversion training
Merge models (diffusers type only)
Download and install models
Change InvokeAI startup options
Re-run the configure script to fix a broken install or to complete a major upgrade
Open the developer console
Update InvokeAI
Command-line help
Q - Quit
Please enter 1-10, Q: [1] 1
Starting the InvokeAI browser-based UI..
A matching Triton is not available, some optimizations will not be enabled.
Error caught was: No module named 'triton'
[2023-07-21 14:42:20,410]::[InvokeAI]::INFO --> Patchmatch initialized
C:\InvokeAI.venv\lib\site-packages\torchvision\transforms\functional_tensor.py:5: UserWarning: The torchvision.transforms.functional_tensor module is deprecated in 0.15 and will be removed in 0.17. Please don't rely on it. You probably just need to use APIs in torchvision.transforms.functional or in torchvision.transforms.v2.functional.
warnings.warn(

Additional context
No response
Contact Details
No response

I got the same error too when installing, but Invoke3 works

Seems to not be getting installed during the main installation i get the same error during startup

There's no Windows triton, and that warning does not mean anything is wrong. We need to suppress the warning message.
It's likely that your install was actually fine - did you try it?

https://huggingface.co/r4ziel/xformers_pre_built/resolve/main/triton-2.0.0-cp310-cp310-win_amd64.whl  you could use this and pip install it on win :)

 {  D: 易InvokeAI3 }  pip install .\triton-2.0.0-cp310-cp310-win_amd64.whl
Processing d:\invokeai3\triton-2.0.0-cp310-cp310-win_amd64.whl
Requirement already satisfied: filelock in d:\invokeai3.venv\lib\site-packages (from triton==2.0.0) (3.12.2)
Collecting cmake
Downloading cmake-3.27.0-py2.py3-none-win_amd64.whl (34.6 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 34.6/34.6 MB 65.1 MB/s eta 0:00:00
Requirement already satisfied: torch in d:\invokeai3.venv\lib\site-packages (from triton==2.0.0) (2.0.1+cu117)
Requirement already satisfied: jinja2 in d:\invokeai3.venv\lib\site-packages (from torch->triton==2.0.0) (3.1.2)
Requirement already satisfied: sympy in d:\invokeai3.venv\lib\site-packages (from torch->triton==2.0.0) (1.12)
Requirement already satisfied: networkx in d:\invokeai3.venv\lib\site-packages (from torch->triton==2.0.0) (3.1)
Requirement already satisfied: typing-extensions in d:\invokeai3.venv\lib\site-packages (from torch->triton==2.0.0) (4.7.1)
Requirement already satisfied: MarkupSafe>=2.0 in d:\invokeai3.venv\lib\site-packages (from jinja2->torch->triton==2.0.0) (2.1.3)
Requirement already satisfied: mpmath>=0.19 in d:\invokeai3.venv\lib\site-packages (from sympy->torch->triton==2.0.0) (1.3.0)
Installing collected packages: cmake, triton
Successfully installed cmake-3.27.0 triton-2.0.0

Same problem......
I have:
"A matching Triton is not available, some optimizations will not be enabled.
Error caught was: No module named 'triton'
[2023-07-22 14:44:36,363]::[InvokeAI]::INFO --> Scanning G:\invokeai_3.0.0\models for new models
[2023-07-22 14:44:36,413]::[InvokeAI]::INFO --> Scanned 5 files and directories, imported 0 models
This window is too short for the user interface. Please make it taller.
Press any key to continue.."
"Press any key" give no results, installation was blocked to this step
The tip given by "damadorPL" does not improve anything !!!!

@gardunorr Actually, the output makes a suggestion:
 This window is too short for the user interface. Please make it taller.
Make your terminal window larger, then press a key to let it continue.

Thank you, after some runs, the installation proceed

I get the same thing. And the webui doesn't load anything except a dark background.

@emilanderss0n
Please follow these steps to reset the UI:

Start the InvokeAI UI and open it in your browser
Follow these instructions to open the browser's console
Copy and paste localStorage.clear() into the console and press Enter to run the command
Refresh the page

We'd love a contribution to suppress the triton warning message on Windows. See  #3954


DO NOT MERGE: Propose a new resource claim controller

Description of your changes

DO NOT MERGE THIS PULL REQUEST.
This pull request is the result of my experimenting with some changes to our “core controller”. The core controller is responsible for satisfying resource claims by provisioning and/or binding concrete resources - e.g. it satisfies a RedisCluster claims by creating a CloudMemorystoreInstance resource.
The core resource controller and the interfaces it leverages are sufficiently pervasive that it’s very challenging to refactor without touching almost every Crossplane controller. In order to demonstrate my proposed changes without updating every single controller I simply deleted all of them except for one claim (RedisCluster) and one resource (CloudMemorystoreInstance). We should not merge the commit that deletes most of our controllers. :)
The “key features” of this proposed pattern are:

Improved requeue logic for all resource claims. Concrete resource controllers must queue a new reconcile speculatively in case the resource they manage changes in the cloud, because there’s no way to subscribe to changes. Resource claims on the other hand can watch the managed resource (i.e. Kubernetes API Resource) they bind to. This means we never need to requeue reconciles in the happy path; we’ll be notified if a claim or resource changes. This relates to #241 and #447.

All claims and resources use the newer conditioned status added in #447 and #514. These statuses are less confusing (a resource can’t be failed and ready at the same time), and discourage making decisions based on the status rather than the real world.

All claims and resources support a set of standard fields (claim reference, class reference, etc) by embedding a struct that defines said fields (fixes #451). One of those fields is .spec.writeConnectionSecretTo, a consistent and unsurprising field that specifies where a claim or resource should write their connection secret. This replaces the inconsistent support for .spec.connectionSecretNameOverride and the surprising behaviour of writing a connection secret named for the resource (fixes #518 and #168). The proposed controller also sets respects controller references when managing secrets (fixes #450).

Another notable change is to the API exposed to users of the “core controller”. In the contemporary implementation the core controller is designed to be embedded in a reconciler for a specific kind of claim, passing any resource-specific logic to a set of handlers for a specific kind of resource.
In this proposed design the core controller itself is the reconciler; it need not be embedded or wrapped in any reconciler logic. There’s also a 1:1 claim:resource reconciler relationship; i.e. a resource claim kind that can be satisfied by three different resource kinds would use three instances of the core controller, rather than one core controller with three handlers. Instantiating the proposed core controller is typically a case of defining a resource-specific Configurator function that populates a spec given a class and claim, then writing a small Add function to instantiate the core reconciler, setup watches, and add it to the manager. The NewReconciler function also supports plugging in different CRUD logic in case a particular claim kind wants to override the defaults. One (arguably) nice property of this pattern is that the controller that binds a resource claim to a concrete resource can live in the same package as the concrete resource’s controller.
If folks want to move forward with this design the process would be roughly:

Write tests for the proposed resource claim controller
Port all existing resource and claim controllers to the new pattern, keeping the scope at changing only what is necessary to support the new core resource controller and its interfaces.
Update examples and documentation.

Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the RBAC permissions in clusterrole.yaml to include any new types.

I still need to do further reviewing, but some initial thoughts:

I really like moving away from the pattern of passing the handlers for providers of a resource type (i.e. how rediscluster.go currently does) into the core controller. I think the initial idea was grouping the different external providers of a resource type together and using a single core controller for the type, but because we still have to implement the separate controllers for each of those providers (i.e. cloudmemorystore) it really only makes it more complex to me. I am a big fan of the 1:1 claim:resource reconciler relationship proposed here!
The new conditioned status is much more clear, and I think enforcing it on all claims and resources is a good practice.
Connection secrets have seemed to be a significant cause of frustration for various issues experienced by community members. Given their importance and and sensitivity, any standardization we can achieve in how they are handled and used is a win IMO.

Overall, I know a lot of work went into thinking about how to refactor this and there are a lot of great changes here. Thanks for the effort and insight @negz !

Closing this in favor of #545.


BUG: calling onyo rm <dir> <dir> <dir> multiple times with same dir leaves git unclean

This issue is about calling onyo rm a/ a/, but the problem should be considered together with onyo rm a/b/ a/ (e.g. different paths are given, but the call would on disk try to delete the same destination twice)!
The bug is that I can call onyo rm multiple times with the same input and onyo even begins running the command, but then errors and leaves the git tree unclean.
❱ onyo rm admin admin admin                                                              130 !
The following will be deleted:
-/Users/tkadelka/onyo/admin/Karl Krebs/laptop_apple_macbookpro.9sdjwa
-/Users/tkadelka/onyo/admin/Karl Krebs
-/Users/tkadelka/onyo/admin
-/Users/tkadelka/onyo/admin/Karl Krebs/laptop_apple_macbookpro.9sdjwa
-/Users/tkadelka/onyo/admin/Karl Krebs
-/Users/tkadelka/onyo/admin
-/Users/tkadelka/onyo/admin/Karl Krebs/laptop_apple_macbookpro.9sdjwa
-/Users/tkadelka/onyo/admin/Karl Krebs
-/Users/tkadelka/onyo/admin
Save changes? No discards all changes. (y/n) y
ERROR: [Errno 2] No such file or directory: '/Users/tkadelka/onyo/admin/Karl Krebs/.anchor'

Basically, when I call the command like this, it seems to work  (e.g. a diff is presented because all paths are "possible to delete" -> no error).  But then onyo tries to execute, and errors --- presumably during the second deletion when it tries to delete the already-not-existing-anymore file.
This causes the problem that the command stops in between executions, which means the commit is not executed and the git tree is afterwards unclean:
❱ git status                                                                             130 !
On branch master
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	deleted:    admin/.anchor
	deleted:    admin/Karl Krebs/.anchor
	deleted:    admin/Karl Krebs/laptop_apple_macbookpro.9sdjwa

no changes added to commit (use "git add" and/or "git commit -a")

Would we actually want to allow this type of szenario (and how we would like to handle sub-paths e.g. onyo rm a/b/  a)? We can either allow it and make sure it does not fail on such calls, or disallow it, and then error correctly:
Dis-allowing:

check input paths for duplicates/sub-paths in the beginning and error if duplicates are found.

Allowing:

de-duplicate the paths before deleting anything.
check before deleting again if the path does actually still exist.

Technically it would also be possibly to find a solution that just reverses/restores changes or fscks/commits them afterwards if such an error occours, though I find these solutions always problematic. IMO just deciding to allow/dis-allow this behavior and then either add appropriate checks or errors should be fairly straight forward and lead to the best behavior.

Note: Another flavor of #546.


question on Mask R CNN COCO dataset to Masks

Hey Adam,
Great to reread these fantastic tutorials..  I'd been in other things but coming back around to working with PyTorch.  One question regarding your creation of the bit mask
https://github.com/akTwelve/tutorials/blob/master/image_composition/BasicImageComposition.ipynb
Did you end up creating a channel in the mask image for each object id like some I have seen?  Or do you create the bit-mask in one layer.. and number each pixel the id of the object overwhich it's covering?  I guess both can work but.. want to conform as best as I can to norms.
thanks!

The second option is better. One mask per channel limits you to only 3 objects.

From: Erik @.>
Sent: Monday, June 14, 2021 1:24:52 AM
To: akTwelve/tutorials @.>
Cc: Subscribed @.***>
Subject: [akTwelve/tutorials] question on Mask R CNN COCO dataset to Masks (#16)
Hey Adam,
Great to reread these fantastic tutorials.. I'd been in other things but coming back around to working with PyTorch. One question regarding your creation of the bit mask
https://github.com/akTwelve/tutorials/blob/master/image_composition/BasicImageComposition.ipynbhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FakTwelve%2Ftutorials%2Fblob%2Fmaster%2Fimage_composition%2FBasicImageComposition.ipynb&data=04|01||979d6502839c4e5618da08d92efd1ee8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637592486942080582|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Vg8EU7%2BogpMhJNcqGp7%2Fnzlt8KMqCxkJequpoV7DuSQ%3D&reserved=0
Did you end up creating a channel in the mask image for each object id like some I have seen? Or do you create the bit-mask in one layer.. and number each pixel the id of the object overwhich it's covering? I guess both can work but.. want to conform as best as I can to norms.
thanks!
—
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%2FakTwelve%2Ftutorials%2Fissues%2F16&data=04|01||979d6502839c4e5618da08d92efd1ee8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637592486942090531|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=EVlrgpXJu%2FbGznpgyrcbD0VFDXQSntQxLAWD9Kpf%2Boc%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABUEBKOE4AIBKMKV4JTCMG3TSWODJANCNFSM46USEW3Q&data=04|01||979d6502839c4e5618da08d92efd1ee8|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637592486942100487|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=b4jxxSIecBED2KVBk5zuToWQOAO7sJckGfHDj68fxV8%3D&reserved=0.

Sounds like a plan... I'm in pytorch these days and I will add the objects to a tensor like this example tutorial then
https://pytorch.org/tutorials/intermediate/torchvision_tutorial.html
import os
import numpy as np
import torch
from PIL import Image

class PennFudanDataset(object):
    def __init__(self, root, transforms):
        self.root = root
        self.transforms = transforms
        # load all image files, sorting them to
        # ensure that they are aligned
        self.imgs = list(sorted(os.listdir(os.path.join(root, "PNGImages"))))
        self.masks = list(sorted(os.listdir(os.path.join(root, "PedMasks"))))

    def __getitem__(self, idx):
        # load images and masks
        img_path = os.path.join(self.root, "PNGImages", self.imgs[idx])
        mask_path = os.path.join(self.root, "PedMasks", self.masks[idx])
        img = Image.open(img_path).convert("RGB")
        # note that we haven't converted the mask to RGB,
        # because each color corresponds to a different instance
        # with 0 being background
        mask = Image.open(mask_path)
        # convert the PIL Image into a numpy array
        mask = np.array(mask)
        # instances are encoded as different colors
        obj_ids = np.unique(mask)
        # first id is the background, so remove it
        obj_ids = obj_ids[1:]

        # split the color-encoded mask into a set
        # of binary masks
        masks = mask == obj_ids[:, None, None]

        # get bounding box coordinates for each mask
        num_objs = len(obj_ids)
        boxes = []
        for i in range(num_objs):
            pos = np.where(masks[i])
            xmin = np.min(pos[1])
            xmax = np.max(pos[1])
            ymin = np.min(pos[0])
            ymax = np.max(pos[0])
            boxes.append([xmin, ymin, xmax, ymax])

        # convert everything into a torch.Tensor
        boxes = torch.as_tensor(boxes, dtype=torch.float32)
        # there is only one class
        labels = torch.ones((num_objs,), dtype=torch.int64)
        masks = torch.as_tensor(masks, dtype=torch.uint8)

        image_id = torch.tensor([idx])
        area = (boxes[:, 3] - boxes[:, 1]) * (boxes[:, 2] - boxes[:, 0])
        # suppose all instances are not crowd
        iscrowd = torch.zeros((num_objs,), dtype=torch.int64)

        target = {}
        target["boxes"] = boxes
        target["labels"] = labels
        target["masks"] = masks
        target["image_id"] = image_id
        target["area"] = area
        target["iscrowd"] = iscrowd

        if self.transforms is not None:
            img, target = self.transforms(img, target)

        return img, target

    def __len__(self):
        return len(self.imgs)


errors when setting properties on a class that extends python class

import { python } from<EMAIL_ADDRESS>
const gi = python.import("gi");
gi.require_version("Gtk", "4.0");
const Gtk = python.import("gi.repository.Gtk");

class MainWindow extends Gtk.ApplicationWindow {
  constructor() {
    super();
    this.a = 4; // error here
  }
}
console.log(new MainWindow());

error: Uncaught TypeError: 'set' on proxy: trap returned falsish for property 'a'
    this.a = 4;
          ^
    at new MainWindow (file:///home/mrcool/dev/deno/lab/b.ts:10:11)
    at file:///home/mrcool/dev/deno/lab/b.ts:14:13

more info here https://github.com/denosaurs/deno_python/issues/53#issuecomment-1797864483

using private variables instead , makes it work
import { python } from<EMAIL_ADDRESS>
const gi = python.import("gi");
gi.require_version("Gtk", "4.0");
const Gtk = python.import("gi.repository.Gtk");

class MainWindow extends Gtk.ApplicationWindow {
 #a;
  constructor() {
    super();
    this.#a = 4; // no error
  }
}
console.log(new MainWindow());

I'm "porting" https://github.com/Taiko2k/GTK4PythonTutorial to deno-python and taking note of issues I find along the way here https://github.com/sigmaSd/deno-gtk-py (grep FIXME)

Here is a more self contained example
import { python } from<EMAIL_ADDRESS>
const m = python.runModule(
  `
class A:
  x = 4
  `,
);

class B extends m.A {
  b;
  constructor() {
    super();
    this.b = 5; // error origin
  }
}

const _b = new B(); // error here

This is annoying in practice because it means I can't access any properties/functions of a class from the outside.
I wonder if there is a way to expose an alternative api for the proxy that allows such things.


OpenVPN exits setup with error.

`<EMAIL_ADDRESS>- OpenVPN connection to vpnname
Loaded: loaded<EMAIL_ADDRESS>disabled; vendor preset
Active: failed (Result: exit-code) since Fri 2016-09-23 11:34:22 EEST; 2min 2
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 7272 ExecStart=/usr/sbin/openvpn --daemon ovpn-%i --status /run/openv
Sep 23 11:34:22 15432.s.t4vps.eu systemd[1]: Starting OpenVPN connection to vpnn
Sep 23 11:34:22 15432.s.t4vps.eu ovpn-vpnname[7272]: Options error: In [CMD-LINE
Sep 23 11:34:22 15432.s.t4vps.eu ovpn-vpnname[7272]: Use --help for more informa
Sep 23 11:34:22 15432.s.t4vps.eu systemd[1]<EMAIL_ADDRESS>Control pr
Sep 23 11:34:22 15432.s.t4vps.eu systemd[1]: Failed to start OpenVPN connection
Sep 23 11:34:22 15432.s.t4vps.eu systemd[1]<EMAIL_ADDRESS>Unit enter
Sep 23 11:34:22 15432.s.t4vps.eu systemd[1]<EMAIL_ADDRESS>Failed wit
lines 1-15/15 (END)
`

Sorry for the late reply, is this still an issue for you?
If so, please attach the full log, the provided one is incomplete.
Also: which distro and version are you using? Try on a clean template.

Was running on Ubuntu 14.x/15.x didn't work. Using CentOS6 now without any problems :)


dxvk.conf does not support escaped characters

Currently, DXVK is set up to read a value in a config file as starting from the first whitespace character after the = until either it reaches another whitespace character or the end of the line, meaning that some parameters (for example, d3d9.customDeviceDesc = Device Name Here) cannot be used properly within a dxvk.conf file as it will end up being read as d3d9.customDeviceDesc = Device.
Could escape character support be added so parameters with whitespace/special characters can be used?

It doesn't support string options because string options just didn't exist before the addition of D3D9.
Guess we'll need to find some way to support those.

You should be able to use d3d9.customDeviceDesc = "Device Name Here" now.


Server can't find module if project not already built

Using my time library as a test, LSP in emacs works well when I

dylan build -a
start a fresh emacs
C-x C-f time.dylan
M-x lsp
move around the file and use M-. or M-? on various things

If I instead change that first (build) step to rm -rf _build to make sure there are no build products, the subsequent steps fail with dylan-lsp-server crashing with:
No module found for /Users/cgay/dylan/workspaces/time/sources/time.dylan
Backtrace:
  invoke-debugger:internal:dylan##1 + 0x29
  default-handler:dylan:dylan##1 + 0x12
  default-last-handler:common-dylan-internals:common-dylan##0 + 0x2a6
  error:dylan:dylan##0 + 0x2a
  error:dylan:dylan##1 + 0x79
  ensure-document-module:lsp-dylan-impl:lsp-dylan##0 + 0x103
  handle-textdocument/hover:lsp-dylan-impl:lsp-dylan + 0x86
  invoke-message-handler:lsp-dylan-impl:lsp-dylan + 0x2cd
  lsp-active-state-loop:lsp-dylan-impl:lsp-dylan + 0x5b
  lsp-server-top-level:lsp-dylan:lsp-dylan + 0xdb
  main:dylan-lsp-server:dylan-lsp-server + 0x360

It requires my dev branch changes that use dylan-tool dev branch changes to choose a reasonable default project to open, to even get this far, at least on macOS. Logging it here in case I get side-tracked before getting it fixed.

In case it's not obvious, it seems fairly natural to get an error if there are no build products. The point is that we need to initiate a build and let the user know it may take some time for the initial build.

Reminder to self... we'll need to run dylan update in the workspace the first time a project is being opened. Or give an appropriate error with a suggestion that the user run it. Or prompt the user to "Run dylan update now?"


Sundials Build Error trying to download

Getting an error when I try to build Sundials. I'm guessing its a permissions issue of some sort as I'm trying to do this on a work laptop that is heavily locked down with a firewall.
Any hints?
Pkg.add("Sundials")
INFO: No packages to install, update or remove
INFO: Package database updated
Pkg.build("Sundials")
INFO: Building Sundials
INFO: Attempting to Create directory C:\Users\scr1\.julia\v0.5\Sundials\deps\downloads
INFO: Directory C:\Users\scr1\.julia\v0.5\Sundials\deps\downloads already created
INFO: Downloading file https://cache.julialang.org/https://bintray.com/artifact/download/tkelman/generic/sundials-<IP_ADDRESS>z
Exception calling "DownloadFile" with "2" argument(s): "The request was
aborted: Could not create SSL/TLS secure channel."
At line:1 char:1
+ (new-object
net.webclient).DownloadFile("https://cache.julialang.org/https://bin ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

==============================[ ERROR: Sundials ]===============================

LoadError: failed process: Process(`'C:\Windows\System32\WindowsPowerShell\v1.0\powershell' -NoProfile -Command '(new-object net.webclient).DownloadFile("https://cache.julialang.org/https://bintray.com/artifact/download/tkelman/generic/sundials-<IP_ADDRESS>z", "C:\Users\scr1\.julia\v0.5\Sundials\deps\downloads\sundials-<IP_ADDRESS>z")'`, ProcessExited(1)) [1]
while loading C:\Users\scr1\.julia\v0.5\Sundials\deps\build.jl, in expression starting on line 37

================================================================================

================================[ BUILD ERRORS ]================================

WARNING: Sundials had build errors.

 - packages with build errors remain installed in C:\Users\scr1\.julia\v0.5
 - build the package(s) and all dependencies with `Pkg.build("Sundials")`
 - build a single package by running its `deps/build.jl` script

================================================================================

we rebuilt a new version of cache.julialang.org recently (cc @staticfloat), maybe your powershell download has issue with the certificates? try removing the cache.julialang.org prefix from the url, see if that helps

Nailed it. That fixed it.

note that Pkg.status() will probably show the package as dirty, you'll need to undo the modifications if you want to get future updates from Pkg.update()

I think bintray has been reliable enough that maybe caching isn't necessary here, but when I moved the binaries from sourceforge to bintray I wasn't sure yet whether that would be the case (sourceforge was definitely down every few days and needed caching)

So do we need to change
provides(Binaries, URI("https://cache.julialang.org/https://bintray.com/artifact/download/tkelman/generic/$sundialsver.7z"),
    sundialslibs, unpacked_dir="usr$(Sys.WORD_SIZE)/bin", os = :Windows)

to
provides(Binaries, URI("https://bintray.com/artifact/download/tkelman/generic/$sundialsver.7z"),
    sundialslibs, unpacked_dir="usr$(Sys.WORD_SIZE)/bin", os = :Windows)

yeah I think that would make sense here. for the sake of other cases where caching is more necessary we should try to work out what's wrong with the certificates though, if we can

@SCR1 just to clarify this was still happening now? when was the last time you ran it? a few days ago the certs did need tweaking, so if it was before than then maybe it was fixed.

@tkelman I had never gotten it installed or running before. This was my first try.  We have weird cert things going on with my work machine so I wouldn't be surprised if that is it. I'm probably an edge case?

I hope so. Several other packages are using the same caching server and actually need it, so keep us posted if you hit this anywhere else.


Add auto merge

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
@conda-forge-admin, please add bot automerge
Installed packages
conda

Environment info
conda

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/astromodels-feedstock#2.


Add documentation for config.json

@midik I think one time we retrieve the language dynamically then probably config.json will vanish (the few things left can be put in the code), and this one would be ready to close as well.

related to #19

After cleaning up the config, it looks like the following:
module.exports = {
    "verbose": true,
    "workers": 4,
    "imageResolution": 600,
    "categoriesToGet": [
        "Physics",
        "Biology",
        "Chemistry",
        "Earth Science",
        "Math"
    ]
}

Would be probably a good idea to remove all of these keys except work because most of the steps use it. The rest keys used only on get step so that could be placed directly into the code. Also, I think would be good solution to move workers key to .env and then remove this config file. Is this ok?

@midik Agree.

config.js removed and migrated to dotenv
(not merged to master yet)


Some strings are not displayed in Spanish

Describe the bug
After create a new Scene, the string Let's write an awesome story! and the dialog to confirm delete a paragraph are displayed in English.
To Reproduce
Steps to reproduce the behavior:

Change the language to Spanish
Click on New Scene (when is available)
See the string in new page

Expected behavior
Show the string "¡Vamos a escribir una historia asombrosa!" and "¿Estás seguro?"
Screenshots

Desktop (please complete the following information):

OS: Linux
Browser: Chrome
Version: 85

Additional context
I think the problem is in omnia-editor maybe here, I'm unsure about that, and I can read TypeScript but I can't write code fluently.

Good catch!
This is actually implemted and I missed 2 strings. There is a i18n store that is being handed the translation from OmniaWrite. It just needs to have the correct variable set:
https://github.com/TorstenDittmann/omnia-editor/blob/master/src/Editor.svelte#L116
https://github.com/TorstenDittmann/omnia-editor/blob/master/src/Editor.svelte#L110
And these can be deleted:
https://github.com/TorstenDittmann/omnia-editor/blob/master/src/Editor.svelte#L17-L18
If you want, you can create a PR at omnia-editor :-)


Error exporting to PDF

To get past other errors, I've added --pdf-engine-xelatex to my custom command, and now I can get this to work from the command line:
pandoc Untitled\ 1.md -f markdown --standalone --lua-filter="/home/akn/Obsidian/.obsidian/plugins/obsidian-enhancing-export/lua/pdf.lua" --embed-resources --pdf-engine=xelatex -s -o test1.pdf
This is my custom command:
-f markdown --resource-path="${currentDir}" --resource-path="${attachmentFolderPath}" --lua-filter="${luaDir}/pdf.lua" --embed-resources --standalone --metadata title="${currentFileName}" --pdf-engine=xelatex -s -o "${outputPath}" -t pdf
The error message that pops up in Obsidian is simply:
/bin/sh/sh: 0: Illegal option -
I can export using the built-in commands for most of the others: epub, rtf, mediawiki, latex, docx, odt, html
Any ideas?

Hi aknisly:
Have you try execute the command generated by this plugin directly? This plugin just generates command from templete for pandoc, then execute it.

Ahha--it works! I'm not sure what changed, but I updated pandoc, and installed several packages trying to get this to work, and never went back and tried the built-in export.
It would be great to tweak the output now (margins, font, etc); can that be done with the built-in pdf export?
Thanks very much for your speedy reply!

Sorry I may not have time to add extra features over recent month.

BTW, you can try to implement it yourself.


Update release process for open-autonomy

There are several missing steps from the open-autonomy release process

Fixed https://github.com/valory-xyz/open-autonomy/pull/1530


Support for subgroups

I see there is support for subgroups CRUD in the API docs but not the terraform provider. Is this on the road map?
Thanks!

@niksoper Please use the latest version 1.0.27 to add subgroups via terraform. https://github.com/site24x7/terraform-provider-site24x7/blob/main/examples/subgroup_us.tf

Thanks for this - I'll try to get round to testing this soon (also https://github.com/site24x7/terraform-provider-site24x7/issues/90).


textlint: support --rule ./path/to/rule.js

We want to support file path to rule file for command line flag and textlinrc.
Actual(Current)
--rule support only rule module name.
textlint --rule <rulename>

Expected
textlint --rule <rulename>
textlint --rule ./path/to/rule.js

Purpose
It help to debug developing rule.
UseCase: check the developing rule with actual texts.
cat example.md | xargs ./node_modules/textlint/bin/textlint.js --rule lib/my-rule.js -f pretty-error

In my real usecase: test my rule with some corpus.
technological-book-corpus-ja | xargs ./node_modules/textlint/bin/textlint.js --rule lib/my-rule.js -f pretty-error

Workaround
Install the rule and textlint to global
# install the rule to global
$ npm i -g . textlint technological-book-corpus-ja
$ technological-book-corpus-ja | xargs textlint --rule textlint-rule-ja-no-redundant-expression -f pretty-error

Task

[ ] support file path in .textlinrc
[ ] support file path in --rule flag

{
   "rules": {
     "./path/to/rule.js": true
   }
}

I don't know that the above case is safe?
Maybe, Other implementation is suitable for this purpose.

Agreed. On systems like NixOS there is more than one path to point at so --rules-base-directory doesn't cut it.

Sob!  I came here, wanting a solution to the statement in https://github.com/textlint/textlint/blob/master/docs/faq/failed-to-load-textlints-module.md :

If you have installed textlint as --global(-g), must install each rule as --global.
If you have installed textlint as --save-dev(-D), must install each rule as --save-dev.

It sounds like this would be that solution - but it's not nearly implemented.


fixes #288

add support for limit with jdbc index parameter. e.g. limit ?1, ?2

Coverage remained the same at 84.333% when pulling 091c5dd5ab5ce93e7e206354b5a34eff9235fd01 on ibeam-cn:master into 335286c492f0b9d76317706bec2d70f5216fab9f on JSQLParser:master.

Merged ... thx for improving JSqlParser


⚠ Bofrost.com has degraded performance

In 71de710, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1832 ms

Resolved: Bofrost.com performance has improved in 6e198cc.


Message Partition by day YYYYMMDD

As a developer I would like to save messages within SQLite and splitted in different files for different partition.

Also, part of this ISSUE is transform storing of messages form classic file to SQLite db-s, these db will be splitted per each day

Add configuration for FushInterval to appsettings

Known issue from this change will be send unacknowledgment messages to re-connected consumer.

PR #47 its merged, this issue is closed


APCs should use directional sprites

Just like lights already do

APCs do not have directional sprites on CEV-Eris so unless someone wants to resprite this i'm closing it.


Getting error while trying to compile ios app for iPhone SE2 iOS 14 but not for emulator

When I try to run complied ionic application on my iPhone SE2 i get this error
ld: in /Users/user/Library/Developer/Xcode/DerivedData/App-eismujpzjeytykgfdircgvnuefmj/Build/Products/Debug-iphoneos/AppsFlyerLib.framework/AppsFlyerLib(AFSDKDevice.o), building for iOS, but linking in object file (/Users/user/Library/Developer/Xcode/DerivedData/App-eismujpzjeytykgfdircgvnuefmj/Build/Products/Debug-iphoneos/AppsFlyerLib.framework/AppsFlyerLib(AFSDKDevice.o)) built for Mac Catalyst, file '/Users/user/Library/Developer/Xcode/DerivedData/App-eismujpzjeytykgfdircgvnuefmj/Build/Products/Debug-iphoneos/AppsFlyerLib.framework/AppsFlyerLib' for architecture arm64
Version 13.0 (13A233)
iPhone SE 2
IOS 14.8
plugin<EMAIL_ADDRESS>I trid to update cocoapods to latest, xcode to latest, plugin to latest, and different solution, like changing the ONLY_ACTIVE_ARCH = YES and NO then adding EXCLUDED_ARCHS arm64 , and so on, but nothing helps ... nothing seems to be helping ...
interestingly, if I select an emulator, it compiles and runs fine
also if i use the command
npx cap run ios
it compiles and runs on the physical device fine ... I spent 2 days already trying to fix this, really frustrating ... please help.

Hi @bboldi ,
Thank you for reaching out to us.
To provide optimal support, we would kindly ask you to submit a support ticket to<EMAIL_ADDRESS>When submitting the ticket, please specify your AppsFlyer sign-up (account) email, app ID, reproduction steps, code snippets, logs, the links you used, and any additional relevant information.

This helped ( got answer from AppsFlyer support )
XCode has a "DerivedData" folder where it stores some of the intermediate data it uses during the build process. By default it's located in ~/Library/Developer/Xcode/DerivedData. Cleaning this folder by deleting it can resolve some build issues.

Thanks!


web hook for jenkins failed  always

Gitea version (or commit ref): 1.9.3
Git version: git version 2.18.0.windows.1
Operating system: windows server 2016
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Log gist:

Description
I configure  webhook  for my repository. but push  test was alway failed.
I change to other repository use same configuration. it test sucessful.
The failed repository is  forked from aother repository.
Screenshots

This is Jenkins server configuration issue

I use chrome send hook request . it is runing sucessfully.
I create new repository and fork it, then it is still not working

I use chrome send hook request . it is runing sucessfully.
I create new repository and fork it, then it is still not working

This is Jenkins server configuration issue
I use chrome send hook request . it is runing sucessfully.
I create new repository and fork it, then it is still not working

This is Jenkins server configuration issue
I use chrome send hook request . it is runing sucessfully.
I create new repository and fork it, then it is still not working

What request is being sent that fails?

I send use chrome ,it is fine. like this image.

I understand, check request headers gitea is sending, there is something that Jenkins (Jetty web server) can not handle because of configuration

I understand, check request headers gitea is sending, there is something that Jenkins (Jetty web server) can not handle because of configuration

I create a new repository and use same webkook configuration. it is fine.

gitea request header is that;

I can't close the security options, how to fix this question?


Problem with assert statement

I tryed to use images of the size 512x512 and ended up in the gaussian_diffusion.py at this assert statement: assert model_output.shape == (B, C * 2, *x.shape[2:])
Why should the channels be twice the size?
My model_output.shape is: torch.Size([1, 3, 512, 512]). Why should it be now (1, 6, 512, 512)?
Can somebody explain why this is needed or what I'm doing wrong? It doesn't work when I comment it out :D
assert model_output.shape == (B, C * 2, *x.shape[2:]) AssertionError
Thanks for your answers :)

I tryed to use images of the size 512x512 and ended up in the gaussian_diffusion.py at this assert statement: assert model_output.shape == (B, C * 2, *x.shape[2:]) Why should the channels be twice the size? My model_output.shape is: torch.Size([1, 3, 512, 512]). Why should it be now (1, 6, 512, 512)? Can somebody explain why this is needed or what I'm doing wrong? It doesn't work when I comment it out :D assert model_output.shape == (B, C * 2, *x.shape[2:]) AssertionError Thanks for your answers :)

Hi Mirko1998,
That's because you set the "ModelVarType" to eigther "LEARNED" or "LEARNED_RANGE",
in this case your model output channels must be doubled (2 * C) , since the last 3 channels are for variance learning.

Thank you very much for your answer! That helps me to understand it in more detail 👍

I tryed to use images of the size 512x512 and ended up in the gaussian_diffusion.py at this assert statement: assert model_output.shape == (B, C * 2, *x.shape[2:]) Why should the channels be twice the size? My model_output.shape is: torch.Size([1, 3, 512, 512]). Why should it be now (1, 6, 512, 512)? Can somebody explain why this is needed or what I'm doing wrong? It doesn't work when I comment it out :D Thanks for your answers :)assert model_output.shape == (B, C * 2, *x.shape[2:]) AssertionError

may i ask u how to do then？ because i am same with u to use 512*512 and find modelvartype.learned

I tryed to use images of the size 512x512 and ended up in the gaussian_diffusion.py at this assert statement: assert model_output.shape == (B, C * 2, *x.shape[2:]) Why should the channels be twice the size? My model_output.shape is: torch.Size([1, 3, 512, 512]). Why should it be now (1, 6, 512, 512)? Can somebody explain why this is needed or what I'm doing wrong? It doesn't work when I comment it out :D  Thanks for your answers :)assert model_output.shape == (B, C * 2, *x.shape[2:]) AssertionError

Hi Mirko1998, That's because you set the "ModelVarType" to eigther "LEARNED" or "LEARNED_RANGE", in this case your model output channels must be doubled (2 * C) , since the last 3 channels are for variance learning.

may i ask u how to do then？ because i am same with u to use 512*512 and find modelvartype.learned .plz


Added Snake Case to Pascal Case Python Converter

Added the required program:

#12

Great work @Hritik-Verma41

Thank you @jatinkumar027


Component esphome.coroutine took a long time for an operation --> Timing issue?!?

Hello,
I have been running this code "Victron-MPPT-ve.direct-to-MQTT"on an ESP8266 for months without any errors. HW ESP8266 with a 5V to 3.3V level shifter and the standard pin configuration. After an electrical overstress of the power supply of the ESP8266, it died.
After that I saw the new "VictronMPPT ESPHOME" code switched to the ESPHOME version and ever since I never got a complete message from the microcontrollers.
I have the code in two setups with different HW both have the same issue.
Setup 1: ESP32 with direct connection to the Victron MPPT
Setup 2: ESP8266 with connection through level shifter Victron MPPT
In both cases I only get either half of the values from the MPPT.
Situation 1: Only Batttery voltage, Panel Current, Panel Power...
Situation 2: Only error code, Yield today, Yield Yesterday, Yield Total...
It seems like the readout of RS232 interface is interrupted by some other routine of the ESPs.
Depending on the timing of flashing or read logs I sometimes get Situation 1 and sometimes Situation 2 on both devices.
ESP32 has Situation 1 and ESP8266 has Situation 2 in the logs below.
Any help is very much appreciated - thanks a lot in advance!
ESP32:
INFO ESPHome 2024.2.2
INFO Reading configuration /config/esphome/esphome-web-fe5eac.yaml...
INFO Starting log output from <IP_ADDRESS> using esphome API
INFO Successfully connected to esphome-web-fe5eac @ <IP_ADDRESS> in 0.059s
INFO Successful handshake with esphome-web-fe5eac @ <IP_ADDRESS> in 0.102s
[19:14:06][I][app:102]: ESPHome version 2024.2.2 compiled on Mar 25 2024, 15:05:28
[19:14:06][C][wifi:577]: WiFi:
[19:14:06][C][wifi:409]:   Local MAC: 24:62:AB:FE:5E:AC
[19:14:06][C][wifi:414]:   SSID: 'WLAN-001'[redacted]
[19:14:06][C][wifi:415]:   IP Address: <IP_ADDRESS>
[19:14:06][C][wifi:417]:   BSSID: 50:E6:36:4C:08:38[redacted]
[19:14:06][C][wifi:418]:   Hostname: 'esphome-web-fe5eac'
[19:14:06][C][wifi:420]:   Signal strength: -80 dB ▂▄▆█
[19:14:06][C][wifi:424]:   Channel: 1
[19:14:06][C][wifi:425]:   Subnet: <IP_ADDRESS>
[19:14:06][C][wifi:426]:   Gateway: <IP_ADDRESS>
[19:14:06][C][wifi:427]:   DNS1: <IP_ADDRESS>
[19:14:06][C][wifi:428]:   DNS2: <IP_ADDRESS>
[19:14:06][C][logger:447]: Logger:
[19:14:06][C][logger:448]:   Level: DEBUG
[19:14:06][C][logger:449]:   Log Baud Rate: 115200
[19:14:06][C][logger:451]:   Hardware UART: UART0
[19:14:06][C][uart.arduino_esp32:137]: UART Bus 1:
[19:14:06][C][uart.arduino_esp32:138]:   TX Pin: GPIO17
[19:14:06][C][uart.arduino_esp32:139]:   RX Pin: GPIO16
[19:14:06][C][uart.arduino_esp32:141]:   RX Buffer Size: 512
[19:14:06][C][uart.arduino_esp32:143]:   Baud Rate: 19200 baud
[19:14:06][C][uart.arduino_esp32:144]:   Data Bits: 8
[19:14:06][C][uart.arduino_esp32:145]:   Parity: NONE
[19:14:06][C][uart.arduino_esp32:146]:   Stop bits: 1
[19:14:06][C][victron:032]: Victron:
[19:14:06][C][victron:035]:   Max Power Yesterday 'max power yesterday'
[19:14:06][C][victron:035]:     Device Class: 'power'
[19:14:06][C][victron:035]:     State Class: ''
[19:14:06][C][victron:035]:     Unit of Measurement: 'W'
[19:14:06][C][victron:035]:     Accuracy Decimals: 0
[19:14:06][C][victron:035]:     Icon: 'mdi:power'
[19:14:06][C][victron:036]:   Max Power Today 'max power today'
[19:14:06][C][victron:036]:     Device Class: 'power'
[19:14:06][C][victron:036]:     State Class: ''
[19:14:06][C][victron:036]:     Unit of Measurement: 'W'
[19:14:06][C][victron:036]:     Accuracy Decimals: 0
[19:14:06][C][victron:036]:     Icon: 'mdi:power'
[19:14:06][C][victron:037]:   Yield Total 'yield total'
[19:14:06][C][victron:037]:     Device Class: 'energy'
[19:14:06][C][victron:037]:     State Class: 'total_increasing'
[19:14:06][C][victron:037]:     Unit of Measurement: 'Wh'
[19:14:06][C][victron:037]:     Accuracy Decimals: 0
[19:14:06][C][victron:037]:     Icon: 'mdi:power'
[19:14:06][C][victron:038]:   Yield Yesterday 'yield yesterday'
[19:14:06][C][victron:038]:     Device Class: 'energy'
[19:14:06][C][victron:038]:     State Class: 'total_increasing'
[19:14:06][C][victron:038]:     Unit of Measurement: 'Wh'
[19:14:06][C][victron:038]:     Accuracy Decimals: 0
[19:14:06][C][victron:038]:     Icon: 'mdi:power'
[19:14:06][C][victron:039]:   Yield Today 'yield today'
[19:14:06][C][victron:039]:     Device Class: 'energy'
[19:14:06][C][victron:039]:     State Class: 'total_increasing'
[19:14:06][C][victron:039]:     Unit of Measurement: 'Wh'
[19:14:06][C][victron:039]:     Accuracy Decimals: 0
[19:14:06][C][victron:039]:     Icon: 'mdi:power'
[19:14:06][C][victron:040]:   Panel Voltage 'panel voltage'
[19:14:06][C][victron:040]:     Device Class: 'voltage'
[19:14:06][C][victron:040]:     State Class: ''
[19:14:06][C][victron:040]:     Unit of Measurement: 'V'
[19:14:06][C][victron:040]:     Accuracy Decimals: 3
[19:14:06][C][victron:040]:     Icon: 'mdi:flash'
[19:14:06][C][victron:041]:   Panel Power 'panel power'
[19:14:06][C][victron:041]:     Device Class: 'power'
[19:14:06][C][victron:041]:     State Class: ''
[19:14:06][C][victron:041]:     Unit of Measurement: 'W'
[19:14:06][C][victron:041]:     Accuracy Decimals: 0
[19:14:06][C][victron:041]:     Icon: 'mdi:power'
[19:14:06][C][victron:042]:   Battery Voltage 'battery voltage'
[19:14:06][C][victron:042]:     Device Class: 'voltage'
[19:14:06][C][victron:042]:     State Class: ''
[19:14:06][C][victron:042]:     Unit of Measurement: 'V'
[19:14:06][C][victron:042]:     Accuracy Decimals: 3
[19:14:06][C][victron:042]:     Icon: 'mdi:flash'
[19:14:06][C][victron:045]:   Battery Current 'panel current'
[19:14:06][C][victron:045]:     Device Class: 'current'
[19:14:06][C][victron:045]:     State Class: ''
[19:14:06][C][victron:045]:     Unit of Measurement: 'A'
[19:14:06][C][victron:045]:     Accuracy Decimals: 3
[19:14:06][C][victron:045]:     Icon: 'mdi:current-ac'
[19:14:06][C][victron:050]:   Load Current 'load current'
[19:14:06][C][victron:050]:     Device Class: 'current'
[19:14:06][C][victron:050]:     State Class: ''
[19:14:06][C][victron:050]:     Unit of Measurement: 'A'
[19:14:06][C][victron:050]:     Accuracy Decimals: 3
[19:14:06][C][victron:050]:     Icon: 'mdi:current-ac'
[19:14:06][C][victron:051]:   Day Number 'day number'
[19:14:06][C][victron:051]:     State Class: ''
[19:14:06][C][victron:051]:     Unit of Measurement: ''
[19:14:06][C][victron:051]:     Accuracy Decimals: 0
[19:14:06][C][victron:052]:   Charging Mode ID 'charging mode id'
[19:14:06][C][victron:052]:     State Class: ''
[19:14:06][C][victron:052]:     Unit of Measurement: ''
[19:14:06][C][victron:052]:     Accuracy Decimals: 0
[19:14:06][C][victron:053]:   Error Code 'error code'
[19:14:06][C][victron:053]:     State Class: ''
[19:14:06][C][victron:053]:     Unit of Measurement: ''
[19:14:06][C][victron:053]:     Accuracy Decimals: 0
[19:14:06][C][victron:055]:   Tracking Mode ID 'tracking mode id'
[19:14:06][C][victron:055]:     State Class: ''
[19:14:06][C][victron:055]:     Unit of Measurement: ''
[19:14:06][C][victron:055]:     Accuracy Decimals: 0
[19:14:06][C][victron:058]:   Charging Mode 'charging mode'
[19:14:06][C][victron:059]:   Error Text 'error'
[19:14:06][C][victron:061]:   Tracking Mode 'tracking mode'
[19:14:06][C][victron:063]:   Firmware Version 'firmware version'
[19:14:06][C][victron:065]:   Device Type 'device type'
[19:14:06][D][sensor:094]: 'battery voltage': Sending state 52.62000 V with 3 decimals of accuracy
[19:14:06][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[19:14:06][D][sensor:094]: 'panel voltage': Sending state 16.10000 V with 3 decimals of accuracy
[19:14:06][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[19:14:06][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:06][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[19:14:06][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:06][D][text_sensor:064]: 'charging mode': Sending state 'Off'
[19:14:06][W][component:214]: Component esphome.coroutine took a long time for an operation (0.08 s).
[19:14:06][W][component:215]: Components should block for at most 20-30ms.
[19:14:06][C][captive_portal:088]: Captive Portal:
[19:14:06][C][mdns:115]: mDNS:
[19:14:06][C][mdns:116]:   Hostname: esphome-web-fe5eac
[19:14:06][C][ota:096]: Over-The-Air Updates:
[19:14:06][C][ota:097]:   Address: esphome-web-fe5eac.local:3232
[19:14:06][C][ota:103]:   OTA version: 2.
[19:14:06][C][api:139]: API Server:
[19:14:06][C][api:140]:   Address: esphome-web-fe5eac.local:6053
[19:14:06][C][api:142]:   Using noise encryption: YES
[19:14:07][D][sensor:094]: 'battery voltage': Sending state 52.61000 V with 3 decimals of accuracy
[19:14:07][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[19:14:07][D][sensor:094]: 'panel voltage': Sending state 16.07000 V with 3 decimals of accuracy
[19:14:07][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[19:14:07][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:07][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[19:14:07][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:07][D][text_sensor:064]: 'charging mode': Sending state 'Off'
[19:14:07][W][component:214]: Component esphome.coroutine took a long time for an operation (0.07 s).
[19:14:07][W][component:215]: Components should block for at most 20-30ms.
[19:14:08][D][sensor:094]: 'battery voltage': Sending state 52.61000 V with 3 decimals of accuracy
[19:14:08][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[19:14:08][D][sensor:094]: 'panel voltage': Sending state 16.03000 V with 3 decimals of accuracy
[19:14:08][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[19:14:08][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:08][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[19:14:08][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:08][D][text_sensor:064]: 'charging mode': Sending state 'Off'
[19:14:08][W][component:214]: Component esphome.coroutine took a long time for an operation (0.09 s).
[19:14:08][W][component:215]: Components should block for at most 20-30ms.
[19:14:09][D][sensor:094]: 'battery voltage': Sending state 52.61000 V with 3 decimals of accuracy
[19:14:09][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[19:14:09][D][sensor:094]: 'panel voltage': Sending state 15.99000 V with 3 decimals of accuracy
[19:14:09][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[19:14:09][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:09][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[19:14:09][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[19:14:09][D][text_sensor:064]: 'charging mode': Sending state 'Off'
[19:14:09][W][component:214]: Component esphome.coroutine took a long time for an operation (0.08 s).
[19:14:09][W][component:215]: Components should block for at most 20-30ms.
ESP8266:
INFO ESPHome 2024.2.2
INFO Reading configuration /config/esphome/esphome-web-85a18a.yaml...
INFO Starting log output from <IP_ADDRESS> using esphome API
INFO Successfully connected to esphome-web-85a18a @ <IP_ADDRESS> in 0.017s
INFO Successful handshake with esphome-web-85a18a @ <IP_ADDRESS> in 2.533s
[19:29:15][I][app:102]: ESPHome version 2024.2.2 compiled on Mar 23 2024, 22:03:23
[19:29:15][C][wifi:577]: WiFi:
[19:29:15][C][wifi:409]:   Local MAC: BC:FF:4D:85:A1:8A
[19:29:15][C][wifi:414]:   SSID: 'WLAN-001'[redacted]
[19:29:15][C][wifi:415]:   IP Address: <IP_ADDRESS>
[19:29:15][C][wifi:416]:   BSSID: 50:E6:36:4C:08:38[redacted]
[19:29:15][C][wifi:418]:   Hostname: 'esphome-web-85a18a'
[19:29:15][C][wifi:420]:   Signal strength: -75 dB ▂▄▆█
[19:29:15][C][wifi:424]:   Channel: 1
[19:29:15][C][wifi:425]:   Subnet: <IP_ADDRESS>
[19:29:15][C][wifi:426]:   Gateway: <IP_ADDRESS>
[19:29:15][C][wifi:427]:   DNS1: <IP_ADDRESS>
[19:29:15][C][wifi:428]:   DNS2: <IP_ADDRESS>
[19:29:15][C][logger:447]: Logger:
[19:29:15][C][logger:448]:   Level: DEBUG
[19:29:15][C][logger:449]:   Log Baud Rate: 115200
[19:29:15][C][logger:451]:   Hardware UART: UART0
[19:29:15][C][uart.arduino_esp8266:118]: UART Bus:
[19:29:15][C][uart.arduino_esp8266:119]:   TX Pin: GPIO15
[19:29:15][C][uart.arduino_esp8266:120]:   RX Pin: GPIO13
[19:29:15][C][uart.arduino_esp8266:122]:   RX Buffer Size: 128
[19:29:15][C][uart.arduino_esp8266:124]:   Baud Rate: 19200 baud
[19:29:15][C][uart.arduino_esp8266:125]:   Data Bits: 8
[19:29:15][C][uart.arduino_esp8266:126]:   Parity: NONE
[19:29:15][C][uart.arduino_esp8266:127]:   Stop bits: 1
[19:29:15][C][uart.arduino_esp8266:131]:   Using software serial
[19:29:15][C][victron:032]: Victron:
[19:29:15][C][victron:035]:   Max Power Yesterday 'max power yesterday'
[19:29:15][C][victron:035]:     Device Class: 'power'
[19:29:15][C][victron:035]:     State Class: ''
[19:29:15][C][victron:035]:     Unit of Measurement: 'W'
[19:29:15][C][victron:035]:     Accuracy Decimals: 0
[19:29:15][C][victron:035]:     Icon: 'mdi:power'
[19:29:15][C][victron:036]:   Max Power Today 'max power today'
[19:29:15][C][victron:036]:     Device Class: 'power'
[19:29:15][C][victron:036]:     State Class: ''
[19:29:15][C][victron:036]:     Unit of Measurement: 'W'
[19:29:15][C][victron:036]:     Accuracy Decimals: 0
[19:29:15][C][victron:036]:     Icon: 'mdi:power'
[19:29:15][C][victron:037]:   Yield Total 'yield total'
[19:29:15][C][victron:037]:     Device Class: 'energy'
[19:29:15][C][victron:037]:     State Class: 'total_increasing'
[19:29:15][C][victron:037]:     Unit of Measurement: 'Wh'
[19:29:15][C][victron:037]:     Accuracy Decimals: 0
[19:29:15][C][victron:037]:     Icon: 'mdi:power'
[19:29:15][C][victron:038]:   Yield Yesterday 'yield yesterday'
[19:29:15][C][victron:038]:     Device Class: 'energy'
[19:29:15][C][victron:038]:     State Class: 'total_increasing'
[19:29:15][C][victron:038]:     Unit of Measurement: 'Wh'
[19:29:15][C][victron:038]:     Accuracy Decimals: 0
[19:29:15][C][victron:038]:     Icon: 'mdi:power'
[19:29:15][C][victron:039]:   Yield Today 'yield today'
[19:29:15][C][victron:039]:     Device Class: 'energy'
[19:29:15][C][victron:039]:     State Class: 'total_increasing'
[19:29:15][C][victron:039]:     Unit of Measurement: 'Wh'
[19:29:15][C][victron:039]:     Accuracy Decimals: 0
[19:29:15][C][victron:039]:     Icon: 'mdi:power'
[19:29:15][C][victron:040]:   Panel Voltage 'panel voltage'
[19:29:15][C][victron:040]:     Device Class: 'voltage'
[19:29:15][C][victron:040]:     State Class: ''
[19:29:15][C][victron:040]:     Unit of Measurement: 'V'
[19:29:15][C][victron:040]:     Accuracy Decimals: 3
[19:29:15][C][victron:040]:     Icon: 'mdi:flash'
[19:29:15][C][victron:041]:   Panel Power 'panel power'
[19:29:15][C][victron:041]:     Device Class: 'power'
[19:29:15][C][victron:041]:     State Class: ''
[19:29:15][C][victron:041]:     Unit of Measurement: 'W'
[19:29:15][C][victron:041]:     Accuracy Decimals: 0
[19:29:15][C][victron:041]:     Icon: 'mdi:power'
[19:29:15][C][victron:042]:   Battery Voltage 'battery voltage'
[19:29:15][C][victron:042]:     Device Class: 'voltage'
[19:29:15][C][victron:042]:     State Class: ''
[19:29:15][C][victron:042]:     Unit of Measurement: 'V'
[19:29:15][C][victron:042]:     Accuracy Decimals: 3
[19:29:15][C][victron:042]:     Icon: 'mdi:flash'
[19:29:15][C][victron:045]:   Battery Current 'panel current'
[19:29:15][C][victron:045]:     Device Class: 'current'
[19:29:15][C][victron:045]:     State Class: ''
[19:29:15][C][victron:045]:     Unit of Measurement: 'A'
[19:29:15][C][victron:045]:     Accuracy Decimals: 3
[19:29:15][C][victron:045]:     Icon: 'mdi:current-ac'
[19:29:15][C][victron:050]:   Load Current 'load current'
[19:29:15][C][victron:050]:     Device Class: 'current'
[19:29:15][C][victron:050]:     State Class: ''
[19:29:15][C][victron:050]:     Unit of Measurement: 'A'
[19:29:15][C][victron:050]:     Accuracy Decimals: 3
[19:29:15][C][victron:050]:     Icon: 'mdi:current-ac'
[19:29:15][C][victron:051]:   Day Number 'day number'
[19:29:15][C][victron:051]:     State Class: ''
[19:29:15][C][victron:051]:     Unit of Measurement: ''
[19:29:15][C][victron:051]:     Accuracy Decimals: 0
[19:29:15][C][victron:052]:   Charging Mode ID 'charging mode id'
[19:29:15][C][victron:052]:     State Class: ''
[19:29:15][C][victron:052]:     Unit of Measurement: ''
[19:29:15][C][victron:052]:     Accuracy Decimals: 0
[19:29:15][C][victron:053]:   Error Code 'error code'
[19:29:15][C][victron:053]:     State Class: ''
[19:29:15][C][victron:053]:     Unit of Measurement: ''
[19:29:15][C][victron:053]:     Accuracy Decimals: 0
[19:29:15][C][victron:055]:   Tracking Mode ID 'tracking mode id'
[19:29:15][C][victron:055]:     State Class: ''
[19:29:15][C][victron:055]:     Unit of Measurement: ''
[19:29:15][C][victron:055]:     Accuracy Decimals: 0
[19:29:15][C][victron:058]:   Charging Mode 'charging mode'
[19:29:15][C][victron:059]:   Error Text 'error'
[19:29:15][C][victron:061]:   Tracking Mode 'tracking mode'
[19:29:15][C][victron:063]:   Firmware Version 'firmware version'
[19:29:15][C][victron:065]:   Device Type 'device type'
[19:29:15][D][sensor:093]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[19:29:15][D][text_sensor:064]: 'error': Sending state 'No error'
[19:29:15][D][sensor:093]: 'yield total': Sending state 21040.00000 Wh with 0 decimals of accuracy
[19:29:15][D][sensor:093]: 'yield today': Sending state 11360.00000 Wh with 0 decimals of accuracy
[19:29:15][D][sensor:093]: 'max power today': Sending state 3438.00000 W with 0 decimals of accuracy
[19:29:15][D][sensor:093]: 'yield yesterday': Sending state 9680.00000 Wh with 0 decimals of accuracy
[19:29:15][D][sensor:093]: 'max power yesterday': Sending state 3270.00000 W with 0 decimals of accuracy
[19:29:15][D][sensor:093]: 'day number': Sending state 1.00000  with 0 decimals of accuracy
[19:29:15][W][component:214]: Component esphome.coroutine took a long time for an operation (0.07 s).
[19:29:16][W][component:215]: Components should block for at most 20-30ms.
[19:29:16][C][captive_portal:088]: Captive Portal:
[19:29:16][C][mdns:115]: mDNS:
[19:29:16][C][mdns:116]:   Hostname: esphome-web-85a18a
[19:29:16][C][ota:096]: Over-The-Air Updates:
[19:29:16][C][ota:097]:   Address: esphome-web-85a18a.local:8266
[19:29:16][C][ota:103]:   OTA version: 2.
[19:29:16][C][api:139]: API Server:
[19:29:16][C][api:140]:   Address: esphome-web-85a18a.local:6053
[19:29:16][C][api:142]:   Using noise encryption: YES
[19:29:16][D][sensor:093]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[19:29:16][D][text_sensor:064]: 'error': Sending state 'No error'
[19:29:16][D][sensor:093]: 'yield total': Sending state 21040.00000 Wh with 0 decimals of accuracy
[19:29:16][D][sensor:093]: 'yield today': Sending state 11360.00000 Wh with 0 decimals of accuracy
[19:29:16][D][sensor:093]: 'max power today': Sending state 3438.00000 W with 0 decimals of accuracy
[19:29:16][D][sensor:093]: 'yield yesterday': Sending state 9680.00000 Wh with 0 decimals of accuracy
[19:29:16][D][sensor:093]: 'max power yesterday': Sending state 3270.00000 W with 0 decimals of accuracy
[19:29:16][D][sensor:093]: 'day number': Sending state 1.00000  with 0 decimals of accuracy
[19:29:16][W][component:214]: Component esphome.coroutine took a long time for an operation (0.09 s).
[19:29:16][W][component:215]: Components should block for at most 20-30ms.
[19:29:18][D][sensor:093]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[19:29:18][D][text_sensor:064]: 'error': Sending state 'No error'
[19:29:18][D][sensor:093]: 'yield total': Sending state 21040.00000 Wh with 0 decimals of accuracy
[19:29:18][D][sensor:093]: 'yield today': Sending state 11360.00000 Wh with 0 decimals of accuracy
[19:29:18][D][sensor:093]: 'max power today': Sending state 3438.00000 W with 0 decimals of accuracy
[19:29:18][D][sensor:093]: 'yield yesterday': Sending state 9680.00000 Wh with 0 decimals of accuracy
[19:29:18][D][sensor:093]: 'max power yesterday': Sending state 3270.00000 W with 0 decimals of accuracy
[19:29:18][D][sensor:093]: 'day number': Sending state 1.00000  with 0 decimals of accuracy
[19:29:18][W][component:214]: Component esphome.coroutine took a long time for an operation (0.10 s).
[19:29:18][W][component:215]: Components should block for at most 20-30ms.
[19:29:19][D][sensor:093]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[19:29:19][D][text_sensor:064]: 'error': Sending state 'No error'
[19:29:19][D][sensor:093]: 'yield total': Sending state 21040.00000 Wh with 0 decimals of accuracy
[19:29:19][D][sensor:093]: 'yield today': Sending state 11360.00000 Wh with 0 decimals of accuracy
[19:29:19][D][sensor:093]: 'max power today': Sending state 3438.00000 W with 0 decimals of accuracy
[19:29:19][D][sensor:093]: 'yield yesterday': Sending state 9680.00000 Wh with 0 decimals of accuracy
[19:29:19][D][sensor:093]: 'max power yesterday': Sending state 3270.00000 W with 0 decimals of accuracy
[19:29:19][D][sensor:093]: 'day number': Sending state 1.00000  with 0 decimals of accuracy
[19:29:19][W][component:214]: Component esphome.coroutine took a long time for an operation (0.10 s).
[19:29:19][W][component:215]: Components should block for at most 20-30ms.
[19:29:20][D][sensor:093]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[19:29:20][D][text_sensor:064]: 'error': Sending state 'No error'
[19:29:20][D][sensor:093]: 'yield total': Sending state 21040.00000 Wh with 0 decimals of accuracy
[19:29:20][D][sensor:093]: 'yield today': Sending state 11360.00000 Wh with 0 decimals of accuracy
[19:29:20][D][sensor:093]: 'max power today': Sending state 3438.00000 W with 0 decimals of accuracy
[19:29:20][D][sensor:093]: 'yield yesterday': Sending state 9680.00000 Wh with 0 decimals of accuracy
[19:29:20][D][sensor:093]: 'max power yesterday': Sending state 3270.00000 W with 0 decimals of accuracy
[19:29:20][D][sensor:093]: 'day number': Sending state 1.00000  with 0 decimals of accuracy
[19:29:20][W][component:214]: Component esphome.coroutine took a long time for an operation (0.09 s).
[19:29:20][W][component:215]: Components should block for at most 20-30ms.
Code ESP32:
esphome:
name: esphome-web-fe5eac
friendly_name: Victron_MPPT_ESP32
esp32:
board: esp32dev
framework:
type: arduino
Enable logging
logger:
#baud_rate: 19200
#level: WARN
#logs:
#component: ERROR
Enable Home Assistant API
api:
encryption:
key: "xxxxx"
ota:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
#ap:
#ssid: "Esphome-Web-Fe5Eac"
#password: "xxx"
captive_portal:
external_components:
#- source: github://B00GI3M4N/VictronMPPT-ESPHOME_FIX@main

source: github://KinDR007/VictronMPPT-ESPHOME@main

uart:
id: uart_0
tx_pin: GPIO17  # Not used! The communication is read-only
rx_pin: GPIO16
baud_rate: 19200
rx_buffer_size: 512 #86
victron:
id: victron0
uart_id: uart_0
sensor:

platform: victron
victron_id: victron0
max_power_yesterday:
name: "max power yesterday"
panel_voltage:
name: "panel voltage"
#filters:
#- throttle: 1s
panel_power:
name: "panel power"
filters:
- throttle: 1s
battery_current:
name: "panel current"
filters:
#- throttle: 1s
battery_voltage:
name: "battery voltage"
#filters:
#- throttle: 1s
max_power_today:
name: "max power today"
filters:
#- throttle: 1s
yield_total:
name: "yield total"
filters:
#- throttle: 1s
yield_yesterday:
name: "yield yesterday"
filters:
#- throttle: 1s
yield_today:
name: "yield today"
filters:
#- throttle: 1s
day_number:
name: "day number"
charging_mode_id:
name: "charging mode id"
error_code:
name: "error code"
tracking_mode_id:
name: "tracking mode id"
load_current:
name: "load current"

text_sensor:

platform: victron
victron_id: victron0
charging_mode:
name: "charging mode"
error:
name: "error"
tracking_mode:
name: "tracking mode"
firmware_version:
name: "firmware version"
device_type:
name: "device type"
serial_number:
name: "serial number"

#binary_sensor:
- platform: victron
victron_id: victron0
load_state:
name: "load state"
relay_state:
name: "relay state"
Code ESP8266:
esphome:
name: esphome-web-85a18a
friendly_name: Victron_MPPT_2
esp8266:
board: d1_mini
Enable logging
logger:
Enable Home Assistant API
api:
encryption:
key: "xxx"
ota:
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Esphome-Web-85A18A"
password: "xxx"
captive_portal:
external_components:
#- source: github://B00GI3M4N/VictronMPPT-ESPHOME_FIX@main

source: github://KinDR007/VictronMPPT-ESPHOME@main

uart:
id: uart_0
tx_pin: D8  # Not used! The communication is read-only
rx_pin: D7
baud_rate: 19200
rx_buffer_size: 128 #86
victron:
id: victron0
uart_id: uart_0
sensor:

platform: victron
victron_id: victron0
max_power_yesterday:
name: "max power yesterday"
panel_voltage:
name: "panel voltage"
#filters:
#- throttle: 1s
panel_power:
name: "panel power"
filters:
- throttle: 1s
battery_current:
name: "panel current"
filters:
#- throttle: 1s
battery_voltage:
name: "battery voltage"
#filters:
#- throttle: 1s
max_power_today:
name: "max power today"
filters:
#- throttle: 1s
yield_total:
name: "yield total"
filters:
#- throttle: 1s
yield_yesterday:
name: "yield yesterday"
filters:
#- throttle: 1s
yield_today:
name: "yield today"
filters:
#- throttle: 1s
day_number:
name: "day number"
charging_mode_id:
name: "charging mode id"
error_code:
name: "error code"
tracking_mode_id:
name: "tracking mode id"
load_current:
name: "load current"

text_sensor:

platform: victron
victron_id: victron0
charging_mode:
name: "charging mode"
error:
name: "error"
tracking_mode:
name: "tracking mode"
firmware_version:
name: "firmware version"
device_type:
name: "device type"
serial_number:
name: "serial number"

#binary_sensor:
- platform: victron
victron_id: victron0
load_state:
name: "load state"
relay_state:
name: "relay state"

Ok, sorry going through all other issues I realized this:
victron:
id: victron0
throttle: 10s# <-- This
uart_id: uart_0
solves the problem at least the messages change from Situation 1 to Situation 2 every 10s.
Still a little unsatisfying because with this delay it is a lot less fun to watch it run :-(

Hi syssi,
thank you that erased the warning and I was able to reduce the throttle down to 6s.
Is there any possibility to split the publishing into two parts to further decrease the throttle?
My wish would be 1-2s throttle to see the MPPT work
INFO ESPHome 2024.2.2
INFO Reading configuration /config/esphome/esphome-web-fe5eac.yaml...
INFO Starting log output from <IP_ADDRESS> using esphome API
INFO Successfully connected to esphome-web-fe5eac @ <IP_ADDRESS> in 0.012s
INFO Successful handshake with esphome-web-fe5eac @ <IP_ADDRESS> in 0.110s
[22:30:42][I][app:102]: ESPHome version 2024.2.2 compiled on Mar 25 2024, 22:27:52
[22:30:42][C][wifi:577]: WiFi:
[22:30:42][C][wifi:409]:   Local MAC: 24:62:AB:FE:5E:AC
[22:30:42][C][wifi:414]:   SSID: 'WLAN-001'[redacted]
[22:30:42][C][wifi:415]:   IP Address: <IP_ADDRESS>
[22:30:42][C][wifi:417]:   BSSID: 50:E6:36:4C:08:38[redacted]
[22:30:42][C][wifi:418]:   Hostname: 'esphome-web-fe5eac'
[22:30:42][C][wifi:420]:   Signal strength: -79 dB ▂▄▆█
[22:30:42][C][wifi:424]:   Channel: 1
[22:30:42][C][wifi:425]:   Subnet: <IP_ADDRESS>
[22:30:42][C][wifi:426]:   Gateway: <IP_ADDRESS>
[22:30:42][C][wifi:427]:   DNS1: <IP_ADDRESS>
[22:30:42][C][wifi:428]:   DNS2: <IP_ADDRESS>
[22:30:42][C][logger:447]: Logger:
[22:30:42][C][logger:448]:   Level: DEBUG
[22:30:42][C][logger:449]:   Log Baud Rate: 115200
[22:30:42][C][logger:451]:   Hardware UART: UART0
[22:30:42][C][uart.idf:139]: UART Bus 1:
[22:30:42][C][uart.idf:140]:   TX Pin: GPIO17
[22:30:42][C][uart.idf:141]:   RX Pin: GPIO16
[22:30:42][C][uart.idf:143]:   RX Buffer Size: 256
[22:30:42][C][uart.idf:145]:   Baud Rate: 19200 baud
[22:30:42][C][uart.idf:146]:   Data Bits: 8
[22:30:42][C][uart.idf:147]:   Parity: NONE
[22:30:42][C][uart.idf:148]:   Stop bits: 1
[22:30:42][C][victron:032]: Victron:
[22:30:42][C][victron:035]:   Max Power Yesterday 'max power yesterday'
[22:30:42][C][victron:035]:     Device Class: 'power'
[22:30:42][C][victron:035]:     State Class: ''
[22:30:42][C][victron:035]:     Unit of Measurement: 'W'
[22:30:42][C][victron:035]:     Accuracy Decimals: 0
[22:30:42][C][victron:035]:     Icon: 'mdi:power'
[22:30:42][C][victron:036]:   Max Power Today 'max power today'
[22:30:42][C][victron:036]:     Device Class: 'power'
[22:30:42][C][victron:036]:     State Class: ''
[22:30:42][C][victron:036]:     Unit of Measurement: 'W'
[22:30:42][C][victron:036]:     Accuracy Decimals: 0
[22:30:42][C][victron:036]:     Icon: 'mdi:power'
[22:30:42][C][victron:037]:   Yield Total 'yield total'
[22:30:42][C][victron:037]:     Device Class: 'energy'
[22:30:42][C][victron:037]:     State Class: 'total_increasing'
[22:30:42][C][victron:037]:     Unit of Measurement: 'Wh'
[22:30:42][C][victron:037]:     Accuracy Decimals: 0
[22:30:42][C][victron:037]:     Icon: 'mdi:power'
[22:30:42][C][victron:038]:   Yield Yesterday 'yield yesterday'
[22:30:42][C][victron:038]:     Device Class: 'energy'
[22:30:42][C][victron:038]:     State Class: 'total_increasing'
[22:30:42][C][victron:038]:     Unit of Measurement: 'Wh'
[22:30:42][C][victron:038]:     Accuracy Decimals: 0
[22:30:42][C][victron:038]:     Icon: 'mdi:power'
[22:30:42][C][victron:039]:   Yield Today 'yield today'
[22:30:42][C][victron:039]:     Device Class: 'energy'
[22:30:42][C][victron:039]:     State Class: 'total_increasing'
[22:30:42][C][victron:039]:     Unit of Measurement: 'Wh'
[22:30:42][C][victron:039]:     Accuracy Decimals: 0
[22:30:42][C][victron:039]:     Icon: 'mdi:power'
[22:30:42][C][victron:040]:   Panel Voltage 'panel voltage'
[22:30:42][C][victron:040]:     Device Class: 'voltage'
[22:30:42][C][victron:040]:     State Class: ''
[22:30:42][C][victron:040]:     Unit of Measurement: 'V'
[22:30:42][C][victron:040]:     Accuracy Decimals: 3
[22:30:42][C][victron:040]:     Icon: 'mdi:flash'
[22:30:42][C][victron:041]:   Panel Power 'panel power'
[22:30:42][C][victron:041]:     Device Class: 'power'
[22:30:42][C][victron:041]:     State Class: ''
[22:30:42][C][victron:041]:     Unit of Measurement: 'W'
[22:30:42][C][victron:041]:     Accuracy Decimals: 0
[22:30:42][C][victron:041]:     Icon: 'mdi:power'
[22:30:42][C][victron:042]:   Battery Voltage 'battery voltage'
[22:30:42][C][victron:042]:     Device Class: 'voltage'
[22:30:42][C][victron:042]:     State Class: ''
[22:30:42][C][victron:042]:     Unit of Measurement: 'V'
[22:30:42][C][victron:042]:     Accuracy Decimals: 3
[22:30:42][C][victron:042]:     Icon: 'mdi:flash'
[22:30:42][C][victron:045]:   Battery Current 'panel current'
[22:30:42][C][victron:045]:     Device Class: 'current'
[22:30:42][C][victron:045]:     State Class: ''
[22:30:42][C][victron:045]:     Unit of Measurement: 'A'
[22:30:42][C][victron:045]:     Accuracy Decimals: 3
[22:30:42][C][victron:045]:     Icon: 'mdi:current-ac'
[22:30:42][C][victron:050]:   Load Current 'load current'
[22:30:42][C][victron:050]:     Device Class: 'current'
[22:30:42][C][victron:050]:     State Class: ''
[22:30:42][C][victron:050]:     Unit of Measurement: 'A'
[22:30:42][C][victron:050]:     Accuracy Decimals: 3
[22:30:42][C][victron:050]:     Icon: 'mdi:current-ac'
[22:30:42][C][victron:051]:   Day Number 'day number'
[22:30:42][C][victron:051]:     State Class: ''
[22:30:42][C][victron:051]:     Unit of Measurement: ''
[22:30:42][C][victron:051]:     Accuracy Decimals: 0
[22:30:42][C][victron:052]:   Charging Mode ID 'charging mode id'
[22:30:42][C][victron:052]:     State Class: ''
[22:30:42][C][victron:052]:     Unit of Measurement: ''
[22:30:42][C][victron:052]:     Accuracy Decimals: 0
[22:30:42][C][victron:053]:   Error Code 'error code'
[22:30:42][C][victron:053]:     State Class: ''
[22:30:42][C][victron:053]:     Unit of Measurement: ''
[22:30:42][C][victron:053]:     Accuracy Decimals: 0
[22:30:42][C][victron:055]:   Tracking Mode ID 'tracking mode id'
[22:30:42][C][victron:055]:     State Class: ''
[22:30:42][C][victron:055]:     Unit of Measurement: ''
[22:30:42][C][victron:055]:     Accuracy Decimals: 0
[22:30:42][C][victron:058]:   Charging Mode 'charging mode'
[22:30:42][C][victron:059]:   Error Text 'error'
[22:30:42][C][victron:061]:   Tracking Mode 'tracking mode'
[22:30:42][C][victron:063]:   Firmware Version 'firmware version'
[22:30:42][C][victron:065]:   Device Type 'device type'
[22:30:42][C][captive_portal:088]: Captive Portal:
[22:30:42][C][mdns:115]: mDNS:
[22:30:42][C][mdns:116]:   Hostname: esphome-web-fe5eac
[22:30:42][C][ota:096]: Over-The-Air Updates:
[22:30:42][C][ota:097]:   Address: esphome-web-fe5eac.local:3232
[22:30:42][C][ota:103]:   OTA version: 2.
[22:30:42][C][api:139]: API Server:
[22:30:42][C][api:140]:   Address: esphome-web-fe5eac.local:6053
[22:30:42][C][api:142]:   Using noise encryption: YES
[22:30:48][D][sensor:094]: 'battery voltage': Sending state 52.76000 V with 3 decimals of accuracy
[22:30:48][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[22:30:48][D][sensor:094]: 'panel voltage': Sending state 3.83000 V with 3 decimals of accuracy
[22:30:48][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[22:30:48][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[22:30:48][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[22:30:48][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[22:30:48][D][text_sensor:064]: 'charging mode': Sending state 'Off'
[22:30:54][D][sensor:094]: 'error code': Sending state 0.00000  with 0 decimals of accuracy
[22:30:54][D][text_sensor:064]: 'error': Sending state 'No error'
[22:30:54][D][sensor:094]: 'yield total': Sending state<PHONE_NUMBER>0 Wh with 0 decimals of accuracy
[22:30:54][D][sensor:094]: 'yield today': Sending state 10030.00000 Wh with 0 decimals of accuracy
[22:30:54][D][sensor:094]: 'max power today': Sending state 3428.00000 W with 0 decimals of accuracy
[22:30:54][D][sensor:094]: 'yield yesterday': Sending state 8330.00000 Wh with 0 decimals of accuracy
[22:30:54][D][sensor:094]: 'max power yesterday': Sending state 3244.00000 W with 0 decimals of accuracy
[22:30:54][D][sensor:094]: 'day number': Sending state 207.00000  with 0 decimals of accuracy
[22:31:00][D][sensor:094]: 'battery voltage': Sending state 52.76000 V with 3 decimals of accuracy
[22:31:00][D][sensor:094]: 'panel current': Sending state 0.00000 A with 3 decimals of accuracy
[22:31:00][D][sensor:094]: 'panel voltage': Sending state 3.83000 V with 3 decimals of accuracy
[22:31:00][D][sensor:094]: 'panel power': Sending state 0.00000 W with 0 decimals of accuracy
[22:31:00][D][sensor:094]: 'tracking mode id': Sending state 0.00000  with 0 decimals of accuracy
[22:31:00][D][text_sensor:064]: 'tracking mode': Sending state 'Off'
[22:31:00][D][sensor:094]: 'charging mode id': Sending state 0.00000  with 0 decimals of accuracy
[22:31:00][D][text_sensor:064]: 'charging mode': Sending state 'Off'

I assume printing the log messages is time consuming. Try to set the log level to INFO. This should free many CPU cycles.

Hi syssi,
good idea, unfortunately did not help to decrease the throttle time. Situation with the messages is the same, as soon as I go below  6s of throttle I lose values. After programing several times over-the-air, one programming was interrupted and I lost connection to the ESP32, now need to setup everything again. If it is ok for you I keep you updated about the status.
Best regards, Michael

All the wiring and timing "problems" let me to switch to this -->[https://github.com/Fabian-Schmidt/esphome-victron_ble] solution. The throttle time is still slower than I would like it, but I don´t have to worry about all the wiring and voltage levels.
If you have a SmartSolar with bluetooth and access to a ESP32, the solution above is very nice.
@syssi: I saw you also contributed to bluetooth solution - thanks for your great work!