Dropdown seperator

Overview of the problem
Buefy version: [0.4.2]
Vuejs version: [2.1.10]
OS/Browser: Chrome, firefox
Description
Copying drop down menu with seperator. I get a error in the console
"Error: You should wrap bDropdownOption on a bDropdown"
It doesn't render the reset of the dropdown to get this to work i have to put an ending tag.

You should wrap bDropdownOption on a bDropdown like this:

    Menu

    Logged as Rafael Beraldo

    Home

    Products

    Blog

    Settings

    Logout

Hi
I did, I copied the example on the website and that's what gives me the error.
The only way to get it to work is putting an ending tag in

From: Gz<EMAIL_ADDRESS>Sent: Tuesday, June 27, 2017 3:40:17 AM
To: rafaelpimpa/buefy
Cc: monder007; Author
Subject: Re: [rafaelpimpa/buefy] Dropdown seperator (#126)
You should wrap bDropdownOption on a bDropdown like this:

Menu

    Logged as Rafael Beraldo

    Home

    Products

    Blog

    Settings

    Logout

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rafaelpimpa/buefy/issues/126#issuecomment-311236668, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJszFVmI_2rhb3Gl6PqDcA3TwalK74UWks5sIGuRgaJpZM4OF4YN.

You mean that the self closing tag is returning error? It's the best practice tbh.

Yeah the self closing tag is causing the error.
I don't think I'm doing anything to cause this.
Do you expect the self closing tag to work or does the documentation need updating to include them as seperate opening and closing tags?

I've removed the self-closing tag from docs.


How to show milliseconds since epoch human readable?

When configuring Kubernetes and components thereof to log in json format the standard is to put a timestamp in the field ts as float signifying milliseconds since epoch. For example<PHONE_NUMBER>.7978325 for Tue Mar 19 14:35:13 2024 (UTC).
Can you make hl parse this and output a human readable time string? If yes, how?
Here is the responsible line of code: https://github.com/kubernetes/component-base/blob/9d90bf7eaa57df6d6e0dd316529274b3c5747f5f/logs/json/json.go#L71

You give an example here<PHONE_NUMBER>.7978325,  but this is actually number of seconds since unix epoch.
But the line of code you referred above puts number of milliseconds since epoch.
Do you have at least one real log line in this format as an example?

You gave an example here<PHONE_NUMBER>.7978325, but that is actually number of seconds since unix epoch. And the line of code you referenced above is number of milliseconds since epoch. Do you have at least one real log line in this format as an example?

Sorry, that was a copy-paste error on my behalf. Here is a real example from the autoscaler:
{"ts":1710923450736.8257,"caller":"eligibility/eligibility.go:104","msg":"Scale-down calculation: ignoring 2 nodes unremovable in the last 5m0s\n","v":1}
I'll try that beta.

That beta worked fine,  thank you!


Devimint should set a FM_INVITE_CODE env var

I was just writing a little script that needed the invite code and had to read it from invite-code file on-disk. Would be nice if an environment variable was exported for this.

Hi! I want to work on this issue.
I was browsing the codebase and trying to see how I could resolve this issue. I was able to find the code related to the exporting of env variables in devimint, but wasn't able to able to find where the invite-code is stored and how I can access it. Any pointers?
PS. I am a new contributor here so would appreciate any help :)

https://github.com/fedimint/fedimint/blob/479bebe32648841c203993eed925462caebd65ce/devimint/src/bin/faucet.rs#L108
https://github.com/fedimint/fedimint/blob/479bebe32648841c203993eed925462caebd65ce/fedimint-server/src/config/io.rs#L29
https://github.com/fedimint/fedimint/blob/479bebe32648841c203993eed925462caebd65ce/devimint/src/federation.rs#L124

devimint first sees the invite code within the dev-fed subprocess. The challenge is to write a global env var from within this subprocess

I don't think we need to we need to have devimint rust program write the env var. Could just user-shell.sh read the invite-code file after devimint completes and export an env var based on it.

devimint first sees the invite code within the dev-fed subprocess. The challenge is to write a global env var from within this subprocess

We don't really need to modify the running's devimint's env.
Downstream should use:
eval "$(devimint env)"

to set env variables. (I"d love to have devimint exec for it as well).

Could just user-shell.sh read the invite-code file after devimint completes and export an env var based on it.

user-shell.sh is just another thing that I'd like to get rid of. It just makes downstream consumption outside of Fedimint repo harder to coordinate.


DDL "truncate table" has some bug

it may be good that we do it in "drop+create" in one transaction.

The PR #113 is not correct and has been disabled... sorry


Spaces in model labels when using capitals

Package
filament/filament
Package Version
v2.17.44
Laravel Version
v10.13.0
Livewire Version
v2.12.3
PHP Version
PHP 8.1.19
Problem description
When setting the $modelLabel or $label in the model resource to a string with multiple capital letters, the outputted string used in  and the breadcrumbs has additional spaces.
Expected behavior
The output should not have any spaces that were not specified in the $modelLabel or $label string.
Steps to reproduce
In a model resource (e.g. UserResource) specify the $modelLabel as follows:
protected static ?string $modelLabel = "ZZP'er";
When viewing the overview page, on several places there are spaces inserted, for example the title:
<title>Z Z P'ers -  MySiteName</title>
And the page title:
<h1 class="filament-header-heading text-2xl font-bold tracking-tight">
    Z Z P'ers
</h1>

Reproduction repository
https://github.com/arne-s/filamentphp-demo-mini
Relevant log output
No response

Unfortunately this is just the behaviour of Laravel's string helper for generating titles. Everything is customisable though, the docs explain how to override things like the page title or heading, or navigation item

We use Str::headline(), as Str::title() destroys the casing

Ok, thanks for looking into it, you may close this issue. I'll figure out how to use a different method. 👍


Template converter, don't skip .yaml extension.

I started running into issues when trying out the templating feature of Drone. Most of our dronefiles are using the .yaml extensions rather than the shorter .yml extension. The template converter ignores for any Dronefile that isn't using the shorter .yml extension.
This pull-request will allow the template converter to accept .yaml extensions as-well.
I believe this pull-request would also fix the issue described here: https://github.com/harness/drone/issues/3237

 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.

 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.

This would be great, because the yaml creator UI marks the extension as .yaml - https://github.com/drone/drone-ui/blob/131c5894f2ed1419ab6616ec7c3c4e5178be1a58/src/pages/settings/templates/templates.jsx#L23

Hey @staffanselander
In order to merge this, you need to accept the CLA agreement.
thanks for the submission and I'll get this merged as soon as you've signed.
Cheers,
Eoin


Add type: module to package.json

Can't deploy to Netlify because package throws an error of not having type: module in package.json:
Dec 29, 11:07:56 AM: 6be0f3aa ERROR  (node:8) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
Dec 29, 11:07:56 AM: 6be0f3aa ERROR  Unhandled Promise Rejection 	{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"SyntaxError: Cannot use import statement outside a module","reason":{"errorType":"SyntaxError","errorMessage":"Cannot use import statement outside a module","stack":["/var/task/node_modules/svelte-carousel/src/main.js:1","import Carousel from './components/Carousel/Carousel.svelte'","^^^^^^","","SyntaxError: Cannot use import statement outside a module","    at Object.compileFunction (node:vm:352:18)","    at wrapSafe (node:internal/modules/cjs/loader:1033:15)","    at Module._compile (node:internal/modules/cjs/loader:1069:27)","    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)","    at Module.load (node:internal/modules/cjs/loader:981:32)","    at Function.Module._load (node:internal/modules/cjs/loader:822:12)","    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:163:29)","    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)","    at async Promise.all (index 0)","    at async ESMLoader.import (node:internal/modules/esm/loader:385:24)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: SyntaxError: Cannot use import statement outside a module","    at process.<anonymous> (file:///var/runtime/index.mjs:1194:17)","    at process.emit (node:events:527:28)","    at emit (node:internal/process/promises:140:20)","    at processPromiseRejections (node:internal/process/promises:274:27)","    at processTicksAndRejections (node:internal/process/task_queues:97:32)"]}
Dec 29, 11:07:56 AM: Unknown application error occurred
Runtime.Unknown
Dec 29, 11:07:56 AM: 6be0f3aa Duration: 634.54 ms	Memory Usage: 58 MB

Can we add a version bump as well?

Would love to see this one merged - it breaks compatibility with Vercel as well as Netlify it seems. Thank you for making this wonderful library!

Ok, thank you guys
Could you please explain, why type module is important here?
Does it work well with csr ?

Could you please explain, why type module is important here?

Without type=module, importing the component fails currently.

This breaks the build process when using Vite. Hopefully the maintainer sees this!

Bumping beause today I discovered that when running vite build the process fails due to the beforementioned reasons. @vadimkorr could you merge this PR please? @MrTact Do you know of a workaround until this is merged?

Merged
<EMAIL_ADDRESS>

For anyone else following along, I have dug much deeper on this in an attempt to get this library to deploy to any of the main simple deployment platforms for svelte/sveltekit apps (netlify, vercel, etc), and I think the issue runs much deeper unfortunately. I was unable to get it successfully deployed even after sinking many, many hours into it. I went as far as forking the library and making dramatic changes to the way that it is built and packaged (primarily using svelte-package, which I think should be the recommended path for a library like this), which helped quite a lot, but didn't resolve the issues entirely.
Ultimately, where I got it to, it was able to deploy and build successfully without breaking, which is much further than it gets trying to deploy straight from the published official version, but there was a persistent issue with css not being output correctly that caused it to be nonfunctional when deployed to Vercel, and Netlify just immediately shit the bed with a confusing error that didn't really make any sense. Ultimately, I ended up switching to using a different carousel library as I didn't really have any more hours to spare grappling with this.
I just want to mention that I am really thankful to @vadimkorr for building such a wonderful library, I was very sad to be put in a position to need to switch to something else, and I hope that others have better luck than I did at getting this into production!

Has anyone made progress with this?
Should this issue be re-opened?
When I import the Carousel component it breaks deploys on Vercel.  Works locally though.

AFAIK there has not been made progress because it would require to completely rewriting this (pretty awesome) package. The reason has to do with the package being written in javascript instead of typescript. The fix in 1.0.21 is only a workaround but doesn't really address the problem.


use Module to define new auth guard

Hi @nWidart,
I'm just asking about something I did and want to ensure it was a good idea. I have used this module package to implement a modular system. Today, I implemented a new module requiring a new auth guard. In an older issue here, I saw that you define configs from the module provider, so I did it (see the code below). I'm wondering if this is the best approach and if it has any side effects. By the way, it works fine as of now.
protected function registerClientAuthGuard(): void
{
    $guards = array_merge(config('auth.guards'), [
        'client' => [
            'driver' => 'session',
            'provider' => 'clients',
        ],
    ]);
    config()->set('auth.guards', $guards);

    $providers = array_merge(config('auth.providers'), [
        'clients' => [
            'driver' => 'eloquent',
            'model' => \Modules\CRM\Models\Client::class,
        ],
    ]);
    config()->set('auth.providers', $providers);

    $passwords = array_merge(config('auth.passwords'), [
        'clients' => [
            'provider' => 'clients',
            'table' => 'password_resets',
            'expire' => 60,
        ],
    ]);
    config()->set('auth.passwords', $passwords);
}

I've explored the documentation and reviewed various suggestions but didn't find a more convenient approach than yours. Many other solutions require publishing configuration files, which isn't ideal for a modular system. I'll proceed with your method.
I've also made some refinements:
/**
* @return void
*/
private function registerUserGuard(): void
{
   $auth = include(__DIR__.'/../../config/auth.php');

   foreach($auth as $key => $value){
       config()->set("auth.{$key}", array_merge(config("auth.{$key}"), $value));
   }
}

And all your new config should reside in module/config/auth.php as follows:
<?php

return [
    'guards' => [
        'users' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
    ],
    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => Modules\SaaSModule\Models\User::class,
        ],
    ],
];

