Added icons to buttons and check the size of the dataset

Added some little button icons to the displayed in the contents.

Also read the dataset and create an array to check the length, for later open a table window.

Update
The table windows can be opened/closed when a tabular dataset is selected.

Issues

checkbox of the table doesn't stay checked, it goes back to the default behaviour immediately

I think it is because of this line. It creates a new default TableWindow object each time.
Maybe it can store the references to those objects somehow.
This issue does not exist on the EGUI's table_demo.rs demo. Try to see how they did it.
This issue is not so critical as the table view is going to be read-only (i.e. users cannot change the values, they can just display).
let mut table_box = Box::<super::table::TableWindow>::default();

There is also an error happening in some cases, for example when clicking the /general/experiment_description item the window disappears and gives the following error:
split_name = ["", "general", "experiment_description"]
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: no conversion paths found', src/gui.rs:76:34
note: run with `RUST_BACKTRACE=1` environment variable to display a `backtrace`

We should remove the upwrap calls there and treat those exceptions.

As far as I can see, we have to handle two cases:

scalar datasets that contain metadata (like in experiment_description).
array datasets that contain the actual data.

For scalar datasets we should use the following:
let x_data: hdf5::types::VarLenUnicode = group
                                .handler
                                .dataset(dataset)
                                .unwrap()
                                .read_scalar::<hdf5::types::VarLenUnicode>()
                                .unwrap();

Ok, the hdf5 -> Rust type binding works now.
For hdf5::types, it appears we cannot get away with handling only Float, Integer and String. We have to handle all of them (the Rust way :) ).
I was afraid handling all of those types would end-up in a lot of duplicated code. To address that I used the generic types.
While working on generic types I learned something. Rust has a syntax to restrict the possible generic types.
E.g.
impl<T: std::fmt::Display> TableWindow<T>

This will restrict the type T for those types that implement the std::fmt::Display trait.
Moreover, it allows us to restrict types that implement multiple traits.
E.g.
    fn show_dataset<T: hdf5::H5Type + std::fmt::Display>(

This means that the show_dataset function takes the generic type T if and only if T implements all of the methods of hdf5::H5Type trait and T implements all of the methods of std::fmt::Display trait.
Here the restriction is mandatory. Inside the generic function body if we ever have to use a function from a trait, Rust forces us to restrict the generic type to that trait. Otherwise T could be a type that does not implement the std::fmt then the program could not compile.

Here the table can display string, float and integer types. Note that some data are represented as an array of a single element in the NWB file.
So far the table supports 1D data. The BBP NWBs contain also 2D data. We also need to handle the n-dimensional case. It shouldn't be so difficult I think.
and these types need to be handled as well :))
                                hdf5::types::TypeDescriptor::Unsigned(_) => todo!(),
                                hdf5::types::TypeDescriptor::Boolean => todo!(),
                                hdf5::types::TypeDescriptor::Enum(_) => todo!(),
                                hdf5::types::TypeDescriptor::Compound(_) => todo!(),
                                hdf5::types::TypeDescriptor::FixedArray(_, _) => todo!(),
                                hdf5::types::TypeDescriptor::FixedAscii(_) => todo!(),
                                hdf5::types::TypeDescriptor::FixedUnicode(_) => todo!(),
                                hdf5::types::TypeDescriptor::VarLenArray(_) => todo!(),
                                hdf5::types::TypeDescriptor::VarLenAscii => todo!(),

That's super nice @anilbey !!!
I pushed a minor fix to keep the scalar values displayed (they were just displayed in one frame and then they were disappearing) and I added a close button to hide the scalar values once they are displayed.

Thanks @adrien-berchet, now we can display every data on our example NWB. :star_struck:
In some NWB files the scalar unicode string can be very long to be displayed. It may not fit the frame. Does it make sense to add a slider (that slides left-to-right) in that case? Like in here: https://github.com/emilk/egui/blob/master/crates/egui_demo_lib/src/demo/table_demo.rs#L89

You guys are great, this is amazing progress.
I vote yes for the sliders 😄

I am not sure this kind of slider will make it. Wouldn't it be easier to just open a new Window as we do for other data? But in this one we would just write one String, so the user could move it, resize it, and so on.

Good idea, a text box window will be more flexible.

Uhhh nice, looks good. Sure, merge it.
I remember there was some plan to have other plot functionalities, but that can be a separate MR.

Now I think it's usable so it would be nice if we can have some testers to give their feedback.

BBP NWBs have 2D datasets, that represents the 2 axes for plotting the voltage or current against time. Once we support that, our scientists can use it I think.

I remember there was some plan to have other plot functionalities, but that can be a separate MR.

Yes, let's do it in another MR. The window with panels demo of EGUI can help there.

Now I think it's usable so it would be nice if we can have some testers to give their feedback.

BBP NWBs have 2D datasets, that represents the 2 axes for plotting the voltage or current against time. Once we support that, our scientists can use it I think.

Ah yeah, I forgot about this :)

Alright merging, thank you both :)


RC3 fails hello-param.cwl

I think this is caused by an unhandled newline passed directly to the echo command.
https://github.com/common-workflow-language/workflows/blob/master/workflows/hello/hello-param.cwl
java -jar rabix-backend-local/target/rabix-backend-local-1.0.0-rc3.jar cwl-workflows/workflows/hello/hello-param.cwl#main cwl-workflows/workflows/hello/params.json

...

09:37:30.461 [JobHandler-Thread-0] INFO  verbose - Running command line: echo -n -e Hello, CWL !
Hello World ! > /Users/buchanae/projects/bunny/cwl-workflows/workflows/hello/hello-param-20170223093729429/root/step0/useroutput.txt
...

09:37:32.064 [Thread-1] INFO  verbose - Failed to execute a Job
...

cat workflows/hello/hello-param-20170223093729429/root/step0/job.err.log
/bin/bash: line 1: Hello: command not found

Yeah, when I was playing with this tool yesterday, I haven't tried it with provided inputs file, so I didn't notice. Working on it.

@StarvingMarvin Thanks!
I think I ran into the same issue while running the conformance tests. I'll describe here so we can decide if it's the same fix. I was running the TES backend when I hit this issue.
Running:
https://github.com/common-workflow-language/common-workflow-language/blob/master/v1.0/v1.0/env-tool1.cwl
baseCommand: ["/bin/bash", "-c", "echo $TEST_ENV"]

gets written to command.sh as:
/bin/sh -c echo $TEST_ENV

but this isn't a well formed sh -c command. We'd need quotes around the echo $TEST_ENV part I think. I guess the CWL spec expects the runner to treat each entry in the baseCommand array as a quoted string?
Heredoc might be a good idea here, to save you the trouble of escaping symbols.

@buchanae unfortunately, it's a bit more complicated, because individual command line parts can be unquoted. It also turns out that there are several issues with the way bunny implemented quoting: it defaulted to false (no quoting), even though by the spec default is true. The way it reused escaping code between input parameters and arguments was a bit clunky, and finally, it didn't quote much, even when occasionally it did decided that it should.
Generally the way this should be handled is by not using shell, if possible and instead doing things through passing array of parameters to Runtime.exec() which voids any need for quoting. But as I said, because of the need to not quite/escape some parameters, this code needed to be fixed anyway. Current state of the affairs is that on fix/shell-escaping branch hello.cwl works, but this conformance test that used to work, now fails.

Ah, makes sense. Thanks for the explanation.
So, if I understand correctly, the spec expects the engine to determine whether to wrap the part in quotes based on the existence of some characters, such as a whitespace?

There is an option in CommandLineBinding to ask engine NOT to quote something. Otherwise it is assumed it will be quoted/escaped, or not being run through shell but invoked directly, which eliminates all shell related issues.
In a meantime, my branch actually passed the build on a build server (including conformance tests) even though it fails locally, so I made a pull request to develop.


Some Clients Load Node Version of Superagent

Some environments will load in the node.js version of superagent, rather than the client version. I believe this arises particularly in node-based build environments that are precompiling frontend assets. This specific issue was discovered because of a meteor attempt.

The node version of superagent fails on the frontend because it has a dependency chain that ends up relying on some server-specific modules (fs, for instance).
It would appear that Superagent has documented this issue, although only for a Webpack environment. I would imagine the solution will be the same for any build environment - we just need to require the client lib specifically instead of the node lib.

also, we're loading a wildly old version of superagent. I wonder if upgrading would solve the issue.

It appears an update to the most recent version of superagent would solve this issue.

Resolved in #393, released to npm as<EMAIL_ADDRESS>running<EMAIL_ADDRESS>We'll roll this into master when a handful of other updates and fixes are ready. Thanks @markoshust @josephwegner!


