Logging improvements

CHANGE DESCRIPTION
Problem:
Misaligned controller names and using the wrong logger which prevents config it with LOG_LEVEL and LOG_STRUCTURED env variables.
Cause:
Besides the logger that we set up in manager/main.go, inside controllers we set up a different logger which is then used for logging.
Solution

Use propper logger
Aling controller names to pxc-controller, pxcbackup-controller and pxcrestore-controller

CHECKLIST
Jira

[x] Is the Jira ticket created and referenced properly?
[x] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[x] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[x] Is an E2E test/test case added for the new feature/change?
[x] Are unit tests added where appropriate?
[x] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[x] Are all needed new/changed options added to default YAML files?
[x] Are the manifests (crd/bundle) regenerated if needed?
[x] Did we add proper logging messages for operator actions?
[x] Did we ensure compatibility with the previous version or cluster upgrade process?
[x] Does the change support oldest and newest supported PXC version?
[x] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
failure

users-5-7
failure

users-8-0
failure

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/202edb6d62e20a10c965adddb31e58a605bc3b1d
image: perconalab/percona-xtradb-cluster-operator:PR-1369-202edb6d

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/202edb6d62e20a10c965adddb31e58a605bc3b1d
image: perconalab/percona-xtradb-cluster-operator:PR-1369-202edb6d

Test name
Status

affinity-8-0
skipped

auto-tuning-8-0
skipped

cross-site-8-0
skipped

demand-backup-cloud-8-0
skipped

demand-backup-encrypted-with-tls-8-0
skipped

demand-backup-8-0
skipped

haproxy-5-7
skipped

haproxy-8-0
skipped

init-deploy-5-7
skipped

init-deploy-8-0
skipped

limits-8-0
skipped

monitoring-2-0-8-0
skipped

one-pod-5-7
skipped

one-pod-8-0
skipped

pitr-8-0
skipped

proxy-protocol-8-0
skipped

proxysql-sidecar-res-limits-8-0
skipped

recreate-8-0
skipped

restore-to-encrypted-cluster-8-0
skipped

scaling-proxysql-8-0
skipped

scaling-8-0
skipped

scheduled-backup-5-7
skipped

scheduled-backup-8-0
skipped

security-context-8-0
skipped

smart-update1-8-0
skipped

smart-update2-8-0
skipped

storage-8-0
skipped

tls-issue-cert-manager-ref-8-0
skipped

tls-issue-cert-manager-8-0
skipped

tls-issue-self-8-0
skipped

upgrade-consistency-8-0
skipped

upgrade-haproxy-8-0
skipped

upgrade-proxysql-8-0
skipped

users-5-7
skipped

users-8-0
skipped

validation-hook-8-0
skipped

We run 0 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/8c8ffce7420d79939ff0b106a167f17f9ae43623
image: perconalab/percona-xtradb-cluster-operator:PR-1369-8c8ffce7

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
failure

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
failure

users-8-0
passed

validation-hook-8-0
passed

We run 36 out of 36

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/c50fb0e820ef08afd394a2f609ff7d0814396720
image: perconalab/percona-xtradb-cluster-operator:PR-1369-c50fb0e8

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
failure

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
failure

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/c9ff245f6afde5c8fdfece7017214c925e090d30
image: perconalab/percona-xtradb-cluster-operator:PR-1369-c9ff245f

Test name
Status

affinity-8-0
skipped

auto-tuning-8-0
skipped

cross-site-8-0
skipped

demand-backup-cloud-8-0
skipped

demand-backup-encrypted-with-tls-8-0
skipped

demand-backup-8-0
skipped

haproxy-5-7
skipped

haproxy-8-0
skipped

ignore-labels-annotations-8-0
skipped

init-deploy-5-7
skipped

init-deploy-8-0
skipped

limits-8-0
skipped

monitoring-2-0-8-0
skipped

one-pod-5-7
skipped

one-pod-8-0
skipped

pitr-8-0
skipped

proxy-protocol-8-0
skipped

proxysql-sidecar-res-limits-8-0
skipped

recreate-8-0
skipped

restore-to-encrypted-cluster-8-0
skipped

scaling-proxysql-8-0
skipped

scaling-8-0
skipped

scheduled-backup-5-7
skipped

scheduled-backup-8-0
skipped

security-context-8-0
skipped

smart-update1-8-0
skipped

smart-update2-8-0
skipped

storage-8-0
skipped

tls-issue-cert-manager-ref-8-0
skipped

tls-issue-cert-manager-8-0
skipped

tls-issue-self-8-0
skipped

upgrade-consistency-8-0
skipped

upgrade-haproxy-8-0
skipped

upgrade-proxysql-8-0
skipped

users-5-7
skipped

users-8-0
skipped

validation-hook-8-0
skipped

We run 0 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/1d3011d5ad8124018360057cd25d58018fb266f6
image: perconalab/percona-xtradb-cluster-operator:PR-1369-1d3011d5

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/8c216b0d81b298622b4a9a83b24aaab877707082
image: perconalab/percona-xtradb-cluster-operator:PR-1369-8c216b0d

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/a5969ffd9233bcecf5230ea12f0b955ee04adaa4
image: perconalab/percona-xtradb-cluster-operator:PR-1369-a5969ffd

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
failure

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/ec75f79ab5924993421048b6ca5022293098763a
image: perconalab/percona-xtradb-cluster-operator:PR-1369-ec75f79a

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/8b6b87a9ba60261adadd22b325c6c3dc82530b91
image: perconalab/percona-xtradb-cluster-operator:PR-1369-8b6b87a9

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1369/commits/8b6b87a9ba60261adadd22b325c6c3dc82530b91
image: perconalab/percona-xtradb-cluster-operator:PR-1369-8b6b87a9


Redesign channel updates API

Currently, the go-perun client exposes two APIs for updating a channel: Update and `UpdateBy'.
func (c *Channel) Update(ctx context.Context, next *channel.State) (err error) {...}
func (c *Channel) UpdateBy(ctx context.Context, update func(*channel.State) error) (err error) {...}

In both cases, the user can modify any property of the state:

Version
Any field in Allocation (Assets, Balances or Locked funds that contain sub-allocations).
Data
IsFinal flag

In many scenarios, arbitrarily modifying these fields would lead to invalid updates that will fail. For instance,

Version must be incremented by 1 for each update, but this API allows the user to arbitrarily modify the version.
Assets field in Allocation must not be changed. It should only read by the user.
Locked funds should not be modified by the user. It is meant only for those updates that fund/withdraw sub/virtual channels. These updates will be done only by the SDK and not by the user.
IsFinal flag can be set only when certain conditions are met. Eg: For ledger channels, there should be no locked funds.

It will a lot of overhead on the user to ensure these conditions when making an update.
Hence, I propose to redesign the update API to make it more easy to use. It can replace both the existing APIs:
Update(updater func(Balances, Data) error) (err error) {...}

In this API,

User is able to modify only the balances and data.

API will validate if sum of balances remain constant and if data is valid for the given app.

If user needs info on Assets or App, they could read it from the channel. These are set during channel opening and never change during the lifetime of the channel.
~3. Finalize flag can be used to finalize a channel. The API will apply the finalize flag only after ensuring if necessary conditions are met.~

Update 1: Removed the finalize flag in the API. If we do not want the user to initiate a final update. The final update can be initiated by the framework when settling the channel.

@matthiasgeihs

@manoranjith
I agree with much of what was written. Some thoughts and questions below.

You propose Update(updater func(Balances, Data) error) (err error) {...}, but how to return the modified values?
How to access the state when the channel is locked during the update?
At first we may want to include a way to modify set the final flag manually. Otherwise the scope of this change will become much larger.

@matthiasgeihs

The modified values need not be returned. Because, what the SDK does it:

Read the latest state.
Modify it using the updater.
Modify some more parameters (inc version, mark as final etc.,)
Do sanity checks
Sign it and propose the update to peer and apply if accepted.

So, the best way for the user to retrieve the modified state will be to use ch.State() after the Update / ForceUpdate function returns.

I don't get your point on accessing the state when the channel is locked ? Because when the channel is locked, we simply shouldn't access the state. User should only be able to read the current Data, Balances (which the updater will receive as inputs) and modify them.`

Yes, I agree that, we should provide a final flag. Client could validate the necessary per-requisites before marking the channel as final and return an error if they are not met.
So, the updated signature could be

Update(updater func(Balances, Data) error), finalize bool) (err error) {...}

I have made a suggestion here: https://github.com/hyperledger-labs/go-perun/compare/main...perun-network:c8b747a1eba9503372e8d16b073d6e7e79f57e83
At the core it proposes the following:

A new type UpdateState where only certain state properties are mutable.
The function signature Update(ctx context.Context, update func(UpdateState) error) error, which passes UpdateState to the update function and thereby controls which state properties can be modified by the user.

Yes, I was referring to that,
Once change in the suggestion would be to take finalize as a boolean flag, rather than making it mutable. Because a state should be marked final only when it meets certain pre-conditions (such as no locked funds), which the client should ensure before marking it as final.
One the other hand changing SetFinal(b bool) to SetFinal(b bool) error could also work.

But we need to be able to set the final flag somewhere. If we cannot set it during state update, we need to be able to set it through calling a different function. For example, we might modify channel.Settle so that it first attempts to update the channel to final off chain. However, this would be a larger change with consequences on how a user interacts with the framework overall, and therefore I would rather like to do that separately. The main point with my suggestion is that I would like to prevent the user from being able to update the version when this is clearly not intended.

Yes, I agree changing a different paradigm of automatically trying to finalize before settle would be a larger change that should be done separately. So, we should indeed allow the user to mark a state as final.
But, there can be an error when SetFinal is called. For eg: when there are locked funds. But, the current API SetFinal(b bool) assumes there will be no error and that the call will always succeed.
The solution, as I described in the previous comment is either modify the signature of SetFinal or to take finalize as a boolean argument and when the the pre-conditions are not met, Update returns an error.


how to reset the Cactus?

i have a  Cactus  to Install WHID Injector.i have some problems when i Install ESP_Programmer,it always become pro micro 3.3V  and can not install drive,then Arduino will say  programmer did not respond to command: exit bootloader.
so i want to reset the Circuit board，can u tell me the way to  reset the Cactus?