@adnane-ka Your code is more elegant 👌


Mend fix visibility filtering options for .blend imports

Godot version
1371a97acfb9263aaca7fa8642e95ba68534fa19
System information
Windows 11, Nvidia 3000
Issue description
<Akien> I'm not sure this fix is complete, the logic that parses the option seems bogus as it treats the integer as a boolean. It will now "work" because All is 0 and so it will use the else branch which does the same as All, but that code is broken.
@jtnicholl
https://github.com/godotengine/godot/issues/66753
Steps to reproduce
Need to recreate the sample.
Minimal reproduction project
None

I didn't notice that when writing the PR.
It does work correctly, there's just some redundant checks and as a result, some code paths that can't be reached. Looking further, the same issue is there for the skinning and materials checks too. The skins one is especially bad since the second check that's never true sets the wrong arguments.
I can make another PR real quick to clean this up.


Switch from legacy setup.py to pyproject.toml

With pip 22.3 you get the warning
DEPRECATION: htmlmin is being installed using the legacy 'setup.py install' method,
because it does not have a 'pyproject.toml' and the 'wheel' package is not installed.
pip 23.1 will enforce this behaviour change. A possible replacement is to enable the
'--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/855

We could install wheel with the pip upgrade in the make venv step of the Makefile, but this feels lazy. Will switch to pyproject.toml.

yes nice! I was going to suggest this.


feat: update borsh-js to v1.0.0

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] Commit messages follow the conventional commits spec
[x] If this is a code change: I have written unit tests.
[x] If this changes code in a published package: I have run pnpm changeset to create a changeset JSON document appropriate for this change.
[x] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
We have developed a new version of borsh-js which is agnostic to the Class being (de)serialized. This means that two "deep equal" objects can be (de)Serialized using the same Schema, no matter their origin or particular Class.
Test Plan
I have updated the dependency of borsh-js and changed the code as minimal as possible until all the tests passed again.
Related issues/PRs
Fixes #1167

@andy-haynes this PR is ready to be reviewed.
The most important thing to take into account is that the new version of borsh uses different SCHEMAS, and near-api-js exports both serialize and deserialize from borsh. This meant that the change in this PR is a breaking change.