Simplify final stage encoding special type handling

Simplify final stage encoding special type handling using the value data type registry.
Issue #72

Codecov Report

Merging #102 (a84850e) into main (43229b9) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #102      +/-   ##
==========================================
+ Coverage   96.64%   96.67%   +0.03%
==========================================
  Files          40       40
  Lines        2114     2105       -9
==========================================
- Hits         2043     2035       -8
+ Misses         71       70       -1

Impacted Files
Coverage Δ

ical/_types.py
88.38% <100.00%> (-0.64%)
:arrow_down:

ical/types/data_types.py
100.00% <0.00%> (+1.35%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Info.plist is not included in project

It looks like the Info.plist isn't included in the project so frameworks are built without them causing trouble with Carthage integration.

Closing along with #12.


CVE-2022-39222 backchannel auth exploit in Dex

Describe the bug
Can we have a official(ish) statement about CVE-2022-39222?
Dex instances with public clients (and by extension, clients accepting tokens issued by those Dex instances) are affected by this vulnerability. The Argo Project tagged versions v2.4.13, v2.3.8, and v2.2.13 as an urgent fix.
An attacker can exploit this vulnerability by making a victim navigate to a malicious website and guiding them through the OIDC flow, stealing the OAuth authorization code in the process. The authorization code then can be exchanged by the attacker for a token, gaining access to applications accepting that token.
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/advisories/GHSA-vh7g-p26c-j2cw
See CVSSv2 score of 9.3

Expected behavior
I checked https://access.redhat.com/security/cve/CVE-2022-39222 for an update
Additional context
There is a non zero chance that customers will start asking about this pretty soon. Most likely this also explains why the scheduled Argo CD 2.5.0 release is delayed.

as per https://docs.openshift.com/container-platform/4.11/cicd/gitops/gitops-release-notes.html gitops-operator >=1.7.0 fixed this by updating to Dex 1.35.1.


refactor: remove Parser class

Use CstParser and EmbeddedActionsParser instead
BREAKING CHANGE: Parser class was removed, use CstParser and EmbeddedActionsParser instead.

Part of #1016

Still need to update the benchmark grammar examples to dynamically choose the base Parser class.


TSDB metrics storage wrapper

This PR introduces wrapped Prometheus' TSDB as a solution for storing metrics on-device.
Metrics retention is controlled by https://github.com/jakub-dzon/k4e-operator/blob/d9c0ae0f8f3b4a756077a3384aba6f447a54abf1/api/v1alpha1/edgedevice_types.go#L43 .

@pkliczewski Base memory TSDB overhead is pretty low - 3MB; it will grow with the amount of data points collected.


what is meant by save_fold/ output_fold

I would like to know a suggestion for an average best practice [save_fold]/[output_fold] value.
I do not really understand what is meant by this option and how to understand the print statement
 $ sh eval.sh 0 100
 1028 0

Much Thanks

It will create a text file where all the predicted SQL queries are written in it.
In the example you provide, there should be a file named 100 in the project folder.


2to3 exporter: Fix NodePath prop remaps in .scn

The previous fix from 13d1df2e4b was applied when writing the NodePath
as text for .tscn/.tres, and thus not used for .scn. So we move the
conversion earlier, while processing all tracks.
@laverneth Could you test this one too? :)

Yep. It works !
Good job.

Thanks for testing :)

I think there ils also an issue in scale and position, I'll make a bug
tomorrow asap.
Le 1 mars 2018 23:08, "Rémi Verschelde"<EMAIL_ADDRESS>a écrit :

Thanks for testing :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/17156#issuecomment-369747897,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE1nWR5km_u-Q3YOwudCpINrXOOv_6wmks5taHFNgaJpZM4SY-xu
.

Added a new test with scaling and position as NodePath props. I haven't been able to test with the latest version of godot 2.0.1 however I had the issue yesterday.
test_export.zip


Add python3-defusedxml key

Debian https://packages.debian.org/buster/python3-defusedxml
Ubuntu https://packages.ubuntu.com/bionic/python3-defusedxml
Fedora https://apps.fedoraproject.org/packages/python3-defusedxml
Gentoo https://packages.gentoo.org/packages/dev-python/defusedxml

This is a python3 equivalent to python-defusedxml which is used by
./ros_comm/rosmaster/package.xml

lol so good I reviewed it twice.

lol so good I reviewed it twice.

Two approvals, does that mean I can merge now :wink: ?

Let me see if I can merge twice!


fix(doc): Typo in table of contents

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Getter function for 'tx' in 'BlockCypher\Api\TXSkeleton' class should have a proper return type.

Hi,
i am getting this error when i try to run my /sample/transaction-api/CreateAndSignAndSendTransactionBCTesnet.php . It was working fine before 2 days , but today it is throwing this error donot know why , can you please help me to solve this things.
Thanks

Try using v2.0.0-beta.1 and please report back. Thank you!


BLD/RLS: ensure wheels are including GDAL built with openssl

I am running into the issue that pyogrio (or geopandas with the pyogrio engine) cannot read  a file from Google Cloud Storage.
I get intermittently either a DataSourceError: CPLRSASHA256Sign() not implemented: GDAL must be built against libcrypto++ or libcrypto (openssl) or DataSourceError: HTTP response code: 403.
This is specifically with the wheels (with conda it works), and using fiona it also works. The first error message seems to indicate we don't properly built with openssl, although vcpkg does install openssl. For the Fiona wheels (and the conda libgdal), I can verify with ldd that the libgdal.so included in the wheel is linking against libcrypto (which comes from openssl). For our own wheel I can't check that the same way because we statically link the gdal dependencies into libgdal.so.
Now, based on the fact that sometimes the message indicates GDAL is not built against libcrypto, I am assuming this is indeed the case.
Looking a bit further into this, the logs of building GDAL with vcpkg on CI clearly shows that vcpkg is also installing openssl. However, the vcpkg port of GDAL has an explicit "feature" for openssl (https://github.com/microsoft/vcpkg/blob/14542c8ad9b6bcb9da755884ab823605c3300b68/ports/gdal/vcpkg.json#L227-L232), and that we are not explicitly enabling. And while GDAL's cmake default is to built against OpenSSL if it is found (docs), I am assuming that vcpkg might override this default to disable GDAL_USE_OPENSSL if you don't explicitly enable the feature through the vcpkg install of gdal (https://github.com/microsoft/vcpkg/blob/14542c8ad9b6bcb9da755884ab823605c3300b68/ports/gdal/portfile.cmake#L47C26-L47C42, not entirely sure how vcpkg_check_features works).
So testing this hypothesis here by explicitly adding "openssl" as a vcpkg feature for gdal. I should be able to test the generated wheel. Although not entirely sure if we also have a way we can test this on CI.

And to be clear, the curl that is included in our wheels that gdal uses for other cloud interaction is built with openssl (as far as I can see in the logs (example log), at least), it's only for a few other things (like google cloud authorization) that GDAL needs itself to be directly built with openssl

And based on my comment at https://github.com/geopandas/pyogrio/pull/161#issuecomment-1279939460, we did correctly build with libcrypto in the past, but I assume because of how vcpkg refactored the gdal port to allow better selection of individual features, we accidentally lost that.


chore: Use Jest

Switch to Jest for API template as agreed

It was quite interesting to get the nestjs modules under test - It might be a significant leg up to give new projects an example module with some dependendencies and tests.
We've got some examples in TCIA, or it would be awesome if you've got a better way :)

It was quite interesting to get the nestjs modules under test - It might be a significant leg up to give new projects an example module with some mocked out dependendencies and tests.
The jest.Mocked type and jest.mock() in particular are worth including (That said, I think we're supposed to use the mocks directory instead of jest.mock(), but I've never personally seen a test-suite get so big that I felt that was lacking).
We've got some examples in TCIA, or it would be awesome if you've got a better way :)

Thanks Jules, I've put a simple mock in there based partly on your work, but I'd love to look into this more deeply and do it the most elegant way. What do you think of what I've implemented here?

It was quite interesting to get the nestjs modules under test - It might be a significant leg up to give new projects an example module with some mocked out dependendencies and tests.
The jest.Mocked type and jest.mock() in particular are worth including (That said, I think we're supposed to use the mocks directory instead of jest.mock(), but I've never personally seen a test-suite get so big that I felt that was lacking).
We've got some examples in TCIA, or it would be awesome if you've got a better way :)

What do you think of what I've implemented here?

It looks good to me!
I'd love to go that next step to using mockResolvedValueOnce and/or mockReturnedValueOnce in the templates because that seems like the 80% spot in terms of being able to write the tests you want to write, but in something like it seems like too much can be worse than not enough 🤷
I'm quietly hoping that you'll come up with some nicer patterns for me to steal as the you the new project develops :)