maybe i selected other board before,now board the red led no blinking

http://wiki.aprbrother.com/wiki/Cactus_Micro_Rev2_Troubleshooting_and_FAQ#How_to_Revive_a_.E2.80.9CBricked.E2.80.9D_Cactus_Micro

If it doesn't work... 99% is your computer.

Try with another one (maybe on a USB 2.0 port)
Change Arduino IDE version (sometimes it get screwed-up)
Completely uninstall and reinstall the existing version of Arduino IDE


any plan of publishing some nuget package for these awesome works?

I'll try to make it an application template once upgrade it to the latest versions of ABP Framework and MudBlazor.
Thanks...


Code for analyzing snATAC-seq data

Hi,

Is there the code for integrating and annotating cluster labels of spatial ATAC-seq data and snATAC-seq data in mouse embryo displayed in Figure 1 h-j?
Is it possible for you to provide the cluster label names such as "Forebrain", "Facial/bone" displayed in Figure 1 c-g? I know you have provided the code for unsupervised clustering, but how can I know what do cluster "0", "1", "2", ... mean?
Thanks.

Hi ttgump,
Thank you for reaching out and for your interest in our research and data!

I added a metadata file to this repo (metadata_integrated_snatac_ours.csv), which includes annotated cluster labels for the snATAC and sATAC integrated object (Figure 1 h-j). The naming was assigned by exploring the expression of the cluster markers from the integrated dataset in the MOCA reference atlas here [https://oncoscape.v3.sttrcancer.org/atlas.gs.washington.edu.mouse.rna/genes] with manual supervision based on the spatial location.
In addition, you can find the code used to integrate the datasets in the file named embryo_sc_integration.R (lines 1-225).

You can find the cluster IDs (0,1,2 etc) in the metadata published on GEO ([https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE214991]). The annotations are as follows:

combined <- RenameIdents(combined,
"5" = "Forebrain", "7" = "Midbrain", "2" = "Hindbrain",
"9" =  "Periventricular", "3" = "Meningeal/PNS", "4" = "Meningeal/PNS", "8" = "Internal",
"0" = "Facial/bone", "1" = "Muscle/Heart", "10" = "Limb", "6" = "Liver")

Let me know if there's anything else I can do for you!


onedrive: add support for Move and MoveDir

Onedrive is capable of Move and MoveDir with the update method

To make --backup-dir work really well on onedrive this is needed.
(Fix the overview table when implemented!)

@olihey have you got time to look at this?

@ncw Sure, I can give it a try but not 2017, busy with day job :)

This is done - thanks @Cnly :-)
It will be in the latest beta shortly and in v1.43

This is done now - thanks @Cnly :-)
https://beta.rclone.org/v1.42-083-gd95667b0/ (uploaded in 15-30 mins)


Typescript typings

Currently the typings in the NPM package are null, preventing type safety when using this with typescript.
Given the fact this is made in typescript, is this intentional?

Well I didn't work on typings although the project is on Typescript it intended to be used with Truffle which is JS framework, so the TS generates the JS lib before publishing on NPM

Truffle supports typescript test files in the latest versions, so this issue still remains. There is a usecase for typescript usage of this package that is not possible (or at least, not typesafe) purely because the types are exported. If the package is written in TS, it should be easy to add those types the npm package.

