Missing audio message beginning for the very first publication in the room

Describe the bug
I have a room with two participants. Autosubscribe is turned on for both sides. When a participant streams an audio publication, the listener often misses the first 1-2 seconds of the stream. I have observed this behavior in two combinations: iOS Client + iOS Client and iOS Client + GO SDK streaming a prerecorded audio.
Subsequent publications work fine, even after reconnection to the room.
Does LiveKit guarantee that an incoming publication is played from the very beginning?
Server

Version: [1.7.0]
Environment: Local Ubuntu
any other information about your deployment setup

Client

SDK: iOS v2.0.11, Go v2.2.0

To Reproduce
Steps to reproduce the behavior:

two clients are connected to room
1st begins transmission
2nd listens to and misses audio beginning for the very first publication (intermittent issue)

Expected behavior
All listeners are able to hear full audio message

Does LiveKit guarantee that an incoming publication is played from the very beginning?

No. LiveKit is a realtime system so there is no buffering of data. What that means is whenever the publisher is pushing out data, if the subscriber is not ready to receive them, they will be missed.
I suspect that's what you are seeing.. the publisher is playing out audio "too early", in the sense that the subscriber has yet to set up the subscription of that track.
We are making this a bit easier moving forward, with a new notification to the publisher that a newly published track has been subscribed to successfully.

I I have same problem just when new version will be ready that improved this subject ?

@davidzhao Is there any update for this:

We are making this a bit easier moving forward, with a new notification to the publisher that a newly published track has been subscribed to successfully.


New option: Custom API should only be triggered when the activity/availability is changed

For example, I configure a webhook in the Custom API for the Presence State Busy.
If my presence state changes from Available to Busy, the webhook is triggered successfully. However, this repeats every few seconds until the presence state changes again to not equal to Busy.
Depending on which target system/architecture/program is used this is very uncomfortable if the webhook is triggered permanently.
A solution for this would be a simple option with which you can specify that the Custom API is only triggered when the presence state changes.
The behavior is very well visible in the log:

I've pushed an update that should resolve this.. WIll only call custom API when it's changed.

Unfortunately, there are still problems with the function.
The API is no longer permanently triggered. But when changing to a new state and back again, the API is not triggered anymore.
Example:
Available API URI: https://testwebhook
Busy API URI: https://testwebhook2
Current Status: Busy

change to available -> API URI called
change to Busy -> API URI called > correct
change to Available -> API URI call is skipped -> not correct
change to Busy -> API URI call is skipped -> not correct


ModelProperty isHidden Does Nothing

Springfox 2.9.2
Use Case:
I am building a multi-tenant API where different tenants use the same base set of models, but they have access to different properties of those models based on a number of criteria. I'm setting up the swagger documentation to build dynamically via ModelBuilderPlugin, but the hidden property does not work as expected. Swagger-core @ApiModelProperty hidden attribute removes the property from the documentation, but the springfox ModelProperty.isHidden does not.

This was a misunderstanding from the documentation. I was implementing ModelBuilderPlugin and trying to mutate it's properties. The appropriate method is to implement ModelPropertyBuilderPlugin, which allows overriding of scanned model property values


Separating the qualifiers on arguments from the qualifiers on binders

We previously used the same type, aqual to represent both the qualifiers on binders as well as those on arguments. Although, the the legal qualifiers on arguments is strictly smaller than those on arguments.
This PR separates them into two types, aqual for argument qualifiers and bqual for binder qualifiers.
I have an everest green.

The changes look good, thanks Nik! Left a few comments.


https://swiftenv-api.fuller.li does not seem to be responding

https://swiftenv-api.fuller.li does not seem to be responding, making swiftenv fail when trying to install swift from Swift.org.

It's back up, closing.


Change TypeName Property with GetType Method

Change TypeName Property with GetType Method

[x] Change details added to Unreleased section of changelog.md?
[x] Added/updated documentation and descriptions in .schema.mof files where appropriate?
[x] Examples updated for both the single server and small farm templates in the examples folder?
[x] New/changed code adheres to [Style Guidelines]?(https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md)?
[x] Unit and Integration tests created/updated where possible?

This change is

Reviewed 4 of 9 files at r1.
Review status: 4 of 9 files reviewed at latest revision, 31 unresolved discussions.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 23 at r1 (raw file):

        $CreateFirewallRules,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 28 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 32 at r1 (raw file):

        $ServerProvisionOrder,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 110 at r1 (raw file):

        $CreateFirewallRules,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 115 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 119 at r1 (raw file):

        $ServerProvisionOrder,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 374 at r1 (raw file):

        $CreateFirewallRules,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 379 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 383 at r1 (raw file):

        $ServerProvisionOrder,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 15 at r1 (raw file):

        $ApplicationPool,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 19 at r1 (raw file):

        $DatabaseName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 23 at r1 (raw file):

        $DatabaseServer,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 28 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 88 at r1 (raw file):

        $ApplicationPool,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 92 at r1 (raw file):

        $DatabaseName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 96 at r1 (raw file):

        $DatabaseServer,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 101 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 185 at r1 (raw file):

        $ApplicationPool,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 189 at r1 (raw file):

        $DatabaseName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 193 at r1 (raw file):

        $DatabaseServer,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 198 at r1 (raw file):

        $Ensure = "Present",

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 11 at r1 (raw file):

        $UserProfileServiceAppName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 19 at r1 (raw file):

        $FarmAccount,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 23 at r1 (raw file):

        $RunOnlyWhenWriteable,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 60 at r1 (raw file):

            $domain = (Get-CimInstance -ClassName Win32_ComputerSystem).Domain
            $currentServer = "$($env:COMPUTERNAME).$domain"
            $syncService = $syncServices | Where-Object -FilterScript {

Something is not right here. A few lines above you populate the $syncService variable, then check if it is null and if so perform the exact same code to fill the variable.
In the old version, another call to Get-SPServiceInstance was done using the $currentServer variable. In this version, this variable is populated, but never used.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 112 at r1 (raw file):

        $UserProfileServiceAppName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 120 at r1 (raw file):

        $FarmAccount,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 124 at r1 (raw file):

        $RunOnlyWhenWriteable,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 261 at r1 (raw file):

        $UserProfileServiceAppName,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 269 at r1 (raw file):

        $FarmAccount,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 273 at r1 (raw file):

        $RunOnlyWhenWriteable,

        [parameter(Mandatory = $false)]

Why did you remove this line?

Comments from Reviewable

I thought in powershell guidelines for dsc that [parameter(Mandatory = $false)] should not be written, only the $true.
I write some PR in xSLQServer, and I had to remove each [parameter(Mandatory = $false)] :(
But if you prefer, I can revert this part.

Yes, I think we need a guideline for this. @luigilink can you submit and issue in the DscResources repo so we can clear this up :)
Not good to have contradicting styles :)