[#460] optimize imporve soul-plugin-apache-dubbo test coverage

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #811 (8bfd630) into master (fd464d8) will increase coverage by 0.87%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #811      +/-   ##
============================================
+ Coverage     66.52%   67.39%   +0.87%
- Complexity     1447     1479      +32
============================================
  Files           275      275
  Lines          6321     6321
  Branches        726      726
============================================
+ Hits           4205     4260      +55
+ Misses         1727     1662      -65
- Partials        389      399      +10

Impacted Files
Coverage Δ
Complexity Δ

...in/apache/dubbo/proxy/ApacheDubboProxyService.java
39.13% <0.00%> (-17.40%)
3.00% <0.00%> (-1.00%)

...g/dromara/soul/plugin/hystrix/command/Command.java
5.00% <0.00%> (+5.00%)
2.00% <0.00%> (+2.00%)

...ra/soul/plugin/hystrix/command/HystrixCommand.java
71.42% <0.00%> (+7.14%)
6.00% <0.00%> (+1.00%)

...plugin/hystrix/command/HystrixCommandOnThread.java
78.57% <0.00%> (+7.14%)
6.00% <0.00%> (+1.00%)

...l/plugin/divide/balance/spi/RandomLoadBalance.java
78.94% <0.00%> (+10.52%)
7.00% <0.00%> (+1.00%)

...ra/soul/plugin/apache/dubbo/ApacheDubboPlugin.java
53.84% <0.00%> (+11.53%)
10.00% <0.00%> (+3.00%)

.../dromara/soul/common/utils/HttpParamConverter.java
88.23% <0.00%> (+11.76%)
8.00% <0.00%> (+2.00%)

...org/dromara/soul/plugin/hystrix/HystrixPlugin.java
74.07% <0.00%> (+14.81%)
10.00% <0.00%> (+2.00%)

...he/dubbo/handler/ApacheDubboPluginDataHandler.java
83.33% <0.00%> (+25.00%)
4.00% <0.00%> (+1.00%)

...gin/apache/dubbo/response/DubboResponsePlugin.java
46.15% <0.00%> (+30.76%)
7.00% <0.00%> (+4.00%)

... and 2 more

Continue to review full report at Codecov.

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


Citadel constantly refreshes cert

Describe the bug
Citadel constantly refreshes cert in every minute
Expected behavior
Only refresh before cert is to expire.
Steps to reproduce the bug
Deploy istio-demo.yaml
Version
istio-1.1.0-rc.0
[lita@lita istio]$ k logs istio-citadel-77669bc49d-x5lxq -n istio-system | grep default/istio.default
2019-03-01T18:15:47.635257Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:16:33.831549Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:17:20.266791Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:18:03.896473Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:18:49.463073Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:19:34.432460Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:19:53.594969Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:20:38.544993Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:21:40.110325Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:22:32.389261Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:23:20.094499Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:24:04.910843Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:24:52.266037Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:25:44.312746Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated
2019-03-01T18:26:28.967745Z	info	Refreshing secret default/istio.default, either the leaf certificate is about to expire or the root certificate is outdated

This was a silly setup issue, i accidentally had multiple citadels running on different namespaces.

Cool. Thanks for the update.


Secant Method Algorithm for Numerical Methods

Description of Change

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

I edited it a bit more and added annotations.
Have a nice day!


Particles rendering incorrectly

The particles has weird behavior when moving the camera, making the particles oscillate up and down. This is most likely due to the particles having the wrong view transform applied to them in the ParticleSystemComponent::render() function.

Solved it. The fault was not in the view matrix but in the demo file. The entity with the particles had a rotating parent, while the particle entity was not influenced by its rotation (its input set an absolute position). Therefore the particles where affected by the world transform of the entity.


Missing possibility to translate the deletion controls

I noticed, that there is a problem with the translations for the ui-delete-controls. When I set the language to de by
SirTrevor.config.language = "de";

these delete controls are already rendered. So it is way too late for reacting to the language change.

Thanks @morpheus-87 i'll modify the controls to use a function if possible.

Great, thanks @raffij!


About the parameter information storage.

It will be more friendly to save the key parameter information in the experiments (like in a txt file) in order not to forget the parameter and it is easier to check the parameter for comparison.

Thanks for the valuable suggestion. We will add this feature in the future.


ENH: have celer() call celer_path()

Currently the order is reversed, so checks on X and y are performed for every alpha.
sklearn does it the other way: when a single lambda needs to be fitted, we pretend it's a path of length 1.
The key is to be able to pass a coef_init for the first value of the path, which I wwasn't doing earlier.
I need the order to be reversed for #20

Codecov Report

Merging #38 into master will increase coverage by 1.99%.
The diff coverage is 92.3%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
+ Coverage   95.06%   97.05%   +1.99%
==========================================
  Files           4        4
  Lines         162      170       +8
  Branches       14       12       -2
==========================================
+ Hits          154      165      +11
+ Misses          4        3       -1
+ Partials        4        2       -2

Impacted Files
Coverage Δ

celer/wrapper.py
100% <100%> (+24%)
:arrow_up:

celer/tests/test_homotopy.py
96.96% <100%> (+0.41%)
:arrow_up:

celer/homotopy.py
94.11% <86.95%> (-5.89%)
:arrow_down:

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 9000712...1c44edf. Read the comment docs.


repair links

closes #96

THANKS!
although can figure out from browsing referenced issue, was hard to spot what actually was changed.  I would recommend providing a description of what actually was done in the commit messages.
I wish that me or someone tamed the linkschecker beast finally in https://github.com/bids-standard/bids-specification/pull/79  so we could avoid such bugs altogether

although can figure out from browsing referenced issue, was hard to spot what actually was changed. I would recommend providing a description of what actually was done in the commit messages.

+1, I'll be more verbose next time!


fix typo in the documentation comment.

I've signed CLA, but I haven't got response from Google yet. Maybe that system doesn't send a confirming report I guess.
I couldn't reopen #321, so I recreated same one. Please check this.

Thanks!


Resolve JSCS warnings

When I run gulp analyze, I get the following warnings

Can I resolve these errors and make a PR?

Yes.


Fix migration v111

backport from #12736 and #12738

I added skip changelog as this won't really be actual when upgrading from previous 1.12.x versions


Gas consumption for water for last two hours is incorrect

I am using this integration with an Ariston Genus One. Everything seems to be working fine except for the "gas consumption for water for last two hours" sensor. The data I get seems to off by orders of magnitude compared to what I read in the Ariston App. Pls fix when you get a chance. Thank you for your good work so far!

Hi @mihaimdinca!
Yeah I know sometimes it is incorrect, but I am not really sure how to fix this. If you have any idea please share with me.

I am not really that knowledgeable. I am just starting to understand how HA, Python and YAML work. Other entities seem to be fine even the gas consumption for water for last month. But the gas consumption for last two hours seems to be totally wrong as even the hours when the hot water was running don't always match

Could it be that what water consumption for last two hours shows in this integration is actually the electricity consumption? Just an idea...

@fustom The issue on this one is caused by an incorrect hard-coded value in const.py for ARISTON_GAS_CONSUMPTION_LAST_TWO_HOURS_TYPE:
https://github.com/fustom/ariston-remotethermo-home-assistant-v3/blob/2f8ec0315cc9cbc93f780befbdb28144ef0472ee/custom_components/ariston/const.py#L268-L278
The code assumes that the first 4 values in the consSequencesApi8 response JSON are the heating values and the next 4 values in that array are the DHW values but that's not the case for this particular boiler (Ariston Genus One). In this case the values that should be extracted are the ones corresponding to k=10 which start at 8 in the array. The fix for this issue in my case was to change this code:
    AristonSensorEntityDescription(
        key="4",
        name=f"{NAME} gas consumption for water last two hours",

to
    AristonSensorEntityDescription(
        key="8",
        name=f"{NAME} gas consumption for water last two hours",

Below is my full consSequencesApi8 API response (k=7 is for heating and k=10 is for DHW in Genus One boilers).
[{"k":7,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},{"k":7,"p":2,"v":[0.0,0.03,0.0,0.655,0.0,0.0,0.0]},{"k":7,"p":3,"v":[0.0,34.291,57.102,46.166,39.361,21.491,24.677,9.066,16.055,31.652,41.355,50.241,44.875,25.052,0.0,0.0,0.0,0.0,0.0,0.0,92.652,72.591,58.652,38.233,28.077,26.194,19.225,25.738,27.936,28.997,36.791,33.169,23.927,21.444,27.422,26.194,1.616,7.152,0.002,0.0,0.313,13.772,0.0,0.0,0.0,0.0,0.0,0.002,1.836,2.03,0.0,0.03,0.0,0.655,0.0,0.0,0.0]},{"k":7,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1271.805,1844.991,859.691]},{"k":20,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},{"k":20,"p":2,"v":[0.0,0.0,0.0,0.002,0.0,0.0,0.0]},{"k":20,"p":3,"v":[0.0,0.783,0.972,0.733,0.533,0.45,0.547,0.2,0.377,0.716,0.847,0.788,0.786,0.583,0.0,0.0,0.0,0.0,0.0,0.0,0.847,0.938,0.783,0.577,0.636,0.594,0.43,0.572,0.622,0.588,0.558,0.569,0.519,0.5,0.605,0.547,0.008,0.172,0.0,0.0,0.0,0.319,0.0,0.0,0.0,0.0,0.0,0.0,0.008,0.011,0.0,0.0,0.0,0.002,0.0,0.0,0.0]},{"k":20,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,23.155,27.513,14.911]},{"k":10,"p":1,"v":[2.144,0.0,0.0,0.0,0.0,3.177,1.741,2.055,1.608,0.0,1.427,1.708,4.277,0.0,0.0,0.0,1.777,1.105,0.6,1.619,3.219,1.419,1.511,3.847]},{"k":10,"p":2,"v":[17.033,10.536,13.086,14.916,13.602,13.272,15.997]},{"k":10,"p":3,"v":[12.855,12.136,16.627,13.269,13.447,16.944,12.827,15.33,19.294,13.102,16.472,13.902,8.386,2.044,3.952,7.694,1.797,3.638,3.652,3.672,14.438,11.675,14.136,13.155,8.766,11.855,21.183,10.677,14.766,17.663,12.83,12.475,12.544,13.838,13.094,12.677,20.005,15.397,12.691,11.805,15.741,12.866,14.866,14.677,13.663,11.677,12.861,15.647,12.966,11.483,17.033,10.536,13.086,14.916,13.602,13.272,15.997]},{"k":10,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,399.913,442.958,349.369]},{"k":21,"p":1,"v":[0.013,0.0,0.0,0.0,0.0,0.019,0.011,0.011,0.011,0.0,0.011,0.011,0.022,0.0,0.0,0.0,0.013,0.005,0.005,0.008,0.022,0.008,0.008,0.025]},{"k":21,"p":2,"v":[0.102,0.063,0.08,0.091,0.083,0.083,0.097]},{"k":21,"p":3,"v":[0.08,0.072,0.102,0.083,0.086,0.102,0.077,0.094,0.113,0.083,0.1,0.083,0.047,0.011,0.027,0.047,0.011,0.025,0.025,0.022,0.086,0.069,0.08,0.077,0.052,0.072,0.122,0.069,0.091,0.108,0.083,0.077,0.077,0.086,0.083,0.08,0.119,0.094,0.08,0.075,0.094,0.083,0.091,0.091,0.08,0.075,0.08,0.097,0.08,0.072,0.102,0.063,0.08,0.091,0.083,0.083,0.097]},{"k":21,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,2.458,2.722,2.127]},{"k":1,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},{"k":1,"p":2,"v":[0.0,0.03,0.0,0.657,0.0,0.0,0.0]},{"k":1,"p":3,"v":[0.0,35.074,58.074,46.899,39.894,21.941,25.224,9.266,16.432,32.368,42.202,51.029,45.661,25.635,0.0,0.0,0.0,0.0,0.0,0.0,93.499,73.529,59.435,38.810,28.713,26.788,19.655,26.310,28.558,29.585,37.349,33.738,24.446,21.944,28.027,26.741,1.624,7.324,0.002,0.0,0.313,14.091,0.0,0.0,0.0,0.0,0.0,0.002,1.844,2.041,0.0,0.03,0.0,0.657,0.0,0.0,0.0]},{"k":1,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1294.960,1872.504,874.602]},{"k":2,"p":1,"v":[2.157,0.0,0.0,0.0,0.0,3.196,1.752,2.066,1.619,0.0,1.438,1.719,4.299,0.0,0.0,0.0,1.790,1.110,0.605,1.627,3.241,1.427,1.519,3.872]},{"k":2,"p":2,"v":[17.135,10.599,13.166,15.007,13.685,13.355,16.094]},{"k":2,"p":3,"v":[12.935,12.208,16.729,13.352,13.533,17.046,12.904,15.424,19.407,13.185,16.572,13.985,8.433,2.055,3.979,7.741,1.808,3.663,3.677,3.694,14.524,11.744,14.216,13.232,8.818,11.927,21.305,10.746,14.857,17.771,12.913,12.552,12.621,13.924,13.177,12.757,20.124,15.491,12.771,11.880,15.835,12.949,14.957,14.768,13.743,11.752,12.941,15.744,13.046,11.555,17.135,10.599,13.166,15.007,13.685,13.355,16.094]},{"k":2,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,402.371,445.680,351.496]}]

P.S. Thank you for building this integration, it's much faster and cleaner than the other options.

Applied the change suggested by dcro and worked fine for my Genus One. The gas consumption for last two hours is broken again after latest update

@mihaimdinca I have not fixed it yet. You can change again in the
https://github.com/fustom/ariston-remotethermo-home-assistant-v3/blob/e3cdf7d7fdf1457771baa8af1e0fc4c1a928e9e6/custom_components/ariston/galevo_device.py#L235
line "4" to "8" until I find out what should be the proper fix.

@dcro
Thank you for your API response. That was very helpful.
So far I we have consSequencesApi8 response for:

Ariston Genus One