So fixing my previous statement, I was checking and the d.ts files are generated indeed, they exist on node_modules/loom-js/dist/*.d.ts, right now I'm using the VSCode and when I code in pure JS the editor autocomplete with all information about the types from loom-js, because the types exist on the package there's no needing from another package like @types/loom-js


module 'warpctc_pytorch' has no attribute 'gpu_ctc'

Hi, I am trying to reproduce the transformer result on Librispeech, however at stage 4, I encounter an error of "module 'warpctc_pytorch' has no attribute 'gpu_ctc' " when calculating the ctc loss. Any idea why?

@zyzpower Did you set path to CUDA, NCCL before installation?

hi, you mean this setting right
CUDAROOT=/usr/local/cuda
NCCL_ROOT=/usr/local/nccl

@zyzpower I think you failed to compile warp-ctc on the GPU mode. Instead, you can also use the native CTC on pytorch.

Same issue as #181. Already fixed by #232.

Same issue as #181. Already fixed by #232.


Unexpected model serialization based on the field annotation and the extra configuration

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Hey there,
I am having an issue with model serialization in Pydantic v2.
To showcase it, let's say I have a model called MyModel with a config field of type BaseConfiguration. Depending on the use case, I want to be able to assign different types of configurations to this field, or in other words, other instances of subclasses inheriting from the BaseConfiguration class (such as the SubConfiguration class).
Creating such instances does not raise a ValidationError, however, while serializing these instances, I got some outputs I was not expecting. Moreover, the outcomes change again depending on the extra parameter, set in the ConfigDict of the configuration classes.
I created the following table to showcase the different behaviors:

param_1
param_2
param_3
Outcome

allow
allow
BaseConfiguration
{'config': {'a': 1}}

allow
forbid
BaseConfiguration
{'config': ({'a': 1, 'b': '2'}, None)}

forbid
allow
BaseConfiguration
{'config': {'a': 1}}

forbid
forbid
BaseConfiguration
{'config': {'a': 1}}

allow
allow
SubConfiguration
{'config': {'a': 1, 'b': '2'}}

allow
forbid
SubConfiguration
{'config': {'a': 1, 'b': '2'}}

forbid
allow
SubConfiguration
{'config': {'a': 1, 'b': '2'}}

forbid
forbid
SubConfiguration
{'config': {'a': 1, 'b': '2'}}

I originally ran into this issue while migrating our codebase from pydantic v1 to v2, and we were using the use case (2) where the config field got serialized as a tuple and I got the following error as well:
  Expected `general-fields` but got `tuple` - serialized value may not be as expected
  return self.__pydantic_serializer__.to_json(

In the v1 equivalent of the same example code, all cases listed above return {'config': {'a': 1, 'b': '2'}} which was the expected output from my side.
Example Code
from typing import Optional

from pydantic import BaseModel, ConfigDict, Field

param_1 = "allow"
param_2 = "forbid"

class BaseConfiguration(BaseModel):
    a: int = Field(default=1)

    model_config = ConfigDict(extra=param_1)

class SubConfiguration(BaseConfiguration):
    b: str = Field(default="2")

    model_config = ConfigDict(extra=param_2)

param_3 = BaseConfiguration

class MyModel(BaseModel):
    config: Optional[param_3] = Field(default=None)

    model_config = ConfigDict(validate_assignment=True)

sub_config = SubConfiguration()
my_model = MyModel(config=sub_config)
print(my_model.model_dump())

Python, Pydantic & OS Version
pydantic version: 2.6.4
        pydantic-core version: 2.16.3
          pydantic-core build: profile=release pgo=false
                 install path: /Users/bariscandurak/.pyenv/versions/3.9.16/envs/zenml-temp/lib/python3.9/site-packages/pydantic
               python version: 3.9.16 (main, Mar 11 2024, 18:29:02)  [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)]
                     platform: macOS-13.5.1-arm64-arm-64bit
             related packages: fastapi-0.110.0 typing_extensions-4.10.0 mypy-1.7.1 pydantic-settings-2.2.1
                       commit: unknown

@bcdurak,
Thanks for your question. The reason for the discrepancy here compared to V1 behavior is because of changes in how subclasses are serialized. To achieve V1-like behavior in all of the above cases, you can use the SerializeAsAny annotation around your param3 type:
from typing import Optional

from pydantic import BaseModel, ConfigDict, Field, SerializeAsAny

param_1 = "allow"
param_2 = "forbid"

class BaseConfiguration(BaseModel):
    a: int = Field(default=1)

    model_config = ConfigDict(extra=param_1)

class SubConfiguration(BaseConfiguration):
    b: str = Field(default="2")

    model_config = ConfigDict(extra=param_2)

param_3 = SerializeAsAny[BaseConfiguration]

class MyModel(BaseModel):
    config: Optional[param_3] = Field(default=None)

    model_config = ConfigDict(validate_assignment=True)

sub_config = SubConfiguration()
my_model = MyModel(config=sub_config)
print(my_model.model_dump())

You can read more about this setting here.
Regarding the case you've linked above, the serialization warning does seem odd. Leaving this open until we figure that out...

Here's a more simple repro of this bug:
from pydantic import BaseModel, ConfigDict, Field, TypeAdapter

class Base(BaseModel):
    a: int = Field(default=1)

    model_config = ConfigDict(extra='allow')

class Sub(Base):
    b: str = Field(default="2")

    model_config = ConfigDict(extra='forbid')

sub = Sub()
print(repr(sub))
#> Sub(a=1, b='2')

print(sub.model_dump())
#> {'a': 1, 'b': '2'}

ta = TypeAdapter(Base)
result = ta.dump_python(sub)
"""
/Users/programming/pydantic_work/pydantic/pydantic/type_adapter.py:356: UserWarning: Pydantic serializer warnings:
  Expected `general-fields` but got `tuple` - serialized value may not be as expected
  return self.serializer.to_python(
"""
print(result)
#> ({'a': 1, 'b': '2'}, None)

Hey @sydney-runkle, thank you for the quick response, that was really helpful.
I will try to adapt our code in a way so that we can use SerializeAsAny in our models.

That's great news :) This was a feature heavily used in our codebase in v1, that would help us a lot.


Runtime endpoint

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/test pull-keb-build

/test pull-keb-build

/test pull-keb-build


classic-aau-report:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: This package is a template for projects written at Aalborg University. It is based on the somewhat official LaTeX template found here.
It can be used by any student at Aalborg University, as it is generic in the department- and field of study.
I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does

[x] added a typst.toml file with all required keys

[x] added a README.md with documentation for my package

[x] have chosen a license and added a LICENSE file or linked one in my README.md

[x] tested my package locally on my system and it worked

[x] excluded PDFs or README images, if any, but not the LICENSE

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks!


Is emulation currently not possible?

I am a student from South Korea with a keen interest in penetration testing through virtualization and emulation.
After reading your paper with great interest, I have a question I'd like to ask. In the paper, you mention using Firewheel for emulation, and one of the reasons cited for this choice is that it's not open-source. This led me to anticipate that your research might provide an open-source emulation solution that others could use.
However, upon further investigation, I've found that Firewheel itself is not publicly available. This leaves me wondering: how can one implement this simulation as an emulator without access to Firewheel?
I would greatly appreciate any insights or guidance you could provide on this matter. Your work is truly inspiring, and I'm eager to learn more about how I might be able to replicate or adapt your methods for my own studies.

At the moment, emulation is currently in development so it is not ready for public use yet. It is something that we are in the process of testing and using with firewheel. It is true that firewheel is not currently publicly available, so it would be difficult to use with the open-source nature of the simulator. We are looking into other possible emulation implementations for the purpose of open-sourcing, we'll update this repo with more information as we work it out. Thank you for reading our paper and checking out cyberwheel!

Thanks for the update. I'll keep an eye on this repo for future developments on the emulation implementation. Looking forward to seeing how it progresses.


--onefile parameter not compatible with projects depending on black

Tl;Dr: Building a CLI depending on black fails.
I uncovered this issue while trying to compile my brand new gha-utils CLI:
$ git clone https://github.com/kdeldycke/workflows
$ cd workflows
$ python -m pip install uv
$ uv venv
$ source .venv/bin/activate
$ uv pip install .
$ uv pip install -r ./requirements/nuitka.txt
Resolved 3 packages in 2.89s
   Built nuitka==2.3.10
Prepared 1 package in 1.33s
Installed 3 packages in 9ms
 + nuitka==2.3.10
 + ordered-set==4.1.0
 + zstandard==0.22.0

$ uv run python -m nuitka --onefile --assume-yes-for-downloads --output-filename=gha-utils-macos-arm64-build-6bc8cc8.bin gha_utils/__main__.py
warning: `uv run` is experimental and may change without warning.
Resolved 51 packages in 17ms
Audited 49 packages in 0.18ms
Nuitka-Options: Used command line options: --onefile --assume-yes-for-downloads --output-filename=gha-utils-macos-arm64-build-6bc8cc8.bin gha_utils/__main__.py
Nuitka: Starting Python compilation with Nuitka '2.3.10' on Python '3.12' commercial grade 'not installed'.
Nuitka-Plugins:anti-bloat: Not including '_bisect' automatically in order to avoid bloat, but this may cause: may slow down by using fallback implementation.
Nuitka-Plugins:anti-bloat: Not including '_json' automatically in order to avoid bloat, but this may cause: may slow down by using fallback implementation.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 15.0.0).
Nuitka-Scons: Backend linking program with 477 files (no progress information available for this stage).
Nuitka-Scons: Compiled 477 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache miss': 477
FATAL: Error, failed to locate package 'black' while trying to look up DLL dependencies, that should not happen. Please report the issue.

For the record, I produced this issue on macOS Sonoma 14.5 with the latest Nuitka
$ uv run python -m nuitka --version
2.3.10
Commercial: None
Python: 3.12.4 (main, Jun  6 2024, 18:26:44) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
Flavor: Homebrew Python
Executable: /Users/kde/workflows/.venv/bin/python
OS: Darwin
Arch: arm64
macOSRelease: 14.5
Version C compiler: /usr/bin/clang (clang 15.0.0).

BTW, the exact same configuration and compilation workflow works perfectly with 2 other CLI I maintain: Meta Package Manager and Mail Deduplicate.

This error is strange as a simple black-based script seems to compile just fine.
Given a small script named ./black_test.py:
from black.mode import TargetVersion

print("\n".join(sorted(str(v) for v in TargetVersion)))

Which returns:
$ uv run python ./black_test.py
warning: `uv run` is experimental and may change without warning.
Resolved 51 packages in 16ms
Audited 49 packages in 0.16ms
TargetVersion.PY310
TargetVersion.PY311
TargetVersion.PY312
TargetVersion.PY313
TargetVersion.PY33
TargetVersion.PY34
TargetVersion.PY35
TargetVersion.PY36
TargetVersion.PY37
TargetVersion.PY38
TargetVersion.PY39

Is compiling just fine:
$ uv run python -m nuitka ./black_test.py
warning: `uv run` is experimental and may change without warning.
Resolved 51 packages in 16ms
Audited 49 packages in 0.17ms
Nuitka-Options: Used command line options: ./black_test.py
Nuitka-Options:WARNING: You did not specify to follow or include anything but main program. Check options and make sure that is intended.
Nuitka: Starting Python compilation with Nuitka '2.3.10' on Python '3.12' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 15.0.0).
Nuitka-Scons: Backend linking program with 6 files (no progress information available for this stage).
Nuitka-Scons: Compiled 6 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache miss': 6
Nuitka: Keeping build directory 'black_test.build'.
Nuitka: Successfully created 'black_test.bin'.

And the binary returns the expected results:
$ file ./black_test.bin
./black_test.bin: Mach-O 64-bit executable arm64

$ ./black_test.bin
TargetVersion.PY310
TargetVersion.PY311
TargetVersion.PY312
TargetVersion.PY313
TargetVersion.PY33
TargetVersion.PY34
TargetVersion.PY35
TargetVersion.PY36
TargetVersion.PY37
TargetVersion.PY38
TargetVersion.PY39

Found the issue. The problem is only appearing when passing the --onefile parameter.
See the result of compiling the simple script above:
$ uv run python -m nuitka --onefile ./black_test.py
warning: `uv run` is experimental and may change without warning.
Resolved 51 packages in 18ms
Audited 49 packages in 0.16ms
Nuitka-Options: Used command line options: --onefile ./black_test.py
Nuitka: Starting Python compilation with Nuitka '2.3.10' on Python '3.12' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 15.0.0).
Nuitka-Scons: Backend linking program with 6 files (no progress information available for this stage).
Nuitka-Scons: Compiled 6 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache hit': 6
FATAL: Error, failed to locate package 'black' while trying to look up DLL dependencies, that should not happen. Please report the issue.

I'll try to dig a bit on that side of thing, in the mean time, here are verbosier output with latest uv v0.2.18:

`$ uv --verbose run python -m nuitka --report=report.xml --onefile ./black_test.py`
```shell-session
DEBUG uv 0.2.18
warning: `uv run` is experimental and may change without warning.
DEBUG Found project root: `/Users/kde/workflows`
DEBUG No workspace root found, using project root
DEBUG Discovered project `gha-utils` at: /Users/kde/workflows
DEBUG Interpreter meets the project `Requires-Python` constraint >=3.8.6
DEBUG Using request timeout of 30s
DEBUG Acquired lock for `/Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685`
DEBUG Preparing metadata for: gha-utils @ file:///Users/kde/workflows
DEBUG No static `PKG-INFO` available for: gha-utils @ file:///Users/kde/workflows (MissingPkgInfo)
DEBUG Found static `pyproject.toml` for: gha-utils @ file:///Users/kde/workflows
DEBUG No workspace root found, using project root
DEBUG Solving with installed Python version: 3.12.4
DEBUG Solving with target Python version: >=3.8.6
DEBUG Adding direct dependency: gha-utils*
DEBUG Searching for a compatible version of gha-utils @ file:///Users/kde/workflows (*)
DEBUG Adding transitive dependency for gha-utils==4.1.0: backports-strenum{python_version < '3.11'}>=1.3.1, <1.4.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: black>=24.4.2, <24.5.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: bump-my-version>=0.24.0, <0.25.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: click-extra>=4.8.3, <4.9.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: mypy>=1.10.0, <1.11.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: packaging>=24.1, <25.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: pydriller>=2.6, <3.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: pyproject-metadata>=0.8.0, <0.9.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: tomli{python_version < '3.11'}>=2.0.1, <2.1.dev0
DEBUG Adding transitive dependency for gha-utils==4.1.0: wcmatch>=8.5.2, <8.6.dev0
DEBUG Found fresh response for: https://pypi.org/simple/backports-strenum/
DEBUG Found fresh response for: https://pypi.org/simple/bump-my-version/
DEBUG Searching for a compatible version of backports-strenum{python_version < '3.11'} (>=1.3.1, <1.4.dev0)
DEBUG Selecting: backports-strenum==1.3.1 (backports_strenum-1.3.1-py3-none-any.whl)
DEBUG Adding transitive dependency for backports-strenum==1.3.1: backports-strenum==1.3.1
DEBUG Adding transitive dependency for backports-strenum==1.3.1: backports-strenum{python_version < '3.11'}==1.3.1
DEBUG Searching for a compatible version of backports-strenum{python_version < '3.11'} (==1.3.1)
DEBUG Selecting: backports-strenum==1.3.1 (backports_strenum-1.3.1-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/tomli/
DEBUG Found fresh response for: https://pypi.org/simple/wcmatch/
DEBUG Found fresh response for: https://pypi.org/simple/click-extra/
DEBUG Found fresh response for: https://pypi.org/simple/packaging/
DEBUG Found fresh response for: https://pypi.org/simple/pyproject-metadata/
DEBUG Found fresh response for: https://pypi.org/simple/pydriller/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/d6/50/56cf20e2ee5127b603b81d5a69580a1a325083e2b921aa8f067da83927c0/backports_strenum-1.3.1-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of backports-strenum (==1.3.1)
DEBUG Selecting: backports-strenum==1.3.1 (backports_strenum-1.3.1-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/black/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/91/d2/fc8d85a1eac8ace33fbcf6e05e406fd8f9e0e87d23ad7ca2a805aa8be3ad/bump_my_version-0.24.1-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of black (>=24.4.2, <24.5.dev0)
DEBUG Selecting: black==24.4.2 (black-24.4.2-cp310-cp310-macosx_10_9_x86_64.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/09/78/533ef890536e5ba0fd4f7df37482b5800ecaaceae9afc30978a1a7f88ff1/wcmatch-8.5.2-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/08/aa/cc0199a5f0ad350994d660967a8efb233fe0416e4639146c089643407ce6/packaging-24.1-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/aa/5f/bb5970d3d04173b46c9037109f7f05fc8904ff5be073ee49bb6ff00301bc/pyproject_metadata-0.8.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/85/5e/d7f5e3fc06c4caa693d785b1372de42bd7f31aab5e3b1c383f9c4f5ce9ae/PyDriller-2.6-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/a1/51/f26eb61fdd24b326c5552bd5d88a56eb9b4f107df2f7c64d393cfb1b65ed/click_extra-4.8.3-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/mypy/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/40/f6/3adc48c210527a7b651aaed43824a9b8bd04b3fb361a5227bad046e1c876/black-24.4.2-cp310-cp310-macosx_10_9_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/56/24/8a179de3ed98e1882f640d431db25a17fc5813258fded79674e475501f87/mypy-1.10.1-cp310-cp310-macosx_10_9_x86_64.whl.metadata
DEBUG Adding transitive dependency for black==24.4.2: click>=8.0.0
DEBUG Adding transitive dependency for black==24.4.2: mypy-extensions>=0.4.3
DEBUG Adding transitive dependency for black==24.4.2: packaging>=22.0
DEBUG Adding transitive dependency for black==24.4.2: pathspec>=0.9.0
DEBUG Adding transitive dependency for black==24.4.2: platformdirs>=2
DEBUG Adding transitive dependency for black==24.4.2: tomli{python_version < '3.11'}>=1.1.0
DEBUG Adding transitive dependency for black==24.4.2: typing-extensions{python_version < '3.11'}>=4.0.1
DEBUG Searching for a compatible version of bump-my-version (>=0.24.0, <0.25.dev0)
DEBUG Selecting: bump-my-version==0.24.1 (bump_my_version-0.24.1-py3-none-any.whl)
DEBUG Adding transitive dependency for bump-my-version==0.24.1: click*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: pydantic>=2.0.0
DEBUG Adding transitive dependency for bump-my-version==0.24.1: pydantic-settings*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: questionary*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: rich-click*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: rich*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: tomlkit*
DEBUG Adding transitive dependency for bump-my-version==0.24.1: wcmatch>=8.5.1
DEBUG Found fresh response for: https://pypi.org/simple/click/
DEBUG Searching for a compatible version of click-extra (>=4.8.3, <4.9.dev0)
DEBUG Selecting: click-extra==4.8.3 (click_extra-4.8.3-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/mypy-extensions/
DEBUG Adding transitive dependency for click-extra==4.8.3: boltons>=24.0.0, <25.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: click>=8.1.4, <9.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: cloup>=3.0.5, <4.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: commentjson>=0.9.0, <0.10.0
DEBUG Adding transitive dependency for click-extra==4.8.3: mergedeep>=1.3.4, <2.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: pyyaml>=6.0.0, <7.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: regex>=2024.4.16, <2025.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: requests>=2.28.2, <3.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: tabulate>=0.9, <0.10
DEBUG Adding transitive dependency for click-extra==4.8.3: tabulate[widechars]>=0.9, <0.10
DEBUG Adding transitive dependency for click-extra==4.8.3: tomli{python_version < '3.11'}>=2.0.1, <3.0.0
DEBUG Adding transitive dependency for click-extra==4.8.3: wcmatch>=8.5, <9.0
DEBUG Adding transitive dependency for click-extra==4.8.3: xmltodict>=0.13.0, <0.14.0
DEBUG Found fresh response for: https://pypi.org/simple/platformdirs/
DEBUG Searching for a compatible version of mypy (>=1.10.0, <1.11.dev0)
DEBUG Selecting: mypy==1.10.1 (mypy-1.10.1-cp310-cp310-macosx_10_9_x86_64.whl)
DEBUG Adding transitive dependency for mypy==1.10.1: typing-extensions>=4.1.0
DEBUG Adding transitive dependency for mypy==1.10.1: mypy-extensions>=1.0.0
DEBUG Adding transitive dependency for mypy==1.10.1: tomli{python_version < '3.11'}>=1.1.0
DEBUG Found fresh response for: https://pypi.org/simple/typing-extensions/
DEBUG Searching for a compatible version of packaging (>=24.1, <25.dev0)
DEBUG Selecting: packaging==24.1 (packaging-24.1-py3-none-any.whl)
DEBUG Searching for a compatible version of pydriller (>=2.6, <3.dev0)
DEBUG Selecting: pydriller==2.6 (PyDriller-2.6-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/pathspec/
DEBUG Adding transitive dependency for pydriller==2.6: gitpython*
DEBUG Adding transitive dependency for pydriller==2.6: pytz*
DEBUG Adding transitive dependency for pydriller==2.6: types-pytz*
DEBUG Adding transitive dependency for pydriller==2.6: lizard*
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/00/2e/d53fa4befbf2cfa713304affc7ca780ce4fc1fd8710527771b58311a3229/click-8.1.7-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of pyproject-metadata (>=0.8.0, <0.9.dev0)
DEBUG Selecting: pyproject-metadata==0.8.0 (pyproject_metadata-0.8.0-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/pydantic-settings/
DEBUG Adding transitive dependency for pyproject-metadata==0.8.0: packaging>=19.0
DEBUG Found fresh response for: https://pypi.org/simple/questionary/
DEBUG Searching for a compatible version of tomli{python_version < '3.11'} (>=2.0.1, <2.1.dev0)
DEBUG Selecting: tomli==2.0.1 (tomli-2.0.1-py3-none-any.whl)
DEBUG Adding transitive dependency for tomli==2.0.1: tomli==2.0.1
DEBUG Adding transitive dependency for tomli==2.0.1: tomli{python_version < '3.11'}==2.0.1
DEBUG Searching for a compatible version of tomli{python_version < '3.11'} (==2.0.1)
DEBUG Selecting: tomli==2.0.1 (tomli-2.0.1-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/rich-click/
DEBUG Found fresh response for: https://pypi.org/simple/tomlkit/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/2a/e2/5d3f6ada4297caebe1a2add3b126fe800c96f56dbe5d1988a2cbe0b267aa/mypy_extensions-1.0.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/rich/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/68/13/2aa1f0e1364feb2c9ef45302f387ac0bd81484e9c9a4c5688a322fbdfd08/platformdirs-4.2.2-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/boltons/
DEBUG Found fresh response for: https://pypi.org/simple/mergedeep/
DEBUG Found fresh response for: https://pypi.org/simple/commentjson/
DEBUG Found fresh response for: https://pypi.org/simple/cloup/
DEBUG Found fresh response for: https://pypi.org/simple/tabulate/
DEBUG Found fresh response for: https://pypi.org/simple/xmltodict/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/26/9f/ad63fc0248c5379346306f8668cda6e2e2e9c95e01216d2b8ffd9ff037d0/typing_extensions-4.12.2-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/pyyaml/
DEBUG Found fresh response for: https://pypi.org/simple/requests/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/cc/20/ff623b09d963f88bfde16306a54e12ee5ea43e9b597108672ff3a408aad6/pathspec-0.12.1-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/pydantic/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e8/4f/aad03d5f711717d94d7de9684cb542343b392df1ad6889118636674fc983/pydantic_settings-2.3.4-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/gitpython/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/0b/e7/2dd8f59d1d328773505f78b85405ddb1cfe74126425d076ce72e65540b8b/questionary-2.0.1-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/pytz/
DEBUG Found fresh response for: https://pypi.org/simple/lizard/
DEBUG Found fresh response for: https://pypi.org/simple/types-pytz/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/97/75/10a9ebee3fd790d20926a90a2547f0bf78f371b2f13aa822c759680ca7b9/tomli-2.0.1-py3-none-any.whl.metadata
DEBUG Acquired lock for `/Users/kde/Library/Caches/uv/built-wheels-v3/pypi/commentjson/0.9.0`
DEBUG Searching for a compatible version of tomli (==2.0.1)
DEBUG Selecting: tomli==2.0.1 (tomli-2.0.1-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/c6/ea/5a0c5a8e6532e971983d1b0fc99268eb66a10f489da35d9022ce01044191/rich_click-1.8.3-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of wcmatch (>=8.5.2, <8.6.dev0)
DEBUG Selecting: wcmatch==8.5.2 (wcmatch-8.5.2-py3-none-any.whl)
DEBUG Adding transitive dependency for wcmatch==8.5.2: bracex>=2.1.1
DEBUG Searching for a compatible version of click (>=8.1.4, <9.0.0)
DEBUG Selecting: click==8.1.7 (click-8.1.7-py3-none-any.whl)
DEBUG Adding transitive dependency for click==8.1.7: colorama{platform_system == 'Windows'}*
DEBUG Searching for a compatible version of mypy-extensions (>=1.0.0)
DEBUG Selecting: mypy-extensions==1.0.0 (mypy_extensions-1.0.0-py3-none-any.whl)
DEBUG Searching for a compatible version of pathspec (>=0.9.0)
DEBUG Selecting: pathspec==0.12.1 (pathspec-0.12.1-py3-none-any.whl)
DEBUG Searching for a compatible version of platformdirs (>=2)
DEBUG Selecting: platformdirs==4.2.2 (platformdirs-4.2.2-py3-none-any.whl)
DEBUG Searching for a compatible version of typing-extensions{python_version < '3.11'} (>=4.0.1)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/73/6d/b5406752c4e4ba86692b22fab0afed8b48f16bdde8f92e1d852976b61dc6/tomlkit-0.12.5-py3-none-any.whl.metadata
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions==4.12.2
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions{python_version < '3.11'}==4.12.2
DEBUG Searching for a compatible version of typing-extensions (==4.12.2)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/regex/
DEBUG Searching for a compatible version of typing-extensions{python_version < '3.11'} (==4.12.2)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Searching for a compatible version of pydantic (>=2.0.0)
DEBUG Selecting: pydantic==2.7.4 (pydantic-2.7.4-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/87/67/a37f6214d0e9fe57f6ae54b2956d550ca8365857f42a1ce0392bb21d9410/rich-13.7.1-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/46/35/e50d4a115f93e2a3fbf52438435bb2efcf14c11d4fcd6bdcd77a6fc399c9/boltons-24.0.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/2c/19/04f9b178c2d8a15b076c8b5140708fa6ffc5601fb6f1e975537072df5b2a/mergedeep-1.3.4-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/96/1a/5a2a4fbf6c95f11b079f02d7b191377ea4509f5e442887e4c7c026bc56d3/cloup-3.0.5-py2.py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/40/44/4a5f08c96eb108af5cb50b41f76142f0afa346dfa99d5296fe7202a11854/tabulate-0.9.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/94/db/fd0326e331726f07ff7f40675cd86aa804bfd2e5016c727fa761c934990e/xmltodict-0.13.0-py2.py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/96/06/4beb652c0fe16834032e54f0956443d4cc797fe645527acee59e7deaa0a2/PyYAML-6.0.1-cp310-cp310-macosx_10_9_x86_64.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/f9/9b/335f9764261e915ed497fcdeb11df5dfd6f7bf257d4a6a2a686d80da4d54/requests-2.32.3-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/17/ba/1b65c9cbc49e0c7cd1be086c63209e9ad883c2a409be4746c21db4263f41/pydantic-2.7.4-py3-none-any.whl.metadata
DEBUG Adding transitive dependency for pydantic==2.7.4: annotated-types>=0.4.0
DEBUG Adding transitive dependency for pydantic==2.7.4: pydantic-core==2.18.4
DEBUG Adding transitive dependency for pydantic==2.7.4: typing-extensions>=4.6.1
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e9/bd/cc3a402a6439c15c3d4294333e13042b915bbeab54edc457c723931fed3f/GitPython-3.1.43-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/9c/3d/a121f284241f08268b21359bd425f7d4825cffc5ac5cd0e1b3d82ffd2b10/pytz-2024.1-py2.py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/ef/4b/557cbe718f0550de5656f7480600989ddfc0279db15e90d9cdc38cb8e61d/lizard-1.17.10-py2.py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e8/8d/f5dc5239d59bb4a7b58e2b6d0dc6f2c2ba797b110f83cdda8479508c63dd/types_pytz-2<IP_ADDRESS>40417-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/bracex/
DEBUG Found fresh response for: https://pypi.org/simple/colorama/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/92/c0/3560006e0f4f0658a5c5be457102f8d8a9577c31b23c893421da8fbac657/regex-2024.5.15-cp310-cp310-macosx_10_9_universal2.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/c0/76/c4aa9e408dbacee3f4de8e6c5417e5f55de7e62fb5a50300e1233a2c9cb5/commentjson-0.9.0.tar.gz
DEBUG Found fresh response for: https://pypi.org/simple/annotated-types/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/2b/f5/8f99837b32e2badc189382774dbe6227fa01e1e928a7eff857fdc89d8a75/bracex-2.4-py3-none-any.whl.metadata
DEBUG Using cached metadata for: commentjson==0.9.0
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/78/b6/6307fbef88d9b5ee7421e68d78a9f162e0da4900bc5f5793f6d3d0e34fb8/annotated_types-0.7.0-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/pydantic-core/
DEBUG Searching for a compatible version of pydantic-core (==2.18.4)
DEBUG Selecting: pydantic-core==2.18.4 (pydantic_core-2.18.4-cp310-cp310-macosx_10_12_x86_64.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/4d/73/af096181c7aeaf087c23f6cb45a545a1bb5b48b6da2b6b2c0c2d7b34f166/pydantic_core-2.18.4-cp310-cp310-macosx_10_12_x86_64.whl.metadata
DEBUG Adding transitive dependency for pydantic-core==2.18.4: typing-extensions>=4.6.0, <4.7.0 | >4.7.0
DEBUG Searching for a compatible version of pydantic-settings (*)
DEBUG Selecting: pydantic-settings==2.3.4 (pydantic_settings-2.3.4-py3-none-any.whl)
DEBUG Adding transitive dependency for pydantic-settings==2.3.4: pydantic>=2.7.0
DEBUG Adding transitive dependency for pydantic-settings==2.3.4: python-dotenv>=0.21.0
DEBUG Searching for a compatible version of questionary (*)
DEBUG Selecting: questionary==2.0.1 (questionary-2.0.1-py3-none-any.whl)
DEBUG Adding transitive dependency for questionary==2.0.1: prompt-toolkit>=2.0, <=3.0.36
DEBUG Searching for a compatible version of rich-click (*)
DEBUG Selecting: rich-click==1.8.3 (rich_click-1.8.3-py3-none-any.whl)
DEBUG Adding transitive dependency for rich-click==1.8.3: click>=7
DEBUG Adding transitive dependency for rich-click==1.8.3: rich>=10.7
DEBUG Adding transitive dependency for rich-click==1.8.3: typing-extensions*
DEBUG Searching for a compatible version of rich (>=10.7)
DEBUG Selecting: rich==13.7.1 (rich-13.7.1-py3-none-any.whl)
DEBUG Adding transitive dependency for rich==13.7.1: markdown-it-py>=2.2.0
DEBUG Adding transitive dependency for rich==13.7.1: pygments>=2.13.0, <3.0.0
DEBUG Adding transitive dependency for rich==13.7.1: typing-extensions{python_version < '3.9'}>=4.0.0, <5.0
DEBUG Found fresh response for: https://pypi.org/simple/python-dotenv/
DEBUG Searching for a compatible version of typing-extensions{python_version < '3.9'} (>=4.0.0, <5.0)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions==4.12.2
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions{python_version < '3.9'}==4.12.2
DEBUG Searching for a compatible version of typing-extensions{python_version < '3.9'} (==4.12.2)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Searching for a compatible version of tomlkit (*)
DEBUG Selecting: tomlkit==0.12.5 (tomlkit-0.12.5-py3-none-any.whl)
DEBUG Searching for a compatible version of boltons (>=24.0.0, <25.0.0)
DEBUG Selecting: boltons==24.0.0 (boltons-24.0.0-py3-none-any.whl)
DEBUG Searching for a compatible version of cloup (>=3.0.5, <4.0.0)
DEBUG Selecting: cloup==3.0.5 (cloup-3.0.5-py2.py3-none-any.whl)
DEBUG Adding transitive dependency for cloup==3.0.5: click>=8.0, <9.0
DEBUG Adding transitive dependency for cloup==3.0.5: typing-extensions{python_version <= '3.8'}*
DEBUG Searching for a compatible version of typing-extensions{python_version <= '3.8'} (*)
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions==4.12.2
DEBUG Adding transitive dependency for typing-extensions==4.12.2: typing-extensions{python_version <= '3.8'}==4.12.2
DEBUG Searching for a compatible version of typing-extensions{python_version <= '3.8'} (==4.12.2)
DEBUG Found fresh response for: https://pypi.org/simple/prompt-toolkit/
DEBUG Selecting: typing-extensions==4.12.2 (typing_extensions-4.12.2-py3-none-any.whl)
DEBUG Searching for a compatible version of commentjson (>=0.9.0, <0.10.0)
DEBUG Selecting: commentjson==0.9.0 (commentjson-0.9.0.tar.gz)
DEBUG Adding transitive dependency for commentjson==0.9.0: lark-parser>=0.7.1, <0.8.0
DEBUG Searching for a compatible version of mergedeep (>=1.3.4, <2.0.0)
DEBUG Selecting: mergedeep==1.3.4 (mergedeep-1.3.4-py3-none-any.whl)
DEBUG Searching for a compatible version of pyyaml (>=6.0.0, <7.0.0)
DEBUG Selecting: pyyaml==6.0.1 (PyYAML-6.0.1-cp310-cp310-macosx_10_9_x86_64.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/6a/3e/b68c118422ec867fa7ab88444e1274aa40681c606d59ac27de5a5588f082/python_dotenv-1.0.1-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/pygments/
DEBUG Searching for a compatible version of regex (>=2024.4.16, <2025.0.0)
DEBUG Selecting: regex==2024.5.15 (regex-2024.5.15-cp310-cp310-macosx_10_9_universal2.whl)
DEBUG Found fresh response for: https://pypi.org/simple/markdown-it-py/
DEBUG Searching for a compatible version of requests (>=2.28.2, <3.0.0)
DEBUG Selecting: requests==2.32.3 (requests-2.32.3-py3-none-any.whl)
DEBUG Adding transitive dependency for requests==2.32.3: charset-normalizer>=2, <4
DEBUG Adding transitive dependency for requests==2.32.3: idna>=2.5, <4
DEBUG Adding transitive dependency for requests==2.32.3: urllib3>=1.21.1, <3
DEBUG Adding transitive dependency for requests==2.32.3: certifi>=2017.4.17
DEBUG Searching for a compatible version of tabulate[widechars] (>=0.9, <0.10)
DEBUG Selecting: tabulate==0.9.0 (tabulate-0.9.0-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/eb/37/791f1a6edd13c61cac85282368aa68cb0f3f164440fdf60032f2cc6ca34e/prompt_toolkit-3.0.36-py3-none-any.whl.metadata
DEBUG Adding transitive dependency for tabulate==0.9.0: tabulate==0.9.0
DEBUG Adding transitive dependency for tabulate==0.9.0: tabulate[widechars]==0.9.0
DEBUG Searching for a compatible version of tabulate (==0.9.0)
DEBUG Selecting: tabulate==0.9.0 (tabulate-0.9.0-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/f7/3f/01c8b82017c199075f8f788d0d906b9ffbbc5a47dc9918a945e13d5a2bda/pygments-2.18.0-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of tabulate[widechars] (==0.9.0)
DEBUG Selecting: tabulate==0.9.0 (tabulate-0.9.0-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/lark-parser/
DEBUG Adding transitive dependency for tabulate==0.9.0: wcwidth*
DEBUG Searching for a compatible version of xmltodict (>=0.13.0, <0.14.0)
DEBUG Selecting: xmltodict==0.13.0 (xmltodict-0.13.0-py2.py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/42/d7/1ec15b46af6af88f19b8e5ffea08fa375d433c998b8a7639e76935c14f1f/markdown_it_py-3.0.0-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of gitpython (*)
DEBUG Selecting: gitpython==3.1.43 (GitPython-3.1.43-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/idna/
DEBUG Adding transitive dependency for gitpython==3.1.43: gitdb>=4.0.1, <5
DEBUG Searching for a compatible version of pytz (*)
DEBUG Selecting: pytz==2024.1 (pytz-2024.1-py2.py3-none-any.whl)
DEBUG Searching for a compatible version of types-pytz (*)
DEBUG Selecting: types-pytz==2<IP_ADDRESS>40417 (types_pytz-2<IP_ADDRESS>40417-py3-none-any.whl)
DEBUG Searching for a compatible version of lizard (*)
DEBUG Selecting: lizard==1.17.10 (lizard-1.17.10-py2.py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/certifi/
DEBUG Searching for a compatible version of bracex (>=2.1.1)
DEBUG Selecting: bracex==2.4 (bracex-2.4-py3-none-any.whl)
DEBUG Searching for a compatible version of colorama{platform_system == 'Windows'} (*)
DEBUG Selecting: colorama==0.4.6 (colorama-0.4.6-py2.py3-none-any.whl)
DEBUG Adding transitive dependency for colorama==0.4.6: colorama==0.4.6
DEBUG Adding transitive dependency for colorama==0.4.6: colorama{platform_system == 'Windows'}==0.4.6
DEBUG Found fresh response for: https://pypi.org/simple/urllib3/
DEBUG Searching for a compatible version of colorama{platform_system == 'Windows'} (==0.4.6)
DEBUG Selecting: colorama==0.4.6 (colorama-0.4.6-py2.py3-none-any.whl)
DEBUG Acquired lock for `/Users/kde/Library/Caches/uv/built-wheels-v3/pypi/lark-parser/0.7.8`
DEBUG Found fresh response for: https://pypi.org/simple/charset-normalizer/
DEBUG Found fresh response for: https://pypi.org/simple/wcwidth/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/e5/3e/741d8c82801c347547f8a2a06aa57dbb1992be9e948df2ea0eda2c8b79e8/idna-3.7-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://pypi.org/simple/gitdb/
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/5b/11/1e78951465b4a225519b8c3ad29769c49e0d8d157a070f681d5b6d64737f/certifi-2024.6.2-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/34/b8/aa7d6cf2d5efdd2fcd85cf39b33584fe12a0f7086ed451176ceb7fb510eb/lark-parser-0.7.8.tar.gz
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/ca/1c/89ffc63a9605b583d5df2be791a27bc1a42b7c32bab68d3c8f2f73a98cd4/urllib3-2.2.2-py3-none-any.whl.metadata
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/d1/d6/3965ed04c63042e047cb6a3e6ed1a63a35087b6a609aa3a15ed8ac56c221/colorama-0.4.6-py2.py3-none-any.whl.metadata
DEBUG Searching for a compatible version of colorama (==0.4.6)
DEBUG Selecting: colorama==0.4.6 (colorama-0.4.6-py2.py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/2b/61/095a0aa1a84d1481998b534177c8566fdc50bb1233ea9a0478cd3cc075bd/charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_universal2.whl.metadata
DEBUG Searching for a compatible version of annotated-types (>=0.4.0)
DEBUG Selecting: annotated-types==0.7.0 (annotated_types-0.7.0-py3-none-any.whl)
DEBUG Using cached metadata for: lark-parser==0.7.8
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/fd/84/fd2ba7aafacbad3c4201d395674fc6348826569da3c0937e75505ead3528/wcwidth-0.2.13-py2.py3-none-any.whl.metadata
DEBUG Adding transitive dependency for annotated-types==0.7.0: typing-extensions{python_version < '3.9'}>=4.0.0
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/fd/5b/8f0c4a5bb9fd491c277c21eff7ccae71b47d43c4446c9d0c6cff2fe8c2c4/gitdb-4.0.11-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of python-dotenv (>=0.21.0)
DEBUG Selecting: python-dotenv==1.0.1 (python_dotenv-1.0.1-py3-none-any.whl)
DEBUG Searching for a compatible version of prompt-toolkit (>=2.0, <=3.0.36)
DEBUG Selecting: prompt-toolkit==3.0.36 (prompt_toolkit-3.0.36-py3-none-any.whl)
DEBUG Adding transitive dependency for prompt-toolkit==3.0.36: wcwidth*
DEBUG Searching for a compatible version of markdown-it-py (>=2.2.0)
DEBUG Selecting: markdown-it-py==3.0.0 (markdown_it_py-3.0.0-py3-none-any.whl)
DEBUG Adding transitive dependency for markdown-it-py==3.0.0: mdurl>=0.1, <1.dev0
DEBUG Searching for a compatible version of pygments (>=2.13.0, <3.0.0)
DEBUG Selecting: pygments==2.18.0 (pygments-2.18.0-py3-none-any.whl)
DEBUG Searching for a compatible version of lark-parser (>=0.7.1, <0.8.0)
DEBUG Selecting: lark-parser==0.7.8 (lark-parser-0.7.8.tar.gz)
DEBUG Searching for a compatible version of charset-normalizer (>=2, <4)
DEBUG Selecting: charset-normalizer==3.3.2 (charset_normalizer-3.3.2-cp310-cp310-macosx_10_9_universal2.whl)
DEBUG Found fresh response for: https://pypi.org/simple/mdurl/
DEBUG Searching for a compatible version of idna (>=2.5, <4)
DEBUG Selecting: idna==3.7 (idna-3.7-py3-none-any.whl)
DEBUG Searching for a compatible version of urllib3 (>=1.21.1, <3)
DEBUG Selecting: urllib3==2.2.2 (urllib3-2.2.2-py3-none-any.whl)
DEBUG Searching for a compatible version of certifi (>=2017.4.17)
DEBUG Selecting: certifi==2024.6.2 (certifi-2024.6.2-py3-none-any.whl)
DEBUG Searching for a compatible version of wcwidth (*)
DEBUG Selecting: wcwidth==0.2.13 (wcwidth-0.2.13-py2.py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/b3/38/89ba8ad64ae25be8de66a6d463314cf1eb366222074cfda9ee839c56a4b4/mdurl-0.1.2-py3-none-any.whl.metadata
DEBUG Searching for a compatible version of gitdb (>=4.0.1, <5)
DEBUG Selecting: gitdb==4.0.11 (gitdb-4.0.11-py3-none-any.whl)
DEBUG Adding transitive dependency for gitdb==4.0.11: smmap>=3.0.1, <6
DEBUG Searching for a compatible version of mdurl (>=0.1, <1.dev0)
DEBUG Selecting: mdurl==0.1.2 (mdurl-0.1.2-py3-none-any.whl)
DEBUG Found fresh response for: https://pypi.org/simple/smmap/
DEBUG Searching for a compatible version of smmap (>=3.0.1, <6)
DEBUG Selecting: smmap==5.0.1 (smmap-5.0.1-py3-none-any.whl)
DEBUG Found fresh response for: https://files.pythonhosted.org/packages/a7/a5/10f97f73544edcdef54409f1d839f6049a0d79df68adbc1ceb24d1aaca42/smmap-5.0.1-py3-none-any.whl.metadata
DEBUG Tried 52 versions: annotated-types 1, backports-strenum 1, black 1, boltons 1, bracex 1, bump-my-version 1, certifi 1, charset-normalizer 1, click 1, click-extra 1, cloup 1, colorama 1, commentjson 1, gha-utils 1, gitdb 1, gitpython 1, idna 1, lark-parser 1, lizard 1, markdown-it-py 1, mdurl 1, mergedeep 1, mypy 1, mypy-extensions 1, packaging 1, pathspec 1, platformdirs 1, prompt-toolkit 1, pydantic 1, pydantic-core 1, pydantic-settings 1, pydriller 1, pygments 1, pyproject-metadata 1, python-dotenv 1, pytz 1, pyyaml 1, questionary 1, regex 1, requests 1, rich 1, rich-click 1, smmap 1, tabulate 1, tomli 1, tomlkit 1, types-pytz 1, typing-extensions 1, urllib3 1, wcmatch 1, wcwidth 1, xmltodict 1
DEBUG Split  took 0.016s
Resolved 52 packages in 18ms
DEBUG Using request timeout of 30s
DEBUG Requirement already installed: annotated-types==0.7.0
DEBUG Requirement already installed: black==24.4.2
DEBUG Requirement already installed: boltons==24.0.0
DEBUG Requirement already installed: bracex==2.4
DEBUG Requirement already installed: bump-my-version==0.24.1
DEBUG Requirement already installed: certifi==2024.6.2
DEBUG Requirement already installed: charset-normalizer==3.3.2
DEBUG Requirement already installed: click==8.1.7
DEBUG Requirement already installed: click-extra==4.8.3
DEBUG Requirement already installed: cloup==3.0.5
DEBUG Requirement already installed: commentjson==0.9.0
DEBUG Requirement already installed: gha-utils==4.1.0 (from file:///Users/kde/workflows)
DEBUG Requirement already installed: gitdb==4.0.11
DEBUG Requirement already installed: gitpython==3.1.43
DEBUG Requirement already installed: idna==3.7
DEBUG Requirement already installed: lark-parser==0.7.8
DEBUG Requirement already installed: lizard==1.17.10
DEBUG Requirement already installed: markdown-it-py==3.0.0
DEBUG Requirement already installed: mdurl==0.1.2
DEBUG Requirement already installed: mergedeep==1.3.4
DEBUG Requirement already installed: mypy==1.10.1
DEBUG Requirement already installed: mypy-extensions==1.0.0
DEBUG Requirement already installed: packaging==24.1
DEBUG Requirement already installed: pathspec==0.12.1
DEBUG Requirement already installed: platformdirs==4.2.2
DEBUG Requirement already installed: prompt-toolkit==3.0.36
DEBUG Requirement already installed: pydantic==2.7.4
DEBUG Requirement already installed: pydantic-core==2.18.4
DEBUG Requirement already installed: pydantic-settings==2.3.4
DEBUG Requirement already installed: pydriller==2.6
DEBUG Requirement already installed: pygments==2.18.0
DEBUG Requirement already installed: pyproject-metadata==0.8.0
DEBUG Requirement already installed: python-dotenv==1.0.1
DEBUG Requirement already installed: pytz==2024.1
DEBUG Requirement already installed: pyyaml==6.0.1
DEBUG Requirement already installed: questionary==2.0.1
DEBUG Requirement already installed: regex==2024.5.15
DEBUG Requirement already installed: requests==2.32.3
DEBUG Requirement already installed: rich==13.7.1
DEBUG Requirement already installed: rich-click==1.8.3
DEBUG Requirement already installed: smmap==5.0.1
DEBUG Requirement already installed: tabulate==0.9.0
DEBUG Requirement already installed: tomlkit==0.12.5
DEBUG Requirement already installed: types-pytz==2<IP_ADDRESS>40417
DEBUG Requirement already installed: typing-extensions==4.12.2
DEBUG Requirement already installed: urllib3==2.2.2
DEBUG Requirement already installed: wcmatch==8.5.2
DEBUG Requirement already installed: wcwidth==0.2.13
DEBUG Requirement already installed: xmltodict==0.13.0
DEBUG Unnecessary package: nuitka==2.3.10
DEBUG Unnecessary package: ordered-set==4.1.0
DEBUG Unnecessary package: zstandard==0.22.0
Audited 49 packages in 0.42ms
DEBUG Using Python 3.12.4 interpreter at: /Users/kde/workflows/.venv/bin/python3
DEBUG Running `python -m nuitka --report=report.xml --onefile ./black_test.py`
Nuitka-Options: Used command line options: --report=report.xml --onefile ./black_test.py
Nuitka: Starting Python compilation with Nuitka '2.3.10' on Python '3.12' commercial grade 'not installed'.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 15.0.0).
Nuitka-Scons: Backend linking program with 6 files (no progress information available for this stage).
Nuitka-Scons: Compiled 6 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache hit': 6
FATAL: Error, failed to locate package 'black' while trying to look up DLL dependencies, that should not happen. Please report the issue.
Nuitka-Reports: Compilation report written to file 'report.xml'.
```

`report.xml`
```xml

```

It would be required to see, how they let the Python interpreter know to find things, most probably some .pth file, or some in site.py or the like, there debug traces don't speak of that at all. But /Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685 might contain stuff, but could also get deleted afterwards.

I just cleared out all my pip/uv/venv/nuitka caches lying around my system and made sure I was running the last version of each. This did not solved the issue which is still persisting.
Note that I also have the same exact issue with the same workflow run within an isolated GitHub action runner: https://github.com/kdeldycke/workflows/actions/runs/9739698397/job/26875394037
A re-run in this clean environment is creating the cache at:
(...)
DEBUG Acquired lock for `/Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685`
(...)

Here is the content of that folder:
$ tree /Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685
Permissions  Size User Group Date Modified    Date Created     Name
drwxr-xr-x      - kde  staff 2024-07-01 11:40 2024-07-01 11:40  /Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685/
drwxr-xr-x      - kde  staff 2024-07-01 11:40 2024-07-01 11:40 ├──  8_OTRHQcudv_KNUMLcmAe/
lrwxr-xr-x      - kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  gha_utils-4.1.0-py3-none-any -> /Users/kde/Library/Caches/uv/archive-v0/u2dUzxqWkDvDUtDB4fkcp/
.rw-r--r--  8.3Ki kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  gha_utils-4.1.0-0.editable-py3-none-any.whl
.rw-------    261 kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  └──  metadata.msgpack
.rw-r--r--      0 kde  staff 2024-07-01 11:40 2024-07-01 11:40 ├──  .lock
.rw-------     36 kde  staff 2024-07-01 11:40 2024-07-01 11:40 └──  revision.rev

And some other folders of interests:
$ tree /Users/kde/Library/Caches/uv/archive-v0/u2dUzxqWkDvDUtDB4fkcp/
Permissions  Size User Group Date Modified    Date Created     Name
drwxr-xr-x      - kde  staff 2024-07-01 11:40 2024-07-01 11:40  /Users/kde/Library/Caches/uv/archive-v0/u2dUzxqWkDvDUtDB4fkcp/
drwxr-xr-x      - kde  staff 2024-07-01 11:40 2024-07-01 11:40 ├──  gha_utils-4.1.0.dist-info/
.rw-r--r--     54 kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  entry_points.txt
.rw-r--r--   17Ki kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  METADATA
.rw-r--r--    586 kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  RECORD
.rw-r--r--     10 kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  ├──  top_level.txt
.rw-r--r--     91 kde  staff 2024-07-01 11:40 2024-07-01 11:40 │  └──  WHEEL
.rw-r--r--     89 kde  staff 2024-07-01 11:40 2024-07-01 11:40 ├──  __editable__.gha_utils-4.1.0.pth
.rw-r--r--  3.3Ki kde  staff 2024-07-01 11:40 2024-07-01 11:40 └──  __editable___gha_utils_4_1_0_finder.py

$ tree /Users/kde/Library/Caches/uv/built-wheels-v3/path/83112afe12350685
Permissions Size User Group Date Modified    Date Created     Name
drwxr-xr-x     - kde  staff 2024-07-01 11:39 2024-07-01 11:39  /Users/kde/Library/Caches/uv/built-wheels-v3/path/83112afe12350685/
drwxr-xr-x     - kde  staff 2024-07-01 11:39 2024-07-01 11:39 ├──  HLviKAAhpkVx6iP79oH1C/
lrwxr-xr-x     - kde  staff 2024-07-01 11:39 2024-07-01 11:39 │  ├──  gha_utils-4.1.0-py3-none-any -> /Users/kde/Library/Caches/uv/archive-v0/--91Ggn4ER6mqnUJKi5b7/
.rw-r--r--  26Ki kde  staff 2024-07-01 11:39 2024-07-01 11:39 │  ├──  gha_utils-4.1.0-py3-none-any.whl
.rw-------   261 kde  staff 2024-07-01 11:39 2024-07-01 11:39 │  └──  metadata.msgpack
.rw-r--r--     0 kde  staff 2024-07-01 11:39 2024-07-01 11:39 ├──  .lock
.rw-------    36 kde  staff 2024-07-01 11:39 2024-07-01 11:39 └──  revision.rev

Here is the content of __editable__.gha_utils-4.1.0.pth:
$ cat /Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685/8_OTRHQcudv_KNUMLcmAe/gha_utils-4.1.0-py3-none-any/__editable__.gha_utils-4.1.0.pth
import __editable___gha_utils_4_1_0_finder; __editable___gha_utils_4_1_0_finder.install()%

And the content of:

/Users/kde/Library/Caches/uv/built-wheels-v3/editable/83112afe12350685/8_OTRHQcudv_KNUMLcmAe/gha_utils-4.1.0-py3-none-any/__editable___gha_utils_4_1_0_finder.py
from __future__ import annotations
import sys
from importlib.machinery import ModuleSpec, PathFinder
from importlib.machinery import all_suffixes as module_suffixes
from importlib.util import spec_from_file_location
from itertools import chain
from pathlib import Path

MAPPING: dict[str, str] = {'gha_utils': '/Users/kde/workflows/gha_utils'}
NAMESPACES: dict[str, list[str]] = {}
PATH_PLACEHOLDER = '__editable__.gha_utils-4.1.0.finder' + ".__path_hook__"

class _EditableFinder:  # MetaPathFinder
    @classmethod
    def find_spec(cls, fullname: str, _path=None, _target=None) -> ModuleSpec | None:
        # Top-level packages and modules (we know these exist in the FS)
        if fullname in MAPPING:
            pkg_path = MAPPING[fullname]
            return cls._find_spec(fullname, Path(pkg_path))

        # Handle immediate children modules (required for namespaces to work)
        # To avoid problems with case sensitivity in the file system we delegate
        # to the importlib.machinery implementation.
        parent, _, child = fullname.rpartition(".")
        if parent and parent in MAPPING:
            return PathFinder.find_spec(fullname, path=[MAPPING[parent]])

        # Other levels of nesting should be handled automatically by importlib
        # using the parent path.
        return None

    @classmethod
    def _find_spec(cls, fullname: str, candidate_path: Path) -> ModuleSpec | None:
        init = candidate_path / "__init__.py"
        candidates = (candidate_path.with_suffix(x) for x in module_suffixes())
        for candidate in chain([init], candidates):
            if candidate.exists():
                return spec_from_file_location(fullname, candidate)
        return None

class _EditableNamespaceFinder:  # PathEntryFinder
    @classmethod
    def _path_hook(cls, path) -> type[_EditableNamespaceFinder]:
        if path == PATH_PLACEHOLDER:
            return cls
        raise ImportError

    @classmethod
    def _paths(cls, fullname: str) -> list[str]:
        paths = NAMESPACES[fullname]
        if not paths and fullname in MAPPING:
            paths = [MAPPING[fullname]]
        # Always add placeholder, for 2 reasons:
        # 1. __path__ cannot be empty for the spec to be considered namespace.
        # 2. In the case of nested namespaces, we need to force
        #    import machinery to query _EditableNamespaceFinder again.
        return [*paths, PATH_PLACEHOLDER]

    @classmethod
    def find_spec(cls, fullname: str, _target=None) -> ModuleSpec | None:
        if fullname in NAMESPACES:
            spec = ModuleSpec(fullname, None, is_package=True)
            spec.submodule_search_locations = cls._paths(fullname)
            return spec
        return None

    @classmethod
    def find_module(cls, _fullname) -> None:
        return None

def install():
    if not any(finder == _EditableFinder for finder in sys.meta_path):
        sys.meta_path.append(_EditableFinder)

    if not NAMESPACES:
        return

    if not any(hook == _EditableNamespaceFinder._path_hook for hook in sys.path_hooks):
        # PathEntryFinder is needed to create NamespaceSpec without private APIS
        sys.path_hooks.append(_EditableNamespaceFinder._path_hook)
    if PATH_PLACEHOLDER not in sys.path:
        sys.path.append(PATH_PLACEHOLDER)  # Used just to trigger the path hook

I guess, we need to pick up MAPPING: dict[str, str] = {'gha_utils': '/Users/kde/workflows/gha_utils'} NAMESPACES: dict[str, list[str]] = {} from there, but I don't see how this relates to your black not being found for DLL location, but I noticed black is a bad package, and maybe, you would have more luck with develop, since I did a bunch for extension module packages, but maybe not, I have to assume you didn't try that.

Yeah... black seems badly packaged. Looking at its latest changes upstream, nothing significant regarding packaging has been committed so I doubt black's develop version will fix anything.
In the mean time, I revisited my usage of black and realized it was a bit over-the-top. I managed to remove my dependency on it completely.
I also noticed some irregularities a couple of years ago regarding the way entry points are used by Nuitka. But it was at a time I was heavily relying on Poetry. I'll probably revisit this issue soon, in which case I'll post my observations in an issue here. But the Tl;Dr was that I needed an intermediate __main__.py file.
So anyway, let's close this issue. And thanks @kayhayen for investing that much time looking at my issue! 🤗

I guess we are not done yet. Eliminating my black dependency, I now have the error with my mypy dependency (which has been there all along since I started documented this bug here). 😅
See:
$ uv run python  -m nuitka --onefile --assume-yes-for-downloads --output-filename=gha-utils-macos-arm64-build-6ac269c.bin gha_utils/__main__.py
warning: `uv run` is experimental and may change without warning.
Resolved 49 packages in 11ms
Audited 46 packages in 0.70ms
Nuitka-Options: Used command line options: --onefile --assume-yes-for-downloads --output-filename=gha-utils-macos-arm64-build-6ac269c.bin gha_utils/__main__.py
Nuitka: Starting Python compilation with Nuitka '2.3.10' on Python '3.12' commercial grade 'not installed'.
Nuitka-Plugins:anti-bloat: Not including '_bisect' automatically in order to avoid bloat, but this may cause: may slow down by using fallback implementation.
Nuitka-Plugins:anti-bloat: Not including '_json' automatically in order to avoid bloat, but this may cause: may slow down by using fallback implementation.
Nuitka: Completed Python level compilation and optimization.
Nuitka: Generating source code for C backend compiler.
Nuitka: Running data composer tool for optimal constant value handling.
Nuitka: Running C compilation via Scons.
Nuitka-Scons: Backend C compiler: clang (clang 15.0.0).
Nuitka: Downloading 'https://nuitka.net/ccache/v4.2.1/ccache-4.2.1.zip'.
Nuitka: Extracting to '/Users/runner/Library/Caches/Nuitka/downloads/ccache/v4.2.1/ccache'
Nuitka-Scons: Backend linking program with 477 files (no progress information available for this stage).
Nuitka-Scons: Compiled 477 C files using ccache.
Nuitka-Scons: Cached C files (using ccache) with result 'cache miss': 477
FATAL: Error, failed to locate package 'mypy' while trying to look up DLL dependencies, that should not happen. Please report the issue.

Source: https://github.com/kdeldycke/workflows/actions/runs/9743400784/job/26886783676

So, 3.12 has an issue with packages that load modules, it's not working with Nuitka anymore, and can't be made to work. We got a plan to have our own fork called "Standalone Backend Python" that allows Nuitka to load these packages properly.
I am not convinced the issue exists when using 3.11, except that black might have implicit dependencies not yet ironed out, I think I gave up on that when I ran my compile library tests a while ago. So I am closing this as a duplicate now.

OK that's fair. It seems the issue has been fixed on my side anyway by massive update of all my dependencies. So let's forget about this issue.


load_internal_assets vs embedded_asset

Assets v2 introduced some new embedded asset features. Should bevy_shader_utils switch?
https://bevyengine.org/news/bevy-0-12/#embedded-assets

tried again to use embedded_asset. I was only able to make it work for Materials. "utility shaders" which offer functions like the noise functions are still on load_internal_asset in 0.7 as I wasn't able to import them after embedding. Notably Bevy's internal shaders are also still using load_internal_asset.

just noting that the status of this hasn't progressed yet


When using --allow-unplayable-formats but not --fixup, yt-dlp still outputs the warning that --fixup was ignored

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
[debug] Command-line config: ['--verbose', '--cookies', '/home/weird/cookies.txt', '--allow-unplayable-formats', '-F', 'https://www.facebook.com/478492418989679/videos/1320343201817221']
WARNING: --fixup is ignored since --allow-unplayable-formats was given
[debug] Loading archive file None
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] yt-dlp version 2<IP_ADDRESS> (zip)
[debug] Python version 3.5.3 (CPython 64bit) - Linux-4.9.0-14-amd64-x86_64-with-debian-9.13
[debug] exe versions: ffmpeg N-54690-g682990a849-static, ffprobe N-54690-g682990a849-static, rtmpdump 2.4
[debug] Proxy map: {}
[facebook]<PHONE_NUMBER>817221: Downloading webpage
[debug] Sort order given by user:
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, vcodec:vp9.2(10), acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[download] Downloading playlist:<PHONE_NUMBER>817221
[facebook] playlist<PHONE_NUMBER>817221: Collected 1 video ids (downloading 1 of them)
[download] Downloading video 1 of 1
[info] Available formats for<PHONE_NUMBER>817221:
ID               EXT RESOLUTION |   TBR PROTO | VCODEC        VBR ACODEC     ABR  ASR    NOTE
---------------- --- ---------- - ----- ----- - ----------- ----- --------- ---- ------- -----------------------------
486634785670353a m4a audio only |  135k https |                   mp4a.40.2 135k 48000Hz DASH audio, m4a_dash, 48000Hz
918757108893872v mp4 256x144    |  112k https | avc1.64000c  112k                        DASH video, mp4_dash
774603623172819v mp4 426x240    |  267k https | avc1.640015  267k                        DASH video, mp4_dash
729443354422455v mp4 640x360    |  527k https | avc1.64001e  527k                        DASH video, mp4_dash
526187182114431v mp4 854x480    | 1045k https | avc1.64001f 1045k                        DASH video, mp4_dash
240211284431385v mp4 1280x720   | 2082k https | avc1.640020 2082k                        DASH video, mp4_dash
[download] Finished downloading playlist:<PHONE_NUMBER>817221

Description
Minor bug, but annoying:
When using --allow-unplayable-formats but not --fixup, yt-dlp still outputs the warning that --fixup was ignored.
It also appears to be missing the color,  WARNING: is usually in yellow.

When using --allow-unplayable-formats but not --fixup, yt-dlp still outputs the warning that --fixup was ignored.

The default of fixup is detect_or_warn, which is why the message is shown. Will fix it

It also appears to be missing the color, WARNING: is usually in yellow.

The warning is issued before the options are fully parsed and so we don't know whether or not to output color. It would be quite difficult to fix this


Move isDefaultAppConfigured to public API for FIRApp

This change moves isDefaultConfigured into FIRApp's public API
Why this is desirable:
Flutterfire plugins want to register the default app when the application launches. However, to prevent an exception when using multiple plugins they need to avoid calling[FIRApp configure] multiple times. To do this, they check if [FIRApp defaultApp] is nil. Unfortunately, it produces a spurious log message.

The default Firebase app has not yet been configured. Add [FIRApp configure]; (FirebaseApp.configure() in Swift) to your application initialization.

Having access to the isDefaultAppConfigured API would allow Flutterfire plugins to determine whether the default app is configured without calling [FIRApp defaultApp], avoiding the confusing log message.
The alternative is that a mechanism could be developed for each plugin to determine if the default app has been configured by a plugin already. If there are third-party plugins that also want to talk to Firebase, they'll all need to use this mechanism to avoid the error message.

@ryanwilson I don't think we ship the private headers in our binary builds of FirebaseCore so this wouldn't work.

We don't, but IIRC you can check for the existence of the default app via [FIRApp appNamed:@"__FIRAPP_DEFAULT"] and it won't log a warning in console.

We don't plan to do more binary builds from this source base.

[FIRApp appNamed:@"__FIRAPP_DEFAULT"] is a good solution


Unable to install version 0.3.0 running pip on Ubuntu

I have a previous version of appman, and I'm trying to install the new one. I tried using pip uninstall appman and gave me an error.
Then:
pip install appman
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: appman in /usr/local/lib/python3.8/dist-packages (0.1.1)
Requirement already satisfied: click<9.0.0,>=8.0.1 in /home/username/.local/lib/python3.8/site-packages (from appman) (8.0.1)
Requirement already satisfied: pyyaml<6.0.0,>=5.3.1 in /usr/lib/python3/dist-packages (from appman) (5.3.1)
However, when I try to run appman it gives me the following error:
appman add
bash: /home/username/.local/bin/appman: No such file or directory
Any help is appreciated :)

I was able to install it by using the commnad:
sudo python3.9 -m pip install appman
However, when I run it I get the following error:
appman add
bash: /home/username/.local/bin/appman: No such file or directory

I was able to install it by using the commnad:
sudo python3.9 -m pip install appman
pip should be called without sudo, like this:
python3.9 -m pip install appman

But first, try uninstalling the sudo installed package:
sudo python3.9 -m pip uninstall -y appman
And then, try installing again:
python3.9 -m pip install appman
Hope this helps

Thank yo, worked like a charm!


What is the detail procedure of manual partition?

I have seen the Kmeans procedure described in part D of Appendix, but I cannot find the manual method.
I wonder how to partition in manual method

这是来自QQ邮箱的假期自动回复邮件。

您好，我已经收到邮件，会尽快给您回复。by小溪

The results of manual method is similar with the figure below，but I don't recommend using the manual methods, since it needs more efforts than applying the K-means partition and achieves similar results with  K-means partition .

Got it. Thank you~

The results of manual method is similar with the figure below，but I don't recommend using the manual methods, since it needs more efforts than applying the K-means partition and achieves similar results with K-means partition .

Another Question, in part D of Appendix, what is exactly normalization described in line 435 of your paper. Because I cannot figure out what is exactly the 435 line in the paper, so I have to ask you.


add debug properties

Allow to activate debugging with -Djboss.debug=true instead of using jvmArguments in arquillian.xml for the use case you need some special jvmArguments and do not want to have multiple configurations just for debugging.

Sorry for the very long delay here. I was not being notified of PR's.
This looks like a feature request. I'll have to think about this. This can already be done with setting the javaVmArguments so this is just a shortcut.

I'm going to close this as it's easy enough to add this to the javaVmArguments.


As a user, I want to see a description of the app.

Components: Splash
Procedure:
1- See description of the app in the first page