[netdiag] add support for Vendor App URL TLV

This commit contains the following:

Adds support for the Vendor App URL TLV.
Includes new public OT APIs and configurations to get and set the TLV value.
Enables use of the TLV in the CLI networkdiagnostic command.
Updates test-020-net-diag-vendor-info.py to validate the new TLV.

Related to SPEC-1249.

@abtink: Thank you for this PR. Could "Server::AppendRequestedTlvs(const Message &aRequest, Message &aResponse)" be made public such that MeshCoP::TcatAgent can call it without making a TcatAgent a friend?

@abtink: Thank you for this PR. Could "Server::AppendRequestedTlvs(const Message &aRequest, Message &aResponse)" be made public such that MeshCoP::TcatAgent can call it without making a TcatAgent a friend?

Hi @arnulfrupp , sounds good to me. Both ways seems fine to me, making it public or having TcaatAgen be a friend so it can access it.

PR review is pending the discussion on the length. 64 is ok for shortened URLs and some normal URLs. But direct links to e.g. app stores may be longer.

New pushed commit changes the OT_NETWORK_DIAGNOSTIC_MAX_VENDOR_APP_URL_TLV_LENGTH to 96.


fix(cxx_indexer): assign usr nodes to the empty corpus

clang-format wants two spaces before the comment.
It's also unsettled whether or not we want to keep an empty corpus for USR nodes or not (my vote would be "not"). @zrlk ?

The way to spell a USR node's vname is part of our public interface. I think we should restore the indexer to a working state (which this PR does), then have a conversation about whether to change the interface.


Add new Mesh Refiners

This implements two new refiners. Maximum Marking and Dörfler Marking.
Maximum marking is one of the original marking schemes due to Babuška and co-authors.
Doerfler marking is described in https://epubs.siam.org/doi/abs/10.1137/0733054, and for some problems has provably-good convergence properties.
Doerfler marking is implemented through the algorithm of https://arxiv.org/abs/1907.13078.
The tests so far have been very limited. I'll try and whip up an example that shows off these refiners.

Reopening with ianabel:refiners now merged up to latest main mfem. Rechecked to confirm that it is style-conforming. As it's a quick feature-add I haven't ported this to a branch within the mfem repo (which I know I ought to have done originally), just want to open / review / merge quickly :)
If there are docs on the new MFEM unit test framework I'll add some tests of the marking algorithms.
The logic behind adding these refiners is that Dörfler marking provides provably-convergent (and sometimes optimal) AMR algorithms (Willy Dörfler. A convergent adaptive algorithm for Poisson’s equation. SIAM J. Numer. Anal., 33(3):1106–1124, 1996.) and Maximum marking which is a classic algorithm providing good refinement properties (Error Estimates for Adaptive Finite Element Computations, I. Babuvška and W. C. Rheinboldt SIAM Journal on Numerical Analysis, Vol. 15, No. 4, pp. 736–754, 1978).
This extends the existing MFEM provision of Threshold and Coefficient refiners. I've specifically written these as I'm writing an MFEM-based implementation of (a generalization of ) https://doi.org/10.1016/j.cpc.2020.107239
I've changed the old PR to put all refiners in mesh_operators.{c,h}pp. I note that I use the stl to implement the Dörfler marking algorithm, if that's stylistically improper, we can try to port it to mfem's internal Array objects (rather than std::vector).
I've tested this on my own problems and it works fine. Both refiners work as a drop-in replacement for ThresholdRefiner in ex6 (I guess I could make ex6 allow one to vary the refiner, but haven't wrangled that yet)
However, these are purely elliptic problems in on a single node (no MPI ParMesh integration). If someone wants to try these out with ParMesh and see if they work, that would be fantastic. Similarly, if anyone reviewing wants to try this on a GPU / offload device that would be very welcome. I'm not yet ready to port my problem to GPUs so this won't be tested by me for a while.

[ ] Unit Tests
[ ] Extend ex6
[ ] Test with a parallel mesh

I have updated both the serial and parallel versions of example 6 to take a --refiner option allowing one to move between Threshold/Dörfler/MaxMark, and a --refinement-parameter option to tune the parameter of the respective models.
This works with MPI on my laptop, but appears to have broken ex6p for windows (see test outputs). Thus this is now a request for assistance, given I lack a windows machine to test on at the moment.
Working to add some Catch2 unit tests for the refiners.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Any progress on this PR? I am interested in the Dorfler marking scheme. Maybe @hughcars could have a review. I see https://github.com/awslabs/palace/pull/110

Any progress on this PR? I am interested in the Dorfler marking scheme. Maybe @hughcars could have a review. I see awslabs/palace#110

We took a different approach to QuickMark because a) the marking step is vanishingly cheap for us compared to everything else in a solve estimate mark refine loop, and b) synchronizing the partition value across processors is very important. I'm not seeing any MPI calls here, so unless I am missing something, I can't see how this would work correctly in parallel. Some kind of synchronization across ranks will be necessary for the scenario of the set M being all on one processor. QuickMark can probably generalize to parallel, but I don't think this PR does that. What I think is happening is each processor computes it's own threshold based on what it locally sees of the global estimate vector, then marks those. This does not give a minimal set, and in fact will miss many elements quite easily.
As a thought experiment, consider 10 elements split on two ranks. All the errors on rank 0 are greater than on rank 1, and theta of the total error is on rank 0. Then a correct marking will refine only those elements on rank 0, none on rank 1. The approach in this PR would mark a subset of the elements on both ranks. It is neither the minimum set, nor a superset of the minimum set.
The advantage of a sort then split approach is that the complexity actually scales (N/P) log (N/P) rather than N log N. Communication across ranks is then restricted to a bisection search on the partitioning value. Again, there's more sophisticated algorithms, but we measured marking as taking vanishingly little time compared to everything else (std::sort is just really good), so opted for simplicity.

Any progress on this PR? I am interested in the Dorfler marking scheme. Maybe @hughcars could have a review. I see awslabs/palace#110

We took a different approach to QuickMark because a) the marking step is vanishingly cheap for us compared to everything else in a solve estimate mark refine loop, and b) synchronizing the partition value across processors is very important. I'm not seeing any MPI calls here, so unless I am missing something, I can't see how this would work correctly in parallel. Some kind of synchronization across ranks will be necessary for the scenario of the set M being all on one processor. QuickMark can probably generalize to parallel, but I don't think this PR does that. What I think is happening is each processor computes it's own threshold based on what it locally sees of the global estimate vector, then marks those. This does not give a minimal set, and in fact will miss many elements quite easily.
As a thought experiment, consider 10 elements split on two ranks. All the errors on rank 0 are greater than on rank 1, and theta of the total error is on rank 0. Then a correct marking will refine only those elements on rank 0, none on rank 1. The approach in this PR would mark a subset of the elements on both ranks. It is neither the minimum set, nor a superset of the minimum set.
The advantage of a sort then split approach is that the complexity actually scales (N/P) log (N/P) rather than N log N. Communication across ranks is then restricted to a bisection search on the partitioning value. Again, there's more sophisticated algorithms, but we measured marking as taking vanishingly little time compared to everything else (std::sort is just really good), so opted for simplicity.

I agree that this PR is limited to the sequential case. How much work if porting https://github.com/awslabs/palace/pull/110 into mfem?

Any progress on this PR? I am interested in the Dorfler marking scheme. Maybe @hughcars could have a review. I see awslabs/palace#110

We took a different approach to QuickMark because a) the marking step is vanishingly cheap for us compared to everything else in a solve estimate mark refine loop, and b) synchronizing the partition value across processors is very important. I'm not seeing any MPI calls here, so unless I am missing something, I can't see how this would work correctly in parallel. Some kind of synchronization across ranks will be necessary for the scenario of the set M being all on one processor. QuickMark can probably generalize to parallel, but I don't think this PR does that. What I think is happening is each processor computes it's own threshold based on what it locally sees of the global estimate vector, then marks those. This does not give a minimal set, and in fact will miss many elements quite easily.
As a thought experiment, consider 10 elements split on two ranks. All the errors on rank 0 are greater than on rank 1, and theta of the total error is on rank 0. Then a correct marking will refine only those elements on rank 0, none on rank 1. The approach in this PR would mark a subset of the elements on both ranks. It is neither the minimum set, nor a superset of the minimum set.
The advantage of a sort then split approach is that the complexity actually scales (N/P) log (N/P) rather than N log N. Communication across ranks is then restricted to a bisection search on the partitioning value. Again, there's more sophisticated algorithms, but we measured marking as taking vanishingly little time compared to everything else (std::sort is just really good), so opted for simplicity.

I agree that this PR is limited to the sequential case. How much work if porting awslabs/palace#110 into mfem?

It wouldn't be particularly hard, it's a pretty self contained free function (dorfler.cpp), so would just require changing some of the types used internally, and using the mfem MPI calls. Placing it within the "Refiner" structure might take some thinking, but the algorithm itself is very simple and we have a reference implementation. If this is something wanted within mfem, I can put a PR together. Would probably be of value for broader testing too, as I've found Dorfler marking to be much more stressful on AMR in general.

Any progress on this PR? I am interested in the Dorfler marking scheme. Maybe @hughcars could have a review. I see awslabs/palace#110

We took a different approach to QuickMark because a) the marking step is vanishingly cheap for us compared to everything else in a solve estimate mark refine loop, and b) synchronizing the partition value across processors is very important. I'm not seeing any MPI calls here, so unless I am missing something, I can't see how this would work correctly in parallel. Some kind of synchronization across ranks will be necessary for the scenario of the set M being all on one processor. QuickMark can probably generalize to parallel, but I don't think this PR does that. What I think is happening is each processor computes it's own threshold based on what it locally sees of the global estimate vector, then marks those. This does not give a minimal set, and in fact will miss many elements quite easily.
As a thought experiment, consider 10 elements split on two ranks. All the errors on rank 0 are greater than on rank 1, and theta of the total error is on rank 0. Then a correct marking will refine only those elements on rank 0, none on rank 1. The approach in this PR would mark a subset of the elements on both ranks. It is neither the minimum set, nor a superset of the minimum set.
The advantage of a sort then split approach is that the complexity actually scales (N/P) log (N/P) rather than N log N. Communication across ranks is then restricted to a bisection search on the partitioning value. Again, there's more sophisticated algorithms, but we measured marking as taking vanishingly little time compared to everything else (std::sort is just really good), so opted for simplicity.

I agree that this PR is limited to the sequential case. How much work if porting awslabs/palace#110 into mfem?

It wouldn't be particularly hard, it's a pretty self contained free function (dorfler.cpp), so would just require changing some of the types used internally, and using the mfem MPI calls. Placing it within the "Refiner" structure might take some thinking, but the algorithm itself is very simple and we have a reference implementation. If this is something wanted within mfem, I can put a PR together. Would probably be of value for broader testing too, as I've found Dorfler marking to be much more stressful on AMR in general.

It would be appreciated if you could do that! I am testing the (sequential) Dorfler marking scheme in this PR for my application .


Deprecated label schema

In Rule 4 there are examples of using labels for adding metadata. These examples use the org.label-schema-specification which is then noted as being deprecated. Wouldn't it be more appropriate to use the currently recommended schema?

The problem is that although there is the deprecation notice, it's still hugely used - people will see labels with that convention very commonly out in the wild. So I think our strategy would best be to mention this, but then point to the now suggested convention (OCI).