Why is there a "GroupingOperation"?

My question is about a specific function defined here!
It seems to me, that this function could easily be replaced by torch.gather in combination with some view manipulation.
So I was wondering if it has some optimization done, that goes beyond torch.gather. I am trying to learn how to better optimize my networks.
I propose and tested it on a small example, that the following line would do the same as the aforementioned GroupingOperation:
out = grouping_operation(features, idx)
out = torch.gather(features[..., None].expand(-1, -1, -1, idx.size(2)), 2, idx.to(torch.long)[:, None].expand(-1, features.size(1), -1, -1))

Note, that PyTorch documentation specifies, that torch.expand just changes the view by modifying the stride parameter and not allocating new memory.
Any insights on this design decision would be greatly appreciated :)

Yes, you are right - This operation can be replaced with torch.gather or just simple indexing.
It is still here since this is a legacy code and also sometimes it runs faster than the default indexing of pytorch.

Ok, thanks. But that means nowadays there is no need for this grouping, as torch.gather should perform similarly fast.


Search for workloads in predefined, absolute folder list given in environment

E.g. add LATTE_WORKLOAD_PATH to point to paths with workload files.
This would allow to use latte from any working directory.

Closed by #45


[BUG] Hot reload & Docker optimization

Description
Currently we have our "start our frontend" with docker feature which can be done using
npm run docker-frontend

But there's a problem. It takes alot of time to get it started (i'm assuming maybe because of improper caching) and also if we would change up something in our file, the changes won't be reflected in the browser when we are running the frontend with docker. Here's what that needs to be done.

Optimize the overall docker part
Make sure the changes are always synced.
Write a small summary of how the docker stuff works so that in future we can enhance it if needed.

Screenshots
No response
Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (blank for no).

Hey, I think docker volume mounting can help reduce reloading time for every change in code.
But as far as build speed is concerned, I think caching methods would help us out. I'm currently looking into it.
I would love to work on this issue but takes a little bit of time than what you would expect. But as this issue is open for almost a fortnight, taking time to solve this issue would do any bad.

Can you please elaborate on 'takes alot of time to get it started'? I mean does it take much time for first start or for everytime the container is started?


Allow confirming the request on password change requests

We should allow Confirm Requester on password change requests. We want to confirm that the request came from the person whose email this is.
Imported from trac ticket #83,  created by ahelsing on 02-10-2014 at 08:26, last modified: 04-02-2014 at 15:22

This is OBE with PR #115