Issue added in DdscResources Repo

Fair point. Up until now we always added the Mandatory part, regardless it being true or false. Lets keep it in for now and see what the result of the other discussion is. If a new guideline is added, we will bulk change it in SharePointDsc

Reviewed 5 of 9 files at r1.
Review status: 6 of 9 files reviewed at latest revision, 31 unresolved discussions.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 23 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 28 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 32 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 110 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 115 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 119 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 374 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 379 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPDistributedCacheService/MSFT_SPDistributedCacheService.psm1, line 383 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 15 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 19 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 23 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 28 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 88 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 92 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 96 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 101 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 185 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 189 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 193 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPSubscriptionSettingsServiceApp/MSFT_SPSubscriptionSettingsServiceApp.psm1, line 198 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 11 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 19 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 23 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 60 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Something is not right here. A few lines above you populate the $syncService variable, then check if it is null and if so perform the exact same code to fill the variable.
>
> In the old version, another call to Get-SPServiceInstance was done using the $currentServer variable. In this version, this variable is populated, but never used.

Done.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 112 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 120 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 124 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 261 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 269 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Modules/SharePointDsc/DSCResources/MSFT_SPUserProfileSyncService/MSFT_SPUserProfileSyncService.psm1, line 273 at r1 (raw file):
Previously, ykuijs (Yorick Kuijs) wrote…
> Why did you remove this line?

Back to previous version.

Comments from Reviewable

Reviewed 1 of 9 files at r1, 3 of 3 files at r2.
Review status: all files reviewed at latest revision, 31 unresolved discussions.

Comments from Reviewable

@luigilink You need to acknowledge all discussions before I can complete the review :-)

The mandatory bit always being there was my doing, and I know I hit this with the powershell team during the OfficeOnlineServerDsc review as well and we decided to leave it there then as well. I'll add my two cents to the issue you opened but for the moment I want them there until we get a definite request to take them out.

No problem :)
I have already doing a roll back for the mandatory parameter equal to false.

Reviewed 4 of 9 files at r1, 3 of 3 files at r2.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable

Just need you to do a pull from dev and resolve the conflicts and we can push this in.

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 6 of 6 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Pi 100

We might need to hold off on merging this (or somehow feature flagging the entity relationship?), until 26th March when the table is added to the Delius database.

LGTM. Thanks. I'm interested in how the table/view r_level_2_head_of_level_2 is populated and maintained as staff are promoted / join or leave as PDU heads?

This will be managed by a new screen in NDelius. It should be kept up-to-date and correct as it will be used for operational contacts


Compile error due to tracy

Describe the bug
Seems that the tracy_catkin package does not install headers and libs into a install space as required.
To Reproduce
Steps to reproduce the behavior:

Setup catkin workspace in install mode (catkin config --install); may be also reproducable with an extending workspace
Install wavemap as described in the tutorial
Run catkin build wavemap_all

Expected behavior
No build errors
Observed outcome
Tracy headers are not available.
Screenshots
Errors     << wavemap:make /home/alex/er/logs/wavemap/build.make.229.log
/home/alex/er/src/wavemap/libraries/wavemap/src/data_structure/volumetric/hashed_chunked_wavelet_octree.cc:5:10: fatal error: tracy/Tracy.hpp: No such file or directory
    5 | #include <tracy/Tracy.hpp>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/wavemap.dir/src/data_structure/volumetric/hashed_chunked_wavelet_octree.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/home/alex/er/src/wavemap/libraries/wavemap/src/data_structure/volumetric/hashed_chunked_wavelet_octree_block.cc:3:10: fatal error: tracy/Tracy.hpp: No such file or directory
    3 | #include <tracy/Tracy.hpp>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/wavemap.dir/src/data_structure/volumetric/hashed_chunked_wavelet_octree_block.cc.o] Error 1
/home/alex/er/src/wavemap/libraries/wavemap/src/data_structure/volumetric/hashed_wavelet_octree.cc:5:10: fatal error: tracy/Tracy.hpp: No such file or directory
    5 | #include <tracy/Tracy.hpp>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/wavemap.dir/src/data_structure/volumetric/hashed_wavelet_octree.cc.o] Error 1
/home/alex/er/src/wavemap/libraries/wavemap/src/data_structure/volumetric/hashed_wavelet_octree_block.cc:3:10: fatal error: tracy/Tracy.hpp: No such file or directory
    3 | #include <tracy/Tracy.hpp>
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/wavemap.dir/src/data_structure/volumetric/hashed_wavelet_octree_block.cc.o] Error 1
make[1]: *** [CMakeFiles/wavemap.dir/all] Error 2
make: *** [all] Error 2
cd /home/alex/er/build/wavemap; catkin build --get-env wavemap | catkin env -si  /usr/bin/make --jobserver-fds=3,4 -j; cd -

System information (please complete if relevant):

OS: Ubuntu 18.04
Wavemap

install: native build, catkin install space (setup via: catkin config --install)
version: v1.5.1
cmake: 3.25.2

Thank you for reporting this bug and for opening a PR Alexander!
I updated the tracy_catkin package to include install rules. Wavemap's CI pipeline now also includes a job to test that catkin builds in --install mode succeed. Hopefully, this will avoid similar issues in the future.

Haven't tested it yet, but thanks for your awesome quick support!!

Welcome! Let me know in case any issues come up.


Request for Help: Dealing with timestamp timezone

Hi,
I'm struggling to understand how I can adjust the timestamp returned from my flux query to reflect my current timezone. I successfully get the timestamp via: -
FluxDateTime time = myResult.getValueByName("_time").getDateTime();
...but this give me the a GMT timestamp, whereas my local time is currently BST - i.e. +1 hour.
I am using...
timeSync("GMT0BST,M3.4.0/1,M10.4.0", "0.uk.pool.ntp.org", "1.uk.pool.ntp.org");
...in the code for both writing and query actions, but I can see from my influxdb data that the timestamp is GMT.
Any help much appreciated.

@prys,  it depends on what do you want to achieve.  If just printing, default format method uses strftime internally, which prints time in local timezone.
For other cases, you can use localtime to get tm in local TZ:
      FluxDateTime time = result.getValueByName("_time").getDateTime();
      time_t absTime = mktime(&time.value);
      tm *localTime = localtime(&absTime);