[{"k":7,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{"k":7,"p":2,"v":[0.0,0.03,0.0,0.655,0.0,0.0,0.0]},
{"k":7,"p":3,"v":[0.0,34.291,57.102,46.166,39.361,21.491,24.677,9.066,16.055,31.652,41.355,50.241,44.875,25.052,0.0,0.0,0.0,0.0,0.0,0.0,92.652,72.591,58.652,38.233,28.077,26.194,19.225,25.738,27.936,28.997,36.791,33.169,23.927,21.444,27.422,26.194,1.616,7.152,0.002,0.0,0.313,13.772,0.0,0.0,0.0,0.0,0.0,0.002,1.836,2.03,0.0,0.03,0.0,0.655,0.0,0.0,0.0]},{"k":7,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1271.805,1844.991,859.691]},
{"k":20,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{"k":20,"p":2,"v":[0.0,0.0,0.0,0.002,0.0,0.0,0.0]},
{"k":20,"p":3,"v":[0.0,0.783,0.972,0.733,0.533,0.45,0.547,0.2,0.377,0.716,0.847,0.788,0.786,0.583,0.0,0.0,0.0,0.0,0.0,0.0,0.847,0.938,0.783,0.577,0.636,0.594,0.43,0.572,0.622,0.588,0.558,0.569,0.519,0.5,0.605,0.547,0.008,0.172,0.0,0.0,0.0,0.319,0.0,0.0,0.0,0.0,0.0,0.0,0.008,0.011,0.0,0.0,0.0,0.002,0.0,0.0,0.0]},
{"k":20,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,23.155,27.513,14.911]},
{"k":10,"p":1,"v":[2.144,0.0,0.0,0.0,0.0,3.177,1.741,2.055,1.608,0.0,1.427,1.708,4.277,0.0,0.0,0.0,1.777,1.105,0.6,1.619,3.219,1.419,1.511,3.847]},
{"k":10,"p":2,"v":[17.033,10.536,13.086,14.916,13.602,13.272,15.997]},
{"k":10,"p":3,"v":[12.855,12.136,16.627,13.269,13.447,16.944,12.827,15.33,19.294,13.102,16.472,13.902,8.386,2.044,3.952,7.694,1.797,3.638,3.652,3.672,14.438,11.675,14.136,13.155,8.766,11.855,21.183,10.677,14.766,17.663,12.83,12.475,12.544,13.838,13.094,12.677,20.005,15.397,12.691,11.805,15.741,12.866,14.866,14.677,13.663,11.677,12.861,15.647,12.966,11.483,17.033,10.536,13.086,14.916,13.602,13.272,15.997]},
{"k":10,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,399.913,442.958,349.369]},
{"k":21,"p":1,"v":[0.013,0.0,0.0,0.0,0.0,0.019,0.011,0.011,0.011,0.0,0.011,0.011,0.022,0.0,0.0,0.0,0.013,0.005,0.005,0.008,0.022,0.008,0.008,0.025]},
{"k":21,"p":2,"v":[0.102,0.063,0.08,0.091,0.083,0.083,0.097]},
{"k":21,"p":3,"v":[0.08,0.072,0.102,0.083,0.086,0.102,0.077,0.094,0.113,0.083,0.1,0.083,0.047,0.011,0.027,0.047,0.011,0.025,0.025,0.022,0.086,0.069,0.08,0.077,0.052,0.072,0.122,0.069,0.091,0.108,0.083,0.077,0.077,0.086,0.083,0.08,0.119,0.094,0.08,0.075,0.094,0.083,0.091,0.091,0.08,0.075,0.08,0.097,0.08,0.072,0.102,0.063,0.08,0.091,0.083,0.083,0.097]},{"k":21,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,2.458,2.722,2.127]},
{"k":1,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{"k":1,"p":2,"v":[0.0,0.03,0.0,0.657,0.0,0.0,0.0]},
{"k":1,"p":3,"v":[0.0,35.074,58.074,46.899,39.894,21.941,25.224,9.266,16.432,32.368,42.202,51.029,45.661,25.635,0.0,0.0,0.0,0.0,0.0,0.0,93.499,73.529,59.435,38.810,28.713,26.788,19.655,26.310,28.558,29.585,37.349,33.738,24.446,21.944,28.027,26.741,1.624,7.324,0.002,0.0,0.313,14.091,0.0,0.0,0.0,0.0,0.0,0.002,1.844,2.041,0.0,0.03,0.0,0.657,0.0,0.0,0.0]},{"k":1,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,1294.960,1872.504,874.602]},
{"k":2,"p":1,"v":[2.157,0.0,0.0,0.0,0.0,3.196,1.752,2.066,1.619,0.0,1.438,1.719,4.299,0.0,0.0,0.0,1.790,1.110,0.605,1.627,3.241,1.427,1.519,3.872]},
{"k":2,"p":2,"v":[17.135,10.599,13.166,15.007,13.685,13.355,16.094]},
{"k":2,"p":3,"v":[12.935,12.208,16.729,13.352,13.533,17.046,12.904,15.424,19.407,13.185,16.572,13.985,8.433,2.055,3.979,7.741,1.808,3.663,3.677,3.694,14.524,11.744,14.216,13.232,8.818,11.927,21.305,10.746,14.857,17.771,12.913,12.552,12.621,13.924,13.177,12.757,20.124,15.491,12.771,11.880,15.835,12.949,14.957,14.768,13.743,11.752,12.941,15.744,13.046,11.555,17.135,10.599,13.166,15.007,13.685,13.355,16.094]},{"k":2,"p":4,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,402.371,445.680,351.496]}]

Ariston Alteas One 24