Replace stream_params with sub (built on

This is done on top of #15393 and is still WIP.
Testing Plan:
GIFs or Screenshots:

Posted a few comments on code quality.  But I'm glad you're working on this.

This is a step forward, merged, thanks @YashRE42!
It's amazing how many follow-up cleanups one can end up needing for just one widget that was originally cesspool of messy code ignored for years and then got rewritten :).

I've manually closed issue #15319. (forgot to add the line to the commit.)


Home and Events: Change Upcoming Meetings Buttons

On the Home page, change the text of the button under the list of upcoming meetings to read, "View Upcoming and Past Meetings."

On the Events page, add a button below the list of Upcoming Meetings -- "Show All Upcoming Meetings" -- to expand the list, similar to the button below Past Meetings.

This is done...to be clear, the logic for the Upcoming Meetings works as follows:
It will show "three days" in advance - so, meetings on 07/19/2017, 07/20/2017, and 07/27/2017 show now. After July 19,  meetings on 07/20/2017, and 07/27/2017, and 09/20/2017 will show. And so on...


Make Get-SqlDatabase AzureAD access token aware enhancement

Having Get-SqlDatabase support the -AccessToken argument seems a very useful thing to do, particularly until all the cmdlets can be updated to support -AccessToken (most if not of them support -InputObject, so that once the object is acquired using Get-SqlDatabase they would benefit from this).

This is going to be fixed in v22 GA, which I expect to roll out in the next few days (or hours).


Update instructions for continuous delivery with Netlify

This adds instructions needed when configuring Netlify for continuous delivery of a GitHub repository.
This is what the form currently looks like:

Thanks!


Reorder boot order indexes on disk or NIC deletion

These changes are required to support the reordering of boot order indexes when disks or NICs are deleted.
Depends on: https://github.com/kubevirt/web-ui-components/pull/199

kubevirt/web-ui-components#199 is merged


no tf output for base_scan

Ubuntu 16.04, gazbeo 8.1, ros kinetic
There are only two tfs output (base_footprint and odom)
How can I check the other frames like base_scan?
Otherwise, I cannot see the laser scan output in rviz correctly.

Sorry just find the solution. It is a little different to turtlebot 2.
I need to run the bringup separately.


couldn't find it in the cached files and it looks like openai/clip-vit-large-patch14-336 is not the path to a directory containing a file named config.json.

couldn't find it in the cached files and it looks like openai/clip-vit-large-patch14-336 is not the path to a directory containing a file named config.json.请问一下，我是要下载这个openai/clip-vit-large-patch14-336模型配套使用吗？要是下载的话我要放在哪里，改哪里的代码？

It seems your network fails to connect to huggingface.
You can manually download openai/clip-vit-large-patch14-336, then change the path in the function build_vision_tower to your local path as follows:
def build_vision_tower():
    # vision_tower = 'openai/clip-vit-large-patch14-336'
    vision_tower = your_local_path
    return CLIPVisionTower(vision_tower)

You can find the file define the function build_vision_tower in the error traceback.

我更改了对应文件的函数，但是执行后就会恢复成原来的样子


Error in IE 11 on 1.4.2

Seeing the following error in IE 11 on 1.4.2:

That's on Ember 2.17.0 with cli 2.17.1. It prevents the app from booting.
Downgrading simple auth to 1.4.0 fixes it.

I'm labeling this good first issue as the first step is to track this down to a concrete line (probably best by using the dummy app) which doesn't require much familiarity with the codebase.

Seems to be fixed in 1.5.1


'az monitor metrics alert create' does not support namespaces containing dashes

Related command
az monitor metrics alert create
Describe the bug
When trying to create a new metric alert where the namespace contains a dash (e.g., some-namespace), the command fails with the message: "Couldn't find a metric named some-namespace.Sample Alert. Make sure the name is correct." even though the metric exists. It appears as though the namespace is not being parsed properly from the metric name and the command is attempting to find a metric named "some-namespace.Sample Alert" and not a metric named "Sample Alert" in the namespace "some-namespace"
To Reproduce
Attempt to create an alert for a custom metric in a namespace that contains a dash.
Expected behavior
I would expect the alert to be created successfully.
Environment summary
macOS Big Sur, az version: 1.37.0, installed via brew
Additional context
I've investigated the problem a little bit, and at first glance the issue appears to be related to the grammar used to parse the metric alert condition. If you look at where the namespace part is defined here: https://github.com/Azure/azure-cli/blob/dev/src/azure-cli/azure/cli/command_modules/monitor/grammar/metric_alert/MetricAlertCondition.g4#L11, you can see that "-" is not allowed. However, it is allowed in the definition of metric, which I believe is why the command is not recognizing the namespace in the definition.

Hi @sgerace, thanks for your feedback. The namespace format maybe out of date now. We will update its format. Before that could you provide an example with '-' contained in namespace? Thanks.

Hi @kairu-ms, in our case, we were attempting to create an alert for a custom metric located in a custom namespace. We were attempting something similar to:
az monitor metrics alert create -n alert1 -g {ResourceGroup} --scopes {VirtualMachineID}
        --condition "avg custom-namespace.Custom Metric > 90"


FileNotFoundError: [WinError 2] The system cannot find the file specified

I get a problem when hitting the stop button "FileNotFoundError: [WinError 2] The system cannot find the file specified"
This is when testing app in visual studio code (and I run visual studio code software first from my Command prompt after activating my conda env, because if I first run visual studio code even if I set the python interpreter to my conda env, it never recognize streamlit or conda).
I have all dependencies installed and I get the following error
C:\Users\user\.conda\envs\streamlit\Lib\site-packages\pydub\utils.py:170: RuntimeWarning: Couldn't find ffmpeg or avconv - defaulting to ffmpeg, but may not work   warn("Couldn't find ffmpeg or avconv - defaulting to ffmpeg, but may not work", RuntimeWarning) C:\Users\user\.conda\envs\streamlit\Lib\site-packages\pydub\utils.py:198: RuntimeWarning: Couldn't find ffprobe or avprobe - defaulting to ffprobe, but may not work   warn("Couldn't find ffprobe or avprobe - defaulting to ffprobe, but may not work", RuntimeWarning) 2024-02-22 09:48:03.486 Uncaught app exception Traceback (most recent call last):   File "C:\Users\user\.conda\envs\streamlit\Lib\site-packages\streamlit\runtime\scriptrunner\script_runner.py", line 535, in _run_script     exec(code, module.__dict__)   File "C:\Users\user\Documents\Python_projects\Streamlit_projects\Test1_Streamlit_App_v1\pages\2_🚀_page 2.py", line 8, in <module>     audio = audiorecorder("Click to record", "Click to stop recording")             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\user\.conda\envs\streamlit\Lib\site-packages\audiorecorder\__init__.py", line 27, in audiorecorder     audio_segment = AudioSegment.from_file(BytesIO(b64decode(base64_audio)))                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\user\.conda\envs\streamlit\Lib\site-packages\pydub\audio_segment.py", line 728, in from_file     info = mediainfo_json(orig_file, read_ahead_limit=read_ahead_limit)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\user\.conda\envs\streamlit\Lib\site-packages\pydub\utils.py", line 274, in mediainfo_json     res = Popen(command, stdin=stdin_parameter, stdout=PIPE, stderr=PIPE)           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "C:\Users\user\.conda\envs\streamlit\Lib\subprocess.py", line 1026, in __init__     self._execute_child(args, executable, preexec_fn, close_fds,   File "C:\Users\user\.conda\envs\streamlit\Lib\subprocess.py", line 1538, in _execute_child     hp, ht, pid, tid = _winapi.CreateProcess(executable, args,                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [WinError 2] The system cannot find the file specified

Hello,
It seems you did not install ffmpeg or it is not visible inside you environment.
From the readme:

This package uses ffmpeg, so it should be installed for this audiorecorder to work properly.
On ubuntu/debian: sudo apt update && sudo apt install ffmpeg
On mac: brew install ffmpeg

Did you install it ?

I don’t think that’s the right way to install ffmpeg.
The library is not visible to other python program I guess.
I would recommend installing it by following this guide: https://phoenixnap.com/kb/ffmpeg-windows


Twitter stream stops

The module is loading correctly, but after a while it just stops refreshing the stream until I restart MM.
Is there any possibility to reconnect, or at least reload the module instead of the whole MM?

I'm having the same issue. Did you fix it yet?


Add TrustCB scraping

They are under the NL scheme, but may have more data on something?
https://www.trustcb.com/common-criteria/nscib/nscib-scheme-procedures/

Actually, they are taking over the NL scheme:


[Feature request] Add "open-actions" property to buttons

Example:
<f7-button open-actions="#action-sheet-id">Open action sheet</f7-button>

Not sure it is a good idea and it is not really the Vue-way of doing it. It is better to handle it using state variables by setting opened prop


Use a static instance of HttpClient to limit open files during tests.

I made some changes -- I see you made some too. The following works for me. Using the latest 'v0.7.4' branch I still got the exception. Using the default JsonLdOptions() constructor invoked new HttpLoader(), which seemed to be at least a partial cause of the problem.

@kevinpeterson  Great, Thanks! The checks have failed because are not configured to work with branch to branch pull request yet.


explain tar xzvf error

When I run explain tar xzvf I get the following error.
Any idea to solve it?
explain tar xzvf
Traceback (most recent call last):
  File "/Users/shinichiokada/.local/share/bin/scrape", line 78, in <module>
    exit(main())
  File "/Users/shinichiokada/.local/share/bin/scrape", line 37, in main
    args.expression = [e.decode('utf-8') for e in args.expression]
  File "/Users/shinichiokada/.local/share/bin/scrape", line 37, in <listcomp>
    args.expression = [e.decode('utf-8') for e in args.expression]
AttributeError: 'str' object has no attribute 'decode'
(23) Failed writing body

The same error on macOS and Ubuntu.

@shinokada hi!
The line in the traceback...
    args.expression = [e.decode('utf-8') for e in args.expression]

... is attempting to convert byte strings, the default string type in python2 (RIP 2020-01) into a unicode string before reassigning to the same variable. Since python3.0 (born 2008-12), the default string type is unicode string. The solution is to remove this line (and for the author to join us in the 21st century 😜 )
❯ python

WARNING: Python 2.7 is not recommended.
This version is included in macOS for compatibility with legacy software.
...

>>> type('')
<type 'str'>
>>> type(''.decode('utf-8'))
<type 'unicode'>
>>> exit()

❯ python3
Python 3.9.10 ...

>>> type('')
<class 'str'>
>>> type(''.decode('utf-8'))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'str' object has no attribute 'decode'

Although, this seems to be an oversight. The book cites python version 3.8

python
An interpreted, interactive, object-oriented programming language. python (version 3.8.5) by The Python Software Foundation (2021). More information: https://www.python.org/.


No Basic Auth

App Version
5.11.1 (via PlayStore)
Device make and model
Motorola Moto G3
Android version
7.1.2 (LineageOS 14.1-20171109-NIGHTLY-osprey)
Steps to reproduce the bug
Visit a site with Basic Auth (try httpbin.org)
Expected behavior
A prompt opens to ask for your username and password
Actual behavior
No prompt is opened, and you get a 401 status code with the message "unauthorized"

Internal issue: https://app.asana.com/0/414730916066338/555891326561611

Hi, thanks for raising this. We have this on our internal backlog but it's never bubbled up to the top priority wise so we haven't got to implementing it yet. If users vote on this issue with 👍 we'll maybe get it prioritised sooner.

Nice to hear it's already in the backlog, looking forward to see it implemented.

Please implement.

@CDRussell is there any desire to have a community PR to resolve this issue?

Good suggestion; this probably should be flagged for community help to get it done. @subsymbolic you agree?

Great shout. It'll be a while before we can look at this, help from the community would be awesome. I've added the "help wanted" label.

Implemented in https://github.com/duckduckgo/Android/pull/460


Jasmine global doesn't recognize spyOnProperty

Jasmine 2.6 added the ability to spy on properties via the new global, spyOnProperty. But JSHint's jasmine setting doesn't recognize that as a valid global.

Thanks for the report! The fix here is pretty straightforward--we'll just need to add an entry to the jasmin object in the vars.js source file. I'm marking this as low-priority, but I would gladly accept a patch introducing the new variable. Any chance you'd like to help out, @mikedaly?

I'm your huckleberry. Happened to hit this today.

@ebullient Does that mean you are putting up a PR? I was hoping to get to this later today, but don't want to duplicate effort.

Doh - just saw that you already did. :)


Enable & fix cascade_invocations

This enables the cascade_invocations lint and fixes all warnings produced by that.
Fixes #77438.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

@Hixie test-exempt? :)
Also, how do we review a PR like this? It would be ~6k LOC changed once all issues are fixed 🤔

Note the fixes in this PR are only completed by 1/4. I am waiting on @goderbauer's input before continuing here (see https://github.com/flutter/flutter/issues/77438#issuecomment-904952242).

Looks like we dropped the ball on reviewing this.
@goderbauer Can you take a look and see if we want to enable this lint?

To be honest, the code base currently does not adhere to it one bit, so I am not sure how much sense it makes to enable it.

Does dart fix support auto-fixing this lint?
There are a lot of cases that look cleaner, but many also do look strange. Maybe we shouldn't apply this lint at this time.

@goderbauer I am not sure - the only way to find out would be running it, right?

That would be one way. There may also be a list somewhere.

I saw that you changed the comment to say that the lint does not match the repo. In that case, I will close the PR.


fix: add dynamic import

@seveibar Need your input in this. The Format is failing and I have tried few things, and it's most probably because of lockfile not updated, should we shift the npm install biome -> bun like in the workflow below?
name: Format PR

on:
  pull_request:
    types: [opened, synchronize, reopened, ready_for_review]

jobs:
  format:
    name: Format code
    runs-on: ubuntu-latest
    if: github.event.pull_request.draft == false

    steps:
    - name: Checkout code
      uses: actions/checkout@v3
      with:
        token: ${{ secrets.TSCIRCUIT_BOT_GITHUB_TOKEN }}

    - name: Setup Bun
      uses: oven-sh/setup-bun@v1
      with:
        bun-version: latest

    - name: Install dependencies
      run: bun install --frozen-lockfile

    - name: Diagnose @tanstack/virtual-core
      run: |
        bun pm ls @tanstack/virtual-core || true
        bun pm why @tanstack/virtual-core || true

    - name: Get @biomejs/biome version
      id: get-biome-version
      run: echo "BIOME_VERSION=$(bun x jq -r '.devDependencies["@biomejs/biome"]' package.json)" >> $GITHUB_OUTPUT

    - name: Install @biomejs/biome
      run: bun add -d @biomejs/biome@${{ steps.get-biome-version.outputs.BIOME_VERSION }}

    - name: Run formatter
      run: bun x @biomejs/biome format . --write

    - name: Commit changes
      uses: stefanzweifel/git-auto-commit-action@v4
      with:
        commit_message: "formatbot: Automatically format code"
        branch: ${{ github.head_ref }}
        commit_user_name: tscircuitbot
        commit_user_email<EMAIL_ADDRESS>        commit_author: tscircuitbot<EMAIL_ADDRESS>