Ah thank you @vlastahajek. In fact, I couldn't find the correct format specifier to print local time, but never mind, what I needed was mktime which applies the correct zone information and using the tm structure helps me with comparison etc.
Many thanks.


Fix for ALBs with no listeners

Also overcome targetgroups exceptions

Fix #72

Current coverage is 75.53% (diff: 60.00%)

Merging #77 into master will decrease coverage by 0.27%

@@             master        #77   diff @@
==========================================
  Files             5          5
  Lines           463        466     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            351        352     +1
- Misses          112        114     +2
  Partials          0          0

Powered by Codecov. Last update ae5ac51...e7671be

:+1:

👍


Create draft release when v* (eg v0.1.0) tag is pushed

Also renames the artifact from "jar.zip" to something like "qupath-extension-wsinfer-main.zip"

https://github.com/github/docs/issues/15319

Should I be attempting the first release using this...?

May as well, if you remove SNAPSHOT from the gradle version and make a v0.1.0 tag it should make the draft for you


App: Fix avatars with no upper chest bone

(adding detail at request of @ahadshams)
Not all VRM armatures are the same - some models make use of optional bones in the VRM spec.
The most frequent appears to be an unincluded upper chest bone (which currently our in-house avatars do have).
Equipping an avatar without optional bones at the moment results in it teleporting (to origin?) and not equipping.
https://user-images.githubusercontent.com/80061436/139651035-96388c69-cbd2-4b3e-95a6-37c3e6b51aac.mp4
The avatar is valid as per VRM spec, but doesn't contain (notably) finger bones, as well as eyes, toes, or an upper chest bone.

Can this be closed now?

This appears to be working (at the moment). I'm not sure on the specifics of #1744 fix, but both appear to be cleared.


Translation

We should somehow implement translation in backend

you mean for errors?
i'd suggest using error keys and an english error message
console can then use the keys for translation
any other ideas?

i think we also need it for the emails?


feat: native Terraform test framework

what

Moved the default boilerplate Terratest into its own folder
Added new main.tftest.hcl for the build in Terraform test framework
main.tftest contains the integration tests, whereas the other test I had cpu-compatability is a unit test (planning)
The integration test needs the /setup and /test-harness module for setup and further validation using data sources.

Test output

I could do more unit tests, but this module is pretty straightforward and simple, and I got the gist of different scenarios. Would appreciate second pairs of eyes to see if there's other things that would be worth testing here.
Most of the tests is just checking that it exists / connected together, not necessarily any specific configurations because there's not much in this module.
references

https://www.notion.so/masterpoint/Terraform-Testing-Investigation-Pipeline-1907ad6d5a4944b5b356e90fde3e2ee9

Summary by CodeRabbit

New Features

Introduced comprehensive tests for validating EC2 instance compatibility with specified architectures.
Added integration tests for the SSM Agent module, focusing on resource validation.
Implemented Terraform configurations for random number generation and AWS data retrieval.

Bug Fixes

Enhanced error handling and validation in existing tests.

Documentation

Updated variable declarations for improved configuration management.

@oycyc looks good, I left a couple of comments/thoughts. I agree it's a simple module, and I don't think we should overload it with tests. I guess our main goal here is to establish a standardized testing framework and pipeline so it can be spread across other modules.
Also, I see that terratest was added in 2020, which definitely requires revisiting. Do you know if there was any discussion around it? Are we going to support both? Do we expect to replace it?

Terratest right now is just pretty empty, just runs an apply and confirms some output. I think we can remove it since we're not going to support it and it's pretty empty. We're not supporting both.

@oycyc looks good, I left a couple of comments/thoughts. I agree it's a simple module, and I don't think we should overload it with tests. I guess our main goal here is to establish a standardized testing framework and pipeline so it can be spread across other modules.

even for unit tests (plans), it requires AWS credentials to call the API and do a plan. what do you think would be the best way to go about this? I'm thinking we set up OIDC connection in our AWS account (testing account maybe?) and use it with GitHub actions? or should we just use a static access key.

even for unit tests (plans), it requires AWS credentials to call the API and do a plan. what do you think would be the best way to go about this? I'm thinking we set up OIDC connection in our AWS account (testing account maybe?) and use it with GitHub actions? or should we just use a static access key.

Definitely OIDC. Yeah, we can utilize testing account for these purposes.
The question is how we'd like to manage the resources required for tests setup as code. We have mp-infra repo, but it's quite messy. The components directory is organized for use by Terraform Controller, and we're not going to proceed with this project, unfortunately. However, you can add OIDC IAC there as a vanilla Terraform code, I believe, and we can discuss further repo reorganization on the next internal call.

@gberenice @oycyc -- First off, well done on both this initial implementation and the back+forth discussion above. Love to see it!
@gberenice I like you last comment (right above this one) and I agree. We just want structure + process to come out of this PR. These tests might not be the most useful to due to the nature of the PR, but in the long run we need to start building up this practice and ensuring we're testing in ALL of our TF code where it makes sense.
Let me also address each of your "includes":

git structure for test files/configs
Yes, we should understand this and it should be repeatable + leave us open to future expansion. It seems like this is relatively straight forward, so I think we're all good here.

configuring access to AWS (and Spacelift in the nearest future)
@oycyc is going to work on this. Instead of doing that for this PR, I am going to say that we ship this and then we follow up with updating it with a Pipeline + OIDC usage. That way we can ship a smaller PR and follow up as we add on the additional, useful automation.

adding pipeline and configuring it to run for each PR
Same as above -- I wanna add this as a follow up PR.

start writing our own best practices if we see the lack of those among the community
There is 100% a lack of this in the community and I think this is something I'm very interested in. This is something for both of you to think on: What blog posts, best practice guides, or OSS projects that we might be able to put together to help out the community + our selves. This is a topic I want us to get GREAT at, have strong opinions, and be thought leaders in, so I am glad we're finally moving this forward. Let's be sure to discuss this live at some point soon -- Maybe we schedule a separate meeting once we get these tests + the corresponding automation in place?

@oycyc I will read over your actual code now and give this a proper review, but I say we push this forward and get it merged ASAP so we have something to start with and then we can iterate on the automation next like I know you're already working on.


Update stable version in repo from 0.2.0 to 0.2.2-beta.0

Think about update stable version to 0.2.2-beta.0
Version: stable=0.2.0 (179 days old) => latest=0.2.2-beta.0 (15 days old)
Installs: stable=53 (66.25%), latest=19 (23.75%), total=80
Click to edit

https://github.com/ioBroker/ioBroker.repositories/pull/922
https://github.com/iobroker-community-adapters/ioBroker.knmi-weather/commit/7a88040a33bb0930726483e8a23e193ccd7f6764


