cimgui.zig: add backends support

[x] Add flags for backends
[x] Add checks for backends
[ ] Add an exemple folder
[ ] Add a run step (to run imgui exemples) depending on backends

Current workspace for this feature: https://github.com/tiawl/cimgui.zig/tree/backends


Add method to oracle to get value for publisher

Close in favor of https://github.com/42labs/Pontis/pull/74


/etc/host configuration docs needed

What happened?
This is a bug w/ the docs, I think there is a missing section about configuring the /etc/host file to allow for local connections through a url like my-dev-env.local. I asked the question on SO and the response allowed this to work for me.
Am I missing something here or is it necessary to update etc/host?
What should've happened instead?
Details about configuring the /etc/host file on the local machine to forward the request.

@Andrew-Chen-Wang I think we're talking about different things here. My issues are with the documentation and that it does not explain clearly how to run locally with HTTPS. I don't believe it's related to your PR.

nginx (jwilder/nginx-proxy:alpine specifically) is being defined in the Docker compose file, local.yml
I'm running docker-compose -f local.yml
This has nothing to do with the doc service

I'm following the documentation, where it's suggested to use nginx in local development to allow for testing with https (local.yml docs)
I've moved away from Docker at the moment but the problem remains, there should be a reference in Getting Up and Running Locally with Docker about updating one's /etc/host file to forward the request from my-dev-env.local to <IP_ADDRESS>.

Ah I see, sorry. Brain must've been no good when reading this (I think I read documentation and <IP_ADDRESS> and came up with a wrong conclusion by the time I finished reading).
Try adding your hostname to the ALLOWED_HOSTS setting in your settings.py:
ALLOWED_HOSTS = ["localhost", "<IP_ADDRESS>", "<IP_ADDRESS>", "my-dev-env.local"]

This is a bug w/ the docs, I think there is a missing section about configuring the /etc/host file to allow for local connections through a url like my-dev-env.local.

You're correct, this is missing.

By default <IP_ADDRESS> is mapped to localhost. This can be verified by running $ host <IP_ADDRESS> or by checking /etc/hosts file, so would it not be easier to simply use localhost as the domain name for local dev?

I also struggle on this topic. While I kind of know what the /etc/hosts is doing, I have added my-dev-env.local.
This seems to work correctly for the main page, but for any page with deeper access I am kicked out.
Example https://my-dev-env.local/admin works until I enter my credentials. I am then presented my a 403 Forbidden under https://my-dev-env.local/admin/login/?next=/admin/.
If I instead enter the admin page via localhost:8000/admin everything works as expected.


Deduplicate sql Queries in ContextFormDetailView

[x] Introduce django-perf-rec inside django-formidable
[x] Deduplicate any queries on the view
[x] Able to use the ContexFormSerializer without manupulating queryset in each context.

Comparison: render a form on "padawan" context with three different fields.
In Master
- db: 'SELECT ... FROM "django_session" WHERE ("django_session"."expire_date" > # AND "django_session"."session_key" = #)'
- db: 'SELECT ... FROM "formidable_formidable" WHERE "formidable_formidable"."id" = #'
- db: 'SELECT ... FROM "formidable_field" WHERE "formidable_field"."form_id" IN (#) ORDER BY "formidable_field"."order" ASC
- db: 'SELECT ... FROM "formidable_field" WHERE "formidable_field"."form_id" = # ORDER BY "formidable_field"."order" ASC'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."access_id" = # AND NOT ("formidable_access"."level" = #) AND "formidable_access"."field_id" IN (...))'
- db: 'SELECT ... FROM "formidable_validation" WHERE "formidable_validation"."field_id" = #'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."field_id" = # AND "formidable_access"."access_id" = #)'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."field_id" = # AND "formidable_access"."access_id" = #)'
- db: 'SELECT ... FROM "formidable_item" WHERE "formidable_item"."field_id" = # ORDER BY "formidable_item"."order" ASC'
- db: 'SELECT ... FROM "formidable_default" WHERE "formidable_default"."field_id" = #'
- db: 'SELECT ... FROM "formidable_validation" WHERE "formidable_validation"."field_id" = #'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."field_id" = # AND "formidable_access"."access_id" = #)'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."field_id" = # AND "formidable_access"."access_id" = #)'
- db: 'SELECT ... FROM "formidable_item" WHERE "formidable_item"."field_id" = # ORDER BY "formidable_item"."order" ASC'
- db: 'SELECT ... FROM "formidable_default" WHERE "formidable_default"."field_id" = #'

In current branch
- db: 'SELECT ... FROM "django_session" WHERE ("django_session"."expire_date" > # AND "django_session"."session_key" = #)'
- db: 'SELECT ... FROM "formidable_formidable" WHERE "formidable_formidable"."id" = #'
- db: 'SELECT ... FROM "formidable_field" WHERE "formidable_field"."form_id" = # ORDER BY "formidable_field"."order" ASC'
- db: 'SELECT ... FROM "formidable_access" WHERE ("formidable_access"."access_id" = # AND NOT ("formidable_access"."level" = #) AND "formidable_access"."field_id" IN (...))'
- db: SELECT ... FROM "formidable_item" WHERE "formidable_item"."field_id" IN (...) ORDER BY "formidable_item"."order" ASC
- db: SELECT ... FROM "formidable_validation" WHERE "formidable_validation"."field_id" IN (...)
- db: SELECT ... FROM "formidable_default" WHERE "formidable_default"."field_id" IN (...)

superseded by #160


fix(deps): upgrade gax to 2.7.1, protobuf to 3.19.1, grpc to 1.42.1, and truth to 1.1.2, upgrade Bazel in GitHub Actions, and fix build error

FTR: this was for #875 and to trigger the release bot to create a release PR (#878).


Class 'Permissions' not found after upgrade from V0.27.5 to V0.29.3

Hi,
I have an error after upgrading Bookstack from V0.27.5 to V0.29.3 (Ubuntu 18.04.3 / PHP 7.2.24 / Laravel 6.18.3 / Apache)

I found issue #2159 that talks about the same thing (but with Nginx). As it's closed and there's a small difference, I took the liberty to open another one... Feel free to mark this one as a duplicate if necessary 😉
I checked the permissions files and everything seems OK
composer install return no error (maybe a warning about abandoned package)
Package operations: 51 installs, 0 updates, 0 removals
  - Installing maximebf/debugbar (v1.16.1): Downloading (100%)
  - Installing barryvdh/laravel-debugbar (v3.2.9): Downloading (100%)
...
  - Installing wnx/laravel-stats (v2.0.2): Downloading (100%)
maximebf/debugbar suggests installing kriswallsmith/assetic (The best way to manage assets)
barryvdh/reflection-docblock suggests installing dflydev/markdown (~1.0)
barryvdh/reflection-docblock suggests installing erusev/parsedown (~1.0)
sebastian/global-state suggests installing ext-uopz (*)
phpunit/php-code-coverage suggests installing ext-xdebug (^2.7.2)
phpunit/phpunit suggests installing ext-soap (*)
phpunit/phpunit suggests installing ext-xdebug (*)
phpunit/phpunit suggests installing phpunit/php-invoker (^2.0.0)
Package jakub-onderka/php-console-color is abandoned, you should avoid using it. Use php-parallel-lint/php-console-color instead.
Package jakub-onderka/php-console-highlighter is abandoned, you should avoid using it. Use php-parallel-lint/php-console-highlighter instead.
Generating optimized autoload files
...
Package manifest generated successfully.
> @php artisan cache:clear
Application cache cleared!
> @php artisan view:clear
Compiled views cleared!

git status return the following
Sur la branche release
Votre branche est à jour avec 'origin/release'.

Fichiers non suivis:
  (utilisez "git add <fichier>..." pour inclure dans ce qui sera validé)
        .env.bak
        composer.phar

aucune modification ajoutée à la validation mais des fichiers non suivis sont présents (utilisez "git add" pour les suivre)

Hi @Nico207
Can you try fully deleting the vendor directory of your BookStack installation direction then re-run the composer install step. Afterwards, if still not working, might be worth trying to run sudo php artisan cache:clear.

I have the same issue, even after deleting vendor directory and running the clear cache command.

Hmm, Might be worth trying php artisan config:clear. If that does not work try sudo php artisan config:clear.

Great!
After php artisan config:clear, everything seems to work.
But, after that, do I need to reconfigure or verify anything?

@Nico207 Awesome, No need to do anything. Everything should have been done by the other update steps, just need to remove the older cached config. Will therefore close this off.

just need to remove the older cached config

Sorry but... how I do that ? 😳

Ah, Sorry, I mean needed. You did that by running the command.


Updated cobra2snooty

Proposed changes

Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

Sure

@JuliaMongo I have addressed your comment.


Improve docs for tee

I was surprised that the docs made it very difficult to figure how tee is supposed to be used.

LGTM


About million points implementation

Hello, first, thank you for amazing works!
I have a question about the scalability of this method to large scale point clouds.
Is this model compatible with million point segmegmentation setting ( > 10^6)?
Thank you.

Hi @a18700 ,
We have not tried this scenario, but in our implementation, you could set a appropriate sampleDl to first sub-sample the whole point cloud to a proper scale. Or you can reduce the network width or depth, this can reduce the computation and memory cost a lot.


Instance file push/pull/delete lifecycle events

add instance file lifecycle events for push, pull, and delete
InstanceFileRetrieved includes the file source and destination as context
InstanceFilePushed includes the file source, destination, and file info as context
InstanceFileRemoved includes the file path as context

@masnax needs a rebase

Oops :)

Testsuite passed

@masnax aren't we also missing those 3 events for containers (driver_lxc)?

Huh, yeah I somehow overlooked that...


submodule commons is not linked to actual ckorzen/commons repo

https://github.com/ckorzen/commons should be recorded as the submodule

Fixed in https://github.com/ckorzen/icecite/commit/47c3e6ee2b66f48e385bfcea980a15d3252d1b18. Thanks for pointing that out.


Target locations doesn't account for plane