[{'k':1,'p':1,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{'k':1,'p':2,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0]},{'k':1,'p':3,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{'k':1,'p':4,'v':[0.0,0.0,0.0,0.0,0.0,810.122,3210.052,3249.777,2125.061,1486.497,750.313,0.044]},
{'k':2,'p':1,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{'k':2,'p':2,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0]},{'k':2,'p':3,'v':[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0]},
{'k':2,'p':4,'v':[0.0,0.0,0.0,0.0,0.0,93.266,350.761,365.308,458.711,296.905,305.33,232.472]}]

Velis EVO Wi-fi

`[{"k":2,"p":1,"v":[0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,2.05,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,964.675,0.425,2.825,0.0]},
{"k":2,"p":2,"v":[2.55,2.3,4.075,2.4,2.8,2.925,2.05]},
{"k":2,"p":3,"v":[3.65,1.7,3.625,1.85,3.175,2.65,2.15,1.725,3.325,2.4,2.6,2.2,4.925,2.075,0.0,0.0,918.775,2.975,2.45,2.55,0.0,0.0,1.825,0.0,0.0,2.8,3.175,2.875,3.025,2.175,2.95,2.55,2.3,4.075,2.4,2.8,2.925,2.05]},
{"k":2,"p":4,"v":[53.525,90.975,87.9,98.675,83.375,78.1,69.475,53.725,72.45,50.425,69.875,69.25,67.825]}]

k=1: heating
k=2: water
k=7: ?
k=10: water?
k=20: ?
k=21: ?
p=1: 122 hours
p=2: 71 day
p=3: 152 days
p=4: 12x year (I don't know)
v: first element is the oldest, last element is the newest
So to get the last 2 hours for water, we need to get k=2, p=1, v=last. At least for Ariston Alteas One 24 and Velis EVO Wi-fi. Are you sure the k=10 is the correct line for Ariston Genus One?

I did a few more tests by requesting the heating data separate from the DHW data and this is what I think all the data means for my boiler
Heating:
k=7: heating gas consumption
k=20: heating electricity consumption
k=1: heating total energy consumption (just the sum of k:7 + k:20)
DHW:
k=10: water gas consumption
k=21: water electricity consumption
k=2: water total energy consumption (just the sum of k:10 + k:21)
The updated data is below and the total electricity consumption shown in my app matches the values from these.
The sum of the values in k:21,p:2 for the last week is 0.505 which matches what the remotethermo website's web service returns as electricity consumption for the same time period in https://www.ariston-net.remotethermo.com/R2/PlantMetering/GetData/<PlanID>
// consSequencesApi8?usages=Ch&hasSlp=false

[{
    "k": 7,
    "p": 1,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 7,
    "p": 2,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 7,
    "p": 3,
    "v": [36.791, 33.169, 23.927, 21.444, 27.422, 26.194, 1.616, 7.152, 0.002, 0.0, 0.313, 13.772, 0.0, 0.0, 0.0, 0.0, 0.0, 0.002, 1.836, 2.03, 0.0, 0.03, 0.0, 0.655, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 7,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1271.805, 1844.991, 859.691, 196.363]
}, {
    "k": 20,
    "p": 1,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 20,
    "p": 2,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 20,
    "p": 3,
    "v": [0.558, 0.569, 0.519, 0.5, 0.605, 0.547, 0.008, 0.172, 0.0, 0.0, 0.0, 0.319, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.008, 0.011, 0.0, 0.0, 0.0, 0.002, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 20,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 23.155, 27.513, 14.911, 3.822]
}, {
    "k": 1,
    "p": 1,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 1,
    "p": 2,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 1,
    "p": 3,
    "v": [37.349, 33.738, 24.446, 21.944, 28.027, 26.741, 1.624, 7.324, 0.002, 0.0, 0.313, 14.091, 0.0, 0.0, 0.0, 0.0, 0.0, 0.002, 1.844, 2.041, 0.0, 0.03, 0.0, 0.657, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]
}, {
    "k": 1,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1294.960, 1872.504, 874.602, 200.185]
}]

// /consSequencesApi8?usages=Dhw&hasSlp=false

[{
    "k": 10,
    "p": 1,
    "v": [1.519, 1.752, 0.0, 1.688, 1.591, 1.608, 0.0, 0.0, 0.0, 1.841, 0.0, 0.802, 0.936, 1.88, 1.4, 1.452, 0.0, 1.725, 1.627, 0.0, 0.0, 0.0, 0.0, 2.147]
}, {
    "k": 10,
    "p": 2,
    "v": [14.566, 11.088, 11.036, 12.627, 9.416, 10.38, 11.666]
}, {
    "k": 10,
    "p": 3,
    "v": [12.83, 12.475, 12.544, 13.838, 13.094, 12.677, 20.005, 15.397, 12.691, 11.805, 15.741, 12.866, 14.866, 14.677, 13.663, 11.677, 12.861, 15.647, 12.966, 11.483, 17.033, 10.536, 13.086, 14.916, 13.602, 13.272, 15.997, 15.891, 7.533, 15.313, 9.136, 14.566, 11.088, 11.036, 12.627, 9.416, 10.38, 11.666]
}, {
    "k": 10,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 399.913, 442.958, 349.369, 420.133]
}, {
    "k": 21,
    "p": 1,
    "v": [0.011, 0.011, 0.0, 0.011, 0.008, 0.011, 0.0, 0.0, 0.0, 0.011, 0.0, 0.005, 0.005, 0.013, 0.008, 0.008, 0.0, 0.011, 0.011, 0.0, 0.0, 0.0, 0.0, 0.013]
}, {
    "k": 21,
    "p": 2,
    "v": [0.091, 0.069, 0.069, 0.08, 0.055, 0.066, 0.075]
}, {
    "k": 21,
    "p": 3,
    "v": [0.083, 0.077, 0.077, 0.086, 0.083, 0.08, 0.119, 0.094, 0.08, 0.075, 0.094, 0.083, 0.091, 0.091, 0.08, 0.075, 0.08, 0.097, 0.08, 0.072, 0.102, 0.063, 0.08, 0.091, 0.083, 0.083, 0.097, 0.102, 0.047, 0.094, 0.058, 0.091, 0.069, 0.069, 0.08, 0.055, 0.066, 0.075]
}, {
    "k": 21,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 2.458, 2.722, 2.127, 2.611]
}, {
    "k": 2,
    "p": 1,
    "v": [1.530, 1.763, 0.0, 1.699, 1.599, 1.619, 0.0, 0.0, 0.0, 1.852, 0.0, 0.807, 0.941, 1.893, 1.408, 1.460, 0.0, 1.736, 1.638, 0.0, 0.0, 0.0, 0.0, 2.160]
}, {
    "k": 2,
    "p": 2,
    "v": [14.657, 11.157, 11.105, 12.707, 9.471, 10.446, 11.741]
}, {
    "k": 2,
    "p": 3,
    "v": [12.913, 12.552, 12.621, 13.924, 13.177, 12.757, 20.124, 15.491, 12.771, 11.880, 15.835, 12.949, 14.957, 14.768, 13.743, 11.752, 12.941, 15.744, 13.046, 11.555, 17.135, 10.599, 13.166, 15.007, 13.685, 13.355, 16.094, 15.993, 7.580, 15.407, 9.194, 14.657, 11.157, 11.105, 12.707, 9.471, 10.446, 11.741]
}, {
    "k": 2,
    "p": 4,
    "v": [0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 402.371, 445.680, 351.496, 422.744]
}]

@dcro
Thanks! I would like to know is there any feature flag for k>2 or I should create a custom feature flag somehow. Can you share your device response? Do not forget to delete the sensitive information before post the comment.
// plants

[
   {
      "zones":[
         {
            "num":1,
            "name":"",
            "roomSens":true,
            "geofenceDeroga":false,
            "isHidden":false
         }
      ],
      "solar":false,
      "convBoiler":false,
      "hpmpSys":false,
      "hybrSys":false,
      "dhwProgSupported":false,
      "virtualZones":false,
      "hasVmc":false,
      "hasExtTP":false,
      "hasBoiler":true,
      "pilotSupported":false,
      "umsys":0,
      "isVmcR2":false,
      "isEvo2":false,
      "gw":"",
      "sn":"",
      "name":"",
      "loc":{
         "country":"",
         "addr":"",
         "cityName":"",
         "city":0,
         "adm1Name":"",
         "adm1":0,
         "adm2Name":"",
         "adm2":0,
         "postalCode":"",
         "lat":0,
         "lng":0,
         "radius":0.0
      },
      "sys":3,
      "utcOft":0,
      "lnk":1,
      "weatherProvider":0,
      "fwVer":"3.5.3_110.15.83",
      "tcByGuest":false,
      "consumptionsSettings":{
         "currency":1,
         "gasType":0,
         "gasEnergyUnit":1,
         "elecCost":1.0,
         "gasCost":1.0
      },
      "geofenceConfig":{
         "lat":0,
         "lng":0,
         "radius":0.0
      },
      "mqttApiVersion":5,
      "isOffline48H":false
   }
]

// features

{
   "zones":[
      {
         "num":1,
         "name":"",
         "roomSens":true,
         "geofenceDeroga":false,
         "isHidden":false
      }
   ],
   "solar":false,
   "convBoiler":false,
   "commBoiler":false,
   "hpSys":false,
   "hybridSys":false,
   "cascadeSys":false,
   "virtualZones":false,
   "hasVmc":false,
   "extendedTimeProg":false,
   "hasBoiler":true,
   "pilotSupported":false,
   "isVmcR2":false,
   "isEvo2":false,
   "dhwModeChangeable":true,
   "hvInputOff":false,
   "autoThermoReg":true,
   "hasMetering":true,
   "weatherProvider":0,
   "hasFireplace":false,
   "hasSlp":false,
   "hasEm20":false,
   "hasTwoCoolingTemp":false,
   "hpCascadeSys":false,
   "hpCascadeConfig":-1,
   "bufferTimeProgAvailable":false,
   "distinctHeatCoolSetpoints":false,
   "hasZoneNames":false,
   "hydraulicScheme":-1,
   "preHeatingSupported":false,
   "hasGahp":false,
   "hasDhwTimeProgTemperatures":2,
   "zigbeeActive":false
}

No problem, here is my plants and features data. From what I can see, there doesn't seem to be any difference in flags:
// plants
[{
    "zones": [{
        "num": 1,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": false
    }, {
        "num": 2,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": false
    }, {
        "num": 3,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": false
    }],
    "solar": false,
    "convBoiler": false,
    "hpmpSys": false,
    "hybrSys": false,
    "dhwProgSupported": false,
    "virtualZones": true,
    "hasVmc": false,
    "hasExtTP": false,
    "hasBoiler": true,
    "pilotSupported": false,
    "umsys": 0,
    "isVmcR2": false,
    "isEvo2": false,
    "gw": "",
    "sn": "",
    "name": "",
    "loc": {
        "country": "",
        "addr": "",
        "cityName": "",
        "city": 0,
        "adm1Name": "",
        "adm1": 0,
        "adm2Name": "",
        "adm2": 0,
        "postalCode": "",
        "lat": 0.0,
        "lng": 0.0,
        "radius": 0.0
    },
    "sys": 3,
    "utcOft": 0,
    "lnk": 1,
    "weatherProvider": 0,
    "fwVer": "104.15.12C",
    "tcByGuest": false,
    "consumptionsSettings": {
        "currency": 0,
        "gasType": 0,
        "gasEnergyUnit": 0,
        "elecCost": 1.0,
        "gasCost": 1.0
    },
    "geofenceConfig": {
        "lat": 0.0,
        "lng": 0.0,
        "radius": 0.0
    },
    "mqttApiVersion": 9,
    "isOffline48H": false
}]

// features
{
    "zones": [{
        "num": 1,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": false
    }, {
        "num": 2,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": true
    }, {
        "num": 3,
        "name": "",
        "roomSens": false,
        "geofenceDeroga": false,
        "isHidden": true
    }],
    "solar": false,
    "convBoiler": false,
    "commBoiler": false,
    "hpSys": false,
    "hybridSys": false,
    "cascadeSys": false,
    "virtualZones": true,
    "hasVmc": false,
    "extendedTimeProg": false,
    "hasBoiler": true,
    "pilotSupported": false,
    "isVmcR2": false,
    "isEvo2": false,
    "dhwModeChangeable": true,
    "hvInputOff": false,
    "autoThermoReg": true,
    "hasMetering": true,
    "weatherProvider": 0,
    "hasFireplace": false,
    "hasSlp": false,
    "hasEm20": false,
    "hasTwoCoolingTemp": false,
    "hpCascadeSys": false,
    "hpCascadeConfig": -1,
    "bufferTimeProgAvailable": false,
    "distinctHeatCoolSetpoints": false,
    "hasZoneNames": false,
    "hydraulicScheme": -1,
    "preHeatingSupported": false,
    "hasGahp": false,
    "hasDhwTimeProgTemperatures": 2,
    "zigbeeActive": false
}

@dcro Thanks! I added you to this project as a collaborator if you don't mind. I was created a pull request and I would be honored if you review it. It seems you understand what is going on here.


DynamicScene Serialization broken by Windows-as-Entities

Bevy version
0.10.0
What you did
use bevy::{
    prelude::*,
    scene::serde::SceneSerializer,
};
use serde::Serialize;

fn save(world: &World) {
    let registry = world.resource::<AppTypeRegistry>();
    let scene = DynamicScene::from_world(world, registry);

    let ser = SceneSerializer::new(&scene, registry);

    let mut buf = Vec::new();
    ser.serialize(&mut rmp_serde::Serializer::new(&mut buf))
        .unwrap();
}

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_startup_system(save)
        .run();
}

What went wrong
The DynamicScene fails to serialize.
called 'Result::unwrap()' on an 'Err' value: Syntax("no registration found for dynamic type with name bevy_window::cursor::CursorIcon")
Additional Information
It is only possible to reproduce this bug when there is a window open.

Thanks for fixing this issue. I'm curious if the problem is more prolific? I run into a similar issue with math:
tfarmpkg-c56c13763289bdd6.js:388 panicked at 'called Result::unwrap() on an Err value: Message("no registration found for dynamic type with name bevy_math::rect::Rect")', src/scene.rs:308:63
I'm pretty new to playing around with all the scene save/load stuff though, so maybe my expectations of what should / shouldn't work out of the box are incorrect.


Shouldn't getReactivly be getReactively?

http://dictionary.reference.com/browse/reactively

@rclai good point, will be fixed in the beta


Is there any cpp-gateway？

Is there any cpp-gateway？

Is there any cpp-gateway？

No and no plan, maybe at the moment.


aspects not work for me

Hello. I'm new in AOP and your plugin is the first try to use AspectJ.  I do all like in your guide but not see that my aspect work .
I have  TestAspectJ.aj  file  in ...\app\src\main\aspectj\com\example\aspectj :
package com.example.aspectj;

aspect TestAspectJ{

     pointcut  helloAscpectJ(): execution ( * *(..) );

     before():helloAscpectJ()
     {
        System.out.println("testAspectJ hello");
     }
}

plugin settings:
aspectj {
    binaryWeave true
    weaveTests false
    exclude "com.example.aspectj"
    weaveInfo true
    addSerialVersionUID true
    ignoreErrors true
}

In android studio "Android monitor" window I do not see any messages like "testAspectJ hello" when use my andorid app.

Hi!
First of all. You don't need all these options you're trying to use. Please, read their description carefully before enabling any of them. In your case you can remove all options.
I can't say exactly where is your problem. You may have no public methods in your java code. Otherwise declare them or modify the aspect to privileged access. The third point is to investigate through the build/ajc-details.log file, where you'll find details of AJ-conpilation process.

Thank you for advice. I remove all options in build.gradle file for aspectj. Rebuild project. And In ajc-details.log i get :

...many lines like this ...

Join point 'method-execution(void com.example.ui.fragment.TestFragment.testAspectJ())'
 in Type 'com.example.ui.fragment.TestFragment' (TestFragment.java:1424)
 advised by before advice from 'com.example.aspectj.TestAspectJ' (TestAspectJ.aj:9)

...

[warning] build config error: skipping missing, empty or
 corrupt aspectpath entry: C:\StudioProjects\SampleProject\app\src\debug\aspectj

[warning] build config error: skipping missing, empty or
 corrupt aspectpath entry: C:\StudioProjects\SampleProject\app\src\customflavor\aspectj

[warning] invalid Class-Path header in manifest
 of jar file: C:\StudioProjects\SampleProject\app\libs\Extasys.jar

C:\StudioProjects\SampleProject\app\src\main\aspectj\com\example\aspectj\TestAspectJ.aj:9 [warning] advice defined in
com.example.aspectj.TestAspectJ has not been applied [Xlint:adviceDidNotMatch]

As I see in your logs, joinpoints creates in a right way. So problem may occur within your build-variant config.

invalid Class-Path header in manifest of jar file: C:\StudioProjects\SampleProject\app\libs\Extasys.jar
This error I see first time. You may try to upload your project and share it to me, I'll take a look on it.

Thank you @Archinamon .I published my project  project on gitHub.

@Archinamon Have you some news ?

Yes. I was busy with my main work. Just looked up your proj. Everything goes fine until multidex step. After this dex output doesn't contains any aj-injects. Will investigate this problem on holidays.

Thank you so much :)

I'd made some fix within your problem. Please, try 1.3.2 version :) On my local clone of your project everything works fine.

I'll try it on Monday on a real project and
I'll give you feedback

v1.3.2 looks like work fine for me . Thank you :)


InstallGuide: update server name parameter in "Configure and deploy web applications" section

Update in copy of guide in release folder.

Instead of updating the version of the guide in the release folder, edit the guide to tell the user to use the value store in the source_hostname variable in the PortalContentPost.py script.

Made change. Just need to check in change to v.next.

Checked in change to v.next. Closing issue.


making machine identity a parameter

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2649 (88f24ec) into main (ae827b2) will decrease coverage by 4.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2649      +/-   ##
==========================================
- Coverage   29.37%   24.91%   -4.46%
==========================================
  Files         290      121     -169
  Lines       35603    12536   -23067
==========================================
- Hits        10457     3123    -7334
+ Misses      25146     9413   -15733

Impacted Files
Coverage Δ

src/agent/onefuzz-agent/src/agent.rs

src/agent/onefuzz-agent/src/commands.rs

src/agent/onefuzz-agent/src/config.rs

src/agent/onefuzz-agent/src/heartbeat.rs

src/agent/onefuzz-agent/src/main.rs

src/agent/onefuzz-agent/src/scheduler.rs

src/agent/onefuzz-agent/src/worker.rs

...ent/onefuzz-task/src/local/libfuzzer_test_input.rs

src/agent/onefuzz-task/src/local/test_input.rs

src/agent/onefuzz-task/src/managed/cmd.rs

... and 159 more

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


Container images based on almalinux for joern

Almalinux 9 and 8 images for joern. Almalinux uses RedHat UBI as the source and is enterprise friendly.
The workflow uses a schedule to publish the images with the tag nightly, master, and latest based on version tags.
After approving this PR, please visit the package settings and make all the packages public. GitHub would create packages as private by default and send a billing notice to upgrade.

publish the images with the tag nightly, master, and latest based on version tags.

Can you elaborate please? I don't quite understand, based on the proposed changes...

Why did you add Dockerfiles for alma8 and 9? Why not just 9?

maybe add a readme section (one-liner) on how to run the dockerfile?

when I build and run it locally, I get a rather strange encoding - probably not a problem but was just wondering if you know...

Why did you add Dockerfiles for alma8 and 9? Why not just 9? Almalinux 9 requires the CPU to support SSE4.2. For kvm64 VM, use the Almalinux 8 version works.

when I build and run it locally, I get a rather strange encoding - probably not a problem but was just wondering if you know...

For this one, we need to pass some xterm env variable or some such to make docker support unicode characters. I forgot the values. If you find this we can get this added to the file.

when I build and run it locally, I get a rather strange encoding - probably not a problem but was just wondering if you know...

For this one, we need to pass some xterm env variable or some such to make docker support unicode characters. I forgot the values. If you find this we can get this added to the file.

Hurray, had to install couple of glibc packages and set the env variables.
❯ docker run --rm -it -v /tmp:/tmp -v $(pwd):/app:rw -w /app -t ghcr.io/joernio/joern
Compiling /app/(console)

     ██╗ ██████╗ ███████╗██████╗ ███╗   ██╗
     ██║██╔═══██╗██╔════╝██╔══██╗████╗  ██║
     ██║██║   ██║█████╗  ██████╔╝██╔██╗ ██║
██   ██║██║   ██║██╔══╝  ██╔══██╗██║╚██╗██║
╚█████╔╝╚██████╔╝███████╗██║  ██║██║ ╚████║
 ╚════╝  ╚═════╝ ╚══════╝╚═╝  ╚═╝╚═╝  ╚═══╝
Version: 1.1.1647
Type `help` or `browse(help)` to begin

joern>

@mpollmeier Anything else needed to get this merged?

@itsacoderepo can you please use your admin rights to configure the package settings as per the PR description?

@prabhu Niko updated the settings as per the PR description - can you please check that it works?

@prabhu looks like the gh action config needs some fixes
https://github.com/joernio/joern/actions/runs/4912708026
Invalid workflow file: .github/workflows/containers.yml#L58
The workflow is not valid. .github/workflows/containers.yml (Line: 58, Col: 13): The identifier 'meta' may not be used more than once within the same scope.

@mpollmeier PR to fix the workflow issue - https://github.com/joernio/joern/pull/2669

the fix was merged, now we're running into
 ERROR: failed to solve: failed to push ghcr.io/joernio/joern-alma8:master: failed commit on ref "manifest-sha256:5ae9ee18db13afddad7616a6eb3e1c03eb28b7dea6f718f0766864382c3e3944": unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/joernio/joern-alma8:master: failed commit on ref "manifest-sha256:5ae9ee18db13afddad7616a6eb3e1c03eb28b7dea6f718f0766864382c3e3944": unexpected status: 403 Forbidden

https://github.com/joernio/joern/actions/runs/4914514555/jobs/8775893593
I manually disabled the workflow for now (on https://github.com/joernio/joern/actions/workflows/containers.yml)

@mpollmeier could you rerun the workflow? Sometimes github might fail for weird reasons.

it's green now


Half bubble show on screen end.

If we add this on recycleview and user preform long press on edge on item bubble will show partially.

Does it exhibit the same behavior when you long press on the right edge? If so, the angle it offsets probably just needs to be tweaked.

@SamThompson yes it exhibit the same behavior when you long press on the right edge but i tweaked it and its working fine for me.


Update branch to 1.2 and add release notes

Signed-off-by: Sruti Parthiban<EMAIL_ADDRESS>Is your feature request related to a problem? Please provide an existing Issue # , or describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you are proposing
Update branch to 1.2 and add release notes
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Check List

[x] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

> Task :buildRca
Starting a Gradle Daemon, 23 busy Daemons could not be reused, use --status for details
----- End of the daemon log -----
FAILURE: Build failed with an exception.
* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)


Support Provider arguments in Configuration extendsFrom method

Fixes #26732.
This does not add new lazy behavior, which would involve many complications.  This just adds porcelain in the API to make using it (the Kotlin DSL especially) easier.

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

Pull Request Feedback (Trigger) (Check)

Adding a Provider overload that resolves the provider immediately... will make the API more confusing, and possibly set a bad precedent? If I see a Provider method I automatically assume that it is lazy.

Adding a Provider overload that resolves the provider immediately... will make the API more confusing, and possibly set a bad precedent? If I see a Provider method I automatically assume that it is lazy.

Yes, this is a potential source of confusion, that we can only document.  But there are issues with a lazy implementation as well.
We are still considering which path would be least bad (until a comprehensive effort could be made to make laziness work) - which is why neither change has been merged yet.


BUG: Problem of dimension during KernelExplainer

Issue Description
tensorflow.python.framework.errors_impl.InvalidArgumentError: In[0] and In[1] has different ndims: [144,1000] vs. [1000] [Op:MatMul]
Problem of dimension in the line w = np.linalg.solve(X.T @ WX, WX.T @ y) of the solve function in shap>explainers>kernel.
I have no issue with the previous solve function in shap version : '0.41.0'.
Minimal Reproducible Example
import shap

explainer = shap.KernelExplainer(model, data, nsamples, silent=True)

explainer.shap_values(data)

Traceback
shap/explainers/_kernel.py", line 747, in solve
    w = np.linalg.solve(X.T @ WX, WX.T @ y)
tensorflow.python.framework.errors_impl.InvalidArgumentError: In[0] and In[1] has different ndims: [144,1000] vs. [1000] [Op:MatMul]

Expected Behavior
No response
Bug report checklist

[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest release of shap.
[X] I have confirmed this bug exists on the master branch of shap.
[ ] I'd be interested in making a PR to fix this bug

Installed Versions
0.44.1

This could be a regression introduced by #3271

Yes I think it is exactly that because the only difference between the 2 versions are that :
Old version which work:
tmp = np.transpose(np.transpose(etmp) * np.transpose(self.kernelWeights))
etmp_dot = np.dot(np.transpose(tmp), etmp)
try:
tmp2 = np.linalg.inv(etmp_dot)
except np.linalg.LinAlgError:
tmp2 = np.linalg.pinv(etmp_dot)
New version:
y = eyAdj2
X = etmp
WX = self.kernelWeights[:, None] * X
try:
w = np.linalg.solve(X.T @ WX, WX.T @ y)
except np.linalg.LinAlgError:

@alice-petit , just to reiterate my comment above, please could you provide a fully reproducible minimal example? We need this to be able to investigate further.

Ran into the same problem. @connortann
The cause is that when using tensorflow model, y is a tf.tensor, and WX.T @ y does not work.
Convert y to np.array would fix it. (X and WX are already np.array).
https://github.com/shap/shap/blob/f6d77f8c1f6a871f86766f3fe2ed23d09c75d1ba/shap/explainers/_kernel.py#L662-L666
A simple reproducible example:
import shap
import tensorflow as tf
from sklearn.datasets import make_classification

X, y = make_classification(100, 6)
model = tf.keras.Sequential([
        tf.keras.layers.Dense(10, input_shape=(6,), activation="relu"),
        tf.keras.layers.Dense(1, activation="sigmoid"),
    ])
model.compile(optimizer="adam", loss="binary_crossentropy")
explainer = shap.KernelExplainer(model, X)
shap_values = explainer.shap_values(X[:1])

PS: a quick workaround is to use explainer = shap.KernelExplainer(model.predict, X).

Thanks @yuanx749 , much appreciated! I can reproduce the issue, and your proposed fix looks good.


L4 module to support fail2ban

This PR provides a module to integrate fail2ban into L4 and works in the same way as https://github.com/Javex/caddy-fail2ban.
The module can be used to protect protocols on layer 4 against brute force attacks by allowing to block an IP address after too many failed login attempts. I have used it to protect a MQTT server, but it could also be used for other protocols with login mechanisms like FTP, SSH, OPC UA, SNMP, IMAP, POP3, SMTP, LDAP...
The module introduces a matcher fail2ban which can be used to check if the IP address of the sender is on a given banned list.
Example Caddyfile:
layer4 {
    :1883 {
        @notbanned {
            not {
                fail2ban banned-ips
            }
        }
        route @notbanned {
            proxy {
                proxy_protocol v1
                upstream message-broker:1883
            }
        }
    }
}

Hi! I actually like the idea of this matcher. As far as I understand, it requires https://github.com/Javex/caddy-fail2ban (a realtively new plugin I haven't conducted a deep analysis of, but it will be inside a go binary, so it's not a big deal then) and https://github.com/fail2ban/fail2ban (a completely separate non-go project). In other words, even if Caddy is built with caddy-l4 and this matcher included, the desired fail2ban functionality won't work unless one installs and configures fail2ban separately. Thus, it makes me doubt whether this matcher should be part of caddy-l4, https://github.com/Javex/caddy-fail2ban, or even be a separate solution.

Hi! I actually like the idea of this matcher. As far as I understand, it requires https://github.com/Javex/caddy-fail2ban (a realtively new plugin I haven't conducted a deep analysis of, but it will be inside a go binary, so it's not a big deal then) and https://github.com/fail2ban/fail2ban (a completely separate non-go project). In other words, even if Caddy is built with caddy-l4 and this matcher included, the desired fail2ban functionality won't work unless one installs and configures fail2ban separately. Thus, it makes me doubt whether this matcher should be part of caddy-l4, https://github.com/Javex/caddy-fail2ban, or even be a separate solution.

Hi, thank you for your review!
The name of the matcher is probably a bit misleading as it basically just monitors a specific file in the file system for banned IPs.
So you don't necessarily need to use fail2ban along with it, although that was the intention behind this module. https://github.com/Javex/caddy-fail2ban does the same for Caddy, this module provides the functionality for L4.

@trefzaxSICKAG Thanks for keeping your PR updated.
I have another topic for discussion with regards to this matcher: shall we actually name it fail2ban? What this matcher does is basically checking if a remote IP is present in the list stored in a predefined file. But once checked and matched, it's up to the user whether to ban it or serve anything. In my view, fail2ban and anything ban-related wouldn't suit this matcher. So I would propose remote_ip_list as a simple and self-explanatory alternative.
If the renaming is approved, I think the code has to be cleared to exclude any words derived from ban to avoid confusion.

Thank you for your suggestion @vnxme
I have renamed the module to remote_ip_list and removed all variables derived from ban. I hope this makes the module easier to understand.

At this point, this is just a remote_ip matcher, which already exists. Maybe the only difference is that it watches for the file update.

Thank you for your review @mholt
I have changed the identifiers containing Ip to IP and renamed the JSON struct tag. Also the tests should now be successful for Windows, there was a problem with joining file paths.


Refactoring + doc improvements + version to 7.6.0

Refactored term methods from Util to Term
Improved documentation in several places
Added textual mode to print lists as [.....] via .toString()
Upgraded JPL version to 7.6.0 (Java, C, and Prolog code)

All tests pass

Thanks for all the good work!  I don't have much opinion on JPL as I'm not familiar with conventions in the Java world.   When ready, just ask me to merge.  I'll quickly check there is nothing weird and all tests still run, merge and push.  @anionic may have more strategic opinions on this.

My pleasure Jan, this my little way of giving back after SWI has given me so much across so many years (decades now!)
It is now all done in this PR. It's mostly documentation enrichment with this that were missing, in particular for those starting to use JPL, and there is a move of some methods from Util to Term, as they were all related to building and manipulating terms.
With this final touch plus the changes before (e.g.,Rational) I moved the version to 7.6.0 as @anionic suggested.

Great.  You've done a lot of typing!   Building gives a little glitch (currently building using OpenJDK 11):
org/jpl7/Util.java:171: warning: [dep-ann] deprecated item is not annotated with @Deprecated
	public static final boolean isList(Term term) {
	                            ^
Note: org/jpl7/fli/atom_t.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 warning
[1522/2400] Building Java objects for jpltest.jar
./org/jpl7/Util.java:171: warning: [dep-ann] deprecated item is not annotated with @Deprecated
	public static final boolean isList(Term term) {
	                            ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 warning

ohhh interesting. That's why I wanted this to be checked on another system/install.
I will look into this. Thanks.

I've added an @Deprecated at the place the compiler complained about.  Didn't want to hold the release which is needed for the Debian testing cycle and think it can't do much harm.  If I messed up anyway, just start a new PR.  Enjoy the weekend!

@JanWielemaker , how do you get that output? Is it when running CMAKE? I am doing:
make -C packages/jpl clean  ; make VERBOSE=1 -j 8 `

I have seen a few minor issues like this in the code, but I am not getting warnings at compile time, so I want to hunt them all before pushing. I am using oracle JDK, but cannot be because of that I guess.

Ohh now I see your latest message. No harm,it is minor. But want to clean up all glitches like that.

Guess it is related to the JDK version?  Did show up using just default built.


fix for removing array items

Using Dexie.delByKeyPath(), which ultimately calls Dexie.setByKeyPath(), causes some problems when the path ends in an array.
Removing an item from an array using delete does not updating the array length. Instead it creates an undefined array item, leaving the length alone.
This fix identifies the object as an Array and uses Array.splice() to remove the keyPath.
See here: delete operator under Deleting Array Elements.

closing this pull request to create another one properly


[Feature]Add Niven Number Calculator

Description
A number that is divisible by the sum of its digits is called a niven number.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Proceed @Nayanika1402


Warning after install this package

Hi @kimkha,
After install this package I gave this warning message in console:
loopback-explorer deprecated The built-in CORS middleware provided by loopback-component-explorer was deprecated. See https://docs.strongloop.com/display/public/LB/Security+considerations for more details. node_modules/loopback-boot/lib/executor.js:437:5

Is it important or everything is OK?

Surprise! I will check it again... But I think it's OK.

Thanks man 😉
I'm waiting for it.

I will update document.


Crash on TTS Android settings

Hi, I cannot select the downloaded engine in the Android settings, because it crashes every time. I've already read #528, but it doesn't matter if the app is closed or still running in the background. The TTS test within the app is working fine. I just cannot use the engine with other apps.

please tell us which version you are using.


Add property muiName on all components

@gabrielgry We only add it where needed. What's your use case?

I'm working on a component that wraps a set of Switch components, as in:
<SwitchGroup>
  <Switch />
  <Switch />
</SwitchGroup>

Since the children could be either a Switch component or a FormControlLabel (with a Switch in the control prop), I was hoping to using muiName to determine the type of each child element (the isMuiElement helper seems ideal for this). However neither Switch nor FormControlLabel has muiName defined.
I suppose an alternative approach would be to could create a custom wrapper component with explicit props for either a Switch component or a FormControlLabel. Is this the approach you'd recommend?

@brentatkins I think that we should limit the usage of the muiName static component property. It has proven to be limited. For instance, as soon as you refactor your logic and hide the source component behind another one, it breaks.


7GUIs - Counter Example

This commit sets up a pnpm monorepo, and adds an example implementing counter, using solid-start.

Should the directory for the examples be called /packages? Wouldn't /apps or /examples make more sense and be more intuitive for people visiting?

Alright, I'm merging this. Any further changes can be made later.

Nice work @mosheduminer!


Update Helm chart to simplify deployment

I mentioned in osmcha/osmcha-frontend#749 and osmcha/osmcha-django#719 that some updates to the Helm chart would be necessary in order to safely deploy those changes. These are those updates.
I tested this today using minikube. Several additional modifications (not included in this PR) were necessary to make the "production" chart work on localhost:

adding a postgres database container to the app pod
setting enable_tls to false, to disable Let's Encrypt automation
overriding OAUTH_REDIRECT_URI to point to http://<IP_ADDRESS>:8000
overriding the OAuth key and secret to point to an openstreetmap.org OAuth app which is registered to http://<IP_ADDRESS>:8000 (rather than https://osmcha.org).
modifying the image names for the frontend and django containers to point to local Docker images rather than GHCR URLs (since the new images aren't yet published to GHCR).

With these modifications, I was able to verify that:

OSMCha loads as expected on http://<IP_ADDRESS>:8000 in the browser
Login works, and afterwards API requests to the backend succeed (rather than 401'ing)
The /admin dashboard loads (I didn't try logging in). This verifies that the static assets generated by Django at build time are being served by nginx correctly.
Other server-rendered pages like /about work
Changeset urls like /changesets/123456 load. The changeset is displayed on the map, however the map background tiles do not load due to a 403 error from the Mapbox API (this happens in my local dev environment too; so I expect it's okay?). The upper-left infobox with changeset metadata is also missing, but this is expected I think (the Django API returns 404 for /api/v1/changesets/157277981/ since I'm running the app with an empty database).

Keeping this as a draft while I do a bit more testing, but this should all be ready to review pretty soon. Once it's reviewed, I'll merge the other two PRs (linked above) which will cause the new container images to get published to GHCR. After that I'll update the version hashes in this PR and then it should be ready to merge.

This is now ready for review, but do not merge it yet. The other PRs linked above need to land first, and then this PR needs to be updated with the hashes of the new container images.

I believe this is now ready to merge. Deploying shortly.


Rename 'shared' folder to 'src' folder

Hi folks! I was wondering if in the next release, we should rename shared folder to src folder. Mostly because it increasingly seems to be the convention (create-react-app popularizes it), and lot of other tools seem to be trying to work out of the box with that convention.
For example, I was trying to integrate catalog as a living style guide for my project and ran into issues. And as per one of the members of the catalog project, they try to work out of the box for projects where components live in src. This is also true for others like react-styleguidist.
Has this been discussed already before? Thoughts?

I'm voting for app. Because we have source files in server, client, config too. With additional tweaks you can achieve something like this:
import config from 'config';
import Component from 'app/components/Component';

Which looks really nice

For example, I was trying to integrate catalog as a living style guide for my project and ran into issues. And as per one of the members of the catalog project, they try to work out of the box for projects where components live in src. This is also true for others like react-styleguidist.

This is an issue of catalog. You can use the tool, that does not make assumptions about the project it runs in, e.g. storybook.

@SleepWalker I'm open to app as well if that is picking up as a convention. To be clear, the matter isn't about catalog, but the fact that as tools that pick a configuration to default to.. we should embrace it as well. create-react-app is the a big way this convention is set, and I just gave the examples of couple of tools that work out of the box for CRA apps, mainly due to the file structure.

I agree that shared should be src
I also think shared/utils/ should be shared/helpers
And that shared/Html/index.js should be shared/helpers/renderHtml.js

From my shared/README.md
.
├── /app/                             # The Application
    ├── /layouts/                    # For different screen resolutions
    └── /routes/                    #
├── /helpers/                       #
├── /modules/                     #
└── /redux/                         #

The base is my typescript Fork, but should be like 99% of the work if someone wants to copy it: https://github.com/Falieson/2017-typescript-react/commit/9b49d7bdf3250288dbfe65321608966dbf3b7be7


Update using-ssh-over-the-https-port.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (eg. a "before and after video")

Thanks for opening a PR 👍 Please fill out the pull request template in the top comment in this pull request, then we'll get this up for review!

Thanks for the pull request. We are unable to accept this change at this time.


[feature] GPU has been used 99% by jadx-gui-1.4.7

Describe your idea:
How to solve the problem
GPU has been used 99% by jadx-gui-1.4.7

Does this happen reproducible? Because Jadx does not make use of GPU directly (may be the Java UI rendering makes use of it). GPU can also be used by background apps, so it may be just coincidence. What Java runtime (exact version and who provides the JDK) do you use?

Maybe related to #2030, check for suggested workarounds.


Fix bug in delete for Raptor

When no rows match for delete, rowsToDelete is not set causing a NPE.
Set it in the constructor because we already know the maximum size.
We might over allocate for cases where no rows are selected for
deletion, but this is a short lived bit vector so it should be low
impact.

Looks good


Chrome://network#state

Chrome://network#state doesn't exist. Is this just a problem with my computer? Should I do this on another browser?

happened to me too, my post got removed/resolved I guess
I don't think there's anything you can do about it, besides find a different exploit

Chrome://network#state doesn't exist. Is this just a problem with my computer? Should I do this on another browser?

You guys did chrome://network/#state. Not chrome://network#state. You added a / before  the #.


Support mixer versioning

We need to make it easy for folks to figure out what they're running. So:

We should generate a version.go file as part of the build which includes the SHA of the latest commit as a const. Perhaps a date string would be handy too.

When the mixer starts, it should pump its version info (taken from version.go) into its logs.

mixs should have a 'version' command that prints out the version info.

We could also consider adding a Version API call to the mixer which returns the version info, and then we could add a version command to mixc to report the version of a running instance.

This is similar to what manager does. We would like to use a common approach.
https://github.com/istio/manager/tree/master/cmd/version

Anything else to do here?

No. I think this is closable now.


[BUG] Broken - Azure cloud shell maven version - OpenJDK 17 conflict

To Reproduce
Clone this repo onto cloud shell: https://github.com/spring-petclinic/spring-petclinic-microservices
Run mvn clean compile
Commands you ran

mvn clean compile
Observed Behavior
Command fails to run
Include error output here

Expected behavior
The command should run
Is this specific to Cloud Shell?
Please verify if the same issue can be reproduced by running the same tool outside Cloud Shell - for example,
by installing it on your own computer. If so, it is likely to be a bug in that tool or in the Azure service it communicates with,
not in Cloud Shell. Please file the issue with the appropriate project.
Interface information
How are you accessing Cloud Shell - https://shell.azure.com, https://portal.azure.com, via Windows Terminal, or some other method?
If a browser, which Operating System and browser are you using? (ex. Edge on Windows 10)
Additional context
Add any other context about the problem here.
AB#14442671

Basically Cloudshell needs to upgrade to Maven 3.8.4 and this will be resolved.

Adding specific maven version to the shell, as the debian package mirror downloads the older version and is end of life.

Fixed - will be available in next production release - approximate ETA 1-2 weeks from now.

Hello , Any information about the fic ETA ?

@bayanlouzi : Fixed and available in production. Check again.


Exclude vgc service from being set to Manual

On my PC, I run Valorant. That software depends on the vgc service (also known as Vanguard, an anti-cheat service ). Without this service running in the background, I cannot play Valorant. After running the command to set services to Manual startup type, it put that service to manual startup. Can it be set so the routine does not mess with the vgc service? It needs to bet set to automatic so the application can run correctly.
Thanks!

Thanks for the report, I'll get this switched in the next update!

The tweaks won't touch the vgc service and not included in the toolbox.


Prevent login for people without write access github repo

Hey there,
I've been trying to setup Keystatic with a Github repo. It works great until I want new people to contribute. I understand that people need write access to use Keystatic but why allow people to login at all? Right now, people can login but get a cryptic error when they try to edit anything:

It seems like keystatic cloud handles this, if I try to login to https://keystatic.com/keystatic I get an expected error message:

Could we have something similar for the Github integration?

As a workaround, i stopped using the keystatic astro integration. Instead, I directly import the ui and api and registered them manually. Then, on the admin page I grab the keystatic github access token and check myself if they access to the repo. If not, hide the UI.
---
import { Keystatic } from '@/components/keystatic'
import { Octokit } from '@octokit/core'
import { z } from 'astro:content'

export const prerender = false

const accessToken = Astro.cookies.get('keystatic-gh-access-token')

let isNotCollaborator = false

if (accessToken) {
	const octokit = new Octokit({
		auth: accessToken.value,
	})

	try {
		const me = await octokit.request('GET /user', {
			headers: {
				'X-GitHub-Api-Version': '2022-11-28',
			},
		})

		await octokit.request(
			'GET /repos/{owner}/{repo}/collaborators/{username}',
			{
				owner: 'soulsspeedruns',
				repo: 'website',
				username: me.data.login,
				headers: {
					'X-GitHub-Api-Version': '2022-11-28',
				},
			},
		)
	} catch (e) {
		const result = z.object({ status: z.literal(404) }).safeParse(e)

		if (result.success) {
			isNotCollaborator = true
		} else {
			throw e
		}
	}
}
---

{
	isNotCollaborator ? (

			It seems like you don't have the write access. Please check this out!

	) : (
		<Keystatic client:only="react" />
	)
}

As a work around, I added some code before loading the keystatic admin using a different access token to verify that the current keystatic logged in user has access to my repo. If not, shows an error. For this, I stopped using the astro integration and just imported the UI and the API endpoints to install them manually, like we used to do before the integration.
---
import { Keystatic } from '@/components/keystatic'
import { Octokit } from '@octokit/core'
import { z } from 'astro:content'
import Layout from<EMAIL_ADDRESS>import { ExclamationTriangleIcon } from '@radix-ui/react-icons'
import { Alert, AlertDescription, AlertTitle } from '@/components/ui/alert'
import config from 'keystatic.config'

export const prerender = false

const accessToken = Astro.cookies.get('keystatic-gh-access-token')
let error: { title: string; message: string } | undefined = undefined

if (config.storage.kind === 'github' && accessToken) {
	const souls = new Octokit({
		auth: import.meta.env.SOULS_PERSONAL_ACCESS_TOKEN,
	})

	const keystatic = new Octokit({
		auth: accessToken.value,
	})

	try {
		const me = await keystatic.request('GET /user', {
			headers: {
				'X-GitHub-Api-Version': '2022-11-28',
			},
		})

		await souls.request('GET /repos/{owner}/{repo}/collaborators/{username}', {
			owner: 'soulsspeedruns',
			repo: 'website',
			username: me.data.login,
			headers: {
				'X-GitHub-Api-Version': '2022-11-28',
			},
		})
	} catch (e) {
		const result = z.object({ status: z.literal(404) }).safeParse(e)

		if (result.success) {
			error = {
				title: 'Forbidden',
				message: `The user is not a verified contributor.`,
			}

			Astro.response.status = 403
		} else {
			console.log(e)
			throw e
		}
	}
}
---

{
	error ? (
		<Layout title="Unauthorized">

					<Alert
						variant="destructive"
						className="mb-6"
					>
						<ExclamationTriangleIcon className="h-4 w-4" />
						<AlertTitle>{error.title}</AlertTitle>
						<AlertDescription>{error.message}</AlertDescription>
					</Alert>

						Please check how to contribute.

		</Layout>
	) : (
		<Keystatic client:only="react" />
	)
}

I had to use a different access token because for some reason I just couldn't get the correct api information using the keystatic token. Not really sure why, not that familiar with github scopes and stuff. Works for now though.

+1