muzzle flash effect looks light bullet is going through the shooters back

Description
probably an upstream issue but eh rmc has a bit more focus on guns

actually the bullet physically spawns there, will only be fixable when players colliding with eachother is real


Create 0000-01-02-TWoname.md

Created a pull request

Was that right

I hope it's well

great

So what do I do next

that's all


"Station is not in Geostationary Orbit!"

Version of Advanced Rocketry
1.12.2 2.0.0-247
Have you verified this is an issue in the latest unstable build
N
Version of LibVulpes
1.12.2-0.4.2-83
Version of Minecraft
1.12.2 Forge build <IP_ADDRESS>47
Crash report or log (if applicable)
http://pastebin.com is a good place to put them
crash reports that are put in the issue itself are
hard to read
[insert here] N/A; not a crash
Description of the problem
Simply try to link a space elevator on a station to an elevator on any planet. and an error in chat will say "Station is not in Geostationary Orbit!"
Also, there is no slot in the elevator GUI for the chip nor is there a wiki article telling people why this occurs or an update to said article from the link provided in the Curseforge page.

Stuff changed since 2.0.0. Your station needs to be in geostationary orbit (wow, it says that in chat, who knew?) and the station chip is currently unused but may be getting a use later.

How do I get the station to Geostat orbit anyway?

You look up what geostationary orbit is, then move your station there.

Last I checked, there was nothing in the creative inventory that moves the station's orbit aside from the warp drive.
How else would I move it?

http://arwiki.dmodoomsirius.me/AdvancedRocketry/1.12.2/blocks/SpaceStationControllers.php

Thanks!

Thanks!

and how did you do it?


Does Not Support Accessories and the Curios Compat Layer

When Accessories and Curios Compat Layer for Accessories are both installed and enabled, this mod then requires Curios 9.0.10+ when the Curios Compat is only 9.0.5
I saw you have dependencies for both Curios and Accessories, I wonder if you have Curios set as a higher priority than Accessories? Causing it to use Curios instead of Accessories, but since the Compat Layer is a lower level than what you require, it does not work.

EDIT: When i disabled the Compat Layer, the mod loaded, but then all my Curios mods stopped working.

Why does the curios compat layer use the mod id curios... that's frustrating. Yes it has to do with priorities. This is an easy fix.

I think the only issue here is the version requirement. The accessories compat is set to be higher priority than curios.


Mirror sql joins

Closed previous PR as it had some extraneous commits from local WIP branch. This one should be easier to follow.
As discussed in Joins and nested tuples here is the implementation I've been working on. In a nutshell this PR enhances existing Quill join queries based on nested tuples with an alternate join syntax that mirrors that of sql.

@fwbrasil build still failing on Cassandra download

Service 'setup' failed to build: The command '/bin/sh -c cd /opt ;      curl http://mirror.nbtelecom.com.br/apache/cassandra/2.1.12/apache-cassandra-2.1.12-bin.tar.gz | tar zx' returned a non-zero code: 2

Feel free to review the commits in the meantime ;-)

The build is fixed on master, could you rebase your branch? I'm going to continue the review today in the evening.

@godenji are you on gitter? I just pinged you there.

Current coverage is 98.29%

Merging #149 into master will decrease coverage by -0.20% as of 5ec43d6

Powered by Codecov. Updated on successful CI builds.

@fwbrasil build passes, looks like missed some test coverage though -- ironically enough I removed a test pre-PR that covers a missing case; I'll put it back ;-)

@godenji LGTM, the only missing bit is the documentation now.

@fwbrasil just updated the README.

@godenji the readme changes aren't compiling: https://travis-ci.org/getquill/quill#L6089

@fwbrasil fixed. Is there a way to run TutMain locally? Would be nice to run a testQuick on a single file rather than kicking off a full Travis build.

@godenji you can use sbt tut

@fwbrasil nice, thanks, just ran locally. More errors, sigh, blind coding is the bane of my existence ;-)
Fixed, now I know it passes...I'll wait for current build to fail and then push changes to my branch.

@godenji tut is a blessing, it's impressive how many times I write invalid code as documentation. :)

@fwbrasil I was actually surprised the readme was typechecked -- agreed, nice feature.


No module named 'pkg_resources' in json_schema - new osx install

[x] I am on the latest Poetry version.

[x] I have searched the issues of this repo and believe that this is not a duplicate.

[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: OSX 10.14.2

Poetry version: 0.12.11

pyproject.toml created by init, no packages added

Issue

OS-X with macports & py2.7/3.6/3.7 installed (plus the various pips)
Installed poetry as recommended (using /opt/local/bin/python3.6 as the interpreter)
Added poetry to path
Nearly all commands crash the same way

$ poetry version -vvv
$ poetry debug:info -vvv
$ poetry add requests -vvv

All generate the same output:
------

[ModuleNotFoundError]
No module named 'pkg_resources'

Exception trace:
 /Users/andrew/.poetry/lib/poetry/_vendor/py3.6/cleo/application.py in run() at line 94
   status_code = self.do_run(input_, output_)
 /Users/andrew/.poetry/lib/poetry/console/application.py in do_run() at line 88
   return super(Application, self).do_run(i, o)
 /Users/andrew/.poetry/lib/poetry/_vendor/py3.6/cleo/application.py in do_run() at line 197
   status_code = command.run(input_, output_)
 /Users/andrew/.poetry/lib/poetry/console/commands/command.py in run() at line 77
   return super(BaseCommand, self).run(i, o)
 /Users/andrew/.poetry/lib/poetry/_vendor/py3.6/cleo/commands/base_command.py in run() at line 136
   self.initialize(input_, output_)
 /Users/andrew/.poetry/lib/poetry/console/commands/env_command.py in initialize() at line 18
   current_env = Env.get(self.poetry.file.parent)
 /Users/andrew/.poetry/lib/poetry/console/commands/command.py in poetry() at line 62
   return self.get_application().poetry
 /Users/andrew/.poetry/lib/poetry/console/application.py in poetry() at line 55
   from poetry.poetry import Poetry
 /Users/andrew/.poetry/lib/poetry/poetry.py in <module>() at line 11
   from .json import validate_object
 /Users/andrew/.poetry/lib/poetry/json/__init__.py in <module>() at line 4
   import jsonschema
 /Users/andrew/.poetry/lib/poetry/_vendor/py3.6/jsonschema/__init__.py in <module>() at line 32
   from pkg_resources import get_distribution

debug:info

I'm pretty sure pipenv also requires you to have pip installed, so I don't think using pipenv will solve this issue for you: https://pipenv.readthedocs.io/en/latest/install/#make-sure-you-ve-got-python-pip

Another reason the pkg_resource error occurs is when you're running the wrong Python.
I had Python 3.7.3 altinstalled and an alias of python=/path.../bin/python3.7.3.
However /usr/bin/env still found the system Python 2.7.
This became obvious when doing the poetry version -vvv command above and seeing poetry was in _vendor/py2.7/ and not _vendor/py3.7/.
Ended up installing pyenv and activating 3.7.3 for the project.


Unable to restore from backups

Unfortunately it seems that the backed up archives are not able to be restored..
ghcr.io/tensorchord/cloudnative-pgvecto.rs:16.2-v0.2.1
Cluster CRD:
---
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster16-vector
  namespace: databases
spec:
  instances: 2
  imageName: ghcr.io/tensorchord/cloudnative-pgvecto.rs:16.2-v0.2.1
  primaryUpdateStrategy: unsupervised
  storage:
    size: 15Gi
    storageClass: local-hostpath
  superuserSecret:
    name: cloudnative-pg-secret
  enableSuperuserAccess: true
  resources:
    requests:
      memory: 1Gi
    limits:
      memory: 2Gi
#  bootstrap:
#    initdb:
#      postInitSQL:
#        - ALTER SYSTEM SET search_path TO "$user", public, vectors;
#        - CREATE EXTENSION IF NOT EXISTS "vectors";
  bootstrap:
    recovery:
      source: &previousCluster postgres-vector-v11
  affinity:
    enablePodAntiAffinity: true
    topologyKey: kubernetes.io/hostname
    podAntiAffinityType: required
    nodeSelector:
      kubernetes.io/arch: amd64

  postgresql:
    shared_preload_libraries:
      - "vectors.so"
    enableAlterSystem: true
    parameters:
      max_connections: "600"
      shared_buffers: 512MB
  monitoring:
    enablePodMonitor: true
    # https://github.com/cloudnative-pg/cloudnative-pg/issues/2501
    podMonitorMetricRelabelings:
        - { sourceLabels: [ "cluster" ], targetLabel: cnpg_cluster, action: replace }
        - { regex: cluster, action: labeldrop }
  backup:
    retentionPolicy: "30d"
    barmanObjectStore:
      wal:
        compression: bzip2
        maxParallel: 4
      data:
        compression: bzip2
      destinationPath: s3://cnpg-main/
      endpointURL: https://s3.skym.fi
      serverName: &currentCluster postgres-vector-v12
      s3Credentials:
        accessKeyId:
          name: cloudnative-pg-secret
          key: aws-access-key-id
        secretAccessKey:
          name: cloudnative-pg-secret
          key: aws-secret-access-key
  externalClusters:
    - name: *previousCluster
      barmanObjectStore:
        wal:
          compression: bzip2
          maxParallel: 8
        destinationPath: s3://cnpg-main/
        endpointURL: https://s3.skym.fi
        s3Credentials:
          accessKeyId:
            name: cloudnative-pg-secret
            key: aws-access-key-id
          secretAccessKey:
            name: cloudnative-pg-secret
            key: aws-secret-access-key

{"level":"info","ts":"2024-10-16T09:49:40Z","msg":"barman-cloud-check-wal-archive checking the first wal","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:40Z","msg":"Recovering from external cluster","logging_pod":"cluster16-vector-1-full-recovery","sourceName":"postgres-vector-v11"}
{"level":"info","ts":"2024-10-16T09:49:42Z","msg":"Target backup found","logging_pod":"cluster16-vector-1-full-recovery","backup":{"backup_name":"backup-20241016083833","backup_label":"'START WAL LOCATION: 46/8E0000E8 (file<PHONE_NUMBER>0000460000008E)\\nCHECKPOINT LOCATION: 46/8F000060\\nBACKUP METHOD: streamed\\nBACKUP FROM: standby\\nSTART TIME: 2024-10-16 08:38:34 UTC\\nLABEL: Barman backup cloud 20241016T083833\\nSTART TIMELINE: 7\\n'","begin_time":"Wed Oct 16 08:38:34 2024","end_time":"Wed Oct 16 08:38:56 2024","BeginTime":"2024-10-16T08:38:34Z","EndTime":"2024-10-16T08:38:56Z","begin_wal":"00000007000000460000008E","end_wal":"000000070000004600000090","begin_xlog":"46/8E0000E8","end_xlog":"46/90000000","systemid":"7368693795026370580","backup_id":"20241016T083833","error":"","timeline":7}}
{"level":"info","ts":"2024-10-16T09:49:42Z","msg":"Starting barman-cloud-restore","logging_pod":"cluster16-vector-1-full-recovery","options":["--endpoint-url","https://s3.skym.fi","s3://cnpg-main/","postgres-vector-v11","20241016T083833","--cloud-provider","aws-s3","/var/lib/postgresql/data/pgdata"]}
{"level":"info","ts":"2024-10-16T09:49:53Z","msg":"Restore completed","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:53Z","msg":"Creating new data directory","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/controller/recovery/datadir_1530716887","initDbOptions":["--username","postgres","-D","/controller/recovery/datadir_1530716887","--no-sync"]}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"initdb","msg":"The files belonging to this database system will be owned by user \"postgres\".\nThis user must also own the server process.\n\nThe database cluster will be initialized with locale \"en_US.utf8\".\nThe default database encoding has accordingly been set to \"UTF8\".\nThe default text search configuration will be set to \"english\".\n\nData page checksums are disabled.\n\nfixing permissions on existing directory /controller/recovery/datadir_1530716887 ... ok\ncreating subdirectories ... ok\nselecting dynamic shared memory implementation ... posix\nselecting default max_connections ... 100\nselecting default shared_buffers ... 128MB\nselecting default time zone ... Etc/UTC\ncreating configuration files ... ok\nrunning bootstrap script ... ok\nperforming post-bootstrap initialization ... ok\n\nSync to disk skipped.\nThe data directory might become corrupt if the operating system crashes.\n\n\nSuccess. You can now start the database server using:\n\n    pg_ctl -D /controller/recovery/datadir_1530716887 -l logfile start\n\n","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"initdb","msg":"initdb: warning: enabling \"trust\" authentication for local connections\ninitdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.\n","pipe":"stderr","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Installed configuration file","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/controller/recovery/datadir_1530716887","filename":"pg_hba.conf"}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Installed configuration file","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/controller/recovery/datadir_1530716887","filename":"pg_ident.conf"}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Installed configuration file","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/controller/recovery/datadir_1530716887","filename":"custom.conf"}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Generated recovery configuration","logging_pod":"cluster16-vector-1-full-recovery","configuration":"recovery_target_action = promote\nrestore_command = 'barman-cloud-wal-restore --endpoint-url https://s3.skym.fi s3://cnpg-main/ postgres-vector-v11 --cloud-provider aws-s3 %f %p'\n"}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Aligned PostgreSQL configuration to satisfy both pg_controldata and cluster spec","logging_pod":"cluster16-vector-1-full-recovery","enforcedParams":{"max_connections":"600","max_locks_per_transaction":"64","max_prepared_transactions":"0","max_wal_senders":"10","max_worker_processes":"32"},"controldataParams":{"max_connections":600,"max_locks_per_transaction":64,"max_prepared_transactions":0,"max_wal_senders":10,"max_worker_processes":32},"clusterParams":{"max_connections":600,"max_worker_processes":32}}
{"level":"info","ts":"2024-10-16T09:49:54Z","msg":"Starting up instance","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","options":["start","-w","-D","/var/lib/postgresql/data/pgdata","-o","-c port=5432 -c unix_socket_directories=/controller/run","-t 40000000","-o","-c listen_addresses='<IP_ADDRESS>'"]}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"pg_ctl","msg":"waiting for server to start....2024-10-16 09:49:54.578 UTC [38] LOG:  redirecting log output to logging collector process","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"pg_ctl","msg":"2024-10-16 09:49:54.578 UTC [38] HINT:  Future log output will appear in directory \"/controller/log\".","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.578 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"1","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"ending log output to stderr","hint":"Future log output will go to log destination \"csvlog\".","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.578 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"2","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting PostgreSQL 16.2 (Debian 16.2-1.pgdg110+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.578 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"3","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv4 address \"<IP_ADDRESS>\", port 5432","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.582 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"4","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on Unix socket \"/controller/run/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.587 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"1","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system was interrupted while in recovery at log time 2024-10-16 07:51:31 UTC","hint":"If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:54Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:54.587 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"2","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"creating missing WAL directory \"pg_wal/archive_status\"","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:55Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:55.732 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"3","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting archive recovery","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:55Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:55.737 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"4","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting backup recovery with redo LSN 46/8E0000E8, checkpoint LSN 46/8F000060, on timeline ID 7","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:56Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:56.254 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"5","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007.history\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:56Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:56.852 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"6","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007000000460000008F\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:57Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:57.509 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"7","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007000000460000008E\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:58Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:58.720 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"8","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo starts at 46/8E0000E8","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:59.270 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"9","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007000000460000008F\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:59.831 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"10","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"completed backup recovery with redo LSN 46/8E0000E8 and end LSN 46/90000000","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:59.831 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"11","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"consistent recovery state reached at 46/90000000","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:49:59.831 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"5","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept read-only connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"pg_ctl","msg":"..... done","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:49:59Z","logger":"pg_ctl","msg":"server started","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:00Z","msg":"Checking if the server is still in recovery","logging_pod":"cluster16-vector-1-full-recovery","recovery":true}
{"level":"info","ts":"2024-10-16T09:50:00Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:00.316 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"12","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"redo done at 46/8F000110 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 1.59 s","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:00Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:00.957 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"13","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007000000460000008F\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:01Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:01.506 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"14","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"selected new timeline ID: 8","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.112 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"15","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"restored log file \"00000007.history\" from archive","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.120 UTC","process_id":"42","session_id":"670f8c42.2a","session_line_num":"16","session_start_time":"2024-10-16 09:49:54 UTC","virtual_transaction_id":"1/0","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive recovery complete","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.122 UTC","process_id":"40","session_id":"670f8c42.28","session_line_num":"1","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: end-of-recovery immediate wait","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.132 UTC","process_id":"40","session_id":"670f8c42.28","session_line_num":"2","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.004 s, total=0.013 s; sync files=3, longest=0.002 s, average=0.002 s; distance=32767 kB, estimate=32767 kB; lsn=46/90000028, redo lsn=46/90000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.138 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"6","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:02Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:02.139 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"1","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:03Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:03.140 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"2","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:04Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:04.141 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"3","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:04Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:04.141 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"4","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000008.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","msg":"Checking if the server is still in recovery","logging_pod":"cluster16-vector-1-full-recovery","recovery":false}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"pg_ctl","msg":"pg_ctl: server is running (PID: 38)\n/usr/lib/postgresql/16/bin/postgres \"-D\" \"/var/lib/postgresql/data/pgdata\" \"-c\" \"port=5432\" \"-c\" \"unix_socket_directories=/controller/run\" \"-c\" \"listen_addresses=<IP_ADDRESS>\"\n","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:05Z","msg":"Shutting down instance","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","mode":"fast","timeout":null}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.047 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"7","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"received fast shutdown request","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.049 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"8","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"aborting any active transactions","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.050 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"9","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"background worker \"logical replication launcher\" (PID 86) exited with exit code 1","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.052 UTC","process_id":"40","session_id":"670f8c42.28","session_line_num":"3","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"shutting down","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.129 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"5","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.129 UTC","process_id":"40","session_id":"670f8c42.28","session_line_num":"4","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: shutdown immediate","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.199 UTC","process_id":"40","session_id":"670f8c42.28","session_line_num":"5","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.071 s; sync files=0, longest=0.000 s, average=0.000 s; distance=16384 kB, estimate=31129 kB; lsn=46/91000028, redo lsn=46/91000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:05Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:05.202 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"6","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:06Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:06.203 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"7","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:06Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:06.203 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"8","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000008.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:06Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:06.204 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"9","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:07Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:07.205 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"10","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.206 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"11","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.206 UTC","process_id":"85","session_id":"670f8c4a.55","session_line_num":"12","session_start_time":"2024-10-16 09:50:02 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000008.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.216 UTC","process_id":"38","session_id":"670f8c42.26","session_line_num":"10","session_start_time":"2024-10-16 09:49:54 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is shut down","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"waiting for server to shut down....... done","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"server stopped","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Exited log pipe","fileName":"/controller/log/postgres.csv","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Updated replication settings","logging_pod":"cluster16-vector-1-full-recovery","filename":"override.conf"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Starting up instance","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","options":["start","-w","-D","/var/lib/postgresql/data/pgdata","-o","-c port=5432 -c unix_socket_directories=/controller/run","-t 40000000","-o","-c listen_addresses='<IP_ADDRESS>'"]}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"waiting for server to start....2024-10-16 09:50:08.321 UTC [102] LOG:  redirecting log output to logging collector process","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"2024-10-16 09:50:08.321 UTC [102] HINT:  Future log output will appear in directory \"/controller/log\".","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.321 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"1","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"ending log output to stderr","hint":"Future log output will go to log destination \"csvlog\".","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.321 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"2","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"starting PostgreSQL 16.2 (Debian 16.2-1.pgdg110+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.321 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"3","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on IPv4 address \"<IP_ADDRESS>\", port 5432","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.324 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"4","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"listening on Unix socket \"/controller/run/.s.PGSQL.5432\"","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.329 UTC","process_id":"106","session_id":"670f8c50.6a","session_line_num":"1","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system was shut down at 2024-10-16 09:50:05 UTC","backend_type":"startup","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.334 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"5","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is ready to accept connections","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.335 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"1","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":" done","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"server started","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Configuring new PostgreSQL instance","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Executing post-init SQL instructions","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Executing post-init template SQL instructions","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"pg_ctl","msg":"pg_ctl: server is running (PID: 102)\n/usr/lib/postgresql/16/bin/postgres \"-D\" \"/var/lib/postgresql/data/pgdata\" \"-c\" \"port=5432\" \"-c\" \"unix_socket_directories=/controller/run\" \"-c\" \"listen_addresses=<IP_ADDRESS>\"\n","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:08Z","msg":"Shutting down instance","logging_pod":"cluster16-vector-1-full-recovery","pgdata":"/var/lib/postgresql/data/pgdata","mode":"fast","timeout":null}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.488 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"6","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"received fast shutdown request","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.490 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"7","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"aborting any active transactions","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.492 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"8","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"background worker \"logical replication launcher\" (PID 115) exited with exit code 1","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.494 UTC","process_id":"104","session_id":"670f8c50.68","session_line_num":"1","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"shutting down","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:08Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:08.565 UTC","process_id":"104","session_id":"670f8c50.68","session_line_num":"2","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint starting: shutdown immediate","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:09Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:09.336 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"2","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:09Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:09.603 UTC","process_id":"104","session_id":"670f8c50.68","session_line_num":"3","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.004 s, total=1.041 s; sync files=4, longest=0.002 s, average=0.001 s; distance=16384 kB, estimate=16384 kB; lsn=46/92000028, redo lsn=46/92000028","backend_type":"checkpointer","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:09Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:09.606 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"3","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:09Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:09.606 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"4","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000008.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:09Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:09.607 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"5","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:10Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:10.608 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"6","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:11Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:11.609 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"7","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"archive command failed with exit code 1","detail":"The failed archive command was: false","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:11Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:11.609 UTC","process_id":"114","session_id":"670f8c50.72","session_line_num":"8","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"WARNING","sql_state_code":"01000","message":"archiving write-ahead log file \"00000008.history\" failed too many times, will try again later","backend_type":"archiver","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:11Z","logger":"postgres","msg":"record","logging_pod":"cluster16-vector-1-full-recovery","record":{"log_time":"2024-10-16 09:50:11.619 UTC","process_id":"102","session_id":"670f8c50.66","session_line_num":"9","session_start_time":"2024-10-16 09:50:08 UTC","transaction_id":"0","error_severity":"LOG","sql_state_code":"00000","message":"database system is shut down","backend_type":"postmaster","query_id":"0"}}
{"level":"info","ts":"2024-10-16T09:50:11Z","logger":"pg_ctl","msg":"waiting for server to shut down....... done","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:11Z","logger":"pg_ctl","msg":"server stopped","pipe":"stdout","logging_pod":"cluster16-vector-1-full-recovery"}
{"level":"info","ts":"2024-10-16T09:50:11Z","msg":"Exited log pipe","fileName":"/controller/log/postgres.csv","logging_pod":"cluster16-vector-1-full-recovery"}