Taking a look

Yea we can move it to bun, in the workflow i noticed you have "bun x" which i think should be "bunx"


Navbar goes to two lines around 770px width

Probably due to styling of name in header. Need to change the changeover point between 3 bar collapsible menu and full menu.

https://github.com/ssuds/ssuds.github.io/commit/a8a7a6266fa5e60e89c0aeeabac3f67932f1abef fixes this.


test: initialize echidna for fuzz testing

just simple tests for now, and instructions on how to run, once we agree on approach we can open more issues for adding more fuzz tests same way its started here
alternatives:
foundry has built in fuzz testing, and bunch of tools for better testing in general (for example cheatcodes: https://book.getfoundry.sh/forge/cheatcodes)

foundry instead of hardhat: too much effort atm to migrate
use hardhat-foundry plugin https://hardhat.org/hardhat-runner/plugins/nomicfoundation-hardhat-foundry and write fuzz tests with foundry, and slowly move towards foundry: this can be reasonable to try
keep using hardhat + echidna for fuzz tests which is used here, it is similar to point above, and echidna has bunch of features as well (including cheatcodes https://github.com/crytic/properties/blob/main/README.md#hevm-cheat-codes-support)

Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 48.09%. Comparing base (41920d0) to head (3190026).

Files
Patch %
Lines

contracts/prototypes/evm/ERC20CustodyNew.sol
0.00%
1 Missing :warning:

contracts/prototypes/evm/GatewayEVM.sol
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #208       +/-   ##
===========================================
- Coverage   59.25%   48.09%   -11.17%
===========================================
  Files          31       31
  Lines        1048     1048
  Branches      217      263       +46
===========================================
- Hits          621      504      -117
- Misses        427      544      +117

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

I think using Foundry more is a good idea. What I still like about Hardhat is the ability to import and use TypeScript tools, we're using them for everything in tutorials: balances, faucet, transaction tracking, code generation. But I think Hardhat-Foundry plugin is a good middle-ground.

I don't have enough experience with Echidna yet to make a proper statement.
Regarding hardhat vs. foundry I'd say I prefer foundry because it allows native solidity testing, fuzzing and in general better it's a better testing suite than hh is. On the other hand, I get that it can be hard to fully migrate.
I agree with the proposed hardhat-foundry usage, it's a good middle ground and the full migration can happen if everyone agrees about foundry being the best solution.
Also, I'll be studying echidna so I can have informed opinions on it.

i think tests and scripts, probably not that much effort if we only do it for v2

We could also consider create entire new repo for v2 as the env is just completely different


Atom Fork

Has anyone forked it for atom, else I'd like to give that a shot :) (would be my first theme)
Edit: I've humbly started making something that's mostly like this and I really like using it so far, will put it to a test on some code the next days:
https://github.com/JonathanMH/nothrill-dark-syntax

No one has forked it for any other editors I am aware of, go nuts!


Add Users.UpdateUserPassword() method

Description
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

Current dependencies on/for this PR:

main

PR #246

PR #247

PR #248

PR #249   👈

This comment was auto-generated by Graphite.


Fix issues reported by JET

Resolves https://github.com/QuantumSavory/QuantumClifford.jl/issues/307.

[x] The code is properly formatted and commented.
[x] Substantial new functionality is documented within the docs.
[x] All new functionality is tested.
[x] All of the automated tests on github pass.
[x] We recently started enforcing formatting checks. If formatting issues are reported in the new code you have written, please correct them.

This is good to go from my POV @Krastanov

This looks great, thank you! It will probably take me a couple of days to get around to completely reviewing it. I am curious about one particular point:
I see that in a lot of places you have changed old historic code like x.rank to much neater and idiomatic rank(x). That is great, but I am curious why did that have an effect on the amount of JET warnings. Do you have a brief explanation?

I see that in a lot of places you have changed old historic code like x.rank to much neater and idiomatic rank(x). That is great, but I am curious why did that have an effect on the amount of JET warnings. Do you have a brief explanation?

In an in-between version while fiddling around with some reports, I thought that one JET report was due to badly inferred .tab (or .rank, don't remember it exactly). My "solution" was to add a type assertion to a tab(::Dunno) return value, and update the call-sites to use this getter instead of direct field access. It turned out that the JET issue was resolved by some other change on its own, but I thought I'll just keep this improvement in the PR.

Thank you, this is very much appreciated! This should be merged soon, just waiting on a final round of tests. I submitted the final list of bounties to NumFOCUS this week, and I will try to add this one as well, but there is a chance they will have to process it in the next round.

I merged master in here because there was a bug in LinearAlgebra 1.11.1 that we were hitting. The master branch has the workaround.

Thank you, this is very much appreciated! This should be merged soon, just waiting on a final round of tests. I submitted the final list of bounties to NumFOCUS this week, and I will try to add this one as well, but there is a chance they will have to process it in the next round.

Thanks!


feat(confirm): Add Confirm component

Add the Confirm component extends the actual modal component using JQuery plugin.
Confirm  receives a callback and provides some customizable options such as: textMessage, textConfirmButton, textCancelButton, and size.

Codecov Report

Merging #224 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #224   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     21    +1
  Lines         379    410   +31
=====================================
+ Hits          379    410   +31

Impacted Files
Coverage Δ

src/js/components/confirm.js
100% <100%> (ø)

Continue to review full report at Codecov.

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


Tables from word documents are not read

https://github.com/Azure-Samples/chat-with-your-data-solution-accelerator/blob/a9997b075f4bf8b228afa79c4b2fbc552846afd4/code/backend/batch/utilities/document_loading/word_document.py#L35
We are just starting to roll out a production version of this application. A user uploaded a word doc that has all their text in tables. The batch was not picking up any text at all. I realized that the code to get the text from word documents is only loading the document.paragraphs objects from word documents which means it is skipping anything that is in a table in a word document.

@andrewwiebe Thank you for your suggestion. We will forward it to the development team for further review and consideration.


Import third-party BOMs in elucidation BOM

Instead of breaking out all the Dropwizard, Jersey, Jetty, JDBI, etc. dependencies in the elucidation BOM, we can and should just import the BOMs from those third-parties.

This was completed as part of #5


MAP API KEY for com.example.mapdemo

Hi,
I would like to know how to get debug MAP API KEY for ApiDemos  ?
Is there any common Api Key available ?

There are no debug/common API keys provided. Please visit Get Started with Google Maps Platform to get an API key of your own. You can learn how our free trial and ongoing free tier works on our Billing Account Credits page.


[FLINK-10068][docs] Add documentation for RocksDB-based timers and st…

What is the purpose of the change
This PR updates the documentation about timers:

Stopping/removing timers.
RocksDB-based timers.
Asynchronous snapshots for timers.

@twalthr @alpinegizmo thanks for the review! I addressed all comments from David and some from Timo (see my comments for those that are unchanged for now).
@twalthr please have another look if that is ok for you so that we can provide at least the initial documentation now. We can still add and improve content in another PR.

Thanks for the update @StefanRRichter. LGTM % the single comment. Feel free to merge this.

Merging.


networkmanager: match pre-meson pre-upgrade behavior more closely

Motivation for this change
I don't have a great way to share this information
as a link or something, haha, but try something
like the following to see what's changed:
$ vim -d <(nix log -f channel:nixos-unstable networkmanager) <(nix log -f channel:nixos-19.03 networkmanager)

Particularly look at the post-configure dump of options.
The version was changed as well, but even so it's unclear
how many of these changes were intentional or desirable.
Beyond the values in these commits, changes that may
be worth discussing/revisitng:

asserts and warnings -- we used to specify --disable-more-warnings
which doesn't trivially map (I don't think) but now we're end up
with "more-logging: true" instead of "more-logging: no" and
"more-asserts: 100" instead of "more-asserts: 0".
I don't know this is bad or not but let's just make sure
these are set as we'd like :).

We added a number of deps that also enable features/changes
but since they were blatant in the diff (add arg, add to buildInputs, etc)
these are presumably what we want (but confirmation would be good).
Related PRs and such:

#59916 - move to meson
f748cc85bd2539619aeb1d205120d5bee8e2520a
#60903 (submitted a few minutes ago, fixes invalid path for sed)

Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Seems reasonable to me :+1:

(no worries but I'm not likely to have time to see this through in the near future-- if someone's blocking on this please feel free to commandeer this and with my full blessing :))

followed up in #65624 which is current

Awesome, thanks for helping wrap these up! My hero! :heart:


TDI-39343 Backport dynamic schema case insensitive changes to 6.4.2 (#923)

fix(TDI-39277): add comparing ignore case by name.

fix(TDI-39277): add test, change behaviour.

fix(TDI-39277): add more tests, change logic for logging unused columns

fix(TDI-39277): create utility class for common dynamic check

fix(TDI-39277): remove unused code.

fix(TDI-39277): improve existing implementation, add tests

fix(TDI-39277): update code according to comments, extend validation

What is the current behavior? (You can also link to an open issue here)
Currently this changes are present only in 6.5.0 version.
What is the new behavior?
Add changes from 6.5.0 to 6.4.2 version.
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[x] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[x] Backport to 6.4.2

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...


battery_last_reported not refreshing.

System Health details
System Information

version
core-2024.12.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.13.0

os_name
Linux

os_version
6.6.66-haos

arch
x86_64

timezone
Europe/Bucharest

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
4994

Installed Version
2.0.1

Stage
running

Available Repositories
1555

Downloaded Repositories
11

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 14.1

update_channel
stable

supervisor_version
supervisor-2024.12.0

agent_version
1.6.0

docker_version
27.2.0

disk_total
30.8 GB

disk_used
10.4 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization
kvm

board
ova

supervisor_api
ok

version_api
ok

installed_addons
Let's Encrypt (5.2.10), Terminal & SSH (9.16.0), Mosquitto broker (6.4.1), File editor (5.8.0)

Dashboards

dashboards
6

resources
6

views
4

mode
storage

Recorder

oldest_recorder_run
December 16, 2024 at 20:53

current_recorder_run
December 20, 2024 at 15:59

estimated_db_size
725.00 MiB

database_engine
sqlite

database_version
3.45.3

Sonoff

version
3.8.1 (ffa7e22)

cloud_online
1 / 3

local_online
1 / 1

debug
failed to load:

Checklist

[X] I have added battery_notes: to my configuration.yaml and restarted.
[X] I have read the FAQ's.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
I believe that battery_last_reported  is not being updated, or not in real time or at least not consistently.
I am pressing the buttons, so the information about the device is being refreshed, and I expect to see the battery_last_reported updated with the new timestamp

As you can see in the attached table, I've made a query to [sensor.blabla_battery_plus]>battery_last_reported and all the devices in the table, have the date of the last HA restart. Except one that decided to update itself.
I've pressed all the buttons, at different times, and they were all registered by HA and did something, but this field
Is there a way to force update ? or is it an known issue ?

Reproduction steps

restart HA to get even times.
press one button
wait a minute
press another
look at the table or do a query for battery_last_reported
the times have not changed.
...

Debug logs
Not really helpful, but ..
Logs
Search logs
Home Assistant Core
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
2024-12-20 15:59:31.647 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.pfsense_obyone_interface_lan_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.lan_upload_mbps'
2024-12-20 15:59:31.647 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (states('sensor.pfsense_obyone_interface_lan_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2352, in forgiving_float_filter
    return float(value)
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 631, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2733, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2355, in forgiving_float_filter
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1909, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
2024-12-20 15:59:31.649 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_lan_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.pfsense_obyone_interface_lan_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.lan_download_mbps'
2024-12-20 15:59:31.650 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (states('sensor.pfsense_obyone_interface_wireguard_interface_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2352, in forgiving_float_filter
    return float(value)
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 631, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2733, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2355, in forgiving_float_filter
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1909, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
2024-12-20 15:59:31.651 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.pfsense_obyone_interface_wireguard_interface_inbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.wireguard_download_mbps'
2024-12-20 15:59:31.652 ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template<template=({{ (states('sensor.pfsense_obyone_interface_wireguard_interface_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=2>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2352, in forgiving_float_filter
    return float(value)
ValueError: could not convert string to float: 'unavailable'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 631, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2733, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1304, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 939, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2355, in forgiving_float_filter
    raise_no_default("float", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1909, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 748, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 633, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified
2024-12-20 15:59:31.654 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError('ValueError: Template error: float got invalid input 'unavailable' when rendering template '{{ (states('sensor.pfsense_obyone_interface_wireguard_interface_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}' but no default was specified') while processing template 'Template<template=({{ (states('sensor.pfsense_obyone_interface_wireguard_interface_outbytes_kilobytes_per_second') | float / 1000) | round(0) }}) renders=4>' for attribute '_attr_native_value' in entity 'sensor.wireguard_upload_mbps'
2024-12-20 15:59:42.327 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:00:02.678 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:00:32.994 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:01:23.361 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:02:53.644 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:04:24.121 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:05:42.009 ERROR (MainThread) [homeassistant.components.script.close] script_Close_blinds: check if relay 1 is on: Error executing script. Invalid data for call_service at pos 2: must contain at least one of entity_id, device_id, area_id, floor_id, label_id.
2024-12-20 16:05:42.009 ERROR (MainThread) [homeassistant.components.script.close] script_Close_blinds: Error executing script. Invalid data for if at pos 2: must contain at least one of entity_id, device_id, area_id, floor_id, label_id.
2024-12-20 16:05:42.010 ERROR (MainThread) [homeassistant.components.automation.press_close_blinds_button_on_somrig_new] Close blinds *: Error executing script. Invalid data for call_service at pos 1: must contain at least one of entity_id, device_id, area_id, floor_id, label_id.
2024-12-20 16:05:42.010 ERROR (MainThread) [homeassistant.components.automation.press_close_blinds_button_on_somrig_new] Error while executing automation automation.press_close_blinds_button_on_somrig_new: must contain at least one of entity_id, device_id, area_id, floor_id, label_id.
2024-12-20 16:05:54.594 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:07:24.929 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:08:55.149 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:10:25.309 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:11:55.592 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:13:26.099 WARNING (SyncWorker_1) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:14:56.394 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:16:26.685 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:17:56.849 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:19:27.124 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:20:57.575 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:22:27.638 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:23:57.741 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:25:28.025 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:26:58.391 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:28:28.552 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:29:58.904 WARNING (SyncWorker_1) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:31:29.365 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:32:59.798 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:34:29.955 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:34:30.987 ERROR (SyncWorker_2) [custom_components.pfsense.pypfsense] Unexpected get_firmware_update_info error err=TimeoutError('The read operation timed out'), type(err)=<class 'TimeoutError'>
2024-12-20 16:36:00.300 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:37:30.767 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:39:00.904 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:40:31.348 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:42:01.470 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:43:31.980 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:45:02.061 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:46:32.284 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:48:02.486 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:49:32.915 WARNING (SyncWorker_1) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:51:03.220 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:52:33.451 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:54:03.716 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:55:33.806 WARNING (SyncWorker_3) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:57:04.243 WARNING (SyncWorker_2) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 16:58:34.338 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:00:04.837 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:01:34.957 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:03:05.067 WARNING (SyncWorker_1) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:04:35.472 WARNING (SyncWorker_0) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:06:05.714 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
2024-12-20 17:07:35.906 WARNING (SyncWorker_4) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "system/info" (no_response)
 Live

Diagnostics dump
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.12.4",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.13.0",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Bucharest",
"os_name": "Linux",
"os_version": "6.6.66-haos",
"supervisor": "2024.12.0",
"host_os": "Home Assistant OS 14.1",
"docker_version": "27.2.0",
"chassis": "vm",
"run_as_root": true
},
"custom_components": {
"truenas": {
"documentation": "https://github.com/tomaae/homeassistant-truenas",
"version": "0.0.0",
"requirements": []
},
"proxmoxve": {
"documentation": "https://github.com/dougiteixeira/proxmoxve",
"version": "3.5.2",
"requirements": [
"proxmoxer==2.0.1"
]
},
"sonoff": {
"documentation": "https://github.com/AlexxIT/SonoffLAN",
"version": "3.8.1",
"requirements": [
"pycryptodome>=3.6.6"
]
},
"ingv_centro_nazionale_terremoti": {
"documentation": "https://github.com/caiosweet/Home-Assistant-custom-components-INGV",
"version": "2024.08.0",
"requirements": [
"aio_quakeml_ingv_centro_nazionale_terremoti_client==0.4"
]
},
"pfsense": {
"documentation": "https://github.com/travisghansen/hass-pfsense",
"version": "0.1.0",
"requirements": [
"mac-vendor-lookup>=0.1.11"
]
},
"hacs": {
"documentation": "https://hacs.xyz/docs/configuration/start",
"version": "2.0.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"battery_notes": {
"documentation": "https://andrew-codechimp.github.io/HA-Battery-Notes/",
"version": "2.7.3",
"requirements": []
}
},
"integration_manifest": {
"domain": "battery_notes",
"name": "Battery Notes",
"codeowners": [
"andrew-codechimp"
],
"config_flow": true,
"documentation": "https://andrew-codechimp.github.io/HA-Battery-Notes/",
"integration_type": "device",
"iot_class": "calculated",
"issue_tracker": "https://github.com/andrew-codechimp/ha-battery-notes/issues",
"version": "2.7.3",
"is_built_in": false,
"overwrites_built_in": false
},
"setup_times": {
"null": {
"setup": 0.09845265500007372
},
"01JF8M4K2KPTD6C6M018SVH0J0": {
"wait_import_platforms": -0.8596171490007691,
"config_entry_setup": 0.8630831249993207
},
"01JF8MGTWK842Q7FYA6G0GQ1GG": {
"wait_import_platforms": -0.8640467320001335,
"config_entry_setup": 0.8671321520014317
},
"01JF8MHARK2PFP39FYAZ15EXYS": {
"wait_import_platforms": -0.8668797550017189,
"config_entry_setup": 0.8703383350002696
},
"01JF8MHK510CMN1VN044D3T1A2": {
"wait_import_platforms": -0.8701156999995874,
"config_entry_setup": 0.8723421989998315
},
"01JF8MJ2N8GGDT5AB0Y2V62X6V": {
"wait_import_platforms": -0.8722216940004728,
"config_entry_setup": 0.8745969940009672
}
},
"data": {
"entry": {
"created_at": "2024-12-16T21:04:05.288215+00:00",
"data": {
"battery_low_template": null,
"battery_low_threshold": 10,
"battery_quantity": 1,
"battery_type": "AAA",
"device_id": "1d1cc54f230f72ce9d70ee5694aece78",
"device_name": "IKEA SOMRIG button",
"manufacturer": "IKEA of Sweden",
"model": "SOMRIG shortcut button",
"model_id": [
null
]
},
"discovery_keys": {},
"disabled_by": null,
"domain": "battery_notes",
"entry_id": "01JF8MJ2N8GGDT5AB0Y2V62X6V",
"minor_version": 1,
"modified_at": "2024-12-16T21:04:05.288219+00:00",
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "integration_discovery",
"title": "IKEA SOMRIG button",
"unique_id": "bn_1d1cc54f230f72ce9d70ee5694aece78",
"version": 2
},
"device": {
"manufacturer": "IKEA of Sweden",
"model": "SOMRIG shortcut button",
"model_id": null,
"hw_version": null
}
}
}

I named the column Last Seen, but the query is based on battery_last_reported

name: Last Seen
data: battery_last_reported

I was thinking, in the terms of: The current battery level was last updated when battery_last_reported
If what you way is true, and the update mechanism is based on when the device wants it to update it, what do you recommend to do in my case?

If what you are trying to do is get an immediate report of a device offline then battery last reported won't do that. Z2M itself states that battery levels can take up to 24 hours to update, which is why the example notifications in battery notes are based on days not reported.

I was trying to understand when was the battery last updated. If it is 10 days ago, the last reading is old and maybe it is already dead, but if it is a recent report, than I can take the battery level as accurate.
I just saw another problem:

After sleeping I noticed that two of my battery reports turned to NaN even though they were pressed at around the same time as the others ~22:00.
Just before taking the screenshot, one of them turned to 0% batt level, but the question remains, why the NaN reporting? and why  only on two devices?

That's exactly what the automation example for battery last reported is for, I have mine set to 5 days which although not instant spots those that died suddenly, which my plant sensors tend to do.
The nan is probably when the device flips to unknown or unavailable temporarily, a few of my sensors do that. Your template query isn't handling unknown or unavailable.

Not gonna have time during holidays, but after I want to take a look at that automation example you mentioned above.
Merry Christmas, and thank you for creating this!

Thanks and Merry Christmas to you.
I'll close this issue as I'm sure the automations will give you a better understanding of what's possible with the last_reported.

I am super sorry to re-open this, but where is the automation that you are referring to ? I am not sure where to search for it.

No problem, it's in the docs community section
https://andrew-codechimp.github.io/HA-Battery-Notes/community/#battery-not-reported
There's also a blueprint if you prefer
https://andrew-codechimp.github.io/HA-Battery-Notes/community/#battery-not-reported_1
Note the requirement to trigger the automation by a schedule, events are a bit odd if you've not used them much.
https://andrew-codechimp.github.io/HA-Battery-Notes/community/#check-battery-last-reported-daily


[Follow-up] Behavior syllables should use ndx-events

Especially given our revelation in the last meeting that we can use the paper figure to map the top 37 syllables using human-readable labels, this implies that the better representation of the neurodata object BehavioralSyllable (just a simple TimeSeries contained in a BehavioralTimeSeries named SyllableTimeSeries) is actually to have it be a LabeledEvent using the ndx-events extension
Now, I suspect it was originally modeled in the TimeSeries fashion because of compatibility with the figure reproductions (which could end up eventually in a notebook attached to the DANDI set); do you think the new representation would unduly complicate that aspect @pauladkisson?

I agree, ndx-events should make sense for this data.  The TimeSeries representation was mostly a convenience choice, but it shouldn't be too hard to convert back to a TimeSeries-style representation for the figures.


Don't use frameworkAssembly references in NuGet packages for .NET Framework

Currently the NuGet packages have '' elements in them which causes the in-box reference assembly version of the DLL to be referenced instead of the one in the NuGet package when compiling on .NET Framework.
This wasn't working when compiling with the .NET CLI, so this PR changes the NuGet packages so that the DLLs in the packages will now be used when compiling for .NET Framework.

LGTM
BTW, aren't the nuspec files "supposed" to be generated and not versioned, just like the lock files?

LGTM

@cdmihai No, generally nuspec files aren't generated automatically.  The version number is passed on the command line when creating the package and overrides what's in the .nuspec file.


Feat: adds huggingface bloom example to torchserve

What this PR does / why we need it:
Adds Huggingface bloom example to Torchserve
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevent result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Thanks @jagadeeshi2i !
/lgtm
/approve


patch fix rules

…for preprocessing; 3. add rules to handle TNM; 4. fix rules in BIO generation to make code more robust
Signed-off-by: bugface<EMAIL_ADDRESS>

@liangchh @YeechingTiger @nvbic @dparedespardo I need at least one of you to review this commit


Error in iD link creation in Old Airports challenge

It is:

http://www.openstreetmap.org/edit?editor=id

Should be corrected to something more like:

http://www.openstreetmap.org/edit?node=369154534&editor=id

@id: "node/369154534"
ele: "1209"
name: "Nixon Landing Strip"
aeroway: "aerodrome"
addr:state: "NV"
source_ref: "geonames.usgs.gov"
gnis:created: "03/01/1991"
gnis:feature_id: "848347"
gnis:county_name: "Washoe"
gnis:feature_type: "Airport"

I think this is because the feature properties have @id but the code is looking for osmid.

This will be handled in #77


MERC-97 - Fixes for ESLint

MERC-97 - Fixes for ESLint

Tons of little changes to fix ESLint errors and warnings
Added rules to ESLint

:green_heart:


Support GHC 9.4

Add support for GHC 9.4. Still not supported on GHC 9.2 because of a GHC bug: https://gitlab.haskell.org/ghc/ghc/-/issues/20836.
When merged, update Cabal metadata on Hackage

Codecov Report

Merging #45 (d7f8fb8) into main (0c0432d) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head d7f8fb8 differs from pull request most recent head 3dd6261. Consider uploading reports for the commit 3dd6261 to get more accurate results

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   83.09%   83.09%
=======================================
  Files           8        8
  Lines         343      343
  Branches        2        2
=======================================
  Hits          285      285
  Misses         58       58

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hello, the persistent-mtl.cabal still mentions that the package is not buildable with ghc 9.2. Is it the case or not?


Error while initPolymer when using with test-package

I try to test a polymer-dart-component using the test-package, but I get a strange error when using initPolymer:
  Failed to load "test/my_component_test.dart": receiver is undefined
  my_component_test.dart.browser_test.dart.js 21261:1   J.$index$asx
  my_component_test.dart.browser_test.dart.js 21858:12  <fn>
  my_component_test.dart.browser_test.dart.js 21975:42  init.<fn>.<fn>
  my_component_test.dart.browser_test.dart.js 16370:22  dart<._setUpPropertyChanged
  my_component_test.dart.browser_test.dart.js 16342:15  dart<.initPolymer.<fn>
  my_component_test.dart.browser_test.dart.js 5617:13   dart<._wrapJsFunctionForAsync.<fn>
  my_component_test.dart.browser_test.dart.js 6109:9    dart<._wrapJsFunctionForAsync_closure.call$2<
  my_component_test.dart.browser_test.dart.js 6097:16   dart<._awaitOnObject_closure.call$1<
  my_component_test.dart.browser_test.dart.js 5940:1    dart<._rootRunUnary<
  my_component_test.dart.browser_test.dart.js 8619:16   dart<._CustomZone.runUnary$2<
  my_component_test.dart.browser_test.dart.js 6909:58   dart<._Future__propagateToListeners_handleValueCallback.call$0
  my_component_test.dart.browser_test.dart.js 6816:53   dart<._Future.static._Future__propagateToListeners
//....

I did everything as stated in the tutorial.
This is the project: https://github.com/flash1293/polymer_dart_example/tree/darttest

The test files are missing in the transformers entry point configuration
transformers:
- web_components:
    entry_points:
      - web/foo.html
      - test/my_component_test.html
- reflectable:
    entry_points:
      - web/foo.dart
      - test/my_component_test.dart

Imports that reach out of top-level directories are not supported with pub and prone to cause troubles.
If you want to import code into several top-level directories (like web and test) move it into the lib folder (or a subfolder) and import it like
import 'package:polymer_dart_example/my_component.dart';

The first line in your test should look like
test("my-component should be initialized correctly", () {
  Element heading = new PolymerDom(componentUnderTest.root).querySelector('h1');
  ...
}

to work properly in Polymer 1.0 (when shady DOM is used - default)

Related SO question http://stackoverflow.com/questions/33864930

Thanks a lot for your help. I updated my code, but it still doesn't work:
Failed to load "test/my_component_test.dart": Unsupported operation: Couldn't find document._registerDartTypeUpgrader. Please make sure that packages/web_components/interop_support.html is loaded and available before calling this function.
I already added <link rel="import" href="packages/web_components/interop_support.html"> to the test.html-file, but it doesn't change anything.
I updated the repo under https://github.com/flash1293/polymer_dart_example/tree/darttest.

It worked for me. Your error message doesn't look familiar. Can you please provide the full stack-trace?
Can you please also try <script src="packages/web_components/webcomponents.min.js"></script> instead of <link rel="import" href="packages/web_components/interop_support.html"> in your my_component_test.html?
What Dart version are you using?

If I use webcomponents.min.js instead of interop_support.html, it doesn't do anything (the test is never completed).
The complete stacktrace:
Failed to load "test/my_component_test.dart": Unsupported operation: Couldn't find `document._registerDartTypeUpgrader`. Please make sure that `packages/web_components/interop_support.html` is loaded and available before calling this function.
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 2903:17   dart<.wrapException
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 22445:1   dart<.registerDartType
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 22428:9   dart<.CustomElementProxy.initialize$1<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 15451:16  dart<.loadInitializers__closure.call$0<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 15396:13  dart<._runInitQueue
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 22489:14  dart<.initWebComponents
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 16580:37  dart<.initPolymer.<fn>
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 5660:13   dart<._wrapJsFunctionForAsync.<fn>
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6152:9    dart<._wrapJsFunctionForAsync_closure.call$2<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6140:16   dart<._awaitOnObject_closure.call$1<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 5983:1    dart<._rootRunUnary<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 8662:16   dart<._CustomZone.runUnary$2<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6952:58   dart<._Future__propagateToListeners_handleValueCallback.call$0
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6859:53   dart<._Future.static._Future__propagateToListeners
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6746:9    dart<._Future._completeWithValue$1
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6938:9    dart<._Future__asyncComplete_closure0.call$0<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 5974:14   dart<._rootRun<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 8655:16   dart<._CustomZone.run$1<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 8739:16   dart<._CustomZone_bindCallback_closure0.call$0<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 7119:16   dart<._AsyncCallbackEntry.callback$0
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 5778:9    dart<._microtaskLoop
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 5784:9    dart<._microtaskLoopEntry<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 6109:9    dart<._AsyncRun__initializeScheduleImmediate_internalCallback.call$1<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 4076:16   dart<.invokeClosure_closure0.call$0
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 1881:20   dart<._IsolateContext.eval$1
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 1525:20   dart<._callInIsolate
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 3053:16   dart<.invokeClosure<
  my_component_test.bootstrap.initialize.dart.browser_test.dart.js 3072:18   dart<.convertDartClosureToJS.<fn>.<fn>

Dart VM version: 1.13.0-dev.7.12 (Fri Nov 13 15:34:05 2015) on "macos_x64"

The project works for me as well...

Firefox is the problem in my configuration - the test runs fine in chrome but crashes with the above stacktrace in firefox. Where should I file this bug?

You must include <script src="packages/web_components/webcomponents-lite.min.js"></script> before  your dart script, and before any html imports. You don't need to manually put <link rel="import" href="packages/web_components/interop_support.html"> (it will get automatically added).

fwiw if you don't include the polyfill script it causes the script in interop_support.html to have errors, which is why it was giving that warning about it not being loaded.


Fix to TransformerPool to handle the PHP 8 deprecation warning

Codecov Report
Base: 94.81% // Head: 95.09% // Increases project coverage by +0.27% :tada:

Coverage data is based on head (7709d9c) compared to base (63b8a44).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##             master      #14      +/-   ##
============================================
+ Coverage     94.81%   95.09%   +0.27%
  Complexity       93       93
============================================
  Files            13       13
  Lines           193      204      +11
============================================
+ Hits            183      194      +11
  Misses           10       10

Impacted Files
Coverage Δ

src/Transformable/Transformer/TransformerPool.php
100.00% <100.00%> (ø)

src/Transformable/TransformableSubscriber.php
98.68% <0.00%> (+0.17%)
:arrow_up:

src/Transformable/Mapping/Driver/Annotation.php
94.11% <0.00%> (+1.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update VueTagInput.vue

Deleting the last tag on backspace is very mistake prone for the user. Often a user will hit backspace a bunch of times to clear the input and may accidentally delete several of their tags. Can we add deleteOnBackspace prop to allow turning off "delete tag if key backspace at the start of input"?

Thank you for your participation.
I check that.

Version 0.0.8 deployed on NPM with your work ;)


Bad position when some ancestor is scaled

If some parent is scaled using CSS, the position of the draggable during dragging isn't the mouse position. For example with a scale of 0.5 the moving distance of the draggable is half the one of the mouse.
Code example:

    drag me

const draggable = new PlainDraggable(document.getElementById('draggable'))

Hi @ogadaki, thank you for the comment.
This may help you: https://github.com/anseki/plain-draggable/issues/13

Hi @aneski, thanks for your quick reply, I'll take a look.
For a bit of context, I saw this while combining PlainDraggable with panzzom.
And I forgot an important point from my initial message: thanks a lot for your work! I'm just starting to use it but, from what I'm reading, this tool (and others like LeaderLine) will be very useful to me.

I'm glad if  I could help you. :smile:
Could you close this issue if it is solved?


Update pick-a-date.js to fix month wrapping bug

Related to issue #22, tested on the latest version of the code 1.2.0.
If we setDate before setMonth there is still a bug when we try to select dates with 31 when the current date is a month with less than 31 days. The following javascript illustrates the problem:
// Want to select 31 May 2016, the current date is 30 April 2016 (or any date in April, doesn't matter)
testDate = new Date(2016, 3, 30); console.log(testDate); // 30 April 2016
testDate.setYear(2016); console.log(testDate); // 30 April 2016, as expected
testDate.setDate(31); console.log(testDate); // 1 May 2016, not what we wanted
testDate.setMonth(4); console.log(testDate); // still 1 May 2016
I think at the moment setting the date to 1 before changing the month would be the safest change.

Thanks! Released on npm as 1.2.1 :smile:


URLCrazy path hardcoded in domain_tools.py

The path to urlcrazy seems to be handcoded in domain_tools.py:
$ cat lib/domain_tools.py | grep cmaddy
subprocess.call("/Users/cmaddy/Lab/URLCrazy/urlcrazy")
cmd = "/Users/cmaddy/Lab/URLCrazy/urlcrazy -f csv -o '{}' {}".format(outfile, target)

Ha, you're right! I put that in for testing and it slipped my mind. Thanks for pointing it out. I'll fix it now.