The solver currently doesn't account for the plane of the location you pick. This also affects using a PluginMessage to specify the exact coordinate (including plane) as a target. The path will prioritize a "better" target even if the plane is wrong.
For example, here the plugin ends up going to the top of the castle as it can walk onto the exact x,y coordinate picked which is blocked on the chosen plane.

This was added in version 1.15.2 and will be live in the client after review in a few days or 1 to 2 weeks.
I actually remember explicitly disregarding the z-plane, but I can no longer remember why I did that. It could have been that many ladders and staircases were missing, which would create even worse paths to unreachable targets cross-plane. This is a much smaller problem now as most ladders and staircases have been added, so I have decided to change cross-plane distance from 0 to almost infinity.


Automate the setup of private Github Repos for CI

Is your feature request related to a problem? Please describe.
The setup describe in this doc requires a number of manual steps using different platforms https://cloud.google.com/build/docs/access-private-github-repos
Describe the solution you'd like
The idea is abstracting away the whole setup in Myiac so there's a single task for it:
myiac setup repo-ssh --url repoUrl --ci cloudbuild --secret-provider gcp-secretmanager

Repository url has been found for Github...

SSH key has been created in Github
SSH public key has been added to repository private deploy keys
SSH private key has been stored in GCP Secret Manager

Generated templated CloudBuild yaml pipeline to access this repository at 'path'

No longer using Cloudbuild


Wfp 1726

not essential but would be nice for https://github.com/ministryofjustice/manage-a-workforce-ui/blob/main/server/models/Allocation.ts to reflect the risk fields returned


Validator is throwing an incorrect error for the Patient resource relating to Race and Ethncity