There's errors in there, but none that are particularly clear about what's going on (as far as I can see). Can you give some more detail about what the Cluster resource does, jobs/pods that are going around, logs from the cnpg operator, etc?

I think this is the problem of the name being too long?

We have patched it in https://github.com/tensorchord/pgvecto.rs/pull/588. However updating version with immich database is quite complicated. We'll work with immich when we have a new production release ready

@beyondwatts Are you experiencing problem at restore or backup?

This was after deleting a pod & pvc in the cluster so I guess restoring

Came here after running into the same issue, for the same reason (immich only supporting <0.4.0) and my HA postgres deployment can't scale or recover a secondary node because of this error.


LGitLibrary needs shutdown

LGitLibrary needs a proper shutdown. The absence of it can cause VM crashes in the next image session (at least on Linux VM)

fixed now


Specify the region to be registered for RMA by the -R option.

Currently -R is just a placeholder. It should define the region to be registered for RMA.

scif_register() fails w/ Bad address when an mmap()-ed region is provided. The cause for this might be the get_user_pages() which cannot be combined w/ the remap_pfn_range() called by the mmap() (https://www.spinics.net/lists/linux-rdma/msg70488.html).
As a result the implementation of scif_register() in mpss modules need to change if possible.


Modify GitHub URL

I was unable to make it work with /organizations/. Only /orgs/ worked.

@SvenAelterman : Thanks for your contribution! The author(s) have been notified to review your proposed change. @Zhchia

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Senior Solution Architect (Customer Implementation) @ MATTR

Senior Solution Architect (Customer Implementation)
Job type
Full-time
Location
Auckland, New Zealand
Company
MATTR
Job description
As a Solution Architect, you will be part of the team who are creating the MATTR platform and helping to establish MATTR as a leader in the world of digital trust. We are looking for someone to work with our customers understanding and interpreting their business needs and drivers and matching those with our cutting-edge solutions
Senior Solution Architect (Customer Implementation)
Contact
Ivan Cheng (程逸凡)

你好大佬 @sschengyf ，请问在新西兰，除了AWS和Microsoft，还有那些公司愿意招应届毕业生做 Solution Architect呢？
我对架构挺感兴趣，但不确定是否应该毕业了马上就去做云，还是老老实实做几年开发


Decompiler: ARM Cortex relative loads

Many ARM Cortex binaries never access any address directly and use PC relative loads instead where they load the actual address from data words that are located after each function. This is what that looks like:
                             **************************************************************
                             *                          FUNCTION                          *
                             **************************************************************
                             undefined FUN_00001484()
             undefined         r0:1           <RETURN>
                             FUN_00001484                                    XREF[1]:     FUN_000082f0:0000832c(c)
        00001484 05 4a           ldr        r2,[DAT_0000149c]                                = 40002400h
        00001486 51 68           ldr        r1,[r2,#offset ADC.CR0]
        00001488 ff 23           movs       r3,#0xff
        0000148a f1 33           adds       r3,#0xf1
        0000148c c0 06           lsls       r0,r0,#0x1b
        0000148e 99 43           bics       r1,r3
        00001490 c0 0d           lsrs       r0,r0,#0x17
        00001492 01 43           orrs       r1,r0
        00001494 51 60           str        r1,[r2,#offset ADC.CR0]
        00001496 00 20           movs       r0,#0x0
        00001498 70 47           bx         lr
        0000149a 00              ??         00h
        0000149b 00              ??         00h
                             DAT_0000149c                                    XREF[1]:     FUN_00001484:00001484(R)
        0000149c 00 24 00 40     undefined4 40002400h                                        ?  ->  40002400

I've named all my peripherals and registers and marked them as volatile and as you can see, the disassembly detects and shows that correctly as "ADC.CR0". Unfortunately, the decompiler does not understand that and creates code like this instead:
undefined4 FUN_00001484(int param_1)
{
  *(uint *)(DAT_0000149c + 4) =
       *(uint *)(DAT_0000149c + 4) & 0xfffffe0f | (uint)(param_1 << 0x1b) >> 0x17;
  return 0;
}

I have seen others talk about read_volatile and write_volatile disassembler output and it seems to be working for them. So what's the issue here?

The issue was simply, that my flash was mapped as writable. Making it read-only made the de-compilation better in all kinds of ways.


picocli treats passwords and session-key input as direct parameters (strings) rather than indirect (file references)

The spec refers to both SESSIONKEY and PASSWORD data types as indirect data types, not direct data types.
However, I notice that the picocli for sop accepts passwords and session keys directly on the command line.  For example:
printf abc123 > password.txt
echo test | sop encrypt --password password.txt

will use the literal string password.txt as the password instead of abc123.
This happens for session-key input as well as passwords (i note that it does treat session-key output correctly, as an indirect parameter).  See discussion at https://gitlab.com/dkg/openpgp-stateless-cli/-/issues/45 about how this was never extremely clear in the spec, sorry about that!
Here are two example lines that treat the incoming parameters as strings:
https://github.com/pgpainless/sop-java/blob/a2f20693800a7e45d6f8613c09419a3c0773e9cd/sop-java-picocli/src/main/java/sop/cli/picocli/commands/EncryptCmd.java#L39
https://github.com/pgpainless/sop-java/blob/a2f20693800a7e45d6f8613c09419a3c0773e9cd/sop-java-picocli/src/main/java/sop/cli/picocli/commands/DecryptCmd.java#L52

I think what particularly contributes to this misunderstanding is the following wording:
sop encrypt [--as={binary|text|mime}]
       [--no-armor]
       [--with-password=PASSWORD...]    <-- PASSWORD
       [--sign-with=KEYS...]
       [--] [CERTS...]

...

--with-password enables symmetric encryption (and can be used
   multiple times if multiple passwords are desired).  If sop encrypt
   encounters a PASSWORD which is not a valid UTF-8 string        <-- PASSWORD
   ([Section 8.7](https://datatracker.ietf.org/doc/html/draft-dkg-openpgp-stateless-cli-03#section-8.7)), or is otherwise not robust in its representation to
   humans, it fails with PASSWORD_NOT_HUMAN_READABLE.  If sop encrypt
   sees trailing whitespace at the end of a PASSWORD, it will trim the
   trailing whitespace before using the password.  See [Section 8.8](https://datatracker.ietf.org/doc/html/draft-dkg-openpgp-stateless-cli-03#section-8.8) for
   more discussion about passwords.

In the argument list the filename is called PASSWORD. Later in the text, the content of the PASSWORD file is being addressed with the name PASSWORD. This suggests that PASSWORD is a string, not a file.


How do I change rowHeight responsively?

Hi I just brought this up in a different issue. But it should have its own. Can you give the shortest example of how you might change the row height according to breakpoints in a responsive grid?
Thanks.

Listen to the breakpoint in the params of RRGL's onBreakpointChange. Use that to setState() from some enum to change rowHeight.


Saving a predefined object with serializer

Hi,
I have read all the tutorials about serialization, but I found that it is still difficult to understand (sorry).
Is there a way to save the state of our own class to the serializer? I tried to define "serialize" method in my object but it doesn't work.
What I am seeking is to save some of other data collected during training other than parameter, so the model can load those data for testing right away.
obj = SomeStatefulObject()
def MLP(Chain):
      self.__init__....

model = L.Classifier(MLP())
model.add_persistent("dict", obj)
serializers.save_hdf5(model) # doesn't work

If it is possible, actually it is very useful to save, let's say, a dictionary of word->word_id, as it is used in many Natural Language Processing application.
Thanks.

I move this problem to the forum, sorry for not realizing that!


Total Revenue Generated Calculator

Hey @Srijita-Mandal, i would like to open this issue under JWOC.
I'll add a calculator to calculate total revenue generated by taking as input sales and average price of service.
Kindly assign

@ritika728 go for it.


[#1712] Update ActivityWrapper to be accessible

#1712
Selected activities will now be noted as checked when selected, and at the same time open the activity in the json viewer.

ActivityWrapper has been changed from button to checkbox, and tests have been updated.

Coverage remained the same at 65.931% when pulling 434aff523a184f367edae672e8255261e0a069c7 on corinagum/1712 into e848885abfc1c2f559bd0db93680e4ac6595f56e on master.


Fix SQL formatting for nested alias or sample

Nested aliases or table samples are formatted without parentheses.  For example, select * from ((select q) x) y would format as select * from (select q) x y.

What's broken?

I updated the description. See added test cases for specific examples.


Upgrade SBT Compiler Maven Plugin version from 1.0.0-rc1 to 1.0.0

Upgrade sbt-compiler-maven-plugin:sbt-compiler-api dependency version from 1.0.0-rc1 to 1.0.0.
For more details see sbt-compiler-maven-plugin 1.0.0 issues.

New 1.0.0-beta8-SNAPSHOT snapshot deployed.

Documentation updated.


using Hugo to resize images, re: #43

I think there's an issue here - Hugo-generated resized images aren't displaying (or weren't created?):


Blender closes when trying to render a simulation

Unable to render fluid particles. They do not load or the blender closes.
This applies to rendering animations.

This seems to be the mistake of the blender itself, not the addon. When rendering Cycles, the blender is very unstable if particles change. Blender version: 2.82


Update Pulsar with partitionKey

Content for: https://github.com/dapr/components-contrib/pull/2647.
@binnn6 please open a PR to update the docs with the new metadata field.

OK

#3536