Since this paper represents a fresh opportunity to encourage best practices going forward (and may be reaching readers who haven't really used labels before), wouldn't it be better to give all the examples in the new recommended (OCI) format with a note to make readers aware? Something along the lines of:

You may also commonly find labels in the deprecated org.label-schema-specification format e.g., ... However we encourage the use of the new OCI schema in all new and unlabelled projects.

There are still plenty of instances of from __future__ import print_function in the wild but I wouldn't give examples in Python 2 for a modern "Ten simple rules for Python Programming" type paper.

That would work for me, for sure.


How to understand the unsupport in c model about command illegal ?

https://github.com/riscv-non-isa/riscv-iommu/blob/main/src/iommu_in_memory_queues.adoc#command-queue-cq

A command is unsupported if it is defined but not implemented as determined by the IOMMU capabilities register.

In the c model, if a iofence.c command is send, but the g_reg_file.fctl.wsi == 0 && command.iofence.wsi == 1  is meet the condition, the command will be illegal. However, it is not  involved in a judgement about IOMMU capabilities register.
        case IOFENCE:
            if ( command.iofence.reserved != 0 || command.iofence.reserved1 != 0 )
                goto command_illegal;
            // The wired-signaled-interrupt (WSI) bit when set to 1
            // causes a wired-interrupt from the command
            // queue to be generated on completion of IOFENCE.C. This
            // bit is reserved if the IOMMU supports MSI.
            if ( g_reg_file.fctl.wsi == 0 && command.iofence.wsi == 1)
                goto command_illegal;

https://github.com/riscv-non-isa/riscv-iommu/blob/main/iommu_ref_model/libiommu/src/iommu_command_queue.c#L160
If a iodir command is send, but command illegal judgement is not involved in ddtp.iommu_mode， which might cause a unexpect condition.  This is also not  involved in a judgement about IOMMU capabilities register. And c model use a g_max_devid_mask to instead.
            switch ( command.any.func3 ) {
                case INVAL_DDT:
                    // The PID operand is reserved for the
                    // IODIR.INVAL_DDT command.
                    if ( command.iodir.pid != 0 ) goto command_illegal;
                    // When DV operand is 1, the value of the DID operand must not
                    // be wider than that supported by the ddtp.iommu_mode.
                    if ( command.iodir.dv &&
                         (command.iodir.did & ~g_max_devid_mask) ) {
                        goto command_illegal;
                    }

https://github.com/riscv-non-isa/riscv-iommu/blob/main/iommu_ref_model/libiommu/src/iommu_command_queue.c#L114
So.  Is the ftcl should not involved in judgement? Or is the ddtp.iommu_mode should involved in judgement?
Thanks.

A command is unsupported if it is defined but not implemented as determined by the IOMMU capabilities register.

This statement is about the command itself. The first statement of that paragraph applies to commands that are implemented:  "A command is determined to be illegal if it uses a reserved encoding or if a reserved bit is set to 1."

Get it. Thanks a lot.


Delphi 11.2: ALVideoPlayer in IOS

Hello,
I can't show video under IOS on Delphi 11.2.
The video is not shown, I hear only the sound from this video.
Black screen instead of video
Tried on Demo: ALFmxControls
And
procedure TForm2.Button2Click(Sender: TObject);
begin
If ALVideoPlayerSurface.VideoPlayer.state in [vpsIdle] Then
ALVideoPlayerSurface.VideoPlayer.prepare('http://techslides.com/demos/samples/sample.mp4', True);
end;
The result is the same: Black screen and sound

And in Delphi 11.3 CE too

I was able to reproduce, i will work on it asap

Not sure if you've got onto this yet, but because of Skia you won't be able to use TCustomCanvasGpu in TALVideoPlayerSurface.Paint anymore. Perhaps it'd be a good idea to recreate your TALVideoPlayerSurface  control to inherit from TViewport3D, and then create an inner control that inherits from TShape3D whose MaterialSource will be TTextureMaterialSource? That way you'll again have direct access to a TTexture property via TTextureMaterial(TTextureMaterialSource.Material).Texture that will trigger Repaint on change in its setter.
Hope I helped!

Hi, i m on it right now, i m doing the migration to Athens. hope I will finish this week or new week


[Pipeline] Repository will automatically been reset randomlly

When I click on the clone step, even if I didn't save the step (by clicking cancel), the step would be reset as random repo.

Useful
Info

Versions
Rancher v2.0.1-rc5 UI: v2.0.45

Access
local admin

Route
authenticated.project.pipeline.pipelines

fixed


Points are static

Should points be static, or be able to move dynamically? Of course they should be able to change the entry's entry.

Uhhh, I like that you ask this question... basically, we can do anything we want!!  My thought right now is that they should be static.  Plot a point (3,2) and that is what you get.

Ahh... I think I get what you are thinking... we can obtain dynamic graphs with a little bit of creative map point work:

Map points are dynamic... create conics using map points and we have dynamics.
https://rawgit.com/johnRedden/OpenGraph/master/opengraph.html?x-1&-x&ellipse\ abc
create the map points on the link and then ellipse will render. When I hit the share button that link should automatically highlight for me!!

So no? At least for now?


update AutoConnect-ASCSubscriptions

updated existing playbook AutoConnect-ASCSubscriptions.

Leverages MSI now instead of App Registration

Updates connector to use Bi-directional sync with Azure Defender

updated readme with information with changes.

Fixes #
Proposed Changes

@swiftsolves-msft Thanks for the great update!!
Why did we get the resource group/subscription as a parameter instead of the ARM template function?

@swiftsolves-msft Thanks for the great update!!
Why did we get the resource group/subscription as a parameter instead of the ARM template function?

Thanks Lior apologies I ahve restored those deploy funcs and removed the params.


Apply some fixes to allow for playwright to run on Linux

@TheCleric I confirm this fixed PW tests on my Linux box too. Thxxxx for looking into it!


[otbn,doc] Add README for RIG internals

I am also planning to add an example of changing the internals to hit a coverage hole but I thought better to have it here for the first feedback.

Applied the feedback, thanks for having a look everyone!


Mark Kafka uri attributes as sensitive

Currently, the definition of some uri attribute on Kafka aiven_service resource doesn't state it as sensitive. uri attribute usually contains the user+password combination of the default/admin user to connect to the service.
Fixes https://github.com/aiven/terraform-provider-aiven/issues/85.

Thank you for the contribution!


xGov-16 - Dotty V2

Dotty V1
Algoneer

Hi @paxsomnius, unfortunately, your proposal doesn't meet the Algorand Foundation criteria, as specified in the instructions:
[(https://github.com/algorandfoundation/ARCs/blob/main/ARCs/arc-0034.md#submit-a-proposal)]
Disclaimer jurisdictions and exclusions
To be eligible to apply for a grant, projects must abide by the Disclaimers (in particular the “Excluded Jurisdictions” section) and be willing to enter into a binding contract with the Algorand Foundation (template link coming soon) . Additionally, applications promoting gambling, adult content, drug use, and violence of any kind are not permitted.


i hope one day u implement Image search

i hope one day u implement Image search

Hi @hiwyn 👋
maybe you want to take a look at nut-tree/nut.js


[AMBARI-24464] Integrate Blueprints with the new MPackAdvisor API for Configuration Recommendations

What changes were proposed in this pull request?
This is a preview patch for mpack advisor support for blueprints. Unit tests are being written at the moment.
Mpack advisor is the new default engine for configuration recommendation. It is possible to use the legacy stack advisor though by setting use.legacy.stackadvisor=true in ambari.properties.
How was this patch tested?
Tested by manual blueprint deployment. Unit tests are being written.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3866/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3906/
Test FAILed.
Test FAILured.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3910/
Test FAILed.
Test FAILured.

Looks like many test failures are due to this change. Looking into it.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3919/
Test FAILed.
Test FAILured.

Thanks for the changes.  Please make sure to fix the remaining unit tests, if possible.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3925/
Test FAILed.
Test FAILured.

retest please

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3929/
Test FAILed.
Test FAILured.

retest this please

Latest build failed at Python tests, and is not caused by this change, happens on the base branch, too.
FAIL: test_get_stack_feature (TestStackFeature.TestStackFeature)


D435 works fine on jetson TX2 but D435i doesn't

Required Info

Camera Model
{ D435&D435i }

Firmware Version
(D435=<IP_ADDRESS>; D435i=NULL)

Operating System & Version
{Linux (Ubuntu 18)}

Kernel Version (Linux Only)
(4.9.140-tegra)

Platform
NVIDIA Jetson

SDK Version
{2.39.0 }

Language
{python }

Segment
{Robot }

Issue Description
I build librealsense from source by cmake ../ -DBUILD_PYTHON_BINDINGS:bool=true -DBUILD_EXAMPLES=true -DBUILD_WITH_CUDA=true and want to run D435 and D435i on jetson TX2 at the same time.
For D435 , command lsusb and rs-enumerate-device output rightly and the camera works all right;
But when I plug D435i on jetson tx2, lsusb command does show the Device Intel Corp. while command rs-enumerate-device outputs no device connect.
Why is this and is there any special settings for D435i
Thanks!

Hi @surefyyq   The key information seems to be that you want to use the D435 and D435i at the same time on Jetson.  The model being D435i instead of D435 is not likely to be the cause of it not working.  There have been past cases in which detection failures have occurred when more than one camera is attached to a Jetson board (though they are capable of multi-camera setups).
Could you test please whether rs-enumerate-devices can find the D435i if it is the only camera attached and the D435 is unplugged, please?

Hi @MartyG-RealSense Thanks for your quick reply!
When D435i alone is plugged on TX2, rs-enumerate-devices outputs No device detected. Is it plugged in?
And the realsense-viewer in jetson Ubuntu can't detect D435i either,
But in win10, realsense-viewer works normally for the same D435i.

Which librealsense SDK version are you using on Jetson please?

Sorry for the late, but how can I check the version of librealsense SDK on jetson?
Before build, I clone it by git clone https://github.com/IntelRealSense/librealsense.git.

If you are installing librealsense from source with CMake then you could choose the version that is built simply by downloading a zip-file of the source code folder from the Assets file list of a specific version on the SDK Releases page.
https://github.com/IntelRealSense/librealsense/releases
Once the source code zip-file is extracted into a folder then you would go to the root directory and perform mkdir build && cd build as usual to prepare that source-code folder for building the particular librealsense version in that folder.
I would not recommmend installing a librealsense version as old as 2.18.0 though.  And I am not aware of a reason why using TX2 with D435i on a modern version such as 2.39.0 would prevent the camera from being detected.
If you prefer to build from source with CMake then you may increase you chances of success if you use instructions in the link below that have been consistently successful with Jetson boards.
https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-707501049
I have also found though that building with Debian packages on TX2 instead of source code has also been successful.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md

Problem solved, thank you!
According to https://github.com/IntelRealSense/librealsense/issues/6980#issuecomment-666858977 and https://github.com/IntelRealSense/librealsense/issues/6964#issuecomment-707501049, the No device detected. Is it plugged in? issue may be related to several reasons including cmake version, librealsense version and cmake build parameters.
I tested several experiments with controlled variable and it turns out that cmake and librealsense version are not the key.
With all other conditions remain the same, my original way of  building from source: cmake ../ -DBUILD_PYTHON_BINDINGS:bool=true -DBUILD_EXAMPLES=true -DBUILD_WITH_CUDA=true  works for D435 but doesn't work for D435i,
but the way cmake ../ -DFORCE_RSUSB_BACKEND=ON -DBUILD_PYTHON_BINDINGS:bool=true  -DCMAKE_BUILD_TYPE=release -DBUILD_EXAMPLES=true -DBUILD_GRAPHICAL_EXAMPLES=true -DBUILD_WITH_CUDA:bool=true works for both D435 and D435i !
Don't know why, but I'm closing this issue~

Great news @surefyyq that you found a method that works for you - thanks very much for the update!


past dates disable

how to disable past dates?

https://github.com/mmazzarolo/react-native-modal-datetime-picker/issues/469

@mmazzarolo thank you


better alignment in flex mode

Integrated in https://github.com/Scrivito/scrivito-portal-app/pull/533/commits/6fe9c8657c147ecb8cd1957d955dc7b6a5d37419


fix: ERC20 read properties function fixed - multiple inlined async/await was causing issues

PR will be reopened.


Shell scripts runs into issue when in startup

I wrote a script that changes wallpaper and color palete(using Pywal) on detecting workspace shifts and it worked swiftly in terminal, however it does not when I put it in the Hypr config file to make it run on startup. It did run in background, but it doesn't work
Here's the script

#!/bin/bash
WALLPAPER_DIR=/home/xyz/Pictures/Background
wal-tile() {
wal -n -i "$1" && swww img "$(< "${HOME}/.cache/wal/wal")"
}
handle() {
notify-send -u normal "chwal-test" "$(wal-tile $WALLPAPER_DIR/$1.png)" #A test method that uses notification, normally there would be outputs from pywal,  except when executed by Hypr on startup
echo $1
echo "Using image $(< $HOME/.cache/wal/wal)"
}
socat -t 2000 -u UNIX-CONNECT:/tmp/hypr/$HYPRLAND_INSTANCE_SIGNATURE/.socket2.sock - | stdbuf -o0 -i0 -e0 sed -En '/^(workspace>>[0-9])$/{s/.*([0-9])$/\1/p}' | while read -r line; do handle $line; done

Steps to reproduce:
Apply the script in the hypr config file, reload session and try switching workspaces
Expected outcome:
Wallpaper and color palette changes, output from notification daemon is not empty
Actual outcome:
Wallpaper and color palette does not change, empty output from notification daemon
Version: Hyprland, built from branch HEAD at commit ce632b7a05a27d121c9544607ccd873adee8bd42dirty (prevent early segfaults on default mouse pos).

solved by using absolute path for pywal bin, seems hyprland doesn't source .bashrc or .zshrc file


Fix Local API update typing

Payload allows for updating doc with only partial data, but the inferred type requires the whole collection type.  Closes #2009
Description

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[x] 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)
[ ] This change requires a documentation update

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

Thanks for the PR @xHomu . I had to make just a small update, so it would compile.


Template config

I use craft for my websites and this plugin is perfect except the template config uses {{ for the variables in the structure which is breaking as craft uses twig for compliling.
Is there a way I can change the template config, perhaps the pattern in the function for the template:
Pattern = /(?:{{2})([\w[].]+)(?:}{2})/;
Sadly, I cannot fathom the pattern setup here, so perhaps its easy to do or perhaps if this is still managed an option can be added to change the template variable wrappers from {{ }} to something else like ## ##

Hi @shaunhalldesign - you can use [verbatim](https://twig.symfony.com/doc/2.x/tags/verbatim.html) or escaping in twig to escape the template variables for instafeed.js and other mustache-y style templates.


Assassination Rogue Requests

1- When filtering weapons for assassination rogue there is currently no way to filter out blacksmithing items that are 365 ilvl which are not available in the first phase of the expansion without also removing Heroic ilvl gear. Can these items such as Brainsplitter please be given the firelands tag as well as Professions tag? On closer inspection it appears that there is currently no phase filter for all items.
2- Can the weapons speed filter for rogues please be split into two sperate filters, one for main hand and one for off-hand, this will allow different speed filters to be applied for each weapon. For assassination the default will be a slow main hand and a fast off-hand.  Currently the same list is shown for both weapons.
Keep up the good work and thanks for the site :)

@Boy-stupid Thanks for your requests.

This is unfortunately not possible. We use WoWHead as data source and unfortunately the items havent been properly tagged yet. We do run database imports every now and then, so once WoWHead fixes it on their end, it should also reflect within our tool.
This should actually be possible, however the input seems to be missing on all Dual wield classes. I will investigate.

Fix for this is implemented here and will be merged soon:
https://github.com/wowsims/cata/pull/770

Closing, this was merged.
Should be deployed to web in a bit, and tomorrows release should have it for the local sim.


Minor defect in report subcommand when using a local path starting with s3

This is pretty minor issue and I wasn't sure if it warranted an issue report or not.
I noticed that there was a discrepancy between how most policies determine whether to use s3 for the storage and how the report subcommand determines it.  If you pass a local file directory starting with s3 to the run subcommand it works fine (and creates a local directory with the given name), but if you pass it to report it will give this error:
$ custodian report -c report.yml -s s3-foo-bar
Traceback (most recent call last):
  File "/Users/kkronenfeld/sixfeetup/cloud-custodian/bin/custodian", line 11, in <module>
    load_entry_point('c7n', 'console_scripts', 'custodian')()
  File "/Users/kkronenfeld/sixfeetup/cloud-custodian/c7n/cli.py", line 144, in main
    options.command(options)
  File "/Users/kkronenfeld/sixfeetup/cloud-custodian/c7n/commands.py", line 40, in _load_policies
    return f(options, policies)
  File "/Users/kkronenfeld/sixfeetup/cloud-custodian/c7n/commands.py", line 103, in report
    raw_output_fh=options.raw)
  File "/Users/kkronenfeld/sixfeetup/cloud-custodian/c7n/reports/csvout.py", line 83, in report
    policy.ctx.output.bucket,
AttributeError: 'DirectoryOutput' object has no attribute 'bucket'

I'll provide a fix on #536

I forgot to link the commit, but this is fixed in PR #536
This works now:
$ custodian run -c report.yml -s s3-foo-bar
2016-11-01 16:58:01,607: custodian.policy:INFO Running policy ec2-running-instances resource: ec2 region:us-east-1 c7n:<IP_ADDRESS>
2016-11-01 16:58:01,607: custodian.resources.ec2:INFO Filtered from 1 to 1 ec2
2016-11-01 16:58:01,607: custodian.policy:INFO policy: ec2-running-instances resource:ec2 has count:1 time:0.00

$ custodian report -c report.yml -s s3-foo-bar
action-date,instance-id,name,instance-type,launch,vpc-id,ip-addr,asv,env,owner
2016-11-01,i-09c1c849ee8955035,c7n-test-ec2,t2.micro,2016-10-25T13:08:35+00:00,vpc-d2d616b5,<IP_ADDRESS>,,,

good catch, thanks


when the required_if condition does not take effect, it also verifies gt=0

Package version eg. v9, v10:
v10.14.1
Issue, Question or Enhancement:
When using required_if, when the required_if condition does not take effect, it also verifies gt=0
Code sample, to showcase or reproduce:

type ParamsValidate struct {
	Finish      int    `form:"finish" binding:"omitempty,eq=1|eq=0"`
	ChunkNumber int `form:"chunkNumber" binding:"required_if=Finish 0,number,gt=0"`
}

params := ParamsValidate{}
err := ctx.ShouldBindWith(&params, bind.NewCompositeBind(ctx.ContentType(), ctx.Params))

if err != nil {
	fmt.Println(err.Error())
}

when post finish = 0 and chunkNumber = -1:
error message: Key: 'ParamsValidate.ChunkNumber' Error:Field validation for 'ChunkNumber' failed on the 'gt' tag
when post finfish = 1 and chunkNumber = -1  or without chunkNumber :
error message: Key: 'ParamsValidate.ChunkNumber' Error:Field validation for 'ChunkNumber' failed on the 'gt' tag
===================
Question:
ChunkNumber should not be validated when Finish is equal to 1 ?
Because the default value of the int type of the struct is 0，how can I fix it ?

ChunkNumber should not be validated when Finish is equal to 1 ?
Because the default value of the int type of the struct is 0，how can I fix it ?

The required_if tag does not stop validation when the requirement is met. For this reason, so long as validation of previous tags succeed, gt=0 will always get evaluated.
It's not clear to me whether ChunkNumber can either be positive or negative when Finish is empty, or if ChunkNumber must be empty when Finish is equal to 1.
Some clarification on your requirements would be helpful as to provide you with a proper solution.
As a side note:
- omitempty,eq=1|eq=0 is effectively the same as omitempty,eq=1 or eq=1|eq=0
- The number tag is meant for validating numbers represented as strings.


[Feature Request] - Ability to add multipart/form-data files to requests

JMeter (as does PostMan) allows us to attach files to our load test requests as part of a multiform/form-data parameter with a path to the file we want to send.
The only other alternative that I see to perform load testing that has a requirement to also send a csv file attached as form-data is to spin up a VM install JMeter and start to scale it to handle volume demand.
AB#1673195

@JoeTomkinson... For the scenario of uploading a file have you tried the scenario locally?

Yes

@JoeTomkinson... For the scenario of uploading a file have you tried the scenario locally with JMeter?

yes, it is possible to do this locally with JMeter - Our scenario is based around IoT devices that send in CSV files as form-data as part of their HTTP Request over our Application Gateway, so for us to volume test the rest of our solution, we need to also send in versions of these CSV files.
I can't see anyway currently to do this with 'Azure Load Testing' I thought at first that we could upload the csv and somehow reference it as an absolute url path; but that isn't something we can do with this resource yet as far as I am aware.

Screenshot above is just a snippet from JMeter showing the 'use multi-part/form-data' checkbox and with a file added.

@JoeTomkinson... you may upload the file along with the JMX test plan and in the file path under the file upload tab in the Jmeter test plan you can just specify the file name. Can you run it and confirm if it is working for you?


[Bug] N5095 Jasper Lake is incorrectly detected

Current Behavior
Right now, the N5095 is incorrectly detected by 54-check-qsv.sh as not supporting QuickSync, which is incorrect.
This is because list_cpu_features returns uarch as INTEL_ATOM_TMT, which is not really correct:
/etc/cont-init.d# list_cpu_features
arch            : x86
brand           : Intel(R) Celeron(R) N5105 @ 2.00GHz
family          :   6 (0x06)
model           : 156 (0x9C)
stepping        :   0 (0x00)
uarch           : INTEL_ATOM_TMT
flags           : aes,clflushopt,clfsh,clwb,cx16,cx8,erms,fpu,gfni,mmx,movbe,movdir64b,movdiri,pclmulqdq,popcnt,rdrnd,rdseed,sha,ss,sse,sse2,sse3,sse4_1,sse4_2,ssse3,tsc
cache_info      : {"level":1,"cache_type":"data","cache_size":32768,"ways":8,"line_size":64,"tlb_entries":64,"partitioning":1},{"level":1,"cache_type":"instruction","cache_size":32768,"ways":8,"line_size":64,"tlb_entries":64,"partitioning":1},{"level":2,"cache_type":"unified","cache_size":1572864,"ways":12,"line_size":64,"tlb_entries":2048,"partitioning":1},{"level":3,"cache_type":"unified","cache_size":4194304,"ways":16,"line_size":64,"tlb_entries":4096,"partitioning":1}

I suspect this will affect all N series, although I don't have an N100 or an N95 handy to test.
Expected Behavior
Jasper Lake CPUs should be correctly detected.
Steps To Reproduce
No response
Environment

OS: ubuntu
OS version: 22.04
CPU: N5095
Docker version:
Device model:
Browser/OS:

Container creation
Using the example docker-compose.yml, with the addition of /dev/dri device passthrough
Container log
[init        ] container is starting...
[cont-env    ] loading container environment variables...
[cont-env    ] APP_NAME: loading...
[cont-env    ] APP_VERSION: loading...
[cont-env    ] DISPLAY: executing...
[cont-env    ] DISPLAY: terminated successfully.
[cont-env    ] DISPLAY: loading...
[cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
[cont-env    ] DOCKER_IMAGE_VERSION: loading...
[cont-env    ] GTK2_RC_FILES: executing...
[cont-env    ] GTK2_RC_FILES: terminated successfully.
[cont-env    ] GTK2_RC_FILES: loading...
[cont-env    ] GTK_THEME: executing...
[cont-env    ] GTK_THEME: terminated successfully.
[cont-env    ] GTK_THEME: loading...
[cont-env    ] HOME: loading...
[cont-env    ] INSTALL_PACKAGES_INTERNAL: executing...
[cont-env    ] INSTALL_PACKAGES_INTERNAL: terminated successfully.
[cont-env    ] INSTALL_PACKAGES_INTERNAL: loading...
[cont-env    ] QT_STYLE_OVERRIDE: executing...
[cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
[cont-env    ] QT_STYLE_OVERRIDE: loading...
[cont-env    ] SUP_GROUP_IDS_INTERNAL: executing...
[cont-env    ] SUP_GROUP_IDS_INTERNAL: terminated successfully.
[cont-env    ] SUP_GROUP_IDS_INTERNAL: loading...
[cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
[cont-env    ] XDG_CACHE_HOME: loading...
[cont-env    ] XDG_CONFIG_HOME: loading...
[cont-env    ] XDG_DATA_HOME: loading...
[cont-env    ] XDG_RUNTIME_DIR: loading...
[cont-env    ] XDG_STATE_HOME: loading...
[cont-env    ] container environment variables initialized.
[cont-secrets] loading container secrets...
[cont-secrets] container secrets loaded.
[cont-init   ] executing container initialization scripts...
[cont-init   ] 10-certs.sh: executing...
[cont-init   ] 10-certs.sh: terminated successfully.
[cont-init   ] 10-check-app-niceness.sh: executing...
[cont-init   ] 10-check-app-niceness.sh: terminated successfully.
[cont-init   ] 10-clean-logmonitor-states.sh: executing...
[cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
[cont-init   ] 10-clean-tmp-dir.sh: executing...
[cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
[cont-init   ] 10-fontconfig-cache-dir.sh: executing...
[cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
[cont-init   ] 10-init-users.sh: executing...
[cont-init   ] 10-init-users.sh: terminated successfully.
[cont-init   ] 10-nginx.sh: executing...
[cont-init   ] 10-nginx.sh: terminated successfully.
[cont-init   ] 10-openbox.sh: executing...
[cont-init   ] 10-openbox.sh: terminated successfully.
[cont-init   ] 10-pkgs-mirror.sh: executing...
[cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
[cont-init   ] 10-set-tmp-dir-perms.sh: executing...
[cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
[cont-init   ] 10-vnc-password.sh: executing...
[cont-init   ] 10-vnc-password.sh: terminated successfully.
[cont-init   ] 10-web-data.sh: executing...
[cont-init   ] 10-web-data.sh: terminated successfully.
[cont-init   ] 10-x11-unix.sh: executing...
[cont-init   ] 10-x11-unix.sh: terminated successfully.
[cont-init   ] 10-xdg-runtime-dir.sh: executing...
[cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
[cont-init   ] 15-cjk-font.sh: executing...
[cont-init   ] 15-cjk-font.sh: terminated successfully.
[cont-init   ] 15-install-pkgs.sh: executing...
[cont-init   ] 15-install-pkgs.sh: terminated successfully.
[cont-init   ] 54-check-optical-drive.sh: executing...
[cont-init   ] 54-check-optical-drive.sh: looking for usable optical drives...
[cont-init   ] 54-check-optical-drive.sh: no usable optical drive found.
[cont-init   ] 54-check-optical-drive.sh: terminated successfully.
[cont-init   ] 54-check-qsv.sh: executing...
[cont-init   ] 54-check-qsv.sh: Processor: Intel(R) Celeron(R) N5105 @ 2.00GHz
[cont-init   ] 54-check-qsv.sh: Microarchitecture: INTEL_ATOM_TMT
[cont-init   ] 54-check-qsv.sh: Kernel: 6.5.11-4-pve
[cont-init   ] 54-check-qsv.sh: Intel Quick Sync Video may not be supported: processor not QSV capable.
[cont-init   ] 54-check-qsv.sh: terminated successfully.
[cont-init   ] 54-check-trash-dir.sh: executing...
[cont-init   ] 54-check-trash-dir.sh: terminated successfully.
[cont-init   ] 55-handbrake.sh: executing...
[cont-init   ] 55-handbrake.sh: core dump file location: core
[cont-init   ] 55-handbrake.sh: core dump file size: unlimited (blocks)
[cont-init   ] 55-handbrake.sh: terminated successfully.
[cont-init   ] 85-take-config-ownership.sh: executing...
[cont-init   ] 85-take-config-ownership.sh: terminated successfully.
[cont-init   ] 89-info.sh: executing...
    ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
    │                                                                      │
    │ Application:           HandBrake                                     │
    │ Application Version:   1.7.1                                         │
    │ Docker Image Version:  23.11.5                                       │
    │ Docker Image Platform: linux/amd64                                   │
    │                                                                      │
    ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
[cont-init   ] 89-info.sh: terminated successfully.
[cont-init   ] all container initialization scripts executed.
[init        ] giving control to process supervisor.
[supervisor  ] loading services...
[supervisor  ] loading service 'default'...
[supervisor  ] loading service 'app'...
[supervisor  ] loading service 'gui'...
[supervisor  ] loading service 'openbox'...
[supervisor  ] loading service 'xvnc'...
[supervisor  ] loading service 'certsmonitor'...
[supervisor  ] service 'certsmonitor' is disabled.
[supervisor  ] loading service 'nginx'...
[supervisor  ] loading service 'logmonitor'...
[supervisor  ] service 'logmonitor' is disabled.
[supervisor  ] loading service 'logrotate'...
[supervisor  ] loading service 'autovideoconverter'...
[supervisor  ] all services loaded.
[supervisor        ] starting services...
[supervisor        ] starting service 'xvnc'...
[xvnc              ] Xvnc TigerVNC 1.13.1 - built Nov 10 2023 13:43:39
[xvnc              ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc              ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc              ] Underlying X server release 12014000
[xvnc              ] Sat Dec  9 16:49:50 2023
[xvnc              ]  vncext:      VNC extension running!
[xvnc              ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc              ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc              ]  vncext:      created VNC server for screen 0
[supervisor        ] starting service 'openbox'...
[supervisor        ] starting service 'nginx'...
[nginx             ] Listening for HTTP connections on port 5800.
[supervisor        ] starting service 'app'...
[supervisor        ] starting service 'autovideoconverter'...
[autovideoconverter] Processing watch folder '/watch'...
[autovideoconverter] Waiting 5 seconds before processing '/watch/The Witcher - S03E05 - The Art of Illusion WEBDL-1080p.mkv'...
[supervisor        ] all services started.
[xvnc              ] Sat Dec  9 16:49:55 2023
[xvnc              ]  Connections: accepted: /tmp/vnc.sock
[xvnc              ]  SConnection: Client needs protocol version 3.8
[xvnc              ]  SConnection: Client requests security type None(1)
[xvnc              ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc              ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc              ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc              ]  ComparingUpdateTracker: (1:-nan ratio)
[autovideoconverter] Starting conversion of '/watch/The Witcher - S03E05 - The Art of Illusion WEBDL-1080p.mkv' (a7839887da339b64a9f11cae4a766dfb) using preset 'General/Very Fast 1080p30'...
[autovideoconverter] 1 title(s) to process.
[supervisor        ] SIGTERM received, shutting down...
[supervisor        ] stopping service 'autovideoconverter'...
[supervisor        ] service 'autovideoconverter' exited (got signal SIGTERM).
[supervisor        ] stopping service 'app'...
[supervisor        ] service 'app' exited (got signal SIGTERM).
[supervisor        ] stopping service 'nginx'...
[xvnc              ] Sat Dec  9 16:55:20 2023
[xvnc              ]  VNCSConnST:  Failed to flush remaining socket data on close: write: Broken
[xvnc              ]               pipe (32)
[xvnc              ]  VNCSConnST:  closing /tmp/vnc.sock: write: Broken pipe (32)
[xvnc              ]  EncodeManager: Framebuffer updates: 3352
[xvnc              ]  EncodeManager:   Tight:
[xvnc              ]  EncodeManager:     Solid: 4.161 krects, 25.9601 Mpixels
[xvnc              ]  EncodeManager:            65 KiB (1:1560.85 ratio)
[xvnc              ]  EncodeManager:     Bitmap RLE: 431 rects, 131.145 kpixels
[xvnc              ]  EncodeManager:                 12.7363 KiB (1:40.6189 ratio)
[xvnc              ]  EncodeManager:     Indexed RLE: 5.728 krects, 3.49215 Mpixels
[xvnc              ]  EncodeManager:                  818.289 KiB (1:16.7524 ratio)
[xvnc              ]  EncodeManager:   Tight (JPEG):
[xvnc              ]  EncodeManager:     Full Colour: 6.957 krects, 42.5452 Mpixels
[xvnc              ]  EncodeManager:                  25.6269 MiB (1:6.33618 ratio)
[xvnc              ]  EncodeManager:   Total: 17.277 krects, 72.1285 Mpixels
[xvnc              ]  EncodeManager:          26.5019 MiB (1:10.3897 ratio)
[supervisor        ] service 'nginx' exited (with status 0).
[xvnc              ]  Connections: closed: /tmp/vnc.sock
[xvnc              ]  ComparingUpdateTracker: 150.611 Mpixels in / 59.1642 Mpixels out
[xvnc              ]  ComparingUpdateTracker: (1:2.54564 ratio)
[supervisor        ] stopping service 'openbox'...
[supervisor        ] service 'openbox' exited (with status 0).
[supervisor        ] stopping service 'xvnc'...
[xvnc              ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc              ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor        ] service 'xvnc' exited (with status 0).
[finish      ] executing container finish scripts...
[finish      ] all container finish scripts executed.

Container inspect
No response
Anything else?
No response

Thanks for reporting. I will adjust the script.
Note that Tremont` seems to be the correct micro-architecture for your CPU: https://en.wikipedia.org/wiki/Tremont_(microarchitecture).

I have the same issue with a J4105 CPU
https://en.wikipedia.org/wiki/Goldmont_Plus
handbrake  | [cont-init   ] 54-check-qsv.sh: Processor: Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
handbrake  | [cont-init   ] 54-check-qsv.sh: Microarchitecture: INTEL_ATOM_GMT_PLUS
handbrake  | [cont-init   ] 54-check-qsv.sh: Kernel: 6.1.0-16-amd64
handbrake  | [cont-init   ] 54-check-qsv.sh: Intel Quick Sync Video may not be supported: processor not QSV capable.
handbrake  | [cont-init   ] 54-check-qsv.sh: terminated successfully.

Full container log

[+] Running 1/1
 ✔ Container handbrake  Recreated                                                                                0.2s
Attaching to handbrake
handbrake  | [init        ] container is starting...
handbrake  | [cont-env    ] loading container environment variables...
handbrake  | [cont-env    ] APP_NAME: loading...
handbrake  | [cont-env    ] APP_VERSION: loading...
handbrake  | [cont-env    ] DISPLAY: executing...
handbrake  | [cont-env    ] DISPLAY: terminated successfully.
handbrake  | [cont-env    ] DISPLAY: loading...
handbrake  | [cont-env    ] DOCKER_IMAGE_PLATFORM: loading...
handbrake  | [cont-env    ] DOCKER_IMAGE_VERSION: loading...
handbrake  | [cont-env    ] GTK2_RC_FILES: executing...
handbrake  | [cont-env    ] GTK2_RC_FILES: terminated successfully.
handbrake  | [cont-env    ] GTK2_RC_FILES: loading...
handbrake  | [cont-env    ] GTK_THEME: executing...
handbrake  | [cont-env    ] GTK_THEME: terminated successfully.
handbrake  | [cont-env    ] GTK_THEME: loading...
handbrake  | [cont-env    ] HOME: loading...
handbrake  | [cont-env    ] INSTALL_PACKAGES_INTERNAL: executing...
handbrake  | [cont-env    ] INSTALL_PACKAGES_INTERNAL: terminated successfully.
handbrake  | [cont-env    ] INSTALL_PACKAGES_INTERNAL: loading...
handbrake  | [cont-env    ] QT_STYLE_OVERRIDE: executing...
handbrake  | [cont-env    ] QT_STYLE_OVERRIDE: terminated successfully.
handbrake  | [cont-env    ] QT_STYLE_OVERRIDE: loading...
handbrake  | [cont-env    ] SUP_GROUP_IDS_INTERNAL: executing...
handbrake  | [cont-env    ] SUP_GROUP_IDS_INTERNAL: terminated successfully.
handbrake  | [cont-env    ] SUP_GROUP_IDS_INTERNAL: loading...
handbrake  | [cont-env    ] TAKE_CONFIG_OWNERSHIP: loading...
handbrake  | [cont-env    ] XDG_CACHE_HOME: loading...
handbrake  | [cont-env    ] XDG_CONFIG_HOME: loading...
handbrake  | [cont-env    ] XDG_DATA_HOME: loading...
handbrake  | [cont-env    ] XDG_RUNTIME_DIR: loading...
handbrake  | [cont-env    ] XDG_STATE_HOME: loading...
handbrake  | [cont-env    ] container environment variables initialized.
handbrake  | [cont-secrets] loading container secrets...
handbrake  | [cont-secrets] container secrets loaded.
handbrake  | [cont-init   ] executing container initialization scripts...
handbrake  | [cont-init   ] 10-certs.sh: executing...
handbrake  | [cont-init   ] 10-certs.sh: terminated successfully.
handbrake  | [cont-init   ] 10-check-app-niceness.sh: executing...
handbrake  | [cont-init   ] 10-check-app-niceness.sh: terminated successfully.
handbrake  | [cont-init   ] 10-clean-logmonitor-states.sh: executing...
handbrake  | [cont-init   ] 10-clean-logmonitor-states.sh: terminated successfully.
handbrake  | [cont-init   ] 10-clean-tmp-dir.sh: executing...
handbrake  | [cont-init   ] 10-clean-tmp-dir.sh: terminated successfully.
handbrake  | [cont-init   ] 10-fontconfig-cache-dir.sh: executing...
handbrake  | [cont-init   ] 10-fontconfig-cache-dir.sh: terminated successfully.
handbrake  | [cont-init   ] 10-init-users.sh: executing...
handbrake  | [cont-init   ] 10-init-users.sh: terminated successfully.
handbrake  | [cont-init   ] 10-nginx.sh: executing...
handbrake  | [cont-init   ] 10-nginx.sh: terminated successfully.
handbrake  | [cont-init   ] 10-openbox.sh: executing...
handbrake  | [cont-init   ] 10-openbox.sh: terminated successfully.
handbrake  | [cont-init   ] 10-pkgs-mirror.sh: executing...
handbrake  | [cont-init   ] 10-pkgs-mirror.sh: terminated successfully.
handbrake  | [cont-init   ] 10-set-tmp-dir-perms.sh: executing...
handbrake  | [cont-init   ] 10-set-tmp-dir-perms.sh: terminated successfully.
handbrake  | [cont-init   ] 10-vnc-password.sh: executing...
handbrake  | [cont-init   ] 10-vnc-password.sh: terminated successfully.
handbrake  | [cont-init   ] 10-web-data.sh: executing...
handbrake  | [cont-init   ] 10-web-data.sh: terminated successfully.
handbrake  | [cont-init   ] 10-x11-unix.sh: executing...
handbrake  | [cont-init   ] 10-x11-unix.sh: terminated successfully.
handbrake  | [cont-init   ] 10-xdg-runtime-dir.sh: executing...
handbrake  | [cont-init   ] 10-xdg-runtime-dir.sh: terminated successfully.
handbrake  | [cont-init   ] 15-cjk-font.sh: executing...
handbrake  | [cont-init   ] 15-cjk-font.sh: terminated successfully.
handbrake  | [cont-init   ] 15-install-pkgs.sh: executing...
handbrake  | [cont-init   ] 15-install-pkgs.sh: terminated successfully.
handbrake  | [cont-init   ] 54-check-optical-drive.sh: executing...
handbrake  | [cont-init   ] 54-check-optical-drive.sh: looking for usable optical drives...
handbrake  | [cont-init   ] 54-check-optical-drive.sh: found optical drive /dev/sr0, group 24.
handbrake  | [cont-init   ] 54-check-optical-drive.sh: terminated successfully.
handbrake  | [cont-init   ] 54-check-qsv.sh: executing...
handbrake  | [cont-init   ] 54-check-qsv.sh: Processor: Intel(R) Celeron(R) J4105 CPU @ 1.50GHz
handbrake  | [cont-init   ] 54-check-qsv.sh: Microarchitecture: INTEL_ATOM_GMT_PLUS
handbrake  | [cont-init   ] 54-check-qsv.sh: Kernel: 6.1.0-16-amd64
handbrake  | [cont-init   ] 54-check-qsv.sh: Intel Quick Sync Video may not be supported: processor not QSV capable.
handbrake  | [cont-init   ] 54-check-qsv.sh: terminated successfully.
handbrake  | [cont-init   ] 54-check-trash-dir.sh: executing...
handbrake  | [cont-init   ] 54-check-trash-dir.sh: terminated successfully.
handbrake  | [cont-init   ] 55-handbrake.sh: executing...
handbrake  | [cont-init   ] 55-handbrake.sh: core dump file location: core
handbrake  | [cont-init   ] 55-handbrake.sh: core dump file size: unlimited (blocks)
handbrake  | [cont-init   ] 55-handbrake.sh: terminated successfully.
handbrake  | [cont-init   ] 85-take-config-ownership.sh: executing...
handbrake  | [cont-init   ] 85-take-config-ownership.sh: terminated successfully.
handbrake  | [cont-init   ] 89-info.sh: executing...
handbrake  |     ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮
handbrake  |     │                                                                      │
handbrake  |     │ Application:           HandBrake                                     │
handbrake  |     │ Application Version:   1.7.1                                         │
handbrake  |     │ Docker Image Version:  23.11.5                                       │
handbrake  |     │ Docker Image Platform: linux/amd64                                   │
handbrake  |     │                                                                      │
handbrake  |     ╰――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╯
handbrake  | [cont-init   ] 89-info.sh: terminated successfully.
handbrake  | [cont-init   ] all container initialization scripts executed.
handbrake  | [init        ] giving control to process supervisor.
handbrake  | [supervisor  ] loading services...
handbrake  | [supervisor  ] loading service 'default'...
handbrake  | [supervisor  ] loading service 'app'...
handbrake  | [supervisor  ] loading service 'gui'...
handbrake  | [supervisor  ] loading service 'xvnc'...
handbrake  | [supervisor  ] loading service 'certsmonitor'...
handbrake  | [supervisor  ] service 'certsmonitor' is disabled.
handbrake  | [supervisor  ] loading service 'openbox'...
handbrake  | [supervisor  ] loading service 'nginx'...
handbrake  | [supervisor  ] loading service 'logmonitor'...
handbrake  | [supervisor  ] service 'logmonitor' is disabled.
handbrake  | [supervisor  ] loading service 'logrotate'...
handbrake  | [supervisor  ] loading service 'autovideoconverter'...
handbrake  | [supervisor  ] all services loaded.
handbrake  | [supervisor        ] starting services...
handbrake  | [supervisor        ] starting service 'xvnc'...
handbrake  | [xvnc              ] Xvnc TigerVNC 1.13.1 - built Nov 10 2023 13:43:39
handbrake  | [xvnc              ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
handbrake  | [xvnc              ] See https://www.tigervnc.org for information on TigerVNC.
handbrake  | [xvnc              ] Underlying X server release 12014000
handbrake  | [xvnc              ] Sat Dec 16 15:52:38 2023
handbrake  | [xvnc              ]  vncext:      VNC extension running!
handbrake  | [xvnc              ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
handbrake  | [xvnc              ]  vncext:      Listening for VNC connections on all interface(s), port 5900
handbrake  | [xvnc              ]  vncext:      created VNC server for screen 0
handbrake  | [supervisor        ] starting service 'openbox'...
handbrake  | [supervisor        ] starting service 'nginx'...
handbrake  | [nginx             ] Listening for HTTP connections on port 5800.
handbrake  | [supervisor        ] starting service 'app'...
handbrake  | [supervisor        ] starting service 'autovideoconverter'...
handbrake  | [autovideoconverter] Processing watch folder '/watch'...
handbrake  | [autovideoconverter] Watch folder '/watch' processing terminated.
handbrake  | [supervisor        ] all services started.

Fix already done, it will be part of the next release.

Fixed with the latest image.


Github flavoured markdown parse code blocks in list incorrectly

For the following markdown source,
1. foo

    ```
    bar

    blah

    foo
    ```

we're expecting it would be parsed to,

foo

bar

blah

foo

but the output in fact is,

foo

 `
 bar

 blah

 foo
 `

that's weird, I thought this was working before... Thanks for reporting!

your code block is indented 1 space further than the list. Thats why it is picked up as a new paragraph.
Will see if this can be detected better.

Fixed, thanks for reporting this!


Shannon vulkaninfo html gen

 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 has been squashed and pulled into a development branch, and will be pushed to Master shortly.


Bugfix: Template creation was failing due to invalid visibility value

Fixes #2458 .
This only impacts Orgs that have multiple Org types (e.g. both a Funder and an Institution).
Changes proposed in this PR:

Add line back into the templates controller that converts the :visibility checkbox from a '0' or '1' into organizationally_visible or publicly_visible.

Thanks @briri
We'd had people's templates which had converted to publicly_visible and were not showing up from within the create-plan wizard, but I'd thought it was just a data-issue with some of the older templates


create integration cli test for -H|--human in docker history

see PR https://github.com/docker/docker/pull/12430

#dibs


Update circe-core, circe-generic to 0.13.0

Updates

io.circe:circe-core
io.circe:circe-generic

from 0.12.3 to 0.13.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

labels: test-library-update, semver-minor

Codecov Report

Merging #422 into master will increase coverage by 0.14%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #422      +/-   ##
==========================================
+ Coverage   81.98%   82.13%   +0.14%
==========================================
  Files          81       81
  Lines        2703     2703
  Branches       79       79
==========================================
+ Hits         2216     2220       +4
+ Misses        487      483       -4

Impacted Files
Coverage Δ

.../akka/actor/process_instance/ProcessInstance.scala
86.48% <0%> (+0.67%)
:arrow_up:

...e/akka/actor/process_index/ProcessIndexProto.scala
99.48% <0%> (+1.53%)
:arrow_up:

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 a943fb1...2490a59. Read the comment docs.


[DX] Added Dockerfile

PR for #45 .
Commands to build and run docker image

docker build . -t job-board from project root
 docker run    --env-file=./local.env  -p 9876:9876 job-board

/claim #45

@dm161 I think this file should go as Dockerfile.local as I made and tested it with local env in mind. Can you tell me more about how prod app gets env variable? (is it also from local.env?)

@Shubham8287 thank you for the PR

it's good to keep Dockerfile for now I will keep deploying as a binary but it might be good in the future and good if people want to run it without any dependencies but docker
looks good, can you please update the ./run-webserver-local.sh and the readme as well? The purpose of this dockerfile is to be able to run the local/prod env without having golang binary installed

de-prioritising this for now


Dashboard section clarifications

Per discussion with @JamiesHQ, here are some clarifications to the dashboarding section. The key steps are the same as what was discussed and agreed upon in PR #8, but with more detail (e.g., links) and a clearer indication of the sequential nature of the work.

👍 from me


Add pod security context from func.yaml

It would be nice to be able to set the pod security context in func.yaml. I ran into this when I was trying to mount a pvc, and I could not write to the pvc. After a lot of digging, I fould that I needed to set fsGroup like this:
kubectl patch services.serving/<name> --type merge \
    -p '{"spec": {"template": {"spec": {"securityContext": {"fsGroup":1000}}}}}'

This is because the default group is 1000 (I used golang's os/user to find it). I would prefer to be able to set that from func.yaml, or have that set automatically to some sane default.

 current func.yaml
specVersion: 0.35.0
name: consumer
runtime: go
registry: <redacted>
image: <redacted>
imageDigest: <redacted>
created: 2023-12-13T00:39:05.888786906-05:00
build:
  builder: pack
run:
  volumes:
  - presistentVolumeClaim:
      claimName: knative-pc-cephfs
    path: /files
deploy:
  namespace: default

 Here's the currently generated service:
You can see that no securityContext data is in the podspec.
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  annotations:
    dapr.io/app-id: consumer
    dapr.io/app-port: "8080"
    dapr.io/enable-api-logging: "true"
    dapr.io/enabled: "true"
    dapr.io/metrics-port: "9092"
    serving.knative.dev/creator: kubernetes-admin
    serving.knative.dev/lastModifier: kubernetes-admin
  creationTimestamp: "2023-12-20T05:20:10Z"
  generation: 1
  labels:
    boson.dev/function: "true"
    boson.dev/runtime: go
    function.knative.dev: "true"
    function.knative.dev/name: consumer
    function.knative.dev/runtime: go
  name: consumer
  namespace: default
  resourceVersion: "11510806"
  uid: ...
spec:
  template:
    metadata:
      annotations:
        dapr.io/app-id: consumer
        dapr.io/app-port: "8080"
        dapr.io/enable-api-logging: "true"
        dapr.io/enabled: "true"
        dapr.io/metrics-port: "9092"
      creationTimestamp: null
      labels:
        boson.dev/function: "true"
        boson.dev/runtime: go
        function.knative.dev: "true"
        function.knative.dev/name: consumer
        function.knative.dev/runtime: go
    spec:
      containerConcurrency: 0
      containers:
      - env:
        - name: BUILT
          value: 20231220T002010
        - name: ADDRESS
          value: <IP_ADDRESS>
        image: <redacted>
        livenessProbe:
          httpGet:
            path: /health/liveness
            port: 0
        name: user-container
        readinessProbe:
          httpGet:
            path: /health/readiness
            port: 0
          successThreshold: 1
        resources: {}
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          runAsNonRoot: true
          seccompProfile:
            type: RuntimeDefault
        volumeMounts:
        - mountPath: /files
          name: pvc-knative-pc-cephfs
      enableServiceLinks: false
      timeoutSeconds: 300
      volumes:
      - name: pvc-knative-pc-cephfs
        persistentVolumeClaim:
          claimName: knative-pc-cephfs
  traffic:
  - latestRevision: true
    percent: 100

Agreed on both suggestions.  I'll add this to our roadmap as a "ready to work" item.

Hello @zalsader! I'd like to work on this issue. Could you share some more context about how the func.yaml file is leveraged to generate the service definition? Perhaps pointing to the source code files would help too! This is my first issue and would love to contribute here!

Sure, yeah. Looking at existing closed PRs is a good first step. For example, my first contribution to the library was to add pvc to the allowed volume options. I am happy to review any PRs you create. I'm not a maintainer, so those people could provide more guidance.

hey @zalsader I after digging into this issue I found out that the podSecurityContext is getting set from here - https://github.com/knative/func/blob/d2fb76c39d5db6301a04ad78108c61e7da949a4b/pkg/k8s/persistent_volumes.go#L121
and the DefaultSecurityContext is defined here - https://github.com/knative/func/blob/d2fb76c39d5db6301a04ad78108c61e7da949a4b/pkg/k8s/security_context.go#L11
func defaultPodSecurityContext() *corev1.PodSecurityContext {
	// change ownership of the mounted volume to the first non-root user uid=1000
	if IsOpenShift() {
		return nil
	}
	runAsUser := int64(1001)
	runAsGroup := int64(1002)
	return &corev1.PodSecurityContext{
		RunAsUser:  &runAsUser,
		RunAsGroup: &runAsGroup,
		FSGroup:    &runAsGroup,
	}
}

if we have defined podSecurityContext then why is it not reflecting in service.yaml. like for containerSecurityContext
we do get the set fields like
securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          runAsNonRoot: true
          seccompProfile:
            type: RuntimeDefault

as passed using this function -

func defaultSecurityContext(client *kubernetes.Clientset) *corev1.SecurityContext {
	runAsNonRoot := true
	sc := &corev1.SecurityContext{
		Privileged:               new(bool),
		AllowPrivilegeEscalation: new(bool),
		RunAsNonRoot:             &runAsNonRoot,
		Capabilities:             &corev1.Capabilities{Drop: []corev1.Capability{"ALL"}},
		SeccompProfile:           nil,
	}
	if info, err := client.ServerVersion(); err == nil {
		var v *semver.Version
		v, err = semver.NewVersion(info.String())
		if err == nil && v.Compare(oneTwentyFour) >= 0 {
			sc.SeccompProfile = &corev1.SeccompProfile{Type: corev1.SeccompProfileTypeRuntimeDefault}
		}
	}
	return sc
}

still if we want to set the podSecurityContext explicitly will have to define new schema in func.yaml followed by creating new struct, setting the value of FSgroup using some function and passing it here - https://github.com/knative/func/blob/d2fb76c39d5db6301a04ad78108c61e7da949a4b/pkg/k8s/persistent_volumes.go#L121
am I on right track?

lets just say if I define the property PodSecurityContext in func.yaml should it be in RunSpec or in DeploySpec I have question over that!


dhw_circulation binary sensor problem

Dear Community,
I am using multimatic 1.11.0 withe the HomeAssistant. My devices are VR720 controller together with VR920 which is allows internet connection. I noticed that binary sensor dhw_circulation is changing between on / off according to schedule set in the Vaillant controller which is good but does not change the state to off when I manually disable heating the water on the controller or mobile app binary sensor does not react. Problem is that I have automation to correlate this binary sensor with external electric heater.
Thanks in advance,
Lukasz

Hello,
as far as I know, circulation and hot water are two independent component. So you can turn them on/off independently.
According to the doc here: https://elearning.vaillant.com/vrc700/ci/en/documents/uk/infopool/Operating_instructions.pdf, point 5.3.3 (page 14), if hot water is turned off, it doesn't seem to turn circulation off.
5.3.3 Operating modes for hot water generation
<IP_ADDRESS> Automatic mode
Operating mode → Domestic hot water → Auto
– The Auto operating mode controls the hot water generation in accordance with the desired temperature set for
DHW circuit and the time periods set.
Within the time period, hot water generation is switched on
and maintains the hot water in the domestic hot water cylinder at the preset temperature. Outside the time period, hot
water generation is switched off.
<IP_ADDRESS> Comfort mode
Operating mode → Domestic hot water → Day
– The Day operating mode controls the hot water generation in accordance with the desired temperature set for
DHW circuit, without taking the time periods into consideration.
<IP_ADDRESS> Off
Operating mode → Domestic hot water → Off
– Hot water generation is switched off and the Frost protection function is active.
5.3.4 Operating modes for circulation
The operating mode for the circulation always corresponds
to the operating mode for the hot water generation. You cannot set a different operating mode.

Thank you for that. Nevertheless I wrote the mail to the local Vaillant support and they confirmed my assumption. I have check also behavior of the physical devices and the fact is that when I manually turn off water heating the circulation pump has also stopped working. The issue is that binary_sensor.dhw_circulation remains on. As this is binary sensor in HA I can only see the status. IS there any way to change the value of binary_sensor.dhw_circulation ex by the service?
If not then the question why the status of binary_sensor.dhw_circulation remains on while controller switching of the physical circulation pump?

Does circulation is off on the application ? Actually, I can only rely on what the API gives me.

What I understood from the Vaillant support is that when heating water is disabled from the mobile application or right from the wall controller then the water circulation pump is also physically switched off and thus working well. Nevertheless this is not visible in the mobile app meaning the schedule for circulation pump is still visible but as long as the water heating is turned off the controller bypasses the schedule and does not turn on the pump. Questions here if the integration somehow trigger this change and set dhw_circulation binary sensor accordingly.

Yep understand your point, but the integration (and the underlying connector to the vaillant API) only rely on what API is returning. There is no way to know from the API that the device is physically turned off.

This is interesting as the device (pump) is managed by VR700 controller. This means that such information should be somewhere in the Vaillant API.

If you know where, I would be happy to integrate it, but I never found such things.
There are a lot of info in the VRC700 (heating curve, min/max temp of the circuit, etc) which are not in the API :/

@kalatos86 does it never switch off? I can replicate the issue by manually start hotwater boost. even without cancellation the circulation sensor remains in state "on". i can only assume that the API is not being queried again for this state
@thomasgermain is there an intervall pollig circulation or only during certain actions/state changes?

By default the integration is polling the API every 2min

@kalatos86 when my HeatPump produces HotWater it doesn't enable the Circulation. (Neither App nor HA) So i will need to check, if Quick Boost enabled\disables the Cirucaltion nad if this mirrors into HA as per thomas

Dear Colleges first of all thanks for active support you are trying to give.
My observation is following:

normally  dhw_circulation entity is switching between on/off well according to the schedule set in Vaillant controller
also while using service QM_HOTWATER_BOOST through HA state of dhw_circulation is set in the proper way meaning if QM_HOTWATER_BOOST is switched on then  dhw_circulation is also on. When I manually would like to switch off QM_HOTWATER_BOOST using RemoveQuickMode then dhw_circulation is also switched off
problem occurring when I'd like to switch off heating water by switching it of from the mobile app or right from the controller. IT seems that Vaillant controller switched off physical circulation pump but dhw_circulation still switch between on/off according to the Vaillant schedule - and here is the issue.

Hope I described it in the way you will understood it :)
BR,
Lukasz

It seems that Vaillant controller switched off physical circulation pump and that's the desired action but dhw_circulation still switch between on/off according to the Vaillant schedule - and here is the issue.

Are you talking about the binary_sensor ? Or the mobile app ? (Or both ?)
I did some tests: I have hot water, but no circulation. I can set a schedule for my hot water AND circulation.
First test: set hot water off (either off or not on schedule) and scheduled circulation ON, here is the result:
Circulation is ON ("marche" means on) while hot water is off.

Second test: Hot water on (either on or on shcedule) and scheduled circulation OFF:
circulation is still off ("arrêt" means off) while hot water is on

I also tested with HOT WATER BOOST quick mode and both hot water and circulation are ON.
Normally, the circulation binary sensor should have the same behavior.
Maybe the behavior is different if you have circulation ? But as far as I know, there is no way to know if circulation is available or not, as far as there is at least hot water, everything is available at API side.

Well I am speaking about binary sensor ant it's status in HomeAssistant. I don't have option to operate circulation expect to schedule the time. I cannot say manually switch it off because there is no such option.
So If the hot water option is auto then circulation is working according the the it's schedule.
If I manually run the profile of boost water and the circulation is out of the schedule it will switch on. I i will remove boost hot water then circulation will switch off.
Whats the problem here why binary sensor in HA switching according to the schedule even if I changed hot water to off? This is the problem. Here the VR700 physically switch off the circulation pump but as I have some automation based on dwh_circulation like steering electric heater it becomes tricky why it behaves like that.

so basically you are saying, when Quick Boost is enabled and Circulation is turned on and overlapps the automatic time shedule for circulation it will turn cirucaltion off, even though the sheduled time setting is running?
Does this happen with HA only? Let say,you run quick boost on VaillantMultimatic App in the same scenario, will it turn off circulation when quick boost finishes?

so basically you are saying, when Quick Boost is enabled and Circulation is turned on and overlapps the automatic time shedule for circulation it will turn cirucaltion off, even though the sheduled time setting is running?

Nope, hot water boost quick mode set circulation ON (whatever the schedule is). When switching hot water boost off, the circulation (as well as hot water) switch back to their schedule.
@kalatos86 what does "ZALACZ" means ?
Did you try to turn your hot water ON (not the hot water boost) while the schedule of the circulation is off ? What does it do ? (in the mobile app).
-> When I'm doing that, my hot water is ON, but my circulation remains off.
Do you have any error in the integration ?

so basically you are saying, when Quick Boost is enabled and Circulation is turned on and overlapps the automatic time shedule for circulation it will turn cirucaltion off, even though the sheduled time setting is running?
Does this happen with HA only? Let say,you run quick boost on VaillantMultimatic App in the same scenario, will it turn off circulation when quick boost finishes?

It is working as the @thomasgermain wrote.

so basically you are saying, when Quick Boost is enabled and Circulation is turned on and overlapps the automatic time shedule for circulation it will turn cirucaltion off, even though the sheduled time setting is running?

Nope, hot water boost quick mode set circulation ON (whatever the schedule is). When switching hot water boost off, the circulation (as well as hot water) switch back to their schedule.
@kalatos86 what does "ZALACZ" means ? Did you try to turn your hot water ON (not the hot water boost) while the schedule of the circulation is off ? What does it do ? (in the mobile app). -> When I'm doing that, my hot water is ON, but my circulation remains off.

For me this works the same. But still why when the hot water is OFF and physical circulation pump is not running dwh_circulation parameter is changing according to it's schedule

Do you have any error in the integration ?

In the main logs I have only information about custom integration which is normal. Where to find details multimatic logs?

if we cannot turn the circulation on manually, can we create an entity containing the circulation schedule? If necessary (with a script / button), reset the schedule to turn off the circulation (manually) and set it again (automatically) to turn it on. I mean controlling the circulation independently of water heating.
I asked vaillant technical support and from the APP level, it is not possible to control the circulation outside the schedule. The ON / OFF / AUTO function is missing as in the other functionalities.

I wondering why this is missing from Vaillant :)

if we cannot turn the circulation on manually, can we create an entity containing the circulation schedule? If necessary (with a script / button), reset the schedule to turn off the circulation (manually) and set it again (automatically) to turn it on. I mean controlling the circulation independently of water heating. I asked vaillant technical support and from the APP level, it is not possible to control the circulation outside the schedule. The ON / OFF / AUTO function is missing as in the other functionalities.

You can have a look here https://github.com/thomasgermain/pymultiMATIC/ (this is the underlying connector the integration is using to get data). Using the Connector, you can basically do whatever requests you want. You could have 2 requests, one to set the schedule always ON and another one the set it always OFF


Shoeless engineer. (Loadout bug)

Description

Shoes did not spawn w/ loadout.
Reproduction

Was playing as CE and did not spawn with shoes. They were not spawned on the floor, either.
Screenshots

Additional context

it happens for all roles. it's just somethin fucky idk. entire rounds i've gone without realizing i had no shoes