Using the patient example json :
https://hl7.org/fhir/us/core/STU6/Patient-example.json.html
Setting the us core to :  hl7.fhir.us.core#6.1.0
Receiving these information and errors even though that OID is correct.
Information
Line: 42, Col:12
The definition for the Code System with URI 'urn:oid:2.16.840.1.113883.6.238' doesn't provide any codes so the code cannot be validated
Error
Line: 42, Col:12
The code provided (urn:oid:2.16.840.1.113883.6.238#1586-7) was not found in the value set 'Detailed Race' (http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0), and a code from this value set is required: The provided code 'urn:oid:2.16.840.1.113883.6.238#1586-7 ('Shoshone')' was not found in the value set 'http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0'
Error
Line: 50, Col:12
The code provided (urn:oid:2.16.840.1.113883.6.238#2036-2) was not found in the value set 'Detailed Race' (http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0), and a code from this value set is required: The provided code 'urn:oid:2.16.840.1.113883.6.238#2036-2 ('Filipino')' was not found in the value set 'http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0'

is this issue reproducible with the command line validator?

Yes it is.    Using the patient example json:  https://hl7.org/fhir/us/core/STU6/Patient-example.json.html
java -Xmx2048m -jar validator_cli.jar Concept.json -version 4.0.1 -ig hl7.fhir.us.core#6.1.1 -tx n/a
FAILURE: 1 errors, 11 warnings, 8 notes
Error @ Patient.extension[0].extension[3].value.ofType(Coding) (line 42, col7): The code provided (urn:oid:2.16.840.1.113883.6.238#1586-7) was not found in the value set 'Detailed Race' (http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0), and a code from this value set is required: The provided code 'urn:oid:2.16.840.1.113883.6.238#1586-7 ('Shoshone')' was not found in the value set 'http://hl7.org/fhir/us/core/ValueSet/detailed-race|6.1.0'

see discussion here: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Missing.20race.20.26.20ethnicity.20codes.20that.20aren't.20missing


Default random seed for non-deterministic DataSplitters

Fixes the random behavior of data splitters that use non-deterministic logic.
If shard descriptors of Envoys use the same data splitter, they should share the same parts of data.
By default, NumPy random seed of all splitters will be equal to zero. It means if Envoys use the same shard descriptor code (where data splitter is created) then data split is identical.
Closes #282.

Jenkins please retry a build

Shouldn't we add in class EqualNumPyDataSplitter 'seed' too? To make the same shuffle on each envoy

Will this line split classes unevenly in case of no shuffle?
if the original dataset is ordered by target, like [0,0,0,1,1,1,1], the first collaborator will get only 0th class.
If it is true, may we use idx[rank : len(idx) : cols] instead of 'np.split_array'?

May we consider including seed in the interface class' signature instead of all the child classes

May we consider including seed in the interface class' signature instead of all the child classes

@igor-davidyuk Interface should include only required parameters. Fully deterministic behaviour does not require random seed.

Will this line split classes unevenly in case of no shuffle? if the original dataset is ordered by target, like [0,0,0,1,1,1,1], the first collaborator will get only 0th class. If it is true, may we use idx[rank : len(idx) : cols] instead of np.split_array?

It's true. In this case the first collaborator will receive the first part of data, and the second the remains. Isn't it better to use shuffling here instead of guessing the ordering?


How to listen dialog_submission

Description
I am trying listen the dialog_submission type. I can see i am getting the event when i submit the dialog created via this.
      client.dialog.open({
        trigger_id: body.trigger_id,
        dialog: {
          title: 'Add your task.',
          callback_id: interactiveEnums.TASK_VIEW_SUBMIT,
          notify_on_cancel: true,
          elements: [
            {
              type: 'textarea',
              name: 'taday_task',
              placeholder: 'Place you daily task in detail form.',
              label: 'Enter your task here in detail form.',
              min_length: 40,
              max_length: 3000,
            },
            {
              type: 'text',
              name: 'hours_spend',
              subtype: 'number',
              label: 'How much hours did you spend on above tasks.',
              value: '8',
            },
          ],
        },
      });

What type of issue is this? (place an x in one of the [ ])

[x] bug
[x] enhancement (feature request)
[x] question
[x] documentation related
[x] example code related
[ ] testing related
[x] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version: ^3.12.1
node version: 18
OS version(s): bulls eye dev container
Steps to reproduce:

Open the dialog on the interactive command

Expected result:
What you expect to happen
When I try to listen to the view
app.view('call_back_id', action())

The action closure function should be called.
Actual result:
What actually happened
I am not getting any event call back of any type when i intercept the call back via app.use
I can see the logs are coming.
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Hi @dharmendrasha, thanks for asking the question!
We generally don't recommend using dialogs over modals because we won't add any new features to dialogs. That being said, if you have a certain reason to still use dialogs, checking my comment at https://github.com/slackapi/bolt-js/issues/265#issuecomment-537449896 can be helpful. More specifically, something like this should work for you:
app.action({ callback_id: interactiveEnums.TASK_VIEW_SUBMIT }, async ({ ack }) => {
  await ack();
});

I hope this was helpful to you.


FR: Add a Fixed Map Option to Embeds

With embedded maps in particular, it would be nice to add a flag that locks the map to a fixed center (possibly where +- zoom could still work), but no scrolling unless the map is opened in the main map view.
On mobile embedded map view tends to get in the way while scrolling through a note, and in most cases a fixed map would be preferred.

I really like this suggestion.

Added in 4.0.0.

Thanks! The new flag is: "lock":true for anyone adding it to the code blocks manually.


added test for getVersionDifference

Pull Request Test Coverage Report for Build 692757587

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 70.014%

Totals

Change from base Build 691245933:
1.9%

Covered Lines:
322

Relevant Lines:
468

💛  - Coveralls


Pycaruna stopped working on Dec 7, 2022

Hi,
I guess Caruna has made some changes in their end around 7 December 2022 which caused pycaruna to stop working.
The login method fails:
import pycaruna
session = pycaruna.login_caruna("my-username", "my-password")

Results in the following traceback...
Traceback (most recent call last):
  File "/path/to/pycaruna/fetch.py", line 2, in <module>
    session = pycaruna.login_caruna("my-username", "my-password")
  File "/path/to/pycaruna/pycaruna.py", line 65, in login_caruna
    r = s.get(url)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 555, in get
    return self.request('GET', url, **kwargs)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 528, in request
    prep = self.prepare_request(req)
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 456, in prepare_request
    p.prepare(
  File "/usr/lib/python3/dist-packages/requests/models.py", line 316, in prepare
    self.prepare_url(url, params)
  File "/usr/lib/python3/dist-packages/requests/models.py", line 390, in prepare_url
    raise MissingSchema(error)
requests.exceptions.MissingSchema: Invalid URL 'e,chrome=1': No schema supplied. Perhaps you meant http://e,chrome=1?

Any ideas, anyone?
Cheers,
Markus

Must be because of this:
https://caruna.fi/ajankohtaista/olemme-uudistaneet-caruna-plus-tunnistautumispalvelua

Fixed.


Spacing on bullet points and after admonitions is a bit awkward

While updating the installation guide I noticed that some of the paragraph spacing is quite large and looks a bit awkward, in particular with bullet points and after admonitions.
After an admonition:

Bullet points:

I think the spacing should be a bit smaller as it is currently distracting and makes paragraphs look unrelated.

@DragaDoncila is this something we can close now that we've switched to pydata fork?

@codemonkey800 yep, margins look good now! Closing this one.


Animated listeners fix

Changelog
[Internal] [Fix] - added listeners to Anumated.add
Hello , this is fix for https://github.com/facebook/react-native/issues/35478

Hey @Quintis1212, could you have a look at the formatting notes from Danger? Thanks!

@GijsWeterings  Hey ! I commited formatting

Could you add a unit test that shows the failing behaviour before, and demonstrates what's being fixed here?


unuse forward when jit exporting transducer

Error when jit exporting transducer with previous code
Found this forward func is not necessary for jit export (like transformer/asr_model.py, line 77 and 78)

https://github.com/wenet-e2e/wenet/issues/2544


Undo updating npm in node artifact builds

In retrospect, that's global, so we shouldn't touch it in the build.

No significant performance differences

No significant performance differences

This only affects the artifact builds, so I think it's OK to merge.


Restore fails

I can't restore backup from my object storage to my cluster-restore.
Context
Operator version: 1.19.1
Description: using Minio to store my backup. I was working well some days ago.
Error
k get pod -w
NAME                                    READY   STATUS    RESTARTS   AGE
cluster-example-1                       1/1     Running   0          2m
cluster-example-2                       1/1     Running   0          89s
cluster-example-3                       1/1     Running   0          2m6s
cluster-restore-1-full-recovery-52r7t   0/1     Error     0          19s
cluster-restore-1-full-recovery-6t4g2   0/1     Error     0          27s
cluster-restore-1-full-recovery-f924z   0/1     Error     0          23s
cluster-restore-1-full-recovery-pcqgw   0/1     Error     0          11s
cluster-restore-1-full-recovery-pql9n   0/1     Error     0          39s
cluster-restore-1-full-recovery-smfdf   0/1     Error     0          15s
cluster-restore-1-full-recovery-zf6nj   0/1     Error     0          31s
^Csergio.romera@laptop390-ma-us:~/Documents/GitHub/kubecon2022-demo
> k logs cluster-restore-1-full-recovery-zf6nj
Defaulted container "full-recovery" out of: full-recovery, bootstrap-controller (init)
{"level":"info","ts":"2023-03-24T15:12:57Z","msg":"PGData already exists, can't overwrite","logging_pod":"cluster-restore-1-full-recovery"}

Cluster Config
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster-example
spec:
  instances: 3
  imageName: ghcr.io/cloudnative-pg/postgresql:14.5
  #imagePullPolicy: Always
  minSyncReplicas: 1
  maxSyncReplicas: 1

  postgresql:
    parameters:
      pg_stat_statements.max: "10000"
      pg_stat_statements.track: all

  storage:
    size: 1Gi

  backup:
    target: "prefer-standby"
    barmanObjectStore:
      destinationPath: "s3://cnp/"
      endpointURL: "http://<IP_ADDRESS>:9000"
      s3Credentials:
        accessKeyId:
          name: minio-creds
          key: MINIO_ACCESS_KEY
        secretAccessKey:
          name: minio-creds
          key: MINIO_SECRET_KEY
      data:
        immediateCheckpoint: true
      #wal:
      #  compression: gzip
      #  maxParallel: 8
      #  encryption: AES256
    retentionPolicy: "1d"

Backup file
apiVersion: postgresql.cnpg.io/v1
kind: Backup
metadata:
  name: backup-test
spec:
  cluster:
    name: cluster-example

Restore file
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: cluster-restore
spec:
  instances: 1
  imageName: ghcr.io/cloudnative-pg/postgresql:14.5
  #imagePullPolicy: Never

  storage:
    size: 1Gi

  bootstrap:
    recovery:
      backup:
        name: backup-test

I'd look for the logs of the first cluster-restore pod, that was created (looking at age times it would be cluster-restore-1-full-recovery-pql9n). The log You've presented is from the second one created and it does not refer to the initial problem (this is a standard error when consecutive restore pods are being created due to initial one failure).
Additionally look at operator logs.

One more thing - are You sure backup-test object exists in the same namespace You perform the restore?

This is my new situation and my new error.
> k get pod -w
NAME                                    READY   STATUS    RESTARTS   AGE
cluster-example-1                       1/1     Running   0          2m20s
cluster-example-2                       1/1     Running   0          2m43s
cluster-example-3                       1/1     Running   0          2m48s
cluster-restore-1-full-recovery-6c68k   0/1     Error     0          105s
cluster-restore-1-full-recovery-f5rw5   0/1     Error     0          117s
cluster-restore-1-full-recovery-jv29b   0/1     Error     0          101s
cluster-restore-1-full-recovery-nccwn   0/1     Error     0          113s
cluster-restore-1-full-recovery-qhw4n   0/1     Error     0          2m1s
cluster-restore-1-full-recovery-rm9ff   0/1     Error     0          109s
cluster-restore-1-full-recovery-sw7nh   0/1     Error     0          2m9s

And this is the log:
k logs cluster-restore-1-full-recovery-sw7nh | jq
Defaulted container "full-recovery" out of: full-recovery, bootstrap-controller (init)
{
  "level": "info",
  "ts": "2023-03-27T14:12:59Z",
  "msg": "Recovering existing backup",
  "logging_pod": "cluster-restore-1-full-recovery",
  "backup": {
    "metadata": {
      "name": "backup-test",
      "namespace": "default",
      "uid": "d45f5f3b-ee4f-4dcf-8aa4-71d4e6140e91",
      "resourceVersion": "2844733",
      "generation": 1,
      "creationTimestamp": "2023-03-27T14:12:50Z",
      "annotations": {
        "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"postgresql.cnpg.io/v1\",\"kind\":\"Backup\",\"metadata\":{\"annotations\":{},\"name\":\"backup-test\",\"namespace\":\"default\"},\"spec\":{\"cluster\":{\"name\":\"cluster-example\"}}}\n"
      },
      "managedFields": [
        {
          "manager": "kubectl-client-side-apply",
          "operation": "Update",
          "apiVersion": "postgresql.cnpg.io/v1",
          "time": "2023-03-27T14:12:50Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:metadata": {
              "f:annotations": {
                ".": {},
                "f:kubectl.kubernetes.io/last-applied-configuration": {}
              }
            },
            "f:spec": {
              ".": {},
              "f:cluster": {
                ".": {},
                "f:name": {}
              }
            }
          }
        },
        {
          "manager": "manager",
          "operation": "Update",
          "apiVersion": "postgresql.cnpg.io/v1",
          "time": "2023-03-27T14:12:52Z",
          "fieldsType": "FieldsV1",
          "fieldsV1": {
            "f:status": {
              ".": {},
              "f:backupId": {},
              "f:beginLSN": {},
              "f:beginWal": {},
              "f:destinationPath": {},
              "f:endLSN": {},
              "f:endWal": {},
              "f:endpointURL": {},
              "f:instanceID": {
                ".": {},
                "f:ContainerID": {},
                "f:podName": {}
              },
              "f:phase": {},
              "f:s3Credentials": {
                ".": {},
                "f:accessKeyId": {
                  ".": {},
                  "f:key": {},
                  "f:name": {}
                },
                "f:inheritFromIAMRole": {},
                "f:secretAccessKey": {
                  ".": {},
                  "f:key": {},
                  "f:name": {}
                }
              },
              "f:serverName": {},
              "f:startedAt": {},
              "f:stoppedAt": {}
            }
          },
          "subresource": "status"
        }
      ]
    },
    "spec": {
      "cluster": {
        "name": "cluster-example"
      }
    },
    "status": {
      "s3Credentials": {
        "accessKeyId": {
          "name": "minio-creds",
          "key": "MINIO_ACCESS_KEY"
        },
        "secretAccessKey": {
          "name": "minio-creds",
          "key": "MINIO_SECRET_KEY"
        },
        "inheritFromIAMRole": false
      },
      "endpointURL": "http://<IP_ADDRESS>:9000",
      "destinationPath": "s3://cnp/",
      "serverName": "cluster-example",
      "backupId": "20230327T141251",
      "phase": "completed",
      "startedAt": "2023-03-27T14:12:51Z",
      "stoppedAt": "2023-03-27T14:12:51Z",
      "beginWal": "000000020000000000000005",
      "endWal": "000000020000000000000005",
      "beginLSN": "0/5000180",
      "endLSN": "0/5011140",
      "instanceID": {
        "podName": "cluster-example-3",
        "ContainerID": "docker://73a463283695bce9eeace27e545f6a8e6fc723c646407985a70c87ff981b2529"
      }
    }
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:12:59Z",
  "msg": "Starting barman-cloud-restore",
  "logging_pod": "cluster-restore-1-full-recovery",
  "options": [
    "--endpoint-url",
    "http://<IP_ADDRESS>:9000",
    "s3://cnp/",
    "cluster-example",
    "20230327T141251",
    "--cloud-provider",
    "aws-s3",
    "/var/lib/postgresql/data/pgdata"
  ]
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:00Z",
  "msg": "Restore completed",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:00Z",
  "msg": "Creating new data directory",
  "logging_pod": "cluster-restore-1-full-recovery",
  "pgdata": "/controller/recovery/datadir_2951822766",
  "initDbOptions": [
    "--username",
    "postgres",
    "-D",
    "/controller/recovery/datadir_2951822766",
    "--no-sync"
  ]
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "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_2951822766 ... 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_2951822766 -l logfile start\n\n",
  "pipe": "stdout",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "logger": "initdb",
  "msg": "initdb: warning: enabling \"trust\" authentication for local connections\nYou can change this by editing pg_hba.conf or using the option -A, or\n--auth-local and --auth-host, the next time you run initdb.\n",
  "pipe": "stderr",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "Installed configuration file",
  "logging_pod": "cluster-restore-1-full-recovery",
  "pgdata": "/controller/recovery/datadir_2951822766",
  "filename": "pg_hba.conf"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "Ignore minSyncReplicas to enforce self-healing",
  "logging_pod": "cluster-restore-1-full-recovery",
  "syncReplicas": -1,
  "minSyncReplicas": 0,
  "maxSyncReplicas": 0
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "Installed configuration file",
  "logging_pod": "cluster-restore-1-full-recovery",
  "pgdata": "/controller/recovery/datadir_2951822766",
  "filename": "custom.conf"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "Generated recovery configuration",
  "logging_pod": "cluster-restore-1-full-recovery",
  "configuration": "recovery_target_action = promote\nrestore_command = 'barman-cloud-wal-restore --endpoint-url http://<IP_ADDRESS>:9000 s3://cnp/ cluster-example --cloud-provider aws-s3 %f %p'\n"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "enforcing parameters found in pg_controldata",
  "logging_pod": "cluster-restore-1-full-recovery",
  "parameters": {
    "max_connections": "100",
    "max_locks_per_transaction": "64",
    "max_prepared_transactions": "0",
    "max_wal_senders": "10",
    "max_worker_processes": "32"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "msg": "Starting up instance",
  "logging_pod": "cluster-restore-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": "2023-03-27T14:13:01Z",
  "logger": "pg_ctl",
  "msg": "waiting for server to start....2023-03-27 14:13:01.261 UTC [36] LOG:  redirecting log output to logging collector process",
  "pipe": "stdout",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "logger": "pg_ctl",
  "msg": "2023-03-27 14:13:01.261 UTC [36] HINT:  Future log output will appear in directory \"/controller/log\".",
  "pipe": "stdout",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.261 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "1",
    "session_start_time": "2023-03-27 14:13:01 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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.261 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "2",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "starting PostgreSQL 14.5 (Debian 14.5-2.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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.262 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "3",
    "session_start_time": "2023-03-27 14:13:01 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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.264 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "4",
    "session_start_time": "2023-03-27 14:13:01 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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.267 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "1",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "database system was interrupted while in recovery at log time 2023-03-27 14:12: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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.267 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "2",
    "session_start_time": "2023-03-27 14:13:01 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": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.704 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "3",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "starting archive recovery",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:01Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:01.969 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "4",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "restored log file \"00000002.history\" from archive",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.778 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "5",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "restored log file \"000000010000000000000005\" from archive",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.792 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "6",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "invalid record length at 0/50001B8: wanted 24, got 0",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.792 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "7",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "invalid checkpoint record",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.792 UTC",
    "process_id": "38",
    "session_id": "6421a46d.26",
    "session_line_num": "8",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "FATAL",
    "sql_state_code": "XX000",
    "message": "could not locate required checkpoint record",
    "hint": "If you are restoring from a backup, touch \"/var/lib/postgresql/data/pgdata/recovery.signal\" and add required recovery options.\nIf you are not restoring from a backup, try removing the file \"/var/lib/postgresql/data/pgdata/backup_label\".\nBe careful: removing \"/var/lib/postgresql/data/pgdata/backup_label\" will result in a corrupt cluster if restoring from a backup.",
    "backend_type": "startup",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.793 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "5",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "startup process (PID 38) exited with exit code 1",
    "backend_type": "postmaster",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.793 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "6",
    "session_start_time": "2023-03-27 14:13:01 UTC",
    "transaction_id": "0",
    "error_severity": "LOG",
    "sql_state_code": "00000",
    "message": "aborting startup due to startup process failure",
    "backend_type": "postmaster",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "cluster-restore-1-full-recovery",
  "record": {
    "log_time": "2023-03-27 14:13:02.796 UTC",
    "process_id": "36",
    "session_id": "6421a46d.24",
    "session_line_num": "7",
    "session_start_time": "2023-03-27 14:13:01 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": "2023-03-27T14:13:02Z",
  "logger": "pg_ctl",
  "msg": "pg_ctl: could not start server",
  "pipe": "stderr",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "pg_ctl",
  "msg": ". stopped waiting",
  "pipe": "stdout",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "logger": "pg_ctl",
  "msg": "Examine the log output.",
  "pipe": "stderr",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "info",
  "ts": "2023-03-27T14:13:02Z",
  "msg": "Exited log pipe",
  "fileName": "/controller/log/postgres.csv",
  "logging_pod": "cluster-restore-1-full-recovery"
}
{
  "level": "error",
  "ts": "2023-03-27T14:13:02Z",
  "msg": "Error while restoring a backup",
  "logging_pod": "cluster-restore-1-full-recovery",
  "error": "while activating instance: error starting PostgreSQL instance: exit status 1",
  "stacktrace": "github.com/cloudnative-pg/cloudnative-pg/pkg/management/log.(*logger).Error\n\tpkg/management/log/log.go:128\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/log.Error\n\tpkg/management/log/log.go:166\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.restoreSubCommand\n\tinternal/cmd/manager/instance/restore/cmd.go:93\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/instance/restore.NewCmd.func2\n\tinternal/cmd/manager/instance/restore/cmd.go:60\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968\nmain.main\n\tcmd/manager/main.go:64\nruntime.main\n\t/opt/hostedtoolcache/go/1.20.2/x64/src/runtime/proc.go:250"
}

If I delete the pvc (cluster-restore-1) and the cluster-restore, when I try to restore again it works!.

I've found the problem.
In fact if the backup is done from an standby database (with the parameter target: "prefer-standby"in the backup section), to restore the database it is necessary to switch the wals with select pg_switch_wal(); command.


Release 1.11.1 (or call it 1.12.0)?

There is no official libGDX release for 1+ years (last official release was in May 2022). I think it might be time to release a new version?There are several changes that would be kind of nice to have:

LWJGL 3.3.2: fixes some bugs on Mac OS.
Misc. Audio Bugfixes, especially for LWJGL3.
MobiVM 2.3.19: Support for latest iOS builds.
many other improvements & fixes over the past year.

I'd probably propose to call it 1.12.0 as it has some breaking changes?

Calling 1.12.0 will be more conventional. I also think it's a better idea.
I think we are waiting for https://github.com/libgdx/libgdx/milestone/4 to be done.

I guess it's just about the window resizing issue resolved (LWJGL 3) as the other pull requests are more or less ready.

What happened to this plan: https://libgdx.com/news/2020/09/devlog_2_release_schedule
Are there just not enough changes for a full release each month or is it too much work to create a proper release?
I don't have any negative feelings, I'm just curious about the reasons.

This was discussed on Discord. More to do with work than a lack of changes.

IIRC we have stated quite a few times that our initial plan of releasing new versions every month was too ambitious. On the other hand, I know that our current release schedule can be pretty frustrating for users and is exactly what we were complaining about ourselves when we joined the team a couple of years ago.
So, what is taking us so long? I think “time” describes it quite well. We need to test and review new PRs and finding spare time for that isn’t always easy. I know I’ve stated this in the past, but I think it bears repeating: if you want libGDX to release faster, this is where you can chime in. Just take a look at open PRs, test them, and write a short review. I’ve also tried using the milestones to make more transparent, which PRs I’d like to get into new releases.
Also, at the moment there aren’t that many people left on the team who can “press the button”, but I think they don’t have that much free time on their hands. Maybe we should look into expanding that circle of people, but that isn’t my call.
There probably is a good middle-ground to be found here: IMO a release every three to four months sounds pretty reasonable and should help get new PRs merged faster. Also, I don’t think there is any reason to fear that libGDX is being abandoned: we all care about the framework, otherwise we wouldn’t be here; also we recently took on two new team members to help get things done quicker.

We need to test and review new PRs and finding spare time for that isn’t always easy. I know I’ve stated this in the past, but I think it bears repeating: if you want libGDX to release faster, this is where you can chime in. Just take a look at open PRs, test them, and write a short review. I’ve also tried using the milestones to make more transparent, which PRs I’d like to get into new releases.

I agree, testing all the PR take time. Maybe we could take a different approach? We release new features anyway and declare all *.*.0 releases as ALPHA/BETA. That way, the users will test and we release *.*.1, *.*.2 etc. versions to fix stability issues?

We could also try to do "release candidate" releases before every version. So we could test things out in 1.13.0-RC1 first and then release 1.13.0 once we're sure everything works.


Show std(out/err) when debugging

When using PyCharm to debug robot keywords written in python, robot will capture all the console output.
This is really annoying, and am forced to use logger.console() when in the console, but even that isn't good enough because if there's an exception in the expression it won't print anything so I'm basically forced to use:
try: logger.console(expr)
except Exception as e: logger.console(e)

😲

Robot intercepting stdout/err and catching exceptions and showing all this information in the log file is a feature. That said, having a way to somehow tell the framework to just log everything to the console could be handy. Do you have ideas how it could work?
Notice that we already have somewhat related --debugfile and that it's possible to create listeners that log everything to console already now. Support for more verbose console output (#1393) is also related.

Listeners won't log things that are printed to stdout ie print or using the console.
Is there a way to capture the stdout and save it to the log but to also send it to the normal stdout?

Want me to put together a pr with this implementation?
import sys
from typing import TextIO

class OutputDuplicator:
    def __enter__(self):
        self.out_file = TextIO()
        self.err_file = TextIO()
        self.stdout = sys.stdout
        self.stderr = sys.stderr
        sys.stdout = DuplicateWriter(self.out_file, sys.stdout)
        sys.stderr = DuplicateWriter(self.err_file, sys.stderr)

    def __exit__(self, a, b, c):
        sys.stdout = self.stdout
        sys.stderr = self.stderr
        self.out_file.close()
        self.err_file.close()

class DuplicateWriter:
    def __init__(self, file, stream):
        self.file = file
        self.stream = stream

    def write(self, data):
        self.file.write(data)
        self.stream.write(data)

    def flush(self):
        self.file.flush()

with OutputDuplicator() as o:
    print("asdf")

There's also the issue of console output being on the same line as the test name and pushing the result to the start of the next line. But this is a separate issue.

I don't think the implementation above (and in PR #3988) is a good idea for these two important reasons:

Printed messages should not be written to the console by default because most of the time they just add noise. Being able to enable that could be considered.
The implementation only handles messages logged using print(), not messages logged using robot.api.logger or logging.

Notice that listeners do get all logged messages if they implement log_message method. A problem with messages logged using print() is that they are logged only after the keyword finishes, not when print() is actually called. That's due to our somewhat naïve stdout/stderr intercepting implementation what could possibly be enhanced.

No updates since June and I doubt this is a good idea in general. Closing.


how about a CLI version

Something like
$ visualize stats.json

which will proceed to build chart and open web page (locally)

Can you write a bit more about the use case for this?
If you're using the plugin you should be able to open dist/stats.html

I am not using the plugin version, but will give it a whirl.

The idea would be to do the same thing as https://github.com/th0r/webpack-bundle-analyzer.
I have an "analyse" npm script that output a lot of information about the bundle size and chunk. I look like that:
webpack --config build/webpack.prod.conf.js --json --profile --progress > stats.json && webpack-bundle-analyzer stats.json --mode static --report report.html

That create a report.html and open it automatically. I also don't have to modify the config files and script to get that. I only feed webpack-bundle-analyzer the stats.json and it output everything relative my project folder, not the output of the bundle.
Since your plugin seem to feed from the same file (stats.json), it would be fantastic to be able to do the same thing:
webpack --config build/webpack.prod.conf.js --json --profile --progress > test/analyze/stats.json && webpack-visualizer-plugin stats.json --output output.html

I have no idea how hard this is, and I have zero knowledge about webpack plugins but maybe the sources of https://github.com/th0r/webpack-bundle-analyzer could help ?
Anyway, thank you for your work on this really nice visualizer. I has already helped me reduce the size of my bundles and efficiently detect the major problems at a glance 👍


Flaky tests on windows

=== Failed
=== FAIL: activation TestBuilder_RetryPublishActivationTx (10.02s)
activation_test.go:1068:
Error Trace:	D:/a/go-spacemesh/go-spacemesh/activation/activation_test.go:1068
Error:      	failed waiting for required number of tries to occur
Test:       	TestBuilder_RetryPublishActivationTx
controller.go:137: missing call(s) to *activation.MocknipostBuilder.BuildNIPost(is anything, is anything) D:/a/go-spacemesh/go-spacemesh/activation/activation_test.go:1043
controller.go:137: aborting test due to missing call(s)
=== FAIL: hare TestRecvDelayedDishonest (8.80s)
consensus_test.go:111: Validity 1 failed: output does not contain the intersection of honest parties
=== FAIL: hare TestEquivocation (10.02s)
consensus_test.go:111: Validity 1 failed: output does not contain the intersection of honest parties
https://github.com/spacemeshos/go-spacemesh/actions/runs/5387202693

they are probably generally flaky. just failed for me on winddows

So far I have only seen TestRecvDelayedDishonest fail on windows:
https://github.com/spacemeshos/go-spacemesh/actions/runs/5424306542/jobs/9863491112
after this test is fixed we can probably add Windows to the unittest job and have it failing block merges.

i found this one as well :(
=== Failed
=== FAIL: hare TestHare_onTick (10.03s)
hare.go:337: Unexpected call to *mocks.MockRolacle.IsIdentityActiveOnConsensusView([context.Background.WithCancel.WithValue(type log.correlationIDType, val af86acdf-1a48-4386-a54e-0caec80fe276).WithValue(type log.correlationIDType, val ).WithValue(type log.correlationIDType, val 456e7430-ef47-44a4-8bb6-29e26384a443) 71a7692c195432e63fa4504fcc5c8c8b2a4d83936b42f84aa703d534fc17be05 9]) at D:/a/go-spacemesh/go-spacemesh/hare/hare.go:337 because:
expected call at D:/a/go-spacemesh/go-spacemesh/hare/hare_test.go:335 doesn't match the argument at index 2.
Got: 9 (types.LayerID)
Want: is equal to 7 (types.LayerID)
expected call at D:/a/go-spacemesh/go-spacemesh/hare/hare_test.go:336 doesn't match the argument at index 2.
Got: 9 (types.LayerID)
Want: is equal to 8 (types.LayerID)

Two more tests failed in a recent build:
TestSndDelayedDishonest:
consensus_test.go:111: Validity 1 failed: output does not contain the intersection of honest parties
https://github.com/spacemeshos/go-spacemesh/actions/runs/5449769234/jobs/9914347141?pr=4630

i will skip hare tests, as they will be removed in upcoming weeks. there are some other flaky tests, but we can address separately


Open project by FTP

Hey guys,
i have other suggestion to better codiad.
Actually we can create project by workspace, folder on same server or github repository.
So, i would like to suggest add connection by FTP. So if we can add project by FTP was awesome.
Tnks!

Hi,
just looking for some advice /idea for mounting the ftp directories in the codiad server with curlftpfs.
I can add a function when codiad loads that checks for the remote projects and mounts them so the user can access those projects. I think I know more or less how to do that.
But, how could I detect that the user is not using them anymore and then unmount them?
I am thinking of adding some sort of cron task that checks for "unmountable" directories and unmounts them, but how could I mark them as unmountables? Let's assume that the user is not signin out, just letting the session stale.
Does it make sense to use the poller to do some sort of updating e.g. a file per user and then externally check that if that file hasn't been updated in a while, it would be safe to unmount the remote folders?
Does any of this make sense? How do other remote editors handle this?
What would be the problem of leaving those connections stale?
Any comment will be welcomed, thanks!

I know this is an old thread, but I'm looking for something similar and was wondering if anyone ever figured this out?
Ideally, it would be great if remote FTP folders could be listed in the 'projects' window, so I can make edits to remote servers from my codiad install. I suppose I could install a separate copy of codiad on that remote server, and just access it from their IP, but it would really be ideal if I could have all my FTP connections consolidated in one codiad install.
Sort of how CodeAnywhere allows you to set up remote projects?


exporting a mesh with animation

Any plans to support exporting a mesh with animation such as .dae format? thanks

Hi,
there is nothing planned for this, threestudio has the option to export meshes:
python launch.py --config configs/fourdfy_stage_3.yaml --export --gpu $gpu exp_root_dir=$exp_root_dir resume=$ckpt system.prompt_processor.prompt="a panda dancing" system.exporter_type=mesh-exporter
This probably can be extended to export a mesh with animation

Thanks for your answer. Will check it.

I'm also interested in this feature.

I am happy to support an implementation of this. Unfortunately, I won't have the time to lead this effort though.

Please reopen if this issue is not addressed.


Billing Statements API: it is not clear which permissions are required to access API

Describe the bug
New Billing statements API was added to AD API documentation.
https://advertising.amazon.com/API/docs/en-us/billing-statements
From API doc page it is not clear which Scope is required for application to access this API
URL of the content
Provide the advanced tools center or GitHub URL where you see the bug.
Description of what the documentation currently says
No information about permissions/scope
Description of what the documentation should say
Information about which scopes are required for API application to have for Billing Statements API
Additional context
It would be useful and very helpful to have Documentation page with table mapping each API available to permissions/scopes required and links on how to obtain those permissions, as currently this data is spread across multiple pages of docs and it is hard to find.

Hi @wolendrah, apologies for the slow response on this issue. I hope the below will answer some of your questions while a user guide for this API remains in development.

Scope
The term "scope" is used two ways in the Ads API:

The permission scope, e.g., advertising::campaign_management as specified in creating the authorization grant. The standard permission scope for the API enables access to the billing statements API.
The Amazon-Advertising-API-Scope, which is required for many requests to the API and is used to pass a profile ID. This header is not required for the billing statements API, but can be used as described below.

Headers and account identity
Global account
The billing statements API can instead accept the Amazon-Ads-AccountId header, whose value is the global ID for an advertising account, which may include multiple marketplaces. This ID is in the format amzn1.ads-account.g.123456789abcdefgh and can be found using the recently released account management API:

Retrieve accounts (user guide)
Account management API specification

The value for the Amazon-Ads-AccountId header will be value of the adsAccountId field for a given account returned from the account management API.
A successful request using this header will create a CSV file whose name begins with the account name.
Profile
Alternatively, the billing statements API can be used with the Amazon-Advertising-API-Scope header, using a profile ID similarly to many other endpoints in the Amazon Ads API. A successful request using this header will generate a CSV file that includes the specified profile only and whose filename begins with the entity ID for that profile.
Permissions
The Amazon user account used to generate the authorization grant must have either View or View and Edit permissions for Billing history on the account or profile in question in order to retrieve a billing statement.
Notes

Use one of the above headers for both the POST request to generate the statement and the GET request to achieve the statement URL. Using both headers in a request may result in "unauthorized" or "forbidden" error responses.
We have recently published user guides for other billing-related endpoints. Unfortunately, these do not currently cover the billing statements API, but you may find the information in these documents useful:

Billing: Getting started
Billing profiles
Payments
Invoices

Thank you for submitting this issue! Please let me know if you have any follow-up questions.
I'll leave this issue open until we have published the user guide for this endpoint.


Actor is not logging for the celery tasks

Is there any way to log the actor for celery tasks.

The first record with UI. Second record with celery.
Changes are saving but the actor is not saving.

@srikanth-chandaluri, it is not possible in the upstream version.
actor_id is set in pre_save signal for LogEntry model, and the signal is connected and disconnected by AuditlogMiddleware. Since there is no request performed in a celery task, the middleware doesn't get called and no signal gets installed.
There is a refactor in our fork of auditlog that achieves just that (logging correct actor_id in user-triggered celery tasks): https://github.com/MacmillanPlatform/django-auditlog/commit/a5381b61957a42406d378d08df6530415a0db006
Example usage (again, this is a custom fork of auditlog):
from auditlog.context import set_actor
@app.task
def do_stuff(actor_id: int):
    actor = get_user(actor_id)
    with set_actor(actor):
        # if your code here leads to creation of LogEntry instances, these will have actor set
        ...

Sadly, the maintainer doesn't appear to work on this package any more, so the chance this gets into upstream is low.

@alieh-rymasheuski An MR is welcome. I don't have a lot of time to work on this (and the maintainers aren't spending time anymore either), but if there is an MR I could have a look at it.

@srikanth-chandaluri, I'm happy to announce that after a long while this changeset has finally got it to the upstream repo! The usage is the same as in my comment above. This feature is not yet part of a release but can be used on the pre-prelease master.


fix: organization add node and level

What this PR does / why we need it:
fix: organization add node and level

Does this PR need to be backport to the previous release branch?:
NONE

/cc @zexi @ioito

/lgtm


YouTube video playback doesn't start when the video is muted

Describe the bug
When attempting to start playback of a YouTube video while it is muted, the video doesn't start. This issue occurs in chrome or chromium based browsers. It behaves normally in firefox.
Steps to reproduce
The issue also occurs in the provided glitch demo playground : https://glitch.com/edit/#!/vlitejs-youtube-video
However, i noticed this playground runs on vlite-js release 5, so I remixed a glitch environment to vlite-js 6.0.3 where the issue also occurs: https://glitch.com/edit/#!/sage-quilted-hippopotamus
It also works when you preview in a new window with glitch, but it doesn't work when it's previewed in the preview pane
Expected behavior
Youtube video's should playback whether muted or unmuted.
Screenshots and recordings
https://github.com/vlitejs/vlite/assets/11197996/0854bc89-a8ee-4752-9348-471a66c41b1a
Vlite.js
6.0.3
Browser
Chrome 126.0.6478.62 (Officiële build) (64-bits)
OS
Windows 11
Additional context
No response

Hello @yoriiis, thanks for the quick response,
I updated the issue with a screen recording of this example: https://glitch.com/edit/#!/sage-quilted-hippopotamus, in a Chrome incognito window with all extensions disabled.

@carelevers I think the issue is on Glitch only. Do you reproduce the same issue outside of this site?

Hmm, yes, I am also experiencing the same issue on some sites where we use vlite with the YouTube provider. Additionally, in other sandbox environments, the issue persists: https://jsfiddle.net/a3tv6zpf/
[
https://github.com/vlitejs/vlite/assets/11197996/cec70615-84dc-42d7-a284-4fed131525ce
](url)
I don't know if there are other ways to reproduce this behavior?

I also receive a warning when autoplay is set to true and muted is set to true. When I unmute the video, I get the following warning:

Sorry for the delay, I think the problem is visible when the player is inside an other iframe. Glitch and JSFiddle use iframe to sandbox the content.
The url of the Glitch iframe works: https://vlitejs-youtube-video.glitch.me
But if I create an iframe with this url, the problem is visible.
Are you using Vlitejs in an iframe? Normally the problem is only present in this case.

I also receive a warning when autoplay is set to true and muted is set to true. When I unmute the video, I get the following warning:

This warning is normal because automatic playback with sound requires user interaction; it is the browser that decides whether sound will be activated, not Vlitejs.
More info from Chrome: https://developer.chrome.com/blog/autoplay

Hi no problem,
Specifically, I am having the issue with vLite on the website I'm working on, where it's not in an iframe. This page uses version 4.2.0 of vLite, but the same problem occurs with version 6.0.3. I'm not sure if the issue is specific to vLite, as I've experienced similar problems with other packages that implement a YouTube video player. I'll try to reproduce the issue in a sandbox environment without an iframe like jsfiddle, to see if it persists.
Here’s the link to the live site where the issue can be observed: Live Site.
Thank you for your assistance.

Hi, I managed to fix it! It wasn’t something with Vlitejs after all, sorry for the confusion :)
The issue was actually with this header in my .htaccess :
Header always set Permissions-Policy "accelerometer=self, autoplay=self, camera=(), gyroscope=self, magnetometer=(), microphone=(), payment=(), publickey-credentials-get=(), usb=()"
Specifically, the autoplay=self policy
Thanks for the help anyway!


Update the openfga organization in Github to be in an independent Github Org.

Relates to Relates to https://github.com/cncf/toc/issues/921

Ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners

https://auth0team.atlassian.net/servicedesk/customer/portal/3/SP-5506


[Enhancement][Cherry-Pick] Tips for optimizing replication_num when creating a table

Fixes #28501
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 15 / 17 (88.24%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
13
15
86.67%
[2251, 2252]

:large_blue_circle:
com/starrocks/common/util/PropertyAnalyzer.java
2
2
100.00%
[]


Neofetch on brew still requires Imagemagick and screenresolution

Neofetch on brew still requires imagemagick and screenresolution, even though it works fine without them (when running neofetch from source). The dependency on imagemagick was also removed in #956. So are these dependencies still required or are they optional? If you state that this dependency is not required I can make the PR on homebrew to remove the dependencies.
$ brew info neofetch
neofetch: stable 7.1.0 (bottled), HEAD
Fast, highly customisable system info script
https://github.com/dylanaraps/neofetch
/usr/local/Cellar/neofetch/7.1.0 (6 files, 351.5KB) *
  Poured from bottle on 2020-08-13 at 13:57:47
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/neofetch.rb
License: MIT
==> Dependencies
Required: imagemagick ✔, screenresolution ✘
==> Options
--HEAD
        Install HEAD version
==> Analytics
install: 4,986 (30 days), 15,486 (90 days), 76,797 (365 days)
install-on-request: 4,986 (30 days), 15,483 (90 days), 76,699 (365 days)
build-error: 0 (30 days)

By removing the imagemagick and screenresolution as dependency, the following packages don't have to be installed:
$ brew deps neofetch
docbook
docbook-xsl
freetype
gdbm
gettext
ghostscript
glib
gnu-getopt
ilmbase
imagemagick
jpeg
libde265
libffi
libheif
liblqr
libomp
libpng
libtiff
libtool
little-cms2
openexr
openjpeg
<EMAIL_ADDRESS>pcre
<EMAIL_ADDRESS>readline
screenresolution
shared-mime-info
sqlite
webp
x265
xmlto
xz

I recently got a conflict with ilmbase when brew upgraded ffmpeg. Turns out ilmbase is deprecated and the only reason it's installed is because of Neofetch:
~$ brew info ilmbase
ilmbase: stable 2.5.5 (bottled) [keg-only]
OpenEXR ILM Base libraries (high dynamic-range image file format)
https://www.openexr.com/
Deprecated because it is not supported upstream!
/usr/local/Cellar/ilmbase/2.5.5 (87 files, 1.8MB) *
  Poured from bottle on 2021-02-23 at 03:46:47
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/ilmbase.rb
License: BSD-3-Clause
==> Dependencies
Build: cmake ✔
==> Caveats
`ilmbase` has been replaced by `imath`. You may want to `brew uninstall ilmbase`
or `brew unlink ilmbase` to prevent conflicts.

ilmbase is keg-only, which means it was not symlinked into /usr/local,
because ilmbase conflicts with `openexr` and `imath`.

~$ brew uninstall ilmbase
Error: Refusing to uninstall /usr/local/Cellar/ilmbase/2.5.5
because it is required by neofetch, which is currently installed.
You can override this and force removal with:
  brew uninstall --ignore-dependencies ilmbase

It'd be nice if neofetch fixed this dependency.

This is a homebrew issue. I don't maintain the neofetch packages in distributions.

I was just seeking the confirmation that neofetch does not require imagemagick and screenresolution

Neofetch at a minimum requires only bash + coreutils. Features are used at runtime based on what is available. Take this up with the homebrew maintainer.


NoClassDefFoundError: zio/ZIO$Fail

Version: 3.11.0
Module: quill-jdbc / quill-jdbc-monix / quill-async-postgres
Database: Postgres
Expected behavior
No Exceptions thrown.
ZIO dependencies should be an implementation detail of quill and not require the app to explicitly depend on ZIO libs.
Actual behavior
Sometimes we see the following exception during unit test teardown. Test finishes successfully, though.
Exception in thread "Thread-23" java.lang.NoClassDefFoundError: zio/ZIO$Fail
	at zio.ZIO$.haltWith(ZIO.scala:3457)
	at zio.ZIO$.die(ZIO.scala:2647)
	at zio.internal.FiberContext.evaluateNow(FiberContext.scala:659)
	at zio.Runtime.unsafeRunWith(Runtime.scala:214)
	at zio.Runtime.unsafeRunSync(Runtime.scala:83)
	at zio.Runtime.unsafeRunSync$(Runtime.scala:80)
	at zio.Runtime$$anon$3.unsafeRunSync(Runtime.scala:280)
	at zio.Runtime.unsafeRun(Runtime.scala:58)
	at zio.Runtime.unsafeRun$(Runtime.scala:57)
	at zio.Runtime$$anon$3.unsafeRun(Runtime.scala:280)
	at zio.Runtime$.$anonfun$unsafeFromLayer$4(Runtime.scala:308)
	at zio.internal.PlatformSpecific$$anon$1.run(PlatformSpecific.scala:37)
Caused by: java.lang.ClassNotFoundException: zio.ZIO$Fail
	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	... 12 more

A ZIO class seems to be required, but not bundled with quill. We have no ZIO dependencies in our app ourself.
Steps to reproduce the behavior
We would need to provide a scaled-down version of our app. The exception ist not happening every time though.
Workaround
Could probably be fixed by adding an explicit dependency to a ZIO lib.
@getquill/maintainers

Getting same error when trying to specify -Dquill.macro.log=false in sbt launcher script. Looks to be related to #1715 implementation as it uses zio-logging now . Rolling back to 3.10.0

Will fix this issue for 3.12.0. For now try -Dquill.log.file=false.

@nilius I've decided to incorporate various ZIO infrastructure into Quill since Quill's motto of zero-dependencies is starting to get unsustainable. That is because zero-dependencies ultimately means that you have to do everything yourself. We have already built our own IO monad, our own tracing system, our own ADT transformation system, and contexts for 3 different driver-frameworks for 6 different databases (6 driver-frameworks for 9 databases if you count all the big-data things), the Quill deploy alone has ~100 jars. This is getting totally unsustainable. Meanwhile, users are complaining about the Quill contexts being buggy and there much context-specific code I can never hope to get to. Right now I am at a breaking point. Either I choose a pre-existing infrastructure library to use for my base-context implementations or I give it all up.
So instead I've decided to start incorporating ZIO components. Firstly in order to ship new features like Query-logging but eventually to be able to rewrite the contexts so that I can continue maintaining this project.
As for the zio.ZIO$Fail issue, I'm going to work on it and try to fix it before the next release.

@deusaquilus  I can definitely understand the stress of having to maintain an open source project in your free time. What does that mean for the future with respect to available contexts? Will only zio-jdbc be supported? I would definitely appreciate it if there was another well maintained non-zio-specific context with streaming available. Firstly because it would be a hard sell at work to use all the ZIO stuff and secondly because I have a feeling that the ZIO-team is stretching itself too thin, so I don't fully trust the non-core ZIO libraries. Perhaps something based on Doobie or jasync with Monix would work; both projects seem fairly active.

@tschuchortdev Contexts will keep the same external APIs but might be different under the hood. For the most part I am sticking to the ZIO-Core libraries which are well maintained. Once ZIO 2 is out I won't even need a zio-logging dependency since it will be part of the core functionality.

See also https://github.com/zio/zio-quill/issues/2333


can't create buckets with policy

I'm using flux 2 (gitops)
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: ack-s3-controller
spec:
  releaseName: ack-s3-controller
  chart:
    spec:
      chart: s3-chart
      version: "v1.0.3"
      ...

apiVersion: s3.services.k8s.aws/v1alpha1
kind: Bucket
metadata:
  name: staging-bucket-it
spec:
  name: staging-bucket-it
  acl: private
  versioning:
    status: Enabled
  ownershipControls:
    rules:
      - objectOwnership: BucketOwnerPreferred
  policy: |
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Sid": "AllowPublicRead",
          "Effect": "Allow",
          "Principal": {
            "AWS": "*"
          },
          "Action": "s3:GetObject",
          "Resource": "arn:aws:s3:::staging-bucket-it/*"
        }
      ]
    }
  cors:
    corsRules:
      - allowedHeaders:
          - "Authorization"
        allowedMethods:
          - "GET"
        allowedOrigins:
          - "https://mydomain.com"
        maxAgeSeconds: 3000

The problem is that the AWS S3 controller fails with a 403 Forbidden error when it tries to perform a policy update right after creating the bucket. The bucket gets created, but without the policy, CORS settings, or the publicAccessBlock setting, if present. I've tried various combinations of adding and removing settings, but I still can't get the bucket to work properly with publicly accessible content on the first synchronization attempt.
I also tried setting the publicAccessBlock to allow public access, but that doesn't work either. The controller attempts to set the policy before applying the publicAccessBlock setting, causing the synchronization to fail.
The only way I've been able to get it to work is by manually going into the AWS S3 console, navigating to the Permissions tab of the "created-but-not-configured" bucket, editing the "Block public access (bucket settings)" settings, ensuring that no checkboxes are selected, and then saving the changes. After that, the synchronization works as expected.
I've raised this issue on GitHub because I'd like to know if there's a way to set up the bucket with publicly accessible content using a manifest without having to resort to manual intervention in the AWS console.

I was able to reproduce the error, and then by syncing the public access configuration before trying to sync the policy I found that it works. This is the modified version of the manifest that I ran (note publicAccessBlock - I'm not sure if they're necessary, but I added them to be sure I had permissions):
apiVersion: s3.services.k8s.aws/v1alpha1
kind: Bucket
metadata:
  name: issue-1796
spec:
  name: issue-1796
  acl: private
  versioning:
    status: Enabled
  publicAccessBlock:
    blockPublicPolicy: false
    blockPublicACLs: true
    ignorePublicACLs: true
  ownershipControls:
    rules:
      - objectOwnership: BucketOwnerPreferred
  policy: |
    {
      "Version": "2012-10-17",
      "Statement": [
        {
          "Sid": "AllowPublicRead",
          "Effect": "Allow",
          "Principal": {
            "AWS": "*"
          },
          "Action": "s3:GetObject",
          "Resource": "arn:aws:s3:::issue-1796/*"
        }
      ]
    }
  cors:
    corsRules:
      - allowedHeaders:
          - "Authorization"
        allowedMethods:
          - "GET"
        allowedOrigins:
          - "https://mydomain.com"
        maxAgeSeconds: 3000

The bug fix for this situation is linked above

https://github.com/aws-controllers-k8s/s3-controller/releases/tag/v1.0.4 was just released, which contains this fix. Please try it out and let me know if it works.

my system still can't see 1.0.4
chart pull error: failed to download chart for remote reference: failed to get 'oci://public.ecr.aws/aws-controllers-k8s/s3-chart:v1.0.4': public.ecr.aws/aws-controllers-k8s/s3-chart:v1.0.4: not found

I'm not sure this is intended https://github.com/aws-controllers-k8s/s3-controller/commit/e0addd656d76730fbf0eac428e29f4520b0525ba
but it removed the "v" before the helm chart versions, so I had to set version: "1.0.4" instead of version: "v1.0.4" to find the new version.
anyway I'm testing the changes, will report back.

I'm not sure this is intended aws-controllers-k8s/s3-controller@e0addd6
but it removed the "v" before the helm chart versions, so I had to set version: "1.0.4" instead of version: "v1.0.4" to find the new version.

Yes, we recently changed the versioning schema to remove the v. Please see the community issue - https://github.com/aws-controllers-k8s/community/issues/1802

s3 bucket to allow for direct changes without passing through an AdoptedResource

The resources have to be actively managed by the S3 controller for you to make changes to them. We can't just edit a single field individually.

so I guess the original problem described in the issue should be solved

Since this original issue has been solved, I'm going to close this GH issue. I'm happy to talk about the issue of S3 bucket adoption, if you want to open a separate GH issue for that - so we can track it separately.


Potentially allow mev-boost run even when check relays fails for one

If validators are connecting to multiple relays and one goes down, should this stop mev-boost?
https://github.com/flashbots/mev-boost/blob/c5344c20eaab2c3b95d7b8652945a098e1367a87/server/service.go#L544

Only at startup, all relays need to be reachable, otherwise mev-boost doesn't start.
During running, it's only used for the getStatus request.

good point... sounds reasonable to just warn on startup, instead of fail completely.

Fixed in mev-boost v1.2.1: https://github.com/flashbots/mev-boost/releases/tag/v1.2.1


co19/LanguageFeatures/FinalizationRegistry/no_ffi/Finalizer/noSuchMethod_A01_t01 crash

Said test causes a crash on the following configurations, cf. https://github.com/dart-lang/co19/issues/1316:
dartk-strong-linux-debug-x64
dartk-strong-linux-release-simarm
dartk-strong-linux-release-simarm64
dartk-strong-linux-release-x64
dartk-strong-win-release-x64
dartk-weak-asserts-linux-debug-x64
dartk-weak-asserts-linux-release-simarm
dartk-weak-asserts-linux-release-simarm64
dartk-weak-asserts-linux-release-x64
dartk-weak-asserts-win-release-x64
dartkp-strong-linux-debug-x64
dartkp-strong-linux-release-simarm64
dartkp-strong-linux-release-x64
dartkp-strong-mac-release-simarm64
dartkp-strong-win-release-x64
dartkp-weak-asserts-linux-debug-x64
dartkp-weak-asserts-linux-release-simarm64
dartkp-weak-asserts-linux-release-x64
dartkp-weak-asserts-mac-release-simarm64
dartkp-weak-asserts-win-release-x64

Here is an example stack trace:
Unhandled exception:
Expect.throws(): Unexpected UnimplementedError(UnimplementedError: Finalizer)
#0      new Finalizer (dart:core-patch/expando_patch.dart:198)
#1      finalizer (file:///C:/b/s/w/ir/tests/co19/src/LanguageFeatures/FinalizationRegistry/no_ffi/Finalizer/noSuchMethod_A01_t01.dart:16)
#2      main.<anonymous closure> (file:///C:/b/s/w/ir/tests/co19/src/LanguageFeatures/FinalizationRegistry/no_ffi/Finalizer/noSuchMethod_A01_t01.dart)
#3      Expect.throws (file:///C:/b/s/w/ir/tests/co19/src/Utils/expect_common.dart:186)
#4      main (file:///C:/b/s/w/ir/tests/co19/src/LanguageFeatures/FinalizationRegistry/no_ffi/Finalizer/noSuchMethod_A01_t01.dart:19)
#5      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:297)
#6      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192)

#0      _fail (file:///C:/b/s/w/ir/tests/co19/src/Utils/expect.dart:18)
#1      Expect.throws (file:///C:/b/s/w/ir/tests/co19/src/Utils/expect_common.dart:189)
#2      main (file:///C:/b/s/w/ir/tests/co19/src/LanguageFeatures/FinalizationRegistry/no_ffi/Finalizer/noSuchMethod_A01_t01.dart:19)
#3      _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:297)
#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:192)

We haven't landed the implementation in the VM yet.

@dcharkes, I created these issues (#48573, #48574, #48575) because they don't have the same failing configurations, so it thought it could be ongoing work. However, it sounds like you'd prefer to avoid having issues like this. Would it be a safe bet that UnimplementedError should never be reported as an issue as long as the given feature is likely to be unfinished?

Yeah, it's better to just take a look at the 'current status' after landing the CL and then triage them all in one go instead of looking at deltas before landing.

'March Release' milestone ?


Actually implement RegionTypeInfinite

~Depends on #327 which depends on #326 which depends on #286~
I’ve implemented this pr for several reasons:
Compatability
On its own this PR slightly increases compatibility with GDI+ as infinite regions are encoded in the data as a type of 0x10000003 instead of a type 0x10000001 and a rectangle with infinite size.
However, this now allows us to differentiate between infinite and non-infinite regions which, in a future PR will be used to increase the compatability with GdipGetRegionData even more
Performance
The cost of creating a new Region() is now cheaper and avoids allocations by creating an infinite rect and putting it in an array.
In the future this flag can easily be used in other settings to increase performance

I’ve implemented this pr for several reasons:
Compatability
On its own this PR slightly increases compatibility with GDI+ as infinite regions are encoded in the data as a type of 0x10000003 instead of a type 0x10000001 and a rectangle with infinite size.
However, this now allows us to differentiate between infinite and non-infinite regions which, in a future PR will be used to increase the compatability with GdipGetRegionData even more
Performance
The cost of creating a new Region() is now cheaper and avoids allocations by creating an infinite rect and putting it in an array.
In the future this flag can easily be used in other settings to increase performance

At least GdipGetRegionScans is returning incorrect results for infinite regions now.

On hold until https://github.com/mono/libgdiplus/pull/287 and https://github.com/mono/libgdiplus/pull/286 are merged
Then I'll send out some PRs fixing other issues I uncovered when writing unit tests

@hughbe could you update the PR?

Fixes #391
Fixes #335
Fixes #337
Fixes #341
Fixes #343
Fixes #344
Contributes to #336
Contributes to #338
Contributes to #339
Contributes to #342

I have just updated this PR. It now fixes lots of edge cases for various region combine methods that were broken or incorrect before.
The list of edge cases covered are
•	Infinite + X = X
o	/* The intersection of the infinite region with X is X */
•	X + Infinite = X
o	/* The intersection of the infinite region with X is X */
•	X + Empty = Empty
o	/* The empty region does not intersect with anything */
•	Empty + X = Empty
o	/* The empty region does not intersect with anything */

Union
•	Infinite + X = Infinite
o	/* The union of the infinite region and X is the infinite region */
•	X + Infinite = Infinite
o	/* The union of the infinite region and X is the infinite region */
•	X + Empty = X
o	/* The union of the empty region and X is X */
•	Empty + X = X
o	/* The union of the empty region and X is X */

XOR
•	Empty + X + X
o	/* The XOR of the empty region and X is X */
•	X + Empty = X
o	/* The XOR of the empty region and X is X */

Exclude
•	Empty + X = Empty
o	/* Nothing is outside the empty region */
•	X + Empty = X
o	/* Everything is outside the empty region */
•	X + Infinite = Empty
o	/* Nothing is outside the infinite region */

Complement
•	Empty + X = X
o	/* Everything is outside the empty region */
•	X + Empty = Empty
o	/* Nothing is inside the empty region */
•	Infinite + X = Empty
o	/* Nothing is outside the infinite region */

I do like the PR in general, but the unit test failures must be accounted for first:
1) Complement_383878 (MonoTests.System.Drawing.TestRegion.Complement_383878)
     Length
  Expected: 2
  But was:  1
  at MonoTests.System.Drawing.TestRegion.Complement_383878 () [0x0006e] in /home/travis/build/mono/mono/mcs/class/System.Drawing/Test/System.Drawing/TestRegion.cs:1476
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0003b] in /home/travis/build/mono/mono/mcs/class/corlib/System.Reflection/MonoMethod.cs:305
2) Intersect_383878 (MonoTests.System.Drawing.TestRegion.Intersect_383878)
     IsEmpty
  Expected: False
  But was:  True
  at MonoTests.System.Drawing.TestRegion.Intersect_383878 () [0x00020] in /home/travis/build/mono/mono/mcs/class/System.Drawing/Test/System.Drawing/TestRegion.cs:1451
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0003b] in /home/travis/build/mono/mono/mcs/class/corlib/System.Reflection/MonoMethod.cs:305

I missed out handling negative rects - quite an odd edge case but this is fixed now. Turns out we had tests for this but I had disabled them even against Windows GDI+ and made some typos that meant they were testing the wrong thing. Fixed now!


Formatted all Markdown Files with vscode Extension

Semua file gw format biar lucuw terutama table

Deemed unnecessary and hindering to those who doesn't use the same formatter


Derive Copy, Clone, and Debug for handles

This just reduces code gen and improves readability.

Both #3015 and #3016 are failing with this GNU dlltool error:
https://github.com/microsoft/windows-rs/actions/runs/8924805385/job/24511973178?pr=3015
Unrelated to this change I believe. Any idea what this might be about? Perhaps a change to the GitHub runners?
@riverar @jeremyd2019 @mati865

Looks like GHA have changed somehow:
C:\msys64\mingw32\bin\dlltool.exe ... -m i386:x86-64

32-bit dlltool cannot create x86_64 import libraries.

Looping in @mati865 for awareness, as they have some dlltool work in the pipe https://github.com/rust-lang/rust/pull/124138

dlltool.exe is normally located by explicitly scouring PATH, which probably got re-ordered in a GHA runner update.
So I suspect adding an explicit dlltool configuration should help here. Let's give it a shot.

On the second thought, failing test runs on x86_64 host but targets i686. But it's a proc macro so it should still build for the host.
It could really be a regression then.

We manually prepend C:\msys64\mingw32\bin onto the path when targeting i686-pc-windows-gnu, not taking proc macros into consideration. So I think the build failure makes more sense to me than the previous successes.

Ah, makes sense then. Previous success doesn't make sense though 😄
It'd probably work if you set PATH to /mingw64/bin:/mingw32/bin:$PATH for cross-compilation builds since 64-bit dlltool can generate both kinds of libraries and the linker is called with a target triple prefix.

Should handle types also #[derive(PartialOrd, Ord)] so they can be stored as keys in BTreeSets/BTreeMaps? Likewise, #[derive(Hash)] would make them eligible as the key in HashSets/HashMaps.

Note that this PR isn't adding these traits - it's merely deriving them rather than generating them directly.


[sysrst_ctrl] Review and merge  #13556

This PR:  #13556 adds a new chip level test for sysrst_ctrl. We must determine if it is still needed and merge (after any required changes) if so.

@doreis-lowrisc, @crteja, @marnovandermaas please note

I decided to close that PR because the test was implemented by @abdullahvarici in October last year and has already been merged into the main repo.


Add English, Spanish and Chinese DateTime Recognizers

@ejadib,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


[Suggestion] Getting spam remaining time from HCore.spam(id, cooldown)

Example:
HCore.spam(id, cooldown) will return remaining time

Hi! Actually HCore.spam(id, cooldown) returns boolean. But If you want I can add HCore.spam(id) to return remain time?

yes.
u can also do something like:
HCore.spam(id, time, TimeUnit/Duration)
and it will return remaining time but it will be returned in provided time unit or duration, example:
HCore.spam("id", 2, TimeUnit.SECONDS)
after 0.5 seconds for example it will return 1.5, or after. 2 seconds it will return 0, so, it means that remaining time end
or:
HCore("id", 15, TimeUnit.MINUTES)
and it will return remaining time in hours, like after 5 minutes it will return
10

This should work for you. (https://github.com/hakan-krgn/hCore/commit/f901db095d8191d83c45bceeb53124fe64d6d72a)


DNM: Some firebase Android workarounds to make progress on more issues

crash serialization is tracked here:
https://github.com/thebrowsercompany/swift-firebase/pull/78


Init-Picovoice without Internet

Hello everyone and Picovoice developers. Currently I am testing an embedded device running an application compiled from C/C++ and using the free version of Picovoice. I noticed that the device must always be connected to the Internet for Picovoice to be able to initialize successfully. Is there any other way to make our device work Offline with Picovoice? That is, without Internet, Picovoice can still successfully initialize?

@bmt1596 you don't need constant connevtivity. You only need connectivity for the initial init and then it can work 100% offline for days. You do need connectivity every couple of weeks though. Connectivity is needed for license management.

So, this is cloud connected, online-only, software advertised as on device?
Big oof.


SSL not working

Unfortunately, ssl settings are not working. Can anyone help?
I am following this;
https://github.com/awslabs/mxnet-model-server/blob/master/docker/advanced_settings.md#configuring-ssl
but no luck.

@vdantu , @frankfliu , could you please assist?

Hi @theprodev
The documentation here needs to be updated and will not produce a working server if followed.  Here are some more accurate steps:

Acquire/Create SSL certificates and rename them to nginx.crt and nginx.key (to match the names you put in the .conf file in step 2)
Create mms_app.conf as follows:
a. Copy mxnet-model-server/docker/mms_app_cpu.conf as your starting point
b. Change the [Nginx Configurations] section to the SSL settings given to enable SSL
c. Replace the path /etc/nginx/ssl in those settings with a path that works from your docker container: /ssl/nginx.crt and /ssl/nginx.key. Note that we map the directory containing the certificates to /ssl in step 3
Run a docker instance with docker run -itd --name mms -v /path/to/mmsconfig/dir:/config -v /path/to/ssl/files:/ssl -p 8080:443 -p 8081:80 awsdeeplearningteam/mms_cpu. This allows your docker container to access the config file at /config/mms_app.conf and the ssl files at /ssl/nginx.crt and /ssl/nginx.key.  It also uses a different prebuilt image from the awsdeeplearningteam.
Run docker exec mms bash -c "mxnet-model-server start --mms-config /config/mms_app.conf" to start mms inside your docker container named mms using the configuration you built in step 2
At this point, you can use curl commands curl -X GET https://your_public_host_name:8080/ping and curl -X GET http://your_public_host_name:8081/ping to check if both your http and https are working.  If you did not get your SSL certificates from a certificate authority, you will need to use curl -k -X GET https://your_public_host_name/ping for insecure.
If you have issues, you can view your nginx logs by running docker exec mms cat /var/log/nginx/access.log and docker exec mms cat /var/log/nginx/error.log. If it complains that your container is not running, restart it with docker start mms.

Do these steps help at all?  If you still have problems, please share what steps you followed and any output or files that you created.

MMS 1.0 release will use new set of SSL configuration, see:  https://github.com/awslabs/mxnet-model-server/blob/master/docs/configuration.md#enable-ssl


Create README.md

Proposing a draft WER metric card, @lhoestq I'm not very certain about "Values from popular papers" -- I don't know ASR very well, what do you think of the examples I found?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

For ASR you can probably ping @patrickvonplaten

I put "Values from popular papers" as a subsection of "Output values" -- I hope that's a compromise that works for everyone :hugs:


Can't edit files on network drives

I'm having problems with text files opening on network drives. I can open folders and see all files in the treeview, but as soon try to open a file in the editor, nothing happens (no error, no message, no contents). This does not happen to images (.png & .gif). I originally reported it here: https://github.com/atom/atom/issues/2313#issuecomment-70653160, but after inspection (running --safe-mode and enabling/disabling all packages) this seems only related to atom-editorconfig.
Windows 8.1
Atom 0.174.0
Editorconfig 0.3.0

I have the same problem. Under Windows, I can open files from mapped network drives but not from UNC paths. After uninstalling this addon, it worked fine.

This plugin doesn't do anything with the path directly the issues is with https://github.com/editorconfig/editorconfig-core-js
Can you console.log the file path passed to this plugin: https://github.com/sindresorhus/atom-editorconfig/blob/d4ab369634e07d67dea7a834473b7af8189e6163/index.js#L13 and share it here?
I've opened an issue on the EditorConfig issue tracker: https://github.com/editorconfig/editorconfig/issues/195

After a lot of console.log's I've found out that the code bugs on https://github.com/editorconfig/editorconfig-core-js/blob/master/editorconfig.js#L69 where path.resolve(filepath).match(/^[^\\]+\\/) resulting in null, making [0] not possible.

The real path is private, but it's something like:
\\<IP_ADDRESS>8\folder\folder\www.site.com_1.2.3a\folder\folder

:frowning: I'm having this issue, too.

@sindresorhus I just released version 0.12.2 of the JS core library which should fix this.

You guys are all awesome. Works like a charm! :clap: